12._SW_Maintenance_Product_Description.pdf

For Official Use Only

AFLCMC/WLS (Galaxy Division)

Air Force Life Cycle Management Center

Robins AFB, GA

21 February 2017

PRODUCT DESCRIPTION (PD)

C-5 Lockheed Software Maintenance

FILE NUMBER: FD2060-16-92838

Revision Record

FILE NUMBER: FD2060-16-92838

Table of Contents

1.0 Product Description

1.1 Emergency Software Update (ESU) Task Orders

2.0 Applicable Documents

2.1 Military Standards (MIL‐STD)

2.2 International Standards Organization (ISO)

2.3 Other Government Documents

2.4 Commercial Engineering Standards and Guidelines

3.0 Operational Flight Program

3.1 Cybersecurity

3.1.1 Airworthiness

3.1.2 CNS/ATM

3.1.3 Interoperability

3.1.4 Product Baseline Management

3.1.5 Software Product Design

3.1.6 Implement, Integrate, and Update

3.2 Quality Assurance

3.3 Product Configuration Verification

3.4 Program and Business Management

3.4.1 Program Management

3.4.2 Business Management

3.5 Data Management

3.5.1 Data Rights

3.6 Formal Qualification Testing (FQT) Capability

3.7 Technical Manuals

3.8 Optional Product Support

3.8.1 SIL Availability

3.8.2 Engineering Support

3.8.3 Special Studies and Engineering Analysis

3.8.4 Software Transition Tasks

3.9 Security Clearance

3.9.1 SIPRNet Access

Appendix A: Entrance/Exit Criteria

Appendix B: CDRL Requirements

FILE NUMBER: FD2060-16-92838

1.0 PRODUCT DESCRIPTION

This Product Description (PD) outlines the software product and supporting product deliverables for the Lockheed Martin Aero (LMA) Software Maintenance contract for the C-5M aircraft.

The product deliverables from task orders awarded under this contract shall include Software Updates (SU) that address Deficiency Reports (DRs) listed in Appendix B of applicable Product Descriptions for each task order. Any or all of the C-5M software partitions may be updated as part of a task order. The product deliverables shall go through Formal Qualification Testing (FQT) and be a C-5M compatible aircraft Operational Flight Program (OFP) with supporting certification artifacts and documentation.

Product deliverables also include engineering analysis of service-revealed software deficiencies.

The products shall comply with all C-5M certifications as found in section 3.1 prior to final acceptance.

1.1 Emergency Software Update (ESU) Task Orders

ESU task order(s) may be required to resolve safety and/or flight critical software deficiencies.

The ESU shall be made against the currently fielded version of the C-5 software or an alternate version identified by the C-5 Program Office. Each task order will identify the specific software issue(s) to be addressed and configuration impacted (i.e., AMP, RERP, or both). The general requirements to achieve these objectives for the various phases of each ESU will be noted on the ESU task order and will follow the same requirements as noted in the SU task order section unless further clarification is provided in the task order.

2.0 APPLICABLE DOCUMENTS

The documents listed below are incorporated into this product description. Compliance is required in order to support product certification prior to final acceptance.

2.1 Military Standards (MIL-STD)

MIL-STD-882E, Department of Defense Standard Practice For System Safety, 11-May-12

2.2 International Standards Organization (ISO)

Joint Aviation Authorities (JAA) Leaflet 10, Airworthiness and Operational Approval For Precision RNAV Operations In Designated European Airspace

2.3 Other Government Documents

AFI 17-130, Air Force Cybersecurity Program, 31 August 2015; AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP), 23 December 2011

ASC/CC Memo, ASC Guidance Memorandum on Information Assurance (IA) Certification and Accreditation (C&A) Requirements for Platform IT (PIT), 25 April 2010

AFI 63-137, Assurance of Communications, Navigation, Surveillance/Air Traffic Management

FILE NUMBER: FD2060-16-92838

(CNS/ATM), Navigation Safety, and Next Generation Air Transportation System (NEXTGEN) Performance, 29 March 2012

Air Force Policy Directive (AFPD) 33-2, Information Assurance (IA) Program, 03 August 2011

DoD Directive 5220.22-V3, National Industrial Security Program Operations Manual, 17 April 2014; DoD Directive 8500.01, IA, 14 March 2014; DoD Instruction 8500.2, IA Implementation, 06 Feb 2003; DoD Instruction 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), 01 March 2014; MIL-HDBK-516B, Airworthiness Certification Criteria, 12 December 2014; NIST SP 800-53, Department of Defense Directive 5230.24

USAF Airworthiness Bulletin (AWB)-007, 5 May 2011

USAF Airworthiness Bulletin (AWB)-013A, 29 June 2011

MIL-HBK-516C Airworthiness, and Cyber AFIs (e.g. AFI33-210)

2.4 Commercial Engineering Standards and Guidelines

AC 20-130C, Airworthiness Approval of Positioning and Navigation Systems, 28-Mar-14

AC 90-91K, North American Route Program (NRP), 11-Dec-08

DO-178C Software Considerations in Airborne Systems and Equipment Certification, December 2011

ARINC 622, ATS Data Link Applications over ACARS Air-Ground Network, 12-October-2001

ARINC 702A-4, Advanced Flight Management Computer Systems, December-2014

3.0 OPERATIONAL FLIGHT PROGRAM

The contractor shall work in partnership with the Government to develop, integrate, test, and deliver software that is compatible for integration into the C-5M baseline. LMA and the Government’s roles and responsibilities will be determined by the Government depending on the technical scope for each task order as defined in the Implementation Agreement (IA) that forms part of the contract. This software shall be compatible with the current C-5M software baseline at the time of task order award. Delivery of this software along with product support documentation shall be on CD/DVD media format and identified with a Government Computer Program Identification Number (CPIN). The contractor shall deliver copies of every engineering test build created during the program, in addition to the final build, to the Government for early insight and evaluation of software capabilities. Delivery of engineering test builds to the Government shall be concurrent with the contractor’s internal release schedule for evaluation.

The Contractor shall maintain a Data Accession List (DAL). The DAL is an index of data or work products generated or modified under the contract but are not covered by existing CDRLs.

Work products and data listed in the DAL shall be delivered to the Government upon request.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL D001 DI-AVCS-80700 Computer Software Product End Item, Complied Loadable

FILE NUMBER: FD2060-16-92838

Image;

CDRL D002 DI-IPSC-81488 Computer Software Product (Source Code);

CDRL D003 DI-IPSC-81488 Computer Software Product (Source Code Test Scripts);

CDRL D004 DI-AVCS-80700 Computer Software Product End Items (SW Licenses);

CDRL D005 DI-AVCS-80700 Computer Software Product End Item (Software Toolsets and Associated Documentation);

CDRL D006 DI-IPSC-81429A Software Transition Plan (STRP);

CDRL D007 DI-IPSC-81488/T Computer Software Product (General Test Scripts)

3.1 Cybersecurity

The contractor shall integrate cybersecurity and cybersecurity risk management into their overall systems engineering, acquisition, test and evaluation, and risk management processes in accordance with AFI33- 210 Air Force Certification and Accreditation (C&A) Program (AFCAP).

Cybersecurity and system security requirements for the product must be identified, traceable and documented as part of a product life cycle systems engineering process in accordance with DoDI 8500.2 and NIST SP 800-53. Cybersecurity for product integration shall include the incorporation of technical and non-technical requirements to protect C-5M cybersecurity systems and data from unauthorized access and exploitation.

The contractor shall provide an analysis of cybersecurity impacts to the existing C-5M baseline as a result of the product introduction per the Government approved IMS. The cybersecurity impact analysis shall be delivered in a scientific and technical report. The impact analysis shall include the entire software chain (e.g. maintenance). Product maintenance activities include on aircraft SUs as well as process related activities for software product development and transfer.

Boundary diagrams for interfaces on the aircraft affected by the product as well as boundary diagrams illustrating the data transfer mechanisms/controls between prime contractor and subcontractors for software products and data transfer shall be provided.

The description of mechanisms and controls for software product/data transfer shall provide sufficient insight to show that the software product/data are not vulnerable to malicious code or erroneous data injected by an outside party. A follow-up detailed analysis of cybersecurity impacts stemming from the product along with recommended controls shall be identified no later than Critical Design Review (CDR).

The contractor shall provide the Government a product Cybersecurity Test Plan that will result in accreditation of the C-5M aircraft-based information technology system to comply with cybersecurity policies and criteria and shall be identified per the Government approved IMS.

The contractor shall provide supporting product documentation via the contract CDRLs and Data Accession List (DAL) that enables the Government to obtain cybersecurity certification of the final software product. Software product cybersecurity modification assessments shall be performed, updated and delivered in a supporting scientific and technical report that identifies the cybersecurity modification’s overview, posture, and impacts. The Contractor shall provide and deliver a means for requirements traceability for the full baseline systems as well as all hardware and software changes to support ATO documentation via CDRL C002, Software

FILE NUMBER: FD2060-16-92838

Requirements Specification (SRS).

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL C002 DI-IPSC-81433A/T Software Requirements Specification;

CDRL C00D DI-MISC-80711A/T Scientific and Technical Reports;

CDRL C00F DI-MGMT-81845 Information Assurance (IA) Design Review Information Package (DRIP);

CDRL C00G DI-MGMT-81844 Information Assurance (IA) Test Plan;

CDRL C00H, DI-MGMT-81843, Information Assurance (IA) Test Report

3.1.1 Airworthiness

The contractor shall deliver product support documentation via the contract CDRLs and DAL that clearly demonstrates adherence to Air Force airworthiness criteria using data generated throughout the product development activities. The contractor shall not create any data that is unique to the demonstration of airworthiness.

A System Safety Risk Assessment shall be provided as part of the product support deliverables and delivered as a scientific and technical report.

Development of product support documentation for airworthiness shall require contractor participation in External Certification Working Groups with the Government to define and review the airworthiness certification criteria to ensure that the product support deliverables are acceptable.

A modification risk assessment for the software product shall be provided as part of the supporting product documentation. The risk assessment shall include an analysis of the functional areas of the modification, detailed description of the modification, and a recommended report-ability determination in accordance with USAF Airworthiness Bulletin

(AWB)-007.

Preliminary product support data flowing to and from the Government shall be exchanged with the Government using a method agreed upon by the Certification Working Group Airworthiness Certification Plan (AWCP) and shall contain the central location which product artifact data are stored.

An Airworthiness Certification Criteria/Compliance Report and Airworthiness Specification for the product shall be updated and delivered to the Government.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL C007 DI-SESS-81768 Airworthiness Certification Criteria Report;

CDRL C008 DI-SESS-81766 Airworthiness Specification;

CDRL C00D DI-MISC-80711A/T Scientific and Technical Reports

3.1.2 CNS/ATM

The contractor shall provide supporting product artifacts via the contract CDRLs and DAL that enables the Government to obtain Communication, Navigation, Surveillance/Air Traffic Management (CNS/ATM) certification of the final software product. Product support documentation for this area shall include a Required Navigational Performance (RNP) impact analysis delivered in the form of a scientific and technical report. The impact analysis shall include an appendix of tailored CNS/ATM matrices for those areas impacted by the product (e.g.

data link matrices). The contractor shall jointly work with the C-5 Program Office and the CNS/ATM compliance authority at Hanscom AFB to tailor generic performance matrices and identify all test artifacts required to achieve continued compliance for operation of the C-5M within civil airspace when the product is installed on the aircraft. Identified test and documentation artifacts shall be incorporated in the final delivery of the scientific and technical report.

3.1.3 Interoperability

The contractor shall provide supporting product artifacts via the contract CDRLs and DAL that enables the Government to obtain Joint Interoperability Test Command (JITC) Certification of the final software product. Impacts to Interoperability shall be documented in the form of a scientific and technical report.

3.1.4 Product Baseline Management

The contractor shall conduct joint reviews with the Government that identify and resolve product requirement uncertainties. The reviews shall be held at the contractor’s facility or Robins AFB, GA. LMA shall perform the following joint reviews: Systems Requirements Review (SRR), Software Requirements Analysis Review (SRAR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), Functional Configuration Audit (FCA)/ Physical Configuration Audit (PCA). These joint reviews shall be performed in concert with the Government and subcontractor as required. The Government defined entry/exit criteria and acceptance/rejection criteria for each formal product review shall be as defined in Appendix A.

The Contractor shall establish associate contractor agreements (ACAs) with Trainer contractors as required for transfer of information necessary to update the C-5M trainers. The Contractor shall include the Trainer contractor and the Trainer System Program Office (SPO) in all milestone technical reviews to establish scope of impacts to training devices, requirements, licensing, etc. necessary to update the Trainers with updated OFP capability. The Contractor

FILE NUMBER: FD2060-16-92838

shall ensure that the Trainer Contractor has a complete and final set of requirements to update the Trainer software by CDR. The Contractor shall negotiate licensing with the Trainer contractor for any software source code or other data necessary for the Trainer contractor to accomplish the required updates under this tasking in order to expedite updates to the training devices.

The contractor shall support a maximum of two Flight Station Working Groups (FSWGs) conducted by the Government early in the product development schedule to enable product users to assess early product design concepts and provide feedback. The FSWGs shall be held at the Warner Robins System Integration Laboratory (SIL). All FSWG collected requirements shall be fully known and included in the final product design presented to the Government as part of the CDR and Verification Review Council (VRC). The contractor shall update and deliver the Human Engineering Design Approach Document - Operator and the Human Engineering Design Approach Document –Maintenance.

CDRL A001, DI-ADMN-81505/T, Report, Record of Meeting/Minutes

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL A005 DI-MGMT-81861/T, Integrated Program Management Report;

CDRL A008 DI-ADMN-81249A Conference Agenda;

CDRL A00D DI-ADMN-81401B, Contract Change Proposal;

CDRL A00G DI-SESS-80639D/T, Engineering Change Proposal;

CDRL A00H DI-SESS-80640D/T, Request for Variance, CDRL C00A DI-HFAC-80747B/T Human Engineering Design Approach Document- Maintainer;

CDRL C00B DI-SESS-81757A/T, Design Review Information Package (DRIP);

CDRL C009 DI-HFAC-80746C/T, Human Engineering Design Approach Document- Operator

3.1.5 Software Product Design

The contractor shall initiate, track, document and deliver updates to the product support documentation to the Government (e.g. Software Product Specifications (SPS), Software Design Document (SDD), Software Requirements Specifications (SRS), Interface Requirements Specification (IRS), System/Subsystem Specification (SSS), and Interface Control Documents (ICDs)). Opportunities for source code optimization shall be considered as part of the design effort.

All product changes required to implement the SUs shall be defined to the lower level product requirements, design and code to be evaluated/analyzed/verified.

The product support package deliverables shall include the following updates:

a. Update impacts and/or changes to the System/Software Engineering Environment

(S/SEE) requirements including test

b. Update the C-5M System Safety Hazard Analysis with the task order SU

c. Update Weapon System and Air Vehicle Specification requirements within DOORS™

d. Update Mission Processing Specification requirements within DOORS™

e. Update Integration Specifications requirements within DOORS™

f. Update Critical Item Development Specification Components

g. Update SRS or Software Requirements Document (SRD) for each Computer Software Configuration Item (CSCI) within DOORS™

h. Update System/Subsystem Design Description

i. Update Software Design Documents

j. Update SPS

k. Deliver updated Software Version Descriptions

l. Update IRS

m. Update Human Engineering Design Approach Documents as appropriate (e.g. HEDAD-

O and HEDAD-M)

n. Update the product ICD Input/Output (I/O) database and/or other ICDs that shall as a minimum, contain all digital data bus I/O, analog I/O, discrete I/O, spare I/O, provisional I/O, and power information along with signal characteristics information required to successfully integrate the updated product with existing C-5M systems. Additionally, any other ICDs not referenced above shall also be updated and delivered to the Government if affected by the product changes under a task order awarded under this effort.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL C001 DI-IPSC-81441A/T, Software Product Specification;

CDRL C002 DI-IPSC-81433A/T Software Requirements Specification;

CDRL C003 DI-IPSC-81434A/T Interface Requirements Specification;

CDRL C004 DI-SESS-81248B/T Interface Control Document;

CDRL C005 DI-SAFT-80101B/T System Safety Hazard Analysis Report (SSHA);

CDRL C006 DI-IPSC-81427A/T Software Development Plan;

CDRL C009 DI-HFAC-80746C/T, Human Engineering Design Approach Document-Operator;

CDRL C00A DI-HFAC-80747B/T, Human Engineering Design Approach

FILE NUMBER: FD2060-16-92838

Document-Maintainer;

CDRL C00C DI-IPSC-81442A/T Software Version Description;

CDRL C00D DI-MISC-80711A/T Scientific and Technical Reports;

CDRL C00K DI-IPSC-81431A/T System/Subsystem Specification;

CDRL C00J DI-SDMP-81465 Performance Specification - Air Vehicle Specification;

CDRL C00L DI-IPSC-81432A System Subsystem Design Description;

CDRL C00M DI-IPSC-81435A Software Design Description;

CDRL C00N DI-SDMP-81465 Performance Specification – Weapon System

3.1.6 Implement, Integrate, and Update

System regression and verification tests for the product shall be developed and/or updated to a fidelity that supports integration and certification of software changes into the C-5M.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL E001 DI-NDTI-80809B/T Test/Inspection Report;

CDRL E002 DI-NDTI-80566A/T Test Plan;

CDRL E003 DI-QCIC-81536 Test Information Sheet (TIS) (Regression Test);

CDRL E004 DI-QCIC-81536 Test Information Sheet (TIS) (VTIS);

CDRL E005 DI-QCIC-81536 Test Information Sheet (TIS) (ITIS);

CDRL E006 DI-IPSC-81440A/T Software Test Report;

CDRL E007 DI-IPSC-81438A Software Test Plan;

CDRL E008 DI-IPSC-81439A Software Test Description

3.2 Quality Assurance

The contractor shall document and implement their Software Quality Program in order to deliver a product that includes software product sustainment.

3.3 Product Configuration Verification

A product Configuration Verification and Audit shall be accomplished to verify that the end product and supporting product documentation package meets the Government requirements.

The contractor shall support/host the final product system and subsystem level FCA and PCA and System Verification Review (SVR), with Government participation and approval for all noncompliance of product requirements. The product and supporting deliverables shall include all CDRLs noted in the Appendix B.

CDRL A001 DI-ADMN-81505/T, Report, Record of Meeting Minutes;

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL A008 DI-ADMN-81249A, Conference Agenda;

CDRL C001 DI-IPSC-81441A/T Software Product Specification;

FILE NUMBER: FD2060-16-92838

CDRL C002 DI-IPSC-81433A/T Software Requirements Specification;

CDRL C003 DI-IPSC-81434A/T Interface Requirements Specification;

CDRL C004, DI-SESS-81248B/T, Interface Control Document (FIDO);

CDRL C005 DI-SAFT-80101B/T SYSTEM SAFETY HAZARD ANALYSIS REPORT

(SSHA);

CDRL C006 DI-IPSC-81427A/T Software Development Plan;

CDRL D006 DI-IPSC-81429A Software Transition Plan (STRP);

CDRL C007 DI-SESS-81768 Airworthiness Certification Criteria Report;

CDRL C008 DI-SESS-81766 Airworthiness Specification;

CDRL C009 DI-HFAC-80746C/T, Human Engineering Design Approach Document- Operator;

CDRL C00A DI-HFAC-80747B/T Human Engineering Design Approach Document- Maintainer;

CDRL C00B DI-SESS-81757A/T, Design Review Information Package (DRIP);

CDRL C00C DI-IPSC-81442A/T Software Version Description;

CDRL C00E DI-SESS-81646B Configuration Audit Plan;

CDRL C00F DI-MGMT-81845 Information Assurance (IA) Design Review Information Package (DRIP);

CDRL C00G DI-MGMT-81844 Information Assurance (IA) Test Plan;

CDLR C00H DI-MGMT-81843, Information Assurance (IA) Test Report

CDRL C00J DI-SDMP-81465 Performance Specification - Air Vehicle Specification;

CDRL C00K DI-IPSC-81431A/T System Subsystem Specification;

CDRL C00L DI-IPSC-81432A System Subsystem Design Description;

CDRL C00M DI-IPSC-81435A Software Design Description;

CDRL C00N DI-SDMP-81465 Performance Specification – Weapon System;

CDRL D001, DI-AVCS-80700, Computer Software Product End Item (Complied Loadable Image);

CDRL D002 DI-IPSC-81488 Computer Software Product (Source Code);

CDRL D003 DI-IPSC-81488 Computer Software Product (Source Code – Test Scripts);

CDRL D004 DI-AVCS-80700 Computer Software Product End Items (SW Licenses);

CDRL D005 DI-AVCS-80700 Computer Software Product End Items (Toolsets);

CDRL D007 DI-IPSC-81488 Computer Software Product (General Test Scripts);

CDRL E003 DI-QCIC-81536 Test Information Sheet (TIS) (Regression);

CDRL E004 DI-QCIC-81536 Test Information Sheet (TIS) (VTIS);

CDRL E005 DI-QCIC-81536 Test Information Sheet (TIS) (ITIS)

3.4 Program and Business Management

3.4.1 Program Management

a. The contractor shall establish, update and provide to the Government an IMS for product delivery. A Post-Contract Award Kickoff Meeting shall be accomplished within 45 days after contract award. The contractor shall address cost planning, project schedule, planned development activities, planned test activities, test venues, and risk management at the contract kick-off meeting for Cost Plus Fixed Fee (CPFF) CLINs. For Firm Fixed Price (FFP) CLINs, the contractor shall address programmatic planning only. Detailed cost data for FFP CLINs is not required. Agenda and Meeting minutes shall be created and delivered.

