SF30 Amend 0003 Alliant 3.pdf

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

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

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

FACILITY CODE

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

PAGE OF PAGES

6. ISSUED BY CODE

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

CODE

2. AMENDMENT/MODIFICATION NUMBER

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

9A. AMENDMENT OF SOLICITATION NUMBER

47QTCB24R0009

11/08/2024

9B. DATED (SEE ITEM 11)

06/28/2024

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 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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.

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)

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

See attached.

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

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

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

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

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

1 Attachment J.P-7 Federal Contract FPDS Sample Crosswalk, Page 2, Row Starting with "Project Value", 2nd column

Completed Projects: Base and Exercised Options Obligated Value.

Ongoing Projects: Base and All Options Estimated Value.

Completed Projects: Base and Exercised Options Value Ongoing Projects: Base and All Options Value (Total Contract Value)

Note: See second FPDS sample titled Sample Contract/Order FPDS Report

2 Attachment J.P-16, Past Performance Section dropdown options

N/A Change Description: Attachment J.P-16 is corrected to show 2500 points for drop-down options Positive and Neutral. The drop-down options Negative and Negative with Narrative are assigned 0 points. See RFP Section L.5.3.3 for more information.

3 Attachment J.P-16, Cell B82 Do any projects involve work in a Foreign Location?

Do any projects have a primary place of performance in a Foreign Location?

4 Attachment J.P-16, Cell B169 Current FPRA, FPRR, and/or Approved Billing Rates

Current FPRA, FPRR, Approved Billing Rates, and/or Final Indirect Cost Rates

5 List of Acronyms, Table 1 - Master Contract Acronyms, first column

JV JV/PT

6 G.20.2, third paragraph If during any respective month(s), the Contractor doesn't report a Paid Invoice on an active Task Order, the Contractor must report a zero invoice for that Task Order so GSA will know there will be no CAF expected for the month.

If during any respective quarter, the Contractor doesn't report a Remitted or Paid Invoice on an active Task Order, the Contractor must report a zero invoice for that Task Order so GSA will know there will be no CAF expected for that quarter.

7 G.20.5 N/A Added as 2nd paragraph:

A confirmed compromise refers to a situation in which there is clear evidence that a security incident has occurred. An example would be if an attacker or unauthorized party has gained access to a system. If verified data exfiltration or exposure, evidence of unauthorized access to sensitive systems or accounts, detection of malicious code or malware executed, confirmation of a security vulnerability that has been exploited.

8 G.20.5 N/A Added as 3rd paragraph:

A potential compromise refers to a situation where there is a possibility that a security incident has occurred, but it has not yet been confirmed. It might involve suspicious activity or unusual behavior that could indicate a breach (unexpected login attempts, unusual network traffic), detection of vulnerabilities that could have been exploited but no clear evidence of exploitation, alerts, or warnings from security monitoring tools that will need verification. The term potential compromise includes any event or incident that poses a risk of supply chain disruption, unauthorized access, or exploitation even if that risk has not yet materialized into an actual compromise. National Institute of Standards and Technology (NIST) guidelines emphasize reporting both imminent threats and suspicious activity that may impact supply chain security. A potential compromise means an incident that has the indicators or characteristics of a compromise but is not yet confirmed, warranting initial reporting so that further investigation and preemptive measures can be undertaken.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

9 G.20.5 Prime contractors are required to report any C-SCRM security incident(s) that involves a potential compromise of the supply chain for any GSA system or data or related stakeholder’s systems within 72 hours of knowledge of the event.

Prime contractors are required to report any C-SCRM security incident(s) that involves a confirmed or potential compromise of the supply chain for any GSA system or data or related stakeholder’s systems within 72 hours of knowledge of the event.

10 H.1, Table 8, page 85 Deleted: Two blank rows were deleted from the table.

11 I.2, Table 9 - FAR Clauses by Ref Removed: Clause 52.223-15, Energy Efficiency in Energy Consuming Products.

12 J-1.2 J.1.2.2 J-1.2.2

13 J-1.2.9 J-1.2.9 J-1.2.10

14 J-1.2.10 N/A Added in full text: 252.239-7009 Representation of Use of Cloud Computing. (SEP 2015)

15 J-1.3 DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting. (JAN 2023).

DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting. (May 2024).

16 J-6.1, Table 19 CLIN Structure Added: R00 - Registered Apprenticeship Program

17 K, Instructions, last Sentence (See Section K.2 below). Deleted: (See Section K.2 below).

Added: Additionally, the Offeror is required to complete the following representations and certifications and return them with the proposal in Symphony.

18 L.3.2, third paragraph For any claimed evaluation element identifying a different name other than that of the Offeror (due to a merger, acquisition, novation, or change-of-name agreement);

For any claimed evaluation element identifying a different name other than that of the Offeror or as identified in the Offeror's Meaningful Relationship Commitment Letter (due to a merger, acquisition, novation, or change-of-name agreement);

19 L.4, End of section N/A Added: Evidence documents supplied by an Offeror to substantiate claimed points shall identify the location within the document that supports the claim. This can be achieved using Symphony’s Tagging Feature. Information on how to use Tagging can be found here:

https://industrysupport.apexlogic.com/support/s olutions/articles/35000255900-tagging-for-alliant -3. As an alternative to tagging, a cover page to the document specifying the page number, section number (if applicable), paragraph number from the top of the cited page, and line number from the top of the cited paragraph should be provided.

20 L.4.1(c) (c) If multiple files are to be submitted for a single scoring element, the files should be uploaded and attached individually, not as one combined file.

Changed to: (c) For a single contract submitted for a scoring element, the files should be uploaded and attached individually, not as one combined file.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

21 L.4.1(d) N/A Added: (d) For a collection of Task Orders or BPA Calls combined as a single Primary NAICS Code Relevant Experience Project, Each task order’s evidence should be combined in a single file and then the collection of task order files should be attached to scoring elements within Symphony for the Project. Files should be arranged in this order for each Task Order or BPA Call, when applicable:

1. FPDS-NG, and/or J.P-2

2. Award Document

3. J.P-1 or J.P-4

4. CPAR or J.P-6 or Award Fee Determination

22 L.4.1, Table 22 - Proposal Format Table Row L.5.1.8, third, fourth and fifth column

Third Column: Single File Fourth Column: PDF Fifth Column: OfferorName.RepsandCerts.pdf

23 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.1.10, first column

Deleted: L.5.6

24 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.1, last column

Added:

For Task Orders & BPA Calls combined to form a single Project:

OfferorName.NAICS1of7.Task1ofX.pdf (to include all evidence files for the individual Task Order or BPA Call) OfferorName.NAICS1of7.Task 2ofX.pdf For each Task Order or BPA Call in the grouping.

25 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.2, last column

Added: OfferorName.NAICS1of7.SOW.pdf

26 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.2, last column

Added:

For Task Orders & BPA Calls combined to form a single Project:

OfferorName.NAICS1of7.Task1ofX.pdf (to include all evidence files for the individual Task Order or BPA Call) OfferorName.NAICS1of7.Task 2ofX.pdf For each Task Order or BPA Call in the grouping.

27 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.3, last column

N/A Added:

For Task Orders & BPA Calls combined to form a single Project:

OfferorName.NAICS1of7.Task1ofX.pdf (to include all evidence files for the individual Task Order or BPA Call) OfferorName.NAICS1of7.Task 2ofX.pdf For each Task Order or BPA Call in the grouping.

28 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.4, last column

N/A Added:

For a collection of Task Orders or BPA Calls, only a single project need be submitted per collection of Orders submitted as a single Project.

OfferorName.NAICS1of7.Task1ofX.pdf https://L.5.1.10

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

29 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.5, last column

N/A Added:

For a collection of Task Orders or BPA Calls, only a single project need be submitted per collection of Orders submitted as a single Project.

OfferorName.NAICS1of7.Task1ofX.pdf

30 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.6, last column

N/A Added: OfferorName.NAICS1of7Award.pdf

31 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.6, last column

N/A Add to last column:

For a collection of Task Orders or BPA Calls, only a single project need be submitted per collection of Orders submitted as a single Project.

OfferorName.NAICS1of7.Task1ofX.pdf

32 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.3.6, last column

OfferorName.NAICS1of7SOW.pdf OfferorName.NAICS1of7SOW-PWS.pdf

33 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.4.2, last column

OfferorNameET1.1of3. CPAR.pdf or OfferorNameET1.1of3.J. P-6.pdf

OfferorNameET1.2of3. CPAR.pdf or OfferorNameET1.2of3.J. P-6.pdf

Deleted:

OfferorNameET1.1of3. CPAR.pdf or OfferorNameET1.1of3.J. P-6.pdf

OfferorNameET1.2of3. CPAR.pdf or OfferorNameET1.2of3.J. P-6.pdf

34 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.2.4.2, third column

7. CPARs report, or J.P-6 Template if CPARS is not available.

Deleted: 7. CPARs report, or J.P-6 Template if CPARS is not available.

35 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.3

Add: For Task Orders & BPA Calls combined to form a single Project, the CPARS or J.P-6 for the Master IDIQ or BPA shall be submitted.

36 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.3.3, last column

OfferorName.NAICS1of 7.CPAR.pdf OfferorName.NAICS1of 7.NPPN.pdf

37 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.4.3, first column

Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Approved Billing Rates

Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, Approved Billing Rates, and/or Final Indirect Cost Rates

38 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.4.3, fifth column

OfferorName.FPRA.pdf or OfferorName.FPRR.pdf or OfferorName.ABR.pdf

OfferorName.FPRA.pdf or OfferorName.FPRR.pdf or OfferorName.ABR.pdf or OfferorName.FICR.pdf

39 L.4.1, Table 22 - Proposal Format Table, Row beginning with L.5.6, fourth column

N/A Added: PDF

40 L.5.1.4, Second Paragraph To receive Organizational Risk Assessment (Section L.5.6) credit, an Offeror submitting a proposal under an existing CTA must demonstrate experience and performance on all relevant experience projects as a

CTA...

To receive Organizational Risk Assessment (Section L.5.6) credit, an Offeror submitting a proposal under an existing CTA must demonstrate experience and performance on each relevant experience project as a CTA...

Item # RFP Paragraph Reference Changed from

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

L.5.1.5, End of second Paragraph

L.5.1.5(b)

L.5.2.1(d)

Offerors who claim a Meaningful Relationship with a Holding Company must provide an explanation detailing the Holding Company’s majority ownership and current operational control of both the Offering Entity and Meaningful Relationship Entity’s business functions, and control over the composition of the Offering Entity and Meaningful Relationship Entities’ boards of directors.

A statement of commitment by the Offering and MRCL entities as to the performance and utilization of the identified entity’s resources on Alliant 3 GWAC Task Orders.

Each Task Order or BPA Call must have a

Offerors who claim a Meaningful Relationship with a Holding Company must provide an explanation detailing the Holding Company’s majority ownership and current operational control of both the Offering Entity and Meaningful Relationship Entity’s business functions, and control over the composition of the Offering Entity and Meaningful Relationship Entities’ boards of directors.

A statement of commitment by the Offering Entity and MRCL entities as to the performance and utilization of the identified entity’s resources on Alliant 3 GWAC Task Orders.

Each individual Task Order or BPA Call must be

44 RESERVED

45 L.5.2.2(d), First Sentence

46 L.5.2.2(d), last sentence

47 L.5.2.2(g)

48 L.5.2.3.1(b), end of paragraph year or more of performance.

With respect to performance, each Primary NAICS Code Relevant Experience Project must be complete or have at least one year of performance.

If at least one year of performance was not completed in the base period, then either an interim or final CPARS, or a completed Award Fee Determination, or a completed A3 Past Performance Rating Template (Attachment J.P-6) will be accepted.

N/A

N/A complete or have a year or more of performance.

With respect to performance, each Primary NAICS Code Relevant Experience Project must be complete or have at least one year of performance prior to the date of proposal submission.

If a final CPARS is not available, then either an interim CPARS, or a completed Award Fee Determination, or a completed A3 Past Performance Rating Template (Attachment J.P-6) will be accepted.

Added: (g) Offerors may use work performed on both Federal and Commercial projects as part of a CTA as described under L.5.1.4 or L.5.1.4-Alt.

The value and scope of the work completed must be verified according to the project verification requirements under L.5.2.3.1 and L.5.2.3.2. The Offeror and CTA member who performed the relevant experience project must be properly identified in Attachment J.P-1. 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.

Added: When a Federal Agency does not allow release of the Award Document or SOW/PWS for submission for ET Relevant Experience Credit, the first line of the Narrative for Attachment J.P-2 shall state, “The Awarding Agency has restricted the access to the Award Document and/of SOW/PWS. The signature of the Cognizant Project Official on this form confirms this restriction and the information provided for the verification of project information to be true.” Credit for missing documents will not be earned without this first line of the Narrative. This is only applicable to Federal Contracts.

NOTE: Non-federal Contracts must include all documents listed in Section L.5.2.3.2 for credit.

There is no option for restricting access to required contract documents needed for validation for Non-federal Contracts.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

49 L.5.2.3.1(b), Second paragraph If the cognizant Contracting Officer’s signature is unattainable, the Government will accept the signature of the cognizant project official directly associated with the Project. The Attachment J.P-2 must include both cognizant CO’s and COR’s direct telephone numbers and email addresses. No copy of the SOW or PWS is required for Federal Contracts.

If the cognizant Contracting Officer’s signature is unattainable, the Government will accept the signature of the cognizant project official directly associated with the Project. The Attachment J.P-2 must include both the cognizant Contracting officer and Cognizant Government Official's (e.g COR, PM) direct telephone numbers and email addresses. No copy of the SOW or PWS is required for Federal Contracts.

50 L.5.2.3.1(d) If at least one year of performance was not completed, then either an interim or final CPARS, or a completed Award Fee Determination, or completed and signed Attachment J.P-6 is acceptable.

If a final CPARS is not available, then either an interim CPARS, or a completed Award Fee Determination, or completed and signed Attachment J.P-6 is acceptable.

51 L.5.2.3.1(g) N/A Added: (g) Offerors may use work performed on both Federal and Commercial projects as part of a CTA as described under L.5.1.4 or L.5.1.4-Alt.

The value and scope of the work completed must be verified according to the project verification requirements under L.5.2.3.1 and L.5.2.3.2. The Offeror and CTA member who performed the relevant experience project must be properly identified in Attachment J.P-1. 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.

52 L.5.2.3.2(g) N/A Added: (g) Offerors may use work performed on both Federal and Commercial projects as part of a CTA as described under L.5.1.4 or L.5.1.4-Alt.

The value and scope of the work completed must be verified according to the project verification requirements under L.5.2.3.1 and L.5.2.3.2. The Offeror and CTA member who performed the relevant experience project must be properly identified in Attachment J.P-1. 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.

53 L.5.2.3.3, End of section N/A NOTE: Federal Government work performed as part of a CTA member who performed the relevant experience project must be properly identified in Attachment J.P-1. 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.

54 L.5.2.3.4, Note at the end of the section NOTE: If Task Orders or BPA Calls under one IDIQ, are combined as a single relevant experience project, credit can only be earned for a single Federal Government Customer even if Task Orders or BPA Calls were placed on behalf of multiple agencies.

NOTE: The Offeror can combine Task Orders for multiple clients under the same IDIQ contract, but credit will only be earned for one Federal Customer. See RFP Section L.5.2.3.4 Demonstrating Experience with Multiple Federal Government Customers (Federal Government Contracts Only).

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

55 L.5.2.3.4, End of second paragraph N/A Federal Government work performed as part of a CTA member who performed the relevant experience project must be properly identified in Attachment J.P-1. 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.

56 L.5.2.3.4, First paragraph, First sentence

For each Primary NAICS Code Relevant Experience Project submitted under L.5.2.3.1, the Offeror will receive points for each unique Federal Government Customer. A Federal Government Customer is determined by the Funding Agency ID identified within the FPDS- NG Report

For each Primary NAICS Code Relevant Experience Project submitted under L.5.2.3.1, the Offeror will receive points for each unique Federal Government Customer. A Federal Government Customer is determined by the Funding Agency ID identified within the FPDS- NG Report or Attachment J.P-2.

57 L.5.2.3.4, First paragraph, Third Sentence

First-Tier Subcontractor Relevant Experience Projects will only receive credit if the Attachment J.P-4 submitted indicates multiple Federal Customers.

First-Tier Subcontractor Relevant Experience Projects will only receive credit for the Federal Customer indicated on the the Attachment J.P-4. Each project submitted can only claim a single Federal Customer.

58 L.5.2.3.4, third paragraph Delete:

For Task Orders combined for Primary NAICS Code Project Experience, the Funding Agency ID for each order can be used to demonstrate experience with each unique Federal Government Customer. Only evidence from one of the Task Orders or BPA Calls in the collection is required.

59 L.5.2.3.4, third paragraph N/A Added: Only evidence from one of the Task Orders or BPA Calls in the collection is required.

60 L.5.2.3.5, end of section N/A Added: Only evidence from one of the Cost-Reimbursement contract type Task Orders or BPA Calls in the collection is required. Prime Contract FPDS-NG report must indicate that the contract is a Cost-Reimbursement type contract.

61 L.5.2.3.5, First paragraph These points are only available for Primary NAICS Code Relevant Experience Projects performed as a prime contractor to the Federal Government or for First-Tier Subcontractor Relevant Experience if the Attachment J.P-4 signed by the prime contractor confirms that the subcontractor performed Cost-Reimbursement functions on the contract.

These points are only available for Primary NAICS Code Relevant Experience Projects performed as a prime contractor to the Federal Government or for First-Tier Subcontractor Relevant Experience if the Attachment J.P-4 signed by the prime contractor confirms that the subcontractor performed Cost-Reimbursement functions on the contract, and the verification documents for the Prime Contract confirm a Cost-Reimbursement contract type. For CTA Relevant Experience, an Attachment J.P-1 must be signed by a CTA member who performed on the Cost-Reimbursement relevant experience project.

62 L.5.2.3.5, fourth paragraph (NOTE), second sentence

Federal Government Subcontracts submitted must include the above for the prime contractor and Attachment J.P-4 which must be provided and signed by the prime contractor as verification of the project work, scope, location, and value performed by the subcontractor.

Federal Government Subcontracts submitted shall provide project verification documents for the prime award and Attachment J.P-4 which must be provided and signed by the prime contractor as verification of the project work, scope, location, and value performed by the subcontractor and the Prime Contract FPDS-NG report must indicate that the contract is a Cost-Reimbursement contract type.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

63 L.5.2.3.6, After fourth paragraph NA Added: NOTE: Federal Government CTA Relevant Experience Projects shall provide Attachment J.P-1 and project verification documents for the prime award, which must be provided and signed by another CTA member as verification of the project work, scope, location, and value performed by the CTA member.

64 L.5.2.3.6, fourth paragraph NOTE: Federal Government Subcontracts submitted must include the above for the prime contractor and for Attachment J.P-4 which must be provided and signed by the prime contractor as verification of the project work, scope, location, and value performed by the subcontractor.

NOTE: Federal Government Subcontracts shall provide Attachment J.P-4 and project verification documents for the prime award, which must be provided and signed by the prime contractor as verification of the project work, scope, location, and value performed by the subcontractor.

65 L.5.2.3.6, Verification Attachment J.P-2 Attachment J.P-2 (Note: Only a formatting Change, bold and italics)

66 L.5.2.4 Add: (b) Task Orders or BPA Calls cannot be combined to form a Project for submission as a single Emerging Technology Relevant Experience Project.

67 L.5.2.4(d).

Note: In V2 it was previously L.5.2.4(c).

If the relevant experience project was not fully completed, but at least one year of performance was not completed in the base period, then either an interim or final CPARS report, or a completed Award Fee Determination document or signed Attachment J.P-6 must be submitted with the proposal.

Deleted: If the relevant experience project was not fully completed, but at least one year of performance was not completed in the base period, then either an interim or final CPARS report, or a completed Award Fee Determination document or signed Attachment J.P-6 must be submitted with the proposal.

68 L.5.2.4(d) With respect to performance, each Emerging Technology Relevant Experience Project must be complete or have at least one year of performance.

With respect to performance, each Emerging Technology Relevant Experience Project must be complete or have at least one year of performance prior to the date of proposal submission.

69 L.5.2.4(h) N/A (h) Offerors performing as a CTA may use 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.

70 L.5.2.4.2 NOTE: Non-federal Contracts must include all documents listed in Section L.5.2.4.2 for credit.

There is no option for restricting access to required contract documents needed for validation for Non-federal Contracts.

71 L.5.2.4.2(a), Second paragraph If the cognizant Contracting Officer’s signature is unattainable, the Government will accept the signature of the Contracting Officer’s Representative (COR) directly associated with the Project. The Attachment J.P-3 must include both cognizant CO’s and COR’s direct telephone numbers and email addresses.

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. The Attachment J.P-3 must include both cognizant Contracting Officer's and Cognizant Government Official’s direct telephone numbers and email addresses.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

72 L.5.2.4.2(a), added as third paragraph N/A When a Federal Agency does not allow release of the Award Document or SOW/PWS for submission for ET Relevant Experience Credit, the first line of the Narrative for Attachment J.P-3 shall state, “The Awarding Agency has restricted the access to the Award Document and/of SOW/PWS. The signature of the Cognizant Project Official on this form confirms this restriction and the information provided for the verification of project information to be true.”

Credit for missing documents will not be earned without this first line of the Narrative. This is only applicable to Federal Contracts.

73 L.5.2.4.2(b) (8) Non-Government Award Form (Must explicitly identify the Contractor, Non-Government Customer, Dollar Value, and the date the customer awarded/signed).

(8) Other Transaction Agreements (OTA), grants, cooperative agreements issued for research and development, prototyping development, and production will be verified using Attachment J.P-3, which shall explicitly identify the Contractor, Government Agency, Order Number, Dollar Value, and the date the Contracting Officer awarded/signed.

(9) Non-Government Award Form shall explicitly identify the Contractor, Non-Government Customer, Dollar Value, and the date the customer awarded/signed.

74 L.5.2.4.2 (e) Deleted:

(e) If at least one year of performance was not completed (i.e.: the contract was fully performed in less than one year, or the base period was for less than a year and performance is still ongoing)If a final CPARS is not available, then the Offeror may submit either an interim or final CPARS, a completed Award Fee Determination, or a completed and signed Attachment J.P-6.

75 L.5.2.4.2(e) N/A Added:

(e) Offerors performing as a CTA may use 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 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 Emerging Technology Relevant Experience Project.

76 L.5.2.4.3, first paragraph, second sentence

A maximum of eleven (11) Emerging Technology Projects may be submitted under L.5.2.4.1 for Emerging Technology points

A maximum of eleven (11) Emerging Technology Projects may be submitted under L.5.2.4 for Emerging Technology points

77 L.5.2.4.4(c) For Federal project only, a signed copy of original contract award document, this may include one of the following:

For Federal project only, a signed copy of the award document, which may include one or more the following:

78 L.5.3, End of section N/A Added: If the Primary NAICS Code Relevant Experience Project is a collection of Task Orders or BPA calls under the same IDIQ, the CPARS report or Attachment J.P-6 must be for the overarching IDIQ Contract and not individual Task Orders or BPA Calls.

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

79 L.5.3.2, second paragraph The Past Performance Rating Template must be completed and signed by either a Contracting Officer or a Corporate Officer with cognizance over the project for the ordering activity.

The Past Performance Rating Template must be completed and signed by either a Contracting Officer or a Cognizant Government Official (e.g.

COR, PM) directly associated with the Project.

80 L.5.4.3, section header L.5.4.3 Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Approved Billing Rates

L.5.4.3 Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, Approved Billing Rates, and/or Final Indirect Cost Rates

81 L.5.4.3, first paragraph If claiming credit for this scoring element, the Offeror must provide current verification from the Defense Contract Audit Agency (DCAA), or Defense Contract Management Agency (DCMA), or any Cognizant Federal Agency (CFA) of Forward Pricing Rate Agreements (FPRA), Forward Pricing Rate Recommendations, and/or Approved Billing Rates in a single pdf file format to include the following information:

If claiming credit for this scoring element, the Offeror must provide current verification from the Defense Contract Audit Agency (DCAA), or Defense Contract Management Agency (DCMA), or any Cognizant Federal Agency (CFA) of Forward Pricing Rate Agreements (FPRA), Forward Pricing Rate Recommendations, Approved Billing Rates, and/or Final Indirect Cost Rates in a single pdf file format to include the following information:

82 L.5.4.3, (b) Part 2 (b) Part 2– Provide at least one of the first two listed items, (1) and (2):

(1) An official letter received from the federal auditing agency on their agency letterhead from DCAA, DCMA, or CFA indicating that the Offeror’s Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Approved Billing Rate had been reviewed, approved, and/or determined acceptable at the time of proposal submission.

(2) A copy of the Offeror’s official Forward Pricing Rate Agreement (FPRA), Forward Pricing Rate Recommendation (FPRR) Approved Billing Rates, audit report and audit report number from DCAA, DCMA, or CFA identifying the rates in the FPRA, FPRR, and/or Approved Billing Rates that have been audited and determined acceptable for generating estimates of costs and other data included in proposals submitted to customers. The offer shall make reference to the page number and paragraph of the audit report or letter that sets forth the FPRA, FPRR, and/or Billing Rates.

(b) Part 2– Provide at least one of the two listed items:

(1) An official letter received from the federal auditing agency on their agency letterhead from DCAA, DCMA, or CFA indicating that the Offeror’s Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, Approved Billing Rate, and/or Final Indirect Cost Rates had been reviewed, approved, and/or determined acceptable at the time of proposal submission.

(2) A copy of the Offeror’s official Forward Pricing Rate Agreement (FPRA), Forward Pricing Rate Recommendation (FPRR), Approved Billing Rates, Final Indirect Cost Rates, audit report and audit report number from DCAA, DCMA, or CFA identifying the rates in the FPRA, FPRR, Approved Billing Rates, and/or Final Indirect Cost Rates that have been audited and determined acceptable for generating estimates of costs and other data included in proposals submitted to customers.

The offer shall make reference to the page number and paragraph of the audit report or letter that sets forth the FPRA, FPRR, Billing Rates, and/or Final Indirect Cost Rates.

83 L.5.4.10, Second Paragraph N/A Added: The FCL letter must be current and dated prior to the proposal due date.

84 L.5.6(d) (d) Mentor-Protégé SBCTA: Contract/Order was previously performed by the Mentor and/or Protégé.

(d) A Mentor-Protégé SBCTA is considered to have previously performed if the Contract/Order was previously performed by the Mentor and the Protégé, working exclusively together.

85 M.2 end of last paragraph Added: Clarifications if any, will be sent by the government to the Offeror via the Symphony system. Offerors will have 10 business days to respond. Offerors that do not respond within the 10 business day period will be deemed nonresponsive to the clarification request. It is important that Offerors monitor the email of the registered user that created the offer in Symphony.

Item #

RFP Paragraph Reference

M.4.2(d)

M.5.2.1

M.6, row beginning with L.5.4.3, second column

L.5.2.3.2(f)

Changed from Alliant 3 RFP V.2 A0002.pdf

Existing Joint Venture or Partnership.

N/A

Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Approved Billing Rates

(f) Offerors combining Task Orders or BPA Calls under one IDIQ, to form a single relevant experience project, must provide all listed evidence for each Task Order or BPA Call in the grouping, except the CPAR must be for the overarching IDIQ.

Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

Existing Joint Venture or Partnership (if applicable).

Added: In the event the CPARS report does not contain a rating for all six rating areas, more than 50% of the rated areas must have received a satisfactory (or above) rating to be considered a positive rating.

Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, Approved Billing Rates, and/or Final Indirect Cost Rates

(f) Offerors combining Task Orders or BPA Calls under one IDIQ, to form a single relevant experience project, must provide all listed evidence for each Task Order or BPA Call in the grouping, except the Attachment J.P-6 must be for the overarching IDIQ.

Clause/Provision Updates Item # RFP Paragraph Reference Changed from

Alliant 3 RFP V.2 A0002.pdf Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

90 I.2, Table 9 FAR 52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper. (MAY 2011)

Removed from RFP because the requirement has been removed from the FAR.

91 I.2, Table 9 FAR 52.223-2 Affirmative Procurement of Biobased Products Under Service and Construction Contracts. (SEPT 2013)

Title, date and text updated: FAR 52.223-2 Affirmative Procurement of Biobased Products Under Service and Construction Contracts.

(MAY 2024)

92 I.2, Table 9 FAR 52.223-5 Pollution Prevention and Right-To-Know Information. (MAY 2011)

Date and text updated: FAR 52.223-5 Pollution Prevention and Right-To-Know Information.

(MAY 2024)

93 I.2, Table 9 FAR 52.223-5 Alternate I (MAY 2011) Removed from RFP because the requirement has been removed from the FAR.

94 I.2, Table 9 FAR 52.223-5 Alternate II (MAY 2011) Removed from RFP because the requirement has been removed from the FAR.

95 I.2, Table 9 FAR 52.223-6 Drug-Free Workplace. (MAY 2001)

Removed from RFP because the requirement has been removed from the FAR.

96 I.2, Table 9 FAR 52.223-10 Waste Reduction Program.

(MAY 2011)

Date and text updated: FAR 52.223-10 Waste Reduction Program. (MAY 2024)

97 I.2, Table 9 FAR 52.223-12 Maintenance, Service, Repair, or Disposal of Refrigeration Equipment and Air Conditioners. (JUN 2016)

Date and text updated: FAR 52.223-12 Maintenance, Service, Repair, or Disposal of Refrigeration Equipment and Air Conditioners.

(MAY 2024)

98 I.2, Table 9 FAR 52.223-13 Acquisition of EPEAT®–Registered Imaging Equipment.

(JUN 2014)

Removed from RFP because the requirement has been removed from the FAR.

99 I.2, Table 9 FAR 52.223-13 Alternate I (OCT 2015) Removed from RFP because the requirement has been removed from the FAR.

100 I.2, Table 9 FAR 52.223-14 Acquisition of EPEAT®-Registered Televisions. (JUN 2014)

Removed from RFP because the requirement has been removed from the FAR.

101 I.2, Table 9 FAR 52.223-14 Alternate I (JUN 2014) Removed from RFP because the requirement has been removed from the FAR.

102 I.2, Table 9 FAR 52.223-15 Energy Efficiency in Energy-Consuming Products. (MAY 2020)

Removed from RFP because the requirement has been removed from the FAR.

103 I.2, Table 9 FAR 52.223-16 Acquisition of EPEAT®-Registered Personal Computer Products. (OCT 2015)

Removed from RFP because the requirement has been removed from the FAR.

Item #

RFP Paragraph Reference

I.2, Table 9

I.2, Table 9

I.2, Table 9

I.2, Table 9

I.4, Table 11

I.4, Table 11

Section J, Table 12

J-1.1

J-1.2.7

J-1.3

J-1.3

J-1.3

J-1.3

K

Changed from Alliant 3 RFP V.2 A0002.pdf

FAR 52.223-16 Alternate I (JUN 2014)

FAR 52.223-17 Affirmative Procurement Of EPA-Designated Items In Service And Construction Contracts. (AUG 2018) FAR 52.223-18 Encouraging Contractor Policies to Ban Text Messaging While Driving. (JUN 2020) FAR 52.244-5 Competition in Subcontracting. (DEC 1996) GSAR 552.216-75 Transactional Data Reporting. (FEB 2023) GSAR 552.232-1 Payments. ((NOV 2009)

(DEVIATION FAR 52.232-1))

GSAM 552.203-71 Restriction on Advertising. (SEP 1999) DFARS 252.225-7035 Buy America—Free Trade Agreements—Balance of Payments Program Certificate. (FEB 2024) N/A

DFARS 252.223-7004 Drug-Free Work Force. (SEP 1988)

DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. (JAN 2023) DFARS 252.225-7004 Report of Intended Performance Outside the United States and Canada—Submission after Award. (OCT 2020) DFARS 252.247-7023 Transportation of Supplies by Sea. (JAN 2023)

FAR 52.204-8 Annual Representations and Certifications. (FEB 2024)

Changed To/Addition/Deletion Alliant 3 RFP V.3 A0003.pdf

Removed from RFP because the requirement has been removed from the FAR.

Removed from RFP because the requirement has been removed from the FAR.

Removed from RFP because the requirement has been removed from the FAR.

Date and text updated: FAR 52.244-5 Competition in Subcontracting. (AUG 2024) Clause is IBR in the RFP as GSAR 552.216-75 Transactional Data Reporting. (MAY 2023).

Removed from RFP because the requirement has been removed from the FAR.

Moved to GSAR 552.203-71 section, date and text has been updated.

Clause title change: DFARS 252.225-7035 Buy American—Free Trade Agreements—Balance of Payments Program Certificate. (FEB 2024) Added to RFP: DFARS 252.226-7003 DRUG-FREE WORK FORCE (AUG 2024); this replaces DFARS 252.223-7004 Drug-Free Work Force. (SEP 1988) Removed from RFP. Replaced with DFARS

252.226-7003 DRUG-FREE WORK FORCE

(AUG 2024)

Date and text updated: DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. (MAY 2024) Date and text updated: DFARS 252.225-7004 Report of Intended Performance Outside the United States and Canada—Submission after Award. (JUL 2024) Date and text updated: DFARS 252.247-7023 Transportation of Supplies by Sea - BASIC.

(OCT 2024)

Date and text updated: FAR 52.204-8 Annual Representations and Certifications. (MAY 2024)