How do you calculate usable asset hierarchy completeness?

Multiply records cleansed per cycle by available cycles to get gross output (85 x 42 = 3,570), then multiply by reviewer availability (88%) and acceptance rate (93%) to get usable completeness, which here is 2,922 records.

What is a good acceptance rate for asset hierarchy records?

First-pass acceptance above 90% is strong for a mature CMMS team with clear naming and parenting standards. The 93% default here means only about 7% of reviewed records bounce back for rework, which is realistic once a data dictionary is locked.

Why is gross completeness higher than usable completeness?

Gross (3,570) counts every record someone touched. Usable (2,922) reflects records that survived limited reviewer availability and acceptance gates. The 648-record gap is work that was started but not yet verified or accepted.

What causes the biggest loss in hierarchy completeness?

In this example, availability limits cost 428 records while data and acceptance gaps cost 220 records. Reviewer bandwidth is usually the larger lever, so protecting review time often beats hiring more cleansers.

Asset hierarchy completeness vs asset register count: what is the difference?

A register count is just how many asset numbers exist. Completeness measures how many are properly cleansed, parented, and accepted, which is what actually enables PM assignment and failure-code analysis.

How many cleanup cycles do I need to finish my register?

Divide your total target records by usable completeness per cycle. If you need 8,000 usable records and each project run yields 2,922, you need roughly three project waves or a higher per-cycle rate.

CMMS, EAM & Spare Parts Management calculator

Asset Hierarchy Completeness Calculator

Asset Hierarchy Completeness estimates how many asset records you can realistically build out and validate in a CMMS or EAM cleanup project, after accounting for reviewer availability and acceptance rates. Reliability engineers, CMMS administrators, and EAM implementation leads use it to size data-cleansing sprints before a SAP PM, Maximo, or Fiix go-live. A clean, fully-parented asset hierarchy is the backbone of every downstream metric, from PM scheduling to MTBF, so a record that is created but never accepted is effectively missing. This calculator separates the gross records touched from the usable records that survive review.

What this calculator does

Estimate usable asset hierarchy records completed after considering records per cleanup cycle, available review cycles, and data acceptance quality.
a maintenance or asset-management team needs to plan asset master data cleanup and know whether the hierarchy will support work orders, PMs, and spare parts linkage for a asset hierarchy cleanup
It computes usable asset hierarchy completeness by discounting gross records produced across all cycles for reviewer availability and first-pass acceptance.

Formula used

Gross asset hierarchy completeness = asset records completed per review cycle × available hierarchy cleanup cycles
Usable asset hierarchy completeness = gross asset hierarchy completeness × CMMS data review availability × asset hierarchy records accepted without rework

Inputs explained

Asset records cleansed and parented per review cycle:
Hierarchy cleanup cycles available before go-live:
CMMS data-review resource availability:
Asset records accepted by reliability without rework:

How to use the result

Use it during CMMS data migration, asset register rebuilds, or hierarchy standardization projects to forecast deliverable record counts and staff the review queue.
It assumes a steady cleansing rate and a constant acceptance percentage; complex parent-child relationships or legacy data quality often degrade throughput as the easy records get done first.

Common questions

How do you calculate usable asset hierarchy completeness? Multiply records cleansed per cycle by available cycles to get gross output (85 x 42 = 3,570), then multiply by reviewer availability (88%) and acceptance rate (93%) to get usable completeness, which here is 2,922 records.
What is a good acceptance rate for asset hierarchy records? First-pass acceptance above 90% is strong for a mature CMMS team with clear naming and parenting standards. The 93% default here means only about 7% of reviewed records bounce back for rework, which is realistic once a data dictionary is locked.
Why is gross completeness higher than usable completeness? Gross (3,570) counts every record someone touched. Usable (2,922) reflects records that survived limited reviewer availability and acceptance gates. The 648-record gap is work that was started but not yet verified or accepted.
What causes the biggest loss in hierarchy completeness? In this example, availability limits cost 428 records while data and acceptance gaps cost 220 records. Reviewer bandwidth is usually the larger lever, so protecting review time often beats hiring more cleansers.
Asset hierarchy completeness vs asset register count: what is the difference? A register count is just how many asset numbers exist. Completeness measures how many are properly cleansed, parented, and accepted, which is what actually enables PM assignment and failure-code analysis.

Last reviewed 2026-05-12.