Missouri Adaptive Enterprise Architecture Information Domain Geographic Information Technology Discipline

1
Missouri Adaptive Enterprise Architecture
Information DomainGeographic Information
Technology Discipline

• MGISAC - NGEA MO GIT Briefing
• Tim Haithcoat
• Missouri Spatial Data Information Service
• HaithcoatT_at_missouri.edu
• Eliot Christian, USGS/FGDC

August 11, 2005
2
What is a Spatial Data Infrastructure?

• SDIs are composed of organizations or
  cross-cutting communities who adopt common
  standards for geospatial data
• There is a Global Spatial Data Infrastructure
  (GSDI) members represent National SDIs (about
  50 at present)
• GSDI Clearinghouse currently has 381 "nodes"
  (searchable metadata collections)

3
Objectives for Spatial Data Infrastructuressource
Open Geospatial Consortium (OGC)
Integrated View
Buildings Roads Images Targets Boundaries
...
Queries extract info from diverse sources
Cedar Lake
Whoville
CatalogView
Internet
Common interfaces enable interoperability
Web Mapping Server, Web Feature Server, Web
Coverage Server
Catalog Services
Gazetteer
Coordinate Transform
Geoparser
Clearinghouse
Geoparser
Geoparser
Vendor Data
Local Government
National Government
Other Collections
Other Services
Geocoder
4
Requirements of Law and Policy Federal Policy
(Circular A-16)

• OMB Circular A-16 (as revised August 19, 2002)
• "establishes a coordinated approach to
  electronically develop the National Spatial Data
  Infrastructure"

Purpose of the NSDITo encourage the
collection, processing, archiving, integration,
and sharing of geospatial data and information
using common standards and interoperable systems
and techniques
5
Requirements of Law and Policy Federal Policy
(Circular A-16)

• "provides direction for federal agencies that
  produce, maintain or use spatial data either
  directly or indirectly"
• directs such agencies, "both internally and
  through their activities involving partners,
  grants, and contracts" to
• (1) Prepare, maintain, publish, and implement a
  strategy for advancing geographic information
  and related spatial data activities appropriate
  to their mission, in support of the NSDI
  Strategy. ...
• (2) Collect, maintain, disseminate, and
  preserve spatial information such that the
  resulting data, information, or products can be
  readily shared with other federal agencies and
  non-federal users, and promote data integration
  between all sources. ...

6
Requirements of Law and Policy Federal Policy
(Circular A-16)

• (4) Use FGDC data standards, FGDC Content
  Standards for Digital Geospatial Metadata, and
  other appropriate standards, documenting spatial
  data with the relevant metadata, and making
  metadata available online through a registered
  NSDI-compatible Clearinghouse node. ...
• Before the obligation of funds, ensure that all
  expenditures for spatial data and related
  systems activities financed directly or
  indirectly, in whole or in part, by federal
  funds are compliant with the standards and
  provisions of the FGDC.
• All Information Technology systems which process
  spatial data should identify planned investments
  for spatial data and compliance with FGDC
  standards within the Exhibit 300 capital asset
  and business plan submission (see OMB Circular
  A-11, sec. 300).

7
Enterprise GISvs.Spatially Enabled Enterprise

• Enterprise GIS
• Focus is on widespread access to (limited)
  technology
• Deployment of GIS web applications to the
  Enterprise
• Often Proprietary to a Specific GIS
• Often Focused on Frequently Asked Questions
• Spatially Enabled Enterprise
• Focus Is on Integration of Geospatial Technology
  Throughout the Enterprise
• Maximises Use of Geospatial Data Through
  Enterprise Repository
• Embeds Spatial Data Technologies in Enterprise
  Applications
• May Allow Mixed Development Tools
• Architecture Supports GIS and Traditional
  Business Applications

8
Integrating Spatial Data into Enterprise Data
Resources

• Its Already There, but No One Noticed!
• So, How to Make Effective?
• Add Graphical Representations
• Use Server-side Technology to Link Graphic to
  Non-graphic Spatial Data
• Use Client-side GIS Query Visualization Tools
• Then, What Gets in the Way?
• Obstacles Include
• Issues of Database Design
• Issues of ETL Procedures
• Issues of Data Conflation
• Issues of Knowledge Mismatch Among Technical Staff

9
Fundamental Business Drivers

• What is changing
• Internet computing
• Service Delivery
• Expectations
• End-users
• Service Providers
• Citizens

