DRAFT_VAFB_PBR_SOO_022013.docx

FA8903-12-R-0033

520 December February 20122013

STATEMENT OF OBJECTIVES (SOO)

FOR

PERFORMANCE-BASED REMEDIATION (PBR)

AT

VANDENBERG AIR FORCE BASE, CALIFORNIA

SOLICITATION NUMBER: FA8903-12-R-0033

CONTRACT NUMBER: TBD

520 December February 20122013

1.0 SCOPE

This requirement is for environmental remediation activities at Vandenberg Air Force Base (VAFB), California. This Statement of Objectives (SOO) defines the scope of 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 one hundred and seven (107) Installation Restoration Program (IRP) sites.

Introduction

VAFB covers approximately 100,000 acres along the central coast of California. It began as a World War II Army Camp in 1943; however the current Air Force mission is military/commercial space launches. Neither VAFB as a whole, nor any of its sites, is on the National Priorities List (NPL). Regulatory oversight is provided through a Federal Facility Site Remediation Agreement (FFSRA) with California Department of Toxic Substances Control (DTSC) and the Central Coast Regional Water Quality Control Board (RWQCB). There is also involvement with California Department of Fish and Game (DFG) and US Fish and Wildlife Service (USFWS) as stakeholders. Underground storage tanks are remediated pursuant to the Santa Barbara County Leaking Underground Fuel Tank (LUFT) regulations. The State Water Resources Control Board (State Water Board) recently adopted (May 1, 2012) the Low-Threat Underground Storage Tank (UST) Policy for total petroleum hydrocarbon (TPH) sites. This policy establishes several scenarios accounting for both general and media-specific criteria (groundwater, soil, and soil vapor) that ensures the protection of human health, safety and the environment pursuant to Health and Safety Code section 25296.10.

VAFB utilizes a base-wide groundwater monitoring program (BGMP) which includes all monitoring and sampling once contamination has been demonstrated at a site during the Remedial Investigation (RI). The BGMP is in the Remedial Process Optimization stage (or Remedial Action- Operation [RA-O] phase) stage. The Base has recently obtained agreements with the State stakeholders on updating the decision tree flow chart and procedures for optimization as outlined in the Draft Basewide Groundwater Monitoring Program Work Plan Addendum, dated May 2012. The program has recently received agreements to switch from separate BGMP and RA-O reports to a combined site-specific Groundwater Monitoring and RA-O report format.

1.2 General PBR Scope and Requirements

The Contractor must perform all the necessary environmental construction and engineering activities as required to meet the performance objectives of this SOO.

Enclosure 1 lists the sites included in the scope of this contract.

The Air Force is required to implement remedies as necessary to protect human health and the environment. The intent of the PBR initiative is to maximize the number of Site Closeouts (SCs) or advance sites as close to SC as practicable during the period of performance (POP) and in a cost effective manner. It is desirable to the Air Force that life-cycle costs (LCC) be reduced. The Air Force is interested in substantial reduction of long-term environmental liabilities and LCCs through accelerated achievement of SC and optimization of environmental restoration activities for all sites included in this contract while complying with applicable federal, state and local laws and regulations; and applicable base-specific orders, agreements, or rules. General performance objectives pursuant to the Air Force’s overarching goals are listed below in order of priority:

1) Achieve SC as defined in Enclosure 5 4 during the POP.

2) For any site not achieving SC during the POoP, achieve, in order of priority;

a. Response Complete (RC)

b. Remedy in Place (RIP)

c. The furthest objective within the regulatory structure for each site (e.g. Decision Document (DD), Preliminary Assessment/Site Inspection (PA/SI), etc.)

3) The Contractor shall develop an Optimized Exit Strategy (OES) for sites identified in Table 1 that have an approved decision document prior to, or during the POP, but do have not achieved SC. The Contractor shall describe the strategy in an OES Plan to meet the following objectives:

· Maintain compliance with all decision documents and plans (currently in place or to be approved) until no longer required or an alternate approach is approved.

· Correct Five-Year Review deficiencies where identified as no longer protective of human health and the environment at all sites.

· Apply innovative technologies to minimize the cost and duration of operating, monitoring and treatment.

· Improve the understanding of the conceptual site model (CSM), existing systems, and contamination sources to support optimization.

· Provide an analysis of alternatives for each site to aggressively accelerate treatment and progress to expedite SC. Alternatives shall include engineering cost estimates, conceptual designs, and business case analyses.

· Develop performance indicators, decision criteria, and objectives consistent with the performance model described in item 4 below that will be used to optimize remedial efficiency, quantifyassess how the response is progressing and demonstrate when the objective has been reached. An OES Plan shall be delivered within one year from either date of award or exercise of the option of the SubCLIN, whichever is applicablenotice to proceed (NTP). An OES Implementation Completion report shall be delivered upon completion of the implementation of the optimization efforts in the approved OES Plan, and one of the final milestones shall be an OES Effectiveness Report.

· The OES Effectiveness Report shall include:

a) Documentation of what remedial strategies were implemented, what remains to be implemented, and any modifications to the OES arising from performance to date.

b) A realistic schedule to achieve SC or RC after the POP (the Contractor shall identify which performance objective is the ultimate optimal endpoint). For sites with an indeterminate endpointproject completion date, a schedule for 30 years including the POP is required.

c) The remaining definable and measurable milestones after the POP.

4) For all sites listed in Table 1 that have an approved decision document prior to or during the POP and are not being proposed to SC during the POP, the Contractor shall develop performance models that describe the expected course of the remediation process (i.e. how conditions are expected to change over time as measured using appropriate performance indicators from the current state until the performance objective is achieved). For all sites being proposed to SC during the POP, the work planning documents are expected to contain the performance model. The Contractor shall provide monitoring reports that demonstrate whether or not the remedial approach is performing in accordance with the performance model. For purposes of reporting Contractor progress and status, these conditions shall be qualified by performance indicators relevant to the proposed remedial approach. A performance model is a graphic representation of a performance indicator value over time until a performance objective is achieved. Several indicators may be needed to adequately reflect performance. The Contractor shall report the actual remedy performance compared to projected performance. The Contractor shall ensure consistency and continuity of information regarding performance between the Project Management Plan (PMP), Integrated Master Schedule (IMS)/Milestone Payment Schedule (MPS), and OES Plan.:

Develop performance models that describe the expected course of the remediation process (i.e. how conditions are expected to change over time as measured using appropriate performance indicators from the current state until the response objective is achieved). A performance model is typically a graphic representation of a performance indicator value over time until a response objective is attained. When fully developed in an OES Plan, a performance model provides sufficient detail to transparently evaluate actual progress against proposed goals and provides the technical basis to justify payment of the proposed SubCLINs. A fully developed performance model includes identification of baseline conditions specific to the proposed performance indicator(s), locations and frequency of performance-data collection, mechanics of the data interpretation or analysis (e.g., statistic used to summarize performance data), identification of key milestone dates for tracking progress, and logic to be used to support decisions regarding achievement of progress milestones prior to the end of the POP, as well as overall performance goals at the end of the POP. The performance model shall be tied to the payment milestones, PMP, and surveillance plan.

Provide monitoring reports that demonstrate whether or not the remedial approach for each site is performing in accordance with the performance model. For purposes of reporting Contractor progress and status, these conditions shall be quantified by performance indicators relevant to the proposed remedial approach. Several indicators may be needed to adequately reflect performance. The Contractor shall report the actual remedy performance compared to projected performance (extrapolation of historical data for remedy at the time of proposal), and estimated performance (based on the Contractor’s approach). The performance model shall be tied to the payment milestones, PMP, and surveillance plan.

Within the construct of the goals and objectives above, those sites with minimum performance objectives (Table 1) to be achieved for each site during the POP for this contract are outlined in Table 1 of the SOO. If the Contractor anticipates the ability to achieve a higher level objectivestretch goal during the POP, the Contractor is encouraged to propose an approach for the alternate objective, which will then become the requirement of the contract (applicable to sites in Table 1 only). The Contractor shall specify the performance objective (to include at least the minimum performance objective as listed for Table 1 sites) and date they intend to achieve it for each site within the POP. Contractors shall explain why the selected performance objectiveend point (including the minimum performance objectiveacceptable endpoint if that is what is proposed) is the optimum solution for the Government. It should be noted that the AF reserves the right to not to exercise all options not awarded at the time of contract award.

Table 1: Minimum Performance Objectives

All Sites

Approved Project Management Plan (PMP):

· Draft Preliminary PMP within 30 calendar days of contract award.

· Final Preliminary PMP within 14 calendar days of receipt of COR comments on the drafts.

· Updated Final PMP expected approximately 4.5 years after the Final Preliminary PMP.

· Time-phased updates, submitted annually (at minimum) or more frequently, as appropriate to maintain accuracy and completeness.

Air Force approval through the Contracting Officer’s Representative (COR).

Provide support (supplying documents to independent reviewers and participation in meetings/interviews) for Five-Year Reviews required for all site(s) identified inunder this Ccontract for the duration of the contract. Correct any remedy or site deficiencies noted in Five-Year Reviews. VAFB plans to consolidate the Five-Year Reviews. A review will be completed in FY13, then another in FY17, then one every five years thereafter.

Air Force approval through the COR and Regulator approval (e.g., formal documentation accepting correction of deficiencies).

Beginning at Notice to Proceed (NTP), or upon achievement of RIP or RC, or any performance objective that is not SC, conduct, as appropriate, RA-O and/or Long Term Management (LTM) and develop an OES to achieve SC and implement the elements of the approved strategy that fall within the POP. RA-O/LTM and implementation of the OES shall continue through the duration of the POP or 1) until no longer required based on Air Force and regulatory concurrence that SC has been achieved, or 2) Air Force and the regulators have approved on implementation of an alternate approach as approved by the AF and state regulators.

Air Force approval through the COR for RA-O/LTM reports and Regulatory approval as required (e.g., formal documentation accepting the RAO/LTM report).

Air Force approval through the COR for OES Plan and OES Effectiveness Report and approval of t. Regulatory approval required documentsof plans and reports resulting from implementation of the OES.

Site Specific

Achieve SC within one (1) year from NTP at the following sites:

· SS333 – BLDG. 13852

· TA549 – BUILDING 11777

· TU561 – BLDG. 13017

· TU563 – BLDG. 13020

· TU580 – BLDG. 06008

· TU582 - DEMO BLDG. 06335

· TU587 - BLDG. 07015

· CD124 - CE MAINTENANCE

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of SC documentation for unrestricted use).

Achieve SC within two (2) years from NTP at the following sites:

· TU329 – BLDG. 7312

· OW512 – O/W SEPARATOR AT BUILDING 10711B

· OW264 – O/W SEPARATOR AT BUILDING 6437

· OW519 – O/W SEPARATOR AT BUILDING 1740

· OW231 – O/W SEPARATOR AT BUILDING 11559

· OW262 – O/W SEPARATOR AT BUILDING 10660

· CB024 - Anderson Peak Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of SC documentation for unrestricted use).

Achieve SC within three (3) years from NTP at the following sites:

· SA283 – BLDG. 06817

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of SC documentation for unrestricted use).

Achieve SC within five (5) years from NTP at the following site:

· TU197 – BUILDINGS 510 – 511

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of SC documentation for unrestricted use).

Achieve RC within two (2) years from NTP at the following sites:

· ST042 - COMPONENT DECONTAMINATION FACILITY

· SA320 – BUILDING 07304

· AB139 – BUILDING 3340, FORMER CAMP COOKE WASTE INCINERATOR

· TU346 – FORMER AIRMEN DINING HALL (BLDG. 21180)

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of RC documentation).

Achieve RIP within two (2) years from NTP at the following sites:

· MY240: FORMER BUILDING 9310

· TU670 - BUILDING 11670

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of acceptance of RIP documentation).

Achieve RIP within three (3) years from NTP at the following sites:

· TU077 - BUILDING 7425

· CG147 - BLDG. 8401

· TU174: BLDG. 9340

· SA228: BLDG. 07426

· MY247 – FORMER BUILDINGS 6441 AND 6451

· MY248 – FORMER BUILDINGS 6442 AND 6452

· MY249 – FORMER BUILDINGS 6443 AND 6453

· MY250 – FORMER BUILDINGS 7306 AND 7315

· MY251 – FORMER BUILDINGS 7307 and 7316

· SA251 – BLDG. 06436

· SA280 – BLDG 6605 FORMER (CAP)

· SA288 – BLDG. 07437

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of acceptance of RIP documentation).

Achieve RIP within four (4) years from NTP at the following sites:

· SS004 - LAUNDRY SITE

· SD015 - ABRES-B LAUNCH COMPLEX

· SD024 – ENTOMOLOGY WASH RACK

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of acceptance of RIP documentation).

Achieve RIP within five (5) years from NTP at the following sites:

· SS003 - OLD RAILROAD PUMPING STATION

· WP005 – SITE 5 CLUSTER

· ST171 – BLDG 1110 – 1113

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of acceptance of RIP documentation).

Achieve RI within two (2) years from NTP at the following site:

· PL351 – CAMP COOKE FUEL DISTRIBUTION LINES

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of acceptance of RI documentation).

Complete PA/SI within two (2) years from NTP for the following sites:

· TU003 – BUILDING 5003

· TU004 – BUILDING 5004

· TU008 – BUILDING 5008D

· ZZ025 - TT-10-AREA-7

· TU044 – BUILDING 1971 – 2

· TU055 – BUILDING 1987

· TU067 – CC-34-9 AND 26

· TU100 – BUILDINGS 13320, 13322

· TU101 – BUILDING 10103

· TU103 – BUILDING 13323

· TU105 – BUILDING 4105

· TU107 – FORMER BUILDINGS 660, 665, AND 668 (FORMER AOI – 107)

· TU114 – FORMER BUILDING 475

· TU115 – FORMER BUILDING 490

· TU129 – BUILDING 6512

· TU130 – BUILDING 13850

· TU133 – BUILDING 7133

· TU136 – BUILDING 4136

· TU187 – FORMER BUILDING 10122

· TU196 – BUILDING 3196

· TU205 – BUILDING 1974

· TU206 – BUILDING 2206

· TU216 – BUILDING 1731

· TU221 – BUILDING 1756

· SA323 – SS-C323 Bldg. 6811 - MISSILE STORAGE IGLOO (FORMERLY AOC-323)

· TU328 – BUILDING 13512

· TU347 – FORMER CAMP COOK DORMITORIES

· TU358 – UST AT FACILITY 23205

· TU416 – DATA COLLECTION REPORTING STATION (BUILDING 22100)

· TU424 – NASA ADMINISTRATION BUILDING (BUILDING 840)

· TU446 – ELEVEN FUEL OIL USTs

· TU448 - BUILDING 4448

· TU459 – CAMP COOKE BLOCKS (CC-37-4000, 4100, 4200, 4300)

· TU472 – BUILDING 2472

· TU476 – BUILDING 725

· TU494 – BUILDING 302

· TU526 – BUILDING 2526

· TU537 – FORMER BUILDINGS 11168 AND 11173

· TU544 – CORRECTIONAL FACILITY (BUILDING 11477)

· TU574 – BUILDINGS 13122 AND 13123

· TU578 – BUILDING 13330

· TU605 – BUILDING 10103

· TU606 – CAMP COOK BUILDINGS (AIRMEN DORMITORIES)

· TU608 – CAMP COOK BUILDINGS (i)

· TU649 – CAMP COOK BUILDINGS (II)

· TU713 – BUILDING 1713

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval of the PA/SI report and either a regulator-approved No Further Remedial Action Planned (NFRAP) or Air Force-approved Technical Memorandum establishing the Data Quality Objectives (DQOs) for the Remedial Investigation (RI) (e.g. written confirmation of acceptance of documentation).

Complete PA/SI within one (1) year from NTP for the following site:

· TU788 - BUILDING 1788

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR and Regulator approval of the PA/SI report and either a regulator-approved No Further Remedial Action Planned (NFRAP) or Air Force-approved Technical Memorandum establishing the Data Quality Objectives (DQOs) for the Remedial Investigation (RI) (e.g. written confirmation of acceptance of documentation).

Develop an OES to achieve SC and implement the elements of the approved strategy that fall within the POP at the following sites:

· ST001 - BX SERVICE STATION

· SS002 - OLD SERVICE STATION

· WP008 – SITE 8 CLUSTER

· WP013 – SITE 13 CLUSTER

· LF018 - LANDFILL NOS 3 & 4

· SD019 - BLDG. 836

· LF020 - LANDFILL NO 1/ DRUM DISPOSAL SITE/UST

· FT021 - FIRE TRAINING AREA NUMBER 1

· LF022 - LANDFILL NO 11

· LF023 - LANDFILL NO 5

· SD025 – SITE 25 CLUSTER

· SS027 - EXPLODED MISSILE SILO

· SD031 - MISSILE SILO 576-C

· SD032 – SITE 32 CLUSTER

· SD033 - MISSILE SILO 576-E

· SS050 - BIONETICS BUILDING

· ST060 - GSA SERVICE STATION

· DC142 - CE MAINTENANCE FACILITY, BUILDINGS 837 AND 839

Compliance with the FFSRA and associated schedules.

Air Force approval through the COR demonstrating achievement of quantitative performance goal as defined in the AF approved OES Plan and approval of Regulatory required documentsof optimized exit strategy and Regulator concurrence with Air Force approved reports confirming implementation of the strategy (e.g. written confirmation of acceptance of documentation).

Specific performance goals per the proposed performance model shall be incorporated upon award.

This SOO and enclosures listed below include general requirements of the project to meet the Air Force objectives.

· Enclosure 1 – Site List

· Enclosure 2 – Key Documents

· Enclosure 3 – Gov. Furnished Equipment (GFE)/Gov. Furnished Property (GFP)

· Enclosure 4 – Document Review Process

· Enclosure 5 4 – Acronyms and Definitions

· Enclosure 6 5 – Format For Metadata and .pdf Documents

The Contractor shall function as an integral team member in support of the Air Force Civil Engineer Center (AFCEC) mission, to include the sharing of information with other AFCEC contractors and Air Force personnel, and cooperation with community stakeholders, regulators, and other government entities.

Requirements for efficient management of the contract include, but are not limited to, the submission of accurate, on-time, quality contract deliverables and timely identification and solution of impediments to successful project execution. Technical requirements include, but are not limited to, early involvement with stakeholders in the process to allow for the development of the most cost-effective and technically sound approach or solution. AFCEC will rely on the Contractor’s expertise in recognizing and addressing problematic issues and successful execution of this contract. The Contractor shall perform all work in accordance with federal, state, and local statutes and regulations. The Contractor shall also comply with base regulations. Remedies shall conform to environmental permits, decision document requirements, or other legal requirements.

APPLICABLE DOCUMENTS

The Contractor shall identify and comply with all applicable federal, state, and local statutes; Air Force/Military instructions, manuals, handbooks, regulations, guidance, and policy letters (including Air Force policy and guidance for IRP, Compliance Restoration Program [CRP], and Military Munitions Response Program [MMRP]); Executive Orders (EOs); American Society for Testing and Materials (ASTM); American Petroleum Institute (API) Codes; National Association of Corrosions Engineers (NACE); National Fire Protection (NFPA); Steel Structures and Painting Counsel (SSPC); National Electrical Code (NEC); Uniform Fire Code (UFC); and International Building Code (IBC) including all changes and amendments in effect on the date of issuance of this contract. It is the Contractor’s responsibility to identify and comply with all applicable requirements. In addition, the Contractor shall refer to the current versions of the Department of Defense (DoD) Policy and Guidelines for Acquisitions Involving Environmental Sampling or Testing and The United States Air Force Construction Management Implementation Guide.

The Contractor shall identify and comply with all applicable documents for the base including Records of Decision (RODs), ROD Amendments, Explanation of Significant Differences (ESDs), Resource Conservation and Recovery Act (RCRA) Permits and subsequent modifications, Risk Evaluation Corrective Action Program (RECAP) documents, the Endangered Species Act, other Decision Documents, Deeds, and conveyance notices. Key base-specific documents are listed in Enclosure 2.

The Contractor is solely responsible for reviewing all publicly available information and forming their independent, professional conclusions/interpretation of site conditions and requirements to meet achieve the performance objectives of this contract. The information provided in this SOO is not intended as a substitute for complete analysis of technical data available, nor is it intended to be a guide for on how the Contractor to should address achievement of the performance objectives.

GOVERNMENT FURNISHED INFORMATION, EQUIPMENT, AND PROPERTY (GFI, GFE, GFP)

Government Furnished Information is listed in Enclosure 2, Key Documents. The Air Force believes that documentation provided with the solicitation represents the most recent and appropriate documentation available for the Installation and sites identified in this contract. However, if there is a conflict between this information and other site documentation (the existing reports), the Contractor is solely responsible for reviewing all available information and forming their independent, professional conclusions/interpretation of site conditions and requirements to meet the objectives of this contract. Specific documents may be made available following a request to the Contracting Officer (CO) if the documentation can be distributed in a timely manner. Electronic format is not guaranteed.

The Contractor shall properly account for and manage all new and existing GFE and/or GFP procured and utilized at the base in accordance with the applicable Federal Acquisition Regulation (FAR). Lists of GFE/GFP are provided in Enclosure 3.

Remediation systems may or may not be listed as GFE and/or GFP. The Contractor is responsible for providing all other supplies and equipment, not already installed and not listed in Enclosure 3, required to meet the performance objectives of this contract. All Air Force owned property used for remediation purposes must be maintained by the Contractor in accordance with applicable maintenance requirements. The Contractor is responsible for proper return or disposal of excess or unserviceable equipment or materials as required during the duration of this contract. Prior to disposal of excess or unserviceable equipment listed in Enclosure 3, the Contractor shall coordinate activities with the CO for disposition instructions.

MANAGEMENT, PLANNING, AND REPORTING REQUIREMENTS

The Contractor shall implement a full range of construction and engineering activities as required to meet objectives of this contract and in accordance with all applicable base, regulatory, and site requirements. The Contractor shall supply all labor, equipment, and materials necessary to accomplish the work. The Contractor shall perform management and planning functions, including performance measurement and fund status reporting.

Milestone Payment Schedule (MPS)

Milestone payments shall be based on the completion of a definable and measurable steps, which areis considered integral and necessary to the achievement of the stated performance objectives. Completion of milestones shall demonstrate payment is appropriate and warranted. Air Force approval of the documentation supporting the completion of the milestone is required for payment (for example, Air Force approval of Draft Remedial InvestigationRI report, Air Force acceptance that interim and final performance goals per approved performance models have been achieved). Where regulatory acceptance/concurrence is required for this documentation, Air Force acceptance of the milestone will occur following regulatory acceptance/concurrence with of the documentation (for example, DTSC and RWQCB approval of Final Record of DecisionROD). For milestones where regulatory acceptance/concurrence is required and regulatory acceptance/concurrence cannot be obtained, the Air Force will evaluate the Contractor’s documents to determine if they are legally and technically acceptable to warrant payment for achieving that milestone.

The Contractor’s proposed MPS may require restructure of Sub-Contract Line Item Numbers (CLIN)/ (Sub-CLINs), if necessary, to align with projected available funding prior to award; however the MPS is not final with award of the contract. Changes made to the MPS prior to award are used to finalize the Sub-CLINs description and value. Award of the contract does not equate to final acceptance of the MPS. The MPS shall be included as part of the Project Management Plan (PMP). The MPS will be negotiated during development of the PMP and may require additional changes. The Contractor shall submit the MPS in an electronic format consistent/compatible with the AFCEC SharePoint website, eDASH. Final decisions regarding the adequacy of milestone and deliverable completion resides solely with the COR. The COR will take into consideration the appropriate acceptance and/or concurrence of necessary site remediation documentation by regulators, consistent with applicable regulatory drivers of this SOO.

Management and overhead type costs (program/project management, monthly reporting, mobilization costs, etc.) do not provide measureable program advancement and are not appropriate milestone payments. These costs/expenses should be allocated into site, site grouping, or Operable Unit (OU)-related milestone payments that provide demonstrable value to the program. Milestones shall not represent a “progress” payment or a monthly payment for level of effort expended. Completing site mobilization/demobilization (unless exempted by CO), accomplishment of field activities, or submittal of a monthly status or Operation and Maintenance (O&M) reports are examples of unacceptable milestone payments.

The first deliverable milestone required in the MPS is the Preliminary Opening Phase PMP. The PMP deliverable milestone shall be contract inclusive. The Contractor shall not allocate costs to specific sites or include indirect costs associated with sites. Upon determination of bona fide need, a second PMP Sub-CLINmilestone for the Final Closing phasePMP may be implementedexercised. The Both PMPs shall be updated annually or as necessary to remain current with the approved execution strategy.

The Contractor shall complete an MPS and identify milestone payments, performance standards, and the associated payment schedule on a site by site basis. The Contractor may also propose logical groupings of sites or OUs for milestone payment purposes where an approach provides greater efficiency for the program; however, a Sub-CLIN involving multiple sites shall identify milestones by individual sites in order to support Air Force reporting requirements. Achievement of the awarded performance objective for Table 1 sites shall be the final payment milestone for each Sub-CLIN.includes the minimum end state milestones acceptable to the Government. Potential CLINs and Sub-CLINs are described in the CLIN/MPS/IMS Guidance.

The number of milestone payments per site should be limited to a reasonable amount based on the scope and anticipated duration to achieve the performance objective at the site. The Contractor is limited to one invoice submitted to AFCEC per month. The invoice must itemize the milestone payments and costs for each site or grouping associated with the invoice.

If the Contractor has to continue working beyond the performance objective date The Contractor may continue working to achieve a final milestone (applies to Sub-CLIN dates only) the Contractor shall submit a period of performance extension request to the Contracting Officer at least 60 days prior to the expiration date of the Sub-CLIN.beyond the performance objective date. However, the Contractor shall not perform work after the funding associated with the milestone cancelsexpires. Specifically, completion of activities on an individual Sub-CLIN cannot exceed 30 days prior to the end of the fiscal year; five years from the date of exercising of the Sub-CLIN. However, the Contractor will not receive payment until milestones are achieved in accordance with the MPS. The Contractor may receive a negative past performance rating for delays in achievement of impacted performance objectives.

Though the contractor can continue work beyond the period of performance until approximately two months from expiration of funds, the government may require consideration or cause the contractor to continue work in delinquent status should a delays be determined to be the fault of the contractor.

Project Management Plan (PMP)

The Contractor shall develop and maintain a detailed PMP. The PMP shall include the Technical Approach, Integrated Master Schedule (IMS), and MPS, prepared as part of the Contractor’s proposal. In addition, the PMP shall specify the resources required for the planning, execution, control, and completion of the stated performance objectives. At a minimum, the PMP shall include the following sections: technical approach, performance objectives in accordance with the SOO, draft Performance Models, organization and integration of the project team, schedule management and project controls, transitional activities, risk management, Sub-CLIN management, quality management, health and safety management, project communications with stakeholders, procurement management, and security management. The PMP should identify the project’s resources and project tasks corresponding to the CLINs/Sub-CLINs for this contract.

In order to align with the availability and expiration of Government funds, the Contractor shall prepare two versions of the PMP. The initial (or opening phase) PMP will govern activities from award to the midpoint of the POP. The closing phase PMP will govern activities from the mid-point of the POP to the end of the POP and will be funded approximately 4.5 years from contract award or upon CO determination of bona fide need.

The first draft of the Preliminary Opening Phase PMP shall be due within 30 calendar days of contract award and subsequent revisions shall be subject to Air Force review and approval. The revised version of the Opening Phase PMP shall be Draft version of the Preliminary PMP and subsequent revisions shall be subject to Air Force review and approval. The Final version of the Preliminary PMP shall be due within 14 calendar days from the Contractor’s receipt of Air Force comments on the Draft version. The PMP shall be updated annually, or as necessary, throughout the contract to remain current with the approved execution strategy.

A first draft of Closing Phase Final PMP shall be due within 30 calendar days of contract award and subsequent revisions shall be subject to Air Force review and approval. The revised version of the Closing Phase PMP shall be due within 14 calendar days from the Contractor’s receipt of Air Force comments. The PMP shall be updated annually, or as necessary, throughout the contract to remain current with the approved execution strategy., and subsequent annual updates, is expected approximately 4.5 years after the approval of the Final version of the Preliminary PMP. The Final Preliminary PMP, annual updates, and the Final PMP shall be submitted in an electronic format consistent/compatible with the AFCEC SharePoint website, eDASH.

The final milestone for the Preliminary Opening Phase PMP Sub-CLIN shall be a Project Status Summary and for the Final Closing Phase PMP Sub-CLIN shall be a Project Closeout Summary.

The Project Status Summary and Project Closeout Summary shall include summaries of the following: progress on achievement of objectives, progress on achievement of milestones including performance models, actual performance against Performance Models, schedule achievements or delays, issues and risks, and other performance indicators as required by the CO or COR. In addition, the Project Closeout Summary shall include required information to support closeout of the contract as defined by the CO and COR.

Project Web Site

The Contractor shall maintain a document repository for all PBR documents to include, but not limited to information on meetings, documents submitted, Sub-CLIN details, milestone status as agreed to in the PMP; current topics associated with the PBR, basic PBR statistics and objectives, stakeholder Point of Contact (POC) information; calendar of events, meetings milestones; laboratory results and reports, 3D conceptual models; groundwater reports, analysis, studies; links to administrative records/information repository records and to associated appropriate reference documents- state and federal policy guidance; and key performance indicator tracking.

The repository is intended to be a single access point repository for all PBR documentation. It shall be accessible to all stakeholders during the life of the PBC. The Contractor shall provide notifications to the COR, CO, and Base POC at the time data is included in the repository. At close-out, all repository documents will be transferred to DVD media and delivered to the AF, and placed on the AFCEC contractor drop-zone website (address provided under separate cover).

The Contractor shall maintain a web-based project folder for the PBR to include, but not be limited to information on meetings, documents submitted, Sub-CLIN details, milestone status as agreed to in the PMP; current topics associated with the PBR, basic PBR statistics and objectives, stakeholder Point of Contact (POC) information; calendar of events, meetings milestones; laboratory results and reports, 3D conceptual models; groundwater reports, analysis, studies; links to Administrative Record/Information Repository records and to associated appropriate reference documents- state and federal policy guidance; and key performance indicator metrics tracking.

The web-based project folder is intended to be a single access point repository for all PBC documentation. The web-based project folder shall be accessible to stakeholders during the life of the PBC. The Contractor shall notify the COR, CO, and Base POC at the time data is posted to the web-based project folder. At close-out, all documentations on the web-based project folder will be transferred to DVD media and delivered to the Air Force, and placed on the AFCEC contractor Sharepoint drop-zone. Periodic format adjustments during the life of the PBC will be required to ensure consistency and will be provided by the COR. Stakeholders will be provided passwords in accordance with appropriate security level restrictions.

1.1 Schedule and Planning Requirements

The Contractor shall provide a monthlyn IMS for tracking work progress as described below.

1.1.1 Integrated Master Schedule (IMS)

The Contractor shall prepare and submit an IMS for approval. The Contractor must that includes activities and milestones at a detailed level and presents sequenced events for completion of the proposed performance objectives within the time designated and any critical path items that may affect the Contractor’s ability to meet the schedule. The Contractor must include and identify all performance project milestones and payments consistent with the approved MPS. Sites associated with each milestone/task must be noted in the schedules using the Site IDs and referencing all site aliases noted in Table 1 and Sub-CLINs. The schedule shall be provided in initial hardcopy and subsequently in electronic format consistent/compatible with Air Force software, currently Microsoft Project, and in Adobe Acrobat portable document file (.pdf). Updated and revised schedules shall be submitted electronically to the AFCEC SharePoint website with monthly status reports with changes clearly identified by the Contractor.

Cost and Status Reporting

The Contractor shall provide a cost and status reports as described below.

Contractor’s Progress, Status, and Management Report (CPSMR)

The Contractor shall prepare and submit a monthly CPSMR. The CPSMR shall be used to review and evaluate the overall progress of the project, along with any existing or potential problem areas. The report shall be prepared in a format coordinated with the COR. The CPSMR shall also be used to indicate whether efforts for each site are on target for meeting the Contractor’s proposed performance objective.

The CPSMR shall include a summary of the events that occurred during the reporting period, discussion of performance, identification of problems, proposed solutions, corrective actions taken, outstanding issues, and payments made toward the MPS to date.

The Contractor is required to report monthly, quarterly, and yearly metrics. The reporting format will be via the AFCEC Contractor’s PBC website and AFCEC’s SharePoint website, e-DASH. . The Contractor will be required to upload the following reports:

· Monthly: % expensed, % complete, and % on time addressing each Sub-CLIN for an AF dashboard roll-up.

· Quarterly: Performance indicators (PIs) associated with a performance model for each site, for an AF dashboard roll-up. Examples for consideration include:

· Mass loading rate

· Volumetric loading rate

· Mass removal rate

· Cumulative mass removed

· Unit cost

· Cumulative cost

· Variable operating cost

· Mass flux

· Energy consumption rate

· Greenhouse gas emission rate

· Decay rate

· Reaction rate

· Center of mass

· Disturbances

· Water consumption rate

· Percent time pump and treat systems are operating

· gallons of GW treated;

· qty/pounds of contaminant removed from water;

· qty/pounds of contaminant removed from soil;

· energy saved using energy saving techniques compared to std approach;

· qty/pounds of recycled material;

· acreage returned for beneficial/mission use;

· Number of sites to SC, LTM, RC, RIP, RI, NFA, NFRAP, OES, of total anticipated for this PBR (i.e. 3/7 SC, 2/9 NFA, 5/15 NFAR, 2/42 OES)

· Yearly: Data in support of the Annual Report to Congress as applicable, to include, but not be limited to the following:

· gallons of GW treated;

· qty/pounds of contaminant removed from water;

· qty/pounds of contaminant removed from soil;

· energy saved using energy saving techniques compared to std approach;

· qty/pounds of recycled material;

· acreage returned for beneficial/mission use;

· Number of sites to SC, LTM, RC, RIP, RI, NFA, NFRAP, OES, of total anticipated for this PBR (i.e. 3/7 SC, 2/9 NFA, 5/15 NFAR, 2/42 OES)

The Contractor shall provide the cost for reporting the data as a separate line item in the CPSMR.

The Air Force will use performance indicators and models, in addition to the PMP, to establish and execute a surveillance plan. The Surveillance Plan will highlight key quality control activities or events. The COR will use the Surveillance Plan to determine when Air Force (COR and/or CO) surveillance activities can be conducted to assess progress toward and/or verify completion of milestone payments. The Air Force will communicate surveillance activities internally and with the Contractor. Current guidance on how the Air Force will develop and implement surveillance is will be provided in the Surveillance Plan.

1.2 Meeting and Conference Requirements

1.2.1 Meeting/Teleconference Support

The Contractor shall participate in post-award meetings and Project Management Review (PMR) meetings or teleconferences with the Air Force, as necessary to achieve the performance objectives in this SOO. The Contractor shall coordinate meetings, provide logistical support (e.g., facilities, audio/visual), present materials, and lead technical discussions. The Contractor shall prepare, and submit for Air Force review and concurrence, any presentation materials and agendas for meetings. The Contractor shall prepare minutes for all meetings attended and supply draft minutes for AF review within two weeks of the meeting.

The Contractor also shall attend and/or support meetings and teleconferences to discuss technical or regulatory issues and project progress and status with the Air Force and regulatory agency representatives as required, including applicable meetings such Scoping Meetings per Uniform Federal Policy for Quality Assurance Project Plans (UFP QAPP) requirements,,as Restoration Program Manager (RPM) meetings, Community Advisory Board (CAB) meetings (minimum of two topical presentations), Triad partnering meetings, Tier 1, Tier II meetings and teleconferences. At a minimum, weekly teleconferences shall also be required to discuss in detail progress and any technical or management issues. Also other periodic meetings/teleconferences shall be required, as necessary. However, the frequency of meetings may change based on the status of the environmental restoration program. Key stakeholders at VAFB include RWQCB, DTSC, DTSC Human and Ecological Risk Division (HERO), and DFG. All communications with USFWS pertaining to threatened and endangered species are made through the Base Biologist (30CES/CEANC). The Air Force will be present for all technical and public meetings as well as any teleconferences with the regulatory agencies; however, the Contractor shall coordinate the meetings, provide logistical support (e.g., facilities, audio/visual), present materials, and lead technical discussions. The Contractor shall clearly identify themselves as “Contractors” in all situations involving stakeholders. The Contractor shall prepare, and submit for Air Force review and concurrence, any presentation materials and agendas for meetings. The Contractor shall prepare minutes for all meetings attended and supply draft minutes for AF review within two weeks of the meeting. Travel to/from the Base and to other CONUS locations for such purposes as meeting attendance, briefings and/or presentations may be required in support of this remedial action. These activities are considered incidental to the effort required and shall not be included for separate milestone payments.

The Contractor shall include and coordinate with the Air Force (Installation) prior to any contact with a regulatory agency. A modified TRIAD approach to project management has been found effective at gaining efficient site closeouts at Vandenberg.

Public Meetings and Hearings

The Contractor shall support all community involvement requirements to meet CERCLA, and other regulatory requirements including public meetings, public notices, Corrective Action Board (CAB) meetings, Technical Working Group, public comment periods, and responsiveness summary preparation. There is an active CAB at VAFB that meets quarterly. However, the frequency of meetings listed may change based on the status of the environmental restoration program.

The Contractor shall coordinate and attend teleconferences as necessary with the assigned IRP Project Manager who will complete the necessary coordination with Public Affairs and/or wing staff agencies

Examples of types of Public Affairs requirements include the presentation of technical information and logistical support (e.g., advertising, audio-visual, handouts, report(s), recordings, verbatim transcripts, poster boards, slides, synopses, etc.) for events and/or meetings in support of the government’s position. CAB slides shall be prepared/formatted by the Contractor in accordance with 30 SW requirements and provided to the Base at least four weeks prior to each CAB meeting. All reports and other information generated under this contract shall become the property of the Government, and distribution to any other source by the Contractor is prohibited unless authorized by the COR.

The Contractor shall utilize staff trained in public affairs to complement the technical staff on the project. These trained staff shall attend all meeting with the public along with the appropriate technical staff. The credentials of the trained staff shall be submitted to and approved by the AFCEC COR in advance of any meeting with the public. The trained staff shall demonstrate effective communications experience and experience in building relationships with the stakeholders involved in cleanup activities or similar efforts.

The Contractor shall research, coordinate and provide responses for short-notice internal and external requests for information such as congressional inquiries and media requests as requested by the Public Affairs Officer (PAO) or other applicable action officers. These inquiries require the Contractor to provide the Air Force factual and responsive information within 24 hours of request.

Contractor Documentation

The Contractor shall create and maintain a Master Document List (MDL) that includes all documents, whether the document is a deliverable or not, which are prepared during the course of the contract. The MDL and its documents shall be maintained in libraries readily available for submittal to the government upon request. The Contractor shall maintain the project documents for the duration of the contract and transfer custody to the Air Force within 90 calendar days prior to POP expiration.

The Contractor shall also provide documentation monthly to maintain the installation’s existing administrative record in accordance with established procedures. Refer to “Enclosure 6 5 - Format For Metadata and .pdf DocumentsFormat – Meta Data” for format guidance when providing documents.

Spatial Data (Map) Requirements

The Contractor shall not establish new Geographic Information System (GIS) systems.

In furtherance of the environmental construction or restoration effort, the Contractor shall provide geospatial data and map(s) of installation features (historical, existing, or planned) altered or constructed as required to meet achieve the performance objectives of this contract.

Source data and product data remain the property of the United States government. The Contractor may be required to explain and demonstrate the company's process for protecting all geospatial data, including but not limited to, geometry, attributes, metadata, topologies, and relational database schemas and operations used in association with this SOO. Further information about security and nondisclosure requirements should be obtained from the installation Geospatial Integration Office (GIO).

The Contractor shall provide data to update the GIS and/or computer-aided design and drafting (CADD) files as required to meet achieve the performance objectives of this contract. Source data and product data remain the property of the United States government.

The Contractor shall also ensure that GIS data is submitted in a format compatible with the Air Force GeoBase program, as outlined in the Air Force GeoBase Strategic Plan. The Contractor shall consult with each Base POC and/or installation GIO office to ensure CADD and GIS data is compatible with each installation’s requirements.