Maximo KPIs and Metrics: A Practical Glossary for EAM Managers

In the world of Enterprise Asset Management (EAM), data is often described as the new oil, but for many maintenance managers, it feels more like an overwhelming flood. IBM Maximo generates millions of data points across work orders, asset histories, and labor transactions, yet without a structured framework for measurement, this data remains dormant. Key Performance Indicators (KPIs) serve as the vital bridge between raw system entries and strategic decision-making, allowing organizations to transition from reactive firefighting to proactive, value-driven maintenance. By mastering the specific metrics that drive reliability and cost-efficiency, Maximo users can transform their Start Centers from simple to-do lists into powerful command centers for operational excellence.

Why KPIs Matter More Than Raw Maintenance Data

The sheer volume of records in a mature Maximo environment can be deceptive. A site might have 50,000 completed work orders, but if those records lack accurate failure codes or actual labor hours, they offer no insight into why assets are failing or where budgets are being leaked. KPIs are the filters that distill this noise into actionable signals. They allow managers to identify the vital few problems among the trivial many, ensuring that limited resources — technicians, spare parts, and capital — are directed toward the assets that impact the bottom line most significantly.

Following enterprise CMMS best practices requires a shift in mindset: moving away from measuring “how much work we did” toward “how much value we preserved.” Raw data tells you that a pump was repaired; a KPI tells you that the pump is failing 20% more frequently than its peers in the same asset class. This distinction is critical for justifying budget increases, optimizing spare parts inventory, and refining PM schedules. Without KPIs, maintenance is a cost center; with them, it becomes a contributor to corporate profitability.

Key Takeaway: KPIs should never be viewed as a report card for punishing teams, but rather as a diagnostic tool for identifying systemic bottlenecks. Effective EAM management relies on using these metrics to advocate for the resources and process changes necessary to improve long-term asset health.

MTBF: Mean Time Between Failures

Mean Time Between Failures (MTBF) is the foundational metric for asset reliability. It measures the average time an asset functions between one breakdown and the next. In Maximo, this is a critical indicator of the effectiveness of your preventive maintenance (PM) program.

• Formula: (Total Operating Time − Total Downtime) / Number of Failures
• Maximo data source: This metric draws from the ASSET and WORKORDER tables. Specifically, it looks at the start and end dates of “Emergency” or “Breakdown” type work orders (Work Type = EM or CM) and compares them against the asset’s total operational hours recorded in meter readings.
• Healthy benchmark: This varies wildly by asset class. For a critical centrifugal pump, a healthy MTBF might be 18 to 24 months. For high-speed packaging equipment, it might be measured in hundreds of hours. A rising MTBF trend indicates improving reliability, while a falling trend suggests that your PMs are either ineffective or being skipped.

To get an accurate MTBF in Maximo, your technicians must consistently use the Failure Reporting tab in the Work Order Tracking application. Without a recorded Failure Class and Problem Code, Maximo cannot distinguish between a scheduled inspection and a genuine functional failure, leading to skewed reliability data.

MTTR: Mean Time to Repair

While MTBF measures reliability, Mean Time to Repair (MTTR) measures maintainability and efficiency. It tracks the average time required to troubleshoot, repair, and return an asset to service after a failure has occurred.

• Formula: Total Maintenance Time Spent on Repairs / Number of Repairs
• Maximo data source: MTTR is primarily derived from labor transactions and the WORKORDER table. It calculates the delta between the actual start and actual finish of corrective work orders.
• Healthy benchmark: For most industrial equipment, an MTTR of 2 to 5 hours is standard for common failures. If MTTR is consistently high, it often points to issues outside the technician’s control, such as poor spare parts availability, lack of technical documentation, or inadequate training.

Reducing MTTR in Maximo often involves streamlining the “waiting on material” status. By ensuring that the asset hierarchy and classification guide is properly implemented, planners can associate the correct spare parts (job plans and bills of material) to assets, ensuring that when a failure occurs, the technician has everything they need immediately, thus driving down the repair clock.

