The Lake MES Platform
The Lake MES Platform ยท The intelligence layer

Your ERP can only reason about what somebody keyed into it

That's the main problem with AI on a shop floor: the limit is usually the data, and the model comes second. This page covers what the intelligence layer does today, what it won't do, and the rules it follows.

Four things available now Three in development Platform-wide AI in development
Read This Part First

Six rules this layer operates under

Here is what happens when the model is wrong. These rules are built into the software, so you can test them.

Rule 1

The model never does the arithmetic

The whole layer rests on this rule. The language model may plan the query. The software computes the answer against SyteLine, and the model only describes the rows that came back. Every number on the screen is calculated.

Rule 2

It says when it doesn't know

Extracted values are validated against real records before they count. A page that doesn't match a record stays unmatched, and the system shows the value it tried so you can check it. Nothing is saved without showing you.

Rule 3

Every answer can be taken apart

Each answer cites its rows, and a control re-runs the underlying query and shows you the raw data. If you don't believe an answer, you can open it.

Rule 4

A human reviews anything customer facing

This is a rule. A person reads every AI output before it reaches a customer.

Rule 5

It waits for your history before it makes claims

Control limits need 20 to 25 operating days of your own data. Until then, the system shows targets and labels them as targets. Demonstration data is never presented as yours.

Rule 6

Nothing ships before it clears an accuracy gate

Every customer-facing AI claim has to pass an internal accuracy bar before we announce it, so this page lists only what has passed.

The One That Matters Most
The model may plan the query. It never does the arithmetic.

The software computes against SyteLine, and the model describes the rows that came back. Every number on your screen is calculated, which is why a controller can rely on it for job cost.

Shipping Today

Four things you can use now

These four are available now. Everything further down this page is in development.

Search or Ask AI across the documents on a record

Available nowDoc-Trak

Doc-Trak FLEX follows you through SyteLine and shows the attachments for whatever record you are on. The Search or Ask AI bar answers a plain-language question across the attachments on screen, and the answer names the files it came from, so you can open the source and check it.

It cites the files it used.

AI summaries of any attachment

Available nowDoc-Trak

Every document attached to a record can carry a generated summary, so a twelve-page supplier agreement or a multi-page certificate can be understood without opening it. The summary sits on the record beside the file.

Read the summary, open the source. Both are on the record.

Paperwork that files itself by rule

Available nowDoc-Trak

Saving rules build the path, the name and the document type from the record's own fields. Mass Scanning matches a stack to receipts, lots, serials and vouchers, with AI Match (early adopter, Doc-Trak 2026) or barcodes, and Receive with Docs files the vendor's packing slip onto the PO as part of receiving. A page that doesn't match stays unmatched.

The saving rule is the instruction, so nobody writes a prompt.

Triggers and alerts from the machine

Available nowMachine-Trak

Out-of-cycle time opens a delay event by itself, triggers and alerts fire as a condition happens, and maintenance can see how often that fault has hit this machine and others. Top alerts and events show by count and by duration, from the records.

The machine tells you when it stops.

And one we use ourselves

Lake support uses this every day. Draft answers come from a knowledge base built from real cases, and an engineer reviews every one before it goes out.

Where Your Data Goes

The question regulated shops ask first

This includes what isn't ready yet.

Your data is never training data

No SyteLine data, no customer data and no procedure content is used to train any foundation model. That's in the contract.

Read-only, and queried in place

The layer reaches SyteLine through a read-only role on an explicit allowlist, with a statement timeout and a row cap. It never writes to SyteLine, and there's no copy of your database anywhere else.

Opt in, never automatic

Document intelligence sends nothing until someone presses the button. Only the page image and the rule-driven instruction leave. Your file system and your SyteLine data stay where they are.

Whose engine

Today Lake provides and maintains the model access. Customer-owned keys and a model running inside your own environment, which is what a controlled unclassified information environment needs, are a later phase and aren't available yet.

Regulated and defense environments

Machine-Trak runs in the cloud or on premises and supports regulated environments, and most of that install base is on premises today. The current AI work doesn't cover the most restricted government tenants.

Planned, and not yet certified

Tenant isolation inside AI context, audit logging of AI output, role based access for AI features and a readiness assessment are all planned work. None of them is an attestation today, and we don't claim them as one.

In Development And Planned

What's coming

AI across the platform flags risk

In development

Jobs at risk of going late and cost drifting from standard, flagged across the platform before they become a late job or a margin miss. A person decides.

Ask the floor in plain language

In development

A plain-language query over your SyteLine data, starting with standard against actual variance by job and operation. It runs on the AI engine you sanction, under your governance.

Every number carrying where it came from

In development

Data trust tiers surfaced inside the answer: system-captured signals you can act on, values a person entered that you verify before a major decision, and derived figures whose fidelity is bounded by the weakest input underneath them.

Cost variance, decomposed

In development

A cost report tells you margin eroded. This shows where it went: setup overrun from the labor record, absorbed downtime from the machine record, and rework that was never tied back to the job.

A knowledge graph over the platform data

In development

So a question can traverse the real relationships between a job, an operation, a machine, a part and a supplier, and return the path it followed, so you can audit the reasoning.

Supplier email read against your open orders

Real, not scheduled

An add-in that reads inbound supplier mail with your SyteLine context attached, and surfaces the date change or the shortage before it becomes a stockout. Built, and paused.

Where We Actually Are

One step at a time

1. Business intelligence shows the problem
Delivered
2. Analytics explains the problem
Delivered in Fact-Trak
3. Decision support suggests the action
In development
4. A closed loop learns which actions worked
Future
5. Autonomy acts within guardrails you set
Long-term direction, with no date

We're on the third step today. Fact-Trak delivers the first two.

Restraint

Six things this layer doesn't do

  • AI for its own sake. We use a rule where a rule works, statistics where the math works, and a language model only where the problem is language.
  • Write back. The intelligence layer doesn't change your ERP. It reads and reports.
  • Workforce and shift scheduling, which we plan to cover through a partner.
  • Planning intelligence that belongs to your ERP vendor: material risk, inventory policy, supplier lead time, make against buy. That's their layer, and they're good at it.
  • Anything in human resources.
  • Act as a chatbot. If the answer needs arithmetic, the software does the arithmetic.
How This Differs From Your ERP Vendor

Both, not either

Their foundation is your ERP data, and it's good. The floor data isn't in it unless something put it there.

This layer gives your ERP vendor's AI the floor data it can't see on its own.

If the answer lives in your ERP, use theirs. If it lives in your people, your machines and your quality, use ours.

Your ERP vendor is investing in AI, and it's worth turning on. It works from the record of work. This layer works from the floor data the platform records.

How it works: the business logic lives outside the model, and the model uses it at runtime. That logic is decades of SyteLine manufacturing knowledge.

Next Step

Ask the hard question first

Ask what happens when it is wrong, ask where the number came from, and ask to see the rows behind an answer. Those three questions show whether an AI layer works.

Talk about your floorWhere this sits in the platform