• slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slide1

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

  • slider3

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

Proposition Modeling

With the Proposition Model all the important architectural components of the Service Delivery, like the Actor (customer), the Life Event or Role, the Product, the Business Service, the Contract, etc. are modeled. When this is performed for several Product types, patterns of the service delivery can be distinguished. If the service delivery of different Product use the some components, the service delivery can be generalized and optimized.

 

Next, the Proposition Model, when completed, can be used to develop the Conceptual Object Model, the Knowledge Function Model, and the Service Delivery concept. Within the Enterprise Architects approach the different maintenance Apps for the components of the Proposition Model can be generated, and next all Products, Contracts, Business Services, etc. can be maintained. In this way the Product and Service Catalog can be established, printed or published on the internet.

 

Problems and Solutions

Within contemporary approaches the proposition model is part of the work of the Marketing and Sales departments.

  1. The ability of the transition process becomes very inflexible
    This is due to the fact that knowledge functions that enable to delivery, and maintainability of products, business services, and product or service oriented resources is difficult to implement when new types of business service delivery are introduced
  2. The Knowledge Function model is incomplete
    Because there are no functions defined in the model, they have to be introduced, including delivery and maintenance functionalities
  3. The Conceptual Object Model is incomplete initially
    Often the different important Enterprise Objects concerning the Service Delivery concept are often not foreseen in the Conceptual Object Model. However, it is of top priority that these – often simple but essential – Enterprise Objects are defined, because there is often real rework necessary to solve these omissions
  4. The Business Service Delivery concept is incomplete
    For the Business Service Delivery concept, in which not only the Pain and Gain issues are relevant, but all Value Creation dimensions, vectors and parameters concerning the Proposition components are relevant

 

Tools to support Proposition Modeling

The following tools support the Proposition Modeling:

  • Marketing Management
 
  • AMM/Proposition Modeling
designing the Proposition Mode
  • AMM/Generating Proposition Apps    
generating the maintenance Apps for Proposition components
  • AMM/Generating KFM
generating the Knowledge Function Model based on
 
 
 
Strategic choice mapping on the Knowledge Function Model
 
Notification of counterproductive Value Creation on Knowledge Functions

Advantages of the Enterprise Architects approach

The problems when the Proposition Model and its components are not used in the Knowledge Function Model is that:

  1. The maintenance Apps for the different components cannot be automatically generated
    Generating the maintenance apps is very simple, so the omission will lead to diminishing a lot of time, costs, and work
  2. The maintenance Apps cannot be used to establish and maintain the Product and Services Catalog
    Together with the maintenance Apps of the different components and their relationships it is possible to create the Product and Services Catalog, leading to the omission to develop this separately
  3. The SAFe™ Core Values are safeguarded and improved as follows
    • 3.1 Alignment
    • 3.2 Built-in Quality
    • 3.3 Transparency
    • 3.4 Program Execution