W56JSR-21-R-0002 Guardrail DRAFT PWS 22 October 2020.pdf

1 | P a g e

PERFORMANCE WORK STATEMENT

CONTRACTOR SERVICES

FOR

GUARDRAIL COMMON SENSORS PAYLOAD SUPPORT

22 October 2020

1.0 Scope.

This Performance Work Statement (PWS) establishes depot-level maintenance requirements in support of the specific parts of the Guardrail Common Sensors (GRCS) program, Receiving Set, Radio AN/ARW-88(V), that are listed in Appendix A of this PWS. Appendix A of this PWS illustrates the applicability of items that are unique to or common between specific variants of the AN/ARW-88(V), including items in the Enhanced Situational Awareness (ESA) P subsystem, ESA-R subsystem, High Band Communications Intelligence (COMINT) (HBC) subsystem, and Guardrail’s Legacy Guardian Eagle, RC-12K and RC-12X aircraft primary mission equipment payload. This PWS also provides the requisite performance standards for these services and the methodology for Government personnel to evaluate and assess Contractor performance of these services. This services contract covers repair, Reset/Overhaul, technical support, obsolescence, and changes/departures from the configuration baseline of repaired items for GRCS equipment.

Additionally, there may be future requirements for software sustainment Post Production

Software Support (PPSS) and acquisition support for the Guardrail Common Sensors Family of Systems (GFoS) and subsystems to Program Executive Office for Intelligence, Electronic Warfare & Sensors (PEO IEW&S) / Product Director Sensors Aerial Intelligence (PD SAI). PPSS support requirements for the Enhanced Situational Awareness (ESA) and Electronics Intelligence (ELINT) sensors within the GFoS includes:

• ESA and ELINT software maintenance on aerial platforms;

• Software maintenance of ESA and ELINT Virtual Machines (VMs) within the Tactical

SIGINT Baseline (TSB) in all Garrisons and Operational Intelligence Ground System (OGS) Shelters;

• Verification and Validation of all IAVA patches against ESA and ELINT software and VMs;

• Guardrail Test Bed Support for ESA and ELINT;

• Configuration management of all software and documentation for ESA and ELIN software and VMs to include support for all Configuration Control Board (CCB) meetings;

• Quarterly Technical Exchange Meetings (TEMs) between the Government and the

Contractor to review technical program status; The TEMs shave be either at the Government or Contractor facility or virtual

• Support troubleshooting and resolution of issues with ESA or ELINT that arise in the field

2 | P a g e

1.1 Period of Performance. The period of performance for this Indefinite Delivery/Indefinite Quantity (IDIQ) requirements contract is five years, with task orders awarded on a Firm Fixed Price (FFP) and Cost plus Fixed Fee (CPFF) basis.

2.0 Applicable Documents, Reference Designations, and Acronyms.

2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the latest issue of the Department of Defense Index of Specifications and Standards (DoDISS) and supplement thereto.

Document Number Document Title

STANDARDS

Department of Defense MIL-STD-129P w/Change 4 Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property

Army Communications- Electronics Command

SPI #AG00000573E CECOM Special Packaging Instruction for Major Components, Spare/Repair Parts

SPI #AG00000601B CECOM Special Packaging Instruction for Circuit Card and Printed Circuit Board Assemblies

Industry

American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations

ISPM No. 15, 01 April 2009 Regulation of Wood Packaging Material in International Trade

2.2 Other Government Documents, Drawings and Publications. The following Government documents, drawings, and publications form a part of this document to the extent specified herein:

REGULATIONS

Federal Acquisition Regulation FAR 52.204-2 Security Requirements FAR 52.246-3 Inspection of Supplies – Cost Reimbursement FAR 52.246-4 Inspection of Services – Fixed Price FAR 52.246-5 Inspection of Services – Cost Reimbursement FAR 52.248-1 Value Engineering

Defense Federal Acquisition Regulation Supplement

3 | P a g e

DFARS 252.246-7007 Contractor Counterfeit Electronic Part Detection and

Avoidance System DFARS 252.211-7003 Item Identification and Valuation DFARS 252.211-7006 Passive Radio Frequency Identification DFARS 252.225-7040, Feb

Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States

DFARS 252.225-7043, Mar

Antiterrorism/Force Protection Policy for Defense Contractors Outside the United States

DFARS 252.239-7001, Jan

Information Assurance Contractor Training and Certification

Army AR 25-2, 24 Oct 2007 Information Assurance AR 380-10, 22 June 2005 Technology Transfer, Disclosure of Information &

Contacts with Foreign Representatives AR 525-13, 11 Sep 2008 Antiterrorism AR 530-1, 19 April 2007 Operations Security (OPSEC)

Army Communications- Electronics Command

MANUALS

Department of Defense DoD 5220.22-M National Industrial Security Program (NISP)

Operating Manual DoD 8570.01-M, with Change 3, 24 Jan 2012

Information Assurance Workforce Improvement Program

DIRECTIVES

DoDD 8570.01, 23 Apr 2007 Information Assurance Training, Certification, and

Workforce Management

Other NDP-1 National Disclosure Policy Directive-Type Memorandum

(DTM) 09-019

Policy Guidance for Foreign Ownership, Control, or Influence (FOCI)

PM ACS SCG, 30 Jun 2010 Security Classification Guide (SCG) for the Project Manger Aerial Common Sensor (PM ACS)

FORMS

DD Form 250 Material Inspection and Receiving Report DD Form 441 Department of Defense Security Agreement

4 | P a g e

Note on Document Versions: The specific versions of the applicable documents cited above may not be specified throughout this PWS; only the basic document designations may be referenced (e.g., MIL-STD-130 vice MIL-STD-130N). The document versions cited above apply to the basic document designations referenced in this PWS.

2.3 Reference Designations for Points of Contact. Reference designations (e.g., PCO, CS, COR, ILSC ILS, ILSC IM, ILSC PROV, PRD ENG, GCS, etc.) are used throughout this PWS for specific points of contact in the Government.

2.4 Acronyms. A list of general and Contract Data Requirements List (CDRL) acronyms is contained in Appendix B of this PWS.

3.0 Requirements.

This performance based requirement is to provide Line replaceable unit (LRU) repair, reset/overhaul, and technical services for various GRCS, Receiving Set, Radio AN/ARW-88(V) items, as well as obsolescence management. Appendix A of this PWS contains a listing of the items that are applicable to this requirements contract. Services under this contract shall be procured via task order and performed on a Cost Plus Fixed Fee (CPFF) basis, with the exception of sections of the PWS that specify performance on a Firm Fixed Price (FFP) basis.

3.1 LRU Repairs. The Contractor shall provide LRU repair services as specified in this PWS, in support of the GRCS, Receiving Set, Radio AN/ARW-88(V). The repair process for an unserviceable item consists of troubleshooting, evaluating, repairing, and verifying its performance. The outcome of the repair will be identified as a (recertified) unit. LRU repair will be completed on a CPFF basis. A listing of LRU’s can be found on Appendix A within this PWS. LRU’s not on this list because of future upgrades to current NSN’s, or possible missing Guardrail repairable items from Appendix A shall need PCO approval before being repaired.

3.1.1 Notification of Receipt. Within one working day of receipt of an unserviceable item and the associated task order, the Contractor shall notify the COR, LRC IM, and GCS via email to facilitate tracking of repair. The Contractor shall also include a scanned copy of the DD Form 1348-1A with the email.

3.1.2 Initial Repair Test and Inspection (T&I). The Contractor shall perform an initial test and inspection of the item to verify identity, physical damage, mishandling, damage from irresponsible use, completeness (i.e., no missing parts), and functional faults, at a minimum, to determine the cause of failure.

3.1.3 Categorization. Following the initial inspection and test, the Contractor shall assign one of the categories below to the item and take the action specified in paragraph 3.1.4.

a Repairable. A repairable item is one that, in the course of operation and use, is found to be non-functional or inoperable, does not satisfy its intended function, or does not perform within its design specifications. The repair process for an unserviceable item typically consists of troubleshooting, evaluating, repairing, and verifying its performance (recertification).

5 | P a g e

b. Beyond Economical Repair (BER). A BER item is one whose damage is so extensive that repair of the item is impossible or economically impractical. Economically impractical means the cost of repair would exceed 65% of the acquisition price of a new item.

c. No Evidence of Failure (NEOF). An NEOF item is one that is inspected, tested, and deemed to not require any repairs. The item is found to be fully functional, operable, satisfies its intended function, and performs within its design specifications.

3.1.4 Initial Repair T&I Notification. Within thirty (30) working days after receipt of the item(s) and authorization for initial test and inspection, the Contractor shall provide notification to the COR as to the appropriate categorization; Repairable Item, BER Item or NEOF. The Contractor may request additional time from the PCO or COR if needed.

3.1.4.1 Repairable Item. The Contractor shall provide the PCO, COR, LRC IM, and PRD ENG via email with a report specifying the results of the initial test and inspection, categorization, and the repair actions to be taken (including acceptance testing), along with the labor hours required, materials, and associated costs to return the item to serviceability.

3.1.4.2 BER Item Once an item is determined to be BER, the Contractor shall provide a determination of findings to the PCO, COR, LRC IM, and GCS via email, to include an analysis showing that the repair price will exceed 65% of the current acquisition price of a new item.

After reviewing the determination of findings, the Government will either direct the Contractor to repair the item despite the cost exceeding the BER threshold, or will otherwise provide disposition instructions The Contractor may invoice the inspection and test to the Government.

3.1.4.3 NEOF Item Upon determining that an item is in this category, the Contractor may invoice the inspection and test to the Government. The Contractor shall notify the COR via email of the findings and request disposition instructions.

3.1.5 Repair Execution. The Contractor shall repair unserviceable items so that following the repair, the item’s form, fit, and function are compliant with its Configuration Baseline Drawing specified in Appendix A; and its interface performance enables the system/subsystem in which the item is a part to work to satisfy its specification requirements.

3.1.6 Acceptance. The Contractor shall comply with FAR 52.246-3, for which repair items are to be considered as supplies. The Contractor shall ensure the repaired item successfully passes its final ATP, as specified in Appendix A.

3.1.7 Finishes and Markings. The Contractor shall repair all damaged protective finishes to the extent necessary to provide adequate protection during usage. The Contractor shall replace damaged markings, identification, and decals, but shall not correct minor cosmetic finish defects, scratches, nicks, or dents, which will not affect the installation or operation of the repaired item.

6 | P a g e

3.1.8 Repair Turn-Around Time (RTAT).

3.1.8.1 Normal Repairs. The Contractor shall return unserviceable items provided by the Government to serviceability within an RTAT of 120 calendar days. RTAT is measured from date of receipt of both the task order and item(s) for repair to the date the repaired item(s) is shipped to the destination specified on the task order.

3.1.8.2 Expedited Repairs. The Government reserves the right to request the Contractor to expedite repairs, with the desired RTAT specified in the request. In the event the Contractor cannot comply with an expedited repair request, the Contractor shall notify the PCO and COR via email, and provide supporting rationale along with an alternative RTAT.

3.1.9 Notification of Completion. Within one working day of completion, the Contractor shall notify the PCO, LRC IM, and GCS via email that applicable actions, based on the categorization(s) of the item(s) provided to the Contractor for repair, have been completed.

The Contractor shall also attach to the email a scanned copy of the DD Form 1348-1A that accompanied the item(s) to be repaired.

3.2 Reset/Overhaul. This section of the PWS provides the tasks necessary for the Contractor to Reset/Overhaul the various GRCS subsystems, such that the subsystem is verified to be in full operational condition, with required maintenance performed, or if unserviceable, returned to full operational condition. Reset is divided into two parts, following Induction. Reset/overhaul test and inspect will be completed on a FFP basis and once complete the contractor will submit a proposal to the Government for evaluation. Negotiations will be completed and the reset will be awarded on a CPFF completion basis. The outcome of the reset will be a fully operational system meeting 10 (operator)/ 20 (field level maintenance) standards as cited in Appendix E of the PWS.

3.2.1 Duration. The Contractor shall successfully complete all Reset actions on the item within 60 calendar days after the Reset has been fully funded. If a Reset cannot be completed within the required duration, the Contractor shall submit to the PCO a request for an extension/variance to the required duration, with supporting rationale, for approval.

3.2.2 Standard Reset Actions.

3.2.2.1 Induction. Within one working day of receipt of both the task order directing Reset and the item(s) to be Reset, the Contractor shall induct the item(s) into the Reset program by email notification to the COR, IM, and GCS that the item(s) has arrived and Reset actions will commence per the task order. The Contractor shall also attach to the email a scanned copy of the DD Form 1348-1A that accompanied the item(s) to be Reset.

