The bottom line
Data governance in manufacturing isn't a compliance exercise - it's what determines whether your analytics are trusted or ignored. If plant managers won't act on a dashboard because they don't trust the data behind it, the governance problem is costing you more than the technology problem.
In This Article
Why OT Data Has No Natural Owner
In a typical manufacturing organisation, IT owns the enterprise systems - ERP, WMS, and the corporate network. The engineering team owns the OT systems - PLCs, SCADA, MES, and the plant-floor network. Operations management owns the production KPIs. Quality management owns the quality data. Maintenance owns the CMMS.
None of these functions owns the data that flows between them. OEE is a good example: it is calculated from availability data (operations), performance data (engineering), and quality data (quality management). Each function has a defensible claim to ownership of one component. Nobody owns the composite metric - which is why OEE figures routinely differ by 5–10 percentage points depending on who ran the calculation and which data source they used.
This is not an organisational failure. It is the natural consequence of a domain where operational responsibility is distributed across functions and operational technology was designed for control, not for data governance. The answer is not to reorganise - it is to establish governance conventions that work within the existing structure.
When OEE figures differ by 8 points depending on who calculated them, the problem is not the formula - it is the absence of an agreed data owner for each component.
The Minimum Viable Governance Framework
Manufacturing analytics does not require a full enterprise data governance programme to get started. It requires three things: agreed KPI definitions, a single equipment hierarchy, and named data stewards per operational domain.
Agreed KPI definitions means writing down - and getting sign-off from operations, engineering, and quality - exactly how OEE, MTBF, first-time-right rate, and the five to ten other metrics that drive decisions are calculated. Which downtimes are included in availability? What counts as a speed loss versus a planned rate? These are political questions as much as technical ones, and they must be resolved before any analytics programme produces numbers that people trust.
A single equipment hierarchy means one agreed list of assets, with consistent naming, consistent grouping (line, cell, plant), and consistent maintenance codes. This is the spine of manufacturing analytics. Every downtime event, every maintenance work order, every quality reject needs to attach to an asset in this hierarchy - otherwise cross-asset analysis is impossible and trend data is meaningless.
The $12.9M Annual Cost of Getting It Wrong
Gartner research has put the cost of poor data quality at an average of USD 12.9 million per organisation per year (Gartner Data Quality Market Survey, 2020/21). In manufacturing, the direct cost is higher because operational decisions are made continuously and at scale — a wrong inventory number drives a wrong replenishment decision that drives a stockout that drives a lost sale that drives a margin hit. The chain is short and the compounding is fast.
The indirect cost is harder to measure but arguably more significant: analytics programmes that produce numbers nobody trusts get abandoned. Once a dashboard is labelled as "unreliable" by the operations team, the investment is effectively lost - regardless of the quality of the underlying platform.
Governance is the investment that makes all other analytics investments pay off. A well-governed dataset with clear ownership, agreed definitions, and named stewards produces numbers that operations teams trust and act on. Without that foundation, the sophistication of the analytics platform is irrelevant.
What Governed Manufacturing Analytics Looks Like
Governance in manufacturing is easier to sustain when it lives in the platform rather than in a policy document. The practical pattern is to land OT and enterprise data — SCADA tags, MES events, the ERP, maintenance records — into one governed store on Microsoft Fabric, with OneLake as the single copy and Azure Data Factory handling the batch feeds. The agreed KPI definitions then live in one place: a Power BI Direct Lake semantic model where OEE, MTBF, and first-time-right are defined once, not re-derived in every report.
That semantic model is where governance stops being theoretical. Row-level security enforces who sees which plant. Lineage shows exactly which PLC tag and which work order fed a number, so a contested OEE figure can be traced rather than argued. Data stewards own their domain inside the model — operations owns availability, quality owns the reject logic — but the composite metric has one definition everyone reads from. The argument about "whose number is right" ends because the lineage is on the screen.
This is also what makes the difference between governance as overhead and governance as enabler. The same governed foundation that produces a trusted OEE number is the one predictive maintenance learns from and the one a manufacturing analytics estate scales on. You are not governing data for its own sake — you are building the single source the whole operation can act on.
Where Governance Still Breaks
Even with the right platform, governance fails when nobody owns it above the function level. IT owns the network, engineering owns the PLCs, quality owns the rejects — and the composite data still falls through the gap between them. Someone has to be accountable for the definitions and the stewardship across functions, with the authority to settle a KPI dispute. Where that role is missing, the Fractional CDO model fills it: embedded senior data leadership a few days a week, owning the foundation without a full-time hire.
The second failure is treating governance as a one-off project. Equipment hierarchies drift as lines are added, KPI definitions get quietly reinterpreted, new source systems appear. Governance that is not maintained decays within a year. It has to be a standing responsibility wired into how the data platform is run, not a binder produced once and shelved.
And the honest limit: governance cannot fix a culture that does not want an honest number. If a plant is rewarded for a green OEE slide, the definitions will bend no matter how clean the lineage is. The technology surfaces the gaming; leadership has to decide it wants the real figure.
It isn't a reporting issue. It's a governance issue wearing a BI costume.
The Governance Operating Model That Actually Holds
Governance that survives contact with a working plant is light, not bureaucratic. Three roles carry it. A data steward per domain — operations for availability, quality for rejects, maintenance for the CMMS feed — owns the definitions for their area. A small cross-functional forum settles the composite metrics that span domains, OEE chief among them. And a single accountable owner, often the Fractional CDO, holds the equipment hierarchy and the change control on definitions so they cannot drift silently. That is the whole structure; anything heavier gets ignored on a shift.
The tooling makes the structure enforceable rather than aspirational. On Microsoft Fabric, lineage and a catalogue (Microsoft Purview over OneLake) show exactly which PLC tag and which work order produced a number, sensitivity labels control who sees which plant, and the Power BI semantic model is the contract everyone reads from. When a definition changes, it changes in one place and propagates — no more six versions of OEE drifting apart across reports.
The cadence is what keeps it alive. New lines and new source systems get onboarded against the existing hierarchy, not bolted on with their own codes. KPI definitions are reviewed on a fixed cycle rather than quietly reinterpreted. This is unglamorous discipline, but it is the difference between a manufacturing analytics estate that compounds and one that decays back into spreadsheets within a year.
Done this way, governance stops being the thing that slows analytics down and becomes the thing that lets it speed up — because every new dashboard, and eventually every predictive analytics model, inherits a trusted definition instead of re-litigating it. The foundation is built once and reused, not rebuilt per project.
What Changes for the Operations Leader
The payoff of governance is not a tidier data model. It is that the operations director can open a dashboard at 7am and act on it without first asking whether the number is real. Trust is the entire return — an analytics estate that people act on, rather than one they quietly work around with their own spreadsheet.
And it does not require an 18-month programme to begin. A six-week Discover and Foundation build can establish the equipment hierarchy, the agreed definitions, and a governed Power BI model on real data — first value in 6 weeks, not a 50-slide roadmap. The governance scope then expands with the analytics, rather than blocking it at the start.
Most operations leaders already suspect their numbers disagree across functions. The governed foundation is what turns that suspicion into one number with the lineage attached — and that single change is usually worth more than the next analytics tool on the shortlist.
I've seen organisations with exceptional technology and unusable analytics because nobody agreed on what 'OEE' meant across sites. And I've seen organisations with modest tools and disciplined data governance producing analytics that actually drive decisions. The governance comes first. Everything else follows.
Free Assessment
Where does your operation sit on the data maturity curve?
8 questions. 3 minutes. You get a scored breakdown across data infrastructure, analytics readiness, and automation potential — with a specific next step for your industry.