Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enterprise Architecture: a focus on Communication and ...


Published on

Published in: Business, Technology
  • Be the first to comment

Enterprise Architecture: a focus on Communication and ...

  1. 1. Enterprise Architecture: a focus on Communication and Stakeholder Engagement Gail Verley: Assistant Director Enterprise Architecture, FDIC
  2. 2. Goals/Scope of Presentation <ul><li>How to obtain high level stakeholder involvement in EA governing processes and address major challenges for building stakeholder engagement </li></ul><ul><li>Identify vehicles to communicate with EA stakeholders while ensuring the architecture accommodates the style and priorities of the stakeholder community </li></ul><ul><li>Provide examples of how stakeholder involvement can lead to consolidation and better management of IT investments </li></ul>
  3. 3. FDIC Organizational Profile <ul><li>An independent agency of the federal government that was created in 1933 in response to the thousands of bank failures that occurred in the 1920s and early 1930s. </li></ul><ul><li>Examines and supervises about 5,300 banks and savings banks. </li></ul><ul><li>The FDIC is managed by a five-person Board of Directors, appointed by the President and confirmed by the Senate, with no more than three from the same political party </li></ul><ul><li>2006 proposed corporate operating budget- $1,050,075,522 </li></ul><ul><li>2006 IT Budget-$170,336,799 </li></ul><ul><li>Currently employs 4,466 people throughout the US (267 IT employees) </li></ul><ul><li>Washington, D.C. Headquarters (209 IT employees) </li></ul><ul><li>6 Regional Offices (58 IT employees) </li></ul>
  4. 4. Architecting the FDIC: A study in information integration and business alignment
  5. 5. Enterprise Architecture Run-down <ul><li>Architectural Framework </li></ul><ul><ul><li>blueprint of beginning to end progression </li></ul></ul><ul><ul><li>integrates agreed upon goals to contrive a target architecture </li></ul></ul><ul><ul><li>a continual process </li></ul></ul>
  6. 6. Architecture Process Business needs and requirements Eliminate Worthless Systems People Perspective Data Perspective Application Perspective Technical Perspective MAPPING STRATEGY TRANSITIONAL PHASE TARGET ARCHITECTURE
  7. 7. FDIC’s Architecture Framework
  8. 8. Implement solution and conduct management tasks Conduct Business Process Reengineering Determine the scope and set strategy Analyze the business Analyze the information technology Construct a business case to support business needs Conduct Business Process Reengineering Conduct data Standardization Execute O&M strategy for minor recommendations Integrate major recommendations into investment requests Define detailed solution architecture Maintain the Blueprint and the architecture Architectural Blueprint
  9. 9. Enterprise Architecture Repository (EA-Rep) <ul><li>2005 Accomplishments </li></ul><ul><li>January – Troux Contract Award </li></ul><ul><ul><li>Acquired Metis COTS product and implementation services </li></ul></ul><ul><li>April – Pilot Project </li></ul><ul><ul><li>Completed pilot project </li></ul></ul><ul><ul><li>Iterative deployment plan developed </li></ul></ul><ul><ul><li>Assembled requirements and extended model for v1.0 </li></ul></ul><ul><li>September – Production Release 1.0 </li></ul><ul><ul><li>Application, Project , and Organization Domains </li></ul></ul><ul><ul><li>Retired CDR reporting tools </li></ul></ul><ul><ul><li>Assembled requirements and extended model for v2.0 </li></ul></ul><ul><li>December – Production Release 2.0 </li></ul><ul><ul><li>CDR retired/replaced </li></ul></ul><ul><ul><li>Business domain, security layer added to applications domain </li></ul></ul><ul><ul><li>Custom UI for Application Managers </li></ul></ul><ul><li>2006 Scheduled Activities </li></ul><ul><li>June – Production Enhancement 2.6 </li></ul><ul><ul><li>Enhance/modify security layer </li></ul></ul><ul><ul><li>Augment search capabilities for applications, applications systems, and projects </li></ul></ul><ul><ul><li>Update associated reporting </li></ul></ul><ul><li>October – Production Release 3.0 </li></ul><ul><ul><li>Upgrade to Metis 5.5, Client Tools 5.2 </li></ul></ul><ul><ul><li>Upgrade production hardware </li></ul></ul><ul><ul><li>Extend model </li></ul></ul><ul><ul><li>Implement Infrastructure and Data Domains </li></ul></ul><ul><ul><li>Implement refinements to existing domains </li></ul></ul><ul><ul><li>Expand Reporting </li></ul></ul><ul><ul><li>Integrate FDIC-specific help facility </li></ul></ul><ul><li>December – Troux Contract Ends </li></ul>
  10. 10. Engaging the Stakeholder
  11. 11. Who are Stakeholders? <ul><li>Defined: an individual with a vested interest in the results of IT solutions and implementation. </li></ul><ul><li>Include: business owners, data owners, developers and technical infrastructure operational staff </li></ul>
  12. 12. 10 Ways to Maximize Stakeholder Engagement <ul><li>1. Executive Management Buy-in </li></ul><ul><li>2. Connect Business Goals with IT </li></ul><ul><li>3. Link pay and performance with IT projects </li></ul><ul><li>4. Communicate Objectives Frequently </li></ul><ul><li>5. Clearly Defined Principles </li></ul><ul><li>6. Demonstrate Benefits </li></ul><ul><li>7. Govern from Different Perspectives </li></ul><ul><li>8. Active Leadership </li></ul><ul><li>9. IT gets a seat at the Business table </li></ul><ul><li>10. Recognition and Success shared by all </li></ul>
  13. 13. Why is stakeholder engagement is important? <ul><li>Stakeholder engagement is critical to applying enterprise architecture EA principles and methodologies in order to achieve value from information technology IT investments </li></ul><ul><li>Multi-layered perspectives and comprehensive strategies result from high levels of stakeholder engagement in EA, from a project’s inception to completion </li></ul><ul><li>Stakeholder experience and subsequent foresight of obstacles in respective program areas can prove invaluable to the smooth process toward target architecture. </li></ul>
  14. 14. Application Rationalization Effort Example <ul><li>PROBLEM </li></ul><ul><li>Many organizations accumulate large and technically diverse portfolio of systems </li></ul><ul><li>Unmanaged, this portfolio is too expensive and unresponsive to change. </li></ul><ul><li>The result, restricting the organization from taking on IT initiatives that are strategically important to its mission </li></ul><ul><li>FDIC SOLUTION </li></ul><ul><li>Engaged both the IT Department and Business Stakeholders in a systematic and joint effort to make targeted reductions in the inventory of applications </li></ul><ul><li>This effort served to raise the awareness of staff and management throughout the FDIC of the life-cycle costs of applications and the increasing need for application integration and consolidation </li></ul><ul><li>This allowed the FDIC implement several new enterprise-wide integrated applications that not only met the need to improve business operations, but at the same time, replaced older, stove-piped legacy applications. </li></ul>
  15. 15. Corporate Data Sharing <ul><li>CDS Data Families </li></ul><ul><li>FDIC Conceptual Data Model describes the relationships between FDIC's data across the data families and the entire enterprise </li></ul><ul><li>The Collaborative Working Groups (CWGs) were established to verify that the data has been defined and categorized correctly in their data family. </li></ul>
  16. 16. Bank Call Reports Use XBRL <ul><li>FDIC is one of the biggest proponents of XBRL </li></ul><ul><li>8,200 U.S. banks use XBRL to submit balance sheets and income statement reports. </li></ul><ul><li>XBRL has proven its value: All XBRL-tagged data received from banks was 95% accurate, compared with 70% accuracy before implementation </li></ul><ul><li>An analyst who could handle 450 to 500 banks before implementation can now handle 550 to 600 of them. </li></ul>
  17. 17. Maximizing the Impact of the Stakeholder <ul><li>Ultimately stakeholder compliance with EA must be governed through a comprehensive system that divides responsibilities to take full advantage of individual strengths as well as increase the efficiency of the corporate structure </li></ul><ul><li>There exist a few mechanisms to reach this end. Two of the most important and effective are Established Governance Systems and Business Metrics </li></ul>
  18. 18. Governance Structures
  19. 19. Governance Mapping <ul><li>A key step in the EA process is to establish a system of governance. One in which rules and order of operation are hashed out between relevant actors to meet the target architecture. </li></ul><ul><li>Every Corporation is different, but the basic requirements for a healthy Governance body are similar to all </li></ul>
  20. 20. Model Governance Structure Requirements Simple Transparent Suitable Governance Framework
  21. 21. The Capital Investment Review Committee (CIRC) <ul><li>Comprised of Senior Level Division Directors </li></ul><ul><li>Evaluate the impact of IT investment decisions on the Corporations capital investment portfolio </li></ul><ul><li>Reviews proposed major investments and makes the final funding recommendations to the FDIC’s Board of Directors </li></ul><ul><li>Indicates Success in integration of EA and the capital investment management process. </li></ul>
  22. 22. FDIC Governance Bodies <ul><li>Capital Investment Review Committee (CIRC) </li></ul><ul><li>CIO Council </li></ul><ul><li>Enterprise Architecture Board (EAB) </li></ul><ul><li>Collaborative Working Groups (CWG) </li></ul><ul><li>Internet Coordinators Group </li></ul><ul><li>Information Security Management Committee </li></ul><ul><li>Technical Review Group </li></ul><ul><li>Enterprise Architecture Advisory Forum </li></ul>
  23. 23. Metrics
  24. 24. Utilize Metrics <ul><li>Metrics guide architecture </li></ul><ul><li>IT desirables are reflected in the IT metrics </li></ul><ul><li>Measure accountabilities </li></ul>
  25. 25. Metrics’ Importance <ul><li>Identify specific EA and Business related metrics early to guide decisions </li></ul><ul><li>Enable the tracking and recording of data required to report results and evaluate the impact of EA related strategies </li></ul>
  26. 26. Linking Business and IT via Metrics <ul><li>You need at least three kinds of metrics to begin establishing a linkage from the business needs and the implementation of them as guided by EA. Chris Curran March 21, 2005, Enterprise Architect </li></ul><ul><li>1. Business Alignment </li></ul><ul><li>2. EA Compliance </li></ul><ul><li>3. EA Governance </li></ul>
  27. 27. Metric Types Quarterly Investment Project Reviews Portfolio Review by CIO Council Measures the degree of participation and effectives of EA governance processes and practices EA Governance New technology to meet target architecture Amount of time to implement Applications retired % reuse of standard services, patterns Measures the number of systems and projects in compliance with EA standards EA Compliance Post implementation review that asks two questions. 1. Was the Benefit achieved 2. Has it met the Target Architecture Measures the number, completeness, and quality of business and IT capabilities delivered against those defined in the EA blueprint(s) Business Alignment Examples Definition EA Metric
  28. 28. Lessons Learned by FDIC EA <ul><li>Work with and enable the business first- critical first step of any EA organization is to identify the problem/business need first and work cooperatively with Business Professionals to show the value of IT and EA setup to the Corporation. </li></ul><ul><li>Optimize EA to enable organizational transformation- continuing on the theme of a complete and stated goal with a strategy to achieve that goal, EA allows, via open communication and cooperation between IT and EA, for a comprehensive evaluation of all business processes and IT involvement to maximize EA goals while serving IT purposes and business needs. </li></ul>
  29. 29. Any Questions?...