W56HZV19R0209-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0002 2021AUG23

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

FREDERICK W. GERRING

EMAIL: FREDERICK.W.GERRING.CIV@MAIL.MIL

W56HZV-19-R-0209

2021JUL22

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 17

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: FREDERICK W. GERRING

Buyer Office Symbol/Telephone Number: CCTA-AHP-A/(586)282-9978

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. The purpose of amendment 0002 to solicitation W56HZV-19-R-0209 is to:

a. Update L.4.2.1 and delete the hyperlink requirement. The sentence, Hyperlink each of these entries in the Table of Contents to the respective files, has been deleted.

b. Update C.4.6.1 and replace DODM 5200.01 Vol 4 with DODI 5200.48.

c. Update L.5 and replace Volume 3 Administrative Volume with Volume 4 Administrative Volume.

2. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0004 ***

2 17

W56HZV-19-R-0209

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 Description: The contractor shall furnish all services, facilities, labor, parts, materials, equipment, tools and data necessary to supply Trophy Kits, Improved Turret Motors (ITM) and Spare Parts for the SEPv2 and SEPv3 M1A2 Abrams vehicles.

C.2 DESCRIPTION OF SUPPLIES

C.2.1 The contractor shall build and deliver the Trophy Kits in accordance with (IAW) drawings in Attachment 0001, Trophy APS ITM SEPV2 and Spare Parts Excel spreadsheet and all associated Technical Data Package (TDP) elements and Attachment 0002, Trophy APS SEPV3 Excel

Spreadsheet in the quantities required per Delivery Order. The delivery lead-times and monthly delivery rates for all delivery orders are included in Section F of this contract. The individual delivery orders will provide the delivery schedule for the requirements ordered thereon.

C.2.2 CONFIGURATION MANAGEMENT

C.2.2.1 The contractor shall deliver the Trophy Kits, per the description and part numbers described in Attachment 0001- Trophy APS ITM

SEPV2 and Spare Parts Excel Spreadsheet and Attachment 0002, Trophy APS SEPV3 Excel Spreadsheet.

C.2.2.2 The contractor shall use all new parts unless the Procuring Contracting Officer (PCO) authorizes changes.

C.2.2.3 Configuration Baseline: The contractor shall manage and maintain the Trophy Line Replaceable Unit (LRU) product baseline as referenced in Attachment 0001 and Attachment 002 throughout the contract performance period to ensure verification of the LRU product baseline configuration of the ExAPS system at any point during production. As a Non-Developmental Item (NDI), the product baseline for the ExAPS system shall be defined by the LRU level part numbers identified in Attachment 0001- Trophy APS ITM SEPV2 and Spare Parts

Excel Spreadsheet and Attachment 0002, Trophy APS SEPV3 Excel Spreadsheet. Changes to the ExAPS LRU product baseline are classified as defined below. The contractor shall provide notification of Minor (Class II) changes IAW Contract Data Requirements List (CDRL) A001

Configuration Status Accounting Report (CSAR). The USG has final authority in determining and approving whether a variance is minor or major.

C.2.2.3.1 Contractor Initiated Major Change or Variance: The contractor shall conduct configuration control IAW SAE-EIA-649-1, and shall prepare and process Engineering Change Proposals (ECPs). The contractor shall deliver engineering change documentation, including ECPs

IAW CDRL A002, Requests for Variance (RFVs) IAW CDRL A003, and Notice of Revision (NOR) IAW CDRL A004.

C.2.2.3.1.1 The ECP shall be clear and comprehensive from technical, cost, and scheduling perspectives. All potential impacts expressed as changes from the ExAPS LRU product baseline, including change increments for technical, operational, logistical, support, schedule, and cost, shall be included with each change. Include redlined drawings, NORs, cost page, log impact sheet, and the ECP enclosure list for Major (Class I) ECPs. Include the interchangeability/spare/repair parts list for each Major (Class I) ECP as applicable. Include new models for government verification of model integrity and/or new drawings for government design and format approval as part of the ECP submittal. ECP submissions that do not include appropriate NORs will not be accepted. A new ECP must be submitted for any additional proposed changes after ECP approval.

C.2.2.3.1.2 ECPs returned for major revisions or rework shall be resubmitted using the ECP number with a MOD A, MOD B, etc. suffix within 7 days of Government notification. A new ECP must be submitted for any additional proposed changes after ECP approval. Content as of Date shall be marked on labels or file names.

