Enterprise Architecture Capability Reference Model

The Enterprise Architecture Capability Reference model is represented by a simple graphic and a complete textual description. Central to the Reference Architecture are the EA purposes.

Based upon the organizations preferences current & target execution is assessed to provide priority for improvement. A simple measure of competency is used: Examining, Emerging & Experiencing.

  • Examining identifies that the EA team has limited ability to deliver to expectation. Individual delivery is possible, but the organization cannot expect consistent delivery.
  • Emerging identifies that EA team ability to deliver to expectation is coming into practice. Individual delivery is probable, but the organization cannot expect consistent high-functioning delivery.
  • Experiencing identifies that EA team can deliver consistently to expectation.

EA Capability Atlas Components

Conexiam's EA Capability Atlas is comprised of

  • Reference Architecture (Capability Component Type)
  • Presentation material distinguishing General Business, Purpose, Foundation categorization
  • Presentation material discussing Central Purpose of an EA Capability
  • Presentation material describing all Capability in the Reference Architecture
  • Information gathering Guide that follows our paper “A Leader’s Approach to Establishing and Evolving an EA Capability
  • Analytic Guide
  • Roadmap report template

Navigate Atlas Design

Navigate Atlases are designed to to address the problem of getting to done.
Through each Atlas we gracefully address new critical questions. The exercise is not to gather all the information that might be useful in some potential future.Just the information we currently need.

  • How to describe an architecture
    Extensible content metamodel built on a end-to-end core
  • Support for gathering information
    Structured gathering templates & presentation stock material
  • Support for analysis
    Analytic support and Guides
  • Support for reporting
    Purpose based reporting & presentation stock material
  • Training materials

Conexiam Atlases address purpose and specialized domain.

Central purposes of enterprise architecture

Typically, there are four broad purposes of an EA Capability:

  • EA to support Strategy: provide an end-to-end target architecture, and develop roadmaps of change over longer time periods. In this context, architecture is used to identify change initiatives and supporting portfolio and programs.
  • EA to support Portfolio: Deliver EA to support cross-functional, multi-phase, and multi-project change initiatives. In this context, architecture is used to identify projects, set their terms of reference, align their approaches, identify synergies, and govern their execution.
  • EA to support Project: Deliver EA to support the Enterprise’s project delivery method to assure compliance with architectural governance, and to support the integration and alignment between projects.
  • EA to support Solution Deployment: Deliver EA that is used to support solution deployment by defining how the change will be designed and delivered, and finally, act as a governance framework for change.

EA Capability Reference Model

Capability Model Heirarchy

The Capability model is hierarchical, with Purpose Architecture supported by Foundation capabilities, which are further broken down into detail.

For example, the ability to create domain architecture supports all purpose-based architecture. The outcome desired is an architecture that addresses a purpose, rather than delivering particular domain architecture.

Capability Modelling

In Navigate, Conexiam uses "Capability" as a management concept that facilitates planning improvements in the ability to do something that must be improved or sustained.

We either derive capability from an organization's Value Propositions or Objectives or use a departmental reference model.

In either case the Capability is a consolidating concept to include all the elements in an ability to do something. Everything that is included in the ability to do something is included in the capability. This can include, organization, business partner, process, equipment, IP, software, location, communication, etc. It really doesn't matter what is included, as long as it is essential in the ability to do something that must be improved or sustained.

When planning improvement we consider three central metrics

  • Efficiency,
  • Fitness, &
  • Maturity

These metrics provide the central requirements that drive the target for everything included in the capability.

Open Roots

Conexiam's EA Capability model has open roots.

The first publication of the base model was the Open Group's "World Class Enterprise Architecture” whitepaper. We used the model and refined it over several years and contributed the essential parts in our paper “A Leader’s Approach to Establishing and Evolving an EA Capability”.

Navigate Atlas Design

Navigate Atlases are designed to to address the problem of getting to done.
Through each Atlas we gracefully address new critical questions. The exercise is not to gather all the information that might be useful in some potential future.Just the information we currently need.

  • How to describe an architecture
    Extensible content metamodel built on a end-to-end core
  • Support for gathering information
    Structured gathering templates & presentation stock material
  • Support for analysis
    Analytic support and Guides
  • Support for reporting
    Purpose based reporting & presentation stock material
  • Training materials

Conexiam Atlases address purpose and specialized domain.

Navigate Guides

Conexiam Guides include proven tools and techniques, including:

  • Reference model (e.g. IT4IT, APQC Process Classification Framework)
  • Information gathering templates (e.g. Business Process spreadsheet)
  • Viewpoint Library (for describing, proving and analyzing)
  • Architecture Trade-off Method
  • How-to for formal modeling with Avolution ABACUS®
  • Governance toolset
  • Process touchpoints

Conexiam has used Navigate in a variety of business sectors including utilities, transportation, energy, telecom, defense and financial services.

Throughout Navigate we maintain a standard set of definitions, and purposes. We find it is often more useful to explain the purpose of a specialized term than attempt a definition.