Published on

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

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Good afternoon Chairman Fitzsimmonds and members of the Board My name is Jeff Holm and I am staff to the Board, To my xxxx is Scott Came ISB Enterprise Architecture Program Director I am here today as a representative of the ISB/Geographic Information Technology Committee . The Committee is seeking BOARD Approval of the GIT Conceptual Architecture. I will provide a brief overview of this Enterprise Architecture initiative and touch on why the executive sponsors have unanimously endorsed the proposed Conceptual Architecture. Let me start by……….
  • Let me start by generally describing the GIT Enterprise Architecture Initiative……………………
  • Critical Success Factors for PII: Drive to operational implementation SA Successfully seek enterprise funding through decision packages for selected SA elements Focus on low-hanging fruit Data theme stewardship Data themes: Orthoimagery, Hydro, Transportation Others ?
  • PPT

    1. 1. Geographic Information Technology Conceptual Architecture January 12, 2006 Information Services Board Meeting
    2. 2. GIT Conceptual Architecture <ul><li>ISB/Committee on Geographic Information Technology (GIT) is seeking Board approval of the proposed GIT Conceptual Architecture </li></ul>
    3. 3. GIT Enterprise Architecture Initiative <ul><li>What is it? </li></ul><ul><ul><li>A chartered initiative of the ISB Enterprise Architecture Program </li></ul></ul><ul><li>What will it do? </li></ul><ul><ul><li>GIT EA will establish a roadmap for the Washington state government enterprise to follow as it works to achieve strategic business results using Geographic Information Technology </li></ul></ul><ul><li>Who are the executive sponsors? </li></ul><ul><ul><li>ISB Enterprise Architecture Committee </li></ul></ul><ul><ul><li>ISB Geographic Information Technology Committee </li></ul></ul>
    4. 4. GIT Conceptual Architecture <ul><li>What is it? </li></ul><ul><ul><li>Complete set of deliverables for Phase 1 of GIT EA development </li></ul></ul><ul><li>What does it do? </li></ul><ul><ul><li>Creates a decision making framework for state agencies to identify the GIT assets that should be managed as enterprise assets </li></ul></ul><ul><li>Who has endorsed the Conceptual Architecture? </li></ul><ul><ul><li>ISB Geographic Information Technology Committee (December 6, 2005) </li></ul></ul><ul><ul><li>ISB Enterprise Architecture Committee (December 21, 2005) </li></ul></ul>
    5. 5. GIT EA Executive Sponsors <ul><li>ISB/Geographic Information Technology Committee (GIT) </li></ul><ul><ul><li>Members: DNR, DOT, DFW, ECY, DOH, MIL, DIS, USGS and WAGIC (CIO’s or executive ) </li></ul></ul><ul><li>ISB/Enterprise Architecture Committee (EAC) </li></ul><ul><ul><li>Members: LNI, ES, DOT, DOR, UW, DIS, DSHS, WSP,DOT, DOL. LSC, DOR (CIO’s) </li></ul></ul>
    6. 6. Value to State Agency CIO’s <ul><li>Creates mechanism to address GIT Strategic Plan Objectives (ISB approved Jan ’05) </li></ul><ul><ul><li>Sets stage for agreement on enterprise solutions that cut across shared information needs </li></ul></ul><ul><ul><li>Identifies elements of shareable infrastructure to lower costs and promotes joint investments </li></ul></ul><ul><ul><li>Increases capacity to support mission-critical decisions both within agencies and across the enterprise </li></ul></ul>
    7. 7. GIT EA Vetting Process <ul><li>‘ Documenter Team’ Developed Draft Documents (GIT Managers & Technical Leads) </li></ul><ul><ul><li>DOT, DFW, DOR, IAC, DIS, </li></ul></ul><ul><ul><li>DNR, ECY, DOH, MIL </li></ul></ul><ul><li>IT and GIT Community Comment & Review </li></ul><ul><ul><li>3 Releases of Conceptual Architecture Documents </li></ul></ul><ul><ul><li>Widely distributed via CAB, WAGIC and other listservs </li></ul></ul>
    8. 8. EA Program Iterative Development Process <ul><li>Phase I – Develop Conceptual Architecture </li></ul><ul><ul><li>Lays out decision making principles and framework to further define architecture for implementation </li></ul></ul><ul><li>Phase II – Develop Logical & Physical Detail </li></ul><ul><ul><li>Identifies Policy areas and further defines relationship to other EA domains </li></ul></ul><ul><ul><li>Identifies Standards and physical implementation layers and details </li></ul></ul>
    9. 9. Phase I - Deliverables <ul><li>Collaborative Process that Documents Conceptual Architecture , - ( Descriptions, Rationale & Implications) : </li></ul><ul><ul><li>GIT Trends </li></ul></ul><ul><ul><li>Decision Making Principles </li></ul></ul><ul><ul><li>Information Architecture </li></ul></ul><ul><ul><li>Technology Architecture </li></ul></ul><ul><ul><li>Business Architecture </li></ul></ul><ul><ul><li>Technology Gaps </li></ul></ul><ul><ul><li>Solutions Architecture </li></ul></ul>
    10. 11. Key Elements Conceptual Architecture <ul><li>Proposed Conceptual Architecture </li></ul><ul><ul><li>‘ Maps-out’ the general direction of GIT EA – creates decision making framework ( does not create Policy or Standards – yet) </li></ul></ul><ul><li>Decision Making Principles </li></ul><ul><ul><li>6 GIT EA Principles – framework for making the tough decisions </li></ul></ul><ul><li>Solutions Architecture Components </li></ul><ul><ul><li>Identifies how architecture components are used to develop and implement enterprise GIT solutions </li></ul></ul>
    11. 12. Questions or Comments? <ul><li>GIT Conceptual Architecture – creating a decision making framework for state agencies to identify the GIT assets that will be managed as enterprise assets </li></ul><ul><li>ISB Geographic Information Technology Committee </li></ul><ul><li>Jeff Holm </li></ul><ul><li>DIS/MOSTD </li></ul><ul><li>[email_address] </li></ul><ul><li>360.902.3447 </li></ul>
    12. 13. What’s Next - Phase II Logical & Physical Iterations <ul><li>Suggested Approach: </li></ul><ul><li>Focus on defining logical and physical elements of Solution Architecture Components </li></ul><ul><li>Sets stage for implementation </li></ul><ul><li>Remaining GIT EA components are further defined as a result of focus on implementing Solution Sets </li></ul>
    13. 14. Information & Technology Gaps <ul><li>The 5 Business Drivers (Section 6) </li></ul><ul><li>Improve Data Access & Integration </li></ul><ul><li>GIT Agencies Partner as an Enterprise </li></ul><ul><li>Improve & Maintain Data Currency </li></ul><ul><li>Develop Operation Support for Enterprise GIT </li></ul><ul><li>Leverage Newer Technology - resolve barriers </li></ul>
    14. 15. Solution Architecture <ul><li>The 3 Solution Components (Section 6) </li></ul><ul><li>GIT Portal and Clearinghouse </li></ul><ul><ul><li>Logically centralized point of discovery and access </li></ul></ul><ul><li>GIT Shared Infrastructure </li></ul><ul><ul><li>Optional use common infrastructure </li></ul></ul><ul><li>GIT EA Support Function </li></ul><ul><ul><li>Sustains operation of enterprise GIT </li></ul></ul>
    15. 16. GIT Decision Making Principles <ul><li>Augment EA Program Principles </li></ul><ul><li>GIT Principles: </li></ul><ul><ul><li>Spatial Data as a Valued Investment & Asset </li></ul></ul><ul><ul><li>Data Stewardship </li></ul></ul><ul><ul><li>Information Access </li></ul></ul><ul><ul><li>Enterprise TCO Based Decisions </li></ul></ul><ul><ul><li>Mainstream Technologies & Industry Standards </li></ul></ul><ul><ul><li>GIT EA Data as Primary Base Data Source </li></ul></ul>