The Lake MES Platform
The Lake MES Platform · One live job record

Follow one job from quote to invoice

This page follows a job through seven stages. At each one, it shows what happens when the floor and the record are separate, and what changes when they share one record. One live job record is the destination the platform is building toward, and each stage says what's there today and what's still to come. Shop-Trak, Doc-Trak and Fact-Trak already work on your SyteLine data today. The next direct integration, Shop-Trak and Machine-Trak, comes with Shop-Trak 2027.

Stage 1 of 7 · Estimating

The job is priced against current standards

Products in play: Fact-Trak

When the floor and the record are separate

  • Standards are folklore, averaged across machines that run the same part at different speeds
  • Setup is buried inside run, so the quote cannot separate them
  • The last overrun taught nobody anything, because its cause was never isolated

When they share one record

  • Part duration variability is visible across machines and runs, so the standard reflects reality
  • Setup and run are separate numbers because they were captured separately
  • Overruns on past jobs are traced to labor, machine and quality drivers, and quoting learns

The quote becomes the first entry on the job record.

The Five Moments

What only the whole record can do

Each of these needs at least two products sharing one job record. Each one carries its status.

Cost on the open job

Available now

Labor cost is on the job today where you use direct job costing. Machine cost joins it with the machine link, coming with Shop-Trak 2027. Quality cost on the job is planned for 2027.

Why it needs the platform: It needs labor capture, machine capture and one cost model on the same job. Any two of the three give a partial answer that a controller won't sign.

Scrap opens a quality case

In development

Scrap recorded at the station will open the Quality-Trak record, with the job, the operator and the documents already attached. In development.

Why it needs the platform: It needs the floor transaction and the quality engine to share a record. A separate quality system can't see the event that should have triggered it.

The machine files its own paperwork

Planned 2027

A machine condition will open the work order, route the technician and write the cost back. Planned 2027.

Why it needs the platform: It needs machine state, a work order and a cost model in the same place. Maintenance management is the one classic function the platform doesn't perform today.

Certification gates the clock-in

Available now

Only a qualified operator starts the operation, through the work center skills check. Available now with Shop-Trak.

Why it needs the platform: It needs the labor transaction and the qualification record to be the same system. A spreadsheet can't stop a transaction.

Performance reviews written by the floor

Planned

Reviews will draw attainment, quality and skills from the record. Planned.

Why it needs the platform: It needs a year of attributed labor and quality data, which only exists if capture was correct from the beginning.