Attachment_1_-_PWSv2_29 Oct 2021.pdf

RFP FA2860-21-R-0013

ATTACHMENT 1

PERFORMANCE WORK STATEMENT

FOR

EXECUTIVE AIRLIFT FLIGHT DISPATCH

Oct 29, 2021

Contents

1. Description of Services

1.1. Scope

1.2. Tasking POCs

1.3. Mission Statement

1.4. Mission Essential Contractor Services

1.5. Task Descriptions

1.5.1. Flight Dispatch Services (TASK 1)

1.5.1.1. Flight Planning Analysis (Pre-Mission Execution)

1.5.1.2. Diplomatic Clearances

1.5.1.3. Mission Planning Package

1.5.1.4. Mission Review

1.5.1.5. Mission Planning Package Update

1.5.1.6. Calculate Final TOLD and W&B

1.5.1.6.1. Configuration and Vertical Profile Hierarchy.................................………………………...9

1.5.1.7. Flight Plan Filing

1.5.1.8. Mission Planning Package Update (“Paper the Crew”)

1.5.1.9. Dispatcher-to-Pilot Briefing

1.5.2. En-route Flight Monitoring (TASK 2)

1.5.2.1. Weather Assessment

1.5.2.2. Re-planning

1.5.2.3. Safety of Flight

1.5.2.4. En-route Mission Planning Package Update

1.5.3. Flight Operations Service Management (TASK 3)

1.5.3.1. ACARS Ground Host Processing

1.5.3.1.1. Technical Support

1.5.3.2. SATCOM ORT Management

1.5.3.3. Boeing Onboard Performance Tool (OPT) on Apple iPad

1.5.3.3.1. OPT Airfield Database Subscription

1.5.3.3.2. OPT Aircraft Database Subscription

1.5.3.3.3. OPT Administrative Services Subscription

1.5.3.4. Locator Transmitter (ELT) Management

1.5.3.5. Identification Friend or Foe (IFF)/Mode S ACARS (ICAO) ID Management

1.5.3.6. SARB Support

1.5.3.7. Support for CNS/ATM and New Aircraft Technologies

1.5.3.7.1. Controller-Pilot Data Link Communications (CPDLC) Management

1.5.3.8. EGPWS Database Management

1.5.3.8.1. EGPWS Database Annual Subscription

1.5.4 FMS Navigation Database (NDB)

1.5.4.1 FMS Navigation Database (NDB) Annual Subscription

1.5.4.2 FMS Navigation Database (NDB) Off Cycle Updates

1.5.4.3 Required Navigation Procedures (RNP) Authorized Requirement (AR) Validation

1.5.5. Dispatch Familiarization Course (Task 4)

1.5.6. Phase-In

1.5.7. Phase-Out

1.5.7.1. Phase-Out Program

1.5.7.2. Description

1.5.7.3. Inclusions

1.5.7.4. Deliverable

1.5.7.5. Cooperation

2. Service Summary

3. General Information

3.1. Program Management Support

3.1.1. Risk Management Program

3.1.2. Program Management POC

3.1.3. Key Contact List

3.1.4. Contractor Manpower Reporting

3.2. Security Requirements

3.2.1. Access to Installation During Force Protection condition (FPCONS)

3.2.2. Property Protection

3.2.3. Contractor Working in Controlled or Restricted Areas

3.2.4. Access to Government Facilities with Controlled or Restricted Areas

3.2.5. Contractor Consent to Background Checks

3.2.6. Citizenship

3.2.7. Badges

3.2.8. Safeguarding For Official Use Only (FOUO) and other Unclassified Information

3.2.9. Information Assurance

3.2.10. Communications Security

3.2.11. Privacy Act

3.3. Place of Performance

3.4. Hours of Operation

3.5. Administrative Items

3.5.1. Dispatchers

3.5.2. English Language

3.5.3. Conduct

3.5.4. Access

3.5.5. Original Equipment Manufacturer (OEM) Data

3.6. Publications and Services

1. Description of Services

1.1. Scope

The purpose of this Performance Work Statement (PWS) is to define the tasks to be accomplished for Flight Dispatch of four Boeing 757-200 (designated C-32A), four Boeing 737-700 (designated C-40B) and seven Boeing 737-700 (designated C-40C) Commercial Derivative Aircraft (CDA). Although Very Important Person Special Air Mission (VIPSAM) operations are not identical to commercial operations, the geographical scope is worldwide and the level of service provided to Federal Aviation Regulation (FAR) Part 121 commercial ops is the most rigorous and thorough. The contractor shall provide flight dispatch services comparable to existing commercial airline 24/7/365 world-wide operations. This PWS describes the efforts and tasks that shall be performed by the contractor for the organizations listed below.

Performance shall be at the contractor’s facility. This PWS covers the United States Air Force (USAF) C-32A, C-40B and C-40C fleet aircraft, hereafter referred to as “Covered Aircraft”. The covered aircraft include:

- (4) Boeing 757-200 (designated C-32A) o 4 at KADW (Andrews 89 AW, 1 AS), AMC 98-0001, 98-0002, 99-0003, 99-0004

- (4) Boeing 737-700 (designated C-40B) o 4 at KADW (Andrews 89 AW, 1 AS), AMC 01-0040, 01-0041, 01-0015, 02-0042

- (7) Boeing 737-700 (designated C-40C) o 3 at KADW (Andrews 201 AS), ANG 02-0201, 02-0202, 02-0203 o 4 at KBLV (Scott 932 AW), AFRC 05-0730, 05-0932, 05-4613, 05-0540

1.2. Tasking POCs

Tasking agency POCs are:

Designation Type IKO Base AS AW MAJCOM # Aircraft COR/POC C-32A 757-200 KADW Andrews 1 89 AMC 4 89 OG/OGP C-40B 737-700 KADW Andrews 1 89 AMC 4 89 OG/OGP C-40C 737-700 KADW Andrews 201 113 ANG 3 201 AS/DOF C-40C 737-700 KBLV Scott 73/54 932 / 375 AFRC/AMC 4 932 OSF/OSO

1.3. Mission Statement

The mission of the covered aircraft is to provide safe, comfortable, and reliable worldwide transportation for executive level Government officials and Department of Defense (DOD) civilian and military senior leaders. This includes the President of the United States (POTUS), the First Lady of the United States (FLOTUS), Vice President of the United States (VPOTUS), Secretary of Defense (SECDEF), Secretary of State (SECSTATE), Congressional Leaders, other Secretarial and Cabinet leaders, US Combatant and Component Commanders from all services, foreign heads of state, Office of the Secretary of Defense (OSD), White House Military Office (WHMO), foreign dignitaries, senior executive, Congressional and senior military leaders, and their respective staff. These missions are collectively referred to as Executive Airlift

(EA).

1.4. Mission Essential Contractor Services

The following tasks are designated as mission essential.

Task 1: Flight Dispatch Services Task 2: En-route Flight Monitoring Task 3: Flight Operations Service Management Task 4: Dispatch Familiarization Course

1.5. Task Descriptions

The PWS includes the following tasks: flight dispatch services, en-route flight monitoring, flight operations management, and dispatch familiarization course. The contractor shall provide all services comparable with the Federal Aviation

Administration’s (FAA’s) FAR 121 standard.

1.5.1. Flight Dispatch Services (TASK 1)

Flight dispatch includes the following subtasks: flight planning analysis, diplomatic clearance, Mission Planning Package delivery, mission review, Mission Planning Package update, calculating final Take Off and Landing Data (TOLD) and Weight and Balance (W&B) data, and “Paper the Crew.” These products will be available on the dispatcher’s website as well as uploaded to the appropriate mission folder on a pre-coordinated file sharing site (Currently the 89th uses https://www.box.com). In addition, dispatcher shall provide the following on their website for each mission:

• Mission Itinerary

• Diplomatic log with diplomatic clearance numbers, prior permission required

(PPR’s), and slot times. Contractor shall obtain slot times when required.

Contractor will obtain PPR’s only at the request of the Aircraft Commander.

• A copy of the mission’s Aircraft and Personnel Automated Clearance System (APACS) message

• Out, Off, On, and In (OOOI) Time report

• Airfield Suitability Report

• Max Weight Takeoff and Landing Report (TLR) Files

• Draft route plots

• Secure messaging capability between unit and dispatch (Comm Center)

• Contact info for all pilots in the unit as well as dispatcher’s pertinent contact information

• Document tab with appropriate handbooks, manuals, user guides, NDB airports and procedures, flight plan knowledgebase, etc.

Contractor shall provide a mobile device application (such as an iOS web app) with access to the same functions and information as the dispatch website and have the application approved by AMC for mobile device management.

1.5.1.1. Flight Planning Analysis (Pre-Mission Execution)

Contractor shall receive tasking from the tasking agency Point of Contact (POC).

Contractor shall perform pre-execution mission analysis in order to ensure tasking is executable. Upon receipt of a tasking from the tasking agency, the contractor shall:

• Perform an analysis of airfields and routes to be used on each sortie for the purposes of verifying airfield operational and physical suitability for listed aircraft type

• Establish the suitability of the route of flight based on historic wind data

• Identify limiting factors relative to aircraft operations and performance

• Ensure Arrivals and Departures meet USAF Terminal Instrument Procedures

(TERPS) requirements.

The analysis and route development shall include potential/proposed en-route and destination alternate airfields (chock to chock). The analysis will be based on and compliant with:

• Tasking Agency direction

• AFMAN 11-230, 11-202V3, 11-202V3 AMC SUP, 11-2EAV3, and

DoD Foreign Clearance Guide (FCG)

• Aircraft operations manuals and performance data

• Aircraft Takeoff & Landing Data (TOLD) and Weight & Balance (W&B) https://www.box.com/

• Extended Range Operations (EROPS)

• Engine-Out Drift down

• High Terrain Decompression and or/engine out escape routing. Escape planning shall be compliant with AFMAN 11-202V3 Oxygen and Pressurization Requirements.

o If terrain clearance presents a problem for either engine loss and/or decompression, determine whether or not an alternative route can be planned and flown that avoids the risk. If the alternative route, however, is greater than 20 minutes more time than the original, or the aircraft cannot fly this route without a fuel stop, the operating squadron (AMC, AFRC, and ANG) must be consulted on their opinion.

• Communication, Navigation, Surveillance/Air Traffic Monitoring (CNS/ATM) equipment compliance

• Flight crew operations manuals

• Central Flow Management Unit (CFMU) validation when applicable

• DOD Flight Information Publications (FLIP) o Foreign Clearance Guide (FCG) o FLIP IFR Supplements o FLIP Area Planning o Airfield Suitability and Restrictions Report (ASRR) o Giant Report o DOD Notice to Airmen (NOTAMS) o USAF/Air Force Reserve Command (AFRC)/Air National Guard (ANG)

Air Force Instructions (AFI)

• Diplomatic Clearances

• Suitable approach/departure procedures o Contractor shall request Foreign Terminal Instrument Procedure (FTIP) Reviews for approach/departure procedures when required (No DoD approach exists and airfield/country is not on the DoD Accepted Host Nation List).

• Applicable Jeppesen (and/or local) airspace/airfield charts and procedures

1.5.1.2. Diplomatic Clearances

Contractor shall create and sustain a program for obtaining and maintaining diplomatic clearances. Upon receipt of a tasking, contractor shall obtain required diplomatic clearances and/or use provided/projected clearances. The contractor shall maintain an Aircraft and Personnel Automated Clearance System (APACS) account with read/write access. Government will provide access or view permissions for each USAF/AFRC/ANG APACS account to the contractor. The contractor shall inform tasking agency POC promptly of any potential problems identified with securing diplomatic clearances.

1.5.1.3. Mission Planning Package

Upon completion of analysis contractor shall generate Mission Planning Package.

The Mission Planning Package shall include:

• Mission Itinerary

• Jeppesen Computer Flight Plan (CFP), or equivalent, for each leg to include

Equal Time Point (ETP) Data, 180 min EROPS Range Summary, EROPS entry point, EROPS exit point, and Critical Fuel Summary on Oceanic legs.

• High terrain decompression and/or engine out escape routing when required

• Diplomatic log with diplomatic clearance numbers, PPR’s and slot times

(Contractor shall obtain slot times when required. Contractor will obtain PPR’s only at the request of the Aircraft Commander).

• A copy of the mission’s APACS message

• A copy of the “Out, Off, On, and In” report (OOOI report)

• Airfield Suitability Report

• A consolidated analysis of aircraft performance capability at each location to include at a minimum: Max Weight Takeoff and Landing Report (taking into account the highest/worst case all engine operating (AEO) climb gradient in addition to OEI climb gradient—List AEO gradient used), Engine Failure Procedures (EFP), weight requirements to meet specified One Engine Inoperative (OEI) Missed Approach Climb Gradient at destination, factored landing distance, and demonstrated landing distance.

• Draft route plots

1.5.1.4. Mission Review

Contractor shall perform a continuous review of each sortie up to and including 48 hours prior to the date and time of mission departure. The review shall confirm all aspects of the mission planning package and provide recommended solutions for any outstanding items. Any weather patterns that may impact mission execution shall be analyzed to ensure each sortie can be successfully completed within the allotted mission timing.

1.5.1.5. Mission Planning Package Update

Upon completion of mission review the contractor shall update the Mission Planning Package. Contractor and tasking agency POC shall have a shared responsibility discussion with the goal of arriving at routing decisions.

1.5.1.6. Calculate Final TOLD and W&B

Contractor shall use the most current forecast conditions to calculate TOLD and W&B data on the day of flight. Provided in the “Day of Ops Paperwork” the Takeoff and Landing Report (TLR) should include at a minimum:

• TLR Takeoff Data Section (MAX TEMP TLR) to include:

o Dispatcher Input Conditions, Remarks Section, and ACARS Runways.

o Takeoff Data and Configuration. This will be a “MAX TEMP TLR” for the

Predicted Takeoff Weight (PTOW) to include the appropriate EFP. Under normal conditions, the MAX TEMP TLR should include a range of sections for the following configurations:

DRY RWY – PTOW – ENG A/I OFF

DRY RWY – PTOW PLUS 2500 – ENG A/I OFF

JOSEPH FLYNN

Removed.

DRY RWY – PTOW PLUS 2500 – ENG A/I OFF – 10KT TW

WET RWY – PTOW – ENG A/I ON 10C AND BELOW

WET RWY – PTOW PLUS 2500 – ENG A/I ON 10C AND BLW

WET RWY – PTOW PLUS 2500 – ENG A/I ON 10C AND BLW –

10KT TW

o Adjust configuration range as appropriate (Contaminated RWY, etc).

o TLR Takeoff Data shall ensure aircraft can meet or exceed 200 ft/nm OR the published climb gradient, whichever is higher, with all engines operating (AEO) to the enroute structure (AFMAN11-202V3, 5.8) Contractor shall ensure compliance with the highest/worst case

AEO climb gradient for the planned and actual runway (SID/ODP/DVA etc.) List the AEO climb gradient used for each RWY Takeoff calculation.

o TLR Takeoff Data shall provide a contingency procedure (EFP) to account for one engine inoperative (OEI) on takeoff.

• TLR Landing Data Section to include:

o Dispatcher Inputs: Display of the dispatcher’s weather and weight inputs.

o Remarks Section: Reserved for handwritten information o Normal Landing Data for Flaps 30 / 40 / 15: This section will show compliance with three items:

Landing distance field length required by 14 CFR Parts 25.125 and

121.195 Balked-landing all engine operating climb gradient of 3.2% required by 14 CFR Part 25.119 One engine inoperative approach climb gradient of 2.1% required by 14 CFR Part 25.121 o Factored Landing Distance o Demonstrated Landing Distance o Weight requirements to meet specified OEI missed approach climb gradients.

Aircraft Communication Addressing and Reporting System (ACARS) menus shall display aircraft Performance and W&B function for pilot interface. ACARS Takeoff Conditions page will allow pilot input of AEO Climb Gradient/Altitude for the selected RWY when calculating Takeoff Data. Takeoff Conditions page will allow manual pilot input of acceleration and thrust reduction altitudes when calculating TLR in order to satisfy Noise Abatement Departure Procedures when required (Default/Optimum assumed when left blank). Takeoff and landing Conditions shall include contaminated takeoff and landing data logic and labels that include selection options for TALPA/RCC, Runway condition description, and pilot reported braking action IAW Runway Condition Assessment Matrix (RCAM)—C-32/C-40 only. Pilot Reported Braking Action will include None, Good, Good to Medium, Medium, Medium to Poor, Poor, and Nil. The aircrew shall have the ability to print results using the ACARS Printer. Contractor will also provide a desktop tool/website to be used on a personal computer or tablet with the same functionality/logic as ACARS for calculating TLR Takeoff Data. The website will allow load sheets to be saved as a ‘scenario’ and then uplinked to the airplane on the day of flight.

1.5.1.6.1 Configuration and Vertical Profile Hierarchy

• Contractor shall determine and present takeoff data according to the following hierarchy. The process is over-ridden when inoperative systems, runway conditions, or pilot-forced ACARS selections are introduced.

Configuration Hierarchy

1. TO-2-RDCD-BLDS ON

2. TO-2-FULL-BLDS ON

3. TO-1-RDCD-BLDS ON

4. TO-1-FULL-BLDS ON

5. TO-RDCD-BLDS ON

6. TO-FULL-BLDS ON

7. TO-FULL-BLDS OFF

Vertical Profile Hierarchy

1. CLB2

2. CLB1

3. CLB

4. CLB FUMS to 2k-10k (in 500 ft increments)

a. Accel Alt left at default

b. Thrust Reduction Alt left at default

5. CLB V2+20 (increase accel alt) to 1.5k-10k (in 500 ft increments), then FUMS to 10k

a. Thrust Reduction left at default

6. CLB V2+20 (increase accel alt AND thrust reduction alt) to 1.5k-10k

(in 500 ft increments), then FUMS to 10k Note: FUMS = Flaps Up Maneuvering Speed

• Dispatch Default Takeoff Settings o Bleeds - ON o Flaps –

C-40B/C: Optimized between 1-25 with 5 preferred (or as determined by unit)

C-32A: Optimized between 1-20 with 15 preferred (or as determined by unit) o Improved Climb – Blended-Improved, if optimum o V1 – Optimized between V1STD and V1MAX o Reverser Credit – Available for Contaminated Takeoff Only

(Applied on when two thrust reversers are available) o Accel/Stop Margin – 1,000 feet for all derated & reduced thrust takeoffs o Acceleration Altitude – 1,000 AGL o Thrust Reduction Altitude – 1,000 AGL

• Dispatch Default Landing Settings o Flaps – 30 o CAT II/III Autoland – Available o Auto Brake Options – Available o Reverser Credit – NO

1.5.1.7. Flight Plan Filing

Contractor shall address filing issues and negotiate with Air Traffic Control (ATC) at all times for the tasking agency and successfully file a flight plan within five minutes of the crew notifying contractor of any issue.

1.5.1.8. Mission Planning Package Update (“Paper the Crew”)

Contractor shall complete and transmit via email, as well as upload to user desired file sharing site (i.e. Box), an updated Mission Planning Package to the aircrew up to and including 4.5 hours prior to takeoff. The updated package shall confirm all aspects of the Mission Planning Package and provide recommended solutions for any remaining outstanding items. Any updated weather patterns that may impact mission execution shall be analyzed to ensure each sortie can be successfully completed within the allotted mission timing. The following new items shall be added:

• Complete and file DD Form 1801 with ATC

• Jeppesen Computer Flight Plan (CFP), or equivalent, to include Equal Time

Point (ETP) Data, 180 min EROPS Range Summary, EROPS entry point, EROPS exit point, and Critical Fuel Summary on Oceanic legs. The flight plan will avoid severe turbulence, severe icing, and volcanic ash. If a severe turbulence SIGMET must be penetrated, provide a meteorologist forecast for expected flight conditions for the category of the operating aircraft (intent to know if the SIGMET should be considered restrictive or not).

• High terrain decompression and/or engine out escape routing when required

• Digital filed flight plan request, ATC acknowledgement and change/amendment messages

• Max Temp TLR

• Text and graphic weather observations, charts and forecasts, and all relevant weather advisories/warnings, Pilot Reports (PIREPS), Significant Meteorological Information (SIGMETS), Airman’s Meteorological Information (AIRMETS), Turbulence charts.

• NOTAMs (Jepessen and DoD)

• RAIM Prediction Report

• Graphic chart depicting the flight plan route to include ETP, First/Last

Suitable Airfields, and EROPS entry and exit when applicable.

• Diplomatic Log with PPRs and/or slot times

1.5.1.9. Dispatcher-to-Pilot Briefing

Contractor shall verbally communicate or provide a physical written summary (or highlights) of issues that are associated with any part of the Mission Planning Package. Any unresolved issues or noteworthy performance issues or concerns should be highlighted in this briefing. The Mission Planning Package briefing shall include a FAR 121 or comparable dispatcher briefing.

1.5.2. En-route Flight Monitoring (TASK 2)

En-route Flight Monitoring includes the following subtasks: weather assessment, re-planning, safety of flight, and en-route Mission Planning Package update.

1.5.2.1. Weather Assessment

Contractor shall provide Enhanced Weather Information Systems Certified dispatchers capable of developing a tailored assessment relative to each flight and providing an assessment and necessary recommendations to the Pilot In Command (PIC). The contractor shall:

• Monitor weather conditions for airports utilized in the flight plan and notify the PIC when conditions are observed or forecast to be below minimums within two hours of arrival.

• Provide continuous proactive flight following and ACARS/ Airborne Flight Information Service (AFIS) monitoring, always aware of the aircraft position in flight progress and proximity relative to adverse and unsafe meteorological or geological activity.

• Advise the PIC of adverse and unsafe meteorological or geological activity immediately upon discovery with recommended courses of action to facilitate the utmost level of safety.

• Provide en-route weather (SIGMETS, PIREPS, forecasts, etc.) and any other meteorological or dispatch information, upon request by the PIC.

• Send Meteorological Terminal Aviation Routine Weather Report (METAR)/Terminal Aerodrome Forecast (TAF)/NOTAMs/En-route Winds/Descent winds via ACARS, to the PIC.

• Monitor and provide updated ETOPS alternate and destination weather forecasts to the aircraft via ACARS/AFIS no later than 30 minutes prior to ETOPS airspace entry.

1.5.2.2. Re-planning

Contractor shall execute any actions for flight re-planning including revised diplomatic coordination if conditions require an adjustment to the route of flight or diversion, subject to coordination with PIC and/or tasking agency POC.

1.5.2.3. Safety of Flight

Contractor shall be prepared to execute any actions relative to flight operations that are requested by the PIC and/or ATC when such action is necessary to ensure safe operations.

1.5.2.4. En-route Mission Planning Package Update

Contractor shall complete and transmit an updated Mission Planning Package to the aircrew via email, user desired file sharing site, and/or ACARS while airborne.

1.5.3. Flight Operations Service Management (TASK 3)

Provide total program management support ACARS, all data subscriptions, and any subscription related services.

1.5.3.1. ACARS Ground Host Processing

Provide ACARS ground host service infrastructure. Contractor shall provide ACARS Ground Host Processing access and deliver service for each sortie. ACARS information to be transmitted includes the following:

• METAR/TAF/NOTAM/En-Route Wind/Descent winds data retrieval

• En-route weather (SIGMETS/PIREP, Forecasts, and any other meteorology/dispatch information)

• Airport weather retrieval

• Text messaging capabilities including ACARS-to-email and aircraft-to-aircraft messaging

• Flight Management System (FMS) flight plan up-link/down-link capabilities

• Automatic ACARS initialization up-link messaging

• Route-specific customized weather briefing up-link

• Full-formatted flight plan up-link and filing strip to flight deck printer

• FMS position report trigger message uplink

• ACARS/AFIS/FMS position report support for flight monitoring and following

• Flight tracking/position reporting, automatic ACARS initialization

• Runway gross weight data

• Aircraft-specific weight and balance/performance data

• Fuel alert function

• Block-in/block-out report message

• "MISC" messages for new applications

1.5.3.1.1. Technical Support

Contractor shall provide the technical support necessary for onboard ACARS/FMS and Data Link Service Provider (DSP) menu set-up, software/label address routing lists, network and aircraft test script development and execution, software updates, and on-going technical management. Contractor is required to keep up to date with current standards and update process/support when standards change.

Contractor shall facilitate daily operations and management of uplink/downlink software configurations. Contractor shall serve as the “single point of contact” for all flight deck data communications problems.

1.5.3.2. SATCOM ORT Management

Contractor shall:

• Coordinate with selected Satellite Communications (SATCOM) suppliers and fleet operators to assure aircraft registration, set-up, activation and sustaining service.

• Provide for maintenance and update of aircraft SATCOM “Owner Requirements Table” (ORT) lists with suppliers and Inmarsat.

• Provide ORT coordination with selected SATCOM suppliers, DSP’s, and fleet operators to assure certified ORT software and fleet aircraft communications system interface.

• Provide troubleshooting coordination and phone maintenance services as required as part of ORT sustaining SATCOM service support of fleet aircraft SATCOM operations with suppliers and Inmarsat.

1.5.3.3. Boeing Onboard Performance Tool (OPT) on Apple iPad

Contractor shall:

• Coordinate with Government selected data service suppliers to set-up and manage operational use of OPT on USAF iPads.

• Provide required OPT datasets / options set-up, performance functionality technical support, and on-going program management.

• Provide sustainment management and coordination of the content, changes, issues, cycle updates, and general field service problem resolution for customer OPT databases.

• Ensure OPT allows manual entry of acceleration and thrust reduction altitudes in the Takeoff-Dispatch Tab in order to satisfy Noise Abatement Departure Procedures when required (Default/Optimum assumed when left blank).

• Ensure OPT RWY CONDITION tabs incorporate contaminated takeoff and landing data logic and labels that include selection options for TALPA/RCC, Runway condition description, and pilot reported braking action IAW Runway Condition Assessment Matrix (RCAM)—C-32/C-40 only.

• Pilot Reported Braking Action will include None, Good, Good to Medium, Medium, Medium to Poor, Poor, and Nil.

1.5.3.3.1. OPT Airfield Database Subscription

Contractor shall provide airfield database annual subscription including airfield data, obstacle data, and single engine departure path/procedures for OPT.

1.5.3.3.2. OPT Aircraft Database Subscription

Contractor shall ensure all covered aircraft are included and maintained in the OPT database.

1.5.3.3.3. OPT Administrative Services Subscription

Contractor shall manage and provide administrative services for OPT to ensure reliable operability at all times.

1.5.3.4. Locator Transmitter (ELT) Management

Contractor shall:

• Assist customer with aircraft ELT registration and data updates.

• Provide troubleshooting coordination and phone maintenance services as part of ELT sustaining service support of fleet aircraft operations.

1.5.3.5. Identification Friend or Foe (IFF)/Mode S ACARS (ICAO) ID Management

Contractor shall:

• Coordinate with the Aerospace and Electronic Systems Society (AESS) to assure aircraft “ID” code identification, aircraft drawing documentation, agency registration, network technical consulting and aircraft in-service support.

1.5.3.6. SARB Support

Contractor shall:

• Attend Government and/or comp “Service Action Review Board” (SARB) and provide support for subscription concerns. This includes participating in scheduled SARB customer meetings and/or telecons and providing technical assistance to Service Engineering personnel.

1.5.3.7. Support for CNS/ATM and New Aircraft Technologies

Contractor shall:

• Coordinate with Government selected suppliers, regulatory agencies, and fleet operators to assure aircraft Controller-Pilot Data Link Communications (CPDLC) registration, software technical support, training, flight operations activation, and in-service Future Aviation Navigation System (FANS) support.

• Provide FANS implementation and program management coordination with regulatory agencies, Boeing Commercial Airplanes (BCA), Data Link Service Provider (DSP), selected SATCOM suppliers and fleet operators to assure CPDLC flight operations and fleet aircraft communications system interface.

• Provide troubleshooting coordination with suppliers, operators, and regulatory agencies as part of FANS/CPDLC sustaining service support of fleet aircraft operations.

1.5.3.7.1. Controller-Pilot Data Link Communications (CPDLC)

Management

Contractor shall create, maintain and provide to each tasking agency via email a CPDLC ID database list.

1.5.3.8. EGPWS Database Management

Contractor shall manage Enhanced Ground Proximity Warning System (EGPWS) and ensure it is up to date.

1.5.3.8.1. EGPWS Database Annual Subscription

Contractor shall provide EGPWS subscription

1.5.4. FMS Navigation Database Management (NDB)

Contractor shall manage Navigation Database and ensure it is up to date. In order to mitigate the growing navigational database and limitations in storage capacity, the Contractor may be required to provide database customization to help minimize negative operational impact. The Contractor, in cooperation with the customer, shall determine the criteria on what to include and exclude from the NDB and change as agreed upon.

1.5.4.1. FMS Navigation Database (NDB) Annual Subscription

Contractor shall provide FMS NDB subscription updates each navigational data cycle. Data is proprietary; suppliers are currently Honeywell, General Electric and Jeppesen. Additionally, contractor will be required to produce an excel spreadsheet and PDF file listing every airfield for each C-32A and C-40B/C Navigation Database Cycle to include at a minimum: every airfield and its associated instrument procedures (SIDs, STARs, approaches, etc.). The files will be uploaded to the Dispatcher’s website as well any additional file sharing location the user requires (i.e. currently the 89th requests upload to 89AW Box/All Files/Airfield Worksheet Library/0. C-32A SF-1 NDB OR C-40B SAM1 NDB as appropriate).

1.5.4.2. FMS Navigation Database (NDB) Off Cycle Updates

Contractor may be required to provide additional off cycle navigational database updates for both the C-32A tails and C-40B/C tails as requested by the contracting officer representative, not to exceed 25 per option year.

1.5.4.3. Required Navigation Performance (RNP) Authorization Required (AR) Procedures Validation

Contractor shall:

• Ensure authorization/validation of all RNP AR procedures contained in the respective C-40B/C and C-32A NDB in accordance with FAA AC 101-90A, specifically Appendix 3 paragraphs 3a, 3b, and 4a.

• Send a copy of the most current C-32A and C-40B/C RNP AR NDB validation letter to each flying unit no later than three days prior to the beginning of each database cycle

1.5.5. Dispatch Familiarization Course (TASK 4)

Contractor shall organize and participate in a semi-annual, one day Dispatch Familiarization Course with AMC crews and other stakeholders (AFRC and ANG) to ensure continuity of service and shared understanding of the operations processes and procedures at the contractor operations center. This course should augment the following subjects with emphasis on Flight-deck operations, ACARS / FANS Data Link functionality, integration and processes:

• Dispatch Process o Dispatcher and Aircrew Interaction o Dispatch Package Explanation o Shared Responsibilities

• Services not provided

1.5.6. Phase-In

The contractor shall implement a phase-in program to ensure all required phase-in activities are completed by the end of the 30 day phase-in period.

1.5.7. Phase-Out

The contractor shall be responsible for full performance of the PWS tasks until the end of the contract during the phase-out period, including all missions that begin and end during the transition period. In missions that begin during the transition period and end during full performance of the follow-on contract, the successor contractor shall be responsible for the PWS tasks. If required, phase-out will be begin 30 days prior to contract expiration.

1.5.7.1. Phase-Out Program

The contractor shall implement a phase-out program to ensure all required phase-out activities are performed prior to the end of the contract.

1.5.7.2. Description

The phase out program shall completely describe the activities, milestones, and timeframes necessary for the contractor to transfer responsibility of the PWS tasks to a successor contractor.

1.5.7.3. Inclusions

The phase-out program shall include any best practices, lessons learned, and checklists utilized during the performance of the contract with the exception of any proprietary or company sensitive information.

1.5.7.4. Deliverable

The contractor shall document the phase out program in a phase-out plan and deliver it to the COR 6 months prior to the end of the contract.

1.5.7.5. Cooperation

The Contractor shall cooperate fully with the Contracting Officer Representative (COR) and any successor Contractor(s) to ensure an orderly transition at the end of this contract.

2. Service Summary The Service Summary (SS) table below summarizes the most important performance objectives and thresholds. The absence of any performance objective and threshold from this SS shall not detract from its enforceability or limit the Government’s rights or remedies afforded under this contract.

Performance Objective PWS Para Performance Threshold (Standard)

Contractor shall provide all management, personnel, labor, and services necessary to perform all requirements IAW the following paragraphs

1.5.1.3 1.5.1.5 1.5.1.8 1.5.1.9 1.5.2.4 1.5.3.3.1 1.5.3.3.2 1.5.3.3.3 1.5.3.4 1.5.3.5 1.5.3.6 1.5.3.7 1.5.3.7.1 1.5.3.8 1.5.3.8.1 1.5.4.1 1.5.4.3

Performance is acceptable when there are not more than two late or incomplete data deliverables per month.

Contractor shall complete flight planning analysis (pre-mission execution)

1.5.1.1 not more than two incomplete flight planning analyses delivered per month.

Contractor shall provide completed diplomatic clearances

1.5.1.2 not more than two incomplete diplomatic clearances per month.

Contractor shall complete mission review

1.5.1.4 not more than two incomplete mission reviews delivered per month.

Contractor shall calculate

TOLD & WB

1.5.1.6 not more than two inaccurate TOLD and W&B calculations per month.

Contractor shall file timely flight plans with ATC for tasking agency

1.5.1.7

Performance is acceptable when there is not more than one untimely filing of a flight plan with ATC per year.

Contractor shall provide weather assessment

1.5.2.1 not more than two incomplete weather assessments provided per month.

Contractor shall provide flight re-planning and package update

1.5.2.2 not more than two incomplete or unexecuted flight re-planning actions per year.

Contractor shall provide safety of flight services

1.5.2.3

Performance is acceptable when there is not more than one incomplete or unexecuted action relative to safety of flight services per year.

Contractor shall provide management of ACARS services

1.5.3.1 1.5.3.2 not more than two instances when ACARS ground host processing is undelivered per year.

Contractor shall provide management of data subscriptions

1.5.4 Performance is acceptable when there is not

more than one instance when data subscriptions are out of date per year.

Contractor shall provide off-cycle navigational database updates on an as requested basis

1.5.4.2 Performance is acceptable when aircraft

databases are updated not later than three days prior to home station departure more than once per year

Contractor shall provide two annual dispatch orientation sessions for each unit

1.5.5 no less than two sessions per year

Contractor shall implement a Phase-In program

1.5.6 Performance is acceptable when activities, milestones, and timeframes are realistic in achieving contract-ready performance by the beginning of the contract period of performance

Contractor shall implement a Phase-Out program

1.5.7 Performance is acceptable when a plan is

submitted and accepted not later than 6 months prior to the end of the contract

Contractor shall provide a single POC responsible for all contract requirements

3.1.2 Performance is acceptable if a POC is

forwarded to the Contracting Officer within 10 days

Contractor shall provide a list of key personnel and subsequent changes to the Contracting Officer Representative

3.1.3 Performance is acceptable if initial list is

accomplished within 15 calendar days, and within 3 business days if changes are made to this list

3. General Information

3.1. Program Management Support

3.1.1. Risk Management Program

Contractor shall provide Program Management support to meet the performance requirements of the PWS. Contractor shall establish and maintain a risk management program for the purpose of early identification of program risks and mitigation of risk so contract performance is not impacted.

3.1.2. Program Management POC

The Contractor shall designate a single POC responsible for the overall management and performance of the PWS. The Contractor designee shall be responsible for all requirements of the contract. The Contractor shall provide the name and contact information of the designee to the PCO within ten working days of contract award.

3.1.3. Key Contact List

The Contractor shall provide names and contact information for key personnel and for the overall contract to the PCO and the applicable Contracting Officer Representative (COR) within 15 calendar days after contract award and provide updates within three business days if changes are made. Contact information shall include provisions for 24-hour contact.

3.1.4. Contractor Manpower Reporting

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for Executive Airlift Flight Dispatch via a secure data collection site.

Department of Defense (DoD) contractors will begin reporting FY 2020 manpower data under applicable service contracts in the Service Contract Reporting (SCR) section of the System for Award Management (SAM) (http://sam.gov) to support the requirements of title 10, U.S.C, section 235 and 2330a. The former DoD Enterprise Contractor Manpower Reporting Application was retired June 2020, in preparation for this transition to SAM.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September.

While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year.

*Reporting Period: Contractors are required to input data by 31 October of each year.

*Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

Additionally; the Contractor shall provide a Contractor Manpower Equivalent (CME) report, annually, no later than 20 days after the end of each Government fiscal year. The Government will have (10) business days to review for correct http://sam.gov/ content and format. If correction is warranted, the contractor has (5) business days after notice to correct deficiencies and resubmit. Criteria for approval shall be correct content and format. The exact format is to be determined by the Government, however the information required shall include but is not limited to:

contract number, functions and missions performed under the contract, the contracting organization administering the contract, the functional organization(s) supported, funding source, performance dates of the contract, and the number of full-time contractor employees (broken down by labor category).

A DoD Guidebook was developed for Service Contract Reporting in the SAM, available on the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr. This Guidebook is designed for both DoD users and contractors.

GSA has also posted additional guidance such as quick start guides, informational videos, and frequently asked questions, go to https://sam.gov and search the “HELP” section. Also, reference the SAM Federal User Guide available in the “HELP” section for comprehensive instructions on navigating SAM. Should contractors have issues using SAM, they should contact the Federal Service Desk at https://www.fsd.gov.

3.2. Security Requirements

3.2.1. Access to Installation During Force Protection condition (FPCONS) Contractor will be assigned a mission essential designation IAW requirements contained in Integrated Defense and Antiterrorism Plans. Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

3.2.2. Property Protection

Property protection for the facility where contractor’s primary work center is located will be the responsibility of the local facility manager and local Government Security Manager, or their duly authorized representative IAW AFI 31-101, Integrated Defense, and command/local directives. Contractor must safeguard all Government-owned equipment and materials in his/her possession or use.

3.2.3. Contractor Working in Controlled or Restricted Areas

In the unlikely event that a contractor requires access to the controlled or restricted area and does not have the proper investigation, government will ensure escort(s) is/are provided for contractor at all times when within a controlled or restricted area.

Contractor must have an issued AF Form 1199 and work on base a minimum of four days a week (must have an assigned workspace on base). Contractor is only allowed to escort visitors from the same company for which he/she works, and all visits must be for official business. In addition, contractor must fulfill, maintain, and comply with all security requirements IAW Integrated Defense and command/local directives.

3.2.4. Access to Government Facilities with Controlled or Restricted Areas Contractor shall comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas on any Air Force Base (AFB), Government may direct contractor to leave the controlled or restricted areas at any given time.

The following scenario (i.e., replacement contractor with an inadequate security clearance) is abnormal. Government will ensure replacement contractors not initially possessing the proper clearances and requiring entry to controlled or restricted areas are escorted continuously. Replacement contractor must submit paperwork within seven days of being assigned to obtain an approved security clearance or favorable review.

Replacement contractor personnel must obtain a security clearance prior to working with, or having direct access to, classified material. In addition, replacement contractor personnel must obtain a “favorable review” prior to having access to a Controlled Area.

3.2.5. Contractor Consent to Background Checks

Contractor shall only employee personnel for performance of this contract that have successfully completed a National Agency Check with Inquiries (NAC-I). Contractor shall not employ persons to perform under this contract if such employee is deemed or identified as a potential threat to the health, safety, security, general well-being or the operational mission of the installation, nor shall contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by Law Enforcement Agency Data System (LEADS) through the National Crime Information Center. LEADS checks will verify if a person is wanted by local, state, and federal agencies. All contractor and subcontractor personnel must consent to LEADS background checks. Contractor and subcontractor personnel who do not consent to LEADS check will be denied access to the installation. Information required to conduct a LEADS check includes: full name, driver’s license number, and/or social security number, date of birth of the person entering the installation, and completion of a background check questionnaire. Contractor must have this information ready to provide to the Installation Visitor Control Center, if requested.

3.2.6. Citizenship

Contractor must ensure their employees and those of their subcontractors having access to any mission information are citizens of the United States. The contractor shall not employ foreign nationals under this contract.

3.2.7. Badges

The contractor is required to provide identification badges for their employees on base.

All contractor personnel shall wear these badges while on duty on the Government site.

Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. The contractor’s identification badge will not be used as an entry requirement for installation entry or into any government designated controlled or restricted area.

3.2.8. Safeguarding For Official Use Only (FOUO) and other Unclassified Information

The contractor shall meet Air Force standards for storing, processing, and handling FOUO and other unclassified information and systems in accordance with DoD Manual 5200.01, Volume 4. Additionally, all resources (e.g. maps, publication/instructions, photos) provided by the Government to assist the contractor in the performance of their contract will be surrendered upon termination of employment or the end of the contract performance period. Contractor shall protect and restrict USAF/AFRC/ANG mission operations information to only its own personnel who have an operational need to know.

3.2.9. Information Assurance

Contractor shall comply with all AMC security requirements pursuant to DOD Directive (DODD) 5200.2 Personnel Security Program, DOD Instruction (DODI) 8500.1

Cybersecurity, and DODD 8570.01-M Information Assurance Workforce Improvement Program. Contractor must ensure that all personnel assigned to work on the contract requiring access to government networks must complete annual Information Assurance (IA) training by on-line CBT. Training can be accessed at -https://golearn.csd.disa.mil/kc/main/kc_frame.asp. Contractor is responsible for having the appropriate Information Assurance baseline certification.

3.2.10. Communications Security:

All communications shall comply with DoDI 5200.48 Controlled Unclassified Information and the Air Force Guidance Memorandum (AFGM 2020-16-01).

3.2.11. Privacy Act

Work on this project may require that personnel have access to Privacy Information.

Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a, and applicable agency rules and regulations.

3.3. Place of Performance

Work shall be primarily accomplished at contractor’s location and/or the contractor’s continuity of operations alternate location.

3.4. Hours of Operation

Contractor shall provide for 24/7/365 coverage. Contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than two weeks.

3.5.Administrative Items

3.5.1.Dispatchers Contractor shall utilize FAR Part 65 licensed dispatchers comparable with the FAA’s FAR 121 standard Domestic/Flag Operations performing dispatch and flight following duties. When FAR Part 121 and Air Force guidance differ, Air Force guidance will be used. Contractor shall protect and restrict USAF/AFRC/ANG mission operations information as FOUO data.

3.5.2. English Language

Contractor shall ensure Contractor employees who are required to communicate with Government personnel have the ability to clearly read, write, and speak English. All program documentation shall be done in English.

3.5.3. Conduct

Contractor and Contractor employees shall identify themselves as contractors when communicating with the Government and shall not represent themselves as or provide direction as if they were a Government representative. Contractors shall not identify themselves either through the display name of their e-mail address, signature, or other electronic communications devices, telephonically, or in person in such a way as to use any part of any tasking agency organizational name. Contractors shall identify themselves by using their company name and the individual’s name when communicating in any official capacity via e-mail, phone, or other means.

3.5.4. Access

Tasking agency POC will provide Avisource mission taskings and all subsequent changes to the contractor.

3.5.5. Original Equipment Manufacturer (OEM) Data

Contractor shall obtain and maintain OEM Proprietary Data license agreement(s) for the access and use of OEM proprietary data necessary to execute this PWS. The use and access of data shall include sharing with AF flight crews for operation and sustainment of the covered aircraft. These agreements may be fee bearing. Contractor shall ensure that any subcontractors have required access and license for OEM data to support their activities under this PWS.

Boeing POC for OEM Proprietary Data License is:

Rebecca O’Brien Business Development & Licensing Boeing Intellectual Property Licensing Company Office: 314-232-2614 Cell: 314-614-8956

3.6. Publications and Services

3.6.1. AF Publications

Most AF publications and forms may be accessed through the AF Publishing website:

http://www.e-publishing.af.mil/

3.6.2. DOD Publications

DOD Issuances (DODD, DODI, DOD Manuals (DODM), etc.) are available through the Defense Technical Information Center (DTIC) website:

http://www.dtic.mil/whs/directives/. DOD Forms available through:

http://www.dtic.mil/whs/directives/infomgt/forms/

3.6.3. FAA Publications

FAA publications and forms…