Exhibit A Technical Requirements.pdf

Exhibit A SPRBL1-24-R-0013 Page 1 of 19 Issue: 13 September 2024

TECHNICAL REQUIREMENTS

MX-11769 Image Intensifier (5855-01-699-1065)

Exhibit A SPRBL1-24-R-0013 Page 2 of 19

TABLE OF CONTENTS

APPLICABLE DOCUMENTS

CONFIGURATION BASELINE

Obsolescence Management Requirements / Obsolete Components and Materials

Definitions DMSMS Management Program Design Changes Subcontractor Management DMSMS Costs

PACKAGING

Marking Wood Packaging Material Military Packaging

SPECIALIZED TESTING

CONTRACT SECURITY REQUIREMENTS

PROGRAM MANAGEMENT REQUIREMENTS

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

Exhibit A SPRBL1-24-R-0013 Page 3 of 19

APPLICABLE DOCUMENTS

Military and Federal Standards MIL-STD-129R w/Chg 2 Military Marking for Shipment and Storage MIL-STD-2073-1E w/Chg 4 Standard Practice for Military Packaging Military and Federal Specifications MIL-PRF-A3256363G Performance Specification, Image Intensifier Assembly, 18MM, Microchannel Wafer MX-11769/UV (1 September 2023) Other Documents CECOM SPI AG00000579 CECOM Special Packaging Instructions Commercial Documents ISPM Number 15 Regulation of Wood Packaging Material in International Trade ANSI/ISO/ASQ(E) Q9001-2015 American National Standard, Quality Management Systems

Requirements EIA-649-1 Configuration Management Requirements For Defense Contracts ANSI/NCSL Z540.3-2006 Requirements for the Calibration of Measuring and Test Equipment ANSI/ASQ Q10012-2003 Measurement Management Systems – Requirements for Measurement

Processes and Measuring Equipment ANSI/ASQ Z1.4-2003 (R2013) Sampling Procedures and Tables For Inspection By Attributes

Security Documents SCG Security Classification Guide for Image Intensifier Devices (31 October

2013)

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.

NSN Nomenclature Part Number

Exhibit A SPRBL1-24-R-0013 Page 4 of 19

5855-01-699-1065 Image Intensifier A3297310-1

Each CI/CSCI, 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). The Contractor shall establish a Configuration Management Program in accordance with EIA-649-1.

No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with EIA- 649-1, CDRL A001, CDRL B001, and CDRL C001, 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.

An Engineering Change Proposal (ECP) describes the changes to be made to the CI/CSCI and all associated Government documents and data that are affected by the proposed engineering change. ECP should be prepared in accordance with EIA-649-1, CDRL A001, and DI-SESS-80639.

A Request For Variance (RFV) is a specific written authorization to depart from a particular requirement(s) of an item’s approved configuration documentation for a specific number of units or a specified period of time, either as an advance request or after the fact.

The contractor shall identify the impact of the RFV on performance, operational readiness and logistics support of the affected CIs.

The Government may require consideration for any RFV. RFV should be prepared in accordance with EIA-649-1, CDRL B001, and

DI-SESS-80640.

A Notice of Revision (NOR) shows the detailed changes that must be made to technical documentation, except specifications, following approval of an ECP. A NOR shall be submitted for each document affected by an ECP. NOR should be prepared in accordance with EIA-649-1, CDRL C001, and DI-SESS-80642.

Obsolescence Management Requirements / Obsolete Components and Materials

Definitions.

For the purpose of this part – An “Approved Item” is the resolution of an obsolescence issue by the use of items already approved for use on the drawing (e.g., an approved alternate part already on a specification control drawing). The use of an approved item does not require configuration management approval or the establishment of a DMSMS Management Case.

“Backorder Avoidance” is an estimate of the number of supply system backorders for the next higher assembly (NHA) which would be avoided by resolving the case proactively. Backorder Avoidance is defined as the user demand for the NHA that would not have

Exhibit A SPRBL1-24-R-0013 Page 5 of 19 been filled as a result of the time spent resolving the issue had the issue been discovered reactively (i.e., the commencement of a contractual procurement or repair action).

A “Bill of Materials (BOM)” is a list of the items, including but not limited to: raw materials, sub-assemblies, intermediate assemblies, sub-components, parts, chemicals, software (SW), and the quantities of each needed to produce an end product. The BOM may include additional information that allows the user to determine the precise location of an item within an end product. A DMSMS BOM is limited to just those items selected for comprehensive monitoring by the DMSMS program.

“Commercial item” and “commercially available off-the-shelf (COTS) item” are items that meet their respective definitions in FAR Part 2.101 – Definitions.

A “Complex Substitute” is the resolution of an Obsolescence Issue by the use of a replacement item that has different specifications which need to be researched and validated, but requires no modification of the Next Higher Assembly (NHA). The use of a complex substitute requires configuration management approval and the establishment of a DMSMS Management Case.

“Cost Avoidance” is the difference between the cost of the government approved proactive DMSMS Case resolution and the estimated cost of case resolution should the DMSMS issue have been discovered reactively (i.e., the commencement of a contractual procurement or repair action). Note that this definition shall be used in lieu of the definitions in SD-22.

“Diminishing Manufacturing Sources and Material Shortages (DMSMS)” is the loss, or impending loss, of qualified source(s), manufacturers, or suppliers that may impact the production or sustainment of an item or system.

“DMSMS Issues” are problems related to shortages or projected shortages of items caused by obsolescence or the loss of qualified manufacturers or suppliers of items. DMSSMS issues are further classified as:

“Documented DMSMS Issues” are DMSMS Issues for which there is documentation advising that an item is unavailable or will be unavailable at a specific date in the future. Documented DMSMS Issues tend to identify issues for which the Years to End of Life (YTEOL) is typically one year or less and rarely in excess of two years.

“Predicted DMSMS Issues” are DMSMS Issues predicted to occur that have been identified by analysis of the item, its technology and market forces affecting the future availability of this item. A number of service providers exist in the private sector with tools capable of predicting DMSMS issues beyond 2 years to as much as 10 years.

A “Reactive DMSMS Issue” is a DMSMS Issue which was not identified until the commencement of a current procurement or production action for the item or a higher assembly for which the item is a component.

Exhibit A SPRBL1-24-R-0013 Page 6 of 19

A “DMSMS Management Case” is a project established to analyze and resolve DMSMS Issues.

“DMSMS Impact” is the negative effect of a DMSMS Issue on the ability to produce and/or support an item and/or its higher assemblies during its planned service life.

A “DMSMS Roadmap” is a data visualization tool, depicting the health of the product's as-sustained configuration that will be used to identify, manage and plan for the resolution of DMSMS Issues at the sub-system or assembly level to include software.

“End of Life” is the last date for which the item can be purchased. In the case of software, it represents the last day a software license is available for purchase.

“End of Support” is the last date for which software support is provided by the software licensor and occurs when either software updates or technical support ends.

“Firmware” is software contained on Non-Volatile Memory (NMV) for which updates occur via either the replacement of the NVM component or by replacement of an assembly containing the NVM component. Software on NVM components which is updated by any other means shall not be considered Firmware.

“Item” means any part, assembly, software, material, chemical, etc., used in the manufacture, assembly, or operation of deliverables of this contract.

“Non-Development Items (NDI)” shall be as defined in the FAR Part 2.101 – Definitions. Privately developed NDI which do meet the FAR definition of a commercial item are considered commercial items.

“Obsolescence” is the condition when a needed item is out of production.

The “Original Component Manufacturer (OCM)” is the organization responsible for the component design, specification and its production.

The “Original Equipment Manufacturer (OEM)” is the organization responsible for the equipment design, specification and its production.

A “Simple Substitute” is the resolution of a DMSMS Issue by its replacement with an existing item that meets all requirements and does not require modification to either the item or its NHA, but has not yet been approved by the design approving authority. Simple

Exhibit A SPRBL1-24-R-0013 Page 7 of 19 substitutes typically require only minimal qualification. The use of a simple substitute requires configuration management approval and the establishment of a DMSMS Management Case.

“Standard Parts” or “Commonly Used Parts” are those parts identified in the contractor’s Parts Management or Parts Selection processes as preferred for use by their design engineers. These parts are typically documented on Preferred Parts List (PPL) or equal.

“Subcontractor” is a person or entity to which the prime Contractor has delegated part or all of its obligations. Note that by this definition, most suppliers will not be considered “Subcontractors”, and as such, would not be automatically subject to the flow down of DMSMS program requirements.

“Technology Insertion” is a defined programmatic system management strategy to redesign an LRU or subsystem to provide new capability or improved performance to the weapon system.

“Technology Refreshment” is a defined programmatic system management strategy to replace the electronics (including software/firmware) in a system over a specific period of time, usually with the goal of resolving multiple DMSMS issues or to prevent the occurrence of DMSMS Issues preemptively by upgrading the technology of the design. From a DMSMS perspective, Technology Refreshment events should be planned to coincide with Technology Insertion events whenever possible.

DMSMS Management Program For the weapon system or items on contract, the Contractor shall establish and execute a proactive DMSMS management program in accordance with (IAW) this Technical Requirements Document (TRD) for the period of performance of this contract. The Government’s objective in this program is to efficiently and effectively identify, report, and resolve DMSMS issues, eliminate unplanned redesigns and maintain alignment to the objective of a minimum five-year interval before any DMSMS issue is forecast to occur within the system.

The program shall include processes or procedures to identify or predict DMSMS issues over a minimum five-year planning horizon, assess risk and develop obsolescence mitigation strategies to determine the most cost-effective solution to DMSMS issues. The program shall also include processes and procedures for selecting standard or commonly available parts and parts with more than one source of supply and with at least five (5) years to the end of life (YTEOL).

Design Changes Design changes shall be made in accordance with the Configuration Management requirements of this contract.

Exhibit A SPRBL1-24-R-0013 Page 8 of 19

Subcontractor Management.

The Contractor shall ensure that its Subcontractors (see Subcontractor definition) adhere to the DMSMS/Obsolescence requirements of this TRD.

DMSMS Costs The Contractor shall be responsible for all costs associated with mitigating DMSMS Issues, including:

- Monitoring parts, material and software availability;

- Locating alternate/substitute parts and/or material and software;

- Vendor interface and communication;

- Implementing the selected solutions, including redesign;

- System compatibility assurance;

- Interface with the Army Network; and

- Non-government qualification testing.

PACKAGING

Marking

All unit packs, intermediate packs, and exterior shipping containers shall be legibly and durably marked in accordance with MIL-

STD-129R.

Wood Packaging Material Wood Packaging Material in compliance with ISPM-15, Regulation of Wood Packaging Material in International Trade, is applicable.

See DLAD T/Q Requirement RP001 DLA Packaging Requirements for Procurement, which includes requirements for treatment of wood packaging material.

Wood Packaging Materials (WPM) shall meet the following requirements:

Exhibit A SPRBL1-24-R-0013 Page 9 of 19

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) 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 Heat Treatment/Kiln Dried (HT/KD) in accordance with 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.

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.

Military Packaging DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

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

Exhibit A SPRBL1-24-R-0013 Page 10 of 19

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 Codes (MP) (CD) (PM) (WM) (CD) (CT) (UC) (IC) (PK) (SM) 5855-01-699-1065 Military SPI AG00000579 B 001 ZZ Z ZZ ZZ ZZ Z ZZ ZZ A 00 BC ZZ and Z = See SPI for requirements.

Exhibit A SPRBL1-24-R-0013 Page 11 of 19

SPECIALIZED TESTING

The contractor shall perform Initial Production Testing (IPT) or Qualification Test (also known as First Article Testing) and Conformance Inspection (CI) IAW MIL-PRF-A3256363F and this document. Products delivered on this contract shall be qualified by Product Manager Soldiers Maneuver Sensors, CECOM Integrated Logistics Support Center (ILSC), or DEVCOM Command, Control, Computers, Communications, Cyber, Intelligence, Surveillance, and Reconnaissance (C5ISR )Center via performance of an IPT. Test methods for the IPT and CI shall be IAW the Government approved Test Procedures.

The Government may require that IPT be repeated over the life of this contract to requalify the product; should the contractor fail to deliver any of these items for a period of one year, make changes to products and/or processes, change a supplier of a component, or move the production line.

The Government reserves the right to waive IPT for contractors that have previously qualified by Product Manager Soldier Maneuver Sensors, CECOM Integrated Logistics Support Center (ILSC), and DEVCOM C5ISR Center and have completed Initial Production Testing. The contractor shall be required to provide evidence that their product has been previously qualified by Product Manager Soldier Maneuver Sensors, CECOM Integrated Logistics Support Center (ILSC), or DEVCOM C5ISR Center and have maintained production, with deliveries to the Government within a period of one year, prior to the Government approving a waiver. The Government also reserves the right to require an IPT if the contractor fails to deliver for a year or there are design changes which require requalification.

The Government reserves the right to conduct an operational test (OT), to include compatibility testing, to ensure the system is operationally effective and suitable, and interoperable with other Army equipment. If an OT is required, IPT approval is contingent on a successful OT.

As part of IPT, the contractor shall:

a. Develop the Qualification Test Plan (QTP) and test procedures necessary to demonstrate that these units conform to the requirements established by the applicable specification(s) and other technical data provided in this contract.

b. Notify the Government and test the IPT units.

c. Provide a Qualification Test Report to the Government which documents the IPT results.

d. Insure all equipment used to take performance readings for acceptance tests are kept within the performance parameters delineated by the manufacturer of that equipment and capable of satisfying the performance parameters of this contract. All equipment manufactured by the contractor shall be listed and the parameters established and maintained for this equipment also.

The sample size shall be 20 units. All IPT samples shall be assembled at the same location at which production units will be assembled, using the same parts, materials, and manufacturing processes to be employed for subsequent production.

Exhibit A SPRBL1-24-R-0013 Page 12 of 19

Prior to any IPT or Qualification, the contractor shall submit a Qualification Test Plan (QTP) in accordance with CDRL E001 and this document. IPT shall be performed IAW the MIL-PRF- A3256363G, the Government approved QTP, Government approved test procedures, and this document. In addition to the information required by DI-NDTI-81307A, this submission shall contain:

a. The delineation and allocation of tests to be performed on each of the IPT units and the order of such tests.

b. Test milestones schedules and the contractor's test readiness posture.

c. A table which cross references the paragraph number of the specification requirement

(including a brief description of the requirement) and the associated test procedure number.

Prior to IPT and Conformance Inspection, the contractor shall submit all Test Procedures to be used in accordance with CDRL F001 and this document. Test Procedures shall contain:

a. Step-by-step test procedures for each test.

b. Data sheets to be employed to document the results of testing.

c. Identification of required test facilities, equipment and personnel.

The contractor shall submit a Quality Validation Plan (QVP) in accordance with CDRL D001 and this document. Conformance Inspection shall be performed in accordance with the Government approved QVP. In addition to the information required by DI-NDTI-81307A, this submission shall contain:

a. The delineation and allocation of tests to be performed as Conformance Inspection on subsequent production lots, to include the order of tests and the sampling plan.

b. Identification of required test facilities, equipment and personnel.

c. Test milestones schedules and the contractor's test readiness posture.

d. A table which cross references the paragraph number of the specification requirement (including a brief description of the requirement) and the associated Test Procedure number.

The contractor shall submit a Qualification Test Report (QTR) in accordance with CDRL G001 and this document. Initial Production Testing approval shall be contingent upon the submission of a complete and acceptable QTR to include verification of corrective action for reported IPT Failures to include adequacy of identified changes to the design/manufacturing process. IPT samples shall meet all contractual requirements, or all variances shall be documented by Government approved waivers.

Exhibit A SPRBL1-24-R-0013 Page 13 of 19

The QTR Report shall be complete, accurate, and readable and shall provide sufficient data to determine that the hardware item meets all the requirements delineated in the contract. The report will include the following:

a. Contractor's name and address.

b. Contract number.

c. Nomenclature, type number and (if assigned) stock number of item represented by the First Article.

d. Name and address of plant where IPT samples were fabricated and assembled.

e. Place and date of performance of tests.

f. Identification of applicable test and inspection equipment used in performance of

Initial Production Testing.

g. Sample size or quantity submitted for test or inspection.

h. A table which cross-references the paragraph numbers of the specification, the test procedures, and data sheet entry.

i. Complete test results showing actual or quantitative observations and all required calculations, allowable tolerances for each parameter, date the test was performed, the name and signature of tester, name and signature of the Government verifier/witness, and serial number of the equipment.

j. The final revision of the Government approved FIAR for each failure that occurred and it’s corresponding approval letter.

The contractor shall report all IPT Failures and submit a Failed Item Analysis Report (FIAR) IAW CDRL H001 and this document. For any failure that occurs in a Government conducted Operational Test (OT), the contractor shall submit a FIAR and incorporate corrective actions.

The IPT samples shall NOT serve as a manufacturing standard. Upon successful completion of IPT, Items which are refurbishable and made fully compliant with contractual requirements shall be delivered as production items. The Government shall determine the acceptability of all IPT samples. Those items which are not refurbishable shall not be delivered as production items.

The contractor shall conduct Conformance Inspections for all product delivered in accordance with the Government approved Quality Validation Plan, MIL-PRF- A3256363G, and this document. Conformance Inspection procedures used to test production units shall be identical to those used to test First Article samples. After IPT is approved, any proposed changes to the QVP and/or production test procedures will be submitted per CDRL D001 and F001 for

Exhibit A SPRBL1-24-R-0013 Page 14 of 19 evaluation. Such submissions will provide complete justification for the change. Changes to the approved test procedures shall not be implemented without written Government approval.

Delivery of subsequent lots shall not be made prior to successful completion of Conformance Inspection.

The contractor shall notify the cognizant Government Quality Assurance Representative (QAR) in writing at least 2 days in advance, of the time and place for each Conformance Inspection.

The contractor shall notify the QAR in writing within 2 working days of completion of Conformance Inspection for a specific production lot.

The contractor shall notify the PCO and Technical Activity in writing upon completion of Conformance Inspection. This notification will be submitted by email not later than 10 days after the test is completed, and will include:

a. Contract Number.

b. Item Identification (Nomenclature and/or Part Number)

c. Date of Testing

d. Lot Size, Number, and time frame represented

e. Sample Size

f. List of any associated failures

The contractor shall report each IPT Failure and each Conformance Inspection failure occurring in Test Groups B, C, and D, to the Government Quality Assurance Representative (QAR) and the Technical Activity (see Block 16 of CDRL H001) within 48 hours of failure occurrence. Within 10 working days of failure occurrence, the contractor shall submit a Failed Item Analysis Report (FIAR) through the cognizant QAR to the Technical Activity as required by CDRL H001. In addition to the information required by DI-SESS-81315B, the report shall include:

a. Contractor's name, address and applicable contract number

b. Identification of failed item

c. Number of units in lot and sample size

d. Date and time of failure occurrence

e. Failure Mode

f. Summary of failure analysis

g. Root cause of failure

h. History of the failure

i. Proposed Corrective Action to eliminate root cause, contain the failure, and prevent reoccurrence

j. Re-inspection plan to validate the corrective action

k. Proposed disposition of failed item and lot

l. Verification that Corrective Action was effective.

The contractor shall implement the proposed corrective action on all units in the lot, select new samples and conduct re-inspection and other required re-testing in accordance with the re

Exhibit A SPRBL1-24-R-0013 Page 15 of 19 inspection plan in the FIAR. Results of the re-inspection and validation of the corrective action shall be included in the FIAR.

Final acceptance and shipment approval will be withheld until results of the re-inspection substantiate that the corrective action was effective and the FIAR was accepted, as authorized by the PCO.

The contractor shall prepare and submit a Production Reliability Acceptance Test (PRAT) for each production lot subjected to Reliability Testing. The PRAT shall be prepared in accordance with CDRL I001 and this document. PRAT shall include but not be limited to a test summary, test description, identification of item(s) under test, lot from which the test sample was taken, lots represented by the sample, test group number, performance requirements, measured values taken during the test, conclusions, and applicable failed item analysis reports (FIARs).

In the event of an Image Intensifier Reliability lot failure, the Government may, with Contractor concurrence, agree to accept consideration in lieu of correcting units that have already been delivered to the Government. The following calculation shall be used to determine the amount of consideration.

Damages = [ ( MTTFREQ – MTTFDEM ) / ( MTTFREQ ) ] * # of units * cost per unit

MTTFREQ = Mean Time To Failure Required MTTFDEM = Mean Time To Failure Demonstrated

The number of units in the above calculation shall be all units delivered since the last production lot to successful complete Reliability test, or any other number of units as agreed to by the Government. The MTTF used in the equation is a cumulative total of all samples subjected to Reliability Testing in that particular lot. When calculating the MTTFDEM for the lot, the MTTF demonstrated for an individual unit shall not exceed the required MTTF for that unit.

The contractor shall prepare and submit an Electromagnetic Interference (EMI) test report documenting the results of all required EMI Testing. The EMI Test Report shall be prepared in accordance with CDRL L001 and this document.

A Government-approved calibration system with respect to radiation sources, photometric equipment, color temperature, and ancillary equipment shall be maintained to support this program. Test requirements matrices shall be found in the pertinent MIL-PRF. Test environments shall be maintained that provide the ability to produce the environmental conditions required to verify performance of delivered product in accordance with system/component performance specifications and the approved test procedure. The US Government’s C5ISR Center, Fort Belvoir, Virginia, defines all of test conditions, technical interpretations, and test methods for the Image Intensifier Tube. The contractor shall have an equal or superior approach to that defined in the associated MIL-PRF documents. If the contractor approach is different than as defined in the associated MIL-PRF documents, Government approval is required for its use. Government-approved production test and acceptance equipment performance will also be monitored through Round Robin correlation tests

Exhibit A SPRBL1-24-R-0013 Page 16 of 19 between the contractors and C5ISR Center. The contractor shall maintain not fewer than three

(3) each contractor-owned image tube standards of each tube assembly and module type. For these image tube standards, the contractor shall maintain measurement records for critical performance parameters including Signal-to-Noise (SNR), Center Resolution, Luminance Gain, Saturation, Equivalent Background Input (EBI), Halo, Modulation Transfer Function (MTF), and Photocathode Sensitivity. These measurements shall be made and documented on at least a quarterly basis (i.e., no longer than every 90 days) and all such data shall be made available to the Government upon request for the life of the contract. All such measurements shall be performed on actual production test and acceptance equipment.

The contractor shall allow the Government to visit the contractor’s production test/evaluation facilities on up to a quarterly basis, in order to ensure conformance with the above requirements.

As part of this process, the contractor shall also measure during this visit, up to fifteen (15) Government-owned tube assemblies and modules of each tube type. These measurements will be used for correlation assessments against measurements made at the C5ISR Center, as well as other manufacturing facilities and DoD organizations. In the case of discrepancies between measurements made at the C5ISR Center and the contractor’s facility, the C5ISR Center’s measurements shall take precedence; the contractor shall correct their measurement system or methodology to bring their measurements into correlation with those of the C5ISR Center; and the Government shall stop product acceptance until such time that the contractor measurement system is brought into correlation with that of the C5ISR Center.

CONTRACT SECURITY REQUIREMENTS

The contractor shall adhere to the requirements of the signed DD-254 Contract Security Classification Specification and "Security Classification Guide (SCG) for Image Intensifier Devices". In the event of a discrepancy between the signed DD 254, included as an attachment to the solicitation/contract, and the language in this section, the signed DD 254 information shall take precedence.

Contractor is required to access and authorized to receive, store, and generate Controlled Unclassified Information (CUI) in the performance of this contract. Information designated as CUI, e.g., For Official Use Only (FOUO), generated or provided under this contract shall be controlled, handled, stored, marked, safeguarded, transmitted, and destroyed IAW DoDM

5200.01 Vol 4, DoDM 5400.0, AR 380-5, AR 25-55, AR 25-2, and the following guidance:

• Electronically transmitted CUI shall be sent via:

1) Encrypted email

2) Password protected/encrypted document.

3) DoD Safe Access File Exchange at https://safe.apps.mil

4) An accredited information system with proper security controls.

• The contractor may disseminate CUI information to their employees and subcontractors that have a need-to-know.

https://safe.apps.mil/

Exhibit A SPRBL1-24-R-0013 Page 17 of 19

• The contractor shall report the unauthorized disclosure of CUI to the KO/COR, CM, or

ISS.

Contractor is authorized to receive, store, and generate classified material at the contractor’s facility. Contractor will reference the appropriate security classification guidance when generating or deriving classified material or hardware, reference item 10k on the DD-254. All classified information received or generated will be properly stored and handled according to the markings on the material. All classified information received or generated is the property of the U.S. Government. At the termination or expiration of this contract, the U.S. Government will be contacted for proper disposition instructions.

