FLIR Competition SOW_RevB_Draft for industry 08-25-2024.docx

ATTACHMENT XXX

Statement of Work (SOW)

USMC Heavy Lift Replacement CH-53K™ Forward Looking InfraRed (FLIR)

DISTRIBUTION STATEMENT D – Distribution authorized to Department of Defense and U.S. DoD Contractors only (Administrative or Operational Use), (07-27-2023). Other requests shall be referred to PROGRAM EXECUTIVE OFFICER, AIR ASW ASSAULT AND SPECIAL MISSION PROGRAM (PMA261), 47123 Buse Road, Bldg 2272, Room 155, Patuxent River, MD 20670.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

DESTRUCTION NOTICE –Destruction notice shall be IAW DODI 5230.24, Enclosure 3, Paragraph 17.

Controlled By: Department of the Navy

NAVAIRSYSCOM: PEO (A); PMA-261

CUI Category: Defense, Financial, Privacy, Provisional Dissemination Control: Distribution Statement D

REVISION HISTORY

CUI

Table of Contents

1.0 Scope

1.1 Introduction

This Statement of Work (SOW) identifies the tasks to be performed by the Contractor for the integration, testing and production of the Forward Looking Infrared (FLIR) System for the CH-53K aircraft. The Contractor will be required to participate in Technical Interchange Meetings (TIMs) and Systems Engineering Technical Reviews (SETRs). The Contractor will demonstrate integration of its system with the CH-53K avionics systems at the Government’s system integration laboratory (SIL) at Patuxent River Naval Air Station. The Contractor will be required to provide material, services and necessary support documentation needed to complete the tasks identified in this SOW. The Contractor will be required to provide technical support to the Government and prime contractor during all ground (to include SIL) and flight integration testing.

1.2 Background

The FLIR is a required avionics component of the CH-53K to provide navigation and situational awareness capability.

2.0 Applicable Documents

All referenced documents are mandatory unless otherwise specified within the body of this SOW or whose use are identified as “Guidance Only” documents not citable as requirements at DOD ASSIST (https://quicksearch.dla.mil ) (e.g. MIL-HNBK-61A(SE)). Guidance documents may be used as an aid in identifying applicable topics to be addressed consistent with meeting the requirements of the program. Unless otherwise specified, the applicable version of the document is the most current version in effect at the time of contract award, except for Contract Data Requirements List (CDRL) item deliverables from other contracts being referenced, which will be the latest U.S.G. approved version. In the event of a conflict between the documents referenced herein or the contents of this SOW, the SOW shall apply.

2.1 Government Documents

PPP

Unclassified Program Protection Plan

2.2 Government Handbooks, Standards, and Guidelines

2.3 Prime Contractor Documents

2.4 Other Documents

3.0 Requirements

3.1 General Requirements

The Contractor shall provide a FLIR system for integration into the CH-53K and provide data necessary to support the FLIR system’s operation, maintenance, installation, calibration, testing and platform software development. The contractor shall provide support to the Government during CH-53K integration and testing. The FLIR system shall meet the performance requirements as described in “CH53K_EOSMS_Performance_Specification”, Attachment X.

3.2 Program Management (All CLINS)

3.2.1 Post Award Conference (PAC)

The Contractor shall host a post contract award conference (PAC) at the contractor location. The PAC should occur within 30 calendar days of the contract award. The purpose of the PAC is for both parties to review all sections of the bi-laterally signed contract and for the Contractor to review and demonstrate to the Government the management procedures, provide progress assessments, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings/actions. The Contractor shall present management, subcontractors, and program implementation processes in accordance with Data Accession List (DAL) (CDRL A019).

CDRL A019: Data Accession List (DAL)

3.2.2 Cost and Software Data Reporting (CSDR)

The Contractor shall use a documented standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04, CSDR Manual.

3.2.2.1 Contractor Cost Data Reporting (CCDR)

The Reporting Entity shall:

a) Use the Government-approved Contract Cost and Software Data Reporting (CSDR) Plan, DD Form 2794, and the related Resource Distribution Table (RDT) as the baseline for reporting provided as contract attachment (X and Y);

b) Prepare and deliver to the Government a Cost and Hour Report (FlexFile) (CDRL A001) for every indicated data element (Data Group B) within the Government-approved Contract CSDR Plan;

c) Provide a Work Breakdown Structure (WBS) Dictionary and Remarks as a part of the FlexFile format (Data Group B) for every data element identified within the approved Contract CSDR Plan;

d) Prepare and deliver to the Government a Quantity Data Report (CDRL A002) for every indicated data element (Data Group B) within the Government-approved Contract CSDR Plan;

e) Prepare and deliver to the Government DD Form Cost Business Data Report (CBDR) 1921-3 (CDRL A003).

f) Provide updates to the Government-approved Contract CSDR Plan and related RDT for Government approval. Updates include: aligning the Subcontractor effort to a single WBS element and updating the RDT as new Subcontracts are awarded;

g) If a submission event slips, the Contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a date change request for the event-driven date through the CSDR Submit-Review (CSDR-SR) system for approval by the Defense Cost and Resource Center (DCARC) before the date reflected in the Office of the Secretary of Defense, Deputy Director Cost Assessment (OSD DDCA) approved Contract CSDR Plan occurs.

h) Hold a Cost and Software Data Reporting-Readiness Review (CSDR-RR) after contract award to include a discussion of the Contractor’s standard cost and software data reporting process that satisfies the guidelines contained in the DoD 5000.04 (CSDR Manual) and the requirements in the Government-approved Contract CSDR Plan and related RDT.

CDRL A001: Cost and Hour Report (FlexFile) CDRL A002: Quantity Data Report CDRL A003: Cost Business Data Report (CBDR)

3.2.2.2 Subcontractor Cost Data Reporting

The Prime Reporting Entity shall:

A. Flow-down Contractor Cost and Software Data Reporting (CSDR) requirements to any Subcontracts valued over $50 million or any Subcontracts valued between $20 million and $50 million that are designated by the Cost Working Integrated Product Team (CWIPT) as high risk, high value, high technical interest or a middle-tier acquisition (804);

B. Notify the Government of any Subcontract changes or new subcontracts awarded for subcontracts that exceeds $50 million;

C. Flow-down DD Form 1921-3 (CDRL A003) to any Subcontractor required to submit Cost and Software Data Reporting.

3.2.3 Schedule Management

The Integrated Program Management Data and Analysis Report (IPMDAR) (DI-MGMT-81861C) shall be developed, maintained, updated/statused and reported on a monthly basis per (CDRL A01H) (per IPMDAR_CDRL_IMS Only_Template_5.31.24).

CDRL A01H: Integrated Program Management Data and Analysis Report (IPMDAR)

3.2.3.1 Reporting

The Contractor shall provide monthly IPMDARs per (CDRL A01H) except as modified and specified per the following:

· Contract Performance Dataset (CPD): Contract Performance Dataset (CPD) is not applicable to this CDRL.

· Schedule (Comprised of both the Native Schedule File and the Schedule Performance Dataset (SPD)): Schedule Performance Dataset (SPD) is not applicable to this CDRL. The Native Schedule File remains applicable to this CDRL.

· Performance Narrative Report (Comprised of both the Executive Summary and the Detailed Analysis Report): Only narrative analysis of data provided in the Schedule is applicable to this CDRL.

3.2.3.2 Joint Baseline Review

After Government receives the baselined integrated master schedule, the contractor shall host a joint baseline review to discuss the following items: schedule construction rationale, key schedule assumptions, review justification fields (for constraints, leads, and lags), review schedule margin approach, and other schedule concern areas identified such as areas of high free float, tasks with long duration, missing logic, or other identified areas.

3.2.3.3 Schedule Validation Deep Dive

If required, the Government may request a Schedule Validation Deep Dive (i.e. Schedule Scrub) be conducted. The purpose of a Schedule Validation Deep Dive is to ensure the IMS is constructed consistent with IPMDAR (CDRL A01H) requirements to include all authorized work, relationships and durations representing a realistic plan forward through contracted completion. The NAVAIR Program Schedule Assessment guidance shall be provided as GFI when conducting a Schedule Validation Deep Dive.

3.2.3.4 Status Reviews

The Contractor shall conduct monthly program management and IPT status update meetings. Meetings shall coincide with, and leverage to the maximum extent practicable, the technical interchange meetings. The information supporting the meeting shall be available to the Government Team no later than close of business the day prior to the meeting. At a minimum, the following information should discussed:

1. CDRL Look-ahead. Status of CDRLs which have delivery or Government response due dates within a six (6) week rolling wave of the weekly meeting. Delinquent contractor deliveries and Government responses shall be reported.

2. Critical Path. Briefing of any issues or concerns with tasks on the critical or driving paths

a. Overall program critical path

b. Near critical path (float/slack value is 22 days or less.)

c. The current driving paths to selected Events and/or major milestones as determined by the Government Program Manager.

3. Risks. For risks pertaining to schedule, status of Estimated Completion Date (ECD)s on all risk mitigation steps overdue and due prior to the next Program Risk Advisory Board (PRAB) and potential candidate risks. Updated projections of schedule impacts should also be addressed.

5. Schedule Status for the following:

a. Slack/Float to next major milestone

i. For all tasks discussed, include Task Name, Unique Identification (UID), Baseline Start/Finish and Forecast Start/Finish as reflected in the latest IMS

b. Critical/near-critical delinquent task identification.

i. For any tasks discussed, include Task Name, Unique Identification (UID), Baseline Start/Finish and Forecast Start/Finish as reflected in the latest IMS

ii. Associated comments related to missed task starts/finishes (and the impact of those to the overall program).

6. Issues/Help Needed.

7. Subcontractor Critical Task Status.

8. Action Items. This shall include status of all program action items

3.3 Engineering (CLIN 0001)

3.3.1 Systems Engineering

3.3.1.1 Systems Engineering Requirements

The Contractor shall utilize systems engineering processes and plans in the execution for the tasks outlined in this SOW. The Contractor shall plan and conduct system requirements analyses, functional analysis, and allocations to translate the requirements identified in the CH-53K FLIR specification and this SOW into their lower-level functional specifications. The Contractor shall recommend and substantiate tailoring of the applicable specifications, standards, and Government documents referenced in this SOW.

3.3.1.2 Requirements Management

The Contractor shall utilize a requirements management process throughout the period of performance of this contract. The Contractor shall maintain traceability among the requirements and work products. The Contractor shall track all changes to requirements. The Contractor shall deliver the Requirements Traceability Verification Matrix (RTVM) (CDRL A004) as described in this SOW. The contractor shall provide status of their requirements management process at the established technical interchange meetings.

· CDRL A004: Requirements Traceability Verification Matrix (RTVM)

3.3.1.3 Interface Requirements Specification

The Contractor shall deliver an Interface Requirements Specification (IRS) in accordance with (CDRL A005). This specifies the requirements imposed on the system Hardware Configuration Items (HWCIs), Computer Software Configuration Items (CSCIs), manual operations, or other system components to achieve one or more interfaces among these entities. The IRS shall document all external and internal interfaces of the FLIR.

· CDRL A005: Interface Requirement Specification (IRS)

3.3.1.4 Interface Design Description / Interface Control Document (IDD / ICD) The Contractor shall deliver an Interface Design Description (CDRL A006) and an Interface Control Document (CDRL A007) for the FLIR. The Interface Design Description shall define all hardware and software interfaces of the FLIR. The Contractor shall provide interface description material in the form of Software Develop Kit (SDK), Application Programing Interface (API), or eXtended Markup Language (XML) message format, and source code examples for use by platform software developers. The Contractor shall provide message use cases and sequence diagram as part of the software message IDD. The Contractor shall provide software application or utilities to exercise functionality as a standalone, or partially integrated subsystem. The communications protocol between FLIR and platform shall be documented as described in this SOW.

· CDRL A006: Interface Design Description (IDD)

· CDRL A007: Interface Control Documents (ICD)

3.3.1.5 FLIR Installation and Control

The FLIR shall mechanically and electrically attach within the existing CH-53K physical location, provisions, and existing structure IAW CH-53K FLIR Specification and APSD Document No. 06524M1300, Attachment XX. Installation adapters may be used but modifications to the airframe are not permitted. Wiring connecter locations are defined but new connecters may be specified by the new system.

The CH-53K has existing user interfaces for FLIR control via the Multi-Function Control Unit (MFCU) and Multi-Function Display (MFD). The Contractor shall implement the MFCU controls as defined in the CH-53K FLIR specification. The Contractor shall use 1553B or Ethernet as the primary interface for command and control from/to the mission computer system.

3.3.1.6 Installation Interfaces and Procedures

The Contractor shall develop preliminary and final installation procedures and installation data products. The procedures shall include installation alignment instructions, attachment methods, cabling, mounting, and clearance information. The Contractor shall identify system installation procedures that include verification of mechanical and electrical installation. The Contractor shall deliver an Installation Control Drawing (ICD) IAW CDRL (A008). An ICD shall contain FLIR weight and center of gravity (CG), mounting locations, electrical connection details, cooling, power, and all data required to install the FLIR system.

· CDRL A008: Installation Control Drawing

3.3.1.7 Systems Engineering Technical Interchange Meetings (SETIM) The Contractor shall conduct the SETIMs in accordance with NAVAIRINST 4355.19E. The data provided will be tailored to only the specifics relevant to the project and these events are intended to be a maximum of one day. SETIMs may be combined with other program events with Government approval.

The System Requirements Review (SRR) shall present the Contractor’s understanding of the requirements and assess their translation into the system technical baseline. The Preliminary Design Review (PDR)/Architectural Design Review (ADR) shall be a Contractor presentation of the proposed design concept identifying risks and challenges. The Critical Design Review (CDR)/Detailed Design Review (DDR) shall present the final design configuration and supporting data prior to build. The Test Readiness Review (TRR) shall present readiness to enter test. The System Verification Review (SVR) shall present post-test results, confirm that performance requirements have been satisfied, and assess program completion.

The SETIM shall be considered complete when all Requests for Action (RFAs) have been closed. The Contractor shall deliver the final presentation materials including official action items in accordance with (CDRL A009) Presentation Materials and Action Items.

· CDRL A009: Presentation Material and Action Items

3.3.1.8 Production Readiness Review

The Contractor shall conduct a Production Readiness Review (PRR) for the Prime Contractor and subcontractors as jointly agreed upon between the Contractor and the Government. The Contractor shall conduct the PRR using the definitions, criteria, and processes defined in the Manufacturing Readiness Level (MRL) Desk book. (Current revision). The contractor shall plan for the participation of subject matter experts to represent the following areas: Technology and Industrial base, Design, Cost and Funding, Materials, process capability and control, quality, manufacturing workforce, facilities, and manufacturing management. The Contractors and Sub-Contractors shall deliver the MRL assessment areas checklist (CDRL A00A). The Contractor shall invite the Government to participate in PRRs for the Prime and Sub-Contractors with a minimum of 30 days advance notice. The Contractor shall host the Government review of the Contractor’s self PRR at the primary manufacturing or integration facility. The Contractor shall present the MRL status at the program CDR. The PRR shall be used to assess the Contractors MRL 9 readiness.

· CDRL A00A: Assessment of Manufacturing Risk and Readiness

3.3.1.9 Other Meetings

The Contractor shall host and participate in a bi-weekly one-hour phone conference with the Government team. The purpose of this meeting is to discuss technical issues, interface issues, progress, status, lessons learned and risks.

The Contractor shall provide technical test support during FLIR system integration and CH-53K flight testing. The Contractor shall be available by phone for teleconference for test meetings.

3.3.1.10 Configuration Audit

The Contractor shall conduct a Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) in accordance with the approved IMS and after having met all entrance criteria as specified in NAVAIR Instruction 4355.19E. The PCA shall ensure that the related design documentation matches the system under review. In addition to the standard practice of assuring product verification, the PCA confirms that the manufacturing processes, quality control system, measurement and test equipment, and training are adequately planned, followed and controlled. It is also used to validate many of the supporting processes used by the Contractor in the production of the item and to verify other elements of the item that may have been impacted/redesigned after completion of the System Verification Review/Production Readiness Review (SVR/PRR).

3.3.1.10.1 Functional Configuration Audit (FCA)

The contractor shall support a PMA-261 l FLIR kit FCA at the contractor’s facility. The FCA will be conducted at contractor’s facility using the CM principles stated in ANSI/EIA-649, consistent with the guidelines stated in MIL-HDBK-61.

This Audit will review and validate that the product requirements are achieved by the product’s design in the applicable product definition information. Conduct of the audit essentially encompasses a review of the results of the tests, analyses, inspections, demonstrations and simulations performed to prove specified performance requirements were achieved. The tests include verification/qualification and acceptance tests verifying all hardware and software functions.

A cognizant engineering representative shall be available to answer questions during the FCA. The contractor shall be responsible for delivering a comprehensive Functional Configuration Audit (FCA) plan in accordance with (CDRL A01K). The FCA plan should outline the necessary steps and procedures to conduct a thorough audit of the functional configuration of the system. It should include details on the scope, objectives, criteria, and methodology for performing the audit. The contractor shall ensure that the FCA plan complies with all applicable regulations, standards, and contractual requirements. Questions or comments regarding this plan will be covered by a joint working group.

CDRL A01K: Functional Configuration Audit (FCA)

All RFAs, RFIs and Actions to Minutes are assigned, resolved and approved by PMA-261 and to be delivered in accordance with (CDRL A009), in compliance with Computer Access Agreement, Attachment 3.

3.3.1.10.2 Physical Configuration Audit (PCA)

The contractor shall support a PMA-261 FLIR kit PCA at the contractor’s facility. The PCA will be conducted at contractor’s facility using the CM principles stated in ANSI/EIA-649, consistent with the guidelines stated in MIL-HDBK-61.

This audit will review the kits content to ensure conformity to the contractor’s engineering documentation, and manufacturing documentation. The contractor shall make available Technical Data Package (TDP) that define the FLIR kit. Contractor owned information, including Certificates of Conformance (CoCs) and First Article Inspection Reports (FAIRs) will be provided by the supplier. PMA-261 will arrange with the supplier directly to make their documentation available for review at the PCA, and to have FLIR kits present to be physically inspected.

A cognizant engineering representative shall be available to answer questions during the PCA. The PMA-261 PCA will validate the kits against the kit parts list, and piece parts against the part drawings. The contractor shall be responsible for delivering a comprehensive Physical Configuration Audit (PCA) plan in accordance with (CDRL A01L). The PCA plan should outline the necessary steps and procedures to conduct a thorough audit of the physical configuration of the system. It should include details on the scope, objectives, criteria, and methodology for performing the audit. The contractor must ensure that the PCA plan is in compliance with the requirements specified in the CDRL. The PCA plan must be delivered within the agreed-upon timeframe and shall meet all applicable regulations, standards, and contractual requirements. Questions or comments regarding this plan will be covered by a joint working group.

CDRL A01L: Physical Configuration Audit (PCA)

Entrance Criteria:

Exit Criteria:

• The kit parts list is determined to be accurate, all piece parts are supported by documentation and match the engineering design

• All RFAs, RFIs and Actions to Minutes are assigned, resolved and approved by PMA-261 and to be delivered by IDE in accordance with (CDRL A009), in compliance with Computer Access Agreement, Attachment 3.

3.3.1.11 Airworthiness Support

The Contractor shall provide assistance to the Government team conducting the airworthiness process. The purpose of this assistance is to ensure engineering data requirements, operating limitations, and restrictions for the specific configuration are available to NAVAIR so that the Interim Flight Clearance (IFC) process can be performed in accordance with NAVAIRINST 13034.1D. The Contractor shall make available to the Government all data on: changes to hardware, configuration reports, component performance, maintenance procedures, operating procedures, and Acceptance Test Procedures (ATPs) in accordance with the DAL (CDRL A019).

3.3.2 Software Engineering

The Contractor shall manage the program Software Engineering life cycle tasking.

These processes shall meet best commercial practices as defined by IEEE/EIA 12207-0 Capability Maturity Model® Integration (CMMI) Level 3 (or higher), or an equivalent model-based maturity model.

3.3.2.1 Software Requirements Management

The Contractor shall distribute the requirements analysis for the individual Computer Software Configuration Item (CSCIs) Software based on the existing CH-53K software to allocate requirements to CSCI and shall develop, manage, and deliver a Software Requirements Specification (SRS) (CDRL A00B) for the relevant individual CSCIs based on the existing CH-53K Software Requirements Specification (SRS). Traceability shall be documented from the Support System Specification (SSS) to the relevant individual CSCIs and included in each of the SRSs. The Contractor shall plan a Software Specification Review (SSR) at the CSCI level IAW the SDP.

• CDRL A00B: Software Requirements Specification

3.3.2.2 Software Design Management

The Contractor shall deliver a Software Design Description (SDD) (CDRL A00C). The Contractor shall plan software Architecture Design Reviews (ADRs) and Software Detailed Design Reviews (DDRs) at the CSCI level IAW the SDP.

• CDRL A00C: Software Design Description

3.3.2.3 Software Test Plan

The Contractor shall develop and submit a Software Test Plan (STP) in accordance with (CDRL A00D).

· CDRL A00D: Software Test Plan

3.3.2.4 Software Test Report

The Contractor shall develop and submit a Software Test Report (STR) in accordance with (CDRL A00E).

· CDRL A00E: Software Test Report

3.3.2.5 Software Product Specification

The Contractor shall develop and submit a Software Product Specification (SPS) in accordance with (CDRL A00F) that contains or references the executable software, source files, & support software information, included as compilation, build, & modification procedures for a CSCI.

· CDRL A00F: Software Product Specification

3.3.2.6 Software Version Description

The Contractor shall develop and submit a Software Version Description (SVD). The Contractor shall provide a SVD with each SPS delivery. The Contractor shall provide documentation for installation and verification of the FLIR software and firmware in accordance with (CDRL A00G).

· CDRL A00G: Software Version Description

3.3.2.7 Software User Manual

The Contractor shall develop and submit a Software User Manual (SUM). The SUM shall specifically address the software configuration of the FLIR during installation and describe the user interface and operation of the software in accordance with (CDRL A00H).

· CDRL A00H: Software User Manual

3.3.2.8 Subcontractor Software Developers

If a subcontractor is utilized for software development, all requirements, design, development, quality assurance and configuration management shall be managed by the prime Contractor software lead and delivered as an integrated product.

3.3.2.9 Software Licensing

The Contractor shall document the procurement requirements of runtime software licenses, e.g. recurring, perpetual and/or subscriptions, required by the Government to operate the FLIR system. Transferable software licenses, purchased on this contract, for operator use, shall convey with FLIR system delivery.

3.3.2.10 Software Loading

The FLIR system shall be capable of being field loadable via the Program Loader Set (PLS) and capable of being stored on Naval Data Distribution System (NDDS). The contractor shall use the Program Loader Set (PLS, AN/USQ-203, part number-4032AS100-1) Common Support Equipment or be loadable through 1553/Ethernet via CH-53K Advanced Data transfer System (ADTS).

3.3.3 System Safety

The Contractor shall provide a safety assessment that reviews/analyzes existing hazards and/or identifies new hazards associated with the design and functionality changes introduced. Analysis shall include identification and assessment of new or changed causal factors and controls, system response, and the mishap risk contribution (severity/probability) of each hazard/change. An initial safety assessment shall be provided as part of the SRR package, and the final assessment shall be provided as part of the Critical Design Review (CDR) in accordance with System Safety Assessment (CDRL A00J).

· CDRL A00J: System Safety Assessment

3.3.3.1 LASER Hazards

The Contractor shall provide safety information relative to the LASER systems with the turreted package and the systems safety features and architecture. The Contractor shall generate and submit a Laser Hazard Analysis Report (CDRL A00K). As part of this report the contractor shall add portions of data required under OPNAVINST 5100.27B/MCO 51041.C as follows:

· Appendix A Laser Design Requirements Checklist

· Appendix B Support Equipment Design Requirements Checklist

· Data to support generating Enclosure (4) Package for LSRB which includes:

a. System Safety Features

b. Laser Masking Area Graphic Illustration with Aircraft Boundaries Referenced

· CDRL A00K Laser Hazard Analysis Report.

3.3.3.1.1 Laser Safety Measurement

The Navy’s Laser Safety Review Board (LSRB) measurement team will take measurement of the 1st article under test at the contractor’s facility. The Contractor shall provide testing space and support for this testing. Design/manufacturing changes shall be implemented by the contractor to successfully alter the system to overcome deficiencies cited by the LSRB. Additional testing maybe be required to confirm the changes.

3.3.3.2 Structural Design

The contractor shall provide a structural load analysis to ensure it meets the structural design load requirements as directed in the Specification in accordance with Structural Load Analysis (CDRL A01J).

CDRL A01J: Structural Load Analysis

3.3.4 System Test and Qualification

The Contractor shall test and evaluate the FLIR system and deliver data products that show compliance with performance and environmental requirements in the CH-53K FLIR Specification and this SOW. The Contractor shall coordinate testing and make such testing open to the Government as required.

3.3.4.1 Design Verification and Reporting

For each qualification effort, the Contractor shall develop and deliver a Qualification Test Plan and Procedure (QTP). The Contractor shall include test success criteria and verification methods, utilizing MIL-STD-810F as reference. Prior to System Requirements Review (SRR), the Contractor shall identify, using a verification matrix, whether verification compliance will be by analysis, inspection, test, similarity, or demonstration. The Contractor shall develop and deliver Qualification Test Report(s) (QTR). Reports may be combined by component or test activity. The Contractor shall include test success criteria, data, and analysis supporting requirement verification. QTR(s) shall state whether verification compliance was by analysis, inspection, test, similarity, or demonstration. If verified by similarity, the similar components’ test data/report shall be included. Testing required to meet specification in accordance with CDRLs A00L and A00M.

· CDRL A00L: Qualification Test Plan and Procedures

· CDRL A00M: Qualification Test Report

3.3.4.2 Test Equipment

The Contractor shall provide all necessary test equipment required to properly execute environmental and performance testing in accordance with the FLIR SPEC. The Contractor shall be responsible for maintaining calibration of all test and measurement equipment.

3.3.4.3 Manufacturing Acceptance Test Procedures (ATP)

The Contractor shall modify and perform Manufacturing Acceptance Test Procedures (ATP) for the FLIR system. The Manufacturing ATPs shall describe the inspection and testing required ensuring manufacturing quality of the component in accordance with CDRL A00N.

· CDRL A00N, Manufacturing Acceptance Test Procedures

3.3.4.4 Manufacturing Acceptance Test Report (ATR)

The Contractor shall deliver the Manufacturing Acceptance Test Report (ATR) for the FLIR system. The Manufacturing ATRs shall describe how the FLIR system meets the requirements and documents any anomalies or discrepancies with their associated dispositions ensuring manufacturing quality of the component in accordance with CDRL A01M.

· CDRL A01M, Manufacturing Acceptance Test Report

3.4 Reliability and Maintainability

3.4.1 Subcontractor and Vendor Reliability

The Contractor shall ensure products obtained from suppliers, vendors and subcontractors meet reliability requirements by establishing, implementing, and maintaining documented procedures which detect and/or preclude the use of substandard or counterfeit parts in the production process.

3.4.2 Reliability and Maintainability Program

The Contractor shall develop and deliver a Reliability and Maintainability (R&M) program plan and ensure the design of the FLIR satisfies the R&M performance requirements of this SOW and the APSD Document No. 06524M1300, Attachment X. Where increased reliability is a project objective or opportunity the Contractor shall identify components that are changing as a part of this engineering change and shall utilize the existing Failure Reporting, Analysis, and Corrective Action System (FRACAS) process and System Inquiry Report (SIR) data to identify root causes and corrective actions and report these at CDR. The Contractor shall deliver R&M plan in accordance with Reliability and Maintainability Program Plan (CDRL A00P).

· CDRL A00P: Reliability and Maintainability Program Plan

3.4.3 Reliability Modeling and Predictions

The Contractor shall perform reliability and maintainability predictions, which can utilize analytical, test, or field data. The data source and methodologies for each prediction shall be included in the Reliability and Maintainability Predictions Report. Predictions shall be done for continuous operation under a worst-case environment. Reliability block diagrams and mathematical models shall be used as part of the allocation and prediction process. The Contractor shall utilize MIL-HDBK-217F, Notice 2 for guidance in the development of the analytical predictions. The Contractor shall deliver the Reliability and Maintainability Predictions Report in accordance with CDRL A00Q.

· CDRL A00Q: Reliability Modeling and Prediction Report

3.4.4 Built in Test (BIT) Description Document & Assessment Procedures The Contractor shall prepare and deliver a BIT Description Document that describes the BIT system to include the methodologies of implementation, coverage plan, and planned architecture of the BIT system. The Contractor shall develop and deliver a BIT Assessment procedures document, to include a list of all potential faults. The Contractor shall perform a BIT Assessment of the FLIR system to demonstrate compliance with the BIT requirements. The contractor shall ensure all levels of BIT are tested. The Contractor shall describe the method of fault insertion in the BIT Assessment procedures. The contractor shall document the result of the assessment in a report and deliver the report in accordance with Built in Test Assessment (CDRL A00R)

· CDRL A00R: Built in Test Assessment

3.4.5 Reliability Test Report

The Contractor shall describe and summarize the results of all reliability testing and provide all data acquired during the reliability test program in accordance with (CDRL A00S).

· CDRL A00S: Reliability Test Report

3.4.6 Integrated Logistics Support (ILS) Planning & Management The Contractor shall provide an ILS Manager to communicate, report and interface with the PMA-261, Avionics Integrated Product Team (IPT) for this effort. As a part of this function, the Contractor shall:

a. Ensure execution of Product Support Analysis (PSA) required to field and maintain the readiness and operational capability of the FLIR including all functions related to weapon system readiness.

b. Interface with their engineering to support system design.

c. Ensure that logistics review of Engineering Change Notices (ECNs) or Engineering Change Proposals (ECPs) is accomplished prior to release of ECNs. The review shall consist of, the inclusion of interchangeability codes and maintenance plans, supply support and spares, publications, training, and support equipment.

d. Provide timely responses to communications received from the Government related to ILS specific issues and communications addressed to logistics functional departments.

e. Be an integral part of the (Government and Contractor) change process to ensure that logistics engineers review the drawings, and that supportability and maintainability concepts, along with all Logistics elements are taken into consideration.

f. Maintain communications with other qualified Contractors, sub-Contractors, and vendors, to ensure effective management of the program.

g. Participate in IPT teleconferences and meetings related to the FLIR integration.

This shall be achieved by an Integrated Product Support/Engineering partnership throughout the design review process.

3.4.7 Product Support Analysis (PSA) Database

The Contractor shall develop the PSA Database utilizing PSA repository software SLICWave, compliant with the requirements of SAE GEIA-STD-0007 utilizing the companion document SAE TA-HB-0007.The contractor shall use SLICWave LPD software in accordance with the GEIA-STD-0007B. The Contractor shall ensure the Logistic Product Database (LPD) has the capability to receive and transfer data compliant with SAE GEIA-STD-0007. The Contractor shall reference MIL-HDBK-502A. The Contractor shall deliver a SLICwave XML file consisting of the complete copy of the Logistics Product Database in accordance with Logistics Product Database (CDRL A00T).

· CDRL A00T: Logistics Product Database

3.4.8 Product Support Analysis (PSA)

The Contractor shall perform the following analysis required to field and maintain the readiness and operational capability of CH-53K weapon systems, subsystems, and components, including all functions related to weapon system readiness.

3.4.9 Failure Mode, Effects, and Criticality Analysis (FMECA) The Contractor shall conduct and document a FMECA that shall be completed at the level of each Shop Repairable Assembly (SRA) and evaluate the worst potential effects of each SRA failure mode at the assembly level, at the next higher level of indenture, and at the level of the entire unit. The scope of the analytical results shall also provide all data and information required for inputs to other reliability, maintainability, logistics related tasks, databases, and documents required herein. The Contractor shall use this information as the basis for developing fault isolation procedures; corrective and preventive maintenance tasks as it correlates with Reliability Centered Maintenance (RCM) concept and safety hazard analyses. Results shall also be input in the Logistics Product Database (LPD) record. The FMECA data shall be submitted to the government for review and updated as necessary to reflect changes in the end item under analysis in accordance with Failure Mode, Effects, and Criticality Analysis (FMECA) (CDRL A00U).

· CDRL A00U: Failure Mode, Effects, and Criticality Analysis (FMECA)

3.4.10 Reliability Center Maintenance (RCM)

The Contractor shall conduct and document an RCM analysis from information identified in the FMECA and Fault Tree Analysis (FTA) to define and balance “Condition-based”, “Interval-based”, and “Run-To-Failure” maintenance requirements balancing availability and risk in an efficient and cost-effective manner. The RCM data shall be submitted to the government for review and updated as necessary to reflect changes in the end item under analysis in accordance with (CDRL A00V) Reliability Center Maintenance via Integrated Reliability-Centered Maintenance System (IRCMS) Data File or submit via the web-based IRCMS.

· CDRL A00V: Reliability Center Maintenance (RCM) Analysis

3.4.11 Level of Repair Analysis (LORA)

The Contractor shall conduct and document a LORA for the FLIR in accordance with TA-STD-0017 activity 11.7. The LORA is used to identify feasible least cost repair or discard decision alternatives for maintenance for the FLIR system leveraging from the existing actual failure data and logistics documentation to the maximum extent possible. The LORA shall be one of the main documents that shall determine the maintenance concept, provisioning, training, IETM, configuration items, and support equipment. The LORA shall be submitted to the government for review and updated as necessary to reflect changes in the end item under analysis in accordance with Level of Repair Analysis (LORA) (CDRL A00W).

· CDRL A00W: Level of Repair Analysis (LORA)

3.4.12 Maintenance Task Analysis (MTA)

The Contractor shall perform MTA for the FLIR IAW TA-STD-0017 activity 12 and documented in the Logistics Product Database (LPD) in accordance with GEIA-STD-0007B. The Contractor shall support and participate in the joint review and resolution of Government comments. The MTA shall include the following:

1. Maintenance tasks required to correct each failure mode.

2. Personnel and support requirements for each subtask.

3. Support Equipment, test equipment, tools and training equipment required for each subtask.

4. Support Equipment is required for the Support Equipment itself (SE for SE).

5. Support Equipment Recommendation Data (SERD) is required.

6. The subtask requires off-equipment use of test equipment.

7. A Test Program is required.

8. Calibration is required.

9. Spares and repair parts, including mandatory replacement parts.

10. All part numbers and associated procurement information.

11. Part numbers on the HA Entity shall be linked with Logistics Support Analysis (LSA), Logistics Control Numbers (LCNs) on the XB Entity along with applicable information about how the item is used in the system and requirements for the supply of the item to support each subtask.

The Contractor shall submit LSA-019 MTA reports using TA-HB-0007-1 as guidance in accordance with the Maintenance Task Analysis (MTA) (CDRL A00X).

· CDRL A00X: Maintenance Task Analysis (MTA).

3.4.13 Maintenance Plan

The Contractor shall develop and deliver a Maintenance Plan for the FLIR. The Maintenance Plan shall consist of three parts: Part I is the summary of the system and shall include the items that make up the system in a top down indenture; Part II should include Nomenclature, technical factors, Source Maintenance and Recoverability (SM&R) codes, Work Unit Code (WUCs), part numbers and stock numbers (if available); Part III shall include fault isolation tasks with appropriate support equipment to perform the task at each maintenance level. The Contractor shall submit LSA-024 MP reports using TA-HB-0007-1 as guidance in accordance with Maintenance Plan (CDRL A00Y) as required.