3.2.2.2 Initial Reset T&I. The Contractor shall perform an initial inspection and test on a FFP basis to determine if the item is fully operational or if not, to confirm that it is in need of repairs.

In cases where visual damage is noted during the inspection, the Contractor shall take digital pictures of the item before repair actions are taken. To determine if the item is fully operational, 7 | P a g e the Contractor shall utilize the ATP cited in Appendix A for the NSN specified, and retain the test results for review by the Government upon request.

3.2.2.3 Reset Repair Notification. When a Reset item(s) is determined to either be unserviceable (i.e., did not pass inspection and testing) or have unserviceable components, the Contractor shall notify the PCO, COR, LRC IM, and GCS via email that a Reset item(s) is in need of repair. In the notification, the Contractor shall include the contract number, applicable Reset task order number, identifying information for the unserviceable item(s) (e.g., NSN, part number, CAGE code, item name, and serial number). The Contractor shall perform needed repairs according to the Reset Repairs section of this PWS on a CPFF “Completion” basis once a proposal is received, evaluated, negotiated and funded. Upon receiving authorization from the PCO, the Contractor shall commence Reset repairs by following the Repairs section of this PWS. The Contractor shall ensure that Reset items, and associated repairs and costs are tracked separately from items being repaired outside of Reset.

3.2.2.4 Cleaning and Maintenance. The Contractor shall clean the Reset item and perform required maintenance actions, in compliance with the operations and maintenance standards (the -10 [operator] and -20 [field level maintenance]) in the technical manuals cited in Appendix E.

3.2.2.5 Reset Acceptance Testing. Following the above actions in this section of the PWS, and subject to any necessary Reset Repairs, the Contractor shall perform acceptance testing on the Reset item(s) to verify that the item(s) is fully operational, by utilizing the ATP cited in Appendix A for the applicable NSN(s).

3.2.2.6 Closeout. Following successful completion of testing of the Reset item, and subject to any necessary Reset Repairs, the Contractor shall perform the following:

a. Package and ship the serviceable item as specified in the Packaging and Shipping section 3.5 of this PWS.

b. Prepare and submit Reset Report for the Reset action, as specified Reporting section

3.13 of this PWS.

c. Within one business day of completing Reset on the item, notify the COR, LRC IM, and GCS via email that Reset has concluded. The Contractor shall also attach to the email a scanned copy of the DD Form 1348-1A that accompanied the item(s) to be Reset.

3.3 Item Unique Identification (IUID).

8 | P a g e

3.3.1 IUID Marking. The Contractor shall mark items delivered IAW the following subparagraphs and DFARS clause 252.211-7003 in Section F of the contract. Items requiring IUID markings are identified in Appendix A.

3.3.1.1 Reset and Repair Items. The Contractor shall inspect items received for Reset and repair, for which IUID markings are required (see the IUID column in Appendix A of this PWS), to determine if IUID markings are present. In cases where the IUID marking is damaged or missing, the Contractor shall apply IUID markings on the item, as specified in this section of the PWS. The Contractor shall request clarification from the PCO when IUID marking requirements for a given item are not clear.

3.3.1.2 IUID Features. The application and features of the IUID markings shall comply with the following requirements specified in MIL-STD-130:

a. 4.1 Methods of Applying.

b. 4.2 Location, Size, and Content.

c. 4.3 Permanency and Legibility.

d. 4.5 Deleterious Effect.

3.3.2 IUID Marking Symbology and Priority. IUID markings shall comply with the minimum machine-readable information marking symbology specified in Figure 10 of MIL-STD-130. The order of priority for information shall be as follows, based on space availability (limited space to sufficiently available space):

a. First priority is the 2D data matrix symbol (machine readable) IUID is the minimum requirement when there are severe space limitations.

b. Second priority is the human readable characters.

c. Third priority is the Linear Bar Code.

3.3.3 IUID Listing. The Contractor shall maintain an accurate, current list of IUIDs applied to items requiring IUID markings on this contract. Dates of manufacture/repair, substitutions, and shop changes, as a minimum, shall be included on this list. The list shall be available for inspection by the Government at any time during this contract, upon request of the PCO or COR. The Contractor shall provide this list to the Government at the end of the contract.

3.3.4 IUID Registry. For items that require IUID markings, the Contractor shall comply with DFARS clause 252.211-7003 and enter data into the IUID Registry (note: specify USARMY as the SERVICE/AGENCY/ COMMAND data element in the information reported to the IUID Registry).

3.3.5 Wide Area Workflow (WAWF) Users and the IUID Registry. WAWF users shall report 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

9 | P a g e

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.3.6 Commercial Markings. The Contractor shall ensure that items not requiring IUID markings 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 Quality.

3.4.1 Quality Assurance Surveillance Plan (QASP). The QASP outlines the Government’s methods for measuring performance of the Contractor against the requirements in this PWS.

The Government relies on the Contractor to monitor daily performance using internal quality procedures and practices (e.g., a Quality Control Plan that describes the internal staffing and procedures that the Contractor uses to meet the quality, quantity, timeliness, and responsiveness requirements/goals to achieve customer satisfaction).

3.4.2 Contractor’s Quality Management System and Government Inspection. The Contractor shall comply with FAR 52.246-5 for CPFF and FAR 52.246-4 for FFP requirements under this contract. The Contractor shall make available to the Government, upon request, quality management system documentation, including documented statements of a quality policy; documented quality objectives; quality manual; documented procedures; and records required by quality management system standard documents, including records determined by the Contractor to be necessary to ensure the effective planning, operation and control of its processes. The Government may limit its inspection to the Contractor’s facility and facilities of subcontractors/suppliers that provide products and/or services valued over 20% of the contract total cost.

3.4.3 Counterfeit Parts Detection and Avoidance. The Contractor shall comply with DFARS 252.246-7007 to detect and avoid the use of counterfeit parts in items delivered to the Government under this contract. The Government reserves the right to review and evaluate the Contractor’s counterfeit electronic part detection and avoidance policies and procedures at any time during the execution of this contract.

3.5 Packaging and Shipping

3.5.1 Packaging, Preservation, Packing and Marking for Shipment. Preservation, packing and marking for shipment shall be in accordance with Section ‘D’ of the requirements contract.

3.5.2 Wood Packaging Material (WPM). 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.

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

10 | P a g e

3.5.2.1 International Standards for Phytosanitary Measures (ISPM) Number 15 Applicability. The Contractor shall ensure that all WPM used meet the requirements of the 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.5.2.2 Heat Treatment Quality Control. The Contractor shall ensure that all WPM used comply with the official quality control program for heat treatment (HT) or kiln dried heat treatment (KDHT) in accordance with American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations (see http://www.alsc.org/).

3.5.2.3 Certification/Quality Markings. The Contractor shall ensure that all WPM used include certification/quality markings per the ALSC standard. The Contractor shall apply markings in an unobstructed area that is readily visible to inspectors. The Contractor shall apply pallet markings 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.

3.5.2.4 Noncompliance Ramifications. Failure of the Contractor to comply with the requirements in the Wood Packaging Material section of this PWS 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.5.3 Passive Radio Frequency Identification (RFID). The Contractor shall comply with RFID requirements in DFARS 252.211-7006, of the contract. The Contractor shall also comply with the Passive Radio Frequency Identification (RFID) section of MIL-STD-129.

3.5.4 Shipping.

3.5.4.1 Instructions. The Contractor shall ensure LRU repaired, Reset/Overhaul, and other items returned to the Government are accompanied by a DD Form 1149 (may be obtained at http://www.dtic.mil/whs/directives/forms/eforms/dd1149.pdf). In order to perpetuate asset visibility, the Contractor shall ensure that the DD Form 1149, block 6 (titled “Requisition Number”), contains the ORIGINAL DOCUMENT NUMBER as provided on the DD Form 1348- 1A, block 24 (card column numbers 30-43). The DD Form 1348-1A is the official shipping document from a Government depot or other Government designated location to the Contractor’s repair facility. Each document number contains 14 digits and starts with W15GK8.

When DD Form 250 submission applies, the Contractor shall include the document number and National Stock Number (NSN) of the returned item(s) in block 16 of the DD 250.

http://www.dtic.mil/whs/directives/forms/eforms/dd1149.pdf

11 | P a g e

3.5.4.2 Destination. The Contractor shall ship repaired, Reset, and other items specified by the Government to the destination(s) cited in the task order or as directed by the PCO.

3.5.4.3 Notification of Shipment. Within one working day of shipment of an item, the Contractor shall notify the COR, LRC IM, and GCS via email to facilitate tracking. The Contractor shall also include a copy of the DD Form 1149 with the email.

3.6 Technical Support.

3.6.1 Internal Support. The Contractor shall provide technical support/engineering services on an as-needed basis, at and from the Contractor’s facility(ies), in response to requests from the Government related to the various GRCS subsystems identified in paragraph 1.0, regardless of the method used for the request (i.e., conversation, telephone, emails, written documents, fax, text message, or otherwise). The Contractor’s response shall be of like kind, unless the person requesting support requests the response via a different method. Verbal communication shall be confirmed in writing at the earliest opportunity. Examples of the types of technical support required include: providing an understanding of, providing assistance with the resolution of, and resolving maintenance, operational, performance, interface, technical, and parts issues; providing inputs to product deficiency investigations and product improvement efforts; clarifying technical documentation, including providing copies of specific technical data; and resolving equipment related problems.

3.6.2 Single Point of Contact. The Contractor shall provide and maintain a single point of contact for technical support with the contact’s telephone number, email address, mailing address, and fax number provided to the Government.

3.6.3 Internal Technical Support Report. The Contractor shall summarize the technical support/engineering services provided and submit as specified in the Contractor Technical Support/Engineering Services Report section 3.13.4 of this PWS.

3.6.4 Meeting Support: The Contractor shall support meetings with the Government at the Contractor’s and Government’s facilities as requested by the COR.

3.7 Obsolescence and Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.7.1 DMSMS Source Data.

The Contractor shall develop source data that will enable the identification, forecasting, and management of piece part obsolescence impacts and mitigations. This data will be used in the

12 | P a g e

Government’s DMSMS forecasting tool. The Contractor may develop the source data from sources such as the preferred parts list, bill of materials, vendor surveys, inspections, etc.

3.7.2 DMSMS Source Data Report. The Contractor shall prepare and submit the DMSMS Source Data Report according to the CDRL DI-SESS-81656 (Data Item A011).

3.7.3 Parts Tracking. The Contractor shall monitor the availability of parts required for the items listed in Appendix A on a quarterly basis, as a minimum. Upon determining that the lack or impending lack of availability of a part(s) will adversely affect the Contractor’s ability to provide an item(s) listed in Appendix A, the Contractor shall immediately notify the Government of the situation and parts involved via email to LRC ILS, LRC SCM, and PRD ENG. All Point of Contact information will be provided at the time of contract award. The Government will then determine an appropriate follow-on action (e.g., procure sufficient parts/spares prior to end of life, fund a study, fund a redesign effort, etc.). If the Contractor is not already a member in the Government-Industry Data Exchange Program (GIDEP) (see http://www.gidep.org/), the Contractor is encouraged to participate, as part of this contract, by contributing the Contractor’s existing, internal efforts related to monitoring vendor/supplier parts availability.

3.7.4 Contractor Recommendations. The Contractor may also provide recommendations to resolve problems of diminishing availability of components. The recommendations may include form, fit, and functional replacement components/items or other alternative actions.

The Contractor is encouraged to use the Value Engineering Change Proposal (VECP) process, in cases where savings can be realized. When the Contractor is no longer able to support the repair of an item listed in Appendix A, the Government may request the Contractor to provide the associated technical data (drawings, specifications, test procedures, etc.), for the purpose of obtaining a possible alternative source of repair (SOR).

3.7.5 End of Life/Obsolete Parts. When the Contractor becomes aware that an Appendix A part or its component(s) is becoming end of life/obsolete, the Contractor shall notify the PCO.

The Contractor shall recommend solutions, including identifying direct replacement parts/components (i.e., form, fit, and functionally equivalent). The end of life status parts and any replacement part recommendations shall be included in the Contractor Technical Support/Engineering Services Report, as specified in the Contractor Technical Support/Engineering Services Report section of this PWS.

3.7.6 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 minimum 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 http://www.gidep.org/

13 | P a g e 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 an Obsolescence Working Group (OWG).

3.7.7 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 A014), ANSI/TA-STD-0016 and this PWS. 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.7.8 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.

14 | P a g e

3.7.9 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 A011) and this PWS. 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.7.10 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 A012) and this PWS.

3.7.11 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.7.12 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 A013) and this PWS 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.7.13 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 A015) and this PWS. 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.7.14 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

15 | P a g e 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:

- Number of items on the DMSMS BOM.

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

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

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

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

- 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 A016) and this PWS. The review of these metrics will be an agenda item for the OWG.

3.7.15 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.8 Calibration and IST Flight Testing.

3.8.1. ESA & HBC Calibration: As directed by the USG and typically a result of SLEP or other airframe or cable changes that affect DF performance, all Guardrail systems shall be calibrated prior to flight testing and fielding using a contractor developed, Government approved, calibration and verification procedure. Calibration of the Direction Finding subsystem shall ensure the Line of Position, is in compliance with specifications: D0002323, GRM-2007-001 and I2WD-GT4-00 for HBC. Verification of ESA calibration is by Matlab playback analysis of separately collected verification data against calibration tables, and demonstration of LOP production against known locations during IST flights. Verification of HBC calibration is by containment analysis of target geolocation collections during IST/performance flights. Pre calibration/verification tasks may include, but are not limited to validation of aircraft antennas and cables, installation and troubleshooting of payload as needed, preflight BIT for ESA and HBC, and aircraft maintenance support and hangar and ramp space lease provisions.

3.8.2. Aircraft IST. Aircraft IST is not a verification of individual requirements, but a confirmation that the hardware is FOC. Additionally, DF Performance (single ship) may also be demonstrated in parallel. IST shall occur through contractor demonstrated, optionally Government witnessed, functional capability demonstration/validation procedures. Pre IST tasks may include, but are not limited to installation and troubleshooting of payload as needed, preflight BIT for all subsystems and repair of non-conformities, applying latest deployed

16 | P a g e patches as required by intended theatre of operation, and aircraft maintenance support and hangar and ramp space lease provisions.

3.9 Technical Manual (TM) Support.

3.9.1 Requirements for Technical Manual Changes. Following Government approval of changes to, or departures from, the configuration baselines related to the various GRCS materiel identified in paragraph 1.0, or as a result of changes in Army Tactics, Techniques, and Procedures (TTPs) that affect the operation and use of such materiel, the Contractor shall make changes to applicable TMs upon authorization by the PCO via individual task order.

Each delivery order that requires a change to a tech manual shall identify the TM and what is required for that task.

3.9.2 Changes. All changes shall be clearly identified in the delivered material, through "change bars" on the left margin of the page or as agreed between the Contractor and the Government. These Technical Manual changes shall be in accordance with this PWS and the following:

a. MIL-STD-40051–1B - Department of Defense Standard Practice, Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) (Exclusive of style and format requirements).

b. MIL-STD-40051–2B - Department of Defense Standard Practice, Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs) (Exclusive of style and format requirements).

c. MIL-DTL-87268D - Interactive Electronic Technical Manuals General Content, Style, Format, and User-Interaction Requirements.

3.9.3 Source Data. The Contractor shall develop the TM changes according to the following source data, which shall be furnished to the Contractor no later than the TM Change start-of-work meeting.

a. Applicable Engineering Change Orders (ECOs)/ECPs.

b. Existing manuals.

c. Existing digital files (if applicable).

d. Maintenance Allocation Chart (MAC).

e. Target audience descriptions.

f. Ozone Depletion Substance Prohibition Listing (with recommended alternatives) - if applicable.

3.9.4 Front Matter “Boilerplate” Source. The Contractor shall incorporate the following boilerplate material (TM paragraph numbers are shown below), to be supplied by the Government, in the front matter of each TM being changed. The Government shall provide this material no later than the TM start-of-work meeting, unless otherwise indicated.

a. 1-2. Consolidated Index of Army Publications and Blank Forms

b. 1-3. Maintenance Forms and Records

c. 1-4. Reporting Equipment Improvements and Recommendations

17 | P a g e

d. 1-5. Administrative Storage

e. 1-6. Destruction of Army Materiel to Prevent Enemy Use

3.9.5 in-Process Reviews (IPRs). IPRs shall take place when 30%, 70%, and 100% of the TM Change(s) has/have been developed. The Contractor shall provide digital Microsoft Word files of the material to be reviewed.

3.9.5.1 TM Change Validation. The Contractor shall validate changed material at the Contractor's facilities. Contractor personnel performing operating and maintenance procedures on the equipment during validation shall be independent of the Contractor's TM preparation activity. Contractor validation records shall be subject to Government inspection at any time during the contract without prior notice. The Contractor shall notify the Government in writing upon completion of the TM Change validation. The Government reserves the right to witness the Contractor validation.

3.9.5.2 TM Change Verification. The Government shall verify the TM Changes at as described by specific task order by performing 100 percent of the operating and maintenance procedures using target audience personnel. A 100 percent desk review of those portions of the publication not subject to hands-on performance, e.g., table of contents, theory, index, etc., shall be conducted. All functional features of the TM shall also be verified. The Contractor shall provide at verification 2 hard copies of each TM Change to be verified; appropriate office or work space; a fully operational configuration of the equipment covered by the TM, including hardware and software, on which Government personnel shall perform the verification;

personnel necessary to document changes to the publications and resolve hardware and software issues; and all tools and test equipment required, according to the maintenance concept/MAC, to perform all procedures in each TM.

3.9.6 Incorporation of Comments. AMSEL-LCW-I-GR is the Government TM Change acceptance authority for this contract. The Contractor shall incorporate all TM Change comments within scope of this contract provided to them by the Government TM Change acceptance activity. If Government activities other than the Government TM Change acceptance activity provide TM Change comments, the Contractor shall forward these comments to the Government TM Change activity for disposition.

3.9.7 TM Delivery. For all technical manuals prepared under this contract, the Contractor shall deliver Microsoft Word digital files per the following CDRL for DI-TMSS-81701C (Data Item A001).

3.9.7.1 Final Digital Delivery. The final digital delivery shall be a complete technical manual with all changes incorporated. The change bars shall be indicated in the margin so the changed data can be readily identified by the user.

3.9.8 Pack-up of Operator’s TMs with Equipment. If a TM containing operator's instructions is being changed or revised under this contract and the equipment is being delivered under this contract, the Contractor shall pack one copy of the changed or revised operator's TM with each equipment package.

18 | P a g e

3.9.9 Maintenance Allocation Chart (MAC). As supporting data for MAC updates, the Contractor shall submit Level of Repair Analysis (LORA) input data needed for the standard Army model in accordance with a specified format to be provided by the Government.

3.10 Provisioning Data.

3.10.1 Provisioning Parts List (PPL). Following Government approval of changes to, or departures from, the configuration baselines related to the various GRCS materiel identified in paragraph 1.0, or as a result of changes in Army Tactics, Techniques, and Procedures (TTPs) that affect the operation and use of such materiel, the Contractor shall provide PPL updates per the CDRL for DI-SESS-81759A (Data Item A002), upon authorization by the PCO via individual task order.

3.10.2 Engineering Data for Provisioning (EDFP). Following Government approval of changes to, or departures from, the configuration baselines related to the various GRCS materiel identified in paragraph 1.0, or as a result of changes in Army Tactics, Techniques, and Procedures (TTPs) that affect the operation and use of such materiel, the Contractor shall provide new EDFP and updated EDFP according to the CDRL for DI- SESS-81874 (Data Item A003), upon authorization by the PCO via individual task order. The EDFP shall consist of product drawings as defined under MIL-STD-31000, unless an alternative format of data is authorized by the PCO.

3.10.3 Repair Parts and Special Tools List (RPSTL). Following Government approval of changes to, or departures from, the configuration baselines related to the various GRCS materiel identified in paragraph 1.0, or as a result of changes in Army Tactics, Techniques, and Procedures (TTPs) that affect the operation and use of such materiel, the Contractor shall provide RPSTL updates per the requirements in Appendix E, upon authorization by the PCO via individual task order.

3.11 Configuration Management.

3.11.1 Configuration Baseline. The configuration baseline for each NSN is specified in the Configuration Baseline and Rev column in Appendix A.

3.11.2 Changes to/Departures from Configuration Baselines. The Contractor shall not change or depart from the Government-approved configuration baselines (i.e., Drawing and the form, fit, and function of the items specified in Appendix A, as previously delivered to the Government), unless such are first submitted to and approved by the Government.