ECOS PWS_draft_22JAN25.pdf

FA8903-25-R-XXXX

Attachment 1

22 January 2025

BASIC CONTRACT

PERFORMANCE WORK STATEMENT

for

ENVIRONMENTAL CONSTRUCTION AND OPTIMIZATION SERVICES

(ECOS)

SOLICITATION: FA8903-25-R-XXXX

TABLE OF CONTENTS

SECTION TITLE PAGE

1.0 SCOPE

2.0 APPLICABLE DOCUMENTS

3.0 GOVERNMENT FURNISHED INFORMATION, EQUIPMENT, AND PROPERTY (GFI, GFE,

GFP)

4.0 MANAGEMENT, PLANNING, AND REPORTING REQUIREMENTS

4.1 PROJECT WEB SITE

4.2 WORK BREAKDOWN STRUCTURE

4.2.1 WBS Requirements (Environmental Projects)

4.2.2 WBS In CSI Format (Traditional Construction)

4.3 SCHEDULE AND PLANNING REQUIREMENTS

4.3.1 Project Planning Chart and/or Construction Planning Chart

4.3.2 Integrated Master Schedule

4.4 COST AND STATUS REPORTING

4.4.1 Contractor’s Progress, Status, and Management Report

4.4.2 Funds and Man-Hour Expenditure Report

4.4.3 Performance and Cost Report

4.4.4 Contract Funds Status Report

4.4.5 Cost/Schedule Status Report

4.4.6 Cost Performance Report

4.5 MEETING AND CONFERENCE REQUIREMENTS

4.5.1 Meeting/Teleconference Support

4.5.2 Public Meetings and Hearings

4.6 CONTRACTOR DOCUMENTATION

4.7 SPATIAL DATA (MAP) REQUIREMENTS

4.8 NOTIFICATION REQUIREMENTS

4.9 PERMITS

4.10 PHOTO DOCUMENTATION

4.11 REMOTE AND/OR AUSTERE SITES

4.12 SITE ACCESS BADGES

4.13 WORKSITE ACTIVITIES AND COORDINATION

4.13.1 Coordination of Activities

4.13.2 Radiological Waste, Hazardous Material and Hazardous Waste Permitting and Reporting

5.0 CHEMISTRY REQUIREMENTS

5.1 QUALITY ASSURANCE

5.2 LABORATORY SELECTION

5.3 ANALYTICAL DATA MANAGEMENT

5.4 RECORD KEEPING

6.0 PLANS AND REPORTS

6.1 QUALITY PROGRAM PLANS

6.2 TECHNICAL PLANS AND REPORTS

6.2.1 Technical Plans

6.2.2 Technical Reports

7.0 SITE WORK

7.1 CONSERVATION

7.2 DEMOBILIZATION

7.3 SITE CHARACTERIZATION

7.4 SITE PREPARATION

7.5 DEMOLITION

8.0 ENVIRONMENTAL REQUIREMENTS

8.1 PERFORMANCE-BASED REMEDIATION

8.2 ENVIRONMENTAL CONSTRUCTION

8.2.1 Completion of Conceptual Design

8.2.2 Study Effort Incidental to Remedy or Corrective Action

8.2.3 Construction

8.2.4 Pre-Final Inspection

8.2.5 Final Inspection

8.2.6 Delivery and Warranty

8.3 ENVIRONMENTAL RESOURCES PROGRAM INFORMATION MANAGEMENT SYSTEM (ERPIMS)

8.4 INNOVATIVE AND PROVEN TECHNOLOGIES

8.5 OPERATIONS AND MAINTENANCE

8.6 ORDNANCE REMOVAL AND SUPPORT

8.7 PRESUMPTIVE AND OTHER REMEDIES

8.7.1 Requirements

8.7.2 Regulatory Site Closure

8.8 RADIOLOGICAL AND HAZARDOUS WASTE REMOVAL AND SUPPORT

9.0. ADDITIONAL REQUIREMENTS

9.1 OTHER CONSTRUCTION

9.1.1 Construction

9.1.1.1 Pre-Final Inspection

9.1.1.2 Final Inspection

9.1.1.3 Delivery and Warranty

9.2 MILITARY FAMILY HOUSING

9.3 FUELING SYSTEM PROJECTS

9.4 RANGE CONSTRUCTION

10.0 POINTS OF CONTACT (POCS)

11.0 ABBREVIATIONS, ACRONYMS AND TERMS

1.0 SCOPE

This basic contract performance work statement (PWS) defines the scope of a full range of environmental planning, investigations/assessments, construction/demolition, compliance, restoration/remediation, and engineering activities necessary to meet Air Force and other customer requirements. This basic contract PWS will be tailored to identify specific requirements at the task order (TO) level. Statements of objectives (SOOs) or Statements of Requirements (SORs) may be used under this contract to define project-specific requirements and establish performance objectives.

Work shall be performed in compliance with all applicable federal, state, and local legislation, regulations, guidelines, policies, procedures, and requirements including the Resource Conservation and Recovery Act (RCRA), Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA), Safe Drinking Water Act (SDWA), Clean Air Act (CAA), Clean Water Act (CWA), Toxic Substances Control Act (TSCA), Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA), Endangered Species Act (ESA) and any other applicable and relevant legislation and regulation necessary to support the planning and execution of applicable requirements.

This PWS encompasses the full range of methods, technologies, and supporting activities necessary to conduct environmental construction/demolition, environmental restoration/remediation efforts interim remedial actions (IRAs), remedial systems design & construction, operation, maintenance, monitoring & optimization, including maintenance of established remedies, implementation of optimization, and remediation activities to address environmental sites and conditions at Air Force installations and other locations in accordance with technical and regulatory requirements. This PWS also includes a full range of construction and ancillary services as required in support of those and other efforts as addressed herein to include emerging requirements for environmental remediation as identified in each contract/TO.

Requirements under this contract will primarily support environmental compliance, restoration/remediation/construction efforts; but requirements may also include traditional construction. Stand-alone design is not included in the scope of this contract. Requirements shall be carried out as specified under TOs at locations in all 50 US States and Territories, including any associate geographically separated unit (GSU) locations.

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

Requirements include efficient management of TOs including, but 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. AFCEC will rely on the Contractor’s expertise in recognizing and addressing problematic issues and successful execution of each TO. The Contractor shall perform all work in accordance with federal, state, and local statutes and regulations. Remedies shall conform to environmental permits, decision document requirements, or other legal requirements.

Task orders under this contract may involve an Optimized Remediation Contract (ORC) approach, where desired outcomes of the work are identified without specifying the methods or technologies to be used. Under such efforts, the contracted work is performed with a focus on results. The range of activities includes maintenance of established remedies, optimization at applicable sites, and achievement of site-specific objectives. An ORC TO enables the Contractor to select actions best suited to the site requirements and ensures that best management practices and best available technologies are employed. The PWS, or SOO will specify ORC requirements, including Performance Objectives, at the TO level.

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 DoD and AF policy and guidance for ERP and Emerging Contaminants); Executive Orders (EO); 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); Occupational Safety and Health Administration (OSHA) regulations, 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.

It is the Contractor’s responsibility to identify and comply with all applicable or relevant and appropriate requirements (ARARs) at federal, state, and local levels. The Contractor shall identify and comply with all applicable documents for the bases including Records of Decision (RODs), ROD Amendments, Explanations of Significant Difference (ESD), 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 available on the AF Administrative Record at https://ar.afcec-cloud.af.mil.

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

3.0 GOVERNMENT FURNISHED INFORMATION, EQUIPMENT, AND

PROPERTY (GFI, GFE, GFP)

3.1 Remedial System Components

The Contractor shall properly account for and manage all new and existing remedial system components including monitoring wells, as applicable, procured and utilized at the installation.

(CDRL A001)

The Contractor is responsible for providing all other materials, supplies and equipment, not already installed or incidental to the place of performance, required to meet the objectives specified in each TO. All AF-owned equipment used for remediation purposes is as-is, where-is and must be maintained by the Contractor in accordance with applicable operations and maintenance (O&M) plans, manufacturer specifications, or other documentation. The Contractor is responsible for proper return or disposal of excess or unserviceable equipment, supplies, or materials as required during the duration specified in each TO.

The Contractor is required to provide secure storage for all remedial system components, as applicable, until such time it is, disposed of or transitioned to other AF contract efforts supporting the associated system at the end of the PoP, whichever comes first, as specified in each TO.

3.2 Government Furnished Information (GFI)

GFI is provided in the AF Administrative Record (AR); see http://ar.afcec-cloud.af.mil. GFI not available in the AR and required for a TO will be provided to the Contractor as appropriate and specified in each TO.

4.0 MANAGEMENT, PLANNING, AND REPORTING REQUIREMENTS

The Contractor shall implement a full range of environmental planning, compliance, restoration/remediation, construction and engineering activities as specified in each TO and in accordance with all applicable compliance documents. The Contractor shall supply all labor, equipment, and materials necessary to accomplish the work assigned unless otherwise specified in each TO. The Contractor shall perform management and planning functions, including performance measurement and fund status reporting, as required in each TO.

4.1 Project Web Site

As specified in each TO, the Contractor shall establish project web site(s) to support multiple projects with real-time access available to AFCEC personnel. The web site features may include, but are not limited to, a submittal tracker or submittal register, a Request for Information (RFI) tracker, a change order tracker, a photographic log, and a file download feature to access status reports and project schedule(s). The web site shall be tailored to the project.

4.2 Work Breakdown Structure

4.2.1 WBS Requirements (Environmental Projects)

The Contractor shall prepare and submit for approval a Work Breakdown Structure (WBS). The WBS shall be used to report the cost and schedule status for each environmental project. All tasks required under this type of TO shall be included in the WBS. (Contract Data Requirements List (CDRL) B001)

4.2.2 WBS In CSI Format (Traditional Construction)

The Contractor shall prepare and submit for approval a WBS in the Construction Standard Institute (CSI) format for traditional construction activities. The WBS shall be used to report the cost and schedule status for each project. All tasks required under this type of TO shall be included in the WBS. (CDRL B001)

4.3 Schedule and Planning Requirements

The Contractor shall provide schedules for tracking work progress as specified in each TO. The PWS for each TO will identify which of the following schedules is required. Generally, the government will require Project Planning Charts (PPC) for less complex projects and Integrated Master Schedules (IMS) for more complex projects and ORCs.

4.3.1 Project Planning Chart and/or Construction Planning Chart

The Contractor shall prepare and submit a PPC for approval. The PPC shall detail the project schedule and status through the use of Gantt charts, which shall depict percent complete for each task. The project schedule shall be reported using the approved WBS. (CDRL B002)

4.3.2 Integrated Master Schedule

The Contractor shall prepare and submit an IMS for approval. The IMS shall detail the project schedule and status through the use of Gantt charts, and Critical Path Method (CPM) analyses.

The project schedule shall be reported using the approved WBS. (CDRL B003)

4.4 Cost and Status Reporting

The Contractor shall provide cost and status reports. Cost and status reports are listed below in order of increasing complexity. The government will specify one of the following reports or combination of the following depending on the complexity and size of the TO. Task orders under $500,000 and ORCs typically require Contractor’s Progress, Status, and Management Reports (CPSMR) with cost information. Task orders under $2M typically require either a Performance and Cost Report (PCR) or a Funds and Man-Hours Expenditure Report (FMER).

Task orders between $2M-$5M typically require a Cost/Schedule Status Report (C/SSR).

Typically, TOs over $5M require a Cost Performance Report (CPR). A Contract Funds Status Report (CFSR) may be required in conjunction with a CPR or C/SSR. ORC TOs also require a Project Management Plan (PMP), Integrated Master Schedule (IMS), and Milestone Payment Schedule (MPS).

4.4.1 Contractor’s Progress, Status, and Management Report

The Contractor shall prepare and submit a monthly CPSMR. The CPSMR shall be used to review and evaluate the overall progress of the contract as specified in each TO, along with any existing or potential problem areas. The report shall be prepared in a format coordinated and approved by the COR including site level details and associated CLIN information. For TOs involving multiple installations, the CPSMR shall also be used to indicate information by installation on a regional basis, describing whether efforts for each site are on target for meeting site-specific Performance Objective. (CDRL B003)

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 projected tasks such as field work, reporting, etc., occurring in the next 90 days.

4.4.2 Funds and Man-Hour Expenditure Report

The Contractor shall implement and maintain a cost accounting system and prepare a FMER to correlate the status of expensed funds and man-hours against the progress of the work completed and the negotiated budget. The FMER and associated graphics shall detail the current project status and identify funds and man-hours required to complete the assigned tasks. (CDRL C001)

4.4.3 Performance and Cost Report

The Contractor shall prepare and submit a PCR. The PCR provides the current status and projected requirements for funds, man-hours, and work completion relative to the negotiated budget. (CDRL C002)

4.4.4 Contract Funds Status Report

The Contractor shall prepare CFSRs as specified in individual TOs where a cost-reimbursement pricing arrangement is involved. The purpose of the CFSR is to update and forecast funding requirements, funding changes and budget estimates, identify funds in excess under the TO which may be available for de-obligation, and provide estimates of termination costs, if applicable. (CDRL C003)

4.4.5 Cost/Schedule Status Report

The Contractor shall prepare C/SSRs, which summarize performance information for program management purposes as specified in individual TOs where a cost reimbursement pricing arrangement is involved. The CSSR contains contract data, including original and current contract values and management estimate at completion, performance data, and narrative explanations which present information on significant cost, schedule variances, contractual problems, or other areas of interest. (CDRL C004)

4.4.6 Cost Performance Report

The Contractor shall implement and maintain a performance measurement system to support the gathering of cost and schedule data for the purpose of determining program status under TOs where a cost reimbursement pricing arrangement is involved. The WBS or equivalent task breakdown shall be used for reporting cost. The CPR presents the performance measurement baseline and actual cost and schedule performance against that baseline. Submittals shall include appropriate figures containing cost and related data for measuring project cost and schedule status. (CDRL C005)

4.4.7 Project Management Plan

For ORCs, 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, management approach including sub-contractor management, organization and integration of the project team, schedule management, project controls, transitional activities, risk management, quality management, health and safety management, procurement management, security management, and communications plans. The Contractor is responsible for complying with the “Optimized Remediation Contract (ORC) Program Management Plan (PMP) Guidance” latest version, as well as standard industry practice. Clarification on PMP content and the level of detail required to address the ORC program shall be provided by the COR.

The PMP shall demonstrate a comprehensive decomposition of each work package/PO deliverable and exhibit a clear and concise correlation between the PWS, IMS, and MPS. The Contractor is responsible for complying with the guidance for the Development of Contract Line Item Number Structures, Integrated Master Schedules, and Milestone Payment Schedules (CLIN, IMS, MPS Guidance) per the latest version of the “Optimized Remediation Contract (ORC) Program Management Plan (PMP) Guidance.”

The first draft of the PMP shall be due within sixty (60) calendar days of contract award. The Draft PMP and subsequent revisions shall be subject to AF review and approval. The Final PMP shall be due within fourteen (14) calendar days of receipt of AF comments on the Draft versions.

The Contractor shall maintain the PMP throughout the duration of the contract utilizing dated page changes and track change deletions and insertions (electronic copies) as practicable. Whole document PMP updates during the life of the ORC may be 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). The Contractor shall prepare two whole document updates during the POP of the ORC. The AF will determine when PMP updates are warranted.

4.4.8 Milestone Payment Schedule

For ORCs, the Contractor shall prepare and submit an IMS, from which they will extract the information required to generate an MPS and will submit as two separate files. NOTE: The MPS is not part of the proposal. Award of the contract does not equate to final acceptance of the IMS.

The IMS and MPS, including payment milestones and percentages, will be discussed and agreed among the Government (AF and Contracting Agent) and Contractor during the review of the initial PMP/IMS/MPS and approved by the COR.

Refer to the ORC PMP Guidance, Section 4.4, for more detailed information on common errors in preparation of the MPS.

The Contractor shall maintain and submit an MPS monthly, in electronic format in accordance with the requirements above and include updates to progress (e.g., Percent Complete, Invoice Number) (see Section 4.4 Cost and Status Reporting). The MPS 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, 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. In general, milestones are considered complete upon approval by AF (and regulators where required). Where regulatory approval or acceptance is required for this documentation, AF approval will occur following regulatory approval of the documentation. Approval 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. The COR will take into consideration the appropriate approval of necessary documentation by regulators consistent with the applicable regulatory drivers of this PWS.

Milestones must represent tangible progress toward achieving the PO. In general, progress payments are disallowed. Progress payments include payment for interim steps needed to achieve the PO. As an example, milestones for conducting monthly landfill inspections would represent progress payments. Acceptable milestones would be a semi-annual or annual LTM Report of the results of the landfill inspections.

For milestones where regulatory approval is required and cannot be obtained, the AF will evaluate the Contractor’s supporting 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 the AF 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 will not approve partial payments.

Note that AF approval of the first version of a document that will be submitted for regulatory review is a valid milestone. AF and regulatory approval of the final version of that document is also an acceptable milestone.

4.5 Meeting and Conference Requirements

4.5.1 Meeting/Teleconference Support

The Contractor shall participate in post-award meetings and periodic contract status, technical review, and/or Project Management Review (PMR) meetings/teleconferences with the AF. The Contractor shall also participate in annual high-level status briefings (format of which is to be coordinated with the CO) to be held at AFCEC.

The Contractor shall also attend and/or support meetings and teleconferences to discuss technical or regulatory issues and progress and status with the AF and regulatory agency representatives as required, including BRAC Cleanup Team (BCT) meetings, and other periodic meetings/teleconferences.

The AF will be present for all technical meetings with the regulatory agencies; however, the Contractor shall coordinate the meeting, provide logistical support (e.g., facilities, audio/visual), presentation materials, agendas, meeting minutes, and lead technical discussions. The Contractor shall prepare and submit for AF review not less than five (5) working days prior to the meeting (unless otherwise approved by the AF), presentation materials for meetings and an agenda. The Contractor shall prepare summaries/minutes for all meetings attended and submit for AF review not less than 10 working days after the meeting has occurred. (CDRLs B005, B006, B007)

If needed, contractor will provide services of a professional facilitator to run public meetings and ensure all parties are provided an opportunity to communicate. This requirement is only necessary in the event of controversial or adversarial situations where predominate viewpoint of vocal community members is negative and impairs free flowing exchange of information.

Professional services can diffuse these negative group dynamics and enable positive outcomes for gaining understanding and trust among various stakeholders.

The Contractor shall not contact, nor take direction from, any regulatory agency without prior notification and approval by the AF. In situations of imminent health or safety risks, regulators may direct the AF and their contractors to stop work.

4.5.2 Public Meetings and Hearings

At the direction of the Government, the Contractor is responsible to support all community involvement requirements to meet CERCLA and other regulatory requirements including public meetings (e.g., Proposed Plan meetings), public notices, public comment periods, and responsiveness summary preparation. The Contractor shall contact the COR to coordinate with the AF Public Affairs (PA) and the assigned BRAC Public Affairs Officer (PAO) for all “external” materials that will be released.

At the direction of the Government, the Contractor shall support, coordinate, and attend community, stakeholder, Restoration Advisory Board (RAB), and other periodic public meetings/teleconferences as necessary. Public meeting requirements include meeting logistics (e.g., facilities, audio/visual), newspaper notices, radio announcements, agendas, presentations, handouts, and meeting summaries/minutes, and transcripts where specified. (CDRLs B005, B006, B007)

At the direction of the Government, the Contractor shall support, coordinate, and attend teleconferences as necessary with the assigned AF 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 AF and its public image. At the direction of the Government, the Contractor shall compile a schedule of planned public meetings, and provide for PA visibility, where PA involvement may be required and to ensure AFCEC/PA is aware of all planned meetings where public involvement may be required. At a minimum and at the direction of the Government, the Contractor shall plan to participate in at least one teleconference per year. The Contractor shall provide technical information to support AF updates to the Community Relations Plan and periodic newsletters, fact sheets, and articles. This may include preparing appropriate text, figures and photos. (CDRL A001)

Examples of types of PA 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. (CDRLs B005, B007)

At the direction of the Government, the Contractor is responsible for providing public affairs support services for public engagements to complement technical staff as specified in each TO;

attendance of PA support staff with PA related expertise at public meetings and other meetings will be at the direction of the Government as specified in each TO.

At the direction of the Government, the Contractor shall research and support coordination and response for short-notice internal and external requests for information such as congressional inquiries and media requests. These inquiries require the Contractor to provide the AF factual and responsive information. (CDRL A001)

4.5.3 Regulatory/Professional Interface

The Contractor shall develop and prepare verbal/written interaction with interested parties related to the project. Forums may include administrative proceedings, judicial proceedings, formal meetings, or informal meetings. The Contractor shall provide all required support including preparation of presentation materials, agendas, minutes, publications, news releases, public notices, and the maintenance of mailing list(s). (CDRLs A001, B005, B006, B007)

The Contractor shall conduct project technical review, analysis, and discussions to integrate comments from interested parties on programs and related data and studies. The Contractor shall develop recommendations for responses and prepare report(s) to communicate government priorities to regulatory agencies and other interested parties. (CDRL A001)

The Contractor shall conduct review and interpretation of new and proposed statutory and regulatory requirements and make recommendations for government planning and policy integration as it applies and as specified in each TO. (CDRL A001)

4.6 Contractor Documentation

The Contractor shall create and maintain a Master Document List (MDL) for all documents including those maintained as part of the document repository, whether the document is a deliverable or not, which are prepared during the course of each TO. The MDL and its documents shall be maintained in libraries readily available for submittal to the government.

The project website may be used to maintain all or portions of the document repository. The Contractor shall maintain the MDL and project documents for the duration of the contract as specified in each TO and transfer custody to the AF within 90 calendar days prior to PoP expiration. For project documents produced in the final 90 calendar days of the PoP, the contractor shall submit an updated MDL and copies of subject writable and PDF documents as specified in each TO PoP expiration. (CDRL A001)

The Contractor shall maintain a document repository for all documents generated during this contract. The repository is intended to be a single access point repository for all documentation.

It shall be accessible to the AF, with limited access to regulatory agencies, as appropriate. The Contractor shall provide notifications to the COR at the time data is included in the repository and at the request of the COR be able to provide all writable files associated with project work such as reports, supporting data tables, figures, trend analyses, graphs, data, log books, field notes and any other documentation utilized in managing and maintaining the environmental program at the installation. The Contractor shall support coordination efforts with other contractors working onsite who may require access to these files. The Contractor shall prepare metadata sheets and consolidated report documentation including regulatory letters for applicable deliverables and submit electronic and/or hard copies as requested by the CO/COR to the AF administrative record (AR) management team for loading to the AR. At close-out, all repository documents will be transferred to DVD media and delivered to the COR.

Original documents such as software versions, GIS files (including layers), CADD files, modified PDFs, spreadsheets, and databases or other supporting data/files/information including figures, drawings, etc. utilized in managing and maintaining the environmental program at the installation shall be provided regularly at the request of the COR and shall also be included in the close-out DVD. The Contractor shall support coordination efforts with other contractors working onsite who may require access to this data.

4.7 Computer-Aided Design Drawing (CADD) and Geographic Information Systems

(GIS) Updates

All products associated with this contract that provide a map/geospatial representation of the natural and built 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) shall adhere to the following requirements:

All maps and associated data shall comply with latest published guidance and Air Force Adaptation version of the Spatial Data Standards for Facilities, Infrastructure, and Environment (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.

The AF Adaptation of SDSFIE will determine file and feature class identification and definition, minimum attribution and valid domain values in accordance with official AF documents included in the Adaptation Release Package. GIS deliverables shall comply with AFCEC GIO published guidance in the “Data Dictionary”, the latest version of the AFCEC/CIB Master BRAC Geospatial Guidance control document, and Federal Geospatial Data Committee (FGDC) metadata standards per the ArcGIS 10.x template. CAD data shall comply with the latest version of the AF Adaptation of SDSFIE for GIS data and A/E/C 5.0. Any future updates to the Master BRAC Geospatial Guidance will be provided to the contractor by AFCEC/CIB as they are developed.

Geospatial data shall be delivered in a geo-referenced GIS format (with one-to-one cardinality between spatial records and attribute records in accordance with the latest AF Adaptation version of SDSFIE) using the Environmental Systems Research Institute’s (ESRI) geospatial file database formats. All attribute data as specifically outlined in the task order contract shall be included either in the GIS data file or as a separate table with an AF Adaptation of SDSFIE identified primary/foreign key used to relationally join the separate table with the associated GIS geodatabase file.

Each TO will specify the reference system that geospatial data shall be delivered in, either the World Geodetic System of 1984 (WGS84) reference system or the North American Datum 1983 (NAD83) projection, State Plane Coordinate System. When using WGS84 use geographic coordinates (latitude/longitude) or, projected to the appropriate zone of the Universal Transverse Mercator (UTM) Grid System, using feet or metric coordinate units per the coordinate system used. Further guidance on mapping units, coordinate systems and projections can be made available by the COR. For all locations within the Restricted Area, Universal Transverse Mercator (UTM) coordinates must also be provided.

It is the responsibility of the Contractor to collect all geospatial data using mapping-grade or survey-grade Global Positioning Systems (GPS) or comparable traditional survey methods. In the case of contracts involving utility construction, location and attribute data will be obtained at the time of excavation. Specific precision requirements shall be established at the TO level.

Source data and product data remain the property of the United States Government. It is the Contractor’s responsibility to be prepared to explain and demonstrate the company's process for protecting all geospatial data, including geometry, attributes, metadata, topologies, and relational database schemas and operations used in association with this PWS. The Contractor shall sign a non-disclosure agreement for a specific TO before source data is released, if required.

Information about security and nondisclosure requirements will be provided by the COR for each applicable TO. Installation map data, source and/or product, may be qualified by the Government to be “sensitive, but unclassified”, as required in each TO. The intent of this language 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. The Contractor is not authorized to release this information to any third party without the explicit consent of the CO, COR, and AFCEC/CIB if required, and dissemination shall be in accordance with established AF policy and guidance. All source information qualified as “sensitive, but unclassified” shall be returned to the Government POC or destroyed with written concurrence from the COR upon completion of this project. (CDRLs A005, A006)

4.8.2 Cybersecurity Reporting

Contractor agrees to require, in writing, that all subcontracting work performed will ensure the subcontractor is equally bound to adhere to all cybersecurity requirements listed below.

Contractor agrees to require, in writing, that all subcontractors provide the subcontract compliance metrics/evidence of compliance for all subcontract work awarded. Contractor agrees to consolidate all subcontract metrics and contract compliance evidence as part of their overall metrics and contract compliance reporting to the government Contracting Officer’s Representative (COR).

Contractor agrees to ensure all products/services provided: Are designed, implemented, and maintained in accordance with the statutes, guidance, and regulatory compliance requirements listed below. Contractor agrees to thoroughly review each of the requirements listed below for targeted applicability to the product/service provided to the government. Contractor agrees to provide, in writing, a catalog showing each applicable section of the regulations listed below;

what design/implementation criteria will be used to meet each individual requirement, along with implementation checklists and maintenance tasks that will be used to ensure compliance is met and retained for all of the following:

Department of Defense Federal Acquisition Regulation (DFAR) 252.204‐7012 Unified Facilities Criteria (UFC) 4‐101‐06 c1A Department of Defense Manual (DoDM) 8140.01-M Cyberspace Workforce

Management Department of Defense Directive (DoDD) 3020.40 Defense Critical Infrastructure

Program Department of Defense Directive (DoDD) 5200.08‐R Physical Security Program

National Institute of Standards and Technology (NIST) Special Publication 800-53 revision 5, Security and Privacy Controls for Federal Information Systems and Organizations

National Institute of Standards and Technology (NIST) Special Publication 800‐82 revision 2, Guide to Industrial Control Systems

AF Systems Security Instruction (AFSSI) 7700 Emission Security Defense Information Systems Agency (DISA) Secure Technical Implementation Guides

(STIGs) Defense Information Systems Agency (DISA) Security Requirements Guides (SRGs)

Contractor agrees to provide, in writing, an explanation for each section of regulatory guidance listed above where a targeted section could apply under a certain set of circumstance but does not apply under the targeted product/service being delivered. The intent of this contractual obligation is to minimize the chances of a situation where the government awards a contract based on contractor acceptance of responsibility where the contractor incorrectly feels certain aspects of regulatory compliance did not apply to their product/service – thus ultimately providing a service/product that does not meet the original intent of the government.

4.8 Notification Requirements

The Contractor is required to notify the CO and COR 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 (NOV) (received or anticipated), and changes in key personnel, and finding unexploded ordnance (UXO). On critical issues, verbal notification shall be made immediately, followed by written notification within three working days. (CDRL A003)

If unanticipated UXO is discovered during field activities, the Contractor shall immediately stop work, report the discovery to the CO and COR, and implement the appropriate safety precautions. Field activities cannot continue until clearance is received from the CO.

The Contractor shall follow the 3Rs (Recognize, Retreat, and Report) Explosives Safety Education Program; see https://www.denix.osd.mil/uxo.

In the event of a dispute with or enforcement action from a regulatory agency arising from performance of work covered as specified in each TO, regardless of whether the AF is a named party, the Contractor shall notify the CO or COR within 24 hours. If the AF is a named party in the dispute or enforcement action, the Contractor shall provide support to the AF as required to resolve the dispute or enforcement action. If the AF is not a named party in the dispute or enforcement action, the Contractor shall provide its proposed response to the dispute or enforcement action to the AF for review and comment prior to submission. Contractor support typically includes preparing a briefing, point paper, and summary of technical data to support the AF position. (CDRL A001)

4.9 Permits

The Contractor shall develop, coordinate, and assist the installation in applying for and obtaining all federal, state, local, and other applicable permits, access (including off-base easements and leases), agreements, licenses, and certificates required to perform and complete effort as specified under each TO. The Contractor shall maintain a library of these documents at the Contractor’s site office on base as well as the corporate facility handling each TO. The Contractor shall comply with all applicable permit conditions. The Contractor shall conduct site visits and develop site visit reports. The Contractor shall develop, coordinate, and assist with obtaining necessary installation-level permits and site access approvals. Documents to be developed may include ancillary plans, surveys, site access requests, permit requests, waivers, impact analysis reports, drawings, and other documentation necessary to meet base-level and off-base level access and permitting requirements. Requirements include all documents necessary for Airfield access waivers and clearance, when required. (CDRL A003)

4.10 Photo Documentation

The Contractor shall prepare digital photographic documentation, as required to meet the objectives specified in each TO. The Contractor shall include photographic documentation of site(s) and building(s) under investigation, field activities, and sample locations. The Contractor shall provide photo documentation to the AF as appropriate, as part of other deliverables, or at the request of the CO and/or COR. Daily Field Quality Control Reports (DFQCRs) shall be completed during the execution of fieldwork and may include photo documentation in addition to reporting field work progress. The Contractor shall prepare digital photographic documentation, as specified in each TO. The Contractor shall include photographic documentation of site(s) and building(s) under investigation, field activities, and sample locations. Photography of any kind must be coordinated through the installation, customer, or facility Point of Contact (POC). (CDRLs B010, B011)

4.11 Remote and/or Austere Sites

The Contractor may be requested to perform work as specified at remote and/or austere locations. The Contractor shall be responsible for all personnel, security, supplies, equipment, and infrastructure (including, but not limited to, potable water, utility systems, housing, dining, transportation, and medical care) when there are no facilities and services available. This shall include providing these facilities and services to a limited number of government personnel or other contractor personnel (such as Title II personnel) present or visiting to oversee or assess the work.

4.12 Site Access: Permits, Easements, and Work Site Access

At the direction of the Government, the Contractor shall develop, coordinate, apply for, pay fees for, comply with, and/or modify all federal, state, local, and other applicable permits required to meet the objectives specified in each TO. The Contractor shall maintain a library of these documents and maintain copies at the installation where applicable. (CDRL A001)

Pursuant to CERCLA (42 U.S.C. 9621(e)), no federal, state, or local permits shall be required for onsite CERCLA removal or remedial actions. The Contractor must consult with the AF prior to obtaining environmental permits for onsite CERCLA activities. For non-CERCLA restoration sites, the Contractor shall comply with all applicable permit conditions, including implementation of the permits 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 requests to provide mapping information for all onsite remediation systems, and other dig/utility locate related requests, requiring the identification of subsurface appurtenances and utilities associated with new and existing remediation systems included in this as specified in each TO. In accordance with individual state requirements, the Contractor shall subscribe to the requisite utility locator service(s). Utility location requests will be sent to the Contractor via utility notification service (i.e. dig safe, etc.) and the Contractor will be required to review, respond, and address all location requirements. The Contractor shall maintain all records pertaining to location requests.

At the direction of the Government, the Contractor must coordinate with the AF prior to supporting notifications to property owners, as required under the appropriate deeds. In addition, the Contractor is responsible for any renewal payments for easements or leases unless otherwise specified.

The Contractor shall be responsible for identifying and obtaining access to the worksite (including site access badges, rights of entry, access agreements, notifications, encroachment permits, etc.) through coordination with the AF, county, municipal, airport, landowner, tenant, and other stakeholders to ensure access to all areas necessary to conduct activities as specified in each TO. (CDRL A001)

At the direction of the Government, the Contractor shall prepare documents using AF-provided templates, pay the rent or purchase price and associated expenses for the AF to maintain or support modification of existing rights of access, or to acquire new rights of access, to non-AF land which the Contractor needs to satisfy the performance objectives of this contract. At the direction of the Government, the Contractor shall support the designated installation official (e.g., BEC) with activities necessary to negotiate and sign the documents to obtain or modify the necessary rights of access with technical inputs 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 inputs expected or that may be requested by the AF from the Contractor under direction of the Government for rights of access including support with developing the 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 providing the aforementioned technical inputs, fees for recordation of real property documents associated with acquiring the right(s) of access, costs for payment of or restoring property damage resulting from Contractor's activities on the property on which the right(s) of access were acquired, costs for obtaining "dig safe" or "utility clearance" approvals from appropriate utility and governmental entities, and costs for notifying or communicating with affected property owners regarding rights of access.

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 except as specified in each TO.

4.13 Worksite Activities and Coordination

4.13.1 Coordination of Activities

The Contractor shall coordinate worksite activities with all applicable personnel and/or agencies to ensure the protection of human health and the environment; the prevention of damage to property, utilities, materials, supplies, and equipment; and the avoidance of work interruptions.

The Contractor shall ensure all work areas are secure and appropriate measures have been taken to eliminate any risk to the public on active environmental sites, as appropriate. The Contractor shall perform emergency response for situations arising from project activities. The Contractor shall perform emergency repairs to facilities, systems, improvements, or utilities damaged in the course of conducting work specified in each TO. The Contractor must comply with OSHA safety and health regulations and local safety office requirements. The Contractor is required to provide the CO copies of any OSHA report(s) submitted during the duration of this contract as specified in each TO. (CDRL A004)

All on-site workers (Contractor and subcontractor) performing hazardous operations, including working with hazardous materials, must have completed the OSHA 1910.120 Hazardous Waste…