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 →
Score History

Track recurring diagnostic improvement across engines.

Authenticated users see monthly or quarterly score snapshots. Public preview mode shows the score-history structure without exposing private customer data.

PreviewPublic-safe
Private dataLogin required
No write-backGoverned action only
Evidence summary

Industrial IQ capability guide

Industrial IQ Score History: This Industrial IQ capability guide explains the operating question, evidence model, review boundary, and next action for the relevant platform workflow. Industrial IQ Score History for AI2COE Industrial IQ diagnostics: evidence, review, action, score history, and governance without ERP write-back.

Run Free Industrial IQ Snapshot
Review ownerIndustrial IQ evaluators, operating sponsors, data owners, and governance reviewers
Input file contextThe platform records, source exports, mappings, reports, score history, actions, and review context relevant to this capability.
Diagnostic evidenceA platform-specific view of how Industrial IQ converts exported data into evidence, reports, governed actions, and recurring visibility.
Recommended actionUse the page to understand the capability, then run Industrial IQ Snapshot or inspect sample reports.
Score history preview

How this surface works after a diagnostic run.

Industrial IQ keeps sample mode, uploaded-data mode, confidence tiers, evidence rows, report outputs, actions, score history, and governance status connected in one portal. Private records require account login.

Trust boundary: This public page shows the product model only. Customer reports, datasets, action items, score snapshots, and review notes remain authenticated.
Buyer interpretation

Why this surface matters after the report is generated.

Industrial IQ is not finished when a diagnostic score appears. The buyer still needs accountable review, evidence ownership, data-quality context, and a safe path from finding to decision. This public preview explains that operating model without exposing private diagnostic records.

Score history gives the buying committee a recurring view of improvement without confusing one diagnostic with a permanent truth. It helps leaders compare uploaded-data runs, sample runs, benchmark assumptions, and completed action outcomes over time. CFO, COO, CIO, procurement, maintenance, and governance owners can see whether the evidence base is improving before they fund broader cleanup, inventory action, ERP migration, or industrial AI adoption.

CFO / Finance

CFO / Finance review lens

Tracks whether inventory exposure, obsolete-stock signals, and capital-at-risk assumptions improve after reviewed actions are completed.

COO / Operations

COO / Operations review lens

Reviews recurring maintenance-readiness and stockout-risk scores across sites without treating a single diagnostic as the final answer.

CIO / ERP

CIO / ERP review lens

Uses score history to show data-readiness progress before ERP migration, master-data cleanup, or AI adoption decisions.

Governance

Governance review lens

Keeps sample, benchmark, and uploaded-data runs visibly separated so executive committees know what evidence is decision-ready.

Product surface contract

What the customer sees when logged in.

LayerBehavior
Score snapshotEngine, score type, date, score, risk level, dataset name, and sample-versus-uploaded-data flag.
Change versus prior runRecurring uploads show whether risk is reducing, stable, or increasing.
Benchmark comparisonScore history separates benchmark assumptions from uploaded-data diagnostic evidence.
Renewal valueExecutives can see identified, reviewed, accepted, resolved, and remaining value over time.