Maintenance data in IBM Maximo is only as valuable as the reports and dashboards that make it visible to decision-makers. A well-configured Maximo reporting environment transforms raw work order and asset data into actionable intelligence: PM compliance trends, emerging asset reliability problems, maintenance cost drivers, and budget forecast inputs. This guide covers the full reporting toolkit available in both Maximo 7.6 and MAS, and explains how to build a maintenance KPI framework that supports continuous improvement.
Reporting Architecture in Maximo 7.6
Maximo 7.6 provides multiple reporting tools to serve different user needs and skill levels. Understanding which tool to use for which purpose prevents the common mistake of trying to build everything in BIRT when a Query Builder report would suffice.
BIRT (Business Intelligence and Reporting Tools) is the primary formatted report engine. BIRT reports are designed using the BIRT Report Designer, an Eclipse-based IDE that report developers install on their workstations. Reports are designed as templates with data sources, query definitions, table layouts, charts, and conditional formatting. The finished report design (a .rptdesign file) is published to Maximo through the Report Administration application.
BIRT is best used for: formal reports distributed to management, reports requiring complex formatting (letterhead, page headers/footers, conditional section display), reports with charts or graphs, and scheduled reports emailed to distribution lists.
Query Builder is an in-application tool accessible to all Maximo users with appropriate permissions. It allows users to select an object, choose fields to display, define filter conditions, and sort results without writing any code. Query Builder results can be exported to Excel, CSV, or PDF. Query Builder reports can be saved and shared with other users.
Query Builder is best used for: ad-hoc operational lists that maintenance supervisors and planners need daily, quick one-off lookups that do not warrant a formal BIRT report, and non-technical users who need data access without developer support.
KPIs (Key Performance Indicators) in Maximo are metric calculations that run on a schedule and display current values on the Maximo Start Center. KPIs are configured through the KPI Manager application and can display a single calculated value (e.g., “PM Compliance this month: 82%”) with a threshold indicator (green/yellow/red) based on configurable target ranges.
Ad Hoc Reporting provides a simplified report builder accessible from within Maximo applications, allowing users to generate quick extracts of the records currently displayed in an application without leaving the application context.
Designing BIRT Reports for Maximo
Building effective BIRT reports for Maximo requires understanding how Maximo’s Application Framework exposes data to the reporting engine. Rather than querying the database directly, BIRT reports in Maximo use the Maximo Reporting API, which respects application-level security restrictions — ensuring users only see data they are authorized to access in the main application.
The report design process follows these steps:
Step 1 — Define the data source: in BIRT Designer, create a Maximo Data Source that connects to your Maximo server. The data source handles authentication and API connectivity.
Step 2 — Create datasets: datasets define which Maximo objects and fields the report will query. You can combine data from related objects (e.g., WORKORDER joined to ASSET and LOCATION) through Maximo’s reporting relationships.
Step 3 — Design the report layout: drag dataset fields into table or chart elements on the report canvas. Add grouping to summarize data (e.g., group work orders by Work Type and show subtotals). Add conditional formatting to highlight out-of-range values.
Step 4 — Add parameters: parameters allow report consumers to filter the report at runtime without modifying the design. Common parameters for maintenance reports include date range, site, work type, and asset classification.
Step 5 — Publish to Maximo: export the .rptdesign file and upload it through Report Administration. Define the report’s category, associated application, and permission level.
A well-designed BIRT library for maintenance operations typically includes 15-25 standard reports covering work order backlog, PM compliance, asset history, inventory status, labor utilization, and cost summaries. These reports form the analytical backbone of a CMMS best practices maintenance intelligence program.
Key Maintenance KPIs and How to Calculate Them in Maximo
KPIs are the heartbeat of a mature maintenance organization. These are the metrics that maintenance managers should be reviewing weekly and presenting to operations leadership monthly.
PM Compliance Rate is the most universally cited maintenance KPI. It measures the percentage of preventive maintenance work orders completed within the acceptable scheduling window (typically +/- 10% of the PM frequency).
Maximo query: count PM work orders with STATUS = ‘COMP’ and TARGCOMPDATE within the period, divided by total PM work orders with TARGCOMPDATE within the period. Target: 80%+ monthly. Industry leaders achieve 90%+.
Emergency Work Ratio measures the percentage of work orders classified as emergency or breakdown against total work orders. A high emergency ratio indicates a reactive maintenance culture. Organizations reducing their emergency work ratio from 40% to 15% typically see a 20-30% reduction in maintenance cost per production unit.
MTTR (Mean Time to Repair) for corrective work orders: average elapsed time between work order creation (failure report) and completion. Calculated per asset class, equipment criticality tier, or plant area. Reductions in MTTR directly improve equipment availability.
MTBF (Mean Time Between Failures) for specific assets or asset classes: average operating time between consecutive corrective failures. An improving MTBF trend on a critical asset class indicates that PM improvements or operating condition changes are having a positive effect.
Schedule Compliance: the percentage of scheduled work orders (those with a specific SCHEDSTART date assigned) that are actually completed on the scheduled date. Low schedule compliance indicates planning or scheduling dysfunction — work is being scheduled but something prevents execution on the planned day.
Cost per Work Order by work type or asset class: total actual labor plus materials cost averaged across the volume of work orders. Trending this metric over time reveals whether maintenance efficiency is improving or whether specific asset classes are driving disproportionate cost.
For asset management reporting specifically, Maximo can generate maintenance cost histories that support lifecycle analysis, comparing cumulative maintenance cost against asset replacement value to identify capital renewal candidates.
MAS Analytics and Cognos Integration
MAS replaces BIRT with Cognos Analytics as the primary reporting platform. Cognos Analytics is IBM’s enterprise business intelligence suite, offering significantly more powerful analytics capabilities than BIRT.
Maximo Analytics content packs provide pre-built Cognos reports and dashboards covering the standard maintenance KPIs out of the box. These packs include:
- Work Management Dashboard: PM compliance, backlog, WO volume trends
- Asset Performance Dashboard: MTTR, MTBF, failure code analysis
- Inventory Dashboard: service level, inventory turnover, dead stock value
- Labor Utilization Dashboard: planned vs. actual hours, craft utilization rates
Self-service analytics in Cognos: unlike BIRT, Cognos allows business users to create their own reports and dashboards without developer support through the Cognos Analytics web interface. Users can drag and drop Maximo fields into visualizations, apply filters, and create calculated measures.
AI-augmented insights in MAS extend beyond traditional reporting. The MAS Health application calculates asset condition scores that aggregate work order history, sensor data, and inspection results into a single health indicator per asset. The Score Summary dashboard shows the fleet-wide distribution of asset health, allowing maintenance managers to identify the assets most likely to fail before the next planned inspection.
Cognos Exploration uses AI to automatically identify patterns and anomalies in maintenance data that a human analyst might miss. For example, it might surface the correlation between a particular weather condition and increased failure rates in certain outdoor equipment — an insight that would require days of manual analysis in a traditional reporting environment.
Scheduling and Distributing Reports
Report scheduling in Maximo 7.6 is configured through the Report Administration application. Key scheduling options include:
- Frequency: one-time, daily, weekly, monthly
- Output format: PDF, Excel, CSV, XML
- Distribution: email to a defined list of recipients, or save to a network share
- Parameters: scheduled reports can use fixed parameter values (e.g., always report on the previous month’s data) or dynamic expressions
For weekly management reports, the most effective distribution approach is a scheduled PDF emailed to the maintenance manager, operations director, and plant manager every Monday morning covering the previous week’s KPIs. This creates a consistent rhythm of data review without requiring managers to log into Maximo.
In MAS with Cognos, report subscriptions allow individual users to receive personalized report outputs on their own schedule. Burst delivery enables a single report to be distributed to multiple recipients with each receiving a version filtered to their specific site, plant, or area — eliminating the need to build separate reports for each organizational unit.
Building a Maintenance Intelligence Program
The most successful Maximo reporting implementations treat reporting not as a technical project but as a business change initiative. The technical work of configuring reports takes weeks; building the organizational habits of using data to make decisions takes years.
The recommended approach for building a maintenance intelligence program on Maximo:
Start with three core KPIs: PM compliance, emergency work ratio, and work order backlog. Configure these as Maximo Start Center KPIs visible to all maintenance supervisors on login. Review these KPIs in every team meeting for 90 days before adding more metrics.
Create a monthly reporting cadence: one standard report package distributed to leadership on the first business day of each month, covering the previous month’s KPIs against targets. Consistency in format and timing is more important than sophistication.
Connect data to decisions: every KPI should have a defined response protocol. If PM compliance drops below 75%, what happens? Who reviews it, what actions are taken, and within what timeframe? Reporting without decision protocols produces awareness without improvement.
Build trust in the data: maintenance teams distrust reports that do not match their operational reality. Invest in data quality — accurate failure codes, complete actual labor entries, timely work order closures — before rolling out KPI dashboards. A dashboard showing inaccurate numbers damages credibility more than no dashboard at all. Industry technology publications like i-actu.fr cover analytics platform updates and emerging tools relevant to enterprise maintenance reporting.
Organizations that follow this disciplined approach to Maximo reporting consistently achieve measurable maintenance performance improvements within 18-24 months: PM compliance increases, emergency work ratios decline, and maintenance cost per unit trends downward as planned work replaces reactive firefighting — the hallmarks of an advanced CMMS best practice organization.