OGC Open Routing API Pilot 2019: Call for Participation (CFP)

Significant progress towards more Web-oriented interfaces has been made in OGC with the emerging APIs WFS 3.0 and WPS 3.0, both using OpenAPI. These successes shall now be applied to the challenge of routing. The pilot will develop an API that allows a WPS or a mobile application to calculate and serve routes based on a user defined set of conditions. Routes will be exchanged according to a well-defined route model. These two elements together will create an abstraction layer on top of routing data sources. Considering online and offline situations, it is expected that this initiative promotes interoperability among route consumers, route calculation engines, and corresponding services.

This Initiative is being conducted under the OGC Innovation Program. The OGC Innovation Program provides a collaborative agile process for solving geospatial challenges. Organizations (sponsors and technology implementers) come together to solve problems, produce prototypes, develop demonstrations, provide best practices, and advance the future of standards. Since 1999 more than 100 initiatives have been taking place.

This Initiative provides a unique opportunity to influence the Routing API definition and by this shape future product landscape. It allows to create new business opportunities while the provided cost sharing boosts your R&D budget. The pilot has the potential for academic recognition and by meeting our sponsors, you gain insight into client needs and market shifts.

The outcomes are expected to shape the future of geospatial software development and data publication. The sponsorship supports this vision with cost-sharing funds to partially offset the costs associated with development, engineering, and demonstration of these outcomes. This offers selected Participants a unique opportunity to recoup a portion of their Initiative expenses.

This initiative will be conducted under the following OGC Policies and Procedures:

The roles generally played in any OGC Innovation Program initiative include Sponsors, Bidders, Participants, Observers, and the Innovation Program Team ("IP Team"). Explanations of the roles are provided in Annex: Tips for New Bidders.

The IP Team for this Initiative will include an Initiative Director and an Initiative Architect. Unless otherwise stated, the Initiative Director will serve as the primary point of contact (POC) for the OGC.

The Initiative Architect will work with Participants and Sponsors to ensure that Initiative activities and deliverables are properly assigned and performed. They are responsible for scope and schedule control, and will provide timely escalation to the Initiative Director regarding any severe issues or risks that happen to arise.

All activities in this pilot will result in a Deliverable. These Deliverables can take the form of Documents or Implementations.

Proposals are expected to be short and precisely addressing the work items a bidder is interested in. A proposal template will be made available. The proposal, including technical and financial details, has a page limit as defined in Appendix A. Details on the proposal submission process are provided in Appendix A: Proposal Submission Guidelines. The proposal evaluation process and criteria are described below.

Initiative participant business/contract representatives are required (per the terms in the Participation Agreement contract) to report the progress and status of the participant’s work. Detailed requirements for this reporting will be provided during contract negotiation. Initiative accounting requirements (e.g., invoicing) will also be described in the contract.

The IP Team will provide monthly progress reports to Sponsors. Ad hoc notifications may also occasionally be provided for urgent matters. To support this reporting, each Pilot participant must submit (1) a Monthly Technical Progress Report and (2) a Monthly Business Progress Report by the first working day on or after the 10th of each month. Templates for both of these report types will be provided and must be followed.

The purpose of the Monthly Business Progress Report is to provide initiative management with a quick indicator of project health from the perspective of each Pilot participant. The IP Team will review action item status on a weekly basis with the Initiative participants assigned to complete those actions. Initiative participants must be available for these contacts to be made.

Call for Participation

The CFP consists of stakeholder role descriptions, proposal submission instructions and evaluation criteria, a master schedule and other project management artifacts, Sponsor requirements, and a initiative architecture. The responses should include the proposing organization’s technical solution, its cost-sharing requests for funding, and its proposed in-kind contributions to the initiative.

Once the original CFP has been published, ongoing authoritative updates and answers to questions can be tracked by monitoring the CFP Corrigenda Table and the CFP Clarifications Table.

Participant Selection and Agreements:

Bidders may submit questions via timely submission of email(s) to the OGC Technology Desk. Question submitters will remain anonymous, and answers will be regularly compiled and published in the CFP Clarifications page.

OGC may also choose to conduct a Bidder’s question-and-answer webinar to review the clarifications and invite follow-on questions.

Following the closing date for submission of proposals, OGC will evaluate received proposals, review recommendations with the Sponsor, and negotiate Participation Agreement (PA) contracts, including statements of work (SOWs), with selected Bidders. Participant selection will be complete once PA contracts have been signed with all Participants.

Kick-off: The Kickoff is a virtual meeting (using GoToMeeting) where Participants, guided by the Initiative Architect, will refine the Initiative architecture and settle upon specific use cases and interface models to be used as a baseline for prototype component interoperability. Participants will be required to attend the Kickoff, including breakout sessions, and will be expected to use these breakouts to collaborate with other Participants and confirm intended Component Interface Designs.

Regular Teleconference and Interim Meetings After the Kickoff, participants will meet on a frequent basis remotely via web meetings and teleconferences.

Development of Engineering Reports, Change Requests, and Other Document Deliverables: Development of Engineering Reports (ERs), Change Requests (CRs) and other document deliverables will commence during or immediately after Kickoff.

Under the Participation Agreement (PA) contracts to be formed with selected Bidders, ALL Participants will be responsible for contributing content to the ERs. But the ER Editor role will assume the duty of being the primary ER author.

Final Summary Reports, Demonstration Event and Other Stakeholder Meetings: Participant Final Summary Reports will constitute the close of funded activity. Further development work might take place to prepare and refine assets to be shown at the Demonstration Event and other stakeholder meetings.

Assurance of Service Availability: Participants selected to implement service components must maintain availability for a period of no less than six months after the Participant Final Summary Reports milestone. OGC might be willing to entertain exceptions to this requirement on a case-by-case basis.

The following requirements apply to the proposal development process and activities.

The two documents that shall be submitted, with their respective templates are as follows: 1. Technical Proposal: https://portal.opengeospatial.org/files/?artifact_id=82493 2. Cost Proposal: https://portal.opengeospatial.org/files/?artifact_id=82494

A Technical Proposal should be based on the Response Template and must include the following:

The Cost Proposal should be based on the two worksheets contained in the Cost Proposal Template and must include the following:

Additional instructions are contained in the templates themselves.

Guidelines:

Once the original CFP has been published, ongoing authoritative updates and answers to questions can be tracked by monitoring this CFP.

Bidders may submit questions via timely submission of email(s) to the OGC Technology Desk. Question submitters will remain anonymous, and answers will be regularly compiled and published in the CFP clarifications table.

OGC may also choose to conduct a Bidder’s question-and-answer webinar to review the clarifications and invite follow-on questions.

Update to this CFP including questions and clarifications will be posted to the original URL of this CFP.

The goal of the pilot is to create an Open Routing API and a Route Exchange Model. The pilot will assess an abstract baseline suite of functions, capabilities, and encodings to address a common standard interface for network routing functionality. This includes guidance for extending the Routing API to account for various routing data models and support for network routing engine configuration via the Routing API.

The pilot shall apply multiple routing engines to multiple data schemas, and allow the dynamic adaptation of routes based on alternative inputs, route characteristics, and constraints. Featuring multiple clients, the pilot shall identify and describe optimal routing processes and workflows within standards-based infrastructures. The implementation scenarios include both online and offline situations. In online scenarios, the clients interact with WPS instances that calculate routes, whereas in offline scenarios, apps on mobile devices interact with GeoPackages stored on the mobile device. Both types include sharing of routes. Routes shall be visualized in clients, but focus is not on portrayal as such!