PULSENet TM and the Application of Sensor Standards in the Defense and Intelligence Community Ocean Innovation 2008 Workshop October 22 nd, 2008 Scott Fairgrieve Northrop Grumman
Oceans Innovation 2008 Conference Workshop 2 Need for proven sensor standards that can support: All types of sensors Legacy and new systems Web services and SOA Security concerns The Defense and Intelligence (D & I) Environment D & I Challenges Many sensors and platforms with various modalities and levels of complexity (sea, ground, air, and space based; mobile and in-situ) Many communication methods and data formats Many security and releasability concerns Many legacy systems Many different organizations with different requirements and often an unwillingness to share data D & I Focus Areas Standards and interoperability Net-centric operations, web services, and SOA concepts Distributed Common Ground/Surface System (DCGS) and DCGS Integration Backbone (DIB) – SOA-based foundation for uniting the various services (Army, Navy, Marine Corps, etc.) and agencies (NGA, DIA, CIA, etc.) Lack of Interoperability Desire for Interoperability
Oceans Innovation 2008 Conference Workshop 3 D & I Support for Sensor Standards National Geospatial Intelligence Agency (NGA) has been a continued sponsor of the OGC standards Defense Intelligence Agency (DIA) has begun to integrate Measurements and Signals Intelligence (MASINT) sensors using OGC standards Defense Threat Reduction Agency (DTRA) is working with DIA to integrate DoD Chemical, Biological, Radiological, and Nuclear (CBRN) sensors Joint Program Executive Office for Chemical and Biological Defense (JPEO- CBD) is investigating the use of OGC standards in conjunction with standards they have developed for Chemical Biological Radiological and Nuclear (CBRN) sensors. The D & I community has supported the development and use of sensor/data type specific standards (i.e. CBRN Data Model, ANSI N42.42, etc.)
Oceans Innovation 2008 Conference Workshop 4 What is PULSENet TM ? Northrop Grumman’s Sensor Web Framework: –The goal of PULSENet TM is to provide discovery, access, visualization, dissemination, and control of widely dispersed, disparate sensor assets through a common, open standards-based suite of web services and encodings – creating the foundation for a Global Sensor Web. –The architecture is based on SOA and Open Geospatial Consortium (OGC®) Sensor Web Enablement (SWE) services and encodings. –Through SWE, PULSENet TM provides an architecture and software framework that enables: Remote discovery of sensors and capabilities Storage and retrieval of sensor observations Subscription to and notification of desired sensor alerts Remote sensor tasking (even automatically) Filtering sensors and data based on temporal and geospatial constraints A sensor standards testbed that can be utilized to evaluate and prove the viability of emerging sensor standards like the OGC SWE standards and IEEE 1451 to the D & I community as well as other communities
Oceans Innovation 2008 Conference Workshop 5 Review: OGC SWE Encodings and Services Encodings: –Sensor Model Language (SensorML): An XML-based format for completely describing and modeling a sensor –Observations and Measurements (O & M): An XML-based format for describing sensor observations –Transducer Markup Language (TML): An XML-based format for streaming sensor descriptions and data in real-time Services: –Sensor Observation Service (SOS): A service for storing and accessing archived and near real-time sensor observations –Sensor Planning Service (SPS): A service for remote tasking of sensors such as cameras and UAVs –Sensor Alert Service (SAS): A service for subscribing to and being notified of sensor alerts –Web Notification Service (WNS): An asynchronous messaging service for long-running processes that works with the SPS and SAS –Catalog Service for the Web (CS/W)/Sensor Registry: A service for publishing and discovering available SWE web services and sensors that meet user needs.
Oceans Innovation 2008 Conference Workshop 6 Non-OGC Encodings/Standards Cursor on Target (CoT): An XML-based format for disseminating critical event information (i.e. who, what, when, where, etc.) used primarily in military applications – used by PULSENet TM to disseminate sensor alerts Common Alerting Protocol (CAP): An XML-based format for disseminating public safety alerts – used by PULSENet TM to disseminate sensor alerts IEEE 1451: A low-level sensor standard developed by the National Institute for Standards and Technology (NIST) that enables sensor plug-and-play capabilities.
Oceans Innovation 2008 Conference Workshop 7 PULSENet TM Accomplishments Successfully developed and integrated a SWE-based sensor web architecture in multiple field tests. Developed the plug-in based Sensor Listener Service (SLS) for translating and publishing legacy/non-standard sensor data into the OGC SWE standard formats Incorporated several disparate types of sensors into the architecture including: –Weather Stations, field and NOAA –Unattended Ground Sensors (UGS) (magnetic, seismic, passive infrared, acoustic, break beam, and mote fields) –Electro-Optical (EO) and Infrared (IR) (UGS cameras and ArgonST’s Mobile Defender) –Air Quality –Traffic Cameras –Working on other sensors Developed a Skyline TerraExplorer Pro based client application for working with the SWE services and formats that allows for: –Discovering sensors within an area of interest –Viewing sensor descriptions –Retrieving sensor observations –Tasking sensors –Subscribing to and being notified of sensor alerts –Performing more complex functions such as event initiated procedures (i.e. tasking a camera to point at a received sensor alert) Developed a KML Adapter web service that allows sensors and data available through SOS instances to be discovered and viewed using Google Earth. Developed a prototype OGC SOS interface to the IEEE 1451 Smart Transducer Web Service (STWS) as a starting point for integrating IEEE 1451 sensors into OGC SWE-based architectures
Oceans Innovation 2008 Conference Workshop 8
9 Video: The Power of Standards
Oceans Innovation 2008 Conference Workshop 10 Empire Challenge (EC) Annual NGA-led (Joint Forces Command (JFCOM)-led in 09 on), multi-INT, joint US/Coalition Intelligence Surveillance and Reconnaissance (ISR) interoperability demonstration Sponsored by JFCOM, Joint Staff (J2/J2S), and Joint Interoperability Test Command (JITC) Simulates real-world operational environments (i.e. Iraq and Afghanistan) Includes support from UK, Canadian, Australian, and NATO assets. Focused on: –DCGS/DIB interoperability –Information Sharing (internally and with Coalition partners) –Rapid development to transition technologies to the warfighter quickly Often includes a maritime component
Oceans Innovation 2008 Conference Workshop 11 PULSENet TM /Sensor Standards in EC 07 Integrated 100+ UGS using OGC standards and Cursor on Target (CoT) Provided National Imagery Transmission Format (NITF) 2.1 compliant imagery from EO/IR sensors through CoT Integrated Full Motion Video (FMV) and other streaming sensor data through OGC TML Multi-source sensor data integrated into multiple Common Operating Pictures (COPs), including the PULSENet TM Client, Google Earth, FalconView, and Command and Control Personal Computer (C2PC).
Oceans Innovation 2008 Conference Workshop 12 PULSENet TM /Sensor Standards in EC 08 Integrated OGC web services provided by several different vendors, including access to data from a variety of UGS, sensors on- board a TigerShark UAS, hundreds of weather sensors, and sensors on-board EO-1. Brought in NASA EO-1 and NOAA weather data and served data through OGC web services. Disseminated weather data via Cursor on Target (CoT) to other exercise participants and the main COP. Converted NASA EO-1 data to NITF 2.1, passed the data up to higher security level networks, and ingested the data into the Imagery Product Library (IPL), where it was shared with initiatives.
Oceans Innovation 2008 Conference Workshop 13 IEEE 1451 Applicability IEEE 1451 will have increased applicability in the D & I world. IEEE 1451 uses: –Swapping sensors in and out of various platforms and systems, allowing the use of the appropriate set of sensors to support mission requirements –Adding new sensors to platforms/networks with no configuration/software changes Integration of IEEE 1451 and OGC SWE standards: –Plugging in/removing a sensor automatically updates corresponding OGC SWE web services and CS/W instances –Appropriate SensorML, O & M, and TML information is generated on the fly from IEEE 1451 transducer information Consider showcasing IEEE 1451 systems in future D & I demonstrations like Empire Challenge
Oceans Innovation 2008 Conference Workshop 14 IEEE 1451 & SOS Interoperability Raw Sensor Data (e.g., IEEE1451) GML Feature Chemical Event Feature IEEE 1451 TEDS + Sensor Channel Data WFS (Rad Feature) Client Schema Mapping WPS (transform + fusion) SOS (IEEE1451 – SensorM/O&M & TML) IEEE 1451 NCAP Composite map Observation Object (e.g., measurement of temperature, rad. spectrum, velocity, etc + metadata) Algorithm Data Center/Workflow Engine IEEE 1451 compliant sensor plugged into the network 1 IEEE 1451 components automatically discover the sensor 2 The SOS Interface interacts with the IEEE 1451 components to discover available sensors, retrieve their data, and publish sensor descriptions and data in OGC SWE standard formats 3 IEEE 1451 sensors are now available to be discovered and utilized by OGC SWE clients and workflows 4
Oceans Innovation 2008 Conference Workshop 15 Sensor webs are used to: Forecast fire behavior, smoke dispersion, and air quality Retask sensors for making new measurements Retrospectively analyze and assess state of atmosphere Validate forecast models Issue public health alerts PULSENet TM /Sensor Webs in Wildfire and Smoke Applications Standard interfaces allow two-way information flow between sensors and forecast models: Sensor data feeds models. Model output feeds sensor tasking.
Oceans Innovation 2008 Conference Workshop 16 Ocean Sensor Applicability to the D & I Community D & I Mission Operations –Providing access to ocean domain sensors using the same standard formats that are used to access ground, air, and space-based sensors allows for easy integration into existing operations. Humanitarian Assistance and Disaster Relief (HADR) –The D & I community provides an important role in responding to natural disasters like Tsunamis, Hurricanes, Monsoons, etc. –HADR requires a coordinated response and effective information sharing between military and civilian agencies and assets. Providing access to ocean domain sensor assets through standard interfaces allows the D & I community to work more effectively with civilian agencies that have access to better information in the ocean and environmental monitoring domains. –Example: A civilian Tsunami warning system automatically notifies D & I agencies when Tsunami pre-conditions are encountered using OGC SWE standard sensor alerting mechanisms. The D & I agencies coordinate with civilian agencies and access civilian sensor assets in the area through OGC SWE standard interfaces to monitor the situation while establishing an effective response.
Oceans Innovation 2008 Conference Workshop 17 Questions?
Oceans Innovation 2008 Conference Workshop 18 Contact Information Dr. Stefan Falke – Project PI –Location: St. Louis, MO –Phone: – Scott Fairgrieve – Technical Lead –Location: Chantilly, VA –Phone: –
Oceans Innovation 2008 Conference Workshop 19