Your ERP plans in weeks. Your floor runs in minutes.
That gap has a name, a standard and a list of jobs someone in your plant is doing right now, with or without software. The Lake MES Platform is MES for SyteLine. It performs manufacturing operations management functions on the SyteLine record you already run.
Four things to know
An MES is a list of jobs someone has to do
The classic shop-floor functions were named in 1997, and the list still holds. Every plant performs all of them, whether by software, by spreadsheet or by someone remembering.
Your ERP is Level 4. Every problem on this site is a Level 3 problem
The international standard puts business planning at Level 4 and manufacturing operations at Level 3. That's the boundary the standard draws. Level 4 plans in months, weeks and days. Level 3 works in days, shifts, hours and minutes.
Capture is half of it, and the workflow that acts on it is the other half
Recording what the operator did is data collection. Guiding what they do next is manufacturing operations management. A monitoring tool does the first. Every capability here is built to do both.
MES functions on the record you already run
A full MES suite is built to be the system of record for production, so two systems end up claiming the same work order. These capabilities perform the Level 3 functions inside the Level 4 system you already run, on the SyteLine record you already have.
Where each layer belongs, and who owns it
The international standard for integrating enterprise and control systems has been in place for years, and it draws the boundary for you.
Business planning and logistics
Your ERPOrder management, planning, procurement, finance. Works in months, weeks and days.
Manufacturing operations management
This is the gapDetailed scheduling, dispatching, data collection, labor, documents, quality, performance, maintenance. Works in days, shifts, hours and minutes.
Control and process
Your machinesControls, sensors and the physical process. Machine-Trak reads this layer directly, so no operator has to describe it.
Your ERP is Level 4, and it's good at Level 4. Every problem in the explorer on this site is a Level 3 problem.
Which product performs which job on the floor
The products, the design rule each one follows, and the integrations between them with their status. Lake doesn't publish a function-by-function score. This shows what each product does, and each product page and the roadmap name what it doesn't do yet.
1. Scrap becomes a case, by itself
In developmentA scrap entry at the operation raises the disposition, with the job, the operator, the machine state and the documents already attached. Nobody has to open a second system and retype the context. In development.
2. Machines open their own tickets
PlannedThe machine will detect the condition and Quality-Trak will run the response workflow, so nobody has to carry the problem from one system to the other. Planned.
3. Quality forms, document enabled
Planned 2027Inspection records, certificates and change documents will file themselves against the job record, which is where an auditor looks. This needs Doc-Trak and Quality-Trak working together and is planned for 2027.
4. Cost of quality meets job cost
PlannedQuality cost will join labor and machine cost on the same job. No single product can produce that number. Quality cost on the job is planned for 2027, after the machine link.
Click any component to open its page. The lower half of each card shows what the product captures and what the workflow layer will do with it.
The ones we don't perform yet
Maintenance management. Machine state, alerts and fault history are in Machine-Trak today. The loop, where a fault opens the work order and books the cost, is planned for 2027 and belongs with the machine data. If preventive maintenance is your first problem, the platform shouldn't be your first purchase.
Calibration and gage management. Not included in Quality-Trak.
Warehouse execution. The platform doesn't cover it today. If you run a warehouse tool, keep it and let the platform read what it produces.
Why we name the gaps
You'd find the gaps during evaluation anyway. Naming them up front means the conversation starts from where you are.
Where a manufacturing operations platform goes next
This is the direction we're heading, and none of it carries a date. Some of it is being worked on, and some of it is where we think the industry should go. Ask your account team which is which.
Workforce, skills and qualification
Certification, training and capability shown by the floor data that already exists.
Maintenance execution
The machine signal exists today. The next step is the loop: the fault that opens the work order, routes the technician and books the cost.
Safety and environmental
Compliance records on the same engine as quality, so they live in one place.
Product data and engineering change upstream
Tying engineering intent to the record the floor works from.
A layer that takes action
The platform proposes an action and, within guardrails you set, takes it. This is a direction, and it isn't a product.
Everything with a date on this site is on the roadmap page, and nothing in this section has a date. If you need one of these domains this year, buy the best available tool for it and let the platform read what it produces.
What choosing a full MES suite asks of you
The best MES suites enforce process and have real depth in high-volume and regulated production. In some plants, they're the right answer. They're designed to be the system of record for production, so your routings, work orders and inventory end up in two systems that both claim them.
That's a defensible choice. It also means a second implementation, a second master data set and a second integration to maintain. This platform performs the same Level 3 functions on the Level 4 record you already run.
MES functions on the record you already run.
The nine category comparisonThe 49 Level 3 problems