N0018918Q1508_Draft_PWS.docx

PERFORMANCE WORK STATEMENT

COMMANDER, NAVAL AIR FORCE RESERVE (CNAFR)

MISSION PLANNING SOFTWARE PRODUCT SUPPORT SERVICES

1.0 INTRODUCTION: The purpose of this Performance Work Statement (PWS) is to define the requirements for Mission Planning Technology Services Support for the Commander, Naval Air Forces Reserve.

2.0 BACKGROUND: Mission Planning Product Support consists of access to on-line software and web-based applications that allow aircraft pilots access to maps, charts, weather, intelligence and aircraft performance data for their use in developing mission planning navigation solutions such as routes, approaches, terminal procedures, communications setting, flight/mission calculations (fuel and leg times,) and other pertinent aircraft operational data. Mission Planning Product Support may include access to visual on-line software or web-based tools and applications optimized for specific aircraft roles, and the automation of the computations associated with aircraft specific flight/mission planning. Once the mission planning information has been generated, it can be printed as hardcopy for kneeboards or strip charts, or alternatively written on to a data storage device or for transfer to aircraft systems navigation system, or saved on a laptop or electronic kneeboard. Some Mission Planning Product Support includes 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. Mission Planning Product Support may also be used for post-flight/mission debriefing. This Mission Planning Product Support is required for aircraft assigned to Commander, Fleet Logistic Support Wing (CFLSW) and the 4th Marine Air Wing (4th MAW). The numbers and Types/Models/Series of the aircraft currently assigned to CFLSW and 4th MAW includes the C-37A/B (4ea); the C-20G (2ea); the C-130T (24ea); the C-40A (15ea); the KC-130T/J (18ea); the UC-35C/D (5ea), and the C-12W (2ea), for seventy (70) aircraft.

C-40A - (Currently - 15) Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 168981 Fleet Logistics Support Squadron - 57 (VR57) - 165835, 165836, 166693 Fleet Logistics Support Squadron - 58 (VR58) - 165829, 165832, 165834 Fleet Logistics Support Squadron - 59 (VR59) - 165830, 165831, 165833 Fleet Logistics Support Squadron - 61 (VR61) - 168980, 166695, 169036

C-130T - (Currently - 24) Fleet Logistics Support Squadron - 53 (VR53) - 164995, 164997, 164998, 165350, 165351 Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165160, 165313, 165314, 165348, 165349 Fleet Logistics Support Squadron - 64 (VR64) - 164993, 164996, 164161, 164378, 164379

C-20G - (Currently - 3) Fleet Logistics Support Squadron - 51 (VR51) - 165152 Executive Transport Detachment – Sigonella (ETD Sig) - 165151

C-37A/B - (Currently - 4) Executive Transport Detachment – Pacific (ETD Pac) - 166375 (C-37A) Fleet Logistics Support Squadron - 1 (VR1) - 166376, 166377, 166378 (C-37B)

KC-130J – (Currently - 5) Marine Aerial Refueler Transport Squadron - 234 (VMGR 234) - 165739, 166473, 168073, 169018, 167111

**By the end of the FY VMGR 234 will have 5 KC-130J / FY 2017-7 / FY 2018-9 / FY 2019-12/ FY 2020-12 (Increase of 7 aircraft by FY 2020 for a total of 12 C-130J/T’s.)

KC-130T - (Currently 13) Marine Aerial Refueler Transport Squadron - 452 (VMGR 452) - 163592, 164105, 164180, 164181, 164441, 164442, 164999, 165162, 165163, 165315, 165316, 165352, 165353

UC-35C/D – (Currently - 5) Marine Transport Squadron Detachment Belle Chasse (VMR DET BELLE CHASSE) - 165740, 165741

VMR DET ANDREWS AFB - 166374, 166714, 166767

C-12 – (Currently - 2) Marine Transport Squadron Detachment Belle Chasse (VMR DET BELLE CHASSE) - 168204, 168205

3.0 SCOPE: In support of CNAFR, the Contractor shall provide Mission Planning Technology Services Support for CFLSW and the 4th MAW in the areas of web-based planning, web-based access, electronic charts, on-line access, aircraft performance data, Airport Ad Hoc and Watch lists, Onboard Performance Tool Airport data for the C-40A, Navigational Data for the C-40A, Integrated Navigational Data services for the C-20G, C-37A and C-37B, C-130T Dual Garmin GNS480 Navigation Data, and Navigational Data for the C-37A and C-37B, Special Aircraft Mission (SAM) Dispatch Services and the Creation of Mission Folders. The details of the support are provided in Section 5 Performance Requirements.

4.0 APPLICABLE DIRECTIVES:

· OPNAVINST 3710.7U NATOPS General Flight and Operating Instructions

· FAR 121.191 Operational Limits with One Engine Inoperative

· FAR 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: This section will outline the contractor services and support for Information Technology requirements for the following:

5.1 WEB-BASED PLANNING / ACCESS: The contractor shall provide web-based access for advanced flight planning functions anywhere, anytime pilots can get worldwide Internet access in order to create, modify, cancel, and file computer flight plans, check up to the minute weather and Notice to Airman (NOTAMs) and be assured that the aeronautical data is always current. No special or dedicated software or hardware is needed, only access to the Internet using any internet browser. The web-based planning/access support shall provide for the following capabilities:

5.1.1 The contractor shall provide a secure, easy-to-use, browser-based interface and feature-rich architecture requiring user name and password that can be accessed through existing internet service provider. DELIVERABLE: Web-based Planning Access for advanced planning functions.

5.1.2 The contactor shall provide 24/7 technical assistance to include flight planning support and software support.

5.1.3 The contractor shall provide the capability to create and save an unlimited number of flight plan requests. The contractor shall provide the ability to access flight plans performed at home base on the personal computers (PC) component, as well as rerun these plans and have the home base access them.

5.1.4 The contractor shall create worldwide optimized flight routes (4D-Optimization) based on cost, cargo loads, fuel efficiency, or time enroute.

5.1.5 The contractor shall provide dispatch center services that give users a tabular view of flight plans.

5.1.6 The contractor shall create and display mission patterns that can be used in flight plans.

5.1.7 The contractor shall create and plot user defined waypoints that can be used in flight plans.

5.1.8 The contractor shall provide electronic Air Traffic Control (ATC) flight plan filing. The user should be able to file the flight plan online as well as see the status of the flight plan (i.e., was the flight plan received, accepted, rejected, or modified).

5.1.9 The contractor shall provide drift down operational flight plans that assist in verifying compliance with Federal Acquisition Regulation (FAR) 121.191, which defines operational limitations with one engine inoperative, and FAR 121.193, which defines operational limitations with two engines inoperative.

5.1.10 The contractor shall create Re-clear or Re-Dispatch flight plans to reduce the legally required fuel uplift by reducing the international reserve or contingency fuel requirement.

5.1.11 The contractor shall provide the capability to retrieve, view, print and save an unlimited number of enhanced flight plans, weather NOTAMs on a 24-hour basis.

5.1.12 The contractor shall provide the ability to tailor graphical and text output formats to customer needs.

5.1.13 The contractor shall provide the capability to plan payload off-load operations.

5.1.14 The contractor shall develop user defined avoid areas.

5.1.15 The contractor shall provide the capability to easily modify and resubmit saved requests.

5.1.16 The contractor shall provide the ability to automate flight plan requests, weather requests and transmissions using time-triggering.

5.1.17 The contractor shall transmit flight plans, weather, messages and NOTAMs via email, datalink, Aeronautical Radio Incorporated (ARINC), Aeronautical Fixed Telecommunications Network (AFTN) and facsimile (FAX).

5.1.18 The contractor shall provide the capability to retrieve, view, print and animate graphical weather (WX) maps.

5.1.19 The contractor shall provide Electronic Route Availability Documents (ERAD) and Conditional Route Availability Message (CRAM) compliant routes automatically accepted by EuroControl and provide access to EuroControl’s Central Flow Management Unit (CFMU) website to verify flight plan status. In the event the web-based planning software is unable to yield a validated flight plan, the contractor shall provide 24/7/365 dispatch support to coordinate with aircrew and air traffic control agencies to achieve a valid flight plan route.

5.1.20 The contractor shall provide the capability to retrieve and view enroute changes and Flight Information Region/Upper Information Region (FIR/UIR) traversals.

5.1.21 The contractor shall overlay flight plan routes and weather graphics on enroute charts.

5.1.22 The contractor shall view and compare planned routes against Extended Twin-Engine Operations (ETOPS) and other constraints.

5.1.23 The contractor shall display route profiles in relation to terrain and restricted airspace.

5.1.24 The contractor shall auto-populate military flight plan forms DD-175 and 1801, as well as Inter-national Civil Aviation Organization (ICAO), Federal Aviation Administration (FAA) and Aviation Supply and Academics (ASA) forms.

5.1.25 The contractor shall determine point of safe diversion for missions.

5.1.26 The contractor shall provide worldwide terminal and enroute weather information.

5.1.27 The contractor shall provide access to the worldwide NOTAM database.

5.1.28 The contractor shall provide access to the worldwide airport database.

5.1.29 The contractor shall provide flight plans that can be up loaded to an aircraft Flight Management System, tailored to the particular flight management system for the aircraft requesting the flight planning information.

5.1.30 The contractor shall provide the capability to the Wing or Squadrons to create databases using the web based planning tool that will assist users in minimizing inputs such as: Airport, Aircraft, Route, Alternate, Restricted Area and Flight Brief databases.

5.1.31 The contractor shall provide 28-day Aeronautical Information Regulation and Control (AIRAC) cycle aeronautical data updates via website update

5.1.32 The contractor shall provide 30 training quotas annually for Web Base Flight Planning Tool (classes can be organized into three sessions with ten (10) quotas each and or can be conducted once during the year with all 30 quotas or spread out throughout the year into smaller quotas to maximize the exposure of personnel to the product) in order to train new and current users on the web based flight planning tool. Training can be web based or at customer’s training facility. Provide three (3) training days (classes are designed to train the user to a proficient level). Note: training will be accomplished primarily at fleet concentration areas; Fort Worth Naval Air Station (NAS) Joint Reserve Base (JRB), Joint Base (JB) Andrews, JB McGuire, NAS Jacksonville FL, NAS North Island and New Orleans NAS JRB.

5.2 GLOBAL NAVIGATION AND PLANNING CHARTS. The contractor shall provide Global Navigation and Planning Charts. This is a quarterly replenishment requirement and includes the following sets:

· North Atlantic Plotting Chart.

· Mid Pacific Plotting Chart.

· East Pacific Plotting Chart.

· North Pacific Plotting Chart.

· South Pacific Plotting Chart.

5.3 ELECTRONIC FLIGHT BAG (EFB). The contractor shall provide Flight Information Publications, including terminal instrument approach procedures, arrival and departure procedures, and enroute navigational charts compatible with the Electronic Flight Bag (EFB) Apple iPad hardware and Apple iOS operating systems software. The contractor shall supply a minimum of 400 application licenses on an annual basis.

DELIVERABLE: 400 EFB licenses.

· The application shall be fully developed and fielded, with demonstrated previous performance in the military and/or commercial aviation industry.

· The application shall display Flight Information Publications (FLIP), including:

· All Federal Aviation Administration National Aeronautical Charting Office FLIP data.

· All National Geospatial-Intelligence Agency (NGA) FLIP products or the ability to import and display NGA FLIP data.

· Terminal Instrument Approach Procedures.

· The application shall display IAP in identical format to the standard published paper version. This PWS defines standard published paper versions as those published by FAA/National Aeronautical Charting Office (NACO) and NGA.

· Arrival Procedures.

· Departure Procedures.

· Airport/Taxi Diagrams.

· Airport Facility Directories.

· Enroute Navigational Charts (Instrument Flight Rules (IFR) High/Low, Visual Flight Rules (VFR) Sectionals).

· Application shall display enroute navigational charts in a seamless, geographically contiguous format.

· Application shall include preflight/in-flight planning functions, including:

· Ability to construct a flight plan and display the planned route of flight on enroute charts.

· Ability to enter user-defined waypoints and display those waypoints on enroute charts.

· Ability to print paper backups of FLIP products such as IAP form within the application.

· Ability to accurately measure distance between two points on enroute charts.

· Application shall include usability functions, including:

· Support for Apple iOS multi-touch gestures, including pinch-to-zoom, while displaying FLIP products.

· Night settings that make the display more suitable for nighttime operations.

5.4 Aircraft Performance Data: The contractor shall provide Aircraft Performance data pertaining to takeoff, climb, range, endurance, decent and landing which includes aircraft weight, atmospheric conditions, runway environment, and the fundamental physical laws governing the forces acting on the aircraft. The contractor Aircraft Performance Data shall include the following:

5.4.1 Aircraft performance data to run algorithms against airport and environmental data to determine Maximum Take Off Weight (MTOW).

5.4.2 Maximum Take Off Weight (MTOW), power settings and critical airspeeds (V speeds) which include:

5.4.2.1 Aircraft specific – built from the appropriate type/model/series NATOPS or Commercial Aircraft Publications Aircraft Flight Manual (AFM).

5.4.2.2 Airport and runway specific – considers runway length, obstacles within the departure path and other airport specific factors;

5.4.2.3 Aircraft configuration specific – includes calculations for multiple flap settings, power settings and other aircraft configurations; and

5.4.2.4 Environmental conditions specific – incorporates temperature, winds and runway contamination (runway wet/dry etc.).

5.4.3 Runway specific graphical Special Departure Procedures (SDPs) designed to maximize the allowable gross takeoff weight while remaining a safe distance from terrain and obstacles. Delivered via a website that enables aircrews and dispatchers convenient access to their performance data and the ability to select 100 airports from over 3,500 airports worldwide.

5.4.4 Easy access to performance data via the Internet.

5.4.5 Calculation of MTOW, V speeds, critical field lengths and power settings for a range of temperatures.

5.4.6 Calculations designed to maximize payloads while adhering to International Air Transport Association (IATA) and International Civil Aviation Organization (ICAO) obstacle avoidance regulations.

5.4.7 Color graphical SDPs that are easy to read and depict the safest departure flight path in case of an emergency. The following Units: C-130T and KC-130J/T Aircraft require Aircraft Performance Data:

C-130T - (Currently - 24) Fleet Logistics Support Squadron - 53 (VR53) - 164995, 164997, 164998, 165350, 165351 Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165160, 165313, 165314, 165348, 165349 Fleet Logistics Support Squadron - 64 (VR64) - 164993, 164996, 164161, 164378, 164379

KC-130J – (Currently - 5) Marine Aerial Refueler Transport Squadron - 234 (VMGR 234) - 165739, 166473, 168073, 169018, 167111

KC-130T - (Currently 13)

Marine Aerial Refueler Transport Squadron - 452 (VMGR 452) - 163592, 164105, 164180, 164181, 164441, 164442, 164999, 165162, 165163, 165315, 165316, 165352, 165353

5.5 WATCH AND AD HOC AIRPORT LISTS: The contractor shall ensure airport information is broken into Watch (on surveillance) and Ad Hoc lists. Airports used frequently by the customer (base airports) are placed on Watch for continual use. Ad Hoc airports are those airports that are flown to infrequently or only once. The Contractor shall have 100 airports on Watch list and unlimited Ad Hoc list requests under this contract for the types of aircraft listed in Section 2 above. Airport Watch lists shall be updated annually. Maintenance shall be provided on the customer’s performance module when changes to the AFM are issued that affect performance. It is the customer’s responsibility to inform the contractor when changes to the AFM affect performance. Included under this contract are the following:

5.5.1 100 Airports on surveillance (Watch): (airports shall be changed annually at the request of the customer). DELIVERABLE: Annual Updated 100 Airport Watch List

5.5.2 Number of Ad Hoc requests: Unlimited (aircrew can request ad hoc analysis of airports not on their surveillance list. Requests must be made 48 hours in advance, or 24 hours prior in an emergency, and surveillance will be provided for 7 days. After this period, the Ad Hoc request will be removed from the website).

