- 02:14AlarmBldg 4 ATS won't transfer
- 02:18ConduitASCO 7000 ladder · cited
- 02:34ActionNFPA 110 manual transfer
- 02:51CapturedSaved for next 2 a.m. call
Planara Conduit · Power generation
Conduit for the gensets that can't fail.
A genset is one part of a larger reliability promise. Conduit makes sure the technician shows up with the right manual before the customer's UPS runs out.
ATS won't transfer — diagnostic ladder?
Specifications
Verify utility is dead before manual transfer. Genset will start in 10 s — clear the cabinet.
Why Power generation
Why Power generation fits Conduit's model.
What makes this vertical fit the Conduit pattern: the standards stack, the documentation density, and how the service work actually happens.
The standards layer.
Power generation lives inside a hard standards stack: NFPA 70 (NEC) for the wiring, NFPA 110 for emergency and standby power systems, NFPA 37 for engine installations, EPA Tier 4 for emissions, the corresponding state and regional codes, and the customer-specific reliability tier requirements (Tier III/IV data center, Joint Commission for hospitals, telecom uptime SLAs). Conduit cites the right standard for the right install — not a generic answer that the AHJ will reject at inspection.
The documentation density.
Genset service technicians work across OEMs (Generac, Cummins, Kohler, Caterpillar, MTU, GE Vernova) and across components: the prime mover, the alternator, the control panel, the ATS, the switchgear, and the paralleling logic if the install is multi-unit. Each layer has its own manual, its own bulletin stream, and its own commissioning procedure. Conduit ingests the whole stack so the tech doesn't carry a binder bag onto the customer's site.
The service workflow.
Power-gen service is distributed: regional teams covering customers from data centers to hospitals to telecom huts. Maintenance is runtime-based and load-bank scheduled, but the unplanned calls — the 2am hospital generator that didn't transfer — define the relationship. Conduit is the layer that gets the right manual into the technician's hands before the truck rolls, and captures what they learned on the call so the next 2am call is faster.
A 2 a.m. call, walked through
The tech showing up to the hospital is the difference. Conduit is what they show up with.
One real after-hours call, narrated against a clock. Illustrative — your customer mix and your platforms vary.
- 02:14
Customer page: hospital ATS won’t transfer.
Building 4, 1.25 MW Cummins QSK60. Re-transfer delay setting is the suspect — but the tech hasn’t worked an ASCO 7000 in months.
- 02:18
Tech opens Conduit on phone in the truck.
Asks: “ATS won’t transfer — diagnostic ladder?”
- 02:18
Conduit returns the ASCO 7000 ladder.
Cited to the IOM § 7.2, p. 88. Re-transfer delay setting, manual transfer procedure, NFPA 110 verification step — all preserved verbatim.
- 02:34
Tech executes manual transfer per NFPA 110.
Verifies utility is dead. Genset starts in 10 s. ATS returns to auto. Customer comes back online before the UPS dropout.
- 02:51
Tech captures the resolution.
Submits the diagnostic path as a correction. The next 2am call on an ASCO 7000 starts with the answer this tech just learned.
What it looks like
What a Conduit deployment in Power generation looks like.
A power-generation Conduit deployment ingests the genset OEM manuals, the control panel and ATS documentation, the switchgear and paralleling configurations, and the relevant NFPA / NEC references. Field technicians ask before and during the call. Service ops sees uptime patterns, technician knowledge gaps, and where the documentation is failing the most critical customers.
ATS won't transfer — diagnostic ladder?
Specifications
Verify utility is dead before manual transfer. Genset will start in 10 s — clear the cabinet.
Last 30 days
47 sites · 0 missed transfers
Sites covered
47
+6
Maintenance windows
138
completed
After-hours calls
9
−3 wk/wk
NFPA cites served
284
70 / 110 / 37
Site queries · 30 days
+12% wk/wk
Early access — by application
We're not shipping a finished product in this vertical yet.
The reference deployment is in marine. We're working with a small number of early pilot customers — companies who want Conduit running on their documentation now and are willing to shape it as we go.
That's a real deployment for you, with real tradeoffs. Here's the trade.
What you get out of it
- A working Conduit deployment built on your actual documentation
- Custom configuration: terminology, standards, and role surfaces tuned to how your techs work
- Locked-in early pricing for the life of the contract
- A direct line to the team building the platform — your feedback shapes the next release
- Named publicly as an early customer when you're ready, kept private until then
What we need from you
- Access to your equipment documentation (PDFs are fine — manuals, bulletins, internal SOPs)
- 3–5 technician interviews so we understand the actual service work
- 30 minutes a week of feedback for the first 8 weeks
- Honesty when something doesn't work
Apply
Apply to deploy Conduit in Power generation.
Tell us what platforms you service, what your customer mix looks like (data center, healthcare, telecom, commercial), and where reliability is being lost. Five fields. We read every one. If we think there's a fit, we'll come back to you within a week.