Attach 0001 - Statement of Work (SOW).pdf

Statement of Work (SOW) For

AN/APR-39 C(V)1 Radar Warning Receiver

10 November 2020

PREPARED BY:

CECOM ILSC/ PRD

Final Version: 10 November 2020 Solicitation: SPRBL1-21-R-0010 P a g e - 1 - | 29

Table of Contents

1.0 Scope

2.0 Applicable Documents

3.0 Requirements

3.1 Requirements for Configuration

3.1.1 Product Definition Information

3.1.2 Configuration Change Process

3.1.3 CIPN Configuration Baseline

3.1.4 Configuration

3.1.5 Application Management

3.1.5.1 Application Management

3.1.5.2 Application Activity

3.1.5.3 Departures from CB

3.1.5.3.1 Request for Change (RFC)

3.2 Requirements for Quality Assurance System

3.2.1 Quality Approach

3.2.2 Initial Quality Planning

3.2.3 Document Control

3.2.4 Records

3.2.5 Control of Purchases

3.2.6 Materials Control

3.2.7 Nonconforming Material

3.2.8 Corrective Action

3.2.9 Manufacturing Operations/Process Controls

3.2.10 Quality Audits

3.2.11 Training Requirements

3.2.12 Continuous Process Improvement

3.3 Inspection and Testing

3.3.1 Acceptance Testing

3.3.2 Measuring, Testing, and Inspection Equipment

3.3.3 Inspection and Test Status

3.3.4 Software Test

Final Version: 10 November 2020 Solicitation: SPRBL1-21-R-0010 P a g e - 2 - | 29

3.3.4.1 Software Test Description

3.4 Technical Review Meetings

3.5 Requirements for Item Marking (Gov't Detailed and/or Performance Design Items)

3.5.1 Part Number Marking

3.5.2 National Stock Number (NSN) Marking

3.5.3 Serial Number Marking

3.5.3.1

3.5.3.2

3.6 Requirements for Item Unique Identification (IUID)

3.6.1 IUID Marking

3.6.1.1 New items

3.6.1.2 Commercial Markings

3.6.1.3 Permanency and Legibility

3.6.1.4 Deleterious Effect

3.6.1.5 Mandatory Information Reporting for all items requiring IUID marking

3.6.1.6 Wide Area Workflow (WAWF)

3.6.2 IUID Coding

3.6.2.1

3.6.2.2

3.6.2.3

3.6.3 Pricing of IUID Requirements

3.7 Handling, Storage, Preservation, Packaging, and Shipping

3.7.1 Shipping Address

3.7.2 Requirements for Packaging

3.7.3 Wood Packaging Material

3.7.3.1

3.7.3.2

3.7.3.3

3.7.3.4

3.7.3.5

3.8 Diminishing Manufacturing Sources and Material Shortages (DMSMS) / Obsolescence Management – Production

3.8.1 Definitions

Final Version: 10 November 2020 Solicitation: SPRBL1-21-R-0010 P a g e - 3 - | 29

3.8.2 DMSMS Management Program

3.8.3 DMSMS Management Plan

3.8.4 Design Changes

3.8.5 Subcontractor Management

3.8.6 DMSMS Costs

3.8.7 DMSMS BOM Establishment & BOM Monitoring

3.8.8 DMSMS BOM Delivery

3.8.9 DMSMS Alerts

3.8.10 Case Management

3.8.10.1 DMSMS Case Management Reports

3.8.11 DMSMS Roadmap

3.8.12 Metrics Report

3.8.13 Obsolescence Working Group (OWG)

3.9 Security

3.9.1 Threat Awareness Reporting Program

3.10 Technical Data

3.11 TAV- C

3.11.1 System Overview and Portal Access Requirements

3.11.1.1

3.11.1.2

3.11.1.2.1 Defense Logistics Management Standards (DLMS) Interfaces

3.11.1.2.2 Army TAV-C Portal

3.11.2 Portal Access Requirements

3.11.2.1 Contractor provided computer system

3.11.2.2 Security Requirements

3.11.2.3 User Training Requirements

3.11.2.4

3.11.3 Problem Resolution

3.11.4 DLMS Transactions / Portal Data Requirements

3.11.4.1

3.11.4.2

3.11.4.3 Army TAV-C Portal

Final Version: 10 November 2020 Solicitation: SPRBL1-21-R-0010 P a g e - 4 - | 29

3.11.4.4 Consumption Reporting

3.11.5 TAV-C Entries

Appendix 1

Appendix 2

1.0 Scope

This Statement of Work (SOW) defines the work efforts required for the Acquisition of the

Radar Warning Receive System items. The contractors shall provide the price quotes for on each National Stock Number (NSN) identified in Table 1 below as requested by the government.

Table 1:

Item Description/CI National Stock Number (NSN) Part Number AN/APR 39 C Processor 5841-01-543-6979 CP-1597C 001-008683-0001

IOP 5998-01-550-6653 150-038181

SPU 5998-01-550-8505 150-038182

MUX 5998-01-550-7630 150-038318

2.0 Applicable Documents

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

3.0 Requirements

The contractor shall produce the items in Table 1 of this Statement of Work SOW and in delivery orders issued by the Government 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 Configuration

3.1.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).

3.1.2 Configuration Change Process

The contractor shall establish a system for managing the configuration changes to the

CIPN baseline.

3.1.3 CIPN Configuration Baseline

The 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 listed in Table 1.

3.1.4 Configuration

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

3.1.5 Application Management

3.1.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 CIPN specified in paragraph 3.1.1. 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.

g) Impact on Cost and/or Schedule

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

i) Software

3.1.5.2 Application Activity

The Government is an Application Activity (AA) for changes that affect the 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.1.5.1. Any changes that affect these conditions shall be submitted for Government review or notification in accordance with (IAW) the procedures outlined below (para 3.1.5.3). Configuration changes not directly affecting the configuration baseline conditions identified in paragraph 3.1.5.1 do not require Government review or notification.

3.1.5.3 Departures from CB

As required changes that affect the CIPN conditions cited in paragraph 3.1.5.1 shall be submitted within 30 days for Government review or notification in accordance with this SOW and the DD Form 1423 for CDRL A001 for DI-MISC-80711A. Upon receipt of notification, the Government will review the impact of the change within 30 days.

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

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.

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

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/CSCI 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.

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.

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 guidance in Section I of this contract for VECPs.

Request for Waiver (RFW) describes a departure from configuration documentation for a specific number of units or period of time. Contractor shall identify the impact of the RFW on performance, operational readiness and logistics support of the affected CIs. The Government will require compensation for any RFW.

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.2 Requirements for Quality Assurance System

The contractor shall maintain a Quality Assurance System for higher-level product integrity that meets or exceeds the requirements established below. These requirements are commonly accepted practices employed by industry in both national and international manufacturing environments.

3.2.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.2.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.2.3 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.2.4 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.2.5 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.2.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 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.2.7 Nonconforming Material

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

3.2.8 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.2.9 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.2.10 Quality Audits

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

3.2.11 Training Requirements

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

3.2.12 Continuous Process Improvement

The contractor shall monitor the effectiveness of their quality approach and continually improve quality processes.

3.3 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 listed in Table 1.

3.3.1 Acceptance Testing

The contractor shall conduct processor acceptance testing IAW AN/APR-39C(V)1 Radar Data Processor & Kit Acceptance Test Procedure, dated 13 June 2013 (Document ID: 094- 014970, Rev C). AS well as Circuit Card level acceptance testing IAW INPUT/OUTPUT

PROCESSOR (IOP) CCA ENGINEERING TEST PROCEDURE FOR THE APR-39C(V)1

RADAR DATA PROCESSOR Document ID: 499-003673, SIGNAL PROCESSING UNIT

(SPU) CCA ENGINEERING TEST PROCEDURE FOR THE APR-39C(V)1 RADAR DATA

PROCESSOR Document ID: 499-003672, MULTIPLEXER (MUX) CCA ENGINEERING

TEST PROCEDURE FOR THE APR-39C(V)1 RADAR DATA PROCESSOR

Document ID 499-004578.

3.3.2 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 that are traceable back to national/international standards.

3.3.3 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.3.4 Software Test

3.3.4.1 Software Test Description

1. Circuit Card Assembly (CCA) programming and Test

1) The Contractor shall execute the program and test of the government furnished

AN/APR-39C(V)1 Signal Processor Unit (SPU) and the Multiplexer (MUX) CCA’s in accordance with Northrop Grumman (NG)drawings A040_322- 005141_Rev04_SPU and A041_322-005150_Rev_Mux

2) The Contractor shall execute all tests specific to the CCA in NG drawings referenced in (a) and provide the test results in PDF format for the individual cards.

