Attachment_0001_Technical_Requirements_Doc-SOW_12-19-2018.pdf

Attachment 0001 SPRBL1-19-R-0026 Page 1 of 12 Issue: 19 December 2018

STATEMENT OF WORK

(TECHNICAL REQUIREMENTS DOCUMENT)

Eleven Spare Parts To Support

AN/AVR-2B Laser Detecting Set

Attachment 0001 SPRBL1-19-R-0026 Page 2 of 12

Statement of Work

1.0 Scope. This Statement of Work (SOW) defines the efforts required to produce the products required by this solicitation in accordance with the Documents listed below. The items being purchased are entitled “ Sensors, Comparators and its Associated Circuit Card Assemblies, all part of AN/AVR-2B Laser Detecting Set (LDS)”.

2.0 Applicable Documents. The following documents are applicable to the extent cited.

2.1 Military Standard

Document No Document Title Applicability

MIL-STD-129R Military Marking for Shipment and Storage Required

MIL-STD-130N

w/change 1 Identification Marking of U.S. Military Property

Required

MIL-STD-2073-1E

With change 1

Standard Practice for Military Packaging Required

2.2 Military and Federal

Specs

NONE

2.3 Other Department of

Defense Document No.

AG00000655

Document Title

CECOM Special Packaging Instruction

Applicability

2.4 Commercial Document

No.

International Standards for Phytosanitary Measures (ISPM) Number 15

Regulation of Wood Packaging Material in International Trade

2.5 Availability of DOD Documents. Unless otherwise indicated copies of specifications, standards, and handbooks listed above are available from the Standardization Document Order Desk, 700 Robbins Ave, Bldg.

4D, Philadelphia, PA 19111-5094.

Attachment 0001 SPRBL1-19-R-0026 Page 3 of 12

3.0 Requirements. The contractor shall produce the items in the quantity set forth in Section B of the schedule in accordance with Documents listed above and this SOW. In the event of a conflict between the requirements of this SOW and any drawings for the item on contract, the requirements of this SOW shall govern.

3.1 Requirements for Packaging. Preservation, packing and marking for shipment shall be in accordance with (IAW) Section 'D' of the contract. Packaging shall be IAW CECOM Special Packaging Instruction (SPI) AG00000655 for NSNs 5860-01-511-8345 and 5865-01-514-2857, and IAW MIL-STD-2073-1E for the remaining NSNs. Level of Preservation (LOP): Military, Level of Pack (LPK): B, Quantity Unit Pack (QUP):

001. Marking shall be IAW MIL-STD-129R. Radio Frequency Identification (RFID) requirements shall be IAW the Section "F" clause, DFARS 252.211-7006, of the contract. MIL-STD-129R is applicable.”

3.1.1 Wood Packaging Material (WPM) shall meet the requirements below.

3.1.2. Wood packaging material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frame and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSB).

3.1.3. All WPM shall meet the requirements of 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.

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

3.1.5. 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 ASLC approved DUNNAGE stamp.

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

3.2 Requirements for Configuration Management.

3.2.1 Product Definition Information. The Product Definition Information describes a product’s performance, functional and physical attributes, including the requirements and design information (specifications, drawings, design descriptions and software). Interfaces, including interfaces with other products, are also documented in the Product Definition Information. The Product Definition Information shall be specified by the Contractor’s Item Part Number (CIPN).

http://www.alsc.org/

Attachment 0001 SPRBL1-19-R-0026 Page 4 of 12

3.2.2 Configuration Change Process. The contractor shall establish a system for managing the configuration changes to the CIPN baseline.

3.2.3 CIPN Configuration Baseline. The Contractor’s Item Part Number (CIPN), as defined by the Contractor’s specifications, drawings, catalog page, etc, at the time of award of this contract, shall form the Configuration Baseline for this acquisition.

The applicable Configuration Baseline (CB) for the listed Configuration Item (CI)/Computer Software Configuration Item (CSCI) is as follows:

CB CI/CSCI

L31-20000 L31-30000

L31-22103 L31-22202

SCD L31-0039A

L31-34002 L31-35002 L31-36002 L31-24000 L31-32300 L31-23200

Sensor Unit (SU), SU-130B/AVR-2B(V) Signal Comparator Module (SCM), CM-

493B/AVR-2B(V)

Circuit Card Assembly (CCA), SU Detector CCA, Sensor Processor Board SU Power Supply SCM CCA, Connector Board Assembly SCM CCA, Processor Board SCM CCA, Power Supply House Sensor unit w/window Signal Comparator Module Internal Cable Harness

3.2.4 Configuration. Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) and any subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO).

3.2.5 Application Management.

3.2.5.1 Application Management. In performing Application Management, the Government must assess the impact of design changes to the Configuration Item. The Government is the Configuration Management authority on application management for all external applications and for all Major changes that affect the Item Part Number (CIPN). A Major change is defined as any change that will impact any of the following conditions of the CIPN:

(a) Overall performance and Form, Fit, Function and Interface (F3I) Characteristics.

(b) Reliability, Maintainability and Survivability (c ) Electromagnetic Interference (EMI), air worthiness certification, or other pertinent requirement.

(d) Safety

(e) Support, operational and training requirements

(f) Impact on Technical Manuals, Repair Parts and Special Tools Lists (RPSTLs), DMWRs, Provisioning Parts List (PPL), etc.

Attachment 0001 SPRBL1-19-R-0026 Page 5 of 12

(g) Impact on Cost and/or Schedule.

(h) Impact on test equipment, support equipment and associated software.

(i) Software.

3.2.5.2 Application Activity. The Government is an Application Activity (AA) for changes that affect the Contractor’s CIPN. The Government does not possess document change authority over the changes affecting the CIPN. As part of the Government’s Application Management process, the Government as AA does have a right to review or be notified of changes made by the Contractor that will affect any of the conditions identified in paragraph 3.2.5.1. Any changes that affect these conditions shall be submitted for Government review or notification IAW the procedures outlined below (para 3.2.5.3). Configuration changes not directly affecting the configuration baseline conditions identified in paragraph 3.2.5.1 do not require Government review or notification.

3.2.5.3 Departures from CB. Changes that affect the CIPN conditions cited in paragraph 3.2.5.1 shall be submitted for Government review or notification in accordance with this SOW and the DD Form 1423 for DI- MISC-80711A. Upon receipt of notification, the Government will review the impact of the change.

3.2.5.3.1 Request For Change (RFC). The Request For Change (RFC) includes both the engineering change and the supporting documentation by which the change is described and suggested. An RFC describes changes to the CI/CSCI and associated Contractor documents and data (if applicable) that are affected by the proposed engineering change. The RFC also describes a full impact analysis of the effect of the change on the logistics, interface, design, cost and schedule requirements of the CIPN.

3.2.5.3.1 .1 RFCs could be generated as any of the following categories: Change Directive; Change Request;

Engineering Change Package; Engineering Change Proposal; Engineering Change Request; Engineering Change Memo; Engineering Change Notice.

3.2.5.3.1.2 RFCs may contain some of the following elements:

(a) A unique change identifier; identification of originating organization and responsible individual.

(b) Change classification, (c ) Identification of product(s) (including components and interfacing products) affected by the change.

(d) Change description and scope (including effects on performance, operation, maintenance, servicing, operation and maintenance training, repair parts, support and test equipment, cost, schedule, and any other effect on physical, functional, and logistics characteristics of the CIPN).

(e) Reason and justification for the change and consequences of not incorporating the change.

(f) Estimated cost increase or savings.

(g) Change implementation (and effectivity) and impact on delivery schedule.

(h) Criteria, if any, for retrofitting products.

3.2.6 Contractor-approved changes that adversely impact any of the CIPN conditions listed in paragraph 3.2.5.1 may require re-evaluation by the Government of the CIPN. Re-evaluation may include operational testing re-assessment or re-assessment of the logistics impact of the proposed change. An approved change to the design of the CIPN must be verified to ascertain that the CIPN has achieved the functional attributes and requirements specified in the baselined Product Definition Information (CIPN) and that it is adequate for its intended purposes. The Government is not obligated to accept any CIPNs that no longer meet the Government’s requirements as established by the CIPN at the time of contract award.

Attachment 0001 SPRBL1-19-R-0026 Page 6 of 12

3.3 Requirements for Item Marking .

3.3.1. Part Number Marking. Each item delivered under contract, along with each assembly, subassembly, and module, shall be legibly marked with the appropriate part number and manufacturer’s identification. Hardware such as screws, nuts, bolts, etc., need not be marked. The marking shall become permanently part of the item after it is applied, and can be applied using deformation, tag, rubber stamp with permanent characteristics, etc.

The marking shall not interfere with proper operation of the item, and shall have no deleterious effect on the item. Any item deemed unsuitable for marking as outlined herein shall be identified to the Contracting Officer for resolution as to marking requirement. This requirement may be entirely met by existing marking requirements contained within the drawings or specifications cited in this contract.

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

3.3.3. Serial Number Marking.

3.3.3.1. 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 contractor shall obtain a block of serial numbers from the Government within 30 days of request from:

Commander, US Army Communications-Electronics Command

ATTN: AMSEL-LCW-SSN

APG, MD 21005

The contractor shall include the following information in the request:

1) Contract Number

2) Quantity of item on contract

3) Item’s part number as noted in Section B of the contract.

4) Contractor’s name and address.

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

3.4 Requirements for Item Unique Identification (IUID). The contractor shall mark all contract deliverables In Accordance With (IAW) DFARS clause 252.211-7003 in Section F of this contract and the following requirements.

3.4.1 IUID Marking.

Attachment 0001 SPRBL1-19-R-0026 Page 7 of 12

3.4.1.1. New items: The contractor shall provide IUID, or DoD recognized equivalent, for all items delivered, or any item the Government requires to be serial numbered. For long term contracts, the Contractor shall implement IUID markings IAW MIL-STD-130R for any range quantity or contract year. This requirement is effective throughout the life of this contract.

3.4.1.2. Repair items: For items returned under warranty for repair shall be inspected for IUID markings. Those items where the marking is damaged or missing the contractor shall mark the equipment. When marking requirements are not clearly specified then the contractor shall advise the PCO. For previously acquired items where the IUID markings were not required the contractor shall follow the procedures as if the item was a new item.

3.4.1.3 Commercial Markings. All other items shall have acceptable commercial markings that meet the guidelines in Department of Defense (DoD) Guide to Uniquely Identifying Items http://www.acq.osd.mil/dpap/pdi/uid/index.html.

3.4.1.4 Permanency and Legibility. The IUID 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-130R.

3.4.1.5 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.4.1.6 Mandatory Information Reporting for all items requiring IUID marking. The contractor shall include the National Stock Number (NSN), if the item has a NSN, the Serial Number marked on the item, if a Serial Number is marked on the item, the original part number, the current part number (only if not the same as the original part number), the current part number effective date (only if the current part number is used) and the USARMY as the SERVICE /AGENCY/COMMAND data element in the information reported to the IUID Registry, in addition to the information required to be reported to the IUID Registry by DFARS clause 252.211- 7003.

3.4.1.6.1 Wide Area Workflow (WAWF) users shall report this mandatory information to the IUID Registry by Direct submission via an X12 Ship Notice/Shipment and Billing Notice (856/857) transaction, an IUID XML transaction, an IUID flat file transaction or a WAWF IUID Material Inspection and Receiving Report/Combo UDF through the Global Exchange (GEX) Service, or manually, via the IUID Web Entry Site at http://www.bpn.gov/iuid. For WAWF users, these methods do not replace the current WAWF interaction, but are performed in addition to it after the shipment has been accepted to provide IUID data that cannot be provided via WAWF.

3.4.2 IUID Coding. IUID markings and readability requirements shall comply with MIL-STD-130R.

3.4.2.1 Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD 130R. First priority is the 2D data matrix symbol (machine readable) IUID is the minimum http://www.acq.osd.mil/dpap/pdi/uid/index.html http://www.bpn.gov/iuid

Attachment 0001 SPRBL1-19-R-0026 Page 8 of 12 requirement when there are severe space limitations. The second priority is the human readable characters. The third priority is the Linear Bar Code.

3.4.2.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.4.2.3 Deleted.

3.4.2.4 Deleted.

3.4.2.5. 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. The contractor shall provide this list to the government at the end of the contract.

3.4.3 Correction of Noncompliant Equipment and Technical Data.

3.4.3.1 If this contract contains 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.4.3.2 If configuration control requirements do not apply and the equipment on order is defined by technical data which conflicts with or omits the marking requirements stated above, the contractor shall advise the PCO.

Such advice shall list the number of each deficient drawing/specification and a brief description of the deficiency.

3.4.3.3 If the item on order is defined by existing Government technical documentation and such documentation is in conflict with the requirements of this SOW, production of equipment with revised markings shall not proceed until Government approval is received.

3.5 Inspection and Testing. The contractor shall perform final inspection and testing on all deliverables in accordance with the contractor's Inspection and Testing Procedures. The contractor shall assure that all necessary inspections and tests are performed on completed products, and this shall include all inspections and tests, which are normally performed for the equipment on order. The contractor shall as a minimum perform any inspections and tests (including visual/mechanical inspections and functional tests) required to satisfy the form, fit, and function requirements of the contract. The form, fit, and function requirements are defined by the contractor's drawings and literature (specification sheets, brochures, technical manuals, etc).

3.5.1. Responsibility. The requirements of this SOW do not relieve the contractor of the responsibility to perform any additional tests or inspections required to assure product quality and compliance with drawings and specification requirements.

3.6. Requirements for Quality Assurance System. The contractor shall implement and maintain a Quality Assurance System to ensure product integrity that meets or exceeds the requirements established below. These

Attachment 0001 SPRBL1-19-R-0026 Page 9 of 12 requirements are commonly accepted practices employed by industry both in national and international environments.

3.6.1 Quality Approach. The contractor shall establish/maintain an approach to ensure product integrity and to satisfy contract or order requirements.

3.6.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 test and inspection resources necessary for assuring product integrity.

3.6.3 Document Control The contractor shall ensure that the latest revisions of drawings, specifications, work instructions, inspection/test instructions, and other documents required to satisfy the contract are utilized in production, inspection, and test.

3.6.4 Records. The contractor shall maintain records of all inspections and tests to demonstrate that the quality approach satisfies contract requirements.

3.6.5 Control of Purchases. The contractor shall ensure that all supplies and services which they purchase from suppliers conform to contract requirements. The contractor shall require that their subcontractors control the quality of their services and supplies.

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

3.6.7 Nonconforming Material. The contractor shall establish and maintain a approach for controlling material which does not satisfy contract requirements, including procedures for its identification, segregation, and disposition (rework/repair, scrap, etc.).

3.6.8 Corrective Action. The contractor shall promptly act to correct nonconforming materials and processes to preclude the recurrence of the problem and to satisfy contract requirements.

3.6.9 Manufacturing Operations/Process Controls. The contractor’s quality approach shall be responsible for assuring/monitoring that all manufacturing operations/processes are accomplished under controlled conditions.

Controlled conditions include documented work instructions (including workmanship), production equipment, special work environments, inspections/test operations, work specifications, and approval/rejection criteria.

