HOPEX Business Architecture : HOPEX Business Architecture : Introduction to HOPEX Business Architecture : The HOPEX Business Architecture method
   
The HOPEX Business Architecture method
 
Building capability maps and business function architectures
Describing the existing architecture of business capabilities
Describing Business function architecture elements
Describing business capability implementation by the business functions
Identifying strategic transformation objectives
Identifying drivers
Assessing the relative importance of drivers
Defining the transformation roadmap
Defining the events and the first enterprise stages
Defining enterprise stages
Assessing a business capabilities map
Defining the transformation roadmap
The method described in this guide is represented in the schema below.
Description of business capabilities and the existing architecture: this first step consists, on the one hand, in defining what the enterprise can deliver (business capabilities), and on the other hand, in defining how it can be structured to deliver this (business function architecture). For a business capability, you can identify the KPI dimensions of interest for the capability which are used to assess business value and performance (e.g.: for a delivery capability, we are interested in the "delivery time" expressed in minutes).
*For more details, see "Building capability maps and business function architectures".
Assessing the transformation drivers: this second step is based on gathering and assessing (SWOT) drivers. The transformation objectives are then deduced from this step.
*For more details, see "Identifying strategic transformation objectives".
Initiating the transformation roadmap: this third step is based on the description of the operational systems of the enterprise, performed during the first step as well on the transformation driver analysis, to schedule the changes to plan to perform the transformation objectives and thus define the courses of action (strategies and tactics) to be implemented with a view to reaching the defined objectives and specify the exhibited business capabilities for each Enterprise Transformation Stage.
For a given exhibited business capability, in a given stage, you can define the key performance indicator (KPI) that is used to define the expected service level requirement, when implementing the capability for the enterprise transformation stage in question (e.g.: for a for a “product delivery” business capability, we expect, for the 'delivery time' KPI dimension, a "delivery time < 30 minutes" in a first enterprise transformation stage, then a "delivery time < 20 minutes" in a later enterprise transformation stage).
*For more details, see "Defining the transformation roadmap".
Defining the solution architectures: this fourth step can be performed by using HOPEX Business Architecture and the Enterprise Architecture solutions jointly; it is used to identify and describe the existing and target solution building blocks and to identify which business capabilities (or business functions) they contribute to implement.
The additional solutions of the HOPEX platform are used to describe in more detail your target organizational models (organizational, application and technological solution building blocks).
*For more details, see "Describing implementation of a transformation plan".
Finalizing the transformation roadmap: this last step aims to finalize the transformation roadmap, in association with each solution environment required to reach the transformation objectives.
*The order of these steps is given by way of information. To define a finalized transformation roadmap, several iterations of this cycle should be performed.
This presentation is based on the example of a pizza making and delivery company that has decided to reorganize itself to ensure pizza delivery and improve product quality.