FDIC Enterprise Architecture Framework: Difference between revisions

Revision as of 20:36, 11 January 2011

Revision as of 02:03, 12 January 2011

Line 1:

[[Image:FDIC’s Enterprise Architecture Framework.jpg|thumb|320px|FDIC’s Enterprise Architecture Framework.<ref>OIG (2005). [http://www.fdicoig.gov/reports05/05-018-508.shtml Implementation of E-Government Principles]. May 2005</ref>]]

'''FDIC Enterprise Architecture Framework''' inaccurately attempts to depictis the [[Enterprise Architecture framework]] of the [[Federal Deposit Insurance Corporation]] (FDIC).

== Overview ==

The FDIC's framework for implementing its [[Enterprise Architecture]] is 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 has been tailored to emphasize [[security]]. The 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] AUDIT REPORT, Report No. 05-018, May 2005</ref>

The information about the FDIC's enterprise architecture is out-of-date and inaccurate.

The FDIC EA framework includes five components. The first component, the Business Architecture, focuses on FDIC's business needs. The next three components, the [[Data Architecture]], Applications Architecture, and Technical Infrastructure Architectures, focus on the technological capabilities that support the business and information needs. The final component, the [[Security Architecture]], focuses on specific aspects of interest to the Corporation that span the enterprise and must be integral parts of all other architectures.<ref name="FDICOIG05"/>

Please visit www.fdic.gov for more current information.

== History ==

Historically, Federal agencies have managed IT investments autonomously. Until the new millennium, there has been little incentive for agencies to partner to effectively reuse IT investments, share IT knowledge, and explore joint solutions. A collective, government-wide effort, supported by the Federal CIO Council, utilizing the [[Federal Enterprise Architecture]] (FEA), has been 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. The FEA is a business-based framework that provides the Office of Management and Budget (OMB) and Federal agencies a way to monitor, analyze, and control Federal IT investments.<ref>FDIC (2003). ''[http://www.iriboffice.ir/LinkClick.aspx?fileticket=up56ppcNQ4M%3D&tabid=246&mid=634 Information Technology Strategic Plan 2004–2007]'' </ref> The [[FDIC]] first realized the value of EA 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]" Gartner, Inc.</ref>

The information in this section is more appropriately about the Federal government's former policy on enterprise architecture and has little or nothing to do with the FDIC.

In 2004 the Federal Deposit Insurance Corporation (FDIC), recently received a 2004 Enterprise Architecture Excellence Award from the Zachman Institute for Framework Advancement (ZIFA) for its initiative to manage corporate data collaboratively. [[John Zachman]], an expert on enterprise architecture, founded ZIFA, a network of information professionals supporting enterprise architecture's role in helping organizations operate from a corporate perspective.<ref>[http://www.fdic.gov/news/news/press/2004/pr13104.html FDIC Receives Technology Award]</ref>

Historically, Federal agencies have managed IT investments autonomously. Until the new millennium, there has been little incentive for agencies to partner to effectively reuse IT investments, share IT knowledge, and explore joint solutions. A collective, government-wide effort, supported by the Federal CIO Council, utilizing the [[Federal Enterprise Architecture]] (FEA), has been 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. The FEA is a business-based framework that provides the Office of Management and Budget (OMB) and Federal agencies a way to monitor, analyze, and control Federal IT investments.

In 2004 the Federal Deposit Insurance Corporation (FDIC), received a 2004 Enterprise Architecture Excellence Award from the Zachman Institute for Framework Advancement (ZIFA) for its initiative to manage corporate data collaboratively. [[John Zachman]], an expert on enterprise architecture, founded ZIFA, a network of information professionals supporting enterprise architecture's role in helping organizations operate from a corporate perspective.<ref>[http://www.fdic.gov/news/news/press/2004/pr13104.html FDIC Receives Technology Award]</ref>

== EA framework topics ==

=== Example of anFDIC EA framework ===

AnThe FDIC EA framework can include the following includes five components.

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

* ''[[Data Architecture]]'' : The Data Architecture describes the activities required to obtain and maintain data that supports the information needed by the Corporation’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 describes the major types of applications that manage data to produce the information needed to support the activities of the Corporation. The Applications Architecture provides a framework that enables the migration from the current applications catalog and software development environment to the target integrated applications, development and engineering environments. The target architecture promotes 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 provides access to application systems and office automation tools used in performance of the business processes. The Corporation places high priority on maintaining a consistent, available, and reliable technical infrastructure. The Technical Architecture describes the underlying technology for the Corporation's business, data, and application processing. It includes the technologies used for communications, data storage, application processing, and computing platforms.<ref name="FDICOIG05"/>

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

=== Future IT Development ===

[[Image:Self-Funding Model for Future IT Development.jpg|thumb|320px|Self-Funding Model for Future IT Development.<ref name="FDIC08"> CIO Council (2008) [http://www.fdic.gov/about/strategic/it_plan/IT_Strategic_Plan_2.pdf Information Technology Strategic Plan 2008–2013], January 23, 2008.</ref>]]

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

As cost savings are realized from a simplified IT environment and more efficient processes, the savings will be reinvested for IT improvements or accrue to the entity. This self-funding model is shown on the right.

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

=== Example of a Technology Roadmap ===

The technology roadmap outlines the major initiatives for standardizing the IT environment and increasing IT’s efficiency and effectiveness over the next 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 are enterprise architecture, security and privacy programs, and fiscal discipline.

=== Example of aFive-Year Technology Roadmap ===

An enterprise architecture initiative can focus on simplifying the environment to ensure stable and economical performance for mission-critical applications. Simplifying the environment to decrease costs will include activities, such as decreasing the number of application systems and migrating applications off the mainframe. Efficiencies can also be gained by expanding capabilities for manipulating large data sets and storing traditional paper-based files electronically. A SOA service center will manage code (or services) for all development teams to discover and use, which can save time and costs in application development, testing and deployment.

The technology roadmap outlines the major initiatives for standardizing the IT environment and increasing IT’s efficiency and effectiveness over the next 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 are enterprise architecture, security and privacy programs, and fiscal discipline.<ref name="FDIC08"/>

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

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

The organizationCorporation canwill continue to enhance IT security and privacy programs to address new and evolving risks by improving controls over sensitive data. In some cases, technology, such as scanning outgoing e-mail for sensitive information and encrypting removable storage devices, can mitigate potential risks. The other cornerstone of mitigating risk is educating employees of emerging security and privacy issues.<ref name="FDIC08"/>

Lastly, in order to continue sound fiscal discipline and responsibility, anthe organizationCorporation canwill establish IT baselines and metrics, study steady-state costs, manage service level agreements, and more judiciously choose new development projects. These three areas – enterprise architecture, security and privacy programs, and fiscal discipline – are shown below with the estimated time frames.<ref name="FDIC08"/>

== See also ==