OSPD base image



OGC Open Science Persistent Demonstrator (OSPD) Initiative: Call for Participation (CFP)

1. Introduction

The Open Geospatial Consortium (OGC) calls for bids to participate in the OGC Open Science Persistent Demonstrator (OSPD) Initiative. This Initiative is planned to run in three phases over several years, with the first phase to commence in early 2024.

Collaborative Open Science is essential to addressing complex challenges whose solutions prioritize integrity and require cross-domain integrations. Today, building workflows, processes, and data flows across domains and sectors remains technically difficult and practically resource intensive, creating barriers to whole-systems change. While organizations increasingly aim to demonstrate accountability, they often lack the tools to take action effectively. By making it simple to connect data and platforms together in transparent, reusable and reproducible workflows, the OGC OSPD aims to enable responsible innovation through collaborative open science. The OSPD focuses specifically on using geospatial and earth observation (EO) data to enable and demonstrate solutions that create capacity for novel research and accelerate the practical implementation of this research.

We encourage anyone interested in developing and demonstrating workflows based on Open Science and FAIR principles and leveraging existing geospatial platforms and data to bid to participate. Different ways to participate are described below.

2. Objectives

The OGC OSPD Initiative aims to explore practical mechanisms for implementing the principles of reusability, portability, and transparency in support of FAIR and Open Science and responsible innovation.

To do so, the OSPD Initiative’s objective is to produce four main elements in its first phase (OSPD24):

  1. A web application that enables collaborative research and data representation, focused on geospatial, earth observation, and complementary data, e.g. a web application that demonstrates how to model a workflow that connects platforms operated by different organizations to build FAIR and Open research, analysis, and data representation applications.

  2. A test environment for web platforms to explore mutual use, e.g. a collaboration space for existing and in-development platforms to access each other’s capabilities and test the reproduction of a workflow across multiple systems.

  3. Learning and outreach materials that make the Open Science platforms known and accessible to a wide range of users and enable efficient use.

  4. Advanced visualization environments to convey the outcomes of workflows across OSPD platforms.

These elements will be extended and refined in future OSPD phases through the incorporation of new use cases, further engagement with user communities and stakeholders, and iterative testing and revision.

The aim is not to develop another analytical or research platform, but to improve the experience of users of multiple platforms, leverage the power of existing platforms, provide training on workflows across multiple platforms, and experiment with advanced visualization across whole workflows, as depicted in Figure 1.

As in other OGC initiatives, this work will take the OGC Baseline (existing and emerging OGC standards and best practices) into account and explore specific topics with broad teams from industry, government, and academia to advance Findable, Accessible, Interoperable, and Reusable (FAIR) principles and OGC’s open standards capabilities. In addition to its technical outputs, the OSPD Initiative will develop reports which capture lessons learned and recommendations that emerge from the process.

OSPD architecture diagram
Figure 1. Open Science Persistent Demonstrator Technical Architecture Overview



2.1. Benefits to the stakeholder community

The outcomes of the OSPD initiative will benefit not only its sponsors and direct Participants, but the broader stakeholder community through:

  • The creation of a long-term framework in which new platforms, platform advancements, and prototypes can be tested prior to adoption by organizations.

  • Enabling users to explore multiple connected open science platforms in action.

  • Providing an integrated educational program, which will support users to learn to modify existing workflows and integrate their own data.

  • Building a network of federated services, which each receive support from the others

  • Connecting scientists and decision makers and encouraging cross-discipline interactions.

  • Linking research with platforms providing innovative visualization capabilities.

  • Leveraging connections to other relevant OGC initiatives.

2.2. Important Features

This Initiative is currently a strategic initiative between ESA and NASA and sponsored by them. It incorporates requirements and ideas from these sponsors, including facilitating the use of their data, services, and systems, together with platforms and data from the wider ecosystem. We welcome and encourage further organizations to become sponsors of this initiative to fund and drive requirements as the architecture matures, as well as to engage as participants through this Call for Participation.

As the architecture develops and sponsors provide more advanced requirements, and as providers and users submit new requirements and requests, the focus and priorities of the OSPD will adapt to reflect these changes. In collating input from stakeholders, OGC’s consortium of experts will ensure that OGC remains a neutral forum to solve issues leveraging the power of geospatial, and delivering open and consensus-based solutions that move at the rapid pace of innovation.

2.3. Benefits to participants

This initiative provides an outstanding opportunity for Participants to connect with stakeholders across the ecosystem, engage with the latest research on geospatial system design, concept development, and rapid prototyping with government organizations (Sponsors) across the globe. The initiative provides a business opportunity for participants to mutually define, refine, and evolve service interfaces and protocols in the context of hands-on experience and feedback. The outcomes are expected to provide a “lab” type system to test capabilities prior to operational adoption and shape the future of geospatial software development and data publications. The Sponsors are supporting 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. OGC COSI Program Participants benefit from:

  • Access to funded research & development

  • Reduced development costs, risks, and lead-time of new products or solutions

  • Close relationships with potential customers

  • First-to-market competitive advantage on the latest geospatial innovations

  • Influence on the development of global solutions and standards

  • Partnership opportunities within our community of experts

  • Broader market reach via the recognition that OGC standards bring.

3. Master Schedule

The following table details the major Initiative milestones and events for the first year of the Open Science Persistent Demonstrator initiative. It is anticipated this will be a multi-year project. Dates are subject to change.

Table 1. Master Schedule
Milestones Project Month Description

M01

July 2023

Development and Release of a Request for Information (RFI) and requirements for the Open Science Persistent Demonstrator (OSPD)

M02

July 2023

Responders Q&A; online answers as questions are submitted

M03

17 September 2023

RFI responses due and review; Development of CFP for OSPD Implementation

M04

18 October 2023

CFP Release for Open Science Persistent Demonstrator Implementation

M05a

10 November 2023

Deadline for submission of questions for the Bidders Webinar

M05b

15 November 2023, 12:30PM Eastern

Bidders Q&A Webinar

M06

1 December 2023

Deadline for proposal submissions

M07

December 2023

Proposals review, participants selection, and contracting

M08

9-11 January 2024

Kick-off meeting

M09

January - September 2024

OSPD Implementation phase

M10

15 March 2024

Use Cases Due and Initial Engineering Reports (IERs)

M11

September 2024

Open Science Persistent Demonstrator ER and presentations

The schedule shown below provides an overview of the planned OGC Innovation Program initiatives involving Design Experiments (DE), Pilots (P), and Engineering Services (ES) with the full envisioned project lifetime of 36 months.

ospd timeline
Figure 2. Overview of the OSPD initiative stages across three planned years of activity.



Activity during the OSPD Pilot will be organized in work items (detailed below) supported by the OSPD Sponsor and Participant teams, underpinned by project coordination and community engagement work by the OGC team.

In the first phase, the OSPD will focus on engaging with platform and resource providers, developers, and training material creators to establish core platform and application functionality. The initial design of the platform will be informed by prior work with the stakeholder community carried out by the sponsors, participating organizations, and the OGC. Limited engagement with the stakeholder community to inform the design of the results representations (visualizations) is anticipated in the first phase. In future phases, more intensive engagement with user communities, use case providers, and a broad range of stakeholders, across research institutions, the public sector, industry, and communities, is planned.

4. Participation

4.1. Who can participate

The OGC welcomes proposals to participate in its Initiatives from organizations and individuals active in the development, management, and use of geospatial data, technologies and systems. Proposers may be active in industry, government (national, regional, local), research, non-profit, community, or other sectors. Past participants have included providers of services and platforms, modelers, end users of platforms and data, researchers, and other stakeholders in relevant domains.

You do not need to be a member of the Open Geospatial Consortium to propose to participate. If your organization’s proposal is selected, you or your organization must become an OGC member if not already one. This is to ensure all participants have equal access to the tools and documentation developed and shared throughout the project phase.

4.2. How to participate

The OSPD is designed to enable interested organizations to participate in a range of ways, from simply engaging in the co-design process without committing any resources other than the participant’s time, to providing funding, in-kind or paid services, or providing a resource such as a dataset or access to infrastructure. Key mechanisms for engagement include:

  • Provide technical expertise Commit staff time to the Pilot to regularly join meetings, develop data and software components, test and evaluate implementations, or produce documentation. Contribute your organization or community’s perspective on how tools should be designed and what would meet your needs as a user by actively participating in workshops and co-design exercises. Add your perspective as a technical or domain expert by providing feedback on the design and implementation of the architecture.

  • Provide a use case Share a real world case study which can be used to inform the development of the OSPD architecture and demonstrate how it can be used to create more FAIR processes and workflows, leading to better outcomes for users. Sample use cases may be provided when you make your proposal with the expectation that these would be refined in consultation with other OSPD Pilot team members.

  • Provide data or tools Make an contribution of existing data, platforms, research or other resources (e.g. models, digital infrastructure components) to support the Pilot.

5. Technical Objectives

This section identifies the technical objectives of the first phase of the OSPD Initiative and the corresponding activities and deliverables participants make a proposal (bid) to undertake in order to help achieve the Initiative’s aims. These activities and deliverables constitute the major part of each participant’s contribution to the OSPD Initiative, together with their contribution to Engineering Report(s) and other materials capturing the process.

5.1. Problem Statement and Research Questions

Collaborative Open Science and FAIR data are widely recognized as critical tools for taking advantage of the opportunities created through addressing complex social and environmental challenges. To date, many millions have been invested in hundreds of initiatives to enable access to analytical tools, provide data management, data integration and exchange, translate research results, and support reproduction and testing of workflows for new applications. These investments have resulted in a plethora of new data, protocols, tools and workflows, but these resources frequently remain siloed, difficult to use, and poorly understood, and as a result they are falling short of their full potential for wider impact and their long term value is limited.

The OSPD Initiative, through its design, development and testing activities, asks:

  1. How can we design Open Science workflows that enable integration across platforms designed for diverse applications used in different domains to increase their value?

    1. What technological tools, standards and protocols will support the implementation of these Open Science workflows in practice?

  2. How can we lower barriers for end users (decision makers, managers in industry, scientists, community groups) who need to create Open Science workflows, processes, and data flows across domains and sectors remains technically difficult and practically resource intensive, creating?

    1. What technologies and standardizations will lower barriers?

    2. What design elements, user interfaces, and data representations will ease use of existing platforms?

  3. How can Open Science workflows and platforms enable collaboration between stakeholders in different domains and sectors?

    1. What are the specific challenges posed by the need for collaborative development of Open Science workflows?

    2. What technological tools and practices can best support the collaborative work that enables Open Science?

  4. How can we empower organizations to demonstrate accountability in their analytical workflows, data, and representations of information through Open Science?

    1. What Open Science tools do organizations need to take action effectively?

    2. How can Open Science and FAIR data standards practically support accountability?

  5. How can we make it simple to connect data and platforms together in transparent, reusable and reproducible (FAIR) workflows?

    1. What training and user friendly guidance can we develop to simplify the use of existing systems in connected Open Science and FAIR workflows?

  6. What are the specific challenges of using geospatial, earth observation (EO), and complementary data in this context?

    1. Where are geospatial-specific standards and tools needed and where can we take advantage of convergence with work in other areas of data science?

ospd stakeholders
Figure 3. The OSPD brings together stakeholders and existing platforms, data and services and will connect them via Open Science and FAIR workflows.



5.2. Work Items and Deliverables

While each proposal should include information on planned contributions, it is anticipated that these proposals do not exceed 5 pages unless necessary to indicate participation in multiple sections. The following diagram outlines all activities (grey boxes), work items (colored boxes), and deliverables (Dxxx) in this initiative. Bidders may submit bids for individual work items or any combination of work items.

ospd deliverables
Figure 4. The OSPD deliverables and main work items



5.2.1. General requirements for all participants

The initiative will support a number of Open Science platforms (D100/101). The goal is to make each platform available to other platforms via standardized interfaces. Details of these interfaces will be defined by all participants collaboratively.

All the provided platforms will be available to the Persistent Demonstrator Application (D110), a web application that demonstrates cross platform interoperability and reproducibility in support of Open Science. It is expected that the Persistent Demonstrator Application will be made available via a Web browser and that its documentation will include the necessary details on how to interact with platforms connected to it and to demonstrate their usage through the Persistent Demonstrator Application. The goal is not to develop a complex application that replicates many of the features provided by the Open Science platforms themselves, but to provide an interface application that facilitates their combined use.

The participant responsible for D110 will agree with all platform providers on the best way to support the various platforms. The design of the Persistent Demonstrator Application (D110) will be informed by the development of initial use cases (D102). D102 will be led by one participant, who will coordinate the process of co-design of use cases with project participants and key stakeholders. All platform providers will make training material available which describe how to interact with their platform specifically. These materials will complement the general documentation on use of the Persistent Demonstrator Application, which will be developed by the provider of D110. All training materials will be aggregated by the Training Portal (D120). The format, content, and level of detail of the training material will be collectively defined by all participants, and informed by the co-design activities under D102.

Scientific workflows often produce results that require additional processing in order to produce results that are readily understood by fellow scientists, decision makers, or the general public. The OSPD initiative will support organizations to develop experiments in advanced representations of workflow results that result in new and creative result representation formats, maximizing the value of the outputs of the OSPD. D130 participants are expected to engage directly with different user groups to understand how to best represent the results of OSPD workflows. While the needs of all user groups will be considered, the OSPD will emphasize the needs of decision makers and the general public. D130 participants are required to describe their results in the training material that will allow the user to interact with the result representation production process. It is up to the D130 participant to describe how this interaction might operate. More than one experiment (D130) may be supported by the OSDP initiative.

All participants are required to participate in all technical discussions and to support the development of the Engineering Report(s) through their contributions. Participants can expect to work closely with the OGC COSI team and to receive their support as they work toward meeting their requirements.

5.2.2. Specific requirements for each work item

The following list specifies all work items and deliverables against which participants can bid.

  • D001 - Engineering Report: Engineering Report – An Engineering Report capturing all results and experiences from this project. It shall respond to all requirements listed above. The Engineering Report shall contain a plain language executive summary to clearly outline the motivations, goals, and critical outcomes of this task.

  • D100 - Open Science Platform VEDA: Deployment and operation of an instance of the NASA Platform VEDA. The participant deploys an instance of the VEDA Open Source Platform on their own cloud platform and makes the platform available to other participants. Data and processing applications are provided. It is possible to deploy a VEDA instance with reduced data and functionality to manage cloud costs. Several instances of D100 may be funded.

  • D101 - Open Science Platform: Provision of any other Open Science Platform. Platforms may provide a range of services, from simple data access services to more complex services that enable modeling or analysis across multiple datasets. The participant operates the Open Science Platform and provides standardized interfaces for interaction with the OSPD application. Several instances of D101 may be funded.

  • D102 - Use Case Development: Co-design with participants to develop initial use cases which will inform the design of the OSPD. The participant will lead activities to elicit user needs and priorities and define potential use cases.

  • D110 - Persistent Demonstrator: A web application that illustrates Open Science in action. It is expected that the application can be embedded into the OGC website. The goal is to demonstrate open science and to have a starting point for outreach and community engagement activities. The goal is not to replicate all functionality of the open science platforms, but to produce a reasonable set of elements that demonstrate the power of open science by building connections across platforms. Important: It is expected that the bidder for this item commits to continue the work on the persistent demonstrator over a period of three years. The OSPD24 initiative will be followed by at least two more initiatives that will enhance the Persistent Demonstrator. Funding will be made available in future OSPD initiatives.

  • D120 - Training: Development of practical step-by-step guidance on how to use the OSPD, including functions such as how to modify requests and how to execute pre-defined or self-defined workflows. The D120 participant will lead the team of D100, D101, and D110 participants. They will develop the format and lead on content for all training material and be responsible for providing access to the training materials during the Initiative. The training materials must be tightly linked to the OSPD and able to be accessed through the OGC Web site. Beyond this requirement, the participant is free to choose the underlying technologies, though solutions that prioritize ease of use and minimal maintenance costs will be preferrenced. Important: It is expected that the bidder for this item commits to continue the work on the persistent demonstrator over a period of three years. The OSPD24 initiative will be followed by at least two more initiatives that will enhance the Persistent Demonstrator. Funding will be made available in future OSPD initiatives.

  • D130 - Result representation: Demonstrations that illustrate different models for conveying the results emerging from OSPD workflows for various audiences. It is expected that these demonstrations will incorporate diverse formats, digital environments and media. D130 participants work closely with platform providers (D100 and D101) and with end users. Solutions that effectively communicate results with non-scientists that require decision-ready result representations are of particular interest to the OSPD. Several instances of D130 will be funded.

6. OGC COSI Program Initiative

This initiative is being conducted under the OGC Collaborative Solutions and Innovation (COSI) Program. The OGC COSI Program aims to solve the biggest challenges in location. Together with OGC-members, the COSI Team is exploring the future of climate, disasters, autonomy and robots, outer space systems interoperability, defense and intelligence, and more.

The OGC COSI Program is a forum for OGC members to solve the latest and hardest geospatial challenges via a collaborative and agile process. OGC members (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 funded initiatives have been executed - from small interoperability experiments run by an OGC working group to multi-million dollar testbeds with more than three hundred OGC-member participants.

OGC COSI initiatives promote rapid prototyping, testing, and validation of technologies, such as location standards or architectures. Within an initiative, OGC Members test and validate draft specifications to address geospatial interoperability requirements in real-world scenarios, business cases, and applied research topics. This approach not only encourages rapid technology development, but also determines the technology maturity of potential solutions and increases the technology adoption in the marketplace.

6.1. Information on bidding, selection, and key requirements

Responding to the Call For Participation (CFP):

To respond to the CFP as a bidder, you will submit an Online Form in which you describe your proposal. This proposal should include your (the bidder’s) technical solution(s) for each deliverable, cost sharing request(s) for funding, and proposed in-kind contribution(s) to the initiative.

The CFP includes a description of the deliverables against which bidders may submit proposals. Bidders may address technical deliverables, such as implementing a component of an infrastructure, or participatory deliverables, such as contributing to meetings and to writing documents. The timeline for completion of the deliverables is set out in the Master Schedule.

Proposal Evaluations will take place on a per-deliverable basis. Therefore, it is important that all proposals should all be entered into the form on a per-deliverable basis.

Proposals in response to the CFP should be submitted by the deadline listed in the Master Schedule.

Questions and Requests for clarification: Bidders have the opportunity to submit questions about the CFP for an initial Q&A Webinar. Questions can be submitted using this Form. Bidders who cannot access the Form should send an email to ospd-questions@ogc.org. The Bidders Q&A Webinar will be held on the date listed in the Master Schedule. The webinar is open to the public, but anyone wishing to attend must register using the provided link. Questions are due on the date listed in the Master Schedule Question submitters will remain anonymous, and answers will be compiled and published in the CFP clarifications.

After the initial Q&A Webinar bidders may submit further questions using the same Form. Again, question submitters will remain anonymous. Ongoing updates and answers to questions will be added to the CFP Corrigenda Table and the CFP Clarifications Table. The HTML version of the CFP will be updated automatically and appear at the same URL as the original version. The PDF file online will be updated following each revision. You should download a new copy for offline work regularly to ensure you are referring to the latest version.

Participant Selection and Agreements: Following the submission deadline, OGC will evaluate received proposals, review recommendations with Sponsors, and negotiate Participation Agreement (PA) contracts, including statements of work (SOWs). Participant selection will be complete once PA contracts have been signed with all Participants.

Required attendance at the Kickoff: The Kickoff is a meeting where Participants, guided by the Initiative Architect, will refine the Initiative architecture and settle on specifics 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 interface Designs.

Required attendance at Regular Telecons and Meetings: After the Kickoff, participants will meet frequently via weekly telecons (videoconferencing) and in person at OGC Member Meetings. As a minimum, participants are required to attend virtual meetings regularly.

Requirements for Development of Deliverables: Development of Components, Engineering Reports, Change Requests, and other deliverables will commence during or immediately after the Kickoff meeting.

Under the Participation Agreement contracts, ALL Participants will be responsible for contributing content to the documents / ERs, particularly regarding their component implementation experiences, findings, and future recommendations. Each participant will be required to provide at least one bullet point per week to the ER on work, progress, technical conversations and decisions, etc., while the ER Editor will be the primary compiler and author on the shared sections such as the Executive Summary. The ER editor is further responsible for capturing all design decisions and lessons learned during the whole initiative execution phase. Compiling the whole report at the end of the initiative does not work!

More detailed deliverable descriptions appear under Types of Deliverables.

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 webinars, demonstration events, and other meetings.

Assurance of Service Availability: Participants selected to implement service components must maintain availability for a period of no less than twelve months after the Participant Final Summary Report milestone.

Appendix A: Pilot Organization and Execution

A.1. Initiative Policies and Procedures

This initiative will be conducted within the policy framework of OGC’s Bylaws and Intellectual Property Rights Policy ("IPR Policy"), as agreed to in the OGC Membership Agreement, and in accordance with the OGC COSI Program Policies and Procedures and the OGC Principles of Conduct, the latter governing all related personal and public interactions. Specifically:

Several key requirements are summarized below for ready reference:

  • Each selected Participant will agree to notify OGC staff if it is aware of any claims under any issued patents (or patent applications) which would likely impact an implementation of the specification or other work product which is the subject of the initiative. Participant need not be the inventor of such patent (or patent application) in order to provide notice, nor will Participant be held responsible for expressing a belief which turns out to be inaccurate. Specific requirements are described under the "Necessary Claims" clause of the IPR Policy.

  • Each selected Participant will agree to refrain from making any public representations that draft Engineering Report (ER) content has been endorsed by OGC before the ER has been approved in an OGC Technical Committee (TC) vote.

  • Each selected Participant will agree to provide more detailed requirements for its assigned deliverables, and to coordinate with other initiative Participants, at the Kickoff event.

A.2. Initiative Roles

The roles generally played in any OGC COSI Program initiative include Sponsors, Bidders, Participants, Observers, and the COSI Program Team. Explanations of the roles are provided in Tips for New Bidders.

The COSI 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 high-impact issues or risks that might arise during execution.

A.3. Types of Deliverables

All activities in this pilot will result in a Deliverable. These Deliverables generally take the form of a persistent demonstrator capability, Documents or Component Implementations.

A.4. Documents

Engineering Reports (ER) and Change Requests (CR) will be prepared in accordance with OGC published templates. Engineering Reports will be delivered by posting on the (members-only) OGC Pending directory when complete and the document has achieved a satisfactory level of consensus among interested participants, contributors and editors. Engineering Reports are the formal mechanism used to deliver results of the COSI Program to Sponsors and to the OGC Standards Program for consideration by way of Standards Working Groups and Domain Working Groups.

Tip

A common ER Template will be used as the starting point for each document. Various template files will contain requirements such as the following (from the 1-summary.adoc file):

The Executive Summary shall contain a business value statement that should describe the value of this Engineering Report to improve interoperability, advance location-based technologies or realize innovations.

Ideas for meeting this particular requirement can be found in the CFP Background as well as in previous ER content such as the business case in the SELFIE Executive Summary.

Document content should follow this OGC Document Editorial Guidance (scroll down to view PDF file content). File names for documents posted to Pending should follow this pattern (replacing the document name and deliverable ID): OGC OSPD24 DocumentName (D001). For ERs, the words Engineering Report should be spelled out in full.

A.4.1. Component Implementations

Component Implementations include services, clients, datasets, and tools. A service component is typically delivered by deploying an endpoint via an accessible URL. A client component typically exercises a service interface to demonstrate interoperability. Implementations should be developed and deployed in all threads for integration testing in support of the technical architecture.

IMPORTANT

Under the Participation Agreement contracts, ALL Participants will be responsible for contributing content to the ERs, particularly regarding their component implementation experiences, findings, and future recommendations. The ER Editor will be the primary author on shared sections such as the Executive Summary.

Component implementations are often used as part of outreach demonstrations near the end of the timeline. To support these demonstrations, component implementations are required to include Demo Assets. For clients, the most common approach to meet this requirement is to create a video recording of a user interaction with the client. These video recordings may optionally be included in a new YouTube Playlist on the OGC YouTube channel.

Tip

Videos to be included in a new YouTube Playlist should follow these instructions: Upload the video recording to the designated Portal directory (to be provided), and include the following metadata in the Description field of the upload dialog box:

  • A Title that starts with "OGC OSPD:", keeping in mind that there is a 100-character limit [if no title is provided, we’ll insert the file name],

  • Abstract: [1-2 sentence high-level description of the content],

  • Author(s): [organization and/or individuals], and

  • Keywords: [for example, OGC, OSPD24, machine learning, analysis ready data, etc.].

Since server components often do not have end-user interfaces, participants may instead support outreach by delivering static UML diagrams, wiring diagrams, screenshots, etc. In many cases, the images created for an ER will be sufficient as long as they are suitable for showing in outreach activities such as Member Meetings and public presentations. A server implementer may still choose to create a video recording to feature their organization more prominently in the new YouTube playlist. Another reason to record a video might be to show interactions with a "developer user" (since these interactions might not appear in a client recording for an "end user").

Tip

Demo-asset deliverables are slightly different from Technology Interoperability Experiment (TIE) testing deliverables. The latter don’t necessarily need to be recorded (though they often appear in a recording if the TIE testing is demonstrated as part of one of the recorded weekly telecons).

A.5. Proposals & Proposal Evaluation

Proposals are expected to be brief, broken down by deliverable, and precisely addressing the work items of interest to the bidder. Details of the proposal submission process are provided under the General Proposal Submission Guidelines.

Proposals will be evaluated based on criteria in two areas: technical and management/cost.

A.5.1. Technical Evaluation Criteria

  • Concise description of each proposed solution and how it contributes to achievement of the particular deliverable requirements described in the Technical Architecture,

  • Overall quality and suitability of each proposed solution, and

  • Where applicable, whether the proposed solution is OGC-compliant.

Management/Cost Evaluation Criteria
  • Willingness to share information and work in a collaborative environment, Contribution toward Sponsor goals of enhancing availability of standards-based offerings in the marketplace,

  • Feasibility of each proposed solution using proposed resources, and

  • Proposed in-kind contribution in relation to proposed cost-share funding request.

Note that all Participants are required to provide some level of in-kind contribution (i.e. costs for which no cost-share compensation has been requested). As a rough guideline, a proposal should include at least one dollar of in-kind contribution for every dollar of cost-share compensation requested. All else being equal, higher levels of in-kind contributions will be considered more favorably during evaluation. Participation may also take place by purely in-kind contributions (no cost-share request at all).

Once the proposals have been evaluated and cost-share funding decisions have been made, the COSI Team will begin notifying Bidders of their selection to enter negotiations to become and initiative Participant. Each selected bidder will enter into a Participation Agreement (PA), which will include a Statement of Work (SOW) describing the assigned deliverables.

A.5.2. Reporting

Participants will be required to report the progress and status of their work; details will be provided during contract negotiation. Additional administrative details such as invoicing procedures will also be included in the contract.

Monthly Reporting

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

The purpose of the Monthly Business Report is to provide initiative management with a quick indicator of project health from each participant’s perspective. The COSI Team will review action item status on a weekly basis with assigned participants. Initiative participants must remain available for the duration of the timeline so these contacts can be made.

Participant Final Summary Reports

Each Participant should submit a Final Summary Report by the milestone indicated in the Master Schedule. These reports should include the following information:

  1. Briefly summarize Participant’s overall contribution to the Initiative (for an executive audience),

  2. Describe, in detail, the work completed to fulfill the Participation Agreement Statement of Work (SOW) items (for a more technical audience), and

  3. Present recommendations on how we can better manage future OGC COSI Program initiatives.

This report may be in the form of email text or an attached document (at the Participant’s discretion).

Appendix B: Proposal Submission

B.1. General Proposal Submission Guidelines

This section presents general guidelines for submitting a CFP proposal. Detailed instructions for submitting a response proposal using the Bid Submission Form web page can be found in the Step-by-Step Instructions below.

Important

Please note that the content of the "Proposed Contribution" text box in the Bid Submission Form will be accessible to all Stakeholders and should contain no confidential information such as labor rates.

Similarly, no sensitive information should be included in the Attached Document of Explanation.

Proposals must be submitted before the deadline indicated in the Master Schedule.

Tip

Non-members or individual members should make a note regarding their intent to join OGC on the Organizational Background page of the Bid Submission Form and include their actual Letter of Intent as part of an Attached Document of Explanation.

Information submitted in response to this CFP will be accessible to OGC and Sponsor staff members. This information will remain in the control of these stakeholders and will not be used for other purposes without prior written consent of the Bidder. Once a Bidder has agreed to become a Participant, they will be required to release proposal content (excluding financial information) to all initiative stakeholders. Sensitive information other than labor-hour and cost-share estimates should not be submitted.

Bidders will be selected for cost share funds on the basis of adherence to the CFP requirements and the overall proposal quality. The general initiative objective is to inform future OGC standards development with findings and recommendations surrounding potential new specifications. Each proposed deliverable should formulate a path for (1) producing executable interoperable prototype implementations meeting the stated CFP requirements and (2) documenting the associated findings and recommendations. Bidders not selected for cost share funds may still request to participate on a purely in-kind basis.

Bidders should avoid attempts to use the initiative as a platform for introducing new requirements not included in Technical Architecture. Any additional in-kind scope should be offered outside the formal bidding process, where an independent determination can be made as to whether it should be included in initiative scope or not. Out-of-scope items could potentially be included in another OGC COSI initiative.

Each selected Participant (even one not requesting any funding) will be required to enter into a Participation Agreement contract ("PA") with the OGC. The reason this requirement applies to purely in-kind Participants is that other Participants will likely be relying upon the delivery of their work. Each PA will include a Statement of Work ("SOW") identifying specific Participant roles and responsibilities.

B.2. Questions and Clarifications

Once the original CFP has been published, ongoing updates and answers to questions can be found in the CFP Corrigenda Table and the CFP Clarifications Table

Bidders may submit questions using the Questions Form or by emailing ospd-questions@ogc.org. When using the form, bidders should check ‘COSI (Innovation)’ from the list of ‘Interests’ and write the Initiative for which they are bidding and their question in the ‘Message’ box. Question submitters will remain anonymous, and answers will be regularly compiled and published in the CFP clarifications.

A Bidders Q&A Webinar will be held on the date listed in the Master Schedule. The webinar is open to the public, but anyone wishing to attend must register using the provided link. Questions are due on the date listed in the Master Schedule.

B.3. Proposal Submission Procedures

The process for a Bidder to complete a proposal is set out in the online Bid Submission Form.

The Bid Submission form will be made available shortly after the CFP release. It will include a series of web forms, one for each deliverable of interest. Bidders should remember to submit one form for each deliverable for which they wish to submit a proposal.

New users must create an account before completing a form.

Once an account is established, the user may log in and will be taken to a home page indicating the "Status of Your Proposal." The user can return to this page at any time by clicking the OGC logo in the upper left corner.

Any submitted bids will be treated as earnest submissions, even those submitted well before the response deadline. Be certain that you intend to submit your proposal before you click the Submit button on the Review page.

Important

Please consider making local backup copies of all text you are entering into the form in case anything needs to be re-entered. If you encounter any technical problems, please contact the OGC.

B.3.1. High-Level Overview

Clicking on the “Propose” link will bring you to the Bid Submission Form.

To complete the form, new users should start by providing organizational information on the “Organizational Background” Page and click “Update” and “Continue”. Existing users should check and confirm the information on the “Organizational Background” Page is correct and click “Continue”.

This will navigate to an "Add Deliverable" page. The user should complete this form for each proposed deliverable.

Tip

For component implementations having multiple identical instances of the same deliverable, the bidder only needs to propose just one instance. For simplicity, each bidder should just submit against the lowest-numbered deliverable ID. OGC will assign a unique deliverable ID to each selected Participant later (during negotiations).

A “Review” link, located on the far right of the screen, navigates to a page summarizing all the deliverables the Bidder is proposing. This Review tab won’t appear until the user has actually submitted at least one deliverable under the Propose tab first.

Tip

Consider regularly creating backup copies of this Review page at various points during proposal creation.

Once the “Submit” button is clicked, the user will receive an immediate confirmation on the website that their proposal has been received. The system will also send an email to the Bidder and to OGC staff.

Tip

In general, up until the time that the user clicks this Submit button, the proposal may be edited as many times as the user wishes. However, this initial version of the form contains no "undo" capability, so please use caution in over-writing existing information.

Under the “Done Adding Deliverables” section at the bottom of this page, a user may attach an additional document with further information and explanations. This document is optional.

Important

No sensitive information (such as labor rates) should be included in the Attached Document.

If this attachment is provided, it is limited to one per proposal and must be less than 5Mb.

This document could conceivably contain any specialized information that wasn’t suitable for entry into a Proposed Contribution field under an individual deliverable. It should be noted, however, that this additional documentation will only be read on a best-effort basis. There is no guarantee it will be used during evaluation to make selection decisions; rather, it could optionally be examined if the evaluation team feels that it might help in understanding any specialized (and particularly promising) contributions.

B.3.2. Step-by-Step Instructions

The “Propose” link takes the user to the first page of the proposal entry form. This form contains fields to be completed once per proposal such as names and contact information.

It also contains an optional Organizational Background field where Bidders (particularly those with no experience participating in an OGC initiative) may provide a description of their organization. It also contains a click-through check box where each Bidder will be required (before entering any data for individual deliverables) to acknowledge its understanding and acceptance of the requirements described in this appendix.

Clicking the Update and Continue button then navigates to the form for submitting deliverable by deliverable bids. On this page, existing deliverable bids can be modified or deleted by clicking the appropriate icon next to the deliverable name. Any attempt to delete a proposed deliverable will require scrolling down to click a Confirm Deletion button.

To add a new deliverable, the user would scroll down to the Add Deliverable section and click the Deliverable drop-down list to select the particular item.

The user would then enter the required information for each of the following fields (for this deliverable only). Required fields are indicated by an asterisk: * Estimated Projected Labor Hours* for this deliverable, * Funding Request*: total U.S. dollar cost-share amount being requested for this deliverable (to cover burdened labor only), * Estimated In-kind Labor Hours* to be contributed for this deliverable, and * Estimated In-Kind Contribution: total U.S. dollar estimate of the in-kind amount to be contributed for this deliverable (including all cost categories).

Tip

There’s no separate text box to enter a global in-kind contribution. Instead, please provide an approximate estimate on a per-deliverable basis.

Cost-sharing funds may only be used for the purpose of offsetting burdened labor costs of development, engineering, documentation, and demonstration related to the Participant’s assigned deliverables. By contrast, the costs used to formulate the Bidder’s in-kind contribution may be much broader, including supporting labor, travel, software licenses, data, IT infrastructure, and so on.

Theoretically there is no limit on the size of the Proposed Contribution for each deliverable (beyond the raw capacity of the underlying hardware and software). But bidders are encouraged to incorporate content by making reference or linking to external materials where possible (rather than inline copying and pasting). There is also a textbox on a separate page of the submission form for inclusion of Organizational Background information, so there is no need to repeat this information for each deliverable.

Important
  • A breakdown (by cost category) of the "In Kind Contribution" may be included in the Proposed Contribution text box for each deliverable.

  • However, please note that the content of this text box will be accessible to all Stakeholders and should contain no confidential information such as labor rates.

  • Similarly, no sensitive information should be included in the Attached Document of Explanation.

The “Proposed Contribution (Please include any proposed datasets)” field can be used to provide a succinct description of what the Bidder intends to deliver for this work item to meet the requirements expressed in the Technical Architecture. This could potentially include a brief elaboration on how the proposed deliverable will contribute to advancing the OGC standards baseline, or how implementations enabled by the specification embodied in this deliverable could add specific value to end-user experiences.

A Bidder proposing to deliver a Service Component Implementation can also use this field to identify what suitable datasets would be contributed (or what data should be acquired from another identified source) to support the proposed service.

Tip
  • In general, please try to limit the length of each Proposed Contribution to about one text page per deliverable.

  • Note that images cannot be pasted into the field Proposed Contribution textbox. Bidders should instead provide a link to a publicly available image.

A single bid may propose deliverables arising from any number of threads or tasks. To ensure that the full set of sponsored deliverables are made, OGC might negotiate with individual Bidders to drop and/or add selected deliverables from their proposals.

B.3.3. Tips for New Bidders

Bidders who are new to OGC initiatives are encouraged to review the following tips:

  • In general, the term "activity" is used as a verb describing work to be performed in an initiative, and the term "deliverable" is used as a noun describing artifacts to be developed and delivered for inspection and use.

  • The roles generally played in any OGC COSI Program initiative are defined in the OGC COSI Program Policies and Procedures, from which the following definitions are derived and extended:

    • Sponsors are OGC member organizations that contribute financial resources to steer Initiative requirements toward rapid development and delivery of proven candidate specifications to the OGC Standards Program. These requirements take the form of the deliverables described herein. Sponsors' representatives help serve as "customers" during Initiative execution, helping ensure that requirements are being addressed and broader OGC interests are being served.

    • Bidders are organizations who submit proposals in response to this CFP. A Bidder selected to participate will become a Participant through the execution of a Participation Agreement contract with OGC. Most Bidders are expected to propose a combination of cost-sharing request and in-kind contribution (though solely in-kind contributions are also welcomed).

    • Participants are selected OGC member organizations that generate empirical information through the definition of interfaces, implementation of prototype components, and documentation of all related findings and recommendations in Engineering Reports, Change Requests and other artifacts. They might be receiving cost-share funding, but they can also make purely in-kind contributions. Participants assign business and technical representatives to represent their interests throughout Initiative execution.

    • Observers are individuals from OGC member organizations that have agreed to OGC intellectual property requirements in exchange for the privilege to access Initiative communications and intermediate work products. They may contribute recommendations and comments, but the COSI Team has the authority to table any of these contributions if there’s a risk of interfering with any primary Initiative activities.

    • Supporters are OGC member organizations who make in-kind contributions aside from the technical deliverables. For example, a member could donate the use of their facility for the Kickoff event.

    • The COSI Team is the management team that will oversee and coordinate the Initiative. This team is comprised of OGC staff, representatives from member organizations, and OGC consultants. ** The COSI Team communicates with Participants and other stakeholders during Initiative execution, provides Initiative scope and schedule control, and assist stakeholders in understanding OGC policies and procedures.

    • The term Stakeholders is a generic label that encompasses all Initiative actors, including representatives of Sponsors, Participants, and Observers, as well as the COSI Team.

    • Suppliers are organizations (not necessarily OGC members) who have offered to supply specialized resources such as cloud credits. OGCs role is to assist in identifying an initial alignment of interests and performing introductions of potential consumers to these suppliers. Subsequent discussions would then take place directly between the parties.

  • Proposals from non-members or individual members will be considered provided that a completed application for organizational membership (or a letter of intent) is submitted prior to or with the proposal.

    • Non-members or individual members should make a note regarding their intent to join OGC on the Organizational Background page of the Bid Submission Form and include their actual Letter of Intent as part of an Attached Document of Explanation.

  • Any individual wishing to gain access to the Initiative’s intermediate work products in the restricted area of the Portal (or attend private working meetings / telecons) must be a member approved user of the OGC Portal system.

  • Individuals from any OGC member organization that does not become an initiative Sponsor or Participant may still (as a benefit of membership) observe activities by registering as an Observer. Prior initiative participation is not a direct bid evaluation criterion. However, prior participation could accelerate and deepen a Bidder’s understanding of the information presented in the CFP.

  • All else being equal, preference will be given to proposals that include a larger proportion of in-kind contribution. All else being equal, preference will be given to proposed components that are certified OGC compliant.

  • All else being equal, a proposal addressing all of a deliverable’s requirements will be favored over one addressing only a subset. Each Bidder is at liberty to control its own proposal, of course. But if it does choose to propose only a subset for any particular deliverable, it might help if the Bidder prominently and unambiguously states precisely what subset of the deliverable requirements are being proposed.

  • The Sponsor(s) will be given an opportunity to review selection results and offer advice, but ultimately the Participation Agreement (PA) contracts will be formed bilaterally between OGC and each Participant organization. No multilateral contracts will be formed. Beyond this, there are no restrictions regarding how a Participant chooses to accomplish its deliverable obligations so long as these obligations are met in a timely manner (whether a 3rd-party subcontractor provides assistance is up to the Participant).

  • In general, only one organization will be selected to receive cost-share funding per deliverable, and that organization will become the Assigned Participant upon which other Participants will rely for delivery. Optional in-kind contributions may be made provided that they don’t disrupt delivery of required, reliable contributions from the assigned Participants.

  • A Bidder may propose against one, several, or all deliverables. In past projects, more participants were assigned one deliverable, and fewer were assigned multiple deliverables.

  • In general, the Participant Agreements will not require delivery of any component source code to OGC.

    • What is delivered to OGC is the behavior of the component installed on the Participant’s machine, and the corresponding documentation of findings, recommendations, and technical artifacts contributed to the Engineering Report(s).

    • In some instances, a Sponsor might expressly require a component to be developed under open-source licensing, in which case the source code would become publicly accessible outside the Initiative as a by-product of implementation.

  • Results of other recent OGC initiatives can be found in the OGC Public Engineering Report Repository.

Appendix C: Abbreviations

The following table lists all abbreviations used in this CFP.

AI

Artifical Intelligence

CFP

Call for Participation

COSI

Collaborative Solutions and Innovation Program

CR

Change Request

DER

Draft Engineering Report

DWG

Domain Working Group

ER

Engineering Report

FAIR

FAIR Findable Accessible Interoperable Reusable

GPKG

GeoPackage

OGC

Open Geospatial Consortium

ORM

OGC Reference Model

OSPD

Open Science Persistent Demonstrator

OWS

OGC Web Services

NSG

National System for Geospatial Intelligence

PA

Participation Agreement

POC

Point of Contact

Q&A

Questions and Answers

RM-ODP

Reference Model for Open Distributed Processing

SIF

Sensor Integration Framework

SOW

Statement of Work

SWG

Standards Working Group

TBD

To Be Determined (at a later date)

TC

OGC Technical Committee

TEM

Technical Evaluation Meeting

TIE

Technology Integration / Technical Interoperability Experiment

URL

Uniform Resource Locator

WFS

Web Feature Service

WPS

Web Processing Service

WG

Working Group (SWG or DWG)

Appendix D: Corrigenda & Clarifications

The following table identifies all corrections that have been applied to this CFP compared to the original release. Minor editorial changes (spelling, grammar, etc.) are not included.

Section Description

no entries

The following table identifies all clarifications that have been provided in response to questions received from organizations interested in this CFP.

Question Clarification

If we want to create an Open Science Persistence Demonstrator (OSPD), D110, will we be informed about all the 'Open Science Platforms' that we are supposed to link?

Yes, all platforms will be presented at the kick-off meeting.

We need more clarification on the provision of 'Open Science Platforms', D101. If we want to create a new open science platform, then what are the requirements or expected features?

It is required that the platform offers Open Science services or data or both. It is up to you to decide what the platform is actually capable of. Ideally, the platform supports customer to deploy and execute their own applications or applications developed by other users,

If we want to bid for an 'Engineering Report - D001', what should be included in the proposal?

The Engineering Report summarizes all key aspects and lessons learned from the initiative. We don’t need much of a proposal, but sufficient information explaining what qualifies you to develop the report. The report should not be a simple summary of all results, but should put the results in context and be written in easy-to-understand language.

Is the OSPD strictly a test and development environment - implying that productionalizing any applications developed over the course of this initiative will be productionalized afterwards?

Yes. The OSPD focuses on design, development and testing of applications. Like other OGC Pilots, the intent is to move software tools, coded workflows, and platforms up the Technology Readiness Levels (TLRs) from early stage prototypes towards production ready products. The outcomes of the OSPD are made available under an open license and could be put into production when they reach maturity after the completion of the Pilot.

For D100, Who is making the decision on what data and applications to host? Or do you want the bidder to suggest?

The OGC team leading the OSPD Pilot will select the data and applications to host in consultation with the OSPD’s sponsors. It is not necessary for the bidder for D100 to suggest data and applications.

For D100 and D101, is there an expectation that the platform will be available for the persistent demonstrator for the anticipated 3 years?

The expectation is that once a platform has been developed, it will be maintained for the duration of the OSPD, and hopefully beyond. It is understood that platforms will be developed during the course of the performance period, and so won’t be available immediately.

For D102 and D110, How many bidders may be funded for these?

The number of bidders funded will depend on the quality, quantity and scale of the applications and is not fixed.

The CFP states in §4.2 that it is possible to contribute to the activity by .. existing data, platforms, research or other resources (e.g. models, digital infrastructure components) ", which seems very flexible. On the other hand, the CFP §5.2 requests bids to address (entire?) "work items" (i.e. the numbered deliverables). Is it necessary to cover the complete work item in the bid or is it allowed to propose one or more components that would implement only part of an entire "work item", and that OGC might combine with other interesting components from other bidders to build the entire work item.

When responding to the work items listed in §5.2, you must select a whole work item from the drop-down menu of deliverables in the submission portal. That said, you may propose to respond to part of the specification for a work item. For example, you could propose to undertake the UI/UX work for a platform, but not the back-end database work. If you choose to respond to part of a deliverable, please clearly describe which part of the work you propose to undertake. If you are proposing in coordination with another organization, please reference their proposal in your response.

Section 3 of the CFP document indicates a completion date of September 2024. However an answer to a question from the RFI stated that the project is likely to run into 2026. Can you please clarify? Which date should be used when calculating our estimated projected hours?

We are currently taking bids for year 1 of three planned years of work. There are two deliverables, D110 and D120, where the bidder is expected to commit to 3 years of participation. For D110 and D120 please state the year 1 hours AND provide an estimate of the hours across all three years in your budget. For all other deliverables, please only include hours relevant to the year 1 work.