© 2004 – fairfax county government - dit information sharing standards and architecture

© 2004 – Fairfax County Government - DIT

Information Sharing Standards and Architecture


InteroperabilityData StandardsXMLWeb Services

SOA

Topics for Discussion


Frame of Reference

• Use Cases– State Magistrate Arrest Warrants

• Local Sheriff Booking-In process• Juvenile Detention Entry Process• Federated Search of Terrorism Watch Lists

– Citizen Complaints

There exists and 80% probability that most organizations will have migrated to a Service Oriented Architecture by 2008. Those who do not will be paying a very high premium to boutique contractors to integrate with existing legacy systems.”-Mike Belchar , Research Analyst with Gartner


Presidential Executive Order 13356


• Information Sharing and Liaison Services– Support and populate metadata registry/repository– Support and populate data source registration

• Standards and Policies Development– Develop and revise MCOE standards for:

• Metadata discovery, modularity, reuse, integration, …– Develop and revise MCOE policies for:

• Governance, Data stewardship, Metadata registration, …• Standards Testing and Prototyping

– Applied research – test implications of multiple standards– Conduct proof-of-concept experiments– Architect and test for scalability and security for:– Cross federated queries

MCOE Activities


• Registry, Catalog and Middleware Services– Establish final COTS Metadata registry– Establish enterprise data source catalog– Future Enterprise Software

• Justice Information Exchange Model (JIEM) Server• Enterprise Taxonomy Server• Analysis Tools

• Education and Outreach Services Support– Training about technical metadata registry/repository & data

sharing concepts• Enterprise Metadata Modeling Services

– Support the adoption of the DHS DRM by other organizations.– Implement a federated query model

MCOE Activities


Solution (What is Core?)

Working with the Core.gov initiative to ensure that these core elements are applicable across the entire Federal Government. (FEA DRM)


Universal Core


Why SOA, XML Data Standards and Web Services for the NCR?


Types of Interoperability

Application Level Agencies or organizations use the same application to perform the same business functions. Shared applications are useful if the application is built specifically with that purpose in mind. Example: WebEOC has a "checkbox" to mark "significant events" that are then shared regionally. A shared CAD system would represent application level interoperability provided it is designed to accommodate multiple agency operations with separate event resourcing and tracking

Data Level Agencies or organizations use standards-based technologies to share specific data elements in specific ways. Example: CAD-to-CAD data level interoperability would include the ability to “push” event and resource data from one CAD system to another CAD system in order to enable another organization to “pull” an event into it’s CAD system.

Portal Level Portals enable communities of interest to share data that is of relevance to each through a common interface or portal. Portal level interoperability provides the option to offer several services via a single portal and to address multiple communities of interest that may have an overarching goal such as homeland security. Portals bring streams of data to particular communities of interest and enable filtering, chat functions and other tools and capabilities to used against the data stream. Portal level interoperability relies on standards-based data level interoperability.


Intelligence Built into the Data

1945-1970 1970-1994 1994-2000 2000-2003 2003-

ProceduralProgramming

Object OrientedProgramming

Model DrivenProgramming

“Data is less important than code”

“Data is as important as code”

“Data is more important than code”

Age of Programs

Age of Proprietary Data

Age of Open Data

Age of Open Metadata

Age of Semantic Models

Minis/Micros WWW Web Services OWL

Program Data

Text, Office Docs, Databases – Proprietary Schemas

HTML, XML – Open Schema

Namespaces, Taxonomies, RDF

Ontologies & Inference

Mike DacontaDHS Metadata Program Manager


Service Oriented Architecture

A collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity.


Information Sharing Architecture

Org 1Org 2

DataElems

DataElems

Exchange

packages

Registry

COI Context

Core Context

Build Components

Assemble Exchange Packages

Publish & Discover

1

3

2


Data Exchange within the

National Capital Region

A proposed vision for data interoperability within a Service Oriented Architecture


Vision

• Provide a real-time interactive system designed to strengthen the flow of information between government functions within the National Capital Region

• Provide a collaborative communications environment, through which member jurisdictions collect and disseminate information between themselves and with federal and state agencies :– Chat rooms

– Threaded discussions

– Virtual Field Offices

– Web Service Registry/Repository and XML

– Federated Searching capabilities


Concept of Operations for a Data Exchange Solution

COI 3

COI 4

COI 5COI 8

COI 1

App4App3G

IS

App 5

App1

App2

SECURITY

SECURITY

Secu

rity

SECURITY

SECU

RITY

SECU

RITY

CROSS FUNCTIONAL TEAM

State 2

State 2

State 1

All Other COIs

LEAD

LEAD FUNCTION

Fed Partner

2

Fed Partner

1


Data Exchange within the COG Where do we start?

Web Services/ GIS/ Federated Identity Management


Build Components

Identify Exchange PackageMap & Transform Data


Web Service Payload - XML


Assemble Componentswithin an Organization

BrowserApplication

Servers

Databases

Mainframes

COI Portal

WebServers

Client TierPresentation Tier Component Tier Back-Office Tier

CO

I A

pp

lic

atio

nIn

fras

tru

ctu

re

AlertingService

COI Service 2 COI Service 3 COI X Future

Service Additions

COI Service 1

Co

mp

on

ents

Emergency Mgmt Framework/Enterprise Service Bus

Enterprise Service Bus

Inte

gra

tio

nIn

fras

tru

ctu

re

Federated Search EngineWeb

ServicesXSLT - GJXDMTransformation

Intelligent Routing

GIS Maps

COI 1

COI 2

WebEOC Status Boards

Federated Identity

Multiple Protocols


Assemble Components Across Organizations Federated Buses

DEH

DC

VA ParticipantsDEH

MD ParticipantsDEH

Integrated DEH

EOCs

Other RegionalAgencies

Other Federal,State, Local AgenciesESFs

WS

Information Exchange Portal

COI 2

COI 3

COG Weather GIS – EMMA, DHS

DHS JRIES NEWS Feeds

WS

WS

Federal Participants

DHS

MCO MRR

Security?

WS

Security?Security?

COI 2

COI 2

COI 2

COI 5

COI 5COI 5

Security?

???

Broadband Wireless Internet

Security?Security?Security?


Information Exchange through Web Services

Jurisdiction 1•Police Stations by Location•Hospitals by Location•First Responder Personnel by Role•Significant Events by Location

Jurisdiction 2•Police Stations by Location•Hospitals by Location•First Responder Personnel by Role•Significant Events by Location

…

Integrated Services•Map Service for NCR

Data Exchange Hub

DiscoverRegistered and Vetted Web Services


Registered and Vetted Web Services


Result – Integrated Incident Information


Business Reference Model (BRM)•Lines of Business

•Agencies

•Customers/Partners

Data Reference Model (DRM)•Business-focused data standardization

•Cross-Agency Information exchanges

Application Reference Model (ARM) •Capabilities

•Functionality

Technical Reference Model (TRM) •IT Services

•Standards

Bu

sin

ess-D

riven

Ap

pro

ach

(HTTP://WWW.FEAPMO.GOV)In

form

atio

n A

rch

itectu

re

NCR Enterprise Architecture


Implications of Standards for GIS Committee Goals and Objectives

•An integrated Map of the NCR with a few high value – low issue layers (ie. Minimum Essential Data Elements).

•Definition of a Federated Identity Management System

•NIEM Based Web Services

•A Web Services Directory for publishing and discovering the individual Web Services produced by participating jurisdictions

•Investigate the capabilities of Enterprise Service Buses

© 2004 – fairfax county government - dit information sharing standards and architecture

Documents

xml data standards

architecture slide

data stewardship

resource data

discussion slide

gartner slide

specific data elements

revise mcoe standards