Can an agent ever write to a machine?

No. The control path is not in the catalog at all, so a write to a PLC or SCADA system is not something access has to catch, it cannot be requested.

So can an agent write anything at all?

Yes, to Nightshift, never to your plant. An agent can draft a work order, propose a maintenance action, or flag an asset, and it lands in a governed Nightshift table where a person approves it before it crosses back to the MES. The agent does real work, and nothing it writes touches equipment or your system of record until a human signs off.

Do you copy our historian?

Only if you choose to. In view mode Nightshift queries the historian where it lives, so tags and work orders stay in your systems. When you ingest for speed, the copy is yours in your governed store, and the access is governed either way.

How do we prove who saw what?

Every request is on the record: the identity, the source, and what came back, queryable and exportable to your system of record.

Nightshift for Industrial Ops

Query the whole plant. Hands off the controls.

Connect the historian, MES, ERP, and maintenance systems once: reliability and ops teams and their agents query live plant data across all of it, with no warehouse to stand up. Agents draft work back into Nightshift for a human to approve, and the path that moves equipment is never in the catalog, so they do real work with zero operational risk.

Get started freeTalk to sales

Plant catalog4 sources

PIpi.historiantag stream4.2kLive

MEmes.workorders48K open1.9kGoverned

SAsap.pm1.2M rows920Governed

OEoee.warehouse60M rows210Governed

Four systems, one governed view · the agent only ever sees this

The control boundary

Agents live above the line.

The plant runs in layers. Nightshift exposes the upper ones as governed reads and leaves the layers that move equipment unreachable. The boundary is the catalog itself, not a firewall rule you hope holds.

L4ERP & asset managementSAP PM, maintenance historyGoverned read

L3MES & historianwork orders, tag streamsGoverned read

Nightshift catalogreads cross up, nothing reaches down

L2SCADA & gatewaysNot exposed

L1PLC & control logicNot exposed

L0Sensors & actuatorsNot exposed

Cross-source root cause

Find the $4.2M no dashboard could.

An agent connects Nightshift over MCP and attributes Q3 scrap and rework across SAP, Siemens, Rockwell, and Oracle, down to the line and supplier lot. No single system holds this answer: the catalog composes all four into one governed query.

The boundary

Reads cross. Writes land in Nightshift, never in the plant.

An agent reads the line through the catalog, and writes its work, a drafted work order, a proposed action, a flagged asset, into Nightshift’s own tables, where a human approves it before anything crosses back. The path that moves a machine is not exposed at all, so a wrong write to the plant is not a risk you have to catch, it is a thing that cannot happen.

reliability-agentreadsCatalogHistorian / MESallowed

reliability-agentwritesNightshift tablesheld for approval

reliability-agentwritesControl systemblocked

What agents do

Reliability agents that earn their access.

Predict the failure

Read historian tags and work-order history to flag the asset about to fail, without ever touching the controls.

Close the work order

Draft a maintenance work order into Nightshift, ready for a human to approve before it ever reaches the MES, with the technician PII column never in scope.

Answer the floor

A plant copilot that answers from live line data, scoped to the sites a crew actually runs.

Governance in plain SQL

Scope to a site, drop a column, grant read.

A governed view limits an agent to two sites and drops the technician PII column. Grant the agent read on the view, and it is the only data the agent can reach.

Scope rows and columns with a governed view
Drop PII and safety-sensitive fields
Agents write to governed Nightshift tables, never to the MES or controls

views/workorders_det.sqlview

-- workorders_det: DET sites only, technician PII dropped
create view workorders_det as
  select work_order_id, site, asset, status
  from mes_workorders
  where site in ('DET-1', 'DET-2');   -- assigned_tech_ssn not selected

grantreliability-agent → workorders_det · read

Questions the plant asks

The questions we get on the floor.

Can an agent ever write to a machine?: No. The control path is not in the catalog at all, so a write to a PLC or SCADA system is not something access has to catch, it cannot be requested.
So can an agent write anything at all?: Yes, to Nightshift, never to your plant. An agent can draft a work order, propose a maintenance action, or flag an asset, and it lands in a governed Nightshift table where a person approves it before it crosses back to the MES. The agent does real work, and nothing it writes touches equipment or your system of record until a human signs off.
Do you copy our historian?: Only if you choose to. In view mode Nightshift queries the historian where it lives, so tags and work orders stay in your systems. When you ingest for speed, the copy is yours in your governed store, and the access is governed either way.
How do we prove who saw what?: Every request is on the record: the identity, the source, and what came back, queryable and exportable to your system of record.

Put an agent on your plant data, safely.

Start free, connect a historian or MES, and watch governed reads flow to your agent in minutes.

Get started free Talk to sales

Want to look first? Take the product tour