🏠 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-118 — Forecast to Stock

Architecture Document (TOGAF BDAT)

End-to-End Integrated Processes (E2E) Tower
Capability E2E-118 · 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-118 Forecast to Stock within the IAO program. It includes 5 BPMN process diagram(s) in Section 3.

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

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

# Step ID Process Name Lanes Tasks Gateways
1 E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-_with_CMMS E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-_with_CMMS Boundary Apps

, SAP S/4 Intel Foundry (Receiving Company) B , SAP S/4 Intel Foundry (Sending Company) A

| 19 | 3 | | 2 | E2E_118G__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_CMM | E2E_118G__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_CMM | Boundary Apps

, SAP S/4 Intel Foundry (Receiving Site) B , SAP S/4 Intel Foundry (Sending Site) A

| 19 | 3 | | 3 | E2E_118H__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_iSTART | E2E_118H__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-_with_iSTART | Boundary Apps

, SAP S/4 Intel Foundry (Receiving Company B , SAP S/4 Intel Foundry (Sending Company) A , UI | 20 | 4 |

| 4 | E2E_118I__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_iST | E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_iST | Boundary Apps

, SAP S/4 Intel Foundry (Receiving Site) B , SAP S/4 Intel Foundry (Sending Site) A , UI | 20 | 4 |

| 5 | Slide_13_-Detail-out_on_TM_Embedded_Steps | Slide_13-_Detail-out_on_TM_Embedded_Steps | Boundary Apps, External Partners/ B2B

, SAP S/4 (Intel Foundry)

| 19 | 13 |

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_CMMS — E2E_118F__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-_with_CMMS

Swim Lanes: Boundary Apps · SAP S/4 Intel Foundry (Receiving Company) B · SAP S/4 Intel Foundry (Sending Company) A

| Tasks: 19 | Gateways: 3

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["Initiate iSTART Approval Process (Factory Team)​"] n2["Send CMMS (Asset Transfer)"] n3["Initiate Asset Transfer Process"] n17["fa:fa-user Return EQ on WO – Return Reason Code Transfer in UI Determine Final Asset or..."] n20(["fa:fa-play Initiate Asset Transfer Request"]) n21(["fa:fa-play startEvent"]) n22(["fa:fa-stop endEvent"]) end subgraph lane_1["SAP S/4 Intel Foundry (Receiving Company) B "] n15["Acquire Asset in Receiving Company"] n16["Update maintenance plant and location after transfer completed in Equipment..."] n23(["fa:fa-stop Asset Received at Receiving Company Code"]) end subgraph lane_2["SAP S/4 Intel Foundry (Sending Company) A "] n4["Initiate Inter-Company Asset Transfer"] n5["Update Transfer Details and Shipment Flag"] n6["Validate Transfer"] n7["Request Submitted for Approval"] n8["Update ISM Number in request line of AMT Table"] n9["TM Embedded"] n10["Generate Shipping/ Commercial Docs"] n11["Post Goods Issue Against ISM Delivery Doc"] n12["Approve Asset Transfer Request"] n13["Post Financial Entry (Via Batch Job)"] n14["Retire Asset in Sending Company"] n18["fa:fa-user Approve via My Inbox App"] n19["fa:fa-user Generate ISM Number (ZISM Delivery Doc)"] n24["Detail-out on TM Embedded Steps"] n25{{"fa:fa-code-branch Shipment Flag?"}} n26{{"fa:fa-arrows-alt parallelGateway"}} n27{{"fa:fa-arrows-alt inclusiveGateway"}} end n4 --> n5 n5 --> n6 n6 --> n7 n26 --> n8 n26 --> n9 n9 --> n24 n8 --> n10 n10 --> n11 n11 --> n27 n27 --> n12 n26 --> n27 n12 --> n13 n13 --> n14 n14 --> n15 n3 --> n2 n20 --> n1 n15 --> n16 n16 --> n23 n1 --> n22 n21 --> n3 n25 -->|"No"| n27 n7 --> n18 n18 --> n25 n25 -->|"Yes"| n19 n19 --> n26 n2 --> n17 n17 --> n4 class n17 userTask class n18 userTask class n19 userTask class n20 startEvt class n21 startEvt class n22 endEvt class n23 endEvt class n24 startEvt class n25 gateway class n26 gateway class n27 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.2 E2E_118G__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_CMM — E2E_118G__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_CMM

Swim Lanes: Boundary Apps · SAP S/4 Intel Foundry (Receiving Site) B · SAP S/4 Intel Foundry (Sending Site) A

| Tasks: 19 | Gateways: 3

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["Initiate iSTART Approval Process (Factory Team)​"] n2["Send CMMS (Asset Transfer)"] n3["Initiate Asset Transfer Process"] n17["fa:fa-user Return EQ on WO – Return Reason Code Transfer in UI Determine Final Asset or..."] n20(["fa:fa-play Initiate Asset Transfer Request"]) n21(["fa:fa-play startEvent"]) n22(["fa:fa-stop endEvent"]) end subgraph lane_1["SAP S/4 Intel Foundry (Receiving Site) B "] n15["Asset Acquired in Receiving Site"] n16["Update maintenance plant and location after transfer completed in Equipment..."] n23(["fa:fa-stop Asset Received at Receiving Company Code"]) end subgraph lane_2["SAP S/4 Intel Foundry (Sending Site) A "] n4["Initiate Intra-Company Asset Transfer"] n5["Update Transfer Details and Shipment Flag"] n6["Validate Transfer"] n7["Request Submitted for Approval"] n8["Update ISM Number in request line of AMT Table"] n9["TM Embedded"] n10["Generate Shipping/ Commercial Docs"] n11["Post Goods Issue Against ISM Delivery Doc"] n12["Approve Asset Transfer Request"] n13["Post Financial Entry (Via Batch Job)"] n14["Asset Retired in Sending Site"] n18["fa:fa-user Approve via My Inbox App"] n19["fa:fa-user Generate ISM Number (ZISM Delivery Doc)"] n24["Detail-out on TM Embedded Steps"] n25{{"fa:fa-code-branch Shipment Flag?"}} n26{{"fa:fa-arrows-alt parallelGateway"}} n27{{"fa:fa-arrows-alt inclusiveGateway"}} end n4 --> n5 n5 --> n6 n6 --> n7 n26 --> n8 n26 --> n9 n8 --> n10 n10 --> n11 n11 --> n27 n27 --> n12 n26 --> n27 n12 --> n13 n13 --> n14 n14 --> n15 n3 --> n2 n20 --> n1 n15 --> n16 n16 --> n23 n1 --> n22 n21 --> n3 n25 -->|"No"| n27 n9 --> n24 n2 --> n17 n17 --> n4 n7 --> n18 n18 --> n25 n25 -->|"Yes"| n19 n19 --> n26 class n17 userTask class n18 userTask class n19 userTask class n20 startEvt class n21 startEvt class n22 endEvt class n23 endEvt class n24 startEvt class n25 gateway class n26 gateway class n27 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.3 E2E_118H__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_iSTART — E2E_118H__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-_with_iSTART

Swim Lanes: Boundary Apps · SAP S/4 Intel Foundry (Receiving Company B · SAP S/4 Intel Foundry (Sending Company) A · UI | Tasks: 20 | Gateways: 4

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["iSTART sends an email notification to the requestor, instructing them to..."] n2["iSTART sends an email notification to the requestor, instructing them..."] n16["fa:fa-user Initiate iSTART Approval Process (Factory Team)​\"] n23{{"fa:fa-code-branch Approval"}} end subgraph lane_1["SAP S/4 Intel Foundry (Receiving Company B "] n13["Asset Acquired in Receiving Company"] n14["Update maintenance plant and location after transfer completed in Equipment..."] n21(["fa:fa-stop Asset Received at Receiving Company Code"]) end subgraph lane_2["SAP S/4 Intel Foundry (Sending Company) A "] n3["Update Transfer Details and Shipment Flag"] n4["Validate Transfer"] n5["Request Submitted for Approval"] n6["Update ISM Number in request line of AMT Table"] n7["TM Embedded"] n8["Generate Shipping/ Commercial Docs"] n9["Post Goods Issue Against ISM Delivery Doc"] n10["Approve Asset Transfer Request"] n11["Post Financial Entry (Via Batch Job)"] n12["Asset Retired in Sending Company"] n17["fa:fa-user Approve via My Inbox App"] n18["fa:fa-user Generate ISM Number (ZISM Delivery Doc)"] n19["fa:fa-user Initiate Intra-Company Asset Transfer"] n22["Detail-out on TM Embedded Steps"] n24{{"fa:fa-code-branch Shipment Flag?"}} n25{{"fa:fa-arrows-alt parallelGateway"}} n26{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_3["UI"] n15["Trigger iSTART process"] n20["fa:fa-user Initiate Work Order"] end n3 --> n4 n4 --> n5 n25 --> n6 n25 --> n7 n6 --> n8 n8 --> n9 n9 --> n26 n26 --> n10 n25 --> n26 n10 --> n11 n11 --> n12 n12 --> n13 n13 --> n14 n14 --> n21 n24 -->|"No"| n26 n7 --> n22 n5 --> n17 n17 --> n24 n24 -->|"Yes"| n18 n18 --> n25 n15 --> n16 n16 --> n23 n23 --> n1 n23 --> n2 n20 --> n15 n3 -->|"Manual Update"| n20 n6 --> n20 n20 -->|"Interface"| n19 n19 --> n3 class n16 userTask class n17 userTask class n18 userTask class n19 userTask class n20 userTask class n21 endEvt class n22 startEvt class n23 gateway class n24 gateway class n25 gateway class n26 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.4 E2E_118I__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_iST — E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_iST

Swim Lanes: Boundary Apps · SAP S/4 Intel Foundry (Receiving Site) B · SAP S/4 Intel Foundry (Sending Site) A · UI | Tasks: 20 | Gateways: 4

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["iSTART sends an email notification to the requestor, instructing them to..."] n2["iSTART sends an email notification to the requestor, instructing them..."] n17["fa:fa-user Initiate iSTART Approval Process (Factory Team)​\"] n23{{"fa:fa-code-branch Approval"}} end subgraph lane_1["SAP S/4 Intel Foundry (Receiving Site) B "] n14["Asset Acquired in Receiving Site"] n15["Update maintenance plant and location after transfer completed in Equipment..."] n21(["fa:fa-stop Asset Received at Receiving Company Code"]) end subgraph lane_2["SAP S/4 Intel Foundry (Sending Site) A "] n3["Update Transfer Details and Shipment Flag"] n4["Validate Transfer"] n5["Request Submitted for Approval"] n6["Update ISM Number in request line of AMT Table"] n7["TM Embedded"] n8["Generate Shipping/ Commercial Docs"] n9["Post Goods Issue Against ISM Delivery Doc"] n10["Approve Asset Transfer Request"] n11["Post Financial Entry (Via Batch Job)"] n12["Asset Retired in Sending Site"] n13["Initiate Intra-Company Asset Transfer"] n18["fa:fa-user Approve via My Inbox App"] n19["fa:fa-user Generate ISM Number (ZISM Delivery Doc)"] n22["Detail-out on TM Embedded Steps"] n24{{"fa:fa-code-branch Shipment Flag?"}} n25{{"fa:fa-arrows-alt parallelGateway"}} n26{{"fa:fa-arrows-alt inclusiveGateway"}} end subgraph lane_3["UI"] n16["Trigger iSTART process"] n20["fa:fa-user Initiate UI Work Order"] end n3 --> n4 n4 --> n5 n25 --> n6 n25 --> n7 n6 --> n8 n8 --> n9 n9 --> n26 n26 --> n10 n25 --> n26 n10 --> n11 n11 --> n12 n12 --> n14 n14 --> n15 n15 --> n21 n24 -->|"No"| n26 n7 --> n22 n5 --> n18 n18 --> n24 n24 -->|"Yes"| n19 n19 --> n25 n16 --> n17 n17 --> n23 n23 --> n1 n23 --> n2 n20 --> n16 n3 -->|"Manual Update"| n20 n6 --> n20 n20 -->|"Interface"| n13 n13 --> n3 class n17 userTask class n18 userTask class n19 userTask class n20 userTask class n21 endEvt class n22 startEvt class n23 gateway class n24 gateway class n25 gateway class n26 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.5 Slide_13_-Detail-out_on_TM_Embedded_Steps — Slide_13-_Detail-out_on_TM_Embedded_Steps

Swim Lanes: Boundary Apps · External Partners/ B2B · SAP S/4 (Intel Foundry)

| Tasks: 19 | Gateways: 13

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"] n15["CTSI Carrier Invoice Reconciliation/ Dispute Management"] end subgraph lane_1["External Partners/ B2B "] n16["Send to SAP B4NL"] n17["Notify carrier"] n18["Capture Execution events via BN4L-GTT"] n19["Receive Physical receipt at receiver company location"] n22(["fa:fa-play Data needs to be Sent to B4NL"]) n36{{"fa:fa-arrows-alt parallelGateway"}} n37{{"fa:fa-arrows-alt parallelGateway"}} n38{{"fa:fa-arrows-alt parallelGateway"}} end subgraph lane_2["SAP S/4 (Intel Foundry) "] n1["Create ZISM Outbound Delivery (S/4)"] n2["Create/Update Freight Unit and Freight Order"] n3["Perform Carrier Selection and Calculate Charges"] n4["Send Rates/Charges/Au to HAWB assignment: Freight forwarders (Within TM)"] n5["Ship (Goods Issue)"] n6["Execute Freight Order and Update Status Post GI"] n7["Create and Update Freight Settlement Document"] n8["Create Service PO/ Entry Sheet"] n9["Post Accrual to Freight Expense Account(s)"] n10["Allocate Freight Costs to Delivery Items (CO/PA) or Material Valuation"] n11["Pick and Pack Updates (IM)"] n12["Update Maintenance Plant and Location after Transfer Completed in Equipment..."] n13["Start tendering/Subcontracting Carrier Selection"] n14["Receive reconciled Carrier Invoice(s)"] n20(["fa:fa-play Rates/Charges need to be Sent"]) n21(["fa:fa-play Initiate Tendering"]) n23(["fa:fa-stop Accrual Posted and Freight Costs Allocated"]) n24(["fa:fa-stop Asset Master Updated with Location"]) n25["Intra-Company Asset Transfer using AMT and ISM Fiori Apps (Same Company Code)"] n26["Inter-Company Asset Transfer using AMT and ISM Fiori Apps"] n27{{"fa:fa-code-branch exclusiveGateway"}} n28{{"fa:fa-arrows-alt parallelGateway"}} n29{{"fa:fa-arrows-alt parallelGateway"}} n30{{"fa:fa-arrows-alt parallelGateway"}} n31{{"fa:fa-arrows-alt parallelGateway"}} n32{{"fa:fa-arrows-alt parallelGateway"}} n33{{"fa:fa-arrows-alt parallelGateway"}} n34{{"fa:fa-arrows-alt parallelGateway"}} n35{{"fa:fa-arrows-alt parallelGateway"}} n39{{"fa:fa-arrows-alt inclusiveGateway"}} end n2 --> n28 n5 --> n34 n22 --> n36 n6 --> n31 n31 --> n35 n36 --> n16 n28 --> n39 n7 --> n8 n8 --> n32 n32 --> n9 n32 --> n10 n10 --> n33 n9 --> n33 n39 --> n3 n17 --> n38 n37 --> n18 n34 --> n6 n38 --> n19 n33 --> n23 n37 --> n39 n35 --> n7 n4 --> n29 n20 --> n4 n29 --> n39 n1 --> n2 n11 --> n5 n16 --> n37 n3 --> n11 n31 --> n36 n37 --> n17 n38 --> n30 n19 --> n12 n12 --> n24 n14 --> n35 n13 --> n39 n21 --> n13 n28 --> n30 n30 --> n15 n26 --> n27 n25 --> n27 n27 --> n1 n18 -->|"POD Receipt Events (via BN4L-GTT)"| n34 n29 -->|"Freight forwarder Rates to CTSI"| n30 n15 -->|"FO (Freight Order) & HAWB (House Airway Bill) Mapping"| n14 class n20 startEvt class n21 startEvt class n22 startEvt class n23 endEvt class n24 endEvt class n25 startEvt class n26 startEvt class n27 gateway class n28 gateway class n29 gateway class n30 gateway 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
👁 View Diagram

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
Boundary Apps
E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_CMMS, E2E_118G__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)-_with_CMM, E2E_118H__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-with_iSTART, E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_iST,
SAP S/4 Intel Foundry

(Receiving Company) B

| E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-_with_CMMS, | | | SAP S/4 Intel Foundry

(Sending Company) A

| E2E_118F__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_CMMS, E2E_118H__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-_with_iSTART, | | | SAP S/4 Intel Foundry

(Receiving Site) B

| E2E_118G__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_CMM, E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_iST, | | | SAP S/4 Intel Foundry

(Sending Site) A

| E2E_118G__Intra-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps(Same_Company_Code)-_with_CMM, E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)_-_with_iST, | | | SAP S/4 Intel Foundry

(Receiving Company B

| E2E_118H__Inter-Company_Asset_Transfer_using_AMT_&ISM_Fiori_Apps-with_iSTART, | | | UI | E2E_118H__Inter-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps-with_iSTART, E2E_118I__Intra-Company_Asset_Transfer_using_AMT&ISM_Fiori_Apps(Same_Company_Code)-_with_iST, | | | Boundary Apps | Slide_13-Detail-out_on_TM_Embedded_Steps | | | External Partners/ B2B | Slide_13-Detail-out_on_TM_Embedded_Steps | | | SAP S/4 (Intel Foundry) | Slide_13-_Detail-out_on_TM_Embedded_Steps | |

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 E2E118CDACL_e_g_Azure_SQL[" "] direction TB E2E118CDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E118CDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E118CDAA_e_g_XEUS -.-> E2E118CDAD_e_g_Azure_SQL end style E2E118CDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E118CDACL_e_g_SAP_HANA[" "] direction TB E2E118CDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E118CDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E118CDAA_e_g_MES_300 -.-> E2E118CDAD_e_g_SAP_HANA end style E2E118CDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E118CDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E118CDAD_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 E2E118FDACL_e_g_Azure_SQL[" "] direction TB E2E118FDAA_e_g_XEUS["e.g. XEUS"]:::appBox E2E118FDAD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud E2E118FDAA_e_g_XEUS -.-> E2E118FDAD_e_g_Azure_SQL end style E2E118FDACL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px subgraph E2E118FDACL_e_g_SAP_HANA[" "] direction TB E2E118FDAA_e_g_MES_300["e.g. MES 300"]:::appBox E2E118FDAD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData E2E118FDAA_e_g_MES_300 -.-> E2E118FDAD_e_g_SAP_HANA end style E2E118FDACL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px E2E118FDAD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| E2E118FDAD_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-118.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 E2E118CLN_Boundary_Applications[" Boundary Applications"] direction LR E2E118C_e_g_MES_300["📦 e.g. MES 300"]:::app E2E118C_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E118CMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E118CDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E118C_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E118CMW_e_g_Azure_Service_Bus E2E118CMW_e_g_Azure_Service_Bus --> E2E118C_e_g_XEUS style E2E118CLN_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-118.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 E2E118FLN_Boundary_Applications[" Boundary Applications"] direction LR E2E118F_e_g_MES_300["📦 e.g. MES 300"]:::app E2E118F_e_g_XEUS["📦 e.g. XEUS"]:::app end E2E118FMW_e_g_Azure_Service_Bus["🔗 e.g. Azure Service Bus"]:::middleware E2E118FDE_e_g_Cost_Element>"📄 e.g. Cost Element
e.g. CSV / IDoc / JSON"]:::data E2E118F_e_g_MES_300 -->|"e.g. Direct / API / File"| E2E118FMW_e_g_Azure_Service_Bus E2E118FMW_e_g_Azure_Service_Bus --> E2E118F_e_g_XEUS style E2E118FLN_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 E2E118CPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E118CPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E118CPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E118CPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E118CPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E118CPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E118CPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E118CPLP_e_g_Azure_PaaS subgraph E2E118CPLLegend["📐 PLATFORM LEGEND"] direction LR E2E118CPLLC["☁️ Cloud"] E2E118CPLLS["🔮 SaaS"] E2E118CPLLO["🏢 On-Prem"] E2E118CPLLD["💾 Data Platform"] E2E118CPLLM["🔗 Middleware"] end style E2E118CPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E118CPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E118CPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E118CPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E118CPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E118CPLLM 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 E2E118FPLP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"] direction LR E2E118FPLA_e_g_XEUS["e.g. XEUS"]:::appBox end style E2E118FPLP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C subgraph E2E118FPLP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"] direction LR E2E118FPLA_e_g_MES_300["e.g. MES 300"]:::appBox end style E2E118FPLP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 E2E118FPLP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| E2E118FPLP_e_g_Azure_PaaS subgraph E2E118FPLLegend["📐 PLATFORM LEGEND"] direction LR E2E118FPLLC["☁️ Cloud"] E2E118FPLLS["🔮 SaaS"] E2E118FPLLO["🏢 On-Prem"] E2E118FPLLD["💾 Data Platform"] E2E118FPLLM["🔗 Middleware"] end style E2E118FPLLegend fill:#F5F5F5,stroke:#999,stroke-width:1px style E2E118FPLLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C style E2E118FPLLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C style E2E118FPLLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20 style E2E118FPLLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40 style E2E118FPLLM 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-118 — Architecture Document (TOGAF BDAT) · End-to-End Integrated Processes · Generated: April 2026