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 →
Proof Pack

The public evidence layer for PartsCleanse AI.

Enterprise buyers should not have to trust a claim without knowing whether it is a benchmark assumption, a calculator estimate, a diagnostic finding, or a platform control. This proof pack puts those surfaces in one place.

Request Diagnostic PilotSafe Claims Registry
8 assetsEvidence surfaces
Source purgeData lifecycle stated
No write-backERP-safe posture
Evidence summary

Buyer evidence resource

PartsCleanse AI Proof Pack: Use this page to understand the operating question, exported-data evidence path, review boundary, and next Industrial IQ action. Open the PartsCleanse AI proof pack: benchmark methodology, engine validation, sample reports, safe claims, source purge, and pilot evidence assets.

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.
Enterprise trust posture

Proof controls buyers expect before they upload operational data.

Source purge Uploaded source files are purged after report generation; summary metrics and Open Findings remain.
No ERP write-back The diagnostic creates evidence for review. It never changes, deletes, merges, or overwrites ERP records.
Local currency Reports display money in the user's selected or country-derived currency, while USD remains the base audit calculation.
Audit trail Report ownership, access, quota, and feedback events are retained for governed review.
Session downloads Excel, Word, PDF, and CSV downloads are available only in the active generation session.
Open Findings Browser findings remain available without retaining the original source catalog rows.
Proof architecture

How a public claim becomes buyer-usable evidence.

01 Source file

CSV or workbook upload is mapped, normalized, and checked for readiness.

02 Engine finding

Duplicate-family candidates are scored with industrial false-positive controls.

03 Executive interpretation

Finance, procurement, operations, and governance views translate findings into decisions.

04 Data lifecycle

Source catalog is purged after report generation; summary metrics and Open Findings remain.

05 Buyer decision

The committee decides whether remediation, governance, or a deeper engagement is justified.

Evidence library

Open the proof surfaces before uploading operational data.

Benchmark methodology

Benchmark methodology

Shows duplicate-rate, item-value, carrying-cost, recoverability, and FX assumptions before they are replaced by uploaded data.

Open evidence page -> Engine validation benchmark

Engine validation benchmark

Explains 50K scale testing, false-positive traps, discriminator controls, and no-write-back governance.

Open evidence page -> Report gallery

Report gallery

Shows the CFO, procurement, operations, CIO, PDF, Word, Excel, and Open Findings evidence surfaces.

Open evidence page -> Sample reports

Sample reports

Demonstrates what leadership sees without exposing customer records or implying customer endorsement.

Open evidence page -> Sample catalogs

Sample catalogs

Provides synthetic SAP-style files so buyers can test the diagnostic flow before using live data.

Open evidence page -> Safe claims registry

Safe claims registry

Separates benchmark assumptions, calculator estimates, diagnostic evidence, controls, and roadmap statements.

Open evidence page -> Pilot proof kit

Pilot proof kit

Gives buying committees a controlled pilot path with ICP decision lenses and demo storyboards.

Open evidence page -> Data handling commitment

Data handling commitment

Documents source-catalog purge, retained metadata boundaries, and report ownership posture.

Open evidence page ->
Competitor pressure control

Proof is where diagnostic-first positioning must stand up.

Competitors can claim larger platforms, deeper services, or broader data networks. AI2COE should win the first decision by proving duplicate exposure from the buyer's own catalog before platform scope, remediation budget, or ERP write-back is approved.

Launch standard: if a value, runtime, data-retention, or output claim appears on the site, it should point back to one of these proof surfaces.