A detailed TOGAF Phase F plan for SAP PLM rollout and transition displayed on a whiteboard
Focus Keyword: TOGAF® ADM Phase F SAP rollout
Successfully implementing SAP ERP, PLM, and surrounding systems requires more than managing individual projects effectively. What ultimately determines success—both domestically and globally—is the ability to design Migration Planning at the enterprise level: deciding which capabilities to deploy, to which locations, and in what sequence.
TOGAF® ADM Phase F focuses precisely on this challenge. It defines how to prioritize implementation initiatives, structure a roadmap, and develop a concrete Implementation and Migration Plan.
Typical SAP projects follow a linear structure: requirements, design, build, test, and go-live. However, from an enterprise architecture (EA) perspective, this is insufficient.
In reality, SAP does not operate in isolation. It must be implemented alongside PLM, MDM, BI, EDI, WMS, MES, and other systems, all with complex interdependencies. These must be deployed across multiple migration waves.
SAP best practices emphasize early business process visualization, data quality assessment, and realistic roadmap design. This aligns directly with TOGAF® Phase F, which addresses:
A key distinction often overlooked in IT organizations is the difference between Migration Planning and individual project planning.
Migration Planning defines the enterprise-level transformation sequence—what to implement first, where to deploy, and how to transition across architectures. In contrast, project planning focuses on executing a specific implementation within scope, time, and budget.
In practical terms:
A common approach is to establish an SAP S/4HANA template at headquarters and roll it out globally.
In one example, a Japan-based company deployed ERP at headquarters, then rolled out a global template to nine overseas locations while simultaneously developing operational capabilities.
The critical Phase F decision here is defining:
Headquarters implementation should not be treated as a standalone project, but as a template-building phase for global deployment.
Global rollout introduces greater complexity in balancing standardization and localization.
A case involving overseas rollout using SAP S/4HANA Public Cloud highlights a key insight: rollout is not about copying templates. It is about redesigning business processes based on a To-Be model.
Migration waves should therefore be defined based on:
A typical strategy is to start with less complex regions and expand to more complex ones.
Rollouts become significantly more complex when they include management accounting transformation.
In one case, SAP S/4HANA was deployed across six countries and nine sites alongside a new production cost model.
Here, success required alignment of:
Migration Planning must therefore include when to standardize management accounting policies and data definitions, not just system deployment order.
ERP-first is not always optimal.
In a manufacturing case, companies first integrated overseas SAP data into a centralized BI system, enabling real-time visibility into previously opaque operations.
This also led to standardization of:
This approach demonstrates a Migration Planning pattern where:
This is particularly effective for complex multi-entity environments.
In manufacturing, ERP rollout alone is insufficient if engineering data remains fragmented.
The key issue is ensuring seamless, real-time integration between design and manufacturing data.
Critical decisions include:
For example:
Separating PLM and ERP rollout without clear ownership leads to major inconsistencies later.
Although headquarters-first is common, some organizations use overseas sites as pilot environments.
In one example, a manufacturer deployed SAP across 50 global locations, starting with overseas sites and later rolling out to domestic factories.
Benefits include:
From a TOGAF perspective, this represents validating Transition Architectures in low-risk environments.
Even if an organization appears to have only one SAP project, Migration Planning remains essential.
In practice, most implementations involve multiple phases:
Phase F provides a framework to design these stages, reduce risk, and accelerate value realization.
When designing SAP and PLM rollout strategies, IT organizations should define:
Crucially, “system go-live” does not equal “business adoption.” Migration Planning must include the path to operational self-sufficiency.
Treating SAP ERP and PLM implementation as isolated projects makes it difficult to achieve global optimization.
The key is to design rollout as an enterprise-level Migration Planning problem—defining what to deploy, where, in what order, and through which transition states.
Real-world patterns include:
The ability to design the right migration waves for your organization is what ultimately determines success.
Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.
The Environments and Locations Diagram is a formal TOGAF Phase D artifact that answers which…
The most common failure in early Enterprise Architecture work is misreading the business strategy. This…
Manufacturing integration must balance the rapid harmonization of management reporting with the safe migration of…
A TOGAF-based framework for identifying, evaluating, and mitigating SAP implementation risks in Tier 1 automotive…
Learn how Enterprise Architects can apply TOGAF Initial Risk Assessment, mitigation, and Residual Risk Assessment…
Learn how Outputs, Deliverables, Artifacts, and Outcomes differ in Enterprise Architecture through a practical automotive…