Alliant_2_Special_Notice_of_Amendment-Number-9-27JUL2016.pdf

A2 Unrestricted SPECIAL NOTICE OF RFP AMENDMENT # 9 27JUL2016 Solicitation # QTA0016JCA0003

ALLIANT 2 UNRESTRICTED GWAC

SPECIAL NOTICE OF RFP AMENDMENT # 9

27 JULY 2016

NOTICE 1: Attachment J-1 DOD REQUIRED PROVISIONS AND CLAUSES is amended to strikeout “Offeror must complete and return the following provisions with their proposal” and replace with Offeror must complete and return the following provisions with their DoD Task Order proposal whenever responding to a DoD requirement. See changes below:

FULL TEXT PROVISIONS / REPRESENTATIONS AND CERTIFICATIONS

Offeror must complete and return the following provisions with their proposal.

Offeror must complete and return the following provisions with their DoD Task Order proposal whenever responding to a DoD requirement.

NOTICE 2: Section L.5.2.2.1.1(1)(a) Verification of PSC Group Relevant Experience Submission is amended to strikeout the first and last sentence; add all red text below:

a. FPDS-NG Report that provides verification of all claimed scoring elements included in Part I of the Attachment J.P-2 Relevant Experience Project Template. FPDS-NG Report that provides most verification of all claimed scoring elements included in the Attachment J.P-2 Relevant Experience Project Template. However, there are entries in Part I that are not answered by the FPDS-NG Report. Therefore, the Offeror MUST COMPLETE PART I of the J.P-2 template. Part II, III, and IV is NOT required. So, the signature of CO/COR is not required when the FPDS-NG includes the claimed PSC.

NOTE: There is no separate or additional template required. Use the same J.P-2 Relevant Experience Project Template provided to complete Part I for proposal submission. See Attachment J.P-10, FPDS-NG Sample and Crosswalk, for a sample FPDS-NG Report and example of which fields will provide appropriate verification of scoring elements. (If multiple FPDS-NG reports are available for a single project, the most recent report shall be submitted as well as any previous reports necessary for verification of claimed scoring elements.) (For a “collection of task orders,” if verification of all claimed elements is achieved without submitting all the task orders that have been awarded, then only submit those task orders that are necessary to provide verification). See Attachment J.P-10 FPDS Sample and Crosswalk for additional guidance.

PCO NOTICE 2 COMMENT: Understand this changed proposal submission requirement in the precise context of Section L.5.2.2.1.1(1)(a). This change applies EXCLUSIVELY if the Offeror has an FPDS-NG with the exact PSC on the document.

NOTICE 3: Section L.5.2.2.1.1(1)(b) Verification of PSC Group Relevant Experience Submission is amended to completely strikeout (b) and replace with paragraph noted in red text below. This change allows for a SOW/PWS incorporated in the Project from a SOO:

b. Copy of Contract Statement of Work - The Statement of Work (SOW) from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract.

Additionally, the Offeror must also identify and call attention to the specific section or sections of the SOW that support the claim of having performed the PSC and any other claimed scoring elements. Copy of Contract Statement of Work/Performance Work Statement - The Statement of Work (SOW) or the Performance Work Statement (PWS) from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract. Additionally, the Offeror must also identify and call attention to the specific section or sections of the SOW/PWS that support the claim of having performed the PSC and any other claimed scoring elements. NOTE: A copy of the government’s Statement of Objectives (SOO) combined with the awarded Project’s incorporated SOW/PWS is also acceptable. The SOO is not incorporated into the contract, but rather an attachment to the RFP’s Section L. CAUTION: GSA does not want a copy of the Offerors entire proposal or the RFP. Only the actual SOW/PWS proposed by the Offeror that was accepted and INCORPORATED into the resultant contract/order, and if available the SOO portion of the RFP. It is preferable to the Offeror to submit the SOO with the SOW/PWS than with it.

NOTICE 4: Section L.5.2.3.1.1(c) Verification of Leading Edge Technology Relevant Experience Submission is amended to completely strikeout (c) and replace with paragraph noted in red text below. This change allows for a SOW/PWS incorporated in the Project from a SOO:

c. Copy of Contract Statement of Work - The Statement of Work (SOW) from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract.

Additionally, the Offeror must provide an index to, and identify by highlighting in yellow, those specific written passages in the SOW that support the claim of having performed the LET as determined by the Offeror’s subjective review. Copy of Contract Statement of Work/Performance Work Statement - The Statement of Work (SOW) or the Performance Work Statement (PWS) from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract. Additionally, the Offeror must also identify and call attention to the specific section or sections of the SOW/PWS that support the claim of having performed the LET and any other claimed scoring elements.

NOTE: A copy of the government’s Statement of Objectives (SOO) combined with the awarded Project’s incorporated SOW/PWS is also acceptable. The SOO is not incorporated into the contract, but rather an attachment to the

RFP’s Section L. CAUTION: GSA does not want a copy of the Offerors entire proposal or the RFP. Only the actual SOW/PWS proposed by the Offeror that was accepted and INCORPORATED into the resultant contract/order, and if available the SOO portion of the RFP. It is preferable to the Offeror to submit the SOO with the SOW/PWS than with it.

NOTICE 5: Section L.5.5.2 Cost/Price Methodology and Instructions is amended to add the following sentence in red text to confirm that rates are firmly set and will be in effect at award/effective date:

NOTICE: Both the escalation rate that is set at 1.93% and all of the Standard IT Labor Category Ceiling Rates indicated in the RFP and in the attachments J.P-6 Direct Labor Rate Ranges and J.P-8 Cost/Price Template WILL NOT BE ADJUSTED OR CHANGED on the Master Contract Award or Effective Date/Notice to Proceed Date.

NOTICE 6: Section G.2.1 Authorized Agencies has been amended to add a recent statutory change at the bottom of this section as noted in red text below:

JUNE 30, 2016 STATUTORY UPDATE: The GSA Order, OGP 4800.2I Eligibility to Use GSA Sources of Supply and Services, has been updated, signed, and posted to the GSA Directives Library. The impetus for issuance of this revised Order is the recent amendment to 48 U.S.C. § 1469e to, in relevant part, include the Commonwealth of Puerto Rico as an eligible user of GSA’s supply sources. The amendment was part of the Puerto Rico Oversight, Management, and Economic Stability Act (PROMESA), which was signed into law on June 30, 2016. The Commonwealth of Puerto Rico has access to the Agency’s sources of supply and services.

The above changes will be enacted via formal SF-30 Amendment to the RFP in the near future anticipated within the two days.

PLEASE NOTE – The Procuring Contract Officer (PCO) anticipates multiple Federal Business Opportunities (FBO) postings into this Alliant 2 Unrestricted RFP document on addressing the critical questions and issues that may affect the Offeror’s submission of a proposal. The intent of the PCO is to provide important information to the public quickly as acquisition team responses for critical questions are developed. Therefore, rather than delay any information to the public for the sake of delivering a single document with all responses and RFP changes, which may inadvertently result in a much later FBO posting date, the PCO has decided to release information in smaller packages over multiple postings. - J. Cavadias, GSA Alliant 2 GWAC PCO