Install-base service — where fleet alarms meet credentialed FSEs.
Energy equipment OEMs in rotating-equipment service — GE Vernova, Siemens Energy, Mitsubishi Power, Wärtsilä, Solar Turbines, Doosan, Ansaldo — ship long-life gas and steam turbines, generators, and reciprocating assets into investor-owned utilities, IPPs, and industrial sites. Your QMS sits under ISO 9001:2015, ISO 14001 / 45001 (environmental and safety), and increasingly IEC 62443-4-1 (secure product-development lifecycle — the rising supplier requirement under customer CIP-013 audits). Your products certify against IEC 61850, IEEE C37, IEC 61400 (wind), IEEE 1547 / 1547.1 (DER interconnection) — type-tested at KEMA, DNV, PEHLA. Your customer-facing surface includes LTSA performance audits and CIP-013 R1 supplier audits scoped per customer. Wēlr is the install-base service record that travels with the asset — the work-execution layer that closes the loop fleet-monitoring platforms (GE APM, Siemens Senseye, ABB Ability, Hitachi Lumada) leave open.
Four pains across the OEM service motion.
- 01
Service evidence is fragmented across product-line platforms.
Turbine telemetry in one stack, transformer DGA in another, relay event records (COMTRADE) in a third. No cross-product service view. Tier 2 OEMs still ship raw archives that field engineers parse in text editors before diagnosis can begin; Tier 1 OEMs collapse the parsing problem but inherit the product-line silo problem.
- 02
FSE credentialing matrix at customer sites tracked by spreadsheet.
FSE coverage at customer sites is tracked across CIP-004 R3 PRA (7-year renewal), utility-specific CIP-004 R2 cyber training, HV authorization, LOTO and hot-work permits, drug-and-alcohol cycle, geographic work authorization, and LTSA-specific OEM qualification ladders. Dispatch decisions optimize geography first and discover credential gaps at site arrival. For nuclear-serving lines, 10 CFR 73.56 fitness-for-duty adds months of lead time per site.
- 03
Fleet-monitoring platforms tell you something is wrong; nothing closes the loop.
GE APM, Siemens Senseye, ABB Ability, Hitachi Lumada — every Tier 1 has built a fleet-monitoring stack. None of them dispatches a credentialed FSE against the signal, schedules the on-site execution, and folds the closure evidence back to the fleet view. The work-execution layer between fleet alarm and credentialed FSE doesn't exist as a product.
- 04
LTSA performance evidence reconstructed at every renewal.
Forced outage rate, starting reliability, EOH / equivalent-starts counters, heat-rate degradation curve, response-time SLA, LD exposure, and bonus accrual — reconstructed from CMMS records, OEM telemetry archives, and customer reports at every quarterly review and year-5 renegotiation. The numbers your CFO sees were assembled by hand under deadline pressure.
Four primitives. One grid-side install-base record.
Cross-product-line evidence on one record
Turbine telemetry, transformer DGA, partial-discharge, vibration, relay event records (COMTRADE), and LTSA performance counters ingest into one per-asset record. Tier 2 OEMs collapse the parsing job; Tier 1 OEMs collapse the cross-product-line silos.
FSE credentialing matrix on the dispatch path
PRA renewal (CIP-004 R3), utility-specific CIP-004 R2 training, HV authorization, LOTO, drug-and-alcohol cycle, geographic work authorization, LTSA-specific OEM qualification ladder, 10 CFR 73.56 fitness-for-duty (where nuclear) — all live as first-class technician attributes. Dispatch optimizes the credentialing matrix first; gaps surface at the matrix, not at site arrival.
Fleet alarm → credentialed dispatch closure
Fleet-monitoring signals attach to a dispatched FSE with the credential set verified at dispatch time. The work-execution layer ties fleet alarm → credentialed dispatch → on-site execution → evidence-back-to-fleet on one record. Where GE APM and Siemens Senseye stop, Wēlr starts.
LTSA performance record per contract, per asset
Forced outage rate, starting reliability, EAF / availability, capacity factor, heat-rate degradation curve, response-time SLA, EOH and equivalent starts, LD exposure and bonus accrual — keyed per LTSA contract, per asset, per reporting period. Year-5 renegotiation evidence is a query, not a quarter-long reconstruction.
Why not extend the fleet-monitoring stack you already run?
Most energy equipment OEMs face the same three options. Build the work-execution layer in-house on top of an existing fleet 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 · Oracle Field Svc |
|---|---|---|---|
| Cross-product-line evidence on one per-asset record | First-class data model | Multi-year build | Bolt-on per product line |
| FSE credentialing matrix on dispatch (8+ dimensions) | First-class attributes · fails closed | Spreadsheet per customer | Spreadsheet matrix |
| Fleet alarm → credentialed dispatch closure | Single workflow | Custom integration build | Two systems · manual handoff |
| LTSA performance record (FOR · SR · heat-rate degradation · EOH · LD) | First-class · audit-on-demand | Custom build | Bolt-on |
| IEC 62443-4-1 product-dev-lifecycle evidence per product line | Structural | Custom integration | Not modeled |
Fleet alarm → credentialed dispatch — one record, one workflow.
An incipient-fault signal at one customer's transformer goes from OEM-owned gas-in-oil monitor (outside the customer ESP) to fleet-wide situational awareness. Other utilities running the same model at the same vintage get a pre-arrival brief on the next scheduled visit — with a credentialed FSE matched at dispatch. The pattern your best FSE noticed at one customer becomes the next site's first hypothesis; the credentialing matrix already verified the right person can act on it.
- DGA sourced from OEM-owned gas-in-oil monitors and oil-sampling programs operating outside the customer ESP — per CIP-005 boundary; vendor scope governed by customer CIP-013 R1 supplier risk plan
- Cross-fleet brief auto-attached to next visits at every utility running the same model · same vintage · with a credentialed FSE matched at dispatch — Wēlr ties the alarm to the work-execution layer
- Aggregated-fleet rights strongest where the OEM negotiates them at purchase / LTSA — Tier 1 OEMs have the leverage; Tier 2 OEMs negotiate site by site
- Pattern-matching across DGA · partial-discharge · vibration · warranty consumption · LTSA performance counters on one per-asset record
If any of these are true, we should talk.
- ✓Your LTSA performance evidence — forced outage rate, starting reliability, heat-rate degradation, EOH, LD exposure, bonus accrual — is reconstructed from CMMS, telemetry archives, and customer reports at every quarterly review.
- ✓Your FSE credentialing matrix at customer sites is tracked on a spreadsheet across CIP-004 R3 PRAs, utility-specific cyber training, HV authorization, LOTO, drug-and-alcohol, and LTSA qualifications — and credential gaps surface at site arrival, not at dispatch.
- ✓Your fleet-monitoring platform (GE APM, Siemens Senseye, ABB Ability, Hitachi Lumada, or an internal build) tells you something is wrong with the fleet but doesn't dispatch a credentialed FSE against the signal.
- ✓Your customer's CIP-013 supplier audit surfaced gaps in your supply-chain risk evidence, IEC 62443-4-1 product-development-lifecycle posture, or vendor-access scoping in the last cycle.
- ✓A major utility customer 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 energy equipment oems.
Founding partners get preferential pricing, a direct line to engineering, and meaningful influence over the Energy & utilities 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