Order To Cash (IF) (OTC-IF) Tower
Capability LO-160 · LO Logistics Management Outbound - OTC (IF)
IAO Program · R1 – R5
Generated: May 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 (IF) within the IAO program.
| Dimension | Value |
|---|---|
| Tower | Order To Cash (IF) (OTC-IF) |
| Process Group | LO Logistics Management Outbound - OTC (IF) |
| Capability | LO-160 - Pick 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 |
System nodes in architecture diagrams are IAPM-linked where matches exist (0/0 matched) — click any linked node to open its IAPM page. Diagrams require
securityLevel: 'loose'for click events.
| Level | Value |
|---|---|
| L0 Tower | Order To Cash (IF) |
| L1 Process | LO Logistics Management Outbound - OTC (IF) |
| L2 Capability | LO-160 - Pick Orders - OTC (IF) |
| # | 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-160 Process Migration | Migrate Pick 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 |
| 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-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 |
(No BPMN files found in input/bpmn/ for this capability.)
Business roles and responsibilities will be derived from BPMN swim lane assignments when process models are available.
Process readiness for LO-160 — Pick Orders - OTC (IF) with automated risk flags from Config Tracker, User Story Tracker, RICEFW Object Tracker, ECA Object Tracker.
| L2 | Description | L3 In-Scope | Config | User Stories | RICEFW | ECA | Status |
|---|---|---|---|---|---|---|---|
| LO-160 | Pick Orders - OTC (IF) | 14/14 | 25% (6/24) | 8F/3G/11 | 19/19 † | 4/5 † | 🟡 |
† RICEFW/ECA counts are shared across Sub-Tower pool — LO-160 shares with LO-170, LO-190, R-200, R-210. Object Tracker does not tag objects at L2 granularity; counts represent the combined sub-tower total.
Risk Flags for LO-160: - 🟡 Config Incomplete — Config at 25% (6/24) - 🟡 ECA Incomplete — 1/5 ECA objects not complete (80%)
📄 Full Process Readiness Detail → — per-capability breakdown with config items, RICEFW objects, transport analysis, and QA verification. For the comprehensive L1/L0 readiness rollup across all capabilities, see the L0 Tower Summary.
Data Sources: Config Tracker, User Story Tracker, S4 R3 Object Tracker, ECA R3 Object Tracker (Smartsheet exports). RICEFW and ECA objects are matched via Sub-Tower Name → L2 mapping. Generated .
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.
RICEFW data objects (Reports and Conversions) will be auto-populated from the Smartsheet Object Tracker when matched to this capability.
Standard governance framework per Intel IDM 2.0 data management policies. Capability-specific governance details will be populated from the Input Portal when tower architects complete the Data Governance tab.
| Concern | Approach |
|---|---|
| Data Ownership | Per-entity owners aligned to Order To Cash (IF) tower organizational structure |
| Data Classification | Per Intel corporate data classification policies |
| Data Retention | Per Intel corporate retention policies |
| Data Quality | Validated at source; reconciliation at target |
| System | IAPM ID | Status |
|---|---|---|
Summary: 9 SAP | RICEFW: 6 Enhancements, 2 Forms, 1 Workflows
SAP platform objects (Reports, Interfaces, Conversions, Enhancements, Forms, Workflows) developed on S/4, MDG, or S/4 BOT:
| Object ID | Type | Description | Status | Dev System | Complexity |
|---|---|---|---|---|---|
| OTCW0638 | Workflow | Dispute Write-off Workflow | 10. Object Complete | 01.S4 | 03.Medium |
| OTCF0431 | Form | Generate Custom Late Payment Interest Charge Output Form | 10. Object Complete | 01.S4 | 03.Medium |
| OTCF0290 | Form | Dunning output form customization | 10. Object Complete | 01.S4 | 03.Medium |
| OTCE1662 | Enhancement | BADI Enhancement for Dispute Write off (workflow Trigger) | 10. Object Complete | 01.S4 | 03.Medium |
| OTCE1658 | Enhancement | Dispute Write-off Enhancement | 10. Object Complete | 01.S4 | 04.Low |
| OTCE1625 | Enhancement | Credit hold release dashboard at line-item level | 10. Object Complete | 01.S4 | 01.Very High |
| OTCE0614_IF | Enhancement | Implement Standard Credit/Collection BADI | 10. Object Complete | 01.S4 | 04.Low |
| OTCE0235 | Enhancement | Credit and Collections - Credit Check Step Configuration | 10. Object Complete | 01.S4 | 04.Low |
| OTCE0234 | Enhancement | Implement mapping between customer’s risk class and credit check steps | 10. Object Complete | 01.S4 | 03.Medium |
This section provides a holistic view of all batch processing and job scheduling — both internal SAP background jobs (SM37) and external orchestration (AutoSys, CWA).
External scheduling data is not yet available. Pending either AutoSys API access or a JIL export to the External Job Scheduling Tracker.
Scheduling and batch job data will be auto-populated once SAP background job extraction (TBTCO/TBTCP via ADT) is run against the development systems and AutoSys metadata is available. Run python scripts/fetch_sap_background_jobs.py to extract SAP internal jobs.
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 |
| Metric | Count |
|---|---|
| ECA Objects (active) | 5 |
| ECA Complete | 4 (80%) |
| ECA In Progress | 1 |
| ECA Rejected/Cancelled | 4 |
| Total Interface Dependencies | 0 |
Data Source: ECA [R3] IDM Object Tracker (Smartsheet). Objects matched via Sub-Tower Name → L2 capability mapping. Rejected/cancelled/on-hold objects excluded from active counts.
| 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%) |
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 (IF) · Generated: May 2026