Network autonomy policy
One policy model for the network with per-site override and approval chains. Tool allow-lists, control-plan envelopes and limits reviewed and versioned like code.
Enterprise
One policy. Every process. Every plant.
Multi-plant OEM and tier-1 networks standardise on Railira for the governance as much as the control: one autonomy policy with per-site override, one audit trail, fleet-managed plant-edge nodes, and carbody, coating, torque and takt models that stay private to each plant and program.
Illustrative scenario: Car 07 of a 4-car metro consist · shell line B · bogie shop · booth 2 · marriage station, one car, one approval gate
Enterprise features
What the Enterprise tier adds
Items marked planned follow the 6 to 12 month roadmap.
SSO, SCIM and tool-level RBAC
Named approvers, role-based access down to the tool. Planned for the 6 to 12 month release.
Plant-edge fleet management
Model versions promoted by process area with canary rollout and automatic fallback across every plant. On-prem options for OEM cyber-reviewed sites.
Custom carbody, coating, torque and takt models
Per-site process models built on the plant's own car types, control plans and recipes and kept private to that tenant and program.
Cross-plant benchmarks
First-time-through, rework, PPM, delivery risk and takt compared across plants without moving designs or program data across tenant boundaries. Data-network tiers are planned.
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.
| Option | Plant edge | Control plane | For |
|---|---|---|---|
| Cloud control plane | Jetson nodes at the station | Railira cloud, per-tenant isolation | Most plants; cloud training optional |
| On-prem control plane | Jetson nodes at the station | In the plant's data centre | OEM cyber-reviewed and regulated plants |
| Plant-edge only | Jetson nodes at the station | In the plant, no external link | Programs with strict IP and security controls |
| Edge-only degradation | Returns to controller last known-good | Unreachable | What happens on any control-plane loss |
Enterprise
Standardise autonomy across the network
One policy model, one audit trail, one benchmark across every process in every plant, with the carbody, coating, torque and takt models kept private to each site and program.
- SSO and role-based access down to the tool level, planned for the 6 to 12 month release
- Network-wide autonomy policy with per-site override and approval chains
- Cross-plant benchmarking on first-time-through, rework, PPM, delivery risk and takt
- On-prem and plant-edge deployment for regulated and OEM cyber-reviewed 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 run, step by step
Every Railira run is an ordered, inspectable sequence. This is run_9b4e27: Car 07 of a 4-car metro consist · shell line B · bogie shop · booth 2 · marriage station. Scenario completes in 10 steps with one approval gate. Shell geometry held inside tolerance after a twin-ranked weld sequence, one heat-input change approved by the shift weld engineer, two torque traces routed to rework before brake test, the livery cure window protected in the sequence, marriage interface inside tolerance, car released with full genealogy.
run_9b4e27
car 07 · 4-car metro consist
illustrative scenario
SUCCEEDED
-
01
ingest.order
SUCCEEDED
0.8 s
Plant Orchestrator · Pulled the work packages for car 07 from MES and PLM: aluminium extrusion shell, EN 15085 weld class per joint, control-plan geometry tolerances, bogie torque specifications, livery recipe and cure window, fit-out and marriage sequence. Locked the approved control-plan envelope for the shift.
-
02
takt.sequence
SUCCEEDED
41 s
Line-and-Logistics · Sequenced the shift against live readiness: booth 2 cure window, bogie B-14 readiness, brake-test slot at 13:40, AMR fleet state and kit inventory. The plan moves car 07 marriage behind car 06 to keep the cure window and the test slot.
-
03
twin.simulate
SUCCEEDED
58 s
Train Twin · Simulated 18 candidate weld sequences for the roof-to-sidewall joints on the as-built twin and ranked them on predicted distortion, door-aperture geometry and heat input. Sequence #6 keeps the aperture inside tolerance with 2% less heat input than the standing sequence.
-
04
weld.sequence
SUCCEEDED
3 m 12 s
Weld-and-Structure · Recommended sequence #6 and the matching clamping plan to the shell line. Seam vision and laser-tracker geometry confirmed the roof-to-sidewall joints inside the control-plan tolerance on the first four seams.
-
05
approve.human
APPROVAL
52 s
Plant Orchestrator · Sequence #6 lowers heat input on the roof joints 2% below the standing weld procedure. Heat-input changes stay with a named engineer, so the step was held for the shift weld engineer and approved at 06:12:44 with the twin evidence attached.
-
06
bogie.torque
SUCCEEDED
continuous
Bogie-and-Running-Gear · Press-fit curves and torque traces on bogie B-14 read at the station. Two traction-motor mounting traces fell outside the expected profile and were routed to rework before brake test; the remaining safety-critical joints verified to spec.
-
07
coat.cure
SUCCEEDED
continuous
Coat-and-Livery · Booth 2 humidity and temperature, film thickness and flash time watched through the livery pass. One masking misalignment on the door band flagged by booth vision before the second coat; the cure window held and handed to the sequence as a hard constraint.
-
08
marry.align
SUCCEEDED
2 m 05 s
Marry-and-Couple · Carbody and bogie scans compared against target interface geometry before the lift. Fit-out readiness confirmed by Fitout-and-Interior for doors and glazing. Marriage guided inside tolerance; coupler and gangway checks verified and written to the twin.
-
09
inspect.fuse
SUCCEEDED
continuous
Quality-and-Anomaly · Weld and coating vision, in-line metrology, torque, wiring continuity and brake-test results fused at the edge across the car. Every finding localised to station, work package and shift, with the two torque reworks and the masking flag already closed.
-
10
car.release
SUCCEEDED
1 m 30 s
Conformance · Car 07 released: genealogy written (weld records per joint, geometry scans, torque traces, coating recipe and cure record, fit-out checks, marriage interface, approvals, test results) and dispositioned against the control plan and IRIS / ISO/TS 22163 criteria with cited evidence for the quality engineer's sign-off.
Guardrails
An agent that can change a weld sequence needs a leash
Railira writes to production systems. Every capability is scoped, every write is policy-checked against the approved control plan, and every action is written to an append-only audit log the plant owns.
- Bounded action space. Each agent acts only through an explicit tool allow-list, inside per-tool rate and magnitude limits and the approved control-plan envelope for the car type.
- Policy engine before every write. Autonomy level, shift, car type, interlock state and operator presence are evaluated before a recommendation becomes a write to a robot, MES, torque tool or work package.
- Human-in-the-loop gates. Heat-input and weld-sequence changes, schedule release and car release wait for a named approver. High-risk changes remain human-approved until IRIS, plant and OEM acceptance is earned.
- Immutable audit log. Append-only and exportable. Every action records source evidence, the control-plan envelope, confidence, estimated quality and takt impact, rollback path, approver and car scope.
- Hard fallback. Loss of the edge node, the network or a model returns control to the robot, PLC or station's last known-good state. Safety systems and interlocks are never in Railira's path.
- Tenant and program isolation. Designs, control plans, program data, models and memory never cross a customer boundary. On-prem and plant-edge deployment is available for regulated plants.
Compliance posture
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I and OEM cyber review | Cloud control plane | QUEUED Planned, first 6 months |
| 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 |
| IRIS and regulatory assurance packages | Disposition and genealogy evidence | QUEUED Planned, 6 to 12 months; not a certification claim |
| Standards-cited reasoning | Control plans, EN 15085, IRIS / ISO/TS 22163, TSI, AAR, APTA, torque and brake-test 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 plants | RUNNING Design option |
Autonomy
Four levels, set per agent and per tool
A rolling-stock plant does not go from manual to unattended in one step. Railira 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 actions. Weld parameters, schedule release and car release stay with named humans until acceptance is earned.
| Level | What the agent does | What the human does | Where it sits in a pilot |
|---|---|---|---|
| L1 · Shadow | Reads weld, metrology, torque, coating, wiring, test, robot and MES signals; predicts and recommends; writes nothing | Runs the line as today; compares predictions to inspection and engineer outcomes | Shadow mode; baseline measured from the plant's own records |
| L2 · Assist | Proposes weld-sequence, geometry, coating, torque and sequencing moves with evidence, confidence, envelope and rollback path | Approves each move in the review console | Assist mode; accuracy and ROI proven against the baseline |
| L3 · Bounded | Executes pre-approved low-risk actions: inspection routing, rework priority, kit feeding, robot path variants and parameter adjustments inside approved bounds | Approves heat-input and weld-sequence changes, schedule release and car release | Graduated autonomy, after audited accuracy and ROI and safety gates |
| L4 · Scaled | Supervised weld-parameter adaptation inside pre-approved control-plan envelopes, across lines and plants | Sets the envelope; reviews the shift record and the evaluation results | Planned; after IRIS, plant and OEM acceptance is earned |
Integrations
It speaks plant, not cloud
Railira 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 rolling-stock plants, not certified integrations; connector availability is confirmed per site.
Rail PLM, MES and sequencing suites (Siemens Teamcenter, Opcenter and Tecnomatix, Dassault DELMIA, Rockwell, iBASEt, Critical Manufacturing class systems)
Work packages, control plans, sequence reads; genealogy and schedule write-back
Robot controllers and process controllers (FANUC, KUKA, ABB, Yaskawa, Comau, Dürr, Kawasaki class systems)
Parameter and path reads; bounded parameter and sequence recommendations
Laser trackers, point-cloud scanners and vision systems (Hexagon, Zeiss, FARO, Cognex, ISRA Vision, Perceptron class systems)
Geometry scans and inspection results per car
Torque tools and controllers (Atlas Copco, Bosch Rexroth, Stanley class systems)
Torque traces per joint, rework routing
Wiring testers, brake-test rigs, traction-test and ETCS, ERTMS or PTC commissioning systems
Continuity, brake and signaling results per car
Booth instruments, thickness gauges, environmental sensors, recipe systems
Film build, flash, cure, humidity and temperature
Plant-simulation and twin tools (Siemens Tecnomatix Plant Simulation, Dassault DELMIA, Visual Components)
Model and result exchange with the train-and-plant twin
Fleet managers and dispatch APIs
Fleet state, dispatch recommendations
FAQ
Straight answers
The questions plant directors, body and coating engineers and quality leads ask in the first meeting.
Only within an explicit tool allow-list with per-tool rate and magnitude limits, inside the approved control-plan envelope, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Railira writes nothing. Heat-input and weld-sequence changes, schedule release and car release stay with a named approver.
Control returns to the robot, PLC or station's last known-good state. Railira is a supervisory layer on top of the controllers, safety systems 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.
Recommendations start from the control plan, the work instructions and the twin in the first weeks. Weld, geometry, coating and torque prediction improve as line history and labelled outcomes accumulate per car type. Onboarding is sized at 100 to 500 GPU-hours per plant and 50,000 to 250,000 synthetic images or scan variants per program, all design targets.
Only if you choose cloud training. Designs, control plans, program data, process models and quality records are isolated per tenant and never used to train another customer's models. Fully on-prem deployment at the plant edge is available for regulated plants, and 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 above your risk threshold 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 line area, scoped to a single wedge with a success metric written into the order form: weld or coating rework reduction, geometry escapes, torque escapes, line stoppage minutes or first-time-through. It starts in shadow mode against a baseline from your own records, moves to assist mode when the engineer is satisfied, and expands only after the number moves.
Get started
Standardise the network
Start with one carbody, bogie, coating, fit-out or sequencing process and one measurable baseline. A paid pilot on weld and geometry, torque assurance, livery defects or line sequencing shows the number before you commit further.