Geographic Information Technology Conceptual Architecture

1
Geographic Information Technology Conceptual
Architecture

• January 12, 2006
• Information Services Board Meeting

2
GIT Conceptual Architecture

• ISB/Committee on Geographic Information
  Technology (GIT) is seeking Board approval of the
  proposed GIT Conceptual Architecture

3
GIT Enterprise Architecture Initiative

• What is it?
• A chartered initiative of the ISB Enterprise
  Architecture Program
• What will it do?
• 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
• Who are the executive sponsors?
• ISB Enterprise Architecture Committee
• ISB Geographic Information Technology Committee

4
GIT Conceptual Architecture

• What is it?
• Complete set of deliverables for Phase 1 of GIT
  EA development
• What does it do?
• Creates a decision making framework for state
  agencies to identify the GIT assets that should
  be managed as enterprise assets
• Who has endorsed the Conceptual Architecture?
• ISB Geographic Information Technology Committee
  (December 6, 2005)
• ISB Enterprise Architecture Committee (December
  21, 2005)

5
GIT EA Executive Sponsors

• ISB/Geographic Information Technology Committee
  (GIT)
• Members DNR, DOT, DFW, ECY, DOH, MIL, DIS, USGS
  and WAGIC (CIOs or executive )
• ISB/Enterprise Architecture Committee (EAC)
• Members LNI, ES, DOT, DOR, UW, DIS, DSHS,
  WSP,DOT, DOL. LSC, DOR (CIOs)

6
Value to State Agency CIOs

• Creates mechanism to address GIT Strategic Plan
  Objectives (ISB approved Jan 05)
• Sets stage for agreement on enterprise solutions
  that cut across shared information needs
• Identifies elements of shareable infrastructure
  to lower costs and promotes joint investments
• Increases capacity to support mission-critical
  decisions both within agencies and across the
  enterprise

7
GIT EA Vetting Process

• Documenter Team Developed Draft Documents (GIT
  Managers Technical Leads)
• DOT, DFW, DOR, IAC, DIS,
• DNR, ECY, DOH, MIL
• IT and GIT Community Comment Review
• 3 Releases of Conceptual Architecture Documents
• Widely distributed via CAB, WAGIC and other
  listservs

8
EA Program Iterative Development Process

• Phase I Develop Conceptual Architecture
• Lays out decision making principles and framework
  to further define architecture for implementation
  
• Phase II Develop Logical Physical Detail
• Identifies Policy areas and further defines
  relationship to other EA domains
• Identifies Standards and physical implementation
  layers and details

9
Phase I - Deliverables

• Collaborative Process that Documents Conceptual
  Architecture, - (Descriptions, Rationale
  Implications)
• GIT Trends
• Decision Making Principles
• Information Architecture
• Technology Architecture
• Business Architecture
• Technology Gaps
• Solutions Architecture

10
(No Transcript)
11
Key ElementsConceptual Architecture

• Proposed Conceptual Architecture
• Maps-out the general direction of GIT EA
  creates decision making framework (does not
  create Policy or Standards yet)
• Decision Making Principles
• 6 GIT EA Principles framework for making the
  tough decisions
• Solutions Architecture Components
• Identifies how architecture components are used
  to develop and implement enterprise GIT solutions

12
Questions or Comments?

• GIT Conceptual Architecture creating a decision
  making framework for state agencies to identify
  the GIT assets that will be managed as enterprise
  assets
• ISB Geographic Information Technology Committee
• Jeff Holm
• DIS/MOSTD
• jeffh_at_dis.wa.gov
• 360.902.3447

13
Whats Next - Phase II Logical Physical
Iterations

• Suggested Approach
• Focus on defining logical and physical elements
  of Solution Architecture Components
• Sets stage for implementation
• Remaining GIT EA components are further defined
  as a result of focus on implementing Solution Sets

14
Information Technology Gaps

• The 5 Business Drivers (Section 6)
• Improve Data Access Integration
• GIT Agencies Partner as an Enterprise
• Improve Maintain Data Currency
• Develop Operation Support for Enterprise GIT
• Leverage Newer Technology - resolve barriers

15
Solution Architecture

• The 3 Solution Components (Section 6)
• GIT Portal and Clearinghouse
• Logically centralized point of discovery and
  access
• GIT Shared Infrastructure
• Optional use common infrastructure
• GIT EA Support Function
• Sustains operation of enterprise GIT

16
GIT Decision Making Principles

• Augment EA Program Principles
• GIT Principles
• Spatial Data as a Valued Investment Asset
• Data Stewardship
• Information Access
• Enterprise TCO Based Decisions
• Mainstream Technologies Industry Standards
• GIT EA Data as Primary Base Data Source