Works from CSV or workbook exports produced from SAP, IBM Maximo, Oracle ERP, Hexagon EAM, Infor, and other ERP, EAM, or CMMS systems. No direct integration or write-back is required — Review data requirements →
Benchmark Methodology

How AI2COE separates assumptions from diagnostic evidence.

Benchmarks are useful only when they are visibly labelled. This page documents the assumptions behind the scorecard, ROI calculator, industry value forms, and executive report interpretation.

LabelledBenchmark assumptions
LocalCurrency-aware display
EvidenceDiagnostic replaces estimates
Evidence summary

Buyer evidence resource

MRO Benchmark Methodology: Use this page to understand the operating question, exported-data evidence path, review boundary, and next Industrial IQ action. Review AI2COE benchmark assumptions for duplicate MRO rates, average item values, carrying-cost drag, recoverable working capital, FX conversion, and report.

Run Free Industrial IQ Snapshot
Review ownerExecutive sponsors, operating leaders, finance reviewers, procurement teams, maintenance owners, ERP/data leaders, and governance reviewers who need evidence before approving action.
Input file contextOperational CSV exports, item master fields, inventory, procurement, asset, work-order, finance, readiness, or governance data depending on the page.
Diagnostic evidenceSource-backed evidence, scores, confidence tiers, report outputs, action tracking, score history, and governance context.
Recommended actionRun Free Industrial IQ Snapshot and select the diagnostic engine that matches the operating question.
Benchmark variableReference rangeInterpretation boundary
Duplicate-rate assumptionBuyer-entered or default planning hypothesisReplaced by uploaded catalog evidence after a diagnostic run.
Average affected item valueBuyer-entered or default planning referenceUsed only where actual unit costs are unavailable.
Carrying-cost assumptionBuyer-entered or default annualized referenceRepresents a planning view of working-capital cost, storage, obsolescence, and management overhead.
Recoverable capital assumptionScenario range selected by the buyerDepends on stock status, criticality, interchangeability, and owner approval.
Emergency-buy premium assumptionBuyer-entered or default planning referenceApplied only as a scenario input where duplicate records may obscure supplier or available-stock logic.
FX conversionDisplay conversion onlyCurrency conversion is for readability and does not change the evidence class of the scenario.
Evidence discipline

Benchmark first. Actual diagnostic second. ERP action only after owner review.

AI2COE uses benchmark variables to help leaders size whether a problem is worth examining. PartsCleanse AI then uses uploaded data to create actual findings. The product never treats a planning benchmark as a command to retire, merge, or delete ERP records.

Proof control: Any public value statement should say whether it is a benchmark assumption, a calculated estimate, or diagnostic evidence from uploaded data.
FAQ

How to interpret AI2COE benchmark numbers.

Are AI2COE planning assumptions financial claims?

No. Public calculator values are planning assumptions. Financial interpretation depends on uploaded data, actual quantities, unit costs, confidence tiers, and owner-approved remediation.

Why does AI2COE use USD as a base value?

USD can be used as a neutral calculation base for scenario comparability. Display conversion does not make the scenario an observed financial result.

Why use Lakh and Crore for India-style currencies?

Large values in INR, PKR, BDT, LKR, and NPR are easier for local executives to read in Lakh and Crore notation than in generic M/B notation.

What makes the diagnostic different from the calculator?

The diagnostic uses the actual uploaded catalog to produce duplicate-family findings, confidence tiers, and report artifacts. The calculator only estimates a directional value signal.