EA management strategyThe EA managment framework
one EA or federated EAEA manangement strategy One EA or Federated EA
In the preamble of Architecture principles for the US government ,
These principles support a single Federal Enterprise Architecture to achieve operational excellence for the American public.
The federal government is a single, unified enterprise
The federal government operates as a single enterprise with decision-making flexibility at the agency level.
A single enterprise with shared strategic objectives, common governance, integrated management processes and consistent policies improves the implementation of government-wide strategies and the coordination of the delivery of agency citizen services.
Government optimizes resource allocations across the enterprise to achieve common goals.
• Government optimizes information across the enterprise to support services and processes.
• Architectural designs integrate services for efficiency and keep autonomy of operations for effectiveness.
• Architectural designs identify and accommodate distinctive (non-homogenous) approaches to maintain important policy objectives.
Federated Architecture, similar to a Federated Government in the United States, subjects to different administration. Each State has its own government. Take the example of the Federal Department of Transportation and the State Department of Transportation. They all follows the same guidelines but under different administration. It is easy to understand that there will be many unhappy drivers if US DOT have to worry about the state road and county road. In an object oriented concept, Federated Architecture is under the same gigantic object with many different instances, the Federated Architecture use the same EA framework and models, but each administration have its own instance.
1.0 THE FEDERATED ENTERPRISE ACHITECTURE APPROACH
1.1 Federated EA governance
In a federated EA architecture approach, the enterprise establish a EA master plan to establish the EA strategic direction. Under the master plan, each business unit conduct their business area enterprise architecture design based on their business need. The headerqartor serve as the facilitator, the coordinator and the orchistrator to compile and consolidate the overall enterprise architecture. It is essential to establish the EA meta data standards
1.1.1 EA must be appropriately compartmentalized
Example : The federal high way department, the state DOT, the county DOT
In the evolution of EA, there are different EA approach, some EA approach suggest EA in one enterprise approach and the others suggest EA is a federated effort. Based on the analysis on the structure of enterprise infrastructure, it is suggested that EA must be must be appropriately compartmentalized within the enterprise. There are global infrastructure for the entire enterprise, business area infrastructure for departmental , line of business infrastructure for different components. It is analogy to highway system, the federal government takes care the interstate highway, State government have the state route, County government handles the local roads.
The Practical guide to Federal Enterprise Architecture by the CIO council state that
“By developing this enterprise-wide understanding of business processes and rules, and information needs, flows, and locations, the agency will be positioned to make good decisions about whether the enterprise, and thus the EA, can be appropriately compartmentalized. Without doing so, scoping decisions about the EA run the risk of promoting “stove-piped” operations and systems environments, and ultimately sub-optimizing enterprise performance and accountability”