Data Foundations · 7 free guides
Data foundations: governed data readiness for industrial AI
Most industrial AI projects that fail, fail on data. This section treats plant data as the control surface for AI risk: who owns it, where it flows, how good it is, and who can touch it.
Most industrial AI projects do not fail because the model was wrong. They fail because the data feeding it was wrong, late, missing context, or owned by nobody. A vibration model trained on a historian with aggressive compression. A scrap predictor that never knew which product was running. A vision QC system labeled by one inspector on day shift and judged by a different inspector on nights. None of these are algorithm problems. They are data problems, and they are governance problems.
That is why data foundations sit inside an AI governance site and not next to it.
Governed data is the control surface for AI risk
When you write an AI policy or run an AI risk assessment, most of the controls you can actually enforce live in the data layer:
- Ownership. Someone signs off on what a tag means, what a label means, and who may use it.
- Lineage. You can trace a model's input back to the sensor, PLC, historian and transformation that produced it.
- Quality. Timestamps, units, calibration and missing context are checked before a model sees them, not after it misbehaves.
- Access. Read and write rights are explicit. Nobody publishes a setpoint into the plant because a dashboard made it easy.
- OT exposure. Every new data path out of Level 2 or Level 3 is a new conduit, and it gets reviewed like one.
- Retention. You know how long raw and derived data are kept, and why.
If those six things are weak, no amount of model documentation will make the AI system trustworthy. If they are strong, most AI risk becomes manageable with the small team you already have.
What this section covers
The pages here walk through the data decisions that mid-market plants actually face:
- Moving OT data to a cloud historian without opening inbound paths into the control network.
- The Unified Namespace in plain terms, and who should be allowed to publish to it.
- Predictive maintenance programs, where the gap is usually failure history, not sensors.
- Digital twins that earn their keep, and how to avoid vanity twins.
- Industrial data quality: drift, deadbands, timestamps and labels.
- Edge vs cloud AI as a governance and security choice, not just an architecture choice.
- The industrial data readiness checklist to score where you stand today.
Each page stays vendor-neutral and assumes a lean IT/OT team, brownfield equipment and OEM-owned assets. Where a product category matters, we name well-known examples without endorsing them.
Where to start
If you have one afternoon, run the industrial data readiness assessment and pick the two lowest-scoring dimensions. Then cross-check them against your AI use case inventory. The use cases that depend on your weakest data are the ones to pause, fix or scope down first.
Start here
Digital twins for mid-market manufacturers: data, governance and security
A digital twin is only useful when it answers a specific operational question at the fidelity that question needs. Govern it like any engineering model: versioned, validated against the plant, clear on who owns the IP, and connected to OT through a reviewed, read-mostly path.
Guide · 6 min read
All Data Foundations guides
- Edge vs cloud AI in manufacturing: a governance and security decision guideEdge vs cloud AI in manufacturing: compare latency, bandwidth, data sovereignty, security and edge MLOps, plus a decision table for mid-market plants.6 min read
- Industrial data quality for analytics and AI: what breaks and who fixes itIndustrial data quality for AI: fix timestamp alignment, sensor drift, historian compression, missing batch context and vision labels, and name data stewards.6 min read
- Industrial data readiness for AI: a 40-point checklist with scoringScore your plant's industrial data readiness for AI with 40 checks across inventory, connectivity, context, quality, ownership, security, platform and skills.6 min read
- Moving OT data to a cloud historian: architecture, security and governanceMove OT data to a cloud historian without exposing the control network: architecture options, outbound-only design, tag naming, cost traps and a checklist.7 min read
- Predictive maintenance programs: data, validation and governanceRun a predictive maintenance program that pays off: fix CMMS failure history, retrofit sensors sensibly, validate models, and govern who acts on each alert.7 min read
- Unified Namespace (UNS) explained for mid-market manufacturersA plain-English guide to the Unified Namespace: ISA-95 topic structure, MQTT and Sparkplug B, who may publish commands, and when a UNS is overkill.7 min read
FREE TEMPLATES
Free templates for this topic
AI use case register for manufacturers (Excel template)
A ready-to-use Excel register for listing every AI system in your plants, including AI hidden inside vendor equipment and SaaS tools, with owners, data sources and a risk tier.
Free download
AI risk triage worksheet (Excel)
Answer twelve yes, no or partial questions per use case and the worksheet computes a risk tier, flags possible EU AI Act high-risk or prohibited indicators and tells you what review comes…
Free download
OT and AI vendor security questionnaire (Excel)
A structured questionnaire to send to OEMs, integrators and AI vendors before purchase or renewal, covering OT security, remote access, SBOMs, AI model behavior and data rights, with…
Free download
Not sure where to start?
Take a 10-minute self-assessment and get a prioritised 30/60/90-day plan for your plants.