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
DC-100 — Revenue Recognition
Architecture Document (TOGAF BDAT)
Finance Plan To Report (FPR) Tower
Capability DC-100 · DC Manage Accounting and Control Data
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 DC-100 Revenue Recognition within the IAO program. It includes 6 BPMN process diagram(s) in Section 3.
Dimension
Value
Tower
Finance Plan To Report (FPR)
Process Group
DC Manage Accounting and Control Data
Capability
DC-100 - Revenue Recognition
Release
R1 – R5
Total Systems
0
System Status
0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM
RICEFW Objects
1 Reports, 1 Interfaces, 12 Enhancements
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
Finance Plan To Report
L1 Process
DC Manage Accounting and Control Data
L2 Capability
DC-100 - Revenue Recognition
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
Ensure SOX compliance and audit trail continuity through the ERP transition period
Intel Corporate Compliance
Medium
4
DC-100 Process Migration
Migrate DC-100 business processes and 0 integrated systems from legacy to S/4 HANA target architecture
IDM 2.0 Finance
High
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
DC-100 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 6 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for DC-100 Revenue Recognition.
#
Step ID
Process Name
Lanes
Tasks
Gateways
1
DC-100-010_Create_Revenue_Accounting_Contracts
DC-100-010_Create_Revenue_Accounting_Contracts
RAR IT Support Analyst, Revenue Accountant
4
2
2
DC-100-030_RAR_Closing_and_Reconciliation
DC-100-030_RAR_Closing_and_Reconciliation
Revenue Accountant
15
12
3
DC-100-040_RAR_Reports
DC-100-040_RAR_Reports
Revenue Accountant
8
1
4
DC-100-050_Define_Transaction_Price
DC-100-050_Define_Transaction_Price
Revenue Accountant
0
0
5
DC-100-060_Determine_Performance_Obligations
DC-100-060_Determine_Performance_Obligations
RAR IT Support Analyst, Revenue Accountant
4
2
6
DC-100-070_Allocate_Transaction_Price
DC-100-070_Allocate_Transaction_Price
Revenue Accountant
0
0
3.2 Business Process Diagrams
BUSINESS ARCHITECTURE — 3.2.1 DC-100-010_Create_Revenue_Accounting_Contracts — DC-100-010_Create_Revenue_Accounting_Contracts
Swim Lanes: RAR IT Support Analyst · Revenue Accountant | 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["RAR IT Support Analyst"]
n1["fa:fa-user Resolve the Error for RAR Contract and Reprocess"]
n4[["fa:fa-cog Perform Real Time Processing of Revenue Accounting Items"]]
n8{{"fa:fa-code-branch If RAI is in Postponed Status then it needs to be Reprocessed?"}}
end
subgraph lane_1["Revenue Accountant"]
n2["fa:fa-user View and Manage RAR Contract"]
n3["fa:fa-user Display Sales Order for RAR Contract"]
n5(["fa:fa-play Request to Create Sales Order Received"])
n6(["fa:fa-stop RAR Contract Created in SAP"])
n7["Revenue Accounting Items - Order Items Created"]
n9{{"fa:fa-code-branch exclusiveGateway"}}
end
n5 --> n3
n3 --> n7
n2 --> n6
n9 --> n2
n1 --> n9
n8 -->|"Yes"| n1
n4 --> n8
n7 --> n4
n8 -->|"No"| n9
class n1 userTask
class n2 userTask
class n3 userTask
class n4 serviceTask
class n5 startEvt
class n6 endEvt
class n7 startEvt
class n8 gateway
class n9 gateway
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["Revenue Accountant"]
n1["fa:fa-user Change Status to 'In Closing' for RAR Period"]
n2["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"]
n3["fa:fa-user Go to Shift Contract to Next Period"]
n4["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"]
n5["fa:fa-user Go to Shift Contract to Next Period"]
n6["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"]
n7["fa:fa-user Go to Shift Contract to Next Period"]
n8["fa:fa-user Rerun Batch Job A"]
n9["fa:fa-user Rerun Batch Job B"]
n10["fa:fa-user Rerun Batch Job C"]
n11["fa:fa-user Update fulfilment of Manual Fulfilment based Performance Obligation"]
n12[["fa:fa-cog Run Batch Job A : Transfer Revenue"]]
n13[["fa:fa-cog Run Batch Job B : Calculate Contract Asset and Liability"]]
n14[["fa:fa-cog Run Batch Job C: Revenue Posting Run"]]
n15[["fa:fa-cog Run Batch Job C for Close Revenue Period"]]
n16(["fa:fa-play RAR Closing and Reconciliation Initiated"])
n17(["fa:fa-stop Contract Shifted"])
n18(["fa:fa-stop Contract Shifted"])
n19(["fa:fa-stop Contract Shifted"])
n20(["fa:fa-stop RAR Closing and Reconciliation Completed"])
n21["Revenue Posting Completed in FI-GL"]
n22{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}}
n23{{"fa:fa-code-branch Error Resolved?"}}
n24{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}}
n25{{"fa:fa-code-branch exclusiveGateway"}}
n26{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}}
n27{{"fa:fa-code-branch Error Resolved?"}}
n28{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}}
n29{{"fa:fa-code-branch exclusiveGateway"}}
n30{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}}
n31{{"fa:fa-code-branch Error Resolved?"}}
n32{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}}
n33{{"fa:fa-code-branch exclusiveGateway"}}
end
n16 --> n11
n1 --> n12
n12 --> n22
n22 -->|"Yes"| n2
n2 --> n23
n23 -->|"No"| n24
n24 -->|"Yes"| n3
n3 --> n17
n25 --> n13
n24 -->|"No"| n25
n23 -->|"Yes"| n8
n26 -->|"Yes"| n4
n4 --> n27
n28 -->|"Yes"| n5
n5 --> n18
n29 --> n14
n27 -->|"Yes"| n9
n13 --> n26
n27 -->|"No"| n28
n30 -->|"Yes"| n6
n6 --> n31
n31 -->|"No"| n32
n32 -->|"Yes"| n7
n7 --> n19
n14 --> n30
n33 --> n15
n21 --> n20
n32 -->|"No"| n33
n28 -->|"No"| n29
n15 --> n21
n31 -->|"Yes"| n10
n8 --> n25
n22 -->|"No"| n25
n26 -->|"No"| n29
n9 --> n29
n30 -->|"No"| n33
n10 --> n33
n11 --> n1
class n1 userTask
class n2 userTask
class n3 userTask
class n4 userTask
class n5 userTask
class n6 userTask
class n7 userTask
class n8 userTask
class n9 userTask
class n10 userTask
class n11 userTask
class n12 serviceTask
class n13 serviceTask
class n14 serviceTask
class n15 serviceTask
class n16 startEvt
class n17 endEvt
class n18 endEvt
class n19 endEvt
class n20 endEvt
class n21 startEvt
class n22 gateway
class n23 gateway
class n24 gateway
class n25 gateway
class n26 gateway
class n27 gateway
class n28 gateway
class n29 gateway
class n30 gateway
class n31 gateway
class n32 gateway
class n33 gateway
BUSINESS ARCHITECTURE — 3.2.5 DC-100-060_Determine_Performance_Obligations — DC-100-060_Determine_Performance_Obligations
Swim Lanes: RAR IT Support Analyst · Revenue Accountant | 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["RAR IT Support Analyst"]
n1["fa:fa-user Resolve the Error for POB and Reprocess"]
n4[["fa:fa-cog Perform Real Time Processing of Revenue Accounting Items for POB"]]
n8{{"fa:fa-code-branch If RAI is in Postponed Status then it needs to be Reprocessed?"}}
end
subgraph lane_1["Revenue Accountant"]
n2["fa:fa-user View and Manage Performance Obligation"]
n3["fa:fa-user Display Sales Order for POB"]
n5(["fa:fa-play Request to Create Sales Order Received"])
n6(["fa:fa-stop Performance Obligations Created"])
n7["Revenue Accounting Items - Order Items Created"]
n9{{"fa:fa-code-branch exclusiveGateway"}}
end
n5 --> n3
n3 --> n7
n7 --> n4
n2 --> n6
n4 --> n8
n9 --> n2
n8 -->|"No"| n9
n8 -->|"Yes"| n1
n1 --> n9
class n1 userTask
class n2 userTask
class n3 userTask
class n4 serviceTask
class n5 startEvt
class n6 endEvt
class n7 startEvt
class n8 gateway
class n9 gateway
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
Data-centric RICEFW objects (Reports and Conversions) from the Object Tracker:
Object ID
Type
Description
Status
Source
Target
Complexity
FPRR1240
Report
Custom report for Revenue Recognition by Stage for Product/Services Sale act…
10. Object Complete
03.Medium
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
FPRR1240
Report
Custom report for Revenue Recognition by Stage for Product/Services Sale act…
10. Object Complete
NA
03.Medium
FPRI1241
Interface
Disti Rebate percentage of gross for Unissued Returns and Intransit Deferral
10. Object Complete
ECA → S/4
BODS
03.Medium
FPRE1660
Enhancement
Enhancement for Revenue Recognition by Stage postings for Product/Services Sa…
10. Object Complete
NA
02.High
FPRE1659
Enhancement
Enhancement for Revenue Recognition by Stage postings for Product/Services Sa…
10. Object Complete
NA
02.High
FPRE1239
Enhancement
Enhancement for Revenue Recognition by Stage postings for Product/Services Sa…
10. Object Complete
NA
02.High
FPRE0760_IP
Enhancement
SAP RAR and TM Integration to trigger POD Event
10. Object Complete
NA
03.Medium
FPRE0760_IF
Enhancement
SAP RAR and TM Integration to trigger POD Event
10. Object Complete
NA
04.Low
FPRE0697
Enhancement
RAR Balance sheet posting with MM & Sold To ID
10. Object Complete
NA
03.Medium
FPRE0500_IP
Enhancement
Rule for Transaction Price Allocation in BRIM vs SD
10. Object Complete
NA
03.Medium
FPRE0500_IF
Enhancement
Rule for Transaction Price Allocation in BRIM vs SD
10. Object Complete
NA
03.Medium
FPRE0477
Enhancement
Rebate for Direct Customer to Rebate of Intransit deferrals for Direct & Dist…
10. Object Complete
NA → NA
NA
03.Medium
FPRE0476
Enhancement
Accounting for Stock Rotation
10. Object Complete
NA → NA
NA
03.Medium
FPRE0475
Enhancement
Accounting for reserves for unissued returns credit note & Rebate Return Accr…
10. Object Complete
NA → NA
NA
03.Medium
FPRE0474
Enhancement
Accounting for technical return reserve
10. Object Complete
NA → NA
NA
03.Medium
Summary: 1 Reports, 1 Interfaces, 12 Enhancements
5.6 Integration Patterns
Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.
