21_30024_PWS_20200811.docx

Performance Work Statement for

C-17 Terrain Awareness and Warning System (TAWS) Tool and Annual Database (DB) Sustainment

Purchase Request: FD2060-21-30024

May 27, 2020

Distribution Statement C: Distribution authorized to U.S. Government Agencies and their contractors; Administrative/Operational Use; 06 April 2020. Other requests for this document shall refer to the C-17 AFLCMC/WLMBA, 235 Byron Street Suite 19A, Robins AFB, GA 31098.

1.0 Description of Services:

Sustain the C-17 TAWS Tool and Annual DB in accordance with the engineering, program management, and control tasks described herein.

1.1 Objective(s):

This Performance Work Statement (PWS) describes the services required to sustain the current performance of the C-17 TAWS tool and the quality of the C-17 TAWS DB used by both the United States Air Force (USAF) and Foreign Military Sales (FMS) C-17 fleets. These services include maintainance and support of all existing and fielded C-17 TAWS Tool software products and Annual DB outputs, including version 2.x and later, to ensure operability with evolving platform avionics.

1.2 Benefit to USAF:

This acquisition will benefit the USAF by providing continuous updates to the TAWS database which provides terrain and obstruction reports to pilots during low level flight.

1.3 Background:

The C-17 TAWS Tool is a stand alone database management tool to support the C-17 TAWS components integral to the C-17 avionics and Terrain Profile Matching (TERPROM) ® systems. The TAWS tool is used to create terrain and obstruction databases (flight maps) for upload to onboard TAWS/TERPROM® avionics. The tool also provides visualization and analysis capabilities to assess and customize these databases and to assist in the evaluation of TAWS event reports (TAWS terrain and obstruction alerts) received from USAF and FMS C-17 flight crews.

Joint Base Charleston System Support Representatives (SSR), assigned to 315 OG/OGV, use TAWS to produce the 28-day cycle Table Formatted Aeronautical Data Set-Obstructions (TFADS-O) and Digital Aeronautical Flight Information Files (DAFIF) database for all USAF C-17 aircraft. All C-17 maintenance units download the database, then transfer the database to their C-17 aircraft. This database consists of Obstacle Flight Map (OFM) files produced from TFADS-O import and represents geographic regions of the world. In addition, the Runway Flight Map (RFM) file is produced from the DAFIF import and contains runway identification, position, heading, elevation, and runway center of mass identification for use in aircraft displays. These files allow crew members to receive warnings of obstacles in the aircraft flight path. SSRs can use TAWS to custom filter obstacles by any height or even individual vertical obstructions as directed by AMC. FMS C-17s utilize the same TAWS Tool and receive the same Annual Data Base as the USAF fleet.

2.0 Services Summary

3.0 Government Property

3.1 Contractor Responsibility:

The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR), all other applicable Government regulations and as specified in the contract/order.

3.2 Government Property to be Provided:

Government property to be provided includes 2 ACE IIs.

3.3 Reporting of Government Property:

The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government Furnished Property (GFP) in the Item Unique Identification (IUID) Registry.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property:

“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property:

The Contractor shall report loss of Government property in the Government-Furnished Property (GFP) Module of Procurement Integrated Enterprise Environment (PIEE).

3.5 Return or Retention of Government Property:

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed by the Procuring Contracting Officer (PCO), but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed by the PCO, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Requirements:

The C-17 TAWS Tool is a database tool used by Air Mobility Command (AMC) personnel to create a 28-day cycle database used for C-17 low altitude flight operations. This database includes TFADS-O and DAFIF data that is transferred to the C-17 aircraft systems. In addition, the tool is used to produce an annual worldwide database with Digital Terrain Elevation Data (DTED) and Shuttle Radar Topography Mission (SRTM) for transferring annual terrain data to the C-17 TAWS glass cockpit display. FMS C-17s utilize the same TAWS Tool and receive the same Annual Database as the USAF fleet.

4.1 Technical Requirements:

The Contractor shall sustain the C-17 TAWS Tool and Annual DB which shall meet the requirements, as specified by the Government, contained in this C-17 TAWS Tool and Annual DB PWS in accordance with (IAW) the engineering, program management, and control tasks described herein.

An integrated management approach shall be implemented during the execution of the C-17 TAWS Tool and Annual DB contract (e.g., when possible, applicable Contract Data Requirements Lists (CDRLs) shall be delivered “under one cover” to eliminate redundancy in documentation, etc.). The contractor shall:

· Support the existing C-17 TAWS Tool and Annual DB implementation that satisfies the requirements within this PWS.

· Maintain and support all existing and fielded C-17 TAWS Tool software products and Annual DB outputs to ensure operability with evolving platform avionics.

· Maintain compatibility with applicable Microsoft Windows-10.x (Win-10.x) and corresponding Standard Desktop Configuration (SDC) v5.x requirements.

· Upgrade fielded software compatibility to meet mandated corrective changes and/or upgrades to SDC requirements.

· Maintain the performance, stability, and sustainability of the software baseline, including, but not limited to, resolving processing limitations due to ingestion of large data file size.

· Ensure compatibility with updated Mission Planning Data Sources, e.g. Notices to Airmen (NOTAM), digital maps and charts.

· Provide software corrections/fixes to Government-approved change requests and Deficiency Reports (DRs). Contractor has 45 days to provide a proposed solution and estimate for reported deficiencies.

· Maintain C-17 TAWS Tool software to ensure scalable, extensible, and seamless transition to follow-on Mission Planning System (MPS) efforts.

· Ensure C-17 TAWS Tool software developed under this effort shall be delivered on a single disk, as a standalone tool.

· Provide a fully integrated, installable “single” disk deliverable for each release of software that complies with the applicable, updated Mission Planning Envioronment (MPE) Letter for the release that has been approved according to the enterprise standards.

· Support FMS requests for system assistance/analysis

· Ensure the TAWS Tool has the capability to digitally sign all created products.

· Work with the prime integrator on a continued basis to ensure seamless integration of digital signatures in the navigational database life cycle.

· Deliver software in accoradance with (CDRL A001)

4.2 Performance Requirements

The Contractor shall apply the following performance requirements to any delivered software throughout this program:

· Windows Operating System (OS). The contractor shall maintain currently fielded C-17 TAWS Tool on corresponding Windows and SDC consistent with the applicable MPE Letter. The contractor shall maintain applicable software to be Windows on Windows (WOW) 64-bit compliant and include provisioning to convert to Windows 64-bit format.

· Developer Tools. The contractor shall use Visual Studio Ultimate and Visual Studio Test Professional for the purpose of communicating information between the development and test organizations

· Source Code. The contractor shall include source code and all other files needed to rebuild the component from source including automated unit tests when delivering the fully qualified software package

· Peer Review. The Government shall be notified of and be invited to attend the contractor’s internal peer reviews (design, code, test, etc.).

· Installation Instructions. The contractor shall produce installation instructions to be included with delivery of the software

· Deficiency Reporting. The contractor shall provide a list of known deficiencies to the Government’s collaboration site that is compatible with the Government’s EDR system for each release no later than 10 business days prior to Final Qualification Test (FQT). Following FQT, there shall be a delivery of all discovered Candidate Deficiency Report (CDRs) during FQT. Those CDRs shall be posted to the collaboration site no later than 15 calendar days after FQT.

· Online Help. The contractor shall maintain online help for all executable software products delivered.

· Configuration Management. The contractor shall deliver all software in conformance with the current enterprise configuration management plan including the Nomenclature Standard.

· Dynamic Object Oriented Requirements System (DOORS). The contractor shall maintain full life-cycle requirement traceability for the full C-17 TAWS Tool product/version line.

· Single Install. The contractor shall maintain a fully integrated, installable “single” disk deliverable for each release of software that complies with the applicable, updated MPE Letter for the release that has been approved according to the enterprise standards.

· Adherence to Mission Planning Enterprise Milestone Entry/Exit Procedures. The contractor shall adhere to milestone entry/exit procedures for applicable events—Software Requirements Review (SRR), Preliminary Design Review (PDR), Criticial Design Review (CDR) and FQT.

· Engineering Change Proposal (ECP) as required. (CDRL A002).

· Request for Variance (RFV) as required. (CDRL A003).

4.3 C-17 TAWS Tool/Annual TAWS DB Sustainment Tasks

The contractor shall sustain the C-17 TAWS Tool/Annual TAWS DB and modernize, when Government directed, the C-17 TAWS Tool software baseline. Updates to the C-17 TAWS tool including but not limited to mandated corrective changes and/or upgrades to fielded software, e.g. Standard Desktop Configuration (SDC) requirements and Category I and/or safety of flight deficiency reports.

The contractor shall maintain compatibility of the C-17 TAWS Tool to the hardware, software, and data components identified in the applicable C-17 TAWS Tool MPE Letter.

The contractor shall plan for the use of the C-17 Flight Simulator(s) to load the C-17 TAWS data, as they are available, to help assess impacts to the databases due to Government directed software changes.

The contractor shall conduct Final Sprint/FQT (and if necessary, regression FQT) and deliver the fully qualified software product, including install instructions, and other deliverables.

The contractor shall support Government DT/OT to include investigate and provide software fixes to Government-approved DRs discovered during Government DT/OT and DT/OT user-training.

The contractor shall update and provide a release of the “Annual” C-17 TAWS Database (Worldwide Flight Map (WFM), Terrain Flight Map (TFM), Airport Flight Map (AFM)) in accordance with the Government-approved schedule.

The contractor shall investigate and provide recommendations to USAF and FMS C-17 TAWS errant/nuisance alerts as directed by the Government.

The contractor shall investigate and scope improvements to the C-17 TAWS Tool software and the Tool-generated TAWS DB in the following areas (CDRL A005):

· Source data validation (Defense Gridded Elevation Data (DGED), DAFIF, TFADS-O) including discovery and report of potential NGA data issues;

· Adaptation of potential new source terrain and obstacle data improvements for the TAWS Map Preparation Software;

· Adding the capability to load higher resolution data to the C-17 TAWS Tool system;

· TAWS changes to support C-17 Hardware and TERPROM upgrade

· Usability of newly available terrain data such as National Geospatial-Intelligence Agencies (NGA) TanDEM-X and/or DGED to improve data accuracy.

The contractor shall investigate and scope the DO-200B and provide recommendations on best approach to meet compliance, if directed by the government. (CDRL A005) The contractor shall support technical interchange meetings and working groups pertaining to C-17 and report findings to Government NLT 15 calendar days post support. (CDRL A005) The contractor shall provide a Management Metric Report and include information used by the contractor to internally track, report, and manage product development, integration, test, quality, function, and performance relative to the contractor processes/procedures and contractual Technical Requirements Documents, Capability Description Documents (CDDs), and System/Software Requirements Documents (S/SRDs) (CDRL A005) The contractor shall consider C-17 FMS geographical requirements for Australia, Canada, Qatar, United Arab Emirates, United Kingdom, Bulgaria, Estonia, Finland, Hungary, Lithuania, Netherlands, Norway, Poland, Romania, Slovenia, and Sweden.

The contractor shall provide documentation to include Mission Planning User’s Manual (CDRL A008) The contractor shall provide documentation to include the Software Requirements Specification (SRS). (CDRL A004) The contractor shall provide documentation to include the Software Version Description (SVD). (CDRL A006)

4.4 Test

The contractor shall create test plans, test descriptions, conduct tests and generate test reports, as required. (CDRL A007)

4.5 Concept of Operations

The Contractor shall provide a Concept of Operations for the C-17 TAWS Tool and DB that describes how both the C-17 TAWS Tool and DB will be operated. (CDRL A005)

4.6 User Participation

The Contractor shall maximize the use of subject matter experts during meetings including, but not limited to, program management reviews, technical reviews, and technical interchange meetings to get early Government insight into the analysis, tradeoffs and decisions that will be required to best utilize the C-17 User Environment to meet user requirements and to best resolve problems and reduce program risk.

4.7 Reserved.

4.8 General Cybersecurity Requirements

4.8.1 The contractor shall support the development/update of Risk Management Framework (RMF) supporting certification documentation (SCD) as specified in the RMF Security Authorization package CDRL item. (CDRL A009)

4.8.2 The contractor shall adhere to DoDI 8500.10 (Cybersecurity), and DODI 8510.01 (RMF).

4.8.3 The contractor shall ensure the C-17 TAWS Tool maintains the capability for digitally signing the database. When required the contractor shall work with C-17 specified personnel to finalize the CONOPS for digital signature implementation. As long as under contract, the contractor shall perform continuous monitoring IAW the Information System Continuous Monitoring Strategy (ISCM) to ensure no negative changes in cybersecurity compliance

4.8.4 The contractor shall support RMF activities of the Government, and participate in regular security related working group meetings. (CDRL A009)

4.8.5 Standard Desktop Configuration, Security Technical Implementation Guides (STIGs), Group Policy Object (GPO), and Time compliance Network Orders / Information Assurance Vulnerability Management (TCNO/IAVM) Requirements:

· The contractor shall implement the MPS Enterprise SDC (Standard Desktop Configuration) Test Strategy process by ensuring during development and test that all testbed computers used for integration and runtime testing are updated to the latest available SDC release. The SDC version must be periodically updated to the latest available version until 60 calendar days before the start of FQT and during DT until 60 calendar days before the end of DT.

· Security Technical Implementation Guides (STIG)/ Time Compliance Network Orders (TCNO) compliance evaluation of all Internet Access (IA)-enabled Commercial Off the Shelf (COTS) components in their software product’s runtime environment (i.e., Windows Operating System (OS), Microsoft (MS) Office, Microsoft Structured Query Language (MS-SQL), MS .NET Framework, etc).

· Code quality evaluation of all contractor-written JMPS application source code and government PM-approved open source code (if any), using (a) HP Fortify or an equivalent automated tool and (b) the DISA Application Security and Development (ASD) STIG.

· Verification of compliance with all allocated JMPS Security Target requirements.

· STIGs must be periodically updated to the latest available versions until 30 calendar days before the start of FQT and during DT until 30 calendar days before the end of DT.

· The contractor shall comply with the MPS Enterprise GPO (Group Policy Object) Management process by ensuring during development and test that all testbed computers used for integration and runtime testing are periodically updated to the latest available GPOs. GPOs must be periodically updated to the latest available versions until 30 calendar days before the start of FQT and during DT until 30 calendar days before the end of DT.

· TCNOs/IAVMs must be periodically updated to the latest available TCNO/IAVM package until 30 calendar days before the start of FQT and during DT until 30 calendar days before the end of DT.

· The contractor shall comply with the MPS Enterprise MPE Letter Generation process and use the MPE letter to document the current SDC version and GPOs installed on the target system. After software delivery, the contractor shall be available via telephone/email to advise Government sustainers on potential impacts of future SDC and GPO updates.

4.8.6 Air Force Evaluated Products List (AF EPL)

The contractor shall ensure the C-17 TAWS software maintenance and software upgrades comply to terms and conditions for current AF EPL certification memo, Software Certification for C-17 TAWS Tool Version 2.x, dated 15 February 2017.

4.9 General Supportability Requirements

The contractor shall allow the Mission Planning System Support Facility Training Team access to software early releases, attendance at Development Evaluations and software documentation (e.g. Version Description Documents, help files) to support the development, sustainment, user, and administrative training.

The contractor shall implement and maintain a centralized problem reporting process for all phases of the development lifecycle. Electronic access to the contractor's problem database shall be provided for Government, other Contractor developers, and the SEIC.

4.10 Program Management and Control

The Contractor shall appoint a Program Manager (PM) to manage the C-17 TAWS Tool and Annual DB Sustainment Contract sustainment effort. The Contractor PM shall have sufficient corporate authority to direct, execute, and control all elements of the C-17 TAWS Tool and Annual DB Sustainment Contract program including the activities required in this PWS. The Contractor PM shall be prepared at all times to present and discuss with the Government designated representative the most current and realistic status of the contractual effort and provide access to all information associated with this effort.

4.11 Status and Schedule

The contractor shall submit a monthly status report which shall include current efforts, risks and problems, accomplishments and a schedule which accurately depicts the flow of tasks (and dependencies) necessary to accomplish the program.The Contractor shall maintain an Integrated Master Schedule (IMS) that identifies all elements and dependencies of the C-17 TAWS Tool and Annual DB Sustainment Contract. The schedule and issue/impacts shall be presented at each program management review. (CDRL A010)

4.12 Associate Contractor Agreements (ACA)

