SF-30_Amendment_2-A2_Unrestricted_14AUG2016-Final.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 # 2 (August 14, 2016) to Solicitation # QTA0016JCA0003

SUMMARY OF CHANGES

The following list of amendments were originally memorialized in one ALLIANT 2 UNRESTRICTED GWAC SPECIAL NOTICES OF RFP AMENDMENT (SNA) that posted on Federal Business Opportunities (FBO) (www.fbo.gov) from 4 August through 5 August 2016, which included a Correction to SNA# 11, NOTICE 6. Those Notices from SNA #11 that were subsequently changed for clarification purposes are noted in this SF-30 as “UPDATED” to indicate that all SNA Notice changes are incorporated into the amended Sections 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 K - AMENDMENTS

1. Section K.2(b)(2) FAR 52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS (APR 2016) is amended to check (i) “Paragraph (d) applies,” and K.2(c)(2) is amended to uncheck all previously checked (iii) through (viii) provisions as indicated below with (i) and

(ii) remaining checked:

K.2 (b)(2) If the provision at 52.204-7 is not included in this solicitation, and the offeror is currently registered in the System for Award Management (SAM), and has completed the Representations and Certifications section of SAM electronically, the offeror may choose to use paragraph (d) of this provision instead of completing the corresponding individual representations and certifications in the solicitation. The offeror shall indicate which option applies by checking one of the following boxes:

_X_ (i) Paragraph (d) applies.

K.2 (c)(2) The following representations or certifications are applicable as indicated by the Contracting Officer:

[Contracting Officer check as appropriate.] X (i) 52.204-17, Ownership or Control of Offeror.

X (ii) 52.204-20, Predecessor of Offeror.

X (iii) 52.222-18, Certification Regarding Knowledge of Child Labor for Listed End Products.

X (iv) 52.222-48, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment- Certification.

X (v) 52.222-52, Exemption from Application of the Service Contract Labor Standards to Contracts for Certain Services-Certification.

X (vi) 52.223-9, with its Alternate I, Estimate of Percentage of Recovered Material Content for EPA–Designated Products (Alternate I only).

X (vii) 52.227-6, Royalty Information.

X (A) Basic.

X B) Alternate I.

X (viii) 52.227-15, Representation of Limited Rights Data and Restricted Computer Software.

SECTION L - AMENDMENTS

2. Section L.5.1.4 Meaningful Relationship Commitment Letters, if applicable is amended to add the following as the last paragraph of section L.5.1.4:

Meaningful relationship commitment letters shall only be used within the offering Prime Contractor’s corporate structure. They are not available for use by subcontractors in a Small Business Prime/Sub CTA or members of a Small Business or Other-than-Small Business Joint Venture or Partnership CTA.

3. Section L.5.1.5-Alt Contractor Teaming Arrangements, if applicable is amended to add the following as the last paragraph of section L.5.1.5-Alt:

NOTE: Offerors proposing as a CTA must offer as a single type of CTA.

Combinations of CTAs are not acceptable, e.g., a joint venture CTA utilizing subcontractors that are not members of the JV or a Prime/Sub CTA utilizing a JV as a subcontractor.

4. Section L.5.1.5.1 Partnership or Joint Venture, if applicable is amended to replace the sentence in (1) to read as follows:

The Joint Venture or Partnership is registered in SAM.GOV at https://www.sam.gov and has a corresponding DUNS Number.

The Joint Venture itself and all members of the Joint Venture must be registered in SAM.GOV and have a corresponding DUNS Number.

5. Section L.5.1.5.1-Alt Partnership or Joint Venture, if applicable is amended to replace the sentence in (1) to read as follows:

The Joint Venture is registered in SAM.GOV at https://www.sam.gov and has a corresponding DUNS Number.

The Joint Venture itself and all members of the Joint Venture must be registered in SAM.GOV and have a corresponding DUNS Number.

6. ** UPDATED ** Changed L.5.2.1 to add one sentence and revise the final two sentences:

Section L.5.2.1 Relevant Experience Projects is amended to add one phrase “is well defined, for a specific purpose.” Additionally, the section is amended to add three new sentences, “If a “collection of task orders” is used as a single project under a Single-Award Indefinite Delivery task order contract or a Single-Award BPA, the “collection of task orders” cannot be unbundled using any of those individual task orders to satisfy other Relevant Experience Projects (PSCs or LETs), with the exception of one Cost-reimbursement project, see L.5.2.2.4. Additionally, from this “single project” only a maximum of one LET for either Breadth or Depth may be used. In no other cases can individual task orders within a single project be used more than once in any manner for earning points if submitted as a “collection of task orders.”

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 Blanket Purchase Agreement (BPA)(FAR 8.405-3).

When a Single-Award an Indefinite Delivery task order contract or a Single Award BPA requirement is well defined for a specific purpose 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. If a “collection of task orders” is used as a single project under a Single-Award Indefinite Delivery task order contract or a Single-Award BPA, the “collection of task orders” cannot be unbundled using any of those individual task orders to satisfy other Relevant Experience Projects (PSCs or LETs), with the exception of one Cost-reimbursement project, see L.5.2.2.4. Additionally, from this “single project” only a maximum of one LET for either Breadth or Depth may be used. In no other cases can individual task orders within a single project be used more than once in any manner for earning points if submitted as a “collection of task orders.”

7. Section L.5.2.2 PSC Group Relevant Experience is amended to correct a reference to the proper section number in item #1. See below in red text.

1. Each project must have included the performance of one of the PSCs listed in L.5.2.2.4 L.5.2.2.7 PSC Code Table. The performance of the claimed PSC must have been integral to the performance of the project and for IT services.

8. Section L.5.2.2.4 PSC Group Relevant Experience Project with Cost-Reimbursement is amended to add one sentence:

If one or more Task Orders, coded in FPDS-NG as a federal government cost-reimbursement contract-type among a “collection of task orders,” is submitted as a single Project under an Indefinite Delivery Task Order contract, the Offeror may claim the maximum points for one occurrence of the two Cost-reimbursement Projects occurrences available. For example, a maximum of 1,500 points out of the 3,000 total points under L.5.2.2.4 may be claimed. No more than one occurrence may be claimed within any single Project.

9. Section L.5.4.4 Earned Value Management Systems (EVMS), Part 2, is amended to allow for an official letter if an audit report is not available noted in red text below:

Part 2- Provide a copy of the Offeror’s official audit report, if applicable and/or an official letter from Defense Contract Management Agency (DCMA) or other Cognizant Federal Agency (CFA), as applicable. The offer shall make reference to the page number and paragraph of the audit report or letter that determined the approval of the EVMS ANSI/EIA Standard-748.

10. Additional information:

ü The Offer deadline is not extended and remains 29 August 2016.

ü Acknowledgement of this amendment on this SF-30 or the SF-33 is not required until the time of Offeror’s submission.

ü Block 13 A, B, C, D, and E on Page 1 of the SF 30 do not apply.

(End of Amendment # 2)