Misplaced Pages

FDIC Enterprise Architecture Framework: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 02:19, 12 January 2011 editMdd (talk | contribs)Autopatrolled, Extended confirmed users54,571 edits Some more← Previous edit Latest revision as of 17:46, 27 March 2024 edit undoInternetArchiveBot (talk | contribs)Bots, Pending changes reviewers5,382,061 edits Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 
(35 intermediate revisions by 20 users not shown)
Line 1: Line 1:
{{Short description|none}}
⚫ . May 2005</ref>]]
{{Update|inaccurate=yes|date=January 2013}}
⚫ '''FDIC Enterprise Architecture Framework''' is the ] of the ] (FDIC), developed around 2005, and currently anno 2011 out-of-date.
⚫ {{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 ] of the United States ] (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}}


== Overview == == Overview ==
The FDIC's framework for implementing its ] is based on Federal and industry best practices, including the Chief Information Officer (CIO) Council's ] (FEAF) and the ] for Enterprise Architecture. FDIC's framework has been tailored to emphasize ]. The FDIC EA framework complies with the FEAF and highlights the importance of security to all other components of the architecture.<ref name="FDICOIG05"> AUDIT REPORT, Report No. 05-018, May 2005</ref> The FDIC's framework for implementing its ] was based on Federal and industry best practices, including the Chief Information Officer (CIO) Council's ] (FEAF) and the ] for Enterprise Architecture. FDIC's framework was tailored to emphasize ]. 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"> {{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 includes five components. The first component, the Business Architecture, focuses on FDIC's business needs. The next three components, the ], Applications Architecture, and Technical Infrastructure Architectures, focus on the technological capabilities that support the business and information needs. The final component, the ], 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"/> The FDIC EA framework included five components. The first component, the Business Architecture, focused on FDIC's business needs. The next three components, the ], Applications Architecture, and Technical Infrastructure Architectures, focused on the technological capabilities that support the business and information needs. The final component, the ], 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"/>


== History == == 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 ] (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). '''' </ref> The ] 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) "" Gartner, Inc.</ref> 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 ] (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). '' {{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) " {{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 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. ], 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></ref>

⚫ In 2004 the FDIC received a 2004 Enterprise Architecture Excellence Award from the ] (ZIFA) for its initiative to manage corporate data collaboratively.<ref></ref>


== EA framework topics == == EA framework topics ==

=== FDIC EA framework === === Historical FDIC EA framework ===
The FDIC EA framework from 2005 included five components. The FDIC EA framework from 2005 included five components.


* '']'' : 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"/> * '']'' : The Business Architecture described the activities and processes performed by the corporation 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 corporation's business needs to its Information Technology (IT) environment. Maximizing IT support for these requirements was intended to optimize Corporate performance.<ref name="FDICOIG05"/>
⚫ * '']'' : The Data Architecture described the activities required to obtain and maintain data that support 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"/>
⚫ * '']'' : The Applications Architecture described the major types of applications that manage data to produce the information needed to support the activities of the corporation. 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"/>
⚫ * '']'' : 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 corporation's business, data, and application processing. It included the technologies used for communications, data storage, application processing, and computing platforms.<ref name="FDICOIG05"/>
⚫ * '']'' : 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 corporation's information and systems.<ref name="FDICOIG05"/>


=== Self-Funding Model for Reinvestment in IT===
⚫ * '']'' : 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"/>
⚫ , January 23, 2008. {{webarchive |url=https://web.archive.org/web/20110103174554/http://www.fdic.gov/about/strategic/it_plan/IT_Strategic_Plan_2.pdf |date=January 3, 2011 }}</ref>]]
⚫ The banking business model of 2008 had become more complex, giving rise to financial instruments such as ]s (CDOs) and ]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 corporation. This self-funding model is shown on the right.<ref name="FDIC08"/>
⚫ * '']'' : 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"/>


=== 2008 - 2013 technology roadmap ===
⚫ * '']'' : 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"/>
⚫ The technology roadmap outlined the major initiatives for standardizing the IT environment and increasing IT'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"/>

⚫ * '']'' : 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 ===
⚫ , January 23, 2008.</ref>]]
⚫ The banking business model has become more complex, giving rise to financial instruments such as collateralized debt obligations (CDOs) and ]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 Corporation. This self-funding model is shown on the right. <ref name="FDIC08"/>

=== Five-Year 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.<ref name="FDIC08"/>
] ]
The enterprise architecture initiative will 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 will also be gained by expanding capabilities for manipulating large data sets and storing traditional paper-based files electronically. The SOA service center will manage code (or services) for all development teams to discover and use, which will save time and costs in application development, testing and deployment.<ref name="FDIC08"/> 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"/>


The organization will 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"/> The organization planned to 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, could mitigate potential risks. The other cornerstone of mitigating risk was educating employees of emerging security and privacy issues.<ref name="FDIC08"/>


Lastly, in order to continue sound fiscal discipline and responsibility, the organization will 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"/> Lastly, in order to continue sound fiscal discipline and responsibility, the organization planned to 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 == == See also ==
Line 48: Line 49:


== Further reading == == Further reading ==
* Gartner (2005) ''''. Industrial research paper.
* Pallab Saha (2007). ''Handbook of Enterprise Systems Architecture in Practice‎''. Chapter IX gives a detailed case study of the FDIC. * Pallab Saha (2007). ''Handbook of Enterprise Systems Architecture in Practice''. Chapter IX gives a detailed case study of the FDIC.

== External links == == External links ==
{{Commonscat|FCIC Enterprise architecture}} {{Commons category|FCIC Enterprise architecture}}
* Homepage. * Homepage.


{{DEFAULTSORT:Fdic Enterprise Architecture Framework}} {{DEFAULTSORT:Fdic Enterprise Architecture Framework}}
] ]
] ]

Latest revision as of 17:46, 27 March 2024

This article's factual accuracy may be compromised due to out-of-date information. Please help update this article to reflect recent events or newly available information. (January 2013)
FDIC's Enterprise Architecture Framework from 2005.

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.

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.

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.

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.

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.

In 2004 the FDIC received a 2004 Enterprise Architecture Excellence Award from the Zachman Institute for Framework Advancement (ZIFA) for its initiative to manage corporate data collaboratively.

EA framework topics

Historical FDIC EA framework

The FDIC EA framework from 2005 included five components.

  • Business Architecture : The Business Architecture described the activities and processes performed by the corporation 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 corporation's business needs to its Information Technology (IT) environment. Maximizing IT support for these requirements was intended to optimize Corporate performance.
  • Data Architecture : The Data Architecture described the activities required to obtain and maintain data that support 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.
  • 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 corporation. 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.
  • 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 corporation's business, data, and application processing. It included the technologies used for communications, data storage, application processing, and computing platforms.
  • 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 corporation's information and systems.

Self-Funding Model for Reinvestment in IT

Self-Funding Model for Future IT Development, 2008.

The banking business model of 2008 had become more complex, giving rise to financial instruments such as collateralized debt obligations (CDOs) and structured investment vehicles (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.

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 corporation. This self-funding model is shown on the right.

2008 - 2013 technology roadmap

The technology roadmap outlined the major initiatives for standardizing the IT environment and increasing IT'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.

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.

The organization planned to 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, could mitigate potential risks. The other cornerstone of mitigating risk was educating employees of emerging security and privacy issues.

Lastly, in order to continue sound fiscal discipline and responsibility, the organization planned to 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.

See also

References

  1. OIG (2005). Implementation of E-Government Principles Archived 2009-01-14 at the Wayback Machine. May 2005
  2. ^ Implementation of E-Government Principles Archived 2009-01-14 at the Wayback Machine AUDIT REPORT, Report No. 05-018, May 2005
  3. FDIC (2003). Information Technology Strategic Plan 2004–2007 Archived 2009-04-22 at the Wayback Machine
  4. Gregg Kreizman, Cathleen E. Blanton (2005) "The FDIC Is Aligning IT to Business Through Enterprise Architecture Archived 2009-03-20 at the Wayback Machine" Gartner, Inc.
  5. FDIC Receives Technology Award
  6. ^ CIO Council (2008) Information Technology Strategic Plan 2008–2013, January 23, 2008. Archived January 3, 2011, at the Wayback Machine

Further reading

External links

Categories: