FA8773-15-R-8007-0001.pdf

38 CONS - FA8773

JULIE A. CHASE

4004 HILLTOP RD

TINKER AFB OK 73143-2713

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See Description of Changes

1. CONTRACT ID CODE PAGE OF PAGES

S 1 34

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 24-Mar-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X FA8773-15-R-8007

X 9B. DATED (SEE ITEM 11)

13-Mar-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

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 Offer X is extended, is not extended.

Offer 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 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 MODIFICATIONS OF CONTRACTS/ORDERS.

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

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)

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

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Mar-2015

CODE

38 CONS - FA8773

CATHY D. SUMMERS

4004 HILLTOP RD

TINKER AFB OK 73145-2713

FA8773 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE FA8773

FACILITY CODECODE

EMAIL:TEL:

FA8773-15-R-8007

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0002

The CLIN extended description has changed from Services non-personal. The contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS Version 1.1, dated 23 March 15, paragraph 3.2 I-NOSC..

CLIN 0003

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 0004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS Version 1.1, dated 23 March 15, paragraph 3.3 ESU..

CLIN 0005

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 0006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

15, paragraph 3.4 APC..

CLIN 0007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 0008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 0009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

Version 1.1, dated 23 March 15, paragraph 3.5 Operations Support (OS)..

CLIN 0010

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 0011

dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 0012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS Version 1.1, dated 23 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC)..

CLIN 0013

The CLIN extended description has changed from Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed..

CLIN 0014

The CLIN extended description has changed from ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS Version 1.1, dated 23 March 15. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed..

CLIN 1002

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 1003

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 1004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 1005

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 1006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 1007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 1008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 1009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 1010

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 1011

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 1012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to

CLIN 1013

shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, CLIN 1014 shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS

CLIN 2002

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 2003

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 2004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 2005

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 2006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 2007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 2008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 2009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 2010

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 2011

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 2012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to

CLIN 2013

shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, CLIN 2014 shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS

CLIN 3002

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 3003

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 3004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 3005

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 3006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 3007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 3008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 3009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 3010

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 3011

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 3012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to

CLIN 3013

shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, CLIN 3014 shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS

CLIN 4002

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 4003

dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 4004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 4005

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 4006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 4007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 4008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 4009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 4010

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 4011

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 4012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to

CLIN 4013

shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, CLIN 4014 shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS

CLIN 5002

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 5003

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.2 I-NOSC. to Services non-personal. The contractor shall perform

CLIN 5004

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 5005

dated 2 March 15, paragraph 3.3 ESU. to Services non-personal. The contractor shall perform all

CLIN 5006

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 5007

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 5008

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.4 APC. to Services non-personal. The contractor shall perform all

CLIN 5009

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 5010

dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 5011

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.5 Operations Support (OS). to Services non-personal. The

CLIN 5012

contractor shall perform all tasks necessary to support the 690th COG IAW the IAFNOS PWS dated 2 March 15, paragraph 3.6 Air Force Information Networks (AFIN) Mission Assurance Center (AMAC). to Services non-personal. The contractor shall perform all tasks necessary to

CLIN 5013

shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS dated 2 March 2016, paragraph 2.6 Travel/Temporary Duty (TDY). This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed. to Travel authorized under this item shall be reimbursed at cost, as limited by FAR 31.205-46(a) IAW the IAFNOS PWS Version 1.1, dated 23 March 15, CLIN 5014

The CLIN extended description has changed from ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS dated 2 March 2016. This is a Not to Exceed (NTE) CLIN.

Profit or fee is not allowed. to ODCs authorized under this item shall be reimbursed at cost. All ODCs must be in support of the IAFNOS PWS Version 1.1, dated 23 March 15. This is a Not to Exceed (NTE) CLIN. Profit or fee is not allowed..

The following have been added by full text:

RFP AMENDMENT 1

DESCRIPTION OF CHANGES

RFP FA8773-15-R-8007 Changes are annotated by a line on the left side in the applicable area

1. RFP due date changed from 3:00 PM local time, 13 Apr 15 to 3:00 PM local time, 27 Apr 15

2. Section B

a. Cost Clause 52.246-5 was added to the list under COST CLINS.

b. CLINs X002-X0014 have been updated to reflect they are IAW

Version 1.1 of the IAFNOS PWS dated 23 Mar 15.

3. Atch_1 PWS has been updated to be Version 1.1 dated 23 Mar 15

Summary of Changes - The following PWS sections were amended in Version 1.1, dated 23 Mar 15: 2.3.4.4, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.5, 3.5.6, 3.5.7, 3.5.8, 4.1.1, and 4.10.

4. PWS Appendix 6 has been updated

5. Atch_5 PPQ Cover Letter - updated to remove draft watermark

6. Atch_6 Past Performance Information (PPI) EZ Source - updated to remove watermark

7. Atch_8 Reading Room Library Instructions - updated to remove watermark

8. Section L

a. Paragraph A.7: Date questions are due has been updated from 7 days after the solicitation is released to 1:00 local time, 30 Mar 15

b. Paragraph C.2 ***EZ Source instructions updated

c. Paragraph E.1 Date PPI is due has been updated from 1:00 PM CT, 30

Mar 15 to 1:00 local time, 8 Apr 15

d. FAR Clause 252.237-7024 Fill-Ins added

9. Section M

Paragraph B.4.a.(3)(c)i: Corrected to include APC

The following have been modified:

COST CLINS

The clauses listed below are only applicable to the following COST CLINs 0013, 1013, 2013, 3013, 4013 and 5013:

52.215-22; 52.215-23; 52.216-11; 52.242-1; 52.242-15 Alt 1; 52.243-2 Alt 1; 52.246-5; & 52.249-6

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The below Table of Contents has been added

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

L-1 PROPOSAL PREPARATION INSTRUCTIONS

A. GENERAL INFORMATION

1. This acquisition is being conducted as a 100% Women-Owned Small Business set-aside under the North American Industry Classification System (NAICS) 517110. The size standard for this NAICS is 1500 employees.

2. Points of Contact. The Contracting Officer (CO) and/or Contract Specialist (CS) are the only points of contact (POC) for questions or concerns regarding this acquisition. Address any questions or concerns to the CO or CS specified in Blocks 10a through 10c of the SF 33.

3. Debriefings. The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with (IAW) FAR

15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing. The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.503.

Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

4. Discrepancies. If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO and CS in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error.

The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion so it is the responsibility of the offeror to ensure the initial proposal conforms to the solicitation requirements.

5. Electronic Reference Documents. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at https://www.fbo.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

6. Communications. The CO will control exchanges of source selection information between Government and offerors. The Government may use email to transmit such information to offerors and will include “Source Selection Information – See FAR 2.101 & FAR 3.104” in the Subject line.

7. Questions: All questions related to this solicitation must be submitted to Julie.Chase@us.af.mil and Cathy.Summers@us.af.mil no later than 1:00 PM local time, 30 Mar 15. Late requests may not be considered.

8. Reading Library. A Reading Library containing a list of Exhibits has been established at Tinker Air Force Base (AFB). The single POC for access is Ms. Julie Chase who can be reached at (405) 734-9711 or julie.chase@us.af.mil. Instructions for the library are included in the request for proposal (RFP) as Attachment 8. Reservations shall be made in advance not later than 3:00 PM CT on 16 Mar 15. The Library will be open 23 Mar – 27 Mar from 8:00 AM CT to 12:00 PM CT and 1:00 PM CT to 4:00 PM CT.

B. GENERAL INSTRUCTIONS

1. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, technical requirements, and Contract Security Classification Specification, in addition to those identified as evaluation factors or subfactors.

2. This section of the Request For Proposal (RFP) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include mailto:Julie.Chase@us.af.mil mailto:Cathy.Summers@us.af.mil all data and information requested by the RFP and must be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and RFP.

Non-conformance with the instructions provided in the RFP may result in an unfavorable proposal evaluation. Alternate proposals will not be accepted.

3. Offeror’s proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its technical evaluation on the information presented solely in the offeror's proposal.

4. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

5. The proposal acceptance period must be specified in Section A, block 12 of the solicitation. The acceptance period must be 275 calendar days or greater.

6. IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. After contract award, the Government will destroy extra copies of such unsuccessful proposals.

C. ORGANIZATION.

1. Number of Copies/Page Limitations.

The offeror shall prepare the proposal as set forth in the Proposal and Binder Organization Tables (Tables 1 and 2 below). The titles and content of each part, all of which shall be within the required page limits, are defined in Table 1, and the number of copies is described in Table 2. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal..

Proposal change pages are customarily subject to the same page limitations stated in Table 1 below;

however, deviated page limitations may be required on responses to Evaluation Notices (ENs). Each page shall be counted except cover pages, table of contents, IAFNOS labor matrix, position descriptions and glossary. The cover page shall include Offeror name, DUNS, Cage Code, POC’s name, phone number, email, and physical address.

2. The response shall consist of four (4) separate parts: Part I – Technical Proposal, Part II – Present/Past Performance Information (PPI), Part III – Price, and Part IV – Contract Documentation. The content of each proposal binder is described in detail as follows:

TABLE 1 – PROPOSAL ORGANIZATION (within binders)

PART TITLE PAGE NUMBERS

I Technical Proposal Not to exceed 75** II Past Performance Information No page limit (submit

EZ Source data via CD) but see citation limits

III Price Proposal No page limit (include Information specified in paragraph F)

IV Contract Documentation No page limit (See paragraph G for additional instruction)

TABLE 2 - BINDER ORGANIZATION

Parts I through IV Original/Copy 1* Part I only 5 Copies Part II only 7 Copies

*Original and Copy 1 binders contain the complete proposal package. Reproduction of the Government RFP is unnecessary (and unwanted). Original proposal shall include a recordable, virus-free data compact disk (CD) which contains all parts (Parts I, II, III, and IV). CD must be secured inside CD/DVD binder storage pages (3-hole type) and secured into binder rings at the front of the Original” binder.

**The IAFNOS Labor Matrix (Attachment 9) will not be included in the page count and shall be submitted via a CD. This should be the only information contained on this CD.

***In regards to the EZ Source data, provide a printed copy. The printed copy can be reproduced “as-is” directly from the EZ Source database. In addition, if you are unable to complete the EZ Source tool database, due to technical limitations (ie. with your dates, percentages, etc.) a hard copy of the PPI outside of EZ Source will be accepted. All PPI should be included on the original CD discussed above.

3. Page Size and Format.

a. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages may be single-spaced but shall have at least double spacing between paragraphs and factors or sub-factors. Except for the reproduced sections of the solicitation document, Attachment 2 (Pricing Table), and items specified in paragraph (b) below, the text size shall be no less than 12 point, Times New Roman, Arial or Courier font type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on all sides. Pages shall be numbered sequentially by part. These limitations shall apply to both electronic and hard copy proposals.

b. Legible tables, charts, graphs and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the part, and shall count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than eight-point. These limitations shall apply to both electronic and hard copy proposals. For the IAFNOS labor matrix refer to the instructions in paragraph C.2 above.

4. Cross Referencing.

The offeror shall provide a cross-reference matrix, which does not count against the page count, at the beginning of Part I - technical volume indicating the PWS paragraph number and the corresponding proposal paragraph. To the greatest extent possible, each part shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other parts of the proposal. Cross referencing within a proposal part is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation which is not found in its designated part will be assumed to have been omitted from the proposal.

5. Indexing.

Tab indexing shall be used to identify parts.

6. Glossary of Abbreviations and Acronyms.

Each part shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.

Glossaries do not count against the page limitations for their respective parts.

7. Binding and Labeling.

The proposal shall be bound in three-ring, loose leaf binders permitting the binders to lie flat when open.

Staples shall not be used. A cover sheet shall be bound in each binder, clearly marked with the title, copy number, solicitation identification, and the offeror’s name. The same identifying data shall be placed on the spine of each binder.

8. Electronic Documents.

The content and page size of electronic documents must be identical to the hard copies. Label the CD with the RFP number, title, and offeror’s name. Within the CD, use a separate electronic file for each part with associated exhibit, annexes, and attachments to permit rapid search and location. Files shall not be compressed. Submit electronic proposal documents in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, and MS Office Power Point 2010, as applicable. In the event of discrepancy(s) between the hard copies and electronic copies of a proposal, the hard copies will be used for evaluation.

D. PART 1 – TECHNICAL PROPOSAL.

1. The Technical Part should be specific and complete. Legibility, clarity, and coherence are very important. Offeror responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide the actual methodology the offeror will use to accomplish/satisfy these subfactors. All the requirements specified in the solicitation are mandatory. By submitting its proposal, the offeror represents that its firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for the offeror to tell the Government so in its proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

2. Identify submitted material by corresponding factor, subfactor, and paragraph/element herein.

3. Format and Specific Content. Offeror shall address its proposed approach to meet the minimum performance or capability requirements of each Technical Proposal subfactor as follows:

a. Subfactor 1: Staffing/Management. The offeror shall present a staffing and management approach that explains how it will meet the PWS requirements and Appendices. The approach shall not include employee names or resumes. The approach shall provide the following:

i. Completed IAFNOS Labor Matrix Chart (Attachment 9) identifying proposed labor categories, quantity of personnel by task and location by team member (see Appendix 5), technical certifications, security clearance by labor category, and shift hours IAW Appendix 4

ii. Position descriptions for each labor category. (No more than one page each and will not be included in the technical proposal page limitations.)

iii. Methods of recruiting, accession, retention, training, and obtaining and maintaining personnel clearances and certifications.

iv. Approach for ensuring continuity of services during personnel absences due to sickness, leave and vacancies such that impact to the Government is minimal.

v. Managing enterprise projects to ensure standard procedures, processes, and capabilities across the 690 COG AOR. This includes coordinating the integration, deployment and employment of enterprise initiatives/projects and addressing project risk management.

vi. Managing processes to ensure personnel maintain ability to operate existing and evolving network resources, topology, processes and procedures.

b. Subfactor 2: Transition Plan. The offeror shall present a that ensures a smooth transition and effective continuity of services between the current contracts and this effort IAW PWS requirements. This plan shall include a WBS and identify the parties, dates, critical actions, and deliverables required.

c. Subfactor 3: AFIN Mission Assurance Center (AMAC) Support. The offeror shall provide their action plan response to the following scenario that demonstrates an AMAC support approach that reflects an ability tomeet PWS sub-paragraphs 3.6 requirements:

Scenario 1: The AMAC is notified of a complete base isolation via a phone call from the affected base communication focal point (CFP). Prior to the phone call, there were no indicators identifying an impending problem. Later, an -NOS infrastructure technician identified the outage was due to high CPU utilization on the External Router.

d. Subfactor 4: Network Operations and Core Services. The offeror shall provide in its response to the following scenarios action plans and/or approaches to supporting network operations and core services that meet PWS requirements:

Scenario 2: Tom, Dick, Harry, and Renee are trying to access the same file, a sensitive but unclassified summary of a particular organization’s logistics and resupply plans while it’s in garrison. Tom has nothing to do with the organization or its resupply effort. Dick has credentials to not only access but also to manipulate and save changes to the data— but not to send it anywhere. After he manipulates the data, he attempts to put it on a USB stick. Harry has credentials to not only access, manipulate, and save changes to the data, but also to send it to the trucking company. Harry decides he wants to work on a particular file at home and attempts to attach and send it to his Hotmail account. When that fails, he decides to cut and paste all of the contents of the file into an email and tries again. Renee has credentials to not only access, manipulate, and save changes to the data, but also to send it to the trucking company. Renee finishes her work, and attempts to email the file to the trucking company. When that fails, she sends the file via FTP. The data owner has determined that this data cannot be transmitted to any Internet-enabled destination, except that of a public trucking company that is assisting in a particular portion of a resupply effort, but then only by FTP.

Describe how you would ensure the checkpoints identifed in Section M are enforced to be proactive and effective rather than reactive.

Scenario 3: On Monday, technicians are managing AFIN infrastructure devices from authorized workstations on the X.X.20.0/24 network. On Tuesday, the infrastructure work center is converted to virtual desktops and the physical workstations are removed.

The work center’s IP space for the virtual desktops is now on the X.X.40.0/24 network.

After the change, the infrastructure technicians notice that they can no longer login and manage AFIN devices.

Include in a demonstrated approach an explanation of why the infrastructure work center is no longer able to access their devices and what actions must be taken to resolve the access problems.

Scenario 4: After performing routine inspection of a remote virtual environment, your fellow virtualization technician notices that a single virtual machine host at site X has alerts stating that connectivity to that site's storage array have been lost and asks that you troubleshoot the issue.

The following tools, accesses and information are available to the technician:

a. VMWare vSphere Web Client

b. VMWare virtual client command line tool

c. PuTTy

d. Storage array web client

e. Windows Command Prompt

f. Web browser

g. RPC access to the remote site's physical Backup Server

h. Remote location's site work book that includes DNS machine names for physical and virtual machines, assigned IP addresses including devices, multiple ESX host virtual environment topology, redundant path Fibre Channel storage connections, Ethernet switch ports and vLAN connections

Recommend tasks required to troubleshoot the virtual machine host.

e. Subfactor 5: Operations Support. The offeror shall provide their action plan and/or approach to the following:

Scenario 5: Geographically separated ESU technicians are making authorized configuration changes inconsistent with each other. These changes are causing storage issues in the Microsoft exchange environments.

The offeror shall provide an explanation for the inconsistent changes and procedures to avoid the inconsistencies.

E. PART II –PAST PERFORMANCE INFORMATION.

1. General. Each offeror shall submit Past Performance Information (PPI) no later than 1:00 PM CT 8 Apr 15 IAW the format contained in Attachment 6 of the RFP. This early submission shall include the seven copies outlined above in paragraph C.2. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners. It shall include a cross-reference matrix identifying the PWS references and the team member(s) proposed to perform that function. Offerors are cautioned the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance. Past performance of either party in a joint venture counts for the past performance of the entity.

2. New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers, employees, and key personnel who have relevant experience and/or data of efforts that will perform major or critical aspects of the requirement. Discuss the roles and responsibilities of personnel involved in the prior contracts cited.

3. Reference Data. The Government reserves the right to contact and use information provided by the references and any other sources. The Government may also obtain and consider information about other contracts not mentioned in the offeror’s proposal, but which the Government determines to be similar to the proposed effort. It is the offeror’s responsibility to ensure all reference data is current and correct so that the Government can properly evaluate PPI.

4. Recency/Relevancy. Offeror shall submit PPI on no more than eight recent contracts the offeror considers most relevant in demonstrating its ability to perform the proposed effort. The total includes any subcontractors or teaming partners. Do not duplicate a contract reference for prime and subcontractor, but rather explain the role each played within the contract reference itself. For a description of the characteristics or aspects the Government will consider in determining how contracts are considered recent and relevant, see Section M, B.4.a 1 and 2.

5. Quality. CPARs information and Past Performance Questionnaires (PPQ) will be used in evaluation of recent and relevant past performance. Offeror may provide any additional information to explain corrective actions taken in the past, if any, for substandard performance and any current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.

6. Past Performance Questionnaire.

a. The offeror shall send out the PPQ (Attachment 4) to each of the offeror’s subcontractors’, teaming contractors’ and/or joint venture partners’ (i.e., each entity’s). The responsibility to send out and track the receipt and submission of the PPQs rests solely with the offeror. For each PPQ, complete and sign a letter containing substantially the same information as in the Sample PPQ Cover Letter (Attachment 5).

Cover letters should be printed on company letterhead. The offeror shall exert its best effort to ensure that a current POC, per relevant contract, submit a completed PPQ directly to the Government not later than the due date for the past performance proposal volume. Each of the offeror’s POCs shall e-mail the completed PPQ directly to Ms. Julie Chase, and Ms. Cathy Summers at: julie.chase@us.af.mil and cathy.summers@us.af.mil. Mailing the PPQs is an acceptable alternative method of transmission. The mailing address is:

38 CONS/LGCC

ATTN: Ms. Julie Chase 4004 Hilltop Rd.

Tinker AFB, OK 73145-2713 If mailing, the outside envelope must be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

SOURCE SELECTION INFORMATION - SEE FAR 3.104 FOR OFFICIAL USE ONLY

b. Once the PPQs are completed by the POC, the information contained therein shall be considered source selection sensitive and shall not be released to the offeror. Questionnaires shall be sent to directly to the Government from at least one of the following:

Program/Project Manager or equivalent, CO/Contract Administrator (CA) or equivalent, or CO Representative (COR).

7. Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of the company. As part of this explanation, show how these changes impact the relevance of any efforts the offeror identifies for past performance evaluation/performance confidence assessment.

Since the Government intends to consider PPI provided by other sources as well as that provided by the offeror(s), the "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

mailto:julie.chase@us.af.mil mailto:cathy.summers@us.af.mil

8. Consent Letters. The offeror shall submit a consent letter, executed by any potential subcontractors, teaming partners, and/or joint venture partners. The consent letter authorizes release of adverse PPI to the offeror so the offeror can, in turn, respond to such information. A sample letter follows:

SAMPLE

Contracting Officer:

We are participating as a (subcontractor/teaming partner) with (prime contractor or name of entity providing proposal) in responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-15-R-8007 for IAFNOS We understand that the Government is placing increased emphasis on past performance in order to obtain best value in source selections. In order to facilitate the performance confidence assessment process we are signing this consent letter to allow you to discuss our past performance information with the prime contractor during the source selection process.

(Signature, printed name, and title of individual who has the authority to sign for and legally bind the company)

Company Name:

Address:

9. Client Authorization Letters. PPI concerning private sector contractors, subcontractors and joint venture partners cannot be disclosed to the Government without their consent. Client authorization letters are required for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror’s performance. The Government will need the consent before contacting commercial customers to assess the offeror’s past performance. In an effort to assist the Source Selection Evaluation Board (SSEB) in assessing offeror’s past performance relevancy and confidence, the Government requests the following client authorization letter be completed for any commercial customers identified in offeror’s proposal. Offeror shall include the completed client authorization letter(s) within the Past Performance Part II.

SAMPLE

“Client:”

We are responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-15-R- 8007 for the IAFNOS contract.

In their acquisitions, the Government is placing increased emphasis on past performance as a source selection factor. The Government requires entities responding to their solicitation to identify clients and requests client participation in the evaluation process. You are hereby authorized to respond to those inquiries if the contracting office contacts you for information on work performed by our firm.

We have identified ______ of your organization as the point of contact based on his/her knowledge of our work. We appreciate your cooperation. You may direct any questions to: _____

F. PART III – PRICE PROPOSAL.

1. Price Reasonableness, Completeness, Balance, and Affordability. This section is to assist the offeror in submitting information other than cost or pricing data that is required to evaluate the reasonableness, completeness, balance, and affordability of the offeror’s proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of offeror’s proposal.

Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal.