🎓 Lesson 14
D5
Defining BOM Data Ownership & Accountability
BOM data ownership means clearly identifying who is responsible for creating, updating, and verifying each piece of information in the Bill of Materials.
🎯 Learning Objectives
- ✓ Explain the difference between data ownership, stewardship, and custodianship using mining equipment BOM examples
- ✓ Apply RACI matrices to assign ownership for critical BOM fields (e.g., explosive type, detonator delay, confinement rating)
- ✓ Analyze a real-world BOM governance failure case to identify root causes linked to undefined ownership
- ✓ Design a role-based BOM ownership policy aligned with ISO 8000-115 and MSHA Part 46 requirements
📖 Why This Matters
In mining blasting operations, a single incorrect BOM entry—such as misassigning a non-MSHA-approved detonator model or misstating emulsion density—can trigger catastrophic safety failures, regulatory penalties, or production delays. Unlike generic manufacturing, mining BOMs integrate geotechnical, explosive, and equipment data across contractors, OEMs, and site engineers—making ambiguous ownership the #1 cause of data drift in blast design systems. This lesson equips you to prevent that.
📘 Core Principles
Data ownership in BOM management rests on three pillars: (1) Role-based accountability—not organizational silos; (2) Attribute-level granularity—not blanket 'engineering owns all BOMs'; and (3) Lifecycle alignment—ownership shifts across design, procurement, field deployment, and post-blast verification. In blasting contexts, ownership must map to legal responsibility under MSHA regulations and contractual obligations (e.g., OEM warranty scope vs. contractor field verification). Governance frameworks like ISO 8000-115 require documented ownership for every data element subject to quality claims—especially for safety-critical parameters like explosive ANFO ratio or stemming column height.
📐 Ownership Clarity Index (OCI)
The Ownership Clarity Index quantifies how well-defined ownership is for a given BOM attribute. A value < 0.7 signals high risk of data conflict or delay. It is calculated per attribute and aggregated for critical subsystems (e.g., initiation network BOM).
Ownership Clarity Index (OCI)
OCI = Nₐ / NₜMeasures the proportion of BOM attributes with unambiguous, documented, and non-conflicting Accountable (A) role assignment.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| Nₐ | Number of attributes with valid Accountable assignment | unitless count | Attributes where exactly one role is designated 'A' in RACI, documented, and approved |
| Nₜ | Total number of BOM attributes in scope | unitless count | All fields subject to data quality governance (e.g., part ID, spec, supplier, revision, safety rating) |
Typical Ranges:
High-integrity blasting BOMs (ISO 8000-certified): 0.90 - 1.00
Legacy mine ERP BOMs: 0.40 - 0.65
💡 Worked Example
Problem: A surface mine’s blast initiation BOM contains 12 attributes (e.g., detonator model, delay interval, voltage rating). For 9 attributes, RACI assignments are documented and signed off by stakeholders; 2 lack accountable owners; 1 has conflicting RACI entries (both Blasting Engineer and Procurement Manager marked 'A').
1.
Step 1: Count total attributes = 12
2.
Step 2: Count attributes with unambiguous, documented, non-conflicting 'A' (Accountable) assignment = 9
3.
Step 3: Calculate OCI = 9 / 12 = 0.75
Answer:
The result is 0.75, which falls within the acceptable range of ≥0.70. However, the one conflicting assignment requires immediate resolution to avoid future approval bottlenecks.
🏗️ Real-World Application
At the Grasberg copper mine (Indonesia), a 2022 incident involved misfired holes due to outdated detonator firmware versions listed in the BOM. Investigation revealed no assigned owner for 'firmware revision' field—Procurement updated hardware part numbers, but Automation Engineering owned firmware validation and never synchronized updates into the BOM. Post-incident, Freeport-McMoRan implemented attribute-level RACI mapping for all digital twin-integrated BOMs, assigning firmware revision ownership exclusively to the Mine Automation Team with mandatory biweekly reconciliation against OEM bulletins.