- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
OGC Web Services, Phase 7 (OWS-7) Request For Quotation and Call For Participation
RFQ Issuance Date: 28 October 2009
OWS-7 Bidder's Conference: 10 November 2009, 11:00-13:00 US Eastern
Proposal Due Date: 1 December 2009, 5:00 p.m. EST.
OGC members who wish to observe OWS-7 may do so upon submission of the OGC Observer Agreement: http://bit.ly/8DvwvK
OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC's Specification Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include test beds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.
The OWS-7 sponsors are organizations seeking open standards for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-7 initiative be organized around the following threads:
OWS-7 is organized in three activity "threads":
- Sensor Fusion Enablement (SFE)
- Feature and Decision Fusion (FDF)
OWS-7 SponsorsU.S. National Geospatial-Intelligence Agency (NGA)
U.S. Federal Aviation Administration (FAA)
EADS Defence Communications Systems (DCS)
U.S. Geological Survey (USGS)
U.S. Army Geospatial Center (AGC)
U.S. Joint Program Executive Office (JPEO)
In June of 2009, the OGC issued a call for sponsors for the OWS-7 interoperability initiative to advance OGC's open framework for interoperability in the geospatial industry. Three meetings were conducted with potential OWS-7 sponsors to review the OGC technical baseline, discuss OWS-7 results, and identify OWS-7 requirements. During the OWS-7 Concept Development phase, a Fusion Standards Study was also conducted, to better inform the requirements for OWS-7 development.
The definition of fusion resulting from the study was:
"Fusion is the act or process of combining or associating data or information regarding one or more entities considered in an explicit or implicit knowledge framework to improve one's capability (or provide a new capability) for detection, identification, or characterization of that entity".
There exist many fusion processes deployed in closed architectures with existing single provider software and hardware solutions. The problem in the study was to move those capabilities into a distributed architecture based upon open standards including standards for security, authorization, and rights management.
In the study, fusion was discussed in terms of the three categories shown in the central column in Figure 1‑1:
Figure 1‑1. Categories of Fusion
The sponsors selected elements of the Fusion Study results to include in the two OWS-7 threads described below. Sensor Fusion is addressed in the Sensor Fusion Enablement (SFE) thread. Object/Feature Fusion and Decision Fusion are addressed in the Feature and Decision Fusion (FDF) thread.
The threads of OWS-7 build upon the threads of previous OWS test beds, as shown in Figure 1-2.
Figure 1‑2. Evolution of OWS Testbed Threads
The Sensor Fusion Enablement (SFE) thread builds on the Sensor Web Enablement (SWE) and Geospatial Processing Workflow (GPW) thread by including Sensor Fusion topics and applying workflow to sensor fusion. The Feature and Decision Fusion (FDF) thread also builds on the OWS-6 Geospatial Processing Workflow (GPW) thread, as well as the OWS-6 Decision Support Services (DSS) thread, by including feature definition and workflow of GPW along with decision support topics.
The third activity thread in OWS-7, the Aviation Thread, began as the Aeronautical Information Management (AIM) Thread in OWS-6, which addressed the use of web services, event notifications, and AIXM 5.0 for Electronic Flight Bag (EFB) applications in the aviation industry. The Aviation Thread in OWS-7 represents an expansion of scope, to include flight planning and aviation operations more broadly.
Sensor Fusion Enablement (SFE)
The SFE Thread builds on the OGC Sensor Web Enablement (SWE) framework of standards that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. SFE will focus on integrating the SWE interfaces and encodings with workflow and web processing services to perform sensor fusion. SFE will continue the development of Secure SWE architecture, as well as the interoperability of SWE and Common CBRN Sensor Interface (CCSI).
Emphasis for SFE during this phase of the OWS testbed will be the following:
- Motion Video Fusion. Geo-location of motion video for display and processing. Change detection of motion video using Web Processing Service with rules.
- Dynamic Sensor Tracking and Notification. Track sensors and notify users based on a geographic Area of Interest (AOI). The sensor and the user may be moving in space and time.
- Trusted SWE in an untrusted environment. Build on OWS-6 Secure Sensor Web development, to investigate secure SOS, SPS in more depth.
- CCSI-SWE Best Practice. Building on OWS-6, develop an ER to be considered by the OGC Technical Committee as a Best Practice.
Feature / Decision Fusion (FDF)
The FDF Thread builds on OWS-6 GPW and DSS work, in particular to advance the state of information cataloguing, Web Processing Services (WPS) profiles, and the Integrated Client. The following task areas have been identified for Feature and Decision Fusion:
- Schema Automation. Transformation from UML to profiles of GML and KML, including generation of constraints.
- Data Discovery and Organization. Use of thematic categories in multi-media data discovery, including augmented metadata for quality of source, fitness for use, and uncertainty of the data values, propagated through usage and workflow.
- Feature and Statistical Analysis. Workflow profiles for feature fusion, including statistical analysis, vector and topological processing. WFS, WMS and WMTS will be used to support statistical mapping.
- Geosynchronization. Web services and client components to support synchronization of geospatial data and updates across a hierarchical Spatial Data Infrastructure (SDI).
- Data and Analysis Sharing. The use of OWS Context for collecting links to web services and analysis results.
- Integrated Client. A field-ready client application to support and display sensor information, cataloguing metadata, notification alerts, feature and statistical analysis, and OWS Context. This client will include an embedded WFS server for geosynchronization support.
This thread seeks to further develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) in an OGC Web Services environment.
The US Federal Aviation Administration (FAA) and EUROCONTROL have developed AIXM as a global standard for the representation and exchange of aeronautical information. AIXM uses the OGC Geography Markup Language (GML) tailored to the specific requirements for the representation of aeronautical objects, including the temporality feature that allows for time dependent changes affecting AIXM features. FAA and EUROCONTROL are using AIXM as an integral part of their efforts to modernize their aeronautical information procedures and to transition to a net-centric, global aeronautical management capability. More specifically, AIXM is being used in the net-centric System Wide Information Management (SWIM)-related components of the US NextGen and European Union (EU)'s SESAR programs. Indeed, it is expected that the results of the Aviation Thread of OWS-7 will be contributed to both programs with a focus on recommended OGC specifications that can be applied in the definition and implementation of both SWIM environments.
WXXM is also jointly developed by FAA and EUROCONTROL, as a proposed standard for the exchange of aeronautical weather information in the context of a net-centric and global interoperable Air Transport System (ATS). WXXM also uses GML tailored to the specific requirements of aeronautical meteorology and is based on the OGC Observation and Measurement Model. WXXM development is harmonized and coordinated with the World Meteorological Organization (WMO), the organization traditionally responsible for standards in meteorology.
The OWS-7 Aviation Thread will investigate and demonstrate the applicability of AIXM and WXXM along with relevant OGC specifications and web services to applications and tools that support Airline Operations Centers and Flight Dispatch applications. Such applications provide information for representing a Common Operating Picture; supporting flight planning (including General Aviation) and preparation (MET and AIM); calculating weight and balance; estimating fuel requirements; in-flight emergency response; etc. The primary focus in OWS-7 is on ground usage of the information, although provision of information packages to the crew, on the ground and in the air, is also of interest.
To support the above goal, the OWS-7 Aviation Thread will cover the following tasks:
- Evaluation and advancement of AIXM, in the areas of using and testing new AIXM 5.1 features, developing components/tools for generating, validating, converting, and parsing AIXM, addressing feature metadata requirements and performance constraints, and supporting the portrayal of AIXM information.
- Evaluation and advancement of WXXM, focusing on the incorporation and demonstration new weather concepts such as the 4-D Weather Data Cube, including the impact of such concepts on the Event Notification Architecture, the support for probabilistic events, and the definition and usage of the time model in WXXM.
- Advancement of the Event Notification Architecture developed and exercised in OWS-6 to support multiple sources of events and multiple types of events and data changes (AIXM, WXXM), and to investigate different delivery protocols (push/pull), registration and subscription lifecycle management approaches, and domain/schema-specific matching between events and subscriptions.
- Integration of AIXM/WXXM in the FAA SWIM environment, focusing on investigating approaches for leveraging SWIM Interface Management, Messaging and Security capabilities, as well as enabling Aviation clients to access SWIM services in addition to OGC services.
For those who have done this before: Please do not reuse old templates, but use our new ones. Thanks!
Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 7 (OWS-7) RFQ (pdf zip format)
Complete OGC Web Services, Phase 7 (OWS-7) RFQ (doc zip format)
OR INDIVIDUAL FILES
OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (doc)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (doc)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (doc)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (doc)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (pdf)
OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (doc)
OGC Web Services, Phase 7 (OWS-7) RFQ Template - Funding (xls)
OGC Web Services, Phase 7 (OWS-7) RFQ Template - Proposal (doc)
Download the final clarifications from the bidder's conference.
We will accept further questions through Thursday, 19-November, which I will post by Friday, 20-November. Then proposals are due by 1-December at 5pm US Eastern.
The Bidder's Conference was held on 10 November 2009. Further questions may be directed by email to techdesk [at] opengeospatial [dot] org until Nov 19.
The above Clarification document has been updated to reflect the questions presented during the Bidder's Conference.