5.5.3 Unlimited AFM performance changes analysis: (it is the responsibility of the U.S. Navy NATOPS Evaluator Representative of the affected aircraft to notify the Contractor and provide AFM changes to the Contractor).

5.5.4 Textual or graphical SDP engine out procedures, based on an engine loss at V1 Critical Engine Failure Speed (CEFS).

5.6 ONBOARD PERFORMANCE TOOL (OPT) AIRPORT DATA FOR THE C-40A: The contractor shall provide OPT Airport Data which contains the airport obstacle and terrain data to calculate flight profile information which displays airplane performance data to the flight crews for the (15) C40A Aircraft. The actual OPT software is provided and maintained by Boeing under a separate contract. The following Units/C-9B and C-40 Aircraft require OPT:

C-40A - (15)

VR56 - 166694, 166696, 168981

VR57 - 165835, 165836, 166693

VR58 - 165829, 165832, 165834

VR59 - 165830, 165831, 165833

VR61 - 168980, 166695, 169036

5.7 NAVIGATION DATA FOR THE C-40A: The contractor shall provide access to the entire navigation database. Updates to the navigation database shall be provided every 28 days in accordance with the AIRAC update cycle. The Contractor shall deliver Flight Management Computer System updates via direct internet download, 3.5 in Compact Disk/Read Only Memory (CD/ROM), Universal Serial Bus (USB) thumb drive or file transfer protocol (.ftp). The following Units: C-40 Aircraft require Navigation Data:

C-40A - (15)

VR56 - 166694, 166696, 168981

VR57 - 165835, 165836, 166693

VR58 - 165829, 165832, 165834

VR59 - 165830, 165831, 165833

VR61 - 168980, 166695, 169036

5.8 INTEGRATED NAVIGATION DATA SERVICE (INDS) FOR C-20G, C-37A AND C-37B: The contractor shall provide worldwide detailed en-route maps with terrain, obstacles, and navigation data that will display on the aircraft displays. Navigation information should include approach charts, airport charts, departure charts, arrival charts, navigation information, terrain and obstacles, airspace and communication information, geopolitical and geographic boundaries, and airport information. The Data should be delivered via internet download or on DVD with updated Data issued biweekly and contain: 1) Worldwide Coverage; 2) Americas, Military Supplement Coverage; 3) Europe, Military coverage; 4) Pacific Basin, Military Supplement Coverage; 5) Middle east, Military Supplement Coverage; 6) Africa, Military Supplement Coverage; 7) Retail Data and Charts, Terrain Database, Internet Delivery; 8) Retail Data and Charts, G/D, USB Assembly GSN; 9) Retail Data and Charts , G/D Internet Delivery. The following Units/C-20G and C-37A/B Aircraft require INDS:

C-20G - (2)

VR-51 - 165152

ETD Sig - 165151

C-37A/B - (4) ETD Pac - 166375 (C-37A)

VR-1 - 166376, 166377, 166378 (C-37B’s)

5.9 NAVIGATION DATA FOR THE C-130T DUAL GARMIN GNS480: Provide access to the entire navigation database. Updates to the navigation database shall be provided every 28 days in accordance with the AIRAC update cycle. The Contractor shall deliver NavData updates via internet download or on CD ROM. The following Units/C-130 Aircraft require Navigation Data for the C-130 Dual Garmin GNS-480:

C-130T - (24)

VR-53 - 164995, 164997, 164998, 165350, 165351

VR-54 - 164762, 164994, 165158, 165159

VR-55 - 163311, 163591, 164106, 164597, 164598

VR-62 - 165160, 165313, 165314, 165348, 165349

VR-64 - 164993, 164996, 164161, 164378, 164379

KC-130J - (5)

VMGR 234 - 165739, 166473, 168073, 169018, 167111

KC-130T – (13)

VMGR 452 - 163592, 164105, 164180, 164181, 164441, 164442, 164999, 165162, 165163, 165315, 165316, 165352, 165353

