Defense Installations Spatial Data Infrastructure Defense Installations Spatial Data Infrastructure (DISDI) Portal: Phase II (DISDI) Portal: Phase II
JSEM 2007JSEM 2007May 23rd, 2007May 23rd, 2007
Contact:Contact:Costi TudanCosti Tudan
ODUSD(I&E) BEI DISDIODUSD(I&E) BEI DISDI
2
Agenda
• Strategic Guidance
• Net-centric data strategy
• Capability Review
• Issues
• Future Direction
3
Background
The RP&ILM CBM will provide the Warfighter and other Core Business Missions with continuous access to I&E information.
“ Data is an essential enabler of network-centric warfare and shall be made visible, accessible, and understandable to any potential user in DoD as early as possible in the life cycle to support mission objectives.” DOD Directive 8320.2 December 2, 2004.
4
• The Net-Centric Data Strategy (signed May 9, 2003) is a key enabler of the Department’s transformation.
• DoDD 8320.2 (signed Dec 2, 2004) directs implementation of the Net-Centric Data Strategy.
• DoD 8320.2 – G (signed April 12, 2006) provides guidance for implementing the DoD Net-Centric Data Strategy.
• The Strategy provides the foundation for managing the Department’s data in a net-centric environment, including:
Ensuring data are visible, accessible, and understandable when needed and where needed to accelerate decision making“Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery by known and unanticipated users in the EnterprisePosting of all data to shared spaces for users to access except when limited by security, policy, or regulationsOrganizing around Communities of Interest (COIs)Establish Communities of Interest to understand the nature of the change.
Strategic Guidance
5
Goals
• Foundational support
• Clean, auditable data
• Net-centric availability
• Standards based
6
Enable Data to be Understandable
Metadata. Metadata. Metadata.
Three types of metadata are relevant to DISDI:
• Geospatial Data– e.g. “This GIS file includes boundaries for Langley AFB”– How? FGDC metadata (CSDGM, ISO 19115)
• Services– e.g., “Use this web service to access boundaries for Langley AFB”– How? OGC WMS, WFS, DDMS (DoD Discovery Metadata Specification)
• Vocabulary and taxonomy– e.g., “I can access the boundary file for Langley AFB, but I do not know how it is
structured”– How? SDSFIE, OWL, taxonomy registered on DoD Metadata Registry
7
Enterprise ObjectivesEnterprise Objectives
MissionsMissions
Technology ProgramTechnology Program
Enterprise objectives established Enterprise objectives established
Missions sets derived fromMissions sets derived fromEnterprise objectivesEnterprise objectives
Technology programs derived Technology programs derived From mission requirements From mission requirements
Enterprise objectives drive technology
Technology expands mission horizons
Missions evolve from convergence of objectives and technology
Missions
Shift from Technology Derived from Missionsto Missions Enabled by Technology
Enterprise ObjectivesEnterprise Objectives
Technology ProgramTechnology Program
8
Geospatial Business Transformation
• Net-Centric Data Strategy– Many users, one map = standard installation map
• Geospatial Data– Discoverable, Understandable and Accessible to
Anticipated and Unanticipated Users
• Authoritative Location– Enterprise-provided – Standards-based– Future BEA 5.0 to include geospatial location
framework
BEA 5.0FutureFuture
9
Example: Geo-enabling the DoD Real Property Inventory
Sites and Land ParcelsDover AFB, DE
SiteBoundariesLand Parcels (fee)Land Parcels (less than fee)
• Goal: Formal Registry of accurate real property data, including site locations.
• Site Registry – Authoritative, non-spatial repository of all DoD “sites”
• Mapping Site Locations (legal boundaries) is a key component of the RPI
– Based on land descriptions from acquisition deeds, lease agreements, SOFA agreements, etc.
– Entered using Coordinate Geometry using legal (parcel) land descriptions
• Relevance to DoD Installations– One Base – One Map– All mission areas
10
DoD Architecture Alignment
• Constructing a universal core data schema that enables information sharing
– Ways to describe “when, where, what” – Minimal set of terms in the core– Agreed to by DoD and Intel Community– Appropriate use of open and Federal
standards– Extensible by COIs and systems as
needed
Log
Common
CoreC2
Common Core
ISR Common Core
Business Common
Core
EIE
Com
mon
Co
re
Universal Core
COI Extensions
DoD Component and IC Member Extensions
WHERE = Geospatial and Real Property Information
11
Geospatial SOA RoadmapGeospatial SOA Roadmap
“Grass-roots” Web MapServices Implementations
Mission CriticalWeb Services
SOA Pilots
Enterprise SOA Buildout
Heterogeneous SystemsProprietary Interfaces
Wrap legacy systems inservices interfaces
Secure Service Interfaces
Manage Services
Dynamic Service Discovery
Implement SOA Metamodel
Service-Oriented Process
Business-Oriented Services
Just-in-time IntegrationService-Oriented
Enterprise
IGI&SCommunity
DoDCommunity
12
InstallationData FeatureStewards
Department,OSD
TacticalTacticalFocusFocus
StrategicStrategicFocusFocus
Regions andMajor Commands
Component
DISDI Concept of Operations (CONOPS)
DoD “Enterprise” DoD “Enterprise” missions (RPI, DCIP)missions (RPI, DCIP)
Defense AgenciesDefense Agencies Federal AgenciesFederal Agencies
Combatant Combatant CommandsCommands
Installations
DISDI
13
data collection and maintenance
data management and QA/QC
data analysis, integrationportal implementation
Component data merge, Joint analysisportal implementaion
The data perspective
14
The technology perspective
desktop GIS, GPS, fieldwork
desktop GIS, geospatial repositoryQA/QC, intranet map services
DB of record, development,metadata, portal implementation
DoD discovery, metadata, access,information assurance, portal implementation
15
KNOWN USERS
User Access Continuum
AF
USMC
Army
Navy
conn
ectiv
ity a
nd s
ecur
ity p
aram
eter
s MDRDoD Portal
…
MetadataRegistry
mer
ged
data
DISDIGeo-enabledApplications
disc
over
y an
d ac
cess
Specific
Joint
Unanticipated
Component assets
Merged pathways
Potential user pathways
Map Service Providers
Metadata and Service RegistriesSearch Engines and SOA Foundation
DoD Portal ApplicationsSOAF users
Dat
aBas
esof
Rec
ord
UNKNOWN USERS
16
Information Assurance Strategy
DoD has developed a new DoD C&A instruction and two DoD-owned Web-based services based on COTS applications to transform the DoD C&A process in support of the
Net-Centric, GIG-based environment
• DIACAP (“DoD Information Assurance Certification and Accreditation Process” - DoDI 8510.bb)– Supersedes DoDI 5200.40, “DoD Information Technology Security
Certification and Accreditation Process (DITSCAP)”– Adjudication of Formal SD 106 comments is near-completion
• DIACAP Knowledge Service (KS)– Web-based resource for DIACAP implementation; – Enterprise Mission Assurance Support Service (eMASS)– IA program management service; automates C&A workflow; pilots in progress
17
DoD Global Enterprise Services Portal Framework
18
FedSearchNSDI
Metadata Harvesting
USAPortal
GIS-R
USNPortal
GeoReadinessRepository
USMCPortal
GeoFidelis
USAFPortalGeoBase
Consuming Geospatial Services
Metadata Harvesting: Z39.50, WAF, OAI
TEC IOImagery
Data Services: OGC WMS, WFS, Data Caching
Internet Web Services
DISDI Portal Architecture Consuming and Publishing Geospatial Data
DISDIPortal
DISDIPortalViewer Metadata
Portal
Producing Geospatial Services
DoD Applications and Systems
OGC WMS, WFS, KML, File Download
19
FedSearchNSDI
Metadata Harvesting
DoD Applications and Systems
OGC WMS, WFS, KML, File Download
Producing Geospatial Services
USAPortal
GIS-R
USNPortal
GeoReadinessRepository
USMCPortal
GeoFidelis
USAFPortalGeoBase
Consuming Geospatial Services
Metadata Harvesting: Z39.50, WAF, OAI
TEC IOImagery
Data Services: OGC WMS, WFS, Data Caching
Internet Web Services
DISDI Portal Architecture Enabling Service-Oriented Architecture (SOA)
DISDIPortal
DISDIPortalViewer Metadata
PortalWeb
Se
rvic
e In
terf
ace,
SO
A
SOAP,WSDL
DoD Metadata Registry
DoD Discovery Catalogs
DoD Service (UDDI) Registry
Global Information Grid (GIG) Connectivity
20
Web Services - Issues
• Appropriate use– Intended use of the data (consider OPSEC issues)– Emerging: GeoDRM
• Access Rights– Control who can access the data (establish “need to know”)– Identity Management, Role Based Access Control
• Metadata– Information on all of the above to accompany each data set– Discover and understand: DoD Metadata Registry
• Data maintenance– Keeping the data up-to-date and accurate
• Service levels– Level of availability that a user/subscriber can expect– Minimal guaranteed content
StandardsStandardsMetadataMetadata
PolicyPolicy
Solution
21
Future Standards Alignment• ISO 19119 – Geographic Information Services
– critical to defining where the web services are deployed and used within the SOA
• Catalog Services (CS-W)– Abstract model and protocol-specific solutions for the discovery of
geospatial resources.
• Styled Layer Descriptor (SLD)– Applying rendering or symbolization rules to features. – An SLD requests a WMS to present a map according to submitted style
rules.
• Web Map Context (WMC)– Companion to WMS – describes howto save a map view comprised of
many different layers from different Web Map Services.
• Filter Encoding Specification (FE)– Used in requests to WFS and queries to CS-W.
• ISO 19115 – Metadata (in implementation)
• Web Coverage Service– Allows access to raster data sets
NGA GEOINTNGA GEOINTStandards Standards BaselineBaseline
22
DISDI Architecture Strategy: Summary
• There are known and unknown users of installation geospatial data– The DISDI CoI needs to accommodate both types of users by aligning with
DoD Net-Centric Data Strategy
• DoD’s Net-Centric Data Strategy defines goals for making our data available to the DoD enterprise– Make data visible– Make data accessible– Make data understandable– Standards alignment
• DISDI architecture strategy will meet these goals by:– Leveraging Service Component geospatial databases of record– Providing the DISDI Portal as a broker to common/joint (merged) data– Registering data, services, metadata and vocabularies to the DoD Metadata
Registry and DoD Portal– Using the DoD Community of Interest (CoI) Model to achieve these goals
23
Questions
Costi Tudan – DISDI ArchitectODUSD(I&E) BEI DISDI
Phone: 703-604-4616Email: [email protected]