This dimension deals with the role of enterprise architecture in the organization.  An immature organization may not have any enterprise architecture practice, whether formal or informal.  Architecture must provide the strategic view necessary to build the right solutions, as well the necessary constraints, principles, and guidelines to ensure that solutions are built the right way.   Enterprise Architecture normally includes technology architecture, however, that has been broken out into a separate dimension for this model.  Within this dimension, the focus is on solution planning and architecture. 

Level 0: Ad Hoc

At this level, architectural models, if they even exist, do not include services as a component.  The organization may not have an enterprise architecture practice, or the Enterprise Architecture team may not be responsible for strategic planning.  A portfolio of all existing applications may or may not exist, and a reference model for the future state architecture probably does not exist. 

Level 1: Common Goals

At this level, some formality needs to exist in the architectural process.   A current state analysis resulting in an as-is application portfolio should be complete.  At least one target state should be identified, with an appropriate roadmap articulated on how to get there.  This effort may not encompass the enterprise, however it should cover a broad enough range of the business to be of significance.

In addition to this basic strategic planning effort on what solutions will be created, guidance should also be provided on how those solutions should be created, mapping the technologies available from the infrastructure to the components of a reference solution architecture. 

Level 2: Foundation

At this level, the enterprise architecture should be formalized, with multiple target states identified as milestones at 6-month intervals.  The organization should have begun an application rationalization process to determine what applications are no longer needed in the enterprise, what gaps exist, and what systems need to be extended.

Level 3: Method and Governance

At this level, IT planning is rooted in Enterprise Architecture; however, there may still be a clear handoff between the business and IT in the strategic planning efforts.  Within the architectural models themselves, the focus has shifted away from applications, and instead focuses on the use of services to represent the enterprise.  This services-based view is the Master Service Blueprint.

Level 4: Service-Oriented Enterprise

At this level, strategic planning is an enterprise effort, not two distinct efforts.  Previously, the business may have had one effort, handing off their results to IT for their own effort.  This should no longer be the case.  The reference models are utilized in this process, with the Master Service Blueprint becoming a primary tool for project definition in contrast to a Master Application Blueprint.  The architectural models encompass the enterprise and are refreshed on a regular basis based upon changes to the business strategy.

Level 5: Optimized

At this level, the effort must move away from a centralized model of strategic planning, to a decentralized model of innovation, including not just the internal organization, but also customers and partners.  Companies at this level are likely defining the new standards in architecture, rather than applying what others have deemed best practice.