OGC Testbed 10

Request for Quotations (RFQ)

and

Call for Participation (CFP)

for

OGC Testbed 10

Annex A - WBS and Work Items

RFQ Issuance Date: 15 July 2013

Proposal Due Date: 26 August 2013

Copyright © 2013 Open Geospatial Consortium
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/

 

1Introduction

This Annex A document describes the Work Breakdown Structure (WBS) and the work items for the OGC Testbed 10 Web Services Initiative – Phase 10 (OGC Testbed 10) Initiative. The Work Items are segregated into three threads. Each thread classifies work items as funded or unfunded items, depending on current sponsorships.

2Sponsor Priorities

The following tables show the OGC Testbed 10 deliverables in each of the threads. Work items that are designated with an “F” are work items that are currently funded. Those that have a “U” are within scope of this RFQ but may not be funded.

All Participants are required to provide in-kind contributions. Some participants will be fully in-kind. Participants are encouraged to propose to provide part or all of a deliverable as in-kind. Any item proposed as a fully in-kind contribution that meets the requirements and architecture for OGC Testbed 10 will be accepted. In-kind contributions are used as a criterion for evaluating proposals seeking cost-share funding.

2.1CCI Deliverables Funding

Table 1 – CCI Thread Deliverables Summary

Deliverables

Funded /
Unfunded

1. Profile Interoperability Engineering Report

F

2. CCI Change Requests – to OGC standards (as needed)

F

3. Virtual Global Gazetteer Client

F

4. Virtual Global Gazetteer Service

F

5. NGA WFS-G

F

6. USGS WFS-G

F

7. Local WFS

F

8. WFS for VGI

F

9. Virtual Global Gazetteer Engineering Report

F

10. CCI OGC Web Services

F

11. Provenance Engineering Report

F

12. CCI OGC Client Applications

F

13. CCI WPS 2.0 Conflation Service

F

14. VGI Component

F

15. Semantic Mediation Service

F

16. Ontology Engineering Report

F

17. OGC Testbed 10 Ontology Mapping Component

F

18. VGI Engineering Report

F

19. Hydro Engineering Report

F

20. Hydro Mediation Service

F

21. Hydro Web Services

F

22. WPS Profiles Engineering Report (Added Aug 15, 2013)

F

2.2Open Mobility Deliverables Funding

Table 2 – Open Mobility Thread Deliverables Summary

Deliverables

Funded /
Unfunded

1. OWS Context JSON Interoperability Engineering Report

F

2. OWS Context Change Requests

F

3. OWS Context in NIEM Engineering Report

U

4. NIEM / OWS Context Client

U

5. Performance Enhancement through Cloud Computing Engineering Report

F

6. Cloud infrastructure for services

U

7. Cloud services

U

8. GeoPackaging Engineering Report

F

9. GeoPackaging Service Reference Implementation Service

F

10. Mobile GeoPackage and OWS Context Client

F

11. GeoPackage Change Requests

F

12. Mobile Device Security Engineering Report

U

13. Mobile App Policy Enforcement Point and Policy Decision Point

U

14. Integrated Client Enhancements Study Engineering Report

U

2.3Aviation Deliverables Funding

Table 3 – Aviation Thread Deliverables Summary

Deliverables

Funded /
Unfunded

1. Aviation Architecture Engineering Report

F

2. Aviation Recommendations for the Exchange of Terrain Data Engineering Report

F

3. Aviation Binding AIXM to Development Tools Engineering Report

F

4. Aviation Human Factor Based Portrayal of Digital NOTAMs Engineering Report

F

5. Aviation Dissemination of Weather Data Engineering Report

F

6. GML for Aviation Compliance Test Suite + GML for Aviation Conformance Testing Engineering Report

F

7. WFS Temporality Extension Discussion Paper Revision

F

8. Change Requests (as needed)

F

9. Web Feature Service WFS-T

F

10. Event Service

F

11. CSW ebRIM Registry

U

12. Aviation Client

F

3Interoperability Initiative Process Framework

This section describes a flexible framework of standards, repeatable processes, which can be combined and adapted as necessary to address the requirements of each Interoperability Initiative. These tasks are executed with a Virtual Team Infrastructure. This Process Framework forms the basis for the OGC Testbed 10 Initiative Work Breakdown Structure. Figure 1 shows Interoperability Initiative Process Framework.

Figure 1: Interoperability Initiative Process Framework.

3.1Tasks

3.1.1Coordination

This task enables overall coordination among assigned OGC Staff, OGC Interoperability Program (IP) Team, Sponsors, selected organizations, and other TC/PC Members as needed to perform the following Subtasks:

Collaborative Environment

OGC IP Team provides synchronous and asynchronous collaboration environments for cross-organization, globally distributed, virtual teams working interdependently to execute Initiative Orders.

Initiative Plan Development

SDevelopment of Project Plans, Project Schedules and Work Breakdown Structures. Input may include technical and project management approach, tasks/schedules, communications plan, resource plans, risk and mitigation strategies, and definition of the standards, component development and integration tasks necessary to realize the architecture.

Management

Services such as requirement, cost, schedule and performance monitoring and status reporting. The goal is to ensure that assigned project tasks are performed within budget, the work is progressing according to the agreed schedule, and any changes to requirements or personnel are managed to reduce the risk of cost overrun or schedule delay.

Communication

Includes communicating status and issues of concern for ongoing Project related activities and planned Initiative to OGC and other organizations e.g. ISO.

3.1.2Assessment and Analysis

Implemented during Planning Studies, this task requires assessment/evaluation and analysis of issues and documentation of an organization’s or domains existing capabilities, and assessment of requirements for OGC compliant technology.

3.1.3Concept Development

This task conducts a Feasibility Study that assesses emerging technologies and architectures capable of supporting eventual Interoperability Initiatives (e.g. Testbed). Part of the concept development process is the use of a Request for Technology (RFT) to gain a better understanding of the current state of a potential technology thrust and the architecture(s) used in support of that technology. The feasibility study examines alternative prototype mechanisms that enable commercial web-services technology to interoperate. The study may also assess the costs and benefits of the architectural approaches, technologies, and candidate components to be utilized in a testbed and potential demonstration. This task also collates Sponsor requirements and assesses the applicability of current specifications.

3.1.4Architecture Development

This task defines the architectural views for any given Initiative. In the context of the OGC Interoperability Program, there are three–and perhaps more - architectural views for any given effort. These views are the Enterprise View, Information View and Computational View (based on RM-ODP, ISO 10746).

3.1.5Initiative Preparation

This task defines the participant budget (if any), develops and executes agreements and contracts that outline roles and responsibilities of each participant. This task may refine the Work Package.

3.1.6Specification Development

This task defines and develops models, schemas, encodings, and interfaces necessary to realize required Architectures. This task may include activities to coordinate ongoing Initiatives with Specification Program activities.

3.1.7Component Development

This task develops prototype interoperable commercial software components based on draft candidate implementation specifications or adopted specifications necessary to realize the required Architecture.

3.1.8Testing and Integration

This task integrates, documents and tests functioning interoperable components and infrastructures that execute operational elements, assigned tasks, and information flows required to fulfill a set of user requirements. It includes Technology Integration Experiments (TIEs).

3.1.9Solution Transfer

This task prepares prototypical interoperable components so that they can be assembled at required sites.

3.1.10Demonstration

This task defines, develops and deploys functioning interoperable components and infrastructures that execute operational elements, assigned tasks, and information flows required to fulfill a set of user requirements.

3.1.11Documentation

This Task ensures development and maintenance of the pre-specification, pre-conformant interoperable OpenGIS technologies (including draft and final Engineering Reports) and the systems level documentation (example user documentation, etc.) necessary to execute the Initiative. This task may include coordination with OGC Specification Program activities.

3.1.12Compliance Testing

This Task ensures development of draft compliance test guidelines (at a minimum) and test suites for engineering specifications detailed in Engineering Reports. This task includes coordination with the OGC Compliance Program.

4OGC Testbed 10 Work Breakdown Structure (WBS)

The following Work Breakdown Structure (WBS) is derived from the OGC Interoperability Initiative Process Framework. This WBS should be interpreted in the following manner:

A proposing organization does not have to respond to all tasks below. However bold italic text in the task explanation indicates which tasks are mandatory or conditional. Conditional tasks are those that are mandatory if a selected organization takes on certain non-mandatory tasks.

5Coordination

5.1Collaborative Environment

The following tasks are mandatory for selected organizations.

5.1.1Routine and ad hoc teleconferences as assigned

The selected organization shall provide a technical representative and an alternate to participate in regularly scheduled teleconferences or an ad hoc teleconference/webinar.

5.1.2E-mail review and comment

Selected organization shall provide technical representatives to participate in specification and prototypical component development discussions via the OGC Testbed 10 mail lists.

5.1.3Action Item status reporting

Selected organizations shall report the status of their work to the relevant work group leader in response to any action item accepted by them in whole or part.

5.2Initiative Plan Development

5.2.1Project Plan Development

5.2.2Project Schedule Development

5.2.3WBS Development

5.2.4Concept of Operations Development

5.3Management

The following tasks are mandatory for selected organizations.

5.3.1Status Reporting

Business/contract representatives for selected organizations shall report the progress and status of their work as assigned to and accepted by them in their SOW following a template provided after SOW signing.

A one-time Kickoff status report shall be provided that includes a list of personnel assigned to support the OGC Testbed 10 initiative. The kickoff status report shall be submitted the OGC Testbed 10 Initiative Manager no later than the last day of the OGC Testbed 10 kickoff in soft copy format only.

Weekly or biweekly thread-level teleconferences will be conducted and recorded in minutes posted on the portal, beginning after the Kickoff. These are for verbal updates and additions of tasks and actions listed on the portal, and to respond to requests for status by the IP Team and Sponsors.

Formal status reports will be submitted on a Monthly basis on the portal for compilation to an overall thread and initiative status. These reports will be due by the tenth of the month or the first Monday thereafter. Two kinds of status reports are required (report templates will be provided):

Monthly Technical Report: Word document posted on portal, and the Thread Architect notified

Monthly Business Report: Word document posted on portal, then the IP Executive Director, Initiative Manager, and OGC Business Manager notified

5.3.2Initiative Accounting

Cost-share compensation to selected organizations is typically invoiced and paid in three bi-monthly installments. The dates of these installments for OGC Testbed 10 will be identified in the Participant Agreement.

Business/contract representatives for selected organizations shall submit an invoice to the OGC Business Office at OGC Headquarters. The invoice shall include the OGC Accounting Job Code provided in the contract, the work completed during the prior period, and itemized list of Deliverables. The invoice shall include the budgetary not to exceed amount.

5.4Communication

5.4.1OGC Internal IP Status Briefings

5.4.2OGC External IP Status Briefings

6Assessments and Analysis

6.1Organizational Capability Review

6.2Organizational OGC Requirements Review

7Concept Development

7.1Sponsor Feasibility Study Review

7.2RFT Development

7.3RFT Response Analysis

7.4RFT Response Review

8Architecture Development

8.1Enterprise View Development

8.2Information View Development

8.3Computational View Development

9Initiative Preparation

9.1Sponsor Planning TEMs

9.2RFQ Development

9.3Participant Budget Development

9.4Contract Development

9.5SOW/SOP Development

10Specification Development

All selected organizations shall send technical representatives to the OGC Testbed 10 Kickoff meeting. Technical representatives of selected organizations shall lead Specification Development effort for each or applicable tasks listed below.

10.1Model Development

Representing a service, interface, operation, message, or encoding that is being developed for the OGC Testbed 10 initiative.

10.2Schema Development

Specifying an interface that is being developed for the OGC Testbed 10 initiative.

10.3Encoding Development

Specifying an interface that is being developed for the OGC Testbed 10 initiative.

10.4Interface Development

Specifying operations, encodings or messages that are being developed for the OGC Testbed initiative.

10.5Specification Program Coordination

Submitting Engineering Reports (ERs) and Change Requests (CRs) developed in OGC Testbed 10 to the OGC Technical Committee for review; and presenting Reports to relevant OGC TC groups and working with members to resolve issues that the members may raise with regard to the ER.

11Component Development

Technical representatives of selected organizations shall lead Component Development effort for each or applicable tasks listed below.

11.1Prototypical Interoperable Software Development

11.1.1Server software development

Selected organizations shall develop server software or modify existing product server software to exercise the interfaces developed under the Specification Development tasks in item 6 above. The selected organizations will make this server software available for sponsor review and input during the initial period of the OGC Testbed 10 initiative.

11.1.2Client software development

Selected organizations shall develop client software or modify existing product client software to exercise the servers developed under the Component Development tasks of OGC Testbed 10. Selected organizations shall develop client software to support their server software or make arrangements with other participants to use their client software to exercise their server during the course of the initiative. This is subject to approval by the sponsors and IP Team to ensure that the third party client is appropriate for exercising the functionality of the relevant server. If the proposing organization is developing server software and client software, then the client software shall exercise other OGC Testbed 10 or OGC services provided by their server.

11.2Special Adaptation Development

Selected organizations shall adapt client or server software to exercise relevant mainstream IT technology and standards such as PKI and e-commerce technologies.

12Testing and Integration

12.1Configuration Management

12.1.1CM Plan Development

Selected organizations shall provide a representative to develop a configuration management plan for interfaces and components developed during the OGC Testbed 10 initiative.

12.1.2Initiative CM

Selected organizations shall provide a representative to exercise the configuration management plan for interfaces and components developed during the OGC Testbed 10 initiative.

12.2Infrastructure Setup

12.2.1Operating Systems

12.2.2Networks

12.2.3Web Server

12.2.4Database Server

12.2.5Web Browsers

12.2.6SW Installation & Integration

12.2.7Data Loading

12.3Technology Integration Experiments

12.3.1Iterations 1-N

12.3.1.1Component Interface Test

Selected organizations shall provide a technical representative to conduct formal Technology Integration experiments that exercise server and/or client component software’s ability to properly implement the interfaces, operations, encodings, and messages developed during OGC Testbed 10. There will be multiple TIEs during the course of OGC Testbed 10 that will exercise various interfaces, operations, encodings, and messages developed during OGC Testbed 10. There may also be multiple iterations of a particular TIE or set thereof. This item is mandatory for all organizations proposing to deploy server interfaces for OGC Testbed 10.

12.3.1.2Test Result Analysis

Selected organizations shall provide a technical representative to report the outcome and relevant software reporting messages from TIEs in which the proposing organization participates. These TIE results shall be submitted to the OGC Testbed 10 email lists and within Monthly Status Report to be courtesy copied to the initiative architect. This item is mandatory for all organizations proposing to develop deploy server interfaces for OGC Testbed 10.

12.4System Tests

12.4.1Functional Test

12.4.2Interface Test

12.4.3 Performance Test

13Solution Transfer

13.1Software Installation

Selected organizations shall provide a licensed copy of OGC Testbed 10 relevant software components for integration onto the OGC Network. This could be accomplished by making the software component(s) available from an open site on their network OR by installing it on a sponsor or other host machine on the OGC Network. If the latter option is taken, then the selected organization shall provide a technical representative to support the installation of the software component(s). This is mandatory for all organizations proposing to develop software components for OGC Testbed 10.

13.2Software Integration

13.3Data Loading

Selected organizations shall provide a technical representative to load data to any server components the proposing organization may develop. This item is mandatory for all organizations proposing to develop server components for OGC Testbed 10.

14Demonstration

14.1Use Case Development

Selected organizations shall provide a technical representative to develop or support the development of use cases that define and explain the utility of the interfaces developed during OGC Testbed 10. These use cases shall be used to provide a basis for demonstration storyboards and the demonstration itself.

14.2Storyboard Development

Selected organizations shall provide a technical or business representative to develop or support the development of the demonstration storyboards that will define the structure and content of the demonstration.

14.3Venue Access

14.4Data Requirements Assessment

14.5Data Acquisition and Distribution

14.6Demonstration Preparation and Delivery

Selected organizations shall provide a technical and/or business representative to develop or support the development of demonstration that will exercise the functionality of the interfaces developed during
OGC Testbed 10. The representative(s) will also support the demonstration event(s) as required. Selected organizations will maintain server and client software for a period of no less than one year after the completion of the OGC Testbed 10 demonstration. This item is mandatory for all organizations proposing to develop software components for OGC Testbed 10.

15Documentation

15.1ER Development

Selected organizations shall provide a technical representative to serve as editor of, reviewer of or contributor to a relevant Engineering Report (ER) (or subsection of an Engineering report). Participants shall use the appropriate Document template posted on the OGC portal when preparing reports for submittal as part of this testbed initiative:

In some cases, the documentation required is a Change Request to an existing OGC standard. All Change Requests are to be entered into the public, online CR system, found here: http://www.opengeospatial.org/standards/cr

15.2System Documentation Development

15.2.1Functional Specification

15.2.1.1Architectural Overview

Selected organizations shall provide a technical representative to develop an architectural overview of their software component(s) relevant to the OGC Testbed 10 architecture.This item is mandatory for all organizations proposing to deploy server interfaces for OGC Testbed 10.

15.2.1.2Use Cases

Selected organizations shall provide a technical representative to develop use cases to show the functionality of their software components in the context of the OGC Testbed 10 architecture.This item is mandatory for all organizations proposing to deploy server interfaces for OGC Testbed 10.

15.2.1.3UML System Models

Selected organizations shall provide a technical representative to develop valid UML documents describing information models and architectures involved in their contribution to OGC Testbed 10.This item is mandatory for all organizations proposing to develop schema automation components for OGC Testbed 10 to be installed at sponsor or other host sites connected to the OGC Network.

15.2.1.4System Configuration

Selected organizations shall provide a technical representative to develop a detailed document describing the combined environment of hardware and software component(s) that compose their contribution to OGC Testbed 10.This item is mandatory for all organizations proposing to develop software components for OGC Testbed 10 to be installed at sponsor or other host sites connected to the OGC Network.

15.2.2Installation Guide

Selected organizations shall provide a technical representative to develop an installation guide for their software component(s).This item is mandatory for all organizations proposing to develop software components for OGC Testbed 10 to be installed at sponsor or other host sites connected to the OGC Network.

15.2.3Training Material & Users Guide

Selected organizations shall provide a technical representative to develop a User’s Guide and Training Materials pertaining to their software component(s) developed or modified for OGC Testbed 10. The documents shall be provided to sponsors and IP Team to support their ability to demonstrate the proposing organization’s contributions to the OGC Testbed 10 initiative.This item is mandatory for all organizations proposing to develop software components for OGC Testbed 10.

15.3Planning Study Report

16Compliance Test Development

Technical representatives of selected organizations shall develop draft compliance test documentation pertaining to an interface developed or enhanced for OGC Testbed 10. For candidate specifications, this test documentation shall, at a minimum, consist of test guidelines that would form the basis for development of more detailed and complete test scripts as the specification matures toward an approved specification. For mature candidate specifications, that are believed to be ready for vote to become approved specifications, participants shall evolve existing or prepare test scripts to form a complete set of tests to fully test an implementation of a specification for compliance with its requirements. Compliance test documentation shall be included in an Engineering Report. This task includes coordination with OGC Compliance Program. Proposals shall address this task along with Task 10, Specification Development and Task 15, Documentation in this Annex.

16.1Summarize TIEs, demo results and data issues

Technical representatives of selected organizations shall include information detailing progress pertaining to the implementation of the interface by including TIE results, lessons-learned from the demo, and particular data issues.

16.2Compliance Test

Technical representatives of selected organizations shall outline all of the necessary information to conduct a valid compliance test of the interface, including the sub items below.

16.2.1Test Cases

Technical representatives of selected organizations shall outline a valid compliance test for the interface. A valid compliance test will include identification of all required and optional server requests in the interface, the acceptable results for testing servers, the syntax checks to perform for testing client requests; an explanation of an acceptable verification of the results (machine, human, etc); a list of expected/valid warnings or exceptions to interface behavior; a matrix of test dependencies and explanation of ordering tests appropriately for inherent tests and dependencies.

16.2.2Data

Technical representatives of selected organizations shall identify appropriate data sets for use in conducting a compliance test for an interface.

16.2.3Recommendations

Technical representatives of selected organizations shall document recommendations to resolve issues with the current state of the interface, or with the compliance tests.