3.6.10 Measuring, Testing, and Inspection Equipment. The contractor shall provide and maintain gages (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 which are traceable back to national/international standards.

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

Attachment 0001 SPRBL1-19-R-0026 Page 10 of 12

3.6.12 Quality Review. The contractor shall assure effectiveness of quality (e.g. internal quality audits, Statistical Process Control, and related measures).

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

3.6.14 Statistical Quality Control and Analysis. The contractor’s quality approach shall establish/utilize statistical methods whenever appropriate to satisfy the contract or order requirements.

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

3.6.16 Handling, Storage, Preservation, Packaging, and Shipping. The contractor shall establish/maintain procedures for handling, storage, preservation, packaging, and shipping to protect the quality of products and prevent damage, loss, deterioration, degradation or substitution of products.

3.7 SECURITY

Security. The security requirements for this task are defined in the attached DD Form 254 and U.S. Army Version of Aircraft Survivability Equipment, Security Classification Guide, dated 4 February 2014, applies to this project. The contractor will be required to have a Secret facility with Secret safeguarding capability limited to two cubic feet at their facility. The contractor is authorized to receive, generate, and store classified material at the secret level.

In performing this contract, the contractor will receive and safeguard classified documents at their facility.

Administration duties will not require a clearance and may require investigation for IT duties.

3.7.1 For contracts that require OPSEC Training. Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. Level I OPSEC training is available at the following website:

http://cdse.edu/catalog/elearning/GS130.html (Duration: 45 minutes).

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

3.7 3 Information Security (INFOSEC). Contractor shall comply with FAR 52.204-2, Security Requirements.

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

Attachment 0001 SPRBL1-19-R-0026 Page 11 of 12

3.7.4 Threat Awareness Reporting Program. For all contractors with security clearances.

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

3.8 Requirements for Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.8.1 The Contractor shall execute a proactive DMSMS management program in accordance with (IAW) this SOW and ANSI/TA-STD-0016 for the period of performance of this contract. The program shall address how the contractor will identify part obsolescence issues, assess potential risk, develop an obsolescence strategy and determine the most cost effective solution to part obsolescence issues. The Contractor’s DMSMS/Obsolescence Plan shall also include procedures for both participation in the Government Industry Data Exchange Program (GIDEP) and the Obsolescence Working Group (OWG).

The Contractor shall ensure its subcontractors adhere to the DMSMS/Obsolescence requirements of this SOW.

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

3.8.2 DMSMS/Obsolescence Bill of Materials (BOM). In accordance with the CDRL for DI-SESS-81656 and this SOW, the Contractor shall submit and update semiannually a Bill of Material (BOM) for Logistics and Supply Chain Risk Management: Production Phase. The BOM shall include the system breakdown to the part level for all electronic, electrical, and electro-mechanical parts, assemblies and software components in the design. The BOM shall also include data entries for the known or projected End of Life (EOL) and case status, if a DMSMS case has been established for the item.

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

In the case of a privately-developed item which does not meet the definition of a commercial item and for which the government will be assuming configuration control of the item and funding engineering changes, the Contractor shall submit the BOM to the component-level.

The Contractor shall ensure that the BOM accurately reflects the current approved design IAW the Contractor’s DMSMS management plan and contract configuration management procedures

3.8.4 Obsolescence Working Group (OWG). The Contractor shall attend and participate at government Obsolescence Working Group (OWG) meetings. The purpose of the OWG is to review open DMSMS cases, the Contractor’s most recent DMSMS Roadmap & Technology Refresh Plan, the current metrics, and other DMSMS issues suggested by either the Contractor or the government. The OWG will meet semiannually at the Contractor’s facility, at government location, VTC, or telecom, with the first meeting occurring no later than 60 days after contract award (DAC). The government will establish the dates for each meeting and will be responsible for publishing the meeting agenda and minutes.

3.8.5 Technology Refreshment Planning. The Contractor shall perform technology refreshment planning based on the systems DMSMS Roadmap and known and projected DMSMS issues. In this regard, the contractor shall

Attachment 0001 SPRBL1-19-R-0026 Page 12 of 12 propose to the government a plan of technical refresh events to occur over a ten-year planning horizon. This plan will be optimized to maximize system readiness and minimize Life Cycle Cost (LCC). This plan shall include, for each recommended refresh event, a summary of the DMSMS issues to be mitigated, the estimated cost to execute, and an estimate of the projected benefits to the government in terms of both cost and improved weapon system readiness. Technology refreshment planning will be coordinated with any planned capability upgrade to allow for an integrated weapon system technical refreshment plan. This plan will include both hardware and software system components. The Contractor shall deliver this plan IAW the CDRL for DI- MISC-80711A, Scientific and Technical Report: 10-year Rolling Technology Refresh Plan and this SOW. Key details of the technology refreshment plan will be an agenda item for the OWG, and a proposed agenda item for any design reviews or contract In Process Reviews (IPR’s).

3.8.6 Metrics. As part of the contractor’s DMSMS program, they will develop a set of DMSMS metrics and document these metrics in the DMSMS management plan. These metrics will be collected by the contractor to document the benefit or effectiveness of the contractors DMSMS management program. Included in these metrics will be an assessment of the overall health of the product design from a DMSMS perspective achieved via analysis of the current BOM. These metrics will include the following at a minimum:

- Number of items on the BOM

- Number of items on the BOM which are less than two years to the end of life (YTEOL) date.

- Number of items with more than two but less than 5 YTEOL.

- Number of BOM items with whose timeline will likely impact readiness.

3.9 Usage of Government Furnished Equipment (GFE) Justification:

The contractor shall use the GFE listed on the attachment, titled, “Government Furnished Equipment for the Production and Operational/Functional Testing of the AVR-2B Spare Parts Acquisition”. These GFEs are already in place with Goodrich under the previous PM contract, W58RGZ-13-D-0147

2.5 Availability of DOD Documents. Unless otherwise indicated copies of specifications, standards, and handbooks listed above are available from the Standardization Document Order Desk, 700 Robbins Ave, Bldg. 4D, Philadelphia, PA 19111-5094.