TAWS_SOW_19Sep2019.pdf

Distribution Statement D:

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

Statement of Work (SOW)

For

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

Database (DB) Sustainment

FA8526-20-C-XXXX

19 September 2019

Prepared By:

C-17 System Program Division (AFLCMC/WLM)

235A Byron Street, Suite 19A

Robins AFB, GA 31098

FA8526-20-C-XXXX

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

FAXXXX-20-C-XXXX

Record of Change

Rev # Revision Date Description of Change Section Affected

1.0 9/19/19 Added FMS reference, deleted requirement for Native 64-bit requirement multiple

Table of Contents

1.0 SOW INTRODUCTION/SCOPE

1.1 SOW PURPOSE/OBJECTIVES

1.2 BACKGROUND

1.3 WEB SITES

2.0 REFERENCES

3.0 C-17 TAWS TOOL AND DB

3.1 GENERAL REQUIREMENTS

3.2 PERFORMANCE REQUIREMENTS

3.3 C-17 TAWS TOOL/ANNUAL TAWS DB SUSTAINMENT TASKS

3.4 TEST

3.5 CONCEPT OF OPERATIONS

3.6 USER PARTICIPATION

3.7 SEIC COORDINATION

3.8 GENERAL CYBERSECURITY REQUIREMENTS

3.9 GENERAL SUPPORTABILITY REQUIREMENTS

4.0 MANAGEMENT OBJECTIVES

4.1 PROGRAM MANAGEMENT AND CONTROL

4.2 STATUS AND SCHEDULE REPORTING

4.3 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)

4.4 ASSOCIATE AGREEMENTS (ACA)

4.5 DATA MANAGEMENT

4.6 PROGRAM AND ENTERPRISE MEETING SUPPORT

4.7 DATA

4.8 INCENTIVES

4.9 PLACE OF PERFORMANCE

4.10 PERIOD OF PERFORMANCE

1.0 SOW Introduction/Scope

This Statement of Work (SOW) covers all functional, technical and management tasks associated with satisfying the USAF and Foreign Military Sales (FMS) C-17 TAWS Tool and Annual DB Sustainment contract.

1.1 SOW Purpose/Objectives

The purpose of this Statement of Work (SOW) is to provide the contractor with specific tasks to be performed for the C-17 TAWS Tool and Annual DB Delivery Order (DO).

The objective of this DO is to sustain the current performance of the C-17 TAWS Tool and the quality of the C-17 TAWS DB used by both the USAF and FMS C-17 fleets. Throughout the document, all references to the C-17 TAWS tool include both the “front end” capability and “back end” TAWS Map Preparation software.

1.2 Background

The C-17 TAWS Tool is a standalone 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, uses TAWS to produce the 28-day cycle Table Formatted Aeronautical Data Set (TFADS) and Digital Aeronautical Flight Information Files (DAFIF) database for all AMC 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 ID, 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 filters to 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.

1.3 Web Sites

Web Site Name Link Content

Mission Planning Central https://mpc3.mission-planning.org/default.aspx

Mission Planning Enterprise SharePoint site

Process Asset Library (PAL) https://mpc3.mission-planning.org/sites/MGT/PAL/default.asp x

Enterprise Processes and Templates

2.0 References

DOD References

Number Title Revision Date

DODD 5220.22 National Industrial Security Program Operating Manual

(NISPOM)

Latest 28 Feb 2006 or latest

DODI 8510.01 Risk Management Framework (RMF) for DOD Information Technology (IT)

Latest 12 Mar 2014 or latest

DODI 8500.01 Cybersecurity Latest 14 Mar 2014 or latest

Multiple DISA STIGs DISA Security Technical Implementation Guides (STIGs) for Microsoft Windows Operating System, Microsoft Desktop Applications, Microsoft SQL Server, and Microsoft .NET Framework

Latest Latest

Air Force References

N/A Air Force Software Management Guidebook Latest Latest

AFI 99-103 Capabilities Based Test & Evaluation Latest Latest

AFMAN 63-

Certification of System Readiness for Dedicated Operational Test and Evaluation

