🏠 Home OTC-IF 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

LO-190 — Ship/Deliver Orders - OTC (IF)

Architecture Document (TOGAF BDAT)

Order To Cash (IF) (OTC-IF) Tower
Capability LO-190 · LO Logistics Management Outbound - OTC (IF)

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 LO-190 Ship/Deliver Orders - OTC (IF) within the IAO program. It includes 3 BPMN process diagram(s) in Section 3.

Dimension Value
Tower Order To Cash (IF) (OTC-IF)
Process Group LO Logistics Management Outbound - OTC (IF)
Capability LO-190 - Ship/Deliver Orders - OTC (IF)
Release R1 – R5
Total Systems 0
System Status 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM
RICEFW Objects 6 Enhancements, 2 Forms, 1 Workflows

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 Order To Cash (IF)
L1 Process LO Logistics Management Outbound - OTC (IF)
L2 Capability LO-190 - Ship/Deliver Orders - OTC (IF)

2.2 Business Drivers

# Driver Description Strategic Alignment Priority
1 Foundry Customer Order Digitization Digitize end-to-end order capture, pricing, and fulfillment for Intel Foundry customers IDM 2.0 Foundry Revenue High
2 Global Trade Compliance Automation Automate export/import compliance screening and customs declarations Global Trade Operations High
3 Revenue Recognition Accuracy Ensure compliant revenue recognition aligned with ASC 606 through S/4 HANA billing Finance & Compliance Medium
4 LO-190 Process Migration Migrate Ship/Deliver Orders - OTC (IF) business processes and 0 integrated systems from legacy to S/4 HANA target architecture IDM 2.0 Order Management (Intel Foundry) High

2.3 Success Criteria

Metric Target Measure Baseline Owner
Order-to-Cash Cycle Time < 5 business days End-to-end cycle from order capture to cash application 8 business days (legacy) OTC Process Owner
Trade Compliance Screening Rate 100% Orders screened for denied parties and export controls 99.2% (current) Global Trade Manager
Billing Accuracy > 99.8% Invoices generated without errors requiring credit/re-bill 98.5% (current) Billing Manager
LO-190 Migration Completeness 100% flow chains validated All 0 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 LO-190 Ship/Deliver Orders - OTC (IF).

# Step ID Process Name Lanes Tasks Gateways
1 LO-190-080_Record_Carrier_Information_-OTC(IF) LO-190-080_Record_Carrier_Information_-OTC(IF) Load Planner 15 3
2 LO-190-100_Ship_Order_-OTC(IF) LO-190-100_Ship_Order_-OTC(IF) Functional Analyst 12 5
3 LO-190-120_Send_Advanced_Shipping_Notice_-OTC(IF) LO-190-120_Send_Advanced_Shipping_Notice_-OTC(IF) Warehouse Operator 4 2

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 LO-190-080_Record_Carrier_Information_-OTC(IF) — LO-190-080_Record_Carrier_Information_-OTC(IF)

Swim Lanes: Load Planner | Tasks: 15 | 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 TD 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["Load Planner"] n1[["fa:fa-cog Trigger NCRM"]] n2[["fa:fa-cog Generate Carrier List and Send RFQ"]] n3[["fa:fa-cog Convert RFQs into Email and Send to Carrier(Included Hyperlink to BN4L 0"]] n4[["fa:fa-cog Receive Carrier Response"]] n5[["fa:fa-cog Verify Responses in LOM and Send for Approval (Best Carrier Selected)"]] n6[["fa:fa-cog Trigger Approval Workflow"]] n7[["fa:fa-cog Show RFQs in FO and Send Notification Mail to LOM"]] n8[["fa:fa-cog Trigger Mail to Selected Carrier for Final Confirmation"]] n9[["fa:fa-cog Receive Confirmation from Carrier"]] n10[["fa:fa-cog Update Carrier on FO"]] n11[["fa:fa-cog Select Other Response/Trigger Tendering Again"]] n12[["fa:fa-cog Trigger Multibid"]] n13[["fa:fa-cog Trigger Spot Bid"]] n14[["fa:fa-cog Trigger Rejection Mail to Rejected Carrier"]] n15[["fa:fa-cog Trigger Email to LOM"]] n16["Ship Order - OTC (IF)_R3"] n17["Determine Mode of Transportation Carrier OTC (IF)_R3"] n18{{"fa:fa-code-branch Approved?"}} n19{{"fa:fa-code-branch FO Pickup date 5 Days?"}} n20{{"fa:fa-code-branch exclusiveGateway"}} end n17 --> n1 n3 --> n4 n5 --> n6 n6 --> n18 n7 --> n8 n8 --> n9 n9 --> n10 n10 --> n16 n1 --> n19 n13 --> n20 n20 --> n2 n12 --> n20 n19 -->|"Yes"| n12 n19 -->|"No"| n13 n18 -->|"Yes"| n7 n2 --> n3 n14 --> n11 n4 --> n15 n15 --> n5 n18 -->|"No"| n14 n11 --> n20 class n1 serviceTask class n2 serviceTask class n3 serviceTask class n4 serviceTask class n5 serviceTask class n6 serviceTask class n7 serviceTask class n8 serviceTask class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 serviceTask class n14 serviceTask class n15 serviceTask class n16 startEvt class n17 startEvt class n18 gateway class n19 gateway class n20 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.2 LO-190-100_Ship_Order_-OTC(IF) — LO-190-100_Ship_Order_-OTC(IF)

