Everything needed to run the loop
Written for controls engineers, process engineers, quality systems teams and platform engineers. Start with the quickstart, then the connector guide, then the envelope reference.
Guides by audience
The first four documents
Quickstart
Install the CLI, start the simulator, enable an agent in shadow mode and watch findings stream. Twenty minutes, no line access required.
ReadConnector guide
Connect PLCs, historians, inspection machines and MES with OPC UA, MQTT Sparkplug B, Modbus TCP, EtherNet/IP, gRPC or file drop.
ReadEnvelope reference
The control envelope schema, action classes, risk levels, approver roles, signing process and rollback semantics.
ReadAutonomy gates
What has to be true to move a station from shadow to assist to bounded autonomy, and how each gate is measured.
ReadBy topic
Agent configuration
Enabling agents, scoping them to stations, setting objectives and weights, and configuring escalation paths and approvers.
Model deployment
Pushing models to the edge, golden-dataset evaluation, promotion between modes, version pinning and rollback.
Genealogy queries
Forward and backward tracing, recall scoping, evidence attachment and export package formats.
Reports and exports
Shift reports, quality summaries, audit packages and webhook payload schemas with replay semantics.
Observability
Health, latency and throughput metrics for edge nodes, agents and connectors, plus alert routing.
Administration
SSO and SAML setup, SCIM provisioning, RBAC scopes, approver policy and support-access controls.
What a site installation involves
Hardware, network and the first connector
A site installation begins with edge nodes placed inside the OT zone, network rules that allow reads from the systems in scope, and a first connector proving the stream end to end. Nothing writes until the envelope is signed.
- Jetson-class nodes at stations, GPU server for site aggregation
- Read access to PLCs, historian and inspection systems
- Signed model bundles delivered inbound through the DMZ
- Write access enabled only after envelope signing
site: "plant-nl-02"
edge_nodes:
- id: "edge-01" role: "mixing+extrusion"
- id: "edge-02" role: "building+inspection"
- id: "edge-03" role: "curing+uniformity"
aggregation:
gpu_server: "site-gpu-01"
storage: "local, 90d hot / 10y cold"
mode: shadowWhat we integrate with today
| System class | Examples | Direction | Status |
|---|---|---|---|
| PLC and control | Siemens S7, Rockwell ControlLogix | Read + envelope writes | Supported |
| Historian | OSIsoft PI, Aveva, InfluxDB | Read | Supported |
| Inspection | X-ray, shearography, uniformity machines | Read | Supported (vendor dependent) |
| Vision | GigE Vision, line-scan cameras, frame grabbers | Read | Supported |
| MES and QMS | Vendor MES, in-house systems | Read + write findings and NCRs | Supported |
| Robotics | ROS 2, Isaac, AGV fleet managers | Read + envelope writes | Supported |
| Identity | SAML 2.0, OIDC, SCIM 2.0 | Read | Supported |
How teams usually work through the docs
- Simulator: Platform engineers run the quickstart and build against the simulator before any site work begins.
- Connectors: Controls engineers land read-only connectors and validate stream alignment against known events.
- Shadow: Process engineers review agent proposals daily and code the disagreements.
- Envelope: Safety, process and operations review the envelope reference and sign the first version.
- Operate: Quality and supervision move to the reports, genealogy and audit-export sections.
On documentation and onboarding
“We had three people watching X-ray images and still shipped uniformity rejects. Treadum flagged the cord shift at the building drum, not four hours later at final inspection.”
“The cure agent found 40 seconds of margin on a construction we had run the same way for eleven years. It proved it in shadow mode before it touched a press.”
“Genealogy is the part I did not expect to care about. Every tire now has a linked record from batch to grade, and audit prep went from weeks to an afternoon.”
[PLACEHOLDER] Design-partner quotes are illustrative until pilot references are published.
Documentation commitments
Working with the documentation
Partially. The conceptual documentation, API reference and envelope schema are available on request; site-specific runbooks live inside your tenant because they describe your plant.
Yes, and we strongly encourage it. The schema and the semantics of every action class are documented specifically so a safety review can happen before deployment, not after.
Yes — role-based onboarding for controls, process, quality and platform teams, delivered on site during installation and refreshed at each expansion.
Email docs@treadum.com or raise it in your shared channel. Corrections to the envelope reference are treated as priority issues.
Put one cell on autonomy in 90 days
Pick one wedge — splice inspection, X-ray defect detection, cure-state optimization or uniformity prediction. We baseline it, run shadow mode, then graduate to bounded autonomy under a signed control envelope.
Pilots start in shadow mode. No line changes until accuracy and safety gates pass.