3) The Contractor shall not perform referenced NG drawing in paragraph (a) program/test CCA if visual inspection indicates CCA damage.

4) The Contractor shall insert the programmed CCA’s individually in a APR-39C(V)1 processor with a compatible OFP to the programmed CCA’s. The Contractor shall execute the IBIT on the processor and record result. The Contractor shall provide the results of the IBIT testing in Contractor format for each individual programmed

CCA.

5) The Contractor shall utilize AN/APR-C(V)1 OFP 524.0 files for programming.

3.4 Technical Review Meetings

The Contractor shall host up to four (4) one-day Engineering Technical Interchange Meetings (TIMs) at the Contractor’s facility during the period of performance. Engineering TIMs may be conducted concurrently with other APR-39 program meetings. Meeting minutes from Engineering TIMs shall be provided to the USG IAW CDRL A002 DI-ADMN-81505. The government requires 30 days to provide comments.

3.5 Requirements for Item Marking (Gov't Detailed and/or Performance Design Items)

3.5.1 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.5.2 National Stock Number (NSN) Marking

In addition to the marking required by para 3.7.1 above, 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.5.3 Serial Number Marking

3.5.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 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.5.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.6 Requirements for Item Unique Identification (IUID)

The contractor shall mark all contract deliverables In Accordance With (IAW) Defense

Federal Acquisition Regulation Supplement (DFARS) clause 252.211-7003 in Section F of this contract and the following requirements.

3.6.1 IUID Marking

3.6.1.1 New items

The contractor shall provide IUID, or DoD recognized equivalent, for all items delivered with a per unit acquisition cost of $5000 or more. For long term contracts, the Contractor shall implement IUID markings IAW MIL-STD-130N w/Ch1, dated 16 Nov 12 for any item that will exceed the $5,000.00 unit price for any range quantity or contract year. This requirement is effective throughout the life of this contract.

For items which currently have IUID Marking requirements defined on its applicable drawing, the contractor shall continue to apply IUID Marking directly to those items. For all other items that do not currently have IUID Marking requirements on it’s applicable drawing, the contractor shall individually package each item and apply the IUID marking to each individual items packaging.

3.6.1.2 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.6.1.3 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-130N w/Ch1, dated 16 Nov 12.

3.6.1.4 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.6.1.5 Mandatory Information Reporting for all items requiring IUID marking The contractor shall include the 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.6.1.6 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.6.2 IUID Coding

IUID markings and readability requirements shall comply with MIL-STD-130N w/Ch1, dated 16 Nov 12.

3.6.2.1 Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD-130N w/Ch1, dated 16 Nov 12. 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.6.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.6.2.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. The contractor shall provide this list to the government at the end of the contract.

3.6.3 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, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price.

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

3.7.1 Shipping Address

The “ship to” address is below or other destination as defined on task order/delivery order. Task order/delivery order destination will take precedent

DODAAC: W25G1W, RIC: BY6

W1BG UEF DIST DEPOT TOBYHANNA

GIBBS AND FIFTH STREETS

WAREHOUSE 6 BAY 4

TOBYHANNA PA 18466-5059

3.7.2 Requirements for Packaging

Preservation, packing and marking for shipment shall be in accordance with Section "D" of the contract. Marking is in accordance with MIL-STD-129R.

Radio Frequency Identification (RFID) Requirements shall be IAW the Section ‘F’ clause, DFARS 252.211-7006, of the contract.

Packaging shall be in accordance with MIL-STD 2073-1E. Level of Preservation (LOP):

Military, Level of Pack (LPK): B, Quantity Unit Pack (QUP):001.

Shipments will be marked and labeled IAW MIL-STD-129 to include the following information on the outer label:

The contractor shall include the following information on the label affixed to the outside of the shipping container:

a) Contract Number

b) Quantity of item on contract

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

d) Contractor’s name and address

e) NSN

f) CAGE Code

g) Part Number

h) UID

3.7.3 Wood Packaging Material

Wood Packaging Material (WPM) shall meet the following requirements.

3.7.3.1

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 anufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSB). See DLAD 52.247-9012 Requirements for Treatment of Wood Packaging Material (WPM).

3.7.3.2

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

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

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 http://www.alsc.org/ 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.7.3.5

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.8 Diminishing Manufacturing Sources and Material Shortages (DMSMS) /

Obsolescence Management – Production

3.8.1 Definitions

For the purpose of this section, key definitions have been included for reference in Appendix 2 of this document. Additional terms and definitions are provided in the definition paragraph of ANSI/TA-STD-0016 and Table 9 of the DMSMS Guidebook, SD-22.

3.8.2 DMSMS Management Program

For the weapon system on contract, the Contractor shall establish and execute a DMSMS management program in accordance with (IAW) this SOW and ANSI/TA-STD-0016 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 address how the Contractor will identify or predict DMSMS Issues over a 5 years planning horizon, assess potential risk, develop an obsolescence mitigation strategy to determine the most cost effective solution to DMSMS Issues. The program shall also include a description of their process 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). The program shall also include procedures for sharing information with GIDEP and participating with the government in a Obsolescence Working Group (OWG).

3.8.3 DMSMS Management Plan

The Contractor’s plan to conduct the DMSMS/Obsolescence program shall be documented in a DMSMS Management Plan (DMP) prepared and delivered IAW DI-MGMT- 81948, DMSMS Management Plan (CDRL A003), ANSI/TA-STD-0016 and this SOW.

ANSI/TA-STD-0016 may be used as a guide. The Contractor is encouraged to make use of or tailor and existing in-house corporate DMSMS or Obsolescence management plans.

The Contractor’s DMP shall include a description of their process and procedures for selecting parts and whether they utilize a Preferred Parts List (or equivalent) to accomplish this.

With regard to predicting DMSMS issues over the 5 year planning horizon, the DMP shall identify any predictive tools or services which the contractor intends to use to accomplish this.

The DMP shall also document the procedures for both participation in the Government Industry Data Exchange Program (GIDEP) and Obsolescence Working Group (OWG) meetings.

3.8.4 Design Changes

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

3.8.5 Subcontractor Management

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

3.8.6 DMSMS Costs

The Contract cost for the following shall be priced in the contractors RFP submittal and included in the basic contract at time of award:

a) DMSMS Program Management

b) DMSMS BOM establishment & monitoring

c) Case Management activities

d) OWG participation and support

e) DMSMS Management Plan CDRL submission

f) DMSMS BOM CDRL submissions

g) Case Management Report CDRL submissions

h) DMSMS Roadmap CDRL submissions

i) DMSMS Metrics CDRL submissions

Upon government acceptance of a proposed DMSMS Issue solution, the PCO may request that the contractor submit a priced proposal or ECP for the purpose of implementing the recommended solution. In addition, the PCO may also ask that the contractor identify any cost changes to any production and/or maintenance CLIN’s affected by this solution.

3.8.7 DMSMS BOM Establishment & BOM Monitoring

For the weapon system under DMSMS management, the contractor shall develop, with the government concurrence, a DMSMS BOM of those items on the manufacturing BOM which are planned to be proactively monitored for availability. For the purpose of this task, the initial baseline of the DMSMS BOM shall be all electronic, electrical and electromechanical (EEE) components; all commercial SW and all commercial or COTS assemblies. This initial baseline may be revised at the time of award by the government acceptance of recommended changes offered by the contractor in their proposal. After award, further revisions may be made using the OWG as the preferred vehicle for recommending these changes. Once the DMSMS BOM is established, the contractor shall monitor each item on the DMSMS BOM for DMSMS issues IAW the frequency defined in the DMP.

In the special case of items which meet the FAR definition of a commercial or COTS item, the Contractor shall monitor these items as a single line BOM entry working with the design owner to forecast when the item will no longer be available. In the case of items developed exclusively at private expense which do not meet the FAR definition of a commercial or COTS item, the Contractor shall include all EEE components; all commercial SW and all commercial or COTS assemblies in the DMSMS BOM baseline as stated above.

Commercial SW shall also be represented on the BOM as a single line entry at the indenture level where it exists, identified by a definitive part/version number.

Firmware shall be represented on the BOM with NVM component or COTS assembly on which the firmware resides.

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

3.8.8 DMSMS BOM Delivery

The Contractor shall deliver and update semiannually the current DMSMS BOM. The

DMSMS BOM shall be submitted IAW the CDRL for DI-MGMT-82274; DMSMS Life Cycle Management Data, BOM (CDRL A004) and this SOW. The BOM shall be a complete indentured design breakdown from the top assembly drawing to the individual EEE component level, but may include single line entries for commercial or COTS items (as defined in the FAR) and commercial SW.

3.8.9 DMSMS Alerts

For the weapon system under DMSMS management, the Contractor will monitor the parts and software identified on the BOM for DMSMS Issues. Should a documented or predicted DMSMS Issue be identified, the Contractor will submit an Obsolescence Alert Notice IAW the CDRL for DI-MGMT-82274, DMSMS Life Cycle Management Data; Alerts (CDRL A005) and this SOW.

3.8.10 Case Management

Concurrent with the delivery of the Alert the contractor shall establish a case to investigate and resolve it. Case management efforts shall commence when case is established and shall include contractor efforts to analyze the issue and its impact, develop candidate solutions and recommend to the government a solution for approval. The recommended solution shall be accompanied with supporting rationale for its selection, its estimated cost and a timeline for implementation upon approval by the government. All open cases shall be discussed at the

OWG.

3.8.10.1 DMSMS Case Management Reports

Once a DMSMS Case is established, the Contractor will report the status of each case to the government IAW the CDRL for DI-MGMT-82274, DMSMS Life Cycle Management Data;

Case Mgmt Reports (CDRL A006) and this SOW with the initial report due 45 days after submitting the DMSMS Alert. The initial Case Management Report will be largely administrative and should include a summary of the issue, an initial assessment of its impact, potential solutions to be considered and a proposed timeline for completion of the case efforts.

Subsequent Case Management Report updates are only required when there is a significant matter or change on the case to report (e.g., issues impacting contractual deliveries, satisfactory resolution, a change in status, a revised solution or schedule, etc.).

3.8.11 DMSMS Roadmap

For the weapon system selected for DMSMS management, the Contractor shall semiannually submit a DMSMS Roadmap at the LRU/SRU/SW level to summarize to the Government all current and forecasted DMSMS Issues projected to occur over the next five years on those items (i.e., LRU/SRU/SW). The DMSMS Roadmap shall be prepared IAW the CDRL for DI-MISC-80508B, Technical Report, Study-Services: DMSMS Roadmap (CDRL A007) and this SOW. The DMSMS Roadmap will include roll-ups of DMSMS Issues at each succeeding hierarchical assembly level up to the weapon system top assembly. The Roadmap shall also include any recommended or planned Technology Refreshment or Technology Insertion events. This planning should also seek to leverage any planned technology insertion capability upgrades or opportunities to include mitigating DMSMS issues. Key details of the DMSMS Roadmap will be an agenda item for the OWG.

3.8.12 Metrics Report

For the weapon system selected for or DMSMS management, the Contractor shall develop a set of DMSMS metrics. These metrics will be collected by the Contractor to document the effectiveness of the Contractors DMSMS management program. Included in these metrics will be the estimated Cost Avoidance of Case resolutions approved by the government during the reporting period and cumulatively for the length of the contract DMSMS Management Program. The Metrics shall also include an assessment of the overall health of the product design achieved via analysis of the current BOM via the following metrics:

a) Number of items on the DMSMS BOM.

b) Number of items on the DMSMS BOM which are considered standard or commonly used parts (e.g., on a Preferred Parts List (PPL) or equivalent).

c) Number of items on the DMSMS BOM with only one source of supply.

d) Number of items on the DMSMS BOM which are no longer available.

e) Number of items on the DMSMS BOM which are available, but have less than two years to the end of life (YTEOL) date.

f) Number of items on the DMSMS BOM with more than two but less than 5 YTEOL.

These metrics will be submitted to the government IAW the CDRL for DI-MISC- 80508B, Technical Report, Study–Services: DMSMS Metrics Report (CDRL A008) and this SOW. The review of these metrics will be an agenda item for the OWG.

3.8.13 Obsolescence Working Group (OWG)

For the weapon system selected for DMSMS management, the Contractor shall attend and participate in government OWG meetings. The purpose of the OWG is to review proposed revisions to the DMSMS BOM, open DMSMS cases, the Contractor’s most recent DMSMS Roadmap and Metrics Report, and any other DMSMS Issues suggested by either the Contractor or the government. The OWG will meet quarterly alternating between a contractor facility and

Aberdeen Proving Ground with the first meeting occurring no later than 60 days after award.

The government will establish the dates for each meeting in coordination with the contractor and will be responsible for publishing the meeting agenda and minutes.

3.9 Security

