FDIC Enterprise Architecture Framework: Difference between revisions

Revision as of 19:49, 28 January 2020

Latest revision as of 09:10, 3 May 2025

(5 intermediate revisions by 4 users not shown)

Line 1:

{{Short description|none}}

{{Update|inaccurate=yes|date=January 2013}}

[[Image:FDIC’s Enterprise Architecture Framework.jpg|thumb|320px|FDIC’sFDIC's Enterprise Architecture Framework from 2005.<ref>OIG (2005). [http://www.fdicoig.gov/reports05/05-018-508.shtml Implementation of E-Government Principles] {{Webarchive|url=https://web.archive.org/web/20090114041340/http://fdicoig.gov/reports05/05-018-508.shtml |date=2009-01-14 }}. May 2005</ref>]]

The '''FDIC Enterprise Architecture Framework (FDIC EAF)''' was thean [[Enterpriseenterprise Architecture frameworkarchitecture]] offramework thedeveloped Unitedby Statesthe [[Federal Deposit Insurance Corporation]] (FDIC) to align its business processes and information technology systems. AIntroduced lotin of2002 theand currentformalized articlearound 2005, it was isbased abouton the [[Zachman Framework]] and the [[Federal Enterprise Architecture Framework]] developed(FEAF), aroundwith 2005,a andstrong currentlyemphasis annoon 2011security out-of-date.{{citationto needed|date=Januaryprotect financial data and systems. 2013}}

By 2011, the framework was considered outdated,{{citation needed|date=January 2013}} and it was likely deprecated as part of the federal government’s shift toward standardized enterprise architecture practices, such as the "Common Approach to Federal Enterprise Architecture" introduced in 2012, which aimed to enhance interoperability and reduce agency-specific frameworks.<ref name="CA FEA">whitehouse.gov (May 12, 2012)[https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/common_approach_to_federal_ea.pdf The Common Approach to Federal Enterprise Architecture]. Accessed January 10, 2013</ref>

== Overview ==

Line 9 ⟶ 11:

== History ==

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] {{Webarchive|url=https://web.archive.org/web/20090422214155/http://www.iriboffice.ir/LinkClick.aspx?fileticket=up56ppcNQ4M%3D&tabid=246&mid=634 |date=2009-04-22 }}''</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>

== EA framework topics ==

Line 20 ⟶ 22:

The FDIC EA framework from 2005 included five components.

* ''[[Business Architecture]]'' : The Business Architecture described the activities and processes performed by the Corporationcorporation to achieve its mission and to realize its vision and goals. Developing the Business Architecture was the first step in creating an Enterprise Architecture (EA) that linked the Corporationcorporation's business needs to its Information Technology (IT) environment. Maximizing IT support for these requirements was intended to optimize Corporate performance.<ref name="FDICOIG05"/>

* ''[[Data Architecture]]'' : The Data Architecture described the activities required to obtain and maintain data that support the information needed by the Corporation’scorporation's major business areas. Data and information are different. Data is the foundation of information. Data is the raw material that is processed and refined to generate information. Information consists of a collection of related data that has been processed into a form that is meaningful to the recipient.<ref name="FDICOIG05"/>

* ''[[Applications Architecture]]'' : The Applications Architecture described the major types of applications that manage data to produce the information needed to support the activities of the Corporationcorporation. The Applications Architecture provided a framework that enabled the migration from the applications catalog and software development environment in use at the time to the target integrated applications, development and engineering environments. The target architecture promoted the use of commercial and government off-the-shelf products, consolidating applications, where applicable, and the use of emerging technologies where appropriate.<ref name="FDICOIG05"/>

* ''[[Technical Infrastructure Architecture]]'' : The IT infrastructure provided access to application systems and office automation tools used in performance of the business processes. The Corporation placed high priority on maintaining a consistent, available, and reliable technical infrastructure. The Technical Architecture described the underlying technology for the Corporationcorporation's business, data, and application processing. It included the technologies used for communications, data storage, application processing, and computing platforms.<ref name="FDICOIG05"/>

* ''[[Security Architecture]]'' : The Security Architecture established a framework for integrating safeguards into all layers of the FDIC's Enterprise Architecture. The security architecture used a risk management and information assurance strategy that provides access control, confidentiality, integrity, and non-repudiation for the Corporationcorporation's information and systems.<ref name="FDICOIG05"/>

=== Self-Funding Model for Reinvestment in IT===

Line 30 ⟶ 32:

The banking business model of 2008 had become more complex, giving rise to financial instruments such as [[collateralized debt obligation]]s (CDOs) and [[structured investment vehicle]]s (SIVs) to manage risk. These instruments created greater dependencies between the domestic and international financial markets. Financial institutions of that time should have, therefore, struck a balance between regulatory, legislative and banker concerns while appropriately managing risk.<ref name="FDIC08"/>

Notionally, as cost savings are realized from a simplified IT environment and more efficient processes, the savings can be reinvested for IT improvements or accrue to the Corporationcorporation. This self-funding model is shown on the right.<ref name="FDIC08"/>

=== 2008 - 2013 technology roadmap ===

The technology roadmap outlined the major initiatives for standardizing the IT environment and increasing IT’sIT's efficiency and effectiveness over five years. The initiatives were determined by various sources including business-side IT roadmaps, executive management planning meetings, client planning sessions, and client year-end reviews. The three major initiatives identified were enterprise architecture, security and privacy programs, and fiscal discipline.<ref name="FDIC08"/>

[[Image:Five-Year Technology Roadmap.jpg|thumb|360px|Five-Year Technology Roadmap, 2008.]]

The enterprise architecture initiative focused on simplifying the environment to ensure stable and economical performance for mission-critical applications. Simplifying the environment to decrease costs included activities, such as decreasing the number of application systems and migrating applications off the mainframe. Efficiencies were also hoped to be gained by expanding capabilities for manipulating large data sets and storing traditional paper-based files electronically. The SOA service center was intended to manage code (or services) for all development teams to discover and use, which was expected to save time and costs in application development, testing and deployment.<ref name="FDIC08"/>