7PWS.pdf

PR: FD2060-19-00038 PWS 1

Distribution Statement: D

Performance Work Statement (PWS)

For

AN/ALQ-172(V) Countermeasures System (CMS)

Line Replaceable Units (LRU’S)-2 and -3

Reliability and Maintainability (R&M) Redesign

Purchase Request: FD2060-19-00038

Date: 30 May 2018

Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors only: Administration & Operational use (16 Feb 2018). Other requests for this document shall be referred to the responsible program manager, USAF AFMC 408 SMCS/GULB, 235 Byron St. Ste. 19-A, Robins AFB, GA 31098. Questions concerning technical content should be directed to the Procuring Contracting Officer (PCO), USAF AFMC AFSC/PZABB for routing to USAF AFMC 408 SCMS/GUEA.

Questions concerning non-technical content should be directed to PCO for routing to USAF AFMC 408

SMCS/GULB.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., S3c. 2751 et seq.) or the Export Administration Act 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violators of these export laws are subject to severe criminal penalties.

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

PR: FD2060-19-00038 PWS 2

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) describes the services required to provide the engineering services to perform a form, fit, function, and interface (FFFI) replacement for the AN/ALQ-172 (LRU-2 and LRU-3). These services include a LRU FFFI redesign, prototype fabrication, and test and delivery effort by redesigning the AN/ALQ-172 (LRU-2 and LRU-3) to meet legacy LRU specification performance requirements. The FFFI prototypes shall exhibit system reliability, availability and performance equivalent to or exceeding the legacy specifications of the AN/ALQ-172 (LRU-2 and LRU-3).

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by increasing the reliability and maintainability of the AN/ALQ-172 (LRU-2 and LRU-3), as well as, sustaining the electronic warfare suite for the B-52H strategic bombers and AFSOC C-130s until retirement.

1.3 Background: This acquisition will benefit the USAF by providing FFFI for the redesign of the AN/ALQ-172 (LRU-2 and LRU-3) in support of the AFGSC B-52H (ALQ-172(V)2), AFSOC MC-130H Combat Talon ‘II’ transports and AC-130U (ALQ-172(V)1) operations.

2.0 Services Summary

Performance Objective PWS Reference Performance Threshold

Provide accurate technical monthly status addressing schedule and cost status

4.4.3 Monthly status reports that shall be technically

accurate and complete with no more than one technical error and no more than five typographical errors.

Provide Test Requirement Documents (TRDs)

4.2.5.1. The contractor shall build FFFI LRU prototypes

with improved system availability by providing accurate Technical Order (T.O.) changes. The

AN/ALQ-172 (LRU-2 & LRU-3)

Countermeasures Receiver shall pass prototype testing requirements. An item that has a high level of Reliability and Maintainability (R&M), is producible, and is supportable, should achieve a high level of operational availability.

Build Form, fit, function and interface LRU prototypes with improved system availability

4.3.1 The form, fit, function and interface prototypes

successfully pass the testing requirements with no more than two retests at the next higher assembly with a calculated LRU MTBF of at least 1,600 hours for LRU-2 and at least 2,600 hours for LRU-3.

PR: FD2060-19-00038 PWS 3

Provide Technical Order (T.O.) changes according to TMCR

4.3.6.1 Final version T.O. changes shall be free of

technical errors and require no major re-work, as determined by the Government.

Pass prototype testing requirements

4.3.1 Successfully pass prototype testing requirements

with no more than two retests at the next higher assembly.

Quality of CDRL deliverable

4.2.1 There shall be no more than one rejection of any

deliverable. There shall be no more than one total rejection(s) of deliverables per contract year. The Government will reject a deliverable if five or more technical errors or five or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 30 business days of notification of Government rejection.

Receipt of CDRL deliverable

4.2.2 There shall be no more than one late submission(s)

of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Contractor Manpower Reporting

5.8 Within 30 calendar days of contract/order award, the

Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data. The Contractor shall provide a count of contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

Adherence to Contractor Quality Management System

5.10 100% compliance with the QMS is required.

3.0 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 furnished equipment is authorized as follows. Applicable Government furnished equipment is already in contractor possession under existing repair contract FA8522-15-D-0002 and is available for use on a rent free non-interference basis. This equipment includes the ALQ-172(V) Enhanced Maintenance Test Set (EMTS). There is only one located at the Harris facility and it is accountable to the repair contract. In addition, Government furnished equipment already at the contractors facility and

