Your recipes are the company. We treat them that way.
Compound formulations, constructions and tolerances are the most valuable data in a tire business. Treadum keeps them in your tenant, runs decisions inside your OT network, and records every agent action in an immutable log built to survive an audit.
Aligned to the standards your quality organization already lives with
Six things we do not compromise on
Recipe and construction IP
Compound formulations, constructions and tolerance data stay inside your tenant. Retrieval is permission-aware and tenant-isolated, and no cross-tenant training occurs on your data.
OT segmentation
Inference runs on factory-edge nodes inside the OT zone. Cloud is never a dependency for a line decision, and on-premises deployment removes outbound plant traffic entirely.
Actuation limits
Writes are only possible through the setpoints your controls engineers expose, bounded by a signed control envelope with per-action risk classes and hard limits.
Immutable audit log
Every agent action records its inputs, evidence, citations, decision, outcome and approver. The log is append-only and exportable for internal and external audit.
Identity and access
SSO and SAML, SCIM provisioning, RBAC scoped to site, line and station, and separate approver roles required for envelope changes.
Release governance
Signed model and prompt bundles, per-site version pinning, golden-dataset gating in CI, and a rollback path that never depends on the production schedule.
Where data lives and where it does not
Plant data stays in the plant by default
Sensor streams, imagery, PLC telemetry and genealogy records are stored and processed at the site. In cloud-connected deployments, only signed model bundles and the aggregates you approve cross the boundary — and in on-premises mode, nothing does.
- Imagery and telemetry stored at the site by default
- Signed model bundles travel inbound through the DMZ
- Aggregate reporting is opt-in and field-level configurable
- Encryption in transit and at rest with customer-managed keys available
site_storage:
imagery: "local"
telemetry: "local"
genealogy: "local"
retention: "site policy (default 10y)"
boundary:
outbound: "none" # on-prem mode
inbound: "signed model bundles"
keys:
management: "customer-managed (optional)"A wrong model must not become a wrong action
Perception errors are inevitable at some rate. The system is designed so that an error becomes a hold or an escalation, not an out-of-spec tire — and so that every error is traceable to a model version, an input and a decision path.
- Grounding and citation checks before any recommendation is shown
- Human-in-the-loop gates per action class, graduated over time
- Continuous evaluation with golden datasets, including rare defect families
- One-key return to assist mode for any station, line or site
Evidence mapped to the standard
Treadum does not certify your plant. It makes the evidence a by-product of running the line.
| Standard | What it needs | What Treadum provides | Status |
|---|---|---|---|
| IATF 16949 | Traceability, control of nonconforming product, corrective action | Linked genealogy, NCR workflow, immutable action and approval log | Supported |
| ISO 9001 | Documented process control and records | Versioned objectives, envelopes and gated releases with records | Supported |
| DOT / TIN | Tire identification and production records | Tire-level records linked to batch, station, press and grade | Supported |
| UNECE R30 / R117 | Type approval evidence and production conformity | Construction-linked records and exportable conformity packages | Supported |
| ISO 27001 | Information security management | Control mapping available; certification in progress | [ASPIRATIONAL] |
| SOC 2 Type II | Security, availability and confidentiality controls | Control mapping available; audit planned | [ASPIRATIONAL] |
| GDPR | Personal data handling for operator records | Minimized operator data, role-scoped access, retention controls | Supported |
Certification statuses marked [ASPIRATIONAL] are targets, not current attestations. Ask for the current security pack before procurement review.
If something goes wrong
- Detect: Anomalous agent behaviour, model drift or infrastructure faults raise an alert in the same console operators already watch.
- Contain: Affected action classes are suspended automatically; agents fall back to assist mode with setpoints held at last approved values.
- Notify: Named contacts at the site and in your security organization are notified on the agreed channel within the contracted window.
- Investigate: The immutable log reconstructs exactly what was seen, proposed, approved and written, by which model version.
- Remediate: Fix, gated re-release, rollback drill and a written post-incident report with corrective actions.
How we build
Gated by evaluation, not by opinion
Every model and prompt change is gated in CI by golden datasets that include rare defect families. A regression on splice-open or bare spot blocks the release regardless of aggregate metrics.
Least privilege, by default
Treadum staff have no standing access to customer plants. Support access is time-boxed, customer-approved, session-recorded and logged in the same immutable log.
Rollback drills
Rollback is exercised on a schedule at every site, not assumed. Evidence of the drill lands in the audit log.
Signed artifacts
Model, container and firmware bundles are signed and verified at the edge before they can be promoted.
Coordinated disclosure
Report a vulnerability to security@treadum.com. We acknowledge within one business day and work to a coordinated timeline.
Quality and IT/OT leaders on trust
“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.
Security by the numbers
What security reviewers ask
No. Recipe, construction and tolerance data is tenant-isolated and never used to train models served to other customers. Cross-site sharing happens only within your own group, and only for the model families you explicitly enable.
No. Safety instrumented systems and interlocks are out of scope by design. Treadum writes only to process setpoints your controls engineers expose, and the plant safety layer remains fully independent.
Minimally. Builder and engineer performance memory is scoped to role-based identifiers, access is restricted, retention is configurable and sites that require full anonymization can enable it.
Yes. Request the security pack and we will return completed questionnaires, architecture documentation, the control mapping and current certification status.
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.