🏠 Home FPR Tower Architecture 📝 ADA Editor ↗
IAO Architecture

DS-030 — Perform Customer and Product Profitability Analysis

Architecture Document (TOGAF BDAT)

Finance Plan To Report (FPR) Tower
Capability DS-030 · DS Provide Decision Support

IAO Program · R1 – R5
Generated: May 2026
Sajiv Francis

IAO Architecture Pipeline — Intel Confidential

Page 1↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

Table of Contents

Page 2↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

1. Executive Summary

This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for DS-030 Perform Customer and Product Profitability Analysis within the IAO program. It includes 3 BPMN process diagram(s) in Section 3.

Dimension Value
Tower Finance Plan To Report (FPR)
Process Group DS Provide Decision Support
Capability DS-030 - Perform Customer and Product Profitability Analysis
Release R1 – R5
Total Systems 0
System Status 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM
RICEFW Objects 3 Enhancements

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.

Page 3↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

2. Business Context & Objectives

2.1 Classification

Level Value
L0 Tower Finance Plan To Report
L1 Process DS Provide Decision Support
L2 Capability DS-030 - Perform Customer and Product Profitability Analysis

2.2 Business Drivers

# Driver Description Strategic Alignment Priority
1 S/4 HANA Finance Consolidation Migrate legacy costing and reporting platforms to unified S/4 HANA finance backbone IDM 2.0 Core Finance Transformation High
2 Real-Time Financial Visibility Enable real-time cost reporting and variance analysis replacing batch-driven legacy processes CFO Digital Finance Initiative High
3 Regulatory Compliance Readiness Ensure SOX compliance and audit trail continuity through the ERP transition period Intel Corporate Compliance Medium
4 DS-030 Process Migration Migrate DS-030 business processes and 0 integrated systems from legacy to S/4 HANA target architecture IDM 2.0 Finance High
Page 4↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

2.3 Success Criteria

Metric Target Measure Baseline Owner
Month-End Close Cycle Time < 3 business days Calendar days from period close trigger to final posting 5 business days (legacy) Finance Controller
Cost Variance Accuracy < 0.5% deviation Variance between standard and actual cost post-migration 1.2% (ICOST baseline) Cost Accounting Lead
System Availability (Finance) 99.9% uptime S/4 HANA finance module availability during business hours 99.5% (legacy) IT Operations
DS-030 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
Page 5↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

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 DS-030 Perform Customer and Product Profitability Analysis.

# Step ID Process Name Lanes Tasks Gateways
1 DS-030-010_Create_and_Maintain_Master_Data DS-030-010_Create_and_Maintain_Master_Data Cost Accountant, SAP Consultant 5 1
2 DS-030-060_Transfer_Costs_from_Accounting DS-030-060_Transfer_Costs_from_Accounting Cost Accountant 20 4
3 DS-030-110_Analyze_Profitability DS-030-110_Analyze_Profitability Cost Accountant 5 2
Page 6↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 DS-030-010_Create_and_Maintain_Master_Data — DS-030-010_Create_and_Maintain_Master_Data

Swim Lanes: Cost Accountant · SAP Consultant | Tasks: 5 | Gateways: 1

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["Cost Accountant"] n4["fa:fa-user Capture Revenue, COGS, Reporting"] n5["fa:fa-user Maintain Profitability Dimension Values"] n6(["fa:fa-stop Master Data Managed"]) end subgraph lane_1["SAP Consultant"] n1["fa:fa-user Define Profitability Dimensions"] n2["fa:fa-user Assign Dimensions to Operating Concerns"] n3["fa:fa-user Define Derivation Strategy for Profitability Dimensions at Transactional..."] n7["Create Customer Master"] n8["Change Customer Master in SAP"] n9["Process Material Master"] n10{{"fa:fa-arrows-alt parallelGateway"}} end n10 --> n1 n1 --> n2 n2 --> n5 n5 --> n3 n3 --> n4 n4 --> n6 n7 --> n10 n8 --> n10 n9 --> n10 class n1 userTask class n2 userTask class n3 userTask class n4 userTask class n5 userTask class n6 endEvt class n7 startEvt class n8 startEvt class n9 startEvt class n10 gateway
👁 View Diagram
Page 7↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

BUSINESS ARCHITECTURE — 3.2.2 DS-030-060_Transfer_Costs_from_Accounting — DS-030-060_Transfer_Costs_from_Accounting

