W911S8-15-R-0004_Amendment_2_MATOC.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 reason for this amendment is to add the Read ID Act of 2005 information into section L, Paragraph 1.11.4. The addition is highlighted in yellow .

1. CONTRACT ID CODE PAGE OF PAGES

J 1 14

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

16C. DATE SIGNED

BY 04-May-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 W911S8-15-R-0004

X 9B. DATED (SEE ITEM 11)

25-Apr-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 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

04-May-2016

CODE

MICC

MISSION AND INSTALLATION CONTRACTING COMMAND

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:

W911S8-15-R-0004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

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.

The Government will evaluate proposals solely on the basis of the information contained within it and the Government will not assume that an Offeror possesses any capabilities not specified. The Offeror shall explain inconsistencies among the parts of each proposal. 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 its 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.

1.1 POINT OF CONTACT

Offerors shall address all questions, concerns, or clarifications to the Procuring Contracting Officer (PCO) listed below as the sole point of contact for this acquisition. Offerors must make all inquiries in writing and submit them electronically to the Contract Specialist with a copy to the PCO. 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 (JBLM), Washington 98438 Phone—(253) 982-0468 Email : renee.m.krahenbuhl.civ@mail.mil and 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 (JBLM), Washington 98438 Phone—(253) 982-9888 Email : linda.j.murphy.civ@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 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 the Offeror’s proposal and information obtained through sources identified in past performance paragraph 8.1.2. The Offeror is reminded that the Government intends to award this contract based on the initial proposal, as received, without discussion.

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 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.7 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 Part 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. Failure to provide the requested data could cause the Offeror to be determined financially irresponsible as discussed in FAR 9.103(b).

1.8 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.9 EVALUATION NOTICE (EN)

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

1.10 EVALUATION

Proposals will be evaluated in accordance with (IAW) Section M of the RFP, Evaluation Factors for Award. The Government will use the Offeror’s responses to this RFP as a validation tool for the Offeror’s capabilities in reference to, and understanding of, the requirement. Failure to comply with the RFP will render the proposal unacceptable, and may eliminate the proposal from consideration for contract award.

1.11 PRE-PROPOSAL CONFERENCE & SEED PROJECT SITE VISIT

1.11.1 The Government will hold a pre-proposal conference and site visit at Building 2015 in the Dallas Conference Room (Room 140), at Joint Base Lewis-McChord (JBLM), Washington on 10 May 2016 beginning at 1:00PM PDT. Attendance is at the Offeror’s expense. All interested firms may attend with a limit of two (2) attendees per firm due to limited conference room space. Please submit, in writing, the names of attendees and any questions they may have in advance by e-mail to Contract Specialist Renee M. Krahenbuhl at usarmy.jblm.acc-micc.list.proposals@mail.mil and renee.m.krahenbuhl.civ@mail.mil prior to 4 May 2016 at 2:00PM PDT. Offeror shall be prepared to provide its own transportation to and from the pre-proposal conference location and the site visit location.

1.11.2 Offerors or vendors are urged and expected to inspect the site where the work will be performed and to satisfy themselves regarding all general and local conditions that may affect the cost of contract performance, to the extent that the information is reasonably obtainable, and to attend a preproposal conference. The purpose of the conference is to eliminate any possible misunderstandings of the terms of the RFP. Comments and/or questions during the conference/site visit will not be answered at the conference. 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 gathered and submitted via a SINGLE email per Offeror, preferably in Microsoft Word documents attached to e-mail to the points of contact in paragraph 1.11.1 above no later than 18 May 2016 at 2:00 PM PST. If responses to technical questions affect the Statement of Work (SOW) requirements or any other portion of the RFP, the Government will issue an amendment to the RFP; the RFP will remain unchanged unless the Government amends the RFP in writing.

1.11.3 In no event shall failure to inspect the site constitute grounds for a claim or adjustment after contract award.

1.11.4 To gain access to JBLM-Main and JBLM-North, if you do not have a contractor’s badge, you must obtain a visitor’s pass from the Visitor’s Center immediately outside the Liberty Gate. Take exit 120 off Interstate 5 and proceed toward the Liberty Gate. Just prior to the Liberty Gate, turn right into the Visitor’s Center parking lot. At the Visitor’s Center service window, state that you need a one (1)-day pass to attend a meeting at the Mission and Installation Contracting Command, Fourth Avenue, Building 2015, Room 140. For a one (1)-day pass, no prior arrangements are necessary and none have not been made. Allow plenty of time to process through the Visitor’s Center because it can be quite busy. To obtain the vehicle pass, the driver of the vehicle must present a valid driver’s license with picture, proof of current vehicle insurance, and valid vehicle registration. All passengers in the vehicle must also enter the Visitor’s Center and present a photo ID. Each passenger’s name will be entered on the vehicle pass in addition to the driver’s name. At the Liberty Gate entrance, guard personnel will check the vehicle pass along with the photo IDs of the driver and all passengers.

Driving directions to Building 2015 Once on post proceed to the 3rd light, make a right onto Pendleton Avenue.

On Pendleton go through 3 lights; Fourth Avenue is to your left.

You may turn onto Fourth Avenue, parking is allowed on either side of the street. There is also a parking lot on the side of Building 2015, a parking lot between building 2015, and the other buildings in the quad. There is also parking across Pendleton. The parking areas on the street and in the quad are mostly open access, but they fill up quickly in the morning with employees; across the street parking is usually available throughout the day. As you face the front of the building, Room 140 (Dallas Conference Room) is on the first floor in the left wing.

On 1 May 2016, JBLM began enforcing the provision of the Real ID Act of 2005. Under provisions of this act, a standard driver’s license or ID card issued by any of the following states is not accepted for unescorted access to JBLM: Illinois, Minnesota, Missouri and Washington. Persons requesting unescorted access to JBLM and who present a standard license or ID from one of those states will be required to present additional documentation to verify their identity prior to being allowed access to JBLM. The list of acceptable documents to present along with a standard driver’s license or ID Card issued by one of those states include: DoD CAC, DoD Uniformed Services Identification and Privileges Cards, U.S. Passport or U.S. Passport Card, VA Issued Health Card, U.S. Coast Guard Merchant Mariner Card, Transportation Worker ID Card (TWIC) issued by DHS, U.S. Government issued, authenticated Federal PIV credentials. US Military or Draft Record containing name and DOB. A full list can be found http://www.lewis-mcchord.army.mil/ under Access to JBLM. The Washington State enhanced driver license is acceptable.

1.11.5 If no one provides notice of attendance, the preproposal conference and site visit will be canceled. No other site visits or preproposal conferences will be scheduled or authorized.

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 IV. Volume IV, 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 the Offeror’s approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. Formulas and tabs shall not be hidden and all links must link successfully to its intended target. 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 2007 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 2007, and Internet Explorer 8.0.

2.1.9 ELECTRONIC REFERENCE DOCUMENTS

All referenced documents for this RFP are available at the Army Publishing Directorate at http://www.apd.army.mil/.

2.1.10 PRICING INFORMATION

All pricing 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, Technical Proposal, Past Performance, and 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.

Table 3.1.1 - Proposal Organization

VOLUME VOLUME TITLE COPIES PAGE LIMIT

I General & Contract Documentation Original + 1 No Limit

+ 1 CD-ROM

II

Technical Proposal

- Management Approach

- Experience

- Seed Project

Original + 1 +1 CD-

ROM

Total 60 (Experience- 30 Pages; Management approach and Seed Project – 30 Pages)

III Past Performance Original + 1

+ 1 CD-ROM

See Para 8.0

IV Price Original + 1

+ 1 CD-ROM

No Limit

4.0 MAILING REQUIREMENT FOR SPECIAL MARKING OF PROPOSAL

4.1 Envelopes or other cover for material submitted in response to this RFP shall be opaque, and must be so presented that they may easily be identified. Offerors shall ensure that the sealed envelope or package used to submit the proposal shows the postmark time and date of receipt by the postal service, the RFP number, and the name and address of the Offeror.

4.2 Offerors shall ensure that mailed proposals (USPS, FedEx, UPS, DHL, etc.) are sent to the following address:

Mission & Installation Contracting Command-JBLM Attn: Renee M. Krahenbuhl 100 COL Joe Jackson Blvd, Ste 2001 Joint Base Lewis-McChord (JBLM), Washington 98438

4.3 Hand-delivered proposals will conform to all of the requirements in the above section 4.0. The Offeror shall deliver the proposal to the contracting office identified in paragraph 4.2 above. It is the Offeror’s responsibility to ensure the sealed proposal package is marked with the date and time the proposal was accepted.

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 BIDDER’S LIBRARY

There will not be a physical Bidder’s Library. All unclassified Bidder documents including SOW attachments are available on the FedBizOpps website. All referenced publications for this RFP are available at the Army Publishing Directorate at http://www.apd.army.mil/.

6.0 VOLUME I – GENERAL & CONTRACT DOCUMENTATION

6.1 Volume I must be clearly marked “VOLUME I - GENERAL & CONTRACT DOCUMENTATION, RFP W911S8-15-R-0004.” Offerors are required to submit a completed SF 1442 (Solicitation, Offer and Award) (including acknowledgment of all Amendments), Section B, and Section K. 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 SF 1442 Solicitation, Offer and Award. The SF 1442 shall be submitted fully completed. The Offeror is cautioned that the SF 1442 must contain an original signature in block 20B of the form. Ensure the following blocks are completed:

14 – Name and Address of Offeror (include DUNS number, CAGE Code, Tax-ID number, and address) 15 – Telephone No. (Include area code) 19 – Acknowledgment of Amendments 20A – Printed name and title of signer

20B – Signature of Offeror/Contractor (must contain an original signature) 20C – Offer Date

6.1.2 SF 30 Amendment of Solicitation. The Contractor shall acknowledge any amendments to the RFP in accordance with the instructions on the SF 30 and with Section L, FAR 52.215-1(b), Instruction to Offerors— Commercial Items. Ensure the following blocks are completed:

8 – Name and Address of Contractor 15A – Printed Name and Title of Signer 15B – Signature of Contractor/Offeror (original signature required) 15C – Date signed

6.1.3 Authorized Representatives. The Offeror shall provide a letter signed by an officer of the company, on company letterhead, which identifies the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.1.4 Section K Representation, Certifications, and Other Statements of Offerors. The Offeror shall ensure that Section K is submitted thoroughly completed with all blocks in each certification/representation completed truthfully and completely. System for Award Management (SAM) is an e-Government initiative that consolidates the capabilities previously found in the Central Contractor Registration (CCR) and Online Representations and Certifications Application (ORCA).

6.1.5 Bonding

6.1.5.1 The Offeror shall submit a proposal bond (Standard Form 24) with good and sufficient surety or sureties acceptable to the Government. A proposal bond equal to $396,000.00 (20% of the maximum contract amount of $9,900,000.00 divided by 5 years) is required for this solicitation.

6.1.5.3 Performance, Payment and Bid bonds MAY be required for task orders issued under any resulting contracts. The penal sum shall be established by each task order for all work considered to be construction by the Contracting Officer. Bonds shall be provided within five (5) calendar days of request by the Contracting Officer.

6.1.6 When proposing as a joint venture, all members of the joint venture shall sign the SF 1442, Corporate Certificate and the bid bond unless a written agreement by the joint venture is furnished with the proposal designating one firm with the authority to bind the other member(s) of the joint venture. In addition, the Offeror shall submit a copy of the joint venture agreement with the proposal. Failure to comply with the foregoing requirements may eliminate the proposal from further consideration. Note: JOINT VENTURE AGREEMENTS - Joint Ventures are allowable, however, the SBA must receive the joint venture agreement prior to proposal due date and approved before award of any resulting contract. If an Offeror is contemplating a joint venture on this project, it must advise its assigned SBA Business Opportunity Specialist (BOS) as soon as possible. It is also recommended that the agreement be submitted as soon as practicable to ensure compliance with established regulations. Any corrections and/or changes needed can be made only when its BOS has adequate time for a thorough review before the proposal due date. NO CORRECTIONS AND/OR CHANGES ARE ALLOWED AFTER TIME OF

SUBMISSION OF PROPOSAL.

6.1.7 Exceptions or Assumptions to Terms and Conditions. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Since the Government intends to award without discussions Offerors are advised that taking exception to any of the requirements specified in this solicitation may result in the proposal being found unacceptable without clarification. Clarification of any requirements or notice of any contractor exceptions or assumptions should be handled by submitting a question/recommended change prior to question submittal due date and proposal submittal. All assumptions/clarifications must be finalized prior to Final Proposal Revisions, if discussions conducted. If the Offeror still finds it necessary to take exception to any of the requirements specified in this solicitation, clearly indicate each exception in the appropriate volume along with a complete explanation of why the exception was taken and what benefit accrues to the Government. All exceptions to the solicitation requirements (Sections A through M, and all attachments) and supporting rationale shall be identified as such and consolidated into an overview section of the subject volume using the format and content of Table 6.1.

An overview section is only required if the Offeror takes exception to any requirement in the solicitation.

Table 6.1 - Solicitation Exceptions

SOLICITATION

Document

Page/ Paragraph

Requirement/ Portion

Rationale

SOW, Model Contract, ITO

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

7.0 VOLUME II – FACTOR 1: TECHNICAL

7.1 GENERAL

The Technical Volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the Offeror’s proposal. Legibility, clarity, and coherence are very important. The Government will evaluate offers against the Technical factors defined in Section M, Evaluation Factors for Award. 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. Statements that the Offeror understands, can, or will comply with the SOW (including referenced publications, technical data);

statements paraphrasing the SOW or parts thereof (including applicable publications, technical data); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” will be considered unacceptable. Offerors shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience, and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

7.2 FORMAT AND SPECIFIC CONTENT

At a minimum, the Technical Capability Volume shall be prepared in a form consistent with the Statement of Work (SOW) and the evaluation criteria for award as set forth in Section M of this solicitation. The section shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation of the Offeror’s technical competence and ability to comply with the contract task requirements specified in the SOW.

7.3 VOLUME ORGANIZATION

The volume shall address the technical capability subfactors and be organized according to the following general outline:

Table of Contents List of Table and Drawings Cross Reference Matrix Glossary Subfactor A – Management Approach Subfactor B – Experience Subfactor C – Seed Project

7.3.1 SUBFACTOR A: MANAGEMENT APPROACH

For this subfactor, the Offeror shall submit a management approach for successful execution of the contract. The management approach shall include, at a minimum, the following:

7.3.1.1 Offerors shall provide a detailed narrative and structure of its management approach. The Offeror shall include discussions on the home office and on-site management, to include onsite management’s interaction with its home office, as well as any other management aspects specific to the solicited work such as roles and responsibilities of dedicated management staff assigned to this contract (Project Manager, Superintendent).

7.3.1.2 The Offer shall demonstrate its ability to be responsive to the requirement of the contract. Offeror shall explain how it will respond to task order Requests for Proposals, warranty work, and Daily Report as well proposal preparation, subcontract management, surveillance of work, acceptance, rejection, documentation, and resolution of deficiencies, trend analysis and shall include corrective actions, and interface with Government inspectors and engineers at each stage of construction. Offeror shall identify those individuals responsible for those actions. The Offer shall explain and demonstrate its ability to respond to warranty work within a two hour time limit, its ability to respond to a task order RFP site visit within 24 hours with an indication as to who would attend, and its ability to prepare and submit an task order RFP within 3 days with an explanation as to accomplish the RFP requirements.

7.3.1.3 The Offeror shall provide a Staffing Plan that addresses the organizational structure of the Offeror's proposed team, including key personnel, “in house” workforce, major subcontractors, teaming partners, joint ventures, quality control personnel. for this project. The staffing plan shall be outlined through a narrative and a diagrammed organizational chart. The staffing plan for the onsite staff shall include the identification of proposed key personnel positions with regards to this contract. The offeror’s narrative shall provide the proposed job title, specific duties, responsibilities, experience, education, and qualifications for each key personnel position. The Offeror shall detail the levels of authority granted to each of the key personnel at the site office. The Offeror shall provide how it will manage and maintain a comprehensive subcontractor base and ensure timely compensatoin for subcontractor services. The Offeror shall explain and demonstrate its ability to provide a Project Manager with at least five years of demonstrated experience with the type of work found in this requirement. This includes experience with the disciplines and managing multiple projects concurrently found in this requirement.

7.3.2 SUBFACTOR B: EXPERIENCE. The Government requires a contractor capable of performing a variety of the different work expected under this contract. The Contractor must be capable of handling multiple projects simultaneously that are comparable in magnitude of construction of what is expected under this contract.

The purpose is to demonstrate the Offeror’s experience completing multiple projects with concurrent periods of performance utilizing multiple construction disciplines.

7.3.2.1 The Offeror, or offering entity in the case of a joint venture, shall provide evidence of no more than five

(5) relevant contracts, projects, or task orders completed within the past six years from the date this RFP was issued.

If more than five (5) projects are submitted only the first five (5) projects will be evaluated. Projects should demonstrate ability to perform or manage multiple construction disciplines and the ability to manage concurrent periods of performance. Provide evidence of a minimum of two instances where a minimum of two or more projects were performed with overlapping periods of performance.

7.3.2.2 Experience shall be performed as a prime contractor, subcontractor, or as the offering entity. If the offering entity does not have the requisite experience, then submit experience as a prime contractor for each individual partner.

7.3.2.3 For each project, submit the following information:

Project Title & Location State whether work was performed as the Prime or subcontractor Dollar Value of Work and Percentage of Overall Project your firm was responsible for (include your firm’s work and your subcontractor’s work) Start & Completion Dates (Month/Year) Brief Description of Project and its relevancy to work that may be ordered under any resulting contract Customer Point of Contact (i.e., name, relationship to project, agency/firm, city, state, current phone no., and email address)

Percentage of project self-performed, dollar value, and specific types of work self- performed.

Percentage, dollar value, and specific types of trades performed by your subcontractors.

7.3.2.4 Projects provided for experience should show the Offeror’s ability to manage/perform multiple projects performed simultaneously, and in the following categories of work:

7.3.2.4.1 The similarity of the scope, magnitude, and complexity of Offeror’s previous experience to the scope and complexity of the requirements for this contract;

7.3.2.4.2 The Offeror’s experience in performing/managing multiple projects being executed either simultaneously or on an overlapping basis;

7.3.2.4.3 The Offeror’s experience in performing multiple disciplines simultaneously and separately.

7.3.3 SUBFACTOR C: SEED PROJECT

7.3.3.1 At a minimum, Offerors shall provide the following:

7.3.3.1.1 Provide documentation of materials and equipment to be installed, to demonstrate conformance to the seed project task order requirements. Offerors shall use Appendix B – Eng_Form_4025-R.

7.3.4.1.2 Submit a project schedule in either Microsoft project or Microsoft excel. The schedule shall demonstrate how the project will be accomplished meeting the SOW prescribed Period or Performance.

7.3.3.1.3 Describe your process for documenting construction activities, to include daily reports.

8.0 VOLUME III – FACTOR 2: PAST PERFORMANCE

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

Past Performance information described herein is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform 50% of the proposed effort based on the total proposed 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.1.1 Early Proposal Information. The Offeror is requested, but not required, to submit the Past Performance Volume any time prior to the closing of the RFP, to the Contracting Officer at the address specified in Section L Paragraph 4.2.

8.1.2 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 six years for the submitted data. The past performance data shall document a successful history of past contract performance.

8.1.3 In conducting the Past Performance evaluation, the Government reserves the right to use both the information provided in the Offeror’s Past Performance Volume and information obtained from other sources, such as the Past Performance Information Retrieval System (PPIRS) or similar systems, Defense Contract Management Agency (DCMA) and commercial sources. Offerors are reminded that both independent data and data provided by Offerors in their proposals may be used by the Government to evaluate Offeror past performance. However, the burden of providing thorough, complete, and current past performance information as requested in this paragraph remains with the Offerors. Proposals that do not contain the information requested by this paragraph risk rejection or a less than acceptable performance rating by the Government. All past performance comments received will be taken into account and could affect the overall rating. The overall past performance evaluation is a subjective decision based on the whole of all data received. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the Offeror may not be evaluated favorably or unfavorably on past performance (see FAR 15.305 (a)(2)(iv)). Therefore, the Offeror shall be determined to have unknown past performance. In the context of acceptability/unacceptability, “unknown” shall be considered “acceptable.”

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

Table of Contents 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 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 2).

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

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.

Specific Relevant Contracts Format - Sheets in accordance with Attachment 3 and are limited to 3 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, size, 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, 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.

8.1.5 Past Performance Questionnaire. - See Attachment 1, 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, via email usarmy.jblm.acc-micc.list.proposals@mail.mil no later than 2:00 PM PDT on 26 May 2016. Any questionnaires not returned directly to the KO 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 the minimum number of questionnaires cannot be provided.

9.0 VOLUME IV – FACTOR 3: PRICE

9.1 Price is not assigned a rating or scored. The Government will evaluate each Offeror’s total proposed price for the Seed Project to determine if the Offeror’s proposed prices are fair and reasonable, complete and balanced utilizing price analysis techniques in accordance with the guidelines in FAR 15.404-1(b)(e)(g). The Seed Project – Price Schedule shall be evaluated to ensure a fair and reasonable price according to this Section. Price will not be assigned an adjectival rating.

9.2 Using Technical Exhibit 11, Attachment 3, Seed Project Bid Schedule, Offerors are to provide a total lump sum price using Technical Exhibit 9, Attachment 1, on a firm fixed-priced basis, for the seed project supported by a narrative and detailed computations that explain and depict how its price for the seed project was developed. Provide a price breakdown of all direct and indirect costs to include overhead and profit. The seed projects is “live,” which means it is anticipated to be awarded at the time of IDIQ contract award, and therefore, Offerors should submit their very best price.

9.4 The Government reserves the right to require the submission of Other Than Certified Cost or Pricing Data if it is deems necessary to arrive at a fair and reasonable price.

9.5 Project Distribution and Historical Task Order Information:

Historical Task Order Data for the Previous Contract # of Task Orders

Issued Total

Lowest Amount

Average Amount

Highest Amount

Base Period 12 $743,357.36 $9,428.00 $61,946.45 $286,802.00 Option Period 1 9 $1,192,061.04 $8,250.00 $132,451.23 $350,000.00 Option Period 2 9 $1,338,398.00 $61,582.00 $189,638.22 $148,710.89 Option Period 3 8 $1,349,003.40 $29,885.00 $168,625.43 $536,446.00 Total $4,662,819.80

9.6 Example Project List: Task orders under this resulting IDIQ are similar in nature the following examples:

Project Title: Asbestos Abatement Duration: 103 days Amount: $103,590.90

Project Title: Install Auto Sink Faucets Duration: 120 days Amount: $109,696.00

Project Title:…