ACMS Draft Statement of Work (SOW)-10-21-2021.pdf

Federal Aviation Administration

AJW Configuration Management Support

(ACMS)

Statement of Work

(SOW)

DRAFT

October 21, 2021

AJW Configuration Management Support (ACMS) Statement of Work i

Table of Contents 1 Introduction

1.1 Background

1.2 Objectives

1.3 Scope of Work

1.4 Inherently Governmental Functions

2 References

3 Support Requirements

3.1 Configuration Management

Configuration Management Plans and Procedures Configuration Management Processes and Standards Configuration Identification and Documentation Configuration Control Configuration Status Accounting Configuration Verification and Audits System/Product/Service Disposition

3.2 Contract Program Management

Contract Management Meeting Attendance Monthly Status Reports Program Management Reviews (PMRs) Task Order Management Transition-In / Transition-Out Requirements

4 End Results/Deliverables

5 Period of Performance

6 Place of Performance

7 Hours of Operation

8 Travel and Other Direct Costs (ODCs)

Appendix A: Acronyms and Abbreviations.............................................................................................. A-1

C-1

1 Introduction This Statement of Work (SOW) describes the requirements for the AJW Configuration Management Support (ACMS) contract. ACMS is an Indefinite Delivery, Indefinite Quantity (IDIQ) contract for configuration management services to support the FAA Technical Operations (AJW) organization’s mission. Each Task Order (TO) established under the ACMS contract will have an associated statement of work (SOW) and will identify project-specific requirements such as programs to be supported, the place of performance, deliverables, and other pertinent information.

1.1 Background

AJW is part of the FAA’s Air Traffic Organization (ATO). AJW’s mission is to ensure a safe and efficient National Airspace System (NAS) through the effective management of air navigation services and infrastructure. The scope of AJW’s mission includes the integration, management, operation, maintenance, and modernization of the systems and services that comprise the NAS.

The following three AJW directorates are anticipated to be the primary users of services provided under the ACMS contract:

• Operations Support, AJW-1 – responsible for providing the support structure, methodology, tools, procedures, performance monitoring, and assurance necessary for the proper operation and maintenance of the NAS.

• Air Traffic Control (ATC) Facilities/Engineering Support, AJW-2 – responsible for the safe and effective lifecycle management of the facilities infrastructure of the National Airspace System (NAS).

• NAS Security and Enterprise Operations (NASEO), AJW-B – responsible for providing operational and cybersecurity management of NAS services.

1.2 Objectives

The primary objective of the ACMS contract is to obtain configuration management services to support the fulfillment of AJW’s mission. With the ACMS contract, AJW is seeking to integrate the support provided to improve efficiency, communications, and collaboration – both across the contractor support staff and relative to their interaction with AJW. ACMS is intended to provide a contract that:

• Is focused on AJW’s mission;

• Facilitates a uniform contracting approach to support AJW and the programs, systems, and services that it manages; and

• Meets the changing needs of AJW across the period of performance as the NAS operating environment evolves.

1.3 Scope of Work

The scope of TOs established under the ACMS contract may include configuration management support to any program, system, or service managed by AJW. Specific requirements within the scope of these functional work areas will be identified, defined, and issued under individually funded TOs.

1.4 Inherently Governmental Functions

In its performance of the ACMS contract, the Contractor must not perform any inherently governmental functions, as identified in the Office of Federal Procurement Policy Letter 11-01.

Inherently governmental functions are those that are so intimately related to the public interest as to require performance by Federal Government employees. The term includes functions that require either the exercise of discretion in applying Federal Government authority or the making of value judgments in making decisions for the Government. This would include, among other things, binding the Government to take or not to take some action by contract, policy, regulation, authorization, order, or otherwise, and exerting ultimate control over the acquisition, use, or disposition of the property of the United States, including the collection, control, or disbursement of appropriations and other Federal funds.

2 References The Contractor must adhere to all applicable FAA Orders. The Contractor must research and employ appropriate FAA Orders, where necessary, under the guidance of the Contracting Officer’s Representative (COR) regarding existing materials and specifications for Government systems. Other business and financial systems must be used.

The Contractor must ensure all work is in full compliance with:

• FAA orders, standards and guidelines

• ATO orders, standards and guidelines

Websites where additional supporting information is available are listed below:

• Orders and Notices:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTo picID/184

• Forms:

http://www.faa.gov/library/forms/

• Acronyms and Abbreviations:

https://www.faa.gov/jobs/abbreviations/

• Contractor & Industrial Security Program:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/ documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/library/forms/ http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573

3 Support Requirements This section identifies the range of support that must be provided by the Contractor when identified within a TO established under the ACMS contract. Additional requirements and details, including but not limited to written deliverables and/or place and period of performance, may be specified in individual TOs, as applicable. The Contractor must provide the full range of support capabilities defined in the TOs issued under this contract.

In the performance of TOs established under the ACMS contract, Contractor personnel may be required to possess in-depth knowledge of the FAA operating environment including, but not necessarily limited, to FAA Financial Management systems, FAA/ATO orders, policies, and standard operating procedures.

The Contractor must furnish the necessary personnel, materials, equipment, and facilities required to satisfy the requirements of the individual TOs.

3.1 Configuration Management

The Contractor must provide configuration management (CM) support for systems, products, and services that are currently in operation within the NAS or are planned for implementation in the NAS. The Contractor must support all aspects of FAA CM involving establishment, monitoring, and administration of change control procedures, collecting, processing, distributing and tracking modification request forms of hardware, software, facilities, data, interfaces, tools, and documentation. The following subparagraphs identify CM requirements across the AMS life cycle for AJW-managed systems, products, and services.

Configuration Management Plans and Procedures

The Contractor must develop and maintain CM plans and standard operating procedures for the CM of AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Ensure CM plans and procedures for AJW-managed systems, products, and services are consistent with applicable FAA policies;

• Develop and maintain technical documentation needed to the support the CM of AJW-managed systems, products, and services;

• Review existing CM plans and CM programs for AJW-managed systems, products, and services; and

• Prepare reports for AJW management on significant CM events.

Configuration Management Processes and Standards

The Contractor must develop and implement CM processes and standards for AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Support development of requirements for engineering documentation, change orders, and releases in accordance with established FAA CM policies and standard operating procedures;

• Review and monitor the implementation of system/product/service acceptance plans;

• Implement FAA configuration management standards, configuration management plans, and procedures for AJW-managed systems, products, and services;

• Implement and maintain standard operating procedures for processing change proposals for AJW-managed systems, products, and services;

• Coordinate with regional, service area and service center communications, infrastructure, and network CM personnel and Headquarters program offices to assist in the resolution of any facility baseline issues associated with AJW-managed systems, products, and services;

• Evaluate and provide recommendations on configuration management tools; and

• Recommend changes to standard operating procedures as automation is introduced into CM processes.

Configuration Identification and Documentation

The Contractor must identify and document the CM baseline for AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Assist AJW program offices with developing the configuration structure of its systems, products, services;

• Assist AJW program offices with: (1) developing configuration documentation, and (2) assigning identifiers to the documentation and to any electronic media on which the documentation is recorded;

• Ensure that all CM documentation is in compliance with the latest NAS CM policy guidance;

• Assist AJW program offices with providing required information to the Operations Planning, NAS Configuration Management Branch; and

• Assist with the determination of which documents constitute the operational baseline AJW-managed systems, products, and services.

Configuration Control

The Contractor must support the configuration control of AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Support Configuration Control Board (CCB) activities including, but not limited to:

o Plan, schedule, and coordinate CCB meetings as directed by the CCB chairperson(s), o Develop and distribute CCB agendas, o Record and distribute minutes of CCB meetings, o Develop, distribute, and maintain status of CCB decisions, o Establish and maintain liaison with other CCBs, o Maintain and publish status information and efficiency measures of CCB activities, o Log case file for each proposed change into the FAA Document Control (DOCCON) Library, o Coordinate the assignment of a NAS Change Proposal (NCP) number for each case file and log it into DOCCON, o Distribute each NCP via e-mail to all CCB members, o Prepare Configuration Control Documents (CCDs) for each NCP and obtain the CCB Chairperson(s)’s signatures, and o Log signed CCDs into DOCCON;

• Assist with the development and coordination of NAS change proposals;

• Provide administrative and technical support to AJW program offices in resolving comments received on its NAS change proposals;

• Support AJW program offices in completing actions assigned by the CCB in the configuration control decision document;

• Assist AJW program offices with the implementation of configuration control decisions;

• Assist AJW program offices with maintaining the documentation that constitutes the operational baseline;

• Maintain and add new material to the CM libraries for AJW-managed systems, products, and services;

• Implement and maintain a screening process in accordance with CM standard operating procedures to ensure NAS Change Proposals do not have operational impacts on AJW-managed systems, products, and services;

• Participate in NAS Configuration Control Board (CCB) activities and ensure that configuration management impacts to AJW-managed systems, products, and services are identified;

• Maintain versioning of all artifacts including but not limited to requirements documentation, design documentation, test cases, test report, release notes, and project plans;

• Assist AJW program offices in evaluating the quality of prime contractor change control processes and how well the contractor’s change control processes map to the requirements of the associated contract;

• Assist AJW program offices in reviewing and processing engineering change proposals submitted by prime contractors;

• Develop and assist with the processing of NAS Program Initiatives (NPIs);

• Develop and assist with the processing of Baseline Management Notices (BMNs);

• Establish and maintain the CM Program Support Library (PSL) for individual AJW-managed systems, products, and services;

• Assist AJW program offices with CM data control and maintenance; and

• Implement a CM status accounting system that accounts for all engineering product and service documents and authorized changes to product and service documentation.

Configuration Status Accounting

The Contractor must support the configuration status accounting of AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Assist AJW program offices with recording the status of configuration documentation and tracking revisions to the documentation;

• Assist AJW program offices with determining whether prime contractors have a documented configuration status accounting processes;

• Assist AJW program offices in determining whether prime contractors are collecting applicable CM information and whether that information is available for display or retrieval in a timely manner; and

• Assist AJW program offices in determining whether information collected by prime contractors is consistent with the information needed by the program offices.

Configuration Verification and Audits

The Contractor must support the configuration verification and audits of AJW-managed systems, products, and services. Specific tasks may include, but are not limited to:

• Assist AJW program office with the planning, scheduling, and conduct of system/product/ service configuration audits;

• Support AJW program offices in reviewing documented audit results and verifying the disposition of audit findings;

• Conduct verifications and audits on operational equipment in coordination with regional, service area, and service center personnel;

• Establish new baselines, if required, based on the results of configuration audits; and

• As applicable, verify that the operational equipment has been restored to its original configuration.

System/Product/Service Disposition

The Contractor must assist AJW program offices with the preparation of NCPs required to decommission/discontinue AJW-managed systems, products, and services.

3.2 Contract Program Management

This section describes work efforts that must be performed by the Contractor as part of the management and administration of the ACMS contract.

Contract Management

The Contractor must efficiently and accurately manage this contract to ensure compliance with all technical, business, and management (e.g., cost, schedule, and deliverable) requirements of this SOW. The Contractor must designate a Program Manager and other primary points of contact for work to be performed under this Statement of Work and individual task orders issued under the ACMS contract. In support of the management of the ACMS contract, the Contractor must perform the following efforts, at a minimum:

• Provide program management support to ensure that identified tasks are performed efficiently, accurately, on time, and in compliance with the requirements;

• Conduct sufficient oversight and supervision of the contract and its employees in order to ensure both are functioning within designated labor categories and performing at acceptable levels;

• Ensure all assignments are completed in a thorough and timely manner;

• Prepare detailed written documentation of accomplishments as stipulated in the monthly report submission;

• Inform the Contracting Officer (CO) and COR of any potential problems and make recommendations for solutions;

• Participate as a member of a government-led team as required by the CO or COR; and

• Provide sufficient personnel, both in number and qualification, to successfully perform work described herein.

Key Personnel

The Program Manager is defined as “Key Personnel” under the ACMS contract. Key Personnel may only be replaced with the approval of the FAA CO, in accordance with AMS Clause 3.8.2-22.

Proposed Key Personnel must be available to work on the ACMS contract and serve in the assigned role for at least six months from their start of performance on the contract.

The following are the required responsibilities of the ACMS Program Manager:

• ACMS Program Manager – The Contractor’s primary focal point for the ACMS contract.

Has overall responsibility for the execution of the contract including questions regarding any of the task orders and their sub-activities. The Program Manager interfaces with the Government management points-of-contact for the contract.

Meeting Attendance

The Contractor must attend and/or participate in meetings at locations identified in Paragraph 6 of this SOW and other locations as may be requested by the Government.

Monthly Status Reports

The Contractor must provide Monthly Status Reports (MSRs). The MSRs must document task order accomplishments and demonstrate value-added activities of the previous month and identify future planned activities. The reports must be delivered to the COR and contain three parts: a narrative of accomplishments, a cost summary, and a personnel listing by Task Order. MSRs must include the following monthly information by Task Order, at a minimum:

• Narrative overview of work completed, work in progress, and work planned for each task by personnel;

• Status of all task deliverables;

• Identification of risk areas with recommended remedial actions;

• Status of all outstanding risks identified in previous MSRs;

• Labor/CLINs used during month by cost and hours funded and expended;

• Projected date when 75% of funds will be expended by task;

• Projected date when funds will be 100% expended by task;

• Funds and hours remaining by labor/CLINs;

• Other direct costs (ODCs) estimated, used, and remaining by month;

• Summary of expenditures by task by resource and CLIN, both for the monthly reporting period as well as cumulative year-to-date totals, for the performance period;

• Personnel listing by task, start and end dates, on or off Government site status, and primary and secondary phone number; and

• Any additional information pertinent to the FAA in administering the performance of tasks or as required by the COR.

Program Management Reviews (PMRs)

The Contractor must conduct quarterly PMRs. The PMRs must be conducted on dates and locations acceptable to the government, and on a consistent schedule, and will generally be held at, or in the general vicinity of, the FAA headquarters location in Washington, DC. The PMRs must include review of documentation submitted in draft to the COR no less than two (2) business days before the PMR. The PMR and documentation must address the following information:

Schedule by Task Order and Project

• Schedule status and progress against all tasks

• Schedule variance and recommended corrective actions

• Issues requiring schedules of events and deliverables

Cost by Task Order and Project

• Current and cumulative costs traceable to the SOW tasks

• Variance from projected costs

• Cost projections for each task

Performance by Task Order and Project

• Achievements against milestones

• Performance and quality issues

• Significant risks

• Communication/Personnel issues

Task Order Management

The Contractor must designate a Project Lead to provide the appropriate program management and project control necessary to manage each task order issued under this contract, so that task order cost, schedule and quality requirements are continually tracked, status is appropriately communicated to the FAA, and the task order is performed successfully. The Contractor must separately track the individual task orders.

Transition-In/Transition-Out Requirements

The following subsections identify required actions on the part of the Contractor upon contract start-up (i.e., Transition-In) and upon contract close-out (i.e., Transition-Out).

3.2.6.1 Transition-In Requirements

The Contractor must ensure all staff have completed their DOT personnel security requirement(s) (SF-85P) and have received all necessary approvals prior to starting work on the contract. The Contractor shall be fully staffed and operational within 60 days of the effective date of contract award, barring any delays or issues that are beyond the control of the Contractor. At a minimum, the Contractor must accomplish the following transition-in activities with the incumbent Contractor and/or the Government as applicable:

• Assume full responsibility for providing the support services required under newly issued task orders;

• Assume version control of historic data, documentation, processes, and training as applicable;

• Assume user and system administration responsibilities for all systems and tools;

• Obtain facility and network access (keys, cards, security codes/PINs) and required training;

and

• Conduct introduction/orientation activities as required to meet the requirement of task orders issued under this contract.

During the first 120 calendar days of contract performance, the Contractor must conduct, as directed by the CO or COR, Weekly Transition Status Meetings to provide active and planned status on all Transition-In activities.

3.2.6.2 Transition-Out Requirements

No less than 30 calendar days prior to the contract end date, the Contractor must:

• Provide the most recent version of all documentation for which the contractor is responsible to manage or maintain version control;

• Provide a final financial summary report that is cumulative across the full contract period of performance;

• Provide a final status report that includes a projection of activities for the remainder of the Task Order;

• Conduct a close-out meeting with the FAA (details and participants to be determined by the FAA); and

• Turn in all FAA-issued PIV cards to the COR no later than the final day of the period of performance under the last Task Order.

4 End Results/Deliverables This section describes the products and tangible end results that are expected from the activities contained in 1) Section 3; 2) the date each deliverable is due; and 3) the government acceptance criteria.

All days are business days unless otherwise specified.

SOW

Para. # End Result / Deliverable Due Date Acceptance Criteria

3.4.3 Monthly Status Reports (MSRs) 10th day of

the month, reporting on the previous month

The MSRs are accurate, complete, submitted on time in conjunction with invoice submission and in accordance with (IAW) SOW Section 3

3.4.4 Program Management Reviews

(PMRs)

Quarterly The PMRs are accurate, complete, and submitted on time and prepared IAW SOW Section 3

Additional deliverable requirements may be identified in individual task orders.

5 Period of Performance The period of performance of the ACMS contract will be five years.

6 Place of Performance The place of performance for this contract will be at both the Contractor facilities and the Government facilities at, but not limited to, FAA Headquarters in Washington, DC; FAA Air Traffic Control System Command Center (ATCSCC); William J Hughes Technical Center (WJHTC); Mike Monroney Aeronautical Center (MMAC); FAA Service Centers; Network Operations Control Centers and Security Operations Control Centers operated by FAA service providers; and NAS Operational facilities throughout the continental United States such as the NEMCs in Hampton, Georgia and Salt Lake City, Utah.

7 Hours of Operation General hours of operation this contract will be 8:00am to 5:00pm local time. The “hours of operation” correspond to the timeframe within a work week for the Contractor must provide the required support. Any task order-specific hours of operation will be identified in the task order as applicable. Alternate work schedules or telework, or both, must be approved in advance by the Contracting Officer, with agreement from the COR. Furthermore, any requests to the Contracting Officer for Contractor employee telework, either intermittent or regularly scheduled, may only be requested if the Contractor Company has a Telework policy and their employee has met the requirements and been approved thereunder.

When FAA offices close, contractor employees may work in their local offices, telework if previously approved by the Contracting Officer, or be granted access to Government buildings, if appropriate, as directed by the FAA.

8 Travel and Other Direct Costs (ODCs) Travel may be required and ODCs may be incurred as part of the performance of individual Task Orders. Travel may include trips to FAA field locations to support work performed on specific contract tasks. ODCs are costs charged directly to the contract that have not been included in proposed material, direct labor, indirect costs, or any other category of costs. Examples of ODCs include special tooling, shipping expenses, reproduction costs, royalties, and federal excise taxes. All ODC expenses must be consistent with the costs of comparable items or services. The Contractor must submit requests for authorization to the Government-designated point of contact, and all ODCs and travel must be approved in advance and in writing before any such costs are incurred.

A-1

Appendix A: Acronyms and Abbreviations

3PAO 3rd Party Independent Assessment

A2LA American Association for Laboratory Accreditation

A&A Assessment and Authorization

ACG ATO Cybersecurity Group

AISS AJW Integrated Support Services

AJM Organization Code for the FAA’s Program Management organization

AJW Organization Code for the FAA’s Technical Operations organization

AMS Acquisition Management System

API Application Programming Interface

ARS Advanced Reporting System

ASRB Acquisition Strategy Review Board

ATC Air Traffic Control

ATCSCC Air Traffic Control System Command Center

ATO Air Traffic Organization

BET Budget Execution Tool

BMN Baseline Management Notice

BOMS Back- fill Overtime Management System

ACMS Business, Financial, and Administrative Support

BPR Business Process Reengineering

CAD Computer-Aided Design

CAI Contractor Acceptance Inspection

CCB Configuration Control Boards

CO Contracting Officer

COR Contracting Officer’s Representative

COTS Commercial-off-the-Shelf

DELPHI FAA accounting and financial management system

DoD Department of Defense

DOT Department of Transportation

DT Development Testing

ECP Engineering Change Proposal

EME Electromagnetic Emissions

ESM Enhanced Security Monitoring

EVM Earned Value Management

FAA Federal Aviation Administration

F&E Facilities and Equipment

FedRAMP Federal Risk and Authorization Management Program

FIPS Federal Information Processing Standards

FMS Financial Management System

FSR Financial Status Review

FY Fiscal Year

GFE Government Furnished Equipment

GIS Geographic Information System

HF Human Factors

HQ Headquarters

IDIQ Indefinite Delivery, Indefinite Quantity

IGCE Independent Government Cost Estimates

ILSP Integrated Logistics Support Plan

IOC Initial Operating Capability

IP Internet Protocol

IPSF IP Supplemental Form

IRAT Independent Risk Assessment and Testing

ISCM Information System Continuous Monitoring

ISPD Implementation Strategy and Planning Document

ISR In-Service Review

ISS Information System Security

IT Information Technology

KML Keyhole Mark-up Language

KSN Knowledge Sharing Network

LOB Line of Business

MIBC Major Investment Business Case

MMAC Mike Monroney Aeronautical Center

MSR Monthly Status Report

NAS National Airspace System

NASEO NAS Security and Enterprise Operations

NCO NAS Cyber Operations

NCP NAS Change Proposal

NDI Non-development Item

NEMC National Enterprise Management Center

NOCC Network Operations Control Center

NPI NAS Program Initiative

NIST National Institute Standards and Technology

NOCC National Operations Control Center

NOG National Operations Group

NOM National Operations Manager

OAG Official Airline Guide

ODC Other Direct Cost

O&M Operations and Maintenance

OMB Office of Management and Budget

OPI Office of Primary Interest

OS Operations Support

OT&E Operational Test and Evaluation

PA Project Authorization

PC Personal Computer

PgSA Program Scope Agreements

PIN Personal Identification Number

PIV Personal Identification Verification

PLA Project Level Agreement

PMR Program Management Review

PO Program Office

POA&M Plan of Actions and Milestones

POC Point of Contact

PSP Program Safety Plan

PTR Problem Tracking Report

QA Quality Assurance

QC Quality Control

R&D Research and Development

RBAT Radar Beacon Analysis Tool

RE&D Research, Engineering, and Development

REGIS Regional Information System

ROE Rules of Engagement

RMA Reliability, Maintainability, and Availability

RPD Resource Planning Document

RSS Radar Support System

SAPS Staffing and Payroll System

SCRB Support Contracts Review Board

SDLC Software Development Life Cycle

SIEM Security Information and Event Management

SLE Second Level Engineering

SOA Service Order Agreement

SOP Standard Operating Procedure

SOW Statement of Work

SP Special Publication

SSD System Support Directive

TBD To Be Determined

TO Task Order

TOM Transition to Operations and Maintenance

TTP Tactics, Techniques, and Procedures

WINPLOT Windows Plot

WJHTC William J. Hughes Technical Center