COSMOS - DRFP Q and A Part 1 10.01.pdf

Contract for Organizing Spaceflight Mission Operations and Systems

(COSMOS)

DRFP Q&A Part 1 – October 1, 2024

Category Sec�on Page Number Ques�on Number

Type Ques�on/Comment Response

Other Solica�on Leter 4 1 Clarity If an innova�on/efficiency is not included in the DRDs at proposal submission, is there a process to propose new innova�ons/efficiencies once on contract?

Yes, please see DRD-

COSMOS-0020

Con�nuous Improvement Plan.

Other Sec�on C, 3.1.1.1 Configura�on Management

C-21 2 Clarity Is all informa�on up to date in AART for all current MSOC applica�ons/tools, such that COSMOS will only be required to update informa�on as it changes?

Agency Applica�on Ra�onaliza�on Tool (AART) is up to date per FOD requirements.

The COSMOS awardee is required to enter data and make changes during the execu�on of COSMOS per the direc�on of the Government. At this �me, the Government can't confirm if the COSMOS awardee will only be required to update informa�on as it changes.

Other Sec�on C, 3.1.1.3 Technical Change Process

C-21 3 Request for addi�onal informa�on

Request the Government provide historical data on the number of Change Requests assessed and es�mated to support Technical Planning per year over the last 5 years.

The Government does not an�cipate that the historical record of change requests under the predecessor contract will indicate the an�cipated number of changes under COSMOS. Therefore, the Government will not be providing this informa�on to offerors at this �me.

Other Sec�on C, 3.1.3 Maintenance and Sustaining Engineering

C-25 4 Request for addi�onal informa�on

Request the Government provide current COTS so�ware licenses managed and quan��es to allow offerors insight into the technologies used to manage mission systems.

Current COTS so�ware licenses managed, and quan��es are in Atachment J-10 List of COSMOS So�ware.

Other Sec�on C, 3.1.3 Maintenance and Sustaining Engineering

C-25 5 Request for addi�onal informa�on

Request the Government provide current inventory of IT hardware components and end user devices managed in each environment (Opera�onal, I&T, Dev) and any schedules for upcoming re�rement/refresh of items.

Current list of IT hardware and end user devices are listed in J-9.

Upcoming re�rement/refreshes (Equipment Replacement Plan) will not be released due to security concerns.

Other Sec�on C, 3.1.3 Maintenance and Sustaining Engineering

C-25 6 Request for addi�onal informa�on

Request the Government provide documenta�on that describes Mission Control Center failover / isola�on scenarios that would ac�vate the TMCCS, BAT, or BCC.

Isola�on/failover determina�on is a real- �me decision resul�ng from the inability to support from a prime loca�on. Examples of poten�al scenarios are:

The Backup Control Center, hosted at the Marshal Space Flight Center and White Sands Test Facility, provides the backup capability for MCC. It can be ac�vated for either planned or unplanned loss of availability of the MCC.

Ac�va�on is not instantaneous, requiring execu�on of a several-hour process.

Backup Control Center Ac�va�on Team (BAT) ac�vates an ini�al, par�al backup MCC capability in the event of the pending or immediate loss of MCC Systems. This system is fully mobile and provides ac�va�on and remote opera�ons services for the Backup

Control Center (BCC).

It is intended to provide a ‘bridge’ control center capability un�l the BCC is fully ac�vated.

Temporary Mission Control Center Systems (TMCCS) are ac�vated in the case when Building 30 MCCS computa�onal and communica�ons assets remain fully available and opera�onal, but personnel are required to leave the facility. In this scenario, flight control and Mission Systems opera�ons personnel will relocate to another facility such as the Mission Training Center and remotely log into MCC Systems to perform flight control opera�ons.

Other Sec�on C, 3.1.4 Opera�ons

C-27 7 Clarity Request the Government provide clarity on support requirements for Secret and TS/SCI in the MSSC.

For example, TS/SCI support is required 8 hours/day x 7 days/week and Secret is required 24 hours/day x 7 days/week.

See atachment L-9, Cer�fica�on and Cri�cal Skills Reference for the minimum number of clearances required to support COSMOS. The real- �me classifica�on requirements vary based on opera�onal needs and therefore the Government can't an�cipate any schedule consistency for support.

Other Sec�on C, 3.1.9 Metrics/Data and Reports

C-31 8 Clarity Request the Government confirm the SharePoint based tool and repository used on the incumbent MSOC program (myMSOC) will be transi�oned to the COSMOS contractor during Phase-In.

The MSOC tool will not be transi�oned to COSMOS. All contract data required for execu�on will be made available during phase-in.

Other Sec�on C, 3.2

UNIQUE MISSION

SYSTEMS SUPPORT

C-32 9 Request for addi�onal informa�on

Request the Government provide the inventory of all Configura�on Items managed by the contract in the MCCS, MTC, &

SVMF.

Please see Atachment J-9, Installa�on- Accountable Government Property and J-10 COSMOS So�ware List

Other Sec�on C, 1.

CONTRACT FOR

ORGANIZING

SPACEFLIGHT

MISSION

OPERATIONS AND

SYSTEMS (COSMOS)

I.22 NFS 1852.216-

80 TASK

ORDERING/DELIVERY

PROCEDURE (OCT

1996)

C-4 I-28

10 Request for addi�onal informa�on

