A balance-of-plant fault should not add a day to the outage.
AIMMS handles the permitted digital tasks around the repair. It connects operating evidence, OEM procedures, asset history, parts, critical spares, warranty rules, suppliers, approvals, and closeout in one governed return-to-service path.
Talk to AIMMS on iOS or Android, or work hands-free with our EQUA smart glasses. One interface across your existing systems. Your permissions. Your approvals.
What you get The OEM procedure, the confirmed cause, the installed variant, usable spares, the warranty position and the spend approval assembled before the outage clock turns into phone calls.
- No live-control writes
- Warranty evidence captured as you go
- Plant-defined approvals
Read-only operating context · Customer-defined approvals · Direct live-control writes permanently out of scope
Forced outage performance is getting worse while the spares queue gets longer.
Each one is a published third-party figure on North American generation reliability and the equipment supply chain around it, carrying its source and its year. None is an EQUA result and none describes your fleet. What each one does to a repair, and what AIMMS does about that, is stated beside it.
-
Critical assets are staying in service longer, and failing more often.
9.2% weighted equivalent forced outage rate for conventional generation in 2025, up year over year across the fleet NERC 2026 State of Reliability, June 2026, opens in a new tabDuring the repairMore corrective events land on the same crew, in the same outage windows, against balance-of-plant equipment whose OEM documentation and installed configuration have drifted apart over twenty years of service.
What AIMMS changesOpens the case against the asset, assembles the OEM evidence and the operating context, and surfaces the likely cause with the check that confirms it before the outage clock becomes phone calls.
-
The oldest units carry the most of it.
14.1% forced outage rate for coal units in 2025, up from 11.2% in 2024 NERC 2026 State of Reliability, June 2026, opens in a new tabDuring the repairThe units under the most maintenance pressure are the ones whose original engineering staff have already retired, so the fastest diagnostic path on the unit is a memory rather than a record.
What AIMMS changesCaptures the confirmed cause, the part fitted, the as-found and as-left readings and the technician’s own account while the work is happening, and keeps it attached to the unit.
-
There is less room for downtime.
39.8 TWh of additional unavailable energy from coal units in 2025, with combined-cycle units adding a further 19.1 TWh NERC 2026 State of Reliability, June 2026, opens in a new tabDuring the repairUnavailable energy is dispatch the fleet was counted on to provide. Every hour the work spends waiting on evidence, a part identity or a spend approval is an hour that competes with the repair itself.
What AIMMS changesTakes the digital delay off the critical path so the work can start when the crew is ready rather than when the last piece of the case is assembled.
-
The right part is harder to get right and get fast.
143 weeks average lead time for a generator step-up transformer in Q2 2025, against 128 weeks for a standard power transformer Wood Mackenzie, Q2 2025 lead times, published October 2025, opens in a new tabDuring the repairWarranty position, installed variant and approved alternates all have to be settled before an order goes out, and the cost of settling them wrongly is measured in seasons rather than in restocking fees.
What AIMMS changesReconciles the installed variant against the parts record and usable stock, keeps the OEM correspondence and configuration evidence attached to the case, and prepares the sourcing route under your policies.
Together these say unavailability is rising and the equipment behind it is harder to get than it was. They say nothing about how much of any given outage is coordination rather than engineering. Only your own outage log answers that, which is what the calculator further down this page is for.
Published third-party sector research does not establish AIMMS effectiveness. Only a baselined deployment on the customer's own workflow can do that.
Price the outage hours that coordination, not engineering, is consuming.
Two numbers from your own outage log: how many corrective balance-of-plant events the unit takes a year, and how long each one sits between the trip and an approved, executable work path. The starting values are examples; replace them with your own records.
The starting values are an editable example, not your operating data or a measured result.
Move both controls. Use last year’s outage log, not our example.
The controls start with an editable example. No recovered hour is credited to AIMMS. Nothing you type here leaves your browser.
This section needs JavaScript to do your arithmetic. The figures beside it are the worked example for 14 balance-of-plant events a year at 17 waiting hours each. To use your own numbers, open the full value model.
238 hours a year
That is outage time spent assembling a decision, not executing one.
Enter an hourly value only if it represents costs or losses that shorter downtime could avoid.
Add an hourly value if you can support one.
Only an event count you changed and a valid hourly value you entered carry forward. Enter your own estimates of coordination time saved and avoidable downtime there; waiting time is not automatically savings.
See AIMMS in actionReturn capacity sooner, and prove it on your own unit.
Four operating outcomes the AIMMS workflow is built to produce around a balance-of-plant fault.
Your KPI contract On a generation or storage deployment, the deciding numbers come off your own outage log. Six KPIs, agreed and baselined on the selected unit before the first outage in scope, then reported against that baseline. See what the first deployment measures.
Build the outage value model on your own dispatch economicsMeasure the outage time that coordination, not engineering, is consuming.
Baseline the current outage workflow before deployment starts, measure results against that baseline, and expand only when the evidence supports the decision. Every number here comes off your unit, not off ours.
- Fault-to-ready-work time
- Elapsed time until the team has a reviewed, executable work path.
- Outage duration
- Unavailable or constrained generation and storage-support hours.
- Part certainty
- Installed variant, approved alternate, usable stock, and lead-time risk confirmed.
- Supplier and warranty cycle
- Elapsed time to a usable supplier or OEM decision.
- Mobilization readiness
- Work packages, parts, evidence, and approvals complete before arrival.
- Closeout completeness
- Required technical, warranty, approval, and return evidence captured.
The equipment waits while evidence, warranty, parts, suppliers, and authority converge.
An alarm or inspection can identify the problem quickly. The team still has to assemble OEM evidence, confirm the operating context, protect warranty, verify the exact component, find stock, mobilize a supplier, route approval, and complete the record.
Where elapsed time accumulates
- 01 Alarm or inspection finding
- 02 OEM evidence and history assembled
- 03 Warranty and safe checks confirmed
- 04 Part, spare, and supplier verified
- 05 Approval and mobilization moved
- 06 Return and closeout documented
Detection has economic value only when approved, executable work starts moving.
Modeled clock from the trip through outage closeout
19 of 28 modeled hours include 17 before work is ready and 2 for closeout after synchronization. Seven hours are physical repair.
- 0.5 h Trip logged, unit off line Waiting on coordination
- 4 h OEM manual, prior case and warranty position assembled Waiting on coordination
- 4.5 h Installed variant and usable spare confirmed Waiting on coordination
- 8 h Supplier mobilization and spend approval Waiting on coordination
- 7 h Physical work at the pump skid Hands on the asset
- 2 h Test, warm-up and synchronize Verified and returned
- 2 h Outage record and warranty file closed Waiting on coordination
Segment lengths follow the modeled premise stated further down this page. Hatched blocks are modeled waiting, the solid block is the physical work, and the green block is the plant’s own verified synchronization.
What the coordination share is worth on one unit in a year.
A 250 MW combined-cycle unit taking 14 corrective balance-of-plant events a year, each holding 17 hours between the trip and an approved, executable work path.
- 14 corrective events a year
- Balance of plant only: circulating water, feedwater, compressed air, cooling and auxiliary electrical. Not turbine or generator majors.
- 17 h waiting per event
- From trip logged to a path with the cause confirmed, the installed variant matched, the spare located and the spend approved. Excludes the physical work, testing and synchronization.
- 0 h improvement assumed
- No AIMMS effect is present anywhere in this arithmetic. The model sizes the delay and stops.
238 modeled coordination hours a year
Roughly 10 elapsed days a year inside the unit’s own outage clock, spent assembling a decision rather than executing one.
14 events multiplied by 17 waiting hours is 238 hours. Each input is an assumption we chose and printed, which is why the figure is hatched rather than solid. Replace them with your own in the calculator at the top of this page.
Modeled from the stated premise and the assumptions shown. No AIMMS effect is applied.
Start with a bounded asset family or outage workflow where delay has a visible cost.
The strongest first scope sits around balance-of-plant, storage-support, outage, commissioning, or warranty work without entering live-control authority.
Generation balance of plant
Pumps, compressors, cooling systems, fans, auxiliary electrical equipment, generators, and fuel or emissions-support assets.
Energy-storage support
BESS HVAC, thermal management, auxiliary power, inverter and container support, communications support, and warranty workflows.
Planned and forced outages
Work packages, inspection findings, job kits, supplier mobilization, contractor evidence, approvals, return, and closeout.
Commissioning and critical spares
As-built configuration, startup issues, OEM exceptions, warranties, installed variants, approved alternates, and long-lead spares.
The same platform. Built around your operation.
Explore the workflow, your business case and the controls behind it.
Written about power generation and storage.
Each of these answers one operating question in full, with its sources named in the text. They are the working detail behind the argument on this page.
- Guide One Power Fleet, Three Maintenance Models A gas turbine, a solar inverter and a battery container may support the same megawatt, but they fail differently, are serviced differently, and are warranted differently. What changes when one organisation has to maintain all three.
- Guide One Pump, Four Identifiers: Mapping the Alarm Tag to the Asset ID A pump has a SCADA tag, a CMMS asset record, a GIS feature and a spares line, and nothing makes them agree. How to build the mapping, what the worksheet looks like, and what to do with the identifiers that will never reconcile.
- Guide Grading the Autonomy Claim: The Questions to Ask a Vendor Whose AI Acts Without You A buyer-side interrogation instrument for maintenance AI. The questions, the evidence a good answer produces, and the red flag a bad answer leaves. Plus what the market actually publishes, and EQUA's answers to its own questionnaire.
- Guide The Maintenance Benchmark Provenance Ledger: Published, Practitioner Opinion, or Folklore Figure by figure: where each maintenance benchmark actually comes from, what was measured, the sample and the year, and whether it traces to a primary source at all. EQUA's own four numbers are graded by the same rule.
Direct answers for outage planning, plant management, commercial, and IT.
The first conversation should resolve where the workflow starts, how far the control boundary sits from live dispatch, and how the outage KPIs will be baselined.
Select a question to read the answer.
Does AIMMS replace our outage, EAM, CMMS, ERP, historian, or monitoring systems?
No rip and replace. AIMMS connects permitted information across existing systems and coordinates authorized digital work. A single voice-first interface helps teams find context and move work forward; business-system connections are mapped, permissioned, and validated with your team.
Where should a generation or storage deployment start?
Start with a workflow where delay matters. Examples include a balance-of-plant pump, BESS thermal-management support, outage readiness, commissioning deficiencies, or warranty coordination. Agree on the control boundaries and measures with your team.
Can AIMMS issue BESS, generator, or plant-control commands?
No. Direct charge, discharge, BMS, generator, fire-system, setpoint, interlock, and other live-control writes are permanently outside AIMMS scope. Qualified customer personnel retain operating and return authority.
How does AIMMS help with warranty and OEM coordination?
It connects the fault, installed configuration, operating evidence, relevant procedure, warranty terms, prior correspondence, required part, supplier action, approval, and final repair record so the case moves with complete context.
How does a first deployment start?
Begin with guidance for a selected workflow. Your team can use natural voice or text in one interface, then expand autonomous digital coordination as the work, permissions, and approvals are validated. Timing depends on data readiness and your requirements.
Where do the NERC and supply-chain figures on this page come from?
The benchmark band cites NERC and Wood Mackenzie inline. The stated-premise model prints its assumptions beside the hatched figure.
Tell us how your team works. We’ll make the next step concrete.
See AIMMS in actionPut AIMMS to work for your power operation.
We will understand your maintenance challenges, explore potential value, and show a relevant example as time permits.