Swim Lanes: Functional Analyst | Tasks: 12 | Gateways: 5

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 TD 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["Functional Analyst"] n1["fa:fa-user Send Loading Instruction to EWM"] n2["fa:fa-user Resolve Block Reason"] n3["fa:fa-user Assign HAWB Number Manually"] n4[["fa:fa-cog Get FO Ready for Transportation Execution"]] n5[["fa:fa-cog Check FO Execution Status"]] n6[["fa:fa-cog Select Carrier"]] n7[["fa:fa-cog Check if Execution Block in Freight Order"]] n8[["fa:fa-cog Propagate GTS Delivery Level Blocks to TM FU as Planning and Execution Block"]] n9[["fa:fa-cog Receive 'Loading End' and 'Departure Events' from EWM in FO"]] n10[["fa:fa-cog Perform EWM Integration"]] n11[["fa:fa-cog Update FU and FO With Tracking ID From Delivery"]] n12[["fa:fa-cog Update Freight Order With HAWB Number"]] n13(["fa:fa-stop Freight Order Delivered"]) n14["Coordinate Transportation"] n15["Process Delivery of Line Items"] n16["Determine Mode of Transportation/Carrier - OTC (IF)"] n17{{"fa:fa-code-branch Is There a Block?"}} n18{{"fa:fa-code-branch exclusiveGateway"}} n19{{"fa:fa-code-branch exclusiveGateway"}} n20{{"fa:fa-code-branch exclusiveGateway"}} n21{{"fa:fa-code-branch HAWB Assignment?"}} end n15 --> n8 n14 --> n18 n18 --> n7 n7 --> n17 n2 --> n19 n5 --> n13 n19 --> n6 n1 --> n4 n9 --> n5 n8 --> n18 n4 --> n9 n10 --> n1 n17 -->|"No"| n19 n11 --> n12 n3 --> n20 n12 --> n20 n20 --> n10 n6 --> n21 n17 -->|"Yes"| n2 n21 -->|"Freight Forwarder"| n3 n21 -->|"Integrator"| n11 n16 --> n18 class n1 userTask class n2 userTask class n3 userTask class n4 serviceTask class n5 serviceTask class n6 serviceTask class n7 serviceTask class n8 serviceTask class n9 serviceTask class n10 serviceTask class n11 serviceTask class n12 serviceTask class n13 endEvt class n14 startEvt class n15 startEvt class n16 startEvt class n17 gateway class n18 gateway class n19 gateway class n20 gateway class n21 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.3 LO-190-120_Send_Advanced_Shipping_Notice_-OTC(IF) — LO-190-120_Send_Advanced_Shipping_Notice_-OTC(IF)

