All learning series · Supplemental add-on · Part 1
Reliability Strategies
Connect equipment functions and failure modes to justified maintenance tasks.
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 Reliability Strategies? 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 Reliability Strategies?
Reliability Strategies turns an operating context into a maintenance strategy for an asset class. It is a supplemental add-on with its own user tier. It does not replace the job plan that Manage will run.
Before configuration
The user tier can be Premium, Base or Limited. There is no Reliability Strategies quantity on the 9.2 install table. Have an asset class and an agreed function before you import a strategy.
Before the first successful journey
One asset class, one operating context, and a strategy with tasks you can see.
Before production use
Someone owns the library, and a strategy becomes a job plan only through a deliberate step. Reading a strategy is not the same as generating work.
Licensing, entitlement and AppPoints
Reliability Strategies is a supplemental add-on. The MAS 9.2 licensing guidance prices it at the Premium, Base or Limited user tier. The install table does not list a Reliability Strategies install quantity. Do not describe it as a zero-AppPoint product, and do not copy Asset Investment Planning’s 200-point install onto it. The user’s actual draw is the Limited, Base or Premium ratio for the way that user is licensed, authorized or concurrent, after the security group is applied.
Keep four facts separate for Reliability Strategies. 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 Reliability Strategies is deployed and the strategy library opens. Record its version. Installed means the application opens. Configured means a strategy is linked to an asset class and an operating context. Usable means a reliability engineer can open that strategy and see its tasks.
Foundation configuration
You need the asset classification that the strategy applies to, and enough of an asset record to know the equipment the context describes. Failure codes and job plans are the Manage side of the same decision. They are the destination of a strategy, not a prerequisite for opening the library. Calendars and crews matter later, when the strategy becomes scheduled work.
Product configuration
Set the operating context: duty, environment and the function the asset must perform. Find or create a strategy for that class. Map tasks to the job-plan language your planners use when you are ready to generate work. Grant library editors and strategy readers different groups. Review any default strategy content before you treat it as your site’s practice.
Infrastructure and integration
The application runs with Manage. A strategy content service, if your deployment uses one, needs to be reachable. No map, historian or optimization service is required to read a strategy.
Data and operational readiness
The first journey needs one asset class, one context and one strategy whose tasks you can name. A strategy with no tasks is an empty record. A missing application is deployment or security. A job plan that does not match the strategy is a later mapping step, not a failed install.
Setup order for a strategy
- 1. User tier: Premium, Base or Limited No separate install quantity in the 9.2 table.
- 2. Application deployed Library opens.
- 3. Asset class and operating context Function, duty and environment.
- 4. Strategy tasks Visible on the strategy before any job plan is generated.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Premium, Base or Limited user entitlement | The guidance prices this supplemental add-on on the user tier. It publishes no install quantity. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | A reliability engineer on Base, or on Limited or Premium if that is how they are licensed. | Grant the application and read the tier and the points reserved or drawn. | The team looks for an install charge that the table does not list, or assumes the product draws nothing. | Use the user-tier ratio that matches the dashboard. Leave install points for products that have an install line. | Licensing in Maximo Application Suite 9.2 |
| Reliability Strategies deployed | The library is a component with its own version. | Mandatory | Suite administration → Catalog, Manage workspace | The strategy application opens. | Record the version and open one strategy list. | The menu has no strategy library. | Deploy the component for this Manage workspace. | Modules and applications in Maximo Application Suite 9.2 |
| An asset class | Strategies apply to a class, not to a single work order. | Mandatory | Classifications, and the class the strategy names. | Classification PUMP, centrifugal. | The strategy and the classification use the same class. | Tasks exist and no asset class can receive them. | Create or select the class before you adopt the strategy. | Modules and applications in Maximo Application Suite 9.2 |
| An operating context | The same pump in a different duty is a different strategy. | Mandatory | The context fields on the strategy: function, duty, environment. | Duty: continuous clean-water service, indoor. | Read the context back with the strategy. | A generic strategy is applied to every pump. | Write the context the tasks assume. | Modules and applications in Maximo Application Suite 9.2 |
| Tasks you can read on the strategy | The journey is the content of the strategy, not only the title. | Mandatory | The strategy task list. | At least three tasks with an interval or a condition. | Open the strategy as a second user and name the tasks. | The record opens and the task list is empty. | Load or author the tasks before you talk about generating a job plan. | Modules and applications in Maximo Application Suite 9.2 |
| A deliberate path to a job plan | Generating Manage work is a second step with its own review. | Optional | Job Plans, after the strategy is accepted. | One training job plan created from the strategy, status draft. | Compare task for task. Leave it in draft. | A strategy import writes active job plans across the class. | Keep generation off until the context is accepted. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- The user’s tier is Premium, Base or Limited and the dashboard shows that draw. No install quantity is expected.
- The application opens.
- An asset class exists.
- You can describe the function and duty of one training asset.
B. Ready for the first end-to-end journey
- A strategy for that class shows its context and its tasks.
- A second person can read the same tasks.
- No active job plan was generated unless you chose that step.
- The tasks are still the strategy’s tasks when you reopen the record.
C. Ready for production operation
- The library has an owner and a review before a strategy is applied to a class.
- Job-plan generation is a separate approval.
- Asset Investment Planning and Health, if you use them, stay separate scores and plans.
- The user tier is rechecked when groups change, because this product follows the user tier rather than an install line.
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.
- Reliability Strategies access and a training asset class.
- A reliability practitioner's agreed operating context and a small example strategy.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Reliability Strategies supports reliability analysis and the review of failure modes. The function is what the equipment must achieve; a failure mode describes how that function can be lost.
A library strategy is a starting point. The equipment's duty, environment and consequences determine whether a proposed task fits the local operating context.
Topics in this series
- Functions and failure modes
- Strategy libraries
- Consequences and task selection
- Review and implementation
- Feedback and strategy revision
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Describe the required function of one training pump, including its duty.
- Find or create a relevant strategy using the available library and installed application procedure.
- Review one failure mode, cause, effect and consequence; remove assumptions that do not fit the training context.
- Select a maintenance activity and explain what evidence it provides or which failure it mitigates.
- Review the strategy and trace how an approved activity would become a controlled job plan or maintenance task in your implementation.
03 · Practical example
Fictional teaching example
A standby pump may appear healthy during normal operations because it rarely runs. A functional test addresses failure to start; a calendar bearing replacement addresses a different failure mechanism. The task choice must follow the analyzed failure.
04 · Practice and verify
Create a worksheet with function, failure mode, consequence, task, interval rationale and review owner for three failure modes.
Expected result
Every proposed task has an explicit reason. Tasks that do not address the selected failure mode are rejected or redesigned.
Common mistakes
- Copying library intervals without reviewing the operating context.
- Treating an imported strategy as implemented maintenance.
05 · Advanced concepts
Assess task effectiveness against observed failures and inspection results. Control strategy revisions and their impact on active job plans and PMs.
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