Revised 24-31731 HSES PWS Contract Final 6-9-25.docx

PERFORMANCE WORK STATEMENT FOR

C-5M SUPER GALAXY

HONEYWELL SOFTWARE AND ENGINEERING SUPPORT (HSES) PROGRAM

Purchase Request: FD2060-24-31731

Air Force Life Cycle Management Center/ C-5M Super Galaxy Division System Program Office (SPO) (AFLCMC/WLS) XX27 February 2025

CUI

CUI

Record of Changes

TABLE OF CONTENTS

4.10 4.11

TECHNICAL DATA AND COMPUTER SOFTWARE

PROCEDURES AND CONTROLS

GENERAL INFORMATION 496

APPENDIX E: C-5M TEMPLATE FOR MAINTENANCE AND FLIGHT CREW

1. DESCRIPTION OF SERVICES

This Performance-based Work Statement (PWS) outlines the tasks and duties required of Honeywell in the sustainment of software for the C-5M model. The Contractor shall develop multiple fully tested C-5M compatible aircraft Operational Flight Programs (OFPs) and/or related software support applications in partnership with the Government and the aircraft intergrader. The Contractor activities shall include but are not limited to, specification/analysis, engineering development, engineering studies/analyses, software design, associated testing, Technical Data Package (TDP) updates, support of airworthiness and Communication, Navigation, Surveillance/Air Traffic Management (CNS/ATM) certifications, collecting of data to support the Joint Interoperability Test Certification (JITC), and Technical Order (TO) updates associated with software maintenance and sustainment.

The Contractor shall plan to provide emergency software corrections, and to investigate and resolve on-aircraft software issues as they arise. The Contractor shall maintain the capability to quickly respond to a Government requirement to accomplish an Emergency Software Update (ESU). The Contractor shall develop a comprehensive plan identifying all resources needed to accomplish ESU corrections providing a safe reliable resolution to a deficiency.

The Contractor shall perform sustaining engineering tasks and accomplish special engineering studies and analysis of service-revealed deficiencies, software deficiencies, obsolescence issues, and enhancements as directed by the Government. In the special engineering and analysis reports, the Contractor shall provide recommendations that fully resolve any Deficiency Reports (DRs) in the most cost-effective means. The Government reserves the right to determine how these efforts shall be accomplished for C-5M.

The Contractor shall provide support to the Government System Integration Laboratory (SIL) located at Robins Air Logistics Center (ALC) along with any updates or maintenance of contractor SILs to include addressing obsolescence. The Contractor shall maintain all C-5M configurations of the contractor's SIL including updates to support efforts contained in this PWS.

1.1. Objectives: This PWS describes the services required to provide multiple fully-tested C-5M compatible aircraft OFPs, related software support applications, sustaining engineering activities, and SIL maintenance. These services include engineering investigations, specification/analysis, engineering development, software design, associated testing, TDP updates, support of aircraft certifications, support of the Government SIL, support/maintenance of contractor SILs, collection of data to support certification/compliance criteria, and TO updates.

The general requirements to achieve the contract/task order objectives are described throughout this PWS. The Contractor shall maintain the capability to support all efforts outlined in the PWS. The Contractor shall ensure software updates, fixes, and corrections are provided to the United States Air Force (USAF) within a reasonable time period as directed by the Government. It is the Government’s intent to manage OFP updates so as to achieve eighteen-to-twenty-four-month product cycles. The Contractor shall flow down all requirements stated in this PWS to any subcontractor(s) as required.

1.2. Benefit to the United States Air Force (USAF):

This acquisition will benefit the USAF by providing a means to investigate/resolve aircraft deficiencies, service-revealed deficiencies, obsolescence, and maintain the C-5M software configurations, thereby allowing the C-5M fleet to maintain its readiness and availability in support of the AF Mission (…fly, fight, and win…in air, space, and cyberspace).

1.3. Background

It is the intent of the Government to allocate a portion of the system integration activities previous performed by the OEM to the Government. Therefore, the Government is seeking to establish a direct contractual relationship with Honeywell in place of what has historically been a sub-contractual relationship through the OEM. Establishing a direct relationship with Honeywell to address the tasks listed in this PWS will bring the required expertise and capability for the Honeywell developed/sustained portions of the C-5M to the Government SIL.

2. SERVICES SUMMARY

Reference Performance Threshold

4.12.1

For performing investigations successfully identify root cause in accordance with TO 00-35D-54. Performance metrics will only apply to first three (3) DRs processed in each calendar month.

The government will provide DR investigations from JDRS via email to the Contractor. The Contractor will provide initial response to DR investigations within the following time periods after the Contractor is assigned DR and is notified (e.g. email, telephone):

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

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

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

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

4.7.15, 4.13.2, 4.13.3 For each task order, DO-178B Criticality Levels A through E Computer Software Configuration Items (CSCIs) shall complete all Requirements-based Testing (RBT) of the Formal Qualification Test (FQT) at a pass rate of 98% or higher. Any Legacy test script failures that the Contractor has not been tasked to update prior to this Contract are not part of this metric. Regression Testing shall pass at a rate of 100% with the exception of any regression tests with existing IPRs prior to this Contract. Structural coverage capability shall be 100% coverage.

4.7.2.2

. Processor throughput usage for the final build shall not increase by more than 5%. Processor throughput for any final build shall not exceed 85% with an objective of 80% at the processing frame level. The Government will provide direction as to which OFPs require optimization should threshold be exceeded.

more than 5%. 1553 Bus Utilization shall not exceed 85%. The government will provide assistance to measure 1553 Bus Utilization at the aircraft level.

4.5.4, 4.6.4, 4.13.2, 4.13.3 Ensure test venues and software are maintained and configured to support all fielded C-5M aircraft.

The Contractor shall provide an S/SEE that is available on-demand to support 120 hours of operation per thirty (30) day calendar period toperiod to meet requirements of this PWS.

4.5.4, 4.13.2, 4.13.3 The differences between all Contractor’s SILs at all locations shall be no more than 10% for each of the following categories:

· Scripts used to compile, link, and build environments

· Hardware components

· Software tools

· FQT software

3. GOVERNMENT PROPERTY

3.1. Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2. Government Property to be Provided: Government property to be provided includes items included in Appendix B, Government- Furnished Property. Other property provided includes items considered consumable for maintenance of the SIL such as but not limited to bolts, nuts, screws, etc.

The Government will provide access to C-5M aircraft, as required and if available, for the Contractor to accomplish sustaining engineering or software sustainment activities. The Contractor shall plan to accomplish any required aircraft ground integration testing for software in no more than two events for each task order unless specifically approved by the Government. The Contractor shall plan to accomplish the majority of engineering or software testing using the SIL and other venues and shall only accomplish aircraft testing as directed by the Government.

The Government will provide access to components/systems, as required, for Contractor to maintain the SILs. The differences between all Contractor’s SILs at all locations shall be no more than 10%.

At the end of each work period, Contractor personnel shall ensure all equipment and materials provided for their use are secure. A report identifying location, use, and status of all Government property assigned to the Contractor for the tasks associated with this PWS shall be provided yearly. CDRL Reference in paragraph 4.2, DI-MGMT-80441C, Government Property (GP) Inventory Report – Reporting of Government Furnished Property and DI-MGMT-80368A/T, Status Report

3.3. Base Support: The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies. The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed.

3.4. Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5. Loss of Government Property:

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

3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil.

3.6 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt. All Honeywell Intellectual property may be marked as appropriate.

4. TECHNICAL REQUIREMENTS

4.1 PERIOD AND PLACE OF PERFORMANCE

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend 12 months with 5 one year options.

4.1.2 Place of Performance: These services shall be performed at the Government SIL and/or the Contractor’s C-5M software development/test facilities and any C-5M permanent base. Engineering investigations and testing will take place as required at Government and Contractor facilities. Travel to C-5M operating locations will be coordinated with the Government program manager as required.

4.2 CONTRACT DATE REQUIREMENTS LIST(s) (CDRL)

Requirements ReportReserve 1.0

Report 3.2

Structure 4.4.2

4.3.2, 4.3.4, 4.4.4, 4.6.6, 4.7.2.1, 4.7.6, 4.7.18, 5.7.1

Associated Lists 4.5.3, 4.6.2, 4.11.2, 4.13.2, 4.13.3

Maintainer 4.5.3, 4.7.2.2, 4.13.32

4.13.2, 4.13.3

DI-MISC-80711A

Scientific and Technical Reports 4.4.3, 4.4.6, 4.5.3, 4.5.5, 4.5.6, 4.7.2.2, 4.7.3.1, 4.7.7, 4.7.8, 4.7.10, 4.12.1, 4.13.2, 4.13.3, 5.2 4.4.4, 4.4.8, 4.5.3, 4.6.5, 4.7.2.2, 4.7.3.1, 4.7.7, 4.7.9, 4.7.11, 4.13.2, 4.13.3, 4.13.4, 4.13.3, 4.13.6

Plan 4.5.3, 4.7.3.1, 4.7.8, 4.13.2, 4.13.3

Report 4.5.3, 4.7.3.1, 4.7.8, 4.13.2, 4.13.3

Description 4.5.3, 4.13.2, 4.13.3

Language (VHDL) Documentation 4.5.3, 4.7.3.1, 4.13.2, 4.13.3

Study/Service 4.3.2.1, 4.5.3, 4.13.2, 4.13.3

Strength Analysis Report 4.3.2.1, 4.5.3, 4.13.2, 4.13.3

Effects (E3) Integration and Analysis Report (E3IAR) 4.5.3, 4.13.2, 4.13.3

Criteria Report 4.5.3, 4.7.9, 4.13.2, 4.13.3

Approach Document – Operator 4.5.3, 4.7.2.2, 4.13.2, 4.13.3

Item – Compiled Loadable Image 4.5.3, 4.6.56, 4.7.3.1, 4.7.3.5, 4.13.2, 4.13.3

Source Code 4.5.3, 4.6.56, 4.7.3.1, 4.7.3.2, 4.7.3.3, 4.13.2, 4.13.3

Items – Software License 4.5.3, 4.6.56, 4.7.3.1, 4.13.3

Items – Software Toolsets and Associated Documentation 4.5.3, 4.6.65, 4.7.3.1, 4.13.3

Plan and Procedures 4.5.3, 4.13.2, 4.13.3

Test Procedure (EMITP) 4.5.3, 4.13.2, 4.13.3

Test Report (EMITR) 4.5.3, 4.13.2, 4.13.3

DI-NDTI-80809B/T

Test/Inspection Report 4.5.3, 4.5.4, 4.7.3.2, 4.7.3.3, 4.7.3.4, 4.7.3.5, 4.13.2, 4.13.3

Sheets – Development 4.4.87, 4.5.3, 4.5.4, 4.7.3.1, 4.7.3.2, 4.7.3.4, 4.7.3.5, 4.13.3

4.2.1 Quality of CDRL Deliverable There shall be no more than one rejection of any individual deliverable. There shall be no more than one total rejection(s) of an individual deliverable per quarter. The Government will reject a deliverable if one or more major technical errors or three or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The CDRLs shall be delivered in the Government MEARS system.

4.2.2 Timeliness of CDRL Deliverable

The Contractor shall notify the Government when delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. There shall be no more than one late submission of deliverables per quarter. The Contractor shall deliver the revised data/document by the revised delivery date acceptable to the Government. The Government will approve or reject the data/document within 45 calendar days from the Contractor delivery date. If the Government does not approve or reject the data/document within 45 calendar days from the Contractor delivery date, the Contractor can assume the Government approved the data/document and the Contractor can mark the data/document “approved.”The contractor shall notify the Government when delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. They shall be no more than one late submission of deliverables per quarter. The data/document shall be delivered by the revised delivery date acceptable to the Government. The government shall approve or reject the data/document within 45 days of delivery date or the data/document can be marked approved by the contractor.

4.2.3 Data Assccession List

The Contractor shall maintain a single Data Accession List (DAL) for the contract and the associated task orders. 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 not to exceed two deliveries per period of performance. Reference in paragraph 4.2, DI-MGMT-81453A, Data Accession List

4.3 Contract Program Management

4.3 RMCD Design and Integration into C-5M Configuration

4.3.1. Contractor Program Manager: The Contractor shall provide a Program Manager (PM) who has the authority and the necessary staff to accomplish the tasks required by the C-5 HSES contract.

The PM shall be the Contractor’s single point-of contact to the Government on all program/operational issues. Responsibilities of the PM shall include, but not be limited to:

· Schedule and support customer Program Management Review (PMR) meetings.

· Coordinate program requirements and information with the customer, and other Government representatives as directed by the customer.

· Ensure timely resolution of business and technical problems.

· Implement corrective action in accordance with the terms and conditions of the contract.

· Report against mutually agreed to performance measurements (metrics).

4.3.2. Integrated Program Management (IPM): The Contractor shall track the project including notification of any schedule changes. The Contractor shall notify the Government of any possible financial or technical changes that may impact the planned completion per the schedule and cost information.

The Contractor shall establish and maintain standard program plans and controls. The Contractor shall develop and maintain a risk management plan to identify and provide resolution to any risks in a timely manner. The risk register, opportunity and mitigation plan shall include impacts to concurrent running programs and be updated once per month. The risk management status shall either be integrated or be an attachment to the Monthly Status Report (MSR).

The Contractor shall plan and conduct a PMR. The Contractor shall hold a PMR once every six months via video teleconference or at a location to be determined by the Government. PMRs will be approximately one day in length. Upon receipt of an approved agenda, PMR slides shall be provided in draft form 24 hour in advance of the meeting. Meeting minutes shall be generated and delivered by the Contractor.

The Contractor may request to revise the PMR schedule or to not conduct a particular PMR. The Government will only consider requests if a particular task order is more than 10% under the baseline planned budget and schedule.

The Contractor shall coordinate tasks associated with each task order with other projects accomplished by the Contractor and shall make every effort to ensure there are no resource conflicts impacting the contract/task order(s). CDRL Reference in paragraph 4.2, DI-ADMN-81505/T, Conference Minutes; DI-MGMT-80368A/T, Status Report; DI-ADMN-81249B/T Conference Agenda

4.3.3 Integrated Master Schedule (IMS): The Contractor shall develop and maintain a logical, networking–detailed program activities IMS for each task order and shall establish a Government-approved schedule baseline within 90 calendar days after contract/task order award. A maximum of two (2) formal schedule re-baselines shall be permitted over the course of each software update unless agreed by the Government. The IMS shall show deviations from the baseline plan as well as the critical path(s). The Contractor shall submit a request to the Government to combine task orders into a common IMS for two or more tasks. The IMS shall show deviations from the baseline plan. If the IMS requires a new baseline, due to significant variance over the course of the task order, the Contractor shall notify the Government PM prior to re-baselining the IMS. The IMS shall be re-baselined only with Government approval via the PCO.. The schedule shall contain the specific activities and milestones, accomplishments, exit criteria, and activities associated with contract/task order events from contract/task order award to the completion of the contract/task order. All key supplier activities and milestones shall also be included in the IMS including USAF provided schedules for associated teams (i.e., test communities, partnership activities). The IMS shall show interrelationships and dependencies of schedule elements along with the critical path of the program. At a minimum, the critical path of the IMS shall be updated for each monthly reporting period. CDRL Reference in paragraph 4.2, DI-MGMT-81861B/T, Integrated Program Management Report – Integrated Master Schedule

4.3.4 Contractor/Task Order Kick-Off: The Contractor shall conduct detailed activity planning for each task order under this contract. The Contractor shall conduct a contract/task order kick-off meeting NLT 20 business days after contract/task order award or other mutually agreed upon date and delivery for the Kick-Off meeting. The Contractor shall address cost planning, project schedule, planned development activities, planned test activities, test venues, and risk management for each contracted activity at the contract/task order kick-off meeting. CDRL Reference in paragraph 4.2, DI-ADMN-81505/T, Conference Minutes and DI-ADMN-81249B/T, Conference Agenda

4.4 Software Update Task Orders

4.4.1 Contractor Integrated Performance Management: Software maintenance task orders under this PWS shall be treated as stand-alone contracts. The Contractor shall utilize its existing internal performance management system to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status applicable to each task order under this contract. The Contractor’s internal performance management system shall serve as the single, formal, integrated system meeting both the Contractor’s internal management requirements and the requirements of the Government for timely, reliable, and auditable performance information. The application of these concepts shall provide an early indication of contract/task order cost, schedule, and technical challenges. The outputs of this system shall be used as the basis to report detailed performance status during PMRs and other status meetings. The Contractor’s system shall satisfy the industry guidelines delineated in the general provisions of the contract/task order, and this PWS.

The IMS, shall be developed, maintained, updated, and reported monthly per CDRL requirements. The application of these concepts shall provide for early indications of contract/task order schedule problems. For task orders under this contract, the above requirements shall apply. CDRL Reference in paragraph 4.2; DI-MGMT-81861B/T, Integrated Program Management Report – Integrated Master Schedule.

4.4.2 Contractor Work Breakdown Structure (CWBS): The Contractor shall develop and maintain the CWBS and CWBS dictionary. The Contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, for Government visibility. The Contractor shall use the CWBS as the primary framework for contract/task order planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements and system specification and translate them into a structure representing the products and services comprising the entire work effort. The Contractor shall prepare the technical elements of the extended CWBS. The Contractor, if necessary, shall update the CWBS during the execution of the contract/task order. CDRL Reference in paragraph 4.2, DI-MGMT-81334D, Contract Work Breakdown Structure

4.4.3 Integrated Baseline Review (IBRs): The IBR shall focus on the realism of the Contractor’s integrated Performance Measurement Baseline (PMB) and the appropriateness of the earned value methodology to be employed. The Contractor shall complete the initial baseline and host an IBR NLT 90 calendar days after award of each task order. Incremental IBRs shall be conducted, as needed, throughout the life of the contract/task order, if required, following major changes (i.e. 10%) to the baseline. The Government will verify during the IBR, and follow-on IBRs if required, that the Contractor has established and maintains a reliable PMB. The Contractor shall ensure the baseline includes the entire contract technical scope of work consistent with contract/task order schedule requirements and has adequate resources assigned. The Contractor shall ensure the Government-effective earned value methods are used to provide accurate status of contract/task order cost, schedule, and technical performance. The IBR will be used to achieve a mutual understanding of the baseline plan, cost and schedule risk, and the underlying management processes used for planning and controlling the program. Participation in the IBR will be a joint responsibility of both the Government PM and the Contractor. An conference agenda and meeting minutes shall be created and delivered by the Contractor. CDRL Reference in paragraph 4.2, DI-MGMT-81505/T, Conference Minutes and DI-ADMN-81249B/T, Conference Agenda

4.4.43 Joint Review: The Contractor shall conduct all joint reviews with the Government (including joint reviews with subcontractors) in person at Robins AFB, GA or at the Honeywell facilities in Deer Valley, AZ or Aguadilla, Puerto Rico, or via video teleconference. The Government will select the in-person location or whether the review will be conducted via video teleconference. For each joint review, the Contractor shall deliver an agenda. The Contractor shall plan to accomplish all joint reviews (including joint reviews with subcontractors) on Robins AFB, GA or the Honeywell facilities in Deer Valley, AZ and Aguadilla, PR or via video teleconference. For each joint review, the Contractor shall deliver an agenda.

The joint reviews shall be as requiredinclude the following:

· System Requirements Review (SRR)

· Flight Station Working Group (FSWG)

· Certification Working Group (CERTWG)

· Software Requirements Analysis Review (SRAR)/Preliminary Design Review (PDR)

· Critical Design Review (CDR)/ Technical Order Guidance Conference (TOGC)

· Verification Review Council (VRC)

· Test Readiness Review (TRR)

· Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA)

For the applicable reviews the Contractor shall deliver a design review information package, Design Review Information Package (DRIP). Reviews listed in Appendix D shall use the established Entrance/Exit criteria listed in Appendix D. The Contractor shall perform a detailed joint SRR with the Government. Testing venues and methods of testing shall also be a part of this event.

The Contractor, as required, shall conduct FSWG meetings early in any software update task order schedule to validate user interface requirements. The Government will select the in-person location or whether the review will be conducted via video teleconference. The Contractor shall ensure all FSWG collected requirements are fully known and included in the final design presented to the Government as part of the CDR. As necessary, the Contractor shall update the Human Engineering Design Approach Document-Operator Document and the Human Engineering Design Approach Document-Maintenance. For changes involving the Primary Flight Display (PFD), the contractor shall provide any necessary documentation and support to aid the Government in obtaining approval and certification from the Air Force Safety Office for the PFD change. The Contractor shall accomplish a TRR to ensure joint understanding of Government requirements, reduce design rework, and reduce the number of code-test-code steps.

The Contractor shall hold a combined SRAR/ PDR including assessment of changes to the requirements. The Government will select the in-person location or whether the review will be conducted via video teleconference. The Government approved entrance and exit criteria for the SRAR and PDR shall be included as part of this event. The Contractor shall provide, as part of the PDR, a PowerPoint presentation (i.e./e, first draft) describing each problem report (e.g., DR, FMS PLIs, etc.) and the solution to correct the problem. In addition, the Contractor shall include in the SRAR/PDR shall include a review of baseline processor throughput, bus utilization, and memory usage for the proposed changes. The Contractor shall also identify Oopportunities for source code optimization shall also be identified.

The Contractor shall perform a CDR, which shall contain the Government approved entrance and exit criteria accomplished in a CDR, with the goal of accomplishing the detailed design review in no more than three business days. A TOGC shall also be held within 60 calendar days after contract award to ensure personnel developing the TO changes gain the benefit of hearing the design requirements and can assess impacts of design changes from the proposal phase of the contract/task order. The Government will select the in-person location or whether the review will be conducted via video teleconference. The Contractor shall consider Government inputs from working groups (e.g., Flight Station, TO, etc.) leading up to the CDR. This recommendation shall be documented as a report and included as part of the minutes for the CDR. The Contractor shall provide, as part of the CDR, a PowerPoint presentation (i.e./e, first draft) describing each problem report (e.g., DR, FMS PLIs, etc.) and the solution to correct the problem. The PowerPoint presentation shall include a list of TO changes and other related information. The Government reserves the right to postpone any review if the draft and final documentation packages are not received within the time limitations noted on the CDRLs or in this paragraph.

The Contractor shall perform a VRC, which shall contain the Government approved entrance and exit criteria accomplished in a VRC. The Contractor shall organize the software update tasks so all VRC efforts are completed with no more than two meetings. Testing venues and methods of testing shall be captured in a PowerPoint presentation as part of the VRC. Processor throughput usage for the final build shall not increase by more than 5%. Processor throughput for any final build shall not exceed 85% with an objective of 80% at the processing frame level. The Government will provide direction as to which OFPs require optimization should threshold be exceeded

The Contractor shall accomplish a TRR to ensure joint understanding of Government requirements, reduce design rework, and reduce the number of code-test-code steps.

Reference in paragraph 4.2, DI-ADMIN-81505/T, Conference Minutes; DI-ADMN-81249B/T, Conference Agenda; DI-SESS-81757A/T, Design Review Information Package (DRIP); and DI-MISC-80711A, Scientific and Technical Reports

4.4.54 C-5 Configuration Control Board (CCB): The Contractor shall support the Government CCB reviews required for the implementation and testing of the elements of this PWS. Support shall include attending the CCB in person or by phone, providing task order documentation, and testing instrumentation documentation as required.

4.4.65 Independent Verification & Validation (IV&V): The Contractor shall support, in the Contractor’s or Government facilities, the IV&V of any conceptual engineering solutions or software products they may develop or test. This shall also include supporting software products (e.g. simulations, models, development environments, etc.) 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) Interface Control Document (ICD). Reference in paragraph 4.2, DI-SESS-81248B/T, Interface Control Document (ICD)

4.4.76 Testing with other Agencies: The Contractor shall support formal qualification, integration, regression, ground and flight tests with the applicable agency in accordance with the task order to ensure the software changes made as part of the task order do not have a negative impact on the current capability. A full dry-run integration/regression tests of the task order software changes shall be performed in the Government SIL to support independent verification/validation activities. This may create the need to update regression test procedures and scripts. All test procedures and scripts shall be delivered to the Government with appropriate rights and licensing. The Contractor shall document and deliver the efforts noted in this paragraph in a separate technical report. Reference in paragraph 4.2, DI-MISC-80711A, Scientific and Technical Reports; DI-IPSC-81488/T, Computer Software Product – General Test Scripts; DI-QCIC-81536/T, Integration Test Information Sheets – Regression and DI-QCIC-81536, Verification Test Information Sheets