If performing on contractor site, the contractor shall develop an OPSEC Plan IAW AR 530-1 as listed in the TRD CDRL number M001. The Requiring Activity (RA) is responsible for providing to the contractor a current and valid program/command OPSEC Plan. The contractor will use the program/command OPSEC Plan to ensure the contractor developed OPSEC Plan includes the same Critical Information List (CIL) and OPSEC measures.

PROGRAM MANAGEMENT REQUIREMENTS

The Government and contractor shall incorporate an Integrated Product and Process Team (IPPT) discipline into the OMNI program. The objective of the IPPT is to implement an open shared data/information environment with results-oriented objectives of on schedule delivery of specification compliant units, continuously improving the various Government/contractor processes, and reducing the system life cycle cost. The IPPT shall also complete the following additional actions throughout the life of the contract:

a. Hold IPPT reviews.

b. Use risk management techniques to document, track, and manage program areas of risk.

c. Review/concur in program documentation.

d. Review follow-on Initial Production Tests (IPTs) with the goal of reducing repetitive testing.

e. Review/concur on all Failed Item Analysis Reports (FIARs), ECPs, Request for

Variances, and Trade studies.

The IPPT process as described in paragaraph(s) is solely to facilitate communications between the Government and contractor during contract administration. Responsibility for dealing with issues raised and for meeting all contract requirements remains with the contractor. No communication made during the IPPT process may be construed as a change unless specifically designated by the PCO.

The IPPT membership shall consist of Government and contractor personnel associated with the ANVIS program and related efforts. CECOM, Integrated Logistics Suport Center (ILSC), Enterprise Soldier Aviation (ESA) Directorate shall co-chair the IPPT with the associated contractor counterpart. The IPPT chairpersons shall concur on all items requiring IPPT concurrence. The co-chairs shall define IPPT membership and issue escalation procedures at the

Exhibit A SPRBL1-24-R-0013 Page 18 of 19 post award conference. For each meeting, the contractor shall prepare and submit an agenda and briefing charts to the Government in accordance with CDRL J001. The contractor and Government at the end of each review/meeting shall jointly prepare action items and review/meeting minutes. The contractor shall submit the meeting minutes and action item list to the Government in accordance with CDRL K001. The contractor shall schedule, prepare for, and conduct the following reviews/meetings with Government concurrence:

The contractor shall participate in and support IPPT reviews at approximately 90-day intervals.

IPPT reviews may be conducted as teleconferences or video-teleconferences (VTCs) if mutually agreed upon by the IPPT chairpersons. IPPT reviews shall provide a working level forum to identify, discuss, and resolve issues that are, or could, affect the systems performance, design, production, testing, logistics support, system deliveries, life cycle cost, and program schedule.

Risk mitigation documentation shall also be reviewed.

Reports, Reviews, Meetings. Reports, reviews and meetings shall be required on a bi-weekly basis for this contract. The contractor shall be available for informal reviews and Government visits in addition to the IPPT reviews. The contractor shall participate in an informal bi-weekly meeting, to identify, discuss, and resolve issues.

The contractor shall submit, as a minimum, written program correspondence or documentation via electronic submittal. The preferred method of file submission is via e-mail. Deviations from this requirement are allowed on a case-by-case basis, with Government verbal concurrence (either Government IPPT chairpersons or Government contracting officer).

Transmission of Classified Material shall be in accordance with DoD 5220.22-M.

Data items shall be submitted to the Government via electronic media. The electronic format shall be compliant with Microsoft Office for text documents, spreadsheets, graphics presentations, and program schedules.

It is the Government’s intent to use Contractor Integrated Technical Information Service (CITIS) to gain on-line access to contractor-maintained data, configuration files, and information supporting this contract. The type of information to be placed on CITIS shall be concurred to by the IPPT prior to its implementation. The most recent version of all data shall be made available within five working days of being updated. The CITIS shall allow the Government the capability of retrieving all current and last modified versions of documentation. If the contractor determines this to be a restrictive cost driver, they can propose any alternative data submittal process (i.e. electronic data submittals, e-mail, etc.). Classified data shall be provided on magnetic or optical media. Classified data shall be handled in accordance with DoD 5220.22-M and DD Form 254 attached to the contract. Any restrictions on the use of the electronic data shall be as prescribed in the Data Rights Clause.

Exhibit A SPRBL1-24-R-0013 Page 19 of 19

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

Refer to separate attachment for CDRLs.