{"data":{"slug":"manufacturing-data-governance","title":"Manufacturing Data Governance: Ownership, Quality and Lineage","summary":"Industrial digitalization projects collect more data every year — historians, MES, quality systems, energy meters, edge devices — and then struggle with the…","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/manufacturing-data-governance","markdown_url":"https://wiki.aspotomasyon.com/article/manufacturing-data-governance.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/manufacturing-data-governance","published":"2026-08-11T13:05:19+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":866,"image":"https://wiki.aspotomasyon.com/assets/social/manufacturing-data-governance-a71162f39625.png","html":"<p>Industrial digitalization projects collect more data every year — historians, MES, quality systems, energy meters, edge devices — and then struggle with the same symptoms: three different systems report different OEE, the KPI dashboard's numbers change depending on who answers, and nobody owns the definitions. <strong>Manufacturing data governance</strong> is the discipline that fixes this: clear ownership, agreed definitions, measured quality, and documented lineage for the data that decisions depend on. It is less glamorous than AI, and it is what makes AI work.</p><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-context.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"An industrial data workflow. Each handoff needs an owner and a documented data contract; collecting more signals alone does not establish business value.\"><figcaption>An industrial data workflow. Each handoff needs an owner and a documented data contract; collecting more signals alone does not establish business value. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-context.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure>\n\n<h2 id=\"what-data-governance-means-on-the-plant-floor\">What Data Governance Means on the Plant Floor</h2>\n\n<p>Governance is not bureaucracy; it is answering five questions for every important data asset:</p>\n\n<ol>\n  <li><strong>What is it?</strong> — an agreed definition. \"Downtime\" means what, exactly? Planned vs unplanned? Does a changeover count? The definition lives in one place and is used everywhere.</li>\n  <li><strong>Who owns it?</strong> — a named accountable person per data domain (production data, quality data, energy data, maintenance data). Ownership means they decide definitions, access, and quality priorities.</li>\n  <li><strong>Where does it come from?</strong> — the authoritative source system for each fact. The historian is authoritative for machine states; the MES for order progress; the CMMS for work orders. Conflicts are resolved by source, not by convenience.</li>\n  <li><strong>How good is it?</strong> — measured quality: completeness, timeliness, accuracy, consistency. \"Good enough for monitoring but not for billing\" is a legitimate, documented classification.</li>\n  <li><strong>Who may use it, and how long do we keep it?</strong> — access rules (who sees downtime by operator?) and retention (how long does process data stay before archival/deletion?).</li>\n</ol>\n\n<h2 id=\"building-the-governance-foundation\">Building the Governance Foundation</h2>\n\n<p>Start small and formalize incrementally:</p>\n\n<ul>\n  <li><strong>Business glossary</strong> — a document (wiki page is fine) with the definitions of the top 50 terms: OEE, availability, yield, downtime classes, scrap, RFT. Each term has one definition, one formula, and one source system.</li>\n  <li><strong>Data owners and stewards</strong> — an owner per domain; a steward does the operational work (definitions maintenance, quality monitoring). This is a role assignment, not a new department.</li>\n  <li><strong>System-of-record map</strong> — one page listing every system and which facts it owns. When two systems disagree, the map says who wins.</li>\n  <li><strong>Quality monitoring</strong> — automated checks on critical data flows: historian gaps, negative values where impossible, stale timestamps, duplicate events. Alert the steward, not the whole plant.</li>\n  <li><strong>Change control</strong> — definitions change (a new product type changes \"yield\"); the change is recorded with an effective date so history stays comparable.</li>\n</ul>\n\n<h2 id=\"data-lineage-and-traceability\">Data Lineage and Traceability</h2>\n\n<p><strong>Lineage</strong> is the record of where a number came from: which sensor, which calculation, which system, which transformation. It matters most when data crosses system boundaries:</p>\n\n<ul>\n  <li>Every KPI on a dashboard should be traceable to its raw data and its calculation (with version).</li>\n  <li>Regulated industries (pharma, food) already demand audit trails; lineage makes them <em>usable</em> for analytics instead of an afterthought.</li>\n  <li>Machine learning models trained on plant data need lineage to answer \"what changed between model version 2 and 3?\" — the most common production ML failure.</li>\n</ul>\n\n<p>Practical lineage tools: the historian's tag metadata (source, engineering unit, last calibration), ETL/edge pipeline logs, and — for the important flows — a simple data catalog that records pipeline versions and refresh times.</p>\n\n<h2 id=\"governance-and-the-automation-layer\">Governance and the Automation Layer</h2>\n\n<p>The automation department is both a data producer and a data consumer, and governance friction concentrates at its boundaries:</p>\n\n<ul>\n  <li>Tag names change during commissioning — the historian consumers downstream break silently. Govern tag renames with a notice period and a mapping table.</li>\n  <li>PLC programs are the de facto definition of machine behavior; the governance model must include the control narrative and interlock documentation as reference data.</li>\n  <li>OT data flowing to IT systems needs contracts (units, quality, timestamps) — the same discipline as any interface, but now with governance consequences.</li>\n</ul>\n\n<h2 id=\"making-governance-stick\">Making Governance Stick</h2>\n\n<p>Governance fails when it is a document exercise. The practices that survive:</p>\n\n<ul>\n  <li>Governance reviews attached to real decisions (monthly performance review walks the glossary; disagreements escalate with evidence).</li>\n  <li>Data quality KPIs in the same dashboard as production KPIs — quality is not a separate report.</li>\n  <li>One owner per KPI, visibly named on the dashboard.</li>\n  <li>Annual data inventory review — systems and facts change faster than documents.</li>\n</ul>\n\n<h2 id=\"summary\">Summary</h2>\n\n<p>Manufacturing data governance is the operating system for industrial analytics: agreed definitions, named owners, authoritative sources, measured quality, and documented lineage. Build the glossary, the system-of-record map, and the quality monitoring first; attach governance to real decisions; and make owners accountable in the visible KPI process. Without it, every analytics project is an argument about whose numbers are right.</p><section class=\"engineering-check\"><h2 id=\"apply-this-to-your-project\">Apply this to your project</h2><ul><li>Name the operational decision, its owner, and the evidence required to judge whether it improved.</li><li>Document asset identifiers, units, timestamps, quality rules, and definitions shared between OT and business applications.</li><li>Compare the pilot against a recorded baseline before extending it to other machines or sites.</li></ul><p><a href=\"https://wiki.aspotomasyon.com/guides\">Follow an ASP project guide</a> to connect the fundamentals with implementation and acceptance.</p></section><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-review.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"Engineering review sequence: Question → Baseline → Pilot → Scale. Keep the recorded evidence with the accepted configuration.\"><figcaption>Engineering review sequence: Question → Baseline → Pilot → Scale. Keep the recorded evidence with the accepted configuration. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-review.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure><h2 id=\"primary-references-and-further-reading\">Primary references and further reading</h2><p>Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.</p><ul><li><a href=\"https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard\" rel=\"noopener noreferrer\" target=\"_blank\">ISA — ISA-95 enterprise/control system integration</a></li><li><a href=\"https://opcfoundation.org/about/opc-technologies/opc-ua/\" rel=\"noopener noreferrer\" target=\"_blank\">OPC Foundation — Information modelling</a></li></ul><!-- asp-editorial-202609 -->","markdown":"# Manufacturing Data Governance: Ownership, Quality and Lineage\n\n> Industrial digitalization projects collect more data every year — historians, MES, quality systems, energy meters, edge devices — and then struggle with the…\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/manufacturing-data-governance\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: Digital Transformation\n- Published: 2026-08-11 · Updated: 2026-09-13\n- Reading time: 4 min · Language: English\n\nIndustrial digitalization projects collect more data every year — historians, MES, quality systems, energy meters, edge devices — and then struggle with the same symptoms: three different systems report different OEE, the KPI dashboard's numbers change depending on who answers, and nobody owns the definitions. **Manufacturing data governance** is the discipline that fixes this: clear ownership, agreed definitions, measured quality, and documented lineage for the data that decisions depend on. It is less glamorous than AI, and it is what makes AI work.\n\n![An industrial data workflow. Each handoff needs an owner and a documented data contract; collecting more signals alone does not establish business value.](https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-context.svg)\n\n*An industrial data workflow. Each handoff needs an owner and a documented data contract; collecting more signals alone does not establish business value.*\n\n## What Data Governance Means on the Plant Floor\n\nGovernance is not bureaucracy; it is answering five questions for every important data asset:\n\n1. **What is it?** — an agreed definition. \"Downtime\" means what, exactly? Planned vs unplanned? Does a changeover count? The definition lives in one place and is used everywhere.\n2. **Who owns it?** — a named accountable person per data domain (production data, quality data, energy data, maintenance data). Ownership means they decide definitions, access, and quality priorities.\n3. **Where does it come from?** — the authoritative source system for each fact. The historian is authoritative for machine states; the MES for order progress; the CMMS for work orders. Conflicts are resolved by source, not by convenience.\n4. **How good is it?** — measured quality: completeness, timeliness, accuracy, consistency. \"Good enough for monitoring but not for billing\" is a legitimate, documented classification.\n5. **Who may use it, and how long do we keep it?** — access rules (who sees downtime by operator?) and retention (how long does process data stay before archival/deletion?).\n\n## Building the Governance Foundation\n\nStart small and formalize incrementally:\n\n- **Business glossary** — a document (wiki page is fine) with the definitions of the top 50 terms: OEE, availability, yield, downtime classes, scrap, RFT. Each term has one definition, one formula, and one source system.\n- **Data owners and stewards** — an owner per domain; a steward does the operational work (definitions maintenance, quality monitoring). This is a role assignment, not a new department.\n- **System-of-record map** — one page listing every system and which facts it owns. When two systems disagree, the map says who wins.\n- **Quality monitoring** — automated checks on critical data flows: historian gaps, negative values where impossible, stale timestamps, duplicate events. Alert the steward, not the whole plant.\n- **Change control** — definitions change (a new product type changes \"yield\"); the change is recorded with an effective date so history stays comparable.\n\n## Data Lineage and Traceability\n\n**Lineage** is the record of where a number came from: which sensor, which calculation, which system, which transformation. It matters most when data crosses system boundaries:\n\n- Every KPI on a dashboard should be traceable to its raw data and its calculation (with version).\n- Regulated industries (pharma, food) already demand audit trails; lineage makes them *usable* for analytics instead of an afterthought.\n- Machine learning models trained on plant data need lineage to answer \"what changed between model version 2 and 3?\" — the most common production ML failure.\n\nPractical lineage tools: the historian's tag metadata (source, engineering unit, last calibration), ETL/edge pipeline logs, and — for the important flows — a simple data catalog that records pipeline versions and refresh times.\n\n## Governance and the Automation Layer\n\nThe automation department is both a data producer and a data consumer, and governance friction concentrates at its boundaries:\n\n- Tag names change during commissioning — the historian consumers downstream break silently. Govern tag renames with a notice period and a mapping table.\n- PLC programs are the de facto definition of machine behavior; the governance model must include the control narrative and interlock documentation as reference data.\n- OT data flowing to IT systems needs contracts (units, quality, timestamps) — the same discipline as any interface, but now with governance consequences.\n\n## Making Governance Stick\n\nGovernance fails when it is a document exercise. The practices that survive:\n\n- Governance reviews attached to real decisions (monthly performance review walks the glossary; disagreements escalate with evidence).\n- Data quality KPIs in the same dashboard as production KPIs — quality is not a separate report.\n- One owner per KPI, visibly named on the dashboard.\n- Annual data inventory review — systems and facts change faster than documents.\n\n## Summary\n\nManufacturing data governance is the operating system for industrial analytics: agreed definitions, named owners, authoritative sources, measured quality, and documented lineage. Build the glossary, the system-of-record map, and the quality monitoring first; attach governance to real decisions; and make owners accountable in the visible KPI process. Without it, every analytics project is an argument about whose numbers are right.\n\n## Apply this to your project\n\n- Name the operational decision, its owner, and the evidence required to judge whether it improved.\n- Document asset identifiers, units, timestamps, quality rules, and definitions shared between OT and business applications.\n- Compare the pilot against a recorded baseline before extending it to other machines or sites.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n![Engineering review sequence: Question → Baseline → Pilot → Scale. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/digital-transformation-review.svg)\n\n*Engineering review sequence: Question → Baseline → Pilot → Scale. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [ISA — ISA-95 enterprise/control system integration](https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard)\n- [OPC Foundation — Information modelling](https://opcfoundation.org/about/opc-technologies/opc-ua/)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/manufacturing-data-governance (Manufacturing Data Governance: Ownership, Quality and Lineage, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"what-data-governance-means-on-the-plant-floor","title":"What Data Governance Means on the Plant Floor"},{"id":"building-the-governance-foundation","title":"Building the Governance Foundation"},{"id":"data-lineage-and-traceability","title":"Data Lineage and Traceability"},{"id":"governance-and-the-automation-layer","title":"Governance and the Automation Layer"},{"id":"making-governance-stick","title":"Making Governance Stick"},{"id":"summary","title":"Summary"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"ISA — ISA-95 enterprise/control system integration","url":"https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard"},{"name":"OPC Foundation — Information modelling","url":"https://opcfoundation.org/about/opc-technologies/opc-ua/"}],"related":[{"slug":"data-integrity-alcoa-plus-21-cfr-part-11-automation","title":"GxP Data Integrity in Automation: ALCOA+ and 21 CFR Part 11","summary":"ALCOA+ describes the properties GxP automation data must have, and audit trails, access control, and synchronized clocks are how PLC, SCADA, and historian…","category":{"slug":"process-industries-solutions","name":"Process Industries Solutions"},"url":"https://wiki.aspotomasyon.com/article/data-integrity-alcoa-plus-21-cfr-part-11-automation","markdown_url":"https://wiki.aspotomasyon.com/article/data-integrity-alcoa-plus-21-cfr-part-11-automation.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/data-integrity-alcoa-plus-21-cfr-part-11-automation","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1848,"image":"https://wiki.aspotomasyon.com/assets/social/data-integrity-alcoa-plus-21-cfr-part-11-automation-fdab5a1cbd0f.png"},{"slug":"llm-rag-industrial-documentation-safe-deployment","title":"LLM Assistants for Plant Documentation: Safe RAG Deployment","summary":"A plant documentation assistant is safe only when it cites controlled revisions, respects source permissions, and stays read-only and advisory, which a fixed…","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/llm-rag-industrial-documentation-safe-deployment","markdown_url":"https://wiki.aspotomasyon.com/article/llm-rag-industrial-documentation-safe-deployment.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/llm-rag-industrial-documentation-safe-deployment","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1927,"image":"https://wiki.aspotomasyon.com/assets/social/llm-rag-industrial-documentation-safe-deployment-40155621b146.png"},{"slug":"asset-administration-shell-digital-twin-interoperability","title":"Asset Administration Shell: A Standard Digital Twin Container","summary":"The Asset Administration Shell gives each physical asset a standard digital container of submodels, so engineering, operations, and enterprise systems can…","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/asset-administration-shell-digital-twin-interoperability","markdown_url":"https://wiki.aspotomasyon.com/article/asset-administration-shell-digital-twin-interoperability.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/asset-administration-shell-digital-twin-interoperability","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1876,"image":"https://wiki.aspotomasyon.com/assets/social/asset-administration-shell-digital-twin-interoperability-aa58402e4e17.png"},{"slug":"unified-namespace-governance","title":"Unified Namespace Governance: Ownership, Topics, and Change Control","summary":"A unified namespace needs shared meaning and ownership, not just a broker with many topics.","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/unified-namespace-governance","markdown_url":"https://wiki.aspotomasyon.com/article/unified-namespace-governance.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/unified-namespace-governance","published":"2026-09-13T11:07:23+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":2,"word_count":353,"image":"https://wiki.aspotomasyon.com/assets/social/unified-namespace-governance-6ca9e2e9e815.png"}],"citation":"ASP OTOMASYON. Manufacturing Data Governance: Ownership, Quality and Lineage. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/manufacturing-data-governance"}}