Heavy Equipment Ops Fails When Parts, Service, and Sales Don't Share a Unit Grain

Parts has a part number. Service has a work order. Sales has a deal, a machine, or a fleet quote.

Leadership wants one margin story across the three. Someone joins on customer or model and calls it a unit. Every rollup invents a different “unit.” Parts attach to the wrong machine. Service hours miss the serial. Sales margin ignores the install base. Heavy equipment ops fails in the grain—not in the chart chrome.

No product-brand theater. Generic dealer and OEM-style ops: unit and serial are the join across parts, service, and sales. Without that grain, Power BI becomes three teams arguing in one workspace.

Unit grain is the join

In heavy equipment and dealer operations, the durable key is usually the unit—often a serial or equipment ID—tied to a customer, site, and configuration over time. Parts consumption, service history, warranty, telematics events, and sales or rental contracts all need that spine. Model, customer name, and stock number are useful attributes. They are not a substitute for unit grain.

When the model uses customer-only or model-only joins, margin by “unit” becomes fiction. Same English word. Different rows. The room inherits why Power BI reports show different numbers as an ops habit.

This sits next to customer margin disappears in the rollup: rollups without a stable grain invent winners and losers. The semantic model is the product. Three departmental extracts are raw material.

The costs of missing unit grain

1. Parts attach to the wrong machine. Bin and invoice truth never reach the serial. Warranty and cost-to-serve lie. Reorder signals drift.

2. Service history orphans. Work orders land without a clean unit key. Repeat failure analysis and contract profitability break before DAX starts.

3. Sales margin ignores installed reality. Deals close on model and price. Aftermarket and service attach later—to a different key. Lifetime margin by unit never exists.

4. Every team invents a unit. Stock number, VIN-like serial, fleet tag, rental asset ID, and CRM opportunity product line compete. One chart axis pretends they matched.

5. Customer rollups hide the damage. Account-level margin looks fine while unit-level losers hide inside—exactly the pattern in customer margin disappears in the rollup.

6. Telematics and hours cannot join. Meter reads and fault codes arrive on serial. Financials arrive on something else. Utilization debates become file swaps.

7. Trust migrates to side systems. Service keeps a bay spreadsheet. Parts keeps an export. Sales keeps a CRM pack. Power BI becomes a slide background.

8. Ownership vacuum on the bridge. Parts, service, and sales each “own” their system. Nobody owns the unit dimension. When numbers disagree, analytics inherits the blame—and who can change a measure never got answered for unit counts.

How to fix it: make unit/serial the spine

1. Write the decisions that require unit grain. Cost to serve by machine. Parts attach rate. Service contract margin. Sales-to-aftermarket attach. If a decision does not need unit, do not fake it on the same page.

2. Pick the system of record for unit identity. Often the equipment master in ERP or dealer management—not the CRM nickname and not the parts invoice alone. Document it.

3. Build a unit dimension you can operate. Serial/equipment ID, customer, site, model, status, in-service dates. History matters when units transfer. Late-arriving units need a policy—not silent orphans.

4. Map parts, service, and sales facts to that dimension. Refuse executive pages that roll “unit margin” on unmatched keys. Bad keys make good DAX look dishonest.

5. Separate measures with adult names. Parts cost on unit. Service hours and dollars on unit. Equipment sales margin. Aftermarket attach. Never one “Unit Margin” that switches grain by bookmark.

6. Show unmatched explicitly. Units with parts and no service. Work orders with no serial. Deals with no equipment ID. Make the gaps visible so operations can fix master data—not so analysts can hide them in filters.

7. Align calendars and as-of. Install date, invoice date, work-order close, and recognition date are different clocks. Label them. Cousin lesson from dual-clock manufacturing: shared nouns are not shared time.

8. Assign stewards. Ops or asset master owns unit identity. Parts, service, and sales own their facts. Analytics owns the model wiring. Control edits via who can change a measure.

9. Treat late unit master and fact loads as pack risk. A Monday ops pack on stale serials is a refresh failure as close risk for dealer operations—even when it is not a financial close.

10. Retire twin mashups on a schedule. Pick the disputed unit KPI from the last QBR. Consolidate to serial grain. Archive the customer-only “unit” page. Repeat.

What good looks like

Parts, service, and sales still run their systems. Power BI exposes a small set of owned measures on a shared unit dimension a successor can read.

Ops opens cost-to-serve by serial. Parts opens attach by unit. Sales opens deal margin and aftermarket follow-through on the same spine. When leadership asks why totals differ, they open grain and as-of—not three exports.

New analysts extend the certified unit model. They do not invent a fourth “unit” in a personal workspace joined on customer name.

A practical first sprint

Day one: export the three pages that claim unit, machine, or serial margin. Note the actual join keys. Day two: sit parts, service, and sales for thirty minutes and name the system of record for equipment ID. Day three: publish a unit dimension stub and remap one disputed measure—service cost by unit is a strong start.

You do not need a new dealer platform to stop unit theater. You need a spine, matched facts, and meeting discipline: if a margin number lacks unit grain and as-of, it does not enter the minutes.

Do not average unmatched serials into a customer rollup and call it insight. Do not hide null equipment IDs behind a top-N filter. Do not ask three departments to stop operating so one chart looks neat.

And do not treat a successful refresh as proof the mashup is honest. Fresh wrong joins are still wrong. Pair with why Power BI reports show different numbers when “unit” means four keys across workspaces.

Executive takeaway

Unit and serial grain is the join across parts, service, and sales.

Without it, every margin rollup invents a different “unit.” Build the spine first. Map the facts second. Then let Power BI tell an ops story the room can defend.

Need a 30-minute look at whether your dealer or heavy equipment pack shares a unit grain? Contact Alluvium. We’ll map one margin KPI to serial keys, unmatched gaps, and the model spine the three teams need.