M Mfg. Schedule and Execution (IP)
TOGAF BDAT — Aggregated Architecture View
Tower: Forecast to Stock (IP) (FTS-IP) · Process: M Mfg. Schedule and Execution (IP) · R1 – R5
IAO Program · R1 – R5
Generated: April 2026
Sajiv Francis
IAO Architecture Pipeline — Intel Confidential
1 Executive Summary
This L1 summary aggregates architecture diagrams from 3 L2 capabilities across Tower: Forecast to Stock (IP) (FTS-IP) · Process: M Mfg. Schedule and Execution (IP) · R1 – R5.
The diagrams below show the consolidated current-state and future-state system landscape without duplicates — each system and connection appears only once even when shared across capabilities. For detailed data flows, integration patterns, technology stacks, and business architecture, refer to the individual L2 capability documents linked in §6 Capability Detail Reference.
| Metric |
Current-State |
Future-State |
Delta |
| Unique Systems |
2 |
2 |
+0 |
| System Connections |
1 |
1 |
+0 |
| Total Flow Hops |
6 |
6 |
+0 |
| Capabilities Covered |
3 |
3 |
— |
2 Capability Inventory
The following 3 capabilities are aggregated in this summary.
Click a capability ID to view its full TOGAF BDAT architecture document.
| # |
Capability ID |
Capability Name |
L1 Process Group |
Current Hops |
Future Hops |
| 1 |
M-080 |
Perform Materials Requirement Planning (IP) |
M Mfg. Schedule and Execution (IP) |
2 |
2 |
| 2 |
M-090 |
Schedule Production (IP) |
M Mfg. Schedule and Execution (IP) |
2 |
2 |
| 3 |
M-100 |
Execute Production (IP) |
M Mfg. Schedule and Execution (IP) |
2 |
2 |
3 Current-State Architecture
Aggregated current-state: 2 systems, 1 connections, 6 flow hops.
3.1 Application Architecture
System-to-system integration flows. Color indicates IAPM lifecycle status (green = deployed, blue = developing, red = end-of-life).
graph TB
%% -- ArchiMate 3.2 + Azure style classes --
classDef business fill:#FFFFB3,stroke:#F9A825,stroke-width:2px,color:#000
classDef app fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef data fill:#BBDEFB,stroke:#1565C0,stroke-width:1px,color:#0D47A1,stroke-dasharray: 5 5
classDef middleware fill:#FFE0B2,stroke:#E65100,stroke-width:2px,color:#BF360C
classDef eol fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
classDef saas fill:#E1BEE7,stroke:#7B1FA2,stroke-width:2px,color:#4A148C
classDef cloud fill:#BBDEFB,stroke:#1565C0,stroke-width:2px,color:#0D47A1
classDef onprem fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
subgraph AL["📦 Application Layer — Systems Integration"]
direction LR
SCA_e_g__MES_300["📦 e.g. MES 300"]
SCA_e_g__XEUS["📦 e.g. XEUS"]
end
SCA_e_g__MES_300 -->|"e.g. Direct / API / File"| SCA_e_g__XEUS
class SCA_e_g__MES_300 app
class SCA_e_g__XEUS app
style BL fill:#FFFDE7,stroke:#F9A825,stroke-width:2px
style AL fill:#E3F2FD,stroke:#0078D4,stroke-width:2px
3.2 Data Architecture
Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "15px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 35, "rankSpacing": 45}} }%%
flowchart TB
classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbCyl fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
classDef dbCloud fill:#BBDEFB,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbData fill:#B2EBF2,stroke:#00838F,stroke-width:2px,color:#004D40
classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
subgraph SCDCL_e_g_Azure_SQL[" "]
direction TB
SCDA_e_g_XEUS["e.g. XEUS"]:::appBox
SCDD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud
SCDA_e_g_XEUS -.-> SCDD_e_g_Azure_SQL
end
style SCDCL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px
subgraph SCDCL_e_g_SAP_HANA[" "]
direction TB
SCDA_e_g_MES_300["e.g. MES 300"]:::appBox
SCDD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData
SCDA_e_g_MES_300 -.-> SCDD_e_g_SAP_HANA
end
style SCDCL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px
SCDD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| SCDD_e_g_Azure_SQL
subgraph Legend["📐 DATA ARCHITECTURE LEGEND"]
direction LR
L_A["Application"]:::appBox
L_D[("🗄️ On-Prem DB")]:::dbCyl
L_DC[("🗄️ Cloud DB")]:::dbCloud
L_DD[("🗄️ Data Platform")]:::dbData
L_E["End-of-Life"]:::eolBox
end
style Legend fill:#F5F5F5,stroke:#999,stroke-width:1px
3.3 Technology Architecture
Applications grouped by hosting platform. Cloud platforms marked with ☁️.
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "14px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 40, "rankSpacing": 50}} }%%
flowchart TB
classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef platBox fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
subgraph SCPP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"]
direction LR
SCPA_e_g_XEUS["e.g. XEUS"]:::appBox
end
style SCPP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C
subgraph SCPP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"]
direction LR
SCPA_e_g_MES_300["e.g. MES 300"]:::appBox
end
style SCPP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
SCPP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| SCPP_e_g_Azure_PaaS
subgraph SCPLegend["📐 PLATFORM LEGEND"]
direction LR
SCPLC["☁️ Cloud"]
SCPLS["🔮 SaaS"]
SCPLO["🏢 On-Prem"]
SCPLD["💾 Data Platform"]
SCPLM["🔗 Middleware"]
end
style SCPLegend fill:#F5F5F5,stroke:#999,stroke-width:1px
style SCPLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C
style SCPLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C
style SCPLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
style SCPLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40
style SCPLM fill:#FFE0B2,stroke:#E65100,stroke-width:3px,color:#BF360C
4 Future-State Architecture
Aggregated future-state: 2 systems, 1 connections, 6 flow hops.
4.1 Application Architecture
System-to-system integration flows. Color indicates IAPM lifecycle status (green = deployed, blue = developing, red = end-of-life).
graph TB
%% -- ArchiMate 3.2 + Azure style classes --
classDef business fill:#FFFFB3,stroke:#F9A825,stroke-width:2px,color:#000
classDef app fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef data fill:#BBDEFB,stroke:#1565C0,stroke-width:1px,color:#0D47A1,stroke-dasharray: 5 5
classDef middleware fill:#FFE0B2,stroke:#E65100,stroke-width:2px,color:#BF360C
classDef eol fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
classDef saas fill:#E1BEE7,stroke:#7B1FA2,stroke-width:2px,color:#4A148C
classDef cloud fill:#BBDEFB,stroke:#1565C0,stroke-width:2px,color:#0D47A1
classDef onprem fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
subgraph AL["📦 Application Layer — Systems Integration"]
direction LR
SFA_e_g__MES_300["📦 e.g. MES 300"]
SFA_e_g__XEUS["📦 e.g. XEUS"]
end
SFA_e_g__MES_300 -->|"e.g. Direct / API / File"| SFA_e_g__XEUS
class SFA_e_g__MES_300 app
class SFA_e_g__XEUS app
style BL fill:#FFFDE7,stroke:#F9A825,stroke-width:2px
style AL fill:#E3F2FD,stroke:#0078D4,stroke-width:2px
4.2 Data Architecture
Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "15px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 35, "rankSpacing": 45}} }%%
flowchart TB
classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbCyl fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20
classDef dbCloud fill:#BBDEFB,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef dbData fill:#B2EBF2,stroke:#00838F,stroke-width:2px,color:#004D40
classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
subgraph SFDCL_e_g_Azure_SQL[" "]
direction TB
SFDA_e_g_XEUS["e.g. XEUS"]:::appBox
SFDD_e_g_Azure_SQL[("🗄️ e.g. Azure SQL")]:::dbCloud
SFDA_e_g_XEUS -.-> SFDD_e_g_Azure_SQL
end
style SFDCL_e_g_Azure_SQL fill:#E8F5E9,stroke:#388E3C,stroke-width:1px
subgraph SFDCL_e_g_SAP_HANA[" "]
direction TB
SFDA_e_g_MES_300["e.g. MES 300"]:::appBox
SFDD_e_g_SAP_HANA[("🗄️ e.g. SAP HANA")]:::dbData
SFDA_e_g_MES_300 -.-> SFDD_e_g_SAP_HANA
end
style SFDCL_e_g_SAP_HANA fill:#E3F2FD,stroke:#1976D2,stroke-width:1px
SFDD_e_g_SAP_HANA ==>|"e.g. Direct / API / File"| SFDD_e_g_Azure_SQL
subgraph Legend["📐 DATA ARCHITECTURE LEGEND"]
direction LR
L_A["Application"]:::appBox
L_D[("🗄️ On-Prem DB")]:::dbCyl
L_DC[("🗄️ Cloud DB")]:::dbCloud
L_DD[("🗄️ Data Platform")]:::dbData
L_E["End-of-Life"]:::eolBox
end
style Legend fill:#F5F5F5,stroke:#999,stroke-width:1px
4.3 Technology Architecture
Applications grouped by hosting platform. Cloud platforms marked with ☁️.
%%{init: {"theme": "base", "securityLevel": "loose", "themeVariables": {"fontSize": "14px", "fontFamily": "Segoe UI, Arial"}, "flowchart": {"useMaxWidth": false, "htmlLabels": true, "nodeSpacing": 40, "rankSpacing": 50}} }%%
flowchart TB
classDef appBox fill:#CCE5FF,stroke:#0078D4,stroke-width:2px,color:#003A6C
classDef platBox fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
classDef eolBox fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#B71C1C
subgraph SFPP_e_g_Azure_PaaS["☁️ e.g. Azure PaaS"]
direction LR
SFPA_e_g_XEUS["e.g. XEUS"]:::appBox
end
style SFPP_e_g_Azure_PaaS fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C
subgraph SFPP_e_g_S_4_HANA_2023["🖥️ e.g. S/4 HANA 2023"]
direction LR
SFPA_e_g_MES_300["e.g. MES 300"]:::appBox
end
style SFPP_e_g_S_4_HANA_2023 fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
SFPP_e_g_S_4_HANA_2023 ==>|"e.g. Direct / API / File"| SFPP_e_g_Azure_PaaS
subgraph SFPLegend["📐 PLATFORM LEGEND"]
direction LR
SFPLC["☁️ Cloud"]
SFPLS["🔮 SaaS"]
SFPLO["🏢 On-Prem"]
SFPLD["💾 Data Platform"]
SFPLM["🔗 Middleware"]
end
style SFPLegend fill:#F5F5F5,stroke:#999,stroke-width:1px
style SFPLC fill:#BBDEFB,stroke:#0078D4,stroke-width:3px,color:#003A6C
style SFPLS fill:#E1BEE7,stroke:#7B1FA2,stroke-width:3px,color:#4A148C
style SFPLO fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#1B5E20
style SFPLD fill:#B2EBF2,stroke:#00838F,stroke-width:3px,color:#004D40
style SFPLM fill:#FFE0B2,stroke:#E65100,stroke-width:3px,color:#BF360C
5.1 System Landscape Changes
| Category |
Count |
Systems |
| Added in Future State |
0 |
— |
| Removed from Future State |
0 |
— |
| Continuing Systems |
2 |
— |
Reconciliation Note: System lifecycle status is sourced from IAPM (Intel Application Portfolio Management). Systems shown as Removed from Future State are not in scope for this release but are not decommissioned unless marked EOL Path above. EOL decommissioning is planned post-R5.
5.2 Integration Complexity Delta
5.3 Release-over-Release Changes
Changes between adjacent releases — additions and removals of applications, databases, and technology platforms. System lifecycle sourced from IAPM.
R1 -> R2
No changes detected between releases.
6 Capability Detail Reference
For detailed architecture information, navigate to the individual L2 capability documents.
Each L2 document contains the full TOGAF BDAT analysis including:
- Business Architecture — BPMN process flows, business drivers, success criteria
- Data Architecture — Source-to-target data flows with DB platforms
- Application Architecture — Integration patterns, middleware, protocols
- Technology Architecture — Platform inventory, deployment topology
- RICEFW / Clean Core — SAP development object tracking
| # |
Capability |
L1 Process |
Architecture Doc |
| 1 |
Perform Materials Requirement Planning (IP) |
M Mfg. Schedule and Execution (IP) |
M-080 |
| 2 |
Schedule Production (IP) |
M Mfg. Schedule and Execution (IP) |
M-090 |
| 3 |
Execute Production (IP) |
M Mfg. Schedule and Execution (IP) |
M-100 |