Run a wedge on one process
Weld and geometry, torque assurance, livery defects or line sequencing, with a metric you already measure.
Railira starts with a paid pilot on one carbody, bogie, coating, fit-out or sequencing process and a baseline agreed in writing. Tell us the process, the metric and the systems on it. We will say plainly whether the wedge fits and what the shadow-mode phase would look like.
Weld and geometry, torque assurance, livery defects or line sequencing, with a metric you already measure.
Welding and coating robot OEMs, PLM and MES, metrology, torque and test vendors, integrators.
We answer plainly, including what is planned rather than done.
Edge perception, OT integration, simulation, rail manufacturing or quality engineering.
On carbody welding, bogies, livery, the train twin, takt and autonomy in the plant.
Pre-revenue, pre-institutional. We do not claim traction we do not have.
The first-release plan, applied to your process.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Land on one workflow with a measured baseline. Expand by process, module and autonomy level. Outcome components are available on rework, line uptime, first-time-through and takt. Annual prepay carries a 15 to 20% discount.
Carbody, coating or assembly autonomy or inspection AI for one process. For plants validating ROI on the wedge.
The whole plant: weld and structure, carbody and join, geometry and framing, coat and livery, marry and couple, fit-out and interior, quality and anomaly, line and logistics, and the twin.
Multi-plant OEM and tier-1 networks standardising on Railira, with custom carbody, coating, torque and takt models and a plant-edge fleet.
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.
| 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 |
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
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.
Weld rework per car, repaint events, torque escapes, line stoppage minutes. We will tell you which wedge fits.
↑↓ navigate↵ openesc close