One control plane for every plant in the group
Standardize the loop across sites without flattening what makes each plant different. Shared models where they help, site isolation where it matters, and one governance model your quality and IT/OT organizations can actually sign.
Built for multi-site tire groups
What changes when you go from one plant to six
Factory edge fleet
Provision, monitor, update and roll back edge nodes across every site from one place, with signed release bundles and pinned per-site versions.
Model portfolio
Group models for shared constructions and compounds, site models for local reality. You choose what is shared and what stays isolated, per family.
Cross-site benchmarking
Compare yield, scrap, uniformity, cure energy and takt across plants on a like-for-like basis, with the causes attached rather than inferred.
Identity and access
SSO and SAML, SCIM provisioning, RBAC scoped to site, line and station, and separate approver roles for envelope changes.
Group governance
One envelope policy framework, per-site signatures, versioned objectives and an immutable action log that survives an external audit.
Named support
24/7 support with a named team, joint quarterly business reviews and a shared roadmap for constructions and compounds specific to your group.
Standardize the loop, not the plant
One plant proves it. The rest inherit it.
The first site does the hard work: connectors, baselines, envelope policy, gates and evidence. Subsequent sites inherit the templates and typically reach assist mode far faster, because the pattern — not just the software — is already proven.
- Connector and envelope templates reused per site
- Objectives and gates standardized, thresholds set locally
- Cross-site model transfer for shared constructions
- Rollout tracked against a group-level metric, not per-plant anecdotes
Priced to expand, not to gate
Enterprise agreements land between $700k and $9M ACV with usage ramps and outcome-based components on the highest-value workflows — yield, scrap, uniformity and first-pass yield. Floor pricing is protected; discounts are traded for term length and reference rights.
- Multi-year agreements with usage ramps
- Annual prepay discount of roughly 15–20%
- Outcome share on measurable improvement for enterprise deals
- Expansion by cells, lines, modules, sites and autonomy level
# illustrative structure
term "3 years"
sites_year_1 2 # reference + fast follower
sites_year_3 6
base_platform "factory tier per site"
usage "per cell above plan limits"
outcome_share "scrap + first-pass yield delta"
custom_models "compound, construction, tolerance"
deployment "on-prem + factory edge fleet"What we run with you, and what you run
Joint operating rhythm
Weekly model and override review with process engineering, monthly gate review with quality and safety, quarterly envelope re-signing and expansion scoping with the plant director.
The envelope
Your process, safety and operations leaders sign every control envelope and can revoke any action class instantly.
The fleet
We keep edge nodes patched, models gated and releases reversible, with health visible to your team in the same console.
The data
Recipes, constructions, tolerances, imagery and the models trained on them belong to you and stay in your tenant.
The roadmap
Group-specific constructions, compounds and integrations are scoped into a shared roadmap with committed dates.
Where Treadum runs
| Option | Line decisions | Training | Outbound data | Typical fit |
|---|---|---|---|---|
| Factory edge + cloud | Edge | Cloud | Model bundles and aggregates | Most sites |
| Factory edge + private cloud | Edge | Your VPC | None outside your tenancy | Groups with cloud standards |
| Fully on-premises | Edge | On-site GPU | None | Recipe-sensitive or air-gapped sites |
| Hybrid group | Edge per site | Central | Signed bundles inbound only | Multi-country groups |
How enterprise deals actually get signed
- Technical fit: Systems, protocols and segmentation reviewed with IT/OT; integration scope written down before commercials.
- Security review: Architecture, tenancy, IP protection, logging and on-premises options assessed against your risk register.
- Paid pilot: One site, one wedge, defined success metric and an agreed baseline, with commercial conversion terms pre-agreed.
- Reference site: Pilot converts to a Factory subscription; templates, envelope policy and gates are formalized.
- Group agreement: Multi-year expansion with usage ramps, outcome components and a named support team.
Enterprise buyers on the rollout model
“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.
The numbers behind the model
Targets from the Treadum business model; actuals are reported to customers during quarterly reviews.
What procurement and IT ask
Only if you say so. Model sharing is configured per family and per site. Many groups share defect perception models and keep cure and rheology models site-isolated, because those encode local equipment reality.
You keep your data and your trained model artifacts, exported in open formats. The control envelope reverts to your existing setpoints, and the line runs exactly as it did before Treadum was installed.
Yes, with fully on-premises deployment. Model bundles arrive as signed artifacts through your DMZ, inbound only, and no plant data leaves the site.
Against a baseline captured during shadow mode, agreed in writing, with an audit trail from the same immutable log that governs actions. Neither side is reconstructing numbers after the fact.
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.