FA8750-17-R-0001_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFRL/RIKD CODE FA8750 7. ADMINISTERED BY (If other than Item 6) CODE

USAF, AFMC

AIR FORCE RESEARCH LABORATORY

26 ELECTRONIC PARKWAY

ROME NY 13441-4514

MEGHAN F. THOMAS 3153302177

meghan.thomas.1@us.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA8750-17-R-0001

X

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers X 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 0 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; 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 you 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.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: ( ) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. 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 Page 2 for Summary of Changes.

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 SIGNER (Type or print)

CHRISTOPHER K. SCIALDONE

15B. CONTRACTOR/OFFEROR

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

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.15.2 FAR (48 CFR) 53.243 Created 12 Apr 2017 9:45 AM

SCHEDULE OF CHANGES

FA8750-17-R-0001 0002

This amendment to the RFP will extend the due date of proposals:

From: 01 May 2017 To: 08 May 2017

IAW with RIK-L006 paragrah 6(d), Offerors must acknowledge amendments within their proposals. The use of the SF 33 for acknowledgement of amendments will suffice.

1. PURPOSE. The purpose of this modification is to revise Section L and Attachment No. 17, as shown on the following page.

2. SUMMARY OF CHANGES.

(a) In SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS, the following changes are made as shown below.

1. RIK-L007(a)(V) has been amended as follows:

FROM:

Verification of current facility clearance and safeguarding capability provided by your Facility Security Officer (FSO). Offerors that do not have the required facility clearance and safeguarding capability at the time of proposal submission will be found noncompliant with the solicitation requirements, and noncompliant proposals will not be further evaluated or considered for award.

Offeror's must possess, at the time of proposal submission, a facility clearance at the Top Secret level and safeguarding capability at the Secret level, as stated on the Contract Security Classification Specification (DD Form 254) attached to this solicitation. For clarification, "facility clearance" refers to having personnel cleared at the Top Secret level and "safeguarding" refers to the storage capability at the Secret level. Offerors can contact their cognizant DSS office to obtain verification information.

TO:

1. Verification of current facility clearance issued by DSS provided by your Facility Security Officer (FSO). Offerors must possess, at the time of proposal submission, a facility clearance at the Top Secret level, as stated on the Contract Security Classification Specification (DD Form 254) attached to this solicitation. Offerors that do not have the required facility clearance at the time of proposal submission will be found noncompliant with the solicitation requirements, and noncompliant proposals will not be further evaluated or considered for award.

2. Offerors determined to be in the competitive range, or selected for award, if a competitive range is not made, must possess, or acquire prior to award of this contract, safeguarding capability at the Secret level. The Government will issue a draft DD Form 254 to those Offerors on or before the time of Final Proposal submission in order to initiate the review by DSS for safeguarding. For clarification, "facility clearance" refers to having personnel cleared at the Top Secret level and "safeguarding" refers to the storage capability at the Secret level.

Offerors can contact their local DSS office for verification purposes.

(b) In SECTION J - LIST OF ATTACHMENTS, Attachment No. 17 is included as shown on the next page.

There are no other change to the RFP.

LIST OF ATTACHMENTS

FA8750-17-R-0001 0002

DOCUMENT PGS DATE TITLE

ATTACHMENT 17 1 07 APR 2017 INDUSTRY QUESTIONS AND ANSWERS -

REQUEST FOR PROPOSAL (RFP) FA8750-17-R-

0001, AMENDMENT NO. 1

Industry Questions and Answers in Reference to Request for Proposal (RFP) Amendment No. 1 FA8750‐17‐R‐0001 0001, dated 07 April 2017 12 April 2017

Reference (Industry Questions and Answers ‐ Request for Proposal (RFP) FA8750‐17‐R‐0001 dated 24 March 2017 7 April 2017 ‐ Question 4)

Facility Clearance, Section L, RIK‐L007, section a.1.v. It states Verification of current facility clearance provided by your Facility Security Officer (FSO). Offerors that do not have the required facility clearance at the time of proposal submission will be found noncompliant with the solicitation requirements, and noncompliant proposals will not be further evaluated or considered for award. Offeror's must possess, at the time of proposal submission, a facility clearance at the Top Secret level and safeguarding capability at the Secret level, as stated on the Contract Security Classification Specification (DD Form 254) attached to this solicitation. For clarification, "facility clearance" refers to having personnel cleared at the Top Secret level and "safeguarding" refers to the storage capability at the Secret level. Offerors can contact their local DSS office to initiate this process.

Question Does “safeguarding capability” mean an existing and approved system for storing classified information or the capability of obtaining or recertifying such a system?

Answer Upon further review of the requirement stated in RIK‐L007, the Contracting Officer has determined that only the Facility Clearance will be required at the time of proposal submission and offerors determined to be in the competitive range, or selected for award, if a competitive range is not made, must possess, or acquire prior to award of this contract, safeguarding capability at the Secret level.

Paragraph (v) has been amended to further clarify these solicitation requirements.

Reference (Industry Questions and Answers ‐ Request for Proposal (RFP) FA8750‐17‐R‐0001 dated 24 March 2017 7 April 2017 ‐ Question 5)

Facility Clearance

Question If an Offeror, intending to prime, has subcontractors on their team, including a large business, which all have an active safeguarding capability at the Secret level, can the prime assert that it's subcontractors having the active capability at the time of submission meets the requirement?

Answer See answer to Question #1 above and also reference the revised language in RIK‐L007(a)(V).

Reference (Industry Questions and Answers ‐ Request for Proposal (RFP) FA8750‐17‐R‐0001 dated 24 March 2017 7 April 2017 ‐ Question 6)

Facility Clearance

Question Will the Government use the Defense Security Service (DSS) Industrial Security Facilities Database (ISDF) to determine the offeror’s possession of “safeguarding capability” at the time of proposal submission?

Answer Yes, the Government will use ISDF to determine the Offeror's possession of the "safeguarding capability", however please reference the changes to RIK‐L007(a)(V) as mentioned above.

Reference Reference RIK‐L011(c).(1).(i).(F), Page L‐20; RIK‐L011.(c).(2).(viii), Page L‐21, RIK‐L012.(a).(5), Page L‐22.

Question The Government has asked for up to 20 resumes attached to Volume III and Volume IV. In the event a resume demonstrates related experience and qualifications that support both Volume III and Volume IV, how should the Offeror annotate that? Should we attach the resume to both Volumes?

Answer The Government recommends annotating the reference on the resume. Per RIK‐L006, no more than 20 resumes representative of your team will be accepted. Therefore, a total of 20 resumes may be submitted across all volumes.

Reference Reference Attachment No. 8, Labor Category Qualifications

FA8750‐17‐R‐0001 0002, Attachment No. 17

Industry Questions and Answers in Reference to Request for Proposal (RFP) Amendment No. 1 FA8750‐17‐R‐0001 0001, dated 07 April 2017 12 April 2017

Question The Government has bundled several skill sets/job titles under common labor categories. For example, “Senior Systems Engineer / Assistant Project Technical Manager” or “Principal Electrical Engineer / Principal Software Engineer / Principal System Analyst / Principal Computer Engineer.” These job titles map to very different Bureau of Labor Statistics SOC codes, making it difficult to justify a common direct labor for each. Question: Would the Government entertain revising the labor categories to break these functions out separately?

We believe this would result in more accurate, reasonable and realistic pricing for the labor categories and for the Sample Task Order.

Answer At this point in time, the Government is not planning to revise the labor categories. As stated in Attachment No. 8, Offerors must include a describtion of the Offeror's own categories explaining/identifying why they match the Government‐defined categories. Additional justification may be used if the Offeror believes it's necessary to explain their approach.

Reference Reference Amendment 1, RIK‐L011.(b).(1) and RIK‐L011.(c).(1) revised text.

Question We interpret this modification as requiring offerors to discuss the experience and qualifications of our proposed personnel. Does the

Government also desire related corporate experience in this section?

Answer No, the appropriate section for corporate experience is RIK‐L012, Management, Volume IV.

Reference Reference Attachment 7, Cross Reference Matrix Question

Does the Government wish us to break the cross reference matrix down to explicitly map individual proposal paragraphs to the requirements? In other words, should we create a separate line in the cross reference matrix for each SOW or STO requirement

Answer As stated in RFP Amendment No. 1 Industry Questions & Answers dated 07 April, The Government requests that Offerors do not alter the format of the Cross Reference Matrix. With that being said, you may annotate whether a reference is referring to the SOW or STO within the appropriate column.

FA8750‐17‐R‐0001 0002, Attachment No. 17