OEE: Overall Equipment Effectiveness

Overall Equipment Effectiveness (OEE) is the gold standard for production-centric EAM environments. It combines three factors: Availability, Performance, and Quality. While Maximo is the system of record for Availability, it often integrates with SCADA or IoT systems (via Maximo Monitor or the MAS Predict suite) to capture Performance and Quality.

• Formula: Availability × Performance × Quality
• Maximo data source: Availability comes from planned production time minus downtime, divided by planned production time (asset downtime records). Performance comes from ideal cycle time multiplied by total count, divided by run time (meter readings or IoT integration). Quality comes from good count divided by total count (production logs or quality management modules).
• Healthy benchmark: “World class” OEE is generally considered to be 85% or higher. Many manufacturing facilities operate in the 60% to 75% range.

In the context of Maximo, OEE allows managers to see the “hidden factory.” If an asset has high availability but low OEE, the maintenance team might be keeping the machine running, but it isn’t running well. This triggers a need for a more detailed Maximo reporting: BIRT, Cognos and MAS analytics guide review to see if the asset requires a major overhaul rather than just routine PMs.

PM Compliance Rate

PM Compliance is a measure of organizational discipline. It tracks the percentage of scheduled preventive maintenance work orders that were completed within a specific window — usually the “ten percent rule,” where a monthly PM must be done within 3 days of its due date.

• Formula: (Number of PM Work Orders Completed on Time / Total Number of PM Work Orders Due) × 100
• Maximo data source: This pulls from the PM and WORKORDER tables, comparing the status date (when it moved to COMP or CLOSE) against the target finish date.
• Healthy benchmark: 90% or higher. Anything below 80% suggests that the maintenance team is in a reactive spiral, where they are too busy fixing breakdowns to perform the work that prevents them.

Low PM compliance is a leading indicator of future failures. In Maximo, you can use the KPI Manager to create a traffic-light indicator on the Start Center. If the light turns red (below 85%), it is a signal to management that the backlog is becoming unmanageable or that the PM schedule is over-optimized and needs to be pruned.

Backlog and Work Order Aging Metrics

Backlog represents the total volume of maintenance work that has been identified but not yet completed. It is usually expressed in “weeks of work” for the available labor force.

• Formula: Total Estimated Labor Hours in Open Work Orders / (Total Available Labor Hours per Week × Number of Technicians)
• Maximo data source: WORKORDER (filtered by status such as approved, scheduled, or waiting on material) and labor availability tables.
• Healthy benchmark: 2 to 4 weeks for a stable maintenance organization. A backlog of less than 2 weeks suggests you are overstaffed; more than 6 weeks suggests you are understaffed or facing a significant deferred maintenance mountain.

Work Order Aging is a subset of this, tracking how long individual records remain in specific statuses. For example, if a work order stays in “waiting for approval” status for more than 48 hours, it indicates an administrative bottleneck. Understanding these nuances is a core part of mastering the Maximo glossary of 50 essential EAM and CMMS terms.

Cost per Asset and Maintenance Cost Ratio

This metric provides the financial perspective of EAM. It tracks the total cost of ownership for an asset, including labor, materials, services, and tools.

• Formula (Maintenance Cost Ratio): Total Maintenance Cost / Estimated Replacement Value of the Asset
• Maximo data source: Asset cost records, which aggregate costs from all related work orders (labor transactions, material receipt transactions, service receipt transactions).
• Healthy benchmark: A Maintenance Cost Ratio of 2% to 3% is typically considered healthy. If the annual maintenance cost of an asset exceeds 5–7% of its replacement value, it is likely time to stop repairing and start a capital replacement project.

Tracking cost per asset in Maximo is only possible if your asset hierarchy and classification is correctly configured, and that spend is best interpreted alongside CMMS best practices for enterprise deployments to avoid over-investing in low-criticality equipment. Costs must roll up from sub-assemblies to the parent asset. If a technician charges parts to a child component, Maximo’s built-in cost roll-up logic ensures the parent asset reflects the true total cost, allowing for accurate repair-versus-replace analysis.

Building a KPI Dashboard in Maximo

Creating a dashboard in Maximo isn’t just about technical configuration; it’s about aligning the user interface with the user’s role. A technician needs to see “my work for today,” while a maintenance manager needs to see “MTBF trends by department.”

Steps to build a KPI dashboard in Maximo:

1. Define the business question. Before touching the KPI Manager, decide what you are trying to solve — for example, “why is our overtime so high?”
2. Verify data integrity. Ensure the underlying fields (failure codes, work types, actual hours) are being populated correctly by the field team.
3. Use the KPI Manager application to write the query logic — for example, filtering on work type equal to emergency, status completed, and finish date within the last 30 days.
4. Set thresholds. Define the “caution” (yellow) and “alert” (red) levels based on your industry benchmarks.
5. Configure the Start Center. Use the layout and configuration tool on the Start Center to add the KPI graph or KPI list portlet.
6. Schedule background jobs. Ensure the relevant cron task is active in the Cron Task Setup application, so the data refreshes automatically every night or every hour.

To truly excel at dashboarding, one must understand data analysis fundamentals for operational metrics to ensure that the correlations shown on the screen represent actual causation in the plant.

Common Reporting Pitfalls to Avoid

Even with a powerful tool like Maximo, KPI reporting can fail if the human element is ignored. One of the most common pitfalls is “metric gaming.” If technicians are measured solely on PM compliance, they may mark work orders as complete without actually performing the work, just to keep the numbers green — a symptom that usually traces back to workflow approval gaps documented in the Maximo Workflow Configuration guide.

• Measuring too many things. “Dashboard fatigue” occurs when a manager has 40 KPIs. Focus on the handful that actually drive behavior.
• Ignoring data latency. If technicians only enter their time once a week on Friday, your “daily productivity” KPI will be useless until Monday morning.
• Lack of context. A 95% PM compliance rate is bad if the missing 5% of PMs were on your most critical, high-risk assets.
• Static benchmarks. Benchmarks should evolve. As your team gets better, your “healthy range” should tighten.
• Poor query logic. Writing a KPI that includes canceled work orders in the total count will artificially deflate your performance percentages.

Key Takeaway: The goal of a Maximo KPI is to trigger an investigation, not to provide a final verdict. If a metric looks off, use the drill-down capabilities of BIRT or Cognos to look at the individual work orders and understand the “why” behind the “what.”

Turning Metrics into Maintenance Strategy

The final stage of EAM maturity is using KPIs to drive a continuous improvement loop. This involves taking the insights from your Maximo Start Center and feeding them back into your job plans and PM schedules. If your MTBF for a specific motor is consistently lower than expected, the data is telling you that your current PM task — perhaps just a visual inspection — is insufficient. You may need to add ultrasound or vibration analysis to that job plan.

Data quality prerequisites before trusting your KPIs:

1. Mandatory failure codes. Technicians must be unable to close a corrective or emergency work order without selecting a problem, cause, and remedy code.
2. Accurate asset criticality. Every asset must have a priority or criticality ranking (1–5) to allow for weighted KPIs.
3. Real-time labor reporting. Actual hours should be entered within 24 hours of work completion.
4. Standardized work types. Clearly defined differences between corrective, emergency, and preventive maintenance.
5. Clean asset registry. No duplicate assets and a clear parent-child hierarchy to ensure cost roll-ups work correctly.

By following these guidelines and utilizing the full power of Maximo’s analytical tools — from simple KPI portlets to advanced Maximo reporting: BIRT, Cognos and MAS analytics — EAM managers can move from a state of constant uncertainty to one of data-driven confidence. Metrics are not just numbers; they are the voice of your assets, and listening to them is the only way to ensure the long-term reliability and profitability of your enterprise.