A19-Exhibit A Statement of Work 17 Micrometer TWV Sensor 2022-04-12.pdf

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 1 of 19

Statement of Work (SOW)

For

Spot Buy Acquisition of Spare Parts on the

Driver’s Vision Enhancer (DVE) AN/VAS-5

Prepared for:

Integrated Logistics Support Center (ILSC) Intelligence Electronic Warfare (IEW&S) Division by DEVCOM C5ISR Center, Fielded Systems Engineering (FSE)

ATTN: FCDD-ISE-HC

Building 6006

Aberdeen Proving Ground, MD 21005

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 2 of 19

0.0 DOCUMENT REVISIONS

1.0 APPLICABLE DOCUMENTS

1.1 Military and Federal Docs

2.0 REQUIREMENT

2.1 All work performed by the Contractor

3.0 CONFIGURATION BASELINE

3.1 Requirements for Configuration Control:

3.1.1 Configuration Baseline

3.1.2 Configuration

3.1.3 Departures from Configuration Baseline (CB)

3.1.4 Baseline Changes

3.1.5 Configuration Management (CM)

3.2 Configuration Control Documentation:

3.2.1 Configuration Management Plan (CMP)

3.2.2 Engineering Change Proposal (ECP)

3.2.3 Request for Variance (RFV)

3.2.4 Notice of Revision (NOR)

3.2.5 Contractor shall provide

3.3 Requirements for Item Unique Identification (IUID)

List of Items Requiring Marking

3.3.1 Commercial Markings

3.3.2 Permanency and Legibility

3.3.3 Deleterious Effect

3.3.4 IUID Coding

3.3.5 Human Readable Form

3.3.6 Part Number Marking

3.3.7 Serial Numbers

3.3.8 Correction of Noncompliant Equipment and Technical Data

3.3.9 Pricing of IUID Requirements

3.4 Requirements for Quality Assurance System

3.4.1 Quality Approach

3.4.2 Initial Quality Planning

3.4.3 Design

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 3 of 19

3.4.4 Document Control

3.4.5 Records

3.4.6 Control of Purchases

3.4.7 Materials Control

3.4.8 Nonconforming Material

3.4.9 Corrective Action

3.4.10 Manufacturing Operations/Process Controls

3.4.11 Inspection and Testing

3.4.12 Measuring, Testing, and Inspection Equipment

3.4.13 Inspection and Test Status

3.4.14 Quality Audits

3.4.15 Training Requirements

3.4.16 Statistical Quality Control and Analysis

3.4.17 Continuous Process Improvement

4.0 PACKAGING

4.1 Handling, Storage, Preservation, Packaging, and Shipping

4.1.1 Preservation, packing and marking for shipment

4.2 Wood Packaging Material

4.3 Military Packaging

4.3.1 DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

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

5.1 CDRL List:

5.1.1 Individual CDRLs: (begin on next page)

Scientific and Technical Reports

Engineering Change Proposals

Request for Variance

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 4 of 19

0.0 DOCUMENT REVISIONS

Date Section / Paragraph / Item Revision

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 5 of 19

1.0 APPLICABLE DOCUMENTS

The latest approved revisions of the following documents are applicable to the extent specified herein. The Contractor shall report any conflicts within this SOW or documents referenced herein to the Procuring Contracting Officer (PCO) for resolution.

1.1 Military and Federal Docs

Military and Federal Standards Document Title MIL-HDBK-61A Configuration Management Guidance, 07 February 2001 MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-130N with change 1 Identification Marking Of U.S. Military Property MIL-STD-2073-1E with Change 1 Standard Practice for Military Packaging MIL-STD-31000B Military Standard: Technical Data Package (TDP) (31-Oct-2018) ANSI/EIA-649B National Consensus Standard for Configuration Management, Jun 2011 Military and Federal Specifications MIL-PRF-49256D Performance Specification For The

Driver’s Vision Enhancer Family Of Systems (Dve-Fos) An/Vas-5 (A) ICD- A3325865B Interface Control Document (Icd)

For The Driver’s Vision Enhancer-Family Of Systems (Dve-Fos) B-Kit Other Documents

DI-MISC-80711A Scientific and Technical Reports – Configuration Control DI-SESS-80639D Engineering Change Proposal DI-SESS-80640D Request for Variance DI-SESS-80642D Notice of Revision DI-SESS-81856 Contractual Baseline Report

80063-8849104B Performance Specification for The Driver’s Vision Enhancer Family of Systems

(DVE-FOS) AN/VAS-5 (A)

Commercial Documents ANSI/ASQC 9001:2015 Quality Management Systems Requirements, 01 January 2015 ASTM D3951-10 Standard Practice for Commercial Packaging ISPM 15 Regulation of Wood Packaging Material in International Trade Security Documents CECOM G2 Anti-terrorism/OPSEC AR 530-1 Operations Security FAR 52.204-2, Security Requirements DOD 5220.22-M The National Industrial Security Program Operating Manual

2.0 REQUIREMENT

2.1 All work performed by the Contractor shall be accomplished in accordance with (IAW) this SOW.

Any changes or additions will be negotiated and approved by the Procuring Contracting Officer (PCO) prior to being implemented. The functional capabilities for which the DVE components Line Replaceable Units (LRU) were designed shall not be changed, modified, or altered unless such changes are directed by the PCO.

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 6 of 19

3.0 CONFIGURATION BASELINE

Requirements. The DVE spares that the contractor shall produce consist of the items set forth in Section B of the contract in the quantity listed. In the event of a conflict between the requirements of this SOW and any cited documents for the item on contract, the requirements of this SOW shall govern.

3.1 Requirements for Configuration Control:

3.1.1 Configuration Baseline. For this contract the Configuration Items (CI) consist of the items identified in Table 1. The applicable Configuration Baseline (CB) for each CI is established by its respective part number, CAGE code, description, and NSN appearing in section B of the contract.

Table 1 Item Description Cage

Code NSN Part Number -

Revision

17 µm TWV Sensor 32865 5855-01-661-4313 1000613-201

3.1.2 Configuration. Each CI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). Configuration changes not directly affecting the configuration baseline do not require Government approval prior to incorporation, but must be documented by the contractor and shall be made available to the Government upon request.

3.1.3 Departures from Configuration Baseline (CB). During the time duration of the contract No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with CDRL A001 DI-MISC-80711A and are approved by the Government and which are made applicable to the contract by the PCO. This requirement does not apply to Class 2 changes. Class 2 changes are defined as those that do not affect form, fit, or function, and do not affect cost or delivery schedules. Class 2 changes do not require the submission of configuration control documents.

3.1.4 Baseline Changes. The Contractor shall be responsible for maintaining the configuration of the baselined components and shall be maintained in the configuration previously delivered to the Government, as documented in the Provisioning Parts List and technical manuals, and other logistics documents previously provided to the Government. It is anticipated that there will be changes to the configuration of the DVE as a result of obsolete parts or other changes that the Contractor determines necessary. Configuration changes may also affect the delivered logistics data, to include but not limited to the TMs, PPL and SDFP. The contractor shall revise and Deliver these products IAW the governments updated control process. The contractor shall provide the deliverables IAW the CDRLs and DIDs provided under this contract.

Any change to System Specifications, technical and/or logistics data used by the Government to operate and maintain the equipment, including technical manuals, PTD (PPL and SDFP) requires Government approval. No Class 1 changes to these documents or delivered DVE components that conform to these documents will be allowed without prior formal Government approval through

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 7 of 19 the submission of a Class 1 ECP, its approval and issuance of a contract modification for its implementation.

3.1.5 Configuration Management (CM). The Contractor shall maintain a Configuration Management system for the control of all aspects of the DVE System to include but not limited to documentation and processes.

3.2 Configuration Control Documentation:

3.2.1 Configuration Management Plan (CMP). The configuration management process shall include specific, approved processes for identification of changes which may instigate engineering change proposals or deviations from designs and architectures presented to or reviewed by the Government. The principles contained in ANSI/EIA-649B, National Consensus Standard for Configuration Management, Jun 2011 and MIL-HDBK-61A, Military Handbook: Configuration Management Guidance, may be used for guidance. The Contractor shall designate a CM representative to serve as a primary POC to the Government for all CM matters and be responsible for any Sub- Contractor CM efforts. The Contractor shall notify the Government of any changes, which affect the Contractor‘s established CM process.

All contractor proposed changes to the requirements described in configuration control documents shall be made by one of the following means. Forms referenced are available at the following website:

http://www.apd.army.mil/.

3.2.2 Engineering Change Proposal (ECP). During the time duration of the contract. The costs to prepare and submit ECPs are not reimbursable. The ECP shall be sufficiently detailed to allow the Government to evaluate its technical, logistics, cost and programmatic impact. ECPs shall be submitted IAW CDRL A002 DI-SESS-80639D. The DD Form 1692, Engineering Change Proposal or Government approved equivalent are the only authorized forms approved for the submission of ECPs to the Government. MIL-HDBK-61A, establishes uniform requirements for the preparation of the DD Form 1692. ECP. Class I and II engineering changes will apply to the DVE Spares IDIQ contract. The Contractor shall submit to the Government for approval any Class I ECPs that result from new parts, performance requirements, safety requirements, or upgrades to already delivered systems or documentation to a new configuration, or Class I ECPs that change contractual provisions, cost or scope. The ECP shall be sufficiently detailed to allow the Government to evaluate its technical, logistics, cost and programmatic impact. The preparation costs of unsolicited contractor proposed ECPs are not reimbursable. All classifications of ECPs shall be submitted to the Government for approval. Unsolicited Class 1 ECPs shall be submitted to the Government for approval. The cost of implementing the ECP shall be negotiated under the “Changes” clause of the contract. A copy of each Contractor internal Class 2 ECP shall be furnished for informational purposes only at no cost to the Government. The implementation of a Class 2 Engineering Change shall not impact contract cost. If implementation of a Class 2 Engineering Change impacts schedule the Government may seek consideration.

ECPs that are initiated by the Contractor shall be solely the Contractor’s responsibility relative to cost.

However, when an ECP is determined to be required, the Contractor shall notify the Government as soon as the ECP enters the Contractor’s configuration control process. The Class I ECP shall be developed as described in this paragraph. The contractor shall include cost and impacts to DVE http://www.apd.army.mil/

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 8 of 19 documentation, provisioning data, and other logistics documentation, which was previously delivered to the Government. ECPs that the Government requests or requires the Contractor to deliver as a result of a Government initiated change shall be delivered IAW this paragraph, and the cost of generating those Class 1 ECPs will be separately priced and funded by the Government. DRAFT Class I and Class II ECPs, highlighting the description and the need for the change, shall be submitted to the Government, prior to the ECP entering the Contractor's configuration control process, and in accordance with CDRL A002, DI-SESS-80639D, Engineering Change Proposals. The Government reserves the right to challenge the contractor's classification of the ECP. Class I ECPs shall be submitted in accordance with CDRL A002 DI-SESS-80639D, Engineering Change Proposals.

Classification of Engineering Changes are as follows:

a) Class I. A change will be classified Class I if:

The functional configuration documentation or allocated configuration document is affected to the extent that any of the following requirements would be outside specified tolerances:

i. Performance

ii. Reliability, maintainability, or survivability

iii. Weight

iv. Interface characteristics

v. Electromagnetic characteristics

vi. Other technical requirements in the performance specification

A change to the product configuration documentation, once established, that affects one or more of the following:

i. Safety

ii. Interfaces to vehicles or humans

iii. Compatibility or specified interoperability with interfacing configuration items (CIs), support equipment or support software

iv. Configuration changes to the extent that retrofit action is required

v. Delivered operation and maintenance manuals for which adequate change/revision funding is not provided in existing contracts

vi. Preset adjustments or schedules affecting operating limits or performance to such an extent that new identification numbers are required

vii. Interchangeability, substitutability, or replaceability as applied to CIs and to all subassemblies and parts except the pieces and parts of non-repairable subassemblies

viii. Sources of CIs or repairable items at any level defined by source-control drawings

ix. Skills, training, or human engineering design

x. Environmental impact and health hazards

b) Class II An engineering change that does not impact one or more of the Class I criterion specified above will be classified Class II.

3.2.2.1.1 A Specification Change Notice (SCN) is used to delineate the exact change(s) in a specification that will be distributed to users when the ECP is approved. The SCN is submitted as part of the ECP. The SCN is not used for a military or federal document, only a Request for Waiver can be used for those documents.

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 9 of 19

3.2.2.1.2 Value Engineering Change Proposal (VECP) is the same as an ECP except there are proposed cost savings for the program. The contractor shall follow the specific guidance in this contract for VECPs.

3.2.3 Request for Variance (RFV) (formerly known as waiver or deviation). The costs to prepare and submit RFVs are not reimbursable. RFVs shall be submitted IAW CDRL A003, DI-SESS-80640D, DD Form 1694, and Request for Variance (RFV). Acceptance/ approval by the Government will be considered on a case by case basis. The DD Form 1694 or Government approved equivalent are the only authorized forms approved for the submission of RFVs to the Government. The MIL-STD-3046, Appendix E, establishes uniform requirements for the preparation of the DD Form 1694. Contractor shall identify the impact of the RFV on performance, operational readiness and logistics support of the affected CIs. The Government will require compensation for any RFV.

3.2.4 Notice of Revision (NOR). When an ECP is approved, the Contractor shall submit change notices as appropriate in accordance with this document and IAW CDRL A002. Both Class 1 and Class 2 ECPs shall be uniquely and sequentially numbered starting with 0001. The costs to prepare and submit NORs are not reimbursable. The submitter of a formal ECP shall include all necessary changes to each affected document on the NOR. The DD Form 1695, Notice of Revision, or Government approved equivalent are the only authorized forms approved for the submission of NORs to the Government. The NOR shall clearly and completely describe the change to each drawing, dataset, specification, associated list, or other affected document and shall describe both the current state of each document and the proposed modification (i.e. change from/change to). A minimum of one NOR shall be provided for each affected document (except as stated in MIL-STD-3046, Paragraph 5.5.4.1 –Tabulated NORs).

Use of alternates to the NOR form (for example, alternate format forms, electronic data transfer, etc.)

are acceptable provided both acquiring and supplying activities agree and the alternate method clearly and completely communicates the recommended change to each document. The MIL-STD-3046, Appendix C, establishes uniform requirements for the preparation of the DD Form 1695.

3.2.5 Contractor shall provide all supporting program or cost data with the CCD. The contractor shall uniquely and sequentially identify (including the use of the contract number) each ECP, VECP, NOR, SCN or RFW. The identification number should use less than 16 characters.

3.3 Requirements for Item Unique Identification (IUID). In accordance with DFARS 252.211-7003 Item Identification and Valuation, the Contractor shall provide unique identification marking. The contractor shall maintain an accurate, current list of IUIDs for all manufactured items on this contract.

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.

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 10 of 19

List of Items Requiring Marking.

Item Description NSN Part Number

Acceptance Criteria

UID Marking Required

Serial Number Marking Required

17 µm TWV Sensor

5855-01-661- 4313 1000613-201 A Y Y

Acceptance Criteria Coding:

A = Acceptance test B = Visual inspection per drawing

3.3.1 Commercial Markings. All other items shall have acceptable commercial markings that meet the guidelines in the DoD Item Unique Identification of Government Property Guidebook, 21 Sep 2007. The guide is available at the following website:

http://www.acq.osd.mil/dpap/pdi/uid/index.html

3.3.2 Permanency and Legibility. All marking and identification plates, tags, etching, or labels when used on equipment, parts, assemblies, subassemblies, units, sets, groups, or kits shall be as permanent as the normal life expectancy of the item and be capable of withstanding the environment, test, cleaning, repair, and rebuild procedures specified for the item. Legibility shall be as required and verified for ready readability per MIL-STD-130N.

3.3.3 Deleterious Effect. Marking of items shall be accomplished in a manner that will not adversely affect the life and utility of the item. Marking materials creating hazardous conditions shall not be used. Placement and choice of the marking shall not create hazardous conditions.

3.3.4 IUID Coding. All IUID markings and readability requirements shall comply with MIL-STD- 130N and the following provisions:

3.3.4.1 Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD 130N. First priority is the 2D data matrix symbol (machine readable) IUID is the minimum requirement when there are severe space limitations. The second priority is the human readable characters. The third priority is the Linear Bar Code.

3.3.4.2 If the technical data has not specified the marking location, markings shall be located such that they are visible during item use, provided that sufficient space is available, and does not interfere with equipment operations.

3.3.4.3 The contractor shall maintain an accurate, current list of IUIDs for all manufactured items on 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 other Government representative at any time during the life of this contract.

http://www.acq.osd.mil/dpap/pdi/uid/index.html

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 11 of 19

3.3.5 Human Readable Form. If items are not described by Government Product Technical Data (i.e. Commercial Items), the Government has not identified the items designated for UID marking.

Any item or subassembly which is serialized, repairable or hazardous such as a printed circuit board (PCB) or a Controlled Cryptographic Item (CCI) that is not described by the Government Technical Data (i.e. Commercial items) and/or the Government has not identified for UID marking shall have the following in Human Readable Form:

a. NSN/Manufacturer’s part number (applicable drawing number)

b. Serial Number

c. CAGE Code

3.3.6 Part Number Marking. Each item delivered under contract, along with each assembly, sub assembly, 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.

3.3.7 Serial Numbers.

3.3.7.1 The Contractor shall meet the requirements of MIL-STD-130N, Identification Markings of U.S. Military Property, 17 December 2007, to establish the UID and the Contractor shall insure that each item UID is unique.

3.3.7.2 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 elsewhere in this SOW, shall also apply.

3.3.7.3 The Contractor shall maintain an accurate, current list of IUIDs for all manufactured items on this contract. Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. The list shall be available for inspection by the Contracting Officer or other Government representative at any time during the life of this contract.

3.3.7.4 IUIDs on Embedded Items. The contractors shall provide IUID markings for all embedded items in this Contract.

3.3.7.5 Manual Entry. Manual entry shall be via the UID Web Entry site. Information on getting access to the website and instructions on entering the data shall be posted to http://www.acq.osd.mil/uid when Quality Assurance testing is complete.

http://www.acq.osd.mil/uid http://www.acq.osd.mil/uid

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 12 of 19

3.3.8 Correction of Noncompliant Equipment and Technical Data.

3.3.8.1 If applicable, configuration control requirements, the contractor shall initiate the appropriate configuration control document to correct all affected drawings/specifications which conflict with or omit the marking requirements stipulated above.

3.3.9 Pricing of IUID Requirements. All efforts required by this SOW and contract, including, but not limited to, the preparation of ECPs or notification of marking deficiencies, Property In the Possession of the Contractor (PIPC) reporting, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price.

3.4 Requirements for Quality Assurance System. The contractor shall implement and maintain a Quality Assurance System that meets or exceeds commercial best practices (i.e. Higher Level Contract Quality ANSI/ISO/ASQ (E) Q9001-2015). These requirements are commonly accepted practices employed by industry both in national and international environments. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

3.4.1 Quality Approach. The contractor shall establish/maintain a quality approach to ensure higher-level product integrity and to satisfy contract or order requirements.

3.4.2 Initial Quality Planning. The contractor during the earliest practical phase of the contract shall conduct a complete review of the contract requirements to identify all the resources necessary for assuring product integrity.

3.4.3 Design. The contractor shall establish/maintain controls over the design process to ensure that contract requirements are satisfied.

3.4.4 Document Control. The contractor shall establish/maintain procedures that control the adequacy, completeness, currentness, and changes of all documents (work instructions, drawings, specifications, etc.).

3.4.5 Records. The contractor shall maintain and utilize all records required for effective operation of the quality approach. The quality approach shall ensure that these records are complete (including subcontractor records) and reliable.

3.4.6 Control of Purchases. The contractor shall ensure that all supplies and services purchased from suppliers conform to contract requirements. The contractor shall require that their subcontractors control the product integrity of their services and supplies.

3.4.7 Materials Control. The contractor shall maintain controls over all materials and products throughout the manufacturing process. These controls shall enable the identification of materials that have passed inspection from those which have not. The contractor shall maintain records identifying the status and final destination of all materials/products.

3.4.8 Nonconforming Material. The contractor shall establish and maintain a system for controlling material that does not satisfy contract requirements, including procedures for its

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 13 of 19 identification, segregation, and disposition (rework/repair, scrap, etc.).

3.4.9 Corrective Action. The contractor shall promptly detect nonconforming material and conditions adverse to product integrity. It shall then initiate the corrective actions required to satisfy contract requirements.

3.4.10 Manufacturing Operations/Process Controls. The contractor’s quality approach is responsible for assuring/monitoring that all manufacturing operations/processes are accomplished under controlled conditions. Controlled conditions include documented work instructions (including workmanship), place of performance, production equipment, special work environments, inspections/tests, work specifications, and approval/rejection criteria.

3.4.11 Inspection and Testing. The quality approach shall assure that all inspections and tests required satisfying contract or order requirements are conducted. Inspection and testing requirements for each item are in accordance with the established drawing and part numbers.

3.4.12 Measuring, Testing, and Inspection Equipment. The contractor shall provide and maintain gauges (including production tooling used for inspection purposes) and other measuring and testing equipment to assure that products conform to contract requirements. These devices shall be calibrated against certified measurement standards that are traceable back to national/international standards.

3.4.13 Inspection and Test Status. The contractor shall maintain a system for the identification of the inspection and test status of all products throughout all stages of the manufacturing cycle.

3.4.14 Quality Audits. The contractor shall perform internal quality audits to verify the effectiveness of their quality approach.

3.4.15 Training Requirements. The contractor shall identify/provide for the training needs of their personnel performing quality functions.

3.4.16 Statistical Quality Control and Analysis. The contractor shall establish/utilize statistical methods whenever appropriate to satisfy the contract or order requirements.

3.4.17 Continuous Process Improvement. The contractor shall monitor the effectiveness of their quality approach and continually improve quality processes.

4.0 PACKAGING

4.1 Handling, Storage, Preservation, Packaging, and Shipping. The Contractor shall establish, maintain, control and be responsible for the handling, storage, preservation, packaging and shipping to protect the quality of the materials and to prevent damage from loss, deterioration, degradation, or substitution of products packaging.

4.1.1 Preservation, packing and marking for shipment shall be in accordance with Section "D" of the contract. Packaging shall be in accordance with the latest MIL-STD-2073-1E for the remaining NSNs.

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 14 of 19

Level of Preservation (LOP); Military, Level of Pack (LPK); B, Quantity Unit Pack (QUP); 001. Marking shall be in accordance with MIL-STD-129R w/Change 1. Radio Frequency Identification (RFID) Requirements shall be IAW Section "F" clause, DFARS 252.211-7006, of the contract. MIL-STD-129R is applicable.

4.2 Wood Packaging Material. Wood Packaging Material (WPM) shall be IAW Wood Packaging Materials

– T/Q RP001 DLA Packaging Requirements for Procurement. Failure to comply with these requirements may result in refusal, destruction, or treatment of materials at the point of entry. The Government reserves the right to recoup from the contractor any remediation costs incurred by the Government.

4.3 Military Packaging

4.3.1 DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

4.3.1.1 Military Packaging is applicable.

DS7029 - DS7033 LEGEND

Qty Quantity Prot Req Protection Required PGE-REF Packaging Reference (Military Standard) 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

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 15 of 19

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 Codes (MP) (CD) (PM) (WM) (CD) (CT) (UC) (IC) (PK) (SM) 5855-01-661-4313 Military MIL-STD-2073-1E B 001 - GX 1 00 00 NB B ED 00 - 39 BC

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 16 of 19

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

5.1 CDRL List:

5.1.1 Individual CDRLs: (begin on next page)

CDRL

Data Line No.

DID Identification Title

A001 DI-MISC 80711A Scientific and Technical Reports – Configuration Control A002 DI-SESS 80639D Engineering Change Proposal (ECP) A003 DI-SESS 80640D Request for Variance (RFV)

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 TDP X TM OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

DVE Spares

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE GROUP

A001 Scientific and Technical Reports Configuration Control

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MISC-80711A 3.1.3 Departure from CB FCDD-ISE-HC INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

LT ASREQ SEE ITEM 16 b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE raft

Final

N/A ASREQ

Reg

Repro

16. REMARKS: Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in SOW 3.#.

Item 12 &13: The contractor shall prepare and submit Configuration Control Documents in accordance with the SOW section 3.1 Requirements for Configuration Control when a change to or departure from a contractual baseline document is deemed necessary.

Item 14: Provide deliverables for Documents in searchable Adobe Acrobat, Microsoft Office (Word, Excel, PowerPoint), rich text, and text digital file formats. Submit the deliverables via electronic mail, FTP, SharePoint, or other means, with concurrence of the requiring office. Alternate formats may be allowed subject to Government review and approval.

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). E-mail notification is required with any electronic submission.

FCDD-ISE-HC

PCO

ACO

QAR

CECOM ILSC

15. TOTAL 0 5 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Vidal Candelaria, FSE Engineer, 443-861-2965 12/14/2021

Robert C. Tyndall Integrated Battlefield Intelligence Sensors Branch Chief, 443-861-2749

12/14/2021

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 18 of 19

Based upon DD Form 1423-1, 1 Jun 90

Original Form Approved

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Advise Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 TDP TM OTHER SESS

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

DVE Spares

A002 Engineering Change Proposals ECP / NOR

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-SESS-80639D

3.2.2 Engineering Change

Proposal

FCDD-ISE-HC INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION IN

LT ASREQ see item 16 b. COPIES SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final see item 16 ASREQ

16. REMARKS:

Block 12: As required. Allow 30 days for Government to review and determine acceptance on Class I. Allow 10 days for Government to review and determine acceptance on Class II.

Block 13: As required. Allow 30 days for Government to review and determine acceptance on Class I. Allow 10 days for Government to review and determine acceptance on Class II.

Block 14: A Notice of Revision (NOR) shall be part of an ECP submission per SOW Para 3.2.4 IAW DI-SESS-80642D. A cover letter shall accompany the report with date of submission. Both cover letter and the ECP/NOR shall be submitted and exchanged electronically in Microsoft Office applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

ACO

PCO

15. TOTAL 2 4 0

Vidal Candelaria, FSE Engineer, 443-861-2965 12/14/2021

Robert C. Tyndall Integrated Battlefield Intelligence Sensors Branch

Issue: 04/12/2022 SPRBL1-22-Q-0029 Page 19 of 19

Based upon DD Form 1423-1, 1 Jun 90

Original Form Approved

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Advise Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 TDP TM OTHER SESS

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

DVE Spares

A003 Request for Variance RFV

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-SESS-80640D

SOW Para 3.2.3 Request For Variance

FCDD-ISE-HC INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION IN

LT ASREQ see item 16 b. COPIES SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

N/A ASREQ

16. REMARKS:

Block 12: As required. Allow 30 days for Government to review and determine acceptance.

Block 13: As required. Allow 30 days for Government to review and determine acceptance.

Block 14: A cover letter shall accompany the report with date of submission. Both cover letter and the RFV shall be submitted and exchanged electronically in Microsoft Office applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

PCO

1 1

0 0

15. TOTAL 3 0

Vidal Candelaria, FSE Engineer, 443-861-2965 12/14/2021

Robert C. Tyndall Integrated Battlefield Intelligence Sensors Branch