Questions_and_Answers_7.21.pdf

1. PWS 3.1.1.3.4: “Availability to troubleshoot and arrive at a diagnosis within twenty (20) minutes of any ground system failure during mission debrief or analysis.”

Question: At sites that have 20 or more ICADS and 1 fails, will troubleshooting take priority over live monitor or concurrent debrief support?

Answer: Live monitor and debrief support take priority over troubleshooting provided there is an alternate ICADS/debriefing station available. PWS paragraph 3.1.3.6.1 updated to clarify this priority.

2. PWS 3.1.3.3.3: "Perform role of TDLM IAW AFI 11-261" This entails formal training, usually only offered to active duty.

Question: Will the Government provide formal training?

Answer: The government will sponsor contractor personnel for the TDLM training

(similar to other government training courses) but selection to attend government training courses is outside the purview of the CO/COR. Selection or Non-selection for a government training course shall not relieve the contractor of requirements in this PWS. Selection for courses with high availability (i.e., TDLM 101 and TDLM 102) is more likely than advanced courses with fewer slots. PWS updated to add new paragraph in Appendix 7, para 1.14.

3. PWS 3.1.3.6.1 “In the event of a malfunctioning GS, the contractor shall respond within 20 minutes of notification of the malfunction. The contractor shall restore the GS to full functionality not later than 30 minutes after arrival. If the contractor is not able to repair the malfunction and the aircrew is not able to accomplish an effective mission analysis, the COR will use these response/restore guidelines to determine if the contractor shall be held responsible for the malfunction.”

Question: Where can the “response/restore guidelines” be found?

Answer: The response/restore guidelines are listed in the same paragraph (PWS 3.1.3.6.1). i.e., respond within 20 mins and restore nlt 30 mins. No PWS change required.

4. PWS 3.1.15.1 “Datalink Support – At the locations that support datalink terminals (Link-16, SADL, BOSS, JRE, etc.), the contractor shall provide O&M level maintenance on subject systems as directed.”

Question: What are the number and locations of these (Link-16, SADL, BOSS, JRE, etc.)

systems?

Answer: The PWS Appendix for each site identifies whether datalink support is required. In each appendix, section 2, 9th row in the table. There are currently 8 sites (plus an optional site) showing support required for datalink systems.

5. PWS 3.1.16.1 “LNCS” –

QUESTION: Can the Government provide a definition for this? SEE BELOW

6. PWS 3.1.16.2 “NICE” –

QUESTION: Can the Government provide a definition for this? SEE BELOW

7. PWS 3.1.16.3 “DIS/GUI” –

QUESTION: Can the Government provide a definition for this? SEE BELOW

8. PWS 3.1.16.4 “PETS” –

QUESTION: Can the Government provide a definition for this? SEE BELOW

ANSWER: 5-8. These software products are the Live-Virtual-Constructive systems provided by AFRL and currently located only at Shaw AFB. PWS

Paragraph 3.1.16 (and subs) and Appendix 6 updated to show the definitions.

Definitions for the acronyms are:

- LNCS (Live, Virtual, and Constructive Network Control Suite)

- NICE (Network Integrated Constructive Environment)

- DIS/GUI (Distributed Interactive Simulation/Graphical User Interface)

- PETS (Performance Evaluation and Tracking System)

9. PWS Appendix 8F – Shaw AFB, SC.

a. “2. Site Specific Equipment Requirements”

i. “Off-Site Facilities – No”

Question: Should Off-Site Facilities include Charleston AFB?

ANSWER: Yes, off-site facilities should include the comm rack at Charleston. PWS

Appendix 8F updated to show this.

10. PWS Appendix 8L – Dyess AFB, TX.

a. “1. Site Specific Mission Requirements”

i. “Pod loading - Yes, contractor supported, but only for exercises w/hosted DACT units (all type fighter jets).”

b. “2. Site Specific Equipment Requirements”

i. “Pods - No”

QUESTION: How will we support pod loading if there will be no pods or pod support equipment at

Dyess?

ANSWER: Pod loading is not required at Dyess AFB. PWS Appendix 8L updated to remove this requirement.

11. QUESTION: RFP L.6.3.5 – Question: Please confirm that the Contractor Quality Manual

(PWS 3.1.12.5) and the Contractor Quality Control Plan (PWS 3.1.12.5) will not be part of the 40 page count limit for Volume I - Technical?

ANSWER: Section 3.1.12.5 of the PWS has been revised. Verbiage requiring the Contractor

Quality Manual and Contractor Quality Control Plan to be submitted as part of the proposal have been. The Contractor Quality Manual and Contractor Quality Control Plan will be a separate submission in accordance with the PWS and will not be part of the 40 page count limit for

Volume I-Technical.