SPECIAL NOTICE
99 -- Request for Information - TraCSS Presentation Layer
- Notice Date
- 10/30/2023 11:02:24 AM
- Notice Type
- Special Notice
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- DEPT OF COMMERCE NOAA SILVER SPRING MD 20910 USA
- ZIP Code
- 20910
- Solicitation Number
- 30421RFI
- Response Due
- 11/6/2023 12:00:00 PM
- Archive Date
- 11/21/2023
- Point of Contact
- Amber Behrns, Noelle Albert
- E-Mail Address
-
amber.behrns@noaa.gov, noelle.albert@noaa.gov
(amber.behrns@noaa.gov, noelle.albert@noaa.gov)
- Description
- Request for Information: TraCSS Presentation Layer This Request for Information (RFI) gauge the marketplace and learn the industry�s capabilities to meet the requirements in the attached draft performance work statement (PWS). This RFI is issued solely for information and planning purposes and does not constitute a solicitation or a commitment for a solicitation in the future, nor does it commit the Government to award a contract for these services in the future. The Government will not pay for any information or administrative costs incurred by responding to this announcement. Proprietary information received in response to this RFI will be safeguarded in accordance with Government regulations. Responses may be reviewed by The Aerospace Corporation and The MITRE Corporation. Background: The NOAA Office of Space Commerce (OSC) is the principal unit for space commerce policy activities within the Department of Commerce (DOC). Its mission is to foster the conditions for the economic growth and technological advancement of the U.S. commercial space industry. OSC is seeking commercial System Integrator and Cloud Management Services for the Traffic Coordination System for Space (TraCSS) (formerly called Open Architecture Data Repository (OADR)). The TraCSS will be developed to fulfill the 2018 US National Space Council released Space Policy Directive-3 (SPD-3), which instructed relevant US government agencies to begin re-assigning many aspects of space traffic management (STM) and space traffic coordination (STC) serving non-military US space operators. This was identified as an intergovernmental approach, and the organization identified to lead many of the efforts was NOAA OSC, in the US Department of Commerce (DOC). TraCSS is the Department of Commerce's enterprise solution for ingesting, archiving, processing, and disseminating Space Situational Awareness (SSA) data and products. TraCSS will provide conjunction analysis and warning services to commercial and civil satellite owner/operators to promote spaceflight safety and foster economic growth and technological advancement of the U.S. commercial space industry. The system will store data from the Department of Defense, Department of State, NOAA, commercial SSA data providers, commercial and civil satellite Owner/Operators (O/O) and select international civil partners. The TraCSS system will operate 24 hours per day, 7 days a week. Purpose and Objectives: The Office of Space Commerce is seeking input from vendors seeking to develop or provide the TraCSS presentation layer.� Responses can address both sections 1 and 2 or choose to address only one. A draft Presentation Layer PWS is attached and references made are to specific sections in that document.� For reference, presentation layer services and functionality are shown in Figure 3.� A description of presentation layers services can be found in Appendix B, item B.1. Information Requested: Capabilities The government intends to operate presentation services on a government owned and operated System Integration Platform based on containerized microservices, i.e., modular data-centric components that separate concerns.� The government intends to use the System Integration Platform running in a commercial cloud provider to integrate components from multiple vendors to form the operational TraCSS system.� The government is seeking information on both the development of a fully government owned TraCSS Presentation Layer and the potential for acquiring an existing capability.� Regardless of acquisition approach, the government desires to maintain an enduring competitive environment for presentation layer vendors. Responses should reflect that approach.� The Contractor and its subcontractors may provide external SSA services for TraCSS such as improved owner/operator ephemerides or SSA data (including ephemerides) consistent with avoiding any conflict-of-interest situations. While such an arrangement is highly discouraged, in such case, an organizational conflict of interest (OCI) mitigation plan shall be submitted and approved by the Government. An organizational conflict of interest (OCI) mitigation plan must be submitted and approved by the government if any conflict of interest (COI) situation is identified by the government.� The Contractor and its subcontractors are prohibited from providing the system integration capability of TraCSS. In such cases, the presentation layer must be able to equally integrate with all capabilities, regardless of vendor.�� Section 1: Government Procurement of Custom-Built Solution A government procurement of custom-built software, entirely produced in performance of this contract, wholly owned by the government, will be developed with agile methodology to align with the phased approach TraCSS mission instantiation.� As such, please address the following questions: Provide a plan for user research for the presentation layer both during initial development and ongoing updates of the presentation layer. Possible users are described in the draft PWS. Does the Draft PWS provide sufficient detail and scope to describe the work to be performed under this effort? If �No�, please provide any comments and/or recommendations on technical elements of the draft PWS that may contribute to a more accurate quotation submission. Please provide feedback on whether or not such a technical approach is viable in the marketplace today. If the approach or elements of the requirements are not viable, please explain why this is the case, as well as provide recommendations for what items in this explanation would need to change to make the requirement viable. Is the PWS written clearly enough such that industry is able to respond or deploy Presentation layer services? If not, please provide specific examples for how the PWS could be clearer. Provide a Capabilities Statement/Vendor Profile which includes current staffing capabilities and the ability, along with timeframe, to quickly scale staff to start executing the project. Include any Space Situational Awareness (SSA)/Space Traffic Coordination (STC) domain knowledge. Provide past performance history on developing systems such as the TraCSS, Indicate if the system was new or existing. Was the work performed as a prime or sub? If as a sub, provide the name and address of the prime contractor. The government will require, clear, irrevocable rights to this software. Should the contractor be required to assign title to the copyright to the software to the government, or should the contractor be allowed to retain copyright but provide a license with unlimited rights (as defined in FAR 27.401)? Provide a rough order of magnitude or estimate to perform the services outlined in the PWS. Section 2: Government Procurement of an Existing Commercial Product A government procurement of an existing commercial product must ensure that the government can maintain a competitive environment for the presentation layer indefinitely. Provide a plan for user research for the presentation layer both during initial development and ongoing updates of the presentation layer. Possible users are described in the draft PWS. Do you have a commercial product that might satisfy the intent of one or more of these services?� If so, which services does your product address? What are the unique features of your product? What types of displays does your product provide?� (See displays and APIs section in draft PWS.) How are your displays configurable or customizable by the user? A description of potential users is found in the draft PWS. Is your product based on modular components that can be disaggregated?� What is your experience disaggregating your components? Are the capabilities within your product modular and disaggregated in such a way that modules can be integrated into, or with, another vendor�s platform? If so, how has this disaggregated modularity been demonstrated with other companies in the past? What is your experience integrating your product with products from other vendors? What is your experience hosting your product on different commercial cloud providers?� Which cloud providers have you used?� Is your product cloud provider agnostic?� If you would modify or augment your existing commercial product with custom software, first produced in performance of the contract, would you prefer assigning title to the copyright to this custom software to the government or providing a license with unlimited rights (as defined in FAR 27.401)? Please provide a ROM and insight into cost structure and/or acquisition model for procuring your existing commercial product. RFI Submission Instructions Interested parties should provide requested information to the following emails by November 6, 2023 at 3:00pm Eastern Standard Time: Noelle Albert, Contracting Officer � noelle.albert@noaa.gov Amber Behrns, Contract Specialist � amber.behrns@noaa.gov Responses should include your firm�s name, Commercial and Government Entity (CAGE) code, Unique Entity Identifier (UEI) number, Federal Supply Schedule numbers (if applicable) and primary points of contact. Proprietary information must be clearly identified.
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/9d829cc0a27e4e13889b576d4f99b12b/view)
- Place of Performance
- Address: Silver Spring, MD 20910, USA
- Zip Code: 20910
- Country: USA
- Zip Code: 20910
- Record
- SN06870865-F 20231101/231030230044 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |