Beale_AFB_FY20_Draft_PWS_20190524.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

OPTIMIZED REMEDIATION CONTRACT (ORC)

AT

BEALE AIR FORCE BASE (AFB), CALIFORNIA

CONTRACT NUMBER:

24 MAY 2019

1.0 SCOPE

This requirement is for environmental remediation activities at Beale AFB. This Performance

Work Statement (PWS) defines the scope of environmental services necessary to conduct site restoration. The range of activities include maintenance of established remedies, implementation of optimization to enhance remedial progress at applicable sites, and achievement of site specific objectives as identified in this contract. The Contractor shall undertake Environmental

Remediation activities to achieve performance objectives (POs) at fifteen (15) Installation

Restoration Program (IRP) sites and eight (8) Military Munitions Response Program (MMRP) sites.

1.1 Introduction

Beale AFB is located in northern California about 10 miles east of the towns of Marysville and

Yuba City and about 45 miles north of Sacramento. Beale AFB opened in October 1942 as

Camp Beale and served as a training ground for infantry and armor units. During World War II, Camp Beale was also used as a personnel deployment depot and prisoner-of-war encampment, and was the site of a large hospital. As many as 60,000 personnel were stationed at Camp Beale at that time.

After World War II, Camp Beale was transferred to the Air Force (AF). From 1948 to 1951, it was known as the Beale Bombing and Gunnery Range and was used for bombardier and navigator training. In 1951, the range was designated as Beale AFB and was under several jurisdictions, including the Air Training Command, the Aviation Engineering Force, the

Strategic Air Command, and the Air Combat Command. The first runway became operational in

1958. Over the years, Beale AFB has been associated mainly with AF refueling and reconnaissance missions. In 1959, Beale AFB received its first KC-135 jet Stratotanker, which was assigned to the 903rd Air Refueling Squadron of the 456th Bombardment Wing. B-52s were assigned to the Base between 1960 and 1976. The 4200th Strategic Reconnaissance Wing was activated in 1956. In 1976, the 99th Strategic Reconnaissance Wing was assigned to Beale AFB.

Aircraft, such as the U-2 and SR-71, have been associated with the strategic reconnaissance wings.

Remediation activities for Beale AFB are being conducted pursuant to Comprehensive

Environmental Response, Compensation, and Liability Act (CERCLA), as amended by the

Superfund Amendments and Reauthorization Act (SARA), and National Oil and Hazardous

Substances Contingency Plan (NCP) requirements for all sites except LF002, LF003, PL582, and

SS023 which are being conducted pursuant to the Resource Conservation and Recovery Act

(RCRA), and ST022, TU002, and TU509 which are being conducted pursuant to the State’s

Leaking Underground Fuel Tank (LUFT) program. Regulatory oversight is provided by the

California Department of Toxic Substances Control (DTSC). The Central Valley Regional

Water Quality Control Board (RWQCB) is involved at all sites except for DP038. The Feather

River Air Quality Management District (FRAQMD) is involved at CG044 (plume 013 only), and

CG041-017.

FOR OFFICIAL USE ONLY

Version 5

1.2 Overview of ORC Scope and Requirements

The Contractor shall perform all the necessary environmental remediation activities required to achieve the POs of this PWS. This PWS and enclosures listed below include requirements of the project to meet the AF objectives:

Enclosure 1 – Acronyms and Definitions

Enclosure 2 – Government Furnished Information

Enclosure 3 – Government Furnished Property

The AF is required to implement remedies as necessary to enable the mission, protect human health and the environment, and comply with laws and regulations. The goal of the ORC initiative is to ensure the AF continues to fulfill all facets of its Environmental Restoration

Program (ERP) mission, while effectively and efficiently managing the program in a performance-based, results-oriented, and cost-conscious framework. The AF desires all sites be cleaned up to standards that allow for the current or reasonably anticipated future land use of the property. The intent of the ORC initiative is to advance site cleanup during the Period of

Performance (POP) in the most efficient and cost effective manner as supported by a business case analysis that achieves the greatest reduction in life-cycle cost (LCC). The AF is interested in substantial reduction of long-term environmental liabilities and total LCC. Hand in hand, accurate documentation and reporting of contaminant removal and cost savings are critical adjuncts to optimization success. The AF defines optimization, under the ORC, as the reduction of contaminant mass and concentrations, reduction in LCC, or any combination of activities leading to acceleration of RC/SC, as a result of remedial implementation the Contractor undertakes, above and beyond what is required to maintain compliance in accordance with an approved Decision Document (DD).

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

Army Corps of Engineers (USACE), other AFCEC Contractors and AF personnel; and cooperation with community stakeholders, regulators, and other Government entities.

Requirements for efficient management of this contract include, but are not limited to, the achievement of the POs in the Performance Period (PP) per Table 1 of this PWS, and timely identification and solution of impediments to successful project execution. The Contractor shall provide all personnel, equipment, supplies, tools, materials and other items necessary to perform the tasks defined in this PWS. The Contractor is solely responsible for reviewing all publicly available information and forming their independent, professional conclusions/interpretations of site conditions and requirements to achieve the POs of this contract within PP specified for each site. AFCEC will rely on the Contractor’s expertise in recognizing and addressing problematic issues during the 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

Installation regulations. Remedies shall conform to environmental permits, DD requirements, or other legal requirements.

Site specific POs are identified in Table 1: Performance Table below. POs that are in keeping with standard Defense Environmental Restoration Program (compendium) milestones are defined in Enclosure 1. In addition, for certain categories of sites, the AF has set data-driven

POs based on current site conditions in keeping with the POP of the contract and ORC goal.

These POs are Optimized Exit Strategy (OES), Alternate Objectives, and Reduce LCC; these terms are described below.

The PP specified in Table 1 starts from the Obligation Date of the first Sub-CLIN for the site unless otherwise specified. All approvals (both Government and regulator) per the Performance

Standard are required in writing.

1.2.1 Optimized Exit Strategy (OES)

Not Applicable

1.2.2 Alternate Objectives

1.2.3 Remedial Action – Operation (RA-O) and Reduce Life-cycle Cost (LCC)/Long

Term Management (LTM) and Reduce LCC

Table 1 of the PWS identifies RA-O and Reduce LCC or LTM and Reduce LCC as the

Performance Objective for selected sites in accordance with the optimization initiative. The goal of these POs is to minimize future AF liability and cost to the greatest degree feasible utilizing remedial optimization techniques. Reduce LCC sites have achieved Remedy in Place (RIP) or

Response Complete (RC), have remedies that are effective (source control, risk mitigation, and plume stability) and have the potential for LCC reduction through a variety of optimization actions, for example:

Reducing frequency

Reducing number of wells sampled per event

Reducing number of analytes per sampling event

The Contractor shall achieve the following objectives for each Reduce LCC site:

Maintain compliance with all DDs/Records of Decision (RODs) and Proposed Plans

(currently in place or to be approved)/RCRA Permits throughout the POP.

Deliver a Reduce LCC Plan, as a stand-alone plan or in the PMP, that identifies opportunities to improve cost efficiency of RA-O or LTM activities, and the planned approach for implementation. The Reduce LCC Plan shall:

o Provide a basis for proposed reductions in LCC throughout the POP compared to the cost of status-quo RA-O activities (those required to maintain compliance).

The planned reduction can be illustrated using a line graph (current, planned, achieved) or verbiage describing the current and planned reductions.

o Estimate reduction of LCC proposed within the POP as well as post-POP.

o Document risk and mitigation strategies for implementing optimization activities to reduce LCC.

Update or revise site-specific work plans, monitoring plans, and/or DDs, as appropriate.

Deliver Reduce LCC Reports to document progress in achieving the planned reductions when those reductions are achieved. Reduce LCC Reports may be combined with monitoring reports. Payments for cost avoidance as a result of reductions in required

RA-O activities are contingent upon regulatory approval.

Deliver an RA-O & Reduce LCC Summary and Forecasting Report two years prior to the

POP end date. The Reduce LCC Summary and Forecasting Report shall:

o Document optimization activities to date, the cost avoidance during the PoP (paid to the contractor) as a result of those activities, the projected reduced cost of RA-

O/LTM activities for 30 years post POP, and forecast remaining opportunities to

Reduce LCC 10 years post POP.

o Provide a realistic schedule to achieve SC or RC after the POP (the Contractor shall identify which PO is the optimal endpoint).

Table 1: Performance Table

Site Performance Objective Performance

Period

Performance Standard

N/A Project Management Plan (PMP):

1) Draft PMP

2) Final PMP

3) Updates as necessary

Draft Preliminary

PMP within 60 calendar days from contract award, Final Preliminary

PMP within 14 calendar days of receipt of

Contracting

Officer’s

Representative

(COR) comments on the draft, and update as necessary throughout the POP

AF and USACE approval of

PMP.

The PMP should be maintained with accuracy and completeness based on the current technical approach for each site, management structure, etc.

N/A Quality Assurance Surveillance Plan

(QASP)

Draft QASP within

60 calendar days from contract award and update as necessary throughout the POP

AF and USACE approval of

QASP.

Site Performance Objective Performance

Period

Performance Standard

N/A Integrated Master Schedule

(IMS)/Milestone Payment Schedule (MPS)

Draft IMS/MPS within 60 calendar days from contract award, Final

IMS/MPS within 14 calendar days of receipt of COR comments on the draft, and updates monthly throughout the POP

AF and USACE approval of

IMS/MPS.

N/A Basewide Quality Program Plans (QPP) Draft Basewide QPP within 60 calendar days from contract award and update as necessary throughout the POP

AF, USACE, and regulatory approval of Basewide QPP.

N/A Land Use Control Implementation Plan

(LUCIP)

Maintain and update the LUCIP as needed throughout the duration of the POP as part of the RA-O/LTM program

One (1) year AF, USACE, and regulatory approval of LUCIP.

Beale AFB

CG041-010

RA-O in accordance with the approved

ROD

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

Operations & Maintenance

(O&M) Reports, etc.).

CG041-016

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

O&M Reports, etc.).

CG041-017

RIP

Upon achievement of RIP, continue RA-O in accordance with the ROD throughout the duration of the POP

Two (2) years AF, USACE, and regulatory approval of RIP (e.g., Construction Completion Report and first RA-O Report demonstrating remedy is operating properly and successfully).

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG041-018

ROD and Reduce LCC

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

Site Performance Objective Performance

Period

Performance Standard

CG041-029

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG041-035

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG041-039

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG041-508

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG041-509

Site Closeout (SC)1 Five (5) years AF, USACE, and regulatory approval of SC documentation

(e.g., I-RACR for NFA).

CG041-517

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

CG044

Remedy in Place

Upon achievement of RIP, continue RA-O in accordance with the ROD throughout the duration of the POP

Six (6) years AF, USACE, and regulatory approval of RIP (e.g., Construction Completion Report and first RA-O Report demonstrating remedy is operating properly and successfully).

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

DP038

LTM in accordance with the approved

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

Inspection Reports).

1 The performance objective for CG041-509 is to achieve Site Closeout in accordance with the definitions provided in this contract; however, since it part of a larger site, CG041, Site Closeout will not be claimed in the AF database of record, the Enterprise Environmental, Safety, and Occupational Health – Management Information System

(EESOH-MIS).

Site Performance Objective Performance

Period

ED631

Site Closeout Four (4) years AF, USACE, and regulatory

(e.g., Site Closeout Report and

Well Abandonment Confirmation

Report).

FR970

(e.g., Site Closeout Report and

Well Abandonment Confirmation

LF002

LTM in accordance with the approved DD and Reduce LCC

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

Inspection Reports, Landfill

Inspection Reports, etc.).

LF003

LTM in accordance with the approved DD and Reduce LCC

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

Inspection Reports Landfill

LF013

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

Inspection Reports, Landfill

ML595

(e.g., Site Closeout Report and

Well Abandonment Confirmation

ML625

(e.g., Site Closeout Report and

Well Abandonment Confirmation

OT017

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

PL582

DD and Reduce LCC

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

SD032

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

SR614

(e.g., Site Closeout Report and

Well Abandonment Confirmation

Site Performance Objective Performance

Period

SR615

(e.g., Site Closeout Report and

Well Abandonment Confirmation

SR617

(e.g., Site Closeout Report and

Well Abandonment Confirmation

SR622

(e.g., Site Closeout Report and

Well Abandonment Confirmation

SS023

RA-O in accordance with the Statement of

Basis/Corrective Measures Implementation

(SB/CMI) and Reduce LCC

Through the duration of the POP

AF, USACE, and regulatory approval of RA-O documentation

(e.g., Annual Groundwater

Monitoring Reports, Monthly

SS043

Site Closeout Five (5) years AF, USACE, and regulatory

(e.g., Site Closeout Report and

Well Abandonment Confirmation

ST018

Through the duration of the POP

AF, USACE, and regulatory approval of LTM documentation

(e.g., Land Use Control

ST022

Site Closeout One (1) year AF, USACE, and regulatory

(e.g., Site Closeout Report and

Well Abandonment Confirmation

TU002

Site Closeout Three (3) years AF, USACE, and regulatory

(e.g., Site Closeout Report and

Well Abandonment Confirmation

TU509

Site Closeout Five (5) years AF, USACE, and regulatory

(e.g., Site Closeout Report and

Well Abandonment Confirmation

2.0 APPLICABLE DOCUMENTS

The Contractor shall identify and comply with all applicable federal, state, and local statutes;

Department of Defense (DoD) and AF instructions, manuals, handbooks, regulations, guidance, and policy letters (including AF policy and guidance for IRP, and 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 DoD Policy and Guidelines for Acquisitions Involving Environmental

Sampling or Testing and The United States AF Construction Management Implementation

Guide.

The Contractor shall identify and comply with all applicable documents for the Installation including RODs, ROD Amendments, ESDs, RCRA Permits and subsequent modifications, Risk

Evaluation Corrective Action Program (RECAP) documents, the Endangered Species Act, other

Decision Documents, Deeds, and conveyance notices.

The information provided in this PWS is not intended as a substitute for complete analysis of technical data available, nor is it intended to be a guide on how the Contractor should address achievement of the POs.

3.0 GOVERNMENT FURNISHED INFORMATION AND PROPERTY (GFI/GFP)

Government Furnished Information is contained in the Administrative Record

(http://afcec.publicadmin-record.us.af.mil) or listed in Enclosure 2. The AF believes the documentation provided represents the most recent and appropriate documentation available for the Installation(s) and sites identified in this PWS. The Contractor is solely responsible for reviewing all available information and forming their own independent, professional conclusions/interpretation of site conditions and requirements to achieve the POs of this contract.

Specific documents not included in the Administrative Record or in Enclosure 2 may be made available following a request to the Contracting Officer (KO), 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 GFP procured and utilized at the Installations as-is where-is in accordance with the Federal Acquisition Regulation

(FAR). Lists of current GFP are provided in Enclosure 3. All Real Property installed during the contract shall be turned over to the Government consistent with procedures identified in section

8.2.3.

The Contractor is responsible for providing all other supplies and equipment, not already installed and not listed in Enclosure 3, that are required to achieve the POs of this contract. All

AF owned property, including real property used for remediation purposes must be maintained by the Contractor in accordance with applicable maintenance requirements and usability for the intended purpose. The Contractor is responsible for disposal of unneeded, unusable, or obsolete

GFP as required, and transition of remaining GFP to other AF Contractors at the end of the contract POP, whichever comes first. Prior to disposal of excess or unserviceable equipment listed in Enclosure 3, the Contractor shall coordinate activities with the Contracting Officer (KO) for disposition instructions.

http://afcec.publicadmin-record.us.af.mil/

4.0 MANAGEMENT, PLANNING, AND REPORTING REQUIREMENTS

The Contractor shall implement a full range of environmental remediation activities as required to meet objectives of this contract and in accordance with all applicable or relevant and appropriate federal, state, and local laws and regulations; DoD policies; and Installation-specific orders, agreements or rules. The Contractor shall supply all labor, equipment, and materials necessary to accomplish the work through the entire POP of the contract. The Contractor shall perform management and planning functions, including performance measurement and fund status reporting. The Integrated Master Schedule (IMS), Milestone Payment Schedule (MPS), and Project Management Plan (PMP) shall be consistent.

4.1 Project Management Plan

The Contractor shall develop and maintain a detailed PMP. The PMP shall specify the project’s resources and tasks corresponding to the Sub-CLINs for this contract as required for the planning, execution, control, and completion of the stated POs. At a minimum, the PMP shall include the following sections: technical approach for achieving the POs in accordance with the

PWS; performance models; organization and integration of the project team; schedule management and project controls; transitional activities; risk management; quality management;

health and safety management; procurement management; and security management. The

Contractor is responsible for complying with the AFCEC ORC PMP Guidance.

The first draft of the PMP shall be due within sixty (60) calendar days of contract award (or a more aggressive schedule if agreed upon). The Draft PMP and subsequent revisions shall be subject to AF and USACE review and approval. The Final PMP shall be due within fourteen

(14) calendar days of receipt of AF and USACE comments on the Draft versions. A one-time payment milestone will be established for AF and USACE acceptance of the Final PMP. The

PMP shall be maintained throughout the duration of the contract utilizing dated page changes and additions as practicable. PMP updates during the life of the ORC will be, as necessary, based on the accumulation of small incremental changes or significant changes (e.g., contract requirements, technical approaches, risk and issue management, or key personnel). Updates to the PMP shall be coordinated with the KO/COR.

4.2 Schedule and Planning Requirements – Integrated Master Schedule (IMS)

The Contractor shall prepare and submit an IMS in hardcopy and in electronic format (Microsoft

Project, and Adobe Acrobat portable document file (.pdf)).

The following are minimum AF requirements for the IMS:

Presents a realistic sequence and timing of all activities and documents necessary to demonstrate achievement of the Performance Objective within the PP.

Organized in a Work Breakdown Structure (WBS) aligned with the CLINs/Sub-CLINs in

Section B and includes the following columns:

o Installation Name: Identify EESOH-MIS Installation Name per Table 1.

o Site Number: Identify EESOH-MIS Site Number per Table 1 and Site Alias, if applicable.

o CLIN/Sub-CLIN: Identify CLIN and/or Sub-CLIN per Section B of the contract.

Note Sub-CLINs for compliance activities (routine regulatory requirements to comply with binding agreements) are denoted as ####CX and Sub-CLINs for performance activities (remedial advancement or progress towards the

Performance Objective) are denoted as ####AX.

o Task Description: Include detailed description of all activities (e.g., meetings, permitting, site access, work plans, mobilization, field work, documents, reviews, coordination with stakeholders, etc.) associated with achievement of the

Performance Objective and a clear indication of regulatory

[CERCLA/RCRA/State Program] phase completions (e.g., RIP Achieved, RC

Achieved, etc.) and Performance Objective achievement.

o Start and Finish Dates: Document Start date and Finish date for each required activity and document including appropriate durations and realistic Government and Regulatory review periods.

a. Include an obligation date, notice to proceed date, or projected award date as the first activity for each Sub-CLIN.

b. Include a clearly identified final field work (e.g., FINAL FIELD ACTIVITY)

Start date and Finish Date for each site (i.e., indicate when the final set of field activities such as injections, groundwater sampling, or others will be complete).

o Milestone Payment Amount: Include negotiated amount consistent with the approved Milestone Payment Schedule (MPS) ensuring the sum of all milestone payments equals the value of the CLIN/Sub-CLIN per Section B of the contract.

o Percent Complete: Record completion status of all activities and documents as approved by the COR.

o Predecessor and Successor: Define relationships and constraints associated with activities and documents.

The Contractor shall maintain and submit an IMS monthly in electronic format in accordance with the requirements above and include updates to progress and approved changes (e.g., Government or regulatory review periods, technical approaches, milestone payment updates, or contract requirements). The IMSs shall be submitted electronically to the Contractor’s ORC document repository and in accordance with instructions from the COR. The Contractor shall prepare and maintain the IMS in accordance with the CLIN, Sub-CLIN, IMS, and MPS

Guidance.

4.3 Milestone Payment Schedule (MPS)

The Contractor shall prepare and submit an MPS monthly (along with the IMS) in hardcopy and in electronic format (Microsoft Excel). The MPS will be negotiated during development of the

PMP and approved by the COR.

The following are minimum AF requirements for the MPS:

Presents appropriate milestone payments considered integral and necessary to the achievement of the POs.

Includes a reasonable number of milestone payments per CLIN/Sub-CLIN based on the scope and anticipated duration to achieve CLIN/Sub-CLIN objective and/or Performance

Objective.

Organized in a Work Breakdown Structure (WBS) aligned with the CLINs/Sub-CLINs in

Section B and includes the following columns:

o Installation Name: Identify EESOH-MIS Installation Name per Table 1.

o Site Number: Identify EESOH-MIS Site Number per Table 1 and Site Alias, if applicable.

o CLIN/Sub-CLIN: Identify CLIN and/or Sub-CLIN per Section B of the contract.

Note Sub-CLINs for compliance activities (routine regulatory requirements to comply with binding agreements) are denoted as ####CX and Sub-CLINs for performance activities (remedial advancement or progress towards the PO) are denoted as ####AX.

o Milestone Payment Identification Number: Include unique number assigned to each milestone payment for tracking purposes.

o Milestone Payment Description: Include detailed description of definable and measurable step considered integral and necessary to the achievement of the

CLIN/Sub-CLIN objective and/or Performance Objective.

o Milestone Payment Amount: Include negotiated amount ensuring the sum of all milestone payments equals the value of the CLIN/Sub-CLIN per Section B of the contract.

o Milestone Payment Percentage: Include percentage of the milestone payment in relation to the total CLIN/Sub-CLIN value. The final payment milestone(s) within a CLIN/Sub-CLIN demonstrating achievement of the CLIN/Sub-CLIN objective must be a minimum of 20% of the total CLIN/Sub-CLIN value. This may include both the AF and USACE approved and regulator approved versions.

o Completion Date: Document completion date for each milestone payment consistent with the Finish date presented in the IMS.

o Percent Complete: Identify completion status (0% or 100%) of all milestone payments as approved by the COR.

o Invoice Number: Clearly indicate the invoice number associated with the milestone payment as approved by the COR for the purposes of tracking payment.

This information can be completed as invoices are prepared.

Excludes unacceptable milestone payments representing a “progress” payment or a monthly payment for level of effort expended including:

o Submittal of documents o Site mobilization/demobilization (unless exempted by KO) o Accomplishment of field activities o Submittal of a monthly status o Management and overhead type costs (e.g., program/project management, monthly reporting, etc.)

o Allocation of PMP, Basewide QPP, or other basewide costs to specific sites

The Contractor shall maintain and submit an MPS monthly (and with PMP updates, as needed), in electronic format in accordance with the requirements above and include updates to progress

(e.g., Percent Complete, Invoice Number). The MPSs shall be submitted electronically to the

Contractor’s ORC document repository and in accordance with instructions from the COR. The

Contractor shall prepare and maintain the MPS in accordance with the CLIN, Sub-CLIN, IMS, and MPS Guidance.

Milestone payments within a CLIN/Sub-CLIN may be revised in response to changes in the approach for achievement of the CLIN/Sub-CLIN objective without a contract modification so long as the changes do not impact the total value or objective of the CLIN/Sub-CLIN. All changes to the MPS, with the exception of tracking invoicing of completed milestone payments, must be approved by the COR. Milestone payments will not be renegotiated if the Contractor is unable to achieve the milestones, CLIN/Sub-CLIN objectives, and/or POs.

Completion of milestones shall demonstrate payment is appropriate and warranted. COR approval of the documentation supporting the completion of the milestone is required for payment. Where regulatory acceptance/concurrence is required for this documentation, AF and

USACE acceptance will occur following regulatory acceptance/concurrence of the documentation. Acceptance/concurrence occurs upon final signature of documents requiring signature by the AF and/or regulators. Final decisions regarding the adequacy of milestone completion resides with the AF and USACE. The COR will take into consideration the appropriate acceptance and/or concurrence of necessary documentation by regulators consistent with the applicable regulatory drivers of this PWS.

For milestones where regulatory acceptance/concurrence is required and regulatory acceptance/concurrence cannot be obtained, the AF and USACE will evaluate the Contractor’s documents to determine if they are legally and technically acceptable to warrant payment for achieving that milestone.

The Contractor is limited to one invoice submitted to USACE per month. The invoice must itemize the milestone payments for each CLIN/Sub-CLIN associated with the invoice. The

Contractor will not receive payment until milestones are achieved in accordance with the MPS.

The AF and USACE will not approve partial payments.

4.4 ORC Document Repository

The Contractor shall maintain a document repository for all ORC documents.

The repository is intended to be a single access point repository for all ORC documentation. It shall be accessible to stakeholders during the life of the ORC. The Contractor shall provide notifications to AFCEC, USACE COR, and Installation Point of Contact (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 AF and USACE.

The Contractor shall create and maintain a Master Document List (MDL) that includes all documents, whether the document is a deliverable or not, prepared during the course of this contract. The Contractor shall maintain the project documents for the duration of this contract and transfer custody to the AF within 90 calendar days prior to POP expiration.

4.5 Cost and Status Reporting

The Contractor shall prepare and submit a monthly Contractor’s Progress, Status, and

Management Report (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 an electronic format to the Contractor’s ORC document repository and/or in accordance with instructions from COR. The CPSMR shall also be used to indicate whether efforts for each site are on target for meeting the PO. The Contractor shall submit an updated

IMS each month with the CPSMR.

The Contractor shall document all optimization actions implemented on an annual basis as required in the AFCEC CPSMR Template. The AF defines optimization, under the ORC, as the reduction of contaminant mass and concentrations, reduction in LCC, or any combination of activities prompting acceleration to RC, as a result of remedial implementation the contractor undertakes, above and beyond what is required to maintain compliance in accordance with an approved decision document. The contractor is encouraged and required to implement potential optimization opportunities at all sites with POs of OES, RA-O & Reduce LCC, LTM & Reduce

LCC, and all other sites where ORC contractor can successfully accelerate the achievement of the PO. This requirement will allow the AF to fulfill DoD requirement to accurately account for accelerated contaminant removal and cost savings (i.e., reduction in liability) as a result of optimization activities.

4.6 Meeting and Conference Requirements

4.6.1 Meeting/Teleconference Support

The Contractor shall participate in post-award meetings and Project Management Review (PMR) meetings and teleconferences with the AF and USACE as necessary to achieve the POs in this

PWS. The Contractor shall coordinate meetings, provide logistical support (e.g., facilities, audio/visual), create and present materials, and lead technical discussions.

The Contractor also shall attend and/or support meetings and teleconferences to discuss technical or regulatory issues and project progress and status with the AF and regulatory agency representatives. Specifically, the Contractor shall host an internal kick-off meeting with the AF and USACE within 30 days from contract award. In keeping with the AF’s commitment to the regulators, the Contractor shall host a kick-off meeting with the AF and regulators within 60 days from contract award. At a minimum, the following topics will be discussed at the regulatory kick-off meeting: review PO and PP for each site; review project schedule for field work and documents; confirm agreement on site or document prioritization; confirm mutual understanding of document review times; and confirm any document requirements, templates, or expectations to facilitate the review process.

The contractor shall also attend and provide support for Restoration Advisory Board (RAB) meetings, Tier 1/Tier II partnering meetings and teleconferences. Monthly 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. Currently, regulatory meetings occur on a monthly basis. However, the frequency of meetings may change based on the status of the environmental restoration program. The AF will be present for all technical and public meetings with the regulatory agencies however, the Contractor shall coordinate the meetings, provide logistical support (e.g., facilities, audio/visual), create and 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 AF and

USACE review and concurrence, any presentation materials and agendas for meetings no less than one week (5 working days) prior to the event. The Contractor shall prepare minutes for all meetings attended within 14 calendar days following the event. Travel to/from the Installation 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 not contact any regulatory agency without prior notification and approval by the Installation POC(s).

4.6.2 Public Meetings and Hearings

The Contractor shall support all community involvement requirements to meet CERCLA, RCRA, and other regulatory requirements including public meetings, public notices, RAB meetings, Technical Working Group, Community Advisory Group meetings, public comment periods, and responsiveness summary preparation. Currently, RAB meetings are held three times per year with two Newsletters published, and an on-base site tour. If there currently isn’t an active RAB, the Contractor shall reassess community interest every 24 months. The frequency of meetings may change based on the status of the environmental restoration program.

In coordination with AFCEC and the Installation POC(s), the Contractor shall attend teleconferences as necessary with the assigned Public Affairs Officer (PAO) to ensure the PAO is fully aware of all ongoing activities, public outreach status, compliance with applicable regulations, and possible issues that might impact the AF and its public image. The Contractor shall coordinate with the Installation POC(s) before any contact with the PAO.

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. 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 use staff trained in public affairs to complement the technical staff on the project. These trained staff must attend all meetings with the public along with the appropriate technical staff. The credentials of the trained staff must be submitted to and approved by the

USACE COR in advance of any meeting with the public. The trained staff shall demonstrate effective public 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 PAO or other applicable action officers. These inquiries require the Contractor to provide the AF factual and responsive information within 24 hours of request, unless otherwise specified by the Installation POC(s).

4.7 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 achieve the POs of this contract.

Source data and product data remain the property of the United States Government. The

Contractor shall protect all geospatial data, including geometry, attributes, metadata, topologies, and relational database schemas and operations used in association with this PWS. 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 achieve the POs 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 file geodatabase that meets the current AF adaptation of Spatial Data Standards for Facilities, Infrastructure, and Environment

(SDSFIE) within the AF GeoBase program. The Contractor shall consult with each Installation

POC(s) and/or Installation GIO office to ensure CADD and GIS data is compatible with each

Installation’s requirements.

All products associated with this contract that provide a map representation of the location of

Installation features (historical, existing, or planned) including Installation maps, site plans, area development plans, walls-out as-built depictions, or other related overhead (plan) views of an

Installation (partial or entire) must adhere to the following requirements. (NOTE: This requirement does not currently involve walls-in facility floor plans or interior renderings.)

All maps and associated data must comply with the latest version of SDSFIE available from the

SDSFIE Web site:http://www.sdsfieonline.org/ or contact the AFCEC GIO at

AFCEC.GIO.Workflow@us.af.mil or (210) 925-4620. These data will be organized using the current version of the standard approved by the Headquarters AF GeoBase Office as the functional lead for Installation mapping and visualization. The SDSFIE will determine file and feature class identification and definition, attribution, and valid domain values. When any geospatial information collected as a result of the contract includes information identified in the

Common Installation Picture (CIP) or recognized Mission Data Set (MDS), the Contractor will deliver data consistent with the established requirements for the data and will ensure functionality with the receiving system. Information must be collected at no less than 1:1200 scale. Spatial data will meet or exceed National Map Accuracy Standards at those scales.

Metadata will be provided and will use Federal Geographic Data Committee (FGDC) Content

Standards for Digital Geospatial Metadata (CSDGM) for organization.

As a requirement of this contract, the Contractor shall provide to the Government all shape files, file geodatabases, map exchange files (MXDs), and Geospatial data accumulated as a result of investigation recorded on compact discs (CDs) (FedEx for delivery on next business day) and also electronically. Geospatial data must be delivered in a geo-referenced GIS format (feature-based file structures with one-to-one cardinality between spatial records and attribute records) which would include Environmental Systems Research Institute's (ESRI) shapefile and geodatabase formats. All attribute data as specifically outlined in the contract must be included either in the GIS data file or as a separate table with a SDSFIE key variable that may be used to relationally join the separate table with the GIS data file. All geospatial data must be delivered in the North American Datum 1983 (NAD83) projection, State Plane Coordinate System, using feet or metric coordinate units. For all locations within the Restricted Area, Universal Transverse

Mercator (UTM) coordinates must also be provided. Further guidance on mapping units, coordinate systems, and projections is available from the Installation GIO.

Mapping- or Survey-Grade Global Positioning Systems (GPS) or comparable traditional survey methods will be used to collect geospatial data. The use of mapping- or survey-grade GPS will depend on the precision requirements of the product data. These requirements will be specified later in this PWS for all contract activities where geospatial data are involved. In the case of contracts involving utility construction, location and attribute data will be obtained at the time of excavation. Further information about precision requirements should be obtained from the

Installation Execution Support (GeoBase) Office.

Source data and product data remain the property of the U.S. Government. The Contractor shall 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 PWS. The Contractor shall be required to sign a non-disclosure agreement attesting to the same before source data are released. Further information about security and non-disclosure requirements should be obtained from the

Installation GIO. Some Installation map data, source and/or product, may be considered by the government to be "sensitive, but unclassified." The intent of this clause is to prevent intentional or unintentional dissemination of "sensitive, but unclassified" information to include unauthorized access to the source and product data by any entity wishing to do harm to the AF or

United States Government while the data resides on the Contractor's computer network.

http://www.sdsfieonline.org/ mailto:AFCEC.GIO.Workflow@us.af.mil

The Contractor is not authorized to release this information to any third party without the explicit consent of the AFCEC GIO (AFCEC/CPAB) or its involved Installation. All source information must be returned to the Government POC or destroyed upon completion of this project.

Documentation of information destruction shall be provided to Installation POC(s). Special requirements for handling classified map data, if applicable, will be addressed elsewhere in this

PWS.

The contractor is required to follow MD 11042.1 regarding Safeguarding Sensitive But

Unclassified (For Official Use Only) information dated 5 January 2005.

4.8 Notification Requirements

The Contractor shall notify the AFCEC, USACE COR and Installation POC(s) of critical issues that may affect the contract performance and/or human health and the environment. Verbal notification shall be made immediately, followed by written notification to the KO with carbon copies to AFCEC and Installation POC(s) within five (5) working days.

The types of issues that require notification include, but are not limited to, health risks, spills, Notices of Violation (NOVs) (received or anticipated), changes in critical personnel, and finding unanticipated unexploded ordnance (UXO) or chemical warfare materiel (CWM). If unanticipated UXO is discovered during field activities, the Contractor shall immediately stop work, report the discovery to AFCEC, USACE COR and Installation POC(s), and implement the appropriate safety precautions. Field activities shall not continue until clearance is received from the KO.

If the Contractor anticipates working beyond the PO date to achieve a final milestone the

Contractor shall submit a period of performance extension request to the KO at least 60 days prior to the expiration date of the Sub-CLIN.

4.9 Permits

The Contractor shall develop, coordinate, apply, comply with, and/or modify all federal, state, local, and other applicable environmental permits, access agreements, easements, licenses, and certificates required to achieve the POs of this contract as detailed in Sections 4.9.1 and 4.9.2.

Generally, the AF will sign all easement agreements and modifications and/or renewals of new or existing permits, licenses, and certificates required under this contract. The Contractor shall maintain a library of these documents at the Contractor’s site office as well as the corporate facility handling this contract. The Contractor shall comply with all applicable permit conditions.

4.9.1 Environmental Permits

Pursuant to CERCLA (42 U.S.C. 9621(e)), no federal, state, or local permits shall be required for onsite removal or remedial actions. The Contractor must consult with the AF prior to obtaining environmental permits for all on-site and off-site CERCLA activities. For non-CERCLA restoration sites, the Contractor shall assist the AF to comply with all applicable permit conditions including permit modification requirements and payment of permit fees. If the

Contractor has any question whether a particular permit may or may not be required, the

Contractor shall consult with the AF prior to obtaining the permit. The Contractor shall be responsible for reviewing and responding to site specific underground utility locating systems request tickets, or other dig permit requests, requiring the identification of subsurface appurtenances and utilities associated with the remediation systems included in this contract. If the Contractor obtains environmental permits, it is responsible for implementing and paying for the permits. Utility location ticket requests will be sent to the Contractor and the Contractor will be required to review, respond, and address all location requirements in accordance with state law and regulations. The Contractor shall maintain all records pertaining to location requests.

4.9.2 Rights of Access to Non-AF Real Property

The Contractor shall prepare documents using AF-provided templates to maintain or modify existing rights of access, or to acquire new rights of access, to non-AF land which the Contractor needs to satisfy the POs of this contract. On the AF’s behalf, the designated Installation official will negotiate and sign the documents to obtain or modify the necessary rights of access with technical assistance from the Contractor. Based on the stated right of access needs of the

Contractor, the AF will decide which type of right of access (e.g., right of entry, license, easement, lease, or fee acquisition) will be obtained. Technical assistance expected or that may be requested by the AF from the Contractor for rights of access include description of the amount of real property on which access is being sought, provision of property surveys, title searches and title insurance (necessary only for easements, leases for greater than 30 years, or fee acquisitions), environmental site due diligence, appraisals of fair market value, amount of expected intrusion on the property or property disturbance, cost estimates of restoring property to its original condition after access is no longer needed, and potential technical witness testimony in the event the AF must pursue involuntary condemnation through the U.S. Department of

Justice in state or federal court. Payment of associated expenses includes costs associated with…