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 →
Industrial IQ documentation

Governance Review Report

Governance Review Report documentation for AI2COE Industrial IQ buyers, operators, data owners, executives, and governance teams.

Run Free Industrial IQ SnapshotRequired Data by EngineDocs Home
8Engines
18Industry guides
0ERP write-back
Evidence-led diagnostic report showing score history, maturity bands, confidence levels, and prioritized enterprise AI recommendations.
Sample reports show the structure of evidence rows, confidence tiers, assumptions, limitations, actions, and executive outputs.
Task overview

Governance Review Report

Explains evidence traceability, confidence tiers, human review, audit trail, false-positive control, and no-write-back boundaries.

This guide explains the operating task, source data needed, validation steps, output interpretation, trust boundary, and where to go next.

UploadCSV export or sample dataset
Source FitRequired fields and data quality
AI MatchColumn aliases and confidence
NormalizeCanonical field preparation
DiagnoseEngine logic and evidence
ReportScore, actions, assumptions
RepeatScore history and renewal value
Required data by engine

Use this table before upload.

EngineRequired Data FileRequired FieldsOptional FieldsOutput GeneratedMinimum Viable UploadEngine-Specific Context
GovernanceMind AI Findings export Finding Id, Finding Type Confidence, Business Impact, Review Status, Reviewer, Source Record, Action Owner, Decision Reason, Action Due Date Governance readiness score, evidence, report, actions, score history Finding Id, Finding Type Confidence, Business Impact, Review Status, Reviewer, Source Record, Action Owner, Decision Reason, Action Due Date
Accepted CSV format

Prepare clean exports before upload.

Use UTF-8 CSV with one header row, one operational record per row, stable identifiers, ISO-style dates where available, numeric values without currency symbols, and separate columns for site, supplier, asset, quantity, value, and owner context.

Common errors: merged header rows, hidden subtotal rows, mixed currencies in one value column, duplicate column names, free-text dates, missing material or asset identifiers, and supplier names embedded inside descriptions.

If fields are missing: Industrial IQ still profiles source fit, but unmapped required fields reduce the AI Match Score, Mapping Readiness Score, diagnostic confidence, and report completeness until the user normalizes the data.

Sample row examples

Minimum viable row patterns.

  • Catalog Intelligence: Description: 6205-2RS bearing sealed SKF
  • Inventory Risk Intelligence: Material Id: MAT-100245 | Quantity: 42
  • Procurement Leakage Intelligence: Po Number: PO_NUMBER | Description: 6205-2RS bearing sealed SKF
  • Working Capital Intelligence: Material Id: MAT-100245 | Stock Value: 1850.00
Related engines

Which diagnostic should the buyer run next?

Related engine

GovernanceMind AI

Evidence traceability, review-level assignment, owner approval, auditability, and no-write-back governance.

Open documentation
Report anatomy

What the buyer can share internally.

Industrial IQ reports include scope, source-fit score, AI match score, mapping readiness, diagnostic confidence, score components, evidence records, assumptions, limitations, review requirements, action items, and recurring score history.

Governance Review ReportValue lever
Uploaded dataCustomer-specific diagnostic required
GovernanceMind AIRelated diagnostic engine
EstimateAssumption-labeled until reviewed
Benchmark assumptionUploaded evidenceConfidence tierHuman reviewReportable value
Documentation context

Use the docs to move from source export to reviewed diagnostic evidence.

Each guide keeps Industrial IQ documentation tied to source preparation, validation, evidence review, and Trust controls.

Docs home
Prepare export Use approved CSV/workbook exports or governed sample data. Map fields Confirm required fields, aliases, source fit, and limitations. Review evidence Inspect findings, confidence tiers, assumptions, and owner actions. Trust controls No ERP write-back, source-file purge after report generation, and human review before action.
AI2COE Copilot