Getting Started with Maximo Health: From Zero to First Health Score

Who this is for: Maximo administrators and project leads who have the green light to implement Health and need a practical roadmap from "we have a license" to "we have scores on our first 50 assets."

Estimated read time: 15 minutes

🔥 The Pilot That Almost Died in Committee

A mining company purchased Maximo Health as part of their MAS deployment. The technical activation took two days. The security configuration took a week. The data validation took two weeks.

The argument about which assets to include in the pilot took three months.

Operations wanted haul trucks. Maintenance wanted crushers. Reliability wanted the processing plant pumps. The VP wanted "all critical assets across all sites." The project manager wanted a Gantt chart.

By the time they agreed on a scope, the executive sponsor had moved to a different division, and the pilot was deprioritized.

"We spent more time choosing assets than configuring the application."

This is not a technology problem. It is an alignment problem. And it kills more Health implementations than bad data ever will.

Here is the rule: Pick 30-50 assets at one site in one asset class. The specific choice matters less than the speed of the decision. You can always expand scope. You cannot recover three months of organizational momentum lost to indecision.

📊 Before You Touch a Configuration Screen

Technical Prerequisites

Let's get the straightforward items out of the way:

TECHNICAL READINESS CHECKLIST

  [ ] Supported MAS environment deployed and operational
  [ ] Maximo Manage running as the asset system of record
  [ ] Health application entitlement confirmed in your MAS license
  [ ] Administrative access to MAS Suite Administration
  [ ] Administrative access to Maximo Manage (domains, security, etc.)
  [ ] Network connectivity for all intended Health users
  [ ] Browser compatibility confirmed (MAS-supported browsers)

These are table stakes. If you are reading this blog, you probably have most of them. The items that actually determine success come next.

Data Readiness -- The Real Gate

Technical readiness is a checkbox exercise. Data readiness is where pilots succeed or fail.

For your pilot scope, assess:

Asset Master Data

  • Are assets correctly linked to locations and parent systems?
  • Are classifications and key attributes populated (asset type, manufacturer, install date)?
  • Is the hierarchy clean enough that portfolio views make sense?

Work History

  • Are failure codes used consistently on corrective work orders?
  • Are downtime and impact fields populated?
  • Is there at least 12 months of work history for pilot assets?

Meters

  • Are key meters defined (runtime, cycles, throughput)?
  • Are readings updated regularly (not just at PM time)?
  • Can you trust the readings (no obviously incorrect values)?

Inspections

  • Are inspection forms defined with structured condition ratings?
  • Are inspections completed on schedule?
  • Do ratings use consistent scales across inspectors?
Key insight: You will find gaps. That is expected. Document them, assess their impact on health scores, and decide which gaps to fix now vs. later. Do not let imperfect data become a reason to delay indefinitely.

Organizational Readiness

  • Defined objectives -- What does success look like in 90 days? "We can show health scores for 50 pumps and use them in weekly planning" is better than "implement Health across the enterprise."
  • Agreed pilot scope -- One site, one asset class, 30-50 assets. Decided, not debated.
  • Identified stakeholders -- Who will consume health dashboards? Who will validate scores? Who will use scores in planning?
  • Named owner -- One person accountable for the pilot. Not a committee.

🛠️ Enabling Health in MAS

The activation process varies between MAS SaaS and on-premises deployments. Rather than prescribing exact click paths (which change between versions), here are the key steps and decisions.

Step 1: Confirm Entitlement

Work with your MAS administrator to verify:

  • Health is included in your MAS license entitlement
  • The Health application is available in the MAS application catalog
  • Required backend services are installed and running

For MAS SaaS, this is typically handled through your IBM subscription. For on-premises, it may involve deploying additional operators or application components.

Step 2: Enable the Application

In the MAS Suite Administration console:

  • Locate Maximo Health in the application catalog
  • Enable it for your target workspace or environment
  • Verify that the Health application appears in the MAS navigator

