NM-AZ_PBR_SOO_FA8903-12-R-0050.doc

FA8903-12-R-0050

Attachment 3

02 August 2012

STATEMENT OF OBJECTIVES (SOO)

FOR

PERFORMANCE-BASED REMEDIATION (PBR)

AT

CANNON afb, new mexico hOLLOMAN afb, new mexico kirtland afb, new mexico & luke AFB, arizona

CONTRACT NUMBER: FA8903-12-R-0050

02 August 2012 1.0

SCOPE

This requirement is for environmental remediation activities at Cannon Air Force Base (AFB), New Mexico, Holloman AFB, New Mexico, Kirtland AFB, New Mexico, and Luke AFB, Arizona. 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 eighty-Eight (88) Installation Restoration Program (IRP) sites, and twenty-one (21) Military Munitions Response Program (MMRP) sites in the Performance Based Remediation (PBR) contract.

1.1 Introduction

Cannon AFB Cannon AFB is home to the 27th Special Operations Wing of the Air Force Special Operations Command. Cannon AFB is located in Curry County, New Mexico, situated approximately eight miles west of the City of Clovis. The base is situated on 3,789 acres (5.9 square miles) of federally-owned land. Off-base facilities include the currently active Melrose Air Force Range (formerly Melrose Bombing Range), located about 24 miles west-southwest of the base on approximately 60,010 acres.

Cannon AFB is regulated by the U.S. Environmental Protection Agency, Region 6 (EPA) and the New Mexico Environment Department (NMED) Hazardous Waste Board (HWB). Cannon has an active Resource Conservation and Recovery Act (RCRA) permit # NM7572124454. It is not on the National Priorities List (NPL).

Holloman AFB

Holloman AFB is located six miles (10 km) southwest of the central business district of Alamogordo, New Mexico. Holloman AFB occupies approximately 60,000 acres and was first established in 1942 as Alamogordo Army Air Field (AAF) flying primarily B-17s, B-24s, and B-29s. In 1947, it became the primary site for the testing and development of un-manned aircraft, guided missiles, and other research programs. In 1968, the 49th Tactical Fighter Wing arrived at HAFB and has conducted fighter aircraft training and operations. Holloman AFB has also served as the German Air Force’s Tactical Training Center since 1996.

Corrective action is regulated by the Holloman AFB RCRA Permit # NM6572124422-2. The Corrective Action Modules and guidance documents, supporting corrective action, are provided by the NMED HWB.

Kirtland AFB Kirtland AFB is located in Bernalillo County, in central New Mexico, southeast of and adjacent to the City of Albuquerque. The approximate area of the base is 52,287 acres. Environmental remediation is being conducted pursuant to RCRA. Regulatory enforcement authority is the NMED HWB. Kirtland AFB has a RCRA Hazardous Waste Permit #NM9570024423.

At Kirtland AFB, project stakeholders may include, but not be limited to, the Air Force, US Army Corp of Engineers (USACE), Kirtland AFB, Air National Guard, New Mexico Environment Division (NMED) Hazardous Waste Board (HWB), the City of Albuquerque and Albuquerque Bernalillo County Water Utility Authority, Veteran’s Administration Medical Center, and private landowners. The required level of involvement may differ from site to site and the Contractor will be responsible for obtaining comments with appropriate approval or concurrence on project deliverables consistent with applicable regulatory drivers and agreements for each site.

Luke AFB Luke AFB covers approximately 4,000 acres west of the Phoenix metropolitan area in Glendale, Arizona. Construction of the facility began on March 29, 1941. Although only a few essential buildings had been completed, training of the first class of pilots began on June 6, 1941. Luke Air Force Base is the largest and only active-duty F-16 Fighting Falcon training base in the world with more than 200 F-16s assigned. The host command at Luke is the 56th Fighter Wing (56 FW), under Air Education and Training Command's 19th Air Force.

The eastern portion of Luke AFB currently consists of a variety of light industrial facilities, office buildings occupied by administrative and community services, Base barracks, and outdoor recreation centers. The central and western portions of Luke AFB include the runways; open space; and aircraft operation, training, and maintenance facilities. Base residential housing and commercial areas are located to the east of Luke AFB across Litchfield Park Road. The base population includes about 7,500 military members and 15,000 family members. With about 80,000 retired military members living in greater Phoenix, the base services a total population of more than 100,000 people.

On August 30, 1990, EPA placed Luke AFB on the NPL. On September 27, 1990, the USEPA, Arizona Department of Environmental Quality (ADEQ), Arizona Department of Water Resources (ADWR), and USAF signed the Federal Facility Agreement (FFA) to establish the procedural framework for conducting the required environmental investigations at Luke AFB. The OU-2 ROD was signed in 1994 and listed Luke AFB as a Federal Superfund site. The OU-1 ROD was signed on September 1999. The signing of the FFA marked the official beginning of the Comprehensive Environmental Restoration, Compensation and Liability Act (CERCLA) investigation of the Base.

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) 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 life-cycle costs 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 during the POP.

2) For any site not achieving SC during the period of performance, 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 that have an approved decision document prior to, or during the POP, but do not achieve 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.

· The next Five-Year Review for Kirtland AFB is scheduled in 2015.

· The next Five-Year Review for Cannon AFB is scheduled in 2017.

· The Five-Year Review for Holloman AFB is scheduled in 2017.

· The Five-Year Review for Luke AFB is currently underway for submission in August 2012 and the next review will be due in 2017.

· Apply innovative technologies to minimize the cost and period 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 a business case analysis.

· 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, assess how the response is progressing and demonstrate when the objective has been reached. An OES Plan shall be delivered within one year from notice to proceed (NTP) and one of the final milestones shall be an OES Effectiveness Report, which 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 objective is the ultimate endpoint). For sites with an indeterminate endpoint 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, 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 response objective is achieved). 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 quantified by performance indicators relevant to the proposed remedial approach. A performance model is typically a graphic representation of a performance indicator value over time until a response objective is attained. 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) and specific end objectives (Table 2) to be achieved for each site during the POP for this contract are outlined in Tables 1 and 2 of the SOO. If the Contractor anticipates the ability to achieve a higher level objective 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 the specific performance objectives of Table 2 sites (with no higher objective proposed)) and date they intend to achieve it for each site within the POP. Contractors shall explain why the selected end point (including the minimum acceptable endpoint if that is what is proposed) is an optimum solution for the Government. It should be noted that the AF reserves the right 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 in the contract for the duration of the contract. Correct any remedy or site deficiencies noted in Five-Year Reviews.

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

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

Site Specific

Achieve an approved RI Report within three (3) years from NTP for the following sites:

Holloman AFB:

· SR859: Former Skeet Range 2

· TS862: Jeep Target Area Skeet Range

· SR864: Poorman Range

· ML865: Ballistics Rain Field

· RR869: Debris Field Air Force approval through the COR and Regulator approval of the RI/FS Report (e.g., written confirmation of acceptance of RI/FS report).

Achieve approved RFI within three (3) years from NTP for the following sites:

Cannon AFB:

· SD022: Storm water drainage & retention pond on GC

· SS501: Former AGE Dispatch Facility spills

· TU502: Former Gas Stations USTs

· TU503: Base Support/ Operations Generator Former UST

· TU504: Hospital Abandoned UST

· TU505: Flight line Generator USTs

· SS507: POL Yard Refueling Area

· DA508: Surface Disposal Area Air Force approval through the COR and Regulator approval (e.g., written confirmation of acceptance of documentation of achieving RFI).

Achieve approved RFI within three (3) years from NTP for the following sites:

· Kirtland AFB: CG570: EOD Hill

Air Force approval through the COR and Regulator approval (e.g., written confirmation of acceptance of documentation of achieving RFI including background study for Perchlorate).

Site Specific

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

Kirtland AFB:

· ST070E: Oil/Water Separator (ST-219)1 Luke AFB

· TU044: Leaking Underground Storage Tank at remote Waterdog Recreational Area

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

Maintain all ongoing RA-O, O&M, and/or LTM activities at the following sites until SC is achieved or the required activities are replaced in accordance with the newly approved exit strategy.

1 O&M and Long Term Management will pick up at the conclusion of the current contract in 4th Quarter 2013 (September 2013). Refer to Section 8.1.2.

Achieve RC within three (3) years from NTP for the following site:

Cannon AFB:

· DP036: MWR Body Shop

· RS-C103: North Playa Lake (Pending NMED decision in FY12)

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

Achieve Response Complete (RC) within five (5) years from NTP for the following sites:

· TG100: Bomb Target

· AL120A: Proximity Fuze Range

· AL120B: Proximity Fuze Range

· PT123: Tijeras Small Arms Range

· DA130: Arroyo Del Coyote Demolition Area

· PL567: UST058

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

Achieve Response Complete (RC) within nine (9) years from NTP for the following sites:

· AL120: Proximity Fuze Range

· ML125: Field Firing Range

(Approved characterization document in 4 years.) Decision Document. (LUC)

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

Site Specific

Achieve Site Closeout (SC) within two (2) years from NTP for the following sites:

Holloman:

· SS013:

· OT014:

· OT032:

· RW042: Radioactive Waste Disposal Area

· SS067:

· SS072:

· SS073:

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

Site Specific

Achieve Site Closeout (SC) within three (3) years from NTP for the following sites:

Cannon AFB:

· TS835: Former Skeet Range (VCA)

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

Achieve Site Closeout (SC) within three (3) years from NTP for the following sites:

Holloman AFB:

· TU500: Building 300

· TU501: Building 1113

· TU503: Building 221

· TU504: Building 301

· TU505: Building 1097

· TU506: Building 901

· TU508: Building 298

· TU513: Building 898

· TU518: UST 7003

· TS851: Former Skeet Range

· XU853: Missile Test Stands Area

· XU854: Able 51 Area

· FI857: Former Bunker

· SR858: Former Small Arms Range

· SR863: 1000 Inch Range

· ML866: Former Bombing Range

· SR867: Possible Firing Range

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

Site Specific

Achieve Site Closeout (SC) within five (5) years from NTP for the following sites:

· CW571: Zia Park

· OT572: Building 5700-1

· OT573: Asphalt Dump Area

· SS575: Transient Alert Pad Holloman AFB:

· OT020: Sewage Lagoon Disposal Trenches

· SD027: PAD 9 Washrack Area, RAD Waste

· OT037: Early Missile Testing Site

· OT038: Test Sled Maintenance Area

· SS065: Test Cell Surface Spill

· SS069: Flight line Fuel Spill Area Air Force approval through the COR and Regulator approval (e.g. written regulator confirmation of acceptance of SC documentation for unrestricted use).

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

Cannon AFB:

· LF002: Landfill No. 21

· SW002: Recovered tank no. 1081

· LF003: Landfill No. 31

· LF004: Landfill No. 41

· SW004: Recovered tank no. 1211

· LF005: Landfill No. 5, cell 31

· FT006: Fire Training Area No. 11

· SW006: POL Tank No. 1291

· SD-012: Stormwater Collection Point South Playa (SWMU 85)

· SD015: AGE drainage ditch1

· SD017: Old entomology rinse area1

· SD020: NE Stormwater Drainage Area (SWMU 95)1

· LF025: Landfill No. 25, Concrete rubble pile1

· MY031: AGE maintenance shop pad1

· FL070: Oil/water separator & leach field 326

· TU071: Recovered JP-4 Fuel Tank No. 390

· SI101: Wastewater Treatment System – lagoons 1 & 2 1

· WL102: Wastewater treatment effluent discharge1

· AT109: SWMU 109, FT-C109

Air Force approval of optimized exit strategy and Regulator concurrence with Air Force approved reports confirming implementation of the strategy (e.g. written confirmation of acceptance of documentation).

Maintain all ongoing RA-O, O&M, and/or LTM activities at the following sites until SC is achieved or the required activities are replaced in accordance with the newly approved exit strategy.

O&M and Long Term Management (preventive and corrective maintenance) at these sites will begin in 4th Quarter 2013 (September 2013). Refer to Section 8.1.2.

Site Specific

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

Cannon AFB (cont.):

· FT-C110: SWMU 110

· SW111: Unlined Pit (used with SWMU 109)

· SW112: Oil/water separator No. 2336

· TU126: Inactive Underground Storage Tank 3

· SW127/128: Oil/water Separator

· TA129: Waste Oil Storage Facility 244- formerly AOC I Holloman AFB:

· SS017: BX Gas Station Fuel Leak2

· SS018: Chromic Acid Spill Site

· LF029: Old Army Landfill

· DP030: Grease Trap Disposal Pits,

· SD033: Cooking Grease Disposal Trench

· SS039: Missile Fuel Spill Area, Groundwater only Kirtland AFB:

· LF001: Landfill No.11

· LF002: Landfill No. 21

· LF008: Landfill No. 4, 5 & 61

· WP026: Base Sewage Lagoons & Golf Course Pond

· ST105: TCE and Nitrate Contaminated Groundwater

Air Force approval of optimized exit strategy and Regulator concurrence with Air Force approved reports confirming implementation of the strategy (e.g. written confirmation of acceptance of documentation).

Maintain all ongoing RA-O, O&M, and/or LTM activities at the following sites until SC is achieved or the required activities are replaced in accordance with the newly approved exit strategy.

O&M and Long Term Management (preventive and corrective maintenance) at these sites will begin in 4th Quarter 2013 (September 2013). Refer to Section 8.1.2.

2 OES activities for Site SS017, Holloman AFB, will begin 2nd Quarter 2016 (January 2016)

Site Specific

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

Luke AFB

· RW002: Low-Level Radioactive Waste Burial Site1

· LF003: Outboard Runway Landfill

· FT007: North Fire-Training Area (West)

· FT007E: North Fire-Training Area (East)

· DP013: Drainage Ditch Disposal Area

· LF014: Old Salvage Yard Burial Site

· ST018: Facility 993

· SD020: Oil/Water Separator Canal and Earth Fissures

· DP023: Surface impoundment west of Facility 993

· LF025: Northwest Landfill

· SD038: Southwest Oil/Water Separator at the Auto Hobby Shop Air Force approval of optimized exit strategy and Regulator concurrence with Air Force approved reports confirming implementation of the strategy (e.g. written confirmation of acceptance of documentation).

Maintain all ongoing RA-O, O&M, and/or LTM activities at the following sites until SC is achieved or the required activities are replaced in accordance with the newly approved exit strategy.

1Long Term Management at LukeAFB will pick up at the conclusion of the current contract in 3rd Quarter 2014 (May 2014).

Table 2: Specific End Objectives (These are the only performance objectives - no higher objective is desired or should be proposed.)

Site Specific

Conduct Long Term Management (LTM) at the following sites:

Luke AFB

· SS042: Bulk Fuels Storage Area Implementation of LTM shall continue through the duration of the POP or until no longer required based on Air Force and regulatory concurrence that SC has been achieved.

Air Force approval through the COR and Regulatory approval (e.g. written confirmation of implementation of LTM (e.g. Land Use Controls, Institutional Controls, etc.)).

This SOO includes general requirements of the project to meet the Air Force objectives; it also includes Enclosures:

· Enclosure 1 – Site List

· Enclosure 2 – Key Documents

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

· Enclosure 4 – Document Review Process

· Enclosure 5 – Acronyms and Definitions

· Enclosure 6 – Format For Metadata and .pdf Documents The Contractor shall function as an integral team member in support of the Air Force Center for Engineering and the Environment (AFCEE) mission, to include the sharing of information with other AFCEE 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 in the process to allow for the development of the most cost-effective and technically sound approach or solution. AFCEE 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.

2.0

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 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 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 bases including Records of Decision (RODs), ROD Amendments, Explanation of Significant Differences (ESDs), 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 own independent, professional conclusions/interpretation of site conditions and requirements to meet the 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 on how the Contractor should address achievement of the performance objectives.

3.0

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 bases in accordance with the applicable Federal Acquisition Regulation (FAR). Lists of GFE/GFP are provided in Enclosure 3 includes:

Cannon AFB, NM:

· Soil Vapor Extraction System Design and Construction is composed of 1 SVE well and 2 vapor monitoring wells that are plumbed to an SVE system which is connected to moisture separator, particulate filter, a blower, monitoring instrumentation, and GAC containers. The system is housed in a shed. The SVE system and all the related components can be explained in detail within Section 3 of the Interim Corrective Measures, Construction Summary Report, SWMU ST-70 (Former ST-219), April 2009.

Holloman AFB, NM:

· Currently there are no remedial systems at Holloman AFB.

· Should remedial systems be required, the AF will provide electricity and water but the Contractor is required to provide the connections and installations.

Kirtland AFB, NM:

· Currently there are no remedial systems at Kirtland AFB.

· Should remedial systems be required, the AF will provide electricity and water but the Contractor is required to provide the connections and installations.

Luke AFB, AZ:

· Currently there are no remedial systems at Luke AFB or at Waterdog Recreational Area.

· Should remedial systems be required, the AF will provide electricity and water but the Contractor is required to provide the connections and installations.

· Contractor should note that NO utilities are available at the remote Waterdog site. Contractor will have to make arrangements, from start to finish, for any and all utilities necessary for any planned activities at this site.

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

4.0

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.

4.1 Milestone Payment Schedule (MPS) Milestone payments shall be based on the completion of a definable and measurable step, which is 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 Investigation report). Where regulatory acceptance/concurrence is required for this documentation, Air Force acceptance of the milestone will occur following regulatory acceptance/concurrence of the documentation (for example, EPA approval of Draft Record of Decision). 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 Contract Line Item Number (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. Award of this 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. 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 O&M reports are examples of unacceptable milestone payments.

The first deliverable milestone required in the MPS is the Preliminary 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 milestone for the Final PMP may be implemented. The PMP 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. Table 1 includes the minimum end state milestones acceptable to the Government. Table 2 includes the only acceptable end state milestones acceptable to the Government. Potential CLIN 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 a t the site. The Contractor is limited to one invoice submitted to AFCEE per month. The invoice must itemize the milestone payments and costs for each site or grouping associated with the invoice.

The Contractor may continue working to achieve a final milestone (applies to Sub-CLIN dates only) if it has progressed beyond the performance objective date. However, the Contractor shall not perform work after the funding associated with the milestone expires. Specifically, completion of activities 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 delay in achievement of the impacted performance objectives.

4.2 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 and stakeholders, procurement management, and security management. The PMP should identify the project’s resources and project tasks corresponding to the Sub-CLINs for this contract. The first draft of the Preliminary PMP shall be due within 30 calendar days of contract award. The 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 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 Final PMP, and subsequent annual updates, is expected approximately 4.5 years after the approval of the Final version of the Preliminary PMP. The final milestone for the Preliminary PMP Sub-CLIN shall be a Project Status Summary and for the Final 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, 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.

4.3 Project Web Site The Contractor shall maintain a web-based project folder for the PBR 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 AR/IR 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 AFCEE 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 with appropriate security password restrictions.

4.4 Schedule and Planning Requirements – Integrated Master Schedule (IMS) The Contractor shall prepare and submit an IMS for approval. The Contractor shall include and identify all performance milestones and payments consistent with the MPS. Sites associated with each milestone/task shall be noted in the schedules using the Site IDs and referencing all site aliases noted in Table 1 and Table 2. The schedule shall be provided in initial hardcopy and subsequently in electronic format consistent/compatible with AF software, currently Microsoft( Project and in Adobe Acrobat portable document file (.pdf), and Microsoft Excel upon request. Updated and revised schedules shall be submitted electronically with monthly status reports with changes clearly identified by the Contractor.

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 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 AFCEE PBC website. 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 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 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 provided in the Surveillance Plan.

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

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 as Restoration Advisory Board (RAB) meetings, partnering, Tier 1, Tier II 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. However, the frequency of meetings may change based on the status of the environmental restoration program. The Air Force will be present for all technical and public meetings with the regulatory agencies. 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. 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 notify the Air Force (Installation) prior to any contact with a regulatory agency.

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, Restoration Advisory Board (RAB) meetings, Technical Working Group, Community Advisory Group meetings, public comment periods, and responsiveness summary preparation. The frequency of meetings listed below may change based on the status of the environmental restoration program.

Cannon AFB: an active RAB is in place with meetings held semi-annually.

Holloman AFB: There is no current active RAB.

Kirtland AFB: There is no RAB; but Kirtland AFB does have a Citizens Advisory Board (CAB). A Community Relations Plan has been developed and implemented for Kirtland AFB and is included in the Basewide Work Plan (Tetra Tech, 2004). Restoration contractors at Kirtland AFB support the CAB meetings by developing information, make briefings regarding project status of all sites, and prepare meeting minutes. The CAB meetings are quarterly. Additional semi-annual meetings are conducted with DOE and the contractors provide the same support. Kirtland AFB also has quarterly leadership meetings which require contractor support.

Luke AFB: There is no active RAB currently, as it was dissolved after the majority of the sites were de-listed.

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 potential issues that might impact the Air Force and its public image in accordance with Clause H029, Implementation of Disclosure of Information. The Contractor shall notify the Base POC 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 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 Air Force factual and responsive information within 48 hours of request.

4.7 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. 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 – “Format for Meta Data and .pdf Documents” for format guidance when providing documents.

4.8 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 the 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 the 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.

4.9 Notification Requirements

The Contractor is required to notify the CO, COR, and Base POC of critical issues that may affect the contract performance and/or human health and the environment. 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).