Deploying the Strategy to Execution Use Case and/or Migrating from Strategic Planning & Execution Use Case

A major overhaul is being done to the Strategic Planning and Execution (SPE) Use Case. By introducing the Strategy to Execution Use Case (S2E), we redesigned much of the Use Case in order to better reflect how an organization operates and address some of the key questions they face. There are several key differences between the SPE Use Cases and the S2E Use Cases that will be discussed in this document.

Ardoq’s S2E solution builds on Use Cases including Organizational Metamodel Modeling, Business Capability Management (BCM), and Application Lifecycle Management (ALM). To learn more about requirements and configuring your Ardoq implementation to establish connections between these use cases, please refer to the Strategy to Execution Metamodel document.

As of now, configuring connections between Use Cases is a manual process, you can check out the following link for more information. If you have any questions about the configuration process, please contact our support team.

Table Of Contents:

S2E ad SPE: A Comparison of Key Differences
SPE to S2E Metamodel Changes (Component & Field Changes)
Deploying S2E with Existing Use Cases
Asset Changes

S2E and SPE: A Comparison of Key Differences:

S2E covers a broader range of strategic planning and execution topics. The focus of SPE is more on managing and executing projects, with an emphasis on aligning projects with strategic goals.
SPE does not cover topics such as company-level objectives, objective progress, and execution impact and benefits.
The SPE provides an understanding of enterprise project management and execution. Through SPE, risks and challenges specific to projects can be evaluated, as well as the alignment between projects and strategic goals.
S2E provides a comprehensive overview of strategic planning and execution within an enterprise, covering a broader range of topics.

SPE to S2E Metamodel Changes

Although much of the model is the same, there are some differences in the component types, which have been expanded to allow for different approaches.

Strategic Planning and Execution Metamodel:

Strategy to Execution Metamodel:

Component Changes Overview:

Component	New/removed/changed	Description	Evt. replacement
Strategy	Removed		Objective
Objective	Changed	The definition expanded to include Strategy	-
Key Result	New		-
Project	Removed		Initiative
Initiative	New	Replaces the project component to account for agile development	-
Capability Delta	New	Represents the change to the business capability	-
Folder	New	Used to group Components within a workspace, specifically to help manage visualization.	-

Deploying S2E with existing Use Cases

S2E includes component types from other Use Cases besides SPE. Additional Use Cases with component types in S2E are listed below:

Organizational Modeling (Organizational Unit & People)
Business Capability Modeling
Application Lifecycle Management (Application)

The Business Capability workspace is the only existing workspace impacted by the S2E Use Case because it introduces the Business/Technical Capability Delta and Folder Components to the workspace. If installing the S2E bundle in an environment that already has use cases installed, the Capability Delta component type and the Calculated Active Period field will need to be created manually in the Business Capability workspace for the bundle assets to work.

To learn more about the different components and the rationale behind the metamodel check out the Strategy to Execution Purpose, Scope, and Rationale and Metamodel documents.

Fields Changes Overview:

Check out the Strategy to Execution Metamodel document for the specific Gremlin Queries used for calculated fields.

Field	Component Type	New/removed/changed	Evt. replacement
Lifecycle Phase	Project/Initiative	Removed	Active Period
Live	Project/Initiative	Removed	Active Period
Delivery Complexity	Project/Initiative	Removed
Strategic Impact	Project/Initiative	Removed	Strategic Investment Category
Total Direct Cost	Project/Initiative	Unchanged
Initiative Stage	Initiative	New	-
Initiative Status	Initiative	New	-
Initiative Type	Initiative	New	-
Percent Progress	Initiative	New	-
Active Period	Initiative	New	-
Business Case	Initiative	New
In Conflict	Initiative	New	-
Strategic Investment Category	Initiative	New	-
Budgeted CAPEX	Initiative	New	-
Budgeted OPEX	Initiative	New	-
Total Budgeted Cost	Initiative	New	-

For more information on the S2E and Cost fields and their respective values and/or Gremlin code please refer to the S2E Metamodel and ITCM Metamodel documents