Fleet autonomy policy
One policy model for the fleet with per-plant override and approval chains. Tag allow-lists, qualified envelopes and limits reviewed and versioned like code. Locked parameters cannot be unlocked by policy.
Multi-plant OEMs and platform fleets standardise on Chassira for the governance as much as the control: one autonomy policy with per-plant override, one audit trail, fleet-managed plant-edge nodes, and weld, paint, geometry and battery models that stay private to each plant and program.
Illustrative scenario: Plant BIW-2 · EV crossover body shop to end of line · shift 1, one approval gate
Items marked planned follow the 6 to 12 month roadmap.
One policy model for the fleet with per-plant override and approval chains. Tag allow-lists, qualified envelopes and limits reviewed and versioned like code. Locked parameters cannot be unlocked by policy.
Named approvers, role-based access down to the tag. Planned for the 6 to 12 month release.
Model versions promoted by line with canary rollout and automatic fallback across every plant. On-prem options for regulated plants.
Per-plant process models built on the plant's own programs, materials and joint families and kept private to that tenant.
First-time-through, rework, repaint, downtime and warranty compared across plants without moving designs or control plans across tenant boundaries. Data-network tiers are planned.
A dedicated deployment engineer, quarterly model review per plant and SLA terms set per agreement.
The plant edge is always local. The control plane can be cloud, on-prem or absent.
| Option | Plant edge | Control plane | For |
|---|---|---|---|
| Cloud control plane | Jetson nodes at the cell | Chassira cloud, per-tenant isolation | Most plants; cloud training optional |
| On-prem control plane | Jetson nodes at the cell | In the plant's data centre | Regulated OEM plants, strict program controls |
| Plant-edge only | Jetson nodes at the cell | In the plant, no external link | Programs that cannot leave the site |
| Edge-only degradation | Returns to controller last known-good | Unreachable | What happens on any control-plane loss |
One policy model, one audit trail, one benchmark across every process in every plant, with the weld, paint, geometry and battery models kept private to each plant and program.
Every Chassira run is an ordered, inspectable sequence. This is run_41a9c2 on Plant BIW-2 · EV crossover body shop to end of line · shift 1. Scenario completes in 10 steps with one approval gate. Weld schedule change on robot W-14 approved by the body-shop launch engineer, framing offset held inside the envelope, booth humidity trimmed before the predicted dirt defects appeared, one pack held at marriage on a torque trace, and the shift released with full as-built records.
Plant Orchestrator · Pulled the shift build sequence, program control plan and qualified envelopes from MES: 412 bodies, four trim variants, weld schedule set W-rev 7, framing targets per station, paint colour blocks, torque specifications. Locked every safety-critical parameter as read-only.
Vehicle-and-Line Twin · Simulated 18 candidate weld-sequence, framing-offset and booth-window combinations on the plant twin, ranked on predicted body geometry, expulsion risk at robot W-14, paint defect map and takt against launch cadence.
Stamp-and-Form · Blank feed on press line P-3 adjusted by 0.4 mm and lubricant dose raised 3 percent for the new coil lot as springback risk on the rear door inner climbed. Panel dimension held inside the window; genealogy handed to framing.
Plant Orchestrator · Candidate #6 lowers weld current 2 percent and adds 20 ms hold on robot W-14 to cut predicted expulsion. Weld schedules are crash-safety critical and stay with a human, so the change was held for the body-shop launch engineer and approved at 06:14:52.
Weld-and-Join · Approved schedule 7b applied on W-14. Current and force traces confirmed inside the window on the first 40 bodies; predicted expulsion risk fell from 0.31 to 0.06 and no geometry debt was introduced at the adjacent seams.
Frame-and-Geometry · Framing station FS-1 offset corrected by 0.3 mm on the left B-pillar datum inside the qualified envelope as in-line measurement trended toward the tolerance edge. Gap-and-flush vision confirmed the correction on the next 25 bodies.
Paint-and-Finish · Booth B-2 humidity trimmed 2 points and airflow rebalanced for the dark-colour block as the defect model predicted dirt on horizontal panels. Film build held inside the window on the first colour block.
Powertrain-and-Battery · Pack PK-1182 held at marriage after a torque-to-yield trace on fastener 7 fell outside the specification curve. Routed to rework with the trace attached; torque specification untouched, as always.
Quality-and-Anomaly · Gap-and-flush and paint-defect cameras, weld and torque traces and test results fused per body. Two paint dirt defects localised to booth B-2 zone 3 before the humidity trim took effect; both routed to spot repair, none escaped to final.
EOL-and-Calibrate · End of line proved alignment, ADAS calibration, leak, brake, roll and functional tests on every vehicle; two ADAS retests sequenced inside takt. Shift 1 released with as-built records, approvals and dispositions written for the quality lead.
Chassira writes to production equipment. Every capability is scoped, every write is policy-checked against the qualified envelope, safety-critical parameters are locked, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Planned, first 6 months, with an IATF and functional-safety-aware review |
| SOC 2 Type II | Cloud control plane | QUEUED Planned, 6 to 12 months |
| SSO and RBAC | Console and approvals | QUEUED Planned, 6 to 12 months |
| IATF 16949 and APQP assurance packages | Disposition and traceability evidence | QUEUED Planned, 6 to 12 months; not a certification claim |
| ISO 26262-aware control | Functional-safety requirements cited in reasoning and gates | RUNNING In the design; not a certification claim |
| Standards-cited reasoning | IATF 16949, APQP and PPAP, torque specs, recall procedures | RUNNING In the design, every answer cites its source |
| Per-tenant and program isolation | Designs, control plans, models, memory | RUNNING In the design from day one |
| On-prem and plant-edge deployment | Regulated OEM plants | RUNNING Design option |
A car plant does not go from manual to unattended in one step. Chassira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then bounded autonomy on low-risk loops. Weld schedules stay supervised until the joint family is qualified, and torque specifications and test verdicts are never written by an agent.
| Level | What the agent does | What the human does | Where it sits in a pilot |
|---|---|---|---|
| L1 · Shadow | Reads weld, metrology, vision, torque, test, robot and MES signals; predicts and recommends; writes nothing | Runs the line as today; compares predictions to audit and engineer outcomes | Design partners start here; the baseline is measured from the plant's own records |
| L2 · Assist | Proposes weld, framing, paint, routing, holding and sequencing moves with evidence, confidence, envelope and rollback path | Approves each action in the review console | Assist mode: accuracy and ROI proven against the signed baseline |
| L3 · Bounded | Executes pre-approved low-risk actions: booth environment, framing offsets, blank feed and lubrication, routing, holds, sequencing, inside PLC and safety limits and the qualified envelope | Approves weld-schedule changes, torque-related decisions and vehicle release | Graduated autonomy, after audited accuracy and ROI |
| L4 · Scaled | Supervised weld-schedule adaptation for qualified joint families, across lines and plants | Sets the envelope; reviews the shift record and evaluation results | Planned; after golden-dataset evaluation, twin validation and quality sign-off. Torque specifications and test verdicts never leave human hands |
Chassira reads and writes through the systems already on the floor. No rip and replace, no parallel historian, no new HMI to learn. Vendor names are examples of systems found in car plants, not certified integrations; connector availability is confirmed per site.
Robot and cell controllers (KUKA, FANUC, ABB, Yaskawa, Comau class systems)
Cell state, traces and paths; guarded writes inside interlocks
Press lines and die protection (Schuler, AIDA class systems)
Force, stroke and feed reads; guarded feed and lube writes
Servo-gun, laser, rivet and adhesive controllers (Bosch Rexroth, FANUC servo-gun class systems)
Trace reads; schedule writes under engineer approval
Booths, ovens and paint robots (Dürr EcoPaint class systems)
Environment and profile reads; guarded booth writes
In-line vision and dimensional systems (Cognex, Keyence, ISRA Vision, Hexagon, Zeiss, Perceptron class systems)
Images, point clouds and measurements per body
Torque tools and traceability (Atlas Copco, Bosch Rexroth, Desoutter class systems)
Traces per fastener; specifications read-only
Pack, ADAS and end-of-line test systems (AVL, Dürr, Burke Porter class systems)
Results per unit; verdicts and limits read-only
Plant MES and twin platforms (Siemens Opcenter and Tecnomatix, Dassault DELMIA, Rockwell Plex, AVEVA, in-house OEM systems)
Sequence, control plans, as-built records; sequence writes inside limits
The questions plant managers, launch engineers and quality leads ask in the first meeting.
Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified envelope, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Chassira writes nothing. Weld-schedule changes wait for a named body-shop engineer, and torque specifications, battery-joint parameters and end-of-line test limits and verdicts are read-only to every agent, always.
Control returns to the press, robot, booth or MES controller's last known-good state. Chassira is a supervisory layer on top of the safety-rated PLCs and interlocks you already run, never a replacement for them, so an outage degrades the line to its current way of running, not to a stop.
Advisory recommendations start from the plant twin and the control plan in the first weeks. Weld, geometry, paint, torque and end-of-line prediction improve as line history and labelled outcomes accumulate per program. The compute plan sizes onboarding at 150 to 600 GPU-hours per plant and 50,000 to 250,000 synthetic variants per program, all design targets.
Only if you choose cloud training. Designs, control plans, specs, process models and quality records are isolated per tenant and never used to train another OEM's models. On-prem and plant-edge deployment are available for regulated plants, and federated cross-plant learning is planned and waits on data-rights agreements.
You are, the same as with any control strategy, which is why every write is policy-checked, bounded, logged and reversible, and why anything crash-safety or IATF relevant waits for a named approver. The audit log records the request, the evidence, the envelope applied and the human decision.
A paid pilot on one process or area at the Process tier, scoped to a single wedge with a success metric written into the order form: weld or geometry rework, downtime minutes, paint defect or repaint rate, warranty or PPM, or launch quality. Shadow mode first, then assist mode with your engineer approving each move, then bounded autonomy on low-risk loops once ROI and safety gates are met.
Start with one process and one measurable baseline. A paid pilot on body-shop weld and gap-and-flush vision, paint-defect detection and film-build control, or torque and battery-joint conformance shows the number before you commit further.
↑↓ navigate↵ openesc close