Vandenberg_Section_L_-_FINAL_22_Feb_13.pdf

SECTION L (Vandenberg PBR)

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

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

PROPOSAL PREPARATION

1.0 Program Structure and Objectives

This requirement is for environmental remediation activities at Vandenberg AFB, California.

The scope of work entails a full range of construction and engineering 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 107 Installation Restoration Program (IRP) sites under a single performance-based remediation (PBR) contract using a competitive Firm-Fixed Price pricing arrangement under FAR Part 15. This is considered a construction 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.0 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 Statement of Objectives (SOO – Attachment 1) 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 Volume I, Contract Documentation that the proposal is valid through the timeframe specified.

(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 Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition.

Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Section 2.4, Distribution.

The PCO for this acquisition is as follows:

Procuring Contracting Officer:

Ms. Rebecca Quint Phone (210) 395-8754 Email: rebecca.quint@us.af.mil

2.1.2. Debriefings

Offerors are entitled to a debriefing in accordance with FAR 15.506. If discussions are entered, the PCO 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 preaward debriefing or they may choose to wait until after the source selection decision to request a postaward debriefing.

However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO 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 PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO 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 reserved right includes requirements for 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 the Government and Offerors will be controlled by the PCO. 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 – See mailto:rebecca.quint@us.af.mil

FAR 2.101 & 3.104” in the Subject line. Otherwise, hardcopy letters will be transmitted to the Offeror(s) as required.

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, and Volume II, Technical.

(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, 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

ITO Paragraph Number 2.3.11.3 2.3.10.1 2.3.10.2 2.3.10.3

VOLUME

ITO

Paragraph Number

TITLE PAGE LIMIT

ORIGINAL

UNBOUND

HARD

COPIES

E-

COPIES

I

3. VOLUME I – CONTRACT

DOCUMENTATION

1 1 2

3.1 Volume Organization

Unlimited

3.2 Contact Information

3.3 Executive Summary

3.4 Standard Proposal Information

3.5 Validity Statement

3.6 Organizational Conflict of Interest

3.7 Construction Bonding

3.8 Teaming Arrangements and/or

Letters of Intent

3.9 Exceptions to Solicitation

Requirements

II

4. VOLUME II – FACTOR 1:

TECHNICAL

1 6 3

4.1 Volume Organization

Unlimited

4.2 Standard Proposal Information

4.3 Teaming Arrangements and/or

Letters of Intent

4.5 Technical Risk Submission 100

(excludes 10, 11”X17” pages for Summary

Table; excludes post-POP Life-

Cycle Cost Activities and Assumptions;

excludes IMS and MPS without cost)

4.7 Technical Subfactor 1.1-

Technical Approach

4.8 Technical Subfactor 1.2- Plan B

Contingency

4.9 Technical Subfactor 1.3 –

Management Approach 10

4.10 Technical Subfactor 1.4 -

Corporate Experience 10

4.11 Technical Subfactor 1.5 – Extent

of Participation of Small Business Concerns (See Section 7.3)

N/A

III 5.0 VOLUME III – FACTOR 2:

PAST PERFORMANCE

1 3 3

5.1 Volume Organization Unlimited 5.2 Standard Proposal Information

5.3 Past Performance Summary 5

5.4 Organizational Structure Change

History Unlimited

5.5 Past Performance Information

Sheets

No more than 10 (2 page per project)

5.6 Past Performance Questionnaires Tab Only

5.7 Consent Letters

Unlimited 5.8 Client Authorization Letters

5.9 Subcontracting Report

IV

6.0 VOLUME IV – FACTOR 3:

PRICE

1 2 2

6.1 Volume Organization

Unlimited

6.2 Standard Proposal Information

6.4 Submission of Schedule B

6.5 Submission of Milestone Payment

Schedule (MPS) with Price V 7.0 VOLUME V – Technical

Subfactor 1.5 – Extent of Participation of Small Business Concerns

7.1 Volume Organization

Unlimited

7.2 Standard Proposal Information

7.4 Submission of Small Business

Participation Information

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

All pricing information shall be addressed ONLY in the Price Proposal Volume (Volume IV).

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 Schedule outlined in Schedule B shall be in both Microsoft Word and pdf.

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 construction for each SubCLIN and include a milestone for the construction bonding fee. In addition, the Offeror shall include a brief description of construction activities associated with each SubCLIN. 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.

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

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

2.3.7. Table of Contents

(a) Table of Contents.

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

(b) Master Table of Contents.

1. Volume I, Contract Documentation, shall contain a consolidation of the individual

Tables of Contents for all Volumes (I through V).

2. 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) 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 IMS shall be provided in hardcopy no larger than 11 x 17 inch single sided pages.

2.3.10.3 Electronic Copies (E-Copies) – Compact Disc (CD): 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.

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

2. Each directory shall contain a Microsoft Word file with the Master Table of Contents for that directory.

3. A PDF electronic version of the proposal shall be included on the CD-ROM. The PDF of the proposal shall be an exact duplicate of the “original” paper proposal. 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 paper proposal shall prevail.

4. Offerors shall ensure electronic copies on CD-ROMs are virus free.

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

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

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

(b) Master copy CD-ROM requirements

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

Document File (PDF) searchable and selectable text format.

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

3. Each CD-ROM and protective sleeve shall be clearly marked as to volume number, Offerer’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 double-sided on recycled paper as much as practical. For example, original letters are exempted from the double-sided requirement.

(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, Arial, or similar font 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 0.5 pages for page limitation purposes. Pages shall be double-sided as much as practicable.

(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 not be read or considered in the evaluation of the proposal; and (2) will be destroyed .

(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) and will be dependent on the nature of the EN.

2.3.11.4 Technical Summary Table

The Technical Summary Table shall be submitted on 11 x 17 inch single-sided pages. Though these pages (Summary Table) are part of the Technical Approach (Subfactor 1.1), they will not be counted against the number of pages allocated for Technical Sub-factors 1.1 and 1.2. The 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 with Activities and Assumptions shall be submitted on 8.5 x 11 inch double-sided pages. Though these pages are part of the Technical Approach, they will not be counted against the number of pages allocated for Technical Sub-factors 1.1 and 1.2.

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) Volume V – Extent of Participation of Small Business Concerns (if applicable)

(d) The Small Business Volume

(e) Executive

(f) Cover pages

(g) Table of Contents

(h) List of Tables and Figures

(i) Glossary of Abbreviations and Acronyms

(j) Tabs

(k) Dividers

(l) Blank pages

(m) Technical Summary Table

(n) Post-POP LCC with Activities and Assumptions

(o) Integrated Master Schedule (IMS)

(p) Milestone Payment Schedule (MPS) with and without cost

(q) Resumes

2.4 Distribution

Proposals shall be addressed to the PCO and mailed or hand carried to:

Regular Mail Courier Rebecca D.M. Quint 772 ESS/PKB

772 ESS/PKB ATTN: Rebecca D.M. Quint 2261 Hughes Ave, Suite 163 3515 S General McMullen, Rm 3026 JBSA Lackland, TX 78236-9853 San Antonio, TX 78226-2018

OFFICIAL BUSINESS

3.0 VOLUME I – CONTRACT DOCUMENTATION

3.1 Volume Organization

(a) Executive Summary

(b) Master Table of Contents

(c) Table of Contents

(d) List of Tables and Figures

(e) Glossary of Abbreviations and Acronyms

(f) Validity Statement/Representation of Delinquent Tax Liability/Felony

(g) Contact Information

(h) Teaming Arrangements and/or Letters of Intent

(i) Exceptions to Terms and Conditions

(j) Representations and Certifications

(k) Proof of Bonding Capability

3.2 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 milestone capability features describing significant 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 Offeror’s shall include a statement that the proposal is valid for 120 days from the date of proposal submission.

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

3.6 Organizational Conflict of Interest (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 Statement of Objectives (SOO). 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. OCI determination will be included as part of the responsibility determination conducted prior to award. 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 construction efforts by SubCLIN 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. Provide a brief description of the construction efforts for each SubCLIN.

(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; Letters of Withdrawal:

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

4.0 VOLUME II – FACTOR 1: TECHNICAL

4.1 Volume Organization

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

(a) Executive Summary (duplication of executive summary in Volume I, Contract

Documentation)

(b) Table of Contents

(c) List of Tables and Figures

(d) Glossary of Abbreviations and Acronyms

(e) Teaming Arrangements and/or Letters of Intent

(f) Technical Subfactor 1.1, Technical Approach

(g) Technical Subfactor 1.2, Plan B, Contingency Approach

(h) Technical Subfactor 1.3, Management Approach

(i) Technical Subfactor 1.4, Corporate Experience

(j) Technical Subfactor 1.5, Extent of Participation of Small Business Concerns (Reference

Volume V)

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

4.5 Technical Risk

Address Technical Risk associated with those aspects of your proposal for Subfactors 1.1, 1.2, and 1.4 that are considered to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with DoD Source Selection Procedures Table 3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOO requirements), whether or not those requirements are identified as Subfactors. Propose a realistic "work-around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

4.6 Proposal’s 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, and coherence 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 of 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 Sub-Factor 1.1 - Technical Approach

(a) The Offeror shall submit a comprehensive technical approach that specifies the performance objective (to include at least the minimum performance objective for sites in Table 1) and date the Offeror intends to achieve it for each site within the POP. Offerors shall explain why the selected performance objective for Table 1 sites (including the minimum acceptable 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/1.%20%20Published%20Baseline/MP5315.3.doc#p5512 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 SOO and other applicable agreements will be met or exceeded.

The proposal shall included the following site-specific information

• Summary Table: The Offeror shall provide a summary table which includes the following information for each site listed in the SOO: Site ID, Site Name, Minimum Performance Objective, Proposed Performance Objective, Date of Achieving Proposed 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 SOO Enclosure 1. Proposed Performance Objective is the performance objective to be achieved within the POP and shall meet or exceed the minimum objective listed in the SOO. A Projected Site Closeout Date shall be provided for all sites including those projected to be closed after the POP.

• The Offeror shall provide the selected performance objective for each site.

• The Offeror shall submit an approach to achieve Site Closeout (SC) or to move as close to SC as possible during the POP without expending large sums for contingencies for Table 1 sites. The Offeror shall provide a business case analysis for why SC is either not technically feasible or not cost effective for those sites not proposed to achieve SC.

• For all Table 1 sites that have or will have a signed Decision Document during the POP and for which the proposed performance objective is not SC, the Offeror shall provide Optimized Exit Strategies (OES). The OES shall include anticipated structure and elements as required in Section 1.0 of the SOO, technical rationale for proposed strategies, technologies expected to be implemented, locations and media targeted for restoration, and expected outcome or state at the end of the POP.

o Where the proposed performance objective for a Table 1 site includes an OES, the Offeror shall identify a performance model.

o Although proposals describing quantitative performance models are encouraged for all sites where the proposed performance objective includes an OES, conceptual-type performance models are acceptable during the proposal stage for all sites except those with a baseline evaluation prepared by the Air Force which will require a fully developed performance model as described below.

o For the sites listed below, the Air Force has developed baseline evaluations. These baselines are statistical evaluations describing groundwater concentration for predominant contaminants of concern from 2002 to the present. These evaluations provide baselines of progress toward site cleanup for the current remediation strategy. A technical memorandum documenting the evaluations has been prepared by the Air Force and is identified in Enclosure 2 of the SOO.

For these sites listed below, the Offeror shall provide a fully developed performance model depicting the concentration that will be achieved by the end of the POP (i.e., minimum target concentration or performance goal) through implementation of the Offerors proposed OES and the time-concentration relationships during the POP as the OES is implemented. A narrative description of the nature of the time-concentration (e.g., straight line, exponential, step function, etc) shall be provided including the technical rationale or logic for the selection of the model (i.e., rationale for the depiction).

SD024 - ENTOMOLOGY WASH RACK

SD015 - ABRES-B LAUNCH COMPLEX

SS003 - OLD RAILROAD PUMPING STATION

WP005 - SPACE LAUNCH COMPLEX (SLC) - 3E

WP008 - SITE 8 CLUST

SS050 - BIONETICS BUILDING

TU077 - BUILDING 7425

WP013 - ABRES-A LAUNCH COMPLEX

SD032 – Missile Silo 576-D

• The Offeror shall provide separate costs for the full value, with activities and assumptions, for closing each landfill, recycling its content (Reminder:

proceeds of metal recycling must be returned to the Installation recycling manager), eliminating future environmental liabilities and returning the cleaned up landfill to productive use as compared to maintaining landfill caps, monitoring systems, and reporting requirements in perpetuity as part of this analysis.

• The Offeror shall provide a post-POP Life-Cycle Cost (LCC) 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:

o Post-POP Life-Cycle cost estimate must be un-escalated o Post-POP Life-Cycle cost estimate must be FY13 cost basis o Post-POP Life-Cycle cost estimate must be provided by site and by fiscal year o 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 FY43 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.

• The Offeror’s approach shall include a description of the processes to implement and refine proposed or existing remediation systems in accordance with California state regulations and Central Coast Regional Water Quality Board.

(b) The Offeror's technical approach shall also include an activity based Integrated Master Schedule (IMS) with the following: Activities and milestones at a detailed level and sequenced events for completion of the proposed performance objectives.

o Performance objectives within the time designated.

o OES deliverables; activities and milestones associated with the OES strategy (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 reduction from baseline conditions throughout the POP; (2) OES implementation ending with an OES implementation completion report or remedial action completion report (RACR) 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.

o Government and Regulatory review periods for deliverables.

(c) 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/Milestone Payment Schedules (MPS)/Integrated Master Schedules (IMS) Guidance (Attachment L-6).

4.8 Subfactor 1.2 - Plan B, Contingency Approach

(a) The Offeror shall identify all 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. (e.g., Plan B). The approach shall include the following:

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

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

• 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:

• A description of a qualified field and management team, including key personnel, subcontractors; and other relevant team members and provide an organizational chart. Key personnel shall include Program Manager, Program Chemist, Program QA/QC, Program Health and Safety Manager, Superintendent for Construction.

• A description of relevant team (prime, teaming members, subcontractors) experience with the proposed remediation technologies identified by the Offeror under Subfactor 1.1 that are similar in size and scope to the Vandenberg PBR Requirements.

• A description of how the Offeror will manage multiple and concurrent events. A description of how the Offeror’s procedures/processes to ensure high-quality services and deliverables. A description of how communication between stakeholders (Air Force, Contractor, Regulators, and Community) will be maintained using a communication hierarchy.

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

(a) Key Personnel Qualification and Parameters: The Offeror shall submit resumes for the following key personnel:

• Program Manager

• Program Chemist

• Program QA/QC

• Program Health and Safety Manager

• Superintendent for Construction

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

(a) The Offeror shall submit a maximum of five project summaries (narrative) demonstrating relevant experience as it relates to this PBR. The Government will not consider performance on a project that concluded more than five (5) years prior to the date of this solicitation. For projects that are actively being performed, performance must be substantially complete (minimum 51% of work completed as of the date of solicitation for this contract). Projects submitted by the Offeror should be the most relevant in demonstrating the Offeror’s ability to perform the proposed effort. Three (3) of the five (5) projects must be from the Prime contractor or a Teaming Partner with a formal teaming arrangement. The Offeror shall include the exact same copies of the project summaries in the volume for Factor 2, Past Performance. Project Summary Submissions shall include the following:

• An individual task order or delivery order or stand-alone contract with an initial award value of greater than $5 Million

• The individual task order or delivery order number, or stand-alone contract number

• 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. Focus on the SOO aspects identified in the Technical Subfactors 1.1, 1.2, and 1.3.

• Number of Environmental Sites.

• Type of contract, i.e. Firm Fixed Price (FFP), Time and Materials (T&M), Cost

Plus Fixed Fee (CPFF), etc.

• Original award amount and final total dollar amount (or estimate at completion) including modifications and options. If the project is currently ongoing, provide the percent of work complete at the time of proposal submission.

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

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

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

4.11 Subfactor 1.5 – Extent of Participation of Small Business Concerns Include all information concerning Extent of Small Business Participation in Volume V, if applicable.

5.0 VOLUME III – FACTOR 2: PAST PERFORMANCE

5.1 Volume organization:

(a) Executive Summary (duplication of executive summary in Volume I, Contract

Documentation)

(b) Table of Contents

(c) List of Tables and Figures

(d) Glossary of Abbreviations and Acronyms

(e) Teaming Arrangements and/or Letters of Intent

(f) Present/Past Performance Summary

(g) Organization Structure Change History

(h) Past Performance Information Sheet

(i) Present/Past Performance Questionnaires (PPQ) (Attachment L-3)

(j) Consent Letter(s) (Attachment L-4)

(k) Client Authorization Letter(s) (Attachment L-5)

5.2 Standard Proposal Information

(a) Provide a Table of Contents for Volume III per Instructions to Offerors (ITO) paragraph 2.3.7.

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

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

5.3 Past Performance Summary

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

AFB 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 requirements of the Technical Sub-factors.

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

5.4 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

5.5 Past Performance Information Sheets

The Offeror shall provide copies of the project summaries under Corporate Experience as a part of the submission for this Factor. Projects must demonstrate relevant experience in that projects submitted are of a nature similar to the efforts addressed under this solicitation in terms of size, scope, and technical and regulatory complexity in accordance with the requirements outlined in the SOO. The Government will not consider performance on a project that concluded more than five (5) years prior to the date of the solicitation. For projects that are actively being performed, performance must be substantially complete (minimum 51% complete as of the date of solicitation for this contract). Information provided in the Past Performance Information (PPI) Sheets will assist the Government in determining both the relevance and confidence ratings for past performance.

5.5.1 Specific Content

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.6 Past Performance Questionnaires (PPQs) – Early Proposal Information

5.7 Consent Letters

The Offeror shall provide original consent letters from each team member and/or joint venture partner using the format (or similar) provided at Attachment L-4. This letter allows the release of team member adverse present/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. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

5.8 Client Authorization Letters

(a) The Offeror shall provide original client authorization letters for the Prime and each team member and/or joint venture partner who…