Swim Lanes: Cost Accountant | 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 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["Cost Accountant"] n1["fa:fa-user Capture Actual Revenue/Cost Flow to Profitability Analysis"] n2["fa:fa-user Capture Sales Order/Billing"] n3[["fa:fa-cog Derive Plant from Sales Order"]] n4[["fa:fa-cog Derive Profit Center from Material Master"]] n5[["fa:fa-cog Derive Company Code from Plant or Sales Organization"]] n6[["fa:fa-cog Derive Bill-to-Party and Bill-to-Country from Customer Master"]] n7[["fa:fa-cog Derive Ship-to-Party and Sold-to party from Sales Order"]] n8[["fa:fa-cog Derive Customer Group from Customer Master"]] n9[["fa:fa-cog Derive Product Hierarchy from Material Master"]] n10[["fa:fa-cog Derive WBS from Sales Order"]] n11[["fa:fa-cog Derive Ship-to Country/Region from Customer Master"]] n12[["fa:fa-cog Derive DOT Process and Stage from Product Master"]] n13[["fa:fa-cog Execute Profitability Reports"]] n14[["fa:fa-cog Analyze Revenue/Cost"]] n15[["fa:fa-cog Capture Customer Master from Sales Order"]] n16[["fa:fa-cog Capture Material Master/Stage Material Number from Sales Order"]] n17[["fa:fa-cog Derive Division from Material Master"]] n18[["fa:fa-cog Derive End Customer and Distribution Channel from Sales Order"]] n19[["fa:fa-cog Derive Technode /Stage from WBS"]] n20[["fa:fa-cog Derive Technode/Stage from Secondary Cost Center"]] n21(["fa:fa-play Secondary Periodic Cost Assessment Initiated"]) n22(["fa:fa-stop Secondary Periodic Cost Assessment Completed"]) n23{{"fa:fa-arrows-alt parallelGateway"}} n24{{"fa:fa-arrows-alt parallelGateway"}} n25{{"fa:fa-arrows-alt parallelGateway"}} n26{{"fa:fa-arrows-alt parallelGateway"}} end n21 --> n1 n1 --> n2 n7 --> n23 n11 --> n23 n10 --> n23 n6 --> n23 n5 --> n23 n3 --> n23 n23 --> n13 n13 --> n14 n14 --> n22 n24 --> n16 n24 --> n15 n2 --> n24 n16 --> n25 n25 --> n4 n25 --> n9 n24 --> n3 n25 --> n12 n24 --> n7 n24 --> n10 n24 --> n11 n24 --> n17 n17 --> n23 n24 --> n6 n24 --> n5 n26 --> n23 n12 --> n26 n18 --> n23 n4 --> n26 n9 --> n26 n24 --> n18 n8 --> n23 n15 --> n8 n24 --> n19 n24 --> n20 n20 --> n23 n19 --> n23 class n1 userTask class n2 userTask 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 serviceTask class n17 serviceTask class n18 serviceTask class n19 serviceTask class n20 serviceTask class n21 startEvt class n22 endEvt class n23 gateway class n24 gateway class n25 gateway class n26 gateway
👁 View Diagram
Page 8↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

BUSINESS ARCHITECTURE — 3.2.3 DS-030-110_Analyze_Profitability — DS-030-110_Analyze_Profitability

Swim Lanes: Cost Accountant | Tasks: 5 | 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["Cost Accountant"] n1["fa:fa-user Maintain Actual Revenue/Cost Flow to Profitability Analysis"] n2["fa:fa-user Capture Sales Order"] n3["fa:fa-user Capture Sales Order - Billing (Revenue)"] n4["fa:fa-user Execute Profitability Reports"] n5["fa:fa-user Analyze Revenue/Cost"] n6(["fa:fa-play Report APP Run Request Initiated"]) n7(["fa:fa-stop Sales Selection and Analysis of COGS GL with Different Combination Complete"]) n8{{"fa:fa-arrows-alt parallelGateway"}} n9{{"fa:fa-arrows-alt parallelGateway"}} end n6 --> n1 n1 --> n8 n8 --> n2 n8 --> n3 n2 --> n9 n3 --> n9 n9 --> n4 n4 --> n5 n5 --> n7 class n1 userTask class n2 userTask class n3 userTask class n4 userTask class n5 userTask class n6 startEvt class n7 endEvt class n8 gateway class n9 gateway
👁 View Diagram
Page 9↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
Cost Accountant DS-030-010_Create_and_Maintain_Master_Data, DS-030-060_Transfer_Costs_from_Accounting, DS-030-110_Analyze_Profitability
SAP Consultant DS-030-010_Create_and_Maintain_Master_Data,
Page 10↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

