Presentation Layer of the Traffic Coordination System for Space (TraCSS)   3

Update: August 1, 2024.

The Government's responses to the draft RFP questions are posted.

The U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) is posting a draft Request for Proposal (RFP) for the Presentation Layer of the Traffic Coordination System for Space (TraCSS). The NOAA, Office of Space Commerce (OSC), requires a Presentation Layer (user interface and user experience) for the TraCSS. The Government seeks to leverage mature commercial capabilities for the TraCSS Presentation Layer (user interface), which consists of web-based Graphical User Interfaces (GUI) and a Data Products service to generate formatted human-readable data products. The Government also requires the Contractor to build the TraCSS website to present the GUIs and Data Products. The GUI, Data Products, and website will utilize TraCSS Application Programming Interfaces (APIs) and Gateway Business Logic defined by the System Integrator to store and retrieve data.

Please use this Draft RFP question session to submit your questions as opposed to waiting until the Final RFP to be released.

The Government intends to allow for questions from potential Offerors upon release of the Draft RFP and related documents. Questions relevant to this Draft RFP must be submitted via email to Noelle.Albert@noaa.gov and Sayed.Hashimi@noaa.gov. Questions are due no later than 12:00 PM Eastern Time on July 25, 2024. Please submit all question on the attached Excel spreadsheet (1305M424R0047 RFP Question and Comment Template).

The Government may not provide a response to questions submitted after the due date. Offerors will not receive a response until all questions have been received by the due date. The Government will not attribute the questions to the submitting Offerors, but the text of the questions and answers will be published and made available to the general public. Please be mindful that if there is a prompt to change a solicitation document, that change will be made in the document itself and the response in the Q&A document does not have the force and effect of a solicitation amendment.