Actions
Look up a history. Draft a work order. Each action has a purpose, a permission, and a limit. The assistant cannot invent a new one.
For operations, engineering, and IT
Let AI use your systems the way your people already do.
We connect an assistant to the systems you already run: ERP, service records, documents, and plant equipment. It can look things up and prepare the work. It cannot change a record, send a part, or close a case unless a named person approves it. Every step is written down.
- Request is in order
- We know who asked
- Draft, not release
- A person still approves
Connects toThe systems you already run
Sign-inThe accounts IT already manages
Runs inYour network, cloud, or plant
On recordEvery request and every approval
One layer, every system
Ten times the output. The same oversight.
The assistant does the reading, cross-checking, and first drafts that eat most of a planner's or engineer's day. Fixed rules check every entry before anyone sees it. A person signs off before anything changes. The pilot measures how much faster that routine work gets done, on your own jobs.
01What your teams get
Quote & orderRFQ to priced quote
MaintenanceAlert to work order
QualityInspection to disposition
ProductionLine stop to new schedule
02Control layer
03Systems and field equipment
ERPOrders, purchasing
MESProduction orders
Maintenance systemWork orders, spares
Quality systemNCRs, inspection
PLM & drawingsBOMs, revisions
on-device.ai agents
Instruments & equipmentSensors, controls, historian
Rules check: a deterministic check, the same input always gets the same answer. No AI judgment involved.
Person approves: a named role signs off before the system of record changes.
System and entry
The assistant prepares
Rules check, every time
A person approves
ERPQuotes, sales orders, purchase requests
A draft quote from the RFQ, the drawing, and similar past jobs.
Part number exists. Price sits inside the approved margin band. Customer credit is in good standing. Quantity is within limits.
Sales or purchasing lead releases it.
MESProduction orders and schedules
A revised schedule after a line stop or a material shortage.
Routing exists. The machine can run the part. Material is on hand. Nothing moves inside the frozen window.
Production supervisor accepts the change.
Maintenance systemWork orders and spare parts
A work order with the asset history and the right procedure attached.
Asset ID is valid. No duplicate open order. The spare is in stock. The lockout procedure is attached.
Maintenance planner or engineer releases it.
Quality systemNonconformance reports and inspection results
A draft nonconformance report with the measurements and photos as evidence.
Limits come from the controlled drawing. The lot is traceable. Every required field is filled.
Quality engineer decides the disposition. Nothing ships on the assistant's word.
PLM & drawingsBills of materials, revisions, change requests
A summary of which parts, orders, and suppliers a change would touch.
Read-only. A released revision cannot be edited.
The engineering change board decides, as it does today.
Instruments & equipmentSensor readings and history, through on-device.ai agents
Trends, drift, and the readings that back up an alert.
Read-only. The assistant can never write a setpoint or touch a control.
Control stays with operators. There is nothing to approve because nothing can be written.
How it is set up
The assistant does not get a back door into your systems.
A person asks a question. The assistant prepares an answer using only the access you have already granted. A control point checks who they are, what they may do, and whether a person must approve the next step. Only then does it reach the system of record, and only for that job.
The person
A named user asks for help in plain language.
The assistant
It decides what to look up and drafts the answer.
The control point
Who they are, what they may do, and who must approve — decided here, not by the assistant.
Your systems
ERP, service history, documents, and plant data. Looking something up and changing a record stay separate.
Looking something up is not changing it
Passwords never sit in the assistant
Every action is logged
Hard-to-undo steps need a person
What it is allowed to do
A short list. Nothing else.
The assistant does not get a login to the whole system. It gets a defined set of jobs, records, and standard procedures.
Records it may read
Manuals, asset history, and the files a person in that role is already allowed to see. Nothing beyond that role.
Standard procedures
The same steps your team already uses for triage, investigation, and shift handoff, so the assistant follows your method.
A job we would start with
From an equipment alert to a work order a person releases.
The assistant gathers the facts. An engineer decides. This is the shape of the first engagement, not a promise that the assistant runs the plant.
The alert
One asset leaves its normal range.
The history
It pulls recent readings, past cases, and the service record. It cannot change them.
The procedure
The answer cites the manual and the limits. If the manual is silent, it says so.
The judgment
If the evidence is thin, it stops. It does not guess the failed part.
The draft
It prepares the work order. It does not submit it.
The release
A named engineer approves it. Who did what stays with the case.
What IT and engineering will ask
The limits are in the system, not in a policy memo.
A careful instruction is not a control. The controls sit in front of your systems, the same way a change ticket does.
Who is allowed
The same company sign-in you already use. Each person, and the assistant, gets only the access that job needs.
What is allowed
A fixed list of actions. The assistant cannot add to it. Your rules decide, not the assistant.
Changes need a person
It may draft. A named person releases anything that writes, sends, or deletes. Asking twice does not create two changes.
When it fails
A time limit, a stop switch, and a person to call. A bad run is paused. It is not left to keep trying.
Where the data stays
Passwords stay on your side. Sensitive fields can be hidden. Nothing leaves the network you approve, and you keep the records.
The audit
Who asked, what was looked up, what was proposed, who approved it, and what happened. Ready for security and quality review.
Where it runs
In the place your risk review already accepts.
A desk pilot, a shared service inside your network, or a connection at the plant. The same rules apply in each case.
On a desk
For one person, and for questions that do not change a system.
- Stays with that person
- Uses their existing login
- The fastest way to see if the job is worth it
Inside your network
For people who share the same systems of record.
- One place to set permissions and keep the log
- Company sign-in
- Stays on your private network
At the equipment
For assets and sites that are not always online.
- Read-only at the asset
- Events are kept until the link returns
- The decision still happens in your system of record
How we know it is ready
A demo is not the test.
We grade it on work your team has already finished. Did it pick the right action, stay inside its permissions, cite the evidence, and stop when it should?
Right action chosen
Request in order
Job finished
Answer cites the record
Stayed inside its limits
Stopped when unsure
Answer comes back in time
Cost per finished job
What we can bring to the first pilot.
- Search that matches both the meaning of the question and the exact words in your records.
- A map from the asset and its sensors to the faults those sensors have pointed to before.
- A check that the answer used the evidence, including when the question is asked a different way.
- A clear “we are not sure” when the record is not enough to name a cause.
- The option to keep the AI inside your own walls.
These come from work we have already tested. We can apply them on your data. They are not a finished product you switch on.
Start with one job
Prove the result, and the controls, before you widen it.
We start with one system, one job your people already do, a clear permission, and a test built from cases your team has already closed.
Talk through a first job