10
Internet Technology Changes Spatial

• Proprietary to Open
• Files to Data
• Fragile to Flexible
• Few to Many
• Experts to Anyone
• Workstations to Any Client Device
• Slow to Fast
• Expensive to Bargain
• Point application to Strategic
• Cost Center to Profit Center

11
GEA within EA Benefits

• Improved Business Processes
• Increased Self-Service - SOA
• Improved Decision Making
• Better, Faster, More Efficient Operations
• Improved Service Levels and Customer Satisfaction
• Enhanced RDBMS features
• Full access to RDBMS Utilities
• Scalability, any volume, any platform
• Open programming standards, Java and SQL
• Spatially enable any database table
• Spatial standards for interoperability
• Ease of Integration
• The ability to publish and distribute spatial
  data to both GIS and Business Applications

12
Enterprise GIT / IT Architecture

• The citizen oriented e-government approach to
  improve information sharing across governmental
  boundaries and support service oriented
  applications can be catalyzed through a spatially
  enabled EA.
• NASCIOs EA effort is adaptive as it must be able
  to support a wide variety of applications and
  also must morph and evolve as technologies
  change. As such, its goal is to provide
  described methodologies for developing an
  organizations IT support functions - to include
  geospatial data and analysis.
• Increased implementation of GIT at federal, state
  and local levels necessitates the need for
  guidance and direction in promoting the
  interoperability of the IT and GIT domains that
  are necessary for addressing the complex business
  needs of government.
• NASCIO EA is currently lacking a geospatial
  template that would outline the governance,
  business, and technical components and processes
  for allowing data to be related and queried via
  their spatial context.

13
Enterprise GIT / IT Architecture

• By sharing horizontally and vertically among
  organizations these developed GIT templates will
  empower each governmental sector participating to
  leverage their investments in geospatial data to
  create new information for support of
  decision-making and their business processes.

14
Process for Achieving Interoperability Services
Oriented Architecture

• Components of systems are now built to
  interoperate primarily through the passing of
  structured messages at interfaces designed for
  networking
• Each set of operations exposed at a network
  interface is defined as a service
• NSDI requires this interoperability approach,
  known as a Services Oriented Architecture

15
Process for Achieving Interoperability Services
Oriented Architecture

• A small number of well-defined and commonly
  supported services provide broad NSDI
  interoperability
• Registries of services (e.g, UDDI, ebXML, GSA
  Core.Gov, ...) can be helpful if there are many
  service specifications in use

16
Process for Achieving Interoperability Technical
Standards

• U.S. NSDI employs various standards, e.g.,
• OGC Web Map Service, Web Coverage Service, Web
  Feature Service
• ISO 23950 (information search and retrieval
  service)
• ISO/IEC 11179 (metadata registries)
• ISO 19115 (documentation and representation)
• ISO 3166 (place codes)
• ... among others

17
Process for Achieving Interoperability Framework
Data

• Key aspects of Framework Data
• institutional relationships and business
  practices that encourage the maintenance and
  use of data
• procedures, technology, and guidelines that
  provide for integration, sharing, and use of
  these data

18
General Principles for Geospatial
Interoperability

• Geospatial interoperability should be inclusive,
  spanning levels of Government (Local, State,
  Tribal and Federal), as well as academic,
  commercial, and other non-Government
  organizations

Hence the term "National Geospatial Enterprise
Architecture"
19
National Geospatial Enterprise ArchitectureIntero
perability KISS

• "What few things must be the same so that
  everything else can be different"
• - Michael Tiemann, CTO of Redhat

20
Missouri Architecture Governance Processes

• Architecture Review Process - The process that
  allows the ARC to review, debate, discuss,
  make decisions about the changes to the
  Architecture Blueprint Manual
• Architecture Communication Process - The process
  that insures the architecture contents are
  communicated in a timely and accurate manner
• Architecture Compliance Process - The process to
  request a variance from the approved product or
  compliance components
• Architecture Vitality Process - The process that
  insures the Enterprise Architecture Blueprint
  contents remain current and accurate
• Architecture Change Management Process - The
  process that insures the architecture Manual
  contents remain current and accurate

21
Architecture Blueprint / Document Structure
Compliance Components apply at these 3 levels
22
Missouri Adaptive Enterprise Architecture GIT
Discipline

1. Descriptive Introductory Materials associated
   with the Geographic Information Technology (GIT)
   Discipline
2. Description What it is with brief examples
3. Rationale Why it is important to Missouri
   government with examples
4. Benefits Why it is important to Missouri
   citizens and other constituencies with examples

23
Missouri Adaptive Enterprise Architecture GIT
Discipline

• BOUNDARY
• Establish initial boundaries for Geographic
  Information Technologies

The GIT Discipline covers all technologies and
standards pertaining to the development of the
geospatial infrastructure, its data and metadata.
In addition, Imagery (Remote Sensing) and
Mapping (including Geographic Information Systems
(GIS), Computer Assisted Design (CAD), Global
Positioning Systems (GPS), Surveying,
Cartography) technologies, products and their
compliances are covered. Specific geospatial
aspects of data acquisition, indexing and
delivery (Internet Mapping Services (IMS)) are
identified and documented.
24
Missouri Adaptive Enterprise Architecture GIT
Discipline

• CRITICAL REFERENCES
• Initially identify the Domains/Disciplines that
  either will affect the GIT Discipline or vice
  versa.
• Further develop and document these possible
  relationships.

25
Missouri Adaptive Enterprise Architecture GIT
Discipline

• OTHER ELEMENTS OF THE DOCUMENTATION
• STANDARDS ORGANIZATIONS
• STAKEHOLDERS / ROLES
• TECHNOLOGY TRENDS
• COMPLIANCE COMPONENTS
• DOCUMENTATION REQUIREMENTS
• KEYWORDS
• EXISTING CONTRACTS
• EXISTING STANDARDS
• CURRENT STATUS
• AUDIT TRAIL

26
Technology Areas
Geographic Information Technology
(GIT) Geographic Information Technology provides
the ability to acquire and manage information
about the location and characteristics of
man-made and natural features and events above,
on and beneath the surface of the earth and to
assess their impact on citizens. Geographic
Information Technology provides the ability to
utilize locational information to model and
analyze relationships and present results to
enable better decision-making. Geographic
Information Technology provides the ability to
track man-made and natural features as they
change over time and space. For example, GIT can
track urban growth and its impacts on both the
municipal infrastructures and on the surrounding
rural communities.
Geospatial Information Technology
Remote Sensing Image Processing
Geospatial Metadata
Global Positioning Systems (GPS)
Geospatial Data Development Standards
Interactive Internet Mapping Service
Computer Aided Drafting and Design (CAD)
Analog to Digital Capture
Cartography
Spatial Indexing
Geographic Information Systems (GIS)
Compliance
Content Standard for Geospatial Metadata
Fit Matrix
Fit Matrix
Compliance Survey Grade Mapping
Grade Recreational Grade
Geospatial Positional Accuracy Standard
Open Geospatial Consortium Standards
Standards
Fit Matrix
Fit Matrix
Product
Product
Fit Matrix
Product ArcGIS 8.x ArcView 3.x Autodesk
Map Geomedia
Product
Product ArcCatalog CorpsMet SMMS M3Cat Tkme Xtme
Compliance
Compliance
Product
National Standard for Spatial Data Accuracy
Product
Compliance
Compliance
Compliance
Product
Digital Ortho Geodetic Control Elevation
Addressing Centerline Transport Hydrography Gov
Units Critical Infrastructure Land Use / Cover
Cadastral Soils Geology
Standards
Compliance
Standards
Compliance
27
Product Component Classification

• Emerging - Indicates new technology, which has
  the potential to become current.
• Current - Indicates recommended technology.
  Technology meets the requirements of the
  architecture.
• Twilight - Items that do not conform the
  Principles, Best Practices and Technology Trends
• Sunset - Items that do not conform to the
  Principles, Best Practices and Technology Trends,
  and a discontinuation date has been set.

28
Compliance Component Types

• Guidelines
• General statements of direction
• Recommended but not mandated
• Standards
• Mandated compliance criteria
• May be more than one standard to allow
  flexibility
• Must seek variance to deviate
• Mandates
• Legislated compliance criteria
• Cannot deviate variance not applicable
• Includes policy, executive order, statute, state
  or federal regulation

29
Repository Procedures
A system for managing the Architecture documents
at all stages of the Architecture Lifecycle

• Creating Architecture Blueprint Details
• Domain, Discipline, Technology Areas, Product/
  Compliance Components
• Reviewed by Architecture Office
• Templates
• Blueprint
• Communication
• Miscellaneous
• Check-Out/Check-In
• In Review
• Work on document halts

30
QUESTIONS