Latest Latest

AFI 17-130 Cybersecurity Program Management Latest Latest

AFMCP 63-

Risk Management Process Latest Latest

Enterprise Reference

Enterprise IMS Process Latest Latest

Test and Evaluation Master Plan (TEMP) Latest Latest

Mission Planning Systems Cybersecurity Strategy Latest Latest

Software Systems Architecture Description (SSAD) Latest Latest

ELSG-SPT-

PRO-CM-

MPS Enterprise GPO Management Process Latest Latest

ELSG-

ENG-PRO-

SE-402

Delta Qualification Process Latest Latest

Mission Planning Enterprise Code Quality Procedure Latest Latest

ELSG-

ENG-PRO-

Enterprise Technical Meeting Procedure Latest Latest

MPE Letter Generation and Management Process Latest Latest

Configuration Management Plan Latest Latest

3.0 C-17 TAWS Tool and DB

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 Table Formatted Aeronautical Data Set – Obstructions (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 Data Base as the USAF fleet.

3.1 General Requirements

The Contractor shall sustain the C-17 TAWS Tool and Annual DB that shall meet the requirements, as specified by the Government, contained in this C-17 TAWS Tool and Annual DB SOW 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 List (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 SOW.

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

Maintain compatibility with applicable Microsoft Windows-10.x (Win-10.x) and corresponding 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. NOTAMS, digital maps and charts.

Provide software corrections/fixes to Government-approved Change Requests (CRs) and Deficiency s (DRs).

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

The contractor shall ensure C-17 TAWS Tool software developed under this effort will be delivered on a single disk, as a standalone tool.

The contractor shall provide 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.

Support FMS requests for system assistance/analysis

Return GFE to Government.

Provide a Contract Funds Status Report (CFSR). (CDRL A002)

The contractor shall ensure the TAWS Tool has the capability to digitally sign all created products.

The contractor shall work with the prime integrator on a continued basis to ensure seamless integration of digital signatures in the navigational database life cycle.

Software deliveries will be made in accordance with CDRL A001.

3.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.

o The contractor shall maintain applicable software to be WOW 64 compliant

Developer Tools. The contractor shall use Visual Studio Ultimate and Visual Studio Test Professional for the purpose of communicating IntelliTrace 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 as well as the Engineering Release (ER) 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 collaborate with Software Engineering Information Center (SEIC) and Government test agencies in order to produce MPE 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 Enterprise Deficiency Reporting (EDR) system for each release no later than 10 days prior to FQT.

Following FQT, there will be a delivery of all discovered Candidate Deficiency Report (CRs) during FQT. Those CRs will be posted to the collaboration site no later than 15 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.

Cost/Schedule/Performance Analysis. The contractor shall submit their cost, resource-loaded MS Project schedule (with critical internal/external dependencies identified), and technical proposal to address delivery of the technical requirement sets.

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--SRR, PDR, CDR and

FQT.

Engineering Change Proposal (ECP) as required. (CDRL A003).

Request for Variance (RFV) as required. (CDRL A004).

GFE Return to Government. The contractor shall ship and deliver all GFE items to the Government at Hanscom AFB, MA at the end of PoP. GFE items include MPE-level desktops/workstations, laptops/tablets, SDTMR, DTDs, associate peripherals, and the associated documents and software.

3.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 will be 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 (DR).

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 (WFM, TFM/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 A008):

Source data validation (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; and Usability of newly available terrain data such as NGA’s 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 A008)

The contractor shall support technical interchange meetings and working groups pertaining to C-17

TAWS.

o The contractor shall report technical interchange meetings and working group findings to Government NLT 15 days post support.

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 Foreign Military Sales (FMS) geographical requirements for all countries (including NATO) except India and Kuwait.

The contractor shall provide documentation to include Mission Planning User’s Manual, System Administrator’s User’s Manual and Pocket Check Lists for Mission Planning and System Administration. (CDRL A013)

The contractor shall provide documentation to include the Software Requirements Specification

(SRS). (CDRL A007)

The contractor shall provide documentation to include the Software Version Description (SVD).

(CDRL A009)

3.4 Test

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

3.5 Concept of Operations

The Contractor shall develop, update, and maintain 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 A008)

3.6 User Participation

The Contractor shall maximize the use of subject matter experts during 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.

All direction and/or any change in the contract shall come from the government’s Procurement Contracting Officer (PCO).

3.7 SEIC Coordination

The contractor shall coordinate with and provide SEIC with SW engineering releases for horizontal integration.

The Contractor shall coordinate any data or software issues discovered, as well as solutions, with SEIC before implementation.

3.8 General Cybersecurity Requirements

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

(CDRL A049)

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

3.8.3 The contractor shall perform and document security test and evaluation during FQT, to include:

STIG/TCNO compliance evaluation of all IA-enabled COTS components in their software product’s runtime environment (i.e., Windows OS, MS Office, 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.

3.8.4 NISPOM Compliance

At facilities processing collateral classified information, the contractor shall comply with all applicable NISPOM requirements for handling of classified and sensitive data associated with the C-17 TAWS development effort.

Additional security-related guidance will be provided in the collateral DD Form 254, Contract Security Classification Specification and in the MPS Security Classification Guide.

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

3.8.6 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 as follows: Ensure 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 days before the start of FQT and during DT until 60 days before the end of DT.

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

The contractor shall comply with the MPS Enterprise GPO (Group Policy Object) Management process as follows: Ensure 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 days before the start of FQT and during DT until 30 days before the end of DT.

TCNOs/IAVMs must be periodically updated to the latest available TCNO/IAVM package until 30 days before the start of FQT and during DT until 30 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.

3.8.7 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 Terrain Awareness and Warning System (TAWS) Tool Version 2.x, dated 15 February 2017.

3.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 (Dev Evals) 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 will be provided for Government, other Contractor developers, and the SEIC.

4.0 Management Objectives

4.1 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 SOW.

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.2 Status and Schedule

The contractor shall implement and maintain a schedule management system 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 A015)

4.3 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop a Contract Work Breakdown Structure (CWBS) and a CWBS dictionary consistent with the C-17 TAWS Tool and Annual DB Sustainment Contract development, integration and test effort. (CDRL A012)

4.4 Associate 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.5 Data Management

The Contractor shall establish and maintain procedures to ensure accurate identification, preparation, tracking, and delivery of all contract data, including data prepared by subcontractors.

Procedures will be in accordance with the Enterprise Configuration Management Plan.

4.5.1 Marking of Technical Data

The Contractor shall mark all technical data to be delivered by CDRL with appropriate distribution statements and export control warning notice IAW the CDRL general instructions.

4.5.2 Data Accession List/Internal Data

The Contractor shall generate and maintain a list of internal data and computer software generated as a result of this DO, but not otherwise required for delivery. (CDRL A006/A008)

4.6 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 DO. All meetings and design reviews will be conducted IAW the Enterprise Meeting Process. (CDRL A011)

4.6.1 Enterprise Level Meetings

Meeting Title Location Frequency Duration

1 C-17 Aircraft Working Group (ACWG) Variable Yearly 3 days

4.6.2 DO Specific Meetings

Meeting Title Location Frequency Duration

1 Delivery Order Kick-Off (DOKO) Review KTR’s Location As Required 1 day

2 Test Readiness Review (TRR) KTR’s Location As Required 1 day

4.7 Data

The contractor shall develop and deliver the data identified on the C-17 TAWS Tool and Annual DB Sustainment Contract CDRL List.

4.8 Incentives

Contractor will be evaluated in CPARS based on meeting performance standards.

4.9 Place of Performance

The Place of Performance shall be at the Contractors facilities, operational units, avionics manufacturer facilities, aircraft OEM facilities, and Government military installations.

Alternate Place of Performance - Contingency Only. Contractor employees may be required to work at home, another approved activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. COR approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing Government resources.

To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the SOW. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment.

4.10 Period of Performance

The POP shall be a base period of 27 November 2019 through 26 May 2020 and two 3 month options.

As directed by the COR, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR.