Amendment_01 _W911RZ-15-R-0002_Ft_Carson_BOS _16_June_2016.pdf

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

The purpose of this amendment is to add the room number of the Pre Proposal/Site Visit Conference location (Section L, Para 1.12.1), to add a clarif ication for enteriance using Gate 1 for the Pre Proposal/Site Visit Conference (Section L, Para 1.12.3), and to provide a local number to reach the Contract Specialist during the Pre Proposal/Site Visit Conference (Section L, Para 1.12.1). Additions are highlighted in yellow .

1. CONTRACT ID CODE PAGE OF PAGES

J 1 18

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

16C. DATE SIGNED

BY 16-Jun-2016

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 W911RZ-15-R-0002

X 9B. DATED (SEE ITEM 11)

07-Jun-2016

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

16-Jun-2016

CODE

MICC-JBLM

BLDG 2015, MS19, BOX 339500

JOINT BASE LEWIS-MCCHORD WA 98433-9500

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W911RZ-15-R-0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

1.0 GENERAL INSTRUCTIONS AND INFORMATION

1.0.1 This section provides general guidance, as well as specific instructions on format and content, for preparing proposals. The Offeror’s proposal must include all information requested and must be submitted in accordance with these instructions. Compliance with these instructions is mandatory and failure to furnish a complete proposal, at the time of proposal submission, may result in the proposal being unacceptable to the Government and may eliminate the Offeror from further consideration for award. It is the Offeror's responsibility to ensure the completeness of the proposal submitted. With respect to cost/price proposals, the burden of proof for credibility rests with each Offeror. Evaluation of a proposal will be conducted solely on the basis of the information contained within it and the Government will not assume that an Offeror possesses any capabilities not specified.

Inconsistencies among the parts of each proposal shall be explained. Any unexplained inconsistency may raise a fundamental question of the Offeror's understanding of the requirement and/or ability to perform. Offerors are advised that their proposals are presumed to represent their best efforts and must complete responses to this Request for Proposal (RFP). Proposals that simply reiterate the contents of this RFP, or contain only superficial responses, may be considered unacceptable. Evidence of experience, capability, and qualifications that clearly demonstrate and support the Offeror’s claims are essential. The absence of such evidence will adversely influence the evaluation of the proposal. Instructions contained herein, prescribe the format for the proposal and describe the approach for the development and presentation of proposal data. These instructions are designed to ensure the submission of necessary information to provide for the understanding and comprehensive evaluation of proposals.

1.1 POINT OF CONTACT

All questions, concerns, or clarifications shall be addressed to the Procuring Contracting Officer (PCO) listed below as the sole point of contact for this acquisition. All inquiries must be made in writing and submitted electronically to the Contract Specialist with a copy to the PCO. The SUBJECT LINE shall be “W911RZ-15-R-0002, Question, ATTN: Renee Krahenbuhl.” Offerors will receive a notice of receipt, but if they do not, it is their responsibility to follow-up by contacting the addressees listed below.

Contract Specialist:

Renee M. Krahenbuhl

MICC-JBLM

100 COL Joe Jackson Blvd, Ste 2001 Joint Base Lewis-McChord, WA 98438 Phone—(253) 982-0468 Email: usarmy.jblm.acc-micc.list.proposals@mail.mil

Procuring Contracting Officer:

Linda J. Murphy

MICC-JBLM

100 COL Joe Jackson Blvd, Ste 2001 Joint Base Lewis-McChord, WA 98438 Phone—(253) 982-9888 Email: usarmy.jblm.acc-micc.list.proposals@mail.mil

1.2 PROPOSAL CLARITY

The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet the requirements. The Government will consider statements and phrases such as “standard procedures will be employed” or “well known techniques will be used", etc. unacceptable. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s capabilities or experience; and as such, the Government will base its evaluation solely on the information presented in its proposal and information obtained through sources identified in past performance. As set forth in FAR 52.215-1 Alternate I (f)(4), the Government intends on conducting discussions with offerors whose proposals have been determined to be in the competitive range

1.3 RESTRICTIONS ON DISCLOSURE AND USE OF PROPOSAL

A proposal may include data, such as technical designs or concepts, financial data, or management plans that the Offeror does not want disclosed to the public for any reason, or used by the Government for any purpose other than proposal evaluation and contract award. If the Offeror wishes to restrict the proposal, the Offeror shall mark it in accordance with FAR 52.215-1(e).

1.4 DISPOSITION OF PROPOSALS

In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain the “original” copy of all proposals and supplemental documents provided. Unless the Offeror requests otherwise, at the completion of this acquisition the Government will destroy all extra copies of proposals and additional documents submitted.

1.5 POST AWARD NOTICES & DEBRIEFINGS

Post-award notices and debriefings will be conducted in accordance with FAR 15.506. The PCO will notify unsuccessful Offerors in accordance with FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing in accordance with FAR 15.505 or 15.506. Offerors desiring debriefings must make their requests in accordance with the requirements of FAR 15.505 or 15.506 as applicable.

1.6 SECURITY REQUIREMENTS

A DoD Contract Security Classification Specification, DD Form 254, will be incorporated as part of the contract.

An Offeror must be able to perform requirements at the highest level (SECRET) to be eligible for award.

1.7 RESTRICTIONS OF CONTACTS

Concurrent with the release of this RFP, appropriate offices will be advised that a source selection action is in progress for the proposed award and that contact by participating Offerors on the subject of this RFP is inappropriate. Recipients of this RFP shall not attempt such contacts during this period.

1.8 PRE-AWARD SURVEY

A pre-award survey may be accomplished on all Offerors submitting proposals to supplement the determination of contractor responsibility as defined in FAR 9.1. The Offeror shall be required to participate in a pre-award survey for the purpose of determining its financial and technical ability to perform. The pre-award survey is conducted with the assistance of the Offeror’s cognizant Government Contract Administration Office to determine its eligibility and ability to perform. Refusal to participate in a pre-award survey and failure to provide all requested information may be cause for rejection of the offer.

The pre-award survey may include performance of a formal financial capability risk assessment or an audit by the Defense Contract Audit Agency (DCAA) or other personnel assigned by the PCO to perform the task. This effort would be performed in accordance with DFARS 232.072-1 and the information required for an audit would include, but not be limited to, the information identified in DFARS 232.072-2. The contractor agrees to provide the financial information for such financial capability effort in a timely manner. The Offeror shall provide information regarding its cognizant DCAA office, to include point of contact, telephone number, and email address. Failure to provide the requested data could cause the Offeror to be determined financially irresponsible as discussed in FAR 9.103(b).

1.9 DISCREPANCIES

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

1.10 EVALUATION NOTICE (EN)

If any additional exchanges are required, a written EN will be sent to the Offeror. Offerors will be allowed sufficient time to submit written responses.

1.11 EVALUATION

The selection of a source for award purposes will be conducted using source selection (negotiated) procedures as delineated in FAR Part 15.3. Proposals will be evaluated IAW Section M of the RFP, Evaluation Factors for Award.

The Offeror’s responses to this RFP will be used as a validation tool for the Offeror’s capabilities in reference to, and understanding of, the mission capability factors. Failure to comply with the RFP will render the proposal unacceptable, and may eliminate the proposal from consideration for contract award.

1.12 NOTICE OF PRE-PROPOSAL CONFERENCE/SITE VISIT

1.12.1 A site visit will be held at MICC-Fort Carson at 1676 Evans St., Bldg 1219, Room 311A (Sunlight Conference Room), Fort Carson, Colorado on 22 June 2016 beginning at 9:00 a.m. MDT if the Government receives a response that at least one Offeror intends to be present. The purpose of the site visit is to allow Offerors to see the site and to allow Offerors to make notes of questions for submission to the Contracting Officer at a later date. At the conclusion of the site visit, there will be a Pre-Proposal Conference. The Pre-proposal Conference will be held in building 1219, Room 311A (Sunlight Conference Room). Prospective Offerors are highly encouraged to attend site visit and the Pre-proposal Conference. Remarks and explanations at the site visit/conference shall not change the terms of the RFP. Any change to the RFP terms will be conveyed through an amendment to the RFP. Failure to attend the site visit or Pre-Proposal conference will not disqualify the Offeror; however, the Offeror acts at its own risk and will not be relieved from complying with the terms and conditions of any resultant contract by reason of such failure. In no event will a failure to inspect the site constitute grounds for a claim after award of a contract.

For the period of 21 June 2016 thru 22 June 2016, a message can be left for Renee M. Krahenbuhl, Contract Specialist, at (719) 526-1767. This number will not be continuously manned. However, messages will be retrieved periodically throughout 21 June 2016 thru 22 June 2016. After 22 June 2016, interested parties shall not use that number in reference to this RFP.

1.12.2 Offerors are limited to three (3) attendees due to limited conference room space. Offerors must notify Renee M. Krahenbuhl, Contract Specialist, by electronic mail (usarmy.jblm.acc-micc.list.proposals@mail.mil) not later than 12:00 p.m. MDT on 17 June 2016, if attending the pre-proposal conference. Include in the Subject Line:

“W911RZ-15-R-0002, Site Visit.” Notification shall include full name, company, email address and phone number.

If no response is received, the conference may be cancelled. No other pre-proposal conference will be scheduled.

Attendance is at the expense of the Offerors. The Government cannot guarantee access to Fort Carson at any other time.

1.12.3 Attendees must arrive on time to be included in the site visit/conference. The visit will start promptly at 9:00 a.m. and anyone arriving after that time will be denied admission. Be advised that Fort Carson is a limited access installation, and people entering its gates are subject to entrance requirements and possible search. Attendees must arrange their travel to accommodate for these procedures. It is the responsibility of the Offeror to gain access to the Government installation. Unless some form of Department of Defense identification is provided, all drivers must provide a valid photo driver’s license, current vehicle registration, proof of vehicle insurance and enter through Gate 1 if driving a privately-owned vehicle and Gate 3 if driving a company-owned vehicle. Attendees entering through Gate 1 need to go to the Visitor Control Center (Bldg. 6012) to receive a visitor's pass prior to entry through the gate.

1.12.4 Comments and/or questions are prohibited to be asked during the conference/site visit. Offerors are to submit all comments and/or questions in writing to be answered at a later date. This will ensure all Offerors have the same opportunity to receive a correct and accurate answer. This also removes any risk of an incorrect answer being provided verbally without first verifying its accuracy. All comments and/or questions must be submitted via a SINGLE email per Offeror, preferably in a Microsoft Word document attached to the e-mail. Submit to the point of contact in paragraph 1.12.2 above no later than 4:00 p.m. MDT on 28 June 2016.

1.12.5 At the site visit/conference there will be no cameras, audio recordings, or videotaping or other recordings allowed except that done by the Government. Cell phones with cameras are allowed but no pictures are permitted to be taken.

2.0 PROPOSAL FORMAT AND PREPARATION INSTRUCTIONS

2.1 PROPOSAL FORMAT

In order to maximize efficiency and minimize the time for proposal evaluation, the paper proposal (and electronic proposal if printed) shall meet format requirements. The proposal shall be limited to the submission of the volumes specified in Table 3.1.1 below. Each volume shall be separately bound in three-ring loose-leaf binders, within the required page limits, and with the specified number of copies.

2.1.1 TEXT

Text type shall be Times New Roman. Except for the reproduced sections of the RFP document, the text size (font) shall be no less than 12-point with normal proportional spacing. Text lines shall have 1.5 line spacing. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

2.1.2 PAGE LIMITATIONS

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will not be returned to the Offeror. For electronic CD-ROM submission, no hidden fields, macros, comments will be read. All information shall be written clearly and be easily accessible. Page limitations may also be placed on ENs, if required. The page limitations for ENs, if any, will be identified in the correspondence forwarding the ENs to the Offerors. When both sides of a sheet of paper display printed material, it shall be counted as two pages. Each volume shall contain a detailed table of contents to delineate what is in the respective volume, which will not be counted in the page limits. In addition, the following will also not be counted in the maximum page limits: cover pages, tabs, cross-reference matrix, and glossaries. The page limitations specified in Table 3.1.1 shall be treated as maximum limits to assist in the evaluation of each proposal.

2.1.3 PAGE SIZE

A page is defined as each face of a 8 ½ x 11-inch sheet of paper containing information (excludes such things as blank pages, title pages, table of contents, tabs, dividers, glossaries, and indices). Page margins shall be a minimum of 1-inch each for the top, bottom and sides. All material must be contained within the page limits identified for each volume or appendix. The background color of each page of the proposal submission shall be white or ivory paper only. If Final Proposal Revisions (FPR) are required, the same initial proposal page limitations apply for each volume or appendix. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs, and to both electronic and hard copy proposals.

2.1.4 TABLES, CHARTS, GRAPHS, AND FIGURES

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and/or task layout, schedules, plans. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size when printed. Foldout pages shall fold entirely within the volume and count as two (2) pages. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point. Text lines in all tables, charts, graphs, and figures shall have single (1) line spacing. All tables, charts, graphs and figures will be included in the page count. Any tables, charts, graphs and/or figures containing smaller than Times New Roman 10 point font will be disregarded. This restriction applies to both electronic and hard copy proposals. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.1.5 TAB INDEXING

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tabs/indexes will not count against the page limitations for the respective volume.

2.1.6 GLOSSARY OF TERMS

Each volume shall contain a glossary of all abbreviations, acronyms and/or terms used, with explanation corresponding definition for each. Glossaries do not count against the page limitations for their respective volumes.

2.1.7 BINDING AND LABELING

Each volume shall be separately bound and labeled in standard three-ring, loose leaf binders, and clearly identified on the front and side. The binders should permit the volume to lie flat when open, and allow for easy removal and replacement of pages. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, RFP number and the Offeror's name. The same identifying data should be placed on the spine of each binder. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Offeror Bid or Proposal Information and Source Selection Information.

2.1.8 ELECTRONIC MEDIA OFFERS AND SUBMISSION

2.1.8.1 To enable the Government to successfully view the proposals electronically, the Offerors shall submit their proposals in Microsoft Office, i.e. Microsoft Word or Microsoft Excel format. These file formats shall be exact duplicates of the paper copies. The Government will use the electronic copies in the evaluation process. The Government may use the electronic/CD proposal for all purposes; however, there is no requirement for the Government to compare or verify the consistency of the electronic proposal to the paper proposal. In the case of an identified dispute or variation in content, the electronic submitted proposal shall be deemed and treated as the official version for all purposes. Each CD-ROM case and the CD-ROM itself must be labeled as to the Offeror and numbered sequentially in the required number of copies.

2.1.8.2 File Preparation. All text, including table and figure identifiers, shall be indexed and 100% searchable text using Microsoft Word. All text shall be displayed as a font and not displayed as a bitmap in any proposal volume or appendix to facilitate the ability to copy and paste to another document.

2.1.8.3 Font and Page Setup. Text font and layout shall be as stated for paper copies.

2.1.8.4 Other Requirements. The Offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible.

2.1.8.5 Proposal Format and Structure. Each volume of the electronic proposal shall be in its own subdirectory on the CD-ROM, sequentially labeled Volume I through Volume III. Volume IV, Cost/Price, shall be submitted on a separate CD-ROM.

2.1.8.6 Proposal Table of Contents file. This file serves as a table of contents for the proposal information.

Also, include the list of key terms used in the proposal with their definitions, and a list of acronyms and abbreviations used in the proposal.

2.1.8.7 Cost/Price Data File. Submit an electronically encoded cost/price model in support of the proposed cost/price. Any cost/price model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. Formulas shall not be hidden and all links cannot exist to files not included with the submission. The Offeror’s submittals shall be free of viruses, Trojans, spyware, and other malicious code for which appropriate detection and removal/quarantine software exists. Cost/price models submitted must comply with the following format requirements:

Data file should be submitted on a CD.

Data file should be .XLS file format (MS-Excel 2013 or earlier) compatible format.

2.1.8.8 Viewing Environment. The Government anticipates viewing the electronic submittals with the following computer software and hardware: 1) IBM-compatible systems, 4.0 GB of RAM, nominal 19 inch color monitors, and standard CD ROM readers, 2) Windows 7 operating system, 3) Microsoft Office 2013, and Internet Explorer 8.0.

2.1.9 ELECTRONIC REFERENCE DOCUMENTS

All referenced documents for this RFP are available at the Federal Business Opportunities (FedBizOpps) website at http://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.

2.1.10 COST/PRICE INFORMATION

All cost/price information shall be addressed ONLY in the Cost/Price and/or the Contract Documentation Volumes.

References to work hour estimates and material may be addressed in other volumes only as appropriate for justifying labor hours and material.

2.1.11 CLASSIFIED INFORMATION

Proposals shall not contain classified information.

3.0 PROPOSAL VOLUME INSTRUCTIONS AND OTHER REQUIRED DOCUMENTATION

3.1 VOLUMES

Offers will consist of four (4) separate proposal volumes: General & Contract Documentation, Mission Capability, Past Performance, and Cost/Price.

3.1.1 PROPOSAL VOLUMES ORGRANIZATION, NUMBER OF COPIES, AND PAGE LIMITS

The Offeror shall prepare the proposal as set forth in Table 3.1.1 and these instructions. The titles and contents of the volumes shall be in accordance with Table 3.1.1. “Original” designates paper/printed submission. In the event that Final Proposal Revisions are required, the Offer shall clearly indicate the revision number within the Volume Name. (Revision X with X indicating the number of the revision.)

Table 3.1.1 - Proposal Organization

VOLUME VOLUME TITLE NO. OF HARD NO OF DIGITAL PAGE LIMIT DIGITAL

COPIES COPIES FORMAT

I General & Contract Documentation 1 Original 2 CD-ROMs No Limit Microsoft

Word

II

Mission Capability

- Technical Understanding

- Management and Organization Plan

- Staffing and Workforce Management

Plan

1 Original + 4 Copies

2 CD-ROMs 75 pages total

Microsoft Word

III Past Performance 1 Original + 2

Copies 2 CD-ROMs See Para 8.0

Microsoft Word

IV Cost/Price 1 Original + 1

Copy 2 CD-ROMs No Limit

Microsoft Excel

4.0 RECEIPT OF PROPOSALS

4.1 Proposals are due 1:00 p.m. MDT on 12 July 2016, and shall be submitted in accordance with the instructions herein. Late proposals may be rejected from consideration IAW FAR 15.208. It is the Offeror’s responsibility to confirm the Government has received the proposal.

4.2 All proposals delivered in response to this RFP shall reflect the following in the address label:

RFP Number: W911RZ-15-R-0002 The Legend. “TO BE DELIVERED UNOPENED TO THE CONTRACTING OFFICER,” and The volume copy numbers contained in the each box.

4.3 Proposals shall be submitted prior to the closing date and time identified on SF33 to the following address:

Regular mail/Express Carrier/Hand Carried:

Mission and Installation Command (MICC) ATTN: Renee M. Krahenbuhl 100 COL Joe Jackson Blvd, Ste 2001 Joint Base Lewis-McChord, WA 98438

4.4 Electronic submissions via email or facsimile will not be accepted. Offers shall be mailed through a commercial/Government carrier or hand carried.

5.0 RESERVED

6.0 VOLUME I – GENERAL & CONTRACT DOCUMENTATION

6.1 Volume I must be clearly marked “VOLUME I - GENERAL & CONTRACT DOCUMENTATION, RFP W911RZ-15-R-0002.” Offerors are required to submit a completed SF 33 (Solicitation, Offer and Award) (including acknowledgment of all Amendments), Section B, Section K, and Section I. All final monetary extensions shall be in whole dollars only (to include unit prices). The General Volume shall be organized as follows and contain the identified information.

6.1.1 TAB A, Signature by the Offeror on company letterhead constitutes an offer the Government may accept.

The “original” copy shall be clearly marked under a separate cover and shall be provided without any punched holes. The letter shall also include the acceptance period of no less than 180 days after the date specified for receipt of offers during which the Government may accept the offer to create a binding contract. Offerors providing less than 180 days for Government acceptance after the date offers are due will not be considered and will be rejected.

6.1.2 TAB B, The Offeror shall provide the company/division's street address, county and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area designation, if applicable. This same information must be provided if the work for this contract will be performed at any other location(s).

6.1.3 TAB C, Solicitation, Offer and Award - The SF33 shall be submitted fully completed. The Offeror is cautioned that the SF33 must contain an original signature in block 17 of the form. The Offeror shall acknowledge any amendments to the RFP in accordance with the instructions on the SF33 and with Section L, FAR 52.215-1(b), Instruction to Offerors—Competitive Acquisition. The Offeror shall provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror’s company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.1.4 TAB D, RFP Section B (Supplies or Services and Prices) - Section B of the RFP shall be submitted fully completed and error free. Offerors shall propose an estimated cost and fixed fee for each CPFF CLIN and a firm fixed price for the FFP CLIN in Section B. The Government has stated the ceiling cost for Other Direct Costs (ODC) and Material, fee will not be paid on materials and ODCs; funding and ceiling amount will be included on the contract when awarded. The Offeror shall ensure that the Prices/Costs are supported by Attachment #16. As part of its proposal, the Offeror will provide the price (if any) incurred to comply with the enterprise Contractor Manpower Reporting Application (eCMRA) requirement. Offeror will determine, in the Schedule, CLINs X012, to price or not-separately-price the CMRA requirement. CLINS X012 shall be the CLINs under which the Contractor shall bill for the price of the eCMRA requirement. The Offeror shall price the CMRA CLIN as a firm-fixed price CLIN. The Offeror shall complete the "Contract Estimated Totals" table located in Section B of the RFP.

6.1.5 TAB E, Complete the DD Form 254 (Contract Security Classification Specification). DD Form 254 is located in Section J as Attachment 4.

6.1.6 TAB F, RFP Section K (Representation, Certifications, and Other Statements of Offerors) – The Offeror shall ensure that Section K of the RFP is submitted thoroughly completed with all blocks in each certification/representation completed truthfully and completely.

6.1.7 TAB G, RFP Section I (Contract Clauses) – The Offeror shall ensure that all applicable Section I clauses/provisions in the RFP that require the Offeror to complete fill-in information are submitted and thoroughly completed with all blocks filled in with accurate and complete information.

6.1.8 TAB H, DCAA information as required in paragraph 1.8. of Section L – Instructions, Conditions and Notices to Offerors.

6.1.9 TAB I, Exceptions/Assumptions (if required) - Identification and explanation of any exceptions or deviations. Additionally, any assumptions used in the proposal preparation must be identified. Also, include any other data the Offeror chooses to bring to the attention of the PCO. See paragraph 10.0. of Section L – Instruction, Conditions and Notices to Offerors..

7.0 VOLUME II – MISSION CAPABILITY

7.1 GENERAL

Volume II must be clearly marked “VOLUME II – MISSION CAPABILITY, RFP W911RZ-15-R-0002.” The purpose of the Mission Capability Volume is to provide the Government information about the Offeror’s management and technical approach in the performance of the Fort Carson Base Operations Services requirement.

The Offeror’s Mission Capability proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The Offeror’s Mission Capability proposal shall provide as specifically as possible the actual methodologies and system that will be used to accomplish/satisfy the Fort Carson Base Operations Services requirement. All the requirements specified in the RFP are mandatory. Through proposal submission, the Offeror represents that it will fulfill the requirements specified in the RFP; therefore, it is not necessary or desirable for an Offeror to state this in the proposal. Offerors shall not merely reiterate the objectives or reformulate the requirements specified in the RFP. The Mission Capability Proposal shall not include cost/price information, classified information, or "For Official Use Only" information. Evaluation will be against the Mission Capability evaluation factors as specified in the Evaluation Factor for Award section of this RFP.

7.2 FORMAT AND SPECIFIC CONTENT

In the Mission Capability volume, Offerors shall address their proposed approach to meeting the requirements of each evaluation subfactor.

7.3 VOLUME ORGANIZATION

The Mission Capability volume shall be organized according to the following general outline:

Table of Contents List of Table and Drawings Cross Reference Matrix Glossary TAB A: Sub-factor 1 – Technical Understanding TAB B: Sub-factor 2 – Management and Organizational Plan TAB C: Sub-factor 3 – Staffing and Workforce Management Plan

7.3.1 SUBFACTOR 1: TECHNICAL UNDERSTANDING

The Offeror shall describe its Technical Understanding to satisfy the Government’s requirements as follows:

7.3.1.1 The Offeror shall describe and explain its understanding of each functional area below by providing an overarching description of each area, including any applicable critical systems (PWS C.5.1.1), associated risk, and required maintenance plans IAW PWS C.5.3.2. Offeror must identify at least one risk per functional area and its plan to mitigate said risk. Each area description will be annotated by the applicable PWS Section it pertains to.

1. Financial Requirements

2. Demand Maintenance Orders

3. Operation and Maintenance Plans

4. Transportation System Maintenance and Repair

5. Electrical System Maintenance and Repair

6. Central Heat Plant

7. Fire Suppression Systems

8. Central Cooling Plant

9. Energy Management Control System

10. Natural Gas Distribution System

11. Sewage Treatment Plant

12. Potable Water System

13. Cathodic Protection

7.3.1.2 The Offeror shall describe how it will utilize proposed processes, procedures and approaches, and innovations for cost savings and efficiencies over the life of the contract, including use of innovations for process reengineering, emerging technologies and management of cross-organizational processes.

7.3.1.3 The Offeror shall provide notional Operations and Maintenance Plans IAW C.5.3.2 of the PWS for the Electrical Systems Maintenance and Repair, Industrial Waste Water Treatment Plant, and Facilities Maintenance and Repair functional areas. The page limit for each plan is five pages. This page limit does not count against the page limit indicated in Table 3.1.1 Volume II.

7.3.2 SUBFACTOR 2: MANAGEMENT AND ORGANIZATIONAL PLAN

The Offeror shall describe its Management and Organizational Plan (including team structure) to satisfy the Government’s requirements as follows:

7.3.2.1 The Offeror shall submit a detailed organizational chart and narrative that includes its organizational structure; provides oversight of all functional areas contained in the PWS (This is applicable to all PWS functional areas); identifies the key personnel, the qualifications of those positions, responsibilities, and their resumes; and explains what parts of the organization are responsible for what work (identifies each organizational element, i.e., Division/ Branch/ Team, and what work they are responsible for managing and accomplishing; where decision making authority lies within the organization; and describes the work performed by teaming partners).

7.3.2.2 The Offeror shall explain the process it will employ to ensure workflow processes have lines of communication for each major functional area in the PWS between the prime and teaming partners that enable seamless performance.

7.3.2.3 The Offeror’s proposal shall describe and explain how it will adjust to changing priorities, timeliness and effectiveness of services rendered. The Offeror’s proposal shall describe and explain its methodology to support changing command priorities. The proposal shall explain how the Offeror will reprioritize the work and how it intends to reintegrate the interrupted work back into the services.

7.3.2.4 The Offeror shall show how the quality control (QC) approach manages the project at the service order level and explain how they will implement a stand-alone QC plan that validates the services and integrates subcontractors. The Offeror shall describe and explain how its quality control approach will fit into the organization at a level demonstrating the Offeror’s commitment to a quality organization and that the proposed Quality Control Manager is autonomous from the local Program Manager (PWS C.1.5.1.1).

7.3.2.5 The Offeror shall describe and explain its proposed interface (vertical and horizontal communication) between on-site project management and off-site corporate management to accomplish the mission. Additionally, it shall describe and explain its interface with the Government (corporate, project teams, Government project managers, contracting officials, inspectors, and users) to ensure smooth mission accomplishment and cooperation with all team members.

7.3.2.6 The Offeror shall provide an overview of its plan for government-furnished and contractor-acquired property management. The Offeror shall identify any customary practices or industry-leading practices and standards to be used by the Offeror in managing Government property. The Offeror shall submit a list or description of all Government property that the Offeror or its subcontractors propose to use. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property). The list shall include the dates during which the property will be available for use (including the first, last, and all intervening months) and, for any property that will be used concurrently in performing two or more contracts.

7.3.3. SUBFACTOR 3: STAFFING AND WORKFORCE MANAGEMENT PLAN

The Government will provide baseline staffing data, which will include required certifications, training, and licenses. The Offeror’s Staffing Plan shall describe and explain how its plan will relate to the Offeror’s understanding of the technical requirements to ensure it contains the appropriate labor mix and hours by functional area in the PWS. Rationale for deviations from the base line data shall be fully described. The Offeror’s proposed staffing must be consistent with the staffing addressed in the Cost volume. The Offeror’s proposed key personnel labor categories and position descriptions shall describe and explain Offeror's understanding of the scope of duties, levels of responsibilities and performance levels required to effectively manage the services for this requirement as stated in the solicitation. The Offeror shall describe its Staffing and Workforce Management Plan to satisfy the Government’s requirements as outlined in section 7.3.3.1 through 7.3.3.5.

7.3.3.1 Based on base line staffing data (excluding management and administrative staff) and manning levels by labor category provided by the Government in Attachment #21, the offeror shall provide its management approach or deviations from the Government’s baseline that result in realized efficiencies and improvements to the PWS requirements. The Offeror’s unique management approach and efficiencies shall be fully explained and justified, keeping in mind that the Government is interested in a management approach that results in continuous improvements and efficiencies that are expected to be reflected in the Mission Capability and Cost proposal.

7.3.3.2 Based on historical base line staffing data provided by the Government, the Offeror shall depict staffing for performance by providing manpower matrices for each functional area in the PWS depicting the proposed total overall manning (total number of Full Time Equivalents [FTEs]) by work years and labor category and describe their approach for each functional area of the PWS. Provide the key personnel labor categories and position descriptions. This document shall not include any pricing information. The Offeror shall not include resumes for this area, only the position description as stated above.

7.3.3.3 The Offeror's Staffing Plan shall describe the organizational structure of its team, including all subcontractors, teaming partners, joint ventures, etc. for this requirement. For each planned subcontractor/teaming member, provide a brief description of the abilities the subcontractor/teaming member will provide and/or work it will perform.

7.3.3.4 The Offeror’s proposed staffing and manpower matrices must be consistent with the staffing addressed in the Cost volume. The Offeror shall describe and explain its cross walk between the technical and Cost volume.

7.3.3.5 The Offeror shall describe and explain how it will to recruit, hire, retain (to reduce employee turnover) and manage personnel with the knowledge, skills, education, experience, and applicable position descriptions, certifications, training (to include refresher training), and licenses required to perform the services the positions (including unique and emerging technology used in specialty areas) identified in the base line staffing data.

8.0 VOLUME III – FACTOR 2: PAST PERFORMANCE

8.1 Volume III must be clearly marked “VOLUME III – PAST PERFORMANCE, RFP W911RZ-15-R-0002.”

The Past Performance evaluation will be accomplished by reviewing aspects of an Offeror's recent and relevant Past Performance, focusing on and targeting performance that is relevant to the effort as it directly relates to the work being procured under this solicitation and as defined in Section M.

8.1.1 Content Of Past Performance Volume.

The Offeror’s Past Performance Volume shall contain the following and be within the specified page constraints.

Additional detail for submission requirements is included in para 8.2.3.

Item Page Limit Exclusions From Page Limitation

Table of Contents Glossary

No Page Limit None

Summary Page Describe the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner.

Five (5) pages None

Organizational Structure Change History Three (3) pages Pre-published items such as brochures, flyers, reference articles, etc. are excluded

Consent/Client Authorization Letters No page limit None

Specific Relevant Contract Reference Sheets Five (5) pages each None List of Questionnaire Recipients No page limit None

8.1.2 Early Proposal Information. In order to expedite evaluations, Offerors are encouraged, but not required, to submit their Past Performance Volumes any time prior to the closing of the RFP, to the Contracting Officer at the address specified in paragraph 4.3.

8.2 Past Performance information described herein is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform 10% or greater of the proposed effort based on the total proposed cost/price. The Offeror shall submit, along with the information required in this paragraph, a consent letter, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

8.2.1 The Offeror shall include documentation regarding their relevant past performance as it directly relates to the work being procured under this solicitation. The Offeror SHALL NOT go back any farther than three (3) years for the submitted data from the date in Block 5 of the SF33. The past performance data shall document a successful history of past contract performance.

8.2.2 NOT USED

8.2.3 Submission Requirements. The Offeror shall submit a Past Performance Volume containing the following:

8.2.3.1 Table of Contents

8.2.3.2 Summary Page describing the role of the Offeror and each subcontractor, teaming partner, and /or joint venture partner that the Offeror is required to provide Past Performance Specific Relevant Contract Reference Sheets for the past performance experience in accordance with Attachment 18.

8.2.3.3 Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing the release of past performance information so the Offeror can respond to such information. A sample consent letter is attached as Attachment 17.

8.2.3.4 Client Authorization Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance.

8.2.3.5 Organization Structure Change History— 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 present or 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 your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

8.2.3.6 Specific Relevant Contract Reference Sheet - Sheets in accordance with Attachment 18 and are limited to 5 pages per reference. The Offeror shall provide documentation outlining the Offeror’s past performance with contracts, as a prime or major subcontractor, which is the same or similar in nature of work, size, scope and complexity to the services being procured under this Solicitation. The submittal shall include rationale supporting your assertion of relevance and how it was determined that the work performed previously was the same or similar in nature, size, scope and complexity to the work specified by this solicitation. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. The Offeror shall submit a minimum of five (5) but no more than a total of eight (8) Specific Relevant

Contract Reference Sheets identifying active or completed contracts, either Government or commercial. Limits on Specific Relevant Contract Reference Sheets are as follows:

8.2.3.6.1 Three (3) sheets identifying active or completed contracts, either Government or commercial, for the prime, team, and/or joint venture (within the same division or cost center)

8.2.3.6.2 Two (2) sheets from each subcontractor who will be completing 10% or more of the technical work.

8.2.4 Past Performance Questionnaire - See Attachment 19, Past Performance Questionnaire. For the contracts identified on each Specific Relevant Contract Reference, the Offeror shall forward a copy of the Past Performance Questionnaire to the points of contact responsible for monitoring performance under such contracts. The points of contact shall return the questionnaires directly to Renee M. Krahenbuhl, Contract Specialist, not later than the proposal due date and time. Any questionnaires not returned directly to the Contract Specialist will not be reviewed and evaluated. The information contained in the questionnaires will be used to evaluate the Offeror’s past performance. New entities that have no past customers shall annotate on the Summary Page that they have had no previous clients and that questionnaires cannot be provided.

8.2.4.1 Offerors shall provide a summary list of questionnaire recipients to include POCs and phone numbers.

9.0 VOLUME IV – FACTOR 3: COST/PRICE

9.1 GENERAL

A separate cost proposal must be submitted using cost summary format provided. The transition phase-in, base year and each option year shall be segregated.

9.1.1 COST/PRICE REASONABLENESS AND REALISM

These instructions provide the Offeror guidance in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness and realism of their proposed cost/price. Failure to comply with such guidance may result in rejection of your proposal. The cost proposal shall be sufficiently detailed to the reasonableness and realism of the proposed costs plus fixed fee.

9.1.2 COST/PRICE INFORMATION

All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

9.1.3 COST OR PRICING INFORMATION REQUIREMENTS

9.1.3.1 A request for Certified Cost or Pricing Data is not anticipated for the award of this contract since adequate competition is expected; however, the Government reserves the right to request such information should it become necessary consistent with Federal Acquisition Regulation (FAR) Subpart 15.4, Contract Pricing.