All learning series · Industry solution · Part 1
Maximo Nuclear
Learn the relationship between work, operational controls and clearance records.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Maximo Nuclear? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Maximo Nuclear?
Nuclear ties work to the permit, the clearance and the condition report the plant process requires. It is an industry solution at Premium or Limited, with no install quantity on the 9.2 table.
Before configuration
Have the plant process for this training site: which record must exist before work is released. Create Condition Report is self-service at 0 AppPoints. The people who prepare permits are not on that row.
Before the first successful journey
One training work order, the equipment, and the permit or condition-report record that work requires.
Before production use
Status mappings and who may release work have owners. This course uses fictional equipment.
Licensing, entitlement and AppPoints
Nuclear is a Maximo Manage industry solution priced at Premium, or at Limited when the three modules include the Nuclear modules. The modules page lists Configuration Change (Nuc), Operation Management (Nuc), Permits (Nuc) and Condition Report (Nuc). The install table does not list a Nuclear install quantity. Creating and viewing condition reports in Create Condition Report is self-service at 0 AppPoints. Permit preparation and work release use the Premium or Limited tier.
Keep four facts separate for Maximo Nuclear. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Confirm the Nuclear applications for permits, condition reports and related work open, and record the version. Installed means those applications are on the menu. Configured means the training process’s required record types exist. Usable means a work order cannot be treated as ready until the record your process requires is in place.
Foundation configuration
You need the site, the equipment or location, people for the requester and the reviewer, and the work-order statuses your process uses. Clearances, permits, lineups and condition reports are Nuclear records on top of that work order. Classifications and impact codes are configuration. A calendar matters when the permit has a window. It is part of the permit, not a substitute for it.
Product configuration
Map the training process: work order, then the permit, clearance, impact or lineup it requires, then the status that means released. Grant requesters the self-service condition-report path if that is all they do. Grant preparers the Permits module. Review default status changes that skip the permit.
Infrastructure and integration
Nuclear runs in Manage. A document or records system for the official permit is an external system with its own access. No GIS or optimization service is required for the first permit link.
Data and operational readiness
The first journey needs one fictional equipment record, one work order and the related Nuclear record. Release is allowed only when that record is complete. Missing equipment is data. A status that jumps to released with no permit is configuration. A hidden application is entitlement or security.
Setup order for a permitted work order
- 1. Nuclear entitlement Premium or Limited. Condition-report self-service is a narrower row.
- 2. Site, equipment, people, statuses The work-order backbone.
- 3. The permit or condition report the process requires Named before the journey.
- 4. Release only with that record The status map enforces the order.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Nuclear entitlement at Premium or Limited | Permit and operations users take the industry tier. Create Condition Report can be the 0-AppPoint self-service row. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | A permit preparer on Premium or qualifying Limited. A requester limited to Create Condition Report. | Read both users on the dashboard. | The requester is given every Nuclear module and still treated as self-service. | Split the groups to match the self-service list. | Licensing in Maximo Application Suite 9.2 |
| Nuclear modules for the process you will run | The modules page separates configuration change, operations, permits and condition reports. | Mandatory | Suite administration → Catalog, Manage workspace | The permit or condition-report application you named opens. | Open that application and record the product version. | A generic work order is used with no Nuclear record type. | Enable the module this process uses. | Modules and applications in Maximo Application Suite 9.2 |
| Equipment and a work order in the site | The Nuclear record hangs off real equipment and work. | Mandatory | Assets or locations, Work Order Tracking. | Equipment PUMP-N and work order WO-N, both fictional, in the training site. | Read both records back. | The permit has no equipment. | Create the equipment and the work order first. | Modules and applications in Maximo Application Suite 9.2 |
| The related permit, clearance or condition report | The process you wrote down is the prerequisite, not every Nuclear module at once. | Mandatory | The Nuclear application for that record type. | One permit linked to WO-N, or one condition report if that is the chosen process. | Open the work order and navigate to the related record. | The work order is released with no related record. | Create the related record before the release status. | Modules and applications in Maximo Application Suite 9.2 |
| A status map that matches the process | Released has to mean the permit is in place. | Mandatory | Work-order statuses and the Nuclear status you use for release. | WO-N stays unreleased until the permit is complete. | Try to advance the work order without the permit and observe the status you get. | Any user can move the work order to a released status. | Change the status flow or the signature option so release requires the record. | Modules and applications in Maximo Application Suite 9.2 |
| Roles for requester and preparer | Creating a condition report and preparing a permit are different entitlements. | Mandatory | Manage → Security → Security Groups, and the suite user type | REQ-N on Create Condition Report. PREP-N on Permits. | Each user completes only their step. | The requester prepares and approves the permit. | Narrow the requester to the self-service applications. | User access and entitlements in MAS 9.1 and later |
A. Ready to configure
- Nuclear is entitled at Premium or Limited, and self-service is used only for the condition-report actions the guidance lists.
- The application for your chosen record type opens.
- The site, one equipment record and the status names exist.
- The process owner has named which related record gates release.
B. Ready for the first end-to-end journey
- WO-N and the equipment save.
- The permit or condition report is linked.
- Release happens only with that record in place.
- The requester cannot perform the preparer’s step.
C. Ready for production operation
- Status maps and authorisations have a process owner.
- Self-service users match the Create Condition Report description.
- Official records outside Manage have an owner and a retention path.
- Training equipment stays identifiable so it is not mistaken for plant equipment.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- Nuclear training environment and an approved training process.
- Fictional equipment and test roles; this is an application-learning exercise.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Nuclear adds records such as clearances, lineups, condition reports, surveillance requirements and technical specifications. These records represent distinct parts of an operating process.
Configuration options can apply at organization or site level. Establish the ownership and scope of an option before testing it.
Topics in this series
- Operational record model
- Site and organization settings
- Clearance/work relationships
- Roles and transitions
- Exceptions and process assurance
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Choose a training work order and identify its equipment and site.
- Map the related clearance, permit, impact or lineup records required by the training process.
- Inspect configured responsibilities and state transitions without changing shared operating rules.
- Follow the approved training sequence and retain the record relationships and history.
- Demonstrate a missing prerequisite and observe whether the configuration blocks or flags the transition.
03 · Practical example
Fictional teaching example
A fictional maintenance task has completed physically but still has an unresolved operational-control step. The example shows why one record's completion cannot stand in for every linked process.
04 · Practice and verify
Produce a dependency table: record, owner, prerequisite, expected state and observed state.
Expected result
Every required handoff has its own recorded state and responsible role; missing prerequisites are visible.
Common mistakes
- Assuming all configuration options are site-specific.
- Using work completion as proof that every operational control is complete.
05 · Advanced concepts
Examine tag sharing, overlapping work and process revisions with the responsible process owner. Preserve the governing procedure alongside the configuration tests.
IBM references
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench