Atch 1 - Alaska Pax HTC71125RC001 PWS.pdf

HTC711-25-R-C001

Attachment 1: Performance Work Statement

Performance Work Statement (PWS)

Alaska Commuter Passenger Services

Twelve (12) Passenger Minimum Requirement

12 March 2025

TABLE OF CONTENTS

1. Introduction

2. Scope – General Requirements

3. Contractor Requirements

4. Schedules

5. Government Furnished Services and Equipment

6. Maintenance

7. Fuel Service

8. Contractor Personnel

9. Reimbursable Services and Costs

10. Cancellations, Diverted, Delayed Loitering, and Re-Routed Flights

11. Contract Administration and Management

12. Invoicing

13. Service Delivery Summary

14. Cyber Security

15. Operations Security

16. Governing Guidance and Directives

1. INTRODUCTION

Except as otherwise stated, the contractor shall provide all personnel, equipment, tools, materials, supervision, and other items and services necessary to perform air transportation services for military and Government civilian commuter passenger transportation and movement of essential cargo in support of 611th Air Support Squadron, Pacific Air Force (PACAF) Regional Support Center (PRSC) for Intra‐Alaska Charter Airlift Services throughout the state of Alaska. Services shall meet or exceed 14 Code of Federal Regulations (CFR) Part 135 Operating requirements: commuter and on‐ demand operations and rules governing persons on board such aircraft.

2. SCOPE ‐ GENERAL REQUIREMENTS

2.1. The contractor shall furnish air transportation passenger services to/from Joint Base Elmendorf-Richardson, AK (JBER, ICAO: PAED) to Eareckson Air Force Station (EAFS, ICAO: PASY) via contractor‐furnished, Instrument Flight Rules (IFR)‐equipped, turbine‐ powered, multi‐ engine aircraft. A typical passenger mission flown under this contract, would be PAED-PASY- PAED, ~7 Hours (~3.5 hours each way).

2.2. The contractor shall carry the scheduled load of passengers and baggage on each flight unless limited by weather.

2.3. The contractor will be responsible and liable for the loss, damage, or destruction of the checked and unchecked baggage and items of personal property in the possession of the passengers on flights performed under this contract from the completion of loading by the government until commencement of unloading by the government. Contractor’s liability for checked baggage is limited to the actual value thereof, not to exceed $3,800.00 per passenger. Contractor’s liability for unchecked baggage, items, or personal property in the possession of passengers exists only for loss, damage, or destruction by aircraft accident or otherwise caused by the contractor.

2.4. Interior cabin appointments, seats, and fixtures in the aircraft shall be maintained in a safe, clean, and presentable condition. Specifically, unsightly wear, holes, and un-mended tears are not acceptable. Aircraft shall be equipped with adequate tie down or restraint system for baggage.

2.5. As a minimum, the contractor shall provide snacks appropriate for the time of day served and commensurate with commercial service offering. Examples of a snack would be a sweet roll, juice, and coffee in the morning, fruit and cookie in the afternoon/evening. No alcohol will be provided on any flights.

2.6. With the contractor’s and government’s concurrence, the aircraft to be used in the performance of this contract may be parked overnight at JBER; however, when the aircraft is parked overnight at JBER the contractor will not be paid positioning/de-positioning costs in the case of a cancellation.

2.7. Twelve (12) Passenger Charter Service (Year-Round)

Route: JBER, AK (PAED) to EAFS (PASY), AK or other destinations along the route, which may include King Salmon, AK (AKN); Cold Bay, AK (CDB); Attu Island, AK (ATU), Adak Island, AK (ADK), Valdez, AK (VDZ) or other locations in the event an aircraft must divert to an alternate location due to weather, mechanical issue or mission shift. Aircraft utilized must:

2.7.1. The contractor’s aircraft must be capable of flying to and from PAED to PASY in no more than 7-8 hours flying time staying airborne with a minimum load of 12 passengers, fuel, and baggage and up to approximately 336 passengers per month. (Note: The Government increases aircraft utilization during summer months.);

2.7.2. Have a range capable to miss approach at EAFS and continue to a suitable alternate with a full load of passengers, fuel and baggage, operating at 19,000 feet or higher;

2.7.3. Be fully self‐supporting with internal passenger stairs, have a pressurized cabin, auxiliary power unit (APU) for self‐starting, and an industry standard lavatory equipped with running water and flushing toilet system; and

2.7.4. Have a minimum Aircraft Allowable Cabin Load (ACL) capable of carrying minimum of 12 passengers with a combined 100 lbs. of checked/hand carried baggage per passenger; hand carried baggage size/storage must meet commuter industry standards with FAA regulated netting to accommodate baggage. Baggage storage space needs to adequately hold 26 bags at 50 lbs. a piece with a max size of 62 linear inches. Small priority cargo will not exceed 75 lbs.

(high priority non‐hazardous).

2.8. SPECIAL REQUIREMENTS ‐ PASSENGER

2.8.1. Excess ACL and Route Support

a. The contractor may transport Government route support items and personnel, including support for aircraft not operationally ready, providing that such support items or personnel are required for performance of this contract, in any available ACL space. The contractor must give at least six hours advance notice to the Contracting Officer Representative (COR), whenever seats are required for mission route support on a contracted mission. The contractor will not be charged for on/offloading services in connection with moving route support cargo. Route support personnel are personnel employed by the contractor for route support and required for performance of this contract.

