Master Data (MDM) Tower
Capability MDM-140 · MDM Manage Master Data
IAO Program · R1 – R5
Generated: May 2026
Sajiv Francis
IAO Architecture Pipeline — Intel Confidential
This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for MDM-140 Maintain ERP Reference Data within the IAO program.
| Dimension | Value |
|---|---|
| Tower | Master Data (MDM) |
| Process Group | MDM Manage Master Data |
| Capability | MDM-140 - Maintain ERP Reference Data |
| Release | R1 – R5 |
| Total Systems | 0 |
| System Status | 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM |
| RICEFW Objects | 8 Enhancements, 1 Workflows |
System nodes in architecture diagrams are IAPM-linked where matches exist (0/0 matched) — click any linked node to open its IAPM page. Diagrams require
securityLevel: 'loose'for click events.
| Level | Value |
|---|---|
| L0 Tower | Master Data |
| L1 Process | MDM Manage Master Data |
| L2 Capability | MDM-140 - Maintain ERP Reference Data |
| # | Driver | Description | Strategic Alignment | Priority |
|---|---|---|---|---|
| 1 | Master Data Governance | Establish single source of truth for vendor, customer, material, and BOM master data | IDM 2.0 Data Foundation | High |
| 2 | Data Quality Improvement | Implement data quality rules and automated validation for master data creation and changes | Data Governance | High |
| 3 | Cross-System Data Synchronization | Ensure master data consistency across S/4 HANA, MDG, and downstream systems | Enterprise Integration | Medium |
| 4 | MDM-140 Process Migration | Migrate Maintain ERP Reference Data business processes and 0 integrated systems from legacy to S/4 HANA target architecture | IDM 2.0 Master Data | High |
| Metric | Target | Measure | Baseline | Owner |
|---|---|---|---|---|
| Master Data Accuracy | > 99% | Master data records passing automated quality validation rules | 94% (current) | Data Governance Lead |
| Data Creation Lead Time | < 4 hours | Vendor/customer/material master data creation cycle time | 2 business days (current) | MDM Operations |
| Data Sync Latency | < 15 minutes | Time for master data changes to propagate to all consuming systems | 4 hours (batch) | Integration Lead |
| MDM-140 Migration Completeness | 100% flow chains validated | All 0 flow chains verified in target state | 0% (pre-migration) | Tower Architect |
| Document | Description |
|---|---|
| Business Architecture | Included in this document (Section 3) — process flows from BPMN diagrams |
| This Document | Full BDAT Architecture — Business + Data + Application + Technology |
(No BPMN files found in input/bpmn/ for this capability.)
Business roles and responsibilities will be derived from BPMN swim lane assignments when process models are available.
Process readiness for MDM-140 — Maintain ERP Reference Data with automated risk flags from Config Tracker, User Story Tracker, RICEFW Object Tracker, ECA Object Tracker.
| L2 | Description | L3 In-Scope | Config | User Stories | RICEFW | ECA | Status |
|---|---|---|---|---|---|---|---|
| MDM-140 | Maintain ERP Reference Data | 34/34 | 96% (27/28) | 0F/0G/0 | 9/9 | — | 🟢 |
📄 Full Process Readiness Detail → — per-capability breakdown with config items, RICEFW objects, transport analysis, and QA verification. For the comprehensive L1/L0 readiness rollup across all capabilities, see the L0 Tower Summary.
Data Sources: Config Tracker, User Story Tracker, S4 R3 Object Tracker, ECA R3 Object Tracker (Smartsheet exports). RICEFW and ECA objects are matched via Sub-Tower Name → L2 mapping. Generated .
Data flows with DB platform details will be populated when tower architects complete the extended flow template columns (42-47) via the Input Portal.
DATA ARCHITECTURE — Database-to-database data flows. Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.
Data lineage (source schema/object → target schema/object mappings) will be populated when tower architects provide validated schema details via the Input Portal.
RICEFW data objects (Reports and Conversions) will be auto-populated from the Smartsheet Object Tracker when matched to this capability.
Standard governance framework per Intel IDM 2.0 data management policies. Capability-specific governance details will be populated from the Input Portal when tower architects complete the Data Governance tab.
| Concern | Approach |
|---|---|
| Data Ownership | Per-entity owners aligned to Master Data tower organizational structure |
| Data Classification | Per Intel corporate data classification policies |
| Data Retention | Per Intel corporate retention policies |
| Data Quality | Validated at source; reconciliation at target |
| System | IAPM ID | Status |
|---|---|---|
Summary: 9 SAP | RICEFW: 8 Enhancements, 1 Workflows
SAP platform objects (Reports, Interfaces, Conversions, Enhancements, Forms, Workflows) developed on S/4, MDG, or S/4 BOT:
| Object ID | Type | Description | Status | Dev System | Complexity |
|---|---|---|---|---|---|
| MDCE0015 | Enhancement | Asset Location - Extended Itego datamodel with 22 custom fields + UI to suppo… | 10. Object Complete | 02.MDG | 03.Medium |
| MDCE0014 | Enhancement | Storage Location - Extended Itego datamodel with 11 custom fields + UI to sup… | 10. Object Complete | 02.MDG | 03.Medium |
| MDCE0013 | Enhancement | Plant - Extended Itego datamodel with 13 custom fields + UI to support govern… | 10. Object Complete | 02.MDG | 03.Medium |
| MDCE0012 | Enhancement | Sales Org Association - Custom Itego Object with 4 customer fields + UI to su… | 10. Object Complete | 02.MDG | 03.Medium |
| MDCE0011 | Enhancement | Holiday Calendar - Custom goveranance | 10. Object Complete | 02.MDG | 03.Medium |
| MDCE0009 | Enhancement | Shipping Point- Custom Itego Object with 6 customer fields + UI to support go… | 10. Object Complete | 02.MDG | 03.Medium |
| DATW0591 | Workflow | Parallel Approver Workflow Process | 10. Object Complete | 02.MDG | 03.Medium |
| DATE0799 | Enhancement | RICEFW for Validations and Derivations where enhancement required for all ref… | 10. Object Complete | 02.MDG | 03.Medium |
| DATE0561 | Enhancement | Adding DQM Functionality for Address validation | 10. Object Complete | 02.MDG | 01.Very High |
This section provides a holistic view of all batch processing and job scheduling — both internal SAP background jobs (SM37) and external orchestration (AutoSys, CWA).
External scheduling data is not yet available. Pending either AutoSys API access or a JIL export to the External Job Scheduling Tracker.
Scheduling and batch job data will be auto-populated once SAP background job extraction (TBTCO/TBTCP via ADT) is run against the development systems and AutoSys metadata is available. Run python scripts/fetch_sap_background_jobs.py to extract SAP internal jobs.
Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.
TECHNOLOGY / PLATFORM ARCHITECTURE — Platforms (green) host applications (blue). Thick arrows show platform-to-platform integration flows.
Platform inventory will be populated when tower architects provide validated technology platform details via the extended flow template.
| Metric | DEV | QAS | PRD |
|---|---|---|---|
| Transport Requests | — | — | — |
| Custom Code Objects | — | — | — |
| CDS Views | — | — | — |
| Fiori Apps | — | — | — |
| BAdIs / Enhancements | — | — | — |
| Category | Requirement | Target / SLA | Priority |
|---|---|---|---|
| Performance | Master data creation and validation within user expectation | < 5 seconds for save/validate | High |
| Availability | MDM systems available during global business hours | 99.9% (follows-the-sun) | High |
| Scalability | Support master data volume growth from new entities | Handle 5M+ master records | Medium |
| Recoverability | Master data systems recover with data integrity guaranteed | RPO = 0 (no data loss), RTO < 2 hours | High |
| Data Volume | Support comprehensive master data model across domains | 500K+ active material masters | Medium |
| Latency | Master data changes propagate to consuming systems promptly | < 15 minutes replication latency | High |
| Concurrency | Support centralized MDM team plus distributed maintainers | 100+ concurrent MDM users | Medium |
| Concern | Approach | Standard / Policy | Owner |
|---|---|---|---|
| Authentication | Single Sign-On (SSO) via Intel corporate Azure AD identity | Intel IT Security Policy - Identity Management | IT Security |
| Authorization | Role-based access control (RBAC) with SAP authorization objects | Intel SAP Security Standards - Role Design | SAP Security Team |
| Data Classification | All financial/operational data classified per Intel Data Classification Standard | Intel Data Classification Policy | Data Governance |
| Data Encryption (at rest) | AES-256 encryption for SAP HANA database and file storage | Intel Encryption Standard | Infrastructure Security |
| Data Encryption (in transit) | TLS 1.3 for all system-to-system and user-to-system communication | Intel Network Security Policy | Network Engineering |
| Network Segmentation | SAP systems in dedicated network zones with firewall controls | Intel Network Architecture Standard | Network Security |
| API Security | OAuth 2.0 / certificate-based authentication for all API integrations | Intel API Security Guidelines | Integration Architecture |
| Audit Logging | Comprehensive audit trail for all data changes and user actions (SAP Security Audit Log) | SOX Compliance / Intel Audit Policy | Internal Audit |
| Certificate Management | Automated certificate lifecycle management for system-to-system trust | Intel PKI Standard | Certificate Authority Team |
| Compliance | SOX controls, export control (EAR/ITAR) screening, data privacy (GDPR) | Intel Corporate Compliance Framework | Compliance Office |
No ECA objects mapped to this capability. The ECA tracker L2/L3 Process columns are empty — objects are mapped via Sub-Tower Name. If ECA objects exist for this capability but are not shown, verify the Sub-Tower → L2 mapping in subtower_capability_map.json.
| ID | Description | FS | TDD | Build | FUT | Status |
|---|---|---|---|---|---|---|
| MDCE0015 | Asset Location - Extended Itego datamodel with 22 custom fields + UI to suppo… | 2024-10-25 00:00:00 (100%) | 2024-11-08 00:00:00 (100%) | 2025-02-07 00:00:00 (100%) | 2025-02-21 00:00:00 (100%) | |
| MDCE0014 | Storage Location - Extended Itego datamodel with 11 custom fields + UI to sup… | 2024-10-11 00:00:00 (100%) | 2024-10-25 00:00:00 (100%) | 2024-11-08 00:00:00 (100%) | 2024-11-15 00:00:00 (100%) | |
| MDCE0013 | Plant - Extended Itego datamodel with 13 custom fields + UI to support govern… | 2024-10-11 00:00:00 (100%) | 2024-10-25 00:00:00 (100%) | 2024-11-08 00:00:00 (100%) | 2024-11-15 00:00:00 (100%) | |
| MDCE0012 | Sales Org Association - Custom Itego Object with 4 customer fields + UI to su… | 2024-09-27 00:00:00 (100%) | 2024-10-11 00:00:00 (100%) | 2024-10-25 00:00:00 (100%) | 2024-11-01 00:00:00 (100%) | |
| MDCE0011 | Holiday Calendar - Custom goveranance | 2024-09-13 00:00:00 (100%) | 2024-09-20 00:00:00 (100%) | 2024-10-11 00:00:00 (100%) | 2024-10-18 00:00:00 (100%) | |
| MDCE0009 | Shipping Point- Custom Itego Object with 6 customer fields + UI to support go… | 2024-10-11 00:00:00 (100%) | 2024-10-25 00:00:00 (100%) | 2024-11-15 00:00:00 (100%) | 2024-11-22 00:00:00 (100%) | |
| DATW0591 | Parallel Approver Workflow Process | 2024-10-18 00:00:00 (100%) | 2024-11-15 00:00:00 (100%) | 2024-11-15 00:00:00 (100%) | 2025-05-02 00:00:00 (100%) | |
| DATE0799 | RICEFW for Validations and Derivations where enhancement required for all ref… | 2024-12-13 00:00:00 (100%) | 2025-03-21 00:00:00 (100%) | 2025-03-21 00:00:00 (100%) | 2025-06-11 00:00:00 (100%) | 3. Off Track |
| DATE0561 | Adding DQM Functionality for Address validation | 2024-11-15 00:00:00 (100%) | 2025-04-18 00:00:00 (100%) | 2025-04-18 00:00:00 (100%) | 2025-05-30 00:00:00 (100%) |
RAID items will be auto-populated from the Smartsheet RAID log when matched to this capability.
| # | Category | Recommendation | Priority | Owner | Target Date | Status |
|---|---|---|---|---|---|---|
| 1 | Architecture | Complete extended flow attributes (Data Entity, Integration Pattern, Tech Platform) in Flows tab for full BDAT coverage | High | Tower Architect | 2026-Q2 | Open |
| 2 | Data | Define data ownership and classification for all 0 flow chains to satisfy Data Architecture (TOGAF D) requirements | Medium | Data Architect | 2026-Q3 | Open |
| 3 | Testing | Develop integration test scenarios covering all 0 flow chains for FUT/SIT readiness | High | Test Lead | 2026-Q3 | Open |
| 4 | Business Architecture | Review and validate Business Architecture process steps against latest Signavio/BIC process models | Medium | Business Analyst | 2026-Q2 | Open |
| 5 | Security | Complete security review for API integrations and data flows per Intel Security Architecture standards | Medium | Security Architect | 2026-Q3 | Open |
MDM-140 — Architecture Document (TOGAF BDAT) · Master Data · Generated: May 2026