Maintenance Usage Dashboard | FireFlight
Last updated: April 2026

Maintenance Usage Dashboard

Parts consumed by asset class and missing parts against active order requirements two live metrics that connect what maintenance is using to what procurement needs to have available before work orders stall.

FireFlight's Maintenance Usage Dashboard shows two live metrics: Parts Used by Asset Class or Type, giving a consumption breakdown by the category of equipment the parts were used on, and Missing Parts for Order Requirements, surfacing active work orders that need parts not currently in stock. Both update in real time from parts consumption and inventory records. Most operations are running live parts tracking in weeks, not months.
FireFlight Maintenance Usage Dashboard showing parts consumption by asset class and missing parts requirements for active work orders

A work order that stalls because a required part is not in stock did not fail because of a purchasing problem. It failed because parts consumption data was not connected to parts availability in a way that let procurement act before the technician arrived. Parts Used by Asset Class shows which equipment categories are consuming inventory at what rate the data that drives accurate reorder planning. Missing Parts for Order Requirements shows which active work already has a gap the data that drives immediate procurement action. Together they close the loop between what maintenance consumes and what procurement needs to provide.

Schedule your free consultation

What does parts consumption by asset class reveal that total consumption cannot?

Total parts consumption tells a maintenance manager how much the parts budget is being spent. Parts Used by Asset Class tells them where it is going and whether the distribution reflects the maintenance program's intent. A single asset class consuming 40% of total parts spend when it represents 15% of the fleet by count is either experiencing a disproportionate failure rate, requiring a specific type of repair that is parts-intensive, or approaching the point where replacement analysis is warranted. None of those conclusions are reachable from total consumption data they require the class-level breakdown.

The class-level view also drives more accurate reorder decisions than aggregate consumption averages. Different asset classes consume different parts at different rates. A generic reorder point calculated from total parts consumption across all asset types will consistently leave some classes under-stocked while others carry excess inventory. When consumption history is available by asset class, reorder points and safety stock levels can be calibrated to the actual consumption pattern of each class which reduces both stockouts and carrying costs simultaneously rather than forcing a choice between them.

Parts availability view in FireFlight showing missing parts flagged against active maintenance work orders before dispatch

Missing Parts for Order Requirements is where the dashboard prevents delays rather than documenting them. The metric surfaces active work orders that have parts requirements the current inventory cannot fulfill. When a gap appears, the procurement action generating a purchase order, contacting a vendor, pulling from a different location can happen before the work order has been dispatched and the technician is standing at the job site waiting for a part that should have been ordered two days ago.

The timing of that information is what determines its value. A missing parts alert that appears when a work order is created gives procurement the full lead time to resolve it days or weeks depending on the part. The same alert discovered when the technician opens the job is worth nothing because the resolution time required exceeds the available response time. FireFlight surfaces the gap as soon as the work order's parts requirements are compared against current inventory, which is at creation rather than at dispatch.

How do these two metrics connect to the Materials and Parts List catalog?

FireFlight's Materials and Parts List app is the master catalog for every part the operation uses sourcing data, preferred vendors, unit standards, and compliance references. The Maintenance Usage Dashboard reads from the transaction records that post against those catalog entries when parts are consumed in maintenance work. A part that appears in the Parts Used by Asset Class metric was consumed from a work order that referenced a catalog entry, which means the consumption record carries the part's full sourcing information.

When Missing Parts for Order Requirements flags a gap, the missing part is identifiable in the catalog along with which vendor supplies it, at what lead time, and at what unit cost. The procurement action is initiated from a complete information set rather than from a part number that someone has to look up separately. For maintenance operations that manage a large parts catalog across multiple vendors and asset classes, that direct connection between the gap identification and the sourcing information is what allows procurement to act on a missing parts flag in minutes rather than in hours.

Parts consumption records in FireFlight are generated at the point of use. When a technician issues a part to a work order, the consumption posts to the dashboard immediately. Missing parts gaps are identified when work order requirements are compared against live inventory levels not when the work order is scheduled, not when it is dispatched, but when it is created and the requirements are first recorded. The earlier the gap is visible, the longer the window for procurement to close it.

PCG has been building parts management and maintenance tracking systems since 1995 industrial maintenance operations, fleet service organizations, and field service companies where a stalled work order has a direct cost measured in downtime, delayed delivery, or failed compliance. The two-metric structure of this dashboard reflects the two questions that drive parts-related maintenance delays: which asset classes are consuming what, and which active work orders will be delayed if nothing is purchased today.

How does this dashboard connect to inventory and procurement workflows?

The Maintenance Usage Dashboard sits at the intersection of maintenance and procurement. Parts Used by Asset Class feeds into the analysis that sets reorder points and safety stock levels for each part category it is the historical consumption data that makes those decisions defensible rather than estimated. Missing Parts for Order Requirements feeds into the day-to-day procurement queue it is the current gap list that tells buyers which purchase orders need to be placed before specific work orders are delayed.

For operations that have historically managed parts availability by walking the stockroom before each week's maintenance schedule, this dashboard replaces that manual check with a live system view. The stockroom walk identifies what is present. The Missing Parts metric identifies what is absent relative to what is specifically needed for work orders that are already queued. The distinction matters because a stockroom with adequate general inventory may still have specific gaps against specific work orders gaps that a general inventory check would not surface but that the work-order-level requirements comparison in FireFlight surfaces automatically.

Ikhana on-screen guide
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 Usage Dashboard, Ikhana explains how parts consumption is attributed to asset classes, what triggers a part to appear in the Missing Parts metric, and how to use the dashboard to initiate a procurement action directly from a flagged gap. Maintenance and procurement team members both understand what the dashboard is telling them and what response each metric supports.

Learn more about Ikhana

What the two metrics give your operation

  • FireFlight Parts Used by Asset Class or Type. Parts consumption broken down by the category of asset the parts were consumed against. Shows which equipment classes are driving the most parts spend, enabling reorder points and safety stock levels to be calibrated to actual consumption patterns by asset type rather than to a generic average. Identifies asset classes with disproportionate parts consumption relative to their fleet share a signal that warrants further investigation into failure rates, repair patterns, or replacement timing.
  • FireFlight Missing Parts for Order Requirements. Active work orders or maintenance tasks that require parts not currently available in inventory. Updated in real time as work orders are created and their parts requirements are compared against live stock levels. The metric surfaces gaps while the work order is still in the planning or queue stage rather than at dispatch, giving procurement the lead time to place the order before the technician's arrival on-site makes the delay inevitable.

What PCG learned across 31 years of maintenance parts management system builds: the operations that had the fewest parts-related work order delays were not the ones with the largest inventory. They were the ones where parts consumption history was connected to parts availability requirements at the work order level, and where the gap between what was needed and what was available was visible before dispatch rather than at the job site.

Inventory investment decisions are most accurate when they are based on actual consumption by asset class rather than on total consumption averaged across all equipment types. Procurement timing decisions are most effective when the gap is identified at work order creation rather than at the moment the technician cannot proceed. Both conditions require the data connection that this dashboard provides between what maintenance is consuming and what procurement needs to have ready before the next work order is dispatched.

What operations see after deployment

  • FireFlight Work orders stop stalling because required parts were not ordered in time. Missing Parts for Order Requirements surfaces the gap when the work order is created. Procurement acts within hours. The technician arrives at the job with the required parts rather than arriving and waiting for an expedited order that should have been placed two days earlier.
  • FireFlight Parts inventory is right-sized by asset class rather than by total consumption average. Reorder points for parts used heavily by one asset class are calibrated to that class's actual consumption rate. Asset classes with lower or more predictable consumption carry appropriate safety stock without holding excess inventory to cover the consumption profile of other asset types.
  • FireFlight Asset classes with disproportionate parts spend are identified before the spend accumulates to the point where it appears in a budget review. The consumption breakdown by asset type makes the comparison between equipment classes visible in real time, surfacing the candidates for reliability review or replacement analysis while the maintenance investment decision is still timely.
  • FireFlight Maintenance and procurement work from the same data rather than from separate systems that only occasionally align. Parts consumption records from maintenance flow directly to the dashboard that procurement reviews. The missing parts list that procurement acts on is the same list that maintenance sees. No reconciliation step and no information lag between when the gap exists and when procurement knows about it.

Questions maintenance and procurement teams ask before deploying FireFlight

FireFlight What does the Maintenance Usage Dashboard show in FireFlight?
+
The dashboard shows two live metrics: Parts Used by Asset Class or Type, which shows parts consumption broken down by the category of asset the parts were consumed against, and Missing Parts for Order Requirements, which surfaces active work orders or maintenance tasks that require parts not currently in stock. Both metrics update in real time from parts consumption records and inventory data.
FireFlight What does Parts Used by Asset Class or Type reveal about maintenance operations?
+
Parts consumption by asset class shows which categories of equipment are driving the most parts spend. An asset class consuming a disproportionate share of parts relative to its size in the fleet may be failing more frequently than comparable classes, may require a specific category of repair that is parts-intensive, or may be approaching the point where replacement is more cost-effective than continued maintenance. The breakdown by asset class makes that comparison possible without manually aggregating parts records by equipment type.
FireFlight How does Missing Parts for Order Requirements prevent maintenance delays?
+
Missing Parts for Order Requirements shows which active work orders or maintenance tasks have parts requirements that cannot be fulfilled from current inventory. When this metric surfaces a gap, the maintenance team can initiate a purchase order before the technician arrives at the job and discovers the part is not available. The gap between discovering a missing part during job preparation and discovering it on-site is the difference between a procurement action and a stalled work order.
FireFlight How does Parts Used by Asset Class connect to purchasing decisions?
+
Parts consumption by asset class is the data that makes reorder logic and safety stock decisions specific to equipment type rather than generic across all inventory. An asset class with high and consistent parts consumption needs a higher safety stock for the parts it commonly uses than an asset class with low and sporadic consumption. Without the class-level breakdown, safety stock decisions are based on average consumption that obscures the difference between asset types.
FireFlight How do these two metrics work together to manage parts availability for maintenance?
+
Parts Used by Asset Class shows historical consumption patterns by equipment type. Missing Parts for Order Requirements shows current gaps against active work requirements. Together they give maintenance and procurement teams both the backward-looking view (which asset classes are consuming the most parts) and the forward-looking view (which current work orders will be delayed if no procurement action is taken now). Historical patterns inform reorder planning. Current gaps drive immediate action.
FireFlight How does the Maintenance Usage Dashboard connect to the Materials and Parts List app?
+
The Materials and Parts List app is the master catalog of every part the organization uses sourcing data, preferred vendors, unit standards, and compliance references. The Maintenance Usage Dashboard reads from the transaction records that post against those catalog entries when parts are consumed in maintenance. Parts that appear in Missing Parts for Order Requirements are identifiable against the catalog, including which vendor supplies them and at what lead time, so the procurement action can be initiated from the same system that identified the gap.
FireFlight How long does it take to deploy FireFlight maintenance parts tracking and usage reporting?
+
Most operations are running live parts consumption reporting in weeks, not months. The Maintenance Usage Dashboard reads from parts consumption records and inventory data that the broader FireFlight deployment captures. Asset class categorization and parts catalog setup are configured during deployment. PCG handles migration of existing parts catalogs and inventory records as part of the deployment process.

If your current view of parts usage is a total consumption number and your current awareness of missing parts comes from a technician calling from the job site, the data you need to prevent that call exists in your work order and inventory records it just is not being connected in real time. FireFlight's Maintenance Usage Dashboard makes that connection live. Configuration takes weeks, not months, and PCG handles the parts catalog and asset class setup during deployment.

Schedule your free consultation

Allison Woolbert
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.

Maintenance Usage Dashboard

 Never miss a service milestone again. Automate asset maintenance with confidence.