5.10 NAVIGATION DATA FOR THE C-37A/B and C-20G: The contractor shall provide access to the entire navigation database. Updates to the navigation database shall be provided every 28 days in accordance with the Aeronautical Information Regulation and Control (AIRAC) update cycle. The Contractor shall deliver Flight Management Computer System updates via internet download, 3.5 CD/ROM, USB thumb drive, or .ftp. .

The following Units/C-37A/B and C-20G Aircraft require Navigation Data:

C-20G - (2)

VR-51 - 165152

ETD Sig - 165151

C-37A/B - (4) ETD Pac - 166375 (C-37A) VR-1 - 166376, 166377, 166378 (C-37B’s)

5.11 SPECIAL AIRCRAFT MISSION (SAM) DISPATCH SERVICES: The contractor shall provide special aircraft mission/flight planning or Dispatch Services to Fleet Logistics Support Squadron One (VR-1), Executive Transport Detachment Pacific (ETD PAC) and Executive Transport Detachment Sigonella (ETD Sig). VR-1 is a three aircraft squadron (C-37B) located at Andrews AFB, Maryland; ETD PAC is a single aircraft detachment (C-37A) located at Hickam AFB, Hawaii and ETD Sig is a single aircraft detachment (C-20G) located at Sigonella, Sicily providing executive transportation services for the U.S. Navy. The C-20G, C-37A and C-37B aircraft all require SAM dispatch services:

C-20G - (1) ETD Sig - 165151

C-37A/B - (4) ETD Pac - 166375 (C-37A) VR-1 - 166376, 166377, 166378 (C-37B’s)

5.11.1 DISPATCH SERVICES: The Contractor shall deliver Contract Dispatch services to VR-1, ETD PAC and ETD Sig on a daily basis to support flight operations. VR-1, ETD PAC and ETD Sig will provide mission tasking information, mission changes and other information required to accurately plan flight operations. Using this information, the Contractor shall create flight plans/flight releases that shall be delivered to VR-1, ETD PAC and ETD Sig via web crew briefing system or fax, as requested by the flight crew. The flight releases shall include weather, NOTAMS and other additional information. The Contractor shall provide charting, prepare and coordinate Diplomatic Clearances (DIPS) and provide flight following services:

5.11.1.1 Flight planning and flight release information.

5.11.1.2 Diplomatic clearance preparation and tracking.

5.11.1.3 Weather (WX) and NOTAMS

5.11.1.4 Delivery of services via web based system or fax.

5.11.1.5 Charting for route of flight via Mission Ops eCharts (MOEC).

5.11.1.6 Filing of flight plans with ATC.

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

5.12 IN-FLIGHT SERVICES: The contractor shall provide in-flight services as requested by VR-1, ETD PAC and ETD Sig to include the following. The contractor shall deliver these in-flight services by ACARS, SATPHONE or via the dispatch site when the aircrew is using the ViaSat Service onboard the aircraft:

5.12.1 WX updates.

5.12.2 ATC coordination.

5.12.4 Emergency assistance.

5.12.5 Creation/dissemination/filing of optimized CFPs. Flight plans shall include weather (WX) and NOTAMS applicable to the route of flight.

5.12.6 Graphical WX charting.

5.12.7 Appropriate MOEC charting for the route of flight.

5.12.8 Mission Planning Services.

5.12.9 Preparation and coordination of assigned missions.

5.12.10 Track changes to missions and make adjustments to flight planning as required.

5.12.11 Preparation, sending and tracking of DIPS.

5.12.12 Coordinate with VR-1, ETD PAC and ETD Sig for sending DIPS that must go by DMS.

5.13 MISSION FOLDER CREATION: Upon notification from VR-1, ETD PAC or ETD Sig of a mission, the Contractor shall create a mission folder on a secure, easy-to-use, browser-based interface requiring user name and password that can be accessed through existing internet service provider. VR-1, ETD PAC or ETD Sig website will be the repository for mission flight plans, WX, NOTAMS, charting and DIPS information. During the planning phase, information in the folder shall be constantly updated as changes are made to the mission, flight plans are modified, diplomatic clearances are requested and received, and other mission information and tasking are being worked. DELIVERABLE: Monthly Mission Folder Creation Report by providing a report NLT 5 days after months end on the number of mission folders created and delivered during the previous month. Make final delivery of the mission package with the following:

5.13.1 Flight plans, WX, NOTAMS at time of filing/takeoff via web based format.

5.13.2 Charting via integrated MOEC route of flight and terminal charting.

5.13.3 Diplomatic clearance spreadsheet listing all required DIP information for the mission.

5.13.4 The contractor shall use mission planning information supplied by VR-1, ETD PAC or ETD Sig to run flight plans which will determine what countries will need diplomatic clearances for both over flight and landing.

5.13.5 Create diplomatic clearance messages in accordance with U.S. DoD Foreign Clearance Guides to request DIPS.

5.13.6 If clearances can be done through standard email/fax or phone calls, process the clearances. Clearances that require DMS messaging shall be forwarded to the individual unit for entry into the DMS system.

5.13.7 Track DIPS and create a DIP sheet for each mission to allow crews easy access to diplomatic clearance information.

5.13.8 The contractor shall follow all FAA regulations and VR-1, ETD PAC and ETD Sig operations manuals (and other manuals) when planning flights. VR-1, ETD PAC or ETD Sig will provide all known minimum equipment lists (MELs) corresponding to each unit’s aircraft. MEL information shall also be passed on as soon as possible after any MEL is determined to affect their aircraft. Pertinent MELs shall be entered into the Jet Plan database. Any MELs that affect aircraft performance and/or operations shall be taken into account when generating flight plans. Prior to generating the flight plan, check pertinent NOTAMS for all departure, destination, and alternate airports before listing these airports on the flight plan. In addition, also check all pertinent Flight Information Region (FIR) NOTAMS along the route of flight. Check all pertinent Terminal Aerodrome Forecast (TAF) and/or Aviation Weather Report (METAR) information for all departure, destination, and alternate airports before generating all flight plans. Store frequently used routes in the database.

5.13.9 The Government will provide basic Mission/Flight/Schedule information as GFI. The Contractor shall prepare and provide the following

w/Schedule

5.14 COMMUNICATIONS: The contractor shall maintain an efficient method of communications between VR-1, ETD PAC and ETD Sig and the Contractor. Regular, daily operational communications between VR-1, ETD PAC and ETD Sig operations and Contractor personnel shall occur and shall be done directly via the existing contact phone, FAX, email, and SITA numbers. In the case of specific questions regarding flight plans, crew members are requested to contact Contractor personnel directly.

5.14.1 The Contractor’s dispatchers shall be available (24/7/365) via VR-1, ETD PAC and ETD Sig Aircraft Communications Addressing and Reporting System (ACARS)/radio communications systems for in-flight assistance

5.14.2 Service and technical telephone conferences or meetings shall be conducted on a regularly scheduled basis and shall include the contractor and VR-1, ETD PAC and ETD Sig Managers. Significant problems and risks shall be communicated immediately to contractor management. Service reviews shall be conducted once per quarter or as applicable. The project review attendees shall:

5.14.2.1 Address current management and technical issues and concerns.

5.14.2.2 Assign and review action items.

5.14.2.3 Review and update schedules.

5.14.2.4 Identify risks and efforts to mitigate them.

5.14.2.5 Document issues and decisions.

5.14.2.6 The Contractor shall create and maintain a U.S. Navy-specific website for 24/7 access. The contractor shall protect the confidentiality of VR-1, ETD PAC and ETD Sig operations through the use of an encrypted secure (user name and password protected) website delivery and other methods.

6.0 PERIOD OF PERFORMANCE:

This purchase order will include a six-month base period and a one-year option period. The performance periods are as follows:

· Base Period: 01 June 2017 through 30 November 2017

· Option Period: 01 December 2017 through 30 November 2018

7.0 TRAVEL: Travel is not authorized for support of this contract/task order.

NON-PERSONAL SERVICES:

The Government and the contractor understand and agree that the services delivered by the contractor to the Government are non-personal services. The parties also recognize and agree that no employer-employee or master servant relationship exists or will exist between the Government and the contractor. Contractor personnel are not employees of the federal Government and are not eligible for entitlement and benefits given federal employees.