E2E-98 — R3 Equipment Product Supporting Items (PSI) Procurement

Architecture Document (TOGAF BDAT)

End-to-End Integrated Processes (E2E) Tower
Capability E2E-98 · Procure to Pay

IAO Program · R1 – R5
Generated: April 2026
Sajiv Francis

IAO Architecture Pipeline — Intel Confidential

1. Executive Summary

This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for E2E-98 R3 Equipment Product Supporting Items (PSI) Procurement within the IAO program. It includes 3 BPMN process diagram(s) in Section 3.

Dimension	Value
Tower	End-to-End Integrated Processes (E2E)
Process Group	Procure to Pay
Capability	E2E-98 - R3 Equipment Product Supporting Items (PSI) Procurement
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	Procure to Pay
L2 Capability	E2E-98 - R3 Equipment Product Supporting Items (PSI) Procurement

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-98 Process Migration	Migrate R3 Equipment Product Supporting Items (PSI) Procurement 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-98 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 3 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for E2E-98 R3 Equipment Product Supporting Items (PSI) Procurement.

#	Step ID	Process Name	Lanes	Tasks	Gateways
1	E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)_Procurement	E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)_Procurement	Boundary Apps, External Partners/Supplier

, SAP S/4HANA IF | 26 | 15 |

Supplier , SAP S/4 (IP & IF) | 12 | 6 |

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)Procurement — E2E-98A_R3_Equipment_Product_Supporting_Items(PSI)_Procurement

Swim Lanes: Boundary Apps · External Partners/Supplier · SAP S/4HANA IF | Tasks: 26 | Gateways: 15

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["Perform Supply Planning ICS (Phoenix)"] n2["Receive Procurement Planning Information"] n3["Review and Approve Procurement Planning Proposal by Intel Product BUs"] n4["Receive Information in ECA"] n5["Organize Transport-Intel Routing Guide (IRG)"] n6["Receive Manual invoices through OCR"] n7["Receive Incoming invoice/ B2B/OpenText/Web suite"] n8["ReadSoft Validation/Exception Handling based on rules setup"] n27(["fa:fa-play Initiate Supply Planning Process"]) n28(["fa:fa-stop Information Received"]) n31{{"fa:fa-code-branch exclusiveGateway"}} n32{{"fa:fa-code-branch B2B or OCR?"}} n33{{"fa:fa-code-branch exclusiveGateway"}} n38{{"fa:fa-arrows-alt parallelGateway"}} end subgraph lane_1["External Partners/Supplier "] n22["Perform Purchase Order Collaboration via SIFRIS"] n23["Perform Carrier Selection via Intel Routing Guide hosted Collaboration Portal"] n24["Pick Goods (Carrier) Order shipment"] n25["Forecast Communication and Commit"] n26["Raise Invoice (Supplier End)"] n36{{"fa:fa-code-branch exclusiveGateway"}} n37{{"fa:fa-code-branch exclusiveGateway"}} n45{{"fa:fa-arrows-alt parallelGateway"}} end subgraph lane_2["SAP S/4HANA IF"] n9["Create Purchase Requisition Change ( Pull-in/Push-out)"] n10["Receive Purchase Requisition Approval"] n11["Create Purchase Order"] n12["Purchase Order Change (Quantity/Schedule Dates)"] n13["Purchase Order Line-Item Deletion"] n14["Trigger GTS Check"] n15["Calculate Taxes"] n16["Publish Purchase Order"] n17["Acknowledge/Confirm Purchase Order"] n18["Create Inbound Delivery with House Airway bill number (HAWB)"] n19["TM Embedded"] n20["Post Goods Receipt"] n21["Post Supplier invoice"] n29["E2E-98C R3 SAP Transportation Management"] n30["E2E-98B R3 CFIN"] n34{{"fa:fa-code-branch Purchase Order Amendment Needed?"}} n35{{"fa:fa-code-branch Invoice Accepted?"}} n39{{"fa:fa-arrows-alt parallelGateway"}} n40{{"fa:fa-arrows-alt parallelGateway"}} n41{{"fa:fa-arrows-alt parallelGateway"}} n42{{"fa:fa-arrows-alt parallelGateway"}} n43{{"fa:fa-arrows-alt parallelGateway"}} n44{{"fa:fa-arrows-alt parallelGateway"}} end n9 --> n43 n10 --> n39 n39 --> n34 n34 -->|"Pull-In/Push-Out"| n12 n34 -->|"Cancellation"| n13 n31 --> n2 n13 --> n36 n11 --> n42 n1 --> n31 n2 --> n38 n27 --> n1 n38 --> n3 n38 --> n4 n4 --> n28 n3 --> n9 n40 --> n14 n40 --> n15 n15 --> n41 n14 --> n41 n41 --> n16 n23 --> n5 n17 -->|"For Intel Qwned Transport only"| n23 n5 --> n24 n42 --> n40 n43 --> n10 n24 -->|"3B2 / E2Open"| n18 n18 --> n44 n44 --> n19 n44 --> n20 n19 --> n29 n25 -->|"Supplier Responses via SIRFIS"| n31 n38 -->|"Forecast sharing via SIRFIS"| n25 n33 --> n8 n6 --> n33 n32 -->|"OCR"| n6 n21 --> n30 n8 --> n35 n37 --> n26 n35 -->|"No"| n37 n26 --> n32 n7 --> n33 n35 -->|"Yes"| n21 n42 --> n31 n43 --> n31 n22 --> n45 n45 --> n17 n16 --> n36 n36 --> n22 n12 --> n36 n32 -->|"B2B"| n7 n39 --> n11 class n27 startEvt class n28 endEvt class n29 startEvt class n30 startEvt class n31 gateway class n32 gateway class n33 gateway class n34 gateway class n35 gateway class n36 gateway class n37 gateway class n38 gateway class n39 gateway class n40 gateway class n41 gateway class n42 gateway class n43 gateway class n44 gateway class n45 gateway

👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.2 E2E-98B_R3_CFIN — E2E-98B_R3_CFIN

Swim Lanes: Boundary Apps · CFIN · MBC · SAP S/4 (IP & IF) | Tasks: 17 | 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 File in Bank"] n2["Update Payment Remittance"] n19(["fa:fa-stop Payment Data Updated"]) end subgraph lane_1["CFIN"] n3["Execute Payment Run"] n4["Create APM Memo Record"] n5["Process BCM Payment Batching Based on Business Rules"] n6["Generate APM Payment File"] n7["Route to Approver"] n8["Correct APM Correction File"] n9["Reverse APP Doc Number and Memo Record Deletion"] n10["Fetch Payments Factory (APM, BCM, MBC Monitor)"] n11["Review Failed Payment Log"] n12["Generate Payment Proposal"] n13["Replicate Supplier Invoice Posting"] n14["Post Collateral Expense Chargeback – IF Profit Center (Allocations)"] n15["Posted Collateral Cost Charged – IP Profit Center"] n18(["fa:fa-play Initiate Charge Back Process"]) n21(["fa:fa-stop Memo Record Created"]) n22(["fa:fa-stop APP Doc Reversed"]) n23(["fa:fa-stop Charge Back Process Completed"]) n25{{"fa:fa-code-branch Manual Approval Necessary?"}} n26{{"fa:fa-code-branch Approved?"}} n27{{"fa:fa-code-branch exclusiveGateway"}} n28{{"fa:fa-code-branch Can Be Corrected?"}} n29{{"fa:fa-code-branch exclusiveGateway"}} n30{{"fa:fa-code-branch exclusiveGateway"}} n31{{"fa:fa-code-branch Reversal or Reprocessing?"}} n32{{"fa:fa-arrows-alt parallelGateway"}} n33{{"fa:fa-arrows-alt parallelGateway"}} n34{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_2["MBC"] n16["Multi-Bank Connectivity (host-to-host)"] n17["Multi-Bank Connectivity (host-to-host)"] end subgraph lane_3["SAP S/4 (IP & IF)"] n20(["fa:fa-stop Payment Details provided back to Source System (IP/IF)"]) n24["E2E-98A R3 Equipment Product Supporting Items (PSI) Procurement"] end n12 --> n3 n3 --> n32 n4 --> n21 n5 --> n25 n25 -->|"No"| n27 n7 --> n26 n27 --> n6 n29 --> n5 n28 -->|"No"| n30 n9 --> n22 n10 --> n33 n30 --> n9 n33 --> n11 n32 --> n4 n11 --> n31 n31 -->|"Reversal"| n30 n2 --> n19 n6 --> n16 n33 --> n2 n8 --> n29 n13 --> n12 n33 --> n20 n24 --> n13 n25 -->|"Yes"| n7 n1 -->|"PAIN.002 (Pay-load file)"| n17 n16 -->|"PAIN.001 (Pay-load file)"| n1 n32 -->|"Reprocessing"| n29 n34 --> n8 n26 -->|"Yes"| n27 n26 -->|"No"| n28 n17 --> n10 n31 -->|"Reprocessing"| n34 n28 -->|"Yes"| n34 n15 --> n23 n14 -->|"Overhead Expense + Service Charges"| n15 n18 --> n14 class n18 startEvt class n19 endEvt class n20 endEvt class n21 endEvt class n22 endEvt class n23 endEvt class n24 startEvt class n25 gateway class n26 gateway class n27 gateway class n28 gateway class n29 gateway class n30 gateway class n31 gateway class n32 gateway class n33 gateway class n34 gateway

👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.3 E2E-98C_R3_SAP_Transportation_Management — E2E-98C_R3_SAP_Transportation_Management

Swim Lanes: Boundary Apps · External Partners/ Supplier · SAP S/4 (IP & IF) | 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/Send Information in Carrier Invoice Reconciliation/Dispute..."] n2["Event updates are received in GTT"] n17{{"fa:fa-code-branch exclusiveGateway"}} end subgraph lane_1["External Partners/ Supplier "] n11["Feed Rates/Charges Integrators 3rd party service – Redwood"] n12["Carrier"] n13(["fa:fa-play Process Initiated Based on Rate/Charges Available"]) n14(["fa:fa-play Events Published"]) n20{{"fa:fa-arrows-alt parallelGateway"}} n21{{"fa:fa-arrows-alt parallelGateway"}} end subgraph lane_2["SAP S/4 (IP & IF)"] n3["Generate Freight Unit (TM)"] n4["Create Freight Order (TM)"] n5["Perform Carrier Updates and Calculate Charges"] n6["Execute Freight Order (TM)"] n7["Post Freight Settlement Document (TM)"] n8["Create Service PO for FSD (TM)"] n9["Post SES with Auto Release (TM)"] n10["Create Cost Distribution/Agency Business Document (TM)"] n15(["fa:fa-stop TM process ended"]) n16["E2E-98A R3 Equipment Product Supporting Items (PSI) Procurement"] n18{{"fa:fa-code-branch exclusiveGateway"}} n19{{"fa:fa-code-branch exclusiveGateway"}} n22{{"fa:fa-arrows-alt inclusiveGateway"}} end n3 --> n4 n5 --> n18 n7 --> n8 n19 --> n5 n6 --> n22 n4 --> n19 n9 --> n10 n10 --> n15 n11 --> n20 n13 --> n11 n17 --> n1 n14 --> n12 n12 --> n21 n21 --> n17 n20 --> n17 n21 --> n2 n1 --> n22 n20 --> n19 n2 -->|"Event Update"| n18 n18 --> n6 n8 --> n9 n22 --> n7 n16 --> n3 class n13 startEvt class n14 startEvt class n15 endEvt class n16 startEvt class n17 gateway class n18 gateway class n19 gateway class n20 gateway class n21 gateway class n22 gateway

👁 View Diagram

3.3 Business Roles & Responsibilities

Role / Lane	Processes Involved	Description
Boundary Apps	E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)_Procurement, E2E-98B_R3_CFIN, E2E-98C_R3_SAP_Transportation_Management
External Partners/Supplier
E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)_Procurement,
SAP S/4HANA IF	E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)_Procurement,
CFIN	E2E-98B_R3_CFIN,
MBC	E2E-98B_R3_CFIN,
SAP S/4 (IP & IF)	E2E-98B_R3_CFIN, E2E-98C_R3_SAP_Transportation_Management
External Partners/

Supplier

| E2E-98C_R3_SAP_Transportation_Management | |

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 E2E98CDACL_e_g_Azure_SQL[" "] direction TB E2E98CDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E98CDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E98CDAA_e_g_XEUS -.-> E2E98CDAD_e_g_Azure_SQL end style E2E98CDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E98CDACL_e_g_SAP_HANA[" "] direction TB E2E98CDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E98CDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E98CDAA_e_g_MES_300 -.-> E2E98CDAD_e_g_SAP_HANA end style E2E98CDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E98CDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E98CDAD_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 E2E98FDACL_e_g_Azure_SQL[" "] direction TB E2E98FDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E98FDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E98FDAA_e_g_XEUS -.-> E2E98FDAD_e_g_Azure_SQL end style E2E98FDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E98FDACL_e_g_SAP_HANA[" "] direction TB E2E98FDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E98FDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E98FDAA_e_g_MES_300 -.-> E2E98FDAD_e_g_SAP_HANA end style E2E98FDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E98FDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E98FDAD_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-98.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 E2E98CLN_Boundary_Applications[" Boundary Applications"] direction LR E2E98C_e_g_MES_300["📦 e.g. MES 300"]:::app E2E98C_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E98CMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E98CDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E98C_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E98CMW_e_g_Azure_Service_Bus E2E98CMW_e_g_Azure_Service_Bus --> E2E98C_e_g_XEUS style E2E98CLN_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-98.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 E2E98FLN_Boundary_Applications[" Boundary Applications"] direction LR E2E98F_e_g_MES_300["📦 e.g. MES 300"]:::app E2E98F_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E98FMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E98FDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E98F_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E98FMW_e_g_Azure_Service_Bus E2E98FMW_e_g_Azure_Service_Bus --> E2E98F_e_g_XEUS style E2E98FLN_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 E2E98CPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E98CPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E98CPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E98CPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E98CPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E98CPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E98CPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E98CPLP_e_g_Azure_PaaS subgraph E2E98CPLLegend["📐 PLATFORM LEGEND"] direction LR E2E98CPLLC["☁️ Cloud"] E2E98CPLLS["🔮 SaaS"] E2E98CPLLO["🏢 On-Prem"] E2E98CPLLD["💾 Data Platform"] E2E98CPLLM["🔗 Middleware"] end style E2E98CPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E98CPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E98CPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E98CPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E98CPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E98CPLLM 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 E2E98FPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E98FPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E98FPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E98FPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E98FPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E98FPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E98FPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E98FPLP_e_g_Azure_PaaS subgraph E2E98FPLLegend["📐 PLATFORM LEGEND"] direction LR E2E98FPLLC["☁️ Cloud"] E2E98FPLLS["🔮 SaaS"] E2E98FPLLO["🏢 On-Prem"] E2E98FPLLD["💾 Data Platform"] E2E98FPLLM["🔗 Middleware"] end style E2E98FPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E98FPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E98FPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E98FPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E98FPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E98FPLLM 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-98 — Architecture Document (TOGAF BDAT) · End-to-End Integrated Processes · Generated: April 2026

E2E-98 — R3 Equipment Product Supporting Items (PSI) Procurement

Architecture Document (TOGAF BDAT)

Table of Contents

1. Executive Summary

2. Business Context & Objectives

2.1 Classification

2.2 Business Drivers

2.3 Success Criteria

2.4 Companion Documents

3. Business Architecture (TOGAF “B”)

3.1 Business Process Overview

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 E2E-98A_R3_Equipment_Product_Supporting_Items_(PSI)Procurement — E2E-98A_R3_Equipment_Product_Supporting_Items(PSI)_Procurement

BUSINESS ARCHITECTURE — 3.2.2 E2E-98B_R3_CFIN — E2E-98B_R3_CFIN

BUSINESS ARCHITECTURE — 3.2.3 E2E-98C_R3_SAP_Transportation_Management — E2E-98C_R3_SAP_Transportation_Management

3.3 Business Roles & Responsibilities

4. Data Architecture (TOGAF “D”)

4.1 Data Flows — Source to Target

4.2 Data Flow Diagrams

4.2.1 Current-State — Current-State Data Flows

4.2.2 Future-State — Future-State Data Flows

4.3 Data Lineage

4.4 RICEFW Data Objects

4.5 Data Governance & Quality

5. Application Architecture (TOGAF “A”)

5.1 Current-State — Current-State Application Landscape

Overview

APPLICATION ARCHITECTURE — Architecture Diagram

Current-State Flow Narrative

5.2 Future-State — Future-State Application Landscape

Overview

APPLICATION ARCHITECTURE — Architecture Diagram

Future-State Flow Narrative

5.3 Change Impact Summary

5.4 Component Overview

System Inventory

5.5 RICEFW Inventory

5.6 Integration Patterns

6. Technology Architecture (TOGAF “T”)

6.1 Platform & Infrastructure

6.1.1 Current-State — Current-State Platform Architecture

6.1.2 Future-State — Future-State Platform Architecture

Platform Inventory

6.2 SAP Development Object Status

6.3 NFRs & Design Principles

6.4 Security & Governance

7. Project Context

7.1 Project Roadmap & Go-Live Plan

7.2 RAID Log

7.3 Recommendations & Next Steps