π Lesson 16
D5
MES/ERP Cost Data Architecture Principles
MES/ERP cost data architecture is the organized blueprint that connects real-time production data (like drilling, blasting, and hauling) to accurate, traceable cost records in mining software.
π― Learning Objectives
- β Explain how cost object hierarchies (e.g., mine β pit β bench β blast round) enable drill-down cost analysis
- β Design a traceable data flow from blast initiation sensor logs to ERP cost postings using MES event triggers
- β Analyze discrepancies between real-time MES labor hours and ERP payroll allocations using reconciliation logic
- β Apply master data governance rules to ensure consistent equipment ID, material code, and activity type definitions across MES and ERP systems
π Why This Matters
In modern surface mines, a $2M blast misfire or 15% overestimation in waste haulage cost can erode margin before finance closes the month. Without robust MES/ERP cost data architecture, engineers rely on lagging, aggregated reports β making it impossible to optimize blast design, validate contractor invoices, or allocate maintenance spend to specific ore zones. This architecture is the nervous system linking field sensors to boardroom decisions.
π Core Principles
Cost data architecture rests on four interdependent pillars: (1) Master Data Consistency β shared definitions of assets, materials, activities, and locations across MES and ERP; (2) Event-Driven Cost Capture β triggering cost postings from discrete operational events (e.g., blast completion signal, truck dump confirmation); (3) Hierarchical Cost Object Modeling β structuring cost collection along geological (bench, zone), operational (shift, round), and asset (shovel #S12, drill rig #D7) dimensions; and (4) Traceability & Auditability β preserving lineage from raw sensor timestamp β MES transaction β ERP journal entry, with immutable metadata (operator ID, GPS coordinates, calibration status). Deviations in any pillar break cost fidelity.
π Cost Allocation Traceability Index (CATI)
CATI quantifies the completeness and consistency of cost attribution across systems. A CATI < 0.85 signals high risk of unallocated or double-counted costs β requiring master data or interface remediation.
Cost Allocation Traceability Index (CATI)
CATI = N_traceable / N_matchedMeasures the proportion of ERP cost postings that are fully traceable to source MES events with complete metadata.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| N_traceable | Number of fully traceable cost postings | count | ERP postings linked to MES event + all required metadata (operator, timestamp, equipment ID, geotechnical classification) |
| N_matched | Number of matched events | count | Minimum of total MES events and ERP cost postings for the same scope (e.g., shift, bench) |
Typical Ranges:
Tier-1 integrated mine: 0.92 - 0.98
Legacy system with manual interfaces: 0.55 - 0.78
π‘ Worked Example
Problem: A copper mineβs MES logs 1,247 blast round events in Q3. ERP shows 1,189 corresponding cost postings to 'Bench 12-Alpha' cost center. Of those, 1,162 include full traceability metadata (drill ID, powder factor, geotech rating). 27 lack geotech rating; 58 have no matching MES event.
1.
Step 1: Calculate matched events = min(MES events, ERP postings) = min(1247, 1189) = 1189
2.
Step 2: Calculate fully traceable events = 1162
3.
Step 3: CATI = Fully traceable / Matched events = 1162 / 1189 = 0.977
Answer:
The CATI is 0.977, which exceeds the industry target of β₯0.95 and indicates strong traceability performance.
ποΈ Real-World Application
At Newmontβs Boddington Mine (WA), integration of iField MES with SAP S/4HANA enabled real-time allocation of explosive costs per blast round using RFID-tagged emulsion tanks, GPS-tracked delivery trucks, and blast initiation timestamps. When a 2023 software patch mismatched 'Round ID' formats between MES and ERP, CATI dropped from 0.96 to 0.71 β revealing $1.4M in unallocated explosive spend over 11 days. Root cause was missing leading zeros in round identifiers; fixed via automated data cleansing rule in the middleware layer.
βοΈ Data Reconciliation Exercise
You are given: MES recorded 892 shovel loading cycles on Bench 7-West during Shift B; ERP posted labor costs for 874 cycles to cost center 'PIT-7W-LABOR'. Of the 874, 851 include operator ID and cycle time; 23 lack operator ID. Shovel telemetry shows 889 valid cycles (excluding <15s partial loads). Calculate CATI and identify the dominant gap category (matching, traceability, or completeness). Propose one corrective action.