Maintenance and Reliability Metrics Dashboard | FireFlight

Last updated: April 2026

Maintenance and Reliability Metrics Dashboard

Overdue work orders and PM inspection outcomes two metrics that together show whether the maintenance program is addressing known problems in time and whether preventive inspections are finding conditions that need correction.

FireFlight's Maintenance and Reliability Metrics Dashboard shows two live metrics: Overdue Work Orders counting maintenance and repair tasks that have passed their due date without completion, and PM Inspection Failed and Completed showing how many preventive maintenance inspections resulted in a pass versus a fail finding. Both update in real time from work order and inspection records. Most operations are running live reliability metrics in weeks, not months.

FireFlight Maintenance and Reliability Metrics Dashboard showing overdue work orders and PM inspection pass and fail outcomes

Reliability is not a property of equipment it is a property of the maintenance program managing that equipment. An asset fleet that is well-maintained produces predictable performance. One that accumulates overdue corrective work and where PM inspections pass without finding problems that actually exist is heading toward a different outcome. These two metrics are the simplest measurable expression of whether a maintenance program is doing what it is supposed to do: addressing known problems before they compound and catching developing problems before they become failures.

Schedule your free consultation

Why is an overdue work order a reliability metric rather than just a scheduling metric?

A work order becomes overdue when a known problem a corrective repair, a maintenance task, an inspection finding passes its resolution deadline without being addressed. The equipment involved is operating with a known condition that has not been fixed. For corrective repairs, that condition is already a failure that is generating wear, risk of secondary failures, and potential safety exposure with every hour it remains unresolved. For maintenance tasks with defined regulatory or warranty windows, an overdue work order may also be a compliance gap that has real consequences beyond the operational risk.

The count of overdue work orders at any moment is therefore a count of known reliability risks that are accumulating unresolved. A count of zero means every known problem has been addressed within its required window. A count that is growing means problems are entering the queue faster than they are being resolved, or that specific categories of work are consistently deprioritized until they age past their due dates. Both patterns have different management responses, but both require the same first step: knowing the count and knowing whether it is stable, growing, or shrinking.

Maintenance condition assessment view in FireFlight showing PM inspection findings and reliability indicators for asset fleet management

PM inspection outcomes tell a different but equally important story about asset reliability. A preventive maintenance program that completes all its scheduled inspections and records no failures is one of two things: either the equipment is genuinely in excellent condition, or the inspections are not rigorous enough to find the conditions that will eventually cause failures. The PM Inspection Failed and Completed metric distinguishes between these two interpretations by making the fail count visible alongside the completion count.

A PM program that never records inspection failures is not necessarily performing well. Zero failures may mean zero problems, or it may mean the inspection criteria are too lenient, the technicians are recording completions without performing full assessments, or the PM intervals are too short for conditions to develop to the point where they would be caught. When inspection failure rate is tracked and visible, a sustained period of zero failures against a fleet with normal age and operating hours warrants investigation rather than reassurance. The metric is what makes that investigation possible rather than invisible.

How do these two metrics together define the reliability health of a maintenance program?

The combination of Overdue Work Orders and PM Inspection Failed and Completed covers reliability from both the reactive and the preventive dimension simultaneously. Overdue Work Orders measures how well the operation is resolving known problems. PM Inspection Failed and Completed measures how effectively the preventive program is finding developing problems before they become failures. A maintenance program that performs well on both metrics low and stable overdue counts, PM inspections that find and record failures at a rate consistent with the age and operating conditions of the fleet is doing what a reliability-focused maintenance program should do.

The scenario that damages reliability most is the combination of a rising overdue work order count and a falling inspection failure rate. Rising overdue counts mean known problems are not being addressed. Falling inspection failure rates in that context are more likely to reflect inspection quality decline than improving equipment health. Both conditions are visible in this dashboard simultaneously, which is what makes the two-metric view a genuine reliability indicator rather than two unrelated counts displayed on the same screen.

Both metrics read from live operational records in FireFlight. An overdue work order count is calculated continuously against due date logic applied in real time a work order that becomes overdue at 11pm appears in the count at 11pm without anyone having to flag it. An inspection outcome is recorded at the point of inspection by the technician performing the PM. The dashboard reflects the current reliability state of the maintenance program from actual records, not from a weekly report that summarizes what happened before the week it was prepared.