Swim Lanes: Warehouse Operator | Tasks: 4 | Gateways: 2

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 TD 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["Warehouse Operator"] n1[["fa:fa-cog Update Post Goods Issue"]] n2[["fa:fa-cog Update Inventory Status"]] n3[["fa:fa-cog Send Advanced Shipping Notice"]] n4[["fa:fa-cog E-Mail Alert to IT and Business"]] n5(["fa:fa-stop ASN Sent"]) n6(["fa:fa-stop E-Mail Alert Sent"]) n7["Update/Reset Cummulative Shipped for Customers - OTC (IF)_R3"] n8["Process Goods Issue for Stock Material - OTC (IF)_R3"] n9{{"fa:fa-code-branch Delivery Stuck in Queue and Update in S/4 Fails?"}} n10{{"fa:fa-arrows-alt parallelGateway"}} end n1 --> n10 n10 --> n2 n10 --> n3 n4 --> n6 n9 -->|"Yes"| n4 n3 --> n5 n8 --> n9 n2 --> n7 n9 -->|"No"| n1 class n1 serviceTask class n2 serviceTask class n3 serviceTask class n4 serviceTask class n5 endEvt class n6 endEvt class n7 startEvt class n8 startEvt class n9 gateway class n10 gateway
👁 View Diagram

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
Load Planner LO-190-080_Record_Carrier_Information_-OTC(IF),
Functional Analyst LO-190-100_Ship_Order_-OTC(IF),
Warehouse Operator LO-190-120_Send_Advanced_Shipping_Notice_-OTC(IF)

4. Data Architecture (TOGAF “D”)

4.1 Data Flows — Source to Target

Data flows with DB platform details will be populated when tower architects complete the extended flow template columns (42-47) via the Input Portal.

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.3 Data Lineage

Data lineage (source schema/object → target schema/object mappings) will be populated when tower architects provide validated schema details via the Input Portal.

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.4 Component Overview

System Inventory

System IAPM ID Status

5.5 RICEFW Inventory

Object ID Type Description Status Source → Target Middleware Complexity
OTCW0638 Workflow Dispute Write-off Workflow 10. Object Complete NA 03.Medium
OTCF0431 Form Generate Custom Late Payment Interest Charge Output Form 10. Object Complete NA → NA NA 03.Medium
OTCF0290 Form Dunning output form customization 10. Object Complete NA → NA NA 03.Medium
OTCE1662 Enhancement BADI Enhancement for Dispute Write off (workflow Trigger) 10. Object Complete NA 03.Medium
OTCE1658 Enhancement Dispute Write-off Enhancement 10. Object Complete NA 04.Low
OTCE1625 Enhancement Credit hold release dashboard at line-item level 10. Object Complete NA → NA NA 01.Very High
OTCE0614_IF Enhancement Implement Standard Credit/Collection BADI 10. Object Complete NA 04.Low
OTCE0235 Enhancement Credit and Collections - Credit Check Step Configuration 10. Object Complete NA → NA NA 04.Low
OTCE0234 Enhancement Implement mapping between customer’s risk class and credit check steps 10. Object Complete NA → NA NA 03.Medium

Summary: 6 Enhancements, 2 Forms, 1 Workflows

5.6 Integration Patterns

Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.

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.

Platform Inventory

Platform inventory will be populated when tower architects provide validated technology platform details via the extended flow template.

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

ID Description FS TDD Build FUT Status
OTCW0638 Dispute Write-off Workflow 2025-08-08 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-11-28 00:00:00 (100%) 2. At Risk
OTCF0431 Generate Custom Late Payment Interest Charge Output Form 2024-08-30 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-05-09 00:00:00 (100%)
OTCF0290 Dunning output form customization 2024-07-18 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-03-14 00:00:00 (100%)
OTCE1662 BADI Enhancement for Dispute Write off (workflow Trigger) 2025-11-13 00:00:00 (100%) 2025-11-21 00:00:00 (100%) 2025-11-21 00:00:00 (100%) 2025-11-28 00:00:00 (100%) 2. At Risk
OTCE1658 Dispute Write-off Enhancement 2025-11-13 00:00:00 (100%) 2025-11-28 00:00:00 (100%) 2025-11-28 00:00:00 (100%) 2025-11-28 00:00:00 (100%) 2. At Risk
OTCE1625 Credit hold release dashboard at line-item level 2024-07-12 00:00:00 (100%) 2025-09-05 00:00:00 (100%) 2025-09-05 00:00:00 (100%) 2026-02-04 00:00:00 (100%) 1. On Track
OTCE0614_IF Implement Standard Credit/Collection BADI 2025-03-14 00:00:00 (100%) 2025-08-13 00:00:00 (100%) 2025-04-18 00:00:00 (100%) 2025-09-10 00:00:00 (100%)
OTCE0235 Credit and Collections - Credit Check Step Configuration 2024-07-19 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-01-31 00:00:00 (100%) 2025-06-06 00:00:00 (100%)
OTCE0234 Implement mapping between customer’s risk class and credit check steps 2024-07-19 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2025-02-14 00:00:00 (100%)

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

LO-190 — Architecture Document (TOGAF BDAT) · Order To Cash (IF) · Generated: April 2026