Performance Work Statement (PWS).pdf

AVIATION SOFTWARE LICENSES FOR U.S. COAST GUARD AIR STATION

WASHINGTON DC

PERFORMANCE WORK STATEMENT (PWS)

1.0 SCOPE.

Coast Guard Air Station Washington DC (ASW) has a requirement for International & Domestic Flight Planning services (via Military Flight Bag (MFB) One licenses), Heavy Tail Dispatch, and Runway Analysis licenses to support the agency's C-37A/B and C-39A Gulfstream aircraft fleet. These services are essential for safe, compliant, and reliable executive air transport for DHS Secretary (S1) and Coast Guard senior officials and must be compatible with Honeywell avionics equipment and Jeppesen ForeFlight INDS software currently installed in the cockpits of the aircraft.

2.0 BACKGROUND.

2.1. Coast Guard Air Station Washington utilizes electronic MFB’s for the purpose of conducting pre-flight planning and in-flight support. The electronic MFB serves as an alternative and/or replacement to paper-based charts, publications, and manuals, significantly reducing pilot workload, streamlining publication management processes, enhancing aircraft performance (though weight reductions) and improving in-flight situational awareness.

2.2. A critical component of the Performance license is the capability to provide the Government with detailed aircraft performance profiles with multiple climbs, cruise and decent profiles as well as paperless Oceanic Plotting capability, record keeping, and automatic gross navigational error detection. The Performance licenses also provide access to enhanced DOD weather information, map layers, and 3D airport preview. Custom content is also available with the Performance licenses which allow users to import tactical map layers and local procedures which can in turn be shared throughout the unit.

2.3. To provide end-users with the full capabilities required of the electronic MFB, appropriate application(s) must be installed on the device and licensed to the user.

2.4 Air Station Washington DC is charged with providing safe, reliable, executive air transport to the Secretary of Homeland Security (S1), Commandant of the Coast Guard (CCG), and other senior government officials globally via mission-ready Long-Range Command and Control (LRCCA) aircraft. To meet mission requirements, the military designated Gulfstream GV/550 and G700 aircraft, C-37A/B and C-39A respectively, must include Military Flight Bag (MFB) Performance license subscriptions, heavy tail dispatch subscriptions, and runway analysis subscriptions. All services are essential for the USCG to meet the demands of the global executive LRCCA transportation mission.

3.0 SPECIFIC REQUIREMENTS / TASKS.

• Application must be compatible with Electronic Flight Bag (EFB) hardware currently deployed in USCG aviation, as well as iOS 11.1.1 and all subsequent iOS releases throughout the duration of the period of service.

• Application must be capable of meeting DISA IL5 requirements to protect Controlled Unclassified Information.

• Application must provide online (through Internet connection) and offline (no Internet connection) access to the following:

- Federal Aviation Agency (FAA) National Geospatial-Intelligence

- Agency (NGA)-published data and publications, to include:

1. All FAA National Aeronautical Charting Office (NACO)

2. FLIP data.

3. All NGA FLIP products.

4. Airport and Facilities Directories (A/FD) and taxi diagrams.

5. FAA and DOD terminal Instrument Approach Procedures (IAP).

• Application will display IAP in identical format to the standard published paper version.

This PWS defines standard published paper versions as those published by FAA/NACO, NGA, and Jeppesen.

• Application will display the IAP in a size no less than 85% of the standard published paper version. Application must meet this criterion without requiring the user to zoom for:

- Arrival procedures.

- Departure procedures.

- Airport/Taxi Diagrams.

- Airport Facility Directories.

- En Route Navigational Charts (IFR High/Low, VFR Sectionals).

• Application will display en route navigational charts in a seamless, geographically contiguous format.

• Provide FAA terminal change notices.

• Provide Class B enhanced graphics.

• Provide FLY charts.

• Provide Visual chart supplemental.

• Provide Federal Aviation Regulations (FARs).

• Provide IFR planning/ocean charts.

• Provide Helicopter charts.

• Provide DOD airport and navigational databases.

• Provide DOD planning documents.

• Provide DOD supplementals.

• Provide DOD terminal change notices.

• Provide FAA publications (e.g. handbooks, chart legends, etc.).

• Application will include situation awareness-enhancing features, including:

• Ability to receive GPS positions from an external GPS source and display own-ship position on en route charts, IAP, arrival procedures, departure procedures, and airport/taxi diagrams.

• Application will include geo-referenced FLIP products that support this requirement:

- Ability to receive and display near-real-time weather information from an external weather data source, such as ADS-B.

- Weather information shall include radar imagery, which can be displayed on en route charts.

- Weather information shall include:

1. Terminal Aerodrome Forecasts (TAF)

2. METAR

3 Significant Meteorological Information (SIGMET), and 4 Airmen’s Meteorological Information (AIRMET).

5 This information will be presented in textual format and/or visual format displayed on en route charts.

• Ability to receive and display Notices to Airmen (NOTAM) from an external data source.

• Ability to display obstacles and terrain (from downloaded databases) within proximity of the EFB, with visual annunciation of a proximity hazard to (based upon GPS position).

• The obstacle and terrain databases referenced must utilize NGA-provided obstacle and terrain data.

• Application will include preflight/in-flight planning functions,

• including:

1. Ability to construct a flight plan (FAA and ICAO) and display the planned route of flight on en route charts.

2. Ability to file FAA and ICAO flight plans through the application.

3. Ability to generate a full weather brief, as described in the FAA Aeronautical Information Manual 7-1-4, to include all items listed EXCEPT “VFR Flight Not Recommended”.

4. Ability to email a copy of the filed flight plan and weather brief to a user-designated email address.

5. Ability to enter user-defined waypoints and display those waypoints on en route charts.

6. Ability to print paper backups of FLIP products such as IAP from within the application.

7. Ability to accurately measure distance between two points on en route charts.

• Application will include usability functions, including:

• Support for iOS multi-touch gestures, including pinch-tozoom, while displaying FLIP products.

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

• Application will provide a visible alert to the user when an expired product is either downloaded or displayed by the application.

• Application will be compatible with BadElf external GPS devices and be able to display “own ship” location based upon the GPS signal received and provided by the BadElf device.

• Application will be compatible with the Stratus ADS-B devices.

• The software must be able to display “own-ship” location based upon the GPS signal received and provided by the Stratus device and be able to display ADS-B In data from the Stratus device, including aviation traffic and weather data (as described above).

• Licenses will include Dispatch: Heavy Tail (MTOW 41,000-107,600) for four aircraft:

C101 (C-37A), C102 (C-37B), C103 (C-39A), and C104 (C-39A).

• Licenses will include Runway Analysis for four aircraft: C101 (C-37A), C102 (C-37B), C103 (C-39A), and C104 (C-39A), to include takeoff, en route, and landing performance data for dry or contaminated runway and all wind conditions. The app will be capable of notifying users when takeoff/landing is out of limits due to weight/performance, runway distance, or obstacle limitations.

• Licenses will be distributed to and managed by the U.S. Coast Guard through association with unit-level license administrator email addresses. These email addresses and associated license allocations will be provided by the U.S. Coast Guard Air Station Washington DC point of contact.

• Paperless Oceanic Plotting capability, record keeping, and automatic gross

• Navigational error detection.

• Automatically upload navigation logs to Dispatch.

• Automate oceanic crossing regulatory compliance.

• Must be incorporated into the training curriculum under the existing CG contract with

Flight Safety International (FSI) for simulator runway analysis training.

• Shall supply 13 application licenses, each granting the user the capability to install and use the application on at least one Apple iPad and one (1) iPhone.

• Electronic Flight Bag Application Support. The application vendor shall provide:

- Technical support to individual users via telephone and/or email communications at no additional cost to the government.

• The application vendor shall supply application updates as required, to correct software bugs and ensure continued compatibility with the latest version of Apple’s iOS, at no cost to the government.

• The application vendor shall provide initial onboarding and training support for USCG personnel, including user guides, quick reference materials, and access to technical assistance for new users.

• The application vendor shall provide instructions and support for license activation, transfer, and deactivation. The vendor shall maintain records of license allocations and provide reports to the COR upon request.

• All support activities, training materials, and license management reports shall be submitted in accordance with Section 11.0 (Deliverables).

• All support and update activities must comply with the security requirements outlined in Section 4.0 (Security Requirements Traceability Matrix).

Services shall be provided during all phases of flight.

4.0 Security Requirements Traceability Matrix (SRTM)

The contractor shall address each of the following security requirements as part of their technical solution and ongoing compliance. The SRTM below identifies the requirements and design references that must be addressed by way of DoW Provisional Authorization Memo and Cyber Security Incident Response Plan.

4.1 Deliverable Requirement:

The contractor shall submit a DoW Provisional Authorization Memo and Cyber Security Incident Response Plan within 30 days of contract award. The DoW Provisional Authorization Memo must detail how SRTM REQ-001 will be met, including describing the technical approach, controls, responsible personnel, and methods for compliance. The Cyber Security Incident Response plan must detail how SRTM REQ-008 will be met, including describing steps to prevent or mitigate incidents as well as methods, controls, and responsible personnel. The contractor shall provide periodic DoW Provisional Authorization Memos and Cyber Security Incident Response Plans as requested by the Contracting Officer’s Representative (COR) and shall submit evidence of compliance with each SRTM item upon request.

4.2 Review and Acceptance:

The government will review the DoW Provisional Authorization Memo and Cyber Security Incident Response Plan for completeness and compliance with the SRTM. Deliverables may be accepted or rejected in accordance with Section 8.0 of this PWS.

4.3 DoW Provisional Authorization Memo Deliverable:

The contractor shall submit a DoW Provisional Authorization Memo within thirty (30) calendar days of contract award. The DoW Provisional Authorization Memo should address Security Requirements Traceability Matrix (SRTM) REQ-001 by describing the technical approach, controls, responsible personnel, and methods for compliance. DoW Provisional Authorization Memo shall be sent to the COR via electronic means to email address:

Justin.L.Dougherty@uscg.mil. Documents must be password protected and encrypted using winzip (or similar) as a container and be sent to the recipient. Password must be provided in a separate email. If documentation cannot be password protected, encrypted and sent via email, please notify the COR, Mr. Justin Dougherty at email:

Justin.L.Dougherty@uscg.mil / Phone: (202) 603-0689 so that other arrangements can be made. If the DoW Provisional Authorization Memo cannot be finalized within thirty

(30) calendar days of contract award, the Contracting Officer's Representative (COR) must be notified via email at least five (5) business days prior to the expiration of the 30-day deadline to initiate the formal Security Plan drafting process.

4.4 Cyber Security Incident Response Plan Deliverable:

The contractor shall submit a written Cyber Security Incident Response Plan within thirty

(30) calendar days of contract award. The Cyber Security Incident Response Plan must address Security Requirements Traceability Matrix (SRTM) REQ-008 by describing steps to prevent or mitigate incidents as well as methods, controls, and responsible personnel.

Cyber Security Incident Response Plan shall be sent to the COR via electronic means to email address: Justin.L.Dougherty@uscg.mil. Documents must be password protected and mailto:Justin.L.Dougherty@uscg.mil mailto:Justin.L.Dougherty@uscg.mil encrypted using winzip (or similar) as a container and be sent to the recipient. Password must be provided in a separate email. If documentation cannot be password protected, encrypted and sent via email, please notify the COR, Mr. Justin Dougherty at email:

Justin.L.Dougherty@uscg.mil / Phone: (202) 603-0689 so that other arrangements can be made. If the Cyber Security Incident Response Plan cannot be finalized within thirty

(30) calendar days of contract award, the Contracting Officer's Representative (COR) must be notified via email at least five (5) business days prior to the expiration of the 30-day deadline to initiate the formal Security Plan drafting process.

4.5 Periodic Updates:

The contractor shall provide updated DoW Provisional Authorization Memo and a Cyber Security Incident Response Plan within thirty (30) days of any significant changes to the system, application, or security posture. Updates shall include evidence of continued compliance with all SRTM requirements.

4.6 Evidence of Compliance:

The government may request additional evidence at any time during contract performance, at which point the contractor shall provide supporting documentation, test results, certifications, or other evidence for each SRTM item.

4.7 Incident Reporting Process:

The contractor shall report all security incidents affecting the application, data, or devices within twenty-four (24) hours of discovery. Incident reports must be submitted to the Contracting Officer’s Representative (COR) and include a description of the incident, affected systems, mitigation steps taken, and corrective actions implemented.

