W56HZV-20-R-0101 Amendment 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 2021AUG04

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

CHARDAE L. WALTON

EMAIL: CHARDAE.L.WALTON.CIV@MAIL.MIL

W56HZV-20-R-0101

2021MAY21

X

X 2021AUG17 01:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 9

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: CHARDAE L. WALTON

Buyer Office Symbol/Telephone Number: CCTA-HDT-E/(586)282-5366

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

1. The purpose of Amendment 0005 to Solicitation W56HZV-20-R-0101 is as follows:

A. The date specified for receipt of offers in block 9 of SF 33 Cover page is extended from August 06, 2021 to August 17, 2021.

B. Section L.2.2.1 Method of Submission Step 1 is revised

From: Offerors shall email Elena Hunt(email:elena.hunt.civ@mail.mil) of their intent to submit a proposal and request the

Government initiate a DoD SAFE Drop-Off Request.

To: Offerors shall email Chardae Walton(email:chardae.l.walton.civ@mail.mil) of their intent to submit a proposal and request the

Government initiate a DoD SAFE Drop-Off Request.

C. Section L.2.2.1 Method of Submission Step 4 NOTE 7 is revised

From: It is highly recommended that the offeror print the Drop Off Completed screen and email a copy to Elena

Hunt(email:elena.hunt.civ@mail.mil)

To: It is highly recommended that the offeror print the Drop Off Completed screen and email a copy to Chardae

Walton(email:chardae.l.walton.civ@mail.mil)

D. Section L.4.1.3 Category B - Logistics Management Task B1 is revised

From: Fleet management support of US Army ground vehicles (manned or unmanned); or

To: Fleet management support of US Army ground vehicles (manned or unmanned) Fleet management encompasses scheduling and capturing data of fleet management events, or the actual conduct of fleet management events. Fleet management events include engineering change proposal (ECP) or modernization upgrades, maintenance, fielding, and vehicle tracking; or

E. Section L.4.1.3 Category B - Logistics Management Task B3 is revised

From: Supply chain management of US Army ground vehicles (manned or unmanned)

To: Supply chain management of US Army ground vehicles (manned or unmanned); Supply chain management is the handling of the entire production flow of a good or service starting from the raw components all the way to delivering the final end product.

F. Contract Data Requirement List DATA ITEM NO.: A001 Block 14 is revised

From:The Contractor shall electronically deliver one final, reproducible copy to the following person(s):

Dawn VanHulle, Contracting Officer, <dawn.m.vanhulle.civ@mail.mil>

Elena Hunt, Contract Specialist, <elena.hunt.civ@mail.mil>

To: The Contractor shall electronically deliver one final, reproducible copy to the following person(s):

Dawn VanHulle, Contracting Officer, <dawn.m.vanhulle.civ@mail.mil>

Chardae Walton, Contract Specialist, <chardae.l.walton.civ@mail.mil>

2. All terms and conditions of this solicitation remain unchanged and in full force and effect.

*** END OF NARRATIVE A0005 ***

2 9

W56HZV-20-R-0101

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Exhibit A CONTRACT DATA REQUIREMENTS LIST (CDRL) 30-MAR-2021 001 DATA

3 9

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 (c) 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 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. 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 240 calendar days.

L.1.2.2. The offeror shall clearly state in its proposal Terms and Conditions 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). Proposals not in English (American Standard) 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 submitted in separate volumes as set forth below. The offerors proposal shall consist of the following volumes:

Volume

Number Title______ _____

Volume 1 Technical Experience Factor

Volume 2 Small Business Participation Factor

Volume 3 Terms and Conditions

L.2.1.2 A Proposal Executive Summary or transmittal letter is optional. It will neither be considered as part of the volumes required, nor will it be evaluated. If a Proposal Executive Summary is submitted, it should be no more than five pages in length and be submitted as part of the Terms and Conditions volume.

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

L.2.2.1 Method of Submission:

Electronic proposals submitted via E-mail or Fax, and hardcopy proposals will NOT be accepted. Hand-carried offers, whether hardcopy or electronic, will NOT be accepted. Offerors are required to submit proposals electronically, via DoD Secure Access File Exchange (SAFE) in accordance with the following Proposal Submission Instructions and Process. Use of DoD SAFE requires the offerors understanding and consent of DoD SAFEs user behavior guidelines and all terms of use. Offerors with CAC cards shall NOT initiate a DoD SAFE Drop-off directly to the Government POC below, all offerors must request the Government POC below initiate a Request for a Drop-Off, and respond in accordance with the DoD SAFE generated e-mail for a Drop-Off Request.

NOTE: 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, in accordance with the Instructions below. It is the offerors responsibility to request all necessary Drop-Off Requests from the Government in order to submit its proposal in a timely manner.

4 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Proposal Submission Instructions and Process:

Step 1 (Offeror): Offerors shall email Chardae Walton(email:chardae.l.walton.civ@mail.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 14 days (Drop Off Requests are only valid for 14 days), and no later than 72 hours, prior to proposal due date and time.

NOTE 2: Unless otherwise specified in its request, the Government will only initiate one Drop-Off Request. The current file limit for

Drop Off is 25 files. If the offeror intends to submit more than 25 files, 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 senders 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 inputted by the Government (See Step 1, NOTE 3). This e-mail will contain a link.

Step 4 (Offeror): The offeror utilizes the link in the DoD SAFE generated e-mail, and submits its proposal by uploading its proposal files and clicking Drop-off File. Proposal submission does not occur until the Drop-off File occurs.

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

NOTE 5: Please note that when submitting through DoD SAFE, it will take time to upload the proposal submission; size and content may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for upload.

NOTE 6: Offerors should not upload any files until it is prepared to submit its DropOff to the Government.

NOTE 7: It is highly recommended that the offeror print the Drop Off

Completed screen and email a copy to Chardae

Walton(email:chardae.l.walton.civ@mail.mil)

Step 5(Offeror): If the offeror needs to update its 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.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 for example: Volume 2, Small

Business Participation Factor)

L.2.2.2.2 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.

L.2.2.2.3 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.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 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.

5 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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 Due Date and Time for Receipt of

Offers specified in the solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 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 solicitation 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, 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 shall 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.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. Technical Experience

b. Small Business Participation

L.4.1 Volume 1 Technical Experience Factor Proposal____________________________________________________

A 15 page limit applies to part of this Volume submission. The page limit only applies to the written narrative(s) required in L.4.1.4.

Any substantiating documents submitted in response to Section L.4.1.4 will not be counted in this page limit (Contract cover sheet, PWS, other substantiating documents in response to L.4.1.4.1.1, L.4.1.4.2.1, or L.4.1.4.3.1, etc).

General Information: The below instructions are provided to advise offerors as to the information required by the Government to assess the contractors proposed experience. Since this information constitutes a basis of the Government's review, it is the offeror's responsibility to submit detailed and complete information as required so the Government may evaluate its Technical Experience volume, and it is imperative that the offeror present its experience in a clear and complete manner. Failure to provide the applicable

6 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

information may result in an assessment that the referenced experience lacks comparability or recency, and be discounted in the evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals. The burden of providing thorough and complete information remains with the offeror.

L.4.1.1 For the Technical Experience Factor, the offeror shall substantiate recent and comparable experience by providing the requested information below. The offeror may provide up to one recent Contract. The Contract must have been performed by the offeror as the prime contractor. In this context, 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 contract that you have with the Governments prime to demonstrate experience as a prime contractor for the company that is a prime contractor for the Government. A Contract may include foreign, federal, state, local and private industry Contracts. The Government will not consider the experience of individuals, key personnel, or subcontractors; only corporate experience will be considered.

NOTE: Submission of a Contract that requires issuance of a separate contractual ordering instrument to execute work, such as Indefinite

Delivery Contracts (FAR 16.5), Basic Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS)) will not be considered to demonstrate experience without also submitting the relevant contractual ordering instrument(s) to substantiate what executed work was performed.

L.4.1.2 The Government will only consider recent experience limited to (up to) one Recent Contract. Recent experience is defined as work completed on a Contract, or (if applicable) an executed contractual ordering instrument under the Contract, that is determined to be recent. Recent Contract(s) are those performed within three years of the date of issuance of this Request for Proposal (RFP). If a

Contract involved issuance of a contractual ordering instrument to execute work (such as Indefinite Delivery Contracts (FAR 16.5), Basic

Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS)), offerors must also submit an associated ordering instrument(s) that is recent and comparable to the proposed Task outlined in the criteria below, and then only the contractual ordering instruments period of performance (such as a single task or delivery order, a single work directive/technical instruction, etc) will be evaluated to determine recency. Any stand-alone Contract that does not involve issuance of a contractual ordering instrument to execute work), or any Contracts associated ordering instrument (single task or delivery order, etc.), that is determined to not be recent will not be considered in the evaluation.

L.4.1.3 Offeror must propose to one experience Task, which can be from any Category. The offeror is limited to propose to only one experience task. If more than one task is proposed or more than one contract is provided, the offerors proposal may be rejected in accordance with M.2.1(a). Proposed recent experience will be assessed for comparability in scope and complexity against the Task to which the offeror proposes:

Category A - Product Assurance and Test Services

Task A1 - Government support contract that provided on-site test support to US Army ground vehicles (manned or unmanned); or

Task A2 - Government support contract that provided product assurance on US Army ground vehicles (manned or unmanned) production lines

Category B - Logistics Management

Task B1- Fleet management support of US Army ground vehicles (manned or unmanned) Fleet management encompasses scheduling and capturing data of fleet management events, or the actual conduct of fleet management events. Fleet management events include engineering change proposal (ECP) or modernization upgrades, maintenance, fielding, and vehicle tracking; or

Task B2 - Publications and software support of US Army ground vehicles (manned or unmanned); or

Task B3 - Supply chain management of US Army ground vehicles (manned or unmanned); Supply chain management is the handling of the entire production flow of a good or service starting from the raw components all the way to delivering the final end product.

Category C - Industrial Base Operations

Task C1 - Operation and management of supply support to include receiving, inventory/storage management, and shipping for US Army's operations; or

Task C2 - RESET of US Army ground vehicles (manned or unmanned; or

Task C3 - Engineering support for a production line of US Army ground vehicles (manned or unmanned)

L.4.1.4 Experience Proposal Information Requested

L.4.1.4.1 Associated Corporate Entities. The Government may consider the experience of an associated entity if the offeror successfully

7 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

demonstrates meaningful involvement by the associated entity in the proposed effort.

L.4.1.4.1.1 An associated entity may include a parent company, separate corporate division within the same parent company, subsidiary company, a legally affiliated company, etc. The offeror shall provide to the Government a narrative that explains the offerors relationship to the associated entity. The offeror shall support the narrative with legal documentation, including but not limited to corporate papers, establishing the legal nexus between the offeror and the associated entity.

L.4.1.4.1.2 The offeror shall provide to the Government a narrative that explains the meaningful involvement the associated entity will provide to the proposed effort. Evidence of meaningful involvement may include a description of the associated entitys 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 meaningful involvement by the associated entity in the proposed effort.

L.4.1.4.2 Predecessor Companies. The Government may consider the experience of a predecessor company if the offeror demonstrates the experience of the predecessor company is reasonably predictive of the offerors performance under the proposed effort.

L.4.1.4.2.1 A predecessor company may include a company which was acquired by the offeror or merged with the offeror. It may also include other instances where the predecessor company was reorganized, restructured, or otherwise altered. A predecessor company does not include an entity which remains separate and distinct from the offeror. The offeror shall provide to the Government a narrative that explains the offerors relationship to the predecessor company. The offeror shall support the narrative with documentation evidencing the offerors status as the successor company.

L.4.1.4.2.2 Offeror shall provide to the Government a narrative that explains why the predecessors experience is predictive of the offerors performance under the proposed effort. Evidence may include, but is not limited to, continuity of operations such as the continued employment of the predecessors employees and the transfer of assets including buildings, furnishings, and fixtures.

L.4.1.4.3 Individual Partners of a Joint Venture. If the offeror is a Joint Venture, the Government may consider the experience of each partner of the Joint Venture and any work performed by the Joint Venture itself previously. The offeror must successfully demonstrate meaningful involvement by the partner to the proposed effort.

L.4.1.4.3.1 Offeror shall provide to the Government a narrative that discloses the individual partners of the Joint Venture and shall provide documentation evidencing the Joint Venture.

L.4.1.4.3.2 Offeror shall provide to the Government a narrative that explains the meaningful involvement the Joint Venture partner will provide to the proposed effort. Evidence of meaningful involvement may include a description of the partners 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 meaningful involvement by the partner in the proposed effort.

L.4.1.4.4 Contract Information: Offerors proposal shall substantiate what executed work was performed under the proposed contract. For the submitted Contract, provide the following information:

(a) Prime Contractor Name and Address;

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

(c) Period of performance (Provide ordering instrument(s) period(s) of performance, if applicable);

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

(e) A copy of the executed contract cover sheet and/or other content that identifies the entities/parties of the Contract and the execution date;

NOTE: If the proposed Contract is an Indefinite Delivery Contracts, BOA, BPA, FSS type contract, then the executed contract cover sheet of the ordering instrument (i.e task/delivery order, work directive, technical instruction) must also be submitted.

(f) A copy of the complete Performance Work Statement (PWS) or Scope of Work (SOW).

NOTE: If the proposed Contract requires separate ordering instruments to execute tasks(e.g. Indefinite Delivery Contracts, BOA, BPA, FSS type contracts) then the PWS or SOW of the ordering instrument (i.e task/delivery order, work directive, technical instruction) must also be submitted to demonstrate executed work.

(g) The offeror shall provide a written narrative that details the executed work performed on the submitted Contract and its comparability to a proposed Task listed in Section L.4.1.3. Note: Do not provide a breakdown of comparability of the entire SOW/PWS of the current RFP to the submitted Contract , or (if applicable) the entire SOW/PWS of associated ordering instrument. Only discuss the comparability the executed work performed to the proposed Task in L.4.1.3. When citing specific work performed on the submitted

Contract or its associated ordering instrument, 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 comparability if stand-alone attachments are submitted in this volume.

(h) An offeror may submit additional information, such as related contractual instruments that enhance the Governments understanding of the tasks performed if it is not identified on the Contract itself. It is incumbent upon the offeror to substantiate what tasks were actually performed.

L.4.1.4.5 A 15 page limit applies to part of this Volume submission. The page limit only applies to the written narrative(s) required in L.4.1.4. Any substantiating documents submitted in response to Section L.4.1.4 will not be counted in this page limit (Contract cover

8 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

sheet, PWS, other substantiating documents in response to L.4.1.4.1.1, L.4.1.4.2.1, or L.4.1.4.3.1, etc).

L.4.2 Volume 2: Small Business Participation____________________________________________

L.4.2.1 All Offerors (Large and Small Businesses) shall submit Attachment 001 which identifies a list of one or more small business concern(s)(which includes the subcategories of Small Disadvantaged Business, Women-Owned SB, HUBZone SB, Veteran-Owned SB and Service-

Disabled Veteran-Owned SB) that it commits to providing, to the maximum extent practicable, opportunities for performance under this contract. SB Offerors may meet this requirement using work they perform themselves.

L.4.2.1.1 Attachment 001 Instructions

CAGE Code: Fill out the Contractor and Government Entity (CAGE) Code from the proposed small businesses record in the System for Award

Management (SAM). If the proposed small businesses is not in SAM, insert None and see L.4.2.2. below.

NAICS Code: Assign the North American Industrial Classification System (NAICS) Code that best fits the work the proposed small businesses will potentially perform. SBA size standards and corresponding NAICS codes are provided here:

https://www.sba.gov/document/support--table-size-standards

Socioeconomic Categories: List any Small Business subcategories (Small Disadvantaged Business, Women-Owned SB, HUBZone SB, Veteran-Owned

SB and Service- Disabled Veteran-Owned SB) applicable to the proposed small business.

L.4.2.2 Subcontractor Registration or Certification. Pursuant to FAR Clauses 52.219-8 and 52.219-9 in this solicitation, the Offeror may not require subcontractors to be registered in SAM. For any potential small business subcontractor listed in Attachment 001 that is not registered in SAM, the Offeror shall provide in accordance with 13 CFR 121.411(g), a Small Business Certification Form (Attachment

0002) from that potential subcontractor verifying its small business size and socioeconomic status. This certification shall contain, on the same page as the size and status claimed, the signature of the official authorized to sign for that firm.

L.5 Volume 3: Terms and Conditions__________________________________

In addition to the proposal evaluation factor volumes above, provide the following information:

L.5.1 Signature Actions/offeror Fill-Ins. Provide a scanned image of a signed copy of the SF33 cover page, a copy of all completed fillins for Sections A through K, and (if applicable) a signed copy of all Amendments to the solicitation. Do Not Fill in Section B of the RFP, as proposed Cost/Price is not being requested or evaluated for this RFP (See Sec A.4.3). System for Award Management (SAM) certifications need not be separately submitted; however, all offerors must be successfully registered and valid in SAM prior to award.

L.5.1.1 Where certifications and approved systems are required for an offeror, if the proposal is being submitted by a Joint Venture, certifications and approved systems for the principals (partners) of the joint venture will be considered as valid for that offeror providing the necessary documentation from all principals (partners) is provided with the proposal.

L.5.1.2 Joint Venture (JV): To be recognized as a JV and eligible for award, the membership arrangements of the JV must be identified and the company relationships fully disclosed in the offeror's proposal IAW FAR 9.603. A copy of the agreement establishing the JV must contain the signatures of all of the members comprising the JV.

L.5.2 Offerors proposal acceptance period in terms of calendar days from the date for receipt of offers specified in the RFP. (See

Section L.1.2)

L.5.3 Statement of Acknowledgement. A statement specifying the extent of agreement with all terms, conditions, and provisions of the

RFP. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be grounds for the Government to reject the proposal from further consideration for award (Reference M.2.1).

L.5.4 Assumptions. The offeror shall consolidate and identify all offeror's generated "assumptions" contained anywhere in the proposal.

The offeror shall include a statement that none of the "assumptions" contradict or take exception to any terms, conditions, or requirements of the solicitation. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be grounds for the Government to reject the proposal from further consideration for award (Reference

M.2.1).

L.5.5 Cost Accounting System. In order to be considered for award, the offeror must provide evidence that it has adequate financial management and fund tracking procedures to accommodate a cost-reimbursement type contract at the time of proposal submittal. This evidence may include a letter from either DCMA or DCAA that states that the offeror has an adequate accounting system.

*** END OF NARRATIVE L0001 ***

9 9

PIIN/SIIN

MOD/AMD

ATT/EXH ID

PAGE

Exhibit A

DATA DELIVERABLE REQUIREMENT TO SATISFY MINIMUM QUANTITY

A.1 Exhibit A to solicitation W56HZV-20-R-0101 serves as notice that the requirement described herein will be awarded against the

Equipment Related Services (ERS) contract suite as the first task order (TO). This requirement will serve as the minimum quantity of services the Government will acquire under the ERS MA IDIQ contracts in accordance with (IAW) Federal Acquisition Regulation (FAR)

16.504(a)(4)(ii) and paragraph A.2.1.

A.2 This requirement is comprised of two semi-annual reports for the first ordering period (date of award through 365 days after award).

The Government is under no further obligation to place any additional orders against the ERS contract suite.

A.3 The Government intends to award this requirement on a Firm-Fixed-Price (FFP) basis, IAW paragraphs B.2 and B.3 below, in the total amount of $1,200.

A.4 The award of this requirement is anticipated to be concurrent with the award of the ERS MA IDIQ contracts under W56HZV-20-R-0101.

SUPPLIES OR SERVICES AND PRICE/COSTS

B.1 CLIN: 0001 - Semi-Annual Reports (First Ordering Period)

B.2 SubCLIN: 0001AA

CLIN Title: 1st Semi-Annual Report

CLIN Contract type: FFP

Inspection: Destination

Acceptance: Destination

Delivery Quantity: 1

Delivery Date: 6-months after award

Price: $600

B.3 SubCLIN: 0001AB

CLIN Title: 2nd Semi-Annual Report

CLIN Contract type: FFP

Inspection: Destination

Acceptance: Destination

Delivery Quantity: 1

Delivery Date: 12 months after award

Price: $600

Contract Data Requirement List (DD 1423)

1. DATA ITEM NO.: A001

2. TITLE OF DATA ITEM: Semi-Annual Reports (First Ordering Period)

3. SUBTITLE: N/A

4. AUTHORITY: N/A

5. CONTRACT REFERENCE: H.1

6. REQUIRING OFFICE: ACC-DTA

7. DD250 REQ: N/A; see Block 16

8. APP CODE: N/A

9. DIST. STATEMENT: C, See Block 16

10. FREQUENCY: Semi-annual

11. AS OF DATE: Date of award

12. DATE OF FIRST SUB: No later than 15 days following the end of the first six month period

13. DATE OF SUBS: No later than twelve months

14. DISTRIBUTION: See Block 16

15. TOTAL: 2

16. REMARKS:

Block 7 continuation: A Wide Area Work Flow invoice is required. Invoice type 2-in-1 shall be used.

Block 9 continuation: The following information shall be included on the deliverable: DISTRIBUTION STATEMENT C: Distribution authorized to US Government agencies and their Contractors; information may contain proprietary information. Other requests for this document shall be referred to the Contracting Officer.

PIIN/SIIN

MOD/AMD

ATT/EXH ID

PAGE

Exhibit A

Block 14 continuation: The Contractor shall electronically deliver one final, reproducible copy to the following person(s):

Dawn VanHulle, Contracting Officer, <dawn.m.vanhulle.civ@mail.mil>

Chardae Walton, Contract Specialist, <chardae.l.walton.civ@mail.mil>

Contents of Report: The reports shall not contain cumulative information from the previous submission. Contractors format is acceptable.

1. Cover page to include: Contractor name and address; IDIQ contract number; title of the report; date of the report; and period covered by the report.

2. The following information shall be repeated, as necessary, for all TOs awarded to your firm against the ERS contract suite during the period covered by the report.

A) Task Order Request (TOR) number and awarded TO number;

B) Date TO was awarded;

C) RA office the TO was in support of (reference Section A of the awarded TO);

D) Performance period of the TO, including option(s) if applicable;

E) Type of TO (e.g., FFP, time-and-materials);

F) Physical location and approximate number of personnel where work was performed under the TO;

G) Brief description of work covered by the TO;

H) Utilization of small business subcontractors, if any, to include:

i. Percentage of subcontracted dollars that went to small businesses, if any;

ii. Percentage of subcontracting effort performed by small business category (i.e. small business, small disadvantaged business, veteran-owned small business, service-disabled veteran-owned small business, or a woman-owned small business); and

iii. NAICS code(s) used for any subcontracted effort.

I) Total dollars obligated to date under the TO, to include any modifications.

3. Number of TORs your firm submitted a proposal(s) against. If your firm did not submit a proposal against any of the TORs, please provide the TOR number and an explanation as to why a proposal was not submitted.

4. Provide any feedback your firm has, for either ACC-WRN or the RA, pertaining to the TORs released to date (e.g. evaluation criterion used, small business go/no-go factor percentage, etc.).

5. Provide any concerns your firm has or suggested areas for improvement.

6. Provide any significant changes to your organization or method of operation.