324_PD_23-31790 Software Services.pdf

For Official Use Only

Lockheed Martin Proprietary Information

AFLCMC/WLS (Galaxy Division)

Air Force Life Cycle Management Center

Robins AFB, GA

30 Jan 2024

PRODUCT DESCRIPTION (PD)

C-5 Lockheed Software Maintenance

FILE NUMBER: FD2060-24-30049

Lockheed Martin Proprietary Information

Revision Record

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 Air Force Documents

2.4 Other Government Documents

2.5 Commercial Engineering Standards and Guidelines

3.0 Operational Flight Program

3.1 Air Vehicle

3.1.1 Airworthiness

3.1.2 CNS/ATM

3.1.3 Interoperability

3.1.4 Product Baseline Management

3.1.5 Product Design

3.1.6 Implement, Integrate, and Update

3.1.7 Verification

3.1.8 Cybersecurity

3.1.9 Systems Engineering

3.2 Quality Assurance

3.3 Configuration Management

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.5.2 Delivery of Software and Associated Data

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

DI-MGMT-81453B Data Accession List DI-MISC-80711A/T Scientific and Technical Reports

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

3.8.4 Software Transition Tasks

3.8.5 Security Clearance

3.8.6 Training

Appendix A: Entrance/Exit Criteria

Appendix B: Deficiencies Report

Appendix C: CDRL Requirements

Appendix D: PD Map

Appendix E: Government Furnished Property…………………………………………………....…...34

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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 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 deficiency issue(s) to be addressed and configuration impacted. The general requirements to achieve these objectives for the various phases of each ESU will be noted on the ESU task order.

The ESU Task Order will follow the same structure as noted in the SU task order section unless further clarification is provided in the task order.

In the event of an ESU need, immediate adjustment of the active Agile software team’s priorities will be executed allowing rapid commencement of work on the DR(s) of interest. Concurrently, a separate task order will be established.

DI-MGMT-81453A Data Accession List

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

DI-SESS-81248B/T Computer Software Product End Item

DI-IPSC-81488/T Computer Software Product (Source Code)

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

DI-MCCR-80700/T Computer Software Product End Items (SW Licenses)

DI-MCCR-80700/T Computer Software Product End Items (Toolsets)

DI-IPSC-81429A/T Software Transition Plan (STRP)

Lockheed Martin Proprietary Information

DI-NDTI-80809B/T Test Inspection Report-Verification Reports and Results

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

MIL-STD-973, Department of Defense Standard Practice For Configuration Management 13-Jan-

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 Air Force Documents

AFI 17-130, Air Force Cybersecurity Program, 13 Feb 2020

AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP), 23 December

AFI 62-6, USAF Airworthiness, 16 January 2019

AFI 62-601_Developmental Engineering Airworthiness, 10 June 2022

AFI 63-137, Assurance of Communications, Navigation, Surveillance/Air Traffic Management (CNS/ATM), Navigation Safety, and Next Generation Air Transportation System (NEXTGEN) Performance, 29 March 2012

AFI 91-202, The USAF Mishap Prevention Program, 24 June 2015

AFI 91-202_AFMCSUP, The USAF Mishap Prevention Program, 17 May 2017

AFI 91-202_AFMCSUP_AFLCMCSUP, The USAF Mishap Prevention Program, 10 April 2018

AFLCMC OI 62-601, USAF Airworthiness Processes for Delegated Technical Authority (DTA), 05 December 2013

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

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

AFPD 62-6, USAF Airworthiness, 16 January 2019

USAF Airworthiness Bulletin (AWB)-002A, Airworthiness Planning, 17 May 2011

USAF AWB-004A, Development of an Airworthiness Certification Basis, 17 June 2011

USAF AWB-005, Tailored Airworthiness Certification Criteria/Modification Airworthiness Certification Criteria (TACC/MACC) Document Construction and Format, 27 September 2010

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

USAF AWB-150B, Airworthiness (AW) Risk Assessment and Acceptance, 30 Sep 20

USAF AWB-215, Change Notices for MIL-HDBK-516, Airworthiness Certification Criteria, 23 July 2018

USAF AWB-225, Airworthiness Delegated Technical Authorities, 20 August 2018

USAF AWB-325, Communications, Navigation, Surveillance-Air Traffic Management (CNS- ATM) Compliance Assessment Process, 03 November 2017

2.4 Other Government Documents

DOD Directive 5030.61, DoD Airworthiness Policy, 31 August 2018

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

Department of Defense Directive 5230.24

MIL-HBK-516C Airworthiness Certification Criteria, 12 December 2014

NIST SP 800-53

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

2.5 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

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

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

National Consensus Standard for Configuration Management (ANSI/EIA-649)

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. The agreed upon license agreement, SLA013-C5-001, shall be used as a basis to develop and deliver software products to the Government. The roles and responsibilities of software tasking will be determined by the Government and Contractor 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

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information award. A final delivery of completed product documentation shall be provided via .zip file as an artifact of the FCA/PCA deliverables. The contractor shall provide engineering test builds created during the program through MEARS and/or EDCS, in addition to the final build, to the Government for early insight and evaluation of software capabilities. The Contractor shall provide engineering test builds to the Government concurrent with the contractor’s internal test schedule to support the Incremental Capability Review cycle. The Government will provide feedback to the contractor during the ICR which will support risk reduction for future aircraft testing. The intended tempo for formalization and release of the software is once per year or after every 4th Program Increment.

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.

DI-MGMT-81453A Data Accession List

DI-SESS-81248B/T Computer Software Product End Item

3.1 Air Vehicle

3.1.1Airworthiness

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)-150B.

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 to be specified in the Implementation Agreement for artifact data storage location.

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

DI-MGMT-81453A Data Accession List

DI-SESS-81768A/T Airworthiness Specification

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

Lockheed Martin Proprietary Information

DI-SESS-81766A/T Airworthiness Certification Criteria Report

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.

DI-MGMT-81453B Data Accession List

3.1.3 Interoperability

The contractor shall provide supporting product artifacts via the contract CDRLs and DAL that enables the Government to obtain Air Traffic Systems (AIMS) Certification of the final software product. Impacts to the avionics system and aircraft transponder information shall be documented in the form of a scientific and technical report.

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), Incremental Capability Reviews (ICRs), 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.

In the event the Contractor uses an electronic specification and requirements toolset or other

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information database type toolsets, then the contractor shall provide periodic snapshots of the database (C-5 specific and limited to 3 deliveries) on the Data Accession List (DAL). In addition, the contractor shall provide the Government remote access to the DOORS Database.

The contractor shall support Flight Station Working Groups (FSWGs) conducted by the Government. The FSWGs shall be held in a manner that supports the program capability increment schedule and such that the design details are mature enough for the working group to be effective. If required FSWGs may be held at the Warner Robins System Integration Laboratory (SIL) with any additional working groups held at the LM facility. As each FSWG is conducted, the collected requirements shall be incorporated into the planned program capability increment and reviewed at the subsequent ICR.

DI-ADMN-81250C/T Conference Minutes

DI-MGMT-81861C/T Integrated Program Management Report - IMS

DI-ADMN-81249C/T Conference Agenda

3.1.5 Product Design

The contractor shall utilize a Scaled Agile development methodology in the execution of the program.

As part of the incorporation of agile development, the contractor shall include all known software system deficiencies, whether contractor or government defined, into an Official Software Backlog List. The contractor shall provide the Official Backlog List to the government for prioritization during each Agile Program Iteration. The contractor shall provide an Official Backlog List at a minimum quarterly. The Official Backlog will consist of the following: to include IPR number, IPR description, and status of corrective action.

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:

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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.

DI-MGMT-81453B Data Accession List

DI-IPSC-81441A/T Software Product Specification

DI-IPSC-81433A/T Software Requirements Specification

DI-IPSC-81434A/T Interface Requirements Specification

DI-SESS-81248B/T Interface Control Document

DI-SAFT-80101C/T System Safety Hazard Analysis Report (SSHA)

DI-IPSC-81427B Software Development Plan

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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

DI-HFAC-80747C/T Human Engineering Design Approach Document-Maintainer

DI-IPSC-81442A Software Version Description

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

DI-SDMP-81431A/T System/Subsystem Specification – Weapon System and/or Air Vehicle System Specification

DI-IPSC-81431A/T System/Subsystem Specification

DI-IPSC-81432A/T System Subsystem Design Description

DI-IPSC-81435B Software Design Document

3.1.6 Implement, Integrate, and Update

System regression and integration tests for the product shall be developed and/or updated to include SU changes and ensure that changes perform adequately per task order requirements on aircraft.

DI-IPSC-81488/T Computer Software Product – ITIS Test Scripts

DI-NDTI-80809B Test/Inspection Report

DI-QCIC-81536/T Test Information Sheet (TIS) (Regression Test)

DI- QCIC-81536/T Test Information Sheet (TIS) (ITIS)

3.1.7 Verification

The Contractor shall verify the System Specification Document (CDRL C00J) system requirements in accordance with the Section 4 verification requirements and the C-5M System Verification Plan (LG13ER5020). The contractor shall conduct a review of the verification approach (plan) to be held jointly with the government to establish scope, criteria for compliance and proposed proof-of-compliance. The Contractor shall prepare Verification Test Information Sheets (VTIS) for verifications that are to be executed in the SIL, Test Information Sheets (TIS) for verifications that are to be executed on the aircraft and Verification Reports (VRPTs) for verifications that are by analysis. The verifications can be executed once all functionality has been implemented versus deferring the test activity until the final release is available.