CDRL A001 DI-ADMN-81505/T, Report, Record of Meeting Minutes;

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL A005 DI-MGMT-81861/T, Integrated Program Management Report;

CDRL A008 DI-ADMN-81249A, Conference Agenda

b. A record of contract obligations and disbursements financial execution by Contract Line

Item Number (CLIN) using standard cost performance reports shall be delivered on only CPFF CLINs.

1. A status report reflecting the project financial overview shall be provided No

Later Than (NLT) 90 calendar days after contract award on only CPFF CLINs.

The financial overview shall show the projected spend plan for labor and material on one chart and projected travel on another chart. The financial overview charts shall contain all subcontractor cost data. The charts shall plot, by month, the actual expenditures against the baseline plan. The charts shall plot from initial award amounts showing any possible changes as a result of contract modifications. The project shall be tracked including notification of any schedule changes.

2. Any possible financial or technical changes that may impact the planned completion per the schedule and cost information shall be reported to the Government. The financial or technical changes shall either be integrated into or be as attachment(s) to the Contract Funds Status Report.

Semi-annual Program Management Reviews shall be conducted and/or supported. The first meeting shall be scheduled approximately 180 days following contract award; subsequent reviews will be held semi-annually. The contractor shall plan to accomplish all Program Management Reviews on Robins AFB, GA or the LMA facility at Warner Robins, GA or via video teleconference.

CDRL A001 DI-ADMN-81505/T, Report, Record of Meeting Minutes;

FILE NUMBER: FD2060-16-92838

CDRL A002 DI-MGMT-80368A/T Status Report;

CDRL A003 DI-MGMT-81468/T Contract Funds Status Report;

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL A005 DI-MGMT-81861/T, Integrated Program Management Report;

CDRL A006 DI-MGMT-81861 IPMR (Contract Performance Report);

CDRL A007 DI-MGMT-81334D Contract Work Breakdown Structure;

CDRL A008 DI-ADMN-81249A, Conference Agenda

3.4.2 Business Management

3.4.2.1 Collaboration with Government C-5 Software Integration Laboratory

The contractor shall be responsible for ensuring that the product is compatible with the C-5 SIL environment at Robins AFB to accomplish required testing. All required commercial and noncommercial toolsets used in the development and testing of the product shall be identified.

Upon request, the contractor shall provide pricing for the licensing and delivery of the identified non-commercial toolsets to the Government for organic use.

The Contractor shall be responsible for ensuring that the product is available for integration testing within the C-5 SIL environment at Robins AFB. All required commercial and noncommercial toolsets necessary for integration testing shall be identified and if applicable, licensed and delivered to the Government. The Contractor shall support independent testing of the product solution in the Robins AFB C-5 SIL as well as the Contractor’s facility. The Contractor shall develop a schedule for periodic releases of software engineering builds and hardware solutions. Periodic releases of software engineering builds, QT builds, FQT entry builds and any hardware solutions shall be delivered to the Robins AFB C-5 SIL for independent testing in the Government SIL concurrent with internal release for test at the contractor’s facility.

One shipset of equipment shall be provided to the Robins AFB C-5 SIL at the same time the equipment is available to the Contractor’s SIL. The Contractor shall identify additional spares as necessary. The Government reserves the right to witness all testing at all contractor facilities used in the development of the product.

CDRL A002 DI-MGMT-80368A/T Status Report (SIL Status);

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL D001 DI-AVCS-80700, Computer Software Product End Item (Complied Loadable Image);

CDRL D002 DI-IPSC-81488 Computer Software Product (Source Code);

CDRL D003 DI-IPSC-81488 Computer Software Product (Source Code – Test Scripts);

CDRL D004 DI-AVCS-80700 Computer Software Product End Items (SW Licenses);

CDRL D005 DI-AVCS-80700 Computer Software Product End Items (Toolsets);

CDRL D006 DI-IPSC-81429A Software Transition Plan (STRP);

CDRL D007 DI-IPSC-81488 Computer Software Product (General Test Scripts)

3.4.2.2 Independent Verification and Validation (IV&V)

The Contractor shall support, in the Contractor’s or Government facilities the IV&V of any software products they update or test as a result of a SU, software development, or ESU task order including software products that interface with or impact the software products sustained under this effort. The Contractor shall maintain, update, and deliver the Flight Information and Data Output (FIDO) ICD along with any other ICDs that are updated as part of the product development.

CDRL C004, DI-SESS-81248B, Interface Control Document

3.5 Data Management

In order to support delivery and certification of the final product, the contractor shall implement and retain a data management program for generating, acquiring, identifying product data, providing status, planning and controlling technical and management data and related information for product support deliverables. The contractor shall mark all deliverable technical documents, data, and information appropriately before primary distribution is accomplished (reference Department of Defense Directive 5230.24). The contractor shall only reference commercial or military standards/processes on their deliverable data products unless any internally referenced standards/processes have also been delivered to the Government with Unlimited rights. The contractor shall generate a list of all data created as part of this PD effort, not delivered under CDRL, and make such data available for delivery to the Government, if requested, via the DAL. Appropriate markings for data rights shall also be identified for all items on the DAL.

3.5.1 Data Rights

