Exhibit A - Technical Requirements Document.pdf

Exhibit A SPRBL1-22-R-0001 Page 1 of 26 Issue: 15 December 2021

TECHNICAL REQUIREMENTS DOCUMENT

FOR

SPRBL1-22-R-0001

REPARABLE SPARE PARTS CONTRACT

FOR THE ELECTRIC POWER PLANT III U/W PATRIOT

Exhibit A SPRBL1-22-R-0001 Page 2 of 26

TABLE OF CONTENTS

APPLICABLE DOCUMENTS

CONFIGURATION BASELINE

Part Revisions

SPECIAL INSTRUCTIONS

PACKAGING

Wood Packing Material

Military Packaging

CONTRACT SECURITY REQUIREMENTS

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

Exhibit A SPRBL1-22-R-0001 Page 3 of 26

APPLICABLE DOCUMENTS

Military and Federal Standards MIL-STD-130N w/Change 1 Identification Marking of U.S. Military Property MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-2073-1E w/ Change 4 Standard Practice for Military Packaging Military and Federal Specifications

N/A Other Documents SPI AG00000605 Special Packaging Instruction SPI AG00000662 Special Packaging Instruction Commercial Documents ISPM Number 15 Regulation of Wood Packaging Material in International Trade ANSI/TA-STD-0016 Standard for Preparing a Diminishing Manufacturing Sources and

Material Shortages (DMSMS) Management Plan ANSI/ISO/ASQ(E)Q 9001-2015 American National Standard, Quality Management Systems-

Requirements

Exhibit A SPRBL1-22-R-0001 Page 4 of 26

CONFIGURATION BASELINE

The applicable Configuration Baselines (CB), for the listed Configuration Item (CI) and/or Computer Software Configuration Item (CSCI), are as listed in the table below.

Configuration. Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). Configuration changes not directly effecting the configuration baseline do not require Government approval prior to incorporation, but must be documented by the contractor and shall be made available to the Government upon request.

NSN Nomenclature Part Numbers

6115-12-341-6789 GENERATOR, ALTERNATING CURRENT 130.03.0063

2920-12-345-5330 ROTOR, GENERATOR 360.08.0051

5840-12-341-7003 POWER DISTRIBUTION UNIT 420.02.0078

2815-12-341-6896 ENGINE, DIESEL 280.06.0071

Exhibit A SPRBL1-22-R-0001 Page 5 of 26

Diminishing Manufacturing Sources and Material Shortages (DMSMS)/Obsolescence Management - Spares Multi-item, Multi-year, IDIQ

Definitions. For the purpose of this part –

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

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

“Diminishing Manufacturing Sources and Material Shortages (DMSMS)” is the loss, or impending loss, of qualified source(s), manufacturers, or suppliers that may cause shortages in the design, manufacture, sustainment, and disposal of an item or system.

“DMSMS Issues” are problems related to shortages or potential shortages of items caused by obsolescence, loss of qualified manufacturers or suppliers of items, legal or policy changes, etc.

“Documented DMSMS Issues” are DMSMS Issues for which there is documentation advising that an item will be unavailable at a specific date in the future.

“Projected DMSMS Issues” are DMSMS Issues predicted to occur that have been identified by the DMSMS monitoring process.

“Unresolved DMSMS Issues” are DMSMS Issues that have been determined to have an impact on production and/or sustainment, but for which no solution has been approved.

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

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

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

“Obsolescence” is the condition when an item needed to produce or support the system is out of production.

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

Exhibit A SPRBL1-22-R-0001 Page 6 of 26

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

“Standard Parts” or “Commonly Used Parts” are those parts identified in the contractor’s Parts Management or Parts Selection processes as preferred for use by their design engineers.

“Subcontractor” is a person or entity to which the prime Contractor has delegated part or all of its obligations to furnish supplies, materials, equipment, or services of any kind under a prime contract or a subcontract entered into in connection with such prime Contractor. Note that by this definition, some suppliers will not be considered “Subcontractors”, and as such, would not be subject to DMSMS program requirements.

“Technology Refreshment” is a defined programmatic system management strategy to replace the electronics (including software/firmware) in a system over a specific period of time, usually with the goal of improved performance, reliability, and supportability. Technology refreshes can be strategically-applied to prevent the occurrence of DMSMS Issues preemptively or to minimize them significantly.

Additional terms and definitions are provided in the definition paragraph of ANSI/TA-STD-0016 and Table 9 of the DMSMS Guidebook, SD-22.

