Maximo & MAS dashboards
Turn work orders, assets and maintenance history into clear dashboards your maintenance, reliability and operations teams can act on—built in the reporting tool you already own.
Maximo or MAS
Classic Maximo runs on its own application server with DB2, Oracle or SQL Server behind it, and most estates carry years of customised screens, domains and report packs. We read the same records your team already knows—work orders, PM plans, assets, locations, failure codes—and build dashboards on top of them without disturbing your Maximo configuration.
MAS is a suite of applications running on Red Hat OpenShift and Cloud Pak for Data, under a single entitlement. Each application holds its own data and its own views: Manage for work orders and assets, Monitor for condition and anomalies, Health for a 360° asset view, Predict for failures, Assist for guided repair, plus Maximo Mobile. Its reporting layer is IBM Cognos Analytics, provided with the suite.
Because MAS dashboards live inside each application, a maintenance manager often reads backlog in one place, PM compliance in another and downtime in a third. The questions your team asks cut across all of them. We join those applications into one view, in the reporting tool your people already open.
Inside the suite
Each MAS application gives you a genuine view of its own world. What we add is the line between them.
Work orders, work assignments, assets and PM schedules, with its own list views and reports.
Backlog age, PM compliance, planned versus reactive split and overdue work by crew, craft or site—on one page a supervisor can read in a minute.
Condition data, KPIs, alerts and anomaly detection for connected equipment.
Alert history and trends lined up against work orders and downtime, so an anomaly turns into an action with an owner and a date.
A 360° view of asset health and criticality.
Reliability reporting leadership can follow: MTBF, MTTR, repeat failures and cost per asset, compared across sites and asset classes.
Predictive failure models and remaining-use estimates.
Model results in plain language—which assets to act on this week, and what the intervention is worth in avoided downtime.
Guided repair help and prescriptive assistance for technicians in the field.
First-time-fix, rework and time-on-tool views that show whether the guidance is genuinely saving your technicians time.
Technician work execution away from a desk: work orders, measurements and parts.
Completion, backlog and data-quality views that show what happened on the shift, not only what was typed in afterwards.
What we build
Open, overdue and completed work orders, backlog age, priority and labour hours by site, crew or craft.
PM compliance, schedule adherence and planned vs. reactive work, so you can see whether maintenance is under control.
MTBF, MTTR, failure codes and repeat failures to show where equipment is letting you down.
Outage and unplanned downtime, condition data and failure codes, read by location, asset class or voltage level.
Critical spares, stock levels, reorder points and parts usage tied to work orders.
Maintenance spend, labour vs. materials and cost per asset to support budgets and planning.
Maximo vocabulary
No translation needed. These are the Maximo records and measures a dashboard is built from, using your system's own names, statuses and splits rather than a generic template.
A WO number, work type, priority, target start and target finish, moving through WAPPR, APPR, INPRG and WOCOMP to COMP and CLOSED. We count actionable work orders, open backlog and work past its target start—the way your planners already count it.
Assets sit in a location hierarchy and carry a classification—switchgear, protection, SCADA, auxiliary or reactive power—with voltage, system and area attached. That is what lets one figure be read for a single plant or the whole estate.
Preventive maintenance schedules, calendar-based or driven by asset meter readings, the job plans behind them, and the PM compliance and PM-versus-reactive share they should produce.
Problem, cause and remedy codes recorded against a failure, plus outage and downtime records—so "the breaker failed" becomes a pattern you can act on.
Spare parts as items with balances, bins and reorder points, issued to a work order; labour, craft and crew hours booked against the asset.
Work order cost lines rolled up as actual against estimate by department, area or asset class, with over and under shown plainly rather than buried in a total.
Counts checked against a target, with variance and a status—matched, needs review, definition gap—so leadership is not asked to trust a number nobody has checked.
Report date, year and month slicers that keep a weekly comparison honest week to week, instead of comparing a full week against a part one.
Data separated by site and organization, with department and area access, so a page shows the right people the right slice.
Share a sample work order screen or one of your existing report packs and we build to your wording—your field names, your statuses, your department and area splits.
A worked example
This one is built from invented figures, so nothing of a client's is shown. The layout, the splits and the checks are the part that carries into your own data.
Counted the way planners count them—actionable work orders only.
Share of completed work orders, month to date.
Work orders closed each week, compared on full weeks only.
Open work orders by age, so old work is not hidden by a total.
Sample units by department, with the gap shown rather than buried.
Each figure checked against a target before anyone is asked to trust it.
| KPI | Target | Model | Var | Status |
|---|---|---|---|---|
| Actionable work orders | 1,284 | 1,284 | 0.0% | Matched |
| Completed this month | 936 | 918 | -1.9% | Review |
| PM compliance | 91% | 91% | 0.0% | Matched |
| Overdue past target start | 62 | 71 | +14.5% | Gap |
Assets and open work orders by classification and voltage.
| Classification | Assets | Open WOs | Voltage |
|---|---|---|---|
| Switchgear | 412 | 386 | 132kV / 33kV |
| Protection | 268 | 194 | 132kV / 33kV |
| SCADA & comms | 154 | 96 | 11kV / 415V |
| Auxiliary systems | 322 | 231 | 415V / 24V |
| Reactive power | 88 | 57 | 132kV / 33kV |
Outage records read alongside the work orders that followed them.
Demonstrated live with safe sample data. Client systems, records and costs stay private and are never published.
Every figure above is fictional sample data created for this page. It is not a client dashboard, a client's records or a claim about results delivered.
Why work with us
No rip-and-replace. We build on Maximo, MAS, Cognos Analytics, Oracle Analytics or the Power BI or Tableau capacity you already pay for.
Work orders, PM, failure codes, storeroom transactions and asset hierarchies are the vocabulary we already think in, so the KPIs mean what your team believes they mean.
A shift supervisor, a reliability engineer and a plant manager need different pages—not one crowded screen that serves nobody.
Cognos Analytics is already in your estate, and it comes with MAS. Our work is to make it worth opening: clearer layout, honest numbers and a page that answers the question in the first few seconds.
Our past Maximo and MAS work contains real client data, so it is never published. Demonstrations are arranged with safe sample data.
Definitions, documentation and a walk-through, so your team can change the dashboard later without calling us back.
IBM Cognos Analytics
You have already invested in Cognos Analytics, and MAS brings it into your estate. Our service is to build dashboards in it that are genuinely worth looking at—stunning to read, honest in the numbers and used every week.
Design work, not just data: visual hierarchy, readable scales, consistent colour and a layout a plant manager can follow without training.
Scheduled delivery, parameters and access set up so the right people get the right view, with no spreadsheet in the middle.
We review what you already have, remove duplicates, settle conflicting definitions and bring the good reports up to standard.
Slow or heavy reports, awkward extracts and permissions nobody understands—we sort these out before adding anything new.
MAS includes Cognos Analytics for reporting across the suite. We make that entitlement earn its place, instead of leaving it to a handful of report authors.
If Power BI or Tableau genuinely suits one specific view or team better, we say so plainly. Cognos stays where it belongs.
How it works
We agree the maintenance questions, the KPIs your team is accountable for and who needs to see them.
We connect to your Maximo or MAS data and confirm the work order, PM and asset records are complete and consistent.
We agree how MTBF, MTTR, PM compliance and backlog age are calculated, so every page shows the same numbers.
We design the dashboards in Cognos Analytics, Oracle Analytics, Power BI or Tableau, and refine them with your team.
We check the results against the records in Maximo or MAS before anyone is asked to rely on them.
We document the definitions and walk your team through the result, so you stay in control of it.
Questions
IBM Maximo 7.x (ASAM) and the Maximo Application Suite (MAS). Tell us your version, your database and who needs the views, and we confirm the approach before anything is agreed.
The MAS applications each show their own slice, and each is strong inside its own walls. We join Manage, Monitor, Health and Predict into one answer for one decision, and put it in the tool your people already use.
No. Cognos stays. We design better dashboards and reports inside it, tidy what already exists, and only suggest another tool when one genuinely fits a specific need better.
Usually no—we build on Cognos Analytics with MAS, or on the Power BI or Tableau capacity you already have. If something extra is genuinely needed, we explain why before you commit to it.
Our past Maximo and MAS work contains real client data, so it is never published. Live demonstrations with safe sample data are arranged on request.
Yes. Client data stays private, is never shown publicly and is never reused in our portfolio.
See it in action