Maximo for Nuclear on MAS 9.2
🎯 Who this is for: Anyone responsible for running, buying, licensing, or auditing IBM Maximo in a nuclear plant — reliability and engineering leads, operations and work control, regulatory and QA, and the IT program owners who have to answer "does Maximo still do nuclear, and what do we actually get?"
Series: Series Index — Maximo for Nuclear on MAS 9 | 7 parts | Total read time: ~2 hours
📖 Why This Series Exists
A nuclear plant does not ask the same questions of an EAM that a manufacturing plant or a transmission utility does. It asks: Which of my regulatory obligations does this system cover out of the box, and which do I have to configure? Where does the Technical Specification live? What runs my Corrective Action Program? Is nuclear tagout really different from Lockout/Tagout — and if so, how? And is this product even still supported, or did it get retired when Maximo became a suite?
Those questions have real answers, and they are not the same answers a generalist Maximo course gives. Maximo Nuclear is a distinct industry solution — historically marketed as 31 new applications plus 16 extensions on top of core Manage, grouped into six nuclear-specific module families. It carries its own regulatory drivers (10 CFR 50, 10 CFR 50.36, 50.59, 50.65, NQA-1, and INPO programs), its own licensing posture (Premium AppPoints only), and, in the MAS 9.x era, its own patch stream.
This series maps that nuclear-specific reality across seven parts. Every claim is grounded in documented IBM behavior and the named regulatory framework it serves. And where a capability has no IBM-named application — the Maintenance Rule and AP-913 scoping are the big ones — we say so, and we explain the configuration path, instead of pretending an app exists that does not. That honesty is not a hedge; it is the single most useful thing a nuclear implementation team can carry into a statement of work or an audit.
<aside>
💡 Key insight: The organizing principle of this whole series is a single line: the regulation is the spec. Every nuclear application exists because a regulation demands it. Read the applications through their regulatory drivers — not through the UI — and you learn how to scope an implementation and survive an audit. Read them as a feature list and you will over-claim the five capabilities that are configuration, and get caught.
</aside>
🧭 Where This Series Fits
This series is deliberately nuclear-specific. It is not a general MAS 9 course, and it does not re-argue the platform-level upgrade case. There is a division of labor across TheMaximoGuys series so you never read the same thing twice:
| If you want… | Read… |
|---|---|
| The generic Maximo 7.6-versus-MAS platform delta (architecture, Carbon UI, OpenShift, generic AppPoints, MAS AI) | THINK-MAS series |
| Feature-by-feature MAS 9 capability walkthroughs (Work Orders RBA, Assistant, Health, Monitor, Predict) | MAS-FEATURES series |
| Core work management, PMs, job plans, mobile execution | MAS MANAGE series |
| The nuclear industry solution: apps, regulatory drivers, licensing, release reality | This series |
<aside>
💡 Key insight: THINK-MAS and MAS-FEATURES already own the "why upgrade at all" story. If a stakeholder needs the platform business case, send them there. This series answers the question that only a nuclear operator asks: given that we are on MAS, what does the nuclear solution actually give us, and what do we have to build?
</aside>
📊 The Series at a Glance
| Part | Title | Focus Area | Read Time |
|---|---|---|---|
| 1 | Product Lineage & AppPoints Premium | MNP 7.6 → Maximo Nuclear on MAS, survived the cull, the EOS clock, Premium-only licensing, part number 5737-M66 | 16 min |
| 2 | Technical Specifications & LCO Tracking | Tech Specs (Nuc), Surveillance Requirements, LCO action-statement timers, surveillance frequency and grace discipline | 17 min |
| 3 | Configuration Control & Nuclear Work Packages | Configuration Change Designer, Changes, Releases, Configuration Items, WOT (Nuc), Impact Plans, hold points | 18 min |
| 4 | The Maintenance Rule (10 CFR 50.65) | The honest no-named-app reality; Assets (Nuc), failure codes, Condition Monitoring, Maximo Health, AP-913 | 17 min |
| 5 | Corrective Action Program & Clearance/Tagout | Condition Reports (Nuc) as the CAP engine, Solutions library, Clearances, Clearance Groups, Sign On/Off, Permits | 18 min |
| 6 | The Regulatory Crosswalk | Capability-to-regulator map across 10 CFR 50, NRC Reg Guides, INPO, and ASME NQA-1 | 16 min |
| 7 | What's New in MAS 9.x | Nuclear-inherited 9.0/9.1 AI, the 9.2 Feature Channel caveat, the AI Service model change, nuclear-vs-generation boundary | 17 min |
🔑 What Makes Nuclear Different
Before the part-by-part guide, three ideas run through every part. Internalize them and the series reads as one argument rather than seven articles.
Named apps carry most of it; configuration carries the rest. Condition Reports, Tech Specs, Surveillance Requirements, LCO Tracking, Configuration Change Designer, Purchasing (Nuc) — these are real, purpose-built applications. The Maintenance Rule, AP-913 scoping, hold points, OPEX, and nuclear e-signature are patterns you configure. Both are defensible; only one is an honest claim of a shipped app.
Maximo supplies evidence; it does not make the judgment. Every regulatory obligation Maximo touches, it touches by producing a record — a corrective action, a surveillance result, an LCO timer, a procurement audit trail. The compliance determination stays with a human program owner. That is the correct division of labor, and it is what a regulator expects.
Version selection is a validation activity. Because the nuclear solution now ships on OpenShift Continuous Delivery, "what version am I on" is a change-control question. The 9.2 Feature Channel is explicitly non-production evaluation, and Nuclear has its own APAR/DT stream. Treat version selection as validation, not IT convenience.
<aside>
💡 Key insight: If you remember only one thing from the index, make it this triad: named-apps-plus-configuration, evidence-not-judgment, and version-as-validation. Every part is an application of one of the three. They are also, not coincidentally, the three places an analyst deck most often goes wrong — claiming phantom apps, implying compliance automation, and treating a Feature Channel build as production.
</aside>
🗂️ The Six Nuclear Module Families
The "31 applications plus 16 extensions" figure becomes concrete when you see the six module families it spans. This grounds the scope — and shows why the series is organized the way it is.
| Module family | Representative applications | Covered in |
|---|---|---|
| Asset & Location (nuclear-extended) | Assets (Nuc), Locations (Nuc), Quick Assets/Locations (Nuc) | Parts 4, 3 |
| Condition Reports | Condition Reports (Nuc), Solutions, Commitment Tracking | Part 5 |
| Configuration Change Management | Configuration Change Designer, Changes, Releases, Configuration Items | Part 3 |
| Operational Management | Tech Specs, Surveillance Requirements, LCO Tracking, Clearances, Lineups, Duty Stations, Impact Plans | Parts 2, 5, 3 |
| Permits | Permits (Nuc), Quick Permits (Nuc) | Part 5 |
| Nuclear-extended standard modules | Planning, PM (Nuc), Purchasing (Nuc), Work Orders (Nuc) | Parts 3, 4, 6 |
The families are not an abstraction — they are why an auditor's question about, say, corrective action resolves to the Condition Reports family, while a question about Technical Specifications resolves to the Operational Management family. The crosswalk in Part 6 ties every family to its regulations in one table.
🧩 Part-by-Part Guide
Part 1: Product Lineage & AppPoints Premium
[Read Part 1 — Product Lineage & AppPoints Premium](/blog/mas-nuclear-product-lineage-apppoints) · 16 minutes
Two generations of the product line, and conflating them is where most analysis goes wrong. This part draws the line between legacy Maximo for Nuclear Power (MNP) 7.6 and the current Continuous Delivery status.
You learn: why Nuclear survived the industry-solution cull when Life Sciences did not; why the 7.6.1.x End of Support date (Sept 30, 2025) is a nuclear audit issue, not just an IT one; the Premium-only AppPoints tier and part number 5737-M66; and how to build a per-persona licensing model with the Authorized-versus-Concurrent break-even.
Part 2: Technical Specifications & LCO Tracking
[Read Part 2 — Technical Specifications & LCO Tracking](/blog/mas-nuclear-tech-specs-lco) · 17 minutes
The Operational Management (Nuc) module is the regulatory core, and this part covers its heart: Tech Specs (Nuc) per 10 CFR 50.36, Surveillance Requirements that prove each Tech Spec is met, and LCO Tracking with its action-statement timers.
You learn: how Tech Specs implements the Technical Specification register; how Surveillance Requirements works as the "prove it" engine; how LCO Tracking's timers operationalize completion-time discipline (walked through a full worked EDG example); and where surveillance frequency and the 25% grace live in Maximo's frequency machinery.
Part 3: Configuration Control & Nuclear Work Packages
[Read Part 3 — Configuration Control & Nuclear Work Packages](/blog/mas-nuclear-configuration-control) · 18 minutes
Design change under 10 CFR 50.59, and the work packages that execute it. This part covers the Configuration Change Management module and how nuclear work packages assemble in Work Order Tracking (Nuc), with Impact Plans and job-plan hold points.
You learn: how Configuration Change Designer drives revision requirements and the 50.59 screen-then-evaluate gate; how Changes and Releases work as work-order classes; how Impact Plans protects operability before work; and why hold points, QC points, and inspection points have no named app — traced through a valve-EC worked example.
Part 4: The Maintenance Rule (10 CFR 50.65) in Maximo
[Read Part 4 — The Maintenance Rule (10 CFR 50.65) in Maximo](/blog/mas-nuclear-maintenance-rule) · 17 minutes
The honest one. There is no application called "Maintenance Rule" in Maximo Nuclear. This part explains how 10 CFR 50.65 is actually implemented — and how AP-913 rides the same configuration-not-app pattern.
You learn: why "no named app" is not "not supported"; the Assets (Nuc) + failure codes + Condition Monitoring + Maximo Health pattern for (a)(1)/(a)(2) monitoring (walked through a service-water-pump slip to (a)(1)); how AP-913 scoping uses classifications, the critical-component flag, and Reliability Strategies; and what NRC Reg Guide 1.160 Rev 3 expects.
Part 5: Corrective Action Program & Clearance/Tagout
[Read Part 5 — Corrective Action Program & Clearance/Tagout](/blog/mas-nuclear-cap-clearance-tagout) · 18 minutes
The CAP backbone and the safety controls around work. This part covers Condition Reports (Nuc) as the CAP engine under 10 CFR 50 App B XVI, the Solutions library, and the nuclear tagout stack.
You learn: how Condition Reports runs the full CAP loop with significance grading (SCAQ/CAQ); how the Solutions library enables operating-experience reuse (with OPEX honestly flagged as no-named-app); why nuclear Clearances are richer than core Lockout/Tagout — walked through a pump-isolation example; and how Permits and Sign On/Off wrap the work package.
Part 6: The Regulatory Crosswalk
[Read Part 6 — The Regulatory Crosswalk](/blog/mas-nuclear-regulatory-crosswalk) · 16 minutes
One table you can hand to an auditor or an analyst: the capability-to-regulator crosswalk across 10 CFR 50, NRC Reg Guides, INPO programs, and ASME NQA-1.
You learn: the full capability → application → regulation map with the gaps flagged; where each 10 CFR 50 Appendix B criterion lands; how INPO frameworks (AP-913, OE) map to configuration; where NQA-1 shows up (procurement, records, quality controls); and how to answer an auditor's traversal question straight down the table.
Part 7: What's New in MAS 9.x
[Read Part 7 — What's New in MAS 9.x](/blog/mas-nuclear-whats-new-mas92) · 17 minutes (Series Finale)
The grounded read on the 9.x era for nuclear — what it inherits, and what its release governance must account for.
You learn: what 9.0 and 9.1 gave nuclear by inheritance (Carbon, RBAs, Assistant, AI Service, Reliability Strategies); why a Feature Channel build is not production-entitled evidence; what the AI Service model change (Granite → GPT-OSS-120B) means for AI-assisted classification; and why Maximo Nuclear is a separate solution from Maximo for Utilities and Renewables.
🧭 Recommended Reading Paths
Reliability / Engineering Lead
"I own equipment reliability and the maintenance basis."
Read Part 4 → Part 2 → Part 3. Start with the Maintenance Rule reality, then see how Tech Specs and configuration control feed it.
Regulatory / Licensing / QA Lead
"I own audit and compliance evidence."
Read Part 6 → Part 5 → Part 2. Start with the crosswalk, then CAP and Tech Specs — the three places auditors look first.
Operations / Work Control Lead
"I own the work and the controls around it."
Read Part 5 → Part 3 → Part 2. Start with clearances and CAP, then how work packages assemble and how Tech Specs constrain them.
IT / Program Owner
"I own the platform, licenses, and roadmap."
Read Part 1 → Part 7 → Part 6. Start with lineage and licensing, then the 9.x release reality, then the crosswalk for scoping.
💡 Key Themes Across the Series
Nuclear survived, and it is entitled — not free. Maximo Nuclear is an active Manage industry solution under one MAS part number, but access lands users at the Premium AppPoints tier. Knowing this up front kills two bad narratives: "nuclear was retired" and "turning it on is free."
Named apps carry most of it — configuration carries the rest. Condition Reports, Tech Specs, Surveillance Requirements, LCO Tracking, Configuration Change Designer, and Purchasing (Nuc) are real, purpose-built applications. The Maintenance Rule, AP-913 scoping, hold points, OPEX, and nuclear e-signature are patterns you configure. Both are defensible; only one is an honest claim of a shipped app.
The regulation is the spec. Every nuclear application exists because a regulation demands it. Reading the apps through their regulatory drivers — not the UI — is how you scope an implementation and survive an audit.
Release governance is a nuclear concern. In the 9.x era, "what version am I on" is a change-control question. The 9.2 Feature Channel is explicitly non-production evaluation, and Nuclear has its own APAR/DT stream. Treat version selection as a validation activity, not an IT convenience.
🧰 How to Use This Series
- Building a statement of work? Use Parts 2–5 to name the real applications and Part 6 to name the five configuration gaps honestly. The difference between "we ship a Maintenance Rule module" and "we configure 50.65 monitoring through Assets, failure codes, Condition Monitoring, and Health" is the difference between a clean audit and an awkward one.
- Facing an analyst or McKinsey-style review? Part 1 refutes "nuclear was retired" and "AppPoints is obviously cheaper"; Part 6 refutes "Maximo doesn't cover nuclear compliance" row by row; Part 7 refutes "MAS 9.2 is cosmetic" and "nuclear just inherits base Manage."
- Preparing for an audit? Rehearse the Part 6 traversals — capability to application to record — so an inspector's question becomes a route, not a hunt.
- Setting the roadmap? Part 1 (lineage, EOS clock, licensing) and Part 7 (Feature Channel governance, AI Service change) are your two anchors.
References
- IBM Maximo for Nuclear Power — Continuous Delivery overview (IBM Documentation)
- Configuring Maximo Nuclear (IBM Documentation)
- MAS Manage — Add-ons and industry solutions (IBM Documentation)
- 10 CFR Part 50 — Domestic licensing of production and utilization facilities (NRC)
- Maximo Secrets — Nuclear Applications app map series
Start the Series
Begin with [Part 1 — Product Lineage & AppPoints Premium](/blog/mas-nuclear-product-lineage-apppoints), or jump to the part your role needs using the reading paths above.
About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.
Published by TheMaximoGuys | July 2026
Posam Lakshminarayana
Venkat Achanta