DMSMS Management Program and Plan.

The Contractor shall execute a proactive DMSMS management program in accordance with (IAW) this SOW and ANSI/TA-STD-0016 for the period of performance of this contract. The government’s objective in this program is to cost-effectively identify and resolve DMSMS issues and maintain—to the maximum practical extent—a minimum five-year interval before any DMSMS issue is forecasted to occur on any LRU in the system.

The program shall address how the Contractor will identify part DMSMS Issues, assess potential risk, develop an obsolescence strategy and determine the most cost effective solution to part DMSMS Issues.The program shall also address plans for the transition of DMSMS/Obsolescence activities from the Contractor to the government or another Contractor at the conclusion of this contract. The Contractor’s plan to conduct the DMSMS/Obsolescence program shall be documented in a DMSMS Management Plan prepared and delivered IAW DI-MGMT-81948, ANSI/TA-STD-0016, and this SOW.

The Contractor’s DMSMS Management Plan shall include a description of their process and procedures for selecting parts which meet the government’s objective of utilizing Standard or Commonly Available Parts with at least five (5) years to the end of life (YTEOL). Note that the Contractor may satisfy this requirement by including a corporate Parts Management Plan (or equivalent, if one exists) as an appendix to the DMSMS Management Plan at the Contractor’s discretion.

The Contractor’s DMSMS Management Plan shall also include procedures for both participation in the Government Industry Data Exchange Program (GIDEP) and participation in a semiannual government chaired Obsolescence Working Group (OWG). To the extent that these procedures may not currently exist in an existing corporate DMSMS Management Plan (or equivalent), then these procedures may documented in the existing plan as an appendix at the Contractors discretion.

Exhibit A SPRBL1-22-R-0001 Page 7 of 26

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

Contractor responsibility includes all costs associated with identifying and investigating DMSMS Issues, including the development of candidate mitigation strategies to propose to the government. For each candidate mitigation strategies developed, the Contractor shall estimate the cost to implement as well as any benefits, including cost benefits, which the government might accrue over a five year planning horizon commencing with the an estimated implementation date.

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

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

In the special case of items which meet the FAR definition of commercial or a COTS item, the Contractor shall work with the design owner to forecast when the item will no longer be available and provide a single line entry on the BOM for the item.

In the case of an item developed exclusively at private expense which does not meet the definition of a commercial item, the Contractor shall submit the BOM to the component-level.

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

DMSMS Alerts and Case Management. The Contractor will monitor the parts and software identified on the BOM for DMSMS Issues. Should a DMSMS Issue be identified, the Contractor will submit an Obsolescence Alert Notice IAW the CDRL for DI-MGMT-81941 and this SOW within 15 calendar days of discovering the DMSMS Issue.

The Contractor will also establish individual DMSMS cases for all Documented and Projected DMSMS Issues within 15 calendar days of discovering the issue. DMSMS cases will be used to plan and manage efforts to resolve and implement a solution to the DMSMS Issue from identification to closure.

Once the case is established, the Contractor will report the status of each case to the government IAW the CDRL for DI-MISC-80508B, Technical Report, Study-Services: Case Management Reports.

DMSMS Roadmap. IAW the CDRL for DI-MISC-80508B, Technical Report, Study-Services: DMSMS Roadmap and this SOW, the Contractor will provide a semiannual DMSMS Roadmap of the system to inform the Government of all current and forecasted DMSMS Issues projected to occur over the next five years. This 5-year rolling DMSMS Roadmap will be at the LRU level and will include roll-ups of DMSMS Issues at each succeeding hierarchical level up to the system.

Exhibit A SPRBL1-22-R-0001 Page 8 of 26

Technology Refreshment Planning. The Contractor shall perform technology refreshment planning based on the systems DMSMS Roadmap and Documented and Projected DMSMS Issues. In this regard, the Contractor shall propose to the government a plan of technology refresh events to occur over a ten-year planning horizon. This plan will be optimized to maximize system readiness and minimize Life Cycle Cost (LCC). This plan shall include, for each recommended refresh event, a summary of the DMSMS Issues to be mitigated, the estimated cost to execute, and an estimate of the projected benefits to the government in terms of both cost and improved weapon system readiness. Technology refreshment planning will be coordinated with any planned capability upgrade to allow for an integrated weapon system Technology Refreshment plan. This plan will include both hardware and software system components. The Contractor shall deliver this plan IAW the CDRL for DI- MISC-80508B, Technical Report, Study-Services: 10-year Rolling Technology Refreshment Plan and this SOW. Key details of the Technology Refreshment Plan will be an agenda item for the OWG, and a proposed agenda item for any design reviews or contract In Process Reviews (IPR’s).

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

