IBM Maximo for Nuclear Power
Tech specs, clearances, condition reports, and configuration control on IBM Maximo Nuclear, plus the upgrade path from Maximo 7.6 to MAS 9
Overview
Nuclear plants work under quality assurance, technical specification, and maintenance rules that shape every work order on safety-related equipment. IBM Maximo Nuclear, historically sold as Maximo for Nuclear Power, is an active industry solution for Maximo Manage in MAS 9. It adds named applications for tech specs, surveillance requirements, LCO tracking, clearances, lineups, impact plans, permits, condition reports, and configuration change control. Some programs plants expect to find, such as the Maintenance Rule, and AP-913 critical-component classification, have no dedicated application; they are built from asset history, condition data, Reliability Strategies, and Maximo Health. We map each Maximo Nuclear application to the requirement it serves, say plainly where configuration fills the gap, and plan the move from Maximo Nuclear 7.6 to MAS 9 with the software QA and change control a licensed site needs.
What nuclear power maintenance leaders are prioritizing
Maximo Nuclear 7.6 is past end of standard support
IBM ended regular base support for Maximo Asset Management 7.6.1.x on September 30, 2025, including Maximo for Nuclear Power 7.6.1.x and 7.6.2.x. Extended and Sustained Support are available to eligible customers who show an upgrade roadmap. In MAS 9, Maximo Nuclear versions align with Manage, Work Centers are replaced by role-based applications, and the MAS 9.2 Feature Channel is for non-production evaluation only.
The problem
94 operating us reactors. Nuclear reactors operated by US electric utilities, per EIA (August 2025)
92% fleet capacity factor, 2024. Capacity factor of the US nuclear reactor fleet in 2024
34 days average refueling outage, 2024. Through July 31, 2024, compared with an average of 38 days in 2023
10 CFR 50 Appendix B requires controlled procedures, calibrated test equipment, corrective action, and retrievable QA records for safety-related work, so the EAM has to produce an auditable trail.
Technical specification surveillances have frequencies and grace periods, and an inoperable component starts LCO action statements that operations must track without gaps.
Design changes must be screened under 10 CFR 50.59 and kept consistent across design documents, the plant, and maintenance records.
Refueling outages compress large volumes of work into a few weeks, and every delay extends the time the unit is offline.
Maximo has no application named Maintenance Rule. Performance monitoring and risk inputs for 10 CFR 50.65 have to be built from asset history, condition data, and work management.
Moving from Maximo Nuclear 7.6 to MAS 9 changes the platform, the Java runtime, and how customizations are delivered, all under nuclear software QA and change control.
How we fix it
Tech Specs (Nuc) holds the technical specification register, Surveillance Requirements (Nuc) defines required tests, and PM (Nuc) with PM Frequencies (Nuc) generates surveillance work with grace periods. LCO Tracking (Nuc) follows action statements against the tech specs.
AI in practice
Surveillance and LCO status can be surfaced on operations and work control dashboards so overdue items are visible before they become findings.
Clearances (Nuc) replaces core Lockout/Tagout with boundary definition, tagging, approvals, clearance groups, temporary lifts, and worker sign on/off. Work orders are related to the clearance, and Permits (Nuc) and Impact Plans (Nuc) complete the work package.
AI in practice
Impact Plans and work-week scheduling in Maximo Scheduler can be configured to supply inputs for Maintenance Rule (a)(4) risk assessment, with risk tools integrated rather than replaced.
Condition Reports (Nuc) documents nonconforming conditions, significance, cause evaluation, and corrective actions tracked through follow-up work, supporting Appendix B Criterion XVI. Commitment Tracking (Nuc) follows regulatory commitments.
AI in practice
The MAS AI Service can suggest cause classifications and draft content from history as decision support, with qualified staff approving every result.
Configuration Change Designer, Changes (Nuc), Releases (Nuc), and Configuration Items (Nuc) record change screening and implementation. This, not Asset Configuration Manager, is the nuclear configuration-control tool.
AI in practice
Changes can be linked to affected assets, job plans, and documents so maintenance records follow the approved design.
Critical-component flags, Reliability Strategies FMEA content, and Maximo Health scores support AP-913 and PM-basis work as a configuration pattern. Purchasing (Nuc), qualified suppliers, and QA-flagged items support 10 CFR Part 21 and commercial-grade dedication.
AI in practice
Maximo Health can score asset condition and risk from work history and condition data to help prioritize the equipment reliability backlog.
Walk through your assets, integrations, and compliance needs with an engineer who has configured Maximo for your industry.
The platform
Compliance
Condition Reports support corrective action, controlled job plans support procedures, calibration records support test equipment control, and e-signature and e-audit support QA records.
Failure and performance history, condition monitoring, and Health scoring provide evidence for monitoring. There is no named Maintenance Rule application; it is a configuration pattern.
Tech Specs, Surveillance Requirements, and LCO Tracking (Nuc) hold the register, required tests, and action statements.
Configuration Change Designer, Changes, and Releases (Nuc) record change screening and implementation.
Purchasing (Nuc) terms, qualified suppliers, QA-flagged items, and receiving inspection support defect reporting and dedication records.
Implements the Maintenance Rule and endorses NUMARC 93-01. Maximo asset history is an evidence source for performance monitoring.
Work-week scheduling in Maximo Scheduler, Quick WOs (Nuc) for minor work, and schedule adherence reporting support the T-week process.
ASME NQA-1 and INPO AP-913
NQA-1 relies on the same QA record controls as Appendix B. AP-913 equipment reliability is supported through criticality classification, Reliability Strategies, PM basis, and Health.
Yes. IBM Maximo Nuclear, historically called Maximo for Nuclear Power, is an active industry solution for Maximo Manage in MAS. It models tech specs, surveillance requirements, LCOs, clearances, lineups, duty stations, impact plans, permits, and condition reports.
Yes. Only the legacy 7.6 line is retired: regular base support for Maximo Nuclear 7.6.1.x and 7.6.2.x ended on September 30, 2025. In MAS 9, Maximo Nuclear versions align with Manage.
It is entitled through the MAS AppPoints pool with no separate part number, but users who access industry-solution applications need Premium or Limited entitlement rather than Base. The AI Service is licensed separately.
In Maximo Nuclear, Clearances (Nuc) replaces core Maximo's Lockout/Tagout application. It adds boundary definition, tagging, approvals, clearance groups, temporary lifts, a kiosk, and worker sign on/off, and work scope is defined by relating work orders to the clearance.
Tech Specs (Nuc) holds the tech spec register, Surveillance Requirements (Nuc) defines the required tests, and PM (Nuc) with PM Frequencies (Nuc) generates surveillance work with frequencies and grace periods. LCO Tracking (Nuc) tracks limiting condition for operation action statements.
There is no application named Maintenance Rule. It is implemented through asset performance and failure data, condition monitoring, critical-component classification, and optionally Maximo Health, while (a)(4) risk assessment usually relies on plant risk tools integrated with work management.
Condition Reports (Nuc) documents nonconforming conditions, significance, cause evaluation, and corrective actions tracked through follow-up work, supporting Appendix B Criterion XVI. Its predefined workflows follow the Standard Nuclear Performance Model.
EIA reports that US refueling outages in 2024 averaged 34 days through July 31, compared with 38 days in 2023. Outage schedules are built well in advance, which is why work management and clearances need to be ready long before the outage starts.
Maximo Nuclear has nothing SMR-specific, but the same tech spec, clearance, and corrective action model applies. New operators benefit from setting up the asset and data model before first criticality.
Work Centers were deprecated in MAS 8.9 and removed by MAS 9.0, replaced by role-based applications. Mobile operator rounds should be validated against current Maximo Mobile and Maximo Nuclear release notes.
Tell us where your maintenance program is today. We will tell you honestly what Maximo can and cannot do for it.
