Title: Information Sharing Standards and Architecture
1Information Sharing Standards and Architecture
2InteroperabilityData StandardsXMLWeb
ServicesSOA
Topics for Discussion
3Frame 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
4Presidential Executive Order 13356
5MCOE Activities
- 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
6MCOE 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
7Solution (What is Core?)
Working with the Core.gov initiative to ensure
that these core elements are applicable across
the entire Federal Government. (FEA DRM)
8Universal Core
9Why SOA, XML Data Standards and Web Services for
the NCR?
10Types 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 its 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.
11Intelligence Built into the Data
OWL
Minis/Micros
WWW
Web Services
Age of Semantic Models
Age of Programs
Age of Proprietary Data
Age of Open Metadata
Age of Open Data
Text, Office Docs, Databases Proprietary Schemas
Namespaces, Taxonomies, RDF
Ontologies Inference
Program Data
HTML, XML Open Schema
1945-1970
1970-1994
1994-2000
2000-2003
2003-
Procedural Programming
Object Oriented Programming
Model Driven Programming
Data is as important as code
Data is more important than code
Data is less important than code
Mike Daconta DHS Metadata Program Manager
12Service 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.
13Information Sharing Architecture
Core Context
COI Context
3
Publish Discover
2
Assemble Exchange Packages
1
Build Components
Org 2
Org 1
14Data Exchange within the National Capital
RegionA proposed vision for data
interoperability within a Service Oriented
Architecture
15Vision
- 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
16Concept of Operations for a Data Exchange Solution
State 1
Fed Partner 1
State 2
COI 1
COI 3
Information Exchange Portal
SECURITY
App1
Security
All Other COIs
COI 4
SECURITY
App 5
App2
App3
GIS
SECURITY
SECURITY
App4
SECURITY
Fed Partner 2
COI 5
COI 8
CROSS FUNCTIONAL TEAM
State 2
17Data Exchange within the COG Where do we
start?Web Services/ GIS/ Federated Identity
Management
18Build Components
Identify Exchange PackageMap Transform Data
19Web Service Payload - XML
20Assemble Componentswithin an Organization
Presentation Tier
Component Tier
Back-Office Tier
Client Tier
COI Portal
ApplicationServers
COI 1
Mainframes
Browser
COI ApplicationInfrastructure
COI 2
WebServers
GIS Maps
WebEOC Status Boards
Databases
Enterprise Service Bus
IntegrationInfrastructure
Emergency Mgmt Framework/Enterprise Service Bus
Federated Search Engine
Intelligent Routing
XSLT - GJXDM Transformation
WebServices
Multiple Protocols
COI Service 2
COI Service 1
Alerting Service
COI Service 3
COI X Future Service Additions
Federated Identity
Components
21Assemble Components Across Organizations
Federated Buses
Federal Participants
Internet
Wireless
Broadband
Security?
Security?
Security?
Security?
???
Integrated DEH
COI 2
Security?
Security?
Security?
COI 5
COI 2
COI 2
COI 5
COI 5
22Information Exchange through Web Services
Discover Registered and Vetted Web Services
Data Exchange Hub
- 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
23Registered and Vetted Web Services
24Result Integrated Incident Information
25NCR Enterprise Architecture
(HTTP//WWW.FEAPMO.GOV)
- Business Reference Model (BRM)
- Lines of Business
- Agencies
- Customers/Partners
Business-Driven Approach
- Data Reference Model (DRM)
- Business-focused data standardization
- Cross-Agency Information exchanges
Information Architecture
- Application Reference Model (ARM)
- Capabilities
- Functionality
- Technical Reference Model (TRM)
- IT Services
- Standards
26Implications 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