Welcome! I can answer questions about RICEFW objects, build readiness, architecture patterns, and towers across the IAO IDM 2.0 program. What would you like to know?
Phase 1 · GitHub Actions backend · ~30-60s response time
E2E-90 — R3 Material Master Data
Architecture Document (TOGAF BDAT)
End-to-End Integrated Processes (E2E) Tower
Capability E2E-90 · Master Data
IAO Program · R1 – R5
Generated: April 2026
Sajiv Francis
IAO Architecture Pipeline — Intel Confidential
Table of Contents
1. Executive Summary
This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for E2E-90 R3 Material Master Data within the IAO program. It includes 1 BPMN process diagram(s) in Section 3.
Dimension
Value
Tower
End-to-End Integrated Processes (E2E)
Process Group
Master Data
Capability
E2E-90 - R3 Material Master Data
Release
R1 – R5
Total Systems
2
System Status
0 Deployed, 0 Developing, 0 EOL, 2 Pending IAPM
RICEFW Objects
Pending — Smartsheet Object Tracker API integration
Change Summary: 0 new flow chains, 0 removed, 0 modified, 1 unchanged between Current-State and Future-State states.
All system nodes in architecture diagrams are IAPM-linked — click any node to open its IAPM page. Diagrams require securityLevel: 'loose' for click events.
2. Business Context & Objectives
2.1 Classification
Level
Value
L0 Tower
End-to-End Integrated Processes
L1 Process
Master Data
L2 Capability
E2E-90 - R3 Material Master Data
2.2 Business Drivers
#
Driver
Description
Strategic Alignment
Priority
1
End-to-End Process Integration
Enable cross-tower integrated processes spanning procurement, manufacturing, and fulfillment
IDM 2.0 Process Excellence
High
2
Intel Foundry Business Enablement
Stand up foundry-specific business processes for external customer engagement
Intel Foundry Services
High
3
Process Visibility & Monitoring
Provide end-to-end process visibility across tower boundaries with integrated monitoring
Operational Excellence
Medium
4
E2E-90 Process Migration
Migrate R3 Material Master Data business processes and 2 integrated systems from legacy to S/4 HANA target architecture
IDM 2.0 Cross-Functional / End-to-End
High
2.3 Success Criteria
Metric
Target
Measure
Baseline
Owner
E2E Process Cycle Time
Per process SLA
End-to-end transaction completion within defined SLA per process
Varies by process
E2E Process Owner
Cross-Tower Integration Success
> 99%
Transactions completing across tower boundaries without manual intervention
92% (current)
Integration Lead
Process Exception Rate
< 2%
Transactions requiring manual exception handling
8% (current)
Operations Manager
E2E-90 Migration Completeness
100% flow chains validated
All 1 flow chains verified in target state
0% (pre-migration)
Tower Architect
2.4 Companion Documents
Document
Description
Business Architecture
Included in this document (Section 3) — process flows from BPMN diagrams
This Document
Full BDAT Architecture — Business + Data + Application + Technology
3. Business Architecture (TOGAF “B”)
3.1 Business Process Overview
This capability includes 1 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for E2E-90 R3 Material Master Data.
SAP S/4, Intel Product
SAP S/4 , NEW SAP MDG, SAP CFIN | 16 | 6 |
3.2 Business Process Diagrams
BUSINESS ARCHITECTURE — 3.2.1 E2E-90_R3_Material_Master_Data — E2E-90_R3_Material_Master_Data
Swim Lanes: Boundary Apps · EWM Decentralized · GTS · Intel Foundry
SAP S/4 · Intel Product
SAP S/4 · NEW SAP MDG · SAP CFIN | Tasks: 16 | Gateways: 6
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%%
flowchart LR
classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20
classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20
classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1
classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C
classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100
classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C
subgraph lane_0["Boundary Apps"]
n1["Fetch IF related material data"]
n2["Update ENT. Hana System"]
n3["Update only legacy material number for IF and IP"]
n4["Update Other Boundary Application System"]
n5["Fetch IP related material data"]
n6["Update material data in ECC"]
n7["Update material details Translator"]
n8["Update material data to Speed via translator"]
n14["fa:fa-user Fetch PLM material related data from Speed"]
n17(["fa:fa-play Material Master Request received for PLM"])
n19(["fa:fa-stop Boundary App Updated"])
n20(["fa:fa-stop Material data sync complete"])
n26{{"fa:fa-code-branch Type of data, IP or IF?"}}
n27{{"fa:fa-code-branch exclusiveGateway"}}
n29{{"fa:fa-arrows-alt parallelGateway"}}
end
subgraph lane_1["EWM Decentralized"]
n12["Update Intel Product and Foundry"]
n24(["fa:fa-stop EWM Data Updated"])
end
subgraph lane_2["GTS"]
n13["Update Intel Foundry and Intel Product"]
n25(["fa:fa-stop GTS Data Updated"])
end
subgraph lane_3["Intel Foundry SAP S/4"]
n11["Update Intel Foundry"]
n23(["fa:fa-stop S/4 Updated"])
end
subgraph lane_4["Intel Product SAP S/4 "]
n10["Update Intel Prodcut"]
n22(["fa:fa-stop S/4 Updated"])
end
subgraph lane_5["NEW SAP MDG"]
n15["fa:fa-user Update New SAP MDG System"]
n16["fa:fa-user Request for Non-PLM related materials"]
n18(["fa:fa-play Material Master Request Received for Non-PLM"])
n28{{"fa:fa-code-branch exclusiveGateway"}}
n30{{"fa:fa-arrows-alt parallelGateway"}}
n31{{"fa:fa-arrows-alt parallelGateway"}}
end
subgraph lane_6["SAP CFIN"]
n9["Update in Intel Foundry and Intel Product"]
n21(["fa:fa-stop SAP CFIN Updated"])
end
n13 --> n25
n12 --> n24
n11 --> n23
n9 --> n21
n17 --> n14
n10 --> n22
n3 --> n29
n29 --> n4
n18 --> n16
n26 -->|"Intel Product (IP)"| n5
n26 -->|"Intel Foundry (IF)"| n1
n1 --> n27
n16 --> n28
n27 --> n28
n28 --> n15
n14 --> n26
n31 --> n10
n31 --> n11
n31 --> n12
n31 --> n13
n31 --> n9
n30 --> n31
n15 --> n30
n8 --> n20
n7 --> n6
n4 --> n19
n30 -->|"Legacy material number"| n3
n30 -->|"Legacy and
new material number"| n7
n2 --> n29
n5 --> n27
n6 -->|"Cluster 2 & 3"| n8
n30 -->|"Old MM ID number"| n2
class n14 userTask
class n15 userTask
class n16 userTask
class n17 startEvt
class n18 startEvt
class n19 endEvt
class n20 endEvt
class n21 endEvt
class n22 endEvt
class n23 endEvt
class n24 endEvt
class n25 endEvt
class n26 gateway
class n27 gateway
class n28 gateway
class n29 gateway
class n30 gateway
class n31 gateway
| NEW SAP MDG | E2E-90_R3_Material_Master_Data | |
| SAP CFIN | E2E-90_R3_Material_Master_Data | |
4. Data Architecture (TOGAF “D”)
4.1 Data Flows — Source to Target
#
Flow Chain
Hop
Source App
Source DB
Target App
Target DB
Data Description
Frequency
Classification
1
e.g. MES Route to ICOST
1
e.g. MES 300
e.g. SAP HANA
e.g. XEUS
e.g. Azure SQL
What data moves
e.g. Near Real-Time
e.g. Intel Confidential
4.2 Data Flow Diagrams
DATA ARCHITECTURE — Database-to-database data flows. Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.
4.2.1 Current-State — Current-State Data Flows
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "15px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 35, "rankSpacing": 45}} }%%
flowchart TB
classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbCyl fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
classDef dbCloud fill:#BBDEFB,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbData fill:#B2EBF2,stroke:#00838F,stroke-width:2px,color:#004D40
classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
subgraph E2E90CDACL_e_g_Azure_SQL[" "]
direction TB
E2E90CDAA_e_g_XEUS["e.g. XEUS"]:::appBox
E2E90CDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud
E2E90CDAA_e_g_XEUS -.-> E2E90CDAD_e_g_Azure_SQL
end
style E2E90CDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px
subgraph E2E90CDACL_e_g_SAP_HANA[" "]
direction TB
E2E90CDAA_e_g_MES_300["e.g. MES 300"]:::appBox
E2E90CDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData
E2E90CDAA_e_g_MES_300 -.-> E2E90CDAD_e_g_SAP_HANA
end
style E2E90CDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px
E2E90CDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E90CDAD_e_g_Azure_SQL
subgraph Legend["📐 DATA ARCHITECTURE LEGEND"]
direction LR
L_A["Application"]:::appBox
L_D[("🗄️ On-Prem DB")]:::dbCyl
L_DC[("🗄️ Cloud DB")]:::dbCloud
L_DD[("🗄️ Data Platform")]:::dbData
L_E["End-of-Life"]:::eolBox
end
style Legend fill:#F5F5F5,stroke:#999,stroke-width:1px
The Current-State architecture represents the current / legacy landscape for E2E-90.This view is generated from CurrentFlows.xlsx (1 flow hops across 1 flow chains).
APPLICATION ARCHITECTURE — Architecture Diagram
Click any system node to open its IAPM application page.
Legend: Deployed · Developing · End-of-Life · No IAPM Match
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "18px", "fontFamily": "Segoe UI, Arial, sans-serif"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 50, "rankSpacing": 60}} }%%
flowchart TB
%% -- ArchiMate 3.2 + Azure style classes --
classDef business fill:#FFFFB3,stroke:#F9A825,stroke-width:2px,color:#000
classDef app fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef data fill:#BBDEFB,stroke:#1565C0,stroke-width:1px,color:#0D47A1,stroke-dasharray: 5 5
classDef middleware fill:#FFE0B2,stroke:#E65100,stroke-width:2px,color:#BF360C
classDef eol fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
classDef saas fill:#E1BEE7,stroke:#7B1FA2,stroke-width:2px,color:#4A148C
classDef cloud fill:#BBDEFB,stroke:#1565C0,stroke-width:2px,color:#0D47A1
classDef onprem fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
subgraph E2E90CLN_Boundary_Applications[" Boundary Applications"]
direction LR
E2E90C_e_g_MES_300["📦 e.g. MES 300"]:::app
E2E90C_e_g_XEUS["📦 e.g. XEUS"]:::app
end
E2E90CMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware
E2E90CDE_e_g_Cost_Element>"📄 e.g. Cost Element e.g. CSV / IDoc / JSON"]:::data
E2E90C_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E90CMW_e_g_Azure_Service_Bus
E2E90CMW_e_g_Azure_Service_Bus --> E2E90C_e_g_XEUS
style E2E90CLN_Boundary_Applications fill:#E8F5E9,stroke:#388E3C,stroke-width:2px
subgraph Legend["📐 LEGEND"]
direction LR
L_APP["📦 Application"]:::app
L_MW["🔗 Middleware"]:::middleware
L_DE>"📄 Data Entity"]:::data
L_EOL["⛔ End-of-Life"]:::eol
end
style Legend fill:#F5F5F5,stroke:#999,stroke-width:1px
The Future-State architecture represents the target landscape for E2E-90.This view is generated from FutureFlows.xlsx (1 flow hops across 1 flow chains).
APPLICATION ARCHITECTURE — Architecture Diagram
Click any system node to open its IAPM application page.
Legend: Deployed · Developing · End-of-Life · No IAPM Match
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "18px", "fontFamily": "Segoe UI, Arial, sans-serif"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 50, "rankSpacing": 60}} }%%
flowchart TB
%% -- ArchiMate 3.2 + Azure style classes --
classDef business fill:#FFFFB3,stroke:#F9A825,stroke-width:2px,color:#000
classDef app fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef data fill:#BBDEFB,stroke:#1565C0,stroke-width:1px,color:#0D47A1,stroke-dasharray: 5 5
classDef middleware fill:#FFE0B2,stroke:#E65100,stroke-width:2px,color:#BF360C
classDef eol fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
classDef saas fill:#E1BEE7,stroke:#7B1FA2,stroke-width:2px,color:#4A148C
classDef cloud fill:#BBDEFB,stroke:#1565C0,stroke-width:2px,color:#0D47A1
classDef onprem fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
subgraph E2E90FLN_Boundary_Applications[" Boundary Applications"]
direction LR
E2E90F_e_g_MES_300["📦 e.g. MES 300"]:::app
E2E90F_e_g_XEUS["📦 e.g. XEUS"]:::app
end
E2E90FMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware
E2E90FDE_e_g_Cost_Element>"📄 e.g. Cost Element e.g. CSV / IDoc / JSON"]:::data
E2E90F_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E90FMW_e_g_Azure_Service_Bus
E2E90FMW_e_g_Azure_Service_Bus --> E2E90F_e_g_XEUS
style E2E90FLN_Boundary_Applications fill:#E8F5E9,stroke:#388E3C,stroke-width:2px
subgraph Legend["📐 LEGEND"]
direction LR
L_APP["📦 Application"]:::app
L_MW["🔗 Middleware"]:::middleware
L_DE>"📄 Data Entity"]:::data
L_EOL["⛔ End-of-Life"]:::eol
end
style Legend fill:#F5F5F5,stroke:#999,stroke-width:1px