Following submission of an incident report, the contractor shall provide a remediation plan within five (5) calendar days, detailing additional steps to address and prevent recurrence of the incident. The contractor shall implement corrective actions as directed by the COR and provide evidence of completion upon request.

5.0 QUALIFIED PERSONNEL.

The Contractor shall provide qualified personnel to perform all requirements specified in this PWS.

6.0 CONTINUITY OF SUPPORT.

The Contractor shall ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor shall ensure that all contract support personnel are present 24/7 in the case of an emergent technical support need.

7.0 CONTRACTOR FURNISHED PROPERTY.

The Contractor shall furnish all facilities, materials, equipment, and services necessary to fulfill the requirements of this contract, and shall supply application updates as required, to correct software bugs and ensure continued compatibility with the latest version of Apple’s iOS, at no cost to the government.

8.0 GOVERNMENT ACCEPTANCE.

The Contracting Officer’s Representative (COR) will review all contract deliverables, including the DoW Provisional Authorization Memo and Cyber Security Incident Response Plans required under Section 4.0, prior to acceptance. The COR will provide the contractor with written notification of acceptance or documented reasons for non-acceptance via email.

The COR reserves the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal or fail to meet the requirements outlined in the Performance Work Statement (PWS), including the Security Requirements Traceability Matrix (SRTM).

In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor shall submit a remediation plan within five

(5) calendar days of notification and provide corrected deliverables within fifteen (15) calendar days, or as otherwise directed by the COR.

Acceptance of deliverables will be based on completeness, accuracy, and demonstrated compliance with all contract requirements. The COR may request supporting documentation, evidence of compliance, or additional information as needed to facilitate review and acceptance.

All deliverables required under this contract shall be prepared and submitted to the Contracting Officer's Representative (COR) in accordance with the schedule, instructions, and distribution requirements outlined in sections 3.0, 8.0, and 11.0 of this Performance Work Statement (PWS).

All deliverables and communications containing Controlled Unclassified Information (CUI), PII, or FOUO data must comply with DHS and USCG security policies.

9.0 PERIOD OF PERFORMANCE.

The government intends to award a Firm Fixed Price contract with the following period of performance dates:

10.0 PLACE OF PERFORMANCE.

The primary place of performance will be USCG Air Station Washington, 1 Reagan National Airport, Hangar 6, Washington, DC, 20593. Since the service provided is electronic, no in person visits from the contractor are to be expected.

11.0 DELIVERABLES.

The contractor shall submit the following deliverables in accordance with the schedule below. All deliverables shall be provided to the Contracting Officer’s Representative (COR) and as applicable, the Contracting Officer (KO).

All deliverables required under this contract shall be prepared and submitted to the Contracting Officer's Representative (COR) in accordance with the schedule, instructions, and distribution requirements outlined in sections 3.0, 8.0, and 11.0 of this Performance Work Statement (PWS).

Item PWS Reference Deliverable/Event Due By Distribution

1 4.3 DoW Provisional

Authorization Memo

30 days after contract award. COR must be notified via email at least 5 business days prior to this deadline if it cannot be met. Also due within 30 days of any significant system changes.

COR

2 4.4 Cyber Security Incident Response Plan

30 days after contract award. COR must be notified via email at least 5 business days prior to this deadline if it cannot be met. Also due within 30 days of any significant system changes.

3 4.7 Incident Report Within 24 hours of discovery COR

4 4.7/8.0

Remediation Plan (if deliverable rejected or incident occurs)

5 days after COR notification

COR,

Contracting Officer

5 4.7/8.0 Corrected Deliverable 15 days after COR notification COR, Contracting Officer

6 3.0 License Management

Report (upon request) As requested

COR, Contracting Officer

7 3.0 Training/Onboarding

Materials Upon initial deployment

12.0 FOREFLIGHTS T&C STATEMENT.

As respects ForeFlight Dispatch, ForeFlight Military Flight Bag One, and ForeFlight Runway Analysis, notwithstanding anything to the contrary, Customer’s use of these solutions is subject to ForeFlight’s EULA, accessible at https://www.foreflight.com/support/eula/ or within the ForeFlight application, and Customer accepts the same.

https://www.foreflight.com/support/eula/