SF30 Amend 0007 Alliant 3.pdf

PDF 235 KB Posted

Attached to
Alliant 3 GWAC, Request for Proposal (RFP) Federal contract opportunity
Solicitation number
47QTCB24R0009
Issued by
GSA Federal Acquisition Service

About this file

This is Amendment 0007 to the Alliant 3 GWAC solicitation (47QTCB24R0009) issued by GSA Federal Acquisition Service. The amendment makes several key changes to the RFP, including extending the proposal due date to February 24, 2025 at 4:00 PM ET, updating requirements around password-protected documents (now allowed for GSA Form 527 and associated financial documents only), and clarifying verification requirements for subcontractor and CTA member experience.

The amendment also modifies language regarding Meaningful Relationship credits, project verification requirements, and small business subcontracting plan elements. Notable changes include updates to how offerors can verify subcontractor experience on federal and commercial projects, revisions to CTA verification requirements, and clarification that offerors must provide descriptions of both the offeror's and MRCL entity's performance for claimed experience or capabilities. The amendment includes specific instructions for submitting passwords for protected financial documents to A3PSWD@gsa.gov prior to the proposal deadline.

View the file

Other files for this federal contract opportunity

Other files attached to Alliant 3 GWAC, Request for Proposal (RFP), newest first.
File Type Posted
Alliant 3 Phase One Award Notice.pdf PDF
SF30 Amend 0012 Alliant 3.pdf PDF
SF30 Amend 0011 Alliant 3.pdf PDF
Alliant 3 RFP A0011 - Version11.pdf PDF
Alliant 3 RFP A0010 - Version10.pdf PDF
SF30 Amend 0010 Alliant 3.pdf PDF
J.P-16 A3 Self-Scoring Worksheet V.5.xlsx XLSX spreadsheet
Alliant 3 RFP A0009 - Version 9.pdf PDF
J.P-10 A3 GSA Form 527 Contractor Qualification and Financial Information V.4.pdf PDF
Alliant 3 Pre-proposal Conference.pdf PDF
Alliant 3 RFP A0006 - Version 6.pdf PDF
SF30 Amend 0006 Alliant 3.pdf PDF
J.P-16 A3 Self-Scoring Worksheet V.4.xlsx XLSX spreadsheet
Alliant 3 RFP A0005 - Version 5.pdf PDF
SF30 Amend 0005 Alliant 3.pdf PDF
J.P-10 A3 GSA Form 527 Contractor Qualification and Financial Information V.3.pdf PDF
Alliant 3 RFP A0004 - Version 4.pdf PDF
SF30 Amend 0004 Alliant 3.pdf PDF
J.P-16 A3 Self-Scoring Worksheet V.3.xlsx XLSX spreadsheet
SF30 Amend 0003 Alliant 3.pdf PDF
J.P-7 A3 Federal Contract FPDS Crosswalk Sample V2.pdf PDF
A3 GR Set 02_09.27.24.pdf PDF
J.P-9 A3 Model Individual Subcontracting Plan Template V.3.xlsx XLSX spreadsheet
J.P-11 A3 Contractor C-SCRM Responsibility Questionnaire V.2.pdf PDF
J.P-18 A3 Labor Rate Attestation V.2.pdf PDF
A3 GR Set 01_08.23.24.xlsx XLSX spreadsheet
J.P-9 A3 Model Individual Subcontracting Plan Template V.2.xlsx XLSX spreadsheet
J.P-12 A3 C-SCRM References V.2.pdf PDF
SF30 Amend 0001 Alliant 3.pdf PDF
J.P-10 A3 GSA Form 527 Contractor Qualification and Financial Information V.2.pdf PDF
J.P-4 A3 Subcontractor Experience Project Template.pdf PDF
J.P-7 A3 Federal Contract FPDS Crosswalk Sample.pdf PDF
J.P-17 A3 C-SCRM Plan Preparation Guide.pdf PDF
J.P-8 A3 Price Template.xlsx XLSX spreadsheet
J.P-10 A3 GSA Form 527 Contractor Qualification and Financial Information.pdf PDF
J.P-13 A3 C-SCRM Plan Template.xlsx XLSX spreadsheet
A3 SF33 47QTCB24R0009.pdf PDF
J.P-1 A3 Contractor Teaming Arrangement (CTA) Template.pdf PDF
J.P-6 A3 Past Performance Rating Template.pdf PDF
J.P-14 A3 C-SCRM Control Selections.xlsx XLSX spreadsheet
J.P-18 A3 Labor Rate Attestation.pdf PDF
Alliant 3 RFP 47QTCB24R0009.pdf PDF
J.P-3 A3 Emerging Technology Relevant Experience Project Template.pdf PDF
J.P-5 A3 Small Business Engagement Template.pdf PDF
J.P-9 A3 Model Individual Subcontracting Plan Template.xlsx XLSX spreadsheet
J.P-11 A3 Contractor C-SCRM Responsibility Questionnaire.xlsx XLSX spreadsheet
J.P-12 A3 C-SCRM References.pdf PDF
J.P-15 A3 Climate Change Risk Management Plan Criteria.pdf PDF
J.P-16 A3 Self-Scoring Worksheet.xlsx XLSX spreadsheet
J.P-2 A3 Primary NAICS Code Relevant Experience Project Template.pdf PDF
Show all 50

