PWS Break Up RFI - Amendment 1.docx

REQUEST FOR INFORMATION – AMENDMENT 1

Subject: North American Aerospace Defense Command (NORAD) Cheyenne Mountain Complex (NCMC) Integrated Tactical Warning/Attack Assessment (NCMC-ITW/AA) and Space Support Contract

FA8723-23-R-0012 – Support Contract PWS Break-Up RFI Amendment 1 RFI Initial Question & Answers and Question Deadline Extension POCs: Lt Col Jessica Morgan (PM) | Capt Jexenia Bennett (Contracting)

This is an amendment to the above reference RFI. This is not a solicitation or a new RFI. This amendment and its parent RFI do not commit the Government to contract for any supply or service. Furthermore, the Government is not seeking proposals at this time and will not accept any unsolicited proposals. Please acknowledge that you have seen this amendment in any final submission provided in response to this RFI.

This amendment is being published for two purposes. The first, the extend the secondary question deadline listed in the original RFI from 15 September 2023, 1400, MST to 18 September 2023, 1700, MST. The second is to provide the answers to all questions received in the first round of questions. If you have additional questions that are not answered in the original RFI or below, please submit them in accordance with the RFI instructions, in writing via e-mail to Capt Jexenia Bennett at jexenia.bennett.1@spaceforce.mil.

1. Are all the Mission Assurance Centers under a common architecture and managed at the enterprise level, or is each center managed and administered locally?

Both; all MACs are locally administered, however, only one MAC has enterprise-wide capability.

2. How much, if any, of the MAC systems are being considered for migration to a secure cloud environment?

At this time the Government does not have a requirement to migrate to a cloud architecture

3. Are there other roadmap activities that we should consider when making recommendations for this PWS disaggregation?

Yes, generally the following are assumed to impact life cycle sustainment: periodic cybersecurity requirements, modularization projects, and technical refreshes.

4. To provide offerors with the necessary information to propose innovative and cost-efficient contract structures, will the Government please provide the CLIN structure and funding for each CLIN (by year) under the current NISSC II contract?

The Government will provide the outline of the CLIN structure (Name/description, etc.); however, the Government will not release the funding and financial information as those are contract sensitive. Contract CLIN Outline will be included at the bottom of this amendment.

5. After reviewing the RFI instructions, it was not clear where the management concepts are listed that was mentioned in Section 3.0 Requested Information: It states, “The Government is seeking to identify vendors who have experience with any or all of the contract management concepts listed above.” Could the Government please clarify which contract management concepts being referred to within the RFI? Please advise. Thank you.

The phrase “contract management strategy” is intended to mean the ability of a company to do the following:

a) Manage more than one contract, subcontract, and/or task order that are in support of a single Government program.

b) Establish and execute business practices through the letting of contracts and agreements that enable productive cooperation between multiple industry partners, such as the ability to team with other companies who will be required to integrate, sustain, and support technology of both companies as part of the Government’s program management strategy.

Example: A single large contract divided into three separate, but complementary contracts:

a) One contract for operations and maintenance for on-site communication and mission system infrastructure elements

b) One contract for the development, security, operation, and integration of software tools and training capabilities; to include management of cybersecurity standards, engineering, and sustainment tools, etc.

c) One contract for software modernization, deployment, and sustainment of core mission systems

6. To help us provide a better recommendation and meet the Government’s goals, are you able to share why you are considering breaking up the NISSC scope into separate contracts?

The consideration of breaking-up the NISSC scope into more narrow and discrete contracts is one of multiple options being examined as part of strategic planning on behalf of the program management office. Disaggregating the larger contract may offer efficiencies in management, as well as execution and delivery, for both the Government and Industry. This RFI seeks to determine the feasibility of that concept in general and gather insight about how that concept could be defined and scoped.

Contract CLIN Outline