• slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider3

    A3 KAM - Triple A(Architectural, Actionable and  Augmented) Knowledge Assets Management

  • slide1

    Enterprise Architecture 3.0 (EA3.0) - the third wave in Enterprise Architecture approaches

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

Strategy to Capability

In two papers the importance and the use of the Strategy-to-Capability model is explained. In the first paper, Plan to Capability - Development and Semantics, the history of the development of the model is explained together with the semantics of the relations between the different components. In the second paper, Plan to Capability - Model, the usage of the strategic plans to derive at the model is explained.

 

Problems and Solutions

In contemporary approaches to enact the implementation of the strategy it is often found that the strategic plans aren’t detailed enough and the derivation is often tiresome. The result is that the details of the subplans might result in plans and concepts that miss the original power, i.e. the Value Creation amongst others, of the strategy. With the help of the approach (ABODE™) and the Enterprise Architecture (EA3.0™) solutions, methods, tools and techniques are supporting:

  1. Modelling the Strategy in so-called Capabilities with the related products, business services, processes, and functionalities, and IT assets
  2. Collect the Capabilities into an organized Capability Map
  3. Develop the Capabilities into an intuitively usable Knowledge Function Model for the development and enrichment of these functions
  4. Model the Enterprise PROSA (Principles)

 

Tools to support Strategy to Capability

The following tools support the Strategy to Capability:

  •  Architecture Management
 
  • AAM/Capability Design  
designing the Capability according to the Strategy
  • AAM/Capability Management
managing, planning and developing Capabilities; connection to Information Planning
  • AAM/Capability Map
designing the Capability Map; connection to Knowledge Function Modeling
  • AAM/Principles Derivation
based on the Strategic Principles the Principles of each Architecture Domain are detailed on a high level

 

Advantages of the Enterprise Architects approach

  1. The necessary Capabilities can be discussed, planned, and developed
  2. The Capability Map to be used as an effective means of communication throughout the organization
  3. Use the Knowledge Function Model to position the strategic choices at the right functional areas
  4. Use the strategic choices as defined in the Knowledge Function Model during process modeling to derive at the value creation
  5. The SAFe™ Core Values are safeguarded and improved as follows
    • 5.1 Alignment
    • 5.2 Built-in Quality