General Dispatch PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

COMMANDER, NAVAL AIR FORCE RESERVE (CNAFR)

GENERAL DISPATCH SUPPORT SERVICES

1.0 INTRODUCTION:

The purpose of this PWS is to define the requirements for General Mission (GM) Dispatch Support Services in support of Commander, Naval Air Force Reserve (CNAFR).

2.0 BACKGROUND:

General Dispatch Support Services includes access to on-line software, web-based tools/applications optimized for specific aircraft roles, iOS applications for use on approved tablet/Electronic Flight Bag (EFB), and the automation of the computations associated with aircraft specific flight/mission planning. Once the mission planning information has been generated, it will be made available in deliverable digital format (i.e. PDF) for display on EFBs and other mobile devices including iPads, as well as aircraft navigation systems. Some Dispatch Support Services include functions to transmit and receive flight/mission information via satellite datalink communications, either at the commencement of a flight/mission, or as real time updates throughout a flight/mission. Dispatch Support Services may also be used for post-flight/mission debriefing. These Dispatch Support Services are required for aircraft assigned to Commander, Naval Air Force Reserve (CNAFR) Types/Models/Series of the aircraft assigned include the K/C-130J (12ea), the KCC-130T (25ea); the C-40A (19ea); the UC-35C/D (3ea), and the UC-12F/W (4ea), for a total of sixty-three (63) aircraft.

C-40A - (Currently 19) Fleet Logistics Support Squadron - 51 (VR51) - 166693, 165830 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165792 Fleet Logistics Support Squadron - 57 (VR57) - 165835, 165836, 169793 Fleet Logistics Support Squadron - 58 (VR58) - 165829, 165832, 168980 Fleet Logistics Support Squadron - 59 (VR59) - 165831, 165833, 168981 Fleet Logistics Support Squadron - 61 (VR61) - 166695, 169036, 165834 Marine Reserve Transport Squadron - 1 (VMR1) - 170041, 170042

KC/C-130T - (Currently 25) Fleet Logistics Support Squadron - 53 (VR53) –164995, 165313, 165348, 165349 Fleet Logistics Support Squadron - 54 (VR54) - 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164996, 165379, 163180 Fleet Logistics Support Squadron - 62 (VR62) -, 164598, 164762, 165314, 165378, 165161 Fleet Logistics Support Squadron - 64 (VR64) - 164993, 164998, 165316, 164597, 164441, 165352 Fort Worth RAMCE C-130T: 164994

KC-130J - (Currently 12)

Marine Aerial Refueler Transport Squadron - 234 (VMGR234) - 166473, 166512, 168068, 169018, 169225, 169228, 169229, 167925, 166763, 166764, 165738, 167923

UC-35C/D - (Currently 3) Marine Transport Squadron Detachment Belle Chasse VMR DET ANDREWS AFB - 166374, 166714, 166767

UC-12 - (Currently 4) Marine Transport Squadron Detachment Belle Chasse (VMR DET BELLE CHASSE) - 168204, 168205, 163558, 163561

3.0 SCOPE:

In support of CNAFR, the Contractor shall provide General Dispatch Support Services for the C-40A, C-130T/J, UC-35 and UC-12 aircraft, web-based planning, web-based access, electronic charts, on-line access, aircraft performance data, flight planning services, and the creation of mission folders. The details of the Dispatch Support Services are provided in Section 5 Performance Requirements.

4.0 APPLICABLE DIRECTIVES:

· CNAF M-3710.7 Naval Air Training and Operating Procedures Standardizations (NATOPS) General Flight and Operating Instructions

· 14 CFR Part 121.191 Operational Limits with One Engine Inoperative

· 14 CFR Part 121.193 Operational Limits with Two Engines Inoperative

· Appropriate Military or Commercial Type/Model/Series (T/M/S) Aircraft Flight Manual

4.1 ACRONYMS AND ABBREVIATIONS

5.0 PERFORMANCE REQUIREMENTS:

The products and services in Sections 5.1 and 5.2 are for all the CNAFR, VR aircraft and aircrews. The below sections will outline the contractor support for Dispatch Support Services requirements for the following:

5.1 GM DISPATCH SERVICES: The contractor shall provide Domestic and International general aircraft flight planning and Dispatch Services to all CNAFR C-40, KC/C-130J/T, UC-35, and UC-12 squadrons. General dispatch services shall be based on execution of an estimated 10,000 flight leg segments worldwide annually. For planning purposes, the C-40’s are estimated to execute 58 percent of leg segments and the KC/C-130’s are estimated to execute 40 percent of leg segments. UC-35 and UC-12’s are estimated to execute 2 percent per year. The following aircraft require General dispatch services:

C-40A - (Currently 19) Fleet Logistics Support Squadron - 51 (VR51) - 166693, 165830 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165792 Fleet Logistics Support Squadron - 57 (VR57) - 165835, 165836, 169793 Fleet Logistics Support Squadron - 58 (VR58) - 165829, 165832, 168980 Fleet Logistics Support Squadron - 59 (VR59) - 165831, 165833, 168981 Fleet Logistics Support Squadron - 61 (VR61) - 166695, 169036, 165834 Marine Reserve Transport Squadron - 1 (VMR1) - 170041, 170042

KC/C-130T - (Currently 25) Fleet Logistics Support Squadron - 53 (VR53) –164995, 165313, 165348, 165349 Fleet Logistics Support Squadron - 54 (VR54) - 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164996, 165379, 163180 Fleet Logistics Support Squadron - 62 (VR62) -, 164598, 164762, 165314, 165378, 165161 Fleet Logistics Support Squadron - 64 (VR64) - 164993, 164998, 165316, 164597, 164441, 165352 Fort Worth RAMCE C-130T: 164994

KC-130J - (Currently 12)

Marine Aerial Refueler Transport Squadron - 234 (VMGR234) - 166473, 166512, 168068, 169018, 169225, 169228, 169229, 167925, 166763, 166764, 165738, 167923

UC-35C/D - (Currently 3) Marine Transport Squadron Detachment Belle Chasse VMR DET ANDREWS AFB - 166374, 166714, 166767

UC-12 - (Currently 4) Marine Transport Squadron Detachment Belle Chasse (VMR DET BELLE CHASSE) - 168204, 168205, 163558, 163561

5.1.1 GENERAL DISPATCH SERVICES: The contractor shall provide General Dispatch Services to all CNAFR, UC-35 and UC-12 squadrons daily to support flight operations for any mission that is scheduled through the Navy Air Logistics Office or through a VR scheduling authority outside the continental United States. For such missions, each squadron will provide mission tasking information, mission changes, and other information required for the contractor to accurately plan flight operations a minimum of 72 hours prior to takeoff for the first segment of each scheduled mission. Following the handoff of mission data at the 72-hour point, the contractor shall create flight plans/flight releases that shall be delivered via iOS application, web crew briefing system, email, or as requested by the operations department or the flight crew (email). The flight releases shall include the Computerized Flight Plans (CFP) that were filed with ATC, WX, NOTAMS, FLIP and other pertinent information provided below. The contractor shall provide charting, coordination of DIPS and provide flight planning services:

5.1.1.1 Flight planning and flight release information.

5.1.1.2 DIPS tracking and coordination.

5.1.1.3 WX and NOTAMS.

5.1.1.4 Delivery of services through integrated iOS application/web-based system/email/FAX.

5.1.1.5 Charting deliverable to EFB through integrated iOS application.

5.1.1.6 Filing of flight plans with ATC.

5.1.1.7 Flight Following with someone on the ground monitoring the aircraft when airborne.

5.1.2 GENERAL DISPATCH IN-FLIGHT SERVICES: The contractor shall provide in-flight services as requested by C-40 and UC-35 squadrons for flights via ACARS or SATPHONE:

5.1.2.1 WX updates.

5.1.2.2 ATC coordination.

5.1.2.3 Flight planning changes.

5.1.2.4 Message relay.

5.1.2.5 Emergency assistance.

5.1.2.6 Refiling flight plans and creation of corresponding computerized flight plans.

5.1.2.7 Mission planning services.

5.1.2.8 Tracking changes, sending and updating missions/DIPS.

5.1.2.9 Coordinating with squadron operations representatives.

5.1.3 GENERAL DISPATCH FOLDER CREATION: The contractor shall create a mission folder on a secure, easy-to-use, browser-based interface requiring username and password that can be accessed through existing internet service provider. Squadrons will upload all mission related data 72 hours prior to any mission launch at which point the contractor will assume control of the mission and shall constantly update changes to the mission, flight plan modifications, status of DIPS, and other mission-related information. Additionally, the contractor shall provide an iOS application that will allow the user to retrieve flight plans and flight releases prior to mission departure that interfaces with the EFB and provides expandability to access compatible performance applications and other flight related information pertinent to the mission. DELIVERABLES: (1) Monthly Mission Folder Creation Report by providing a report NLT five (5) days after months end on the number of mission folders created and delivered during the previous month. (2) iOS Application for mission package delivery with EFB interface and expandability. Expandability includes capabilities to interface and link to aircraft performance applications, real-time WX and NOTAM information, and other information/applications as requested by the end user. Final delivery of the mission package shall be accessible through the browser based interface and accessible through an integrated iOS application with internet service with the following:

5.1.3.1 Flight plans, WX, NOTAMS at the time of filing/takeoff.

5.1.3.2 Charting presentable through EFB navigation application or web-based application.

5.1.3.3 DIPS spreadsheet and corresponding Aircraft and Personnel Automated Clearance System (APACS) report listing all required DIP information for the mission.

5.1.3.4 The contractor shall use mission planning information supplied by the squadron to run flight plans which conform to the DIPS requirements disclosed at the 72 hour prior to mission launch point and any updates thereafter.

5.1.3.5 Create DIPS messages or requests via APACS for any additional requirements.

5.1.3.6 Update, request, and track DIPS when required after mission launch.

5.1.3.7 The contractor shall follow all FAA regulations, all C-40A Flight Crew Operations Manuals, C-130 and UC-35 NATOPS flight manuals, CNAFR Standard Operating Procedures (SOP) when planning flights. The CNAFR and subordinate units will provide Aircraft manuals, SOPs and MELs corresponding to each unit’s aircraft. MEL information shall also be disclosed by the squadron 72 hours prior to mission launch point if known; otherwise, the squadron shall communicate any MEL items as soon as discovered after the 72-hour point. Any MEL that affects aircraft performance and/or operations shall be considered when generating flight plans. Prior to generating the flight plan, the Contractor shall check pertinent NOTAMS for all departure, destination, and alternate airports before listing these airports on the flight plan. In addition, the Contractor shall check all pertinent FIR and GPS related NOTAMS along the route of flight and check all pertinent Terminal Aerodrome Forecast and/or Aviation WX Report information for all departure, destination, and alternate airports before generating all flight plans. Frequently stored routes shall be stored in a database.

5.1.3.8 The government will provide mission/flight/schedule information as GFI through the browser based interface 72 hours prior to each mission launch.

5.2 ROUTINE COMMUNICATIONS. The contractor shall maintain an efficient method of communications between all squadrons. Regular, daily operational communications between the contractor and squadron shall occur for GM Dispatch services. Acceptable means of communication are existing dispatch website, contact phone, FAX, emails and SITA numbers. In the case of specific questions regarding flight plans, crew members are permitted and requested to contact contractor personnel directly via phone.

5.2.1 The contractor’s dispatchers shall be available (24/7/365) via all VR Squadron Aircraft Communications Addressing and Reporting System (ACARS)/radio communications systems for in-flight assistance.

5.2.2 Service and technical telephone conferences or meetings shall be conducted on a regularly scheduled basis and shall include the contractor, FLSW, all VR squadron Managers. Significant problems and risks shall be communicated immediately to contractor management. Service reviews shall be conducted once per quarter or as applicable.

5.2.2.1 Address current management and technical issues and concerns.

5.2.2.2 Assign and review action items.