3.4 Process Readiness

Process readiness for DS-030 — Perform Customer and Product Profitability Analysis 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
DS-030 Perform Customer and Product… 3/3 0% (0/5) 57F/10G/71 3/3 † 0/12 † 🔴

† RICEFW/ECA counts are shared across Sub-Tower pool — DS-030 shares with DS-010, DS-020. Object Tracker does not tag objects at L2 granularity; counts represent the combined sub-tower total.

Risk Flags for DS-030: - 🔴 Config Incomplete — Config at 0% (0/5) - 🔴 ECA Incomplete — 12/12 ECA objects not complete (0%)

📄 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 .

Page 11↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

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

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 Finance Plan To Report 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
Page 12↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

5. Application Architecture (TOGAF “A”)

5.4 Component Overview

System Inventory

System IAPM ID Status

5.5 Development Object Inventory

Summary: 3 SAP | RICEFW: 3 Enhancements

5.5.1 SAP Development Objects

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
FPRE0764_IP Enhancement Import Headcount details by cost center and update in S4 for HR benefits spen… 10. Object Complete 01.S4 03.Medium
FPRE0764_IF Enhancement Import Headcount details by cost center and update in S4 for HR benefits spen… 10. Object Complete 01.S4 04.Low
FPRE0574_IP Enhancement Margin analysis Dimensions creation 10. Object Complete 01.S4 04.Low

5.5.5 Scheduling & Batch Objects

This section provides a holistic view of all batch processing and job scheduling — both internal SAP background jobs (SM37) and external orchestration (AutoSys, CWA).

5.5.5b External Scheduling Objects

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.

Page 13↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

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 Month-end batch costing/closing completes within SLA window < 4 hours end-to-end batch window High
Availability S/4 HANA finance modules available during business hours 99.9% (Mon-Fri 06:00-22:00 PST) High
Scalability Support 2x transaction volume growth over 3-year horizon Handle 500K+ journal entries/day Medium
Recoverability RPO/RTO for financial systems meets audit requirements RPO < 1 hour, RTO < 4 hours High
Data Volume Support growing data volumes from legacy migration + BAU 50M+ records in material ledger Medium
Latency Near-real-time posting for financial transactions < 5 seconds for online postings Medium
Concurrency Support concurrent month-end users across time zones 200+ concurrent finance 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

6.5 ECA Development Object Status

Metric Count
ECA Objects (active) 12
ECA Complete 0 (0%)
ECA In Progress 12
ECA Rejected/Cancelled 1
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.

Page 14↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

7. Project Context

7.1 Project Roadmap & Go-Live Plan

ID Description FS TDD Build FUT Status
FPRE0764_IP Import Headcount details by cost center and update in S4 for HR benefits spen… 2024-12-13 00:00:00 (100%) 2025-05-23 00:00:00 (100%) 2025-05-23 00:00:00 (100%) 2025-07-16 00:00:00 (100%) 1. On Track
FPRE0764_IF Import Headcount details by cost center and update in S4 for HR benefits spen… 2024-12-13 00:00:00 (100%) 2025-05-23 00:00:00 (100%) 2025-05-23 00:00:00 (100%) 2025-07-16 00:00:00 (100%) 1. On Track
FPRE0574_IP Margin analysis Dimensions creation 2024-10-18 00:00:00 (100%) 2025-01-17 00:00:00 (100%) 2025-01-17 00:00:00 (100%) 2024-11-08 00:00:00 (100%)
Page 15↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis

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

DS-030 — Architecture Document (TOGAF BDAT) · Finance Plan To Report · Generated: May 2026

Page 16↑ Back to TOCDS-030 — Perform Customer and Product Profitability Analysis
IAO Architecture Document | Intel IDM 2.0 | Generated by IAO Architecture Pipeline
↑ Back to TOC DS-030 — Perform Customer and Product Profitability Analysis IAO Architecture Pipeline — Intel Confidential