10. OGC
®
An OGC Framework for Smart Cities
• “OGC Smart Cities
Spatial Information
Framework”
– https://portal.opengeospatial.org/files/?artifact_id=61
188
• Influenced by:
– OGC’s geospatial, sensor, processing,
mobile standards work
– Survey of Smart City Standards
Activities:
• JTC 1, ITU, ISO, BSI, DIN, others
– Survey of OGC CityGML
implementations
• Goals:
– Pilot Smart Cities Spatial Framework in
select cities (http://www.opengeospatial.org/blog/1886)
– Advance an OGC Best Practice for
Location Enabled Smart Cities
OGC Smart Cities Spatial Information
Framework
SWE standards are developed and maintained by OGC members who participate the OGC Technical Committee's Sensor Web Enablement Working Group .SWE offers integrators:
Open interfaces for sensor web applications
"Hooks" for IEEE 1451, TML, CAP, WS-N, ASAP
Imaging device interface support
Opportunity to participate in an open process to shape standards
Sensor location tied to geospatial standards
Fusion of sensor data with other spatial data
Ties to IEEE and other standards organizations
Sensor technology, computer technology and network technology are advancing together while demand grows for ways to connect information systems with the real world. Linking diverse technologies in this fertile market environment, integrators are offering new solutions for plant security, industrial controls, meteorology, geophysical survey, flood monitoring, risk assessment, tracking, environmental monitoring, defense, logistics and many other applications.
The SWE effort involves OGC members in developing the global framework of standards and best practices that make linking of diverse sensor related technologies fast and practical. Standards make it possible to put the pieces together in an efficient way that protects earlier investments, prevents lock-in to specific products and approaches, and allows for future expansion. Standards also influence the design of new component products. Business needs drive the process. Technology providers and solutions providers need to stay abreast of these evolving standards if they are to stay competitive.
OGC StandardsThe main adopted or pending OGC Standards in the SWE framework include:
Observations & Measurements (O&M) –The general models and XML encodings for observations and measurements.
PUCK Protocol Standard – Defines a protocol to retrieve a SensorML description, sensor "driver" code, and other information from the device itself, thus enabling automatic sensor installation, configuration and operation.
Sensor Model Language (SensorML) – Standard models and XML Schema for describing the processes within sensor and observation processing systems.
Sensor Observation Service (SOS) – Open interface for a web service to obtain observations and sensor and platform descriptions from one or more sensors.
Sensor Planning Service (SPS) – An open interface for a web service by which a client can 1) determine the feasibility of collecting data from one or more sensors or models and 2) submit collection requests.
SWE Common Data Model – Defines low-level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework.
SWE Service Model – Defines data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types.
Other SWE standards are under discussion or in various stages of development.
The OGC and SensorsThe OGC® is an international industry consortium of more than 330 companies, government agencies, research organizations, and universities participating in a consensus process to develop publicly available interface standards.The OGC has become involved in the sensor web standards effort because this technology domain needs standards that address a broad set of critical real world information interoperability demands, including information about location. OGC members have reached agreement on the most of the issues involving digital communication about location, motion, coordinate systems, spatial operations, raster and vector representations of features and phenomena, etc. Many of the major software vendors, solution providers and government members who want sensor web standards were already involved in the OGC consensus process. And the OGC has demonstrated its ability to facilitate a process in which members can rapidly develop, test and validate standards and harmonize them with standards from other standards organizations.Key components of the OGC standards process are the OGC Innovation Program and the OGC Specification Program
The OGC Innovation Program (IP) is a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards into OGC's Specification Program, where they are formalized for public release. OGC Innovation Program Initiatives include test beds, pilot projects, and interoperability experiments
The OGC Specification Program provides an effective and well-trusted industry consensus process to plan, review and officially adopt OGC Standards for interfaces, encodings and protocols that enable interoperable services, data, and applications. The Specification Program consists of two primary organizational units, the OGC Technical Committee (TC) and the OGC Planning Committee (PC).
Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report
The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives:
Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management.
Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability.
Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability.
Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.
These principles continued through the IoT Pilot Extension, with additional objectives of:
Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1.
Steps to begin the integration of existing incident management infrastructure, e.g., pulling in National Institute of Emergency Management (NIEM) message feeds.
Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility).
The initial Pilot activity has been documented in three OGC public engineering reports. This present report describes and documents the additional activities and innovations undertaken in the Extension.
The Standards of organisations such as the OGC belong to all