Your ERP plans in weeks. Your floor runs in minutes.
That gap has a name, a standard, and a list of jobs somebody in your plant is doing right now, whether or not software is helping. The Lake MES Platform is MES for SyteLine: the manufacturing operations management functions performed on the SyteLine record you already run, rather than in a second system beside it.
Four things worth being clear about
An MES is not a product category you buy, it is a list of jobs somebody has to do
The classic shop-floor functions were named in 1997 and have not needed revising. Every plant performs all of them. The only question is whether they are performed by software, by a spreadsheet, or by a person 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 is not a criticism of your ERP, it is 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. The workflow that acts on the capture is the other half
This is the difference between a monitoring tool and an MES function. Recording what the operator did is data collection. Guiding what they do next is manufacturing operations management. Every capability here is built to do both, which is the whole design.
MES capability without MES replacement
A full MES suite is built to be the system of record for production, which means two systems end up believing they own the 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 is not a marketing frame. 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 intelligence reads this layer directly rather than asking an operator to describe it.
Your ERP is Level 4 and it is 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 does not publish a function by function score; this is what each product does, and what it does not do yet is named on each product page and on the roadmap.
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 opens a second system and retypes the context. In development.
2. Machines open their own tickets
PlannedThe machine detects the condition and Quality-Trak runs the response workflow, so detection and response stop being connected by a person who has other work. Planned.
3. Quality forms, document enabled
Planned 2027Inspection records, certificates and change documents file themselves against the same job record, which is where an auditor looks rather than where somebody filed it. Doc-Trak and Quality-Trak together, planned 2027.
4. Cost of quality meets job cost
PlannedQuality cost joins labor and machine cost on one job. This is the number the business runs on, and it is the one no single product can produce. Cost of quality on the job follows the machine link; planned.
Click any component to open its page. The lower half of each card is the design rule: what it captures, and the workflow layer that acts on the capture.
The ones we do not perform yet, named
Maintenance management. Machine state, alerts and fault history exist today in Machine-Trak. The loop, where a fault opens the work order and books the cost, does not. Ownership is settled, it belongs with the machine data, and it is in development with no date. If preventive maintenance is your first problem, this is not your first purchase.
Calibration and gage management. Not included in Quality-Trak, and that is a deliberate boundary.
Warehouse execution. Not covered today. If you run a warehouse tool, keep it and let the platform read what it produces.
Why we name the gaps
A completeness claim with no exceptions is a claim nobody believes. An evaluator will find the gaps anyway. Naming them means the conversation starts from where you actually are rather than from a claim that has to be walked back.
Where a manufacturing operations platform goes next
This is the direction of travel, and none of it carries a date. Some of it is being worked on, some of it is a view of the world we think is right, and the honest distinction between those two is not something a website can settle.
Workforce, skills and qualification
Certification, training and capability evidenced by the floor data that already exists, rather than by a spreadsheet.
Maintenance execution
Not just the machine signal, which exists today, but the loop: the fault that opens the work order, routes the technician and books the cost.
Safety and environmental
Compliance records riding the same engine as quality, so it is one surface rather than another system.
Product data and engineering change upstream
Tying engineering intent to the record the floor executes against, rather than handing the floor a document.
A layer that acts rather than reports
Where the platform proposes and, within guardrails you set, takes the action. This is a direction of travel, not a product.
Everything with a date on this site is on the roadmap page, and everything in this section has no date on purpose. If you need one of these domains this year, the honest answer is to buy the best available tool for it and let the platform read what it produces.
What choosing a full MES suite actually asks of you
The strong MES suites are strong. They enforce process, they have real depth in high volume and regulated production, and in some plants they are the right answer. What they are designed to be is the system of record for production, which means your routings, your work orders and your inventory now exist in two systems that both believe they own them.
That is a defensible choice. It is also a second implementation, a second master data set, a second integration to maintain, and a second place for the truth to diverge. The alternative is to perform the same Level 3 functions on the Level 4 record you already run, which is what this platform does.
MES capability without MES replacement.
The nine category comparisonThe 49 Level 3 problems