Enterprise Architecture Executive Handbook - U.S. Coast Guard
Enterprise Architecture Executive Handbook - U.S. Coast Guard
Enterprise Architecture Executive Handbook - U.S. Coast Guard
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Enterprise</strong> <strong>Architecture</strong> Overview<br />
<strong>Enterprise</strong> <strong>Architecture</strong> (EA) is a way of helping leaders view business and technical information in a<br />
simple way. When complexity is simplified, the value of the underlying information is visible and<br />
executives can make decisions to improve efficiency and effectiveness. EA provides the information<br />
needed by decision-makers to identify both redundancies and gaps in capability among organizational<br />
units.<br />
More formally, EA is the practice of aligning Command, Control, Communications, Computers, and<br />
Information Technology (C4&IT) requirements to mission and performance goals.<br />
The following definitions of EA, as provided by other guiding organizations, support the USCG definition<br />
of EA while providing insight into EA implementation throughout the Federal government.<br />
• Federal <strong>Enterprise</strong> <strong>Architecture</strong> (FEA) Practice Guidance, Nov 2007: EA is a management<br />
practice that maximizes the contribution of an agency’s resources, IT investments, and system<br />
development activities to achieve its performance goals. <strong>Architecture</strong> describes clear relationships<br />
from strategic goals and objectives through investments to measurable performance improvements for<br />
the entire enterprise or segment of the enterprise.<br />
• Chief Information Officers (CIO) Council, 2001: EA establishes a roadmap to achieve an agency’s<br />
mission through optimal performance of its core business processes within an efficient information<br />
technology environment. Simply stated, enterprise architectures are ‘blueprints’ for systematically and<br />
completely defining an organization’s current (baseline) or desired (target or to-be) environment.<br />
• Federal <strong>Enterprise</strong> <strong>Architecture</strong> Framework, Sept 1999: The Federal <strong>Enterprise</strong> <strong>Architecture</strong> is a<br />
strategic information asset base that defines the business, information necessary to operate the<br />
business, technologies necessary to support the business operations, and transitional processes for<br />
implementing new technologies in response to the changing needs of the business.<br />
• Office of Management and Budget (OMB) Circular A-130: An EA is the explicit description and<br />
documentation of the current and desired relationships among business and management processes<br />
and information technology. This definition supports the approach of optimizing the organization’s<br />
structure and business processes before making IT investments.<br />
Figure 1: Three-part EA Program<br />
Figure 1: Three Stage EA Diagram<br />
An EA includes an As-Is EA, a To-Be (Target) EA, and an <strong>Enterprise</strong> Transition Plan, as depicted in<br />
Figure 1.<br />
6