DRAFT_CAF_ADAIR_Tyndall_PWS_25_Jul_17.pdf

PERFORMANCE WORK STATEMENT

FOR

THE COMBAT AIR FORCES (CAF)

CONTRACT ADVERSARY AIR (ADAIR) SERVICES

TYNDALL AFB SUPPORT

SECTION A

DESCRIPTION OF SERVICES

1.0 SCOPE AND COMPLIANCE. The objective of the CAF ADAIR acquisition is to provide realistic advanced adversary air threats from commercial ADAIR sources to support pilot combat readiness training. For the purpose of this document and program, the terminology

“CAF” refers to both the Combat Air Forces and those Formal Training Units (FTU) supplying

Combat Air Forces. This PWS is the task order servicing 325 Fighter Wing (FW). This PWS is must be utilized concurrent with the core PWS on CAF ADAIR. The contractor will provide sorties to facilitate 325 FW and Tyndall AFB missions. ADAIR sorties will integrate as part of the 325 FW force in support of adversary air requirements. The Government will identify within Appendix I the required threshold and objective aircraft performance attributes needed to progressively expand aircraft system capabilities to replicate peer combatant threats. CAF

ADAIR contractors may support multiple customers/locations across the CAF with Operations and Maintenance services. The contractor will be responsible for all supplies and services to meet task order requierments, except for those outlined in the PWS Section C, Government-

Furnished Property and Services, regardless of on- or off-base beddown.

1.1 Tyndall Task Order. Contractors shall provide complete ADAIR services including, aircraft, pilots, aircraft maintenance, program and contract management to meet this PWS requirements. Tyndall ADAIR contractor operations are projected to be on-station.

1.1.1 Task Order requirements may expand over time to support additional CAF ADAIR requirements. Additional exercise support for events or an increased required level of support may be best suited to be met through a contractor deployment capability versus a continual presence but is at the discretion of the contractor.

1.1.2 325 FW will provide a GFR and GGR and alternates, responsible to the AMIC

Government Program Office (GPO), to surveil flight and ground operations, including deployment locations. GFRs and GGRs will surveil the Contractor using the criteria outlined in the core PWS, this task order, AFI 10-220, Contractor’s Flight and Ground Operating

Procedures, Quality Assurance Surveillance Plan (QASP), and the approved Quality

Management System (QMS).

3.0. OPERATIONS AND MAINTENANCE

3.1. Operations. Contractors will: Provide advanced ADAIR sorties to meet 325 FW Task

Order PWS requirements and integrate as part of the sponsoring unit.

3.1.1. Flying hour program. The projected combined 325 FW and 53 WEG ADAIR mission requirements are 2438 sorties, 2925 hours, 1.2 Average Sortie Duration (ASD). The table below provides the projected monthly sorties, maximum and the typical turn-pattern. Included within this projection are night flying requirements of two to three weeks per quarter. Flying hour program may deviate 5% any given month or annually based upon mission needs and operational scheduling constraints.

3.1.2. 325 FW Operations requirements:

Note: *See 325 Scheduling spreadsheet for more details concerning turn patterns. Max turn pattern identified is the baseline Tyndall requirements for line and FTU operations excluding any Combat Archer support identified below.

3.1.3. 325 FW FW Exercise requirements: The exercises below are built into the max turn-patters above. This will require the contractor to support split operations during these periods.

3.1.4. 53 WEG Requirements: The requirements below approximate an annual Combat Archer schedule. The contractor must be able to support these requirements concurrent to the 325 FW requirements above.

Month Projected

Sorties

Max Turn

Pattern*

Typical Turn

Pattern

October 72 2 T 2 2 T 2

November 120 4 T 4 4 T 4

December 166 8 T 6 6 T 6 / 4 T 4

January 172 10 T 10 4 T 4 / 2 T 2

February 140 8 T 8 8 T 8 / 2 T 2

March 158 8 T 8 8 T 8 / 2 T 2

April 110 4 T 4 4 T 4 / 2 T 2

May 120 6 T 4 2 T 2

June 136 6 T 4 4 T 4 / 2 T 2

July 118 4 T 4 4 T 4

August 64 2 T 2 2 T 2

September 102 8 T 8 2 T 2

Total 1478

Exercise Projected

Sorties

Max Turn

Pattern

Typical Turn

Pattern

Sentry Savannah 2 weeks (winter) 80 4 T 4 4 T 4

Sentry Savannah 2 weeks (winter) 80 4 T 4 4 T 4

Sentry Savannah 2 weeks (winter) 80 4 T 4 4 T 4

Exercise Projected

Sorties

Typical Turn

Pattern

Combined

Max*

Combined

Typical*

Combat Archer 2 weeks/Mid

Nov

80 4 T 4 8 T 8 4 T 4 / 6 T 6

Combat Archer 2 weeks/Mid

Dec

80 4 T 4 12 T 10 10 T 10

Combat Archer 2 weeks/Late

Jan/Feb

80 4 T 4 14 T 14 12 T 12

Combat Archer 2 weeks/Late

Feb

80 4 T 4 6 T 6 6 T 6

Notes:

* The combined max and combined typical columns represent the approximate maximum and typical turn patterns of the total Tyndall requirement combining Combat Archer and 325 FW requirements for the duration of the Combat Archer.