The contractor will be required to have a Secret facility clearance to perform Acceptance Testing, storage of material and software. The contractor also will be required to have a Secret safeguarding capability for classified documentations that is limited 2 cu. Ft of space. The contractor will require access to FOUO information. The contract will also require access to Security/Program Classification Guide (SCG). To perform this contract, the contractor will receive and generate classified material and fabricate/modify/store the classified software.

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

All classified material will be forwarded as request and clearance is approved.

Information Security (INFOSEC)

a. For Contracts That Require Handling or Access to Classified Information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with—

(1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

OPSEC program:

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award in accordance with DI-MGMT-80934C, 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.

OPSEC Training:

For contracts that require a formal OPSEC program (Required if non administration work is performed, e.g.,time sheets, and HR functions at contractor facilities):

"The contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan within 90calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer and COR. 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. Details on obtaining Level II certification can be furnished by the Government OPSEC Officer.(Duration: 2 Hours).

3.9.1 Threat Awareness Reporting Program

Per AR 530-1 Operations Security, the CECOM OPSEC Plan, and AR 350-1 Army Training and Leader Development contractor employees must complete Level I OPSEC Awareness training within 30 calendar days of reporting for duty and annually thereafter. Level I OPSEC training is available via the Army Learning Management System (ALMS) application at the following link:

https://www.lms.army.mil/ and by searching "Army OPSEC Level I (Duration:2 hours). An Enterprise Access Management Service Army(EAMS) account is required to access the ALMS application. Contractors shall also participate in any command directed OPSEC standowns, e.g., ad-hoc refresher trainings. If Computer Based Training (CBT) via ALMS cannot be completed, the organization's OPSEC Officer can provide the training to meet the Initial and Refresher training requirements."

3.10 Technical Data

NGC will provide updates to the Technical Data Package (TDP) upon the Government’s request (e.g. resulted from Obsolescence)

The Contractor shall be willing and able to produce a complete set of Technical Data upon a triggering event as mutually agreed upon with the USG. This Technical Data Package (TDP) will include all associated technical documentation for the CIPN. The Technical Data Package CLIN XXX is to be delivered upon one or more of the triggering events described in this section.

Changes approved under the Contractor’s configuration management, Obsolescence Management or other issues and DMSMS program shall be concurrently applied to the TDP.

The TDP produced by the Contractor shall include the following data:

a. Product Drawings and Associated Lists IAW CDRL A009 for DI-SESS-81000E & MIL- STD-31000 Para. 5.3.3.3

b. Software Product Specification IAW CDRL A0010 for DI-IPSC-81441A

Flow Down Requirement

The Contractor shall flow down the technical data requirement to Subcontractors, as required, to ensure that in the event a Subcontractor refuses to continue support of Program AN/APR 39C(V) spare or repair parts, ceases to provide sustainment support, or goes bankrupt, the Government is not left without sustainment support of the Program AN/APR 39C(V) product.

3.11 TAV- C

Army Materiel Command (AMC) and its units use Total Asset Visibility – Contractor (TAV-C) capability in its Logistics Management Program (LMP) to account for Government Furnished Equipment, Materiel, or Property (GFE/M/P) placed in the possession of contractors to support contracts for: 1) repair, modification, or upgrade work; 2) materials held for Stock, Store and Issue (SSI), or 3) New Production. Accounting records within LMP for this inventory are subject to verifying physical inventories and audits by the Army to ensure accuracy. This section addresses contractor requirements for repair, modification and/or upgrade contracts.

3.11.1 System Overview and Portal Access Requirements

3.11.1.1 To use TAV-C, Contractors shall request one of two TAV-C access methods below to exchange required inventory data with LMP: 1) Defense Logistics Management Standards (DLMS) interface or 2) the Army TAV-C Portal. Approval of the contractor’s access method will be based first on the type of work being performed, second, the sufficiency of the contractor’s existing property accountability and connectivity to LMP, and third, request by the to use the portal based on economic factors.

3.11.1.2 Contractors can choose between the two methods for accounting for government property as further described below:

3.11.1.2.1 Defense Logistics Management Standards (DLMS) Interfaces Contractors that have accounting systems capable of using a DLMS interface (see: DLM 4000.25, Defense Logistics Management Standards (DLMS) on the Defense Logistics Agency (DLA) website) shall request to use their accounting system and interface to account for Government Furnished Equipment/Materiel/Property (GFE/M/P) using DLMS transactions.

NOTE: If a contractor does not currently have an established DLMS interchange with Defense

Logistics Agency (DLA) Defense Automated Addressing System (DAAS), it will be the contractor’s responsibility to contact DAAS to establish access to DAAS messaging system to support the exchange of DLMS transactions with the Army. DAAS provides a value added service for standard Military Standards (MILS) transactions providing the ability to receive, edit and route logistics transactions for the Military Services and Federal Agencies.

Information on DAAS can be found at https://www.dla.mil/HQ/InformationOperations/DAAS/

3.11.1.2.2 Army TAV-C Portal

Contractors who, during negotiation with the government, are determined to be allowed to use the TAV-C Portal, will comply with prescribed processes to provide qualified workers to access the system to exchange data with LMP.

3.11.2 Portal Access Requirements

Contractor personnel who input data into the TAV-C Portal, must meet qualification requirements specified in the TAV-C Portal Guide Detailed Procedures and requirements are detailed in the TAV-C Portal Guide (Attachment X). These requirements include:

3.11.2.1 Contractor provided computer system

The contractor shall provide a computer system and internet connectivity that meets acceptable standards as identified in the TAV-C Portal Guide.

3.11.2.2 Security Requirements.

a) The government requires contractor personnel accessing the LMP system to possess either a United States Government Common Access Card (CAC) or a Department of the Defense approved External Certification Authority (EAC). To apply for these credentials, contractor personnel must possess a soft certification from a security credentialing firm.

NOTE: At the time of this writing, the government has successfully used IdenTrust and WidePoint (formerly ORC) for satisfactory credentials. It is the contractors’ responsibility ensure operators accessing the portal have and maintain current credential and to comply https://www.dla.mil/HQ/InformationOperations/DAAS/ with the selected vendors’ service contract requirements. These firms are provided as a courtesy and are not an endorsement for any firm by the U.S. Government.

b) Contractors will coordinate with the Contracting Officer’s Representative or designated government representative to complete required forms to obtain the CAC/EAC. This will require the above certification, forms of identification, etc.

3.11.2.3 User Training Requirements

TAV-C Portal user training is government provided and varies by the function performed. The training is online and completion of the training by each operator is required before accessing and using TAV-C.

3.11.2.4 The on-line training site will be provided by the government after award and access to the system has been granted. Functional training required to begin work should take no more than 15 hours to complete.

3.11.3 Problem Resolution

LMP is a government owned and maintained system. The contractor shall notify the COR or designated government point of contact for system related issues and government resolution.

3.11.4 DLMS Transactions / Portal Data Requirements

3.11.4.1 For DLMS Transactions for repair, modification and/or upgrade contracts, the inventory management transactions to be provided to the government by DLMS interface are:

1. DLMS 527R Materiel Receipt Acknowledgement (MRA) Transactions (for GFM expected to be consumed).

3.11.4.2 For DLMS Transactions for repair, modification, and/or upgrade contracts, the material receipt transactions to be provided to the contractor by the government via the DLMS interface are:

1. DLMS 527D Pre-positioned Material Receipt Document for stock in-transit to vendor.

3.11.4.3 Army TAV-C Portal

Contractors who, during negotiation with the government, are allowed to use the TAV-C Portal to exchange required data directly with LMP, will provide the following information via data inputs to LMP.

1. TAV-C Portal Requirements: Details on entry of the input into the LMP Portal will be provided as part of the government provided training.

2. The required data will be based upon the business process being performed. Inputs and input formats will be driven by the role performed for this work as directed in the contract.

3. The LMP Portal will provide to the contractor reports which will serve to inform the contractor and aid in work performance. Details on the various reports and how they can be used will be covered as part of the government provided LMP Portal training.

3.11.4.4 Consumption Reporting

Quarterly reports on the consumption of repair parts, disposition of equipment, and adjustments to inventories will be provided to the government as specified.

3.11.5 TAV-C Entries

A. Following an inventory effecting event, the Contractor shall accurately report transactions by the end of the next regular business day. The contractor shall report, on a quarterly basis, inventory activity and balances in accordance with the CDRL A011.

B. The Contractor shall physically confirm material received for actual National Item Identification Number (NIIN) and Quantity prior to recording receipt into LMP.

C. The Contractor shall notify the Contracting Officer (KO) or the Property Administrator prior to contract end to ensure inventory is properly dispositioned and all transactions have been entered.

D. The Contractor shall maintain 100% accuracy in its…