Alliant 3 GWAC, Request for Proposal (RFP) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 PAGE OF PAGES

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

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

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

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

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.

copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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.

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

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

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

2. AMENDMENT/MODIFICATION NUMBER

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

See attached.

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

9A. AMENDMENT OF SOLICITATION NUMBER

47QTCB24R0009

1 5

01/23/2025

9B. DATED (SEE ITEM 11)

06/28/2024

X

(b) If any amendments to the solicitation are issued, the Offeror must acknowledge each ck amendment number and date in Block 14 of the SF-33 or complete Blocks 8 and 15 of the SF-30 for each amendment.

o d

Consequently, in addressing the fifteen elements described at FAR 52.219-9(d) of the clause in this contract entitled Small Business Subcontracting Plan, the Offeror shall:

Alliant 3 Amendment 7 Summary of Changes Item # RFP Paragraph Reference Changed From

Alliant 3 RFP V.6 A0006.pdf Changed To/Addition/Deletion

Alliant 3 RFP V.7 A0007.pdf

1 G.19.1, Last paragraph Contractor is responsible for ensuring that Task Order data pulled into the CPRM, is accurate and complete based upon the award documents received via the OCOs.

Contractor is responsible for ensuring that Task Order data pulled into the CPRM (or Government Designated System), is accurate and complete based upon the award documents received via the OCOs.

The Offeror shall not submit classified information without redaction, sanitization, and government official authorization. The Offeror shall not submit password protected documents. Be advised that the Offeror bears the risk that password protected documents will not receive credit and may result in the Government ending the proposal evaluation and removing the Offeror from consideration for award.

The Offeror shall not submit password protected documents with the exception of GSA Form 527 and the associated finacial documents. Be advised that the Offeror bears the risk that password protected documents that are not accessible by the government will not receive credit and may result in the Government ending the proposal evaluation and removing the Offeror from consideration for award.

Proposals are due no later than Proposals are due no later than 02/24/2025, 4:00 p.m. Eastern Time (ET).02/03/2025, 4:00 p.m. Eastern Time (ET).

2 L.3, 10th Paragraph

3 L.3.4, First paragraph

4 L.5.1.1, Third to last paragraph (b) If any amendments to the solicitation are issued, the Offeror must acknowledge each amendment number and date in Blo 14 of the SF-33 or complete Blocks 8 and 15 of the SF-30 for each amendment.

NOTICE: Offeror may acknowledge up to four official amendments on the SF-33 form. However, if exceeding four amendments the Offeror must submit a signed SF-30 for each amendment above four. It is also acceptable for the Offeror t sign any and all SF-30 Amendments issue via Block 14 on the SF-33.

5 L.5.1.3.2(c), Last Sentence Consequently, in addressing the eleven elements described at FAR 52.219-9(d) of the clause in this contract entitled Small Business Subcontracting Plan, the Offeror shall:

6 L.5.1.5(f)(5) (5) A list and description of at least one (5) For an Offeror to claim Meaningful Relationship credit, the Offeror must provide descriptions of the Offeror’s and MRCL entity’s performance (jointly and individually) for at least one project per experience or capability claimed (e.g. past performance, system(s), certification(s), or facility clearances). The MRCL project must be either: a Primary NAICS Code Relevant Experience Project, or a project that is the same or similar scope as of one of the offered Primary NAICS Code Relevant Experience Projects, with at least a $7.5 million dollar value threshold size.

For purposes of L.5.1.5, “performance” is defined as: actual performance of the contractually required tasks prescribed in the MRCL project’s Statement of Work.

Shared business functions and activities that are not specific to performance of the MRCL project’s Statement of Work will not be considered “performance” of a MRCL project.

Non-qualifying shared business functions and activities include, but are not limited to:

• General corporate and business oversight, functions and activities,

• Physical proximity (including proximity to cleared facilities),

• Communal workspace or shared infrastructure, real estate, or utilities,

• Shared corporate programs (such as compliance, tax, legal, etc.)

Please note: a Meaningful Relationship within a corporate structure and an offering entity CTA are distinct matters.

For Unclassified federal projects, and with the exception of cost reimbursement projects which may only be verified by the FPDS-NG Report, if the FPDS-NG Report is not available or the FPDS-NG Report does not substantiate claimed scoring elements (e.g., an Offeror claims a different NAICS code than the NAICS code assigned in FPDS- NG), the following verification documents must be included:

project (involving the claimed capability, resource, or experience) that the offeror has previously performed with the Meaningful Relationship entity for which the Offeror claims a Meaningful Relationship credit. Please note: a Meaningful Relationship within a corporate structure and an offering entity CTA are distinct matters.

7 L.5.2.3.1, Fourth paragraph If the FPDS-NG Report is not available or the FPDS-NG Report does not substantiate all claimed scoring elements (e.g., an Offeror claims a different NAICS code than the NAICS code assigned in FPDS-NG), the following verification documents must be included:

8 L.5.2.3.1(e) (e) Offerors may use work performed as a Offerors may use work performed as a subcontractor on Federal Projects. However, they may only use the value and scope of the work subcontracted. For verification of cost-reimbursement contract type, the FPDS-NG Report for the prime contract award, and the subcontract must be a cost-reimbursement contract type. When an FPDS-NG report does not verify the multiple federal government customer or foreign location on the prime contract award, the Offeror may use an Attachment J.P-2 signed by the prime contractor or cognizant government official. In addition, Offerors shall provide Attachment J.P-4 signed by the prime contractor as verification of the project work, value, scope, and cost-reimbursement contract type performed by the subcontractor.

subcontractor on Federal projects.

However, only use the value and scope of the work subcontracted, as delineated in the project verification requirements under L.5.2.4.2, may be claimed. In addition, the Offeror shall provide Attachment J.P-4 signed by the prime contractor as verification of the project work, scope and value performed by the subcontractor.

9 L.5.2.4(g) (g) Offerors may use work as a Paragraph deleted in its entirity.

subcontractor for both Federal and Commercial projects. However, they may only use the value and scope of the work subcontracted and in addition to the project verification requirements under L.

5.2.4.2 which shall be provided for the prime award, they shall additionally provide Attachment J.P-4 signed by the prime contractor as verification of the project work, scope and value performed by the subcontractor.

10 L.5.2.4(h) (h) Offerors performing as a CTA may use Paragraph deleted in its entirity.

work for Federal and Commercial projects.

However, they may only use the value and scope of the work performed by the CTA member. Project verification requirements under L.5.2.4.2 shall be provided for the prime award. In addition, as verification of the work performed by the Offering CTA member, Attachment J.P-1 must be signed by a CTA member who performed on the relevant experience project.

11 L.5.2.4.2(a), Second paragraph If the cognizant Contracting Officer’s If the cognizant Contracting Officer’s signature is unattainable, the Government will accept the signature of the Cognizant Government Official (e.g. COR, PM) directly associated with the Project. For Federal projects only, the cognizant Contracting Officer or Government Official is authorized to redact the attestation statement in Attachment J.P-3, Part IV: Project Verification Method, “and I understand that any falsification, omission, or concealment of material fact may subject me to administrative, civil, or criminal liability.”

The Attachment J.P-3 must include both cognizant Contracting Officer and Cognizant Government Official’s direct telephone numbers and email addresses.

signature is unattainable, the Government will accept the signature of the Cognizant Government Official (e.g. COR, PM) directly associated with the Project. The Attachment J.P-3 must include both cognizant Contracting Officer and Cognizant Government Official’s direct telephone numbers and email addresses.

12 L.5.2.4.2(d) (d) Offerors may use work as a (d) Offerors may use work as a subcontractor for both Federal and subcontractor for both Federal and Commercial projects. However, they may Commercial projects. However, they may only use the value and scope of the work only use the value and scope of the work subcontracted. In addition to the project subcontracted. In addition to the project verification requirements under Section L. verification requirements under Section L.

5.2.4, which shall be provided for the 5.2.4, which shall be provided for the prime prime award, they shall additionally award, they shall additionally provide provide Attachment J.P-4 signed by the Attachment J.P-4 signed by the prime prime contractor as verification of the contractor as verification of the project project work, scope and value performed work, scope and value performed by the by the subcontractor. subcontractor.

Alternative: Offerors may use work as a subcontractor for both Federal and Commercial projects. However, they may only use the value and scope of the work subcontracted. The project verification requirements under Section L.5.2.4 shall be provided for the subcontract award.

Attachment J.P-3 must be signed by the Prime Contractor (Federal projects) or Corporate Officer/Official (Commercial projects) as verification of the subcontract project work, scope and value performed by the subcontractor.

13 L.5.2.4.2(e) (e) Offerors performing as a CTA may use (e) Offerors performing as a CTA may use work for Federal and Commercial projects. work for Federal and Commercial projects.

However, they may only use the value and However, they may only use the value and scope of the work performed by the CTA scope of the work performed by the CTA member. Project verification requirements member. Project verification requirements under L.5.2.4 shall be provided for the under L.5.2.4 shall be provided for the prime prime award. In addition, as verification of award. In addition, as verification of the the work performed by the Offering CTA work performed by the Offering CTA member, Attachment J.P-1 must be signed member, Attachment J.P-1 must be signed by a CTA member who performed on the by a CTA member who performed on the Emerging Technology Relevant Experience Emerging Technology Relevant Experience Project. Project.

Alternative: Offerors may use work performed in a previous or existing CTA for both Federal and Commercial projects.

However, they may only use the value and scope of the work performed by the CTA member. Project verification requirements under section L.5.2.4 shall be provided for either the prime contract or subcontract award. In addition, as verification of the work performed in a previous or existing CTA, Attachment J.P-3 must be signed by a cognizant Contracting Officer or Government Official for Federal projects when the work is performed as a prime contractor, signed by the Prime Contractor for subcontracted work, or the Corporate Officer/Official for Commercial work.

14 L.5.5.1, New sixth paragraph N/A Added: Offerors are permitted to password regarding GSA Form 527 protect the GSA Form 527 and associated financial documents. If your organization is going to be providing password protected financial documents, they will only be viewed and evaluated if the password is emailed to: A3PSWD@gsa.gov, prior to the proposal due date and time. The resubmission or correction of a password(s) will not be permitted after the proposal due date and time. The email shall include the following information:

Offering Entity Name:

Offering Entity UEI:

CTA Member Name:

CTA Member UEI:

GSA Form 527 or Associated Document

(s) File Name:

Password:

15 M.4.2.1(a) (a) Does the Individual Subcontracting Plan (a) Does the Individual Subcontracting Plan adequately respond to each of the required elements of FAR 52.219-9(d) paragraphs (1) through (15)?

adequately respond to each of the required elements of FAR 52.219-9(d) paragraphs

(1) through (11)?

47QTCB22R0007+SF30
Polaris SDVOSB Pool RFP SF30 Continuation Page Final 30 Sept

File details come from the government source that posted it. Updated .