SECTION_L_Amendment_31Dec2013_clean.pdf

FA8903-14-R-0004

Section L

31 December 2013

SECTION L (FAIRCHILD PBR)

Instructions, Conditions, and Notices to Offerors or Respondents

L-III - INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR

PROPOSAL PREPARATION

1 PROGRAM STRUCTURE AND OBJECTIVES

This requirement is for environmental remediation activities at Fairchild Air Force Base, Washington. This scope of work entails a full range of environmental, minor construction and engineering, and operations and services activities necessary for investigation, design, remedial action, remedial construction, and environmental remediation activities to achieve minimum performance objectives and stretch goals and support progress to Site Closeout (SC) at 60 sites under this Performance-Based Remediation (PBR) contract using a competitive Firm-Fixed Price pricing arrangement under FAR Part 15. This is considered a services effort and is being solicited under NAICS code 562910, Environmental Remediation Services. The Period of Performance (POP) is 120 months from date of contract award.

2 GENERAL INSTRUCTIONS

a) The Offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and its attached Enclosures. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

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

c) The proposal acceptance period is specified in Section A of the solicitation. The Offeror shall make a clear statement in Section A of the contract documentation volume that the proposal is valid through this date. Offerors must also acknowledge any Amendments issued for this solicitation (See Block 11 of the SF30 for instructions).

d) In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of unsuccessful proposals.

2.1 General Information

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the solicitation. The CO for this acquisition is as follows:

Contracting Officer:

Ms. Linda Cavazos Phone (210) 395-8732 Email: linda.cavazos@us.af.mil

2.1.2 Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3 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 CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.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.5 Oral Presentations

Oral presentations will not be used for this requirement.

2.1.6 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via mail.

2.1.7 Teaming

All Team Members shall have a signed Teaming Arrangement (TA) or Letter of Intent (LOI).

TAs/LOIs must be provided in Volume I, Contract Documentation, Volume II, Factor 1:

Technical, and Volume III, Factor 2: Past Performance.

mailto:linda.cavazos@us.af.mil http://www.fedbizopps.gov/

(a) Any business entity without a TA or LOI with the Prime is NOT considered a Team

Member and will not be evaluated.

(b) Mentor-Protégé (M-P) is a relationship and not a business entity. M-Ps require formal

TAs or LOIs to qualify for consideration as a Team Member.

(c) A Joint Venture (JV) will be considered a sole business entity. Signed JV documentation must be provided in Volume I, Contract Documentation, and Volume II, Factor 1: Technical.

(d) The proposal shall present a complete, coherent presentation of the Team’s ability as applicable.

2.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.2. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 2.2 Proposal Organization

Volume

ITO

Paragraph Number

Title Page Limit Original Unbound

Hard Copies

CD

Copies

I

3 VOLUME I - CONTRACT

DOCUMENTATION

3.2 Cover Letter/Contact

Information

3.3 Executive Summary

3.4 Standard Proposal Information

3.5 Validity Statement(No

submittal/tab required include in 3.2)

3.6 OCI Analysis and Mitigation

Plan

3.7 Construction Bonding

3.8 Teaming Arrangements and/or

letters of Intent Unlimited 1 1 1

3.9 Exceptions to Solicitation

Requirements

3.10 Model Contract

Volume

ITO

Paragraph Number

Title Page Limit Original Unbound

Hard Copies

CD

Copies

II

4 VOLUME II – FACTOR 1:

TECHNICAL

4.2 Standard Proposal Information

4.3 Teaming Arrangements and/or

Letters of Intent

4.4 General (No submittal/tab

required)

100 single sided pages (excludes 5, 11”X17” pages for Technical Summary

Table; post- POP Life- Cycle Cost

Activities and Assumptions;

and IMS and MPS without cost)

4.5 Technical Risk (No

submittal/tab required)

4.6 Proposal Requirement

Specifications (No submittal/tab required)

4.7 Technical Subfactor 1.1 -

Technical Approach

4.8 Technical Subfactor 1.2 - Plan

B Contingency Approach

4.9 Technical Subfactor 1.3 -

Management Approach

8 single sided pages

4.10 Technical Subfactor 1.4 -

Corporate Experience

5 single sided pages (1 page per project)

III

5 VOLUME III – FACTOR 2:

PAST PERFORMANCE

5.2 Standard Proposal Information

5.3 Teaming Arrangements and/or

Letters of Intent

5.4 Past Performance Summary 5 single sided

pages

5.5 Organizational Structure

Change History

5 single sided pages

5.6 Past Performance Information

Sheets

5 single sided pages (1 page per project)

5.7 Past Performance

Questionnaires Tab Only

5.8 Consent Letters

5.9 Client Authorization Letters

IV

6 VOLUME IV – FACTOR 3:

PRICE

6.2 Standard Proposal Information

6.3 General Instructions (No

submittal/tab required)

6.4 Submission of Section B

6.5 Milestone Payment Schedule

(MPS) with Price

2.3 Proposal Format

2.3.1 Guidance

a) This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal.

b) The Offeror's proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions.

c) All the requirements specified in this solicitation are mandatory.

d) You are representing that your firm will perform all the requirements specified in the solicitation by submitting your proposal.

e) These instructions are intended to elicit brief and specific responses. However, simply stating that the Offeror understands and intends to comply with this effort or paraphrasing statements in the solicitation is inadequate.

f) The offer shall comply with the requirements as stated in the solicitation.

2.3.2 Sufficient Detail

a) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims.

b) 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 or exceed these requirements.

c) Offeror(s) shall assume that the Government has no prior knowledge of their capabilities and experience, and will base its evaluation solely on the information presented in the Offeror's proposal.

2.3.3 Elaborate Presentations Not Desired

Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are NOT desired.

2.3.4 Price Information

a) All pricing information shall be addressed ONLY in the Price Proposal Volume

(Volume IV), with the exception of the Model Contract, Section B requirements and bonding amounts to be provided under Volume I and Volume IV.

b) Post-Period of Performance (POP) Life-Cycle Cost (LCC) estimates and landfill closure estimates are not considered pricing information and will not be evaluated as such. The electronic version of Section B (Pricing Schedule, pages 2-22 of the solicitation) shall be submitted in pdf. The electronic version of the Milestone Payment Schedule (MPS) shall be submitted in Microsoft Excel and pdf. Prices shall be provided in whole-dollar amounts in both the hardcopy and electronic version of the Schedule outlined in Section B of the RFP and the MPS. The Offeror shall provide the proposed total amount of any construction for each SubCLIN and include a milestone for any construction bonding fee. Any SubCLIN construction amounts and bonding fee amounts shall be totaled and provided for evaluation of bonding requirements. Reference Attachment L-2 for MPS submission format.

2.3.5 No Cross-Referencing

a) Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal.

b) Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal.

c) Each response to each Subfactor shall be self-contained. No cross-referencing between Subfactor responses is allowed.

2.3.6 Tab Indexing

a) Tab indexing shall be used to identify sections within each volume.

b) Tabs for items identified in the Title column of Table 2.2 Proposal Organization shall be utilized unless otherwise noted.

c) Tabs do not count against the page limitations for their respective volumes.

d) Note: DO NOT include proposal information on tabs.

2.3.7 Table of Contents

a) Table of Contents.

i. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

b) Master Table of Contents.

i. Volume I, Contracting Documentation, shall contain a consolidation of the individual Tables of Contents for all Volumes (I through IV).

ii. A separate e-file of the Master Table of Contents shall be provided in accordance with Electronic Copy requirements in paragraph 2.3.10.3.

c) The Table of Contents will not count against the page limitations for their respective volumes.

2.3.8 List of Tables and Figures

a) Each volume shall contain a list of all tables and figures within that volume.

b) The List of Tables and Figures will not count against the page limitations for their respective volumes.

2.3.9 Glossary of Abbreviations and Acronyms

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

b) One glossary may be developed for the entire proposal and provided in each volume.

c) Glossaries do not count against the page limitations for their respective volumes.

2.3.10 Proposal Copies

a) All copies of an Offeror’s proposal must be submitted together.

b) All Prime and Team Member(s) information must be incorporated into one coherent submittal.

c) Staples shall not be used.

d) 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 FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.3.10.1 “Original” Unbound Proposal One hardcopy of each volume shall be clearly identified as “original”. The “original” shall be formatted as follows:

a) Clearly marked as “Original”

b) Unbound

c) Hole-punched with a standard 2-hole punch at the top of each page

d) Printed head-to-foot so that each page can be read when placed in a standard 2-hole file folder

e) Each volume shall have a cover sheet, clearly marked as volume number, “ORIGINAL”, Offeror's name, solicitation title, and solicitation number.

2.3.10.2 Hard Copies

a) With the exception of the original noted in 2.3.10.1, each hard copy volume of the proposal shall be separately bound in a three-ring loose-leaf binder, which shall permit the volume to lie flat when open.

b) A cover sheet shall be bound in each book, clearly marked as to volume number, copy number, Offeror's name, solicitation title, and solicitation number.

c) A Label shall be placed in the front cover of each binder clearly identifying volume number, copy number, Offeror's name, solicitation title, and solicitation number.

d) A Label shall be placed in the spine of each binder clearly identifying volume number, copy number, Offeror's name, solicitation title, and solicitation number.

e) All unclassified document binders shall have a color other than red or other applicable security designation colors.

f) The Technical Summary Table shall be submitted on 11 x 17 inch single sided pages

g) The Integrated Master Schedule (IMS) shall be provided in hardcopy no larger than 11 x

17 inch single sided pages.

2.3.10.3 Compact Disc (CD) Copies

General requirements

a) The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the Offeror’s name, volume number, and solicitation number and title. Use separate files to permit rapid location of all portions, including Subfactors, exhibits, annexes, and attachments, if any. All electronic copies shall be submitted on CD-ROM in a flexible plastic protective sleeve. Protective sleeves shall be hole-punched with a standard 2-hole punch at the top of each sleeve.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc#b522151 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b31044

i. Electronic file directory titles and organization shall reflect the titles and organization of these instructions.

ii. Each directory shall contain a Microsoft Word file with a Table of Contents for that directory.

iii. The CD-ROMs will be used for proposal evaluation. The Government will not perform a word-by-word check of the “original” vs. the PDF version. However, if discrepancies are identified between the electronic proposal and the “original” paper proposal, the “original” paper proposal shall prevail.

iv. Offerors shall ensure electronic copies on CD-ROM are virus free.

v. Electronic copies of each volume shall be compatible with the following available Government equipment and software products:

Windows compatible PCs Adobe Acrobat Reader 9.0 Microsoft Office 2007 Microsoft Project 2007

vi. Sound or video (e.g. MPEG) files shall not be embedded into the proposal files.

vii. A separate CD-ROM shall be used for each volume.

b) Master copy CD-ROM requirements

i. Complete electronic copies of all volumes shall be submitted in Adobe Acrobat

Portable Document File (PDF) searchable and selectable text format.

ii. A separate CD-ROM shall be used for each volume.

iii. Each CD-ROM and protective sleeve shall be clearly marked as to volume number, Offeror's name, solicitation title, and solicitation number.

2.3.11 Page Format Restrictions and Limitations

2.3.11.1 Page Format

a) Unless otherwise specified, all pages shall be printed single-sided on recycled paper as much as practical.

b) Unless otherwise specified, pages shall be 8.5 x 11 inches, not including foldouts.

c) Text pages shall be portrait oriented. Graphics and tables may be landscape oriented if required to properly present the information.

d) Pages shall be typed with single line spacing.

e) No condensed fonts allowed. Times New Roman or Arial is preferred. The font size shall be no less than 10 point.

f) Margins on all four edges of each sheet will be at least one inch.

g) Proprietary statements, security markings, and page numbers can fall within the defined margin area.

h) Except for the Price Volume, each required section within a volume shall be numbered consecutively.

i) These page format restrictions shall apply to responses to Evaluation Notices (ENs).

2.3.11.2 Foldouts

a) Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics.

b) Foldout pages may not be used for pages of text.

c) Legible tables, charts, graphs, diagrams, schematics and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, design drawings, plans, etc.

d) These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size.

e) All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15-1/2 inches.

f) Foldout pages shall fold so that the Government can read and evaluate them without removal from proposal binder.

g) Foldout pages shall fold entirely within the volume.

2.3.11.3 Page Limitations

(a) Page limitations shall be treated as maximums.

(b) Each side of each 8.5 x 11 inch sheet that displays printed material shall be counted as 1 page for page limitation purposes.

(c) Each side of each 11 x 17 inch sheet that displays printed material shall be counted as 2 pages for page limitation purposes.

(d) Compliance with page count limits shall be verified via the hardcopy.

(e) If page limits are exceeded, the excess pages (1) will be destroyed; and (2) will not be read or considered in the evaluation of the proposal.

(f) Page limitations shall be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offeror(s).

2.3.11.4 Technical Summary Table

The Technical Summary Table shall be submitted on a maximum of five (5), 11 x 17 inch single-sided pages. Though these pages (Technical Summary Table) are part of the Technical Approach they will not be counted against the number of pages allocated for the technical volume. The Technical Summary Table shall also be provided electronically via CD or DVD in MicrosoftTM Excel compatible format. The spreadsheet shall not contain any hard-pressed numbers or locked cells or formulas.

2.3.11.5 Post-Period of Performance (POP) Life-Cycle Cost (LCC) with Activities and Assumptions The Post-PoP LCC estimates with Activities and Assumptions shall be submitted on 11 x 17 inch single-sided paper with the Technical Volume. The Post-Pop LCC estimate has no page limitations and will be excluded from the page count. However, if any text other than the cost estimate is provided in these pages, they will be counted against the page count.

2.3.11.6 Project Summary

Project summaries submitted for Subfactor 1.4, Corporate Experience, shall be submitted under the Technical Volume, but shall be submitted on five, single-sided 8.5 X 11 inch pages. Each project must be contained on a single page.

2.3.11.7 Pages Counted

Each page shall be counted except the following:

(a) Volume I – Contract Documentation

(b) Volume IV – Pricing

(c) Executive Summary

(d) Cover pages

(e) Table of contents

(f) List of tables and figures

(g) Glossary of Acronyms and Abbreviations

(h) Tabs

(i) Dividers

(j) Blank pages

(k) IMS

(l) Resumes

(m) Milestone Payment Schedule (MPS)

(n) Technical Summary Table

(o) Post-POP LCC with Activities and Assumptions

2.4 Distribution

All originals and copies shall be addressed to the PCO and mailed or hand carried to:

Regular Mail Courier

772 ESS/PKS 772 ESS/PKS

ATTN: Linda L. Cavazos ATTN: Linda L. Cavazos 2261 Hughes Ave., Suite 163 3515 S. General McMullen, Rm 3026 JBSA Lackland, TX 78236-9853 San Antonio, TX 78226-2018

2.5 Responsibility Determination

The PCO is required to make a determination of responsibility IAW FAR 9.1. As part of this determination, the PCO may request a Financial Capabilities Assessment from the cognizant Defense Contract Management Agency (DCMA) Office.

3 VOLUME I - CONTRACT DOCUMENTATION

3.1 Volume Organization

The Contract Documentation Volume shall be organized according to the following general outline:

3.2 Cover Letter/Contact Information

The Offeror shall identify the point of contact (POC) in the cover letter [name, phone number and e-mail address] for any questions regarding the submitted proposal and the POC shall have authority to negotiate and bind the company.

3.3 Executive Summary

(a) The Executive Summary is a concise narrative summary of the entire proposal, excluding price.

(i) The summary shall include key mission capability features describing key technical, performance, and management features of the Offeror.

(ii) The summary shall also include key contract features describing subcontractors, or TAs, delivery schedules for the period of performance including schedules for the basic and all options.

(b) The salient features shall tie in with Section M evaluation criteria.

(c) Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.4 Standard Proposal Information

(a) Provide a Master Table of Contents for the entire proposal (all volumes).

(b) Provide a Table of Contents for Volume I per ITO paragraph 2.3.7.

(c) Provide a List of Tables and Figures for Volume I per ITO paragraph 2.3.8.

(d) Provide a Glossary of Abbreviations and Acronyms for Volume I per ITO paragraph

2.3.9.

3.5 Validity Statement

(a) The cover letter shall include the Offeror’s confirmation that the proposal is valid for

180 days.

(b) The proposal acceptance period is specified in the SF 33, Page 1, Block 12 of the model contract/solicitation.

3.6 OCI Analysis and Mitigation Plan

(a) If your company (including Teaming Partners, subcontractors, subsidiaries and legacy companies) performed any cleanup related work in the past/present at sites identified in as part of this requirement, the Offeror shall submit identifying information – scope, applicable sites, specific document titles and descriptions, and contract or task order number in Volume 1, Contract Documentation. The Offeror shall identify any potential OCI issues or appearance of any potential OCI your company, (including all Teaming Partners, subcontractors, subsidiaries and legacy companies) may have with respect to the scope of effort as outlined in the PWS. OCIs may exist at least in the following three ways:

• Unequal access to information- access to non-public information that gives a contractor an unfair competitive advantage.

• Biased ground rules - when a contractor has in some sense set the ground rules for another procurement action creating the potential that the contractor may have tilted the playing field in the new competition (usually toward its own strengths and away from its weaknesses).

• Impaired objectivity - when the contract requires exercise of judgment and the independence of its judgment may be affected (e.g., when the contractor may be required to evaluate its own work in a way that could be adverse to its economic interests).

(b) If your company did perform past/present cleanup related work at the sites for this PBR, a mitigation plan shall be submitted in Volume 1, Contract Documentation Volume to show how your company will either satisfactorily mitigate or eliminate any potential OCI issues or appearance of any potential OCI. If your firm, including all Teaming Partners, subcontractors, subsidiaries, and legacy companies, has not performed any work on the sites included as part of this requirement, then the Offeror must so state.

(c) Any submitted OCI analysis and plan will not be evaluated unless the Offeror is considered the apparent successful Offeror under the evaluation Factors listed in this RFP. If the OCI analysis and plan needs to be evaluated, the Government will determine if an OCI exists and whether adequate mitigation is proposed. If adequate mitigation is not proposed, the Government may engage in exchanges with the apparent successful Offeror to determine if the problems with the mitigation plan may be resolved. If an OCI exists that cannot be adequately mitigated, the Government may seek waiver of the OCI issue or may award to another Offeror who does not have an OCI, or who has an OCI and has submitted a mitigation plan that is adequate or may be made so after exchanges between the Government and the Offeror.

3.7 Construction Bonding

(a) Provide the total proposed amount for any construction efforts by Sub-CLIN and total contract. Provide a construction amount for each fiscal year of the POP (i.e. Fiscal Year 1, Fiscal Year 2, Fiscal Year 3, etc. based on chronological milestone payment date).

Provide the bonding fee total and the bonding fee by year.

(b) Provide assertion that the Prime contractor can meet the bonding requirements of the contract (100% performance and payment bond) with respect to the proposed totals for construction by year. Provide proof of excess bonding capacity commensurate with the proposed amount for construction with bonding capability letters from an approved surety listed with the Department of Treasury. Letters must be notarized and signed by an authorized representative of the surety. Letters signed by agents are unacceptable unless accompanied by a Power of Attorney granting proper authority to the agent.

Bonding capability must be for the Prime only (stacking of Teaming Partners/subcontractor bonds will not be accepted).

3.8 Teaming Arrangements and/or Letters of Intent:

Provide all Teaming Arrangements and Letters of Intent for all Team Members to receive credit for performing as a team as required in Volume I, Contracting, ITO, Paragraph 2.1.7.

3.9 Exceptions to Solicitation Requirements

(a) 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 Subfactor. Failure to meet a requirement may result in an offer being ineligible for award. Offerors shall clearly identify any exceptions to the solicitation, including any exceptions to the terms and conditions of the model contract.

Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

(b) Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

(c) Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation.

(d) This information shall be provided in the format and content of Table 3.9. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

Table 3.9 – Solicitation Exceptions Solicitation Document

Paragraph/Page Requirement/Portion Rationale

Contract clause, solicitation paragraph, model contract, ITO, etc.

Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Justify why the requirement will not be met

3.10 Model Contract

(a) The Contract Award Document will consist of Sections A through J and the attachments listed under paragraph 3.10.2 Attachments for the Awarded Contract.

(b) The Model Contract consists of Sections A through J to include completed Section B

Price Schedule and the Representations and Certifications. (Note: Section B pricing shall be in line with the MPS as proposed). 1-Orginal Unbound and 1-Copy as follows:

(1) “Original Unbound” copy (reference Section L, paragraph 2.3.10.1):

The Offeror shall submit the “original” signed copy of the Model Contract.

Signature by the Offeror on the Standard Form (SF) 33 constitutes an offer, which the Government may accept.

(2) A copy of the “original” Model Contract is also provided under Volume 1.

Reference Table 2.2 and paragraph 3.1(m).

3.10.1 Representations and Certifications

The Offeror's proposal shall include a signed copy of the Representations and Certifications, Section K. The Offeror may submit a signed copy from the System for Awards Management (SAM) website in lieu of completing the representations and certifications included in the solicitation. The original copy is provided with the “Original Unbound” proposal and a copy in Volume I, Tab Model Contract.

3.10.2 Attachments for the Awarded Contract

The following is a list of attachments, including Enclosures, which are anticipated to be made part of the Fairchild PBR Contract upon Award. Informational purposes only - No submittal required.

(a) PWS

(b) PWS Table 1

(c) PWS Table 2

(d) PWS Enclosure – Site List

(e) PWS Enclosure – Acronyms and Definitions

(f) PWS Enclosure – Format For Metadata and .pdf Documents

(g) Service Contract Act Wage Determination No. 2005-2565, Revision 13, posted 25

June 2013 (Note that most current WD at the time will be incorporated)

(h) Davis Bacon Wage Determination for Washington, Heavy for Spokane County – most current General Decision Number WA130101, dated 08/23/2013 (Note that most current WD at the time of award will be incorporated)

(i) Key Personnel Qualifications and Parameters

(j) Fairchild AFB Base Support Letter

4 VOLUME II – FACTOR 1: TECHNICAL

4.1 Volume Organization

The Technical Volume shall be organized according to the following general outline:

4.2 Standard Proposal Information

(a) Provide a duplicate copy of the Executive Summary narrative as required in Volume I, Contracting, ITO paragraph 3.3.

(b) Provide a Table of Contents for Volume II per ITO paragraph 2.3.7.

(c) Provide a List of Tables and Figures for Volume II per ITO paragraph 2.3.8.

(d) Provide a Glossary of Abbreviations and Acronyms for Volume II per ITO paragraph

2.3.9.

4.3 Teaming Arrangements and/or Letters of Intent

Provide duplicate copies of all TAs and LOIs for all Team Members as required in Volume I, Contract Documentation, ITO paragraph 3.8 to perform as a Team.

4.4 General

The Technical Volume shall be specific and complete. In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical Subfactor. If the Contractor anticipates the ability to achieve a stretch goal during the POP, the Contractor is encouraged to propose that stretch goal, which will then become the requirement of this contract (applicable to sites in Table 1 of this PWS only). At award, PWS Table 1 will be updated to reflect the PROPOSED performance objectives and PROPOSED duration for all sites. The Contractor shall specify the performance objective to include at least the minimum objective as listed for sites in Table 1 of this PWS and the specific performance objectives for sites listed in Table 2 of this PWS (with no stretch goal proposed) and date they intend to achieve it for each site within the POP. Contractors shall explain why the selected performance objective (including the minimum performance objective if that is what is proposed) is an optimum solution for the Government.

4.5 Technical Risk

The identification of weakness(es), considers potential for disruption of schedule, increased costs, or degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Informational purposes only - No submittal required.

4.6 Proposal Requirement Specifications

(a) Marketing presentations are not wanted and will not be evaluated. Hard evidence of capabilities is required to receive credit for evaluation factors.

(b) Legibility, clarity, coherence, and free of spelling errors and typos which can lead to misinterpretations are very important.

(c) Your responses will be evaluated against Section M, Evaluation Factors.

(d) Provide as specifically as possible, the actual methodology you would use for accomplishing and satisfying the requirements.

(e) All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your Team will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

(f) Technical Subfactors.

(1) Include capabilities of Prime and Team Members.

(2) Describe the Offeror’s proposed strategic approach to meeting the requirements of each Technical Subfactor.

4.7 Subfactor 1.1: Technical Approach:

The Offeror shall submit a comprehensive technical approach that specifies the performance objective (to include at least the minimum objective for sites in Tables 1 and 2 of the PWS) and date they intend to achieve it for each site within the POP. Offerors shall explain why the selected performance objective for sites in Table 1 of the PWS (including the minimum acceptable performance objective if that is what is proposed) is an optimum solution for the Government. The comprehensive approach shall describe how all the performance objectives in the PWS and other applicable agreements will be met or exceeded.

1. Technical Summary Table: The Offeror shall provide a technical summary table which includes the following information for each site listed in the PWS: Site ID, Site Name, Minimum Performance Objective, Proposed Performance Objective, Date of Achieving Performance Objective, Brief Description of the Technical Approach, and Projected Site Closeout Date (Quarter/Calendar Year or Indefinite). Site ID and Site Name should be copied from PWS Enclosure 1. Proposed Performance Objective is the performance objective to be achieved within the POP and shall meet or exceed the minimum performance objective listed in the PWS. A Projected SC Date shall be provided for all sites including those projected to be closed after the POP. Provide the page number in Volume II where narrative discusses proposed approach and line number in IMS where activity schedule is provided for the site.

2. For each site, the proposed performance objective is that performance objective to be achieved within the proposed timeframe and shall meet or exceed the minimum performance objective listed in the PWS. The Offeror shall provide a business case analysis with sufficient detail to support why each proposed performance objective for sites listed in Table 1 of the PWS are the optimum end state for the Government, including those sites for which SC is proposed. The Offeror shall submit an approach to achieve SC or to move as close to SC as possible during the POP without expending large sums for contingencies for sites in Table 1 of the PWS and the specific performance objectives for sites listed in Table 2 of the PWS (with no stretch goal proposed).

3. For each site in Table 1 of the PWS that has or will have a signed Decision Document during the POP and the proposed performance objective is not SC (i.e., the proposed performance objective is OES, DD, RIP, or RC), the Offeror shall provide an Optimized Exit Strategy (OES). The OES shall include technical rationale for proposed strategies, technologies expected to be implemented, locations and media targeted for restoration, performance models, and expected outcome or state at the end of the POP.

i. Where the proposed performance objective for a site in Table 1 of the PWS includes an OES, the Offeror shall identify a performance model.

ii. Proposals describing quantitative performance models are required for the following sites: LF002, FT004, ST010, DP012, DP013, SD031, FT032, LF001, WP003, SS018, and SS026. The quantitative performance models shall be based on Air Force data available on the website provided in PWS Enclosure 2. Although proposals describing quantitative performance models are encouraged for all sites where the proposed performance objective includes an OES, appropriately detailed conceptual-type performance models for the remainder of the OES sites is acceptable during the proposal stage.

The proposed performance model would indicate how concentrations and/or mass will be reduced over time, or how other factors that drive LCC will be reduced. If a quantitative model is not provided, the Offeror should indicate the degree to which the approach will reduce the time required to achieve SC, if at all. While the model will be refined during the development of the OES Plan, sufficient information must be provided in the proposal for the Air Force to understand what they are getting for the proposed price

4. The Offeror shall provide a post-POP life-cycle cost estimate. Sufficiently detailed assumptions must be provided for the anticipated activities in order for the Government to validate the Offeror’s post-POP life-cycle cost estimate. Specific instructions include:

i. Post-POP Life-Cycle cost estimate must be un-escalated

ii. Post-POP Life-Cycle cost estimate must be FY14 cost basis

iii. Post-POP Life-Cycle cost estimate must be provided by site and by fiscal year

iv. Detailed activities and assumptions must be provided and broken out by site, fiscal year, and milestones. The Offeror shall provide activities and assumptions beginning with estimated completion of the performance objective or contract, whichever comes first, and carry them through Offeror’s projected SC date (or FY44 for site with indefinite closeout date).

Note: The Offeror shall not provide the total LCC in the technical volume. The Government will compute the total LCC by adding the post-POP LCC and the proposed price included under Factor 3.

5. The Offeror's technical approach shall also include an activity based Integrated Master Schedule (IMS) with the following:

i. Activities and milestones at a detailed level and sequenced events for completion of the proposed performance objectives.

ii. Achievement of the performance objectives within the time designated. The activity/milestone demonstrating achievement of the proposed objective shall be clearly identified as such.

iii. OES deliverables; activities and milestones associated with the OES strategy from sites in Table 1 of the PWS (i.e., interim and final performance goals associated with the performance model). At a minimum, the OES shall be structured to include sequential periods of (1) detailed OES development ending with preparation of an OES plan that includes quantitative and measureable performance goals which entails a contaminant reduction from baseline conditions throughout the POP, (2) OES implementation ending with an OES implementation completion report and an OES effectiveness report documenting the remedial activities, and (3) OES performance evaluation including efforts to meet several interim objectives prior to the end of the POP, as well as attainment of overall performance goals at the end of the POP.

iv. Government and Regulatory review periods for deliverables.

6. The Offeror's technical approach shall include a copy of the Milestone Payment

Schedule (MPS) without price information (Attachment L-1) and IAW Contract Line Item Number (CLIN) Structures/MPS/IMS Guidance (Attachment L-6).

7. The Offeror’s technical approach shall include a description of routine, preventative, and proactive operations and maintenance (i.e. vegetative management, corrosion control, and other activities as described in the O&M Plan) to preserve the value of the Government’s infrastructure and reduce LCC.

8. Offerors shall demonstrate an approach to energy management that will minimize costs to the Government and reduce impacts on the environment.

9. Offerors shall describe a technical approach and field efforts required to demonstrate compliance and effectiveness of monitoring and treatment systems.

4.8 Subfactor 1.2 Plan B Contingency Approach

The Offeror shall submit a Plan B Contingency Approach that identifies significant risks associated with the project and proposed technical approach, including potential system failures, and outline strategies for elimination or mitigation of the risks and/or contingencies to address the risks. The approach shall include the following:

1. Risk factors associated with obtaining the performance objectives using the proposed technical approach.

2. A description of how the proposed approach minimizes risks to meet the performance objective, including a description of risk mitigation strategies.

3. Contingency plans (alternate technical approach/i.e. Plan B) that will be implemented to ensure achievement of the proposed performance objective. Contingency Plans shall not be additional activities of the same initial approach that is not working as proposed (i.e.

more of Plan A is not equal to Plan B). The proposal shall include the decision logic and timing for implementation of the contingency plan if the proposed approach proves incapable of meeting the proposed performance objectives within the required timeframes.

4.9 Subfactor 1.3: Management Approach

The Offeror shall submit a detailed management plan for achieving the proposed site-specific performance objectives and milestones as scheduled, managing the requirements, and ensuring quality services and deliverables. The plan shall include the following information:

1. A description of a qualified field and management team, including the key personnel listed below, subcontractors, roles and responsibilities, and other relevant team members and provide an organizational chart (includes key personnel).

2. A description of how the Offeror will manage the work in order to meet the requirements of the PWS.

3. A description of the how the Offeror will manage multiple and concurrent events.

4. A description that the team members have relevant experience with the remediation technologies proposed.

5. A description of the Offeror’s procedures/processes to ensure high-quality services and deliverables.

6. A description of how communication between stakeholders (Air Force, Contractor, Regulators, and Community) will be maintained.

7. A description of how team members/subcontractors will be managed.

Key Personnel Qualifications: The Offeror shall submit resumes for the following key personnel that meet the labor category qualifications in Attachment 4 of the RFP. These key personnel categories will be included in the contract and will require notification of personnel change:

• Program Manager

• Program QA/QC Manager

• Program Health and Safety Manager

• Program Chemist

• Senior Project Manager

• Toxicologist

Note: After award of the contract, the CO and Contracting Officer Representative (COR) shall be notified of any proposed changes to the key personnel listed above at least 10 days in advance. The Government reserves the right to reject proposed changes in key personnel. Such notification shall include:

-An explanation of the circumstances necessitating the substitution -A complete resume of the proposed substitute

-Any other information needed by the CO and COR to enable them to judge that the Contractor is maintaining the same quality of personnel as those included at the time of award

4.10 Subfactor 1.4: Corporate Experience (same projects as Past Performance):

The Offeror shall submit five (5) project/contract/task order (TO) summaries (narratives) describing their team experience as it relates to this PBR. The Government will not consider performance on a project/contract/TO that concluded more than five (5) years prior to the date of this solicitation. For projects/contracts/TOs that are actively being performed, performance must be a minimum of 50% complete as of the date of solicitation for this contract.

Projects/contracts/TOs submitted by the Offeror should be the most relevant in demonstrating their ability to perform the proposed effort. Three (3) of the five (5) projects must be from the Prime contractor. The Offeror shall include the exact same copies of the project/contract/TO summaries in the volume for Factor 2, Past Performance.

Project/Contract/TO Summary Submissions shall include the following:

1. The individual task order or delivery order number, or stand-alone contract number with an initial award value of greater than $2 Million.

2. Title of the project and a brief description of the effort including the characteristics or aspects of the project that the Government will consider in determining relevance (i.e.

whether or not it was a PBR). Focus on the PWS aspects identified in the Technical and Managerial Factors.

3. Number of Environmental Sites and types of contaminants (i.e. TCE, fuels, etc.)

4. Type of contract/pricing arrangement, i.e. Firm Fixed Price (FFP), Time and Materials

(T&M), Cost Plus Fixed Fee (CPFF), etc.

5. Original award amount and final total dollar amount (or estimate at completion) including modifications and options (with reasons for any changes in dollar amounts). If the project is currently ongoing, provide the percent complete at the time of proposal submission.

6. Original and final period of performance (Start and End dates).

7. Current contract points of contact (POCs). Provide a current e-mail address and phone number. Provide a minimum of two Government POCs. Whenever possible, provide one from the technical or program management community and one from the contracting community. For commercial efforts, provide similar points of contact.

8. The status of the project, if it was completed on-time/budget and whether or not the Offeror encountered any performance issues or challenges. If issues or challenges did arise, provide information on how they were addressed by the Offeror.

5 VOLUME III – FACTOR 2: PAST PERFORMANCE

5.1 Volume Organization

The Past Performance Volume shall be organized according to the following general outline:

5.2 Standard Proposal Information

(a) Provide a duplicate copy of the Executive Summary narrative as required in Volume I, Contracting, ITO paragraph 3.3.

(b) Provide a Table of Contents for Volume III per ITO paragraph 2.3.7.

(c) Provide a List of Tables and Figures for Volume III per ITO paragraph 2.3.8.

(d) Provide a Glossary of Abbreviations and Acronyms for Volume III per ITO paragraph 2.3.9.

5.3 Teaming Arrangements and/or Letters of Intent

Provide duplicate copies of all TAs and LOIs for all Team Members as required in Volume I, Contract Documentation, ITO paragraph 3.8 to perform as a Team.

5.4 Past Performance Summary

(a) Describe the role of the Prime and each team member that will perform on the Fairchild

PBR contract and identify the percentage of the proposed effort each will perform.

(b) Discuss how the projects submitted for evaluation demonstrate the Offeror’s ability to meet the Fairchild PBR contract requirements.

(c) This information is to assist the evaluators in determining the relevance of projects submitted for past performance evaluation by confirming the role of the team member compared to the scope of the projects submitted for evaluation.

(d) 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. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.

5.5 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes within the last 5 years in the organization of your company, and team members as applicable. Show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment.