Attachment 0001 Technical Requirements Document.pdf

Exhibit A SPRBL1-24-R-0007 Page 1 of 17 Issue: 27 October 2023

Statement of Work

(TECHNICAL REQUIREMENTS DOCUMENT)

Twelve Spare Parts To Support

AN/AVR-2B (V)

Laser Detect Set (LDS)

Spares

Exhibit A SPRBL1-24-R-0007 Page 2 of 17

TABLE OF CONTENTS

1 APPLICABLE DOCUMENTS

2 CONFIGURATION BASELINE

3 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

REQUIREMENTS

4 CHEMICAL AGENT RESISTANT COATING (CARC)

5 PACKAGING

6 ITEM MARKING

7 TESTING AND QUALITY ASSURANCE

8 CONTRACT SECURITY REQUIREMENTS

9 ADDITIONAL REQUIREMENTS

10 CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

Exhibit A SPRBL1-24-R-0007 Page 3 of 17

1 APPLICABLE DOCUMENTS

The Contractor shall report any conflicts within this TRD, or documents referenced herein to the Procuring Contracting Officer (PCO) for resolution.

Military and Federal Documents MIL-STD-3018 Parts Management (15 OCT 2007) MIL-STD-129R Military Marking for Shipment and Storage (18 FEB 2014) MIL-STD-130N, W/ Change 1 Identification Marking of U.S. Military Property (17 DEC 2007) MIL-STD-2073-1E Military Packaging (23 MAY 2008) DD Form 1692 Engineering Change Proposal (ECP) DD Form 1695 Notice of Revision (NOR) CDRL A003 Request for Variance (RFV) Defense Federal Acquisition Regulations Supplement (DFARS) 252.211-7006

Radio Frequency Identification (RFID) (NOV 2005)

SP L31-0034, Rev. B AN/AVR-2B(V) Laser Detecting Set Performance Specification (13 April 2004)

SF328-18 Standard Form 328 Certificate Pertaining to Foreign Interests OMB No. 0704-0579

SPI AG00000601 Special Packaging Instruction SPI AG00000655 Special Packaging Instruction Commercial Documents EIA-649-C Configuration Management Standard ANSI/TA-STD-0016 Diminishing Manufacturing Sources and Material Shortages

(DMSMS) Management Plan ASME) Y14.44-2008 Reference Designations for Electrical and Electronics Parts and

Equipment ISPM 15 Internation Standard for Wood Packaging SD-22 DMSMS Guidebook ISO 9001:2000 Quality Management Standard Security Documents DoDM 5200.01, Vol 2

DoD Information Security Program: Marking of Information

DoDI 5200.48 Controlled Unclassified Information (CUI) Security Classification Guide (SCG) Security Classification Guide for U.S. Army Version of Aircraft

Survivability Equipment (ASE) (15 MAR 2016)- (See Appendix A)

2 CONFIGURATION BASELINE

The applicable Configuration Baselines (CB), for the listed Configuration Item (CI) and/or Computer Software Configuration Item (CSCI), are as listed in the table below.

Exhibit A SPRBL1-24-R-0007 Page 4 of 17

NSN Nomenclature Part Numbers 5860-01-511-8345 Sensor Unit (SU), SU-130B L31-20000 5865-01-514-2857 Signal Comparator Module (SCM), CM- 493B L31-30000 5998-01-555-6985 Circuit Card Assembly (CCA), SU Detector L31-22103 5998-01-555-7243 CCA, Sensor Processor Board L31-22204 6130-01-560-1699 Power Supply, SU SCD L31-0039 5998-01-555-7358 CCA, SCM Connector Board Assembly L31-34003 5998-01-555-7075 CCA, SCM Processor Board L31-35003 5998-01-555-7083 CCA, SCM Power Supply L31-36003 2510-01-598-1459 Housing, Sensor unit w/window L31-24000 6150-01-556-4305 Internal Cable Harness, SU L31-32300 6150-01-556-4310 Cable Assembly, SCM L31-23200

5810-01-561-3121 Electronic Key Management System L31-38000

2.1 Configuration Management (CM)

The contractor shall implement and maintain a CM program (item identification, control, audit and status accounting) that shall define the functional and physical characteristics of the products throughout the production effort. The Product Definition Information, which describes a product’s performance, functional and physical attributes, requirements, and design information (specification, drawings, design descriptions, software, interfaces, and interfaces with other products), shall be specified by the Contractor’s Item Part Number (CIPN).

2.2 CIPN Configuration Baseline (CB)

The Contractor’s Item Part Number (CIPN), as defined by the Contractor’s specifications, drawings, catalog page, etc, at the time of award of this contract, shall form the Configuration Baseline for this acquisition. Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) and any subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO).

The contractor shall establish a system for managing the configuration changes to the CIPN baseline. The only changes or departures from the configuration baseline (CB) permitted are those which are submitted to and approved, and which are made applicable to the contract by the PCO.

2.3 Application Management

In performing Application Management, the Government must assess the impact of design changes to the Configuration Item. The Government is the Configuration Management authority on application management for all external applications and for all Major changes that affect the Item Part Number (CIPN). Major and Minor Changes (alias Class I & Class II respectively) shall be classified IAW paragraph 5.3.1.3 & Table 4 of

EIA-649-C.

Exhibit A SPRBL1-24-R-0007 Page 5 of 17

2.4 Departures from CB

Changes that affect the CIPN conditions cited in EIA-649-C shall be submitted for Government review or notification in accordance with this TRD. Upon receipt of notification, the Government will review the impact of the change.

2.4.1 Engineering Change Proposal (ECP)

The Contractor shall use an Engineering Change Proposal (ECP) to document changes to the approved configuration documentation. ECP includes both the engineering change and the supporting documentation by which the change is described and suggested. An ECP describes changes to the baseline and associated configuration documentation that is affected by the proposed engineering change and testing required to verify proper implementation and function of the ECP. The Contractor shall not incorporate product improvements until directed by the Government. Major Change Requests shall be submitted for Government approval as Class I ECP’s IAW CDRL A001, DI-SESS-80639E. Minor Change Requests shall be processed for approval IAW the Contractors CM procedures and require Government concurrence in the classification.

An approved change to the design of the CIPN must be verified to ascertain that the CIPN has achieved the functional attributes and requirements specified in the baselined Product Definition Information (CIPN) and that it is adequate for its intended purposes. The Government is not obligated to accept any CIPNs that no longer meet the Government’s requirements as established by the CIPN at the time of contract award.

2.4.2 Notice of Revision (NOR)

The Contractor shall prepare a NOR if change is made to technical documents. Each NOR shall be submitted to the Government for approval, and the Contractor shall not incorporate such changes until directed by the Government. All NOR shall be IAW CDRL A002, DI-SESS-80642E.

2.4.3 Request for Variance (RFV)

The Contractor shall prepare a RFV if change to specified configuration of specific number of units or specific period of time is made. Each RFV shall be submitted to the Government for approval, and the Contractor shall not incorporate such changes until directed by the Government. All RFDs/RFWs shall be IAW CDRL A003, DI-SESS-80640E.

3 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

REQUIREMENTS

3.1 DMSMS Definitions

For the purpose of this section, key definitions are provided in the definition paragraph of ANSI/TA-STD-0016 and DMSMS Guidebook, SD-22.

3.2 DMSMS Management Program

The Contractor shall establish and execute a DMSMS management program IAW this TRD and ANSI/TA- STD-0016 for the period of performance of this contract. The program shall address how the Contractor will identify or predict DMSMS Issues over the life of the contract to assess potential risk, develop an obsolescence mitigation strategy to determine the most cost-effective solution to DMSMS Issues. The Contractor shall also include a description of their process and procedures for selecting standard or commonly

Exhibit A SPRBL1-24-R-0007 Page 6 of 17 available parts and parts with more than one source of supply. The Contractor shall ensure its subcontractors adhere to the DMSMS/Obsolescence requirements of this TRD. Design changes shall be made in accordance with the Configuration Management requirements of this contract. The Contractor shall also include procedures for sharing information with Government Industry Data Exchange Program (GIDEP) and participating with the government in an Obsolescence Working Group (OWG).

3.3 DMSMS Management Plan

The Contractor’s plan to conduct the DMSMS/Obsolescence program shall be documented in a DMSMS Management Plan (DMP) prepared and delivered IAW CDRL A004 DI-MGMT-81948 and this TRD.

ANSI/TA-STD-0016 may be used as a guide. The Contractor is encouraged to make use of or tailor an existing in-house corporate DMSMS or Obsolescence management plans. The Contractor’s DMP shall include a description of their process and procedures for selecting parts and whether they utilize a Preferred Parts List (or equivalent) to accomplish this. Regarding predicting DMSMS Issues, the DMP shall identify any predictive tools or services which the Contractor intends to use to accomplish this. The DMP shall also document the procedures for both participation in the Government Industry Data Exchange Program (GIDEP) and Obsolescence Working Group (OWG) meetings.

3.4 Obsolescence Working Group (OWG)

The Contractor shall attend and participate at government Obsolescence Working Group (OWG) meetings as requested by the government. The purpose of the OWG is to review open DMSMS cases, the Contractor’s most recent DMSMS CDRL deliverables, and other DMSMS issues suggested by either the Contractor or the government. The OWG will meet at the Contractor’s facility, at government location, or via teleconference or others virtual means (e.g., Microsoft Teams). The government will establish the dates for each meeting and will be responsible for publishing the meeting agenda and minutes. The first OWG meeting shall occurring no later than 90 days after contract award (DAC) and shall meet bi-annually thereafter unless otherwise notified by the government.

3.5 DMSMS/Obsolescence Bill of Materials (BOM)

The Contractor shall submit and update semiannually a Bill of Material (BOM) in accordance with the CDRL A005 DI-MGMT-82274 and this TRD. The BOM shall include the system breakdown to the part level for all electronic, electrical, and electro-mechanical parts, assemblies and software components in the design. The BOM shall also include data entries for the known or projected End of Life (EOL) and case status, if a DMSMS case has been established for the item.

In the special case of commercial or COTS items where the design owner will not relinquish configuration control of the design to the government, the Contractor shall work with the design owner to forecast when the item will no longer be available and provide a single line entry on the BOM for the item.

In the case of a privately developed item which does not meet the definition of a commercial item and for which the government will be assuming configuration control of the item and funding engineering changes, the Contractor shall submit the BOM to the component-level. The Contractor shall ensure that the BOM accurately reflects the current approved design IAW the Contractor’s DMSMS management plan and contract configuration management procedures.

Exhibit A SPRBL1-24-R-0007 Page 7 of 17

3.6 DMSMS Alerts

For the weapon system under DMSMS management, the Contractor will monitor the parts and software identified on the BOM for DMSMS Issues. Should a documented or predicted DMSMS Issue be identified, the Contractor will submit an Obsolescence Alert Notice IAW the CDRL A006 DI-MGMT-81941 and this TRD.

3.7 Case Management

Concurrent with the delivery of the Alert, the Contractor shall establish a case to investigate and resolve it. Case management efforts shall commence when case is established and shall include Contractor efforts to analyze the issue and its impact and develop candidate solutions. Case management efforts will be tracked and managed by the Contractor. Cases will commence when an obsolescence issue is verified. Case research may include Contractor efforts to analyze the issue and its impact and develop candidate solutions accompanied with supporting rationale for its selection, its estimated cost avoidance, and a timeline for implementation. Open cases shall be discussed at the OWG.

3.8 DMSMS Health Report

As part of the DMSMS program the Contractor shall document the effectiveness of the Contractor’s DMSMS management program by assessing the overall health of the product design from a DMSMS perspective achieved via analysis of the current BOM. The DMSMS Health Assessment Report will aid in determining the scope of DMSMS issues within systems and subsystems and determining optimal mitigation strategies. The contract shall submit this report IAW CDRL A007 DI-MGMT-82273 and this TRD. The DMSMS Health Report will include roll-ups of DMSMS Issues at each succeeding hierarchical assembly level up to the weapon system top assembly. The Health Report shall also include any planned or recommended Technology Refreshment or Technology Insertion events. Key details of this deliverable shall be discussed at OWG.

3.9 DMSMS Costs

The Contract cost for DMSMS program management to include case management activities, CDRL submissions, and OWG participation and support shall be not separately priced (NSP) in the Contractor’s RFP submittal and included in the basic contract at time of award.

The Contractor may submit an ECP for the purpose of implementing the recommended solution. In addition, the PCO may also ask that the Contractor identify any cost changes to any production and/or maintenance CLINs affected by this solution.

Exhibit A SPRBL1-24-R-0007 Page 8 of 17

4 CHEMICAL AGENT RESISTANT COATING (CARC)

4.1 Paint Colors

X = Applicable Location Color

Color No.

FED-STD 595

Exterior – Lusterless Green Green 383 34094

Exterior – Camouflage – Desert Colors Green 383 34094 Black 37030 Tan 686A 33446 Green 24533 Brown 383 30051 White 27875

Interior Shelter Surfaces Green 24533

(White or Green) White 27875 Other: Area enclosed by dotted line Green (Olive

Drab) 34087

X Exterior- Touch Up Green 34031

4.2 Special Instructions

X = Applicable Location or Part Instruction

Exhibit A SPRBL1-24-R-0007 Page 9 of 17

5 PACKAGING

Military Packaging shall be in accordance with MIL-STD-2073-1E, SPI AG00000601, and/or SPI AG00000655, as applicable.

5.1 Wood Packing Material: N/A

Wood Packaging Material in compliance with ISPM 15, Regulation of Wood Packaging Material in International Trade. Wood packing material includes pallets. See DLAD 52.247-9012 Requirements for Treatment of Wood Packaging Material (WPM).

5.2 Military Packaging

DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

Military Packaging shall be in accordance with MIL-STD-2073-1E, SPI AG00000601, and/or SPI AG00000655, as applicable.

DS7029 - DS7033 LEGEND

Qty Quantity Prot Req Protection Required PKG-REF Packaging Reference (Military/Federal Specification or Standard) SPI Special Packaging Instruction LPK Level of Packing QUP Quantity per Unit Pack ICQ Intermediate Container Quantity Pkg Reqmt Codes Packaging Requirement Codes when PKG-REF cites MIL-STD-2073 The below codes are for special markings:

PC Project Code WG Warranty/Guarantee SL Shelf Life BC Bar Code FMS Foreign Military Sales

DS7029 - DS7033

NSN Prot Req PKG-REF or SPI LPK QUP ICQ Special Markings

Pkg J. J J J J J J J J J Reqmt I. II. III. IV. V. VI. VII. VII.a IX X

Exhibit A SPRBL1-24-R-0007 Page 10 of 17

Codes (MP) (CD) (PM) (WM) (CD) (CT) (UC) (IC) (PK) (SM) 2510-01-598-

Military MIL-STD-2073-1E B 1 - 31 1 00 00 NA B ED 00 - 00 BC

5860-01-511-

Military SPI# AG00000655 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 00 BC

5865-01-514-

Military SPI# AG00000655 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 00 BC

5998-01-555-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 39 BC

5998-01-555-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 39 BC

5998-01-555-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 39 BC

5998-01-555-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 39 BC

5998-01-555-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 39 BC

6130-01-560-

Military SPI# AG00000601 B 1 ZZ Z ZZ ZZ ZZ Z ZZ ZZ - 00 BC

6150-01-556-

Military MIL-STD-2073-1E B 1 31 1 00 00 NA B BL ED - 00 BC

6150-01-556-

Military MIL-STD-2073-1E B 1 31 1 00 00 NA B BL ED - 00 BC

5810-01-561-

Military MIL-STD-2073-1E B 1 41 1 00 00 NA B ED 00 - 00 BC

Exhibit A SPRBL1-24-R-0007 Page 11 of 17

6 ITEM MARKING

6.1 Part Number Marking

Each item delivered under contract, along with each assembly, subassembly, and module, shall be legibly marked with the appropriate part number and manufacturer’s identification. Hardware such as screws, nuts, bolts, etc., need not be marked. The marking shall become permanently part of the item after it is applied, and can be applied using deformation, tag, rubber stamp with permanent characteristics, etc. The marking shall not interfere with proper operation of the item and shall have no deleterious effect on the item. Any item deemed unsuitable for marking as outlined herein shall be identified to the Contracting Officer for resolution as to marking requirement. This requirement may be entirely met by existing marking requirements contained within the drawings or specifications cited in this contract.

6.2 NSN Marking

In addition to the marking required by para 6.4 below, hardware deliverables in this contract shall be identified with its Government assigned NSN. The intent of this requirement is to ensure that using personnel can identify the circuit card or assembly when it is removed from its assembly, and when it is received from stock as a spare part. The marking can be on a paper label, placed in a location that will not harm the item. If guidance is necessary to implement this requirement, contact the Contracting Officer for guidance.

6.3 Serial Number Marking

Any item or subassembly which contains a serialization requirement shall have serial numbers applied to each item in the place provided (generally on a nameplate/serial number plate). In addition, the NSN, CAGE Code, Part Number and if space permits Contract Number shall also be applied. When applicable, the Unique Item Identification (UID) requirements, cited in this TRD, shall also apply.

The contractor shall maintain an accurate, current list of serial numbers for all manufactured items under this contract. Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. The list shall be available for inspection by the PCO or government representative at any time during the life of the contract and for a period of 3 years following the completion of the contract.

6.4 Item Unique Identification (IUID)

The Contractor shall mark all contract deliverables under this contract, ensuring all equipment meeting the IUID criteria is marked, and the applicable data is submitted to the DOD IUID Repository. The Contractor shall comply with DFARS 252.211-7003, Item Unique Identification and Valuation to provide IUID, or DOD recognized unique identification equivalent, for all applicable equipment items per the guidance called out in DFARS 252.211-7003, MIL-STD 130N, and MIL-STD 129R or current version. This requirement is effective through the life of this contract. The IUID markings are also required for embedded components in this contract. Guidance for IUID Marking of embedded components shall also be per the latest version of MIL- STD-130, and the https://www.acq.osd.mil/asda/dpc/ce/index.html website and AR 700-145. The human readable characters and the machine- readable UID symbology will be marked on the hardware. If there is not enough space to include both, the machine-readable UID shall take precedence.

The Contractor shall provide and maintain an accurate, current list of IUIDs for all manufactured items under https://www.acq.osd.mil/asda/dpc/ce/index.html

Exhibit A SPRBL1-24-R-0007 Page 12 of 17 this contract to include dates of manufacture, substitutions, shop changes, etc., in accordance with ASME Y14.100 and MIL-STD-130N or current version. The list shall be available for inspection by the PCO or other Government representative at any time during the life of this contract. The contractor shall provide this list to the government at the end of the contract.

6.4.1 Wide Area Workflow (WAWF)

The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003. Invoice and Receiving Report (Combination) is required. The WAWF website is https://wawf.eb.mil/ also the new Procurement Integrated Enterprise Environment (PIEE) system website and IUID Web Entry Site is https://www.acquisition.gov/dfars/252.232-7003-electronic-submission-payment-requests-and-receiving-reports.

6.4.2 Pricing of IUID Requirements

All efforts required by this TRD and contract, including, but not limited to, the preparation of ECPs or notification of marking deficiencies, serial number data reporting at end of contract and the actual marking of hardware, will be NSP.

6.5 Radio Frequency Identification (RFID)

Radio Frequency Identification (RFID) requirements shall be IAW the Section "F-7" clause, DFARS 252.211- 7006, of the contract. If the item(s) are to be shipped to a location deemed necessary by the requiring activity per DFARS 252.211-7006(b) (1) (ii) (B).

7 TESTING AND QUALITY ASSURANCE

7.1 Product Acceptance

The contractor shall plan, develop, implement, and/or maintain a product acceptance system that demonstrates compliance to the technical and contractual requirements. The product acceptance system shall address system and subsystem component requirement verification, in-process inspection, and final acceptance testing at all levels, including lower tier subcontractors and suppliers. End item Acceptance Test Procedures (ATPs) and equipment, including Special Inspection Equipment (SIE) and Special Test Equipment (STE), shall be validated prior to use for delivery of hardware. The Government shall be given the opportunity to participate in the validation. Changes to acceptance test procedures and/or associated equipment, vendor changes, line relocations, production disruptions, or downtime exceeding 12 months shall be reviewed by the Government for determination of re-validation requirements and shall be prepared IAW CDRL A008, DI-NDTI-80603A.

7.2 Inspection and Testing

AN/AVR-2B(V) systems submitted for delivery under this TRD shall successfully undergo inspection and testing IAW AN/AVR-2B(V) Performance Specification Rev B SP L31-0034 and/or the most recent government approved procedures and specifications. The contractor shall assure that all necessary inspections and tests are performed on completed products, and this shall include all inspections and tests, which are normally performed for the equipment on order. The contractor shall perform any inspections and tests (including visual/mechanical inspections and functional tests) required to satisfy the form, fit, and function requirements of the contract.

Upon a failure of inspection and test, the Government and DCMA will be notified electronically within 24 hours of the event. Should a failure occur on a subsequent test, the contractor shall be liable for repair of each

Exhibit A SPRBL1-24-R-0007 Page 13 of 17 and every unit exhibiting that defect from the previous conduct of inspection and test to meet the AN/AVR- 2B(V) Performance Specification. The inspection requirements called for in this TRD are to be used as a guide or goal. In the event of a conflict with the AN/AVR-2B(V) Performance Specification, the inspection requirements, frequency, and procedures listed in the AN/AVR-2B(V) Performance Specification will take precedence.

7.3 Failure Notifications

The Contractor shall notify the Government via electronic means of any contractor, subcontractor, or supplier qualification test failures and factory acceptance test failures, or any safety related failures within 24 hours of contractor awareness of the failure. Government Product Assurance personnel shall be notified prior to the contractor's conducting Failure Review Boards (FRBs) for the determination of failure cause and corrective actions that are required. The Government may choose to be a member of these FRBs and all FRBs held for failures.

7.4 Control of Non-Conforming Material

Decision to accept nonconforming material (variances from Contractor drawings and specifications) classified as major will require Government COR approval via Material Review Board (MRB) or Request for Deviation (RFD) process. The Contractor shall use its Material Review Board (MRB) process to classify, document, evaluate, and recommend disposition of nonconforming material with Government oversight. Standard repair procedures approved with Government concurrence authorized for use. When non-conforming material is produced, the Contractor shall perform root cause analysis and corrective actions to determine the cause and improve the processes or materials. The Contractor shall allow the local Quality Assurance Government Representative (QAR) to oversee the MRB process and shall notify the local (QAR) 5 days prior to the scheduled MRB. Nonconforming material classified as major shall not be given a disposition of “use as is” or “repair” through Contractor actions without contracting office approval of an RFV. Nonconforming material classified as minor by the MRB and verified by the local Government Representative is allowed without a formal RFV. The definition of a minor nonconformance is a nonconformance which does not adversely affect any of the following: Health and Safety, Performance, Interchangeability, Reliability, or Maintainability, Effective use of operation, Weight or Appearance (when a factor). Multiple non-conformances classified as minor are highly discouraged. The Contractor shall control the identification, documentation, evaluation, disposition, and segregation of non-conforming products. The Contractor shall upon discovery, immediately notify the Government Representative (QAR) and the COR of any nonconforming material that exists in previously delivered products. Notification shall include a description of the suspected nonconforming material, potential risk or product impact, contract number, Part Number, NSN, affected serial numbers, and/or lot numbers when applicable. Final decisions regarding acceptance of non-conforming material/supplies shall be solely the prerogative of the Government. When non-conforming material is accepted, consideration may be required. Grounds for consideration shall be determined on a case-by-case basis.

7.5 Quality Assurance

The Contractor shall maintain a Quality Assurance System IAW Federal Acquisition Regulation (FAR) Clause 52.246-2 and shall execute an internal quality system per an ISO 9001 and AS91000 certified process or equivalent, to ensure production hardware is manufactured to a high level of product integrity, reliability and repeatability, and is consistently compliant to contract and System Specification requirements. The Contractor shall conduct a complete review of the contract requirements to identify all test and inspection

Exhibit A SPRBL1-24-R-0007 Page 14 of 17 resources necessary for assuring product integrity and ensure that the latest revisions of drawings, specifications, work instructions, inspection/test instructions, and other documents required to satisfy the contract are utilized in production, inspection, and test. The contractor shall maintain records of all inspections, tests, and materials/products to demonstrate that the quality approach satisfies contract requirements, as well as maintain procedures for handling, storage, preservation, packaging, and shipping to protect the quality of products and prevent damage, loss, deterioration, degradation, or substitution of products. The Contractor shall flow down all quality requirements to Subcontractors as they apply to procured material and services. The contractor shall monitor the effectiveness of their quality system and continually improve quality processes. The Government reserves the right to examine or audit the Contractor's Quality Management System and any manufacturing/production processes.

8 CONTRACT SECURITY REQUIREMENTS

REFER to the Security AT/OPSEC Appendix to the TRD. See Appendix B.

9 ADDITIONAL REQUIREMENTS

9.1 TAV-C Requirements for accounting and reporting Government Furnished Property/Equipment

(GFP/GFE)

Army Materiel Command (AMC) and its units use TAV-C capability in its logistics management program (LMP) to account for Government furnished equipment, materiel, or property (GFE/M/P) placed in the possession of contractors to support contracts for: 1) repair, modification, or upgrade work; 2) materials held for stock, store and issue (SSI), or 3) new production. Accounting records within LMP for this inventory are subject to verifying physical inventories and audits by the Army to ensure accuracy. Contractor shall report inventory to verify record accuracy and provide updates to TAV-C to adjust balances. Reports of inventories will be in accordance with the CDRL A009 for DI-MGMT-80441D. See appendix C.

DoD policy now requires that all GFP/E be reported in the GFP module or Wide Area Workflow module of the Procurement Integrated Enterprise Environment (PIEE) as required by the DFARS clause 252.245-70XX, Management and Reporting of GFP/E. This clause provides guidance on what is an acceptable system or systems for managing and accounting GFP/GFE. Contractors will use these methods for accounting Government property as further described below:

The Contractor shall use the (GFP) module of (PIEE) to: - (a) Report physical receipt of GFP/E, (b) Report the loss of Government property, in accordance with paragraph (f)(1)(vii) of the FAR 52.245–1 clause. Unless otherwise provided for in this contract, this requirement applies to a loss of GFP/E that results from damage that occurs during work in process, (c) Report the transfer of GFP/E to another DoD contract, (d) Report the shipment of GFP/E to the Government or to a contractor. The GFP module generates the electronic equivalent of the DD form 1149, DD form 1348–1, or other required shipping documents, (e) Report when serially managed items of GFP/E are incorporated into a higher-level component, assembly, or end item,(f) Complete the plant clearance inventory schedule in accordance with paragraph (j)(2) of the FAR 52.245–1 clause unless disposition instructions are otherwise included in this contract. The GFP module generates the electronic equivalent of the Standard Form (SF) 1428, Inventory Disposal Schedule and (g) Submit a request to buy back or to convert to GFP/E items of Contractor-acquired property.

Exhibit A SPRBL1-24-R-0007 Page 15 of 17

Contractor or contracted firm-The contractor shall provide to the COR a physical inventory plan demonstrating how the contractor will achieve a 100% physical inventory count of all material in the contractor’s custody over the length of period of performance or 1 calendar year for the start of the period of performance. Inventory records are subject to verification by the government. Contractor must maintain record of physical inventory counts performed to be provided in the event of an inspection.

Information regarding the GFP module is available in the GFP Module Vendor Guide at https://dodprocurementtoolbox.com/site-pages/gfp-resources. Users may also register for access to the GFP module and obtain training on the PIEE home page at https://wawf.eb.mil/piee-landing.

9.2 Surge Requirements

The Contractor shall maintain its surge capability to produce and deliver the surge quantity identified in solicitation/contract. The Government reserves the right to exercise either the Standard Delivery Schedule or Surge Delivery Schedules in any Delivery Orders. This Surge request shall be generated by the Contracting Officer via written notification to the contractor identifying the surge requirement, setting forth the item(s) for which the Government seeks accelerated delivery and the requested revised required delivery schedule(s) associated therewith. The contractor agrees to submit a proposal in response to the Government's request within 30 days of receipt of the request. The proposal shall set forth a delivery schedule and any proposed price adjustment applicable to the accelerated delivery schedule. The contractor shall utilize its best efforts to propose a delivery schedule conforming to the Government's requested revised delivery schedule. No Government liability for price adjustment shall accrue as a result of the surge request unless there is a negotiated written contractual modification requiring the accelerated schedule.

9.3 Supply Chain Risk Management (SCRM)

The Supply Chain Risk Management (SCRM) Plan defines the structured, contractor proposed SCRM strategy relative to the products and services to be provided by the prime, its suppliers, and subcontractors. This information will be used by the Government to maintain oversight of the contractor's holistic approach to identify, manage and monitor the risks associated with unintended, adverse events and failure points within the supply chain, addressing both processes and products. The contractor shall prepare Supply Chain Risk Management Plan IAW CDRL A010 for DI-MGMT-82256. This shall be NSP CLIN.

9.4 Quarterly Integrated Program Reviews (QIPRs)

The Contractor shall host and support QIPRs on dates mutually agreed upon by the Contractor and the Government. Each QIPR shall be held for a maximum of two days. The QIPR location is the contractor’s facility in Danbury, CT. The purpose of the QIPRs shall be to assess the progress and status of the AN/AVR-2B program. At a minimum, the Contractor shall present an update of overall program status, cost, schedule, status of CDRL deliverables, as well as programmatic concerns, to include DMSMS, for spares and engineering services efforts at each QIPR. The Contractor shall, IAW CDRL A011, DI-ADMN-81249C, prepare an agenda and deliver it to the Government for approval. Additionally, draft briefing charts will be provided to the Government NLT three working days prior to the QIPR. The Contractor shall provide meeting minutes IAW

CDRL A012, DI-ADMN-81250C.

https://dodprocurementtoolbox.com/site-pages/gfp-resources https://wawf.eb.mil/piee-landing

Exhibit A SPRBL1-24-R-0007 Page 16 of 17

9.5 Foreign Interests

Offerors shall complete Standard Form 328 Certificate Pertaining to Foreign Interests OMB No. 0704-0579.

Government shall use SF328 responses to inform supply chain risk management. Form shall be provided as part of the solicitation package and modified if there are any changes over the contract period of performance.

Exhibit A SPRBL1-24-R-0007 Page 17 of 17

10 CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

10.1 CDRL List

CDRL

Data Line No. DID Identification Title

A001 DI-SESS- 80639E ENGINEERING CHANGE PROPOSAL (ECP)

A002 DI-SESS- 80642E NOTICE OF REVISION (NOR)

A003 DI-SESS- 80640E REQUEST FOR VARIANCE (RFV)

A004 DI-MGMT- 81948 DMSMS MANAGEMENT PLAN (DMP)

A005 DI-MGMT- 82274 DMSMS LIFECYCLE MANAGEMENT DATA

A006 DI-MGMT- 81941 OBSOLESCENCE ALERT NOTICE

A007 DI-MGMT- 82273 DMSMS HEALTH ASSESSMENT REPORT

A008 DI-NDTI- 80603A TEST PROCEDURE

A009 DI-MGMT- 80441D TAV-C MONTHLY

A010 DI-MGMT- 82256 SUPPLY CHAIN RISK MANAGEMENT

A011 DI-ADMN- 81249C MEETING AGENDA

A012 DI-ADMN- 81250C MEETING MINUTES

10.2 APPENDIXES:

Appendix A: Security Classification Guide (SCG)

Appendix B: Security AT/OPSEC

Appendix C: J&A for GFP use.

ANTITERRORISM/OPSEC COVER HEET

Contract/Solicitation Number: Requiring Activity:

Section I. Purpose and Policy.

Purpose of cover sheet: To document the review of the requirements Performance Work Statement (PWS), Statement of Objectives (SOO), Statement of Work (SOW), uality ssurance urveillance p an (QASP) and any applicable source selection evaluation criteria for antiterrorism (AT) and other related protection matters to include, but not limited to: AT, Operations Security (OPSEC), cyber security, physical security, law enforcement, intelligence, and foreign disclosure. Army policy requirement: A signed AT/OPSEC cover sheet is required to be included in all requirement package .

Mandatory review and signatures: The organizational Antiterrorism Officer (ATO), OPSEC Officer, Information System Security Manager/Officer, ISSM/ISSO, Security Manager (SM), and Contracting Officer Representative (COR) must review and sign each requirements package prior to submission to the supporting contracting activity, to include coordination with other staff review, as appropriate per section II below. The ATO must be certified as a U.S. Army ATO Level II. The OPSEC Officer must be certified as a Level II OPSEC Officer. If the requiring activity does not have any qualified reviewers, the first functional person in the chain of command will review the contract for each functional consideration. Changes to the security requirements after the functional reviews are completed will void the review and require a subsequent functional review again. Items Checked “Y ”, apply to this effort. Items checked “N ” are not applicable to this effort and requirements will not be levied against the contractor.

Section II. Standard Contract Language Provision/Contract Clause Text Applicability and/or Additional Language.

If standard contract or clause language found on the following pages of this form, including site specific guidance is sufficient to meet specific contract request requirements, check " " in block below and include this language in the PWS/SOO/SOW. If standard contractual text (provisions or clauses) or clause language does not apply, check " ." If standard contract text or clause language is not desired, but there is related contract specific language in the PWS/SOO/SOW, check " " and "PWS/SOO/SOW."

If is marked for items 1, 2, 3 6, 8, or 12, training is required. Mandatory Training must be measured as a deliverable and evaluated in the QASP.

Section III. Functional Review.

Requirements Reviewer Selection Specific Guidance

1. AT Level 1 training ATO YES NO

2. AT awareness training for US-based contractor personnel traveling overseas for both unofficial and official travel ATO YES NO

3. iWATCH training ATO YES NO

4. Mass Warning Notification System (MWNS) Requirement ATO YES NO Antiterrorism Review Signature: I am an ATO (Level II Certified) and have reviewed the requirements package and understand my responsibilities in accordance with Army Regulation 525-13, Antiterrorism.

Signature

5. For contracts that require a formal OPSEC program OPSEC YES NO

6. Requirement for OPSEC training OPSEC YES NO Operations Security Review Signature: I am OPSEC level II certified and have reviewed the requirements package, and it is in compliance with Army Regulation 530-1, Operations Security.

Signature

7. Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems

ISSM

ISSO YES NO

8. Cybersecurity/information technology training ISSM

ISSO YES NO

9. Cybersecurity/information technology certification ISSM

ISSO YES NO

Information System Security Manager/Officer Review Signature: I have reviewed the requirements package and it contains the correct information to meet this effort’s cybersecurity requirements.

Signature

10. Access and general protection policy and procedures SM YES NO

11. Handling/Access to Classified Information SM YES NO

12. Security Training SM YES NO

Security Manager Review Signature: I have reviewed the requirements package and it contains the correct information to meet this effort’s security requirements.

Signature

13. Common Access Card (CAC)/Information Technology (IT) Level Requirements COR YES NO

14. For contractor not eligible for CAC, but requires access to DoD facility or installation COR YES NO

15. Contractor Authorized to Accompany the Force clause COR YES NO

16. Contract requiring performance or delivery in a foreign country COR YES NO Contracting Officer Representative Review Signature: I have reviewed the requirements package and it contains the correct information to meet this effort’s contractual requirements.

Signature

CECOM G2 - This version is dated 2022. All previous versions are obsolete.

SPRBL1-24-R-0007

FERRELL.ANDR

EA.K.1291697395

Digitally signed by

FERRELL.ANDREA.K.1291697395

Date: 2023.09.14 07:48:08 -04'00'

FERRELL.ANDR

EA.K.1291697395

Digitally signed by

FERRELL.ANDREA.K.1291697395

Date: 2023.09.14 07:48:30 -04'00'

DIRLA.JASON.

R.1387296340

Digitally signed by

DIRLA.JASON.R.1387296340

Date: 2023.09.14 09:00:53 -04'00'

FERRELL.ANDRE

A.K.1291697395

Digitally signed by

FERRELL.ANDREA.K.129169739

Date: 2023.09.14 07:48:51 -04'00'

PHILLIPS.NATALIE.

NICOLE.1403972050

Digitally signed by

PHILLIPS.NATALIE.NICOLE.1403

972050 Date: 2023.09.13 15:26:18 -04'00'

Section IV. Standard Contract Language/Contract Clause Applicability and/or Additional PWS/SOO/SOW Language.

1. AT Level I Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area:

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 60 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://jkodirect.item.mil/ for CAC holders (Course number “-US007”). Non-CAC-holders may go to:

http://jk

2. AT Awareness Training for Official and Unofficial Contractor Personnel Traveling Overseas:

US based contractor employees and associated subcontractor employees shall receive government provided area of responsibility (AOR) specific AT awareness submit training as directed by AR 525-13, or other C COM specific requirements, as necessary.

Specific AOR training content is directed by the combatant commander with the unit ATO being the local point of contact. US based contractor employees and associated subcontractor employees will update their PRO-File survey prior to their official or unofficial travel, in accordance with AR 525-28, Personnel Recovery. The PRO-File survey is available at the following link:

https://prmsglobal.prms.af.mil/prmsconv/Login/Banner.

3. iWATCH Training (This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area):

The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 60 calendar days after contract award.

4. Mass Warning Notification System (MWNS) Requirement: Per DoDI 6055.17, all contractors accessing government installations must register with the MWNS system in use at the government place of performance.

5. For contracts that require a formal OPSEC program: The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan shall include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

6. For contracts that require OPSEC Training:

7. Army Training Certification Tracking System (ATCTS) Registration (Required when contractor employees require access to government information systems): All contractor employees with access to a government information system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DoD Cybersecurity Awareness Challenge and Accepted Use Policy (AUP) prior to access to the IS, and then annually thereafter. IT access requests must include current AUP and training certificates for initial and contract renewals.

8. For Cybersecurity/Information Technology (IT) training:

All contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to Cybersecurity/IT functions.

9. For cybersecurity/information technology (IT) certification:

Per DoD 8570.01-M (Ch4) , DFARS 252.239.7001 and AR 25-2, the contractor employees supporting Cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M (Ch4) must be completed upon contract award.

CECOM G2 - This version is dated ber 2022. All previous versions are obsolete.

10. Access and general protection/security policy and procedures (This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area):

Contractor and all associated subcontractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

11. For contracts that require handling or access to classified information:

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

12. Security training for contractors: Several training requirements exist for contractor personnel per DoD and Army regulation/ directives. On-site contractors may receive training briefs from the government appointed Security Manager; however, contracting companies will be required to provide training to off-site contractor employees. Training is tailored to the organization’s requirements as well as local policy. Some examples of Security training provided to integrated/embedded contractors may include, but is not limited to, the following:

Threat Awareness Reporting Program (required for all contractors with security clearances) - Per AR 381-12 Threat Awareness and Reporting Program (TARP), cleared contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b.

Initial Security Orientation: Online training available on the Army Learning Management System (ALMS) site, reference ALARACT207-2103 - Initial training Annual Security Orientation: Online training available on the Army Learning Management System (ALMS) site, reference ALARACT 207-2103 - Annual training requirement Derivative Classification Training, reference DoD 5200.01-V3-biennial training requirement Foreign travel training, AR 525-13 - Required when traveling abroad DA, AMC, and/or commander directed security stand-downs, e.g., ad-hoc refresher training

13. Common Access Card (CAC) and Information Technology (IT) Level Requirements:

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated T1/National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

IT Level Designations. Contractor personnel shall be designated as IT-I IT-II or IT-III, as defined in the Traditional Security Checklist:

Version 1, Release 3, Benchmark Date 15 Jun 2020, STIG ID: PE-02.02.01 at https://cyber.mil/. Contractor personnel shall obtain the appropriate security screening as prescribed in STIG PE-02.02.01 and DoD 8570.01-M (Ch4), before being granted access…