b. The contractor may also move its own route support items and personnel, including support for aircraft not operationally ready in space not used by the government (available ACL).

However, in any such case, any passengers or baggage displaced by said route support will result in appropriate reduction in payment on a pro rata basis to the contractor for such flight.

c. The procurement of charters is for use of the entire ACL of the aircraft. When aircraft performance data allows, the Government is entitled to excess weight capacity and seats exceeding the minimums identified in PWS Para. 2.7.4. This also applies to substituted aircraft.

The Government is not entitled to transport excess ACL if the contractor would be required to make an otherwise unrequired operational stop as a result of the carriage of the excess ACL.

2.8.2. Overnight stays

Maintenance or other unforeseen problems may warrant an overnight stay. Such instances will be worked on a case‐by‐case basis by the PRSC 611th Traffic Management (DSN 552-4935, Comm 907- 552-4935) and COR. Overnight stays or extended ground times at JBER, exceeding four hours, required for follow‐on missions will be coordinated with the carrier and approved by the PRSC 611th Traffic Management.

2.8.3. Stand‐By Time

In the event the contractor is directed by the government to stand‐by for flights performed under this contract, the first hour of stand‐by time, for each stand‐by period, will be at no cost to the government. At mission origin, stand‐by time shall commence one hour after the scheduled departure time or one hour after aircraft is in place, ready for loading, whichever is later. At destination and en route stops, stand‐by time shall commence one hour after the aircraft is offloaded at destination and shall end when the authorized government representative releases the aircraft for departure, makes the determination that the aircraft will remain overnight, or the flight is cancelled. The Government requests three hours of stand-by time that will occur approximately once per month. Stand‐by time will not be chargeable to the government for contractor controllable delays or for delays caused by Acts of God, or weather conditions below minimums that preclude takeoff of flight to the destination. For the purpose of payment, the carrier will be reimbursed under the reimbursable CLIN.

2.8.4. Loiter Phase of Flight (i.e., airfield circling)

