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-100 — R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box
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-100 R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box within the IAO program. It includes 2 BPMN process diagram(s) in Section 3.
Dimension
Value
Tower
End-to-End Integrated Processes (E2E)
Process Group
Procure to Pay
Capability
E2E-100 - R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box
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-100 - R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box
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-100 Process Migration
Migrate R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box 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-100 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 2 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for E2E-100 R3 - Purchase Requisition to Payments for Direct procurement with Planning Integration (Box.
#
Step ID
Process Name
Lanes
Tasks
Gateways
1
E2E-100_R3_CFIN
E2E-100_R3_CFIN
Boundary Apps, CFIN, MBC, SAP S/4HANA IP
15
10
2
E2E-100_R3_SAP_Transportation_Management
E2E-100_R3_SAP_Transportation_Management
Boundary Apps, External Partners/
Supplier
, SAP S/4HANA IP | 12 | 6 |
3.2 Business Process Diagrams
BUSINESS ARCHITECTURE — 3.2.1 E2E-100_R3_CFIN — E2E-100_R3_CFIN
Swim Lanes: Boundary Apps · CFIN · MBC · SAP S/4HANA IP | Tasks: 15 | 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"]
n17(["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"]
n19(["fa:fa-stop Memo Record Created"])
n20(["fa:fa-stop APP Doc Reversed"])
n21{{"fa:fa-code-branch Manual Approval Necessary?"}}
n22{{"fa:fa-code-branch Approved?"}}
n23{{"fa:fa-code-branch exclusiveGateway"}}
n24{{"fa:fa-code-branch Can Be Corrected?"}}
n25{{"fa:fa-code-branch exclusiveGateway"}}
n26{{"fa:fa-code-branch exclusiveGateway"}}
n27{{"fa:fa-code-branch Reversal or Reprocessing?"}}
n28{{"fa:fa-arrows-alt parallelGateway"}}
n29{{"fa:fa-arrows-alt parallelGateway"}}
n30{{"fa:fa-arrows-alt inclusiveGateway"}}
end
subgraph lane_2["MBC"]
n14["Multi-Bank Connectivity (host-to-host)"]
n15["Multi-Bank Connectivity (host-to-host)"]
end
subgraph lane_3["SAP S/4HANA IP"]
n16(["fa:fa-play Supplier Payment Process initiated"])
n18(["fa:fa-stop Payment Details provided back to Source System (IP/IF)"])
end
n12 --> n3
n3 --> n28
n4 --> n19
n5 --> n21
n21 -->|"No"| n23
n7 --> n22
n23 --> n6
n25 --> n5
n24 -->|"No"| n26
n9 --> n20
n10 --> n29
n26 --> n9
n29 --> n11
n11 --> n27
n27 -->|"Reversal"| n26
n2 --> n17
n6 --> n14
n29 --> n2
n8 --> n25
n13 --> n12
n29 --> n18
n21 -->|"Yes"| n7
n1 -->|"PAIN.002 (Pay-load file)"| n15
n14 -->|"PAIN.001 (Pay-load file)"| n1
n28 -->|"Reprocessing"| n25
n30 --> n8
n22 -->|"Yes"| n23
n22 -->|"No"| n24
n15 --> n10
n27 -->|"Reprocessing"| n30
n24 -->|"Yes"| n30
n16 --> n13
n28 --> n4
class n16 startEvt
class n17 endEvt
class n18 endEvt
class n19 endEvt
class n20 endEvt
class n21 gateway
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
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 E2E100CDACL_e_g_Azure_SQL[" "]
direction TB
E2E100CDAA_e_g_XEUS["e.g. XEUS"]:::appBox
E2E100CDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud
E2E100CDAA_e_g_XEUS -.-> E2E100CDAD_e_g_Azure_SQL
end
style E2E100CDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px
subgraph E2E100CDACL_e_g_SAP_HANA[" "]
direction TB
E2E100CDAA_e_g_MES_300["e.g. MES 300"]:::appBox
E2E100CDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData
E2E100CDAA_e_g_MES_300 -.-> E2E100CDAD_e_g_SAP_HANA
end
style E2E100CDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px
E2E100CDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E100CDAD_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-100.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 E2E100CLN_Boundary_Applications[" Boundary Applications"]
direction LR
E2E100C_e_g_MES_300["📦 e.g. MES 300"]:::app
E2E100C_e_g_XEUS["📦 e.g. XEUS"]:::app
end
E2E100CMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware
E2E100CDE_e_g_Cost_Element>"📄 e.g. Cost Element e.g. CSV / IDoc / JSON"]:::data
E2E100C_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E100CMW_e_g_Azure_Service_Bus
E2E100CMW_e_g_Azure_Service_Bus --> E2E100C_e_g_XEUS
style E2E100CLN_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-100.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 E2E100FLN_Boundary_Applications[" Boundary Applications"]
direction LR
E2E100F_e_g_MES_300["📦 e.g. MES 300"]:::app
E2E100F_e_g_XEUS["📦 e.g. XEUS"]:::app
end
E2E100FMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware
E2E100FDE_e_g_Cost_Element>"📄 e.g. Cost Element e.g. CSV / IDoc / JSON"]:::data
E2E100F_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E100FMW_e_g_Azure_Service_Bus
E2E100FMW_e_g_Azure_Service_Bus --> E2E100F_e_g_XEUS
style E2E100FLN_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
