Missouri Adaptive Enterprise Architecture Information Domain Geographic Information Technology Discipline MGISAC - NGEA & MO GIT Briefing Tim Haithcoat

Missouri Adaptive Enterprise Architecture Information DomainGeographic Information Technology Discipline

MGISAC - NGEA & MO GIT Briefing

Tim HaithcoatMissouri Spatial Data Information [email protected]

Eliot Christian, USGS/FGDC August 11, 2005

N S D I

National Spatial Data Infrastructure

August 11, 2005MGISAC Meeting 2

What is a Spatial Data Infrastructure?

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


Objectives for Spatial Data Infrastructuressource: Open Geospatial Consortium (OGC)

ClearinghouseClearinghouse

GeoparserGeoparser

• Reduce deployment costs by reusing information from other communities

• Tools to provide custom information to users

• Foundation for interoperable service networks

• Easier access to multiple online info sources and services

• Use and reuse different vendor solutions.

VendorData

Local Government

NationalGovernment

OtherCollections

Clearinghouse

WhovilleCedar Lake

WhovilleCedar Lake

BuildingsRoadsImagesTargetsBoundaries ...

CatalogView

Common interfaces enable interoperability

Queries extract info from diverse sources

Integrated View

Gazetteer CoordinateTransform

Web Mapping Server, Web Feature Server, Web Coverage Server Catalog Services

OtherServices

MetadataData

MetadataData

MetadataData

Metadata

Internet

Geoparser

Geocoder


Requirements of Law and PolicyFederal 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 NSDI:

To encourage the collection, processing, archiving, integration, and sharing of geospatial data and

information using common standards and interoperable systems and techniques



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. [...]



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).

August 11, 2005MGISAC Meeting

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


Integrating Spatial Data into Enterprise Data Resources

It’s 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


Fundamental Business Drivers

Do MoreWith Less

Improve Efficiencies

ImprovedServices

FundamentalBusiness

Drivers HaveNot Changed

What is changing:Internet computingService DeliveryExpectations

End-users Service Providers Citizens


Internet Technology Changes Spatial

Proprietary to OpenFiles to DataFragile to FlexibleFew to ManyExperts to AnyoneWorkstations to Any Client DeviceSlow to FastExpensive to BargainPoint application to StrategicCost Center to Profit Center


GEA within EA: Benefits

Improved Business ProcessesIncreased Self-Service - SOAImproved Decision MakingBetter, Faster, More Efficient OperationsImproved Service Levels and Customer SatisfactionEnhanced RDBMS featuresFull access to RDBMS UtilitiesScalability, any volume, any platformOpen programming standards, Java and SQL Spatially enable any database tableSpatial standards for interoperabilityEase of IntegrationThe ability to publish and distribute spatial data to both GIS and Business Applications


Enterprise GIT / IT ArchitectureThe 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. NASCIO’s 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, it’s goal is to provide described methodologies for developing an organization’s 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.


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.


Process for Achieving InteroperabilityServices Oriented

Architecture

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


Process for Achieving InteroperabilityServices Oriented

Architecture

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


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


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


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

General Principles for Geospatial

Interoperability

Hence the term "National Geospatial Enterprise Architecture"


National Geospatial Enterprise ArchitectureInteroperability KISS

"What few things must be the same so that everything else can be different"

- Michael Tiemann, CTO of Redhat


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


Architecture Blueprint / Document Structure

* Compliance Components apply at these 3 levels* Compliance Components apply at these 3 levels


Missouri Adaptive Enterprise Architecture – GIT Discipline

1. Descriptive Introductory Materials associated with the Geographic Information Technology (GIT) Discipline

1. Description – ‘What it is’ with brief examples2. Rationale – ‘Why it is important to Missouri

government’ with examples3. Benefits – Why it is important to Missouri citizens

and other constituencies’ with examples



BOUNDARYEstablish 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.



CRITICAL REFERENCESInitially identify the Domains/Disciplines that either will

affect the GIT Discipline or vice versa. Further develop and document these possible

relationships.



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


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

Geographic Information

Systems (GIS)

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

CartographySpatial Indexing

Fit Matrix

Digital Ortho Geodetic Control

Elevation Addressing

Centerline

Transport Hydrography

Gov Units Critical

Infrastructure Land Use / Cover

Cadastral Soils Geology

Geospatial Positional Accuracy Standard

National Standard for Spatial Data

Accuracy

Product

ArcGIS 8.x

ArcView 3.x

Autodesk Map

Geomedia

Compliance

Product

ArcCatalog

CorpsMet

SMMS

M3Cat

Tkme

Xtme

Compliance

Content Standard for Geospatial Metadata

Product

Compliance

Survey Grade

Mapping Grade

Recreational Grade

Standards

Product

Compliance

Open Geospatial Consortium Standards

Fit Matrix

Product

Compliance

Standards

Fit Matrix

Product

Compliance

Compliance

Standards

Fit Matrix

Product

Compliance

Fit Matrix

Product

Compliance

Technology Areas


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.

BestPractices

Principles Technology Trends


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


Repository Procedures

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

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


QUESTIONS

Documents

Missouri Adaptive Enterprise Architecture Information Domain Geographic Information Technology Discipline MGISAC - NGEA & MO GIT Briefing Tim Haithcoat