5.2.2.3 Review and update schedules.

5.2.2.4 Identify risks and efforts to mitigate them.

5.2.2.5 Document issues and decisions.

5.2.2.6 The Contractor shall maintain a U.S. Navy-specific website for 24/7 access. The contractor shall protect the confidentiality of all CNAFR squadrons username and password protected) website delivery and other methods.

5.3 MONTHLY CONTRACT STATUS REPORT (MCSR). The Monthly Contract Status Report (MCSR) is prepared by the contractor in contractor format as approved by the Contracting Officer Representative (COR). The MCSR is designed to provide a comprehensive review and analysis of cost, schedule and technical performance for the purchase order. The MCSR report data is used by the COR to evaluate task performance and deliverables provided, to identify the magnitude and impact of actual and potential problem areas which could cause cost or schedule variances from plan, and to provide, valid, timely and auditable task information. The MCSR must be password protected submitted electronically to the COR not later than the fifth working day of each month. The contractor shall send document passwords to the Government points of contact via separate email. The contractor shall have seven (7) calendar days from receipt of the Government response to provide their own response to any questions or challenges raised by the Government.

6.0 PERIOD OF PERFORMANCE

This purchase order will have a one-year base period of performance (01 June 2026 to 31 May 2027 with option years to be decided.

7.0 PLACE OF PERFORMANCE

The primary place of performance for this purchase order shall take place at the contractor’s facility. The contractor may be required to work at other Government facilities as required. See Section 5.1.33 for additional information.

8.0 TRAVEL

Travel is not anticipated for this purchase order. Any nominal travel required is the responsibility of the contractor and will NOT be separately priced.

9.0 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP):

9.1. Purpose: To ensure that the Government has an effective and systematic method of surveillance for the services in the PWS. The QASP will be used primarily as a tool to verify that the contractor is performing all services required by the PWS in a timely, accurate and complete fashion.

9.2. Critical performance processes and requirements. Critical to the performance of Mission Planning and Dispatch Support Services in support of CNAFR is the timely, accurate and thorough completion of all purchase order requirements.

9.3. Performance Standards

9.3.1. Schedule - The due dates for deliverables and the actual accomplishment of the schedule will be assessed against original due dates and milestones established for the purchase order.

9.3.2. Deliverables – The deliverables required to be submitted will be assessed against the specifications for the deliverables detailed in the purchase order for the required content, quality, timeliness, and accuracy.

9.3.3. Past Performance - In addition to any schedule, deliverables, and cost aspects of performance discussed above, pursuant to FAR 42.15, the Government will assess the contractor’s record of conforming to contract requirements and to standards of good workmanship, the contractor’s adherence to contract schedules including the administrative aspects of performance, the contractor’s history of reasonable and cooperative behavior and commitment to customer satisfaction, and the contractor’s business-like concern for the interest of the customer.

9.4. Surveillance methods: The primary methods of surveillance used to monitor performance of this purchase will include, but not be limited to, random or planned sampling, periodic or inspection, and validated customer complaints.

9.5. Performance Measurement: Performance will be measured in accordance with the following table:

If performance is within acceptable levels, it will be satisfactory. If not, overall performance may be considered unsatisfactory.

9.6 Incentives/Disincentives:

The COR’s makes an annual report on Contractor Performance (CPARS or other annual report). The contractor’s failure to achieve satisfactory performance under the purchase order, reflected in the COR’s annual report, may result in termination of the purchase order and may also result in the loss of future Government contract actions.

For each item that does not meet acceptable levels, the Government may issue a Contract Discrepancy Report (CDR). CDRs will be forwarded to the Contracting Officer with a copy sent to the contractor. The contractor must reply in writing within five (5) days of receipt identifying how future occurrences of the problem will be prevented. Based upon the contractor’s past performance and plan to solve the problem, the Contracting Officer will determine if any further action will be taken.

In accordance with the inspection of services provisions of the purchase order, the contractor will be incentivized to provide quality products in a timely manner since the Government can require the Contractor, at no additional cost, to replace or correct work that fails to meet the requirements of the purchase order.