FDIC Enterprise Architecture Framework: Difference between revisions

Revision as of 23:07, 18 January 2022

Revision as of 08:29, 28 September 2022

Line 1:

{{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>]]

'''FDIC Enterprise Architecture Framework''' was the [[enterprise architecture framework]] of the United States [[Federal Deposit Insurance Corporation]] (FDIC). A lot of the current article is about the enterprise architecture framework developed around 2005, and currently anno 2011 out-of-date.{{citation needed|date=January 2013}}

Line 20:

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:

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"/>