47QTCB22R0001 SF30 SB Amend0002.pdf

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 or (c) By separate letter or electronic communication 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 letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

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.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

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

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.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

See attached

General Services Administration/FAS/ITC 1800 F Street, N.W., Washington, D.C. 20405

47QTCB22R0001

1 6

06/30/2022

03/25/2022

Polaris GWAC Program Small Business Pool

RFP No. 47QTCB22R0001 Amendment 0002

1. G.5.1 and G.5.2 are updated to reflect the Contractor Program Manager and Contractor Contract Manager must be a direct employee of a member company if a joint venture.

2. GSAR 552.216-75 is removed from I.2.1 and inserted in full text in I.12.

3. Section J, List of Attachments, section II is updated to include the following attachments:

○ Attachment J.P-6, Project Verification Form

○ Attachment J.P-7, Joint Venture Work and Qualifications

4. Section L.3.4 is updated to extend the proposal due date to August 10, 2022.

5. Section L.3.5 is updated to reflect the revisions made to submission of questions announced on April 6, 2022 and provide additional time for the submission of questions through July 12, 2022.

6. Section L.4 is updated to the following:

Offerors must provide all documentation and proposal contents exclusively via the PSP. The PSP will guide Offerors through the submission process. Proposals submitted through other methods will not be considered. All submitted documents must be in .pdf format. All supporting documentation submitted shall contain comments (“tags”) indicating the specific reference for verification purposes. Failure to tag supporting documentation may result in an inability of the government to validate claimed scoring.

It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Proposal submissions must not be locked, encrypted, or otherwise contain barriers to opening.

7. Section L.5.1.3 is updated to the following:

Contractor teaming arrangement (CTA) means an arrangement in which –

1. Two or more companies form a partnership or joint venture to act as a potential prime contractor; or

2. A potential prime contractor agrees with one or more other companies to have them act as its subcontractors under a specified Government contract or acquisition program.

8. Section L.5.1.3.1 is updated to include the following:

Two or more companies may form a partnership or joint venture, hereafter referred to as a joint venture, to submit a proposal in response to this solicitation.

2. The joint venture meets the definition of a joint venture for size determination purposes

(13 C.F.R. 125.8 and 13 CFR 121.103(h)).

RFP No. 47QTCB22R0001 Amendment 0002

● L.5.2 Relevant Experience - Relevant Experience Projects may be from the joint venture or an individual member of the joint venture.

For offers from SBA Mentor-Protégé joint ventures, a minimum of one Primary Relevant Experience Project or Emerging Technology Relevant Experience Project must be from the Protégé or the offering Mentor-Protégé Joint Venture. No more than three Primary Relevant Experience Projects may be provided by the Mentor.

● L.5.6 Responsibility - Financial responsibility documents required by L.5.6 must be submitted for each member of the joint venture. The Uncompensated Overtime Policy and Professional Employee Compensation Plan may be either from the Joint Venture or from each member of the joint venture.

4. The Offeror must submit a complete copy of the joint venture agreement that established the joint venture relationship, and the agreement must meet the requirements of FAR 52.207-6, 13 C.F.R. 125.8 and/or 13 C.F.R. 125.9, as applicable. Failure to submit a copy of the joint venture agreement with the proposal meeting these requirements will result in the proposal being rejected. GSA is not obligated to acquire this information for an Offeror.

5. In support of the requirements of 13 C.F.R. 125.8(e), joint venture offerors must complete and submit Attachment J.P-7, Joint Venture Work and Qualifications, detailing the work done and qualifications held individually by each partner to the joint venture as well as any work done by the joint venture itself previously. If any partner or the joint venture itself has no previous work done or no qualifications held, this should be stated within the submitted Attachment J.P-7, Joint Venture Work and Qualifications.

Additional rows should be added as necessary based on the number of members within the joint venture. The submission may include no more than two pages per partner to the joint venture and no more than two pages for the joint venture itself.

9. Section L.5.1.3.3, the first sentence is updated to the following:

“An Offeror (to include members of a joint venture and proposed subcontractors) may use experience performed as a member of a joint venture, subject to the following conditions:”

10. Section L.5.1.3.3(1)(c) is updated to include “other Government employee” based on separate changes to L.5.2.2.1.1(2)(b) and L.5.2.3.1.1(1).

11. Section L.5.2.1 is updated to include the following:

A Relevant Experience Project (also referred to as a “Project”) is defined as (1) a single contract or subcontract; (2) a single task order awarded under a Multiple Award contract (as defined below); (3) a single task order awarded under a master Single-Award Indefinite Delivery task

RFP No. 47QTCB22R0001 Amendment 0002 order contract (Definite Quantity, Requirements, or Indefinite Quantity) (FAR 16.5); (4) a single task order placed under a Federal Supply Schedule contract (FAR 8.405-2); (5) a single task order placed under a Blanket Purchase Agreement (BPA) (FAR 8.405-3 or FAR 13.303); (6) a single task order placed under a Basic Ordering Agreement (BOA) (FAR 16.703) or (7) a single Other Transaction Authority (OTA) award issued under 10 U.S.C. 4021 or other applicable authority.

An indefinite delivery, indefinite quantity contract may not be claimed as a project unless performance is evident through funding at the contract level. Typically, performance on an indefinite delivery, indefinite quantity contract is through one or more task orders. As noted in the above paragraph, a task order may be submitted as a project.

12. Section L.5.2.2(a) is updated to note that only one NAICS may be claimed for a project.

13. Section L.5.2.2 (b) is updated to specify “Primary” Relevant Experience.

14. Section L.5.2.2(c) is updated to the following:

With respect to timing, each Primary Relevant Experience Project must be ongoing or have been completed on or after May 14, 2017.

15. Section L.5.2.2(d) is updated to note with respect to performance, each Primary Relevant Experience Project must be complete or have at least six months of performance by the date proposals are due.

16. The below sections are updated to note the Project Verification Form from either the PSP or Attachment J.P-6, Project Verification Form, may be utilized.

○ L.5.2.2.1.1

○ L.5.2.2.1.2

○ L.5.2.3.1.1

17. The below sections are updated to replace references to “index” with “tag”

○ L.5.2.2.1.1(2)(d)

○ L.5.2.2.1.2(c)

○ L.5.2.2.7

○ L.5.2.3.1.1

18. Sections L.5.2.2.1.1(2) and L.5.2.3.1.1(1) are updated to remove “ If at least one year of performance was not completed, then either an interim or final CPARS, or a completed Award Fee Determination” based on separate changes to L.5.2.2(d) and L.5.2.3(d).

19. Sections L.5.2.2.1.1(2)(b) and L.5.2.3.1.1(1) are updated to also allow for signature verification from a government employee with cognizance over the submitted project.

20. Section L.5.2.2.4 is updated to clarify projects with cost-reimbursement may be demonstrated by either the contract or a specific CLIN.

RFP No. 47QTCB22R0001 Amendment 0002

21. Section L.5.2.2.7 is updated to remove, “If applicable, the index should map those services to services identified in Section C.4.2, Cybersecurity.“

22. Section L.5.2.3(a) is updated to the following:

Each Project must have included the performance of one of the Emerging Technologies listed in L.5.2.3.1 Emerging Technology Listing. Only one Emerging Technology may be claimed for a project.

23. Section L.5.2.3(c) is updated to the following:

With respect to timing, each Emerging Technology Relevant Experience Project must be ongoing or have been completed on or after May 14, 2017.

24. Section L.5.2.3(d) is updated to the following:

With respect to performance, each Emerging Technology Relevant Experience Project must be complete or have at least six months of performance.

25. Section L.5.3.2 is updated to also allow for completion of the Past Performance Rating Form by a Government employee with cognizance over the submitted Project.

26. Section L.5.5.1 is updated to add the following sentence:

An IDIQ contract or BPA without performance does not satisfy the requirement of this element for previous performance.

27. Section M.4.2 is updated to the following:

The following will be evaluated to determine whether the requested proposal submission information meets the criteria for the information requested in Section L.5.1 and is current, accurate, and complete.

● Offeror’s signed SF33

● Joint Venture Information (if applicable)

● Proposed Subcontractors Verification and Subcontractor Letter(s) of Commitment (if applicable)

● Meaningful Relationship Commitment Letters (if applicable)

Any proposal which does not meet the requirements of the Acceptability Review will b e removed from consideration for award. Teaming arrangements without required documentation establishing the relationship will result in removal of claimed scoring elements and/or rejection of the proposal.

28. Section M.5.1 is updated to include:

Any proposal that fails to provide the identified minimum Relevant Experience Projects will be ineligible for award.

RFP No. 47QTCB22R0001 Amendment 0002

29. Section M.7 is updated to include joint venture work and qualifications for consideration with the determination of responsibility.

30. Attachment J.P-2 instructions are updated based on changes to L.5.2.2.1.1(2)(b) and L.5.2.3.1.1(1). Original version of Attachment J.P-2 remains acceptable for use.

31. Attachment J.P-3 document title is updated to “FPDS-NG Sample” and FPDS Data Fields for Total Period of Performance and Project Value are updated.

32. Attachment J.P-4 is updated based on separate changes to Section L.5.3.2 to allow for completion of the Past Performance Rating Form by a Government employee with cognizance over the submitted Project. Original version of Attachment J.P-4 remains acceptable for use.

33. Attachment J.P-6 instructions are updated based on changes to L.5.2.2.1.1(2)(b) and L.5.2.3.1.1(1). Original version of Attachment J.P-6 remains acceptable for use.