Content deleted Content added
Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta15) |
Rescuing 3 sources and tagging 0 as dead.) #IABot (v2.0 |
||
Line 4:
== Overview ==
The FDIC's framework for implementing its [[Enterprise Architecture]] was based on Federal and industry best practices, including the Chief Information Officer (CIO) Council's [[Federal Enterprise Architecture Framework]] (FEAF) and the [[Zachman Framework]] for Enterprise Architecture. FDIC's framework was tailored to emphasize [[security]]. The historic FDIC EA framework complies with the FEAF and highlights the importance of security to all other components of the architecture.<ref name="FDICOIG05">[http://www.fdicoig.gov/reports05/05-018-508-figure1.shtml Implementation of E-Government Principles] {{Webarchive|url=https://web.archive.org/web/20090114045425/http://fdicoig.gov/reports05/05-018-508-figure1.shtml |date=2009-01-14 }} AUDIT REPORT, Report No. 05-018, May 2005</ref>
The FDIC EA framework included five components. The first component, the Business Architecture, focused on FDIC's business needs. The next three components, the [[Data Architecture]], Applications Architecture, and Technical Infrastructure Architectures, focused on the technological capabilities that support the business and information needs. The final component, the [[Security Architecture]], focused on specific aspects of interest to the Corporation that span the enterprise and must be integral parts of all other architectures.<ref name="FDICOIG05"/>
Line 11:
Historically, Federal agencies managed IT investments autonomously. Until the new millennium, there was little incentive for agencies to partner to effectively reuse IT investments, share IT knowledge, and explore joint solutions. Starting in the second half of 1990 a collective, government-wide effort, supported by the Federal CIO Council, utilizing the [[Federal Enterprise Architecture]] (FEA), was undertaken in an effort to yield significant improvements in the management and reuse of IT investments, while improving services to citizens, and facilitating business relationships internally and externally.<ref>FDIC (2003). ''[http://www.iriboffice.ir/LinkClick.aspx?fileticket=up56ppcNQ4M%3D&tabid=246&mid=634 Information Technology Strategic Plan 2004–2007]''</ref>
The Federal Deposit Insurance Corporation (FDIC) first realized the value of Enterprise Architecture in 1997, when two business executives had to reconcile data that had come from different systems for a high-profile report to the banking industry. The FDIC's first EA blueprint was published in December 2002.<ref>Gregg Kreizman, Cathleen E. Blanton (2005) "[http://www.aea-dc.org/resources/2006-7-12-Gail-Verley-FDIC-EA-Business-Alignment-Gartner.pdf The FDIC Is Aligning IT to Business Through Enterprise Architecture] {{Webarchive|url=https://web.archive.org/web/20090320115109/http://www.aea-dc.org/resources/2006-7-12-Gail-Verley-FDIC-EA-Business-Alignment-Gartner.pdf |date=2009-03-20 }}" Gartner, Inc.</ref>
In 2004 the FDIC received a 2004 Enterprise Architecture Excellence Award from the [[John Zachman|Zachman Institute for Framework Advancement]] (ZIFA) for its initiative to manage corporate data collaboratively.<ref>[http://www.fdic.gov/news/news/press/2004/pr13104.html FDIC Receives Technology Award]</ref>
Line 48:
== Further reading ==
* Gartner (2005) ''[https://web.archive.org/web/20090320115109/http://www.aea-dc.org/resources/2006-7-12-Gail-Verley-FDIC-EA-Business-Alignment-Gartner.pdf The FDIC Is Aligning IT to Business Through Enterprise Architecture]''. Industrial research paper.
* Pallab Saha (2007). ''Handbook of Enterprise Systems Architecture in Practice''. Chapter IX gives a detailed case study of the FDIC.
| |||