Attachment 0001 - Statement of Work - SIR - 697DCK-24-R-00438- WSA - Engineer Services -06-05-2024.pdf

PDF 227 KB Posted

Attached to
BIL Funded Engineering Professional Services - Western Service Area Districts (Anchorage, Denver, Salt Lake City, Seattle, Honolulu, Los Angeles, Oakland)
Solicitation number
697DCK-24-R-00438
Issued by

About this file

This document is a Statement of Work (SOW) for a federal contract opportunity to provide engineering professional services to support the Federal Aviation Administration's (FAA) Bipartisan Infrastructure Law (BIL) projects in the Western Service Area (WSA) districts (Anchorage, Denver, Salt Lake City, Seattle, Honolulu, Los Angeles, Oakland).

The key details are: The contractor must provide up to 7 certified engineers in various disciplines to support design efforts, project planning, engineering, construction oversight, and implementation support for projects such as new facility construction, modernization, and upgrading of existing FAA facilities across the WSA. The contractor will be responsible for onboarding the initial 3 engineers within 1 month and submit a hiring plan for the remaining 4 engineers. Work will be assigned by the Contracting Officer's Representative based on recommendations from the District Project Coordinators. The contractor must comply with FAA requirements for operational risk management, safety, quality control, and information management. This is a set-aside for vendors on the FAA's Qualified Vendors List for District Project Coordination and Engineer Project Oversight Contract Support.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Solicitation No.: 697DCK-24-R-00438

Attachment 0001 - Statement of Work

BIL Funded Engineering Professional Services - Western Service Area Districts

(Anchorage, Denver, Salt Lake City, Seattle, Honolulu, Los Angeles, Oakland)

STATEMENT OF WORK

Bipartisan Infrastructure LAW (BIL) Engineering Professional Services

For the

Western Service Area Districts

(Anchorage, Denver, Salt Lake City, Seattle, Honolulu, Los Angeles, Oakland)

Table of Contents

1.0 INTRODUCTION

1.1 BACKGROUND ............................................................................................................................................... 3-4

1.2 SCOPE OF WORK

1.3 CONTRACTOR HIRING REQUIREMENTS ..........................................................................................................4-5

1.4 TECHNICAL WORK AREAS

1.5 DISTRICT ENGINEER/IMPLEMENTATION SUPPORT ......................................................................................... 5-6

1.6 Travel

1.7 Key Functions and Activities ........................................................................................................................ 6-7

1.7.1 DELIVERABLES ............................................................................................................................................. 7-8

1.8 Technical Work Management

1.9 Operational Risk Management (ORM) ...................................................................................................... 9-10

1.10 Information Management

1.0 - INTRODUCTION

This Statement of Work (SOW) sets forth the requirements for a procurement for district engineering and implementation support of the Federal Aviation Administration’s portion of the

Bipartisan Infrastructure Law (BIL) and reimbursable programs (including those arising from

Airport Improvement Program (AIP) appropriations and other directly funded reimbursable projects). Work under this contract will be distributed across the three service areas of the National

Airspace System (NAS) which includes all 50 states, US territories and possessions and may also include aviation-related sites globally. There will be three contracts, one for each service area. The contractor will be responsible to provide necessary services for the service area assigned under the contract. Engineers will not be assigned to individual districts but will support work requirements for each district as determined by the Program Management Office by taking recommendations and assigning priorities to those recommendation from the District Project Coordinators and in consultation with District Managers.

Throughout this document the term “District” refers to the FAA Air Traffic Organizations (ATO)

Technical Operations (Tech Ops) Districts. There are 22 districts, and they align with the NAS airspace boundaries. The Districts for the Western Service Area include: Anchorage, Denver, Salt

Lake City, Seattle, Honolulu, Los Angeles, Oakland. The term “FAA Headquarters” refers to the

FAA National Headquarters, located at 800 Independence Avenue, SW, Washington, DC, and its associated satellite office locations.

The FAA currently anticipates FAA points of contact at most, if not all, of the district locations identified above. At any point during the performance of this Contract, however, the FAA may reorganize or change the locations of the local points of contact. It is the responsibility of the

Contractor to determine and maintain the most efficient and effective management organization for planning, coordinating, implementing, performing, and conducting all work efforts required under the contract, regardless of the FAA organizational structure.

1.1 - BACKGROUND

The US National Airspace System (NAS) is a very complex and diverse system with a vast number of systems with varying modernization timelines and operational maintenance needs and timelines.

The NAS is inherently complex and needs additional support to address the growing backlog of work to sustain facilities. The Bipartisan Infrastructure Law (BIL) is intended to address the increased amount of needed work to improve and sustain our infrastructure. The BIL not only increases the magnitude of funding within the ATO, but also increases the activities and projects at airports, many of which may result in reimbursable agreements for the FAA.

Work will be provided to support and conduct design efforts on multiple projects throughout the

Service Area and will be assigned by the COR based on recommendations provided by individual

District Project Coordinators. However, inclusion of a project or program in BIL does not guarantee that work under the project or program will be accomplished under this contract. Project requirements are subject to change as necessary and the selection of projects for performance under this Contract rests solely with the FAA.

Support services offered by Contractor personnel must provide depth, breadth, and quality. Depth is identified as “up to 7 engineers for each Service Area.” Breadth is required to respond to a wide range of needed support services at multiple locations throughout the United States, the FAA’s

NAS and within each Service Area and beyond. Quality is required to assure the best possible results are achieved in any given work effort. Quality requirements further dictate that the

Contractor must possess the requisite experience levels and past performance history, as well as the ability to acquire and manage personnel resources to provide the highest possible levels of quality.

1.2 - SCOPE OF WORK

Except for FAA furnished property (equipment, supplies, and/or material), the Contractor must furnish professional certified engineers in various disciplines as outlined in the solicitation. The contractor must also provide technical and support labor, material, supplies, management services, data, and facilities required to accomplish the work to be ordered under this contract. All work performed under this Contract will be ordered through the issuance of requirements issued by the

FAA based on the recommendations of the individual District Project Coordinators, input from

District Managers. Ultimately, the COR will set and assign work assignments and priorities to the contractor. This may also be communicated in a letter issued by the Contracting Officer (CO) or its

Representative in limited cases. The District Project Coordinator will identify and provide recommendations and priorities to the FAA which may include but not be limited to project coordination and oversight activities related to new construction or installation, restoration, service life extension, demolition, removal, and refurbishment of FAA facilities.

1.3 - Contractor Hiring Requirements

The contractor shall onboard the first proposed three engineers within a month after contract award and submit their hiring plan to hire the remaining four engineers in the varying disciplines. The FAA will be clear to communicate to the contractor the Service Area needs and will work closely with the

Service Area District Managers to clearly identify and prioritize those needs for the contractor and allow the contractor the necessary time to onboard sufficient resources to meet those needs. Any additional engineers will be subject to the needs of the Government and the FAA reserve the right to adding or not adding any of the remaining four engineers.

To ensure that engineering support positions are effectively utilized and add value to the districts, the engineering support positions will be assigned to Service Areas to support select Districts based on local project needs. The engineer shall reside within the Service Area to minimize travel and response times. The FAA will gather lessons learned and refine processes and procedures based on the initial positions filled. The FAA will evaluate the effectiveness and value of engineering support and make needed adjustments six months after the initial positions are in place. Again, the contract employees will not be assigned to the individual districts but rather the Service Areas.

1.4 - Technical Work Areas

Types of work that may be performed under this contract are described below. In performing all work under the Contract, the Contractor must adhere to all Occupational Safety and Health

Administration (OSHA) requirements, all FAA occupational safety programs and requirements as set forth in the List of Applicable Documents, all taxation laws, and all applicable federal, state, and local government codes, statutes, laws, and regulations (including the obtaining of any required permits. The Contractor will be responsible for only the scope of work contained in its requirements outlined in the agreed-upon contract and any future modifications.

1.5 - District Engineer/Implementation Support:

The contractor must provide oversight and quality assurance for projects on behalf of the FAA.

Work may relate, but is not limited to, potential new FAA facilities, modernization, and/or upgrading of existing FAA facilities. Contractor must support the project planning, engineering and construction oversight for alteration, relocation, installation, and inspection of facilities and equipment.

The Contractor must provide certified and licensed, as appropriate, engineering expertise and assistance for the implementation of projects. Professional, licensed engineers from a variety of engineering disciplines may be required, as applicable, including, but not be limited to, civil, construction, electrical, electronics, mechanical and fire protection.

This position will provide contract design support and construction oversight of local projects within the districts. The engineering support position will work closely with the District Project

Coordinator, the NAS Implementation Manager (NIM) or NAS Implementation Program Manager

(NPPM). This position will provide support and coordination of local projects (e.g., providing site access, oversight of site survey and implementation activities, periodically checking in on active projects, etc.) as necessary.

This is a Service Contract and the contractor must comply with the following AMS Procurement

Guidance:

T3.8.2 Service Contracting Revised 10/2008, A Service Contracting, section 4 Support Services

Contracting Revised 7/2023, paragraph J.

Contractor Identification: Contractors providing support services for FAA, as defined in this Section, must identify themselves as supporting an FAA office or program when there is any reasonable question regarding their status. This identification must be in all forms of support- related communication including meetings and teleconferences, individual phone calls, and email. For example, in meetings where everyone is introducing themselves or when making or receiving calls though the FAA telephone system, such contractors must identify themselves as contract support. At meetings where there is a “sign-in” sheet or similar roster, contractors must identify themselves as contract support. Similarly, the signature block of support contractor personnel using the FAA email system (in addition to the “ctr” in the email address) must identify the individual as a support contractor. Such identification will reduce the potential for appearances of an employer-employee relationship between FAA and its contract support personnel. FAA program managers, CORs, and contracting personnel are responsible for ensuring compliance with this requirement as part of the administration of individual support contracts.

Scope: These positions will support locally implemented projects as well as oversee project execution of select projects where Engineering Services is not involved nor required, such as:

• EG and FST replacements at tier 4 and 5 facilities

• Small scale shelter replacements

• Small scale parking lots and fences

• Small HVAC Replacements such as window units or mini splits

• Roof replacements

• Small scale elevator service life extension and maintenance projects

Any project oversight of projects where Engineering Services is not involved will be coordinated with and agreed to by the districts through coordination by the District Project Coordinator prior to taking on this work.

1.6 - Travel

Occasional travel is required in the performance of this contract. Prior to any travel being conducted in the performance of this contract, the Contractor must submit a travel request to the

COR. The COR will follow AMS Procurement Guidance Appendix 2, Selected Cost, paragraph 43, Travel Costs, (Revised 10/2023) to ensure that cost incurred as a result of travel in the performance of the contract is properly invoiced and the invoices comply with the requirements outlined under clause 3.3.1-40 Electronic Submission of Payment Requests (APR 2022).

As prescribe by AMS Procurement Guidance Appendix 2, Selected Cost, paragraph 43, Travel

Costs, (Revised 10/2023), costs incurred for lodging, meals, and incidental expenses as defined in the regulations below shall be considered to be reasonable and allowable only to the extent that they do not exceed on a daily basis the maximum per diem rates in effect at the time of travel as set forth in these regulations.

(i) Federal Travel Regulations, (Stock No. 922-002-00000-2) prescribed by the General Services Administration, for travel in the conterminous 48 United States, available on a subscription basis from the: Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402.

(ii) Department of Defense Per Diem, Travel and

Transportation Allowance Committee (PDTATAC) bulletins, for travel in Alaska, Hawaii, The

Commonwealth of Puerto Rico, and territories and possessions of the United States, available in the Federal

Register (or in the Section 925 Supplement to the guidance cited under (a)(2)(iii) below); or

(iii) Standardized Regulations (Government Civilians, Foreign

Areas), Section 925, "Maximum Travel Per Diem

Allowances for Foreign Areas," (Stock No. 744-008-

00000-0) prescribed by the Department of State, for travel in areas not covered in (a)(2)(i) and (ii) of this subparagraph, available on a subscription basis from the:

Superintendent of Documents, U.S. Government Printing

Office, Washington, DC 20402.

Costs for transportation may be based on mileage rates, actual costs incurred, or on a combination thereof, provided the method used results in a reasonable charge.

Airfare costs in excess of the lowest-priced airfare available to the contractor during normal business hours are unallowable except when the lowest priced airfare requires circuitous routing, require travel during unreasonable hours, excessively prolong travel, result in increased cost that

In accordance with Clause 3.3.1-40 Electronic Submission of Payment Requests (APR 2022), all invoices which include charges pertaining to travel expenses will catalog a breakdown of reimbursable expenses with the appropriate receipts to substantiate the travel expenses.

1.7 - Key Functions and Activities

The contractor will provide engineering support to the districts to support locally implemented projects (those projects being implemented by the Systems Service Center (SSC) without ES involvement). This type of support will involve creating and reviewing simple engineering packages, coordinating with vendors, and overseeing onsite work.

• Conducting site surveys

• Preparing required engineering packages and documentation (including statements of work, independent government cost estimates, etc.)

• Coordinating acquisitions on local procurement.

• Coordinating with vendors on required permits and certifications and/or submittals as required by regulation and/or site requirements.

Provide project construction surveillance and oversight (as defined in the Construction Surveillance and Oversight section below) of district implemented projects.

This position will provide engineering support for local projects, including but not limited to the following activities and tasks:

• Assist in designing local projects:

o Create statements of work o Develop independent cost estimates o Coordinate with acquisitions on local procurements o Create Project Risk Plans for local projects o Review simple design packages and submittals

• Provide construction oversight of local projects o Coordinate site surveys o Oversee and monitor active projects

▪ This may include overseeing projects implemented by local vendors or national implementation contractors (e.g., TSSC) o Coordinate Operational Risk Management Program (ORMP) and Joint Acceptance

Inspection (JAI) requirements as appropriate o Complete/verify 3900 Forms (e.g., EOSH Checklists) o Participate in Contractor Acceptance Inspections (CAI) and JAIs when needed

• Manage project execution activities

• Provide project schedule status to Planning and Requirements Group (PRG), Program

Implementation Managers and Schedulers

• Coordinate and work closely with the NIM/NPPM and District Project Coordinator

1.7.1 - Deliverables

The table below outlines the key deliverables the district engineer will provide. It’s not all inclusive and may be amended.

PRODUCTS Conditions and Due Date

• Conducting site surveys Within 30 days from requirement identification or work assignment

• Develop independent cost estimates Within 30 days from requirement identification or work assignment

• Create Project Risk Plans for local projects Within 30 days from requirement identification or work assignment

• Review contractor product and construction submittals

In coordination with and aligned to the project construction schedule

• Provide construction oversight of local projects In coordination with and aligned to the project construction schedule

• Coordinate ORMP and JAI requirements as appropriate

In coordination with and aligned to the project construction schedule

• Complete/verify 3900 Forms (e.g., EOSH

Checklists)

In coordination with and aligned to the project construction schedule

• Participate in CAI/JAI when needed In coordination with and aligned to the project construction schedule

• Provide project schedule status to Planning and

Requirements Group (PRG) PIMs/Schedulers

Monthly

This position will NOT:

• Align or schedule Preventative Maintenance Tasks (i.e., PM Alignment)

• Coordinate outages for the SSCs (Technician function)

• Coordinate activities for the district (District Project Coordinator function)

• Provide CWP project planning/management of local projects (PRG PIM function)

1.8 - Technical Work Management

Technical work management includes policies, procedures, and practices by which the Contractor’s organization will operate within existing and react to new, changed, deleted, or emergent work requirements. The Contractor must be capable of simultaneously performing work at multiple locations across the Service Area.

1.9 - Operational Risk Management (ORM)

Operational Risk Management (ORM) practices must be adhered to on all projects and support of

ORM processes is expected by/of the Contractor for all Work Areas. For all projects, the contractor must also follow the procedures defined in Order 6000.50, National Airspace System

(NAS) Project Implementation Risk Planning and Order 6000.15, General Maintenance Handbook for NAS Facilities. ORM principles and concepts must be included in safety plans for projects that affect the NAS, from design and planning through construction and turn-over to the FAA.

Operational consequences are the result of unexpected loss or degradation of NAS services (i.e., unscheduled outages) that potentially compromise the ability to provide safe air traffic services and every effort must be taken to minimize such events.

Principles of ORM include Situational Awareness; Planned Actions; Identifying Operational

Consequences; Communication; Coordination; Mitigation Implementation; Safe Project

Implementation; Close out. A Generic Site Implementation Plan (GSIP) may be written by an FAA

Program Office or by the Contractor as part of the work requirement. The GSIP describes the steps necessary to complete construction and/or installation of a NAS system. These plans are intended to cover all construction and/or installation aspects that are common, regardless of where the activity is being accomplished in the NAS. In addition, a Project Risk Plan (PRP) will be developed for the project(s) either by the FAA and provided to the Contractor or may be required to be developed as part of the requirement issued by the DPC. The PRP is required to be completed prior to allowing certain construction and/or installation activities to proceed. The FAA System Support

Center (SSC) is responsible for assimilating the risks and mitigations from the PRP into an

Operational Risk Management Plan (ORMP) for every project. The SSC is responsible for initiation, routing, and approval of the ORMP, however work on identified activities requiring and

ORMP must not commence until approval has been granted.

Work requirement risk planning must include a risk assessment for each work location within the work plan. Project risk also includes cost risk elements to be incorporated into the Estimate to

Complete (ETC). Initial Plans (pre site visit) will include a presumptive risk analysis based upon available information at the time. After a site visit is accomplished, the risk plan must be updated.

• Risk Identification - generate a comprehensive list of credible risks that might negatively impact the project

• Risk Analysis - develop an understanding of the risk

• Assessment of the probability of an occurrence of a specific event - what is the likelihood the risk would happen

• Impact - what is the impact if it does (systems and operations)

• Risk Evaluation - make decisions based on the outcomes of risk analysis

• Approach - which risks need mitigation

• Methodology - identify the options for mitigating the risks

• As the work progresses, reassess the risk and adjust cost-based risk in the ETC (for projects scheduled for, or continuing, more than 75 days)

The Contractor must also implement quality control, safety and security programs and procedures with an objective to ensure high quality performance and total compliance with all Contract requirements. This must include a defined process for accomplishing prompt corrective actions should deficiencies be found and a feedback process for revising procedures to prevent recurrence of identified deficiencies. For work plan and safety requirement activities, the Contractor must also provide a safety and QC incident trend analysis process to reduce incidents across the contract.

Information Management

The Contract will be administratively managed using an FAA-provided Knowledge Management

System. The system will be only accessible on the FAA Intranet following approved FAA IT security procedures. The Contractor must maintain an interface capable of electronically sharing contractor-generated data with IMS. The interface must be available to provide data access unless an outage is scheduled and coordinated with the FAA in advance.

The Contractor must maintain compliance with all government Information Systems Security policies, training, and procedures (such as the FAA Information Systems Security Program Order

1370.82 and its successors, updates, and/or supplements) as required and directed by the FAA.

Contractor employees are required to apply for FAA email accounts. Contractor personnel must have Virtual Private Network (VPN) accounts and all accounts must be approved by the Program

Office.

File details come from the government source that posted it. Updated .