C.2.2.3.1.3 The contractor shall submit a major RFV within 24 hours of identification of a known departure from requirements. Include justification, documentation, and consideration. If the Government determines that an RFV should be a permanent change, the request may be rejected for re-submittal as an ECP. Unless otherwise directed, the Government will typically approve or disapprove major deviations within 30 days. The Government will not approve critical RFVs; these shall be submitted as ECPs. ECP and RFV submittals shall contain the reason for the change, timeline for incorporation, and effected form, fit, or function to include hardware, software, connections and special packaging changes. The contractor shall include available test data from all tests conducted to validate design interchangeability concepts on the proposed change or variance. USG shall have 45 days to review and approve a proposed change or variance.

C.2.2.3.1.4 Upon incorporation of a major change, the contractor shall deliver updated Attachment 0001- Trophy APS ITM SEPV2 and Spare

Parts Excel Spreadsheet and Attachment 0002, Trophy APS SEPV3 Excel Spreadsheet to account for changes to the LRU ExAPS product baseline configuration and the effective date of the change. Within 45 calendar days of approval of the change, the contractor shall deliver at no additional charge to the Government, revisions to all affected contractual data deliverables, to include CDRL A001 Configuration

Status Accounting Report (CSAR). CDRL A001 shall be delivered in contractor format. All ECPs and Interface Control Documents (ICDs) IAW

CDRL A005 shall be delivered IAW Section J, Exhibit A. When the contractor provides assertion of restrictions at the time of an ECP or

ICD then the U.S Government will review the various aspects of the contractor's proposal (and assertion of restrictions) and determine whether to proceed.

C.2.2.3.2 Contractor Initiated Minor Change or Variance: The contractor shall have approval authority for Minor changes and RFVs IAW the

3 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

published outlined contractor procedures listed below in C.2.2.3.2.1 and shall report them to the Government. The contractor shall provide monthly notification via CDRL A001 (CSAR) of all approved Minor changes and RFVs to the PCO and COR.

C.2.2.3.3 Responsibility for the Cost of Changes: The responsibility for the cost of changes is as follows:

There shall be no price increases, or any additional cost to the Government, as a result of a contractor initiated configuration change.

The Government is not responsible for additional testing or software costs associated with any contractor initiated configuration change. Further, any production or delivery delays caused by additional testing and inspection shall not be the basis for an excusable delay as defined in the default clause of this contract. Such delays shall not form the basis for adjustment in contract price or delivery schedule. When a contractor initiated configuration change results in reduced contractor costs, the Government may, at the sole discretion of the PCO, require an equitable downward adjustment to the contract price. The Government is not liable for any costs the contractor may incur, due to delay in contract performance, as a result of any of the contractor's requests for a contractor initiated configuration change.

C.2.2.3.4 Government Initiated Changes: In the event the Government proposes a change to the end item configuration, the PCO will submit a request for technical and price proposal from the contractor. Upon approval, a contract modification will be executed to incorporate the change into the contract. Once the change is incorporated, the contractor shall submit an updated Attachment 0001- Trophy APS ITM

SEPV2 and Spare Parts Excel Spreadsheet and Attachment 0002, Trophy APS SEPV3 Excel Spreadsheet documenting the change. Within 45 calendar days of a bilateral agreement, the contractor shall submit revisions to all affected contractual data deliverables, whether they affect form, fit, or function or not. When the contractor provides assertion of restrictions at the time of an ECP or ICD then the

U.S Government will review the various aspects of the contractor's proposal (and assertion of restrictions) and determine whether to proceed.

C.2.2.3.5 Assertions of Restriction for ECPs: Throughout the life of the contract, for each ECP with each ECP package submission, contractor must submit a complete Assertion of Restrictions IAW DFARS 252.227-7017, 7013, 7014, 7015, and 7028. The contractor shall not deliver or otherwise provide to the Government any technical data or computer software with restrictive markings (or otherwise subject to restrictions on access, use, modification, reproduction, release, performance, display, or disclosure) unless the technical data or computer software has been identified in the Assertion of Restrictions.

C.3 SERIALIZATION AND TRACKING OF MATERIAL

C.3.1 The contractor shall ensure that all LRU hardware have serial numbers that are visible when installed IAW MIL-STD-130. The contractor will provide the USG a copy of all assigned serial numbers.

C.3.2 The contractor shall provide the packing list to PM Abrams within 5 calendar days IAW CDRL A006 (Serialization and Tracking of

Material). The packing list shall include serial numbers of the Trophy Kits in each shipment container per hardware delivery set.

C.4 Security Requirements

C.4.1 Classification

The contract will not require access to classified information in performance of this contract. The contractor will have access to

Controlled Unclassified information (CUI). CUI provided to or generated pursuant to this contract shall be protected. The procedures for the protection of CUI are below and in DFARS 252.204-7012.

C.4.1.1 General: There are types of information that are not classified but that require application of access and distribution controls and protective measures for a variety of reasons. This information is known as controlled unclassified information (CUI). The types of information considered CUI for the program are information marked For Official Use Only by the U.S. Government and technical information. When handling CUI material, all personnel are to comply with these requirements and follow their company policy and/or applicable Proprietary Information Agreements (PIA) concerning the protection of proprietary information in situations not clearly stated herein.

