NVR Section C.pdf

693KA8-19-D-00006

Page C-i

SECTION C

STATEMENT OF WORK

TABLE OF CONTENTS

C.1.0 INTRODUCTION

C.1.1 PURPOSE

C.1.2 OVERVIEW

C.1.3 LEGACY VOICE RECORDING EQUIPMENT

C.1.4 OPERATIONAL CONCEPT

C.1.5 NVR SYSTEM DESCRIPTION

C.1.6 NVR SYSTEM REQUIREMENTS

C.1.6.1 General Requirements C.1.6.2 Size and Capacity Requirements

C.2.0 APPLICABLE DOCUMENTS

C.2.1 GOVERNMENT AND MISCELLANEOUS DOCUMENTS

C.2.2 SOURCES OF DOCUMENTS

C.2.3 PRECEDENCE OF DOCUMENTS

C.2.4 TERMINOLOGY

C.3.0 CONTRACTOR TASKS

C.3.1 PROGRAM MANAGEMENT

C.3.1.1 Program Management Plan C.3.1.2 Risk Management C.3.1.3 Contract Work Breakdown Structure (CWBS) C.3.1.4 Integrated Master Schedule

C.3.2 REVIEWS AND TECHNICAL INTERCHANGE MEETINGS (TIMS)

C.3.2.1 Post Contract Award Review (PCAR) C.3.2.2 Program Management Review (PMR) C.3.2.3 Final System Review (FSR) C.3.2.4 Functional Configuration Audit (FCA) C.3.2.5 Physical Configuration Audit (PCA)

C.3.3 MONTHLY STATUS REPORT

C.3.4 SYSTEM

C.3.4.1 System Requirements Allocation Document (SRAD) C.3.4.2 Interface Control Documents C.3.4.3 Engineering Change Proposals (ECPs) C.3.4.4 Routine System Updates

C.3.5 ENVIRONMENTAL AND OCCUPATIONAL SAFETY AND HEALTH (EOSH)

C.3.6 DELIVERY AND INSTALLATION OF NVR OPERATIONAL TEST & EVALUATION (OT&E) EQUIPMENT C.3.6.1 Operational Test & Evaluation (OT&E) System

C.3.6.1.1 Site Spares for OT&E C.3.6.1.2 OT&E System Contractor Services

C.3.6.2 Production Systems

Page C-ii

SECTION C

C.3.7 DELIVERY, INSTALLATION, AND INTEGRATION OF NVR PRODUCTION EQUIPMENT

C.3.7.1 Site Installation Management Plan (SIMP) C.3.7.2 Site Installation

C.3.7.2.1 Adds, Moves, and Changes C.3.7.2.2 Packing, Shipping, Off-Loading, and Placement C.3.7.2.3 Equipment Installation C.3.7.2.4 Tools and Test Equipment C.3.7.2.5 Site Installation Constraints

C.3.7.3 Site Acceptance and Out-briefing C.3.7.3.1 Site Acceptance Test (SAT) C.3.7.3.2 Clean Up C.3.7.3.3 Contract Acceptance Inspection (CAI)

C.3.8 CONTRACTOR ENGINEERING/TECHNICAL/ SUPPORT SERVICES

C.3.9 CONFIGURATION MANAGEMENT (CM)

C.3.9.1 Configuration Identification C.3.9.2 Configuration Control C.3.9.3 Configuration Status Accounting C.3.9.4 Configuration Audits

C.3.10 QUALITY CONTROL PROGRAM

C.3.11 SECURITY REQUIREMENTS

C.3.11.1 General C.3.11.2 Security Measures

C.3.12 SAFETY PROGRAM

C.3.12.1 Safety Program Implementation

C.3.13 NVR TEST PROGRAM

C.3.13.1 Contractor Master Test Plan (CMTP) C.3.13.2 Test Procedures C.3.13.3 Conduct of Tests

C.3.14 TRAINING

C.3.14.1 Training Analysis C.3.14.2 Training Design C.3.14.3 Training Development

C.3.14.3.1 Operations and Maintenance Course C.3.14.3.2 Front Line Manager (FLM)/Operations Manager (OM) Course C.3.14.3.3 Quality Assurance (QA) Specialist Course

C.3.14.4 Web-based Training C.3.14.5 Training Delivery – Operations and Maintenance Course Conduct C.3.14.6 Training Delivery – Second Level Engineering C.3.14.7 Training Delivery – Depot

C.3.15 INTEGRATED LOGISTICS SUPPORT (ILS) PROGRAM

C.3.15.1 ILS Program Requirements C.3.15.2 ILS Management C.3.15.3 Integrated Support Plan (ISP) C.3.15.4 Integrated Logistics Support (ILS)

C.3.15.4.1 ILSMT Meeting (TIM) Participation C.3.15.5 Logistics Management Information (LMI)

C.3.15.5.1 LMI Data Reviews C.3.15.5.2 NVR Hardware Breakdown Structure C.3.15.5.3 Provisioning Guidance Conference C.3.15.5.4 Provisioning Conference

Page C-iii

SECTION C

C.3.15.5.5 Cataloging C.3.15.6 Site Spares C.3.15.7 System Asset Identification Report C.3.15.8 Technical Instruction Books C.3.15.9 Maintenance Concept

C.3.15.9.1 Field Maintenance C.3.15.9.2 Engineering Support (2nd level) C.3.15.9.3 Contractor Provided Depot Logistics Support (CDLS)

C.3.15.10 Pre and Post Acceptance Technical Assistance Hotline Support C.3.15.11 NVR Warranty C.3.15.12 Failure Reporting C.3.15.13 Diminishing Manufacturing Sources/Material Shortages (DMS/MS)

Page C-1

C.1.0 INTRODUCTION

C.1.1 Purpose

This Statement of Work (SOW) describes the tasks that the Contractor must perform in order to satisfy the requirements stated in this document. The Contractor must also perform fully in accordance with the NVR Technical Specification, Section J-1, which is incorporated herein.

C.1.2 Overview

The National Airspace System (NAS), System Requirements Document (NAS-RD-2013 and

NAS-RD-2025), sections 3.6.1.c and 3.6.3.c require that both air-to-ground (A/G) and ground-to-ground (G/G) communications be recorded and stored for later retrieval. This applies to all Air

Traffic Control (ATC) domains, including Air Traffic Control Towers (ATCT), Terminal Radar

Approach Control (TRACON) facilities, Air Route Traffic Control Centers (ARTCC), and the

Federal Aviation Administration (FAA) Command Center and Alaskan Automated Flight

Service Stations (AFSS). FAA Order JO 7210.3, Facility Operation and Administration, requires that ATC facilities “record operational communications to the maximum extent practicable.”

The NAS Voice Recorder Program (NVRP) within the ATO’s Communications, Information and

Network Organization is responsible for procuring and installing voice recording systems; these systems must meet the needs of both the FAA and Department of Defense (DOD). NAS Voice

Recorders (NVRs) must provide certified recordings between air traffic controllers, pilots, and ground-based Air Traffic Control (ATC) facilities. These recordings support accident and incident investigations, search and rescue (SAR) operations, training, evaluations, quality assurance, risk-based monitoring, and responses to Freedom of Information Act (FOIA) requests.

The NAS Voice Recorder (NVR) will replace the Digital Audio Legal Recording (DALR) systems starting in 2018 and take advantage of evolving recorder technology to provide enhanced digital voice recording functionality to meet new requirements that include compliance with Air Traffic Organization (ATO) safety orders. These ATO safety orders require risk-based monitoring of air traffic operational safety events that have evolved since the implementation of the DALR. The replacement of these aging voice recorders will address the increasing demand for more expeditious access to audio data via a controlled centralized remote access. The NVR will record and store data provided through various interfaces from a portfolio of legacy voice switch systems, as well as the new NAS Voice System (NVS) projected for introduction into the

NAS in 2020. It will introduce new capabilities with increased recording capacity that allows recording of administrative phones, recording of Voice over Internet Protocol (VoIP) telephones, and connection to FAA Telecommunications Infrastructure (FTI)'s Enterprise Network Time

Protocol (NTP) where available.

C.1.3 Legacy Voice Recording Equipment

Legacy voice recorder system functions include voice recording and audio monitoring, audio record playback, duplication, quarantine, archive, erasure and audio record certification. Near real time audio monitoring and recorded audio playback in the legacy voice recorder is available from both local and remote workstations. Local access is defined as a voice recorder that can be accessed from operator positions on-site without the need to connect through a network system

Page C-2 to off-site facilities, while remote access would involve communications across physical facility boundaries.

Additional legacy voice recorder system functions include system security, administration, maintenance, and test. DALR system configurations are deployed in 24 channel increments (i.e., 24, 48, 72, etc.).

DALR voice recordings are stored on local hard drives as archive, quarantine, and duplicate recordings. Audio recordings may be selectively duplicated and the files can then be saved to remote servers or external storage devices such as CD-writeable drives, DVD-writeable drives, and Universal Serial Bus (USB) drives.

Audio access is restricted to personnel with authorized user privileges. Consistent with FAA policy, both FAA and DOD voice recorders typically retain audio recordings for 45 calendar days, after which recordings are automatically erased unless quarantined.

Quarantined files cannot be automatically deleted following the typical 45-day retention period;

they must be manually deleted by authorized personnel or set to be automatically deleted following a user-defined date and time. The audio recording configuration assigns unique voice channel names to individual voice channels associated with a specific controller position within each facility. Audio recording function is managed by the system administrator.

The physical locations in which the DALR are housed include TRACONs, ARTCCs, ATCSCCs, AFSSs, mobile towers, and DOD facilities. A facility may also include lab or test environments.

C.1.4 Operational Concept

The NVR will provide the capability to securely record, store, retrieve, playback, duplicate, erase, and manage operational and administrative voice data. NVR will record communications by interfacing to voice switches and administrative telephone systems at FAA and DOD ATC facilities in all domains. It will automate a number of tasks that were previously performed manually and incorporate the latest requirements for information security, safety, remote maintenance monitoring, and remote audio retrieval.

NVR information security features will include features for guarding against external and internal information security attacks including but not limited to emerging threats from attacks that use telephony resources. These will be used in conjunction with existing and future gateways, firewalls, and other security measures that are part of a facility’s network design.

NVR voice recordings will be stored for a user-configurable period, in one-day increments.

Currently the FAA and DOD recorders are set for 45 calendar days after which the recordings are automatically erased and permanently irretrievable unless quarantined. The NVR will provide the ability to retain quarantined recordings beyond the 45-day period.

C.1.5 NVR System Description

The NVR system consists of the voice recording hardware and associated software that will be interfaced to a facility’s voice switch, radio node, administrative telephone system, computer

Page C-3 network, and FAA Telecommunication Infrastructure’s (FTI) time-code source. The NVR system is ground based and will consist of a majority of analog channels with a transition to digital and Internet Protocol (IP) channels. System functions include recording, storing, and time stamping data provided to it through its various interfaces with other equipment, including the voice switch interfaces. The NVR will be used to record both outgoing and incoming A/G and

G/G communications. The Government user may set the recording mode, such as Voice

Operated Exchange (VOX) or record channels continuously. Incoming A/G communications will be recorded when VOX is active and terminated when VOX does not detect voice. G/G outgoing and incoming communications will be recorded when a telephone call is initiated and terminated when the call ends.

Access to the recorder’s functionality will be available to authorized personnel at designated network-based workstations that have recorder software installed. To safeguard recorded information, authorized personnel will be assigned passwords and be required to logon to the

NVR. Authenticated and certified duplications of data contained on the recorder’s storage media will be copied by authorized personnel onto various media using the workstation’s media resources, which include removable media (i.e., CD-writeable drives, DVD-writeable drives, and

USB). One of the concepts of the NVR is to reduce the need for and use of removable media by delivering files over the dedicated network, which is a more secure, efficient and timely process.

The protected duplicate recording will use a file format (such as .wav) that allows secure playback from a secure playback resource with sound capability. The synchronized time code signal will also be present on the duplicate recording and can be displayed along with the audio playback on the user’s computer display.

The NVR will provide enhanced digital voice recording functionalities such as increased recording channel capacity, recording of Voice over Internet Protocol (VoIP) telephones, enhanced compatibility with FAA Telecommunications Infrastructure (FTI) resources, more efficient remote access, compliance with mandatory security standards, and an enterprise time-source solution. Both local access and remote access will be incorporated into NVR. Local access is defined as a voice recorder that can be accessed from operator positions on-site without the need to connect through a network system to off-site facilities, while remote access would involve communications across physical facility boundaries.

C.1.6 NVR System Requirements

C.1.6.1 General Requirements

a) The NVR System consists of Commercial-Off-The-Shelf (COTS) or Non-

Developmental-Item (NDI) for hardware, firmware and software described in the NVR

Technical Specification, Section J-1, and this SOW.

b) The NVR System must provide the capability to record, monitor, reproduce, duplicate, archive and erase the voice communications involving air traffic control operations. A

NVR Functional Block Diagram is illustrated in Figure 1-1 of the NVR Technical

Specification, Section J-1. The NVR system must consist of a workstation, one or more logger recording units, an external alarm indicator; an equipment enclosure (cabinet or rack); and speakers.

Page C-4

c) Equipment that is shown as ANCILLARY in Section B CLIN X012 series, and described in the NVR Specification, is equipment that may or may not be ordered depending on the specific site configurations. Ancillary equipment may include

• Remote Alarms,

• Workstations or access terminals (not located at the equipment enclosure),

• GPS Time Source Reserve power supply (Uninterruptible Power Source), and

• Analog Patch Panel.

The ancillary equipment must be mounted in an equipment enclosure.

d) The NVR System must provide centralized remote access, retrieval and dissemination through a common, modern and flexible enterprise solution via a two-way interface with

FAA Telecommunications Infrastructure (FTI) via the NAS Enterprise Security Gateway

(NESG).

C.1.6.2 Size and Capacity Requirements

The NVR System may be ordered in any system size configurations scalable from 24 up to 900 channel systems with a combination of analog, digital and IP configurations

C.2.0 APPLICABLE DOCUMENTS

C.2.1 Government and Miscellaneous Documents

The following reference documents, version in effect as of the date of the Screening Information

Request (SIR), form a part of this SOW and are applicable to the extent specified herein. In the event a document referenced herein has been withdrawn or cancelled, the document version in effect as of the date of the SIR must remain the standard. The Contractor must notify the FAA of any changes or revisions to the applicable documents identified in the SOW.

Agency and Document Type Specific Reference

Federal (FED) Standards

• FIPS PUB 102, Guideline for Computer Security Certification and Accreditation

Federal Aviation Administration (FAA) Documents

• NVR Technical Specification (Attachment J-1

• FAA William J Hughes Technical Center Test and Evaluation

Handbook

FAA Specifications

• FAA-D-2494, Technical Instruction Book Manuscript:

Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books

• FAA-G-2100, Electronic Equipment, General Requirements

FAA Standards

• FAA-STD-019, Lightning and Surge Protection, Grounding, Bonding and Shielding Requirements for Facilities and

Electronic Equipment

• FAA-STD-028, Contract Training Programs

FAA Orders & Notices

• Order 1370.121, FAA Information Security and Privacy

Program and Policy

• Order 1600.69, Facility Security Management Program

• Order 1800.66, Configuration Management Policy

• Order JO 7210.3, Facility Operation and Administration

Non-Government and Miscellaneous Agency

Documents - Standards

• ANSI/ISO/ASQ Q9001, Quality Management Systems –

Requirements

• Uniform Code Council, Incorporated/EAN International

Page C-5

Agency and Document Type Specific Reference

(UCC/EAN) UCC/EAN Code GS1-128, Bar Code Symbology

Standard

• RTCA D0-278, Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic

Management Systems

• NFPA-70, National Electrical Code

C.2.2 Sources of Documents

Copies of DOT or FAA documents, specifications, standards, and orders and notices may be obtained from the Contracting Officer. Requests must fully identify the documentation desired, i.e., document type (specification, Standard, Order), number, and title. The FAA “Test and

Evaluation Handbook” is available on the Internet at http://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/initiatives/vnv/documen ts/publications/VVSPT-A2-PDD-013_TnE_Handbook_v3.0.pdf.

American National Standard Institute (ANSI) documents can be obtained from:

American Society for Quality

611 East Wisconsin Avenue

P.O. Box 3005

Milwaukee, WI 53201-3005

Telephone 800-248-1946 or 414-272-8575, Fax 414-272-1734 http://www.asq.org/.

National Institute of Standards and Technology (NIST) documents can be obtained from:

https://www.nist.gov/publications.

Radio Technical Commission for Aeronautics (RTCA) documents can be obtained from:

http://www.rtca.org/

National Fire Protection Association (NFPA) documents can be obtained from:

http://www.nfpa.org/codes-and-standards/all-codes-and-standards/list-of-codes-and-standards?mode=code&code=70

C.2.3 Precedence of Documents

If the requirements of this SOW and documents listed in Section.2.0 Applicable Documents are in conflict, the SOW must have precedence. In the event of a conflict between an FAA document and a non-FAA document, the FAA document must have precedence. The Contractor must immediately notify the Government Contracting Officer of any conflicts detected between any documentation used in this SOW.

C.2.4 Terminology

For the purpose of simplicity, the NAS Voice Recorder will hereinafter be referred to as “NVR.”

All references to “Government” and “FAA” must mean the FAA Contracting Officer (CO) assigned to the NVR procurement. “Government” also includes DOD activities.

http://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/initiatives/vnv/documents/publications/VVSPT-A2-PDD-013_TnE_Handbook_v3.0.pdf http://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/initiatives/vnv/documents/publications/VVSPT-A2-PDD-013_TnE_Handbook_v3.0.pdf http://www.asq.org/ https://www.nist.gov/publications http://www.rtca.org/

Page C-6

C.3.0 CONTRACTOR TASKS

The Contractor must design, implement, and test NVR equipment in accordance with the requirements contained in the NVR Technical Specification, Section J-1 of this document.

The Contractor must prepare SOW deliverables in accordance with the contract data requirements list (CDRL) and the associated data item descriptions (DIDs). Deliverables referenced throughout this SOW by their CDRL titles are to be prepared and delivered in accordance with the CDRL of the same name even when the CDRL or DID number is not specified.

The Contractor must make maximum use of Commercial-Off-the-Shelf (COTS) and Non-

Developmental Item (NDI) parts and components that have demonstrated high reliability. For purposes of this procurement, the term COTS must be understood to mean material available from a variety of sources as a commercial product, currently in use in the Government or commercial market place. The use of commercial item hardware does not exempt the contractor from complying with the contract requirements. The Contractor must propose and obtain approval from the FAA for the use of any non-commercial items or modified COTS hardware.

The Contractor must ensure that all hardware, software and documentation required for operation and support of the NVR is provided as part of the supplies and services provide herein.

The Contractor must provide and deliver to the Government all COTS software that is part of the

NVR system delivered by the Contractor in accordance with the following. The Contractor

a. Must provide software licenses and the associated documents needed to maintain the computational software for all software delivered under the NVR contract;

b. Must permit the Government user to prepare back-up copies of all software delivered with the NVR without restriction—i.e. an unrestricted copyright unless the software is commercial software and the Contractor is not entitled to make backup copies;

c. Must maintain the software from the delivery of the Operational Test & Evaluation

(OT&E) System to the FAA to the end of the warranty period for each NVR system installation;

d. Must test and validate using Contractor-prepared and Government-approved test procedures all NVR software modifications and updates before delivering them to the

Government;

e. Must provide the Government with a copy of all the validated software updates and modifications (e.g. routine updates to improve performance, enhancement maintenance operations, and corrections of system shortcomings) and the associated test procedures employed in testing of such updates and modifications;

f. Must assist the Government in software verification, integration, and regression testing as specified in the NVR contract; and

Page C-7

g. Must describe the process for accommodating software upgrades and future version changes in the Program Management Plan (PMP).

C.3.1 Program Management

The Contractor must establish a NVR management program to plan, organize, direct, and control all the activities necessary to meet the requirements of the NVR SOW and NVR Technical

Specification, Section J-1. The Contractor must assign a Program Manager with responsibility for controlling and coordinating all work to be performed. The Program Manager must have the resources and the authority to ensure efficient and timely program execution and must be the single focal point within the Contractor’s activity for all required program tasks. The Program

Manager must be prepared at all times to discuss, with the Contracting Officer (CO) or the

Contracting Officer's Representative (COR), the current status of all contract requirements.

C.3.1.1 Program Management Plan

The Contractor must prepare, deliver, and maintain a Program Management Plan (PMP). The

PMP must describe the Contractor’s organization and internal lines of communication, assignment of management and engineering responsibilities and duties, data management structure and procedures, resources plans for the conduct of contractually required tasks, decision making processes, plans for accommodating software upgrades and version changes, risks, and the program milestone schedule. The PMP must include a description of the Contractor’s plan for managing technology insertions and technical refresh activities associated with component obsolescence.

The Contractor must implement a system for program control to include earned value management best practices, or in the event such a system already exists, must utilize that system for internal schedule performance, control, and measurement. The Contractor must determine the general management procedures to be used in each and all major program and functional areas. The Contractor must maintain total data management, including monitoring, reporting, status accounting, and correlating (e.g., in Government change requirements versus implemented changes) all changes to the PMP. The Contractor must maintain a database to track the status of all problem reports (hardware and software) and maintain records to verify corrective action.

The Contractor must ensure that its sub-contractor’s data satisfies all of the engineering, logistics, training, and technical requirements of the NVR contract.

The Contractor must report on all exceptions, changes and modifications made to the PMP at the

Program Management Reviews (PMRs) (Section C.3.2.2) and include exceptions, changes and modifications in the Monthly Status Report (MSR) (Section C.3.3).

(CDRL PGM001 – Program Management Plan (PMP))

C.3.1.2 Risk Management

Suggest change the below (and throughout) as follows. This is IAW our plain language policy.

Instead of repeatedly stating “the contract must”, use lists as follows. Also, don’t duplicate what’s already in the DID or we run the risk of being inconsistent/contradictory.

Page C-8

At a minimum, the Contractor must:

• identify cost, schedule and technical risks, issues and opportunities.

• describe how it will effectively manage these risks throughout the performance of this contract.

• describe the process for identification of risks; risk assessment; development and implementation of mitigation plans; and monitoring, tracking and reporting of risk items in the Program Management Plan.

• quantify risks with respect to cost, schedule and technical impact.

• develop and maintain a register identifying, analyzing, and classifying program risks, issues and opportunities.

• include in the register courses of action for mitigating or eliminating each risk and issue as well as achieving each opportunity.

• classify risks, issues and opportunities as low, medium, or high priority.

• provide the register of risks, issues and opportunities in the Monthly Status Report and at

Program Management Reviews.

• include risk management content related to the Program Management Reviews in Program

Management agendas and minutes.

(CDRL PGM001 – Program Management Plan (PMP))

C.3.1.3 Contract Work Breakdown Structure (CWBS)

The Contractor must develop and deliver as part of the Program Management Plan a Contract

Work Breakdown Structure (CWBS). The Contractor must use the CWBS framework as the basis for contract planning, budgeting, reporting program costs and master program schedule status to the Government. The Contractor must maintain the CWBS throughout the life of the contract.

(CDRL PGM003 – Contract Work Breakdown Structure (CWBS))

C.3.1.4 Integrated Master Schedule

The Contractor must develop, maintain, and deliver an Integrated Master Schedule based on the

CWBS in sufficient detail to plan, manage, and control all program activities. At a minimum, the program schedule must include the following:

a. Identification of critical and high-risk efforts,

b. Substantiation of schedule risk analysis and subsequent schedule adjustment,

c. Subcontractor and supplier efforts,

d. Activities associated with risk mitigation plans, and

e. Identification of the program critical path.

The Contractor must provide a monthly assessment of schedule progress to date and include changes to schedule assumptions, potential impacts, and recommended corrective actions to minimize schedule delays.

Page C-9

The Contractor must update and maintain the Integrated Master Schedule for the duration of the contract.

(CDRL PGM004 – Integrated Master Schedule (IMS))

C.3.2 Reviews and Technical Interchange Meetings (TIMs)

As a part of its program management responsibilities, the Contractor must plan, support, conduct, and participate in NVR Reviews and TIMs at the Contractor’s facility. The Contractor must prepare and submit to the Government an agenda for each Review or TIM in the format of its choice. The Contractor must prepare and submit to the Government the minutes in support of each Review or TIM in the format of its choice; the minutes must include action items resulting from the review with planned closure dates, responsible persons and planned actions to resolve.

The status of all open action items must be included in each of the subsequent review minutes.

The Contractor must make available cognizant technical personnel, including sub-contractor personnel, in each of the areas to be covered during the review or TIM. The Contractor must address all current aspects of the NVR status as related to the contract. A free exchange of ideas between the Contractor and the Government is encouraged in order to establish NVR program progress, identify technical problems and resolve the problems in a timely manner.

For the Reviews and TIMs, the Contractor must make available a separate meeting room with a telephone for use by the Government.

Unless otherwise agreed to by the Government, all conferences, meetings, and reviews described below to be held at the Contractor's facility must be understood to mean a Contractor facility located in the Continental United States (CONUS).

(CDRL ADM001 – Meeting Agenda)

(CDRL ADM002 – Meeting Minutes)

C.3.2.1 Post Contract Award Review (PCAR)

The Contractor must plan, host, provide administrative support for, and participate in a Post

Contract Award Review (PCAR) to be held at the Contractor’s facility following contract award.

The Government will determine the date for the PCAR, which is to occur not later than 15 calendar days after the contract award date. The agenda for the PCAR will be coordinated between the Government and Contractor.

As a minimum, the Contractor must assume that the participants are not familiar with the

Contractor’s proposal and must provide a comprehensive review of its plans and schedule for satisfying each of the SOW requirements and include a discussion of the roles and responsibilities of its sub-contractors. The Contractor must ensure the participation of all its

NVR managers and Team Leads (e.g., systems engineering, testing, installation, logistics, training, security, and configuration management) and sub-contractor personnel, if applicable, who are responsible for fulfilling NVR contract tasks.

Page C-10

C.3.2.2 Program Management Review (PMR)

The Contractor must plan, prepare and conduct monthly program management reviews (PMRs).

The first PMR must be held no later than 45 calendar days after the PCAR. PMRs must be held at the Contractor’s facility, unless otherwise directed by the Government.

The Contractor must prepare the PMR agenda and minutes. Each PMR must include a review of the NVR schedule, Contractor program accomplishments (e.g., milestones met and unmet), risks, status of CDRL deliverables, problems, open action items, and a discussion of its sub-contractor activities. The Contractor must ensure the participation of knowledgeable NVR technical, logistics and training personnel, including sub-contractor personnel, for each of the topics identified in the agenda.

C.3.2.3 Final System Review (FSR)

The Contractor must conduct a final system review (FSR) to review and verify specific system solutions proposed for the NVR Specification requirements, prior to start of the Factory

Acceptance Test (FAT). The FSR must address the pre-test system configuration and the technical and schedule risks associated with each hardware configuration item (HWCI) and computer software configuration item (CSCI) and must include the resolution of all problems identified during prior reviews. The FSR must be held prior to the start of Factory Acceptance

Test (FAT). The date of the FSR must be coordinated with the Government.

(CDRL ADM001 – Meeting Agenda)

(CDRL TES002 – Factory Acceptance Test (FAT) Procedures)

C.3.2.4 Functional Configuration Audit (FCA)

The Contractor must conduct a Functional Configuration Audit (FCA) (see also Section C.3.9, Configuration Management). During the FCA, the Contractor and the Government will determine whether or not each configuration item meets the functional requirements of the NVR

Specification. The Contractor must support the FCA in accordance with the Government approved Contractor’s Configuration Management Plan (CMP).

(CDRL CMP002 – Configuration Audit Summary Report)

C.3.2.5 Physical Configuration Audit (PCA)

The Contractor must conduct a Physical Configuration Audit (PCA) (see also Section C.3.9, Configuration Management). During the PCA, the Contractor and the Government will determine if the as-built version of the configuration items are identical to the technical documentation. The PCA includes a detailed review of all of the documentation described in

Section C. The Contractor must support the PCA in accordance with the Government approved

Page C-11

Contractor’s CMP. After successful completion of the PCA, the product baseline must be established. The PCA will be limited to the LRU level of documentation.

(CDRL CMP002 – Configuration Audit Summary Report)

C.3.3 Monthly Status Report

The Contractor must prepare and deliver to the Government a Monthly Status Report (MSR) that provides an assessment of the program's progress, identifies problems encountered or foreseen, updates the program schedule, and provides the status of any open action items assigned to the

Contractor during Reviews and TIMs.

(CDRL PGM002 – Monthly Status Report (MSR))

C.3.4 System

The Contractor must develop and implement a System Engineering Program for the definition, development, verification, integration and testing of the NVR requirements. System engineering efforts must include all aspects of performance, quality, life cycle costs, maintainability, reliability, schedule, data processing reserves and future growth requirements.

The Contractor must describe its System Engineering Program and its hardware development plan, which must include any hardware developed, produced or modified in the System

Engineering Management Plan (SEMP).

If ordered by the Government, the Contractor must develop a separate Software Development

Plan (SDP) which includes the software coding standards to be used for the program as part of its overall system engineering program.

The Contractor must maintain effective control over the system engineering and design development process, including subcontract items and services, to ensure cost, performance and schedule requirements are met, to provide early detection and resolution of problems and to reduce risk.

The Contractor must ensure that all system software developed under this contract (including changes or updates made to software, hardware and/or configuration) are documented, tested and managed in accordance with an industry standard software assurance process that is approved by the government.

Any waiver from the software implementation requirements must be justified in writing and approved by the FAA Contracting Officer.

The Contractor must permit authorized FAA personnel and designees to inspect all software documentation and must make available to the FAA for review the information, practices, procedures and documentation developed or purchased by the Contractor or its sub-contractors in connection with the NVR software program. The FAA must be allowed to witness all tests

Page C-12 associated with software development or integration. The contractor must define a software coding standard and demonstrate that its software development processes follow that software coding standard. The contractor must demonstrate that its software development processes identify and address failure modes and risks (including hardware, software, human and system) that may impact critical operations in its software design. The contractor must demonstrate that its software development processes produce software that is maintainable through the system life-cycle

(CDRL SE001 – System Engineering Management Plan (SEMP))

(CDRL SE002 – Software Development Plan (SDP))

C.3.4.1 System Requirements Allocation Document (SRAD)

The Contractor must prepare and deliver a System Requirements Allocation Document (SRAD) that describes the design of the system in terms of HWCIs and CSCIs and their relationship to requirements in the NVRP specification. The SRAD must clearly show both the allocation of

NVR requirements to the contractor HWCIs and CSCIs and how the design satisfies each requirement.

(CDRL SE003 – System Requirements Allocation Document (SRAD))

C.3.4.2 Interface Control Documents

The Contractor must develop Interface Control Documents (ICDs) for all interface requirements documents (IRDs) identified in the NVR Technical Specification, Section J-1 of this document.

(CDRL SE004 – Interface Control Document (ICD))

C.3.4.3 Engineering Change Proposals (ECPs)

The Contractor must seek Contracting Officer concurrence prior to submitting engineering changes. Upon receiving concurrence from the Contracting Officer, the Contractor must formally submit an ECP for review and approval prior to initiating any changes to the approved

NVR product baseline. The ECP must contain sufficient information to allow the Government to evaluate the total impact of the proposed change and must be form, fit and function to the baselined system requirements. The Contractor must not make any changes without prior written approval from the CO. The Contractor must have a plan in place to continue to meet the requirements of the contract if the CO does not approve the change.

(CDRL SE005 – Engineering Change Proposal (ECP))

C.3.4.4 Routine System Updates

The Contractor must provide routine software updates, hardware upgrades, drivers, security patches, design modifications and corrective performance improvements. The Contractor must notify the FAA before incorporating any adaptation, update or upgrade of commercially available hardware, software or firmware. Routine system updates must be form, fit and function compatible with the baselined system requirements. The Contractor must conduct a risk

Page C-13 benefit analysis to include life cycle and transition planning prior to notification to the FAA.

The Contractor must notify the CO 30 days in advance of implementing any changes, including a summary of the risk analysis. The FAA will notify the Contractor, in writing, of its approval or disapproval for the change and what testing is required prior to the Contractor implementing the change. The Contractor must not make any changes without prior written approval from the CO.

The Contractor must have a plan in place to continue to meet the requirements of the contract if the CO does not approve the change.

C.3.5 Environmental and Occupational Safety and Health (EOSH)

The Contractor must develop an Environmental and Occupational Safety and Health (EOSH)

Program Plan describing its approach to protecting the environment and the safety and health of

FAA and Contractor personnel. The EOSH Program Plan must detail how the Contractor will apply EOSH principles, criteria, and techniques as part of a formalized risk assessment process to identify, assess, and mitigate the potential for environmental impacts, property damage and incidents that may cause harm to personnel.

The Contractor’s EOSH Program Plan must be submitted and all FAA comments resolved prior to commencement of work.

If the Contractor becomes aware of any previously unknown hazardous conditions at a

Government facility that may pose a hazard to Contractor or Government personnel or affect performance of work related to the NVR implementation, the Contractor must immediately notify the Contracting Officer and the Contracting Officer’s Representative.

(CDRL EOSH001 – EOSH Program Plan)

C.3.6 Delivery and Installation of NVR Operational Test & Evaluation (OT&E) Equipment

The Contractor must deliver and install an NVR system at the Mike Monroney Aeronautical

Center (MMAC) in Oklahoma City, OK and at the William J Hughes Technical Center

(WJHTC) in Egg Harbor Township, NJ in accordance with Section C.3.6 below. After the system is installed, the Contractor must conduct a Site Acceptance Test (SAT) on the system.

The Government will not start OT&E until the successful completion of SAT. After SAT, this system will be referred to as the Operational Test & Evaluation (OT&E) system.

C.3.6.1 Operational Test & Evaluation (OT&E) System

The NVR OT&E system must be fully configurable and capable of meeting all the functional and performance requirements of the NVR Specification. The Contractor must provide a listing and quantity of all the system hardware, LRUs, cables, racks etc., that comprise the OT&E system.

C.3.6.1.1 Site Spares for OT&E

The Contractor must deliver to the Government a Recommended Spare Parts list. The spares and quantities recommended must support the Government’s OT&E testing requirements. The list must be in Contractor format and must identify each LRU/site spare’s noun nomenclature, part number, national stock number (if available), commercial and Government entity (CAGE) code, quantity and unit price and Contract Line Item Number (CLIN). The Government reserves the

Page C-14 right to add or delete NVR spares on the list or to increase/decrease the quantities on the list.

The Contractor must deliver the spares ordered by the Government with the OT&E system.

(CDRL LOG004 – Recommended Spare Parts List (RSPL))

C.3.6.1.2 OT&E System Contractor Services

The Contractor must provide on-call engineering, technical and maintenance support services assistance for the OT&E activities at Oklahoma City, OK and WJHTC, as required throughout

OT&E. As a minimum, the Contractor must provide technical personnel with functional and operational knowledge of the NVR to support all Government NVR OT&E activities.

The Contractor must also conduct NVR system familiarization on the NVR functions, capabilities, operations and maintenance for Government test personnel at the FAA Oklahoma

Communications Engineering Team (OKCET) test facility and WJHTC. The purpose for this familiarization is to enable Government test personnel to operate and maintain the NVR during

Government conducted OT&E testing. The familiarization materials and the documentation used must be in Contractor format. Copies of the familiarization materials and documentation must be provided to the Government personnel who participate in the familiarization. The

Government personnel receiving the familiarization will retain any materials and documentation provided.

C.3.6.2 Production Systems

No on-site surveys will be conducted for the NVR recorder installations, unless ordered by task order. An NVR Site Worksheet will be prepared by the Government sites to identify their recorder requirements. These NVR Site Worksheets will be processed through the Government

NVR program office for validation and be used for ordering the site specific voice recorder equipment from the vendor.

The Contractor must verify that each production system is free from manufacturing defects, and except for configuration differences is identical to the OT&E system. Contractor must perform a

PAT on each production NVR at the Contractor’s facility. See Contract Section E for

Government Acceptance procedures.

C.3.7 Delivery, Installation, and Integration of NVR Production Equipment

The Contractor must deliver, install, integrate and test the NVR system components and remote access capability in accordance with the NVR Technical Specification, Section J-1 and the

Government approved Site Installation Management Plan (SIMP). The Contractor must provide all cabling, wiring, connectors, and associated hardware within the NVR, including cabling, hardware, and software/firmware associated with any backup capabilities ordered by the

Government. The Contractor must include all commercial manuals and NVR Technical

Documentation for the system.

The Contractor must provide the personnel, tools and test equipment, software, materials, and services required to meet this requirement. The Contractor must assign a site installation representative to function as the Contractor’s on-site interface with the Government. The

Page C-15

Contractor’s site representative must be responsible for integration, control, and coordination of all installation activities.

The Contractor must bear the travel and per diem for CONUS installations. For OCONUS travel, the Contractor may charge travel in accordance with CLIN X017.

(CDRL IMP001 –Site Installation Management Plan (SIMP))

C.3.7.1 Site Installation Management Plan (SIMP)

The Contractor must develop documentation describing the planning and execution of the NVR installation, integration, and acceptance testing. Documentation required includes a Site

Installation Management Plan (SIMP), governing all site installation activities. The SIMP must include the Contractor’s requirements for primary power, data communication lines (or any other line of information transfer), cabling, and ducting needed in preparation for the installation, operation, maintenance, and support of the NVR equipment. The SIMP must include the

Contractor’s approach to managing and implementing the installation, integration, and acceptance testing of the NVR. When approved by the Government, the SIMP must be used as the guideline for the coordination and conduct of all NVR installation activities.

(CDRL IMP001 –Site Installation Management Plan (SIMP))

C.3.7.2 Site Installation

The Contractor must be responsible for all Contractor NVR site installation activities as specified in the NVR contract.

C.3.7.2.1 Adds, Moves, and Changes

If ordered by the Government, the Contractor must provide technicians and general labor category personnel to provide equipment adjustment services at facilities where NVR hardware is being, has been, or will be installed by the Contractor. The Contractor technicians must be familiar with operation and maintenance of the NVR system and must be responsible for supervising the general labor category personnel when used. The services must include adding, moving, and/or changing NVR hardware or associated equipment. These services are exclusive of the fixed price line items within the NVR contract and must be addressed by task orders in the

CLIN – X020 series.

C.3.7.2.2 Packing, Shipping, Off-Loading, and Placement

The Contractor must be responsible for the packing, shipping, and delivery of all NVR equipment and material from the Contractor’s facility to the designated Government site’s equipment room. The Contractor must remove all NVR equipment packing and shipping materials and other installation generated trash from the site at the conclusion of site acceptance test (SAT).

The Contractor must include a copy of each shipment’s packing list and site specific bill of materials (BOM) with each shipment and must provide a copy of each packing list and site specific BOM to the addressees specified by System Packing List/Bill of Materials.

Page C-16

The Contractor must comply with any additional Packaging, Handling, Storage and

Transportation requirements shown in Section D.

(CDRL IMP003-System Packing List/Bill of Materials (BOM))

C.3.7.2.3 Equipment Installation

The Contractor must physically install all NVR equipment ordered by the Government for the specific site in the designated locations within the Government facility. The Contractor must supply all mounting hardware and tools necessary to attach the NVR equipment to rack assemblies, facility flooring, or other connection points as required.

The Contractor must support a Site Readiness Review (SRR) teleconference 30 days prior to

NVR equipment delivery to each site as designated in the approved SIMP. The designated

Government representative will review and validate that all site preparation activities are complete, the site is ready for installation of NVR equipment, and the complete system can be delivered to the site by the planned equipment delivery date.

All NVR equipment must be designed and installed in accordance with DOT Specification FAA-

G-2100, Electronic Equipment, General Requirements. The seismic installation of mechanical components must be executed in accordance with the seismic requirements specified in the

International Building Code (IBC) and in the DOT Specification FAA-G-2100, Section 3.2.1.1.1, Seismic Zone Design, and 3.3.5, Personnel Safety and Health. The equipment electrical components must be U/L listed and must be installed and used in accordance with their rating.

The equipment must be grounded in compliance with FAA-STD-019.

The Government will be responsible for the removal and disposal of the displaced legacy voice recording system equipment from the installation site.

C.3.7.2.3.1 Specific Installation Tasks

a. The Contractor must execute mechanical mounting of all NVR components.

b. The Contractor must provide and install all cabling, wiring, connectors, and associated hardware within the NVR and between the NVR and the Government provided demarcation point for connection to external equipment and power. This includes Contractor furnished electrical cabling and connectors for all special test equipment. The Contractor must supply all the tools and test equipment needed to install and checkout the electrical cables. All electrical work must be accomplished in accordance with NFPA-70 and the local codes.

c. The Contractor must connect the NVR equipment to external interfaces and bring the NVR

System to a fully functional and operational status.

C.3.7.2.4 Tools and Test Equipment

The Contractor must provide all tools, test equipment, and test jigs for all installation, integration and testing activities on the NVR and ancillary equipment delivered at Government designated facilities in accordance with the Contractor’s Government approved SIMP and test procedures.

Page C-17

C.3.7.2.5 Site Installation Constraints

Two weeks before the scheduled installation date at each site, the Contractor must notify the

Government Point of Contact, of the Contractor’s scheduled arrival. The Contractor-Installer must conduct an in-briefing at the site prior to initiating installation activities to introduce themselves and to inform site personnel of the plan and schedule for the installation and testing of the NVR. The Government will brief the Contractor/Installer about the site’s constraints and administrative requirements (e.g., security, parking, access to the facility, etc.).

As described in the SIMP, the Contractor must perform all installation activities in such a way that they have minimum impact on the site’s operations. The Contractor must make adequate provisions in the specific site installation schedule to avoid conflicts with Government activities at the site. The Contractor must perform all installation, integration, and testing activities on a non-interference basis. The Government will endeavor to permit Contractor installation and checkout to proceed during the site’s normal daytime working hours.