- Number of items on the BOM

- Number of items on the BOM which are considered standard or commonly used parts;

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

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

- Number of BOM items with open cases whose timeline to closure that might likely impact contract performance or readiness.

These metrics will be submitted to the government IAW the CDRL for DI-MISC-80508B, Technical Report, Study–Services: DMSMS Metrics Report and this SOW. The review of these metrics will be an agenda item for the OWG and a proposed agenda item for the any contract In Process Reviews (IPR’s).

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

Part Revisions Departures from CB. No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with DI-MISC-80711A and are approved by the Government Configuration Manager (C Mgr.) or Configuration Management Officer (CMO) and which are made applicable to the contract

Exhibit A SPRBL1-22-R-0001 Page 9 of 26 by the PCO. Configuration Control shall be affected by the Configuration Control Documents (CCDs) as follows:

Engineering Change Proposal (ECP) includes both the engineering change and the supporting documentation by which the change is described and suggested. An ECP describes changes to the CI/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 and is used to determine any Technical Manual (TM) impacts. The Government must be notified of any part changes in order to update the proper TMs.

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.

Identification of Authorized Personnel. The contractor shall identify to the PCO, Administrative Contracting Officer (ACO), and the technical office identified on the DD Form 1423 for DI-MISC-80711A, the name(s) of the official(s) of its organization who are authorized to submit CCDs 30 Days after Contract (DAC).

Documentation. The contractor shall document by serial number each products configuration, applicable documentation, maintenance support requirements and spares in relation to the contractor’s configuration baseline. The data in use shall be available for government review and use.

Use of CB Data. The contractor shall assure that all necessary contractor’s activities have access to and use of the contractually specified configuration baseline(s), approved changes and departures, and effectivity data.

The data in use shall be available for government review and use.

SPECIAL INSTRUCTIONS

Requirements for Item Marking (Commercial Off The Shelf Items). 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

Exhibit A SPRBL1-22-R-0001 Page 10 of 26 be marked. This requirement should be entirely met by the contractor’s standard commercial marking.

However, if there is any question about marking it shall be directed to the Contracting Officer for resolution.

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

IUID Marking.

New items: The contractor shall provide IUID, or DoD recognized equivalent, for all items delivered with an acquisition cost of $5000 or more. For long term contracts, any items that have range quantity prices established, that will exceed the $5000 unit price shall have IUID markings from the beginning of the contract.

IUID markings shall be IAW MIL-STD-130N.

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.

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.

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.

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

Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD 130N. 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.

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.

If items are not described by Government Product Technical Data (i.e. Commercial Items), the contractor shall submit diagrams showing placement and description of the IUID marking and applicable installation and processing instructions for government review and approval IAW with CDRL for DI-MISC-80711A and this

SOW.

Per the Department of Defense, Item Unique Identification of Government Property Guidebook, Reporting Government Property In the Possession of the Contractor (PIPC), Guidance for: Defense Federal Acquisition http://www.acq.osd.mil/dpap/pdi/uid/index.html

Exhibit A SPRBL1-22-R-0001 Page 11 of 26

Regulation (DFARS) 252.211-7007, Item Unique Identification of Government Property, Version 1.0, September 21, 2007

For new contracts issued after September 13, 2007, DoD will include an Interim Rule, DFARS 252.211-7007, Item Unique Identification of Government Property (DFARS Case 2005-D015), which permanently revises requirements for reporting of PIPC. The interim rule permanently replaces the DD Form 1662 reporting requirements with requirements for DoD contractors to electronically submit, to the IUID registry, the IUID data applicable to PIPC.

It should be understood that in accordance with DFARS 211.274-5, Contract clauses, the clause at DFARS 252.211-7003, Item Identification and Valuation, must be included in any contract that incorporates the clause at DFARS 252.211-7007, Item Unique Identification of Government Property. This is essential to assure there is no ambiguity in the requirements for assigning, registering, reporting and marking PIPC.

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.

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

Requirements for Final Inspection and Test . The contractor shall implement and maintain a Final Inspection and Test System that meets or exceeds the requirements established below. These requirements are commonly accepted practices employed by industry.

Quality System . The contractor shall establish/maintain an effective inspection and test system for final inspection and test of completed products IAW ANSI/ISO/ASQ(E) Q9001-2015.

Inspection and Testing Procedures . The contractor shall utilize documented procedures for final inspection and testing of finished products to ensure that all contract requirements are satisfied.

Inspection and Testing . The quality system shall assure that all final inspections and tests required satisfying contract requirements are conducted.

Records . The contractor shall maintain adequate records of final inspections and tests to demonstrate that the product satisfies contract requirements.

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 finished products conform to contract requirements. These devices shall be calibrated against certified measurement standards that are traceable back to national/international standards.

Inspection and Test Status . The contractor shall maintain a system for the identification of the final inspection

Exhibit A SPRBL1-22-R-0001 Page 12 of 26 and test status of all products.

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

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

Training Requirements . The contractor shall identify/provide for the training needs of their personnel performing inspections and tests.

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

Exhibit A SPRBL1-22-R-0001 Page 13 of 26

PACKAGING

Requirements for Packaging. Requirements for Packaging. Preservation, packaging, and marking shall be in accordance with (IAW) Military Standard Practice for Military Packaging MIL-STD-2073-1E and Section ‘D’ of the contract. Level of Preservation (LOP):

Military, Level of Pack (LPK): A, Quantity Unit Pack (QUP): 001. Marking shall be in accordance with MIL-STD-129R. Wood Packaging Material (WPM) shall meet the requirements below. Please ensure the following packaging clauses are included in Section ‘D’ of the contract: DS7029 and/or DS7033 Preservation, Packing and Marking Instructions.

Wood Packing Material

Wood packaging material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frame and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSB). Wood packing material includes pallets. See DLAD 52.247-9012 Requirements for Treatment of Wood Packaging Material (WPM).

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.

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

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

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.

Wood packing material includes pallets. See DLAD 52.247-9012 Requirements for Treatment of Wood Packaging Material (WPM).

http://www.alsc.org/

Exhibit A SPRBL1-22-R-0001 Page 14 of 26

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

DS7029 - DS7033 LEGEND

Qty Quantity Prot Req Protection Required PKG-REF Packaging Reference (Military/Federal Specification or

Standard) SPI Special Packaging Instruction LPK Level of Packing QUP Quantity per Unit Pack ICQ Intermediate Container Quantity Pkg Reqmt Codes

Packaging Requirement Codes when PKG-REF cites MIL-

STD-2073

The below codes are for special markings:

PC Project Code WG Warranty/Guarantee SL Shelf Life BC Bar Code FMS Foreign Military Sales

Exhibit A SPRBL1-22-R-0001 Page 15 of 26

DS7029 - DS7033

NSN

Prot Req PKG-REF or SPI LPK QUP ICQ

Special Markings

Pkg J. J J J J J J J J J Reqmt I. II. III. IV. V. VI. VII. VII.a IX X Codes (MP) (CD) (PM) (WM) (CD) (CT) (UC) (IC) (PK) (SM)

6115-12-341-6789 Military AG00000662 A 1 - ZZ Z ZZ ZZ ZZ Z ZZ - - 03 BC 2920-12-345-5330 Military MIL-STD-2073-1E A 1 - 42 1 00 00 JC D ED - - - 00 BC 5840-12-341-7003 Military MIL-STD-2073-1E A 1 - 43 1 00 00 AD Z* FF - - - 00 BC 2815-12-341-6896 Military AG00000605 A 1 - ZZ Z ZZ ZZ ZZ Z ZZ - - 03 BC ZZ/Z = See SPI for requirements Z* = As required

Exhibit A SPRBL1-22-R-0001 Page 16 of 26

CONTRACT SECURITY REQUIREMENTS

N/A

Exhibit A SPRBL1-22-R-0001 Page 17 of 26

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

CDRL

Data Line No. DID Identification Title A001 DI-MISC- 80711A Scientific and Technical Reports – Configuration Control B001 DI-MISC- 80711A Scientific and Technical Reports – IUID Marking Diagram/Instructions C001 DI-MGMT- 81948 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Management Plan D001 DI-PSSS- 81656B Bill of Materials (BOM) for Logistics & Supply Chain Risk

Management – Production Phase E001 DI-MGMT- 81941 Obsolescence Alert Notice F001 DI-MISC- 80508B Technical Report-Study/Services – Case Management Report G001 DI-MISC- 80508B Technical Report-Study/Services – DMSMS Roadmap H001 DI-MISC- 80508B Technical Report-Study/Services – 10 year Rolling Technology

Refreshment Plan J001 DI-MISC- 80508B Technical Report-Study/Services – DMSMS Metrics Report -

Production

Exhibit A SPRBL1-22-R-0001 Page 18 of 26

Individual CDRLs

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

A001 Scientific and Technical Reports Configuration Control

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

TOTAL PRICE

DI-MISC-80711A TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

DD ASREQ SEE BLOCK 16 b. COPIES SECT. B

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

SUBMISSION

a. ADDRESSEE Draft

Final

A SEE BLOCK 16

Reg

Repro

16. REMARKS:

Data Item Description DI-MISC-80711A: Delete Block 10 instructions entirely and follow instructions in SOW. The contractor shall prepare and submit Configuration Control Documents in accordance with the SOW section for Configuration Control when a change to or departure from a contractual baseline document is deemed necessary. All deliveries shall be in digital format. All digital files shall be provided both by electronic submission, e.g., e-mail, FTP, etc., as arranged with the requiring office. Alternative delivery media may be discussed with the Contracting Officer prior to delivery.

FCDD-ISR-HFF

PCO

ACO

QAR

* 1 COPY VECP ONLY.

15. TOTAL 0 4 0

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

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Chief, C5ISR Center Branch

10/14/21

Exhibit A SPRBL1-22-R-0001 Page 19 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

B001 Scientific and Technical Reports IUID Marking Diagram/Instructions

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

TOTAL PRICE

DI-MISC-80711A TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

DD ASREQ SEE BLOCK 16 b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

A N/A SEE BLOCK 16

Block 4: Delete Block 10.2 of Data Item Description (DID) and prepare in accordance with the Statement of Work.

Block 12: Delivery of draft shall be 30 DAC. Government has 30 days to review/comment.

Block 13 Delivery of final shall be 30 days after receipt of Government comments. Government has 30 days to determine acceptance.

Contractor to submit DD250 upon acceptance of UID Marking Diagram/Instructions.

Block 14: All digital files will be provided both by electronic submission, e.g., e-mail, FTP, etc., as arranged with the requiring office.

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). CDRLs that are NSP shall not use WAWF to notify the government. E-mail notification is required with any electronic submission.

ACO

15. TOTAL 0 4 0

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 20 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

C001 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

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

DI-MGMT-81948 TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

DD ASREQ 30 DAC b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

Draft to be submitted 30 DAC. Government comments or draft approval will occur 30 days after receipt or 15 days after the contract start of work meeting whichever occurs later. The DMSMS program processes shall be continually reviewed by the contractor and recommended improvements to the management plan shall be proposed at the next OWG meeting.

Changes to the plan deemed by the contractor as critical need not wait for the next OWG. Revisions will be submitted as required. Government comments or revision approval will occur within 15 days after receipt.

Submit electronically in Microsoft Word (unless otherwise approved by the government).

ACO

15. TOTAL 2 2 0

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 21 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

D001 Bill of Materials (BOM) for Logistics & Supply Chain Risk Management

Production Phase

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

TOTAL PRICE

DI-PSSS-81656B TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

DD BLOCK 16 60 DAC b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

The government requires 30 days to provide comments or approve the first submission. Subsequent semiannual submissions to reflect changes or updates will be submitted 30 days prior to each OWG meeting.

Government comments or approval of subsequent submissions will occur concurrent with the OWG minutes. The contractor needs only to submit data for the following BOM data fields: OEM Part Number, OEM CAGE, Software/Firmware Version (if applicable), Indenture Level, Reference Designator (if assigned), NHA Part Number, NHA CAGE, Nomenclature, NSN (if assigned), Manufacturer's Part Number and Manufacturer's CAGE. The contractor shall also provide the following additional data fields; "Case Number" (if assigned), "Case Status" (open (being worked); pending approval (submitted to the government for approval); resolved (approved); closed (implemented)), "End of Life (EOL) date".

Note that where the configuration baseline is to government drawings rather than OEM p/n's, then the government drawing numbers & CAGE codes shall be used in lieu of the OEM p/n & CAGE in the BOM.

Submit electronically in Microsoft Excel format (unless otherwise approved by the government)

ACO

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 22 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

E001 Obsolescence Alert Notice

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

DI-MGMT-81941 TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

LT ASREQ SEE BLOCK 16 b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

Alert notices shall be submitted within 15 days of discovering a DMSMS issue. DID paragraph 2.g. shall indicate the system name. Data provided in response to paragraph's 2. l. & m. need not be provided as the recommended mitigation approach and its estimated cost will be addressed in the resulting DMSMS case.

ACO

15. TOTAL 0 2 0

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 23 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

F001 Technical Report-Study/Services Case Management Report

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

TOTAL PRICE

DI-MISC-80508B TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

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

LT ASREQ SEE BLOCK 16 b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Draft

Final

A BLOCK 16 SEE BLOCK 16

Individual Cases will be established within 15 days of discovering a DMSMS issue. The initial report shall be submitted when the case is established and only document the DMSMS issue and administrative entries. A second submission will be made 30 days later and will describe the contractors proposed plan and time-line to resolve and close the case. Subsequent updates to the case report shall occur whenever there is a significant matter to report (e.g., a change in status, cost, schedule, impact or in the proposed mitigation strategy.

The report shall contain:

Case Number: The DMSMS case number assigned by the contractor for the referenced item.

Current Case Status: "open" (being worked); "Pending" (awaiting approval); "Resolved" (approved); "Closed" (approved and implemented).

Case Opened Date: self explanatory.

Case Status Date: The date that the Case Status was last revised.

DMSMS Issue: Describe the nature of the DMSMS issue.

Case Status Summary: Briefly describe the current status of the case.

Statement of Impact: Describe the impact the issue will have on the affected system if the issue is not resolved. DMSMS impact is defined as the inability to produce or sustain the NHA(s) or the system because of a known or forecasted DMSMS issue.

Impact Date: The impact date is the estimated date that the impact will occur without the adoption of a mitigation strategy.

Proposed Mitigation: The OEM's proposed mitigation strategy to resolve the issue. Briefly describe any alternate mitigation strategies to be considered. For the proposed mitigation strategy, provide estimates for the following: cost, cost avoidance (the difference between the cost of the solution recommended and the solution which, in the assessment of the contractor's case management team, would have been adopted if the DMSMS issue(s) were not discovered until the commencement of a procurement for an item containing the unavailable part), a proposed case schedule identifying key events from the case approval (resolved) to completion (closed).

Submit electronically in Microsoft Word (unless otherwise approved by the government).

ACO

QAR

* 1 COPY VECP

ONLY.

15. TOTAL

2 2 0

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 24 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

9000 A TDP TM OTHER MISC

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

Reparable Spares for the Electric Power Plant III U/W

PATRIOT

TBD TBD

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

G001 Technical Report-Study/Services DMSMS Roadmap

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

TOTAL PRICE

DI-MISC-80508B TBD FCDD-ISR-HFF INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

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

DD SEMIA 180 DAC b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Draft

Final

A

SEE BLOCK 16

The government requires 30 days to provide comments or approve. Subsequent submissions will be 30 days prior to the scheduled date of each future (semiannual) Obsolescence Working Group (OWG) meeting.

The DMSMS Roadmap will be a color coded representation of the DMSMS health of the complete hierarchal design of the system. The report shall graphically present the impact of all DMSMS issues presently forecast to occur over the next five years (i.e., current plus next 5).

The report shall address DMSMS impacts from the lowest spare part assembly level affected (e.g., SRU/LRU) and all hierarchical system elements (NHA's, assemblies, subsystems, etc.)

affected up to and including the subsystem level immediately below the weapon system level.

The report shall provide the quantity of DMSMS issues and the estimated cost to resolve them rolled up from lowest spare part level and at every hierarchical hardware level to the subsystem level just below the weapon system level. Spare part assembly level cells and subsequent hierarchical level cells without any projected DMSMS issues shall be shaded "green". If an impact is forecast to occur within two years the cells for the two preceding years shall be shaded "yellow" (and at all hierarchal levels) The cells for year's when an impact will occur and all succeeding years shall be shaded "red" (and all hierarchal levels).

The "red"cells shall also indicate in text the number of DMSMS issues being reported and the total estimated cost to mitigate these issues at that level. This report shall be provided electronically in a tabular format (Microsoft Excel shall be used unless otherwise approved by the government) with Fiscal Years as the column headers and system elements as indentured rows capable of roll up such that at each hierarchal level the sum of all lower level issues and costs shall be added. To the right of the 5th year a remarks block shall be included to allow the contractor to communicate any pertinent information such as any open actions or information to add clarity to the report. It is unnecessary to duplicate remarks at higher levels of assembly.

ACO

QAR

* 1 COPY VECP

ONLY.

15. TOTAL

2 2 0

Scott Mahoney

FCDD-ISR-HFF

Product Realization Engineer

10/14/21 Mark Caringi

FCDD-ISR-HFF

Exhibit A SPRBL1-22-R-0001 Page 25 of 26

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.