FENS Section C.docx

Federal Aviation Administration

FAA Enterprise Network Services

(FENS)

Section C Statement of Work V1.2V1.3

March,August 2024

Federal Aviation Administration 800 Independence Avenue, SW Washington, DC 20591

C-69

List of Changes

· CDRL F039-SPD is deleted.

· CDRL F040-ISCP is changed from an Information System Contingency Plan to a NAS System Contingency Plan (NSCP).

· CDRL F041-ISCP is changed from an Information System Contingency Test Plan to a NAS System Contingency Test Plan (NSCTP).

· CDRL F042-ISCP is changed from an Information System Contingency Test Results to a NAS System Contingency Test Results (NSCTR).

Table of Contents

PART I - THE SCHEDULE

SECTION C – STATEMENT OF WORK

Introduction Background This Statement of Work (SOW) defines the requirements for the services that the Contractor must provide to the Federal Aviation Administration (FAA) under the FAA Enterprise Network Services (FENS) contract. Detailed functional and performance specifications are contained in the FENS Functional and Performance Specification (FFPS), Attachment J-1.

The FENS program will provide highly available and secure communications, information management services, functions, and capabilities required by the FAA to support its continuing mission of providing the safest, most efficient aerospace system in the world. In addition, FENS will provide access to administrative information systems and functions including e-mail, payroll, and on-line training. To meet applicable security standards and policies, FENS services will be segmented into distinct Networking Capabilities, e.g., Critical Services, Essential Services, and Administrative Services, and others as defined by the Government. The ability to support secure communications within FENS Networking Capabilities, between FENS Networking Capabilities, and between FENS Networking Capabilities and external networks (e.g., the Public Internet) is also required.

Managed Services Framework The FENS SOW is based upon a Managed Services Framework. This means that the Government defines its requirements and the Contractor provides the services, functions, and capabilities needed to meet those requirements. The Contractor is responsible for all facets of service delivery including the design and provisioning of services, the operation and management of network infrastructure, and network monitoring, troubleshooting, and service restoration – all of which are subject to a significant level of Government operational oversight.

Pursuant to this contract, the Government provides its requirements via service orders and the Contractor interfaces directly with communications service providers (CSPs) and other supply chain sources as needed to meet the requirements. The Contractor also provides the Government with visibility into the status of services through all phases of ordering, implementation, and operation. While the Government and the Contractor have distinct roles and responsibilities under a Managed Services Framework, there is extensive collaboration required between the Government and the Contractor due to the safety-critical nature of the FAA’s mission referenced in Paragraph C.1.1.

Fundamental to the delivery of solutions and services under a Managed Services Framework is the establishment of a Service Level Agreement (SLA) that formally documents the Contractor’s commitment to performance of the provided services. The SLA is comprised of measurable Key Performance Indicators (KPIs) relative to services required under the contract. The KPIs may be based on meeting or exceeding contract requirements. For each KPI, the SLA defines specific terms and conditions that apply if the Contractor does not meet the SLA. The SLA is intended to incentivize Contractor performance in a manner that directly benefits the customer. The FENS SLA is documented in Attachment J-10.

Scope of Services As depicted in Figure 1-1, the scope of services under the FENS contract includes: (1) services, functions, and capabilities defined in the FFPS; and (2) Support Services defined in this SOW. The FFPS defines requirements for Communications Services, Enterprise-level Functions, and User Portal Functions. Communications Services are divided into two subcategories: (1) Network Services that support the transfer of data from a source to one or more destinations, and (2) Information Management Services that are based on Application Layer messaging standards. Enterprise-level Functions are capabilities provided at the enterprise level that can be shared by multiple Communications Services or are provided to the benefit of the entire enterprise (e.g., boundary protection). User Portal Functions enable Government-designated users to access: (1) Contractor-provided applications and tools that support required processes such as service ordering; and (2) information pertaining to FENS services. Support Services are requirements defined within this SOW that are performed by Contractor personnel to support the delivery and operation of the Communications Services, Enterprise-level Functions, and User Portal functions.

Figure 1-1. Scope of FENS Required Services The scope of the required Communications Services includes, but is not limited to, interfacility and intra-facility exchanges of voice, data, and video. The range of service delivery locations is defined in SOW Paragraph C.1.4.

The range of users of FENS services is determined by entities connected to FENS Network Capabilities. The FFPS defines a Networking Capability as an isolated Network Infrastructure operated with a common set of resources, security capabilities and security policies. The FFPS identifies three distinct FENS Networking Capabilities:

1) Critical Services Networking Capability (CSNC): Networking capability to support service flows to/from National Airspace System (NAS) Safety-Critical and NAS Efficiency-Critical systems, as defined in the NAS Requirements Document (RD).

2) Essential Services Networking Capability (ESNC): Networking capability to support service flows to/from NAS Essential and most NAS Routine systems as defined in the NAS RD.

3) Administrative Services Networking Capability (ASNC): Networking capability to support service flows to/from a combination of select NAS Routine systems, FAA administrative systems, and other non-NAS systems.

Depending on the service criticality level, the users connected to the respective Networking Capabilities may include information systems and applications operated by the FAA, Department of Defense (DoD), National Weather Service (NWS), other Government agencies, and non-Government entities that are stakeholders in the FAA’s mission.

The scope of services obtained under the FENS contract is not limited with respect to specific technologies (e.g., wireline, wireless, satellite, microwave, etc.) as long as the services, functions, and capabilities meet the applicable requirements defined in the FFPS.

Services provided under the FENS contract will evolve and change over the contract period of performance to meet emerging requirements as existing user systems are modernized and new user systems are implemented.

Service Delivery Locations The locations for the delivery of services required under this contract include sites within the contiguous United States (CONUS) and outside the contiguous United States (OCONUS), e.g., Alaska, Hawaii, U.S. territories, and foreign countries. The majority of service delivery locations are Government facilities, but may include commercial or other types of non-Government facilities.

Applicable Documents Services provided under this contract must comply with the applicable orders, directives, standards, and policies (collectively referred to as “applicable documents”) listed in this section. An additional list of applicable documents is provided in the FFPS (Attachment J-1).

The applicable documents consist of Government documents as well as non-Government documents. The Contractor is responsible for reviewing all applicable documents, understanding their impact on the delivery of the required services, and complying with the applicable requirements. The most current version of each document at time of contract award will be the applicable version at the beginning of contract performance. When and if updates are made to applicable documents during the contract period of performance, the Contractor will be allowed to assess the update for any effect on contract performance before it is incorporated into the contract.

Government Documents The Contractor must adhere to all applicable Government documents listed in Table C.2.1-1.

Table C.2.1-1. Applicable Government Documents

Non-Government Documents The following non-Government documents are applicable to the performance of Contractor work efforts. Unless specifically identified by version, the latest version of the document applicable is the one that was current at the time of contract award.

Table C.2.2-1. Applicable Non-Government Documents

(2016) Quality Management System – Requirements for Aviation, Space and Defense Organizations

Order of Precedence Between the SOW and Applicable Documents

(a) If the requirements of this SOW and the Applicable Documents referenced in SOW Paragraph C.2 are in conflict, the SOW has precedence.

(b) If the Contractor identifies a potential conflict between the SOW and the Applicable Documents, the Contractor must advise the FAA Contracting Officer (CO) for resolution in accordance with the conditions specified in Section H.5.

Availability of Documents Copies of FAA orders, directives, and policies may be obtained from the FAA Contracting Officer as identified in Section G of this contract. Requests must clearly identify the title and/or number of the document.

Government-furnished Items and Government Responsibilities Government-Furnished Items (GFI) This paragraph identifies items that the Government will furnish to the Contractor as needed to support the delivery of services provided by the Contractor.

Facility Access With respect to FENS service delivery locations, the Government will provide the Contractor with access to Government facilities and arrange for Contractor access at non-Government facilities as needed.

Site Documentation The Government will provide the currently available site documentation (e.g., site drawings and building blueprints) to support the delivery of FENS services at Government facilities. When the Government performs a Site Survey rather than ordering a Contractor-performed Site Survey under SOW Paragraph C.4.2.7.1, the Government will provide the Contractor with the results of the Site Survey.

Equipment Space Facility space available at FENS Service Delivery Locations for installation of Contractor-provided equipment, inclusive of commercial telecommunications service provider (a.k.a. “carrier”) equipment installed to support FENS services, will be determined on a case-by-case basis. The amount and type of space at facilities available for use in on-site maintenance activities, equipment storage, and related purposes will also be determined on a case-by-case basis. As indicated in SOW Paragraph C.4.2.7.4, the Contractor may be required to install its equipment in a temporary location due to space constraints and then relocate the equipment to its permanent location at a later date.

If a site survey is not conducted by the Contractor for a facility, the Government will determine the amount, the type, and the location of available space for equipment installation, on-site maintenance activities, equipment storage, and related purposes.

Workspace, Computers, and Computer Networks Upon request by the Contractor and subject to availability, the Government will provide workspace for Contractor personnel permanently located on-site at FENS Services Delivery Locations. Workspace will generally be available at Air Route Traffic Control Centers (ARTCCs), large Terminal Radar Approach Control (TRACON) facilities, and other large facilities as determined on an individual case basis. The workspace will include a desk and chair, telephone, and personal computer with connections to the FAA Local Area Network (LAN) and Wide Area Network (WAN), if required. Contractor personnel must adhere to FAA policies for use of Government computers and computer networks.

Demarcation Equipment The Government will furnish the demarcation equipment required to support the delivery of the Contractor-provided Communications Services unless ordered from the Contractor as specified in SOW Paragraph C.4.2.7.9.

Intra-facility Wiring and Cabling The Government will furnish the intra-facility wiring and cabling to support the delivery of FENS Communications Services on the Government’s side of the Service Delivery Point (SDP) unless ordered from the Contractor as specified in SOW Paragraph C.4.2.7.6.

Environmental Control The Government will provide the environmental control at FENS service delivery locations in accordance with FAA Order 1050.1F, Environmental Impacts: Policies and Procedures.

Electrical Power and Grounding The Government will provide the electrical power required for the operation of Contractor-provided equipment at FENS service delivery locations. Power will be available from Government-provided power panels. While the physical implementation of power systems may vary across sites in terms of manufacturers, models, and other factors, the available power sources will conform to the electrical standards specified in FAA-G-2100H for domestic locations. Electrical standards for non-domestic locations will be determined on a case-by-case basis.

At NAS operational facilities, Contractor-provided equipment requiring power will be connected the highest quality of power available at the site, e.g., the critical power bus where available. FENS equipment at non-NAS facilities will be connected to the standard commercial power source. Government-furnished uninterruptible power supplies (UPSs) or back-up power capabilities may not be available for FENS use at all sites.

The Government will connect Contractor-provided power ground and signal ground cables to the Government-provided power panels.

Networking Equipment and Services In some cases, the Government may be able to furnish networking equipment and services to the Contractor to support its delivery of services, functions, and capabilities required under this contract. The Government will advise the Contractor when such items are available to the Contractor. The Contractor must inform the Government of its intent to use Government-furnished items and must conform by the terms and conditions defined in Section H.27 regarding the use of Government-furnished items in the delivery of FENS services, functions, and capabilities. The Government will update the list of Government-furnished items in Section H.28 of the contract as needed to reflect additional items that become available for Contractor use.

Government Responsibilities The section identifies activities that are the responsibility of the Government in support of the execution of the FENS contract.

Program Management The Government Program Office is responsible for the management of the FENS program. The Government Program Office will coordinate interaction with FAA facility and operational points of contact (POCs), other Government agencies, and other Government contractors to support the FENS scope of services.

Site Preparation and Equipment Installation The Government will perform all work necessary at Government facilities to prepare the sites for the receipt of Contractor provided and installed equipment, unless otherwise ordered under the provisions of SOW Paragraph C.4.2.7.3. The Government will be responsible for the drilling of holes, if needed, to accept rack tie-down bolts and any hazardous materials abatement required to support the drilling.

Removal of Government-Owned Equipment The Government is responsible for the removal of any Government-owned equipment displaced by the introduction of FENS equipment.

Coordination with Legacy Service Providers The Government is responsible for coordination with its legacy service providers to ensure the necessary coordination takes place to support the transition of services from legacy networks to FENS.

Test and Verification Per SOW Paragraph C.4.2.6.9, the Government may conduct independent operational test and evaluation activities to confirm interoperability of Contractor-provided services with end user systems.

Depending on the availability of personnel, the Government may witness Contractor-conducted test and verification activities.

Security Authorization The Government, with Contractor support required by SOW Paragraph C.4.2.12, is responsible for managing and conducting all activities necessary to obtain the security authorization of Contractor-provided infrastructure and services as required by FAA Order 1370.121, FAA Information Security and Privacy Program & Policy, Chapter 2, Section 5.4. The Government will authorize Contractor-provided services and capabilities prior to operation in the NAS. The Government will conduct independent security assessments and report on the security posture through testing and evaluating compliance with security requirements to secure the NAS and meeting Federal Information Security Management Act (FISMA) security authorization reporting requirements.

Service Cutovers The Government is responsible for the cutover of FENS communications services to operational use following successful completion of service acceptance testing by the Contractor. The Government may request cutover support from the Contractor per SOW Paragraph C.4.2.9.

Contractor-Provided Services and Functions This portion of the SOW defines specific requirements that must be met by the Contractor when providing the scope of services identified in SOW Paragraph C.1.3. In alignment with Section B of the contract, the requirements are divided into two major groupings:

1) Communications services, functions, and capabilities defined in the FFPS; and

2) Support services defined in SOW Paragraph C.4.2.

The Contractor must provide the services and perform the efforts described in this SOW within the timeframes specified in Section F of this contract or as otherwise specified at the time of order. The Contractor is responsible for providing all items necessary to meet the requirements of this contract except for those items identified as Government-furnished in Paragraph C.3.1.

Communications Services, Functions, and Capabilities As ordered by the Government, the Contractor must provide communications services, functions, and capabilities in accordance with the corresponding requirements defined in the FFPS (Attachment J-1). Communications services, functions, and capabilities are divided into three categories:

1) Communications Services (FFPS Section 4);

2) Enterprise-Level Functions (FFPS Sections 5 and 8); and

3) User Portal Functions (FFPS Section 6).

Communications Services are further divided in two subcategories:

1) Network Services (FFPS Section 4.1); and

2) Information Management Services (FFPS Section 4.2).

Separately-orderable communications services, functions, and capabilities within each category are identified in the respective sections of the FFPS (Attachment J-1). As stated in Section B of the contract, communications services, functions, and capabilities will be ordered on an indefinite delivery, indefinite quantity (IDIQ) basis.

The Contractor must provide all of the Communications Services, Enterprise-level Functions, and capabilities identified in the FFPS as part of a Managed Service Framework as defined in Paragraph C.1.2. Under a Managed Service Framework, in which the Contractor is responsible for the end-to-end performance of the services, functions, and capabilities and must perform all of the associated support service functions defined in SOW Paragraph C.4.2, as applicable.

Telecommunications Access Diversity At Single Entrance Facilities with AV-1, AV-2, AV-3 services as defined in FFPS Section 1.2 or other FENS Service Delivery Locations at the Government’s discretion, the Government may request a proposal from the Contractor for the implementation of an additional telecommunications access that is diverse from the existing telecommunications access. If the proposal is accepted, as ordered via task order, the Contractor must engineer and provide diversity for the services identified in scope of the task order in accordance with FFPS Section 3.1.5. If the proposal is not accepted, the Contractor must implement Electrical Diversity over the segments where physical diversity does not exist.

When the Government has opted not to establish diversity at a service delivery location and an AV-1, AV-2, AV-3 service incurs an outage as a result of a failure along the non-diverse portion of the service implementation, the Contractor may submit, on a per outage basis, a Request for Variance (RFV) to the applicable performance requirements and SLA terms and conditions.

Avoidance At Single Entrance Facilities with an Avoided Service Pair as defined in FFPS Section 1.2, the Government may request a proposal from the Contractor for the implementation of an additional telecommunications access that is diverse from the existing telecommunications access. If the proposal is accepted, as ordered via task order, the Contractor must engineer and provide avoidance for the services identified in scope of the task order in accordance with FFPS Section 3.1.5. If the proposal is not accepted, the Contractor must implement Electrical Diversity for avoided service pairs over the segments where physical diversity does not exist.

When the Government has opted not to establish diversity at a service delivery location and an Avoided Service Pair incurs a simultaneous outage as a result of a failure along the non-diverse portion of the service implementations, the Contractor may submit, on a per outage basis, a RFV to the applicable performance requirements and SLA terms and conditions.

Special Construction As ordered via task order, the Contractor must engineer and implement a telecommunications access solution to a Government-specified FENS service delivery location. Special construction of a new telecommunications access solution may be required when: (1) there is no existing commercial telecommunications access; or (2) commercial telecommunications access exists, but it lacks the capacity or the ability to support FENS service requirements.

Emergency Communications Capability When ordered by the Government, the Contractor must implement and operate an Emergency Communications Capability in accordance with the specifications defined in FFPS Section 5.6 to support the establishment of communications services comprising the CSNC and the ESNC (as applicable). The Emergency Communications Capability may be required to support temporary operational needs including but not limited to when commercial telecommunications infrastructure is lost due to an unpredictable event such as a natural disaster. The Contractor must deploy and operate the Emergency Communications Capability at up to one FAA control site and up to two FAA remote sites concurrently as specified at the time of the order. The Contractor must deploy the Emergency Communications Capability and have it ready for operation within 48 hours of the Government’s order.

The Emergency Communications Capability must include the required Customer Premise Equipment (CPE), as defined in FFPS Section 1.2, and provide a communications transmission capability that interfaces with FENS network infrastructure in order to establish communications connectivity with FENS users at other network locations.

If commercial power is unavailable at a location where the Emergency Communications Capability is being deployed and the Government is unable to provide a back-up power source, the Contractor must provide a power source for the Emergency Communications Capability when separately ordered by the Government. Costs to deploy the Emergency Communications Capability will be recoverable on a task order basis.

Broadband Wireless Communications Capability As ordered by the Government, the Contractor must provide a Broadband Wireless Communications Capability that meets the specifications defined in FFPS Section 5.7.

Site Reconstitution The Contractor must support the reconstitution of any FENS Service Delivery Location within 28 days of a Catastrophic Event as defined in FFPS Section 1.2. A Service Delivery Location is considered to be reconstituted after a Catastrophic Event when all Networking Capabilities, Enterprise-level Functions, Communications Services, and other FENS-provided capabilities previously in operation at the site prior to the Catastrophic Event have successfully completed Site and Service Acceptance Testing.

If additional cost recovery is needed and justified for the actual Site Reconstitution process following a Catastrophic Event, a task order will be established for non-CLIN based efforts per the magnitude of the impact to the specific site.

As part of the Site Reconstitution, the Contractor may also be requested by the Government to provide Service Cutover Support per SOW Paragraph C.4.2.9 in order to restore the affected facilities to operation.

The requirements in this paragraph apply to the reconstitution of a single Service Delivery Location at any point in time.

Support Services This section of the SOW identifies services that must be provided by the Contractor in support of Contractor-provided communications services, functions, and capabilities as defined in SOW Paragraph C.4.1. Depending on the service, the Government may order Support Services by task order or by Contract Line Item Number (CLIN), as applicable. If a Support Service is not orderable on a task order or CLIN basis, then it is not separately priced (NSP) and must be provided as part of other services or enterprise-level functions ordered under this contract.

General Unless specified otherwise, the Contractor must comply with the following order and standards when performing work at FENS Service Delivery Locations:

· FAA Order 3900.19C, FAA Occupational Safety and Health Program;

· 29 Code of Federal Regulations (CFR) Part 1960, Basic Program Elements for Federal Employees Occupational Safety and Health Programs and Related Matters;

· FAA Order JO 3900.57A, EOSH Requirements in the Planning and Execution of Construction and Maintenance Activities at NAS Facilities;

· FAA Order JO 3900.64, Air Traffic Organization Electrical Safety Program;

· National Fire Protection Association (NFPA) 70E, Standard for Electrical Safety in the Workplace;

· NFPA 101, Life Safety Code; and

· Asbestos abatement and control requirements in accordance with 29 CFR 1910.1001, Asbestos.

Program Management The Contractor must establish and maintain a program management organization to manage all Contractor resources, personnel, subcontractors, and activities involved in the delivery of the services ordered under this contract.

The Contractor must designate a full-time Program Manager (PM), dedicated to the FENS program, who has overall responsibility for the services provided under this contract and who serves as the Contractor’s focal point for interactions with the Government Program Office for the contract. The Contractor must also designate a Deputy PM to fulfill the duties of the PM when the PM is unavailable. The Contractor’s PM and Deputy PM must possess the skills and meet the requirements for the PM position defined in Section H.2. As requested by the Government, the Contractor must designate additional focal points to serve as the primary interface for the Government Functional Leads for the FENS program in Government-designated key areas. The Contractor-designated focal points must respond to Government requests for technical information and collaborate with their Government-designated counterparts on the planning and execution of required work efforts in their respective functional areas.

The Contractor must prepare and submit a Program Management Plan (PMP) (Contract Deliverable Requirements List (CDRL) F001-PMP) describing its approach to managing the services required under the FENS contract.

The Contractor must report on the program status and other items of interest to the Government Program Manager and Functional Leads in the Monthly Status Report (CDRL F002-MSR).

In addition to formal quarterly Program Management Reviews required in SOW Paragraph C.4.2.2.6.1, the Contractor must respond to ad hoc requests from the Government for status information regarding specific projects. Status requests will occur throughout the contract period of performance and will likely occur more frequently during the period immediately following contract award through the Government’s In-Service Decision (ISD) milestone and continuing through completion of all transition-related activities. Coordination between the Government and the Contractor may include, but is not necessarily limited to daily phone calls and e-mail requests, weekly working group meetings, and other forms of interaction as needed.

Supply Chain Management The Contractor must implement a Supply Chain Management Function to ensure that all services, equipment, components, and other supplies used to meet the requirements of the FENS contract are available as needed. The Contractor must describe its Supply Chain Management processes and procedures in the PMP (CDRL F001-PMP). The Contractor must perform Supply Chain Management in accordance with the Government-approved PMP to ensure the integrity of the FENS supply chain and prevent disruption to the FENS supply chain.

The Contractor must describe its approach for identifying, assessing, selecting, and implementing risk management and mitigating controls throughout the organization to manage Information and Communications Technology (ICT) supply chain risks in the Supply Chain Risk Management Plan (CDRL F003-SCRM). The Contractor must perform supply chain risk management in accordance with the Government-approved Supply Chain Risk Management Plan (CDRL F003-SCRM).

Quality Control / Quality Assurance The Contractor’s Program Management organization must include a Quality Control / Quality Assurance (QC/QA) function that is responsible for assessing and maintaining the quality of services and products provided under this contract. The Contractor’s QC/QA function must be compliant with:

· The inspection requirements defined in Section E of this contract (Inspection and Acceptance);

· AS9100, Quality Management Systems – Requirements for Aviation, Space and Defense Organizations, Rev. D;

· FAA-STD-013D, Quality Control Program Requirements; and

· FAA-STD-016A, Quality Control System Requirements.

The Contractor must implement and maintain QC/QA systems and processes that comply with the Government-approved Quality System Plan (QSP) contained within the PMP (CDRL F001-PMP). The Contractor must take corrective action when deficiencies are identified.

All QC/QA functions performed by the Contractor are subject to Government verification at any time. Verification may consist of, but is not be limited to:

a. Surveillance of the operations to determine that practices, methods and procedures of the QC/QA program are being properly applied; and

b. Government inspection to measure quality of the services offered for acceptance.

The Contractor must conduct periodic audits of its QC/QA functions in accordance with the Government-approved QSP. The Contractor must document and maintain the results of their audits and recommended corrective actions associated with each quality evaluation performed. The evaluations must be maintained by the Contractor's QC/QA organization, and made available for the Government upon request.

The absence of Government witnessing tests or conducting inspections does not relieve the Contractor of the responsibility of ensuring that all services submitted to the Government for acceptance comply with all requirements of the contract.

Configuration Management The Contractor must implement a Configuration Management (CM) function that encompasses the processes for identifying, controlling, and maintaining the physical and logical configuration of FENS Communications Services. The Contractor’s CM function must be conducted in accordance with FAA Order 1800.66, Configuration Management Policy. The Contractor must describe its approach to CM in the PMP (CDRL F001-PMP).

The Contractor must obtain the approval of the Government-chaired FENS Configuration Control Board (CCB) for any changes to contract requirements or Requests for Variance (RFVs). The Contractor must submit a CCB item through the FAA User Portal (per FFPS Section 6.1.1.2) when seeking a change to contract requirements. The Government may also initiate changes to the contract requirements through a CCB item. In addition, the Contractor must submit an RFV through the FAA User Portal (per FFPS Section 6.1.1.2) for approval of temporary and selected exceptions to contract requirements. The Contractor must identify the associated rationale for the change and the associated cost, schedule, and performance impacts of the proposed RFVs and CCB items. The Government will inform the Contractor as to whether RFVs and CCB items are approved or disapproved. The Contractor must only implement solutions that conform to the contract requirements baseline inclusive of approved RFVs and CCB items when informed by the CO in writing.

Risk, Issues, and Opportunities (RIO) Management The Contractor must implement a Risk, Issue, and Opportunity (RIO) management function that supports the FAA RIO management process as defined in the FAA’s Program Management Organization (PMO) RIO Management Plan (RMP), PMO-PLN-0002. The Contractor must support the FENS program office’s RIO management process by participating in monthly joint FAA/Contractor RIO meetings as requested. The Contractor must report on medium and high RIO items including the status of the associated mitigation plans during Program Management Reviews (PMRs) and within the Monthly Status Report (CDRL F002-MSR). The Contractor must describe its approach to performing the RIO management function in the PMP (CDRL F001-PMP).

Program Control and Status Reporting The Contractor must track the performance of all services provided under this contract relative to cost, schedule, and technical performance. The Contractor must assess the progress of ongoing activities, identify problems encountered or foreseen, update the program schedule and risks as needed, and provide the Government with the status of any open action items assigned to the Contractor. In addition to the formal monthly reporting cycle, the Contractor must provide the Government with timely assessments of program progress and ongoing issues associated with high priority activities.

The Contractor must respond to informal requests from Government POCs via e-mail or verbally, as applicable, regarding the status of Contractor-provided services and any issues affecting the delivery of services ordered under this contract.

Earned Value Management The Contractor must implement and utilize an Earned Value Management System (EVMS) that complies with the ANSI/EIA-748 standard for Earned Value Management Systems from contract award through the expenditure of all FENS program Facilities and Equipment (F&E) funding. The Contractor must use its EVMS to plan, integrate, and control project scope, schedule, costs, resources, to measure performance, and to identify cost and schedule variances. The Contractor must provide EVMS database reporting in a monthly Integrated Program Management Report (CDRL F004-IPMR) to assist the FAA’s efforts to validate Contractor cost and schedule status information. The Contractor’s EVMS reporting must contain information sufficient to predict early indications of cost and schedule problems, and their relationship to any technical progress affected.

Contract Work Breakdown Structure The Contractor must develop and submit a Contract Work Breakdown Structure (CWBS) as part of the PMP (CDRL F001-PMP). The Contractor must provide a mapping of the CWBS to the FAA Work Breakdown Structure (WBS). The Contractor must use the CWBS as the primary framework for planning, budgeting, managing, tracking, and reporting of program cost and schedule status to the Government of all Contractor-performed work efforts. The Contractor must maintain the CWBS throughout the required Earned Value Management (EVM) reporting period as defined in Paragraph C.4.2.2.5.1. Once approved by the Government, the Contractor must not modify the CWBS or associated definitions for any reporting elements identified in the CWBS without the written approval of the FENS CO.

Integrated Master Schedule The Contractor must develop and maintain an Integrated Master Schedule to plan, manage, and control all program activities throughout the required EVM reporting period as defined in Paragraph C.4.2.2.5.1. The Integrated Master Schedule must identify all contract deliverables identified in Attachment J-2 and critical milestones (including applicable support activities) to meet program activities as defined in this SOW and Section F. The Contractor must deliver the Integrated Master Schedule under CDRL F005-IMS and ensure that it aligns with the corresponding delivery of the Integrated Program Management Report (CDRL F004-IPMR).

Integrated Baseline Review The Contractor must participate in a joint Government/Contractor Integrated Baseline Review (IBR) for the purpose of reviewing the Contractor's planned efforts to meet contractual requirements in areas including, but not limited to, complete coverage of the SOW, logical scheduling of work activities, adequate allocation of resources, and risk management. The Contractor must refer to the National Defense Industrial Association (NDIA) IBR Guide for guidance in the preparation and conduct of an IBR. The Contractor must coordinate the scheduling of the initial IBR with the Government so that it occurs no later than 120 calendar days after contract award. The Government may require the Contractor to support additional IBRs within 120 calendar day after the exercise of contract options or major modifications to the contract.

Meetings, Reviews, and Working Groups As a part of its program management responsibilities, the Contractor must plan, support, and participate in FENS-related meetings, reviews, and working groups as described in the following subparagraphs.

Program Management Reviews The Contractor must support the Government’s conduct of quarterly PMRs that address the following on a contract-wide basis:

· the Contractor’s accomplishments since the previous review;

· the Contractor’s plans for the next 90 days;

· quarterly and year-to-date metrics summarizing the support services provided;

· EVMS and Integrated Master Schedule status including identification of major drivers behind schedule variances and the action plans to resolve any variances, if applicable;

· review of all open actions from previous PMRs and actions closed since the most recent PMR;

· any risks, issues and concerns that should be brought to the Government’s attention; and

· recommended actions to mitigate any risks, issues and concerns that are identified.

The Contractor must submit PMR Presentation Materials (CDRL F006-PMR) to the Government at least seven calendar days prior to the scheduled start of the review. PMRs may be held at a Government facility or a Contractor facility as determined by the Government on a case-by-case basis.

Working Groups As requested by the Government, the Contractor must participate in working groups that are established to focus on a particular functional area (e.g., Program Management, Contract Administration, Transition, Network Engineering, Operations, or Security Management) within the scope of the FENS contract. Working groups will meet on a regularly scheduled basis as needed to support the objectives of the working group. The Contractor must assign a focal point to serve as a counterpart to the Government-designated lead for each working group. The Contractor’s responsibilities relative to participation in working groups include the requirements identified in SOW Paragraph C.4.2.2.6.3 for Technical Interchange Meetings (TIMs) and other meetings.

Technical Interchange Meetings (TIMs) and Other Meetings As requested by the Government, the Contractor must attend and participate in technical, contractual, and programmatic meetings to address specific issues. The Government will indicate whether the meeting will be held at a Government facility or a Contractor facility. In addition, the Government will indicate whether Contractor participation must be in-person or whether it may be via teleconference depending on the nature of the meeting. The personnel representing the Contractor must have the requisite knowledge, skills, experience to discuss the topics identified on the meeting agenda. As requested by the Government, the Contractor must coordinate the scheduling of meetings with required participants, issue calendar invitations, and prepare agendas, presentation materials, meeting minutes, and action item lists to support the conduct of the meetings.

If the Contractor holds service improvement meetings or other meetings of similar scope with its major suppliers, the Contractor must allow Government points of contact to participate in the portions of the meetings related to FENS services.

Secure Repository for Contractual Documentation The Contractor must provide a secure repository for contractual documentation within the FAA User Portal as defined in FFPS Section 6.1.1. The Contractor must only grant access to the security repository to those individuals approved by the CO or COR.

The Contractor must retain contractual documentation per FAA and NARA records retention requirements. The FAA’s official contract file will be maintained by the Government separate from the Contractor-provided repository.

Solution Development The Contractor must perform the solution development activities described in the following subparagraphs to support: (1) the FAA’s achievement of the ISD milestone for the FENS program, implementation of FENS network infrastructure, and the transition of services to FENS; and (2) the introduction of new service offerings and capabilities (relative to the existing set of service offerings and capabilities defined in the FFPS) into one or more FENS Networking Capabilities.

Requirements Reviews For the scope of activities described in SOW Paragraph C.4.2.3 ranging from enterprise-wide establishment of the FENS network to the introduction of additional capabilities during steady state operations, the Contractor must support the Government’s conduct of Requirements Reviews to demonstrate the Contractor’s understanding of the requirements applicable to the scope of the effort. Each Requirements Review must address:

a) All applicable requirements and the Contractor’s understanding of those requirements;

b) Any derived requirements;

c) Design-driving/cost-driving requirements;

d) Scope of the FENS architecture impacted by the new requirements including the Operational Support System (OSS), as defined in FFPS Section 1.2, and the associated User Portal functions, as defined in FFPS Section 6;

e) Processes and resources required to support the solution development including any hardware and software development required to meet the requirements;

f) Implications to Safety Risk Management;

g) Potential implementation and transition challenges; and

h) Potential impacts to:

i. the Reliability, Maintainability, and Availability (RMA) and failure modes of the affected services and capabilities;

ii. the information system security of the affected Networking Capabilities;

iii. the configuration of the Contractor’s Service Verification Lab and the FENS Network Testbed (NTB); and

iv. existing contract deliverables.

The Contractor must provide Requirements Review materials at least seven (7) calendar days prior to the scheduled start of the review. Successful completion of all required elements of the Requirements Review and closure of any resulting actions items assigned to the Contractor are required in order to proceed with the solution design.

In the event the FAA introduces a new capability into a…