The Government intends to exercise its data rights as set forth within the contract. Procurement and use of proprietary contractor/subcontractor technical data not previously delivered to the Government that are required for execution of this contract shall be the responsibility of the contractor. Certain data rights regarding the C-5M computer software, computer software documentation and technical data have been previously negotiated under a Specially Negotiated License Agreement (SNLA) SLA-13-C5-001, AMD 001. Computer software, computer software documentation and technical data modified as part of the task order product development that are included within the SNLA shall be marked and delivered with the level of data rights defined within the SNLA.

All product and specification documents modified under this program using program funds that are not part of the SNLA, shall be delivered with the appropriate data rights legend/markings.

All new requirements documents developed using program funds shall be delivered with Unlimited Rights. Those areas developed with mixed funding shall be delivered with the appropriate rights as specified at Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation). Additionally, acquisition of new and modified computer

FILE NUMBER: FD2060-16-92838

software, computer software documentation, or other technical data shall be subject to Department of Defense (DoD) FAR Supplement clauses 252-227-7013 Rights in Technical Data-Noncommercial Items and 252-227-7015 Technical Data- Commercial Items.

3.5.2 Delivery of Software and Associated Data

The Contractor shall provide to the Government prior to contract award, Identification and Assertion of Use, release, or Disclosure Restrictions (DFARS 252.227-7017) notifications for any data to be provided to the Government with restrictions on use, modification, reproduction, release or disclosure. Justification and data to substantiate such claims via source of funds determination shall be provided. Software rights previously negotiated under SLA-13-C5-001, AMD 001 shall apply to this task where applicable if any software listed under that agreement is to be updated as part of the task order effort.

All software source code and documentation comprising CSCIs modified under this Contract with Government funding for the Operational Flight Program(s) (OFPs), build files, and test scripts shall be delivered to the Government. The contractor shall deliver new/modified software documentation in accordance with the appropriate DFARS clause(s). All software development toolsets purchased with program funds shall be delivered to the Government along with appropriate transferable licenses at the end of the program. Licenses for any approved proprietary toolsets or software shall be identified and negotiated for delivery. The Contractor shall develop and deliver a software transition plan for all software modified under this program.

The software transition plan shall clearly detail and present all processes and procedures necessary to rebuild each piece of software, file, build script or test script necessary to successfully create a loadable image of the computer software in question.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL D001 DI-AVCS-80700, Computer Software Product End Item (Compiled Loadable Image);

CDRL D002 DI-IPSC-81488, Computer Software Product (Source Code);

CDRL D003 DI-IPSC-81488, Computer Software Product (Source Code-Test Scripts)

CDRL D004 DI-AVCS-80700, Computer Software Product End Item (Software Licenses);

CDRL D005 DI-AVCS-80700, Computer Software Product End Item (Software Toolsets and Associated Documentation);

CDRL D006 DI-IPSC-81429A, Software Transition Plan;

CDRL D007 DI-IPSC-81488, Computer Software Product (General Test Scripts)

Acquisition of new and modified computer software and computer software documentation shall be subject to Department of Defense (DoD) FAR Supplement clauses: 252.227-7037 Validation of restrictive markings on technical data, 252-227-7013 Rights in Technical Data- Noncommercial Items, 252-227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation; and 252-227-7015 Technical Data- Commercial Items.

FILE NUMBER: FD2060-16-92838

3.6 Formal Qualification Testing (FQT) Capability

A full FQT of the partitions affected in each task order shall be accomplished under this effort and shall be accomplished in partnership with the Government. FQT activities shall be executed at established testing venues (e.g. organic Government SIL) as directed by the Government for each task order. All FQT activities for formal sell-off of software shall be accomplished in the Government SIL at Robins AFB using contractor and Government personnel unless otherwise approved by the Government. The FQT capability shall meet the testing requirement of DO- 178B and MIL-STD 882E. All supporting work products including test scripts and associated test procedures to accomplish a full FQT as well as new or modified requirements from the software product update shall be delivered to the Government with the appropriate level of rights per the DFARS.

CDRL E001 DI-NDTI-80809B/T, Test Report;

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL D003 DI-IPSC-81488, Source Code Test Scripts;

CDRL E002 DI-NDTI-80566A/T, Test Plan;

CDRL E003 DI-QCIC-81536A Test Information Sheet (TIS) (Regression Test);

CDRL E004 DI-QCIC-81536A Test Information Sheet (TIS) (Verification TIS);

CDRL E005 DI-QCIC-81536A Test Information Sheet (TIS) (Integration TIS - Development);

CDRL E006 DI-IPSC-81440A/T, Software Test Report;

CDRL E007 DI-IPSC-81438A, Software Test Plan;

CDRL E008 DI-IPSC-81439A, Software Test Description

The Contractor shall provide engineering support to the Government engineering flight test team through development and operational testing. The Contractor shall document the results of all test phases that the Contractor participates in with flight test reports. The Contractor shall provide technical support for C-5M computer resources and interfaces to members of the C-5 software sustainment Integrated Product Team (IPT) including, but not limited to, trainers, Government test organizations, field users, and maintainers of systems that interface with C-5M components. The Contractor shall ensure WR-ALC/WLSE stays fully apprised of all discussions and support to Government agencies.

CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Report

3.7 Technical Manuals

The Contractor shall provide source data for all changes implemented as part of the applicable task order. The affected part of any established baseline manual or technical data package will be marked-up to indicate data changes and delivered as a pdf file in the form of Contractor Formatted Source Data.

FILE NUMBER: FD2060-16-92838

Final delivery of source data shall be delivered after a table-top verification and Pre-Publication Review (PPR). Any comments generated during the verification and/or PPR will be the responsibility of the Contractor to incorporate into the final source data. The Contractor shall provide source data changes per the Government-approved Integrated Master Schedule (IMS).

The Contractor shall support the TO Guidance Conference, which shall be held in person at the Contractor’s facility or via teleconference, to provide opportunities for TO source data development personnel to identify changes or impacts to the TO source data development activities since contract award.

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL B001, Technical Manual Contracts Requirement, ref. TMCR 86-01N

CDRL B002 DI-SESS-81000E/T Drawings and Associated Lists

3.8 Optional Product Support

3.8.1 SIL Availability

The Contractor shall provide a SIL that is available on-demand to support 80 hours of operation per thirty (30) day calendar period (within the constraints of one shift during the normal five-day workweek). The Contractor shall provide the Government and other contractors supporting C-5 aircraft systems that interface with or support the C-5 avionics suite impacted by the C-5M software configurations access to their facility as well as the use of test venues including but not limited to AHMU 1, AHMU 2, AHMU 3, ESIM, and Operational Flight Program Mock-Up (OFPMU) and associated SIL equipment. The Contractor shall ensure that the SIL software is maintained and configurable to support all fielded C-5 AMP/RERP modified aircraft. The Contractor shall document usage and issues for all Government-owned benches in a usage log and provide a copy of the usage log data in the MSR. The usage log shall document the start and stop date/time of use, the specific bench component of each venue and associated SIL equipment used. Additionally, the usage log shall also document any SE or interfacing systems, the state(s) of each venue and associated SIL equipment and software. The specific task supported and the user shall be included in the usage logs.

The Contractor shall ensure that each venue and associated SIL equipment and software are maintained and configurable to support all fielded C-5 aircraft with an availability rate of 50% of the time for a one-shift operation (i.e., equivalent to 80 hours per thirty (30) day calendar period) during the normal five-day workweek. In the event of a situation requiring more than 80 hours of operation within a thirty (30) day calendar period, the Contractor shall advise the Government in advance and negotiate a resolution. The primary purpose of the SIL is to support the task orders awarded under this effort. The measure of success is 80 hours of availability in a thirty

(30) day calendar period.

CDRL A002 DI-MGMT-80368A/T Status Report (SIL);

CDRL A004 DI-MGMT-81453A Data Accession List

FILE NUMBER: FD2060-16-92838

3.8.2 Engineering Support

The Contractor shall provide technical support for C-5M computer resources and interfaces to members of the C-5 software sustainment Multi-Functional Team including, but not limited to, trainers, Government test organizations, field users, and maintainers of systems interfacing with AMP and RERP components. Unless otherwise directed by the Government Contracting Officer the Contractor shall directly interface with the Government test organizations, field users, and maintainers of system interfacing with AMP and RERP components. The Contractor shall contact the Government Integrated Product Team (IPT) as a means of communication to these organizations. The Contractor shall not construe requests from Government test organization, field users or maintainers as direction to accomplish work under this contract. The technical support shall also include testing of commercially released software changes (i.e. EGPWS, TCAS, SDU, etc.)

For software related activities, the Contractor shall:

a. Provide subject matter expert information and technical support to operational, maintenance, program office and depot maintenance personnel.

b. Respond to requests from depot maintenance or field operations for engineering support (i.e., Request of Assistance “107”, TO 00-25-107 Maintenance Assistance and Nonconforming Technical Assistance Request and Reply “202” process [Air Force Material Command (AFMC) Manual 21-1, Air Force Materiel Command Technical Order System Procedures], that does not include Contractor’s intellectual property.

c. If requirements for engineering and/or maintenance actions are identified, prepare project plans identifying man-hour and associated cost estimates for planning, execution, and reporting of projects as applicable.

d. Prepare and present briefings as required to the Government on operation and/or maintenance of the systems and on engineering services supported by the applicable tasks.

e. Perform evaluations of guidance from regulatory organizations (e.g., Airworthiness Directives, Service Bulletins, Federal Aviation Administration Revisions, Commercial Consortiums, CNS/ATM) including apprising the Government of the potential impacts to the C-5.

f. Support various reviews, working groups, and boards (e.g., quarterly Computer Resource Working Group, semi-annual/annual Aircraft Information Working Group, bi-weekly CCB telecom, annual Product Improvement Working Group (PIWG), annual CNS/ATM Conference and other meetings) related to tasks under this contract/task order.

g. DR Investigations: Identify root cause in accordance with TO 00-35D-54.

Provide initial response to DR investigations as an interim report within JDRS within the following time periods after Contractor is assigned DR and is notified (e.g. JDRS, email, telephone):

CAT I: 20 clock hours CAT II: 7 calendar days

FILE NUMBER: FD2060-16-92838

Provide final resolution response or resolution plan, including new Estimated Completion Date (ECD), as an interim report within JDRS with a notification to the Program Manager (PM) within the following time periods:

CAT I: 45 calendar days CAT II: 100 calendar days PM requested corrective action to the interim report within JDRS shall be completed within 48 hours.

DRs in open status which have been referred to the Contractor shall be updated with an interim report within JDRS every 90 days with a notification to the PM, with the exception of DRs in open awaiting funds status. PM requested corrective action to interim report shall be completed within 48 hours. DRs in open awaiting funds status shall be updated every 350 days. Responses for all categories shall meet the requirement 100% of the time.

3.8.3 Special Studies and Engineering Analysis

The contractor shall perform special studies and engineering analysis that are not defined in depth in the current PD but fall within the general scope of the C-5M Lockheed Software Maintenance Program. The contractor shall conduct these special studies and engineering analysis if requested and authorized by the PCO. Special studies and engineering analysis include but are not limited to:

a) Analysis of potential changes to the program budget, schedule, and/or content, and the impacts thereof

b) Budgetary cost estimates in support of Government contract/task order planning

c) Cost reduction initiatives

d) DR and/or requirements analysis in support of future task orders

e) Investigation and resolution or service-revealed deficiencies

f) Modification analysis studies in support of future task orders

g) Analysis of alternatives in support of future task orders

When instructed in an engineering study task order for a software-related deficiency, the Contractor shall determine the corrective action of a software deficiency to the level necessary to clearly show that the corrective action is viable (e.g. pseudo-code level, source code level, developmental build). The Contractor shall provide a safety/airworthiness risk assessment that details at the CSCI level the impacted software changes and the testing required to maintain the C-5M in accordance with the DO-178B specifications. The assessment, impacted changes and associated testing shall be documented in the CDRLs identified in each task order. The engineering study shall identify any shortfalls in testing capability with proposed solutions to resolving the shortfall. The Contractor shall provide block flow analysis to the CSCI level for the incorporation of new software capability.

FILE NUMBER: FD2060-16-92838

When instructed in an engineering studies task order, the Contractor shall provide a report of all open C-5M software deficiencies. Specific format and CDRL requirements will be identified in the task order. The report shall be developed from a list of software deficiencies that is documented and regularly updated in the monthly status report. The Contractor shall document as a software DR any Contractor findings, i.e. Integration Problem Report (IPR), the Government has reviewed and agrees to track as an unresolved deficiency against the software.

The Contractor shall also, at the PCO’s request, provide recommendations for potential special studies and analysis to the PCO and/or Government PM.

3.8.4 Software Transition Tasks

There are three major tasks that must be accomplished in order to transition the C-5 AMP/RERP Licensed Software, Licensed Computer Software Documentation, and Licensed Technical Data to the Government in accordance with the SNLA. A detailed schedule in Microsoft Project format shall be developed for this effort that shows progress and planned activities associated with each task. Monthly status shall also be provided.

CDRL A002 DI-MGMT-80368A/T Status Report;

CDRL A004 DI-MGMT-81453A Data Accession List;

CDRL A005 DI-MGMT-81861/T, Integrated Program Management Report;

CDRL A006 DI-MGMT-81861 IPMR (Contract Performance Report)

3.8.4.1 Research of ICD Form, Fit, and Function (F3) Data

The contractor shall review all ICDs cited in Tables 3 and 4 of the SNLA to determine what data may not be F3 in nature, the PoP is 6 months ARO. Any data that is deemed not to be F3 in nature shall be identified to the Government and reviewed in technical interchange meetings (TIMs) to be held at Robins, AFB. These reviews are necessary to obtain the Government’s concurrence that such data are not F3 in nature. No more than three (3) TIMS shall be scheduled for this task. Minutes and associated briefing content shall be delivered to the Government. Any ICDs that do not require modification and contain only F3 data shall be delivered to the Government.

CDRL A001 DI-ADMN-81505/T, Report, Record of Meeting/Minutes

CDRL C004 DI-SESS-81248B/T Interface Control Document

3.8.4.2 Cost Estimate and Delivery of Updated ICDs

The contractor shall work with its subcontractors and vendors to secure the release of F3 data contained within the C-5 AMP/RERP ICDs, cited in the SNLA Tables 3 and 4, to the Government with Unlimited Rights as required by 10 USC 2320. This task shall be completed

FILE NUMBER: FD2060-16-92838

within 12 months ARO. The contractor shall provide a cost estimate for removing any data from the ICDs that the Government agrees does not meet F3 criteria as defined by 10 USC 2320 along with the cost of delivery of the revised ICDs. The cost estimate shall be delivered as part of the Record of Minutes. All ICDs that do not require revision or that only require markings changes shall be delivered in accordance with CDRL C004.

CDRL A001 DI-ADMN-81505/T, Report, Record of Meeting/Minutes

CDRL C004 DI-SESS-81248B/T, Interface Control Document

3.8.4.3 Removal of Proprietary Information from ICDs

When the Government has agreed under 3.8.4.1 that certain information contained within each specific ICD identified in the SNLA is not F3 data, the contractor shall remove such data from the identified ICD and deliver the newly revised ICD to the Government under CDRL C004.

This task shall not be executed until the Government has approved the proposed ICD changes and has provided funding for the task. 100% of the delivered ICDs shall be correctly marked in accordance with SNLA SLA013-C5-001 AMD 001, for Categories I-II Rights, mark in accordance with DRARs 252.227-7013. The PoP for this task is 12 months ARO.

CDRL C004 DI-SESS-81248B/T, Interface Control Document

3.8.4.4 Requirement ID Header Update

The contractor shall update the source code header files for all delivered software to reflect the latest requirement identification numbers (REQ IDs) for the C-5 RERP/AMP consolidated DOORs database. All delivered source code file headers shall reflect the most up to date REQ IDs for each associated requirement upon delivery to the Government. This task shall be completed in conjunction with Section 3.0 of this PD and be completed within the 6 months ARO. Any tools or scripts developed to accomplish this task shall be delivered under the DAL.

CDRL A004 DI-MGMT-81453A Data Accession List

3.9 Security Clearance

The Contractor shall ensure Contractor personnel have a valid security clearance appropriate to the access required for proper accomplishment of contract/task order requirements listed on the DD Form 254, Department of Defense Contract Security Classification Specification. The Contractor shall be responsible for obtaining Contractor personnel security clearances.

Contractor inability to obtain proper security clearances…