Exhibit A Technical Requirements.pdf

TECHNICAL REQUIREMENTS

Hardware Spares

Warfighter Information Network – Tactical Increment 2

20 January 2022

Prepared by:

Integrated Logistics Support Center (ILSC)

Command, Control, Communications Tactical (C3T) Directorate Warfighter Information Network – Tactical (WIN-T) Increment 2 (INC 2)

Aberdeen Proving Ground, Maryland 21005

TABLE OF CONTENTS

1.0 Applicable Documents

2.0 Configuration Baseline

2.1 Part Revisions

2.1.1 Configuration

2.1.2 Departures from Configuration Baseline

3.0 Item Unique Identification (UID)

3.1 Unique Identification Marking

3.2 Unique Identification Marking Data Submission Guidance

4.0 Packaging

4.1 Wood Packing Material

4.2 Preservation, Packing and Marking Instructions

4.2.1 Part Number Marking

4.2.2 Permanency and Legibility

5.0 Performance Requirements

5.1 Inspection and Testing

5.2 Quality

5.3 Hardware Procurement Requirements

6.0 Security Details

6.1 Security Requirements

7.0 Contract Data Requirement List (CDRL) DD 1423-1

CDRL A001: Configuration

Exhibit A SPRBL1-22-Q-0026 Page 1 of 6 Issue: 15 April 2022

1.0 APPLICABLE DOCUMENTS

Military and Federal Standards MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property

Military and Federal Specifications DFARS 252.211-7003 Item Identification and Valuation DFARS 252.211-7006 Passive Radio Frequency Identification FAR 42.503 Post Award Conferences

Other Documents None

Commercial Documents ASTM D 3951-18 Standard Practice for Commercial Packaging

ANSI/ASQ 9001:2015

Security Documents None

2.0 CONFIGURATION BASELINE

The applicable Configuration Baselines (CB), for the listed Configuration Item (CI), are as listed in Appendix A.

NSN Nomenclature MFG PN

7025-01-692-6521 INTERFACE UNIT, AUTOMATIC DATA

PROCESSING 402227-01

2.1 Part Revisions

2.1.1 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.

2.1.2 Departures from Configuration Baseline

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 Configuration Manager (C Mgr.) or Configuration Management Officer (CMO) and which are made applicable to the contract by the PCO. Configuration Control shall be effected by the Configuration Control Documents (CCDs) as follows:

Engineering Change Proposal (ECP) includes both the engineering change and the supporting documentation by which the change is described and suggested. An ECP describes changes to the CI and associated Government documents and data that are affected by the proposed engineering change.

A Notice of Revision (NOR) shows the detailed changes that must be made to technical documentation, except specifications, (one NOR per document) following approval of an ECP. The NOR is submitted as part of the

ECP.

Exhibit A SPRBL1-22-Q-0026 Page 2 of 6

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 Variance (RFV) can be used for those documents.

The RFV describes a departure from configuration documentation for a specific number of units or period of time. Contractor shall identify the impact of the RFV on performance, operational readiness and logistics support of the affected CIs. The Government may require compensation or consideration for any approved

RFV.

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

3.0 ITEM UNIQUE IDENTIFICATION (UID)

The contractor shall implement item Unique Identification (UID) marking, as defined in MIL-STD-130-M and DoD Guide to Uniquely Identifying Tangible Items, Assuring Valuation, Accountability and Control of Government Property, Version 2.5, September 15, 2012. The two-dimensional item UID marking shall be incorporated into existing data plates, shall be machine-readable with common optical scanning devices, and be accompanied by the corresponding human readable markings when practical.

3.1 Unique Identification Marking

The contractor shall comply with DFARS 252.211-7003, Item Identification and Valuation to provide UID. UID markings shall be per the latest version of MIL-STD-130. UID markings are also required for embedded components in this contract. Guidance for UID Marking of embedded components shall be per the latest version of MIL-STD-130 and the http://www.acq.osd.mil/dpap/UID/ website. Refer to DFARS 252.211-7003 for additional requirements. The Contractor shall ensure that all delivered equipment meeting the UID criteria is marked and the applicable data is submitted to the DOD UID Repository.

3.2 Unique Identification Marking Data Submission Guidance

The Contractor shall submit UID data via the Wide Area Work Flow (WAWF) Paperless Contracting Environment per the latest published guidance. The latest UID Data Submission guidance may be found at http://www.acq.osd.mil/dpap/sitemap.html.

4.0 PACKAGING

All hardware items shall be packaged and marked IAW ASTM D 3951-18, Standard Practice for Commercial Packaging. Level of Protection: Commercial, Level of Pack (LPK): Commercial, Quantity Unit Pack (QUP): 001.

Packaging requirements will be provided with the delivery order. Marking shall be IAW MIL-STD-129R with change 4. Radio Frequency Identification (RFID) requirements shall be IAW the Section "F" clause, DFARS 252.211-7006 of the contract.

4.1 Wood Packing Material

Wood packaging material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frames and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSB). All WPM shall meet the requirements of the International Standards for Phytosanitary Measures (ISPM)

Exhibit A SPRBL1-22-Q-0026 Page 3 of 6

Number 15, "Regulation of Wood Packaging Material in International Trade". DoD shipments inside and outside of the United States shall meet the requirements of ISPM 15 whenever WPM is used to ship DoD cargo.

All WPM shall comply with the official quality control program for heat treatment (HT) or kiln dried heat treatment (KDHT) IAW American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations (see http://www.alsc.org/).

All WPM shall include certification/quality markings IAW the ALSC standard. Markings shall be placed in an unobstructed area that will be readily visible to inspectors. Pallet markings shall be applied to the stringer or block on diagonally opposite sides of the pallet and be contrasting and clearly visible. All containers shall be marked on a side other than the top or bottom, contrasting and clearly visible. All DUNNAGE used in configuring and/or securing the load shall also comply with ISPM 15 and be marked with an ALSC approved DUNNAGE stamp.

DoD Components are defined as all entities, including Contractors that engage in logistical functions supporting elements of the U.S. Armed Forces. See DLAD 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. 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

4.2 Preservation, Packing and Marking Instructions

4.2.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. The packaging shall be labeled with NSN, part number, contract number, cage code, and condition code. Hardware such as screws, nuts, bolts, need not be marked. The marking shall become permanently part of the item after it is applied, and can be applied using deformation, tag, and rubber stamp with permanent characteristics or stencil. 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 KO 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 Task order.

4.2.2 Permanency and Legibility

The UID 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 the latest version of MIL-STD-130N.

5.0 PERFORMANCE REQUIREMENTS

Under this Indefinite-Delivery Indefinite-Quantity (IDIQ) contract, the Contractor shall serve as the prime Contractor and shall procure all of the items as ordered by the Government in accordance with this Technical Requirements document.

5.1 Inspection and Testing

The contractor shall maintain a system for the identification of the process, inspection/test status of all NSNs. The contractor shall perform final Inspection and testing on all deliverables in accordance with the contractor's

Exhibit A SPRBL1-22-Q-0026 Page 4 of 6

Inspection and Testing Procedures. These inspection reports shall be available to the Government or their representatives upon request. Equipment and facilities required for inspection and testing shall be the Contractor’s responsibility.

5.2 Quality

The Contractor shall comply with a higher-level quality management system such as the ANSI/ASQ 9001:2015, Quality Management Systems - Requirements, or equivalent in all production facilities involved in this contract.

The Contractor shall provide and maintain a comprehensive quality assurance program within its producing/manufacturing facility which addresses Hardware and Software/Firmware Quality. The Contractor shall flow down all quality requirements to sub-Contractors as they apply to procured material and services. The Contractor may change to an alternate Quality Management System during the term of the contract as long as a written request is submitted and approved by the Government.

The Government reserves the right to examine or audit the contractor's Quality Management System and any manufacturing/production processes and may interview key business and technical staff at the Government's discretion. The Contractor shall provide the Government the right to make such inspections and audits while the work is in process in order to provide confidence that the project complies with contractual requirements. The Contractor shall provide personnel and facilities to support Government's inspections and audits.

5.3 Hardware Procurement Requirements

The Contractor shall supply all items in accordance with the delivery schedule. Items shall be completed, packaged, shipped, and received at the specified ship to location. Supply Turnaround Time shall be from date of delivery order to the date the item arrives at the Government depot.

6.0 SECURITY DETAILS

6.1 Security Requirements

The contract has been deemed Controlled Unclassified Information (CUI)/UNCLASSIFIED. The Contractor shall be required to have CUI/UNCLASSIFIED facility clearance with appropriate CUI/UNCLASSIFIED safeguarding capability.

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

CDRL Data Line No. DID Identification Title

A001 DI-MISC 80711A Scientific and Technical Reports – Configuration

Exhibit A SPRBL1-22-Q-0026 Page 5 of 6

CDRL A001: Configuration

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 A TDP TM OTHER MISC

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

WIN-T INC 2

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

GROUP

A001 Scientific and Technical Reports Configuration

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

TOTAL PRICE

DI-MISC-80711A Tech Requirements, sec 2.1.2

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

N/A N/A ASREQ BLOCK 16 b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Draft

Final

BLOCK 16

Reg

Repro

16. REMARKS:

BLK 4: Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in this Technical Requirements. WIN-T Increment 2 Hardware Spares.

The Contractor shall prepare and submit a Request for Variance (RFV) for Government review in accordance with this Technical Requirements section for Configuration Management when there is a change or departure from a contractual baseline.

All RFVs for changes shall be submitted for Government review or notification within 5 business days of Contractor approval and prior to presentation of the product for acceptance, but not later than 30 calendar days, of any such product.

The Government shall review, accept, and/or comment on the draft submission in 30 calendar days. The Contractor shall incorporate changes and re-submit within 30 calendar days. The Government will have 30 calendar days to review, accept, or comment on the final submission.

Data shall be submitted and exchanged electronically in Microsoft Office suite of applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

PCO

AMEL-LCC-NB

15. TOTAL 0 2 0

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

Nick Burley Systems Engineer FCDD-ISP-CS 14 April 2022

Matthew Modlin Branch Chief FCDD-ISP-CS 14 April 2022

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages

Exhibit A SPRBL1-22-Q-0026 Page 6 of 6

Appendix A – NSNs for Procurement

NSN Nomenclature MFG PN

7025-01-692-6521 INTERFACE UNIT, AUTOMATIC DATA

PROCESSING 402227-01