Due to adverse airfield weather conditions or airfield obstructions, a flight could be diverted or requested to be put in a loitering phase of flight. The request to loiter must be approved by PRSC 611th Traffic Management (DSN 552-4395, Comm 907-552-4395 or Capability Forecasting through verbal confirmation. The carrier will document the name of the PRSC 611th Traffic Management approving authority and the total loitering time using the aircraft flight log. Payment for loitering will be calculated as follows: loitering time in flight hours multiplied times the flight hour unit price. The carrier will include a flight log as an attachment with the request for payment.

In addition, the calculations used to support the loitering time needs to be identified in the Wide Area Work Flow (WAWF) remarks.

2.8.5. Special Handling Equipment

Equipment which is not common to government and contractor aircraft and/or cargo handling systems, such as tow bars and special equipment for loading/unloading, will not be available at military installations and must therefore be furnished by the contractor. Contractor will also furnish personnel to operate such equipment.

2.8.6. Command and Control

a. On positioning legs, the contractor shall call the Information Controllers at the PRSC 611th Traffic Management, (907) 552‐4395/2858 or at provided designated telephone number, after the aircraft departs for the originating station. The contractor shall advise PRSC 611th Traffic Management of the estimated arrival time at originating station, call sign, type aircraft, and available ACL.

b. Upon departure, if the contractor determines that the aircraft arrival time is expected to deviate by more than 15 minutes from the scheduled arrival time, contractor shall advise PRSC 611th Traffic Management of the reason for the deviation and the proposed new arrival time.

c. In the performance of this contract, the contractor shall utilize the United States Air Force (USAF) High Frequency (HF) Global Command and Control System, in addition to other radio frequencies listed in the Flight Information Publication (FLIP) Alaska Supplement, or as provided by the Government.

d. On all inbound flights to JBER, the aircraft commander shall call PRSC 611th Traffic Management within 15 minutes of occurrence with its estimated time of arrival (ETA) at JBER and any special requirements.

e. On all departures (except the de-positioning leg) from JBER, the aircraft commander shall call PRSC 611th Traffic Management (Very High Frequency (VHF) 134.1‐call DENALI) with its actual take‐ off time and ETA to next destination.

f. When diversions or flyovers of any site are warranted because of weather, the aircraft commander shall notify PRSC 611th Traffic Management by one of the following means and request instructions:

(i) directly, via assigned HF;

(ii) request phone patch to PRSC 611th Traffic Management via USAF Global Command and Control System Station;

(iii) pass a message through the Base Operations via VHF and in turn, they will request PRSC 611th Traffic Management guidance; or

(iv) request a VHF phone patch through a local flight service station.

2.8.7. The contractor shall comply with PRSC 611th Traffic Management instructions and shall be paid for all flight hours flown as directed by the PRSC 611th Traffic Management.

Payment will be in accordance with the negotiated rate.

2.8.8. If the PRSC 611th Traffic Management does not issue diversion instructions within 15 minutes, the aircraft commander will exercise their best judgment and divert at their discretion.

2.8.9. If the aircraft commander fails to notify PRSC 611th Traffic Management of impending diversions or fails to follow the PRSC 611th Traffic Management instructions, the contractor shall be responsible for the care of passengers, if any, and for loading/offloading and storage of baggage, if required. In addition, the contractor shall be reimbursed only for the flight hours set forth in the original routing, if they subsequently complete the routing. If the contractor completes only a portion of the routing, they shall be paid accordingly.

2.8.10. The contractor shall provide all personnel, equipment, tools, materials, supervision and other items and services necessary to perform the air transportation services under this contract via contractor‐furnished IFR equipped, multi-engine aircraft.

3. CONTRACTOR REQUIREMENTS

3.1. Commercial Airlift Review Board (CARB) Approval

The contractor must be a Department of Defense (DoD) approved air carrier. The contractor must meet all DoD Commercial Air Carrier Quality and Safety Requirements outlined in 32 CFR Part 861 and must maintain this approval throughout the performance of this contract. The contractor shall comply with all Federal Aviation Administration (FAA) requirements.

3.2. Contractor Availability

Aircraft/crew shall be able to perform missions 7 days a week, 365 days a year, including all holidays. Flight times and schedules may vary from day‐to‐day and dependent on foggy season. The PRSC 611th Traffic Management Ordering Officers (OO) will coordinate schedule and flight times with the contractor. Sample flight window is 1030, 1130 if foggy.

See PWS paragraph 4. Schedule.

Note: The 611th Air Support Squadron shall have primary use of the aircraft. When the aircraft is not being utilized by the 611th Air Support Squadron, the contractor may use the aircraft for other purposes, however, the 611th Air Support Squadron shall be given priority.

Per section 4.1, the 611th Air Support Squadron OOs will provide at least a 24-hour notice prior to departure.

3.3. Aircraft

The Contractor shall provide the necessary aircraft to support the mission requirements and ensure all aircraft are safe and maintained in accordance with applicable regulations. Aircraft utilized must be licensed, operated, and maintained in accordance with all applicable rules and regulations of the FAA and Department of Transportation (DoT), giving particular attention to the responsibility of the air carrier to perform air transportation with the highest degree of safety. The aircraft performing missions under this contract will not be considered public aircraft. The contractor shall have a current FAA authorization certificate to operate over routes and into the airfields specified under both IFR and Visual Flight Rules (VFR) conditions and rules. IFR capability authorization is not required for operations into airfields that do not have published IFR approach procedures.

3.4. Substitute Aircraft

Aircraft substituted by the contractor on any one flight shall meet the minimum seating/ACL and/or equipment requirements for that flight and be approved by the Contracting Officer (CO) prior to operation. Aircraft substituted must be from a DoD approved air carrier and will be handled IAW TRANSFAR Clause 5552.247-9002, Contractors Failure to Provide Service.

3.5. Accepted Flight Hours

Actual flight hours flown are the accepted flight hours for the purposes of performance and payment. The Flight Hours listed between the points in the schedule are the estimated accepted flight hours. Calculated flight hours for re‐routed or diverted missions due to adverse weather conditions will be coordinated with the COR or handled as a partial mission (Para. 2.8.9.). A typical passenger mission flown under this contract would be PAED-PASY-PAED, ~7 hours (~3.5 hours each way). Please note the ferry legs are not included in billable flight hours.

3.6. Partial Missions

Partial missions shall be supported by flight logs which should include time of departure and arrival.

These are scheduled missions but are forced to return due to inclement weather or other unforeseen circumstances. Calculations that support the invoice amount for partial missions shall be clearly identified in the "Description" block of the invoice in WAWF.

3.7. Landing Permits

The contractor shall have an identified base of operations for performance of this contract and have current landing permits from appropriate military services. Landing permits may be obtained as follows:

a. AIR FORCE BASES. Pursuant to Air Force Instruction (AFI) 10‐1001, DD Form 2400 Certificate of Insurance (COI), DD Form 2401 Landing Permit, and DD Form 2402 Hold Harmless Agreement may be secured from United States Transportation Command (USTRANSCOM)/TCAQ‐CE. Forms to be returned via email upon completion to TCAQ‐C Point of Contact (POC): Tyler Gilmore, Contract Specialist, tyler.r.gilmore2.civ@mail.mil

(618) 817-9502, alternate POC to be cc’d, Barbara Wolf, Contracting Officer, barbara.l.wolf11.civ@mail.mil(618) 817-9382.

b. NAVY AIR STATIONS. POC: Civil Aircraft Landing Permit (CALP) Manager, (202) 433-

0120. Email: CALP.HQ@navy.mil

c. MARINE CORPS AIR STATIONS. POC: Civil Aircraft Landing Permit (CALP) Manager,

(315) 636-3207. Email: MCICOM_CALP@usmc.mil

d. ARMY INSTALLATIONS. POC: US Army Aeronautical Services Agency Branch, (703) 806‐0687. Email: usarmy.belvoir.hqda-dcs-g-3-5-7.list.usaasaops@mail.mil

3.8. Submission of Collective Bargaining Agreements

The contractor agrees to provide the CO, upon request, a copy of any Collective Bargaining mailto:tyler.r.gilmore2.civ@mail.mil mailto:CALP.HQ@navy.mil mailto:MCICOM_CALP@usmc.mil mailto:usarmy.belvoir.hqda-dcs-g-3-5-7.list.usaasaops@mail.mil

Agreement (CBA) applicable to employees performing this contract.

3.9. Airfield Suitability and Restrictions/Certification Airfields

Contractors can obtain an Airfield Suitability and Restrictions Report (ASSR), at no cost, by contacting Headquarters (HQ) Air Mobility Command (AMC)/A3AS, 510 POW MIA Drive, Room 316, Scott AFB, IL 62225‐5302, (618) 229‐3112.

3.9.1. Certification Airfields. The ASSR also lists “certification airfields” which are the equivalent to FAA-designated “special airfields”. Operations into these airports are exposed to increased risk due to unique hazards. These fields have unique operating procedures requiring increased aircrew awareness and familiarity. This contract requires that at least one pilot member of an aircrew, operating a DoD mission into a designated certification airfield, shall have performed pilot duties to that airfield within the past 12 months or reviewed an FAA‐accepted pictorial or video detailing airfield hazards within 30 calendar days prior to performing the DoD contract mission. Contractors shall ensure that air crews are adequately briefed on all restrictions at applicable airfields, including certification airfields, and properly trained before performing any missions into these airfields.

3.9.2. Airfield Approach Data. Airfield approach data acquired and generated by AMC for use in military flight operations will be provided to the contractor at no cost. The information is provided without warranty or accuracy or suitability for commercial aircraft operations. The contractor remains responsible for safety of flight to include verifying the accuracy and suitability of airfield approach data and reconciling any conflict that may exist between AMC provided data and standard commercial data. The contractor may communicate the AMC provided data to other parties only if the disclaimer of US Government responsibility for accuracy and suitability is prominently incorporated. AMC airfield approach data information will be passed at the time of mission scheduling except for after duty hours or for short-notice missions where departure has a window of less than 24 hours. Under such circumstances, the contractor should contact the 618 AOC (TACC) at (618) 229-0320 for contingency missions, (618) 229-0321 for channel missions, and (618) 229-0323 for SAAM and exercise missions or at provided designated telephone number.

3.10. Mobilization

Mobilization. The Contractor shall position personnel, equipment, and aircraft for this contract and be fully operational and mission capable no later than 60 calendar days from contract award. Mobilizing prior to receipt of a contract award, or prior to the effective date of this contract, is not authorized and such costs will not be paid. The contractor shall ensure minimal service disruption to vital Government business and no service degradation during the position period. The government will not provide compensation for the flight hours required for the contractor's aircraft to position themselves from their place of mobilization to JBER.

4. SCHEDULES

Flight times, schedules, and number of passengers may vary from day‐to‐day. Flight window is dependent on foggy season. The Contractor shall be positioned at JBER no later than 1 hour prior to scheduled mission take of time for passenger manifesting, loading and refueling. Note: Occasionally, a fourth round-trip flight is requested by the Government.

Table 1: Summer Schedule:

Schedule Minimum Passengers Return Minimum Passenger Monday 12 12 Wednesday 12 12 Friday 12 12

Table 2: Winter Schedule:

Schedule Minimum Passengers Return Minimum Passenger Monday 12 12 Wednesday 12 12 Friday (bi-weekly) 12 12

4.1. For this paragraph, the term, "schedules," means the days and time of day of the flight operations. To the extent such schedules are not specified in this contract, they shall be established by mutual agreement between the contractor and the appointed PRSC 611th Traffic Management OO at least 24 hours prior to the departure time. Schedules may be given verbally or in writing. When the schedules are given verbally, the government will confirm the schedules in writing prior to mission departure. The scheduler/OO will assign a call number to identify the scheduled mission. The contractor shall include the call number, the AMC mission number (provided by Capability Forecasting at initial mission setup), along with the contract and delivery order number on all invoices submitted for payment. Only the appointed OO is authorized to obligate the Government.

4.1.2. The contractor shall contact Eareckson Air Station (EAS) Weather Observer, Shemya, Alaska (907) 392-3505 or (907) 392-3606, DSN 317-392-3505 or 317-392-3606 or at provided designated telephone number, two hours prior to positioning the aircraft at the originating station for the purpose of obtaining weather status at destination stations. If the government and the contractor agree that the aircraft may not be capable of transporting the full ACL under this contract due to adverse weather conditions. The weight of additional flight planned fuel may be deducted from the ACL for those flights where adverse weather conditions require this additional fuel. In these cases, the contractor must present to PRSC 611th Traffic Management, the facts/conditions that would preclude transportation of cargo up to the required ACL.

4.2. SCHEDULE RELIABILITY

4.2.1. Schedule reliability refers to a record of both carrier‐controllable and carrier‐ uncontrollable delays. A daily record of all delays will be tracked and recorded by the PRSC 611th Traffic Management in Global Decision Support System (GDSS). Delays will be further reviewed and adjudicated by TCAQ‐C with the carrier during the reliability appeal process.

4.2.2. The contractor’s schedule reliability rate shall be based upon on‐time arrivals and computed for any rolling three‐month period by subtracting the total number of contractor‐controllable delays during the three‐month period, from the contractor’s total number of scheduled originating and turnaround missions operated in that three‐month period, and dividing the remainder by the contractor’s total number of scheduled originating and turnaround missions operated for the period.

This reliability rate computation shall be made as of 2400 hours Greenwich Mean Time (GMT) on the last calendar day of each month. The turnaround station is defined as that station of a round‐ trip mission where the mission number changes.

4.2.3. Contractor controllable delays extending from 1 hour up to 4 hours will be counted as one‐ half (0.5) delay. Contractor‐controllable delays exceeding 4 hours will be counted as one (1) delay.

A contractor‐controllable delay of 1 hour or less will not be counted in the schedule reliability rate.

4.2.4. Contractor’s schedule reliability rate will be calculated to the nearest whole number. Less than .5 will round down and .5 or more will round up. For example, a carrier has four (4) contractor‐controllable delays for the three‐month period. Total missions operated are 30.

Reliability rate is calculated as 26 divided by 30 = .866 or 87%.

4.2.5. A delay shall be deemed to have occurred at the mission’s final arrival/offload destination station if the contractor’s aircraft arrives at the blocks more than 1 hour after the scheduled arrival time.

4.2.6. The contractor‐uncontrollable delay time experienced at the originating and en route stations on a mission shall be added to the scheduled final arrival/offload destination station for purposes of determining the scheduled arrival time at the turnaround mission’s final arrival/offload destination station on that mission.

4.2.7. Carrier Performance: The carrier operating passenger missions shall maintain a 95% schedule reliability rate as the minimum acceptable standard of performance during a three‐ month period. Delay calculation applies to an entire round trip. Failure to maintain a 95% schedule reliability rate for a three‐month period will be reason for termination, pursuant to Federal Acquisition Regulation (FAR) 52.212‐4(m). However, nothing in this paragraph shall limit the right of the government to terminate this contract for other reasons or to limit any other rights and remedies provided the government by law or under this contract.

4.2.8. The contractor shall adhere to the schedule published by the PRSC 611th Traffic Management. Whenever any contractor operated aircraft delays beyond the 4-hour arrival/turnaround limit, the reason for the delay will be passed to the PRSC 611th Traffic Management as soon as possible, but not later than (NLT) 1500 local time (L) of the same day as the delay is incurred. If the delay is incurred after 1500L, the reason for the delay will be passed to the PRSC 611th Traffic Management NLT 0900L of the following calendar day. On the day of mission execution, changes to the PRSC 611th Traffic Management schedule may be made by the Capability Forecaster or the Aerial Port Duty Officer. In this case, delays will be measured against the amended schedule.

4.2.9. The Contractor shall notify the COR immediately in the event of a contractor-controllable delay (mechanical, crew, etc.) or Not Mission Capable (NMC) status. In the event of the aircraft becomes NMC a Get-Well Plan Standard Operating Procedure (SOP) shall be submitted within 24 hours. Get-Well Plan SOP shall be specific and detailed and address contractor plan of action to minimize service disruption and impact to mission in the event of delay in schedule due to contractor controllable delay as defined in paragraph

4.0 Schedules and 4.2 Schedule Reliability. At a minimum the Get-Well Plan SOP shall address action(s) the Contractor will take as well as timelines to become fully mission capable (FMC) to include as applicable, securing replacement of crew members, replacement/spare aircraft parts, availability of aircraft mechanics, and availability of alternate CARB-approved aircraft in accordance with paragraph 3.4 Substitute Aircraft to minimize schedule delay, impact to mission and NMC status. Contractor shall adhere to Get-Well Plan SOP to promptly address issue(s) and return to FMC status minimizing impact to mission and down time. Contractor shall provide daily status updates to the COR until returned to (FMC).

4.2.10. The contractor shall not deviate from the scheduled points of landing without prior approval of the PRSC 611th Traffic Management, except in a bona fide emergency.

5. GOVERNMENT FURNISHED SERVICES AND EQUIPMENT

5.1. Military Station Landings

The government will provide the following services for all landings made at military installations (originating, en route, and terminating stations) at no cost to the contractor except as otherwise provided in this paragraph. The services prefaced with an asterisk (*) will be available only at JBER AK, Eielson AFB AK, and King Salmon AFS AK:

a. Transient alert and ramp services to include:

(i) *landing;

(ii) *follow‐me vehicle;

(iii) *towing (a qualified contractor representative will be in cockpit during towing operations);

(iv) *parking;

(v) *chocking and grounding of aircraft;

(vi) *positioning, connecting, operating, and de-positioning of aircraft ground power unit;

(vii) *fire guard for engine starts;

(viii) *positioning, connecting, operating, and de-positioning of engine start carts;

(ix) *positioning, operating, and de-positioning of compressor for airing of struts and tires.

Nitrogen may be used when available to inflate aircraft tires. A qualified contractor technical representative will be present to supervise;

(x) *position, de-position, and supervise the operation of aircraft axle jacks for tire changes. A technically qualified contractor representative will jack the aircraft;

(xi) *ramp sweeping;

(xii) * to‐plane service of hydraulic fluid and supply of oxygen (gaseous or liquid oxygen (LOX)) on a reimbursable basis. Equipment and necessary operators will be furnished for wing de‐icing at no cost; the de‐icing fluid will be furnished on a reimbursable basis;

(xiii) *maintenance stands, when required for ground servicing operations;

(xiv) *to‐plane fuel servicing. A contractor representative will connect/disconnect the fuel hose to/from the aircraft Single Point Refueling (SPR), and control the flow of fuel into the plane; and

(xv) *Chief Servicing Supervisor (CSS) and fuel unit monitors, in accordance with T.O.

00‐25‐172, when a concurrent ground servicing is accomplished.

b. Terminal and traffic services to include:

(i) loading, tie down and unloading. Loading will be in accordance with the load breakdown provided by the contractor on the Load Planning product or Cargo Manifest.

The load supervisor will annotate the form to show the actual load;

(ii) cargo manifesting;

(iii) cargo handling equipment and associated cargo restraining nets;

(iv) flight line transportation for crews;

(v) *fleet service; and

(vi) provide access to specified parking spots and flight line drivers training.

c. Fire and crash rescue support.

d. Aircraft clearance facilities and Base Operations Support.

e. Emergency medical services to contractor aircrews and personnel on a reimbursable basis.

f. Weather forecasting.

5.2. Billeting and Messing

Billeting and messing for contractor’s crews and government owned property required in support of this contract, not specifically provided for in other provisions of this contract, will be provided by the government at the discretion of the commanding officer of the military installation involved.

Any expenses incurred by the contractor for billeting and messing for contractors’ crews shall be borne by the contractor; however, in the case of authorized delays such as weather or government direction, the contractor may be reimbursed. If the delay is a result of mechanical delay or other contractor-controlled events, the contractor shall not be entitled to reimbursement by the government. Other services at military bases, where commercial services are not available, or not available on a timely basis may be made available to the contractor on an emergency basis only, as determined by the CO. Aerospace Ground Equipment (AGE) and traffic handling and servicing equipment, with necessary operators shall be furnished without charge to the contractor. Technical services and maintenance labor provided, as well as supplies and parts issued, shall be on a reimbursable basis and in accordance with and subject to the provisions of applicable DoD/Air Force and local installation guidance.

6. MAINTENANCE

6.1. No scheduled maintenance except en route, turnaround service, and safety of flight items will be accomplished at military installations under the terms of this contract, except as otherwise authorized by the PRSC 611th Traffic Management when deemed to be in the best interest of the government.

6.2. If any maintenance service is to be performed including en route, turnaround, safety of flight, or scheduled maintenance during ground time of aircraft of the 611th Air Force installations, the contractor will notify the COR and CO as follows:

a. specific type of maintenance to be performed;

b. anticipated duration;

c. type of government‐furnished service in conjunction with performance of the turnaround or en route maintenance service;

d. any reimbursable support desired in conjunction with performance of the turnaround or en route maintenance service; and

e. any change in status or type of work to be performed subsequent to initial notification to the COR will be immediately communicated to PRSC 611th Traffic Management. PRSC 611th Traffic Management will coordinate the above information with maintenance control to assure proper spotting of the aircraft in relation to the degree of hazard associated with the maintenance work to be performed. Other interested base agencies will be notified by PRSC 611th Traffic Management. Requests for reimbursable services will be passed from the PRSC 611th Traffic Management to the COR, who will arrange for performance of the required services.

7. FUEL SERVICE

7.1. The contractor may purchase petroleum products at US military locations for use while performing DoD business hereunder. Purchase of petroleum products by the contractor at any US military location shall be in accordance with FAR Part 51 and DoD 4140.25M. When available, petroleum products will be furnished to the contractor at the DoD standard price (see PWS paragraph 9.4). A fuel purchase agreement with Defense Logistics Agency – Energy (DLA Energy) is required. Contact DLA Energy using DLAENERGYFPA@dla.mil.

7.2. The pilot in command will be present for supervision and control of contractor personnel/equipment during aircraft fuel servicing. All concurrent aircraft refueling services will be conducted in accordance with Technical Order 00‐25‐172.

8. CONTRACTOR PERSONNEL

a. All contractor personnel shall comply with all pertinent military regulations and/or directives when in base flight patterns and on military installations. Regulations can be obtained from the Airfield Operations Managers. The regulations include but are not limited to presenting valid identification for installation entrance; obtaining and using vehicle passes for all contractor‐owned vehicles; obeying all posted directives; and providing strict adherence to security police direction in instances where security police have been dispatched to a particular location.

b. Derogatory Information. If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests or endangers the security of the United States of America, that employee shall be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contractor personnel during the course of the contract’s period of performance as noted in Defense Information System for Security (DISS). Personnel who have incident reports posted in DISS will be denied the ability to support the contract until the issues have been resolved and the incident has been removed in DISS. The contractor shall make any changes necessary in the mailto:DLAENERGYFPA@dla.mil appointment(s), at no additional cost to the Government. If any incident involves or may involve the mishandling of classified information or a potential Negligent Discharge of Classified Information, the USTRANSCOM TCJ3-M, Mission Assurance Division (618-220-6538/6531) will be notified within 24 hours during the normal work week and within 72 hours if the incident occurs over the weekend.

8.1. Health and Safety on Government Installations.

8.1.1. In performing work under this contract on a Government installation, the contractor shall:

8.1.1.1. Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way preserve the health and safety of contractor and Government personnel; and

8.1.1.2. Take such additional immediate precautions as the Contracting Officer may reasonably require for health and safety purposes.

8.2. The Contracting Officer may, by written order, direct applicable installation occupational safety and health standards and/or health/safety standards as may be required in the performance of this contract and any adjustments resulting from such direction will be in accordance with the Changes clause of this contract.

8.3. Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the Contracting Officer, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

9. REIMBURSABLE SERVICES AND COSTS

9.1. Reimbursable expenses shall be identified as separate items and shall be supported by paid receipts and submitted to the COR for approval. All indirect costs, such as overhead, G&A, profit, etc., are specifically prohibited.

9.2. In the event the contractor is requested by the government to care for passengers during a mission delay or diversion, which is not a contractor controllable delay, the government will reimburse the contractor using the principles of FAR 31.205-46, Travel Costs.

9.3. In the event the contractor’s crew is required to remain overnight, the contractor will be reimbursed per diem rates consistent with the Joint Travel Regulation (JTR), Federal Civilian Employees and Contractor Travel Expenses Act of 1985 and FAR 31.205‐46(a)(2), during the performance period of this contract for each authorized overnight lodging. Food and lodging arrangements are the contractor’s responsibility.

Claims for food/lodging expenses shall be supported by paid receipts in accordance with FAR 31.205-46(a)(3)(iv). See Section 5.2 for more information.

9.4. Reimbursable Fuel Costs. The Government will provide DLA-sourced fuel at the main operating locations of JBER (PAED) and AEFS (PASY). The contractor may purchase fuel at off-station sites as mission requirements dictate; however, DLA is the preferred source of fuel. Fuel costs that exceed DLA prices, when DLA-sourced fuel is reasonably available, will only be reimbursed at the DLA-source rate. Fuel costs for contract flights will be billed on a time and materials basis. Fuel for non-contract flights should be purchased by the contractor and will not be reimbursed by the Government. Contractor flights not directed by the Government are non-billable, e.g., flights to an offsite maintenance location. Fuel reimbursement shall be identified as separate items and shall be supported by paid receipts that will be submitted to the COR for payment. All indirect costs, such as overhead, G&A, profit, etc. are prohibited.

10. CANCELLATIONS, DIVERTED, DELAYED LOITERING, AND RE‐ROUTED

FLIGHTS

10.1. Cancellations

a. In the event a flight is canceled prior to the scheduled departure time, or substitute service is used at the point of origination of the flight or en route, due to contractor controllable reasons, movement of any aircraft into and out of scheduled service will be at the contractor’s expense. The contractor shall notify the COR immediately of any delay of aircraft departure including the reason thereof.

b. Should the government cancel a scheduled flight after the contractor’s aircraft has already departed its home base en route to position or has already positioned for a scheduled flight when notice of cancellation is given, the government shall reimburse the contractor positioning and re-positioning costs at the established flight hour unit price using actual flight hours flown (carrier will provide logbook/automated entry times). The government will incur no liability for costs until the aircraft departs the base of operations to position at JBER.

10.2. Diverted, Delayed, Loitering, and Re‐Routed Flights

a. The PRSC 611th Traffic Management may divert, re‐route, or request an aircraft to loiter as long as it is to any route within the same area of operation.

b. For the diverted, request to loiter, or re‐routed airlift contemplated by paragraph 10.2.a. above, the contractor shall, in all such instances, furnish the required flight hours of air transportation specified in the PRSC 611th Traffic Management or Capability Forecasting directives, or in accordance with all the terms and conditions of this contract. For aircraft requested to loiter, follow the mathematical formula for determining reimbursable per unit flight hours as set forth in paragraph 2.8.4 above. The contractor shall comply with all directions, including those given orally, of the PRSC 611th Traffic Management concerning diverted or re‐routed airlift.

c. If a mission is delayed due to a contractor controllable delay (includes maintenance delays), the contractor shall provide snacks if the delay extends over a normal meal period, for all passengers manifested. If the delay requires an overnight stay, the contractor is responsible for meals, transportation, and billeting for those passengers manifested. If the delay or diversion is not a contractor controllable delay, care of the passengers shall be the responsibility of the government

(contractor arranges passenger care if requested on a government reimbursable basis with COR approval).

11. CONTRACT ADMINISTRATION AND MANAGEMENT

11.1. The contractor shall furnish to the CO, the name of a person and POC who will serve as a liaison between the contractor and government. This person must have authority to adjust schedules, engage substitute airlift, and make decisions pertinent to the airlift, in the name of the contractor.

11.2. Schedules will be provided by the PRSC 611th Traffic Management.

12. INVOICING

Invoices shall be submitted monthly through Procurement Integrated Enterprise Environment (PIEE) WAWF e-Business Suite.

13. DELIVERABLES SCHEDULE/SERVICE DELIVERY SUMMARY

13.1. Deliverables Schedule Table

All deliverables shall be submitted directly to the COR electronically in Microsoft Office format (e.g., Word, Excel, Power Point, Project). Deliverables shall be identified by contract number/task order number, PWS task/subtask number, and deliverable title. All deliverables must meet professional standards and comply with the requirements set forth in this PWS.

PWS Para. Deliverable Title Initial Delivery Due Date Government Review Time Frame

4.2.9. Get-Well Plan SOP Within 72 hours of when

aircraft becomes NMC;

and daily updates until aircraft is FMC.

Within 24 Hours.

14.2 Cybersecurity

Incident Reporting

As soon as practical but no later than 72 hours after discovering a reportable cyber-incident;

Follow-on cyber-incident report within 5 days of becoming aware of a reportable cyber-incident

Ongoing until cyber-incident is resolved.

13.2. Service Delivery Summary (SDS).

The SDS represents the most important contract objectives. Although not all PWS requirements are listed in the SDS, the contractor is fully expected to comply with all requirements in the PWS.

Desired

Outcome

PWS

Para

Performance Threshold (Metric)

Source of Data

How Often Collected

Calculation

Provide timely passenger and cargo transportation services.

4.0 Schedule

and 4.2.7 Carrier Performance Schedule Reliability

95% of the time measured quarterly;

computed on a rolling three-month average

In-Person Inspection

Monthly # of on-time flights in the last three months/ # of total flights in the last three months*100

Operational Reliability

3.3 Aircraft

and 4.2.9 Schedule Reliability

No more than two instances of aircraft in an NMC status for more than 72 per year

Get-Well Plan SOP

Notification of

NMC

# of instances aircraft is in an NMC status more than 72 hours per year

Cyber-Incident Reporting.

14. Cyber Security

No more than one late cyber-incident report or unreported cyber-incident in a 12-month period

Submitted (or Discovered) Cyber- Incident Reports

As required # of late reports or unreported cyber-incidents per 12-month period

14. CYBER SECURITY

14.1. Operationally Critical Support

The services designated under this contract are “operationally critical support” as defined in Defense Federal Acquisition Regulation Supplement DFARS 252.204-7012.

14.2. Cybersecurity Incident Reporting

14.2.1. In addition to the DFARS 252.204-7012 reporting requirements for unclassified systems and DoD Manual (DoDM) 5220.22, National Industrial Security Program Operating Manual (NISPOM) for classified systems, reportable cyber-incidents include, but are not limited to, the following:

14.2.1.1. Cyber-incidents as defined in Table 1.

14.2.1.2. Notifications by a federal, state, or local law enforcement agency or cyber-center (i.e., National Cyber Investigative Joint Task Force (NCIJTF), National Cybersecurity & Communications Integration Center (NCCIC)) of being a victim of a successful or unsuccessful cyber-event, anomaly, incident, insider threat, breach, intrusion, or exfiltration.

14.2.1.3.

Cyber Security Table 1.

Incident Category Description Root Level Intrusion Unauthorized privileged access to an Information System (IS).

Privileged access, often referred to as administrative or root access, provides unrestricted access to the IS. This category includes unauthorized access to information or unauthorized access to account credentials that could be used to perform administrative functions (e.g., domain administrator). If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

User Level Intrusion Unauthorized non-privileged access to an IS. Non-privileged access, often referred to as user level access, provides restricted access to the IS based on the privileges granted to the user. This includes unauthorized access to information or unauthorized access to account credentials that could be used to perform user functions such as accessing Web applications, Web portals, or other similar information resources. If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

Denial of Service Denial of Service (Incident)—Activity that denies, degrades, or disrupts normal functionality of an IS or DoD information network.

Malicious Logic Installation of software designed and/or deployed by adversaries with malicious intentions for the purpose of gaining access to resources or information without the consent or knowledge of the user. This only includes malicious code that does not provide remote interactive control of the compromised IS. Malicious code that has allowed interactive access should be categorized as Root or User Level Intrusion incidents. Interactive active access may include automated tools that establish an open channel of communications to and/or from an IS.

Ransomware Malware designed to encrypt files on a device, rendering any files and the systems that rely on them unusable. Malicious actors then demand ransom in exchange for decryption. Ransomware actors often target and threaten to sell or leak exfiltrated data or authentication information if the ransom is not paid. Ransomware is a reportable incident that may be associated with multiple incident categories depending on the attack vector and execution.

14.2.2. If the cyber-incident affects a classified system, vulnerabilities associated with the incident will be classified per the current version of USTRANSCOM Instruction 31-02, Security Classification Guide.

14.3. Cybersecurity Incident Reporting Timelines

In addition to providing the notification required by DFARS 252.204-7012, the contractor is required to notify USTRANSCOM as soon as practical, but no later than 72 hours after discovering a reportable cyber-incident. The reporting timeline begins when the incident is discovered or reported to the company, its employees, contractors, or cybersecurity firm responsible for providing cybersecurity and response for the company. The contractor shall contact the USTRANSCOM Cyber Operations Center (CyOC) via phone at 618-817-4222 or at provided designated telephone number. If the contractor does not immediately reach the CyOC via phone, the contractor shall send an email notification to transcom.scott.tcj6.mbx.cyoc-dodin-operations@mail.mil.

14.4. Mandatory Reporting Data

14.4.1. The contractor shall work with the USTRANSCOM CyOC through resolution of the incident.

Within 72 hours of becoming aware of a reportable cyber-incident, the contractor shall provide an initial notification of the incident, even if some details are not yet available, which includes, but is not limited to, the following information:

(a) Company Name

(b) Who will be the POC with contact information

(c) Contracting Officer POC (name, telephone, email)

(d) Overall Assessment –Description of incident, data at risk, mitigations applied

(e) Indicators of compromise

(f) Vector of attack (if known)

(g) Estimated time of attack (if known)

14.4.2. The contractor shall provide a follow-on cyber-incident report to the USTRANSCOM CyOC within 5 calendar days of becoming aware of a reportable cyber-incident, which includes, but is not limited to, the following information:

(a) Contractor unique Commercial and Government Entity (CAGE) code

(b) Contract numbers affected

(c) Facility CAGE code where the incident occurred if different than the prime Contractor location

(d) POC if different than the POC recorded in the System for Award Management (name, address, position, telephone, email)

(e) Contracting Officer POC (name, telephone, email)

(f) Contract clearance level

(g) DoD programs, platforms, systems, or information involved

(h) Location(s) of compromise

(i) Date incident discovered

(j) Type of compromise…