†Combat Archer may deploy annually for operations on the White Sands Missile Test

Range. The contractor is not required to support Combar Archer requirements off the Tyndall complex unless pursued through a contr

3.1.5. Total Flying Hour Program:

3.1.5.1. Due to the cyclic nature of both F-22 B-course requirements and Combat Archer, the contractor must be able to rapidly transition from low usage requirements, as low as 0 T 0 or 2

T 2, to maximum performance. Close long range scheduling with 325 FW schedulers will be required.

3.1.5.2. The contractor may be required to support 325 FW split ops (local and Sentry) concurrently with Combat Archer requirements.

3.1.5.3. Close coordination and workload sharing between the contractor and 2 FTS T-38

ADAIR operations will be required.

3.1.5.4. The contractor may on occasion be asked to support 3-go days due to F-22 FTU operations. Front line capacity will not exceed projected maximum turns.

3.1.6. Contractor shall:

3.1.6.1. Ensure all contract pilots are qualified to serve as Red 1 Mission Commander.

3.1.6.2. Ensure all contract pilots are qualified pilots to augment as Baron Controllers.

Combat Archer 2 weeks/Late

Mar

80 4 T 4 12 T 12 12 T 12

Combat Archer 2 weeks/Mid

Apr

80 4 T 4 8 T 8 6 T 4

Combat Archer 2 weeks/Mid

May

80 4 T 4 8 T 6 6 T 6

Combat Archer 2 weeks/Mid

June

80 4 T 4 8 T 8 8 T 6

Combat Archer 2 weeks/Mid

June

80 4 T 4 10 T 8 8 T 8 / 6 T 6

Combat Archer 2 weeks/Mid

July

80 4 T 4 8 T 8 8 T 8

Combat Archer† 1 week/Mid

Aug

80 0 T 0† 6 T 6 6 T 6

Combat Archer 2 weeks/Mid

Sep

80 4 T 4 6 T 6 6 T 6

Total 960

3.1.6.3. Provide an ICADs capable mission data file for each aircraft to support debrief requirements.

3.2. Contractor Flight Operations Plan (FOP). The Contractor shall operate their aircraft

IAW 14 CFR. Ensure adherence to Government approved Core Contractor Flight Operations

Plan IAW AFI 10-220, and augmented by the 325 FW Contractor Flight Operations Plan.

Contractor 325 FW FOP must specifically address the following:

3.2.1. Integration of operations with TAFBI 11-250, Airfield Operations Procedures and

Programs (23 June 2017).

3.2.2. Integration of flight operation with (INSERT TYNDALL LOCAL SAFETY

REGULATION).

3.2.3. A program to provide to the supported unit a complete ICADS-compatible mission file for all participating Contractor aircraft, not later than 30 minutes after the last Contractor aircraft landing, to support debrief requirements.

3.2.4. A program to integrate assigned pilots into 325 FW Baron Control checkout and scheduling.

3.2.5. Typical profiles will require contract aircraft to travel to airspace including, but not limited to W-470 and W-151 (primary), Tyndall MOA’s B, C, H, and E.

3.3. Ground Operations Plan (GOP). The Contractor shall maintain the aircraft IAW applicable FAA regulations and standards. Ensure the GOP includes all procedures required by

AFI 10-220, plus any hazardous ground operations not specifically mentioned in the core PWS but required to operate at Tyndall AFB. Ensure adherence to Government approved Core GOP in accordance with AFI 10-220, and 325 FW GOP.

3.3.1. Ensure contractor OL GOP is integrated with 325 MXG OI 21-101, Aircraft and

Equipment Maintenance Management (10 Jan 2017); 325 MXG OI 91-201, Transportation, Storage, and Handling of Egress Explosive Components (1 Oct 2012).

3.3.1.1. Maintenance personnel shall receive Tyndall AFB flight line maintenance support training as it pertains to flight line vehicle operations (day and night), maintenance safety requirements, Foreign Object Damage (FOD) prevention and reporting, flight line security, aircraft tow procedures including runway crossing, and all other subjects as deemed necessary by the 325 MXG to ensure safe flight line maintenance operations.

3.3.1.2. Acceptance and loading of equipment provided as Tyndall GFE in Appendix D.

3.3.2. Integration of scheduling with 325 OG OI 11-1, 325th Fighter Wing Wing Scheduling (1

Mar 2011).

3.3.2.1. The normal schedule for flight operations is Monday through Friday, 0600 to 2000 local time. The weekly schedule will will identifyidentify when operations are required outside of this period or are of longer duration. After Range Wars, the squadron scheduling offices will coordinate directly with each other and the contractor to finalize requirements by 1630L on the final duty day of the week, not to include UTA weekends. The contractor will publish its weekly schedule after receiving final change requests from the supported squadrons.

3.3.2.2. The government will generally finalize the schedule 24 hours in advance. Any changes to the following day’s schedule will be coordinated a minimum of 12 hours prior to execution.

The contractor will make every attempt to accommodate changes occurring between 12 and 24 hours prior to execution (defined as aircraft declared “crew ready” by maintenance).

3.3.2.3. The Government will give the Contractor 24 hours advance notice before assigning any additional tasking for aircraft. Additional tasking is defined as a new requirement, not previously scheduled during the weekly scheduling period.