Enterprise Transformation

A Pragmatic Approach Using POET


◄◄◄ Previous Page         


          Next Page ►►►

Here we see the fundamental levels of Enterprise Transformation based on the fundamental levels of Idealisation/Realisation.

The Direction part of the Enterprise feeds Contextual information into the Transformation part of the Enterprise which delivers Physical Things into the Operations part of the Enterprise.

It should be noted that the Transformation part of the Enterprise may also deliver Physical Things into the Direction, Support or even Transformation (the whole point of POET) part of the Enterprise but we just show Operations here as that is the most common occurrence.

The fundamental levels are:

¨      The Enterprise Context consists of all the things that are not part of the Enterprise (i.e. not directly under its control) but affect or is affected in some way by it. Things like Customers, Suppliers, Partners, Regulators, etc.

¨      The Contextual level consists of the Enterprises Strategy (Mission, Vision, Goals, Objectives, Strategies, Tactics, etc).

¨      The Conceptual level consists of Transformational Roadmaps (Business and Technical), Conceptual Structural Models (Current, Target and Intermediate), and definitions of a series of programs projects and initiatives that effect the transformation.

¨      The Logical level consists largely of Logical structural designs.

¨      The Physical level consists largely of Physical structural designs.

¨      The Operational level consists largely of the CMDB - Configuration Management Database.

While these levels are often portrayed as separate it should be noted that the information at each level is not insular. The information at each level is fundamentally related to the information in the other levels and it is these relationships which are of paramount importance as they provide the glue that makes the whole coherent.

Most relationships occur with the information that exists above and below each level and diminish for levels further away.

This also illustrates that while people may be working with information primarily at one particular level, they need access to information at other levels to understand context (from above) and to understand implications (from below).

In terms of naming these levels there are two fundamentals:

¨      The Enterprise Architecture Model (EA) consists of Contextual and Conceptual information set in the Context of Enterprise Context information and Logical information.

¨      The Enterprise Engineering Model (EE) consists of the Logical, Physical and Operational information set in the Context of the Conceptual information and the Physical World.


Questions to ponder...

Does your Enterprise have the concept of an EA Model and an EE Model?

If not, should it?

Where does your Enterprise draw the boundaries?

Do the boundaries exist?

How are they managed?

◄◄◄ Previous Page          

          Next Page ►►►


© 2008-2019 Pragmatic EA Ltd