Fleet alarm → credentialed dispatch — across customer carriers.
Rolling-stock and rail-equipment OEMs — Wabtec, Alstom, Siemens Mobility, Stadler, Hitachi Rail, CRRC, Knorr-Bremse — ship locomotives, EMU and DMU consists, signaling systems, and onboard subsystems into multi-decade revenue service. Your QMS sits under IRIS ISO/TS 22163 (the rail-industry standard), ISO 9001:2015, ISO 14001 / 45001, AAR M-1003 for North American freight customers, and increasingly IEC 62443-4-1 for secure product-development lifecycle (the rising requirement as CBTC, PTC, and HMI cybersecurity tightens). Your products certify against IEC 62278 (RAMS), IEC 61375 (TCN onboard network), IEEE 1474 (CBTC), EN 50128 (software safety), AAR S-9201 / S-9701 (US freight), and IRIS technical specifications. Your customer-facing surface includes LTSA / Maintenance Service Agreement performance audits and customer FRA / FTA inspector access. Wēlr is the install-base service record — the work-execution layer that closes the loop between rolling-stock fleet monitoring (Wabtec Trip Optimizer, Alstom HealthHub, Siemens Railigent) and credentialed FSE dispatch.
Four pains across the OEM service motion.
- 01
LTSA / MSA performance evidence reconstructed at every quarterly review.
MDBF (mean distance between failures), availability, on-time performance contribution, parts-consumption per million-mile, response-time SLA, LD exposure — reconstructed from CMMS, OEM telemetry archives, and customer reports every quarter for the LTSA renewal cycle (5-30 years on rolling stock). The numbers your CFO sees were assembled by hand under deadline.
- 02
FSE credentialing matrix at customer carriers tracked by spreadsheet.
Customer-specific safety training (carrier rules), FRA Roadway Worker Protection / 49 CFR Part 214, OSHA confined-space and electrical-safety qualifications, customer-issued credentials per carrier (badging, dispatched-territory authorization), drug & alcohol cycle, geographic work authorization, and LTSA-specific OEM technician qualification ladders — tracked per customer in spreadsheets.
- 03
Fleet-monitoring platforms tell you something is wrong; nothing closes the loop.
Wabtec Trip Optimizer, Alstom HealthHub, Siemens Railigent — every Tier 1 has a rolling-stock fleet-monitoring platform. None of them dispatches a credentialed FSE against the signal, schedules on-site execution, and folds closure evidence back to the fleet view. The work-execution layer between fleet alarm and credentialed FSE doesn't exist as a product.
- 04
Component health surfaces at overhaul, not before.
Bogie wear, traction-motor commutator condition, HVAC compressor cycle life, brake-rigging wear, draft-gear cycle counters — component-level health surfaces at scheduled overhaul. Predictive intervention is a slide deck in quarterly business reviews. It doesn't operationalize against the next dispatch.
Four primitives. One fleet-aware install-base record.
LTSA / MSA performance record per contract, per asset
MDBF, availability, on-time performance contribution, parts consumption per million-mile, response-time SLA performance, LD exposure / bonus accrual — keyed per LTSA / MSA contract, per asset, per reporting period. Quarterly review evidence is a query; year-end LTSA renewal evidence is a query.
FSE credentialing matrix on the dispatch path
Customer-carrier safety training, FRA Part 214 Roadway Worker Protection, OSHA confined-space and electrical-safety, customer-issued badging and dispatched-territory authorization, LTSA-specific OEM technician qualifications — all first-class technician attributes. Dispatch fails closed when the credential set doesn't cover the customer carrier or work-site task class.
Fleet alarm → credentialed dispatch closure
Component-health and fleet-monitoring signals attach to a dispatched FSE with credentials verified at dispatch. The work-execution layer ties fleet alarm → credentialed dispatch → on-site execution → evidence-back-to-fleet on one record. Where Wabtec Trip Optimizer, Alstom HealthHub, and Siemens Railigent stop, Wēlr starts.
Cross-fleet component reliability intelligence
Bogie wear, traction-motor commutator condition, HVAC compressor cycle, brake-rigging signals across customer carriers — Weibull-fitted component survival curves per component family, per same-vintage subset. A pattern caught at one carrier becomes the next carrier's pre-arrival brief; predictive intervention is operational, not slide content.
Why not extend the rolling-stock fleet-monitoring platform you already run?
Most rolling-stock OEMs face the same three options. Build the work-execution layer in-house on top of an existing fleet-monitoring platform (multi-year project; specialized credentialing-matrix architecture; an FSE org that has to ship while engineering builds). Extend a generic field-service platform (no fleet-signal model; no credentialing matrix; no LTSA performance record). Or Wēlr.
| Capability | Wēlr | Build in-house 24+ mo · 10 engineers · ~$5M | Generic field-service platform ServiceMax · Salesforce FS · IFS |
|---|---|---|---|
| LTSA / MSA performance record (MDBF · availability · OTP) | First-class · audit-on-demand | Custom build | Bolt-on |
| FSE credentialing matrix (Part 214 RWP · carrier · LTSA) | Auth-gated · fails closed | Spreadsheet per customer | Spreadsheet matrix |
| Fleet alarm → credentialed dispatch closure | Single workflow | Custom integration build | Two systems · manual handoff |
| Cross-fleet component reliability (Weibull, per-vintage) | First-class data model | Quarterly slides | Not modeled |
| IRIS / AAR M-1003 / IEC 62443-4-1 evidence per product line | Structural | Custom integration | Not modeled |
Cross-carrier component reliability — and the next-visit brief writes itself.
A bogie BG-3 wear signal on Amtrak's EMU-71 fleet at 142k miles is the same signal forming on NJ Transit's same-vintage fleet — and likely to surface at Metro-North and LIRR next. Wēlr issues a pre-arrival brief to the next visits at all three carriers with the affected vintage; a credentialed FSE is matched at dispatch with Part 214 Roadway Worker Protection verified and customer-carrier badging confirmed. The pattern your best FSE noticed at one customer becomes the next site's first hypothesis.
- Weibull-fitted component-survival curves per family · per same-vintage subset across customer carriers
- Cross-fleet brief auto-attached to next visits at every carrier running the same fleet · same vintage · with a credentialed FSE matched at dispatch
- Customer-specific scoping enforced — Amtrak's fleet data never visible to NJ Transit at the database row
- LTSA / MSA performance evidence (MDBF, availability, OTP contribution, LD exposure) updates in-band as the dispatch closes
If any of these are true, we should talk.
- ✓Your LTSA / MSA performance evidence — MDBF, availability, OTP contribution, parts consumption per million-mile, LD exposure — is reconstructed from CMMS, telemetry archives, and customer reports every quarterly review.
- ✓Your FSE credentialing matrix at customer carriers is tracked on a spreadsheet across FRA Part 214 Roadway Worker Protection, customer-specific safety training, customer-issued badging, OSHA confined-space and electrical, and LTSA qualifications — and gaps surface at site arrival.
- ✓Your fleet-monitoring platform (Trip Optimizer, HealthHub, Railigent, or an internal build) tells you something is wrong with the fleet but doesn't dispatch a credentialed FSE against the signal.
- ✓Component-level health (bogie wear, traction-motor commutator, HVAC compressor cycle, brake rigging) surfaces at scheduled overhaul — predictive intervention is quarterly slide content, not operational.
- ✓A major carrier issued a supplier finding or LTSA performance dispute in the last cycle, and the root cause was evidence you couldn't reconstruct inside the response window.
A small founding cohort is shaping Wēlr for rolling-stock & rail-equipment oems.
Founding partners get preferential pricing, a direct line to engineering, and meaningful influence over the Transit & rail roadmap. Limited to a small cohort per vertical.
- Preferential pricing
- Direct line to engineering
- Roadmap influence
- Limited cohort
Ready to stop stitching service evidence together?
If your team is juggling PDFs, support packages, work orders, customer updates, and QA evidence across five systems, Wēlr is worth a look.
Welr LLC · Delaware