With the removal of IDIQ and LOE tasking/cost, request the Government provide details on when ini�al task requests might be expected. With a projected award date of June 12, 2025, phase-in start of July 1, 2025 and base period/effec�ve start date of Oct 1, 2025, request the task requests be provided no later than start of phase-in.

The Government an�cipates that ini�al FY26 Task Orders will be provided to the Contractor during phase-in.

Other Sec�on C, 1.2.2 Mission Training Center (MTC)

C-6 11 Clarity Is there a difference between Mission Training Center (MTC) and Training Systems (TS) or are they synonymous?

Mission Training Center (MTC) refers to the facility and the Training System (TS) refers to the collec�on of systems used in facility opera�ons.

Other H.7 Associate Contractor Agreement (ACA) for COSMOS Ac�vi�es

H-11 12 Other Suggest NASA consider AEGIS be included as a key par�cipa�ng contractor based on the COSMOS dependency for the network services provided by AEGIS.

AEGIS will be added to clause H.7 ACA for COSMOS Ac�vi�es.

Other Standard Labor Categories, Technician I

J-12.8 13 Request for addi�onal informa�on

The labor category does not list the years of experience. Please provide to enable bidders to beter es�mate the

The Final RFP will include the following, "Experience for Technical I typically require 0-4 years of experience".

rate for this labor category.

Other DRD-COSMOS-0044 Configura�on Management Plan, Contents: ix

J-17.130 14 Clarity There is a DRD DRD- COSMOS-0004 Contract Configura�on Management Plan whose scope is “The plan shall describe the Contractor's management approach and planned implementa�on methods for accomplishing the Configura�on Management (CM) of the contract.” And contents that include “shall describe the Contractor 's CM organiza�on, policies, procedures, implementa�on approach, and control systems which are used to ensure proper contract CM ac�vi�es.”.

This seems to duplicate the following in the CM Plan DRD: Descrip�on of the Contractor's management approach and planned implementa�on methods for accomplishing the CM of the contract. Plan will

Please refer to the DRDs in sec�on J-17 of the DRFP and Final RFP when it's released.

describe the Contractor's CM organiza�on, policies, procedures, implementa�on approach, and control systems that are to be used to ensure proper contract CM ac�vi�es.”

In the final DRD for the Configura�on Management Plan, request the Government consider removing the duplicate requirement?

Other DRD-COSMOS-0044 Configura�on Management Plan, Contents

J-17.130 15 Clarity Request the Government confirm that the management and control of contract related documents, including DRDs, is governed by

DRD-COSMOS-0004

Contract Configura�on

Please see DRD-

COSMOS-0002

Contract Management Plans. Contract related documents, including DRDs are not considered to be configura�on items

Management Plan and that they are not considered CIs to be governed by the Configura�on Management Plan?

governed by DRD-

COSMOS-0044

Configura�on Management Plan.

Other DRD-COSMOS-0044 Configura�on Management Plan, Contents

J-17.130 16 Request for addi�onal informa�on

Request the Government provide a lis�ng of all current CIs maintained under the MSOC contract.

Please see Atachment J-10, List of COSMOS So�ware, which includes a list of all current CIs. This has been published in the Atachment Sec�on of this pos�ng.

Technical scenario

TA.3 Technical Scenarios

L-29; J-16.4 17 Clarity Please clarify if the Equipment Replacement Plan (DRD-COSMOS- 0048) reference is expected to be delivered with the proposal, or if it is due at Contract Start + 1 month as indicated in sec�on J.

DRD-COSMOS-0048,

Equipment Replacement Plan will be removed from Sec�on L.19.2, and will be required per the

DRD.

Sec�on L Proposal Instruc�ons

L.22 RESPONSIBILITY

CONSIDERATIONS -

VOLUME IV

L-48 18 Request for addi�onal informa�on

Request the Government provide the Prime/Subcontractor Iden�fica�on and SOW Division of Work Lis�ng (Atachment L-7).

The Government will include atachment L-7 as part of the Final RFP.

This has been published in the Atachment Sec�on of this pos�ng.

Sec�on L Proposal Instruc�ons

Volume V Model Contract, Atachment L-2 Small Business Tables

L-60 19 Clarity Table 2 (Lists of Small Business Subcontractors) requires that DUNS/CAGE codes be provided for each of the subcontractors.

Considering that the Federal Government switched from DUNS to a Unique En�ty Iden�fier (UEI) in 2022, please confirm that a UEI can be used in place of DUNS.

Yes, UEI can be used in place of DUNS. DUNS refences will be updated to UEI as part of the Final RFP

Sec�on L Proposal Instruc�ons

Atachment L-9 Cer�fica�on and Cri�cal Skills Reference

L-80 20 Clarity Request the Government confirm that the posi�ons listed in Atachment L-9 as requiring clearances are the only posi�ons that will require clearances on the contract. Or were these only specific to support to the SVMF? If these are only for the SVMF, what other posi�ons will require security clearances?

The Minimum Clearances list in L-9 contains all the expected Secret clearance requirements for

COSMOS.

Sec�on L Proposal Instruc�ons

L-6 COSMOS Past Performance Relevancy Matrix

Matrix 21 Clarity Request the Government confirm that the "dots" that are entered are reflec�ve of past performance applicability only and are not reflec�ve of the work that

L-6 COSMOS Past Performance Relevancy Matrix only reflects the past performance of the en�ty. Planned work for COSMOS is reported in L-7 is to be performed by that en�ty under

COSMOS.

Prime/Subcontractor Iden�fica�on and SOW Division of Work Lis�ng.