The Contractor shall establish and maintain Contractor-to-Contractor agreements (i.e., ACAs) to exchange any interface documentation required to complete the effort that is not provided by the Government and to ensure successful integration and interoperability with the aircraft Operational Flight Program (OFP), Video Integrated Processor, and TERPROM® avionics systems.

4.13 Program and Enterprise Meeting Support

The contractor shall support Enterprise level and DO specific meetings as required and as specified below. The contractor shall participate in other contractor’s status meetings, design meetings or other meetings as required to successfully execute this delivery order. Below is a list of possible meetings.

4.14 Period and Place of Performance

4.14.1 Contract/Order Period of Performance:

The Period of Performance shall be one year from date of contract with 9 1 year options.

4.14.2 Place of Performance

These services will be performed at the contractors facility with periodic visits to other contractor and Government facilities.

4.15 Contract Data Requirements List(s) (CDRL)

Authorization Package 4.8.1, 4.8.4

4.15.1 Quality of CDRL Deliverable:

There shall be no more than 1 rejection of any single deliverable. There shall be no more than a total of 1 rejection of deliverables per contract year. The Government will reject a deliverable if any technical errors or 3 or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.15.2 Submission of CDRL Deliverable:

CDRL deliverables may be submitted via Procurement Integrated Enterprise Environment (PIEE) / Wide Area Workflow (WAWF) and/or be submitted directly to the MFT member identified on the CDRL. The CDRL will determine submittal requirements.

4.15.3 Receipt of CDRL Deliverable:

There shall be no more than one late receipt of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.16 Travel:

Travel requests for contractor/subcontractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of 15 business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis:

The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations:

The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with all applicable Government regulations including, but not limited to, Department of Defense Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; Department of Defense (DoD) Manual 5205.02, DoD Operations Security (OPSEC) Program Manual; and DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

5.2.2 Security Clearance:

It is not expected contractor/subcontractor personnel will require security clearance(s) for proper accomplishment of contract/order requirements. Contractor/subcontractor personnel will not be authorized access to classified information and/or Controlled Unclassified Information (CUI) and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.3 Security Incident or Violation:

The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.4 Security of Contractor System(s):

The Contractor shall ensure the security of their Automated Information System(s) (AIS) to preclude all potential security incidents or violations in accordance with DoD 5220.22-M and all other applicable Government regulations.

5.3 Trafficking in Persons:

The Contractor shall comply with all applicable Government regulations including, but not limited to, FAR 52.222.50, Combating Trafficking in Persons.

5.4 Environmental Management System (EMS):

These services will not be performed at a Government facility; therefore, the requirement does not apply.

5.5 Agency Affirmative Procurement Programs:

This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.6 Safety Requirements .

5.6.1 Contractor Compliance:

The Contractor shall comply with all applicable Government regulations including, but not limited to, Public Law 91-596 as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.6.2 Mishap Notification/Investigation:

The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The AFLCMC Safety office shall be notified by phone at (937) 904-3386 during duty hours and (937) 510-1184 after hours within four business hours after initial notification of all mishaps or incidents for damage to DoD property. The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within four business hours. The Contractor shall cooperate with Government safety investigations.

5.7 Contractor Manpower Reporting:

In accordance with 10 United States Code 2330a, the Contractor shall provide an annual count of contractor/subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity and if the acquisition is in excess of $3,000,000.00. The Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA). Reporting shall be conducted for each fiscal year, which extends October 1 through September 30. While inputs may be made any time during the fiscal year, all data shall be reported no later than October 31 of the following fiscal year. The Contractor shall establish a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award. The Contractor shall enter Order Data, Contact Data and Location Data. User guides may be found at https://www.ecmra.mil/help/help.html.

5.8 Inspection of Services:

In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.9 Quality Management System (QMS):

The Contractor shall ensure the quality of services through an internal quality and/or inspection system. The QMS should address detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The QMS should include a schedule of quality assurance/control inspections.

5.10 Invoicing/Payment and Receipt/Acceptance:

The Contractor shall submit/process payment requests and receipt/acceptance documents via PIEE/WAWF.

PR: FD2060-21-30024 PWS REVISION: 0 1

Distribution Statement: D

6.0 Appendices

6.1 Appendix A, Reference(s)

6.2 Acronyms: