All learning series · Suite application · Part 1
Maximo Health
Explain an asset health score before acting on its color.
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 Health? 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 Health?
Health scores a group of assets from the contributors you configure. Have the assets and the inputs before you trust a score. Health is not Predict, and it is not Health, Safety and Environment.
Before configuration
Health is a suite application at the Base tier. Limited does not add Health. The user-access topic lists Health with the Base entitlement, together with Collaborate.
Before the first successful journey
A small group of comparable assets and at least one contributor with a value on each asset, such as age or a maintenance fact already stored on the asset.
Before production use
The score method, the scale and the missing-value behaviour are agreed. A score without a named contributor is not a reason to replace an asset.
Licensing, entitlement and AppPoints
The MAS 9.2 licensing guidance prices Maximo Health at the Base tier for authorized and concurrent users. The application table shows Health under Base and Premium, not under Limited. The user-access topic for 9.1 and later says Base adds Maximo Health and Maximo Collaborate. Premium includes Health because Premium includes Base. There is no Health install quantity on the install table. Predict is a separate Premium application. HSE is a separate Manage add-on. Do not price Health as Predict, and do not price it as HSE.
Keep four facts separate for Maximo Health. 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
Health is a suite application with its own deployment and its own version. Confirm it is deployed and that Score settings open. Installed means the application opens. Configured means a score type and a method exist for a group. Usable means an asset in that group shows a score you can trace to a contributor.
Foundation configuration
Health reads assets that already exist in Manage: the site, the asset, and the facts the score uses. Age comes from the asset. Maintenance history comes from work. A meter or an external reading is a contributor only when you connect it. You do not need a failure model, a map or an incident matrix for the first score.
Product configuration
In Score settings, choose the group, the score type and the calculation method. Name each contributor and the scale. Grant health administrators the configuration application and grant reviewers read access to the scores. Review the default method and the treatment of a blank contributor before anyone ranks a fleet with it.
Infrastructure and integration
Health runs as a suite application against Manage data. A historian, SCADA or weather feed is an optional contributor and needs its own connection, identity and licence. The first score can use data already on the asset.
Data and operational readiness
The first journey needs three assets in one group with the same contributor populated, and one asset with that contributor empty, so you can see how the method treats a gap. A missing asset is data. A missing score application is deployment or security. A score you cannot explain from the contributors is a configuration problem.
Setup order for a health score
- 1. Base or Premium entitlement Limited does not include Health.
- 2. Health deployed Its own application and version, not the HSE add-on.
- 3. Assets and the contributor values The score reads facts you already store.
- 4. Score type, method and group Then open one asset and trace the score.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Base or Premium entitlement for Health | The 9.2 guidance prices Health at Base. Limited does not include it. Premium includes Base. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | A reliability engineer as an authorized or concurrent Base user. | Grant Health and read the tier. Confirm a Limited user is not expected to open it. | A Limited user is given Health and the dashboard moves them, or they cannot sign in to the application. | Use a Base or Premium user for Health. Keep Limited users on the applications their tier includes. | Licensing in Maximo Application Suite 9.2 |
| Health deployed, distinct from HSE and Predict | The score application is not the incident add-on and not the predictive model. | Mandatory | Suite catalog and the Health application. | Health opens. HSE incident and Predict stay different tiles. | Record the Health component version and open Score settings. | The team configures HSE and calls it Health. | Open the Health application by name before changing a score. | Licensing in Maximo Application Suite 9.2 |
| A group of comparable assets | The score ranks assets that share a method. Mixed types hide the meaning. | Mandatory | Assets in Manage, and the group or query Health uses. | Three pumps in one site, same classification. | The group query returns those three and no transformers. | One score method is applied to assets that are not comparable. | Narrow the group before you publish a ranking. | Modules and applications in Maximo Application Suite 9.2 |
| At least one contributor with values | A method with no inputs has nothing to calculate. | Mandatory | The asset fields, meters or work history the method lists. | Age filled on all three pumps. | Open each asset and read the contributor, then open the score and see the same input named. | The score is a number you cannot trace. | Fill the contributor or remove it from the method. | Modules and applications in Maximo Application Suite 9.2 |
| A declared method and scale | People need to know whether 80 is better or worse, and what a blank does. | Mandatory | Score settings. | One score type, a method that uses age, and a written scale. | Calculate the group and read one asset’s contributors beside the score. | Two engineers disagree on what the number means. | Write the method and the scale into the score settings you will reuse. | Modules and applications in Maximo Application Suite 9.2 |
| A blank contributor on one asset | You need to see the gap behaviour before you rank a fleet. | Mandatory | One asset in the group with the contributor empty. | Pump 3 has no age. Pumps 1 and 2 do. | Compare the three scores and the way the blank is shown. | The blank becomes a silent zero and the asset looks newest or oldest by accident. | Set the method’s treatment of missing data, or keep the asset out of the group until the value exists. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- The user is Base or Premium and AppPoints Usage agrees.
- Health is deployed and Score settings open.
- Manage has the assets you will group.
- You have named the first contributor.
B. Ready for the first end-to-end journey
- Three comparable assets are in the group and the contributor is filled on two of them.
- The score calculates.
- You can point from one score back to the contributor.
- The blank asset is visible as a gap, not as a confident rank.
C. Ready for production operation
- Each production score has an owner, a scale and a review of missing data.
- External feeds, if added, have identities and licences of their own.
- Health scores are not used as Predict output or as HSE risk scores.
- A reviewer who did not configure the method can explain one asset’s score.
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.
- Health deployed and accessible.
- A training asset group with known input values and permission to configure scores.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Health uses scoring to help assess assets and locations. Score settings control how health, criticality and risk are calculated; these are related but distinct measures.
A scoring group establishes which records share a scoring approach. Data quality and calculation freshness are part of interpreting the result.
Topics in this series
- Health, criticality and risk
- Scoring groups
- Inputs and formulas
- Interpreting results
- Scoring dependencies and action
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Choose a small, comparable group of training assets and list available condition inputs.
- In Score settings, inspect the score types and the group's calculation method.
- Create or copy a training scoring group using the installed-version instructions; document the formula and input ranges.
- Calculate or refresh the score through the supported action and record input timestamps.
- Change a single training input and recompute. Compare the result with the formula by hand, including missing-input behavior.
03 · Practical example
Fictional teaching example
For teaching only, define a health score as 70% normalized condition plus 30% normalized inspection quality, both higher-is-better. Inputs 60 and 80 give 66. This is an illustrative formula, not an IBM default or a universal engineering model.
04 · Practice and verify
Build a three-asset score sheet with inputs, formula, expected score, observed score and refresh time. Include one asset with a missing input.
Expected result
The result agrees with the configured formula. A missing input is handled explicitly and does not silently become evidence of good condition.
Common mistakes
- Mixing a high-is-good condition scale with a high-is-bad risk scale.
- Comparing different asset classes using an unexplained common formula.
05 · Advanced concepts
Consider weighted measures, group hierarchies where supported, and how score changes become investigation or maintenance decisions. Validate dependencies before scheduling recalculation.
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