C.4.1.2 Technical Information Description: Any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process, or can be used to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The information may be graphic or pictorial delineations in media (e.g., computer software, drawings, or photographs), text in specifications, related performance or design documents, or computer printouts. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation.

C.4.1.3 For Official Use Only (FOUO) Information Description: For Official Use Only (FOUO) is a Government designation applied to

UNCLASSIFIED information that may be exempt from mandatory release to the public under the Freedom of Information Act (FOIA). FOUO information includes information identified as such in the Abrams Family of Vehicles (FOV) Security Classification Guide (SCG), dated 2

February 2017, the TROPHY Active Protection System (APS) SCG, dated 23 December 2019, or information from a government document marked

FOUO.

4 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.4.1.4 CUI Markings: Marking of FOUO documents will be IAW Army Regulation (AR) 25-55. Information extracted from an FOUO document will carry the FOUO marking until formally reviewed by the government. AR 25-55 can be found at http://www.apd.army.mil/ProductMaps/PubForm/AR.aspx . Marking of Technical information will include the statement provided in the Security Classification Guide. If the contents of the technical document require more than one Distribution Statement, apply the most restrictive statement. This does not preclude additional mandated markings as may be required by the contract.

C.4.1.5 Protection of CUI Information

C.4.1.5.1 Access: CUI may be released only to an individual who has a valid need for such access in connection with the accomplishment of a lawful and authorized Government purpose. Information in any media format may only be disseminated on a need-to-know basis. The need-to-know restricts the use or dissemination of CUI data to those individuals or organizations with direct affiliation with the given program or project. Further dissemination of such information will be at the discretion of the Government Security Manager. Personnel no longer requiring access to CUI must dispose (see Disposal below) or surrender any in their possession and terminate future access to it.

C.4.1.5.2 Storing/Handling: During working hours, take reasonable steps to minimize risk of access to CUI by unauthorized personnel.

After working hours, when not in physical possession of the owner, all CUI (whether hardcopy or optical media (e.g., DVDs, CDs) that contain CUI) must be afforded a reasonable degree of physical protection to prevent theft of program information (e.g., store CUI information in locked desks or file cabinets, locked rooms, cable lock laptops, storing in a trunk, storing out of site or similar means). Do not display CUI in public places (e.g., airports, airplanes, restaurants). Electronic storing and processing of CUI shall be

IAW DFARS 252.204-7012 Safeguarding Controlled Defense Information and Cyber Incident Reporting. Do not process CUI on public computers

(e.g., those available for use by the general public in kiosks, hotel business centers), public wireless networks or computers that do not have access control. Personally owned computers and personally owned devices are not authorized to process CUI. Portable electronic devices (e.g., smartphones, laptop computers, and tablets), non-portable computers, and removable media (e.g., external hard drives, flash drives, USB drives; not including optical media) must be physically and electronically protected as described in this instruction and the DFARS 252.204-7012.

C.4.1.5.3 Dissemination: CUI printed documents and material may be transmitted through mail channels, commercial carrier or hand-carried without formal courier orders. FOUO information may be disseminated to DoD personnel and DoD contractors to conduct official business for the program. If dissemination is required outside of DoD personnel or DoD contractors, contact the Government Security Manager for approval. Technical information will follow the release instructions identified in the Distribution Statement. Use secure communications whenever possible; however, land-line telephones are more secure than cellular telephones and should be used whenever available for discussions involving CUI. Transmit voice and facsimile transmissions only when you have a reasonable assurance that only authorized recipients will have access to the transmission. Digital transmission shall comply with the below.

C.4.1.5.3.1 All transmission and/or dissemination of CUI (i.e., email and file transfers) must use National Institute for Standards and

Technology/National Information Assurance Partnership (NIST/NIAP)-approved cryptographic products/algorithms, e.g., DoD-approved Public

Key Infrastructure Certification or DOD Safe Exchange at https://safe.apps.mil . These are available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm . This encryption requirement includes communications that contain passcodes to teleconferences or web conferences where there is a reasonable expectation that CUI may be discussed. When encryption is not available, a government collaborative suite (aka Integrated Digital Environment [IDE]) must be used to transmit CUI.

C.4.1.5.3.2 Contractor-hosted collaborative suites may be used for digital transmission and/or dissemination of CUI by personnel not located on a government backbone (e.g., NIPRNET), provided the following conditions apply: 1) use only NIST/NIAP-approved cryptographic products/algorithms. The latest validation lists may be obtained at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm ; and 2) use an internally hosted service that does not use a third-party collaborative suite service provider.