This is usually a straightforward process, but timing varies. Backend service initialization can take minutes to hours depending on environment size.

Step 3: Verify Basic Access

Before configuring anything:

  • Log in as an administrator and confirm Health opens without errors
  • Verify that the application can connect to Maximo Manage data
  • Check that basic navigation works (portfolio views, asset search)

If Health opens but shows no data, do not panic. You have not configured scope or onboarded assets yet. That comes next.

🔐 Security Configuration: Who Sees What

Maximo Health serves different roles with different needs. Get security right early to avoid the "everyone is an admin" antipattern.

Define Your Role Model

Role — What They Need — Access Level

Executive / Leadership — Portfolio dashboards, trend KPIs, risk summaries — View-only, enterprise scope

Maintenance Manager — Site-level health views, high-risk asset lists — View + drill-down, site scope

Planner / Scheduler — Asset-level detail, work backlog with health context — View + link to work management

Reliability Engineer — Indicator-level detail, model validation, trend analysis — View + advanced analytics

Administrator — Model configuration, threshold management, data mapping — Full configuration access

Configure Security Groups

In Maximo Manage:

  1. Create or update security groups that map to the roles above
  2. Grant application access to Health for each group
  3. Apply site and organization restrictions so users see relevant data
  4. Align with existing asset security -- Health should respect the same data boundaries as Manage
"We gave everyone admin access during the pilot. It was faster."

>

It is faster right up until someone changes a weighting and nobody knows who did it or why. Set up proper roles from day one. The extra hour of configuration saves weeks of confusion later.

Key Settings to Review

Depending on your version, check:

  • Default time horizons for health and risk calculations (12 months is a common starting point)
  • Organization and site scope for initial views
  • Default filters and sort orders in portfolio dashboards

Keep settings simple for the pilot. You will tune them as you gain experience.

📦 Onboarding Assets: Your First 50

This is where the rubber meets the road. You are going to bring assets into scope and see health scores for the first time.

Choose Your Pilot Scope

The best pilot scopes share three characteristics:

  1. Reasonable data quality -- not perfect, but consistent enough to produce meaningful scores
  2. Engaged stakeholders -- people who will look at the scores, challenge them, and use them
  3. Visible improvement potential -- an area where better prioritization will produce measurable results

Good examples:

  • Critical pumps on the main production line
  • Transformers in one substation district
  • HVAC units in the flagship facility
  • Fleet vehicles in one operating region

Bad examples:

  • "All assets" (too broad, no focus)
  • Assets with no work history (nothing to score)
  • Low-importance assets where nobody cares about the results

Validate Data for Pilot Assets

Before enabling health views, run a data quality check on your pilot set:

PILOT DATA VALIDATION

  For each of the ~50 pilot assets, verify:

  [ ] Asset record exists with correct classification and location
  [ ] At least 12 months of work order history
  [ ] Failure codes populated on corrective work orders (>70% target)
  [ ] Key meters defined and readings current (<30 days stale)
  [ ] At least one structured inspection within the past 6 months
  [ ] Parent/child and system relationships are correct

  DOCUMENT any gaps and their expected impact on scores.

You will not hit 100% on every item. That is fine. Document the gaps so you can explain to stakeholders why certain scores might be lower confidence than others.

Enable Health Views

With your pilot scope validated:

  1. Ensure pilot assets are visible in Maximo Health dashboards (check filters and scope settings)
  2. Confirm users can navigate from portfolio views to individual asset health details
  3. Verify that health metrics appear -- even if they are basic or preliminary
  4. Note any assets that show no health data and investigate (missing data or configuration)

The First Score Review

Schedule a meeting with 3-5 key stakeholders within the first week of scores being live. Walk through:

  • The top 5 highest-risk assets -- do the scores match intuition?
  • The top 5 healthiest assets -- any surprises?
  • Any scores that feel obviously wrong -- investigate why
  • Any assets with missing or incomplete scores -- identify data gaps

This validation session is critical. It builds trust (or identifies problems) before you expand scope.

✅ The Verification Checklist

Do not declare "we are live" until every item passes.

Access and Navigation

  • [ ] Maximo Health appears in MAS navigation for all target users
  • [ ] Users can open Health without errors
  • [ ] Users see relevant organizations, sites, and assets based on security settings
  • [ ] Navigation between portfolio, asset list, and asset detail works cleanly

Data and Views

  • [ ] At least one portfolio view shows health and risk metrics for pilot assets
  • [ ] Users can filter and sort by health score, criticality, or risk
  • [ ] Drilling into an asset shows health details, contributing indicators, and related work history
  • [ ] Health scores are updated when new work orders or inspections are completed

Data Integrity

  • [ ] Health scores reflect recent work orders, meter readings, and inspections
  • [ ] Known data gaps are documented and communicated to stakeholders
  • [ ] Stakeholders understand that scores may be refined as models and data improve
  • [ ] No assets show obviously incorrect scores (0 when they should have data, 100 when they are known bad actors)

Governance and Ownership

  • [ ] A named owner is responsible for the Health pilot
  • [ ] Stakeholders know how to report issues or question scores
  • [ ] Initial success criteria are defined (e.g., "use health views in weekly planning for 4 weeks")
  • [ ] A plan exists to address top-priority data quality gaps
  • [ ] Review cadence is established (weekly during pilot, monthly after stabilization)

🚫 The Five Ways Pilots Fail

We have seen enough Health pilots to know the patterns. Avoid these:

1. The Scope Creep Death Spiral

Starts with 50 assets. Someone adds "just a few more." Within a month it is 500 assets, half with terrible data. Scores are inconsistent. Stakeholders lose confidence. Pilot stalls.

Prevention: Lock the pilot scope. Expansion happens after validation, not during.

2. The Data Denial

"Our data is fine." It is not. Nobody's is. But instead of acknowledging gaps, the team ignores them until a stakeholder points to an obviously wrong score in a meeting. Trust evaporates.

Prevention: Lead with data quality findings. Show what you know is good and what needs work.

3. The Configuration Perfectionist

Spends weeks tuning weightings and thresholds before anyone sees a single score. By the time the model is "ready," stakeholders have lost interest.

Prevention: Ship a reasonable starting configuration. Tune based on feedback from real users seeing real scores.

4. The Dashboard Tourist

Creates beautiful dashboards. Nobody uses them in actual planning or scheduling. Health becomes a demo, not a tool.

Prevention: Define specific decisions that will use health scores before you build the dashboards.

5. The Orphaned Pilot

No named owner. No review cadence. No success criteria. The pilot runs for 6 months in a state of ambient neglect until someone asks "did we ever do anything with Health?"

Prevention: One owner. Weekly reviews. Written success criteria. Non-negotiable.

🎯 The 7 Commandments of Getting Started

  1. Thou shalt pick a scope in one meeting. If the second meeting is still debating scope, the pilot is already at risk.
  2. Thou shalt not wait for perfect data. Start with honest data. Improve it in parallel.
  3. Thou shalt configure security properly from day one. "Everyone is admin" is not a strategy.
  4. Thou shalt validate scores with humans before trusting them. The model is a starting point. Expert judgment is the calibration.
  5. Thou shalt name one owner. Not a committee. Not a working group. One person.
  6. Thou shalt define success before you start. "Use health scores in weekly planning for 4 weeks" is measurable. "Implement Health" is not.
  7. Thou shalt use the checklist. If the checklist is not green, you are not live.

Next in the series: Part 4 -- Configuring Health Scores and Criticality dives into the configuration details -- structuring components, mapping indicators, setting weightings, and modeling criticality.

About TheMaximoGuys: We help Maximo developers and teams build, configure, and optimize IBM Maximo Application Suite. Our content comes from real implementations, not marketing slides. If it is in our blog, we have done it in production.