PCG has been building maintenance and reliability tracking systems since 1995 industrial facilities, fleet operations, environmental service equipment, and healthcare technology assets where equipment reliability has direct operational, safety, and compliance consequences. The two-metric structure of this dashboard reflects the two questions that maintenance programs are actually designed to answer: are known problems being addressed in time, and is the preventive program finding problems before they become failures.

How does this dashboard connect to Project Work Orders in FireFlight?

Project Work Orders in FireFlight connect individual maintenance and inspection tasks to overarching project structures providing sequence, accountability, and traceability across multi-step maintenance engagements. When a PM inspection records a failure finding, the corrective action it triggers is a work order that can be linked to the originating PM record and, where appropriate, to the project structure that governs the maintenance engagement.

The Overdue Work Orders metric on this dashboard counts all work orders past their due date standalone, PM-generated, and project-linked giving the reliability view a picture of the full open maintenance obligation regardless of how the work was created. For operations managing complex multi-step maintenance projects where individual work orders within a project sequence may have their own due dates and dependencies, the overdue count surfaces schedule slippage at the work order level before it has propagated through the project timeline to affect downstream work.

Meet Ikhana

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page explained with clarity, right where you need it.

On the Maintenance and Reliability Metrics Dashboard, Ikhana explains the distinction between overdue work orders as a scheduling metric versus a reliability metric, why a zero PM inspection failure count warrants investigation rather than celebration in certain fleet conditions, and how to interpret the two metrics together rather than in isolation. Maintenance managers and reliability engineers both use the dashboard correctly from day one.

Learn more about Ikhana

What the two metrics give your operation

Overdue Work Orders. The live count of work orders that have passed their due date without reaching a completed status. Calculated continuously from due date logic applied to live work order records. A count of zero reflects a maintenance program that is resolving known problems within required windows. A growing count reflects either a capacity gap or a systematic deprioritization of specific work categories. The underlying work order records show which assets, which locations, and which work types are driving the overdue count making the management response specific rather than generic.
PM Inspection Failed and Completed. The outcomes of preventive maintenance inspections, shown as a breakdown between completed with a pass result and completed with a fail finding. The fail count is the leading indicator that the PM program is doing its job: finding conditions that require corrective action before those conditions produce failures. A sustained period of zero or near-zero inspection failures against a fleet with normal age and operating history is a signal to review inspection criteria and recording practices rather than to confirm that the fleet is uniformly in excellent health.

What PCG learned across 31 years of maintenance and reliability system builds: the operations with the highest equipment reliability were not the ones with the most maintenance staff or the largest PM budgets. They were the ones where overdue work was visible and acted on before it accumulated, and where PM inspection outcomes were honest enough to generate corrective work orders at a rate consistent with the age and operating conditions of the fleet.

A maintenance program that records no failures is not necessarily running well. Reliability requires finding problems, not just executing a schedule. These two metrics are the simplest possible measurement of whether the maintenance program is accomplishing both: resolving known problems in time, and finding developing problems before they require resolution under emergency conditions.

What operations see after deployment

Known maintenance problems do not age undetected. The overdue work order count is visible and current at all times. Maintenance managers who see the count growing have the information they need to identify which specific work orders are involved and what is driving the accumulation before it reaches the point where the overdue work orders become a safety or compliance exposure rather than a scheduling lag.
PM inspection quality is measurable rather than assumed. When inspection failure outcomes are tracked and visible alongside completions, the quality of the inspection program can be evaluated over time. An inspection failure rate that is appropriate for the fleet's age and operating conditions confirms the program is finding what it should find. A failure rate that seems implausibly low prompts the investigation that either confirms good fleet health or identifies a problem with inspection rigor.
Reliability conversations with leadership are grounded in current data. When the overdue work order count is visible in real time and inspection outcomes are tracked, the discussion of whether the maintenance program is adequate is based on what the records show rather than on the maintenance team's general sense of how things are going. That is a different kind of conversation, and it produces different decisions about maintenance investment and staffing.
Reactive and preventive maintenance performance are visible together. A single dashboard view that shows overdue work order count alongside PM inspection outcomes gives maintenance managers a simultaneous picture of how the program is performing on both dimensions without switching between separate reports. The relationship between the two metrics often tells the most important part of the reliability story.

Questions maintenance and reliability managers ask before deploying FireFlight

What does the Maintenance and Reliability Metrics Dashboard show in FireFlight?

The dashboard shows two live metrics: Overdue Work Orders, counting all work orders that have passed their due date without reaching a completed status, and PM Inspection Failed and Completed, showing the results of preventive maintenance inspections broken out by pass and fail outcomes. Both update in real time from work order and inspection records.

How does tracking Overdue Work Orders specifically support reliability management?

Overdue work orders are not just a scheduling problem they are a reliability risk. A corrective repair that is 14 days overdue is a known failure that has been operating without resolution for 14 days. For equipment with defined maintenance windows under warranty, safety regulations, or service agreements, an overdue work order may also represent a contractual or regulatory gap. The dashboard surfaces the count and, through the underlying work order records, the specific assets and locations involved so the exposure is addressable rather than estimated.

What does PM Inspection Failed and Completed show in FireFlight?

PM Inspection Failed and Completed shows the outcomes of preventive maintenance inspections: how many were completed successfully and how many recorded a failure finding. The fail count is the leading indicator that separates a PM program that is finding problems from one that is simply executing a schedule. Tracking fail outcomes alongside completions shows whether the PM program is catching problems before they become failures.

How does PM Inspection failure rate signal asset health trends?

A rising PM inspection failure rate across a specific asset class or location signals that the equipment is increasingly not meeting inspection standards at the time of the PM. This may indicate that the PM interval is too long, that a specific component type is reaching end of reliable service life, or that an operational condition is creating accelerated wear. The failure rate trend is an earlier signal than waiting for corrective work orders to accumulate.

How do these two metrics work together as a reliability view?

Overdue Work Orders and PM Inspection Failed and Completed address reliability from two different directions. Overdue Work Orders shows where known problems are not being addressed in time. PM Inspection Failed shows where the preventive program is finding problems before they escalate. An operation with a low overdue count and a stable PM failure rate is managing reliability well in both dimensions. An operation with rising overdue work orders and a rising PM failure rate is accumulating deferred maintenance and finding more problems simultaneously a combination that produces equipment failures.

How does this dashboard connect to Project Work Orders in FireFlight?

Project Work Orders connect individual maintenance and inspection tasks to overarching project structures. When a PM inspection produces a fail finding, the corrective action can be linked to the originating project structure. The Overdue Work Orders metric counts all work orders past their due date regardless of whether they are standalone or project-linked giving the reliability view a complete picture of all open maintenance obligations.

How long does it take to deploy FireFlight maintenance and reliability reporting?

Most operations are running live maintenance and reliability dashboards in weeks, not months. Both metrics read from work order and inspection records that the broader FireFlight deployment captures. PM inspection pass/fail outcomes are recorded at the point of inspection using the maintenance scheduling app, and the results post to the dashboard immediately. PCG handles configuration of inspection outcome categories and due date logic during deployment.

If your current maintenance metrics show total work order volume and PM completion counts without tracking overdue accumulation or inspection failure outcomes, the two signals that most directly measure whether the program is producing reliability rather than just activity are not in your view. FireFlight's Maintenance and Reliability Metrics Dashboard provides both from live records. Configuration takes weeks, not months.

Schedule your free consultation

Allison Woolbert

Principal, Phoenix Consultants Group | Developer, FireFlight Data Systems

PCG founded 1995. 500+ applications built across 31 years, roughly one-third in regulated environments where software failure carries direct operational and compliance consequences. FireFlight is the platform built from that body of work. When you contact PCG, Allison is the person who answers.

phxconsultants.com LinkedIn

FireFlight Data Systems is a product of Phoenix Consultants Group. PCG founded 1995. All system configurations are custom-built for each deployment. Implementation timelines, module availability, and integration scope vary by organization. Contact PCG directly to discuss requirements specific to your operation.