Master Data and Interface Governance — The Foundation of a Digital Quality System
1. Disorganized Master Data, Disorganized Quality System
Typical conversation:
- Quality Department: "The inspection plan version is incorrect."
- IT: "The BOM in ERP was just updated yesterday."
- Production: "The process route in MES is still from last week."
- Laboratory: "The sample name in LIMS doesn't match the customer's terminology."
Four systems, four versions — when the auditor asks, "Which one is the effective version?" no one can answer within a minute. This is the daily cost of master data (Master Data) and interface governance failures.
In a digital quality system, master data serves as the foundation of the "single source of truth"; interfaces are the blood vessels that transmit facts between systems. If the foundation is skewed or the blood vessels are blocked, the QMS, MES, SPC, and supplier portal will become expensive silos.
2. Quality-Related Master Data: Scope and Owner
| Master Data Object | Typical Content | Suggested Owner | Role of Quality Department |
|---|---|---|---|
| Material / Part Number | Raw materials, semi-finished products, finished products, customer-supplied parts | Supply Chain / Engineering | Define quality attributes, inspection types |
| BOM | Parent-child components, quantities, substitute materials | Engineering / Manufacturing Engineering | ECN effectiveness, breakpoints |
| Process Route / Operation | Sequence of operations, work centers | Manufacturing Engineering | Control plan, special characteristic associations |
| Inspection Plan / Specification | Items, sampling, limits | Quality | Primary maintenance |
| Customer / Supplier | Codes, qualifications, requirements | Sales / Procurement | Admission, special requirements |
| Equipment / Measuring Tools | Numbers, calibration cycles, capabilities | Equipment / Metrology | MSA, inspection associations |
| Personnel Authorization | Positions, operations, approval authorities | Quality + HR | Primary or joint responsibility |
Golden Rule: Each master data object has and only has one Data Owner; other departments consume (Consumer) rather than privately modify copies.
3. Master Data Governance: Five Gates
3.1 Creation Gate
- New part numbers, new operations, new inspection items — must have an application form + approval flow
- Prohibit "using temporary codes in production first, then updating later"; if business requires, temporary codes validity ≤ 30 days and automatic alerts
3.2 Change Gate
- Linked with ECN: BOM, process, and inspection plan changes must not bypass the change procedure
- Three key elements of effective date + breakpoint: when it takes effect, how to handle work-in-progress, and when the old version is retired
3.3 Quality Gate
Example of a pre-release checklist:
- Have special characteristics been identified and associated with CP/FMEA?
- Is the inspection plan consistent with the latest customer specifications?
- Are there equivalent substitute materials that need to be updated simultaneously?
3.4 Distribution Gate
- The Owner system writes once, downstream systems subscribe and receive — prohibit manual Excel transfers
- Distribution log: who, when, and which version received
3.5 Retirement Gate
- Part numbers, suppliers, and old specifications — change status to Inactive, preventing new orders from referencing them
- Historical records are retained in read-only format to meet traceability and audit requirements
4. Interface Governance: From "Point-to-Point" to "Manageable and Auditable"
4.1 Interface Inventory
Each interface should at least record:
| Field | Example |
|---|---|
| Interface ID | IF-ERP-MES-001 |
| Source / Target | ERP → MES |
| Data Object | BOM, process route |
| Frequency | Real-time / Hourly / Batch |
| Trigger | ECN effectiveness, order release |
| Exception Handling | Retry, alert, manual queue |
| Business Owner | Manufacturing IT + Quality |
| Last Verification Date | CSV/OQ record |
4.2 Integration Mode Selection
| Mode | Applicable | Note |
|---|---|---|
| Master-Slave Replication | BOM, process issued once | Version conflict detection |
| Event-Driven | ECN effectiveness, inspection completion | Message loss monitoring |
| Query API | QMS pulls ERP orders | Performance and permissions |
| File Batch Processing | Legacy systems | Most prone to errors, plan for retirement |
Quality Focus: Inspection results, release status, deviation status — prioritize event-driven + audit trail to avoid overnight batch processing leading to "released yesterday but shown in the system today."
4.3 Exception and Reconciliation
- Dead Letter Queue: Failed messages must not be silently lost
- Daily Reconciliation: ERP released orders vs MES received; QMS inspected vs ERP inventory status
- Difference SLA: Must be claimed and handled within 24 hours
5. Version and Consistency: The Three Most Common Questions from Auditors
"Please show the BOM version in effect for this batch production." → There should be a time-point version (As-built BOM) or production snapshot, not just the "current latest version"
"Which version of the specification was the inspection based on?" → Inspection records must reference the specification version number and be consistent with the version provided to the customer
"Is the system consistent with the site?" → Sampling comparison: MES operation parameters vs on-site PLC/paper; QMS sampling vs actual samples
As-built / As-tested records are the crown jewels of master data governance — many disputes are not about "whether it is correct now," but "whether it was correct at the time."
6. Organization and Process: Who Meets, What to Discuss
It is recommended that the Master Data Governance Committee (MDM Steering) meet once a month for 30-60 minutes:
- Approval of new master data object types
- Review of major interface changes
- Clearing open issues (Open Issues)
- KPI review: interface failure rate, reconciliation differences, number of temporary codes
The Quality Department should permanently attend — this is not just an "IT matter."
7. Intersections with CSV, Security, and Permissions
- Computerized System Validation (CSV): Interface changes = change control, requiring impact assessment and re-validation
- Permissions: Who can modify the BOM in ERP? Who can change inspection limits in QMS? Consistent with the position authorization matrix
- Audit Trail: Master data changes must be traceable (old value, new value, person, time, reason)
8. Common Failure Modes
| Phenomenon | Root Cause | Countermeasure |
|---|---|---|
| Dual BOM: Excel vs ERP | No single Owner | Disable unauthorized copies, Excel read-only export |
| Occasional interface message loss | No monitoring | Reconciliation + alerts + Runbook |
| Inspection plans always lag behind | ECN and QMS not linked | ECN effectiveness automatically triggers inspection plan revision tasks |
| Three different ways to write customer names | Customer master data not unified | Golden record + alias table |
| No one understands interfaces after implementation consultant leaves | Lack of documentation | Interface inventory + architecture diagram in knowledge base |
9. 90-Day Improvement Path
| Week | Action |
|---|---|
| 1～2 | Inventory quality-related master data objects, designate Owners, publish RACI |
| 3～4 | Establish interface inventory v1.0; select one key interface (e.g., BOM→MES) for end-to-end mapping |
| 5～8 | Initiate daily reconciliation (at least orders + inspection status); close the top 3 root causes of differences |
| 9～12 | Improve ECN and inspection plan linkage; conduct a "time-point version" traceability drill |
10. KPI Suggestions
- Percentage of NCRs / deviations related to master data (trend should decrease)
- Number of interface failures and average recovery time
- Number and age of open reconciliation differences
- Number of temporary part numbers / temporary processes
- Number of "version inconsistency" observations during audits
11. Implementation Toolkit (Ready to Use)
It is recommended to maintain the following templates in the QMS or IT knowledge base to reduce cross-departmental collaboration costs:
- Master Data RACI Matrix: Fill in Owner, Approver, and Consumer for materials, BOM, processes, inspection plans, customers, and suppliers
- Master Data Change Application Form: Includes ECN number, breakpoint explanation, work-in-progress handling, and downstream system confirmation
- Interface Runbook: One page per key interface — failure alert contact, rerun steps, temporary manual business solutions (for emergencies only)
- Monthly Reconciliation Report Template: Categorize differences (master data errors / interface delays / business non-compliance)
- New System Launch Checklist: Before launch, complete "master data migration verification + interface parallel reconciliation ≥ 1 complete cycle"
The Quality Department can reference these templates in supplier admission, NPI phase gates, and internal audit plans to transform master data governance from an "IT project" into a routine discipline across the entire value chain.
Master data and interface governance may sound like IT topics, but they are the prerequisites for the credibility of the quality evidence chain. Strengthening the foundation ensures that digital quality reconstruction (see knowledge code 12.3.2) does not turn into "two sets of evidence after system implementation."
Simplified Inspection with a Single Source of Truth: For the same part number, are the name, version, and critical limits aligned to a single version number at any given time in ERP, MES, QMS, inspection reports, and packaging labels?
Knowledge code: 12.3.2
Version: v20260630
Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management professionals, helping enterprises continuously improve their quality capabilities.