W912CH24Q0035 Solicitation AMD 0001.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

0001 2025JAN21

W912CH

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

HEATHER R. MIERENDORF

EMAIL: HEATHER.R.MIERENDORF.CIV@ARMY.MIL

W912CH-24-Q-0035

2025JAN08

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 6

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SUPPLEMENTAL INFORMATION

Buyer Name: HEATHER R. MIERENDORF

Buyer Office Symbol/Telephone Number: CCTA-APN-A/(517)644-4388

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

Weapon System: Tank, M1 Abrams Family of Vehicles

*** End of Narrative A0000 ***

1. The purpose of this Amendment 0001 is to update Solicitation W912CH-24-Q-0035 with the following:

Section C:__________

a) Update contractor instructions for Section C.3 OPSEC Training Requirement. See C.3.4.

2. All other terms and conditions of the Solicitation remain unchanged and in full force and effect.

*** END OF NARRATIVE A0002 ***

2 6

W912CH-24-Q-0035

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 TECHNICAL DATA PACKAGE INFORMATION______________________________________

C.1.1 The following Xd item applies to this solicitation:

[ ] 1. There is no Technical Data Package (TDP) included with this solicitation.

[ X ] 2. The TDP for this solicitation resides within the System for Award Management (SAM) (https://SAM.gov ) associated with this solicitation number:

W912CH-24-Q-0035

To access the data through SAM:

a. Log on to the SAM web site: https://SAM.gov .

b. Search for the solicitation number.

c. Click on the attachment you would like to view.

d. If the attachment is restricted, request access to the document.

(1) TDPs that have an Export Control Warning Notice are subject to the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et.seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C, App. 2401 et. seq..

(2) Further dissemination must be in accordance with provisions of DoD Directive 5230.25. This also applies to distribution of the TDP to all SUBCONTRACTORS at every level.

(3) To obtain these TDPs, contractors must have a current DD 2345, Militarily Critical Technical Data Agreement on file with Defense

Logistics Information Service (DLIS). To obtain certification, go to https://public.logisticsinformationservice.dla.mil/jcp/search.aspx

(4) Upon completion of the purposes for which Government Technical Data has been provided, the Contractor is required to destroy all documents, including all reproductions, duplications, or copies thereof as may have been further distributed by the Contractor.

Destruction of this technical data shall be accomplished by: shredding, pulping, burning, or melting any physical copies of the TDP and/or deletion or removal of downloaded TDP files from computer drives and electronic devices, and any copies of those files.

C.1.2 If technical data is otherwise restricted, select Request Explicit Access. This will generate an email to the Contract Specialist and Contracting Officer at Army Contract Command - Warren (DTA) with all the information needed to grant contractor access to restricted documents. SAM will automatically generate an email stating when the requesting contractor has permission to view or download TDP items.

C.1.3 If multiple individuals in the contractors organization need access to the Technical Data Package (TDP) for a solicitation and an explicit access request is required, each individual MUST submit an explicit access request to be granted approval to view the TDP.

Those same individuals MUST be registered in SAM. Any individuals no longer with the company should be deleted. Questions related to registration in SAM should be directed to https://www.sam.gov/ The SAM helpdesk phone number is (866) 606-8220. Vendors are responsible for placing correct information in SAM.

C.1.4 It is strongly suggested that contractors submit the explicit access request and provide the buyer with the completed Use and Non-

Disclosure Agreement at the same time if the solicitation requires both to gain access to view the TDP.

C.2 CONFIGURATION MANAGEMENT DOCUMENTATION__________________________________________

The Contractor may submit Engineering Change Proposals (ECPs), Requests for Variance (RFVs), and Notices of Revision (NORs) for the requirements in the Government-provided Technical Data Package (TDP).

C.2.1 The Configuration Change Management section of SAE EIA-649-1 (current revision) Configuration Management Requirement for Defense

Contracts, Paragraph 3.3, shall be used for configuration control of material with the following exclusions: paragraph 3.3(3); and the second sentence of paragraph 3.3.1.8.1(1).

C.2.2 Furnished item(s) shall conform to the approved configuration requirements/revision unless an RFV is processed and approved as provided by Paragraph e. below. The term "Request for Variance" includes Requests for Deviations and Waivers.

c.2.3 Value Engineering Change Proposals (VECPs) for cost saving improvements to the TDP should not be processed per SAE EIA-649-1

(current revision) and should be referred to Section I Clause 52.248-1 VALUE ENGINEERING.

3 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.4 All ECPs submitted will be deemed routine. The Contractor must include justification for an ECP it considers emergency or urgent in the submittal and include all supporting documentation.

C.2.5 For ECPs, RFVs, and NORs, the Contractor must submit the documentation listed in sub-paragraphs e (i) through e (iii). Failure to submit a complete legible package may result in return of the ECP/RFV/NOR without processing.

C.2.5.1 for ECPs, the Contractor shall prepare and deliver the ECP in accordance with (IAW) CDRL A001.

C.2.5.2 for RFVs, the Contractor shall prepare and deliver the RFV IAW CDRL A002.

C.2.5.3 for NORs, the Contractor shall prepare and deliver the NOR IAW CDRL A003.

C.2.6 The Governments acceptance of the data deliverable required by CDRL/DD Form 1423 in e(i)-(iii) above signifies only that the data satisfies the requirements of the DID and is considered acceptable for Government processing. Acceptance of the data deliverable does not signify "technical approval" of the change proposed by the deliverable and should not be interpreted as authorizing the Contractor to proceed with the work proposed by the change. Disposition of the change (approval/disapproval) will follow acceptance of the CDRL at the Governments sole discretion. Incorporation of an approved RFV or ECP will require execution of a contract modification.

C.2.7 The Contractor should direct questions regarding the status of an ECP or RFV to the Procuring Contracting Officer (PCO), copy to the Administrative Contracting Officer (ACO).

C.2.8 The submission of an ECP/RFV/NOR does not affect the required delivery date of the contract.

C.3 REQUIREMENT FOR AN OPSEC STANDING OPERATION PROCEDURE/PLAN______________________________________________________________

C.3.1 The contractor is subject to provisions of the TACOM LCMC OPSEC Standing Operating Procedures (SOP/Plan), or other U.S. Government

OPSEC plan, per AR 530-1, Operations Security. This SOP/Plan specifies the governments critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it.

C.3.2 The contractor will receive a copy of the SOP/Plan at time of award. Local form STA Form 7114 (or similar) will be used to document and record security OPSEC reviews which are conducted by G2, TACOM LCMC or individual organizations supporting OPSEC Officers.

C.3.3 The contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual is

OPSEC Level I.

C.3.4 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 CUI or classified information) shall be required to follow an OPSEC Plan. The contractor may choose to follow the TACOM OPSEC plan in lieu of developing a new OPSEC plan. Personnel who have taken the approved OPSEC training within the last 12 months shall be considered compliant.

C.4 OPSEC TRAINING REQUIREMENT______________________________

Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of reporting for duty. All contractor employees must complete annual OPSEC awareness training. OPSEC awareness training is available at:

https://securityawareness.usalearning.gov/opsec/index.htm . The Contractor shall maintain the training certificates/proof of complettion and make them available to the Contracting Officer's Representative (COR) or Procuring Contracting Officer (PCO) upon request.

C.5 THREAT AWARENESS REPORTING PROGRAM______________________________________

C.5.1 All contractor employees with security clearances working on any Army contract must receive annual TARP training by a Counter

Intelligence (CI) agent, or other authorized designated training method, per Army Regulation 381-12, para. 2-4b, Threat Awareness and

Reporting Program (TARP). The in-person training is the preferred method, and is available by contacting the local CI Office to arrange for the conduct of training.

C.5.2 The Contractor shall contact the CI Office within (30) days of contract award to schedule TARP training. Once training is complete, the Contractor shall maintain the training certificates/proof of completion and make them avaiblable to the Contracting

Officer's Representative (COR) or Procuring Contracting Officer (PCO) upon request.

C.5.3 The Contractor shall contact the CI Office to schedule training for any new employee whose performance commences after award, and who did not attend the initial TARP training session. Upon completion of the TARP training, certification/proof of completion shall be provided as required in paragraph (b).In special circumstances (on deployments or in remote locations) when in-person training is not available, TARP computer based training (CBT), which has been approved by Deputy Chief of Staff (DCS), G-2, is the only authorized online training method permitted. This alternate CBT training is only authorized in special circumstances with written approval obtained

4 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

from the PCO. Upon receipt of the necessary written approval, contractor employees possessing an Army Knowledge Online (AKO) account and password or a Common Access Card can register and complete the online TARP training course by utilizing the Army Learning Management

System (ALMS) at: www.lms.army.mil .

C.6 ADDITIONAL GUIDELINES FOR CONTROLLED UNCLASSIFIED INFORMATION_________________________________________________________________

C.6.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 are U.S. Government technical information and information listed at the CUI registry

(https://www.archives.gov/cui/registry/category-list ). When handling CUI material, all personnel are to comply with these requirements and follow their company policy and/or applicable Non-Disclosure Agreement (NDA) concerning the protection of proprietary information in situations not clearly stated herein.

C.6.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 data 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.6.3 CUI Information Description: Unclassified Information that requires safeguarding or dissemination controls pursuant to and consistent with applicable law, regulations, and government-wide or LRGWP policies but is not classified under EO 13526, (Classified

National Security Information).

C.6.4 CUI Markings: All documents containing CUI will carry the CUI markings in accordance with DoDI 5200.48. Discontinue all use of legacy or other markings not permitted or included in either the CUI Registry or DoDI 5200.48. 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.6.5 Protection of CUI Information

C.5.5.1 Access: In accordance with (IAW) DoDI 5200.48, Controlled Unclassified Information (CUI), 6 MAR 2020, all contractors supporting this contract who receive, store, or generate CUI are required to take the DoD Mandatory CUI training available on the Security

Awareness Hub at : https://securityawareness.usalearning.gov/cui/index.html . Per DoDI 5200.48 and pursuant to all contractual requirements, DoD contractors require initial CUI training and annual CUI refresher training. 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. Further dissemination of such information will be at the discretion of the Government Security Manager. All personnel supporting this contract shall sign a CUI Non-disclosure Agreement prior to gaining access to the information. 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.6.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 in accordance with 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, tablets), nonportable 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, DFARS

252.204-7012 and DoDI 8582.01.

C.6.5.3 Dissemination: CUI printed documents and material may be transmitted through mail channels, commercial carrier or hand-carried without formal courier orders. CUI 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.6.5.3.1 All transmission and/or dissemination of CUI (i.e., email and file transfers) must use NIST/NIAP-approved cryptographic products/algorithms, e.g., DoD-approved Public Key Infrastructure Certification or DoD Safe Exchange at https://safe.apps.mil/ .

5 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.6.5.3.2 Contractor-hosted collaborative suites may be used for digital transmission and/or dissemination of CUI bypersonnel not located on a government backbone (e.g., NIPRNET), provided the following conditions apply: 1) Useonly 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 aninternally hosted service that does not use a third-party collaborative suite service provider.

C.6.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 aDoD 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.As new technologies become available in the electronics arena, care should be given to providing a reasonable degree of protection from known vulnerabilities.

C.6.5.3.4 The Internet is Public Access. CUI must be reviewed and officially approved by the TACOM Public AffairsOfficer for public release before placing on the Internet. This is not applicable when the Internet is used for e-mailtransmissions and encryption is used as noted above.

C.6.5.4 Disposal: 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 in accordance with (IAW) National Institute of Standards and Technology

(NIST) Special Publication (SP) 800-88, Revision 1: Guidelines for Media Sanitization (December 2014) (NIST SP 800-88, rev 1), destruction methods, or any destruction method approved for Classified National Security Information (32 CFR 2001.47) unless the CUI category's authority mandates other destruction methods (CUI Specified categories). Agencies must also use destruction methods specifically required by law, regulation, or Government-wide policy for CUI Specified categories. Destroy CUI documents in a manner that makes it unreadable, indecipherable, and irrecoverable (32 CFR 2002.14(f)(2)). For paper documents, Reference CUI Notice 2019-03:

Destroying of Controlled Unclassified Information (CUI) in paper form.

C.6.5.5 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. Initial report content shall include the following information as available.

C.6.5.5.1 Applicable dates, including dates of compromise and dates of discovery

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

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

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

*** END OF NARRATIVE C0001 ***

6 6