Currently Active
Requests for Proposal (RFPs)
&
Requests for Information (RFIs)
Make a selection for further information.
Generic Sonar Interface RFP
Shared Operational Picture Exchange Services (SOPES) Information Exchange Mechanism (IEM) RFP
Shared Operational Picture Exchange Services (SOPES) Information Exchange Data Model (IEDM) RFP
Combat Management System (CMS) Application Management RFP
Alert Management Service of CMS Systems RFP
Generic Radar Interface (GRI) RFI
Generic Sonar Interface (GSI) RFP
Status: Voting List deadline has passed.This RFP solicits proposals for the following:
- Generic Sonar Interface - external interfaces
- Generic Sonar Interface - internal interfaces
- Generic Sonar Interface - simulator interfaces
| Event | Date | Notes |
|---|---|---|
| RFP Issued | June 28, 2002 | Relevant documents: c4i/02-06-06 (Generic Sonar Interface RFP) |
| LOI Deadline | November 22, 2002 | |
| Initial Submission Deadline | March 3, 2003 | Deadline extended at the Washington meeting, old date was January 3, 2003 |
| Voting List Deadline | January 23, 2005 | Voting List reopened at Washington (November 2004) meeting. Old date was March 28, 2003. |
| Revised Submission Deadline | November 14, 2005 | Deadline extended at the Boston (September 2002) meeting. Old date was October 27, 2003. |
Shared Operational Picture Exchange Services (SOPES) Information Exchange Mechanism (IEM) RFP
Status: RFP has been issued; responses pending.The objective of Shared Operational Picture Exchange Services (SOPES) is to enhance the ability of first responders, government, military and civilian organizations to develop and sustain a complete, timely and accurate awareness of the operational situation (“Operational Picture”). SOPES will enable users to selectively share information between and across participating organizations; providing an improved visibility of the operational environment, and enhancing the effectiveness of decisions and resource commitments. The intent is to provide the decision maker with relevant information in real time and support the challenge of tactical communication links. SOPES will also protect sensitive, private, confidential or legally significant information from general dissemination. SOPES will enable all participants within a coalition to have the same understanding of the operational scenario and environment within their areas of interest. This RFP solicits proposals for the following: -Platform Independent Model (PIM) for the SOPES Information Exchange Mechanism (IEM). -A specification (standard) describing the functional, operational and performance requirements for a SOPES IEM. -Two (2) Platform Specific Models (PSMs) for potential implementations of the IEM
| Event | Date | Notes |
|---|---|---|
| RFP Issued | June 25, 2004 | Relevant documents: c4i/04-06-28 (SOPES IEM RFP) |
| LOI Deadline | December 5 , 2005 | Deadline extended at the Washington (November 2004) meeting. Old date was October 4, 2004. |
| Initial Submission Deadline | April 3, 2006 | Deadline extended at the Washington (November 2004) meeting. Old date was February 1, 2004. |
| Voting List Deadline | April 17, 2006 | Deadline extended at the Boston (June 2005) meeting. Old date was February 15, 2005. |
| Revised Submission Deadline | TBD | Deadline extended at the Burlingame (February 2005) meeting. Old date was March 31, 2005. Deadline extended at the Boston (June 2005) meeting. Old date was November 2005. |
Shared Operational Picture Exchange Services (SOPES) Information Exchange Data Model (IEDM) RFP
Status: RFP has been issued; responses pending.The objective of the Shared Operational Picture Exchange Services (SOPES) initiative is to enhance the ability of first responders, government, military and civilian organizations to develop and sustain a complete, timely and accurate awareness of the operational situation (Common Operational Picture). SOPES will enable users to selectively share information across and between participating organizations; providing an improved visibility of the operational environment affecting decisions and resource commitments. The intent is to provide the decision maker with relevant information in near real time and to support the challenge of tactical communication links. SOPES will also protect sensitive, private, confidential or legally significant information from general dissemination. SOPES will enable all participants within a coalition to have the same understanding of the operational scenario and environment within their area of interest. This RFP solicits proposals for the following: -A Platform Independent Model (PIM) capable of containing and representing data/information exchanged between and across boundaries within any multi-faceted enterprise in support of the preparation and management of civil and military Crisis Response Operations (CRO). -A specification describing the requirements, structure, components, relationships and conceptual understanding of the SOPES Information Exchange Data Model (IEDM) sufficiently detailed to enable the provision of: -A consistent and common understanding of exchanged data/information. -Common operational views of the data that can be developed independently. -A conceptual/logical schema of data for the design of systemÂ’s databases.
| Event | Date | Notes |
|---|---|---|
| RFP Issued | June 25, 2004 | Relevant documents: c4i/04-06-27 (SOPES IEDM RFP) |
| LOI Deadline | December 5, 2005 | Deadline extended at the Burlingame (February 2005) meeting. Old date was October 4, 2004. |
| Initial Submission Deadline | April 3, 2006 | Deadline extended at the Burlingame (February 2005) meeting. Old date was January 10, 2005. Deadline extended at the Boston (June 2005) meeting. Old date was August 8, 2005. |
| Voting List Deadline | April 17, 2006 | Deadline extended at the Boston (June 2005) meeting. Old date was January 24, 2005. |
| Revised Submission Deadline | TBD | Deadline extended at the Burlingame (February 2005) meeting. Old date was March 31, 2005. Deadline extended at the Boston (June 2005) meeting. Old date was November 2005. |
Combat Management System (CMS) Application Management RFP
Status: RFP has been issued; responses pending.The domain of naval Combat Management Systems is characterized by a huge variety of underlying computing platforms, with different and often incompatible means of managing applications (e.g. starting and stopping). Existing application management solutions do not consistently address the quality-of-service aspects relevant for the Naval CMS domain. As cooperation and drive towards open systems increases within the domain, a strong need arises for standards-based application management solutions allowing increased interoperability. This RFP solicits proposals for the following: A standard for Application Management and System Monitoring in CMS systems, consisting of service part and a data model part
| Event | Date | Notes |
|---|---|---|
| RFP Issued | June 25, 2004 | Relevant documents: c4i/04-06-26 (CMS Application Management RFP) |
| LOI Deadline | November 18, 2004 | |
| Initial Submission Deadline | May 30, 2005 | Deadline was extended at the Washington (November 2004) meeting. Old date was January 10, 2005. |
| Voting List Deadline | January 24, 2005 | |
| Revised Submission Deadline | May 30, 2005 | Originally posted as June 1, 2005 as a preliminary date pending the scheduling of the Boston (June 2005) meeting. |
Alert Management Service of CMS Systems RFP
The domain of naval Combat Management Systems is characterized by a huge variety of underlying computing platforms, with different and often incompatible means of managing & reporting alerts. Standards-based alert management services are essential for interoperable and open systems. This RFP solicits proposals for the following: -A standard for ALert MAnagement Service (ALMAS) in CMS systems, consisting of a standard alerts data model and a model for an alert delivery and lifecycle management service.
| Event | Date | Notes |
|---|---|---|
| RFP Issued | November 5, 2004 |
Relevant documents: c4i/04-11-13 (Alert Management Service of CMS Systems RFP) |
| LOI Deadline | May 31, 2005 | Reopened at the Athens (April 2005) meeting. Original date was March 21, 2005 |
| Initial Submission Deadline |
August 22, 2005 | Deadline was extended at the Athens (April 2005) meeting. Original date was May 30, 2005 |
| Voting List Deadline | June 13, 2005 | |
| Revised Submission Deadline |
January 23, 2006 | Deadline extended at the Boston (June 2005) meeting. Old date was October 31, 2005. |
Generic Radar Interface (GRI) RFI
Status: RFI has been issued; responses pending.Integration of radar systems and naval combat management systems is today a major cost driver. It also introduces a high risk. Standardization of the radar/combat management system interface can reduce cost and risk of integration. It also allows for the future evolution of radars without need to reconfigure the combat management system. This RFI therefore addresses naval CS integrators, radar developers, research facilities and invites them to take part in a respective standardization process. This Request for Information (RFI) solicits information about requirements, standards, products and work in progress regarding the integration of tactical radar systems into the combat management system. The Object Management Group (OMG) and, specifically, the Command, Control, Communications, Computers, and Intelligence (C4I) Domain Task Force (C4I DTF), will use this information to begin the technol-ogy adoption process for OMG compliant models and interfaces for radar systems to be used in maritime military platforms. The intent of the RFI is also to gather radar related information that would contribute to the standardization of interfaces applicable for the civilian navigation radar systems.
| Event | Date | Notes |
|---|---|---|
| RFI Issued | June 25, 2004 | Relevant documents: c4i/04-03-01 (Generic Radar Interface RFI) |
| RFI Response Deadline | January 31, 2005 | Deadline was extended at the Washington (November 2004) meeting. Old date was November 2, 2004. |