SF-30_Amendment_Summary_of_Changes-A2_Unrestricted-02AUG2016.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 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 your 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.

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 NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

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

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION

NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

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 ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. 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 NO.

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, 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 (No., 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)

NSN 7540-01-152-8070

Previous edition unusable

ALLIANT 2 UNRESTRICTED GWAC

Amendment # 1 (August 2, 2016) to Solicitation # QTA0016JCA0003

SUMMARY OF CHANGES

The following list of amendments were originally memorialized in ten (10) separate ALLIANT 2 UNRESTRICTED GWAC SPECIAL NOTICES OF RFP AMENDMENTS (SNAs), plus five (5) Attachment J Proposal (J.P) revisions posted on Federal Business Opportunities (FBO) (www.fbo.gov) from 14 July through 29 July 2016. Those few Notices from some of the SNAs that were subsequently changed for clarification purposes are noted in this SF-30 as “UPDATED,” and those RFP Sections that were changed more than once within the 10 SNAs are noted in this SF-30 as “COMBINED” to indicate that all SNA changes are incorporated into the amended Section below. This SF-30 Amendment officially enacts those changes detailed in the Special Notices, including any updates provided within this document, and it incorporates them into Solicitation # QTA0016JCA0003.

SECTION B - AMENDMENTS

1. Section B.14 GWAC Contract Access Fee (CAF) is amended, in red/italic text, to add the following sentence to this fourth paragraph of the section to clarify that a task order’s CAF rate remains consistent for the entire Task Order term:

If a customer organization has negotiated a CAF rate based on a special written agreement and/or Memorandum of Agreement by the GWAC Program that is other than the established CAF rate, GSA will provide advance notification. The CAF Rate, effective at time of the Task Order award, shall remain the same for that Task Order for the full term of the Order.

SECTION C - AMENDMENTS

2. Section C.7.1. Master Contract PWS and Goals for Contractor Engagement, 2nd paragraph, is amended to add one phrase and delete two words as indicated in red/bold text and a red/bold text strikeout below to make reference to F.7 and correct a typographical error. All other text in this section remains as-is.

All measurable performance standards in terms of quality, timeliness, quantity, and the method of assessing Contractor performance against performance standards for the Master Contract are established in Section J’s Attachment J-5 Performance Requirements Summary (PRS). The PRS listings of Performance Standards indicate the acceptable performance level required by the Government to meet the key Master Contract deliverables. The standards will be measured and structured to permit an assessment of the Contractor’s performance whereby the results will also be written into the Contractor Past Performance Assessment Reporting System (CPARS). The Government will request the Contractor to develop a Quality Control Plan, within the time specified in Section F.7, in response to a Government Quality Assurance Surveillance Plan (QASP) that will be developed and implemented by the GSA for the PRS Performance Standards at or after the Effective Date during the first contract year of the Master Contract.

SECTION F - AMENDMENTS

3. SECTION F.7-TABLE OF DELIVERIES OR PERFORMANCE (1) change the heading name from F.7 Deliveries or Performance to F.7-TABLE OF DELIVERIES OR PERFORMANCE, and (2) to replace the entire table with the new table below. All changes and additions are indicated with a YELLOW highlight.

ID RFP SECTION/

TITLE

DELIVERABLE FREQUENCY DELIVER TO

1 C.7.1 Master Contract PWS

Quality Control Plan

Due within sixty (60) calendar days after date of the government issued

QASP.

Alliant2@gsa.gov

2 G.8

CONTRACTOR

PROGRAM

MANAGER AND

CONTRACTS

MANAGER FOR THE

GWAC MASTER

CONTRACT

Identify the Program/ Contract Managers including replacements

Within thirty (30) calendar days after the Notice to Proceed and/or within thirty (30) calendar days of any vacancy.

Alliant2@gsa.gov and Government Designated System

3 G.10

CONTRACTOR WEB

PAGE

Contractor webpage including updates

Within thirty (30) calendar days after the Notice to Proceed and/or within thirty (30) calendar days of a GSA signed/approved document.

Contractor Webpage

4 G.12

STANDARD IT

SERVICE LABOR

CATEGORY CROSS-

WALK MATRIX

Initial submission of IT LCAT Matrix including updates

Within thirty (30) calendar days after the Notice to Proceed and/or within thirty (30) calendar days of update request by GSA.

Alliant2@gsa.gov

5 G.13.1 Mandatory Contractor Meetings and Conferences

Exceptions to meeting attendance.

Within five (5) calendar days prior to the PMR provide written request.

Alliant2@gsa.gov

6 G.14.1 Electronic Communications

Shared contractor GWAC electronic mailbox

Within five (5) calendar days after the Notice to Proceed.

Alliant2@gsa.gov

7 G.19.1 Master Contract Performance Assessments

Provide comments to the Master Contract performance assessments.

Within 14 calendar days from the date of notification of availability of the past performance evaluation.

CPARS

8 G.20.1 GWAC Data Calls

1. Proposal Engagement

2. Task Order Protest.

• Responses due within ten (10) calendar days after a GSA request for the proposal engagement.

• Notifications due within ten (10) calendar days Protest lodged.

Alliant2@gsa.gov

9 G.20.2 GWAC Transactional Data

1. Invoice

2. Zero Invoice

3. No Transactional

Data

4. Correction to data

● (applicable to all Invoices) Due by the 30th calendar day after the month in which the invoice(s) were either remitted or paid by the agency client.

● (applicable to Zero Invoices) Due by 30th calendar day after the month in which there is no invoice issued for Order(s).

● (applicable to No Transactional Data) Due by 30th calendar day after the month in which Contractor has no Order activity.

• Correction to data due within five (5) calendar days of the GSA request for correction

Government Designated System

10 G.21

GWAC CONTRACT

ACCESS FEE (CAF)

AND FEE

REMITTANCE

CAF payments due to GSA/GWAC

CAF paid within the month that invoices are reported in the TDR.

Pay.gov via the Government Designated System

11 G.22.2 Subcontracting Reports

1. ISR

2. SSR

• ISR

Period 10/01–03/31 Due 04/30 Period 04/01–09/30 Due 10/30

• SSR

Period 10/01–09/30 Due 10/30 e-SRS system

12 G.24.4 Notice Required for Ownership Changes and Change of Name Agreements

Notification to GSA GWAC and provide a copy of the Novation or any other agreement that changes the status of the Contractor

Within 30 calendar days of the DCAA/DCMA or Cognizant Contracting Officer (CCO) signed Ownership/Name Change Modification.

Alliant2@gsa.gov and Government Designated System

13 G.25

ENVIRONMENTAL

OBJECTIVES AND

REQUIREMENTS

1. 1nd

Deliverable

2. 2nd

Deliverable

3. 3rd

Deliverable

4. 4th

Deliverable

5. Reporting progress towards meeting the

GHG

reduction target(s)

• 1st Deliverable – Within 12 Months from the Notice to Proceed.

• 2nd Deliverable - Within 12 months after initially filed Disclosures.

• 3rd Deliverable - Within 24 months after initially filed Disclosures.

• 4th Deliverable - Within 36 months after initially filed Disclosures.

• Within the 4th Deliverable, report annually on the Master Contract anniversary date, the progress towards meeting the GHG reduction target(s).

Online and notification to Alliant2@gsa.gov

14 G.26.1 Expired Task Order Verification/Validation

Verify/validate all data elements are correct

Within 6 months after Task Order period of performance end date.

Government Designated System

15 G.27

MASTER CONTRACT

CLOSEOUT

Corrections requested to the government designated system data.

Responses are due within ten (10) calendar days of the requested information.

Government Designated System

SECTION G - AMENDMENTS

4. Section G.2.1 Authorized Agencies is amended to add the following paragraph:

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.

5. Section G.20.2.1 Change of GSA Business System(s) during Term of the Master Contract is amended to correct a mistake of repeating this identical paragraph. The RFP is changed by deleting the second G.20.2.1 paragraph as presented below, and deleting the G.20.2.1 duplicate Table of Contents reference. G.20.2.1 still remains incorporated into the RFP as written below:

G.20.2.1 Change of GSA Business Systems during Term of the Master Contract

The Government might decide to change their business systems, whether it is a significant upgrade or a complete replacement of GSA’s current business system after the date of Master Contract award. Should the Government effect a change, develop or purchase a new system it will be incorporated into GSA as the required system of record for reporting transactional data and shall be adopted by the Contractor. The Contractor will be notified with a no-cost unilateral Modification to the Master Contract in the event of any upgrade/replacement of the business system.

6. Section G.25 ENVIRONMENTAL OBJECTIVES AND REQUIREMENTS is amended to revise 4th deliverable item by inserting the italic and red text at the end of the sentence as indicated below. All other text in this section remains as is.

4) Within 36 months after initially filed Disclosures - Disclosures must report on progress towards meeting the GHG reduction target(s), and as specified in Section F.7.

7. Section G.26.1 Expired Task Order Verification/Validation is amended to delete the entire subsection and replace it with the following paragraph immediately below the deleted one:

DELETE the original RFP paragraph:

G.26.1 Expired Task Order Verification/Validation The Contractor shall verify that all data elements have been reported and validated within the GWAC Program designated reporting system Any data identified during verification that is incorrect, must be corrected within 30 calendar days after identification has been made as specified in Section F.7.

G.26.1 Expired Task Order Verification/Validation The Contractor shall verify that all data elements have been reported and validated within the GWAC Program designated reporting system The Contractor shall verify that all data elements for each expired Task Order has been reported and validated in the Government Designated System within the time specified in Section F.7

SECTION J ATTACHMENTS - AMENDMENTS

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

SECTION J.P ATTACHMENTS - AMENDMENTS

9. The following proposal Attachments/Templates are amended and revised:

J.P-1 Document Verification and Self-Scoring - REVISED 14 July 2016

Revised RFP Attachment J.P-1 Document Verification and Self-Scoring Worksheet. The Contracting Officer has made the below listed revisions / technical corrections:

1. Changed date in cell A4 to July 14, 2016.

2. Cell A7 is now “unlocked” to permit input of offeror’s name.

3. The print layout style is now set to “landscape” format, to allow proper printing.

4. Under Section L.5.2.3.2, corrected calculation at cell E124 (subtotal score) for Breadth of Leading Edge Technologies Relevant Experience.

5. Under Section L.5.3, Past Performance for Relevant Experience Projects, cell C128 is highlighted to direct offerors to enter total number of PSC projects.

6. Under Section L.5.7, the cross-reference to RFP sections at cells A162 and A164 have been updated.

7. Under Section L.5.2.2.3, corrected description of PSC Group Relevant Experience Project – Multiple Agency Awards at cell B53.

10. J.P-8 Cost Price Template - REVISED 17 July 2016 Revised with the following changes:

1. Two comments inserted in cell C6 and G1 for clarification. Columns can be inserted if needed.

2. Protection of spreadsheet cells and both sheets are set and active.

3. Spreadsheet title amended to state "REVISED 17 July 2016".

11. J.P-2 Relevant Experience (PSC Group) Project Template, and J.P-3 Relevant Experience (Leading Edge Technology) Project Template Both J.P-2 and J.P-3 templates are amended and provided on 26 July 2016 on FBO to allow for one single extra page to be used exclusively for Part III of each template. Offeror may use the attached extra page (provided in MS Word, unlocked) and must not exceed the single extra page provided. This allowance is OPTIONAL for those Offerors who believe they require additional text in Part III. The original J.P-2 and J.P-3 templates are unchanged and remain locked. They can be used and submitted in their proposal with or without the extra Part III page provide.

- Electronic/Digital Signatures are acceptable to the PCO along with hand written signatures for templates J-P.2, J-P.3, and any other forms in the RFP requiring an official signature.

- The Offeror cannot use any templates from Draft RFPs previously posted to the official RFP.

No exceptions will be considered.

12. UPDATED: J.P-10 FPDS Sample and Crosswalk - REVISED 25 July 2016 Provided only for purposes of providing guidance on understanding certain fields of an FPDS-NG form:

1. Resorted in the order the data elements appear on the FPDS.

2. Added data element "Type of Contract".

** 3. Made a distinction between COMPLETED and ONGOING Projects for Values and Period of Performance.

4. Added the reference to the FPDS-NG User Manual.

** UPDATED Change to item #3 - COMPLETED Projects correspond with the “Action Obligated” field on the FPDS-NG if not “Incrementally Funded,” or may correspond with the “Base and all Option Values” field; however, for ONGOING Projects, Action Obligated with Base and all Option Values may result in a lower Project Value since it may not consider options that have not been exercised yet. NOTE: If the FPDS-NG’s “Amount” is incorrect, defer to the definition of Project Value found in Section L.5.2.2 PSC Group Relevant Experience, Item # 7, which states “Project value for ongoing projects is determined based on the total estimated dollar value.” Therefore, the Offeror may enter that value into the Project Value field in Part I of the J.P-2 or J.P-3.

SECTION L.3 - AMENDMENTS

13. Section L.3 PROPOSAL SUBMISSION INSTRUCTIONS is amended to read as the following for clarification purposes:

“The Offeror shall submit only one proposal, and only one Master Contract will result from this solicitation if the Offeror is awarded the Master Contract, with the exception of the following condition:

SHARING PROPOSAL EVALUATION ELEMENTS AND/OR COMMITTING

RESOURCES from other entities by way of a Meaningful Relationship

If the Offeror is NOT sharing proposal evaluation elements and/or committing resources from other entities by way of a Meaningful Relationship (See Section L.5.1.4) within a Corporate Structure (including its Parent Company/Holding Company or any one or more of its affiliates, subsidiaries, business units, joint ventures, or any other types of independent business structures), more than one Offer, e.g., proposal, from that Corporate Structure may be submitted.

Otherwise, if the Offeror submits more than one proposal with any Meaningful Relationships sharing proposal evaluation elements, only the first proposal received will be considered for evaluation and all other proposals received will be rejected.”

14. Section L.3.4 Proposal Due Date and Address Location is amended to add the name of the contracting officer to the address, and a phone number for delivery purposes:

Proposals must be mailed or hand delivered to:

General Services Administration Federal Acquisition Service Alliant 2 GWAC Program Office Attn: John Cavadias, Contracting Officer 333 W. Broadway, Suite 950 San Diego, CA 92101

Phone: * 619-696-2875

* Phone is exclusively for deliver purposes only, i.e., required for shipping labels for FedEx, USPS, and other courier services. Do not call this number for any questions relating to this procurement.)

SECTION L.4 - AMENDMENTS

15. COMBINED: Section L.4.1 PROPOSAL TABLE amended in its entirety as presented below. Therefore, replace the original L.4.1 section with the revised table.

MATERIAL AND TYPOGRAPHICAL CHANGES AMENDING THE RFP ARE

HIGHLIGHTED IN YELLOW.

All changes enacted on Section L.4.1 are from a total of four Special Notices of RFP Amendments (SNA) noted below. They are combined and updated below into one proposal table (see next page):

(1) SNA # 3 - Notice 8 (18 July 2016)

(2) SNA # 4 - Notice 3 (19 July 2016)

(3) SNA # 7 - Notice 2 (25 July 2016)

(4) SNA # 8 - Notice 3 (26 July 2016)

(15. Continued) SECTION L.4.1 PROPOSAL TABLE – REVISED 18/19/25/26 JULY 2016

VOL

RFP

Section # Title Format or Template Page Limit Example File Name

1 L.4.1 Proposal Format Table

PDF

Table of Contents

No Page Limit. CompanyName.VOL1.TOC.pdf (Inclusion of Table of Contents is

OPTIONAL)

1 L.5.1.1 SF-33 PDF Limited to SF-33 document.

SF-30, required if more than four amendments issued. Otherwise it is optional.

CompanyName.VOL1.SF33.pdf

If SF 30 is applicable:

CompanyName.VOL1.SF30.pdf

1 L.5.1.2 Document Verification and Self Scoring Worksheet

MS Excel Worksheet

PLUS

One Printed Paper Copy

** Limited to J.P- 1 Template.

CompanyName.VOL1.JP1.xls

1 L.5.1.3 (Other than Small Business ONLY) Individual Subcontracting Plan

PDF

Reference GSA Model Plan J.P-9 or

FAR 19.704

Limited to 25 pages.

CompanyName.VOL1.SP.pdf

1 L.5.1.4 Meaningful Relationship Commitment Letters (MRCL)

1 PDF per company relationship

Each MRCL must be separate and distinct

Applicable ONLY IF submitting an MRCL;

otherwise, no file need be submitted.

No Page Limit. CompanyName.VOL1.MRCL1.pdf CompanyName.VOL1.MRCL2.pdf CompanyName.VOL1.MRCL3.pdf

(If applicable, the Offeror may include more files by using the next sequential numbers to the file naming convention)

1 L.5.1.5

(Other-than- Small Business

ONLY)

Existing Joint Venture or Partnership Agreement

PDF

Applicable ONLY IF submitting as a JV/Partnership(PT);

otherwise no file need be submitted.

No Page Limit.

JVName.VOL1.JV.pdf or CompanyName.VOL1.CTA.pdf

1 CTA /

Subcontrac ting

L.5.1.5-Alt

L.5.1.5.2- Alt

(Small business

ONLY)

Small Business Contractor Teaming Arrangements, if applicable

Proposed Small Business Subcontractors, if applicable.

1 PDF for JV/PT/CTA and Separate PDFs for each Subcontractor Letter(s) of Commitment

Applicable ONLY IF submitting as a JV/PT/CTA; otherwise, no file need be submitted.

No Page Limit. JVName.VOL1.JV.pdf or CompanyName.VOL1.CTA.pdf and CompanyName.VOL1.SubcontractorN ameLOC.pdf

(If applicable, the Offeror may include more files by using the next sequential numbers to the file naming convention)

VOL

RFP

Section # Title Format or Template Page Limit Example File Name

1 L.5.1.6 Professional Employee Compensation Plan

Single PDF Recommended 10-page maximum.

CompanyName.VOL1.CP.pdf

1 L.5.1.7 Uncompensated Overtime Policy

Single PDF Limited to 10 pages.

CompanyName.VOL1.UOP.pdf

1 L.5.1.8 Representations and Certifications

1 PDF per company (each teaming member, if applicable)

Limited to Section K.

No Page Limit.

CompanyName.VOL1.RC.pdf

(Offeror may include more files by using the next sequential numbers to the file naming convention)

2 L.5.2.2 PSC Group Relevant Experience

1 PDF per project (Maximum of 7 files).

Each Project with all supporting documents should be submitted in a single .pdf in the following order:

1. Section J.P-2

2. FPDS, if applicable

3. Award Form, if applicable

4. Contract Statement of Work, if applicable

5. Supporting Information Related to a Merger, Acquisition, Novation, or Change of Name on a Specific Project, if applicable

6. Section J.P-7 and CTA agreement, if applicable

** Section J.P-2 Template limited to 3 pages for the locked template, plus one extra Part III page (optional) totaling 4 pages.

No page limit for supporting documents.

CompanyName.VOL2.PSC1-1.pdf CompanyName.VOL2.PSC1-2.pdf CompanyName.VOL2.PSC1-3.pdf CompanyName.VOL2.PSC1-4.pdf and/or CompanyName.VOL2.PSC2-1.pdf CompanyName.VOL2.PSC2-2.pdf and/or CompanyName.VOL2.PSC3-1.pdf

2 L.5.2.3 Leading Edge Technology Relevant Experience

1 PDF per project (Maximum of 30 files) Each Project with all supporting documents should be submitted in a single .pdf in the following order:

1. Section J.P-3

2. Original Contract Award Document

3. Contract Statement of Work

4. Supporting Information Related to a Merger, Acquisition, Novation, or Change of Name on a Specific Project, if applicable

5. Section J.P-7 and CTA agreement, if applicable.

** Section J.P-3 Template limited to 3 pages for the locked template, plus one extra Part III page (optional) totaling 4 pages.

No page limit for supporting documents.

CompanyName.VOL2.LET1-1.pdf CompanyName.VOL2.LET1-2.pdf CompanyName.VOL2.LET1-3.pdf and/or CompanyName.VOL2.LET2-1.pdf CompanyName.VOL2.LET2-2.pdf CompanyName.VOL2.LET2-3.pdf and/or

(If applicable, the Offeror may include more files by citing one or more of the LET categories indicated in the RFP)

VOL

RFP

Section # Title Format or Template Page Limit Example File Name

3 L.5.3 Past Performance for Relevant Experience Projects

1 PDF per Past Performance for each PSC Group Relevant Experience Project submitted

PPIRS/CPARs report, or Section J.P-5 Past Performance Rating Form if PPIRS/CPARS is not available.

No Page Limit. CompanyName.VOL3.PP.PSC1-1.pdf CompanyName.VOL3.PP.PSC1-2.pdf CompanyName.VOL3.PP.PSC1-3.pdf CompanyName.VOL3.PP.PSC1-4.pdf and/or CompanyName.VOL3.PP.PSC2-1.pdf CompanyName.VOL3.PP.PSC2-2.pdf and/or CompanyName.VOL3.PP.PSC3-1.pdf

3 L.5.3.3 Negative Past Performance Narrative

1 PDF per each negative past performance project (Maximum of 7 files).

This document is not required, only necessary if Offeror wishes to explain any negative past performance.

Limited to 2 pages per project

CompanyName.VOL3.NPP.PSC1- 1.pdf CompanyName.VOL3.NPP.PSC1- 2.pdf CompanyName.VOL3.NPP.PSC1- 3.pdf CompanyName.VOL3.NPP.PSC1- 4.pdf and/or CompanyName.VOL3.NPP.PSC2- 1.pdf CompanyName.VOL3.NPP.PSC2- 2.pdf and/or CompanyName.VOL3.NPP.PSC3- 1.pdf

4 L.5.4.1 Cost Accounting System and Audit Information

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.CASAUDIT.pd f

4 L.5.4.2 Approved Purchasing System

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.APS.pdf

4 L.5.4.3 Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Approved Billing Rates

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.FPRA.pdf or CompanyName.VOL4.FPRR.pdf or CompanyName.VOL4.ABR.pdf

4 L.5.4.4 Earned Value Management Systems (EVMS)

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification

CompanyName.VOL4.EVMS.pdf

4 L.5.4.5 Acceptable Estimating System

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification

CompanyName.VOL4.AES.pdf

VOL

RFP

Section # Title Format or Template Page Limit Example File Name

4 L.5.4.6 CMMI

Certification

Single PDF (either CMMI SVC or

DEV)

If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.CMMISVCcert.

pdf or CompanyName.VOL4.CMMIDEVcert .pdf

4 L.5.4.7 ISO 9001

Certification

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.ISO9001cert.pd f

4 L.5.4.8 ISO 20000

Certification

Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.ISO20000cert.p df

4 L.5.4.9 ISO/IEC 27000 Single PDF If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.ISOIEC27000c ert.pdf

4 L.5.4.10 Facility Clearance Level

(FCL)

PDF

If not applying for these additional points, no file need be submitted.

Limited to the verification document.

CompanyName.VOL4.FCL.pdf

5 L.5.7

(Other-than-small business Existing JV/PTs)

Organizational Risk Assessment

See VOL 1 JV/PT file format

If the Offeror is a JV/PT, the JV/PT documents should be listed in

VOL 1

If an Offeror is an established individual company, NO FILES NEED BE SUBMITTED to receive the Organizational Risk Assessment points.

5 L.5.7

(Small business CTAs)

Organizational Risk Assessment

PDF

Copies of Subcontracts if Offeror is a Prime/Subcontractor business arrangement.

(JV/PT documents requested earlier in VOL 1)

If a CTA is not applying for these additional points, no file need be submitted.

If an Offeror is an established individual company no file need be submitted to receive additional points.

Limited to the verification

CompanyName.VOL5.SUB.pdf

VOL

RFP

Section # Title Format or Template Page Limit Example File Name

6 L.5.5.1 Basis of Estimate PDF Limited to 10 pages.

No page limit for supporting documents.

CompanyName.VOL6.BoE.pdf

6 L.5.5.2 Cost/Price Template

MS Excel Worksheet ** Limited to J.P- 8 Template

CompanyName.VOL6.JP8.COSTPRI CE.xls

7 L.5.6.1 Financial Resources

1 PDF per company (and each teaming member, if applicable)

Limited to J.P-11 GSA Form 527 template.

No page limit for additional financial documentation.

CompanyName.VOL7.GSA527.pdf

(If applicable, the Offeror may include more files by citing the teaming partner company name in a sealed envelope with the Offeror’s proposal)

** The Government will not reject any locked proposal templates the Offeror submits, including J.P-1, J.P-2, J.P-3, and J.P-8, due to exceeding page limits caused by formatting problems caused by limitations of the locked template.

(END OF A2 SECTION L.4.1)

SECTION L.5 - AMENDMENTS

16. UPDATED: Section L.5.1.1 Standard Form (SF) 33 is amended to clarify the acknowledgment of official RFP Amendments, to change the subsection title to Standard Form (SF) 33 and SF-30 for Amendments, and to add two sentences to item #2 under this subsection as to when an SF-30 is required with the proposal submission. UPDATED: The two sentences were changed on this SF-30 since the SPECIAL NOTICE OF RFP AMENDMENT #3 posted on 18 July 2016 for correction/clarification:

L.5.1.1 Standard Form (SF) 33 and SF-30 for Amendments

2. If any amendments to the solicitation are issued, the Offeror must acknowledge each amendment number and date in Block 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 into Volume 1.

It is also acceptable for the Offeror to sign any and all SF-30 Amendments issued if Block 14 on the SF-33 is not completed.

1) Government recommends not to exceed 10 pages, as only a brief statement summarizing the plan is required. However, if the Offeror finds it necessary to exceed the 10 pages, the Government will not reject the additional pages.

17. Section L.5.1.2 Document Verification and Self Scoring Worksheet is amended to add the comment for item #3, The only exception is spreadsheet row number 128, Total PSC Projects Submitted; and for item #5 replace J.P-10 with J.P-2; and for item # 7 to replace the words LET 17-3 and J-P.11 with LET-10-3 and J.P-3 respectively so to correct typographical errors:

3. The Offeror must fill in Column C by entering a “Yes” or “No” for each element. (The only exception is row 128, Total PSC Projects Submitted.) Just type the word, not the quotation marks. Do not leave any Rows under Column C blank.

5. The Project Identifier (PSC Project 1-1 through PSC Project 3-1) in the Document Verification and Self Scoring Worksheet must mirror the same Project Identifier selected in the Relevant Experience (PSC Group) Project Template found in Attachment J-P.2.

7. The Project Identifier (LET 1-1 through LET 10-3) in the Document Verification and Self Scoring Worksheet must mirror the same Project Identifier selected in the Relevant Experience (Leading Edge Technology) Project Template found in Attachment J.P-3.

18. Section L.5.1.6 Professional Employee Compensation Plan is amended to add a second item to clarify Page Formatting, which is also referenced in L.4.1 Proposal Format Table:

Page Formatting:

(2) Government recommends not to exceed 10 pages, as only a brief statement summarizing the plan is required. However, the Offeror may exceed the 10 pages if necessary.

19. Section L.5.2.1 Relevant Experience Projects is amended for the following two items:

(1) To remove the word “Single” under item number “(5)” so to clarify to the Offeror that both a single award BPA and a Multiple Award BPA (FAR 8.405-3) are an acceptable Project for Relevant Experience:

A Relevant Experience “project” is defined as (1) a single contract; (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 Order contract (Definite Quantity, Requirements, or Indefinite Quantity) contract (FAR 16.5); (4) a single task order placed under a Federal Supply Schedule contract (FAR 8.405-2); or (5) a single task order placed under a master Single Award Blanket Purchase Agreement (BPA)(FAR 8.405-3). When a Single-Award Indefinite Delivery task order contract or Single Award BPA’s requirements are well defined, for a specific purpose(s), and task orders are issued on a recurring basis, a collection of task orders placed under it may be combined and submitted as a single project. A combination of U.S.

Federal Government, State Government, International Public Sector, and Non-Government projects awarded from the private sector can be submitted.

(2) UPDATED: To add the following clarifying statement in red/bold text as it concerns earning points for relevant experience from a collection of Task Orders (Note: Yellow highlighted text is UPDATED wording):

NOTICE FOR COLLECTION OF TASK ORDERS, APPLIED TO SINGLE-

AWARD INDEFINITE DELIVERY TASK ORDER CONTRACT OR SINGLE

AWARD BPA ONLY. The Offeror must list every Task Order that is covered, and this collection of Task Orders can only be used once for claiming credit for PSCs, and only once for claiming credit for LETs.

20. Section L.5.2.2 PSC Group Relevant Experience is amended as follows: (1) Item 5(c.) word basic is changed to base, and the word complete is changed to completed. (2) Definition of words and terms as added below:

5. Each PSC Group Relevant Experience Project must be ongoing or have been completed within 5 years from the date proposals are due. Each project must have at least one year of performance unless one of the following situations exist:

a. The project has an Interim or a Final CPARS.

b. The project has a completed Award Fee Determination.

c. year and that period of performance is completed.

DEFINITION: For purposes of this section L.5.2.2, the words “Ongoing” is defined as a Project that has not yet been “Completed” by the proposal submission date (29 August 2016).

“Completed” is the date on the contract/order document indicating the final day of performance or delivery; in other words, the day the contract is to be completed. Should a Contract Modification indicate an extended date of completion beyond the original completion date of the Project, the Modification completion date becomes the adjusted completion date. “Completed” date (or sometimes referred to as “Completion” date) is not the contract Closeout date, which is when all obligations of both parties have been fulfilled, e.g., unsettled funding obligations due to indirect cost audits pending after the Completion date. The word Completed, however, as applied to “a completed Award Fee Determination” is defined as the date the Award Fee Determination is officially approved by the contract officer, such as via a Modification.

21. Section L.5.2.2.1 PSC Group Relevant Experience Project Submission is amended to add the following bullet items changes noted in red text (including two new items and two existing items clarified), and to move one sentence from immediately above the Section title to below the section title and added “when applicable and required” to the end of that sentence:

For each PSC claimed, offerors must submit Attachment J.P-2, Relevant Experience (PSC Group) Project Template, with the following information when applicable and required:

● Contractor Name

● Contract Number

● Order Number, if applicable

● Project Title

● Customer Name

● Total Period of Performance (including Options)

● Project Value

● Funding Agency ID (if applicable) Funding Agency Name

● Was the project cost-reimbursement?

● Was the project a Fair Opportunity Order (per FAR 16.505) against a Multiple

Award federal government contract?

● Task Order against a Multiple Award federal government contract?

● Did the project include performance in a foreign location?

● Is this project from an existing or previous CTA?

● PSC Group Project Identifier and PSC

● Description of the work performed relevant to the PSC being claimed

● Contact information (Name, Title, Agency/Company, Phone, and Email) of the

Contracting Officer (Corporate Official for Commercial Experience) with cognizance over the project

● Contact information (Name, Title, Agency/Company, Phone, and Email) of the COR, if applicable.

22. UPDATED: 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. In addition to the SNA #9, Notice 2 (27 July 2016), all highlighted text was subsequently added to this SF-30 further clarifying the amended J.P-2 template’s mandatory and optional submission requirements, noted below:

1. FPDS-NG AVAILABLE WITH THE CORRECT PSC, COMPLETE AND

ACCURATE. If the FPDS-NG Report provides verification of all critical information included on the Attachment J.P-2, Relevant Experience (PSC Group) Project Template.

Submit the following verification documents:

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. As long as the PSC is correct on the FPDS-NG, then the FPDS-NG document is acceptable for proposal submission. However, there are entries in the J.P-2 template 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 necessarily required or mandatory. It is acceptable, nevertheless, to complete any or all other non-mandatory sections (Parts II, III, and IV) of J.P-2 at the discretion of the Offeror should they believe it to be necessary. Although, the signature of CO/COR is not required when the FPDS-NG includes the claimed PSC, it is an acceptable Part IV submission at the discretion of the Offeror. NOTE:

There is no separate or additional template required. Use the same J.P-2 Relevant Experience Project Template provided. to complete required 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.

23. 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 without it.

24. UPDATED: Section L.5.2.2.1.1(2)(c) Verification of PSC Group Relevant Experience Submission is amended to allow for an SF-30 Modification as an optional submission. See red text below:

c. Copy of original contract award document, and if applicable, any subsequent contract modification documents. This may include the following:

SF 30 – Amendment of Solicitation/Modification of Contract, or any other official modification document that changes the terms of the original contract in writing, if applicable. The Modification document must include the completed and fully executed SF-30 form with the entire Summary of Changes attached. Examples of Modification purposes that might be considered for use as supporting documentation include (1) Funding, (2) Exercise Option with additional funding, (3) Supplemental Agreements, (4) Change Orders, (5) and Changes to Scope.

Modifications are not a mandatory proposal submission requirement, and every Modification that was issued on a Project may not be relevant or necessary for submission, thus, not required.

However, should the Offeror need to present supplemental evidence of total contract dollar value so to meet required dollar thresholds, and/or a modified Scope that supports claims of PSCs, then the Offeror has the option to submit those executed Modifications. NOTE: Only the completed and fully executed Modification form, e.g., SF-30, needs to be submitted if presented for administrative purposes, i.e., Change of Address, Funding; otherwise, when submitting, include the entire Modification.

25. Section L.5.2.2.7 PSC Code Table, PSC Code Table (Group III) is amended to correct a clerical mistake in numbering. Number 11 is deleted and replaced with 10; Number 12 is deleted and replaced with 11. The number of available PSCs remains the unchanged:

GROUP

III

PSC Code Table (Group III Continued)

6 D315 IT AND TELECOM- DIGITIZING

7 D317 IT AND TELECOM- WEB-BASED SUBSCRIPTION

8 D320 IT AND TELECOM- ANNUAL HARDWARE MAINTENANCE SERVICE

PLANS

9 D324 IT AND TELECOM- BUSINESS CONTINUITY

11 10 K060 MODIFICATION OF EQUIPMENT- FIBER OPTICS MATERIALS,

COMPONENTS, ASSEMBLIES, AND ACCESSORIES

12 11 U012 EDUCATION/TRAINING- INFORMATION

TECHNOLOGY/TELECOMMUNICATIONS TRAINING

26. Section L.5.2.3 Leading Edge Technology Relevant Experience is amended as follows: (1) Item 4(c.) word basic is changed to base, and the word complete is changed to completed. (2) Definition of words and terms as added below:

4. Each Leading Edge Technology Relevant Experience Project must be either ongoing or had been open and active within 5 years from the date proposals are due. Each project must have at least one year of performance unless one of the following situations exist:

a. The project has an Interim or a Final CPARS/PPIRS.

b. The project has a completed Award Fee Determination.

c. The project had a base period of performance less than one year and that period of performance is completed.

DEFINITION: For purposes of this section L.5.2.3, the words “ongoing” and “open and active” is defined as a Project that has not yet been “Completed” by the proposal submission date (29 August 2016). “Completed” is the date on the contract/order document indicating the final day of performance or delivery; in other words, the day the contract is to be completed. Should a Contract Modification indicate an extended date of completion beyond the original completion date of the Project, the Modification completion date becomes the adjusted completion date.

“Completed” date (or sometimes referred to as “Completion” date) is not the contract Closeout date, which is when all obligations of both parties have been fulfilled, e.g., unsettled funding obligations due to indirect cost audits pending after the Completion date. The word Completed, however, as applied to “a completed Award Fee Determination” is defined as the date the Award Fee Determination is officially approved by the contracting officer, such as via a Modification.

27. Section L.5.2.3.1.1(b) Verification of Leading Edge Technology Relevant Experience Submission is amended to allow for an SF-30 Modification as an optional proposal submission.

See red text below:

b. Copy of original contract award document, and if applicable, any subsequent contract modification documents. This may include the following:

SF 30 – Amendment of Solicitation/Modification of Contract, or any other official modification document that changes the terms of the original contract in writing, if applicable. The Modification document must include the completed and fully executed SF-30 form with the entire Summary of Changes attached. Examples of Modification purposes that might be considered for use as supporting documentation include (1) Funding, (2) Exercise Option with additional funding, (3) Supplemental Agreements, (4) Change Orders, (5) and Changes to Scope. Modifications are not a mandatory proposal submission requirement, and every Modification that was issued on a Project may not be relevant or necessary for submission. However, should the Offeror need to present supplemental evidence of total contract dollar value so to meet required dollar thresholds, and/or a modified Scope that supports claims of LETs, then the Offeror has the option to submit those executed Modifications.

28. 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 without it.

29. Section L.5.2.3.1.1(d) Verification of Leading Edge Technology Relevant Experience Submission is amended to allow for a current FPDS-NG report as an optional proposal submission. See red text below:

(OPTIONAL) The Contract’s Section B Supplies/Services & Prices or Costs Contract Line Items (CLINS) - If a LET is specifically and clearly called out in a single or in multiple CLINS, the Offeror may include that section of the contract and should highlight the relevant CLINS. Additionally, the most current FPDS-NG Report is acceptable if it is relevant to supporting the Offerors LET claim, e.g., total contract dollar value (if correct).

30. Section L.5.2.3.1 Leading Edge Technologies Group Relevant Experience Project Submission is amended to add the one new bullet item noted in red text; and to add words to the sentence immediately below the section title, “a completed,” and “when applicable and required” noted in red text below:

For each Leading Edge Technology Project claimed, offerors must submit a completed Attachment J.P-3, Relevant Experience (Leading Edge Technology) Project Template, with the following information if applicable and required:

● Contractor Name

● Contract Number

● Order Number, if applicable

● Project Title

● Total Period of Performance (including Options)

● Project Value

● Is this project from an existing or previous CTA?

● Leading Edge Technology Project Identifier

● Leading Edge Technology

● Description of the work performed and how the selected Leading Edge Technology was integral to the performance of the contract.

● Contact information (Name, Title, Agency/Company, Phone, and Email) of the

Contracting Officer (Corporate Official for Commercial Experience) with cognizance over the project

● Contact information (Name, Title, Agency/Company, Phone, and Email) of the COR, if applicable

● Signature by a Contracting Officer, Contracting Officer’s Representative (COR), or Corporate Official for the ordering activity

31. Section L.5.2.3.3 Leading Edge Technology Listing is amended to add the following two sentences on the bottom of this section noted in red text below for purposes of clarification:

T…