This article provides insights into the latest version (2024) of the SAP Enterprise Architecture Framework which was initially released beginning of 2023. Based on your feedback, further expansion of the reference architecture content and the acquisition of LeanIX a more sophisticated version has been released.
Enterprise Architecture Framework (EAF) - Change log
- Updated visualisation of the EAF
- Practice as a fifth cornerstone of the EAF introduced
- Introduction of the domain model
- Updated Metro Map
- SAP LeanIX modelling of key artefacts
History: The need for a common and aligned framework
Over the course of time, we have seen as Enterprise Architects in SAP Business Transformation Services, both SAP internal as well in the interaction with customers and partners, that different methodologies, artifacts, and approaches are used in architecture engagements. With the creation of a reference architecture the need for a common Enterprise Architecture Framework at SAP was obvious as different departments within the SAP organization produce and consume the content of the reference architecture. Only one common “language” and approach would ensure that information can be leveraged in an efficient and effective way both inside and outside the organization.
SAP Enterprise Architecture Framework
The SAP Enterprise Architecture Framework is centered around the following four cornerstones:
Methodology:
The SAP EA Methodology is based on industry standards (such as TOGAF®, BPMN™, UML®, APQC®) and supports enterprise architect journeys from the definition of target architectures to implementation and continuous transformation. It introduces concepts, artifacts, techniques, and principles.
Reference Architecture Content:
SAP Reference Business and Solution Architecture Content maps the business strategy and architecture to SAP solutions.
Tooling:
EA Tooling supports documentation, adjustment and consumption of EA artifacts complying to SAP EA Methodology.
Practice (NEW):
The EA Practice is the organizational implementation of EA. It operates enterprise architecture within the organization, by adopting the EA methodology and establishing governance processes incl. change management process for the framework.
Services:
EA Services are supporting transformations by applying the methodology and using EA tooling and reference architecture content. Services can be sourced from SAP, other external providers, or provided by the practice. They can include enablement of different EA target roles in customers’ and partners’ organizations provided
Figure 1 – SAP Enterprise Architecture Framework
SAP Enterprise Architecture Methodology
The SAP Enterprise Architecture Methodology is structured around a well defined set of architecture domains covering the full lifecycle of an Enterprise Architecture engagement:
Figure 2 – Enterprise Architecture Methodology - Domain Model
Definition of domains
| Architecture Vision | The Architecture Vision domain focuses on an initial sketch on what the overall outcome of the architecture work is expected to be. To ensure success, relevant stakeholders should be identified and the context from both business and IT should be gathered. This includes already formulated business and IT strategies, which will be refined for the selected scope within the Strategy & Motivation domain. Finally the “statement of architecture work” defines the scope and requirements of what to do in next phasis of the project. |
| Strategy & Motivation | The Strategy & Motivation domain is the first part of “Business Architecture” deriving objectives (value drivers) from company strategic priorities and long-term goals establishing company's vision. This domain ensures that the enterprise architecture is not only aligned with the business strategy but also motivates stakeholders by clearly communicating the benefits and rationale behind architectural decisions and transformations. |
| Business Architecture | The Business Architecture domain focuses on describing an organization with reference to all business aspects including capabilities, processes, data, and organizational structure. It facilitates business-led discussions with all stakeholders and decisions on the basis of agreed business terms. It enables communication of business values and impact of architecture work to all stakeholders. |
| Solution Architecture | The Solution Architecture domain covers reference, base, target, and/or transition architectures focusing on capabilities, processes, data, and organizational structure. The value of Solution Architecture lies in its ability to align technology solutions with business goals and requirements. Solution architectures serve as a bridge between the business side and the technical side of an organization, ensuring that technology solutions are designed and implemented in a way that meets business needs. |
| Technology Architecture | The Technology Architecture domain focuses on documenting how the target solution architecture building blocks are delivered via technology components (e.g. operating systems, virtualized environments, hardware, networks) and depicts the deployment of organization’s IT systems in specific data center locations. |
| Roadmap & Transition | The Roadmap & Transition domain focuses on uncovering project growth opportunities and managing the transition of systems or processes. It involves pinpointing potential advantages, planning migrations, and executing changes to achieve the project's objectives efficiently. |
Requirements & Governance | The Requirement and Governance domain is not linked to a particular phase of an architecture engagement, but includes relevant governance artifacts like a risk catalog, architecture principles and captures important architecture decision as Architecture Decision records (ADR). Requirements are not only collected when creating the statement of architecture in the architecture vision domain, but can come up any architecture domain. |
The overview of artifacts is visualized in form of a Metro Map (see figure 3), which depicts the architecture domains in conjunction with the artifacts rendered as stops on the metro map.
Please note that the arrows in the figure outline rather a natural flow than a strict sequence of artifacts. Majority of the artifacts are based on the TOGAF Version 10 standard.
Beside the TOGAF based artifacts, we complemented our framework with additional artifacts which have been proven to be successful in the stakeholder interaction for example the Business Model Canvas (now in its latest version as Sustainable Business Model Canvas) or the Business Context Diagram (complementing the TOGAF Solution Context diagram)
Figure 3 - SAP Enterprise Architecture Methodology – Metro Map
Reference Architecture Content
A key highlight of the SAP Enterprise Architecture Framework are the Reference Business Architecture (RBA) and the Reference Solution Architecture (RSA), as both provide standardized and authored reference content provided by SAP.
The SAP Reference architecture can be applied in SAP’s Customer Facing EA ADM and supports multiple of the artifacts outlined in figure 3.
The Reference Business Architecture and Reference Solution Architecture are structured alongside the following four architecture views:
- Capability View
- Process View
- Data View
- Organization View
Figure 4 - SAP Enterprise Architecture Methodology - Overview of core domains & models
The four views cover a business and IT related model and allow the navigation between these two perspectives. Having said that, navigation between different views and respective entities adds significant value, as the content of the reference architecture is an official and authored content.
For further information on the Reference Architecture, please refer to the blog of Maria Goltz SAP Reference Architecture Content: An Overview
Enterprise Architecture Tooling
The SAP Enterprise Architecture Framework is featured by a set of SAP tools, among these are
- SAP LeanIX EAM
- Signavio Process Explorer and Signavio Process Manager
- SAP Business Accelerator Hub
- SAP Discovery Center
- SAP Trust Center
Enterprise Architecture Service
The SAP Enterprise Architecture Framework comes along with a set of predefined enterprise architecture consulting service. As every organization is unique in its setup and level of maturity, individual services can be tailored to specific needs. This happens in a modular service approach. Following services build the modular foundation alongside the known architecture domains:
Figure 5 – Enterprise Architecture Service Offering
The outlined services can be booked individually and are delivered by experienced SAP Enterprise Architects around the world. For further information, please get in touch with your SAP Account team.
Conclusion
The SAP Enterprise Architecture Framework is a comprehensive Framework which combines a sound methodology with a valuable reference architecture featured by a set of tools and supported by service offerings. It offers the opportunity to create a common language and practices within the SAP Enterprise Architecture community with the potential to accelerate and streamline enterprise architecture engagements.
Interested in learning more about the SAP Enterprise Architecture Framework?
If you are interest to learn more about the new SAP Enterprise Architecture Framework you can book our new training offering which is described in this blog: SAP Enterprise Architecture Training - SAP Community Groups
44 Comments
