Access Official Technical PDF

Share Summary:LinkedInEmail

Supply chain data governance gives organizations a disciplined way to define, manage and monitor the information used across operational processes. As supply chains become more connected and digital, inconsistent or poorly understood data can undermine process standardization, automation, planning and decision-making. The experience shared by Corning Optical Communications offers a practical lesson: begin with a focused business problem, establish clear ownership and build the governance program as results emerge.

Why supply chain data governance matters

Supply chains are becoming more horizontal, with organizations needing to communicate across a wider network. At the same time, digitalization increases the speed at which customer demand and related information must move through business processes. Standardization is also important: consistent processes make it easier to coordinate work and support automation.

These trends make dependable data a strategic asset. A product, customer or material record may be used by multiple teams and processes. If its meaning, ownership or values differ across the organization, people can lose confidence in the information and processes may break down. Data quality is therefore not simply a technical concern. It means data is fit for its intended use in operations, decision-making and planning.

A governance program helps address this challenge by creating a common language, defining who is accountable for data and processes, and establishing global standards. The intended business outcomes include greater confidence in data, better management of cost and complexity, support for risk management and compliance, and increased business value.

Build governance around people, process and policy

Technology can support governance, but it is only one part of the operating model. The approach described for Corning Optical Communications included strategy, organizational roles, policies and standards, measurement and monitoring, technology, and communication. These elements connect governance decisions to the daily work of the people who create and use data.

Corning described its model as a virtual, cross-functional organization rather than a separate team operating in isolation. Business-area leads from functions such as product development, commercial operations, supply chain, procurement and finance worked alongside IT, program management and change management. Data domain stewards represented global or regional work streams, while end users brought operational experience from daily use.

This structure supports both operational and tactical work. Users can surface issues and process breakdowns; stewards and cross-functional leaders can consider their wider impact, clarify policy and determine practical ways to address them. Clear roles matter because data is touched by multiple people and processes. Without ownership, business rules and agreed definitions, it is difficult to maintain consistent data content.

Start with a bounded data quality problem

A large-scale governance initiative can be difficult to launch if its scope is too broad. Corning’s key advice was not to “boil the ocean”: start with pain points that cause business process breakdowns, document them and use available tools where possible. A bounded effort gives teams a concrete issue to investigate and a way to demonstrate value before expanding the program.

A repeatable data quality workflow can help structure that work:

  1. Identify the data issue and the process affected by it.
  2. Define the relevant business terms, ownership and acceptable values.
  3. Cleanse records that do not meet the agreed requirements.
  4. Document definitions, decisions and rules so they can be understood and reused.
  5. Enforce business rules to detect when data falls outside acceptable limits.

Rules turn expectations into something teams can monitor. They can help identify exceptions and make the quality standard explicit, rather than leaving users to interpret records differently. Monitoring also makes it possible to see whether data remains within the agreed specification over time.

Use metadata and rules to create shared understanding

In the Corning example, SAP Information Steward was used to provide visibility into critical data and to assess, measure and report on ERP data quality. The presentation also described using SAP Data Services alongside Information Steward. These tools supported governance activities, but the underlying goal was broader than deploying software: make data definitions and quality expectations visible to the people responsible for them.

A business glossary can help establish that shared understanding. Corning used Information Steward’s Metapedia to organize definitions for SAP fields and common business terminology. Business users could contribute content, helping connect technical field names with the language used in business operations. A term such as “Delivery Plant,” for example, could be documented with its SAP field name and location, data owner, definition and a link to the relevant rule.

This kind of documentation helps users understand what a field means, where it is used and who is responsible for it. It also gives stewards a reference point when reviewing a data issue or deciding whether a rule needs attention.

Standardize customer data and demonstrate value

One example in the presentation involved rules used to identify and maintain nonstandard customer classifications. The work was associated with reported labor savings of $150,000 over four weeks. This illustrates how a focused data quality effort can connect governance to a specific operational outcome. It is not a universal forecast; the value of a similar initiative will depend on the organization, the problem and the work required.

For system integrators and operations leaders, the practical takeaway is to select an issue that is both meaningful to the business and feasible to address. Define the classification or data standard, identify the owners, document the rule, and determine how exceptions will be handled. Then share the outcome with stakeholders to build support for the next step.

Make governance an ongoing journey

Information excellence is not a one-time cleanup. Organizations may need to profile data, catalog metadata, discover quality problems, establish standards and monitor results, then extend stewardship as business needs evolve. The presentation framed this as a progression: assess and remediate quality issues, establish governed maintenance processes, and extend governance across the enterprise and newer data sources.

The practical implication is to treat supply chain data governance as an operating discipline, not a standalone technology project. Begin with a clearly defined process problem, assign cross-functional ownership, establish shared definitions and enforceable rules, and measure progress. By using results to earn buy-in, organizations can grow governance in manageable steps while improving confidence in the data that supports supply chain operations.

Access Official Technical PDF

About The Author