C.4.1.5.3.3 Do not post CUI to web pages that are publicly available or have access limited only by domain/IP restrictions. As permitted by other contract provisions, CUI may be posted to web pages that control access through the use of a DoD approved Public Key

Infrastructure Certification and that provide protection via use of secure sockets, or other equivalent technologies. These are available at http://iase.disa.mil/pki/eca .

C.4.1.5.3.4 As new technologies become available in the electronics arena, care should be given to providing a reasonable degree of protection from known vulnerabilities.

C.4.1.5.3.5 The Internet is Public Access. CUI must be reviewed and officially approved by the Program Executive Office Ground Combat

Systems (PEO GCS) Public Affairs Officer for public release before placing on the Internet. This is not applicable when the Internet is used for e-mail transmissions and encryption is used as noted above.

C.4.1.6 Disposal: Destroy CUI documents by any means approved for the destruction of classified information, i.e. cross-cut shredding or other means that would make it difficult to recognize or reconstruct the information. The contractor shall ensure any covered defense information provided by the Government under this contract is destroyed or sanitized from contractor-owned media and reported IAW NIST

Special Publication (SP) 800-88, Rev 1, Guidelines for Media Sanitization, December 2014, or returned to the owning organization upon the completion of the contract or as directed by the PCO.

5 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.4.1.7 Report of Loss of CUI: Report any loss of CUI to the Government Security Manager. Initial reports shall be made as expeditiously as possible in all cases within 72 hours of discovery. If additional information is required after submission and review of the initial report, guidance will be provided at that time. Mark any reports For Official Use Only, exemptions 2 and 5 apply. Initial report content shall include the following information as available.

Applicable dates, including dates of compromise and dates of discovery

Threat methodology, including all known resources used (e.g. IP addresses, domain names, software tools)

Account of what actions the threat(s) may have taken on victim system/network

What information may have been compromised or lost, and its potential impact on government programs.

C.4.2 Public Release Requests. The contractor shall screen all information submitted for determination of public release to ensure it is both unclassified and technically accurate. The contractor shall provide a letter of transmittal certifying a screening was conducted and that the contractor attests that the information is unclassified and technically accurate, to the best of the contractor's knowledge. The contractor shall not release program information outside of program channels until the Government review process is complete. The contractor shall submit all requests for public release approval through the PCO for a review by Government technical and security personnel and by the Government's Public Affairs Officer (PAO). The PCO will, after appropriate review, either authorize or reject the request to disseminate Government information publicly. Note that authorization may be given contingent on specified changes being made to the material for which public release has been requested. The program requires 45 calendar days to process the request and render a decision. Requests for public release shall be sent electronically via encrypted email using cryptographic products that are

NIST/NIAP approved or mail a Compact Disc/Digital Video Disc (CD/DVD) using U.S. Postal First Class mail.

C.4.3 Operations Security (OPSEC) Requirements. The contractor is not required to produce an OPSEC Plan. U.S. contractors with access to CUI (e.g. technical information, information marked with a distribution statement or FOUO) information shall be required to follow the Product Director Main Battle Tank Systems (PD MBTS) OPSEC Plan, Attachment 0003. To ensure awareness of the PD MBTS OPSEC Plan, the contractor shall provide annual training for personnel supporting this contract on the contents of the PD MBTS OPSEC Plan. The contractor shall ensure that new personnel receive PD MBTS OPSEC Plan specific training within 30 days of program assignment. Personnel who have taken the PD MBTS OPSEC Plan training within the last 12 months shall be considered compliant unless the PD MBTS OPSEC Plan has been revised since the last training. The contractor shall report IAW CDRL A007, (OPSEC Awareness Training Report).

C.4.4 Information Flow Down. The contractor shall ensure the security requirements and guidelines contained in section 4.1 is flowed down to U.S. subcontractors and consultants.

C.4.5 Training Requirements

C.4.5.1 OPSEC Awareness Training Requirements

All contractor employees shall complete OPSEC Awareness for Military Members, DoD Employees and Contractors training. This training is available at: https://securityawareness.usalearning.gov/opsec/ . All training shall be completed and reported IAW CDRL A007

(OPSEC Awareness Training Report). An alternative method is to conduct face-to-face training in a classroom or auditorium setting, using a sign-in or attendance sheets in lieu of certificates. The instructor will be OPSEC Level II certified to perform this alternative training method.

C.4.6 Covered Defense Information

C.4.6.1 Identify all covered defense information associated with the execution and performance of this contract. At the post-award conference the contractor and the Government/Program Office shall identify and affirm marking requirements for all covered defense information, as prescribed by DoDI 5200.48, Controlled Unclassified Information, and DoDI 5230.24, Distribution Statements on Technical

Documents, to be provided to the contractor, and/or to be developed by the contractor, associated with the execution and performance of this contract.

C.4.6.2 Track all covered defense information associated with the execution and performance of this contract. The contractor shall document, maintain, and provide to the Government, a record of tier 1 level subcontractors, vendors, and/or suppliers who will receive or develop covered defense information as defined in DFARS Clause 252.204-7012, and associated with the execution and performance of this contract. The contractor shall report IAW CDRL A007.

C.4.6.3 Restrict unnecessary sharing and/or flow down of covered defense information associated with the execution and performance of this contract. The contractor shall restrict unnecessary sharing and/or flow down of covered defense information as defined in DFARS

Clause 252.204-7012, and associated with the execution and performance of this contract IAW marking and dissemination requirements specified in the contract and based on a need-to-know to execute and perform the requirements of this contract.

C.4.6.5 System Security Plan

C.4.6.5.1 The contractor shall, upon request, provide to the government, a system security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of DFARS 252.204-7012, and IAW NIST Special Publication (SP) 800-

171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations in effect at the time the solicitation is issued or as authorized by the PCO, to describe the contractors unclassified information system(s)/network(s) where covered defense

6 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

information associated with the execution and performance of this contract is processed, is stored, or transmits. The contractor shall report IAW CDRL A008.

C.4.6.5.2 The contractor shall, upon request, provide the government with access to the system security plan(s) (or extracts thereof) and any associated plans of action for each of the contractors tier one level subcontractor(s), vendor(s), and/or supplier(s), and the subcontractors tier one level subcontractor(s), vendor(s), and/or supplier(s), who process, store, or transmit covered defense information associated with the execution and performance of this contract. The contractor shall report IAW CDRL A008.

C.5 Monthly Status Reports

The contractor shall deliver a monthly Production Status Report IAW CDRL A009.

C.6 MEETINGS

C.6.1 Start of Work Meeting: The contractor shall conduct a Start of Work meeting within 14 calendar days after the award of the contract. The Start of Work meeting shall be conducted via MS Teams, face-to-face at U.S. Army TACOM in Detroit Arsenal, MI or contractor location per COR concurrence. The Start of Work Meeting is to assure a clear and mutual understanding of the contract terms, conditions, line items, technical requirements and sequence of events needed for successful execution of the contract. The contractor shall have no more than six representative in attendance at the meeting and shall be prepared to discuss the scope of work.

C.6.1.1 The contractor shall prepare and deliver meeting minutes and action items IAW CDRL A020 for all meetings in C.6.1.

C.6.2 Program Review Meeting

The contractor shall host Program Review meetings every three months beginning 60 calendar days after contract award to provide a formal detailed information exchange between the contractor and the Government on all associated aspects of the project, to include programmatic, technical, and logistical statuses. The contractor shall provide to the Government at least 14 calendar days advance notice of the time, date, and location of the review meetings.

C.6.2.1 The contractor shall prepare and deliver meeting minutes and action items IAW CDRL A020 for all meetings in C.6.2.

C.6.3 Progress Status Meetings

Progress status meetings shall be held as directed by the Program Management Office. These meetings shall be scheduled on a recurring basis with intervals no more than weekly but no less than monthly, The goal of progress status meetings is to discuss the critical aspects of this project related to program success. The contractor shall provide to the Government at least 4 calendar days advance notice of the time, date, and location of the progress status meetings.

C.6.3.1 The contractor shall prepare and deliver meeting minutes and action items IAW CDRL A020 for all meetings in C.6.3.

C.7. Hazardous Materials Management

For the purposes of this contract, hazardous materials are defined by section 3.2 of FED-STD-313E.

C.7.1. Prohibited Hazardous Materials

The system shall not have prohibited materials (including alloys containing prohibited materials) present in or on any delivered systems or support equipment, required for operation and sustainment of the system, or used in final manufacture and assembly processes(T=O).

Prohibited materials are as follows:

- Asbestos

- Beryllium

- Cadmium,

- Class I and Class II Ozone Depleting Substances

- Hexavalent Chromium

- Lead

- Mercury

- Radioactive Materials

- Group 1 Agents classified as carcinogenic to humans by the International Agency for Research on Cancer (IARC) Monographs

C.7.2. Exceptions to the Hazardous Materials Requirements

The following exceptions to the Prohibited Hazardous Materials listed in Section C.7.1 are allowed without prior approval from the

Government:

1) Cadmium and hexavalent chromium on electrical connectors and back shells used to mate with cadmium electrical connectors on

Government Furnished Equipment (GFE)

2) Cadmium and hexavalent chromium on electrical connectors used in Automatic Fire Extinguishing Systems (AFES)

7 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3) Chemical Agent Resistant Coating (CARC) primers and topcoats meeting MIL-DTL-53039, MIL-DTL-64159, MIL-DTL-53030, MIL-DTL-53022

4) Lead-acid batteries

5) Lead solder

6) Leaded battery terminal adaptors/clamps

7) Steel containing up to 0.35 % lead by weight

8) Aluminum containing up to 0.4 % lead by weight

9) Copper and Brass alloys containing up to 4 % lead by weight

10) Beryllium and Beryllium alloys used in electrical components

11) Mercury containing components compliant with European Union (EU) Directive 2002/95/EC (RoHS)

12) Trace amounts of identified restricted materials contained in base materials and/or alloys. For the purposes of this contract trace amounts are defined as <0.1% by weight for carcinogens and <1%by weight for all other materials.

C.7.3 Hazardous Materials Waivers

Waivers from the hazardous materials requirements shall not be permissible except where a suitable alternative does not exist. The contractor shall submit formal waiver requests to the Government using the Request for Use of Prohibited Materials Form (Attachment

0012). The Government will make the final determination on whether sufficient justification has been provided to support approval of any waiver requests. The contractor shall not use or deliver any prohibited hazardous materials without prior Government waiver acceptance, with the exception of the materials listed in Section C.7.2. If a waiver is approved by the Government there shall be no adjustment to the delivery schedule. If a waiver is granted and results in reduced contractor costs, the Government may, at the sole discretion of the

PCO, require an equitable downward adjustment to the contract price.

C.8. Disposal and Demilitarization

Supplies delivered under this contract are classified as military items. Therefore, the contractor shall follow all the instructions provided by Defense Contract Management Agency (DCMA) Plant Clearance Officer IAW FAR 52.245-1 for the disposal of completed or partially completed parts, assemblies, subassemblies, and end items. Property (whether title to the property is with the Government or not and including parts, components, subassemblies, and assemblies) covered by this contract for which the contractor does not claim or is refused payment (including, but not limited to, rejects or overruns), but which is manufactured, fabricated, assembled, or produced in connection with items covered by this contract shall be completely destroyed or mutilated so as to be non-reclaimable for its original purpose and to preclude the possibility of reconditioning to make it saleable as an implement of war.

C.8.1 Demilitarization is required IAW demilitarize (DEMIL) Code D requirements. These requirements can be obtained through the Federal

Logistics Information Service or FedLog at https://www.dla.mil/HQ/InformationOperations/Offers/Products/LogisticsApplications/FEDLOG.aspx .

C.8.2 The contractor shall be responsible for demilitarization. Demilitarization dispositioning through approved Government facilities or depots is allowed provided that the Government facility or depot agrees. This authorization in no way binds the Government facility or depot to perform demilitarization under this contract.

C.9 Costed Indentured Bill of Material (BOM)

C.9.1 Costed Indentured Bill of Material (BOM)

The contractor shall prepare and deliver the Costed Indentured Bill of Material (BOM) IAW CDRL A010 Costed Indentured Bill of Material

(BOM).

C.9.1.1 The contractor shall develop, maintain, and deliver a Costed Indentured Bill of Material (IBOM) in accordance with DI-MISC-

80508B(T). The contractor shall ensure the Costed Indentured BOM deliverables show "part level" detail including all of the following:

- CWBS Element and Structure Level of Assembly (Hierarchy)

- Unit of Measure (each, pounds, inches, or other)

- Quantity or Value (count, weight, length, or other)

- Nomenclature

- Part Number (Contractor or Vendor as applicable)

- National Stock Number (NSN), if applicable

- Cost Source (quote, purchase order, estimate, or other)

- Make or Buy

- Unit Cost

- Extended Cost

- Vendor

- BOM Tree Level

C.9.1.2 The contractor shall supplement the Costed Indentured BOM with an analysis that provides traceability and linkage to the data submitted in the Cost and Hour Report (FlexFile) (CDRL A012) The contractor shall provide this information in MS Excel format, without encryption, locks, passwords, or other security protection features which would prevent the Government from editing, sorting, merging, or otherwise manipulating the data for Government purposes.

8 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.9.2 Cost and Software Data Reporting (CSDR)

Cost and Software Data are the primary means by which the Department of Defense (DoD) collects data on the costs that contractors incur on DoD programs. Reliable and comprehensive cost data is essential to produce credible cost estimates as required in both statute and regulation. The governments goals and use of CSDR data is to improve the quality of cost estimates; ensure proper resource allocation occurs within the DoD; and enable data driven decision making by program and department leadership. The contractor shall systematically collect and report actual contract costs IAW with the following CDRLs:

Report Title CDRL

Resource Distribution Table A011

Cost and Hour Report (FlexFile) A012

Quantity Data Report (DD Form 1921-Q) A013

Contractor Business Data Report (DD Form 1921-3) A014

Technical Data Report (TDR, DD Form 1921-T) A015

C.9.2.1 Application to Subcontractors

The contractor shall flow-down CSDR requirements referenced in sections C.9.2 and its sub-paragraphs to subcontractors (regardless of subcontractor tier) when the subcontract value is expected to exceed $50 million using the maximum allowable contract quantities, hours, or options (as applicable), as required by Department of Defense (DoD) 5000.04-M-1 - CSDR Manual. The contractor shall require subcontractors to electronically submit CSDR deliverables directly to the Defense Cost and Resource Center (DCARC). The contractor shall ensure that Subcontractors subject to CSDR reporting thresholds collect data in sufficient detail to meet Attachment 0005 - CSDR Plan requirements. The Contractor shall collect and deliver data on all subcontractors to comply with CDRL A011 - Resource Distribution Table and Attachment 0005- CSDR Plan requirements. A subcontractor is any organization which the prime contractor has any agreement, purchase order, or instrument other than a prime contract calling for work or for the material required for the performance of one or more prime contracts. It usually covers procurement of major components or subsystems that require the subcontractor to do extensive design, development, engineering, and testing to meet a prime contractors procurement specifications.

C.9.2.2. Resource Distribution Table (RDT)

The contractor shall prepare and deliver the Resource Distribution Table (RDT) IAW CDRL A011. This document is meant to identify the value of work assigned to the contractor and its subcontractors.

C.9.2.3 Cost and Hour Report (FlexFile)

The contractor shall prepare and deliver the Cost and Hour Report (FlexFile) IAW CDRL A012. This document is meant to report actual costs and hours related business data incurred in order to perform this contract.

The contractor shall develop and maintain a Contractor Work Breakdown Structure (CWBS) and CWBS Dictionary IAW CDRL A012 throughout the life of the contract. The contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The contractor shall extend the CWBS to provide adequate internal management, surveillance, and performance measurement of the contract. For any given parent WBS element, additional child WBS may be utilized to collect Other costs, however, the Other WBS shall not contain more the 10% of the total anticipated cost of the parent WBS element. The contractor shall ensure all CWBS oriented reporting is compliant with at least the lowest WBS levels identified by

Attachment 0005 - CSDR Plan.

C.9.2.4 Quantity Data Report (DD Form 1921-Q)

The contractor shall prepare and submit the Quantity Data Report (DD Form 1921-Q) IAW CDRL A013. This document is meant to report program quantity information to provide context to cost and hour data and in order to derive accurate unit cost information.

C.9.2.5 Contractor Business Data Report (CBDR, DD Form 1921-3)

The contractor shall prepare and submit the Contractor Business Data Report (DD Form 1921-3) IAW CDRL A014. This document is meant to provide the means to facilitate estimating and analysis of indirect contract costs.

C.9.2.6 Technical Data Report (TDR, DD Form 1921-T)

The contractor shall prepare and submit the Technical Data Report (TDR, DD Form 1921-T) IAW CDRL A015.

C.9.2.7 Post-Award Cost and Software Data Reporting Conference

The contractor shall host a Post-Award CSDR Conference at the contractors facility where CSDRs are prepared with the Governments Cost

Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD 5000.04-M-1 (CSDR Manual). The purpose of the Post-Award

CSDR Conference is to review the contracts CSDR requirements and assess how the Contractors accounting system satisfies the CSDR requirements found in DoD 5000.04-M-1, CSDR Manual and Attachment 0005- CSDR Plan. In a briefing presented by the contractor in its own format, the contractor shall:

Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.

Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.

Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by Attachment 0005 - CSDR

Plan.

9 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Present the methodologies used for mapping internal cost accounts to the CWBS, specifically showing how individual CWBS elements and functional element codes will be populated.

Propose changes to Attachment 0005- CSDR Plan in order to tailor the plan to the contractors accounting system, to include any contractor recommended changes or additions to the CWBS elements in Attachment 0005 - CSDR Plan. These changes may include adjustments to the contractors submission events and/or submission timeline, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.

The contractor and CWIPT will also review the initial submission for CDRL A011, the Resource Distribution Table (RDT) in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the

Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver IAW

Attachment 0004 - RDT and Attachment 0005 - CSDR Plan.

Within 30 days of completing the Start of Work Meeting or CSDR Readiness Review, whichever is later, the Government will inform the contractor of the exact date and location of the Post-Award CSDR Conference. This conference has an anticipated duration of one business day.

C.9.2.8 Contractor Business Data Report (CBDR, DD Form 1921-3)

The contractor shall prepare and deliver IAW CDRL A014, the contractor Business Data Report (DD Form 1921-3) to provide the means to facilitate estimating and analysis of indirect contract costs, as specified in Attachment 0005 - CSDR Plan.

C.10 Import and Export Licenses and Authorizations

C.10.1 The contractor shall be responsible to obtain and maintain all necessary import and export licenses and authorizations.

*** END OF NARRATIVE C0001 ***

10 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 General Proposal Information

L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal paragraph of Instructions to Offeror(s)

Competitive Acquisitions (FAR Provision 52.215-1) contained in Section L of the solicitation, shall be submitted in the format and quantities set forth below. All information necessary for the review and evaluation of a proposal is to be contained in the proposal volumes set forth below. Section M of the solicitation sets forth the evaluation criteria and delineates the Factors to be evaluated and their relative order of importance. The offeror's proposal, as required by this section, will be evaluated as set forth in Section

M of this solicitation. The Government will not assume the offeror possesses any capability, understanding, or commitment not specified in its proposal. It is an offeror's responsibility to submit a well-written proposal, with adequately detailed information, which clearly demonstrates an understanding of and the ability to comply with the solicitation requirements to allow for a meaningful evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals.

L.1.2 Minimum Acceptance Period

This provision supersedes any language pertaining to the acceptance period that may appear elsewhere in this solicitation (e.g. SF 33

Box 12).

ACCEPTANCE PERIOD means the number of calendar days available to the Government for awarding a contract from the date specified in this solicitation for receipt of offers.

L.1.2.1. The Government specified minimum acceptance period of 180 calendar days.

L.1.2.2. The offeror shall clearly state in its proposal Administrative volume the acceptance period. Offerors may specify a longer acceptance period than the Government's minimum acceptance period stated above.

L.1.2.3. An offer allowing less than the Government's minimum acceptance period, or fails to provide a proposal acceptance period, may be rejected.

L.2 Proposal Content, Format and Instructions

L.2.1 Proposal Content

L.2.1.1 All proposals shall be in English (American Standard) and shall be in US dollars. Proposals not in English (American Standard) or in US Dollars may be rejected. The proposal shall include all information specified and shall address all requirements outlined in

Section L. The offeror's proposal shall be organized in the following volumes:

Volume Number Title

Volume 1 Technical Factor

Volume 2 Price Factor

Volume 3 Small Business Participation

Volume 4 Administrative

L.2.1.2 A Proposal Executive Summary or transmittal letter is not required nor will it be evaluated.

L.2.2 Proposal Method of Submission, Format, and Instructions

L.2.2.1 The proposal shall be electronically submitted via E-mail to the Contract Specialist, Frederick Gerring, and cc the Contracting

Officer, John Sarti, at the following e-mail address(s) with the subject header: Proposal Submission - W56HZV-19-R-0209 (company name):

Contract Specialist: Frederick.w.gerring.civ@mail.mil

Contracting Officer: John.m.sarti2.civ@mail.mil

Fax, hardcopy, and DVD/CD-ROM proposals will NOT be accepted. Hand-carried offers, whether hardcopy or electronic, will NOT be accepted.

Maximum size of each e-mail shall be 10 megabytes. The offeror may use multiple e-mail messages for each submission, however, it should annotate the subject lines as described above for each message, and number them in this manner: Message 1 of 3, 2 of 3, 3 of 3.

Note: There is no "expected" or "target" length of time for proposal submission via email; size and content may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

L.2.2.1.1 Each submitted File shall be labeled so it is easily identifiable for which volume it pertains.

11 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.2.1.2 Acceptable File Formats. All electronic information provided in response to the solicitation must be provided in Microsoft

(MS) Office 2013 compatible or Adobe Portable Document Format (PDF) format or except as noted in instructions for individual volumes.

For files in PDF format, scanners should be set to 200 dots per inch. The proposal shall not contain citations for, or active links to live Internet sites or pages. All linked information shall be contained within the electronic proposal. Any linked information that is not contained in the proposal will not be accepted.

L.2.2.1.3 Electronic Files. The proposal electronic file name should not exceed 50 characters in length (not including the file extension). Ensure the file name does not contain any periods, does not contain spaces, and does not contain special characters, which should limit Government virus scanners rejecting the email as unscannable.

L.2.2.1.4 Unless otherwise specified, it is recommended that the proposal be formatted for 8.5 inch x 11 inch paper with a minimum font size of 10 pt. and with a minimum of 0.5 margins. Schedules, drawings and other documents more appropriate to larger size should be formatted for no larger than 8.5 inch x 14 inch dimensions.

L.2.2.1.5 Provide spreadsheets that include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets are to be visible. Do not include Zero height and zero width rows and columns in Worksheets. Do not format Worksheet cells with the font color equal to the fill color. If Workbooks or Worksheets are password protected, then the passwords must be provided. Do not submit Print image files or pictures or files containing only values.

Failure to provide fully functional excel spreadsheets in the proposal may result in the…