PR: FD2060-19-00038 PWS 4

accountable to contracts FA8540-14-D-0002, is also available for use on a rent free non-interference basis. The Contractor shall report any type of loss of Government furnished property IAW all applicable Government property clauses provided in the contract.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) and Contractor-Acquired Property (CAP) in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.4 Loss of Government Property

3.4.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.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools.

3.5 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 upon 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. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

The Government obtains title to Contractor Acquired Property (CAP) acquired or fabricated by the Contractor to perform tasks under the contract in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. CAP shall be returned to the Government upon completion of the contract unless retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes GFP added to the successor contract by modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the

4.0 Technical Requirements

PR: FD2060-19-00038 PWS 5

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

4.1.2 Place of Performance: These services will be performed at the contractor’s facility in Clifton, NJ.

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier DID Title PWS Reference(s)

A001 Scientific and Technical Reports

DI-MISC-80711A 4.3.2, 4.3.3, 4.3.4,

4.3.5, 4.3.17.4, 4.3.17.5

A002 System/Subsystem Specification (SSS)

DI-IPSC-81431A 4.3.2, 4.3.15

A003 Conference Agenda DI-ADMN-81249B 4.3.2.1, 4.3.3.1, 4.3.4.1, 4.3.5.1, 4.3.6.1, 4.3.11, 4.3.15.3.8, 4.3.16, 4.4.4

A004 Conference Minutes DI-ADMN-81250B 4.3.2.1, 4.3.3.1, 4.3.4.1, 4.3.5.1, 4.3.6.1, 4.3.15.3.8, 4.3.16, 4.4.4

A005 Safety Assessment Report

DI-SAFT-80102C/T 4.3.3.2

A006 Test Procedure DI-NDTI-80603A 4.3.6.2, 4.3.7, 4.3.8, 4.3.9, 4.3.13.2

A007 Test/Inspection Report

DI-NDTI-80809B 4.3.6.2, 4.3.7,

4.3.8, 4.3.9, 4.3.13.7

A008 Configuration Audit Summary Report

DI-SESS-81022D 4.3.11

A009 Data Accession List

(DAL)

DI-MGMT-81453B NOT 1 4.3.13.3, 4.4.5

A00A Technical Manual Contract Requirement

(TMCR)

TM-86-01P 4.3.14

A00B Notice of Revision

(NOR)

DI-CMAN-80642C 4.3.14

A00C Product Drawings/ Models and Associated Lists

DI-SESS-81000E/T 4.3.15

PR: FD2060-19-00038 PWS 6

A00D Status Report DI-MGMT-80368A/T 4.3.17.4, 4.4.3 A00E Management Plan DI-MGMT-80004A 4.4.1, 4.4.5 A00F Contract Funds Status

Report (CFSR)

DI-MGMT-81468 4.4.3

A00G Item Unique Identification Marking Plan

DI-MGMT-81803 4.5.5

A00H IUID Marking Activity and Verification Report

DI-MGMT-81804A 4.5.5

A00J Counterfeit Prevention Plan

DI-MISC-81832 4.6.1

A00L Quality Assurance Program Plan

DI-QCIC-81794 5.10

B001 Software Development Plan

DI-IPSC-81427B 4.3.13.2

B002 Software Requirements Specification

DI-IPSC-81433A 4.3.13.2

B003 Interface Requirements Specification

DI-IPSC-81434A 4.3.13.2

B004 Software Design Description

DI-IPSC-81435A 4.3.13.2

B005 Software Test Description

DI-IPSC-81439A 4.3.13.2

B006 Software Product Specification

DI-IPSC-81441A 4.3.13.2

B007 Software Version Description

DI-IPSC-81442A 4.3.13.2

B008 Software User Manual

DI-IPSC-81443A 4.3.13.2

B009 Computer Software Product

DI-IPSC-81488 4.3.13.2

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than two total rejection(s) of deliverables per contract year.

The Government will reject a deliverable if two or more technical errors or five or more minor errors are found within the deliverable. 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 rejected deliverable shall be corrected and resubmitted within 15 business days of notification of Government rejection.

PR: FD2060-19-00038 PWS 7

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) or be submitted directly to the MFT member identified on the CDRL. There shall be no more than one late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Engineering Services

4.3.1 The contractor shall develop a FFFI replacement LRU’s configuration that eliminates part obsolescence and replaces the AN/ALQ-172 (LRU-2 and LRU-3) with a single design. The form, fit, function and interface prototypes shall successfully pass the testing requirements with no more than two retest at the next higher assembly with a calculated (MIL-HDBK-217F) LRU Mean Time Between Failure (MTBF) of at least 1,600 hours for LRU-2 and at least 2,600 hours for LRU-3. The contractor shall not degrade AN/ALQ-172 system performance. The contractor shall design the AN/ALQ-172 (LRU-2 and LRU-3) equipment only such that no Group A modifications shall be required to incorporate the design. The contractor shall maximize use of Non-Developmental Technology, with consideration given to multiple supply channels, produce-ability and long-term availability. The contractor shall consider and include current state-of-the-art technology wherever possible. The contractor shall conduct a survey of vendors down to the component level to determine if there is an acceptable industry base for the components being recommended in the redesign options. The contractor shall ensure that all redesign options maintain existing performance allowing for no system level degradation due to proposed hardware or software changes. The contractor shall identify, minimize, and document impacts to contractor and government existing fielded support equipment due to the new AN/ALQ-172 (LRU-2 and LRU-3). The contractor shall identify and document any required modifications to Test Program Sets (TPSs), with respect to both hardware and software. The contractor shall identify update requirements for the documents listed in the Affordable System Operational Effectiveness Diagram and generate development documentation sufficient to allow Air Force installation and test of the LRU with the new (LRU-2 and LRU-3) on B-52H and AFSOC C- 130’s aircraft. The contractor shall produce an as built and tested technical data package for the internal LRU’s configuration. The contractor shall not recommend proprietary or sole source components unless there is no alternative available. Any proprietary or sole source components recommended shall be explicitly identified at status and design reviews. The Development Phase Relationship Illustration provides a top level overview of the development process to be accomplished by the contractor. All PWS activity shall be planned and scheduled using a detailed integrated master schedule (IMS) as part of a comprehensive program management plan described later in this document.

4.3.2 Requirements Definition: The contractor shall follow a structured Integrated Product and Process Design (IPPD) systems engineering process to accomplish AN/ALQ-172 (LRU-2 and LRU-3) redesign. The contractor shall accomplish system analyses to define and develop system technical requirements that address all identified requirements. The contractor shall calculate legacy AN/ALQ-172 (LRU-2 and LRU-3) system availability utilizing reliability, maintainability, supportability, and produce-ability data. The exit criteria for this phase shall be:

PR: FD2060-19-00038 PWS 8

program objectives and execution plan (including processes and metrics); program constraints;

system concept architecture; program risk assessment; technology readiness assessment; system performance specification; allocation of system requirements to hardware and software subsystems; identification of all software components; cost and critical path drivers; product support plan; draft system/subsystem specification tree; program R&M plan; draft R&M methodology; and successful System Requirements Review (SRR) that establishes the requirements baseline. The contractor shall document the analysis in a requirements definition engineering report in accordance with (IAW) the IMS. Work products shall contain no more than one technical error and no more than five typographical errors per submittal. [CDRL A001, DI- MISC-80711A, Scientific and Technical Reports], [CDRL A002, DI-IPSC-81431A, System/Subsystem Specification]

4.3.2.1 Systems Requirement Review (SRR): The contractor shall conduct a multi-functional technical SRR to ensure that all system and performance requirements: are defined in sufficient detail to enable system functional definition and functional decomposition; and are consistent with program cost, schedule, risk, and other system constraints. The SRR shall demonstrate consistency between the system requirements, system specification, system/subsystem specification tree, the recommended system solution, and available technologies. SRR approval is required prior to proceeding to the system design phase. The contractor shall prepare an SRR agenda and submit final briefing charts one week prior to the review. The contractor shall develop and deliver SRR minutes IAW the IMS. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.3 System Design Engineering: The contractor shall follow a structured IPPD systems engineering process to accomplish AN/ALQ-172 (LRU-2 and LRU-3) redesign. The contractor shall progressively identify and analyze the system function and sub-function alternatives for meeting system performance and design requirements. The contractor shall identify the required system functions based on the requirements performance parameters and all other requirements and constraints, and allocate subsystems to each function. The contractor shall define subsystem interfaces and integration requirements based on this partitioning. The contractor shall evaluate alternative solutions to optimize system availability using the functional architecture, allocated performance, and design specification requirements. The systems analysis goal is achievement of the proper balance among operational, economic, and logistic factors by use of a trade-off matrix to compare the alternative solutions. The analysis shall address cost of ownership and Reliability and Maintainability (R&M) parameters in addition to technical, cost and schedule performance. The analysis shall result in system functional definition and functional decomposition to the configuration item level to provide a system description in performance requirements terms. The contractor shall develop plans for the subsystem integration, verification, and validation processes, as well as verification and validation plans for the system as a whole. The exit criteria for this phase shall be: trade-off analysis results; program objectives and execution plan (including processes and metrics); program constraints; cost and critical path drivers; program risk assessment; technology readiness assessment; requirements functional allocation to a hardware and software top-level design (functional architecture); system specification updates; system architecture updates; subsystem specifications; draft development specifications; draft interface specification; R&M analysis results; R&M methodology; approved product support plan; and successful System Functional Review (SFR) that establishes the

PR: FD2060-19-00038 PWS 9

system functional baseline. The contractor shall document the work effort in a system design engineering report IAW the IMS. Work products shall contain no more than one technical error and no more than five typographical errors per submittal. [CDRL A001, DI-MISC-80711A, Scientific and Technical Reports]

4.3.3.1 System Functional Review (SFR): The contractor shall conduct a multi-disciplined technical SFR to ensure that: the system functional requirements are captured in system specifications; all required system performance is fully decomposed and traced to lower-level subsystem functionality that define hardware and software requirements; and the system functional design is consistent with program cost, schedule, risk, and other system constraints.

The SFR shall demonstrate consistency between the system requirements, system specification, system/subsystem specifications, the recommended system solution, and available technologies.

SFR approval is required prior to proceeding to preliminary design. The contractor shall prepare an SFR agenda and submit final briefing charts one week prior to the review. The contractor shall develop and deliver SFR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.3.2 Safety Assessment Report: A Safety Assessment Report shall be submitted 15 calendar days prior to the preliminary design review. The Government approval/comments will be provided within 30 business days after submittal. Contractor format is acceptable. Additional Safety Assessment Reports shall be submitted if there are any additional changes after first approval. [CDRL A005, DI-SAFT-80102C/T, Safety Assessment Report]

4.3.4 Preliminary Design: The contractor shall follow a structured IPPD systems engineering process to accomplish AN/ALQ-172 (LRU-2 and LRU-3) preliminary design. The contractor shall allocate the functional architecture to system functions and sub-functions, across all configuration items, each with an associated set of performance and design requirements addressing all identified requirements. The derived requirements shall be stated in sufficient detail for allocation to AN/ALQ-172 (LRU-2 and LRU-3) hardware, software, and interface.

The derived requirements shall be traceable, through the analysis by which they were derived, to the system requirement they are designed to fulfill. The output of this analysis will be allocated performance and other limiting requirements to all functional levels documented in the first set of subsystem and component product performance descriptions. The contractor shall establish an allocated baseline that includes all functional and interface characteristics allocated from the system, interface requirements with other critical items (CI), and design constraints. The allocated baseline shall describe the verification required to demonstrate the achievement of specified functional and interface characteristics, with emphasis on critical concept components.

The contractor shall accomplish a Failure Mode Effects and Criticality Analysis, a Failure Tree Analysis, and a Reliability-Centered Maintenance (RCM) Analysis on the allocated baseline.

The exit criteria for this phase shall be: trade-off analysis results; program objectives and execution plan (including processes and metrics); program constraints; cost and critical path drivers; program risk assessment; updates to the top-level functional architecture design; system specification updates; subsystem specifications; requirements allocation to hardware and software development specifications for all configuration items; interface specifications (physical and functional); R&M analysis updates; R&M predictions; test method for verification

PR: FD2060-19-00038 PWS 10

of requirements; CI configuration management plan; production support plan update; and successful Preliminary Design Review (PDR) that establishes the allocated baseline. The contractor shall document all the work effort in a preliminary design engineering report IAW the IMS. [CDRL A001 DI-MISC-80711A, Scientific and Technical Reports]

4.3.4.1 Preliminary Design Review (PDR): The contractor shall conduct a multi-disciplined technical PDR to ensure that: each function in the functional baseline has been allocated to one or more system configuration items; the allocated hardware and software requirements are completely captured in performance specifications for each configuration item of the preliminary design (allocated baseline); subsystem and configuration item requirements trace to system design; and the system preliminary design is consistent with program cost, schedule, risk, and other system constraints. PDR approval is required prior to proceeding to detailed design. The contractor shall prepare a PDR agenda and submit final briefing charts one week prior to the review. The contractor shall develop and deliver PDR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.5 Critical Design: The contractor shall follow a structured IPPD systems engineering process to accomplish AN/ALQ-172 (LRU-2 and LRU-3) detailed design. The contractor shall accomplish detailed design of all hardware and software components, each with an associated set of performance and design requirements addressing identified requirements. The contractor shall accomplish detailed design of the entire system, to the subsystem/component level, to demonstrate that the allocated baseline hardware, software, and system requirements are satisfied by the design. The contractor shall develop drawings and other documentation required for building components, subsystems, and the AN/ALQ-172 (LRU-2 and LRU-3). The contractor shall accomplish testing and validation of critical system components and plan for the integration and testing of all components. The contractor shall develop a Level of Repair Analysis and a Maintenance Task Analysis. The contractor shall update the projected system reliability based on demonstrated reliability rates. The contractor shall project improved system availability based on the detailed design reliability, maintainability, supportability, and produce-ability. The contractor shall identify critical manufacturing processes that impact key performance characteristics and determine their capability to meet design tolerances. The exit criteria for this phase shall be: trade-off analysis results; program objectives and execution plan (including processes and metrics); program constraints; cost and critical path drivers; program risk assessment; updates to the top-level functional architecture design; system specification updates;

subsystem specifications update; function and sub-function development specifications update;

interface specifications (physical and functional) update; hardware and software development specifications update for all configuration items; R&M analysis updates; R&M predictions updates; critical CI test results; updated test methodology (performance, qualification, environmental, etc.); updated Interface Control Documents (ICDs); CI configuration management plan update; production support plan update; AN/ALQ-172 (LRU-2 and LRU-3) minimum MTBF for LRU-2 of 1,600 hours and LRU-3 of 2,600 hours; AN/ALQ-172 (LRU-2 and LRU-3) maximum MTTR of four hours, excluding TPS run time; and successful Critical Design Review (CDR) that establishes the product baseline (built-to). The contractor shall document all the work effort in a detailed design engineering report IAW the IMS.

[CDRL A001, DI-MISC-80711A, Scientific and Technical Reports]

PR: FD2060-19-00038 PWS 11

4.3.5.1 Critical Design Review (CDR): The contractor shall conduct a multi-disciplined technical CDR to ensure that: subsystem detailed design correctly and completely implement all system requirements allocated to the subsystem; each hardware and software product in the product baseline has been captured in the detailed design documentation to enable hardware fabrication and software coding of configuration items; upward and downward traceability of final subsystem requirements to final system detailed design; the system under review can proceed into system fabrication and test; and the detailed design is consistent with program cost, schedule, risk, and other system constraints. CDR approval is required prior to proceeding to fabrication and test. The contractor shall prepare a CDR agenda and submit final briefing charts one week prior to the review. The contractor shall develop and deliver CDR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. [CDRL A003, DI-ADMN- 81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.6 Prototype Fabrication: The contractor shall fabricate, assemble, code (using the product baseline build-to documentation), and deliver fully functional, operational, compatible prototypes as the contract defined quantity of FFFI AN/ALQ-172 (LRU-2 and LRU-3) prototypes. The contractor shall maintain configuration control of the product baseline build-to documentation to accurately reflect final prototype configuration. The contractor shall screen all the electrical/electronic components selected in the redesign of the AN/ALQ-172 (LRU-2 and LRU-3) to eliminate any premature Diminishing Manufacturing Sources and Material Shortages (DMSMS). The AN/ALQ-172 (LRU-2 and LRU-3) and all repairable sub-assemblies shall be marked with permanently attached machine-readable “unique identifier” or “UID”. Military Standard 130M (MIL-STD 130M) provides further clarification and increased insight and guidance for the implementation of machine-readable information (MRI) processes for item identification marking and facilitating automatic data capture. Official AF guidance is provided in: DFARS Clause 252.211-7003.

4.3.6.1 Prototype Delivery & Test Readiness Review (TRR): The contractor shall deliver four fully functional, operational, and compatible form, fit, function, and interface LRU-2 and LRU-3 prototypes to the Government. The contractor shall conduct a multi-disciplined technical TRR to ensure that: planned tests are traceable to program requirements; all planned preliminary, informal, functional, unit level, subsystem, system, and qualification tests have been conducted;

the test objectives, test methods and procedures, scope of tests, and safety issues have been properly identified and documented; required test resources have been properly identified and coordinated to support planned tests; the AN/ALQ-172 (LRU-2 and LRU-3) and applicable components subsystems and system are ready to proceed into formal test; and the fabricated prototypes are consistent with program cost, schedule, risk, and other system constraints. TRR approval is required prior to proceeding to formal test. The contractor shall prepare a TRR agenda and submit final briefing charts one week prior to the review. The contractor shall develop and deliver TRR minutes IAW the IMS. Minutes shall include all briefing materials as an attachment. Work products shall contain no more than one technical error and no more than five typographical errors per submittal. The contractor shall provide Test Requirement Documents (TRDs). The contractor shall build FFFI LRU’S prototypes with improved system availability by providing accurate Technical Order (T.O.) changes. Final version T.O. changes shall be free of technical errors and require no major re-work, as determined by the Government.

PR: FD2060-19-00038 PWS 12

The AN/ALQ-172 (LRU-2 and LRU-3) shall pass prototype testing requirements. An item that has a high level of Reliability and Maintainability (R&M), is producible, and is supportable, should achieve a high level of operational availability. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.6.2 Prototype Test: The contractor shall utilize existing/developed test equipment to test the FFFI AN/ALQ-172 (LRU-2 and LRU-3) prototypes in accordance with the approved test methodology to verify and validate that operational performance and system availability requirements are met. The contractor shall accomplish individual configuration item, integrated subsystem, and assembled AN/ALQ-172 (LRU-2 and LRU-3) prototype testing. The contractor shall demonstrate, according to the verification and validation plans, the physical, electrical, software, and other characteristics of the individual configuration items to be integrated. The contractor shall demonstrate, according to the verification and validation plans, integrated subsystem hardware and software performance compliance to their respective subsystem design requirements specifications. The contractor shall demonstrate, according to the verification and validation plans, integrated AN/ALQ-172 (LRU-2 and LRU-3) hardware and software system performance compliance to the system design requirements specification IAW the IMS. The FFFI LRU’S prototypes shall successfully pass subsystem testing requirements with no more than two retests at the next higher assembly. [CDRL A006, DI-NDTI-80603A, Test Procedure], [CDRL A007, DI-NDTI-80809B Test Report]

4.3.7 System Level Test: The contractor shall develop an AN/ALQ-172 system level test procedure to demonstrate form, fit, function and interface compliance of the AN/ALQ-172 R- 2247 (LRU-2 and LRU-3) prototypes in the AN/ALQ-172 system and submit the system level test procedure for Government approval. The contractors shall conduct system level tests on the redesigned AN/ALQ-172 (LRU-2 and LRU-3) prototypes in accordance with the Government approved test procedure and document the results in a system level test report. The Government reserves the right to witness all testing performed by the contractor. The contractor shall perform baseline system level tests in the Electronic Warfare Avionics Integration Support Facility (EWAISF) with the existing AN/ALQ-172 (LRU-2 and LRU-3) prior to inserting the redesigned AN/ALQ-172 (LRU-2 and LRU-3) into the AN/AN/ALQ-172 system IAW the IMS. The results of both tests shall be compared to demonstrate that there are no impacts to the AN/ALQ-172 system. Work products shall contain no more than one technical error and no more than five typographical errors per submittal. [CDRL A006, DI-NDTI-80603A, Test Procedure], [CDRL A007, DI-NDTI-80809B Test Report]

4.3.8 Acceptance Test Procedure (ATP): The contractor shall develop a detailed acceptance test procedure for the AN/ALQ-172 (LRU-2 and LRU-3) and submit the acceptance test procedure for Government approval. The contractor shall conduct acceptance test on each prototype AN/ALQ-172 (LRU-2 and LRU-3) in accordance with the approved ATP testing and submit a test report for each prototype AN/ALQ-172 (LRU-2 and LRU-3) for Government approval following testing. The contractor shall deliver the prototype AN/ALQ-172 (LRU-2 and LRU-3), following successful acceptance test, for formal Air Force test IAW the IMS. Work products shall contain no more than two technical error and no more than five typographical errors per submittal. Successfully pass prototype testing requirements with no more than two retests at the

PR: FD2060-19-00038 PWS 13

next higher assembly. [CDRL A006, DI-NDTI-80603A, Test Procedure], [CDRL A007, DI- NDTI-80809B Test Report]

4.3.9 Qualification Testing: The contractor shall develop a qualification test procedure (QTP) based on MIL-STD-810 to qualify the AN/ALQ-172 (LRU-2 and LRU-3) and submit the QTP for Government approval. The contractor shall conduct qualification tests on the AN/ALQ-172 (LRU-2 and LRU-3) in accordance with the Government approved QTP and document the results in a qualification test report. Qualification-by-similarity shall be considered where applicable. The Government reserves the right to witness all testing performed by the contractor.

The contractor shall submit a test report for Government approval following testing IAW the IMS. Successfully pass prototype testing requirements with no more than two retests at the next higher assembly. [CDRL A006, DI-NDTI-80603A, Test Procedure], [CDRL A007, DI-NDTI- 80809B Test Report]

4.3.10 Government Testing: The prototype of the redesigned AN/ALQ-172 (LRU-2 and LRU-3) configuration will be tested at the EWAISF at Robins AFB GA, the Robins AFB depot, and ground/flight tested on a B-52H aircraft at a main operating base to ensure full system level interoperability and operational performance compliance. The contractor shall provide technical support for Government testing efforts, as required. Government testing of the prototypes will be performed using existing and/or new/modified procedures and new technical orders. The prototypes must successfully pass testing requirements with no more than two retests at the next higher assembly.

4.3.11 Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA): The contractor shall conduct a multi-disciplined FCA/PCA of the final Government tested, redesigned prototype AN/ALQ-172 (LRU-2 and LRU-3) within at least two months prior to delivery of prototypes to ensure that: the actual performance meets the functional specification requirements (derived from the requirements specifications) documented in the Functional, Allocated, and Product Baselines; the configuration controlled product baseline (build-to) documentation reflects the physical item tested; and the system functional design is consistent with program cost, schedule, risk, and other system constraints. The contractor shall update, as required, the technical data package to reflect any changes that occur during test. The contractor shall prepare a FCA/ PCA agenda and submit final presentation material one week prior to the review. The contractor shall develop and deliver a FCA/PCA report that documents audit findings IAW the IMS. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes], [CDRL A008, DI-SESS-81022D, Configuration Audit Summary Report]

4.3.12 Hardware Deliverables

The contractor shall deliver all prototype units, test fixtures and special test equipment that was developed, fabricated and tested under this work effort to AFLCMC/WNY.

4.3.13 Software Deliverables

The contractor shall deliver all software, source code and executable code, with applicable documentation, that is designed and/or developed under this effort to AFLCMC/WNY.

PR: FD2060-19-00038 PWS 14

4.3.13.1 Test Program Software (TPS) Development: The contractor shall develop LRU level software updates on the Government owned, currently-fielded test equipment. The performance of the new LRU-2 and LRU-3 EMTS TPS shall isolate and diagnose to the same level as the legacy LRU-2 and LRU-3 EMTS TPS.

4.3.13.2 TPS Design: The contractor shall deliver all software and source code developed under this effort. The contractor shall deliver a Software Development Plan (SDP), Software Requirements Specification (SRS), Interface Requirements Specification (IRS), Software Design Description (SDD), Software Test Description (STD), Software Product Specification (SPS), Software Version Description (SVD), Software User Manual (SUM), Computer Software Product (CSP), Acceptance Test Procedure (ATP), and Acceptance Test Report (ATR).

[CDRL B001, DI-IPSC-81427B, Software Development Plan (SDP)], [CDRL B002, DI- IPSC-81433A, Software Requirements Specification (SRS)], [CDRL B003, DI-IPSC- 81434A, Interface Requirements Specification (IRS)], [CDRL B004, DI-IPSC-81435A, Software Design Description (SDD)], [CDRL B005, DI-IPSC-81439A Software Test Description (STD)], [CDRL B006, DI-IPSC-81441A, Software Product Specification (SPS)], [CDRL B007, DI-IPSC-81442A Software Version Description (SVD)], [CDRL B008, DI- IPSC-81443A Software User Manual (SUM)], [CDRL B009, DI-IPSC-81488, Computer Software Product (CSP)], [CDRL A006, DI-NDTI-80603A, Test Procedure], [CDRL A007, DI-NDTI-80809B Test Report]

4.3.13.3 New Test-Fixtures: Additional test fixtures if required, shall be developed and delivered to the Government while maximizing the use of the existing Interface Test Adapters.

The contractor shall deliver test fixture Developmental Drawings & Associated Lists and product drawings at the end of this effort. [CDRL A009, DI-MGMT-81453B, Data Accession List]

4.3.14 Technical Orders

The contractor shall refer to Technical Manual Contract Requirements (TMCR) for technical orders impacted by any redesign effort associated with the AN/ALQ-172 (LRU-2 and LRU-3).

All submissions will be IAW the Contract Data Requirements List (CDRL) and IMS. [CDRL A00A, TM-86-01P (TMCR)], [CDRL A00B, DI-CMAN-80642C, Notice of Revision]

4.3.15 Data

4.3.15.1 Hardware Requirements Specifications: The contractor shall update the hardware requirements specifications for all items developed under this effort, as necessary. This is to include developmental specifications and product specifications. All submissions will be IAW the IMS. [CDRL A002, DI-IPSC-81431A, System/Subsystem Specification]

4.3.15. Engineering Data: The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design

PR: FD2060-19-00038 PWS 15

engineering effort or recourse to the original design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the following American Society of Mechanical Engineers (ASME) standards:

ASME Y14.100-2017, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings Models and Associated Lists (Engineering Data) under this contract.

Data set classification code marking IAW Appendix F of ASME Y14.100-2017 is required.

CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752) The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16. [A00C DI- SESS-81000E/T] The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to CDR. [DI-DRPR- 81961]

4.3.15.3 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

4. 3.15.3.1: Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

4.3.15.3.2: TDP review requirements and schedules.

4.3.15.3.3: TDP delivery requirements and schedules.

4.3.15.3.4: Contractor’s drafting practices/procedures/TDP drawing formats.

4.3.15.3.5: The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

4.3.15.3.6: The role of subcontractors and vendors who may deliver TDP documents under this

PR: FD2060-19-00038 PWS 16

4.3.15.3.7: The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

4.3.15.3.8: Digital Technical Data Package deliverables.

Note: The Engineering Data Guidance Conference may be held in conjunction with other meetings or conferences. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI-ADMN-81250B, Conference Minutes]

4.3.16 In-Process Review (IPR) of the TDP: The contractor shall host, support, and co-chair (at his facility) an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (e.g., PDR, CDR). The contractor shall notify AFLCMC/WNY and 408 SCMS and AFLCMC/EZGEM a minimum of 30 working days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, e.g., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. Minutes shall include all briefing materials as an attachment. [CDRL A003, DI-ADMN-81249B, Conference Agenda], [CDRL A004, DI- ADMN-81250B, Conference Minutes]

4.3.16.1 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program, except for subassemblies where the supplier has asserted data rights or an unwillingness to develop and deliver a full TDP.

4.3.16.2 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

4.3.16.2.1: All engineering changes shall be incorporated into the applicable engineering data within 90 working days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

4.3.16.2.2: All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

PR: FD2060-19-00038 PWS 17

4.3.16.2.3: All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all EO’s generated as a result of the preliminary data review.)

4.3.17 Restrictions on Use of Proprietary or Sole Source

The contractor shall not recommend proprietary or sole source components unless there is no alternative available. Any proprietary or sole source components recommended shall be explicitly identified at status and design reviews. The contractor must obtain written permission from the Government contracting officer prior to incorporation of proprietary data/components, etc. and submitted under the proper DFARS clause (DFARS 252.227-7).

4.3.17.1 Software/Data Products: The contractor shall not develop any proprietary software or data product in the performance of the actions required by the contract. Any software owned by the Government and provided by the Government to the contractor shall remain the property of the Government after modification by the contractor. Any software purchased or developed to complete, or that contributes to the completion, of the contract shall be the property of the Government. Said software shall be documented and delivered to the procuring agency within ten days of a specific written request from the PCO, and in no event, later than the completion/termination of the contract.

4.3.17.2 Government Data Rights: The contractor shall provide the Government unlimited or unrestricted rights to all contractor developed technical data, drawings and software developed exclusively with Government funding for this contract.