The Implementation phase of PEAF is concerned with making the necessary identified changes and adjustments to the enterprise in preparation for it to be able to utilise Enterprise Architecture. The work required to be undertaken is totally dependant on each enterprises specific goals and timescales identified in the Prepare phase of PEAF (which considers their current and target EA maturity levels).

Prepare EA Education

This process creates the necessary communication materials required for ongoing and continuous education and two way communication. It is concerned with educating people about Enterprise Architecture in general and about the framework the organisation has chosen in particular.

This process, coupled with the provision of training and education in the “Operate” phase, is the most important of all the processes.

Change Motivation Model

This process effects the cultural and human change necessary to bring about a more long term view of the management and direction of the organisation.

Without this, it does not matter how many principles, processes or models you adopt as the direction and management will continue to compromise the future of the organisation for short term (usually) financial individual gain.

Define the EA Metamodel

This process defines the Metamodel that will be used for gathering and analysing information that is to be stored in the EA Modelling Tool.

Since some EA Modelling Tools have pre-existing and somewhat static Metamodel’s this process may not be required. However, even if the approach is to use whatever Metamodel that comes with the Tool that will be selected, it is still a good idea to go through this process to identify the initial entities, relationships and views that are initially important to the enterprise as beginning with a massive and detailed Metamodel can dilute the focus.

In addition, the Metamodel for the Structural domains (e.g. Current, Target and Intermediate as distinct from the Strategy, Portfolio and Principles domains) is somewhat driven by the process for populating the current model. I.E. based on the question(s) that are required to be answered.

Another dimension to be aware of is that whatever Metamodel is chosen, the Metamodel will expand as times goes on and therefore consideration should be given not only to the initial Metamodel but also how that Metamodel will grow over time and therefore consideration should be given to an EA Metamodel Roadmap.

Setup an EA Modelling Tool

This process is concerned with the procurement of an EA modeling tool.

It should be noted that any information within the organisation is not an island and therefore due consideration must be give to how the EA tool fits in with the landscape of other tools utlised by the organisation (e.g. portfolio planning and management, Risk Management, Configuration Management and change management, etc).

Setup EA Governance

This process creates a set of principles and puts in place the governance structure required to operate them effectively.

Mitigate the EA Risks

This process identifies and mitigates the risks associated with an EA initiative.

Plan

This is an example Microsoft Project Plan which assumes an organisation is at level 1 in all areas of maturity, and wishes to move to level 2 in all areas of maturity.