Order To Cash (IP) (OTC-IP) Tower
Capability LO-160 · LO Logistics Management Outbound - OTC (IP)
IAO Program · R1 – R5
Generated: April 2026
Sajiv Francis
IAO Architecture Pipeline — Intel Confidential
This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for LO-160 Pick Orders - OTC (IP) within the IAO program. It includes 7 BPMN process diagram(s) in Section 3.
| Dimension | Value |
|---|---|
| Tower | Order To Cash (IP) (OTC-IP) |
| Process Group | LO Logistics Management Outbound - OTC (IP) |
| Capability | LO-160 - Pick Orders - OTC (IP) |
| Release | R1 – R5 |
| Total Systems | 0 |
| System Status | 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM |
| RICEFW Objects | 6 Conversions, 3 Enhancements, 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.
| Level | Value |
|---|---|
| L0 Tower | Order To Cash (IP) |
| L1 Process | LO Logistics Management Outbound - OTC (IP) |
| L2 Capability | LO-160 - Pick Orders - OTC (IP) |
| # | Driver | Description | Strategic Alignment | Priority |
|---|---|---|---|---|
| 1 | IP Order Management Transformation | Transform Intel Products order management onto S/4 HANA with integrated pricing and ATP | IDM 2.0 Products Revenue | High |
| 2 | Customer Experience Improvement | Reduce order processing time and improve order visibility for IP customers | Customer Centricity | High |
| 3 | Returns & Rebate Automation | Automate returns processing, rebate management, and chargeback handling | Revenue Assurance | Medium |
| 4 | LO-160 Process Migration | Migrate Pick Orders - OTC (IP) business processes and 0 integrated systems from legacy to S/4 HANA target architecture | IDM 2.0 Order Management (Intel Products) | High |
| Metric | Target | Measure | Baseline | Owner |
|---|---|---|---|---|
| Order Processing Time | < 2 hours | Time from order receipt to order confirmation | 6 hours (current) | Order Management Lead |
| Customer Credit Decision Time | < 15 minutes | Automated credit check and approval for standard orders | 2 hours (manual) | Credit Manager |
| Returns Processing Cycle | < 3 business days | End-to-end returns receipt to credit memo issuance | 7 business days (current) | Returns Manager |
| LO-160 Migration Completeness | 100% flow chains validated | All 0 flow chains verified in target state | 0% (pre-migration) | Tower Architect |
| Document | Description |
|---|---|
| Business Architecture | Included in this document (Section 3) — process flows from BPMN diagrams |
| This Document | Full BDAT Architecture — Business + Data + Application + Technology |
This capability includes 7 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for LO-160 Pick Orders - OTC (IP).
| # | Step ID | Process Name | Lanes | Tasks | Gateways |
|---|---|---|---|---|---|
| 1 | LO-160-020_Plan_Daily_Pick_Flow_-OTC(IP) | LO-160-020_Plan_Daily_Pick_Flow_-OTC(IP) | Warehouse Operator | 3 | 0 |
| 2 | LO-160-030_Consolidate_Appropriate_Pick_Items_-OTC(IP) | LO-160-030_Consolidate_Appropriate_Pick_Items_-OTC(IP) | Warehouse Operator | 1 | 0 |
| 3 | LO-160-040_Generate_Pick_Tickets_-OTC(IP) | LO-160-040_Generate_Pick_Tickets_-OTC(IP) | Warehouse Operator | 1 | 0 |
| 4 | LO-160-050_Pick_Order_Items_-OTC(IP) | LO-160-050_Pick_Order_Items_-OTC(IP) | Warehouse Operator | 2 | 2 |
| 5 | LO-160-070_Note_and_Record_Exceptions_-OTC(IP) | LO-160-070_Note_and_Record_Exceptions_-OTC(IP) | Warehouse Operator | 3 | 3 |
| 6 | LO-160-080_Confirm_Quantity_and_Location_Picked_-OTC(IP) | LO-160-080_Confirm_Quantity_and_Location_Picked_-OTC(IP) | Warehouse Operator | 1 | 1 |
| 7 | LO-160-090_Transport_Product_to_Staging_Area_-OTC(IP) | LO-160-090_Transport_Product_to_Staging_Area_-OTC(IP) | Warehouse Operator | 2 | 0 |
Swim Lanes: Warehouse Operator | Tasks: 3 | Gateways: 0
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 1 | Gateways: 0
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 1 | Gateways: 0
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 2 | Gateways: 2
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 3 | Gateways: 3
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 1 | Gateways: 1
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
Swim Lanes: Warehouse Operator | Tasks: 2 | Gateways: 0
Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process
| Role / Lane | Processes Involved | Description |
|---|---|---|
| Warehouse Operator | LO-160-020_Plan_Daily_Pick_Flow_-OTC(IP), LO-160-030_Consolidate_Appropriate_Pick_Items_-OTC(IP), LO-160-040_Generate_Pick_Tickets_-OTC(IP), LO-160-050_Pick_Order_Items_-OTC(IP), LO-160-070_Note_and_Record_Exceptions_-OTC(IP), LO-160-080_Confirm_Quantity_and_Location_Picked_-OTC(IP), LO-160-090_Transport_Product_to_Staging_Area_-OTC(IP) |
Data flows with DB platform details will be populated when tower architects complete the extended flow template columns (42-47) via the Input Portal.
DATA ARCHITECTURE — Database-to-database data flows. Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.
Data lineage (source schema/object → target schema/object mappings) will be populated when tower architects provide validated schema details via the Input Portal.
Data-centric RICEFW objects (Reports and Conversions) from the Object Tracker:
| Object ID | Type | Description | Status | Source | Target | Complexity |
|---|---|---|---|---|---|---|
| OTCC1341 | Conversion | Payer Profile Data Conversion | 10. Object Complete | 03.Medium | ||
| OTCC1340 | Conversion | Payer Segment Data Conversion | 10. Object Complete | 03.Medium | ||
| OTCC1339 | Conversion | Payer Relationship Data Conversion | 10. Object Complete | 03.Medium | ||
| OTCC0803 | Conversion | Open Credit Case Conversion | 10. Object Complete | 02.High | ||
| OTCC0679 | Conversion | Open Dispute Case Conversion | 10. Object Complete | 02.High | ||
| OTCC0678 | Conversion | Collection Master Conversion | 10. Object Complete | 02.High |
| 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 |
| System | IAPM ID | Status |
|---|---|---|
| Object ID | Type | Description | Status | Source → Target | Middleware | Complexity |
|---|---|---|---|---|---|---|
| OTCW1683 | Workflow | Additional WRICEF for Credit Limit Request Workflow | 10. Object Complete | NA | 03.Medium | |
| OTCE0737 | Enhancement | Implement Standard BADI to activate Credit Limit Request Workflow | 10. Object Complete | NA | 04.Low | |
| OTCE0614_IP | Enhancement | Implement Standard Credit/Collection BADI | 10. Object Complete | NA | 03.Medium | |
| OTCE0021 | Enhancement | Credit hold release dashboard at line-item level | 10. Object Complete | NA → NA | NA | 01.Very High |
| OTCC1341 | Conversion | Payer Profile Data Conversion | 10. Object Complete | NA | 03.Medium | |
| OTCC1340 | Conversion | Payer Segment Data Conversion | 10. Object Complete | NA | 03.Medium | |
| OTCC1339 | Conversion | Payer Relationship Data Conversion | 10. Object Complete | NA | 03.Medium | |
| OTCC0803 | Conversion | Open Credit Case Conversion | 10. Object Complete | NA | 02.High | |
| OTCC0679 | Conversion | Open Dispute Case Conversion | 10. Object Complete | NA | 02.High | |
| OTCC0678 | Conversion | Collection Master Conversion | 10. Object Complete | NA | 02.High |
Summary: 6 Conversions, 3 Enhancements, 1 Workflows
Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.
TECHNOLOGY / PLATFORM ARCHITECTURE — Platforms (green) host applications (blue). Thick arrows show platform-to-platform integration flows.
Platform inventory will be populated when tower architects provide validated technology platform details via the extended flow template.
| Metric | DEV | QAS | PRD |
|---|---|---|---|
| Transport Requests | — | — | — |
| Custom Code Objects | — | — | — |
| CDS Views | — | — | — |
| Fiori Apps | — | — | — |
| BAdIs / Enhancements | — | — | — |
| 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 |
| 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 |
| ID | Description | FS | TDD | Build | FUT | Status |
|---|---|---|---|---|---|---|
| OTCW1683 | Additional WRICEF for Credit Limit Request Workflow | 2025-12-12 00:00:00 (100%) | 2026-02-04 00:00:00 (100%) | 2026-02-04 00:00:00 (100%) | 2026-03-04 00:00:00 (100%) | 1. On Track |
| OTCE0737 | Implement Standard BADI to activate Credit Limit Request Workflow | 2025-07-11 00:00:00 (100%) | 2025-12-03 00:00:00 (100%) | 2025-12-03 00:00:00 (100%) | 2026-03-04 00:00:00 (100%) | 1. On Track |
| OTCE0614_IP | 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-05 00:00:00 (100%) | |
| OTCE0021 | Credit hold release dashboard at line-item level | 2024-07-19 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 |
| OTCC1341 | Payer Profile Data Conversion | 2025-05-02 00:00:00 (100%) | 2025-06-24 00:00:00 (100%) | 2025-08-01 00:00:00 (100%) | 2025-09-10 00:00:00 (100%) | |
| OTCC1340 | Payer Segment Data Conversion | 2025-05-02 00:00:00 (100%) | 2025-06-24 00:00:00 (100%) | 2025-08-01 00:00:00 (100%) | 2025-09-10 00:00:00 (100%) | 1. On Track |
| OTCC1339 | Payer Relationship Data Conversion | 2025-06-06 00:00:00 (100%) | 2025-10-23 00:00:00 (100%) | 2025-11-05 00:00:00 (100%) | 2025-11-21 00:00:00 (100%) | 4. Completed |
| OTCC0803 | Open Credit Case Conversion | 2025-06-06 00:00:00 (100%) | 2025-10-24 00:00:00 (100%) | 2025-11-05 00:00:00 (100%) | 2025-11-28 00:00:00 (100%) | 4. Completed |
| OTCC0679 | Open Dispute Case Conversion | 2025-06-06 00:00:00 (100%) | 2025-07-29 00:00:00 (100%) | 2025-08-29 00:00:00 (100%) | 2025-10-08 00:00:00 (100%) | 4. Completed |
| OTCC0678 | Collection Master Conversion | 2025-03-21 00:00:00 (100%) | 2025-05-02 00:00:00 (100%) | 2025-06-06 00:00:00 (100%) | 2025-08-29 00:00:00 (100%) |
RAID items will be auto-populated from the Smartsheet RAID log when matched to this capability.
| # | 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-160 — Architecture Document (TOGAF BDAT) · Order To Cash (IP) · Generated: April 2026