Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel3
outlinefalse
stylenone
typelist
printabletrue

...

The Merge update clarification popup provides a guided step-by-step interface to help users update merge two capabilities while ensuring clarity on the intended outcome. It prompts users to assess how they want to combine processes, dependencies, and functions of the capabilities, and how the merge will impact business units.

...

For instance, if both capabilities include separate approval processes for similar tasks, discarding the redundant process would involve keeping only one streamlined approval process that covers the necessary functions, thus avoiding duplication and saving time.

...

Update merge clarification popup questions

These are the defining questions and options in the Merge capability popup to define the method of update merge.

 Defining question 

 Option A 

 Option B 

 Option C 

 Fully integrate the processes,  functions,  and elements of both capabilities into the Target capability? 

 Yes 

 No 

 Discard duplicate or conflicts in processes,  functions, and elements? 

 Yes 

 No 

 Prioritize specific attributes (e.g.  performance indicators, dependencies) from which capability? 

 Source 

 Target 

 If the capabilities are in different business units, should the updated capability maintain relevance to: 

Both

 Business Unit 1 

 Business Unit 2 

 Link the dependencies from each business unit? 

 Yes 

 No 

 

 If the capabilities are in the same business unit: 

 

 

 

 Streamline the dependencies and processes within that unit? 

 Yes 

 No 

 

 Create unified dependencies? 

 Yes 

 No 

 

 Combine attribute data from both or select from one? 

 Source 

 Target 

 

 Prioritise a capability when merging their technologies and tools? 

 Source 

 Target 

 

 Include the risks and opportunities from which capability? 

 Source 

 Target 

 

 If from different business units,  align the Target capability with the strategic objectives from the Source? 

 Yes 

 No 

 Retain both child elements,  processes,  and functions under the new merged capability? 

 Yes 

 No 

 Preference which capability for elements,  processes, and functions?

 Source 

 Target 

 Integrate child processes 

 Yes 

 No 

 

 Discard redundant processes 

 Yes 

 No 

 

Update merge clarification popup tooltips

 Defining question 

Tooltip

 Fully integrate the processes,  functions,  and elements of both capabilities into the Target capability? 

Choose 'Yes' to combine all elements seamlessly from each source; select 'No' to keep them separate.

 Discard duplicate or conflicts in processes,  functions, and elements? 

Select 'Yes' to eliminate duplicates or conflicting elements; choose 'No' to retain them.

 Prioritize specific attributes (e.g.  performance indicators, dependencies) from which capability? 

Choose 'Source' if prioritizing attributes from the original source, or 'Target' for attributes from the target system.

 If the capabilities are in different business units, should the updated capability maintain relevance to: 

Select 'Both' to merge capabilities from both business units, or specify a preference between Business Unit 1 or Business Unit 2.

 Link the dependencies from each business unit? 

Choose 'Yes' to create links between dependencies; select 'No' to handle them separately.

 If the capabilities are in the same business unit: 

N/A

 Streamline the dependencies and processes within that unit? 

Opt for retaining only key processes that align with strategic goals; otherwise, retain all.

 Create unified dependencies? 

Consider linking supporting documents across units for comprehensive integration.

 Combine attribute data from both or select from one? 

Prioritize attributes from one capability over the other.

 Prioritise a capability when merging their technologies and tools? 

Prioritize technologies and tools from one capability over the other.

 Include the risks and opportunities from which capability? 

Include risks and opportunities from one capability over the other.

 If from different business units,  align the Target capability with the strategic objectives from the Source? 

Choose 'Yes' to adopt strategic objectives from the Source capability into the Target capability's framework; select 'No' to maintain separate strategic alignments.

 Retain both child elements,  processes,  and functions under the new merged capability? 

Select 'Yes' to preserve all child elements from both capabilities; choose 'No' to selectively maintain elements based on other merge preferences.

 Preference which capability for elements,  processes, and functions?

Choose 'Source' to prioritize elements from the original capability, or 'Target' to favor elements from the target capability when conflicts arise.

 Integrate child processes 

Decide on the level of customization required for the integrated capabilities.

 Discard redundant processes 

Select 'Yes' to automatically remove duplicate or overlapping processes; choose 'No' to manually review and decide on process retention.

Unmerge

To unmerge elements from the business architecture domain of one organizational unit from another, follow these steps:

...