🏠 Home E2E Tower Architecture
🤖 IAO Architecture Assistant AI-Powered
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
IAO Architecture

E2E-72 — IP

Architecture Document (TOGAF BDAT)

End-to-End Integrated Processes (E2E) Tower
Capability E2E-72 · Forecast to Stock

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-72 IP within the IAO program. It includes 4 BPMN process diagram(s) in Section 3.

Dimension Value
Tower End-to-End Integrated Processes (E2E)
Process Group Forecast to Stock
Capability E2E-72 - IP
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 Forecast to Stock
L2 Capability E2E-72 - IP

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-72 Process Migration Migrate IP 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-72 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 4 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for E2E-72 IP.

# Step ID Process Name Lanes Tasks Gateways
1 E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a Boundary Apps, External Partners/

Supplier , SAP S/4 Intel Foundry Purchase Req – Purchase Order

| 12 | 6 | | 2 | E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | Boundary Apps, External Partners/

Supplier , SAP S/4 Intel Foundry Purchase Req – Purchase Order

| 19 | 10 | | 3 | E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | Boundary Apps, External Partners/

Supplier , SAP S/4 Intel Foundry Purchase Req – Purchase Order

| 19 | 10 | | 4 | E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | Boundary Apps, External Partners/

Supplier , SAP S/4 Intel Foundry Purchase Req – Purchase Order

| 19 | 10 |

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a — E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a

Swim Lanes: Boundary Apps · External Partners/ Supplier · SAP S/4 Intel Foundry Purchase Req – Purchase Order

| Tasks: 12 | 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["Receive inventory request in Planning Hub"] n2["Fetch Inventory Data from Speed"] n3["Fetch BOM Data from MDG"] n4["Fetch Inventory demand from BY"] n5["Receive Updates via PDH"] n13(["fa:fa-play Initiate Inventory request process"]) n19{{"fa:fa-arrows-alt parallelGateway"}} n20{{"fa:fa-arrows-alt parallelGateway"}} n22{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_1["External Partners/ Supplier "] n6["PO Received at Supplier"] n7["Order Acknowledgement sent to S/4"] n8["Send and Receive Forecast communication commit"] n15(["fa:fa-play Forecast communication from ECA"]) n16(["fa:fa-stop Forecast communicated"]) end subgraph lane_2["SAP S/4 Intel Foundry Purchase Req – Purchase Order "] n9[["fa:fa-cog Create Purchase Req"]] n10[["fa:fa-cog Use 'MD04' Fiori App to show PR and Stock levels"]] n11[["fa:fa-cog PR converted to PO (Based on Planning Design Horizon)"]] n12[["fa:fa-cog Do Excel Upload or Manual Creation"]] n14(["fa:fa-play Initiate Excel Upload or Manual Creation"]) n17["intermediateThrowEvent"] n18{{"fa:fa-code-branch exclusiveGateway"}} n21{{"fa:fa-arrows-alt parallelGateway"}} n23{{"fa:fa-arrows-alt inclusiveGateway"}} end n11 --> n21 n3 --> n20 n19 --> n2 n2 --> n20 n6 --> n7 n18 --> n11 n21 -->|"3A4 (EDI 850) E2Open"| n6 n19 --> n4 n13 --> n19 n9 --> n10 n21 --> n17 n10 --> n18 n14 --> n12 n12 --> n23 n23 --> n9 n4 --> n22 n1 --> n22 n22 --> n5 n5 --> n23 n20 --> n1 n19 --> n3 n7 -->|"3A4 (EDI 855) Order Confirmation E2Open"| n18 n8 --> n16 n15 --> n8 class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 startEvt class n14 startEvt class n15 startEvt class n16 endEvt class n17 startEvt class n18 gateway class n19 gateway class n20 gateway class n21 gateway class n22 gateway class n23 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.2 E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T — E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T

Swim Lanes: Boundary Apps · External Partners/ Supplier · SAP S/4 Intel Foundry Purchase Req – Purchase Order

| Tasks: 19 | Gateways: 10

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["Receive inventory request in Planning Hub"] n2["Fetch Inventory Data from Speed"] n3["Fetch BOM Data from MDG"] n4["Fetch Inventory demand from BY"] n5["Receive Updates via PDH"] n20(["fa:fa-play Initiate Inventory request process"]) n28{{"fa:fa-arrows-alt parallelGateway"}} n29{{"fa:fa-arrows-alt parallelGateway"}} n32{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_1["External Partners/ Supplier "] n6["PO Received at Supplier"] n7["Order Acknowledgement sent to S/4"] n8["Perform Supplier Activities"] n22(["fa:fa-stop PO Updated to Supplier"]) n27{{"fa:fa-code-branch exclusiveGateway"}} end subgraph lane_2["SAP S/4 Intel Foundry Purchase Req – Purchase Order "] n9[["fa:fa-cog Create Purchase Req"]] n10[["fa:fa-cog Use MD04 Fiori App to show PR and Stock levels"]] n11[["fa:fa-cog PR converted to PO"]] n12[["fa:fa-cog Check if PR Approved as per Planning design"]] n13[["fa:fa-cog Validate Vendor through Routing tables"]] n14[["fa:fa-cog Check if Supplier is E2E Open enabled"]] n15[["fa:fa-cog Move PO's to Staging"]] n16[["fa:fa-cog Send PO's to E2Open"]] n17[["fa:fa-cog B2B config (OpenText)"]] n18[["fa:fa-cog PO’s sent to WebSuite"]] n19[["fa:fa-cog Send PO's to Ariba P2P"]] n21(["fa:fa-stop PO Sent"]) n23{{"fa:fa-code-branch exclusiveGateway"}} n24{{"fa:fa-code-branch Supplier E2Open Enabled?"}} n25{{"fa:fa-code-branch Supplier is B2B enabled"}} n26{{"fa:fa-code-branch Has ANID"}} n30{{"fa:fa-arrows-alt parallelGateway"}} n31{{"fa:fa-arrows-alt parallelGateway"}} end n10 --> n12 n11 --> n30 n3 --> n29 n2 --> n29 n6 --> n7 n23 --> n11 n30 -->|"3A4 (EDI 850) E2Open"| n6 n28 --> n3 n29 --> n1 n1 --> n32 n30 --> n13 n13 --> n14 n14 --> n24 n24 -->|"Yes"| n16 n15 --> n25 n25 -->|"Yes"| n17 n7 -->|"3A4 (EDI 855) Order Confirmation E2Open"| n23 n17 --> n27 n18 --> n27 n27 --> n8 n8 --> n22 n12 --> n23 n16 --> n21 n25 -->|"No"| n31 n26 -->|"Yes"| n19 n24 --> n26 n26 -->|"No"| n15 n19 -->|"All PO’s sent to WebSuite for viewing"| n31 n5 --> n9 n32 --> n5 n31 --> n18 n28 --> n4 n28 --> n2 n4 --> n32 n20 --> n28 n9 --> n10 class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 serviceTask class n14 serviceTask class n15 serviceTask class n16 serviceTask class n17 serviceTask class n18 serviceTask class n19 serviceTask class n20 startEvt class n21 endEvt class n22 endEvt class n23 gateway class n24 gateway class n25 gateway class n26 gateway class n27 gateway class n28 gateway class n29 gateway class n30 gateway class n31 gateway class n32 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.3 E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T — E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T

Swim Lanes: Boundary Apps · External Partners/ Supplier · SAP S/4 Intel Foundry Purchase Req – Purchase Order

| Tasks: 19 | Gateways: 10

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["Receive inventory request in Planning Hub"] n2["Fetch Data from Speed"] n3["Fetch BOM Data from MDG"] n4["Fetch Inventory demand from BY"] n5["Receive Updates via PDH"] n20(["fa:fa-play Request Response Process Initiated"]) n27{{"fa:fa-arrows-alt parallelGateway"}} n28{{"fa:fa-arrows-alt parallelGateway"}} n31{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_1["External Partners/ Supplier "] n6["PO Received at Supplier"] n7["Order Acknowledgement sent to S/4"] n8["Perform Supplier Activities"] n21(["fa:fa-stop PO updated to Supplier"]) n26{{"fa:fa-code-branch exclusiveGateway"}} end subgraph lane_2["SAP S/4 Intel Foundry Purchase Req – Purchase Order "] n9[["fa:fa-cog Create Purchase Req"]] n10[["fa:fa-cog Use 'MD04' Fiori App to show PR and Stock levels"]] n11[["fa:fa-cog PR converted to Sub-Con PO"]] n12[["fa:fa-cog Check if PR Approved as per Planning design"]] n13[["fa:fa-cog Validate Vendor through Routing tables"]] n14[["fa:fa-cog Check if Supplier is E2E Open enabled"]] n15[["fa:fa-cog Move PO's to Staging"]] n16[["fa:fa-cog Send PO's to E2Open"]] n17[["fa:fa-cog B2B config (OpenText)"]] n18[["fa:fa-cog PO’s sent to WebSuite"]] n19[["fa:fa-cog Send PO's to Ariba P2P"]] n22{{"fa:fa-code-branch exclusiveGateway"}} n23{{"fa:fa-code-branch Supplier E2Open Enabled?"}} n24{{"fa:fa-code-branch Supplier is B2B enabled"}} n25{{"fa:fa-code-branch Has ANID"}} n29{{"fa:fa-arrows-alt parallelGateway"}} n30{{"fa:fa-arrows-alt parallelGateway"}} end n10 --> n12 n11 --> n29 n27 --> n2 n2 --> n28 n6 --> n7 n22 --> n11 n27 --> n3 n28 --> n1 n20 --> n27 n14 --> n23 n15 --> n24 n7 -->|"3A4 (EDI 855) Order Confirmation E2Open"| n22 n3 -->|"MDG feeds data to S4"| n28 n17 --> n26 n29 -->|"3A4 (EDI 850) E2Open"| n6 n13 --> n14 n23 -->|"Yes"| n16 n30 --> n18 n24 -->|"Yes"| n17 n24 -->|"No"| n30 n12 --> n22 n19 -->|"All PO’s sent to WebSuite for viewing"| n30 n18 --> n26 n25 -->|"No"| n19 n5 --> n9 n1 --> n31 n4 --> n31 n27 --> n4 n31 --> n5 n9 --> n10 n29 --> n13 n25 -->|"Yes"| n15 n26 --> n8 n8 --> n21 n23 -->|"No"| n25 class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 serviceTask class n14 serviceTask class n15 serviceTask class n16 serviceTask class n17 serviceTask class n18 serviceTask class n19 serviceTask class n20 startEvt class n21 endEvt class n22 gateway class n23 gateway class n24 gateway class n25 gateway class n26 gateway class n27 gateway class n28 gateway class n29 gateway class n30 gateway class n31 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.4 E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T — E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T

Swim Lanes: Boundary Apps · External Partners/ Supplier · SAP S/4 Intel Foundry Purchase Req – Purchase Order

| Tasks: 19 | Gateways: 10

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["Receive inventory request in Planning Hub"] n2["Fetch Data from Speed"] n3["Fetch BOM Data from MDG"] n4["Fetch Inventory demand from BY"] n5["Receive Updates via PDH"] n20(["fa:fa-play Request Response Process Initiated"]) n27{{"fa:fa-arrows-alt parallelGateway"}} n28{{"fa:fa-arrows-alt parallelGateway"}} n31{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_1["External Partners/ Supplier "] n6["PO Received at Supplier"] n7["Order Acknowledgement sent to S/4"] n8["Perform Supplier Activities"] n21(["fa:fa-stop PO Posted to Supplier"]) n26{{"fa:fa-code-branch exclusiveGateway"}} end subgraph lane_2["SAP S/4 Intel Foundry Purchase Req – Purchase Order "] n9[["fa:fa-cog Create Purchase Req"]] n10[["fa:fa-cog Use MD04 Fiori App to show PR and Stock levels"]] n11[["fa:fa-cog PR converted to Sub-Con PO"]] n12[["fa:fa-cog Check if PR Approved as per Planning design"]] n13[["fa:fa-cog Validate Vendor through Routing tables"]] n14[["fa:fa-cog Check if Supplier is E2E Open enabled"]] n15[["fa:fa-cog Move PO's to Staging"]] n16[["fa:fa-cog Send PO's to E2Open"]] n17[["fa:fa-cog B2B config (OpenText)"]] n18[["fa:fa-cog PO’s sent to WebSuite"]] n19[["fa:fa-cog Send PO's to Ariba P2P"]] n22{{"fa:fa-code-branch exclusiveGateway"}} n23{{"fa:fa-code-branch Supplier E2Open Enabled?"}} n24{{"fa:fa-code-branch Supplier is B2B enabled"}} n25{{"fa:fa-code-branch Has ANID ?"}} n29{{"fa:fa-arrows-alt parallelGateway"}} n30{{"fa:fa-arrows-alt parallelGateway"}} end n10 --> n12 n11 --> n29 n27 --> n2 n2 --> n28 n6 --> n7 n22 --> n11 n27 --> n3 n28 --> n1 n1 --> n31 n14 --> n23 n23 -->|"No"| n25 n15 --> n24 n7 -->|"3A4 (EDI 855) Order Confirmation E2Open"| n22 n3 -->|"MDG feeds data to S4"| n28 n17 --> n26 n26 --> n8 n29 -->|"3A4 (EDI 850) E2Open"| n6 n23 -->|"Yes"| n16 n24 -->|"Yes"| n17 n18 --> n26 n29 --> n13 n24 -->|"No"| n30 n12 --> n22 n8 --> n21 n25 -->|"Yes"| n15 n25 -->|"No"| n19 n31 --> n5 n4 --> n31 n27 --> n4 n20 --> n27 n5 --> n9 n9 --> n10 n13 --> n14 n30 --> n18 n19 -->|"All PO’s sent to WebSuite for viewing"| n30 class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 serviceTask class n14 serviceTask class n15 serviceTask class n16 serviceTask class n17 serviceTask class n18 serviceTask class n19 serviceTask class n20 startEvt class n21 endEvt class n22 gateway class n23 gateway class n24 gateway class n25 gateway class n26 gateway class n27 gateway class n28 gateway class n29 gateway class n30 gateway class n31 gateway
👁 View Diagram

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
Boundary Apps E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a, E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T
External Partners/

Supplier

| E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a, E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | | | SAP S/4 Intel Foundry

Purchase Req – Purchase Order

| E2E-72-Intel_Foundry-Request_and_Response_process_with_planning_integration(Process_for_Type_A_a, E2E-72A-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72B-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T, E2E-72C-FTS-Intel_Product-Request_and_Response_process_with_planning_integration(Process_for_T | |

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 E2E72CDACL_e_g_Azure_SQL[" "] direction TB E2E72CDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E72CDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E72CDAA_e_g_XEUS -.-> E2E72CDAD_e_g_Azure_SQL end style E2E72CDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E72CDACL_e_g_SAP_HANA[" "] direction TB E2E72CDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E72CDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E72CDAA_e_g_MES_300 -.-> E2E72CDAD_e_g_SAP_HANA end style E2E72CDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E72CDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E72CDAD_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
👁 View Diagram

4.2.2 Future-State — Future-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 E2E72FDACL_e_g_Azure_SQL[" "] direction TB E2E72FDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E72FDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E72FDAA_e_g_XEUS -.-> E2E72FDAD_e_g_Azure_SQL end style E2E72FDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E72FDACL_e_g_SAP_HANA[" "] direction TB E2E72FDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E72FDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E72FDAA_e_g_MES_300 -.-> E2E72FDAD_e_g_SAP_HANA end style E2E72FDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E72FDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E72FDAD_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
👁 View Diagram

4.3 Data Lineage

# Source System Source Schema/Object Target System Target Schema/Object Transformation
1 e.g. MES 300 e.g. CKMLHD table e.g. XEUS e.g. dbo.CostElements Lineage notes

4.4 RICEFW Data Objects

RICEFW data objects (Reports and Conversions) will be auto-populated from the Smartsheet Object Tracker when matched to this capability.

4.5 Data Governance & Quality

Concern Approach
Data Ownership Per-entity owners listed in Section 3.1
Data Classification Financial data classified as Intel Confidential
Data Retention Per Intel corporate retention policies
Data Quality Validated at source; reconciliation at target

5. Application Architecture (TOGAF “A”)

5.1 Current-State — Current-State Application Landscape

Overview

The Current-State architecture represents the current / legacy landscape for E2E-72.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 E2E72CLN_Boundary_Applications[" Boundary Applications"] direction LR E2E72C_e_g_MES_300["📦 e.g. MES 300"]:::app E2E72C_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E72CMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E72CDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E72C_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E72CMW_e_g_Azure_Service_Bus E2E72CMW_e_g_Azure_Service_Bus --> E2E72C_e_g_XEUS style E2E72CLN_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
👁 View Diagram

Current-State Flow Narrative

# Flow Chain Path Interface Freq
1 e.g. MES Route to ICOST e.g. MES 300 → e.g. XEUS e.g. Direct / API / File e.g. Near Real-Time

5.2 Future-State — Future-State Application Landscape

Overview

The Future-State architecture represents the target landscape for E2E-72.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 E2E72FLN_Boundary_Applications[" Boundary Applications"] direction LR E2E72F_e_g_MES_300["📦 e.g. MES 300"]:::app E2E72F_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E72FMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E72FDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E72F_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E72FMW_e_g_Azure_Service_Bus E2E72FMW_e_g_Azure_Service_Bus --> E2E72F_e_g_XEUS style E2E72FLN_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
👁 View Diagram

Future-State Flow Narrative

# Flow Chain Path Interface Freq
1 e.g. MES Route to ICOST e.g. MES 300 → e.g. XEUS e.g. Direct / API / File e.g. Near Real-Time

5.3 Change Impact Summary

Change Type Flow Chain Detail
UNCHANGED e.g. MES Route to ICOST No change

Totals: 0 new - 0 removed - 0 modified - 1 unchanged

5.4 Component Overview

System Inventory

System IAPM ID Status
e.g. MES 300 - N/A
e.g. XEUS - N/A

5.5 RICEFW Inventory

RICEFW inventory will be auto-populated from the Smartsheet S/4 Object Tracker when matched to this capability.

5.6 Integration Patterns

# Pattern Flow Chain Middleware Protocol Auth
1 e.g. Pub-Sub / P2P / ETL e.g. MES Route to ICOST e.g. Azure Service Bus e.g. REST / RFC / SFTP e.g. OAuth / NTLM / Cert

6. Technology Architecture (TOGAF “T”)

6.1 Platform & Infrastructure

TECHNOLOGY / PLATFORM ARCHITECTURE — Platforms (green) host applications (blue). Thick arrows show platform-to-platform integration flows.

6.1.1 Current-State — Current-State Platform Architecture

%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "14px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 40, "rankSpacing": 50}} }%% flowchart TB classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C classDef platBox fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C subgraph E2E72CPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E72CPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E72CPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E72CPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E72CPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E72CPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E72CPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E72CPLP_e_g_Azure_PaaS subgraph E2E72CPLLegend["📐 PLATFORM LEGEND"] direction LR E2E72CPLLC["☁️ Cloud"] E2E72CPLLS["🔮 SaaS"] E2E72CPLLO["🏢 On-Prem"] E2E72CPLLD["💾 Data Platform"] E2E72CPLLM["🔗 Middleware"] end style E2E72CPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E72CPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E72CPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E72CPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E72CPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E72CPLLM fill:#FFE0B2,stroke:#E65100,stroke-width:3px,color:#BF360C
👁 View Diagram

Legend: 🖥️ Platform · 📦 Application · ⛔ End-of-Life · 📋 Unassigned

6.1.2 Future-State — Future-State Platform Architecture

%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "14px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 40, "rankSpacing": 50}} }%% flowchart TB classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C classDef platBox fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C subgraph E2E72FPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E72FPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E72FPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E72FPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E72FPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E72FPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E72FPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E72FPLP_e_g_Azure_PaaS subgraph E2E72FPLLegend["📐 PLATFORM LEGEND"] direction LR E2E72FPLLC["☁️ Cloud"] E2E72FPLLS["🔮 SaaS"] E2E72FPLLO["🏢 On-Prem"] E2E72FPLLD["💾 Data Platform"] E2E72FPLLM["🔗 Middleware"] end style E2E72FPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E72FPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E72FPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E72FPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E72FPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E72FPLLM fill:#FFE0B2,stroke:#E65100,stroke-width:3px,color:#BF360C
👁 View Diagram

Legend: 🖥️ Platform · 📦 Application · ⛔ End-of-Life · 📋 Unassigned

Platform Inventory

# Platform Type Systems Using Environment
1 e.g. Azure PaaS Cloud / SaaS e.g. XEUS DEV,QAS,PRD
2 e.g. S/4 HANA 2023 On-Premise e.g. MES 300 DEV,QAS,PRD

6.2 SAP Development Object Status

Metric DEV QAS PRD
Transport Requests
Custom Code Objects
CDS Views
Fiori Apps
BAdIs / Enhancements

6.3 NFRs & Design Principles

Category Requirement Target / SLA Priority
Performance Order/transaction processing within interactive SLA < 3 seconds for online transactions High
Availability Business-critical systems available during extended hours 99.9% (06:00-22:00 all time zones) High
Scalability Support seasonal and promotional volume spikes Handle 2x baseline transaction volume Medium
Recoverability Customer-facing systems recover within business impact window RPO < 30 min, RTO < 2 hours High
Data Volume Support transactional data growth from business expansion 10M+ documents/year Medium
Latency Near-real-time integration for order status updates < 30 seconds for status propagation Medium
Concurrency Support global user base across business functions 300+ concurrent users Medium

6.4 Security & Governance

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

7. Project Context

7.1 Project Roadmap & Go-Live Plan

Project roadmap and RICEFW timelines will be auto-populated from the Smartsheet Object Tracker when matched to this capability.

7.2 RAID Log

RAID items will be auto-populated from the Smartsheet RAID log when matched to this capability.

7.3 Recommendations & Next Steps

# 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 1 flow chains to satisfy Data Architecture (TOGAF D) requirements Medium Data Architect 2026-Q3 Open
3 Testing Develop integration test scenarios covering all 1 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

E2E-72 — Architecture Document (TOGAF BDAT) · End-to-End Integrated Processes · Generated: April 2026