GEARSS_II,_Gov_Responses_to_Draft_RFP_CRM.pdf

Page #, Section #, Paragraph #

Was (Original Language) ACTION (Suggested Change) Rationale Government Response

1 Pages 10‐11, Section 4.2.2.1, Paragraph 1 (CLIN x001)

AND

Pages 11‐12, Section 4.2.3, final bullet

The offeror shall include any transition costs for DCO in this CLIN respective to the year the DCO will transition (~Feb 2021). The Government anticipates a 90 day transition period for DCO activities.

Please clarify the exact date for DCO transition to ensure pricing is accurate. In addition, we would recommend separate CLINs for DCO transition that are similar to initial contract phase‐in (CLINs 0004, 0005), with a services CLIN that is not included in the Total Evaluated Price (TEP) for the same reason that other phase‐in costs are not included in TEP. As an alternative, all DCO support could have a separate CLIN structure, to include phase‐in.

Ensures accurate pricing and fair competition.

The current estimate for DCO transition, as described in the RFP, includes the estimated transition month (~Feb 2021), and details the need for a transition period, which the Government anticipates to be approximately 90 days.

The incumbent DCO contractor is a large business, not qualified to prime GEARSS II, therefore there is no incumbent advantage to a lower DCO phase‐in price. The transition does not include ODCs and the primary tasks are on the DCO contract, the GEARSS II contractor is only responsible for ingesting the DCO labor, eliminating the need to price this support separately.

2 Page 4, Section 3.8.4, Table L‐2 Page limitations for the Technical Proposal (subfactors 1‐3) is set at 15 pages.

Please consider increasing the page limitation to 20 pages.

Allow enough space to identify technical approach.

The Government anticipates 15 pages is sufficient to describe the offeror's technical approach.

3 Page 63, PWS Section 3.2.1, second note NOTE: Once the Government transitions from the NAO to the GSS position, the contractor shall provide trained, proficient and certified GSS crew members IAW published training standards and guides. The Government will provide all applicable standards and guides when the transition occurs.

With the undefined date for OCX transition and a long time period for OCX to be operationally accepted, will the contractor be required to staff both NAOs and GSSs during this acceptance period or will the NAO role transition to GSSs without any overlap? Also, will GSS crew member training materials be provided by the Government or will offeror need to develop training standards and guides?

Defined scope is unclear. The GEARSS II contractor is expected to provide NAO, RST, and DCO support throughout the OCX trial period, prior to Ops Acceptance. The OCX contractor is incentivized to transition the OCX support activities to the GEARSS II contract as early as possible, but the OCX contractor will provide GSS and Cyber SME support until that transition occurs.

All training materials will be provided as GFI and the contractor will then be required to maintain those documents as described in the PWS.

FA8823‐18‐R‐0007, GEARSS II ‐ DRAFT RFP

Comment Resolution Matrix

Section #, Paragraph #

Was (Original Language) ACTION (Suggested Change) Rationale Government Response

FA8823‐18‐R‐0007, GEARSS II ‐ DRAFT RFP

Comment Resolution Matrix

4 Page 51, PWS Section 1.2, 7th paragraph OCX is anticipated to be delivered October 2022 (Objective)/October 2023 (Threshold). Once delivered, OCX and OCX will perform dual operations until the operational community formal accepts OCX. Additionally, OCX interim contractor support (ICS) is anticipated to begin when OCX is delivered and possible extend beyond operational acceptance (~18‐30 months in length).

Will the GEARSS II contractor be required to provide sufficient manning for 24/7 NAO and DCO Ops for both AEP and OCX after transition and through formal acceptance?

Defined scope is unclear. The GEARSS II contractor is expected to provide NAO, RST, and DCO support throughout the OCX trial period, prior to Ops Acceptance. The OCX contractor is incentivized to transition the OCX support activities to the GEARSS II contract as early as possible, but the OCX contractor will provide GSS and Cyber SME support until that transition occurs.

5 Page 74, PWS Section 3.5, first note NOTE: The DCOM is synonymous with the Cyber SME position as part of the OCX operations staff. The tasks below apply to the OCS DCOM and the OCX Cyber SME.

Will the GEARSS II contractor be required to staff both DCOMs and Cyber SME positions during this OCX acceptance period or will the DCOM role transition to Cyber SMEs without any overlap?

Defined scope is unclear. The GEARSS II contractor is expected to provide NAO, RST, and DCO support throughout the OCX trial period, prior to Ops Acceptance. The OCX contractor is incentivized to transition the OCX support activities to the GEARSS II contract as early as possible, but the OCX contractor will provide GSS and Cyber SME support until that transition occurs.

6 Page 55, Section 1.3, 6th bullet … all on‐site GCS contractors. … all on‐site GEARSS contractors. Emergency Management requirements will be performed for GEARSS contractor personnel.

PWS updated.

7 Page 55, Section 1.3 and Page 85, Section 4.1 COSPM support identified Does GEARSS II scope include COSPM support? Defined scope is unclear. PWS updated to remove COSPM support.

8 General Would the Government provide a list of proprietary software currently used on the GEARS contract?

There is no proprietary software currently used on the GEARSS contract.

9 General Would the Government provide a list of all Software used on the GEARS contract?

Per Atch 3: Rights in Data, there are no software licenses required for the GEARSS II contract.

The PWS defines the tool/software required.

10 General Will the Government provide the delivery date of OCX standalone simulators that will require GEARSS II support?

OCX is anticipated to be delivered October 2022 (Objective)/October 2023 (Threshold).

All applicable HW/SW will be provided to the GEARSS II contractor after OCX Ops Acceptance.

Section #, Paragraph #

Was (Original Language) ACTION (Suggested Change) Rationale Government Response

FA8823‐18‐R‐0007, GEARSS II ‐ DRAFT RFP

Comment Resolution Matrix

11 General 1. Can the Gov’t provide current statistics on activates to date?

a. Amount of times traveled to perform maintenance on remote sites

b. Average hours to fix down equipment

c. Average hours to travel to remote site before maintenance occurs

d. Average hours per day per requirement to be met

The statistics for maintenace activities are part of another sustainment contract.

The GEARSS II contractor must ensure remote site maintenance activities are IAW PWS paragraph 3.3.

12 Are there any undisclosed CBAs at any locations?

No, there are no CBAs applicable to this solicitation.

13 Are there any vehicle requirements for contractor?

All information pertaining to vehicles is included in the Host Tenant Site Agreements. There are government‐ provided vehicles at each of the remote sites.

14 Are there any personal protective equipment requirements for contractor?

The personal protective equipment requirements are all IAW OSHA standards, and are specified in the Host Tenant Site Agreements.

15 Are there any certifications (Cisco/CompTIA) requirements for contractor?

The only certifications required are those identified in the PWS or compliance documents (e.g. NAO PTS/PTG, DCO Crew Binder)