N0018920RZ003_Performance_Work_Statement_(PWS)_-_DRAFT.docx
DOCX document 65 KB Posted
- Attached to
- MISSION PLANNING AND DISPATCH SUPPORT SERVICES
- Solicitation number
- N0018920RZ003
About this file
N0018920RZ003_Performance_Work_Statement_(PWS)_-_DRAFT.docx
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT (PWS)
COMMANDER, NAVAL AIR FORCE RESERVE (CNAFR)
MISSION PLANNING AND DISPATCH SUPPORT SERVICES
1.0 INTRODUCTION
The purpose of this Performance Work Statement (PWS) is to define the requirements for Mission Planning and Dispatch Support Services in support of the Commander, Naval Air Forces Reserve (CNAFR).
2.0 BACKGROUND
Mission Planning and Dispatch Support Services consists of access to on-line software, web-based applications, and iOS applications that allow aircraft pilots access to maps, charts, weather (WX), Notice to Airman (NOTAMs), 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 and Dispatch Support Services may include access to visual on-line software, web-based tools/applications optimized for specific aircraft roles, Apple operating system for mobile devices (iOS) applications for use on approved tablet/electronic flight bag, and the automation of the computations associated with aircraft specific flight/mission planning. Once the mission planning information has been generated, it will be available to be printed as a hardcopy and in deliverable digital format for display on kneeboards, strip charts, aircraft navigation systems, and electronic flight bags. Some Mission Planning and 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. Mission Planning and Dispatch Support Services may also be used for post-flight/mission debriefing. These Mission Planning and Dispatch Support Services are 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 (1ea); the C-130T (24ea); the C-40A (17ea); the KC-130T/J (18ea); the UC-35C/D (5ea), and the UC-12W (2ea), for seventy-one (71) aircraft.
C-40A - (Currently - 17) *Fleet Logistics Support Squadron – 51 (VR51) – 166693, 169792 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165830 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
C-130T - (Currently - 24) Fleet Logistics Support Squadron - 53 (VR53) - 164995, 164997, 164998, 165348, 165351 Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165313, 165314, 165349, 165378 Fleet Logistics Support Squadron - 64 (VR64) – 164993, 164996, 165161, 165379
C-20G - (Currently - 1) 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 - 7) Marine Aerial Refueler Transport Squadron - 234 (VMGR 234) - 165739, 166473, 167111, 168073, 169018, 169228, 169229
KC-130T - (Currently 11) Marine Aerial Refueler Transport Squadron - 452 (VMGR 452) - 164105, 164180, 164181, 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
UC-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 and Dispatch Support Services 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 for the C-37A/B and C-20G aircraft, General Aircraft Mission Dispatch for the C-40A and C-130T aircraft, Flight Planning Services, and the Creation of Mission Folders. The details of the Mission Planning and Dispatch Support Services is provided in Section 5 Performance Requirements.
4.0 APPLICABLE DIRECTIVES
· CNAF M-3710.7 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
| · 4th MAW | 4th Marine Aircraft Wing | |||
| · ACARS | Aircraft Communications Addressing and Reporting System | |||
| · AFB | Air Force Base | |||
| · AFM | Aircraft Flight Manual | |||
| · AFMC | Aircraft Flight Management System | |||
| · AFTN | Aeronautical Fixed Telecommunication Network | |||
| · AIRAC | Aeronautical Information Regulation and Control | |||
| · ARINC | Aeronautical Radio Incorporated | |||
| · ASA | Aviation Supply and Academics | |||
| · ATC | Air Traffic Control | |||
| · CAC | Common Access Card | |||
| · CDR | Contract Discrepancy Report | |||
| · CD/ROM | Compact Disk/Read Only Memory | |||
| · CEFS | Critical Engine Failure Speed | |||
| · CFLSW | Commander, Fleet Logistics Support Wing | |||
| · CFMU | Central Flow Management Unit | |||
| · CFP | Computerized Flight Plan | |||
| · CI | Critical Information | |||
| · CNAFR | Commander, Naval Air Force Reserve | |||
| · CNRFC | Commander Naval Reserve Forces Command | |||
| · COMNAVFORINST | Commander Naval Forces Instruction | |||
| · COR | Contracting Officer Representative | |||
| · CPARS | Contractor Performance Assessment Reporting System | |||
| · CRAM | Conditional Route Availability Message | |||
| · CSR | Contractor Security Representative | |||
| · CUI | Controlled Unclassified Information | |||
| · DIP/DIPS | Diplomatic Clearances | |||
| · DMS | Defense Messaging System | |||
| · DoD | Department of Defense | |||
| · DON | Department of Navy | |||
| · DONCAF | Department of Navy Central Adjudication Facility | |||
| · DSS | Defense Security Service | |||
| · EFB | Electronic Flight Bag | |||
| · EGPWS | Enhanced Ground Proximity Warning System | |||
| · ERAD | Electronic Route Availability Document | |||
| · ETD | Executive Transportation Detachment | |||
| · ETOPS | Extended Twin-Engine Operations | |||
| · FAA | Federal Aviation Administration | |||
| · FAR | Federal Acquisition Regulation | |||
| · FAR | Federal Aviation Regulation | |||
| · FAX | Facsimile | |||
| · FFP | Firm Fixed Price | |||
| · FIR | Flight Information Region | |||
| · FIR/UIR | Flight Information Region/Upper Information Region | |||
| · FLIP | Flight Information Publications | |||
| · FOUO | For Official Use Only | |||
| · .ftp | File Transfer Protocol | |||
| · FSO | Facility Security Officer | |||
| · GAM | General Aircraft Mission | |||
| · GPWS | Ground Proximity Warning System | |||
| · GPI | Government Provided Information | |||
| · HSPD-12 | Homeland Security Presidential Directive 12 | |||
| · IA | Information Assurance | |||
| · IAP | IAP Worldwide Services | |||
| · IATA | International Air Transport Association | |||
| · ICAO | International Civil Aviation Organization | |||
| · IFR | Instrument Flight Rules | |||
| · INDS | Integrated Navigation Data Service | |||
| · iOS | Apple Operating System mobile devices | |||
| · IT | Information Technology | |||
| · JB | Joint Base | |||
| · JPAS | Joint Personnel Adjudication System | |||
| · JRB | Joint Reserve Base | |||
| · KO | Contracting Officer | |||
| · LOA | Letter of Authorization | |||
| · MEL | Minimum Equipment List | |||
| · METAR | Aviation Weather Report | |||
| · MOEC | Mission Ops eCharts (electronic charting product) | |||
| · MTOW | Maximum Takeoff Weight | |||
| · NACO | National Aeronautical Charting Office | |||
| · NACLC | National Agency Check and Credit Check | |||
| · NALO | Naval Air Logistics Office | |||
| · NAS | Naval Air Station | |||
| · NATOPS | Naval Air Training and Operating Procedures Standardization | |||
| · NAVEUR | U.S. Navy Europe | |||
| · NCS | Noncritical Sensitive | |||
| · NGA | National Geospatial-Intelligence Agency | |||
| · NMCI | Navy Marine Corps Internet | |||
| · NOTAMS | Notice to Airmen | |||
| · OPSEC | Operations Security | |||
| · OPT | OnBoard Performance Tool | |||
| · PAO | Public Affairs Officer | |||
| · PC | Personal Computers | |||
| · PII | Personally Identifiable Information | |||
| · PSI | Personal Security Investigation | |||
| · POP | Period of Performance | |||
| · PWS | Performance Work Statement | |||
| · QASP | Quality Assurance Surveillance Plan | |||
| · SAAR-N | Systems Authorization Access Request-Navy | |||
| · SAM | Special Aircraft Mission | |||
| · SCHED | Schedule | |||
| · SDP | Special Departure Procedures | |||
| · SECNAVINST | Secretary of the Navy Instruction | |||
| · SITA | A company specializing in air transport communications and | |||
| information technology | ||||
| · TAD | Temporary Additional Duty | |||
| · TDY | Temporary Duty | |||
| · TAF | Terminal Aerodrome Forecast | |||
| · T/M/S | Type/Model/Series | |||
| · TPOC | Technical Point of Contact | |||
| · USB | Universal Serial Bus | |||
| · USC | United States Code | |||
| · VFR | Visual Flight Rules | |||
| · VR-1 | Fleet Logistics Support Squadron One | |||
| · V speeds | standard term to define various critical airspeeds | |||
| · WX | Weather |
5.0 PERFORMANCE REQUIREMENTS
This section will outline the contractor support for Mission Planning and Dispatch Support Services 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 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.
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 International 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 electronically retrieve filed flight plans through the electronic flight bag when an internet connection is available.
5.1.31 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.32 The contractor shall provide 28-day Aeronautical Information Regulation and Control (AIRAC) cycle aeronautical data updates via website update
5.1.33 The contractor shall provide 40 training quotas annually for Web Base Flight Planning Tool (classes can be organized into four sessions with ten (10) quotas each and or can be conducted once during the year with all 40 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 484 application licenses on an annual basis. The EFB application shall be capable of receiving information associated with the mission packages described with dispatch services described below or shall be interfaced through a dashboard application that allows access to the EFB and mission package information.
DELIVERABLE: 484 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.
· Ability to automatically retrieve flight plans through the web-based planning tool
· Ability to automatically receive mission package information pertinent to Special Aircraft Mission and General Aircraft Mission Dispatch services
· Expandability to include links/buttons to access Aircraft Performance Software
· 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, 165348, 165351 Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165313, 165314, 165349, 165378 Fleet Logistics Support Squadron - 64 (VR64) – 164993, 164996, 165161, 165379
KC-130J – (Currently - 7) Marine Aerial Refueler Transport Squadron - 234 (VMGR 234) - 165739, 166473, 167111, 168073, 169018, 169228, 169229
KC-130T - (Currently 11) Marine Aerial Refueler Transport Squadron - 452 (VMGR 452) - 164105, 164180, 164181, 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 purchase order 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 purchase order 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 (17) C-40A Aircraft. The actual OPT software is provided and maintained by Boeing under a separate contract action. The following C-40 Aircraft require OPT:
C-40A - (Currently - 17) Fleet Logistics Support Squadron - 51 (VR51) – 166693, 169792 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165830 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
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 - (Currently - 17) Fleet Logistics Support Squadron - 51 (VR51) – 166693, 169792 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165830 Fleet Logistics Support Squadron - 57 (VR57) - 165835, 165836, 166693 Fleet Logistics Support Squadron - 58 (VR58) - 165829, 165832, 168980 Fleet Logistics Support Squadron - 59 (VR59) - 165831, 165833, 169793 Fleet Logistics Support Squadron - 61 (VR61) - 166695, 169036, 165834
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 - (Currently - 1) 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)
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 - (Currently - 24) Fleet Logistics Support Squadron - 53 (VR53) - 164995, 164997, 164998, 165348, 165351 Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165313, 165314, 165349, 165378 Fleet Logistics Support Squadron - 64 (VR64) – 164993, 164996, 165161, 165379
KC-130J – (Currently - 7) Marine Aerial Refueler Transport Squadron - 234 (VMGR 234) - 165739, 166473, 167111, 168073, 169018, 169228, 169229
KC-130T - (Currently 11) Marine Aerial Refueler Transport Squadron - 452 (VMGR 452) - 164105, 164180, 164181, 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 - (Currently - 1) 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)
5.11 SPECIAL AIRCRAFT MISSION (SAM) DISPATCH SERVICES (C-20G & C-37A/B). 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 - (Currently - 1) 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)
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 iOS application, 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.11.2 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.11.2.1 WX updates.
5.11.2.2 ATC coordination.
5.11.2.3 Flight planning changes.
5.11.2.4 Message relay.
5.11.2.5 Emergency assistance.
5.11.2.6 Creation/dissemination/filing of optimized CFPs. Flight plans shall include weather (WX) and NOTAMS applicable to the route of flight.
5.11.2.7 Graphical WX charting.
5.11.2.8 Appropriate MOEC charting for the route of flight.
5.11.2.9 Mission Planning Services.
5.11.2.10 Preparation and coordination of assigned missions.
5.11.2.11 Track changes to missions and make adjustments to flight planning as required.
5.11.2.12 Preparation, sending and tracking of DIPS.
5.11.2.13 Coordinate with VR-1, ETD PAC and ETD Sig for sending DIPS that must go by DMS.
5.11.3 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.11.3.1 Flight plans, WX, NOTAMS at time of filing/takeoff via web based format.
5.11.3.2 Charting via integrated MOEC route of flight and terminal charting.
5.11.3.3 Diplomatic clearance spreadsheet listing all required DIP information for the mission.
5.11.3.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.11.3.5 Create diplomatic clearance messages in accordance with U.S. DoD Foreign Clearance Guides to request DIPS.
5.11.3.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.11.3.7 Track DIPS and create a DIP sheet for each mission to allow crews easy access to diplomatic clearance information.
5.11.3.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.11.3.9 The Government will provide basic Mission/Flight/Schedule information as GFI. The Contractor shall prepare and provide the following
| Work Item/Deliverable |
| Deliverable ID |
| Phase Delivery |
| Mission/Flight Schedule with load/passenger information |
| [SCHED] |
| As Required |
w/Schedule
| Minimum Equipment List(Aircraft Daily Status Report) |
| [MEL] |
| As Applicable |
| 5.xx | GENERAL AIRCRAFT MISSION (GAM) DISPATCH SERVICES: The contractor shall provide Domestic and International general aircraft mission/flight planning or Dispatch Services to the following C-40A Fleet Logistics Support Squadrons: VR-51, VR-56, VR-57, VR-58, VR-59, VR-61 and the following C-130T Fleet Logistics Support Squadrons: VR-53, VR-54, VR-55, VR-62, VR-64. Currently each C-40A squadron contains three aircraft except VR-51, which has two for a total of 17 aircraft. The C-130T inventory is 243 aircraft. VR-53, VR-55, VR-62, and VR-64 each have five aircraft, while VR-54 has four aircraft. The C-40A and C-130T all require general mission dispatch services. GAM services shall be based on 1,215 (195 C-130T / 1,020 C-40A) flight leg segments outside the continental United States and 2,670 (160 C-130T / 2,510 C-40A) flight segment legs within the continental United States. |
| C-40A – (Currently 17) |
Fleet Logistics Support Squadron - 51 (VR51) – 169792, 1666939793 Fleet Logistics Support Squadron - 56 (VR56) - 166694, 166696, 165830 Fleet Logistics Support Squadron - 57 (VR57) - 165835, 165836, 1666931669793 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
| C-130T – (Currently 243) |
| Fleet Logistics Support Squadron - 53 (VR53) - 164995, 164997, 164998, 165348, 165351 |
Fleet Logistics Support Squadron - 54 (VR54) - 164762, 164994, 165158, 165159, 165160 Fleet Logistics Support Squadron - 55 (VR55) - 163311, 163591, 164106, 164597, 164598 Fleet Logistics Support Squadron - 62 (VR62) - 165313, 165314, 165349, 165378 Fleet Logistics Support Squadron - 64 (VR64) – 164993, 164996, 165161, 165379
5.xx.1 GENERAL DISPATCH SERVICES: The contractor shall provide GAM Dispatch Services to VR-51, VR-56, VR-57, VR-58, VR-59, VR-61, VR-53, VR-54, VR-55, VR-62, and VR-64 on a daily basis 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 to the Contractor to accurately plan flight operations 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 to VR-51, VR-56, VR-57, VR-58, VR-59, VR-61, VR-53, VR-54, VR-55, VR-62, and VR-64 via iOS application, web crew briefing system, or fax as requested by the flight crew. The flight releases shall include weather, NOTAMS and other pertinent information provided below. The Contractor shall provide charting, coordination of Diplomatic Clearances (DIPS) and provide flight planning services:
| 5.xx.1.1 | Flight planning and flight release information. |
| 5.xx.1.2 | Diplomatic clearance tracking and coordination. |
| 5.xx.1.3 | Weather and NOTAMS. |
| 5.xx.1.4 | Delivery of services through integrated iOS application/web based system/fax. |
| 5.xx.1.5 | Charting deliverable to EFB through integrated iOS application. |
| 5.xx.1.6 | Filing of flight plans with ATC. |
| 5.1xx.1.7 Flight Following with someone on the ground monitoring the aircraft when airborne. |
| 5.xx.2 | GENERAL AIRCRAFT MISSION DISPATCH IN-FLIGHT SERVICES: The contractor shall provide in-flight services as requested by VR-51, VR-56, VR-57, VR-58, VR-59, VR-61, VR-53, VR-54, VR-55, VR-62, and VR-64 for flights via ACARS or SATPHONE: | |
| 5.xx.2.1 | Weather updates. | |
| 5.xx.2.2 | ATC coordination. | |
| 5.xx.2.3 | Flight planning changes. | |
| 5.xx.2.4 | Message relay. | |
| 5.xx.2.5 | Emergency assistance. | |
| 5.xx.2.6 | Refiling flight plans and creation of corresponding computerized flight plans. | |
| 5.xx.2.7 | Mission planning services. | |
| 5.xx.2.8 | Tracking changes, sending and updating missions/DIPS. | |
| 5.xx.2.9 | Coordinating with squadron operations representatives. |
| 5.xx.3 | GENERAL AIRCRAFT MISSION FOLDER CREATION: 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-51, VR-56, VR-57, VR-58, VR-59, VR-61, VR-53, VR-54, VR-55, VR-62, and VR-64 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 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 weather 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.12.3.1 | Flight plans, weather, NOTAMS at the time of filing/takeoff. | |
| 5.xx.3.2 | Charting presentable through EFB navigation application. | |
| 5.xx.3.3 | Diplomatic clearance spreadsheet and corresponding APACS report listing all required DIP information for the mission. | |
| 5.xx.3.4 | The contractor shall use mission planning information supplied by the squadron to run flight plans which conform to the diplomatic clearance requirements disclosed at the 72 hour prior to mission launch point and any updates thereafter. | |
| 5.xx.3.5 | Create diplomatic clearance messages or requests via APACS for any additional requirements. | |
| 5.xx.3.6 | Update, request, and track diplomatic clearances when required after mission launch. | |
| 5.xx.3.7 | The contractor shall follow all FAA regulations, all C-40A and C-130T manuals, and Fleet Logistics Support Wing Standard Operating Procedures (SOP) when planning flights. The Fleet Logistics Support Wing will provide SOPs and minimum equipment lists (MELs) corresponding to each unit’s aircraft. MEL information shall also be disclosed by the squadron at the 72 hour 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 taken into account 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 Flight Information Region (FIR) NOTAMS along the route of flight and check all pertinent Terminal Aerodrome Forecast and/or Aviation Weather Report information for all departure, destination, and alternate airports before generating all flight plans. Frequently stored routes shall be stored in a database. | |
| 5.xx.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.12 COMMUNICATIONS. The contractor shall maintain an efficient method of communications between all VR Squadrons and ETD PAC and ETD Sig. Regular, daily operational communications between the contractor and VR-1, ETD PAC, and ETD Sig operations shall occur for SAM Dispatch services. Regular, daily operational communications between the contractor and VR-51, VR-56, VR-57, VR-58, VR-59, VR-61, VR-53, VR-54, VR-55, VR-62, and VR-64 operations shall occur for GAM Dispatch services. Acceptable means of communication are existing 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.
5.12.1 The Contractor’s dispatchers shall be available (24/7/365) via all VR Squadron and ETD PAC and ETD Sig Aircraft Communications Addressing and Reporting System (ACARS)/radio communications systems for in-flight assistance
5.12.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 and 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.12.2.1 Address current management and technical issues and concerns.
5.12.2.2 Assign and review action items.
5.12.2.3 Review and update schedules.
5.12.2.4 Identify risks and efforts to mitigate them.
5.12.2.5 Document issues and decisions.
5.12.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 all FLSW Squadron and ETD PAC and ETD Sig operations through the use of an encrypted secure (user name and password protected) website delivery and other methods.
5.14 Monthly Contract Status Report (MCSR). The Monthly Contract Status Report (MCSR) is prepared by the contractor in contractor format as approved by the 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 Contracting Officer Representative (COR) not later than the fifth working 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
It is anticipated that the resultant contract will have a one-year base period and contain two (2) one-year option periods: The anticipated performance periods are as follows:
· Base Period: 01 December 2019 through 30 November 2020
· Option I: 01 December 2020 through 30 November 2021
· Option II: 01 December 2021 through 30 November 2022
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 (as outlined in Section 7.0) is the responsibility of the contractor and will NOT be separately priced.
GOVERNMENT PROVIDED INFORMATION (GPI)
The GFI will include material that CNRFC provides via conferences, graphs, manuals, documentation, reports and phone calls. All reports, manuals, audio/visual aids generated under the contractor performance will become the property of CNRFC.
· Meeting facilities at NSA Hampton Roads (or other Government sites) for Discovery Workshop, Journey Mapping Workshop and Design Sprint.
· Audio/Visual equipment as identified within the Kickoff meeting.
· The Contractor shall have access to the following user groups and stakeholders for user research purposes and validation. Additionally, the Contractor may request access to additional groups as necessary to further the user research process.
· Military Service members
· Command leadership access
· N5 ProcessQuik Management Office
· N6 IT Management Office
· All pertinent program managers
· Time on-site at local Navy Operational Support Centers (NOSCs)
SPECIAL INSTRUCTIONS/CONSIDERATIONSPROPRIETARY DOCUMENTS
The contractor shall be responsible for appropriately marking contractor documents that the contractor deems proprietary. The contractor agrees to enter into a written agreement with any firm whose proprietary data is used in connection with performance of the purchase order, to protect all proprietary information from unauthorized disclosure or use for as long as it remains proprietary, to furnish the contracting officer with executed copies of all such agreements, and to refrain from using any proprietary information in supplying to the Government goods or services, or for any purpose other than that for which it was intended. The contractor agrees that any information furnished by the Government to the contractor not generally available to other contractors shall be used only for performance under this purchase order, and all copies of such information shall be returned to the Government upon completion of the effort. Any information furnished by the Government containing trade secrets or commercial or financial data of other contractors shall be treated as proprietary data. Additionally, the contractor shall not disclose outside the Government any information generated in the performance of this purchase order.
NON-PERSONAL SERVICES
Contractor employees performing services under this purchase order shall be controlled, directed and supervised at all times by management personnel of the Contractor. Contractor management shall ensure that employees properly comply with the performance work standards outlined in the PWS. Contractor employees shall perform their duties independent of, and without supervision of, any government official. The tasks, duties, and responsibilities set forth in this purchase order may not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal Policy, obligating the appropriated funds of the United States Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Part 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will control access to the facility and will perform the inspection and acceptance of the completed work.
DELIVERABLES
The contractor shall provide the Contracting Officer’s Representative (COR) with a monthly report that summarizes accomplishments of the previous month. These monthly reports shall explicitly address the status of the current project. The monthly reports shall also briefly project the next month’s goals and task activity. Finally, these monthly reports shall address any problems/concerns with the program (including any delays or potential delays to project deliverables) and resolutions/remedies taken (if applicable). These monthly reports shall be submitted to the COR electronically by the fifth working day of each month.
File details come from the government source that posted it.