Solicitation Attach - P8A OFT Projection DRAFT SOW_08APR2026.docx

XX XXX 2026

STATEMENT OF WORK

FOR

P-8A Operational Flight Trainer (OFT) Projection System Upgrade

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICE PMA290, PMA205

NAVAL AIR SYSTEMS COMMAND

PATUXENT RIVER, MD 20670

Controlled by: Department of the Navy Controlled by: Naval Air Warfare Center Training Systems Division (NAWCTSD) CUI Category: CTI, EXPT Distribution/Dissemination Control: D POC: [IPTL name, phone number, email] Program Office – PMA 290, PMA205 (or Designated Representative)

DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD Contractors only for CTI and export controlled 29 August 2025. Other requests for this document shall be referred to Commanding Officer, Naval Air Systems Command, (PMA290), 47123 Buse Road, Patuxent River, MD 20670 .

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Control Reform Act of 2018 (Title 50, U.S.C., Chapter 58, Sec. 4801-4852). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

DESTRUCTION NOTICE - For unclassified, limited distribution documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

CUI

SOW 260086

Revision – XX XXX 2026

21 December 2015 Table of Contents Section Title Page

CUI

CUI

List of Tables:

Statement of Work P-8A Operational Flight Trainer (OFT) Projection System Upgrade

SCOPE

This Statement of Work (SOW) establishes the contractor tasks for the modifications of the P-8A Aircrew Training Device (ATD) - Operational Flight Trainer (OFT) Projection System located at Jacksonville, FL Integrated Training Center (ITC); Whidbey Island, WA Fleet Training Center (FTC); and Royal Australia Air Force (RAAF) Base Edinburgh, SA ITC.

NAS JAX Devices Table 1. NAS JAX ATD

NAS WHI Devices Table 2. NAS WHI ATD

RAAF Base Edinburgh Table 3. RAAF ATD

APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

Government Documents

SPECIFICATIONS:

STANDARD PRACTICES:

Copies of the above handbooks are available at https://www.usace.army.mil/Missions/Safety-and-Occupational-Health/Safety-and-Health-Requirements-Manual/

Copies of the above handbooks are available https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204783

Copies of latest version these document are available from http://www.nfpa.org/Catalog/ or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322

OTHER PUBLICATIONS:

(Occupational Safety and Health Administration (OSHA) regulations are downloadable from https://www.osha.gov/law-regs.html)

Non-classified, OFFICIAL: Sensitive and PROTECTED cables are coloured neither salmon pink nor red.

Control: ISM-1718; Revision: 1; Updated: Mar-23; Applicable: S; Essential 8: N/A SECRET cables are coloured salmon pink.

Control: ISM-1719; Revision: 1; Updated: Mar-23; Applicable: TS; Essential 8: N/A TOP SECRET cables are coloured red.

Copy of the above references are available at https://www.cyber.gov.au/sites/default/files/2025-12/Information%20security%20manual%20%28December%202025%29.pdf

DFARS Clauses are downloadable from http://farsite.hill.af.mil/vfdfara.htm

Copy of the above Instructions are available from https://www.esd.whs.mil/

Copy of the above Instruction is available from https://www.cnss.gov/CNSS

NIST SP 800-53 Rev 5

Security and Privacy bookmark://acronym/Controls for Information Systems and Organizations, dated September, 2020

Copy of the above Instructions are available from https://csrc.nist.gov

Naval Aviation Training Systems Program Office (PMA205)

REQUIREMENTS

General Program Management The Contractor shall

a. organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services;

b. provide the necessary program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this SOW for the P-8A ATD - OFT Projection System listed in section 1.

Work Planning and Scheduling The Contractor shall

a. develop maintain an Integrated Schedule that presents the Contractor’s plans and schedules to meet the requirements of the contract showing all program milestones events, reviews, data submittals, and deliveries P-8A ATD - OFT Projection System;

b. prepare the Contractor’s Progress and Status Report in accordance with (IAW) CDRL BA02.

Program Planning The Contractor shall define, document, manage, and apply program planning processes in accordance with the P-8A System Engineering Plan (SEP) version 1.0.

Management and Technical Integrated Product Teams (IPTs) The Contractor shall

a. participate in the following IPTs throughout the project lifecycle:

· Management/ Technical IPT (biweekly);

· Technical Working Group (biweekly) focus on technical design, systems integration, planning and executing PMI, and tests to verify and validate system performance and compliance with requirements;

b. include both contractor and subcontractor personnel with expertise across functional areas relevant to the respective IPT’s objectives;

c. operate in a collaborative environment where communication, information sharing, and decision-making are transparent and inclusive.

Risk Management The Contractor shall

a. conduct risk management to systematically control the uncertainty in the project’s ability to meet cost, schedule, and performance requirements;

b. provide the Government visibility into the Contractor’s tools, assessment, mitigation, and control techniques;

c. update issues related to risk management and contractual execution to include critical path items, engineering, and logistics milestones.

Change Management The Contractor shall

a. define, document, manage, and apply a process to accomplish change management;

b. use Engineering Change Proposals (ECPs) to request changes to an approved product baseline. The Contractor shall prepare the Engineering Change Proposal (ECP) IAW the CDRL AA07.

Cyber Security The Contractor shall

a. deliver cybersecurity compliant upgraded trainer components that satisfies the DODI 8510.01 Risk Management Framework (RMF) security control set as defined in NIST SP 800-53 and for a CNSSI 1253. The Security Categorization is defined for this National Security System as (Confidentiality = Moderate), (Integrity = Moderate), (Availability = Low) within Enterprise Mission Assurance Support Service (eMASS) package #S-4811;

b. apply the cyber testing and reporting requirements to the upgraded trainer components for NAS Jacksonville and NAS Whidbey IAW CDRL AA06 and use the latest Navy Security Control Assessor (SCA) Risk Management Framework (RMF) and Risk Assessment Guide (RAG).

c. use DoD-authorized assessment tools to perform cybersecurity testing (e.g. Assured Compliance Assessment Solution (ACAS), Defense Information Systems Agency (DISA) Security Content Automation Protocol (SCAP) Tool, Evaluate STIG, STIG Viewer, HP Fortify or substitute source code scanning tool), document, verify, and validate each applicable operating system configuration;

d. develop USN A&A artifacts using the templates that are approved by the ISSO. Submit the A&A artifacts IAW CDRL AA06.

e. provide a CMMC Certificate IAW the CDRL AA06.

f. harden all cyber devices by applying all patches and closing all STIGs.

g. Provide justification for any unclosed STIG items is required if it conflicts with system functionality, mission needs, or safety. This justification shall be included in the POA&M, which must follow the guidelines of CDRL AA06 and the latest Navy Security Control Assessor (SCA) Risk Management Framework (RMF) and Risk Assessment Guide (RAG).

Vulnerability Scans The Contractor shall

a. scan the upgraded trainer components with approved vulnerability scanning tools as identified by the Designated Approval Authority (DAA)/Functional Authorizing Official (FAO), Authorizing Official (AO), or Information Systems Security Manager (ISSM);

b. update the vulnerability scanner with the latest signatures and scanning engines prior to the execution of each vulnerability scan;

c. conduct scans pre-IT-C1 on training devices used for software development with authorized scanning tool and provide results in an approved format to the ISSO IAW CDRL AA06.

d. handle the vulnerability scans in accordance with the System’s classification level.

STIGs, SRGs, SCAP Benchmarks The Contractor shall

a. Cyber harden the upgraded trainer components and provide results in an approved format to the ISSO IAW CDRL AA06.

b. Non-compliant STIG, SRG, and SCAP Benchmark findings shall be documented in the System POA&M on a hardware/software release basis IAW the CDRL AA06.

c. Implement STIGs, SRGs, and SCAP Benchmark updates into the System as they are released IAW section 3.1.2

d. provide all STIG, SRG, and SCAP Benchmark artifacts to the ISSO. The format for these artifacts must be approved by the DAA/FAO, AO, and ISSM, and must comply with the latest Navy SCA RMF and RAG. All artifacts must be handled in accordance with the system's classification level, and any non-compliant findings shall be documented in the system's POA&M..

Plan of Action and Milestones (POA&M) The Contractor shall

a. develop a POA&M using the approved DAA/FAO, AO, or ISSO format IAW CDRL AA06. The POA&M shall be considered a ‘living’ document and the Contractor shall update it as required it throughout the contract performance, until device acceptance;

b. create the POA&M with all Not Applicable Security Controls, All Non-Compliant Security Controls, and all Non-Compliant Vulnerability Findings as identified in the Vulnerability Scans, STIGs, SRGs, SCAP Benchmarks and include all required mitigation statements IAW the latest version of the Office of the Navy Security Control Assessor (SCA), Risk Management Framework (RMF), Risk Assessment Guide (RAG).

RAAF Cyber Security The Contractor shall adhere to the following cybersecurity requirements to ensure the delivery of compliant and secure trainer components.

General Requirements The Contractor shall deliver cybersecurity-compliant upgraded trainer components that satisfy the DODI 8510.01 Risk Management Framework (RMF) security control set as defined in NIST SP 800-53 and for a CNSSI 1253. The Security Categorization for this National Security System is defined as (Confidentiality = Moderate), (Integrity = Moderate), and (Availability = Low).

The Contractor shall apply the cyber testing and reporting requirements to trainer components in accordance with (IAW) CDRL AA08 and use the latest Navy Security Control Assessor (SCA) Risk Management Framework (RMF) and Risk Assessment Guide (RAG). The Contractor will use DoD-authorized assessment tools to perform cybersecurity testing, such as the Assured Compliance Assessment Solution (ACAS), Defense Information Systems Agency (DISA) Security Content Automation Protocol (SCAP) Tool, Evaluate-STIG, STIG Viewer, HP Fortify, or a substitute source code scanning tool. The Contractor shall document, verify, and validate each applicable operating system configuration.

The Contractor shall develop USN Assessment and Authorization (A&A) artifacts using templates approved by the Information Systems Security Officer (ISSO) and submit them IAW CDRL AA08. Furthermore, the Contractor shall provide a Cybersecurity Maturity Model Certification (CMMC) Certificate IAW CDRL AA08.

The Contractor is required to secure all cyber devices by applying all patches and closing all Security Technical Implementation Guides (STIGs). Justification for any unclosed STIG items is required. This justification shall be included in the Plan of Action & Milestones (POA&M), which must follow the guidelines of CDRL AA08 and the latest Navy SCA RMF and RAG.

Vulnerability Scans The Contractor shall scan trainer components with approved vulnerability scanning tools as identified by the Designated Approval Authority (DAA)/Functional Authorizing Official (FAO), Authorizing Official (AO), or Information Systems Security Manager (ISSM). The vulnerability scanner shall be updated with the latest signatures and scanning engines prior to the execution of each scan. The Contractor will conduct scans pre-IT-C1 on training devices used for software development with an authorized scanning tool and provide results in an approved format to the ISSO IAW CDRL AA08. All vulnerability scans shall be handled in accordance with the System’s classification level.

STIGs, SRGs, and SCAP Benchmarks The Contractor shall secure the upgraded trainer components and provide results in an approved format to the ISSO IAW CDRL AA08. Any non-compliant STIG, Security Requirements Guide (SRG), and SCAP Benchmark findings shall be documented in the System POA&M on a hardware/software release basis IAW CDRL AA08. The Contractor will implement STIG, SRG, and SCAP Benchmark updates into the System as they are released IAW section 3.1.2. All STIG, SRG, and SCAP Benchmark artifacts shall be provided to the ISSO. The format for these artifacts must be approved by the DAA/FAO, AO, and ISSM, and must comply with the latest Navy SCA RMF and RAG.

Plan of Action and Milestones (POA&M) The Contractor shall develop a POA&M using the approved DAA/FAO, AO, or ISSO format IAW CDRL AA08. The POA&M shall be considered a ‘living’ document, and the Contractor shall update it as required throughout the entire lifecycle of the System through to device acceptance. The POA&M will be created with all Not Applicable Security Controls, all Non-Compliant Security Controls, and all non-compliant vulnerability findings as identified in the Vulnerability Scans, STIGs, SRGs, and SCAP Benchmarks. It shall include all required mitigation statements IAW the latest version of the Department of the Navy SCA RMF and RAG.

Detailed Tasks The Contractor shall replace, deliver, and document a new projection system for the P-8A ATD OFTs, in accordance with the Performance Specification in PRF 260087 and as specified in section 1 of this SOW.

Common Baseline Updates The Contractor shall

a. replace the USN and RAAF OFT Projection System to common hardware baseline and software baseline to the maximum extent practical; without degrading the existing OFT performance and operational requirements;

b. ensure compatibility with the existing OFT interfaces, including hardware connections and software message protocols, of the current projection system;

c. procure and deliver hardware of the same form, fit and function, ensuring compatibility with cybersecurity and operational requirements, where a common hardware baseline is not practical;

d. release, integrate, install, deliver, and test P-8A country-specific updates (e.g., databases, libraries, configurations, etc.) separately, as specified in this SOW and in PRF 260087.

OFT Visual Display System (VDS) Modification The Contractor shall

a. update, integrate, test, document and deliver new Out the Window (OTW) projectors, including the removal and replacement of existing OTW projectors and associated mounting hardware with a new projection system that meets the Performance Specification for VDS in PRF 260087. All removed existing projectors and hardware shall be disposed in accordance with section 3.8.4, and 3.8.7;

b. provide an automatic-alignment system and calibration process that replaces the existing systems to support the new projection system and produces a visual display system image quality that meets the Performance Specification for VDS in PRF 260087 without manual intervention;

c. modify or replace OFT hardware, including but not limited to sensors, mounts, cables, blackout, lenses and blending mechanisms needed to deliver the new projection system that meets the Performance Specification for VDS in PRF 260087;

d. avoid structural modifications to the trainers by excluding changes to the structure holding the OTW projectors or to the external hull of the OFT trainer;

e. only have one OFT down at a time to perform this upgrade.

Pre-Modification Inspection (PMI) The contractor shall

a. lead and perform a PMI to establish and record the premodification configuration and performance of the OFT prior to Government turn over for modifications;

b. develop PMI procedures based on the baseline requirements provided by the government, including existing Aceptance Test Procedures (ATPs) and specifications, and coordinate with the Government to determine the hardware and software baseline condition;

c. execute transport delay objective tests to determine light sensor hardware condition, identify if transport delay issues are hardware or software-related, and verify the transport delay tests comply with the transport delay section of the performance specification;

d. execute motion objective tests to verify compliance with the motion section of the performance specification;

e. record and make available to the Government all of the PMI findings that could assist determining future projection system requirements such as but not limited to: software and hardware problems, anomalies, discrepancies, deficiencies, specification/performance requirements non-conformance.

Systems Engineering Processes The Contractor shall

a. derive and decompose the requirements for the OFT projection system solution;

b. transform the requirements into a product; and

c. verify and validate that the functionality of the delivered OFT projection system meets the baseline performance specification and any modification performance requirements in PRF 260087.

Requirements Analysis The Contractor shall

a. establish system requirements for the replacement of the projection system, derive and decomposed from this SOW and in the specification requirements in PRF 260087;

b. perform the system requirements analysis tasks to transform the technical requirements into a set of measurable and verifiable system requirements;

c. define the functional boundary of the system in terms of behavior;

d. define each function that the system is required to perform;

e. define contractual implementation constraints and unavoidable solution limitation;

f. analyze the interaction between systems, subsystems, and components to derive the functional requirements;

g. establish system requirements for internal and external interfaces;

h. identify and analyze the system requirements on the operating environment;

i. verify the requirements have been allocated to hardware items and software items according to the design criteria; and

j. verify the derived and decomposed requirements are testable.

Required Documentation The Contractor shall deliver the following USN and RAAF Aircrew CDRL’s to document integration of the OFT projection system by this SOW.

· Acceptance Test Procedures (ATPs) CDRL AA01

· Software Product Package (SPP) CDRL AA02

· Product Engineering Design Data and Associated Lists (PEDDAL) CDRL AA03 and the associated Option Selection Worksheet (OSW)

· Requirements Traceability Verification Matrix (RTVM) CDRL AA04

· RAAF SPP CDRL BB01

· RAAF Product Engineering Design Data and Associated Lists (PEDDAL) CDRL BB02 and the associated Option Selection Worksheet (OSW)

Traceability The Contractor shall

a. define and manage traceability between the specification requirements, product design baseline, implementation configuration items, and test procedures.

b. define and provide bi-directional traceability of requirements;

c. provide the Government access to the traceability tool and its database; and

d. prepare Requirements Traceability Verification Matrix (RTVM)in accordance with CDRL AA04.

Software Installation Software Product The Contractor shall

a. deliver all commercial software licenses, associated documentation (e.g., manuals, installation procedures), physical media, and warranty information required to meet the performance defined in this SOW and in the VDS specification requirements in PRF 260087.

b. deliver the contractor owned, P-8A source funded, non-proprietary executable code and configuration information. The contractor shall deliver contractor owned, non P-8A source funded and proprietary software as licensed binary libraries and applications.

c. deliver the commercial item software with the associated vendor manuals, documentation, physical media, warranty information, licenses, and installation procedures. The contractor shall transfer the commercial item software licenses to the Government at device acceptance. The commercial item software licenses shall be valid at the time of DD250 of the first article P-8A Training Devices (JAX, and AUS).

d. ensure the delivered materials clearly explain to end users how they can and cannot use the software, vendor manuals, physical media, documentation, and installation procedures consistent with the license rights granted under this contract. Commercial software licenses shall be transferred to the Government upon device acceptance and remain valid for five years beyond the acceptance/RFT of the first article P-8A Training Devices;

e. prepare the Software Product Package (SPP) in accordance with CDRL AA02 and BB01. The contractor shall deliver all files required to build and compile executables.

Media and Storage Devices The Contractor shall

a. provide a complete set of software media and storage devices required to perform the SPP procedures independent of software media and storage devices used by the contractor to develop, troubleshoot or operate the training system device during Government testing. The Government will retain custody and control of the media and storage devices created or used by the Government to accomplish testing;

b. provide the additional media and mass storage devices necessary for the Contractor’s internal archiving, development, testing, and other engineering and CM purposes;

c. deliver the commercial and noncommercial software, databases and the build tools required to perform the SPP procedures.

Cold Start Procedure Media The Contractor shall

a. prepare a unique set of physical media for each computational subsystem;

b. prepare the physical media required to perform each subsystem SPP procedure with labeling that:

(1) Is formatted consistently,

(2) Is permanently attached to the physical media,

(3) Includes the media’s identifying number

(4) Identifies device name,

(5) Identifies the software item name (s),

(6) Idetifies the software vendor name,

(7) Identifies the software version number,

(8) Identifies the software release date,

(9) Identifies the security classification,

(10) Identifies the Contractor’s configuration management identifier (if different than media’s identifying number),

(11) Identifies the media piece number, for multiple piece items (e.g. Disk 1 of 3, Disk 2 of 3),

(1) Includes the applicable export control marking.

Automated Processes The Contractor shall document, control, maintain, validate, and deliver all computational automated processes (e.g., scripts, batch files, job control language, kick-start, and slipstreamed media) in the same manner as software items.

Cold Start Execution The Contractor shall

a. execute and verify all SPP procedures prior to the Test Readiness Assessment (TRA);

b. provide technical support for the Government-led execution and verification of the SPP procedures prior to the Integration Test Readiness Assessment (ITRA) in JAX, the first Follow-on Articles Acceptance Test in WHI, and RAAF ITRA in EDN.

Reviews The Contractor shall

a. conduct and participate in conferences and reviews and ensure subcontractor participation as required;

b. Prepare conference agenda, presentation material, and conference minutes for required conferences and reviews, IAW the CDRL BA01;

c. Ensure presentation materials are releasable to RAAF otherwise present it in a separate forum.

Dry Run Execution The Contractor shall conduct a comprehensive Dry Run in preparation for each Technical Interchange Meeting (TIM), Test Readiness Assessment (TRA), and Integration Test Readiness Assessment (ITRA). The purpose of each Dry Run is to ensure all systems, procedures, and personnel are prepared, thereby minimizing risks and uncertainty during the formal event. Each Dry Run shall, at a minimum, consist of a full presentation of all relevant entry criteria and material content for the upcoming event.

Post Award Conference (PAC) The contractor shall conduct the PAC within 30 calendar days after contract award. The purpose of the conference shall be to establish the framework for contractor and Government interaction during the performance period of the contract. The contractor shall present and discuss:

a. Introduction and contract overview;

b. discussion and clarification of specification, SOW and CDRL requirements;

c. CDRL delivery schedule and status;

d. subcontract limitations;

e. IMS and detailed schedule with status;

f. Government Furnished Equipment/Government Furnished Information needs and status;

g. IPT structure, membership, and responsibilities;

h. action item reporting and status;

i. team contact list (names, IPT memberships, phone numbers, and email addresses);

j. risks, issues and mitigation plan;

k. logistics Overview: The Logistics Overview shall include, but not be limited to, the following elements:

(1) long lead item and spare identification and status;

(2) reliability and maintainability (R&M) engineering reporting requirements;

(3) discrepancy reporting requirements;

(4) operations and maintenance technical documentation;

(5) commercial product license rights;

(6) data rights assertions;

(7) facilities and infrastructure;

(8) maintenance planning;

(9) training;

(10) technical Manual Initial Guidance Conference TMIGC;

Prior to the PAC, establish an Integrated Development Environment (IDE) repository to serve as the central location for official CDRL deliverables, and provide the Government with access to this repository.

Post Award Conference Completion Criteria The contractor shall meet the following PAC completion criteria:

a. the contractor assigned Request for Action (RFAs) are closed or adjudicated by the Government, and

b. the program has obtained a level of risk accepted by the Government.

System Requirements Technical Interchange Meeting (TIM) The System Requirements TIM assesses the system functional requirements and ensures that the required system performance is fully decomposed and is traceable to the functional baseline in PRF 260087. At the System Requirements TIM, the Contractor shall:

a. identify, present, and discuss the project schedule, including the hardware, software development schedule, specifying major milestones, current status, and critical path;

b. provide a complete project organizational structure;

c. identify resource availability to support the schedule;

d. Identify relevant Subject Matter Experts (SMEs) to be used during development and testing;

e. show that the functional requirements are traceable to the allocated baseline and methodology;

f. show that the explicit and derived requirements are quantified and documented;

g. address the following areas:

(1) Hardware,

(2) Software,

(3) Logistics,

(4) Technical Documentation,

(5) Risk, Issue and Opportunities Management

(6) Interoperability,

(7) Environment, safety, and occupational health

(8) Configuration Management,

(9) Security and Cybersecurity

(10) Test and Evaluation

h. present the results of a comprehensive risk assessment for the production, integration, and test of the requirements in this contract;

i. ensure that the system modifications under review can proceed into the next project phase.

System Requirements TIM Entry Criteria The Contractor shall meet the following entry criteria prior to convening System Requirements TIM:

a. PAC completion criteria has been met;

b. Deliver System Requirement TIM presentation materials IAW CDRL BA01;

c. Delivery and acceptance (when applicable), in accordance with CDRL requirements, of the CDRL items scheduled to be delivered prior to the System Requirements TIM;

d. Availability RTVM showing traceability of requirements including the requirements derived from the results of the analysis performed per para. 3.3.4;

e. Project risk have been identified and mitigation plans are being executed for each risk; and

f. The functional baseline is established.

System Requirements TIM Completion Criteria The Contractor shall meet the following Systems Requirements TIM completion criteria:

a. System Requirements TIM RFAs have been resolved and closed.

b. The required technical areas have been presented.

c. The Requirements analysis traceability performed per para. 3.3.4 has been accepted by the Government.

d. Functional requirements, as disclosed, will satisfy the training objectives.

e. System functional definition and functional decomposition is detailed enough to support detailed design.

f. Processes and metrics are in place.

g. Risks are known and are manageable for implementation of the functional requirements into detailed design.

h. Program schedule is executable within the anticipated cost and technical risks.

i. Program is properly staffed

Critical Design Technical Interchange Meeting (TIM) The Contractor shall

a. conduct a Critical Design TIM. The Critical Design TIM is for the Contractor and Government to formally review the activities and work products generated by the Contractor during the performance of the trainer modification design stage in order to develop the product baseline, and to verify that the systems are ready to proceed into the hardware assembly, and integration phase;

b. present the finalized requirements traceability from the requirements to the product baseline;

c. explicit and derived requirements are quantified and documented;

d. facility and infrastructure planning;

e. The following items shall be topics of discussion and presentation at the Critical Design TIM:

(1) Modified system hardware and software design, including:

i. Computational system,

ii. HW and SW Interfaces,

iii. Network,

iv. Software tools,

v. Open architecture, including design modularity and commonality,

(2) Project status: resource availability to support the schedule, current status vs. critical path

(3) Project problem and risk areas, recommended solutions, evaluation of alternatives, and/or mitigation plan

(4) Teardown, pack, and ship criteria,

(5) Logistics design aspects and concerns,

(6) IUID marking of training device equipment and Initial Support Kit,

(7) Parts management program status,

(8) Cybersecurity,

(9) Test and Evaluation,

i. traceability from design documentation to sub-system test requirements;

ii. product baseline test procedures;

iii. defined mission validation scenarios;

iv. discrepancy reporting process;

v. discrepancy adjudication process;

(10) Safety assessment

Critical Design TIM Entry Criteria The Contractor shall meet the following entry criteria prior to convening the Critical Design TIM:

a. Deliver Critical Design TIM presentation materials IAW CDRL BA01.

b. CDRL items scheduled to be delivered prior to the Critical Design TIM have been delivered and accepted (when applicable) IAW CDRL requirements.

c. Program Risks and their respective mitigation plans are in place, being executed, and manageable for implementation of the functional requirements into a final production design.

d. Trade-off analyses have been completed if applicable.

e. Logistics analysis has been completed and plans have been implemented.

Critical Design TIM Completion Criteria The Contractor shall meet the following production Critical Design TIM completion criteria:

a. CDRL items that were part of the Critical Design TIM entry criteria have been satisfactorily discussed.

b. Updated risk assessments and risk mitigation plans have been satisfactorily discussed.

c. Risks and their respective mitigation plans are in place and manageable for implementation of the functional requirements into a product baseline evolution.

d. Program schedule is executable within the anticipated cost and technical risks.

e. Program is properly staffed.

f. Critical Design TIM Request for Actions (RFAs) have been resolved and closed.

g. An updated Critical Design TIM presentation incorporating feedback and changes identified during the Critical Design TIM.

h. An executable schedule has been presented.

i. Product baseline has been established.

Test Readiness Assessment (TRA) The Contractor shall

a. Conduct TRA in the time between the Critical Design TIM and the beginning of DT-C1 as directed by the Government;

b. Assess the readiness of the training system and the test objectives, processes, documentation and facilities;

c. Present and discuss the following at TRA:

(1) Status of risks;

(2) Design changes since the Critical Design TIM;

(3) Installation and checkout process to show the system is integrated, operational, and ready for test;

(4) Program schedule;

(5) CDRL status;

(6) Updated RTVM;

(7) Test program resources (e.g. personnel, facilities, test environment, software, tools, test assets);

(8) Status of issues (if applicable);

(9) All System Trouble Reports (STRs) noted from the final System Integration Test have been provided to the Government;

(10) Results of Contractor-led execution of SPP procedures.

(11) Detailed test schedule;

(12) SPP procedure results and documentation; and

(13) Cyber Security scanning results and documentation

TRA Entry Criteria Prior to TRA, the contractor shall

a. Deliver TRA presentation materials IAW CDRL BA01;

b. Ensure all applicable CDRLs have been delivered;

c. SPP procedures have been executed with results provided to the Government;

d. All applicable Cyber scans have been executed with Government participation; and

e. Confirm plan for testing has been established and ATPs have been accepted by the Government.

TRA Exit Criteria The Contractor shall attain Government concurrence that the following TRA completion criteria have been met:

a. Test Logs and ATPs have been successfully updated per Government comments;

b. Baseline configuration has been verified;

c. TRA RFI / RFA have been closed out; and

d. The Contractor has demonstrated that the installation and checkout process for system integration has been completed and is ready for test.

Defect Review Board (DRB) The Contractor and Government DRB co-chairs will prepare an agenda at least 24 hours prior to the DRB and collect artifacts.

The Contractor shall

a. identify a Contractor DRB co-chair;

b. conduct DRB meetings at the end of each test event;

c. provide Government DRB chair with agenda inputs at least 24 hours prior to DRB;

d. defer to the Government as the final authority on System Trouble Report (STR) priority

e. categorize all defects by impacts against an established training objective or by impact against system stability

f. manage of STRs, which consists of maintaining the STR reporting system to include entering, modifying and developing STRs;

g. document and send to the Government for correction all defects against GFE / GFI / GFX;

Table 4. Defect Categorization Table

Jeopardize safety, security, or other requirement designated “critical”

Note on Priority 3 defects, workarounds are only valid if being executed by an instructor and/or system administrator. Any defect causing the student to execute a procedure differently than aircraft procedures (i.e. NATOPS/NATIPS) is a Priority-2 defect unless explicitly downgraded by the Government.

Result in inconvenience or annoyance for development or maintenance personnel but does not prevent the accomplishment of the responsibilities of those personnel

Government Decision of Defect Correction The Contractor shall

a. correct all STRs as directed by the government unless otherwise adjudicated during DRB, prior to the entry into the next testing milestone;

b. label STRs not selected for correction by the Government as “DRB Deferred STRs” within the Contractor’s Discrepancy Reporting System;

c. disposition DRB deferred STRs as a “New STR” may be selected for correction at future DRBs

Integration Test Readiness Assessment (ITRA) The Contractor shall:

a. Conduct an ITRA prior to commencement of USN IT-C1 and RAAF OSIV as directed by the Government;

b. Present and discuss the following during ITRA:

(1) Installation and checkout process to show the system is integrated, operational and ready for test;

(2) Detailed test schedule;

(3) Updated requirement traceability to ATPs to verify specification requirements have been tested;

(4) Updated test log;

(5) USN DT-C1 test results, including completed ATPs & STRs;

(6) All applicable software versions;

(7) Summary of all outstanding STRs.

ITRA Entry Criteria The contractor shall attain Government concurrence that the following have been satisfied as entry criteria prior to proceeding into the TRAs:

a. Deliver ITRA presentation materials IAW CDRL BA01;

b. Updated ATPs, to include all corrections discovered throughout previous test events, have been submitted to the Government;

c. All tests procedures agreed upon by the Technical IPT have been run as evidenced by the existence of contractor test logs;

d. Corrections resulting from testing have been incorporated into the baseline prior to follow-on testing;

e. A complete Government-led execution of SPP procedures has been performed including documented step by step results; and

f. All STRs not corrected from previous test events have been adjudicated by the Government PM.

ITRA Exit Criteria The contractor shall request and receive Government concurrence that the TRA has been completed by satisfying the following completion criteria:

a. Contractor test logs and records demonstrate that a complete run of the ATPs has been executed;

b. The Integrated Test Team has been identified to include applicable personnel names and functions for team members involved in testing;

c. Contractual CM processes have been followed, and contractor generated CM logs are available for Government review/inspection;

d. Baseline configuration has been established and verified;

e. Agreed plan for IT-C1 has been established and ATPs have been accepted by the Government; and

f. Discrepancy reporting system’s STR database is up to date.

System Test and Evaluation The contractor shall

a. establish a T&E program to ensure verification and validation of system performance, functionality, and compliance with the requirements of this SOW and the Performance Specification in PRF 260087;

b. ensure all test components are executed IAW Government Test Plan (GTP); and

c. ensure all test data is captured IAW section 3.6.13.8.

Responsibility for Tests The Contractor shall

a. designate a Contractor Test Director (TD) to coordinate with the Government TD;

b. report and document incidents (e.g. safety, facility, operations, urgent communications and findings) to the Government TD;

c. lead the execution of the DT test milestones, with government participation;

d. support in the IT test milestones, with the government leading execution;

e. provide materials and test equipment required for execution of necessary test procedures;

f. terminate testing at the request of the Government TD; and

g. terminate testing when there is a concern about safety of personnel and/ or equipment.

Test, Inspection, Examination Resources and Facilities The Contractor shall

a. furnish the inspection and equipment, and Contractor personnel to conduct testing at USN/RAAF sites, to ensure that the training system meets the requirements of this contract;

b. ensure the Contractor personnel, test equipment, support equipment, spare assemblies, parts, and test logs are available for the entire test event.

Test Procedures The contractor shall

a. develop or update applicable Acceptance Test Procedures (ATPs) to verify the Performance Specification in PRF 260087;

b. develop ATP using the methods of analysis, inspection, demonstration and test to ensure thorough evaluation of the TS;

c. execute and validate the ATPs prior to the start of the DT-C1 test milestone;

d. prepare and deliver the ATPs IAW CDRL AA01.

Testing Interruptions Due to Safety Concerns The Contractor shall

a. have the authority to stop testing during test events when anyone raises a safety concern;

b. immediately cease testing and report safety concerns to the Government test team if a safety concern is raised during testing; and

c. resume testing after requesting and receiving concurrence from the Government test team that the safety concern has been cleared.

Testing Suspension Due to System Defects The Contractor shall

a. have the authority to suspend testing during Developmental Testing (DT) if a defect causes the system or subsystems to become unusable/untestable or inoperative in a way to prevent further reliable testing;

b. use the following guidelines to determine if the test event should be suspended:

(1) High Priority STR that is terminal: Does the STR preclude further testing of the trainer such that the problem requires correction prior to continuation of testing?

(2) Numerous major/moderate level STRs: Does the accumulation of major STRs affect functionality in numerous areas of the trainer? Do the problems interrupt executions of the test to the point that time would be better spent evaluating trainer issues than to continue testing?

(3) Excessive Total STRs: Does the total quantity of all STRs degrade trainer operation to the extent that testing or training cannot proceed uninterrupted without an excessive amount of workarounds?

(4) System Stability or Maintenance events: Does the accumulation of the number of system hot starts or warm starts, or down time for maintenance preclude a continuation of the planned testing evolution?

c. defer to the government for testing suspension during Integration Testing (IT)

System Stability The contractor shall implement a design that does not reduce system stability. The System Stability is defined as the state in which the training device can operate with minimal interruptions. Minimal interruption is defined as a training device discrepancy that can be identified and corrected within a timeframe that allows for successful completion of mission training objectives (i.e., restart (“hotstart”) subsystem, clear memory, etc.) over the remaining time allotted.

a. No more than one restart per device subsystem, per event.

b. No more than two device subsystem restarts per event.

c. Recovery to original simulation state before failure shall not exceed 30 minutes.

d. Combined recovery time throughout event shall not exceed 45 minutes.

Tolerance Data The contractor shall

a. identify test tolerances for pass / fail criteria; and

b. identify test tolerances and the source from which the specified tolerances are derived in the ATPs for each applicable criteria.

Test Log The Contractor shall

a. prepare and maintain a log of subsystem and system discrepancies found during test events;

b. begin the entries of the test log at the start of DT-C1 testing, continuing for all following test events and follow-on articles;

c. record STR sign off by the Government test representative after a successful retest; and

d. make the test log available to the Government upon request.

Software Changes During Government Testing The Contractor shall

a. obtain Government authorization prior to making changes to software baselines during DT and IT events;

b. maintain configuration control of software baselines used during DT, IT and Follow-on test milestones;

c. provide proof to the Government that proposed software baseline changes do not display signs of regression by Contractor regression testing; and

d. report any design changes that resulted from…