Requirement closure can occur once all related verifications have been performed for a requirement and the associated proof-of-compliance released.

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, Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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.

DI-NDTI-80809B/T Test/Inspection Report (Verification Reports and Results)

DI-NDTI-80809B Test/Inspection Report

DI-QCIC-81536/T Test Information Sheet (TIS) (VTIS)

DI-ISPC-81440A Software Test Report

DI-ISPC-81438A Software Test Plan

DI-ISPC-81439A Software Test Description

DI-QCIC-81536/T Test Information Sheet (TIS) (TIS)

DI-MISC-80711A/T Scientific and Technical Report

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

DI-MGMT-81453B Data Accession List

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

DI-MGMT-81845/T Information Assurance (IA) Design Review Information Package

(DRIP)

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

DI-MGMT-81844/T Information Assurance (IA) Test Plan

DI-MGMT-81843/T, Information Assurance (IA) Test Report

3.1.9 Systems Engineering

The Contractor shall implement a disciplined system engineering approach that balances the design constraints of cost, schedule, and performance while maintaining an acceptable level of risk in order to ensure system effectiveness, suitability, survivability and sustainability of the modification. The Contractor shall utilize their current Systems Engineering Management Plan (SEMP) (LG02ER0131) that addresses the overall life cycle approach to the technical management of the program.

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 Configuration Management

The Contractor shall maintain the current configuration management approach, which establishes and controls product attributes and the technical baseline across the total system life cycle. This approach shall be defined in the Contractor’s SEMP and the Contractor’s Configuration Management Plan (CMP). At completion of the system level Physical Configuration Audit (PCA), Functional Configuration Audit (FCA) and System Verification Review (SVR), the Contractor shall deliver the supporting Technical Data Package(s) (TDP) and transfer control of the initial product baseline for all Class I (Major A) configuration changes to the Government.

a. Configuration Management and Planning: The Contractor shall prepare and maintain a configuration management plan utilizing the National Consensus Standard for Configuration Management (ANSI/EIA-649) and MIL-STD-973 as guides.

b. Configuration Identification: The Contractor shall define product structure identifying Configuration Items and Computer Software Configuration Items (Cis/CSCIs) affected as part of this contract. The Contractor shall perform functions of configuration item selection, baseline, specification, and drawing identification, document and item identification numbering, labeling, engineering release, and nomenclature assignments.

c. Configuration Control: The Contractor shall establish and maintain Contractor configuration control processes and procedures, including Configuration Control Board (CCB) which provides change identification, evaluation, coordination and approved change implementation disposition and verification of completion. This includes evaluation of subcontractor configuration control processes to ensure it is adequate and in conformance with the CMP. The Contractor shall support the AFLCMC/WLS CCB meetings.

1) The Contractor shall process proposed changes to approved contract baseline

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information configuration documentation via Contract Change Proposals (CCPs) and ECPs, with applicable Notice of Revisions (NORs) and Specification Change Notices (SCNs), as required.

2) The Contractor shall monitor subcontractor generated service bulletins and FAA Airworthiness Directives that potentially affect any of the equipment specific to the modification and shall forward these to the Government. The Contractor shall recommend acceptance or rejection of service bulletins for equipment under Government configuration control and describe impacts to the baselined system design, to include Airworthiness Certification & Safety impacts.

3) The Contractor shall submit a request for variance (deviation or waiver) for any departure from a CI/CSCI Government approved configuration documentation for Government approval.

d. Configuration Status Accounting (CSA): The Contractor shall establish a configuration status accounting system that will systematically capture, record, safeguard, and disseminate data about the product and product configuration information created over the product lifecycle. The Contractor shall provide a configuration description (CSA listing) and monthly CSA report, from approval at the Government CCB through project closure, which provides current status of the engineering and development processes, kitting and delivery status, etc. The CSA shall correlate the as-designed and as-built configuration of any serial-numbered unit of the Cis/CSCIs for each modification kit delivered and/or installed per the contract.

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

DI-ADMN-81249C/T Conference Agenda

DI-ADMN-81401C/T Contract Change Proposal

DI-SESS-80639E/T Engineering Change Proposal

DI-SESS-80640E/T Request for Variance

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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.

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.

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

DI-ADMN-81250C/T Conference Minutes

DI-MGMT-80368A/T Status Report

DI-MGMT-81453B Data Accession List

DI-MGMT-81861C/T Integrated Program Management Report – IMS

DI-ADMN-81249C/T Conference Agenda

DI-MGMT-81468/T Contract Funds Status Report

DI-MGMT-81334D Contract Work Breakdown Structure

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

3.4.2 Business Management

3.4.2.1 Collaboration with Government C-5 Software Integration Laboratory

The contractor shall be responsible for providing a properly configured aircraft VIA/AIU OFP as an Engineering Test Build to perform system regression testing in the C-5 SIL as a risk reduction exercise. The C-5 SIL will perform testing and provide a test report outlining the tests performed and any anomalies that occurred. The contractor is invited to the test event, if desired. 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 Engineering Test Builds (ETBs).

Periodic releases of ETBs, QT builds, and FQT entry builds 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. The Government reserves the right to witness all testing at all contractor facilities used in the development of the product.

DI-MGMT-81453B Data Accession List

DI-IPSC-81488/T Computer Software Product (Source Code)

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

DI-MCCR-80700/T Computer Software Product End Items (SW Licenses)

DI-MCCR-80700/T Computer Software Product End Items (Toolsets)

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.

3.4.2.3 Sub-Contractor Communication

The Contractor shall support the Government on software development efforts with sub-contractors that provide documentation and source code changes for the mission processing system (VIA/AIU). The Government tasks Honeywell International using a separate, stand-alone contract for Honeywell-specific software. It is expected that some changes to be

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information incorporated by Honeywell may have been prototyped using the direct contract between the Government and Honeywell. The Government directed Honeywell software changes will be considered as prototype software to be incorporated and integrated as part of the LM Aero to Honeywell subcontract. The Contractor shall subcontract directly with Honeywell to implement changes in Honeywell-owned software as required by the Government prioritized backlog. The subcontracted effort to Honeywell will include all requirements, development, integration and test activity required to field the changes. The Contractor shall obtain all the necessary documentation to support the changes directly from the subcontractor.

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

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information 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 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.

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.

DI-IPSC-81488/T Computer Software Product (Source Code)

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

DI-MCCR-80700/T Computer Software Product End Item (Software Licenses)

DI-MCCR-80700/T Computer Software Product End Item (Software Toolsets and Associated Documentation)

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 Contractor’s test venue using contractor and Government personnel. 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. The Contractor shall allow time to perform a system regression test using the Government SIL at Robins AFB prior to the Configuration Test Board (CTB). The regression test at the Government SIL will be entry criteria to the CTB. This requirement is to provide risk reduction prior to on-aircraft testing.

DI-IPSC-81440A Software Test Report

DI-IPSC-81438A Software Test Plan

DI-IPSC-81439A Software Test Description

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.

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.

DI-MGMT-81453B Data Accession List

Technical Manual Contracts Requirement, ref. TMCR 86-0P

DI-SESS-81000F/T Drawings and Associated Lists

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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 aircraft configurations for which the Contractor has technical cognizance. The Government will provide the latest configuration information, i.e. TDP and TOs, to the contractor. 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.

Government Property to be Provided: The Government will provide Government Furnished Property (GFP). The GFP list will be developed/produced by the Government with the aid of the contractor 30 days after contract award and made part of the contract via modification. The Contractor shall manage all Government Property in accordance with FAR 52.245-1, FAR Part 45 and DFARS Part 245 as supplemented. The Contractor shall provide necessary Product Quality Deficiency Report (PQDR) information for deficient Government Furnished Equipment (GFE) / Government Furnished Property (GFP) in accordance with TO 00- 35D-54. CDRL Reference in Appendix C DI-QCIC- 80736, Quality Deficiency Report; DI- QCIC- 80736, Quality Deficiency Report; and DI-MGMT-80441D, Government Property (GP) Inventory Report – Reporting of Government Furnished Property.

DI-MGMT-80368A/T Status Report

DI-MGMT-80259/T Physical Inventories Report

DI- QCIC-80736 Quality Deficiency Report

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information

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:

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

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.

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.

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.

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.

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.

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):

Lockheed Martin Proprietary Information

Lockheed Martin Proprietary Information o CAT I: 20 clock hours o CAT II: 7 calendar days

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:

o CAT I: 45 calendar days o 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.

To support the development of Honeywell Product Line Improvements for future consideration in the formal software development and release contract defined herein, the Contractor shall provide engineering and programmatic support on software deficiency description tasks, status meetings, documentation reviews and software test requirements for FMS and AFCS to the Government. The Contractor will be provided information by the Government to support the task descriptions, documentation reviews and meetings.

The Contractor shall provide technical and programmatic advisement to the Government to support software delivery to the fleet using agile framework methodologies. The Contractor shall provide a status report and recommendations to the Government on fielding software items as well as providing the required documentation for completing airworthiness of the software changes.

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.