Enterprise

One policy. Every process. Every plant.

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.

Land $1M to $15M ACVFleet-managed plant edgePer-plant private models

run_41a9c2 · agent graph · plant BIW-2 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.shift ✓ SUCCEEDED 02 · vehicle_line twin.simulate ✓ SUCCEEDED 03 · stamp_form stamp.form ✓ SUCCEEDED 04 · orchestrator approve.human ◆ APPROVAL 05 · weld_join weld.join ✓ SUCCEEDED 06 · frame_geometry frame.geometry ✓ SUCCEEDED 07 · paint_finish paint.finish ✓ SUCCEEDED 08 · powertrain_battery marriage.torque ✓ SUCCEEDED 09 · quality_anomaly inspect.fuse ✓ SUCCEEDED 10 · eol_calibrate eol.release ✓ SUCCEEDED

Illustrative scenario: Plant BIW-2 · EV crossover body shop to end of line · shift 1, one approval gate

Enterprise features

What the Enterprise tier adds

Items marked planned follow the 6 to 12 month roadmap.

Governance

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.

Identity

SSO, SCIM and tag-level RBAC

Named approvers, role-based access down to the tag. Planned for the 6 to 12 month release.

Fleet

Plant-edge fleet management

Model versions promoted by line with canary rollout and automatic fallback across every plant. On-prem options for regulated plants.

Models

Custom weld, paint, geometry and battery models

Per-plant process models built on the plant's own programs, materials and joint families and kept private to that tenant.

Benchmarking

Cross-plant benchmarks

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.

Support

Dedicated engineer, SLAs

A dedicated deployment engineer, quarterly model review per plant and SLA terms set per agreement.

Deployment

Where it runs

The plant edge is always local. The control plane can be cloud, on-prem or absent.

Deployment options
OptionPlant edgeControl planeFor
Cloud control planeJetson nodes at the cellChassira cloud, per-tenant isolationMost plants; cloud training optional
On-prem control planeJetson nodes at the cellIn the plant's data centreRegulated OEM plants, strict program controls
Plant-edge onlyJetson nodes at the cellIn the plant, no external linkPrograms that cannot leave the site
Edge-only degradationReturns to controller last known-goodUnreachableWhat happens on any control-plane loss
Enterprise

Standardise autonomy across the fleet

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.

Talk to us Enterprise details

  • SSO and role-based access down to the tag level, planned for the 6 to 12 month release
  • Fleet-wide autonomy policy with per-plant override and approval chains
  • Cross-plant benchmarking on first-time-through, rework, repaint, downtime and warranty
  • On-prem and plant-edge deployment for regulated OEM plants
  • Edge autonomy that survives control-plane loss by returning to the controller's last known-good state
  • Dedicated deployment engineer and quarterly model review per plant
Run timeline · scenario

One scenario shift, step by step

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.

run_41a9c2 Plant BIW-2 · EV crossover body shop to end of line · shift 1 illustrative scenario SUCCEEDED
  1. 01 ingest.shift SUCCEEDED 0.8 s

    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.

  2. 02 twin.simulate SUCCEEDED 1 m 40 s

    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.

  3. 03 stamp.form SUCCEEDED continuous

    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.

  4. 04 approve.human APPROVAL 3 m 12 s

    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.

  5. 05 weld.join SUCCEEDED continuous

    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.

  6. 06 frame.geometry SUCCEEDED continuous

    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.

  7. 07 paint.finish SUCCEEDED continuous

    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.

  8. 08 marriage.torque SUCCEEDED continuous

    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.

  9. 09 inspect.fuse SUCCEEDED continuous

    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.

  10. 10 eol.release SUCCEEDED 2 m 05 s

    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.

Guardrails

An agent near a crash-safety joint needs a leash

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.

  • Bounded action space. Each agent writes only to an explicit tag allow-list, inside per-tag rate and magnitude limits and the qualified process envelope for the joint family, colour block or vehicle program.
  • Policy engine before every write. Autonomy level, shift, program, interlock state and operator presence are evaluated before a setpoint moves. NeMo Guardrails enforces spec, IATF, functional-safety, cyber and human-approval policy before any action writes back to robots, MES, QA or work instructions.
  • Safety-critical parameters locked. Weld schedules wait for a named body-shop engineer until the joint family is qualified. Torque specifications, battery-joint parameters and end-of-line test limits and verdicts are read-only to every agent, always.
  • Immutable audit log. Append-only and exportable. Every action records source evidence, the approved envelope, confidence, estimated quality, rework, downtime and warranty impact, rollback path, approver and vehicle scope.
  • Hard fallback. Loss of the edge node, the network or a model returns control to the press, robot, booth or MES controller's last known-good state. Safety-rated PLCs and interlocks are never in Chassira's path.
  • Tenant and program isolation. Vehicle designs, control plans, specs, models and memory never cross an OEM boundary. On-prem and plant-edge deployment are available for regulated plants.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Planned, first 6 months, with an IATF and functional-safety-aware review
SOC 2 Type IICloud control plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
IATF 16949 and APQP assurance packagesDisposition and traceability evidence QUEUED Planned, 6 to 12 months; not a certification claim
ISO 26262-aware controlFunctional-safety requirements cited in reasoning and gates RUNNING In the design; not a certification claim
Standards-cited reasoningIATF 16949, APQP and PPAP, torque specs, recall procedures RUNNING In the design, every answer cites its source
Per-tenant and program isolationDesigns, control plans, models, memory RUNNING In the design from day one
On-prem and plant-edge deploymentRegulated OEM plants RUNNING Design option

Read the security overview

Autonomy

Four levels, set per agent and per tag

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.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads weld, metrology, vision, torque, test, robot and MES signals; predicts and recommends; writes nothingRuns the line as today; compares predictions to audit and engineer outcomesDesign partners start here; the baseline is measured from the plant's own records
L2 · AssistProposes weld, framing, paint, routing, holding and sequencing moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode: accuracy and ROI proven against the signed baseline
L3 · BoundedExecutes pre-approved low-risk actions: booth environment, framing offsets, blank feed and lubrication, routing, holds, sequencing, inside PLC and safety limits and the qualified envelopeApproves weld-schedule changes, torque-related decisions and vehicle releaseGraduated autonomy, after audited accuracy and ROI
L4 · ScaledSupervised weld-schedule adaptation for qualified joint families, across lines and plantsSets the envelope; reviews the shift record and evaluation resultsPlanned; after golden-dataset evaluation, twin validation and quality sign-off. Torque specifications and test verdicts never leave human hands
Integrations

It speaks plant, not cloud

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 cells

Robot and cell controllers (KUKA, FANUC, ABB, Yaskawa, Comau class systems)

Cell state, traces and paths; guarded writes inside interlocks

Presses and dies

Press lines and die protection (Schuler, AIDA class systems)

Force, stroke and feed reads; guarded feed and lube writes

Welding and joining

Servo-gun, laser, rivet and adhesive controllers (Bosch Rexroth, FANUC servo-gun class systems)

Trace reads; schedule writes under engineer approval

Paint systems

Booths, ovens and paint robots (Dürr EcoPaint class systems)

Environment and profile reads; guarded booth writes

Vision and metrology

In-line vision and dimensional systems (Cognex, Keyence, ISRA Vision, Hexagon, Zeiss, Perceptron class systems)

Images, point clouds and measurements per body

Torque and fastening

Torque tools and traceability (Atlas Copco, Bosch Rexroth, Desoutter class systems)

Traces per fastener; specifications read-only

Battery and EOL test

Pack, ADAS and end-of-line test systems (AVL, Dürr, Burke Porter class systems)

Results per unit; verdicts and limits read-only

MES, andon and sequencing

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

See all integrations

FAQ

Straight answers

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.

Get started

Standardise the fleet

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.