The Lake MES Platform
The Lake MES Platform ยท Implementation

What an implementation takes, including the part that's yours

One product takes 30 to 120 days. The full platform takes six to nine months. Data quality and operator adoption drive the range more than the software install does, so the first phase is mostly your work.

Phase 1

Data readiness

Mostly you, with Lake alongside

Routings, work centers and standards get reconciled against what the floor actually does. This phase decides whether the rest of the program works, and it's the phase most proposals skip.

Yours
  • Routings and operation sequences that match reality
  • Work center and resource definitions
  • Standards you're willing to be measured against
  • A decision about who owns data quality afterwards
Lake's
  • The reconciliation method and the validation routines
  • The list of what's wrong, in priority order
  • A straight estimate of how long your list will take
Phase 2

Capture on the floor

Shared

Labor and machine capture go live at the workstation. Operators are the first users, because nothing above the floor works if the floor doesn't adopt it.

Yours
  • Time on the floor with your supervisors as well as your IT lead
  • A decision on identification method per person
  • Patience through the first two weeks, when the data will surprise somebody
Lake's
  • Installation, configuration and floor training
  • Machine interfaces, including the older assets
  • No formal machine training until there are about two weeks of data, so the first conversation is about your numbers
Phase 3

Answers and activation

Mostly Lake, with you deciding

Analysis and planning run on data the floor trusts. You're already entitled to the products in your tier, so adding the next one means deciding to install it.

Yours
  • Decisions about which questions matter most
  • One owner per subject area who will defend the definitions
Lake's
  • Subject areas, reports and role views
  • Scheduling method and validation routines
  • Installation and configuration of whatever comes next, without a new sales cycle
The Part Most Proposals Leave Out
Phase one is mostly yours

Routings, work centers and standards have to be reconciled against what the floor actually does, and software can't do that. Lake brings the method, the validation routines and a list of what's wrong, in priority order.

Activation

Switching on the next product

Every product in your tier is yours from day one. You decide what to install and when. Activation is how a product gets switched on: we install and configure it and train your administrator to run it.

What every activation includes

  • The standard configuration for the product, done with your team
  • Train-the-trainer for your lead users, so the knowledge stays in your building
  • Included configuration hours for any product that is new to your account

As time allows

Further configuration, in the order you choose, as the included hours permit.

Quoted separately

Work beyond the standard configuration is quoted before it starts, as a fixed fee wherever possible. Included hours are scheduled during our business hours, 8:00 AM to 5:00 PM Central, Monday through Friday. Work you need outside those hours is quoted in advance at our after-hours rate.

What activation includes, product by product

Shop-Trak

Shop-Trak parameters; employee, item, work center and workstation profiles; shift, indirect and scrap codes; standard labels; daily transaction administration; train-the-trainer on the Labor, Materials and Info tabs and Visual Dispatch.

Quoted separately: payroll integration and custom labels.

Doc-Trak

Doc-Trak parameters and polling; security; the standard repository and archiving plan; starter document saving rules, form output profiles and virtual rules; utilities; train-the-trainer on attachments and emailing reports.

Machine-Trak

Your tier's included machine licenses, installed by Lake on your network over standard connections (FOCAS, MTConnect, OPC, MQTT), with no extra hardware. Lake installs the Machine-Trak licenses included in your tier, and you pay nothing if you decide not to use them. Machines you keep using may require a setup fee.

A two-month cloud trial of the included licenses is available. After the trial, hosting is a paid service.

Fact-Trak

On Infor's multi-tenant cloud, a data streaming pipeline from Infor is required first. Your account team confirms what your version supports and what the activation covers.

Quality-Trak activation is scoped with your account team. Vantage is expected early 2027 and is included in every tier when it ships. Vantage on the web works with SyteLine 9.01 and later. The fully integrated platform, including Vantage inside your SyteLine, Doc-Trak and Shop-Trak screens, runs on current versions.

Before we start

Prerequisites are listed per product. The common ones: SyteLine 9 or later; machines on your network with assigned IP addresses and the required ports open; a Windows server for machine data collection; email enabled and user email addresses loaded for Quality-Trak.

How to ask

Talk to your account team, or use Talk about your floor. An activation request form is coming. It will route your request to the activation desk instead of the support queue.

After go-live

Check-ins and activation help are part of the subscription. Support runs through one portal for every product.

Before You Start

Five things that stall the first ninety days

  • Being several ERP releases behind. Getting current is a services conversation before it's a platform conversation. A project that skips it tends to stall. The minimum for every platform product is SyteLine 9.
  • Routings and standards nobody has reviewed in years. This is phase one, and it can't be skipped.
  • Machine-Trak runs in the cloud or on premises, including alongside cloud ERP.
  • No data streaming pipeline in place for Fact-Trak on cloud ERP.
  • Treating the operator as the last user instead of the first. If the floor doesn't adopt it, nothing above it works.
How To Start Small

A pilot that actually tells you something

  • Pick machine types, not machine counts. Two or three different control generations tell you more than ten identical machines.
  • Pick the work center where the argument is loudest. If the data settles that argument, adoption follows.
  • Run the first two weeks without formal training on the machine data, so the first real conversation is about your numbers.
  • Expect the first two weeks of data to surprise somebody.
  • Lake installs the Machine-Trak licenses included in your tier, and you pay nothing if you decide not to use them. Machines you keep using may require a setup fee.
Talk about a pilot