4.5 Engineering Studies and Analyses

4.5.1 Studies and Analyses: The Contractor shall provide engineering studies and analyses in support of service-revealed deficiencies and C-5M software activities as required by task orders issued under this contract. The Contractor shall flow all requirements stated in this section to subcontractors as applicable. The Contractor shall establish Associate Contractor Agreements (ACAs) with necessary contractors as required for transfer of information necessary to complete studies and analysis task.

4.5.2 Special Studies and Analyses: The Contractor shall perform special studies and analyses that are not defined in depth in the current PWS but fall within the general scope of the C-5M engineering and software sustainment activities. The Contractor shall conduct these special studies and analyses, if requested and authorized by the PCO. The Contractor shall include, but not limited to, the following in the special studies and analyses. is include but are not limited to:

a. Budgetary costs estimate in support of Government contract/task order planning

b. Analysis of impacts to changes to program requirements that affect program budget, schedule, and/or content

c. Cost reduction initiatives

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

e. Investigation and resolution of service-revealed deficiencies

f. Investigation of and potential solutions to update or replace items affected by obsolescence in 10-year rolling period beginning at the review date (e.g. aircraft components, support equipment, SIL items)

g. Analysis of alternatives in support of future task orders

The Official Backlog List 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 finding, i.e. Integration Problem Report (IPR), that the Government has reviewed and agrees to track as an unresolved deficiency against the software. 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 the status of corrective action.

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

4.5.3 Proof of Concept Engineering: A request for proof-of-concept engineering will normally follow an analytical engineering effort that has pinpointed the cause of deficiencies or problems and determined the course of engineering action necessary to design and develop corrective changes or improvements. The Contractor shall perform proof of concept engineering services in SIL testing and Cockpit SIL testing to design, modify subsystems/software, and test proposed solutions to address operational capability requirements and/or deficiencies as authorized by task orders. The Contractor shall submit, in a technical report, a plan for accomplishing the proof-of-concept effort and document design, cost, hardware, software code activities, and technical data applicable to the proof of concept. Work requirements shall include, but may not be limited to:

a. Reviewing data generated during investigation and confirming initial design proposal

b. Identifying proof of concept hardware and software code requirements

c. Identifying and documenting detailed design

d. Conducting system and aircraft testing in Cockpit SIL

e. Preparing Engineering Change Proposal (ECP) and applicable engineering drawing changes

The Contractor shall also, at the PCO’s direction, provide recommendations for proof of concept engineering to the PCO and/or Government PM.

Deliverables will be identified for the specific task order and will include all or a subset of the following: Reference in paragraph 4.2, DI-SESS-80639D/T, Engineering Change Proposal; TM-86-01P, Technical Manual Contract Requirement; DI-SESS-81000E/T, Product Drawings/Models and Associated Lists; DI-IPSC-81441A/T, Software Product Specification; DI-IPSC-81433A/T, Software Requirements Specification (SRS); DI-IPSC-81434A/T, Interface Requirements Specification (IRS); DI-SESS-81248B/T, Interface Control Document (ICD); DI-SAFT-80101C, System Safety Hazard Analysis Report; DI-IPSC-81427A, Software Development Plan; DI-SESS-81768, Airworthiness Certification Criteria Report; DI-SESS-81766, Airworthiness Specification; DI-HFAC-80746C/T, Human Engineering Design Approach Document – Operator; DI-HFAC-80747C/T, Human Engineering Design Approach Document – Maintainer; DI-SESS-81757A/T, Design Review Information Package (DRIP); DI-IPSC-81442A, Software Version Description; DI-MISC-80711A, Scientific and Technical Reports; DI-MGMT-81844/T, Information Assurance (IA) Test Plan; DI-MGMT-81843/T, Information Assurance (IA) Test Report; DI-SDMP-81465A/T, Performance Specification – Air Vehicle Specification; DI-IPSC-81431A/T, System/Subsystem Specification; DI-IPSC-81432A/T, System/Subsystem Design Description; DI-IPSC-81435A, Software Design Document; DI-SDMP-81465A/T, Performance Specification – Weapon System Specification; DI-EDRS-81729, VHSIC Hardware…