W56HZV20R0164-0005.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

0005 2023AUG04

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

ELISE C. WONG

EMAIL: ELISE.C.WONG.CIV@ARMY.MIL

W56HZV-20-R-0164

2023MAY31

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 14

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: ELISE C. WONG

Buyer Office Symbol/Telephone Number: CCTA-MFA-P/(571)588-8992

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

Solicitation: W56HZV-20-R-0164

Amendment: 0005

Prepared by: EW

1. The purpose of Amendment 0005 to Solicitation W56HZV-20-R-0164 is to:

a. Update language in Section L.2 to allow for transmittal of proposals that contain Controlled Unclassified Data (CUI).

b. Update language in Section L.5.6 to clarify CSDR Requirements.

2. As a result of this amendment, the following section has been changed:

a. SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

i. From:

L.2 UNCLASSIFIED Proposal Content, Format and Instructions

The offerors proposal shall be UNCLASSIFIED. The following instructions are for UNCLASSIFIED proposals only:

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 Past Performance Factor (Section L.4.1)

Volume 2 Price Factor (Section L.4.2)

Volume 3 Administrative (Section L.5.1)

L.2.1.2 A Proposal cover/transmittal letter is not required. If provided, it will neither be considered as part of the volumes required, nor will it be evaluated.

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

L.2.2.1 Method of Submission: The proposal shall be electronically submitted via E-mail to the Contract Specialist, Elise C. Wong and

Regina N. Ihns, and cc the Contracting Officer, Julianna R. Santi, at the following e-mail address(s) with the subject header:

Proposal Submission: W56HZV-20-R-0164

(company name):

Contract Specialist: elise.c.wong.civ@army.mil, regina.n.ihns.civ@army.mil

Contracting Officer: julianna.r.santi.civ@army.mil

L.2.2.1.1 Fax, hardcopy, and DVD/CD-ROM proposals will NOT be accepted. Hand-carried offers, whether hardcopy or electronic, will NOT be accepted. Other electronic submission methods (i.e., SAM.GOV or DoD SAFE) will NOT be accepted.

L.2.2.1.2 In accordance with FAR 15.208, it is the responsibility of the Offeror to ensure the proposal is received, in its entirety, at the required destination by the Due Date and Time for Receipt of Offers specified in the solicitation. 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.3 Maximum size of each e-mail shall be 20 megabytes. The offeror may use multiple e-mail messages for each submission, however, it shall 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.

2 14

W56HZV-20-R-0164

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.2.2 Proposal Format and Instructions

L.2.2.2.1 Each submitted File shall be labeled and named so it is identifiable for which volume it pertains (example: Vol2 - Price

Factor).

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

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

(MS) 365 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 information shall be contained within the electronic proposal. Any linked or referenced information that is not contained in the proposal will not be accepted.

L.2.2.2.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 inch 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.2.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 proposal being rejected (See Section M.2.1

(a)).

L.2.2.2.6 The offeror shall make every effort to ensure that the proposal is virus-free. Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as

"unreadable" as described in FAR 15.207(c).

L.2.2.3 Submission Due Date

The offeror must ensure its proposal, in its entirety, reaches the required destination before the Offeror Due Date and Time established in this solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors-Competitive Acquisition and are incorporated into this solicitation.

L.2.3 Single Proposal Submission

Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An offeror is defined as an entity competing independently that does not share a common parent with any other offeror or does not have a parent/subsidiary relationship with any other offeror or is not affiliated with any other offeror. For this section L.2.3 the Government will consider Affiliation to exist if associated business concerns or individuals, directly or indirectly, either controls the other or can control the other (control can exist through common ownership, common management, or a contractual relationship such as a joint venture, where members have the power to control performance of the contract); or a third-party controls or can control both.

L.2.4 Organizational Conflict of Interest

L.2.4.1 The provisions of FAR 9.5, Organizational Conflict of Interest (OCI), apply to any award under this Request For Proposal (RFP).

Potential offerors should review their current and planned participation in any other Government contracts or Government agreements

(which include OTAs, CRADAs, Public-Private Partnerships, etc.), subcontracts, consulting, or teaming arrangements where they may be in a position of actual or perceived bias or unfair competitive advantage.

L.2.4.2 Offerors should disclose any potential OCI situations to the Contracting Officer as soon as identified including prior to proposal submission. The disclosure should include the facts and an analysis of the actual or perceived conflict and a recommended approach(s) to neutralize or mitigate the potential conflict. The preferred approach to potential conflicts is to negate/obviate the conflict. Mitigation is considered only if it is not practical to negate/obviate the conflict. The Contracting Officer will promptly respond to resolve any potential conflicts.

L.2.5 Export Controlled Information

This solicitation contains Export Controlled information. It is the responsibility of the offeror, not the Government, to obtain access, and to obtain any appropriate export licenses, process appropriate export license exemption necessary for authorization to share any

3 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

such information with subcontractors who are foreign persons as defined in applicable export laws and regulations. The Government shall consider the failure or inability of an offeror to obtain access and, when applicable, obtain the appropriate export compliance documentation and provide that in its proposal as grounds for rejection IAW M.2. See Section A.5 DISTRIBUTION AND DESTRUCTION OF EXPORT

CONTROL TECHNICAL DATA PACKAGE for instructions on how to access Export Controlled information.

To:

L.2 UNCLASSIFIED Proposal Content, Format, and Instructions

The offerors proposal shall be UNCLASSIFIED. The following instructions are for UNCLASSIFIED proposals only:

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 Past Performance Factor (Section L.4.1)

Volume 2 Price Factor (Section L.4.2)

Volume 3 Administrative (Section L.5.1)

L.2.1.2 A Proposal cover/transmittal letter is not required. If provided, it will neither be considered as part of the volumes required, nor will it be evaluated.

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

L.2.2.1 Method of Submission: The offeror shall submit its proposal by one of the two methods according to the instructions below.

Method 1:

For UNCLASSIFIED proposals that do not contain Controlled Unclassified Information (CUI): The proposal shall be electronically submitted via E-mail to the Contract Specialist, Elise C. Wong and Regina N. Ihns, and cc the Contracting Officer, Julianna R. Santi, at the following e-mail address(s) with the subject header:

Proposal Submission: W56HZV-20-R-0164

(company name):

Contract Specialist: elise.c.wong.civ@army.mil, regina.n.ihns.civ@army.mil

Contracting Officer: julianna.r.santi.civ@army.mil

Method 2:

For UNCLASSIFIED proposals that contain CUI: The proposal shall be submitted via DoD SAFE. Use of DoD SAFE requires the offerors understanding and consent of DoD SAFEs user guidelines, rules of behavior, and all terms of use. Refer to DoD SAFE User Guide:

https://safe.apps.mil/help/dod-safe-help.xml#intro . It is the responsibility of the Offeror to ensure that its proposal submission Drop-Off is completed timely and is retrievable by the recipients listed below. DoD SAFE Drop-Offs proposal submissions that are not retrievable will not be considered. NOTE: Offerors who are DoD CAC authenticated users shall NOT initiate a DoD SAFE Drop-Off directly to the Government POCs below, all offerors must request the Government POCs below to initiate a Request for a Drop-Off, as instructed below, and respond in accordance with the DoD SAFE generated e-mail for a Drop-Off Request.

Step 1 (Offeror): Offerors shall email Elise Wong (email: elise.c.wong.civ@army.mil) and Julianna Santi (email:

julianna.r.santi.civ@army.mil) of their intent to submit a proposal and request the Government initiate a DoD SAFE Drop-Off Request.

NOTE 1: It is recommended that this request is submitted no sooner than 7 days and no later than 72 hours, prior to proposal due date and time. It is the offerors responsibility to request all necessary Drop-Off Requests from the Government to submit its proposal in a timely manner.

NOTE 2: Unless otherwise specified in the Offerors request, the Government will only initiate one Drop-Off Request. Refer to the DoD SAFE website for the file and size limits. It is the offerors responsibility to inform the Government of the number of Drop-Off

Requests it needs to submit its complete proposal.

NOTE 3: Unless otherwise specified in the request, the Government will use the requesters e-mail address to initiate the DoD

SAFE Drop-Off Request (See Step 2). The Government will input a single email address when initiating a Request For Drop-Off.

Step 2 (Government): The Government will initiate a Request For Drop-Off via the DoD SAFE website.

4 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Step 3 (Offeror): DoD SAFE will generate an email to the e-mail address input by the Government (See Step 1, NOTE 3). This e-mail will contain a link.

Step 4 (Offeror): The offeror shall utilize the link in the DoD SAFE generated e-mail. The Offeror shall ensure that the Drop-Off is sent to the following recipients: Contract Specialist: Elise Wong (email: elise.c.wong.civ@army.mil) and Contracting Officer Julianna

Santi (email: julianna.r.santi.civ@army.mil).

NOTE 4: The DoD SAFE Request for Drop-Off link will no longer be active after the Drop-Off File submission has occurred. The

Drop-Off link can only be used once.

NOTE 5: Please note that when submitting through DoD SAFE, files do not begin uploading until the Send Drop-Off has been initiated. It will take time for the files to be uploaded and scanned by DoD SAFE prior to the completion of the Drop-Off; File size, network connection, connection type, and number of files are factors in the total upload/download time of files, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for completion of the Drop-Off prior to the established due date and time of proposal submission. DoD SAFE does NOT guarantee a delivery time. DoD SAFE recommends allowing AT LEAST 4 hours for delivery.

NOTE 6: Offerors should not select any files for upload until it is prepared to complete the DropOff to the Government. DoD

SAFE is approved for CUI file exchange, but files must be encrypted. Follow the instructions in Section 3.5 of DoD SAFE User Guide for file encryption: https://safe.apps.mil/help/dod-safe-help.xml#encrypt-files . Send encryption passphrase to Contract Specialist:

Elise Wong (email: elise.c.wong.civ@army.mil) and Contracting Officer Julianna Santi (email: julianna.r.santi.civ@army.mil) in a separate e-mail. Failure to provide the encryption passphrase to the recipients may render the Dop-off unretrievable.

NOTE 7: It is highly recommended that the offeror prints the Drop-Off Completed screen, verify the correct files and recipients were included in its completed Drop-Off, and e-mail a copy to the required recipients listed above prior to the closing date and time of the RFP.

Step 5(Offeror): If the offeror needs to update its proposal submission prior to the RFP closing date and needs the Government to initiate a new DoD SAFE Drop-Off Request, it shall follow the same steps outlined above.

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

L.2.2.1.2 In accordance with FAR 15.208, it is the responsibility of the Offeror to ensure the proposal is received, in its entirety, at the required destination by the Due Date and Time for Receipt of Offers specified in the solicitation. There is no "expected" or

"target" length of time for proposal submission via email or DoD SAFE; File size, content, network connection, connection type, and number of files may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

L.2.2.1.3 Maximum size of each e-mail shall be 20 megabytes. The offeror may use multiple e-mail messages for each submission; however, it shall 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.

L.2.2.2 Proposal Format and Instructions

L.2.2.2.1 Each submitted File shall be labeled and named so it is identifiable for which volume it pertains (example: Vol2 Price

Factor).

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

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

(MS) 365 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 information shall be contained within the electronic proposal. Any linked or referenced information that is not contained in the proposal will not be accepted.

L.2.2.2.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-inch 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.2.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 proposal being rejected (See Section M.2.1

5 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(a)).

L.2.2.2.6 The offeror shall make every effort to ensure that the proposal is virus-free. Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as

"unreadable" as described in FAR 15.207(c).

L.2.2.3 Submission Due Date

The offeror must ensure its proposal, in its entirety, reaches the required destination before the Offeror Due Date and Time established in this solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors-Competitive Acquisition and are incorporated into this solicitation.

ii. From:

L.5.6 Cost and Software Data Reporting System. The provision 252.234-7003 is included in this RFP. However, the offeror is not required to submit the information outlined in 252.234-7003, sub paragraphs (b)(1)-(b)6) and (c) as part of it's proposal.

To:

L.5.6 Cost and Software Data Reporting System. DFARS 252.234-7003(b) requires Offerors to submit CSDR information as part of their proposal. Please note, although 252.234-7003(b)(6) calls for the submission of DD Forms 1921 and 1921-1, these are legacy formats and are no longer a reporting requirement for CSDRs. Offerors shall submit CSDRs as defined in the CAPE approved DD Form 2794.

3. All other terms and conditions of Solicitation W56HZV-20-R-0164 remain unchanged.

*** END OF NARRATIVE A0006 ***

6 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 General Proposal Information

Offerors are cautioned to consult the Contracting Officer IN WRITING before submitting an offer that proposes any deviations or exceptions to any of the requirements, terms, and conditions of the solicitation because it may be cause for rejection of the proposal

(See Section M.2).

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. Offerors should not assume data submitted for one Factor or Volume will be considered for the other Factors or Volumes of the proposal. However, the Government reserves the right to utilize this data in other areas of the evaluation at its sole discretion.

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 270 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 IAW M.2 Rejection of Offers.

*L.2 UNCLASSIFIED Proposal Content, Format, and Instructions

The offerors proposal shall be UNCLASSIFIED. The following instructions are for UNCLASSIFIED proposals only:

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 Past Performance Factor (Section L.4.1)

Volume 2 Price Factor (Section L.4.2)

Volume 3 Administrative (Section L.5.1)

L.2.1.2 A Proposal cover/transmittal letter is not required. If provided, it will neither be considered as part of the volumes required, nor will it be evaluated.

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

L.2.2.1 Method of Submission: The offeror shall submit its proposal by one of the two methods according to the instructions below.

Method 1:

For UNCLASSIFIED proposals that do not contain Controlled Unclassified Information (CUI): The proposal shall be electronically submitted via E-mail to the Contract Specialist, Elise C. Wong and Regina N. Ihns, and cc the Contracting Officer, Julianna R. Santi, at the following e-mail address(s) with the subject header:

Proposal Submission: W56HZV-20-R-0164 (company name):

7 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Contract Specialist: elise.c.wong.civ@army.mil, regina.n.ihns.civ@army.mil

Contracting Officer: julianna.r.santi.civ@army.mil

Method 2:

For UNCLASSIFIED proposals that contain CUI: The proposal shall be submitted via DoD SAFE. Use of DoD SAFE requires the offerors understanding and consent of DoD SAFEs user guidelines, rules of behavior, and all terms of use. Refer to DoD SAFE User Guide:

https://safe.apps.mil/help/dod-safe-help.xml#intro . It is the responsibility of the Offeror to ensure that its proposal submission

Drop-Off is completed timely and is retrievable by the recipients listed below. DoD SAFE Drop-Offs proposal submissions that are not retrievable will not be considered. NOTE: Offerors who are DoD CAC authenticated users shall NOT initiate a DoD SAFE Drop-Off directly to the Government POCs below, all offerors must request the Government POCs below to initiate a Request for a Drop-Off, as instructed below, and respond in accordance with the DoD SAFE generated e-mail for a Drop-Off Request.

Step 1 (Offeror): Offerors shall email Elise Wong (email: elise.c.wong.civ@army.mil) and Julianna Santi (email:

julianna.r.santi.civ@army.mil) of their intent to submit a proposal and request the Government initiate a DoD SAFE Drop-Off Request.

NOTE 1: It is recommended that this request is submitted no sooner than 7 days and no later than 72 hours, prior to proposal due date and time. It is the offerors responsibility to request all necessary Drop-Off Requests from the Government to submit its proposal in a timely manner.

NOTE 2: Unless otherwise specified in the Offerors request, the Government will only initiate one Drop-Off Request. Refer to the DoD SAFE website for the file and size limits. It is the offerors responsibility to inform the Government of the number of Drop-Off

Requests it needs to submit its complete proposal.

NOTE 3: Unless otherwise specified in the request, the Government will use the requesters e-mail address to initiate the DoD

SAFE Drop-Off Request (See Step 2). The Government will input a single email address when initiating a Request For Drop-Off.

Step 2 (Government): The Government will initiate a Request For Drop-Off via the DoD SAFE website.

Step 3 (Offeror): DoD SAFE will generate an email to the e-mail address input by the Government (See Step 1, NOTE 3). This e-mail will contain a link.

Step 4 (Offeror): The offeror shall utilize the link in the DoD SAFE generated e-mail. The Offeror shall ensure that the Drop-Off is sent to the following recipients: Contract Specialist: Elise Wong (email: elise.c.wong.civ@army.mil) and Contracting Officer Julianna

Santi (email: julianna.r.santi.civ@army.mil).

NOTE 4: The DoD SAFE Request for Drop-Off link will no longer be active after the Drop-Off File submission has occurred. The

Drop-Off link can only be used once.

NOTE 5: Please note that when submitting through DoD SAFE, files do not begin uploading until the Send Drop-Off has been initiated. It will take time for the files to be uploaded and scanned by DoD SAFE prior to the completion of the Drop-Off; File size, network connection, connection type, and number of files are factors in the total upload/download time of files, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for completion of the Drop-Off prior to the established due date and time of proposal submission. DoD SAFE does NOT guarantee a delivery time. DoD SAFE recommends allowing AT LEAST 4 hours for delivery.

NOTE 6: Offerors should not select any files for upload until it is prepared to complete the DropOff to the Government. DoD

SAFE is approved for CUI file exchange, but files must be encrypted. Follow the instructions in Section 3.5 of DoD SAFE User Guide for file encryption: https://safe.apps.mil/help/dod-safe-help.xml#encrypt-files . Send encryption passphrase to Contract Specialist:

Elise Wong (email: elise.c.wong.civ@army.mil) and Contracting Officer Julianna Santi (email: julianna.r.santi.civ@army.mil) in a separate e-mail. Failure to provide the encryption passphrase to the recipients may render the Dop-off unretrievable.

NOTE 7: It is highly recommended that the offeror prints the Drop-Off Completed screen, verify the correct files and recipients were included in its completed Drop-Off, and e-mail a copy to the required recipients listed above prior to the closing date and time of the RFP.

Step 5(Offeror): If the offeror needs to update its proposal submission prior to the RFP closing date and needs the Government to initiate a new DoD SAFE Drop-Off Request, it shall follow the same steps outlined above.

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

L.2.2.1.2 In accordance with FAR 15.208, it is the responsibility of the Offeror to ensure the proposal is received, in its entirety, at the required destination by the Due Date and Time for Receipt of Offers specified in the solicitation. There is no "expected" or

"target" length of time for proposal submission via email or DoD SAFE; File size, content, network connection, connection type, and

8 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

number of files may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

L.2.2.1.3 Maximum size of each e-mail shall be 20 megabytes. The offeror may use multiple e-mail messages for each submission; however, it shall 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.

L.2.2.2 Proposal Format and Instructions

L.2.2.2.1 Each submitted File shall be labeled and named so it is identifiable for which volume it pertains (example: Vol2 Price

Factor).

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

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

(MS) 365 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 information shall be contained within the electronic proposal. Any linked or referenced information that is not contained in the proposal will not be accepted.

L.2.2.2.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-inch 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.2.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 proposal being rejected (See Section M.2.1

(a)).

L.2.2.2.6 The offeror shall make every effort to ensure that the proposal is virus-free. Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as

"unreadable" as described in FAR 15.207(c).

L.2.2.3 Submission Due Date

The offeror must ensure its proposal, in its entirety, reaches the required destination before the Offeror Due Date and Time established in this solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors-Competitive Acquisition and are incorporated into this solicitation.

3. All other terms and conditions of Solicitation W56HZV-20-R-0164 remain unchanged.

L.2.3 Single Proposal Submission

Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An offeror is defined as an entity competing independently that does not share a common parent with any other offeror or does not have a parent/subsidiary relationship with any other offeror or is not affiliated with any other offeror. For this section L.2.3 the Government will consider Affiliation to exist if associated business concerns or individuals, directly or indirectly, either controls the other or can control the other (control can exist through common ownership, common management, or a contractual relationship such as a joint venture, where members have the power to control performance of the contract); or a third-party controls or can control both.

L.2.4 Organizational Conflict of Interest

L.2.4.1 The provisions of FAR 9.5, Organizational Conflict of Interest (OCI), apply to any award under this Request For Proposal (RFP).

Potential offerors should review their current and planned participation in any other Government contracts or Government agreements

(which include OTAs, CRADAs, Public-Private Partnerships, etc.), subcontracts, consulting, or teaming arrangements where they may be in a position of actual or perceived bias or unfair competitive advantage.

L.2.4.2 Offerors should disclose any potential OCI situations to the Contracting Officer as soon as identified including prior to

9 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

proposal submission. The disclosure should include the facts and an analysis of the actual or perceived conflict and a recommended approach(s) to neutralize or mitigate the potential conflict. The preferred approach to potential conflicts is to negate/obviate the conflict. Mitigation is considered only if it is not practical to negate/obviate the conflict. The Contracting Officer will promptly respond to resolve any potential conflicts.

L.2.5 Export Controlled Information

This solicitation contains Export Controlled information. It is the responsibility of the offeror, not the Government, to obtain access, and to obtain any appropriate export licenses, process appropriate export license exemption necessary for authorization to share any such information with subcontractors who are foreign persons as defined in applicable export laws and regulations. The Government shall consider the failure or inability of an offeror to obtain access and, when applicable, obtain the appropriate export compliance documentation and provide that in its proposal as grounds for rejection IAW M.2. See Section A.5 DISTRIBUTION AND DESTRUCTION OF EXPORT

CONTROL TECHNICAL DATA PACKAGE for instructions on how to access Export Controlled information.

L.3 All or None

Offers in response to this solicitation must be submitted for all the requirements identified in the solicitation. Offers submitted for less than all the requirements called for by this solicitation may be rejected or ineligible for award. Proposals that contain alternative terms and conditions may be considered as taking exception to the requirements of the solicitation. See Section M.2.

L.4 Evaluation Factors

Offeror proposals shall address the following Factors:

a. Past Performance Factor

b. Price Factor

L.4.1 Volume 1 Past Performance Factor

For the Past Performance Factor, the offeror is limited to proposing a total of up to two submissions of a Recent Contract(s) the offeror considers to have relevance to the RFP requirements in Section L.4.1.2 below. The contract must have been performed by the offeror or performed by an entity allowed by Section L.4.1.4 below, as the prime contractor. Contracts may include foreign, federal, state, local and private industry contracts. A prime contractor is the party that executes an agreement with another party to perform work. For example, if youre a subcontractor on a Government contract, you can provide the private industry contract that you have with the firm who signed the contract with the Government to demonstrate past performance as a prime contractor. The Government will not consider the past performance of individuals, key personnel, or subcontractors; only corporate past performance will be considered.

For the purpose of this Factor, a Contract is defined as a written instrument that requires the performance of a distinct effort and demonstrates the distinct effort was actually performed. Written instruments containing supplies or services that can be ordered but typically do not demonstrate actual performance, such as Indefinite Delivery Contracts (FAR 16.5), Basic Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS) do not meet the definition of a Contract. Written instruments considered to demonstrate actual performance may include a single task or delivery order, a single work directive, or a single definite quantity contract provided it demonstrates a distinct effort was actually performed. If a contract instrument executed under a broad ordering instrument (such as a task or delivery order, etc) also functions as a broad ordering instrument and does not require or demonstrate that a distinct effort be performed (i.e requires other written instruments to execute performance), then this contract instrument would NOT meet the definition of a Contract. An offeror may submit, or the Government may require, written instruments that enhance the Governments understanding of the distinct effort actually performed if it is not identified on the Contract itself. It is incumbent upon the offeror to demonstrate that a distinct effort was actually performed.

The burden of providing thorough and complete past performance information remains with the offeror. It is the offeror's responsibility to submit detailed and complete information so the Government may evaluate its Past Performance volume. The Government does not assume the duty to search for data to cure problems it finds in proposals. While the Government may elect to consider data obtained from internal and external sources other than the proposal, the burden to provide thorough and complete past performance information rests with the offeror. The below instructions are provided to advise offerors as to the information required by the Government to assess the contractors Recent and Relevant past performance. Since this information constitutes a basis of the Government's review, it is imperative that the offeror present its past performance in a clear and complete manner. Failure to provide the information requested under paragraph L.4.1.3 and L.4.1.4 (if applicable) below may result in an assessment that the offeror does not possess a record of

Recent and Relevant past performance.

Page Recommendation: It is recommended that the offeror submit no more than 10 pages total in response to the written narrative(s) required in Section L.4.1.3 and L.4.1.4. This page recommendation excludes i) any substantiating documents submitted in response to

Section L.4.1.3 and L.4.1.4 (Copies of requested Contract information, other requested substantiating documents in response to Sections

L.4.1.4.1 through L.4.1.4.4 when applicable), and ii) a cover page and table of contents.

L.4.1.1 Recent Contracts are those performed within 3 years of the date of issuance of this RFP.

10 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.1.2 Relevant Contracts are those that are:

a) Comparable in scope and complexity to the following RFP requirements: Manufacturing and assembling armor protection kits in

Accordance With (IAW) a Technical Data Package

(TDP) for use on a military ground vehicle; and

b) Comparable in scope and magnitude of effort and complexity to the following RFP requirements: Manufacturing and assembling of add-on armor protection kits In Accordance With (IAW) a Technical Data Package (TDP) for use on a military ground vehicle at a rate of 20 protection kits per month;

L.4.1.3 Contract Information: Refer to the definition of a Contract above (See paragraph L.4.1). The offerors proposal shall substantiate what distinct effort was required and actually performed under each of the proposed contract submission(s). Clearly identify/number each proposed contract submission and provide the following information:

(a) Prime Contractor name and address. Provide a copy of the executed contract submissions s cover sheet(s) and/or other sections of the contract submission that identifies the entities/parties and the execution date if not identified on the cover sheet;

(b) Contract Number (and delivery/task order number if applicable);

NOTE: Only propose a single Order (i.e task/delivery order, work directive, technical instruction) for a contract submission if the effort is part of broader contractual instrument such as an Indefinite Delivery, BOA, BPA, FSS. See paragraph L.4.1 for definition of a

Contract.

(c) Contract Type;

(d) Total Value of the Contract (beginning & ending value);

(e) Contract period of performance. Provide a copy of the contract submissions period of performance, and any copies of any other information necessary to substantiate recency (which may include copies of executed modifications to extend the contract submissions period of performance, exercise of an option/option period(s), etc);

(f) Delivery Rate and Delivery Schedule. Provide a copy of the section(s) of the contract submissions delivery rate and delivery schedule requirements ;

(g) Government or private industry contracting activity address, telephone number and e-mail;

(h) Procuring Contracting Officers (PCO) and/or Contract Specialists name, or point of contact for private industry entity responsible for signing or administering the Contract, telephone number and email;

(i) Government (DCMA) or private industry administrative contracting officer (ACO), contracting officers representative (COR), performance certifier, and/or quality assurance representative (QAR), name, telephone number and email;

(j) Specify the Government or private industry Point(s) of Contact for which the Questionnaire was sent,and provide the date(s) it was sent;

(k) The offeror shall provide a written narrative that shall be specific only to the work performed on the proposed contract submission and its relevancy to one or more RFP requirements listed in Section L.4.1.2. Do not provide a discussion of comparability of all past Contract requirements to all current RFP requirements, only discuss what is comparable and related to the RFP requirements identified in Section L.4.1.2. In the written narrative, shall clearly describe/identify the relevant contract deliverable, whether or not the deliverable is considered to be an add-on armor protection kit, what TDP the deliverable conforms to, what military ground vehicle the deliverables end use is intended for. In order to be considered for any additional evaluation credit per M.4.1.1.1, the offeror must provide what specification or standards any aluminum or steel welding the armor protection kits had to conform to. When citing specific work performed on the proposed Contract submission, provide references to the specific locations within the scope or other substantiating documents, such as paragraph or page number, when possible. When applicable, in its description, the offeror should specify the location in the proposal (to include filename or document reference with page and paragraph of the past contract information) that further substantiates relevancy if stand-alone attachments are submitted in this volume;

(l) Provide a brief self-assessment of Contract performance. The self-assessment must address performance to meet Technical and

Schedule requirements;

(m) A copy of the executed contractual instrument cover sheet(s) and/or other sections of the Contract that identifies the entities/parties of the proposed Contract and the execution date if not identified on the cover sheet;

(n) Copy of the complete Performance Work Statement or Scope of Work for each of the submitted Contracts. If the proposed Contract was issued under or in connection with a related written instrument (e.g. Indefinite Delivery Contracts, BOA, BPA, FSS) and the details of

11 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

the distinct effort actually performed needed to establish relevancy on the proposed Contract are further defined within the terms and conditions (e.g. statement of work) of that related written instrument, provide that information and any other information necessary to establish this instruments relationship to the proposed Contract. (These documents can be submitted as stand-alone attachments within the proposal volume).

L.4.1.4 Associated Entity, Predecessor Company, Joint Venture, and Other Transaction Authority (OTA) Consortia Member. As stated above

(L.4.1), only Contracts performed by the named offeror will be considered, unless it was performed by an entity allowed by this Section

L.4.1.4 as explained below.

L.4.1.4.1 Associated Entity. The Government may consider the past performance of an associated entity if the offeror successfully demonstrates the associated entity will perform significant and critical aspects of the contract if awarded.

a) An associated entity may include a parent company, sister company, separate corporate division within the same parent company, subsidiary company, an individual member of a previously established Joint Venture, a legally affiliated company, etc. The offeror shall provide to the Government a narrative that explains the offeror's relationship to the associated entity. The offeror shall support the narrative with legal documentation, including but not limited to corporate papers and/or copy of previously established Joint Venture

Agreement, establishing the legal nexus between the offeror and the associated entity.

b) The offeror shall provide to the Government a copy of a written agreement between the associated entity and the prime offeror describing what the associated entity will provide and/or be responsible for, and a written narrative that explains the significant and critical aspects the associated entity will provide to the proposed effort - i.e. the work to be performed by the associated entity.

This may include a description of the associated entity's resources, such as its workforce, facilities, and/or other resources that will be provided or relied upon in the proposed effort. A Contract will not be considered unless the offeror successfully establishes that significant and critical aspects of the contract, if awarded, will be performed by the associated entity.

L.4.1.4.2 Predecessor Company. The Government may consider the past…