693KA8-21-PSIR-APC-01 Attach 02 APC Draft SOW v.5 20210325.pdf

693KA8-21-PSIR-APC-01 Part I – The Schedule

03/25/2021 Section C – Statement of Work

Contents

C.1 APC SYSTEM

C.1.1 INTRODUCTION

C.1.2 SCOPE OF WORK

C.2 APPLICABLE DOCUMENTS

C.2.1 FAA AND MISCELLANEOUS DOCUMENTS

C.2.2 SOURCES OF DOCUMENTS

C.2.3 PRECEDENCE OF DOCUMENTS

C.3 PROGRAM MANAGEMENT

C.3.1 PROGRAM MANAGEMENT OVERSIGHT

C.3.2 PROGRAM MANAGEMENT REVIEWS

C.3.3 POST CONTRACT AWARD REVIEW (PCAR)

C.3.4 PROGRAM CONTROL

C.3.5 PERFORMANCE MANAGEMENT

C.3.6 RISK MANAGEMENT

C.3.7 MEETINGS, REVIEWS, AUDITS, AND WORKING GROUPS

C.4 ENGINEERING

C.4.1 ENGINEERING MANAGEMENT

C.4.2 SYSTEM ENGINEERING

C.4.3 HUMAN FACTORS ENGINEERING

C.4.4 ENVIRONMENTAL OCCUPATIONAL SAFETY AND HEALTH (EOSH) 24

C.4.5 SAFETY PROGRAM

C.4.6 RELIABILITY, MAINTAINABILITY, AND AVAILABILITY

C.4.7 IP ADDRESSING

C.4.8 SYSTEM SECURITY AUTHORIZATION SUPPORT

C.4.9 CONFIGURATION MANAGEMENT

C.4.10 ED-137 VOLUME 1 INTEROPERABILITY ACTIVITY SUPPORT

C.5 APC SUPPORT SYSTEMS

C.5.1 VALIDATION TEST SYSTEMS

C.5.2 IFAT/FAT SYSTEM

C.5.3 CONTRACTOR ENGINEERING DEVELOPMENT SYSTEM

C.5.4 MANUAL AND TRAINING DEVELOPMENT SYSTEM

C.5.5 SYSTEM TEST SYSTEM/OT&E SYSTEM

C.5.6 TRAFFIC LOAD GENERATOR

C.5.7 FAULTED MODULES

C.6 TEST AND EVALUATION

C.6.1 TEST AND EVALUATION MANAGEMENT

C.6.2 TEST AND EVALUATION ACTIVITIES

C.6.3 CONTRACTOR MASTER TEST PLAN (CMTP)

C.6.4 TEST AND EVALUATION PROCEDURES

C.6.5 TEST AND EVALUATION REPORTS

C.6.6 TEST LOGS

C.6.7 PROGRAM TROUBLE REPORTING

C.6.8 CONDUCT OF TEST

C.6.9 TEST ASSETS

C.7 QUALITY CONTROL PROGRAM

C.8 INTEGRATED LOGISTICS SUPPORT (ILS) PROGRAM

C.8.1 ILS PROGRAM REQUIREMENTS

C.8.2 ILS MANAGEMENT

C.8.3 INTEGRATED SUPPORT PLAN (ISP)

C.8.4 TRAINING

C.9 APC PRODUCTION SYSTEMS

C.9.1 PRODUCTION MANAGEMENT

C.9.2 GENERAL PRODUCTION

C.10 APC SYSTEM DEPLOYMENT

C.10.1 DEPLOYMENT MANAGEMENT

C.10.2 DEPLOYMENT

C.10.3 SUPPLEMENTAL IMPLEMENTATION SUPPORT

C.1 APC SYSTEM

C.1.1 Introduction

The mission of the FAA’s Voice Switch & Recorder (VS&R) Program Office’s VoICE over IP

Communication Enterprise (VoICE) program is to provide a flexible, network-based voice communication enterprise system that will replace aging, increasingly expensive to maintain legacy voice switches. The VoICE program will also address Radio Control Equipment (RCE) obsolescence and End-of-Life (EOL) issues.

The VoICE program will replace voice switching core infrastructure at select ATCTs, TRACONs, and ARTCCs with a modern and supportable Voice over Internet Protocol (VoIP) enabled networked voice communication system.

The VoICE program will consist of multiple competitive procurements in a two-phased approach:

Phase 1 will provide IP-analog interfaces (i.e., Air-to-Ground (A/G) Protocol Converter

(APC) and Ground-to-Ground (G/G) Protocol Converter (GPC) Systems) through two procurements:

o The APC System procurement will involve deploying an A/G interface capability that converts analog voice/signaling (currently used by all FAA voice switches, radios, and RCE) to European Organization for Civil Aviation Equipment

(EUROCAE) ED-137-compliant VoIP. The APC System will also convert ED-

137-compliant VoIP to analog voice/signaling. The APC System will replace the aging RCE with an IP-compatible capability.

o The GPC System procurement will involve deploying a G/G interface capability that converts analog voice/signaling (currently used by all FAA VoICE switches) to European Organization for Civil Aviation Equipment (EUROCAE) ED-137-compliant VoIP. The GPC System will also convert ED-137 compliant VoIP to analog voice/signaling.

Phase 2 will provide native-VoIP switching systems through one or more procurements with a priority to replace the voice switches at the ARTCCs and Core Terminal facilities.

The native-VoIP communications systems will use the APC and GPC Systems deployed with phase 1 for communicating with legacy analog interfaces.

This Statement of Work (SOW) describes the work required for the design, development, test, and implementation of the APC System.

C.1.2 Scope of Work

The scope of work includes all services and supplies required for the successful design, development, test, and implementation of the APCs, including program management, systems engineering, test and evaluation, delivery, and installation, integrated logistics support (including training), and operational support.

The APC System Contractor must perform in accordance with (IAW) the requirements of this

Statement of Work (SOW) and in conjunction with all other terms contained within the other sections of this contract.

C.1.2.1 FAA Furnish Property (GFP)

FAA Furnished Property is provided under this contract and is identified in Section J.5, FAA

Furnished Property.

a) The Contractor must maintain the accuracy of the inventory of GFP held in the custody of the

Contractor.

b) The Contractor must perform an annual physical inventory of all GFP.

c) The Contractor must perform more frequent audits as required by the FAA.

d) The Contractor must document results of the GFP physical inventory IAW Contract Data

Requirements List (CDRL)/Data Item Description (DID) APC-GFP001, Physical Inventory

Report.

CDRL/DID APC-GFP001 Physical Inventory Report

C.2 APPLICABLE DOCUMENTS

C.2.1 FAA and Miscellaneous Documents

a) In addition to Section J.1 and J.2 Attachments, the following table outlines the specifications, handbooks, orders, standards, and guidance documents that form a part of this SOW and are applicable to the extent specified herein.

b) The latest version of these documents as of the contract date must apply.

c) In the event a document referenced herein has been withdrawn or canceled, the document version in effect as of the date of the SIR must remain the standard.

d) The Contractor must obtain the documents listed in the table below and pay any applicable fees required. The applicable websites or addresses are listed in paragraph C.2.2 Sources of

Documents.

Agency and Document Type Specific Reference

Federal (FED) Standards

FIPS PUB 102, Guideline for Computer Security

Certification and Accreditation

Federal Aviation Administration (FAA)

Documents

FAA William J Hughes Technical Center Test and

Evaluation Handbook FAA Program Level Integrated Baseline Review Guide

FAA eLMS Content Integration Guide eLearning Design and Style Guide Technical Specification for Content Developers Guide

FAA Acquisition Management System (AMS) Policy

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-2100G, Electronic Equipment, General

Requirements FAA-C-1217H Federal Aviation

Administration, Construction Specification ELECTRICAL

WORK, PREMISES WIRING

FAA-D-2494, Appendix I, Commercial Instruction Books

FAA Standards

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

Electronic Equipment

FAA-STD-025f

FAA-STD-028c, Contract Training Programs

FAA HF-STD-004A, Standard Practice: Requirements for a

Human Factors Program

FAA Section 508 Standards and Guidelines

FAA Orders & Notices

FAA Order 1800.66, Configuration Management Policy

FAA Order 6000.30F, National Airspace System

Maintenance Policy

FAA Order 3900.19C “Federal Aviation Administration

(FAA) Occupational Safety and Health (OSH) Policy

Military Documents

MIL-STD-973, Configuration Management

Reliability Centered Maintenance methodology using MIL-

STD-3034

MIL-STD-3034A Notice 1 Reliability-Centered Maintenance

(RCM) Process

MIL-HDBK-61B, Configuration Management Guidance

MIL-HDBK-470A Appendix A and Appendix B

Army-Navy Aeronautical - Military Standards (AN-MS)

Non-FAA and Miscellaneous Documents -

Standards

ANSI/ISO/ASQ Q9001, Quality Management Systems –

Requirements

SAE AS9100 Rev. D: Quality Management System –

Requirements for Aviation, Space, and Defense

Organizations.

Uniform Code Council, Incorporated/EAN International

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

Symbology Standard

NFPA-70, National Electrical Code

EIA-748 Earned Value Management System Standard

HF-STD-001B Human Factors Design Standard Checklist

HF-STD-001 Human Factors Design Standard

ANSI/EIA-649, National Consensus Standard for

Configuration Management

EIA-HB-649, Configuration Management Standard

Implementation Guide

29 CFR 1910 Occupational Safety and Health Standards

NFPA 101 Life Safety Code

RTCA DO-278A (Software Integrity Assurance

Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems)

Sharable Content Object Reference Model (SCORM)

Aviation Industry Computer-Based Training Committee

(AICC)

NDIA’s “Guide to the Integrated Baseline Review (IBR) -

SAE International

C.2.2 Sources of Documents

a) Copy of Acquisition Management System (AMS) Policy:

URL: fast.faa.gov

b) Copies of FAA Orders and Notices may be obtained from the following website, and selecting the hyperlink for Orders & Notices under the Regulations and Guidelines is in the middle of the webpage. You can then search for the applicable FAA Orders and Notices.

URL: www.faa.gov

c) Copies of documents starting with MIL- can be obtained from the following website and then selecting the “Quick Search” tab on the left side of the webpage:

URL: Assist.dla.mil

d) Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The on-line internet address of

FAST is http://FAST.faa.gov.

e) The FAA “Test and Evaluation Handbook” is available on the Internet at https://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/library/v&vsummit

/vvDocuments/documents/handbook/TEHandbook.pdf

f) 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/.

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

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

https://appriver3651010256-my.sharepoint.com/personal/marie_plummer_lstechllc_com/Documents/Documents/VoICE/SIR/Draft%20SIR%20Feb%20CO%20Review/Section%20C/fast.faa.gov http://www.faa.gov/ https://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/library/v&vsummit/vvDocuments/documents/handbook/TEHandbook.pdf https://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/library/v&vsummit/vvDocuments/documents/handbook/TEHandbook.pdf http://www.asq.org/ https://www.nist.gov/publications

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

http://www.rtca.org/

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

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

j) SAE International documents can be obtained from:

https://www.sae.org/

C.2.3 Precedence of Documents

a) If the requirements of this SOW and documents listed in Section.2.1 Applicable Documents are in conflict; the SOW takes precedence.

b) In the event of a conflict between an FAA document and a non-FAA document, the FAA document takes precedence.

c) The Contractor must immediately notify the FAA Contracting Officer (CO) of any conflicts detected between any documentation used in this SOW.

C.3 PROGRAM MANAGEMENT

The Contractor must provide all resources, equipment, materials, and support services necessary to accomplish the work efforts described in this SOW.

C.3.1 Program Management Oversight

a) The Contractor must establish an APC System management program to plan, organize, direct, and control all activities necessary to meet the requirements of all APC System SOW sections and all Section J.1 and J.2 attachments.

b) The Contractor must assign a Program Manager (PM), dedicated to the APC System program, who has overall responsibility for controlling and coordinating all work to be performed under this contract.

c) The Contractor must assign a Deputy PM to fulfill the duties of the PM when the PM is unavailable.

d) The PM must have the resources and the authority to ensure program execution and must be the single focal point within the Contractor’s activity for all required program tasks.

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

IAW CDRL/DID APC-PGM001, Program Management Plan.

f) The PMP must outline and define how the Contractor intends to manage, execute, and control the overall requirements of the APC System contract.

g) The Contractor must prepare and submit a draft version of the PMP with the agenda for the

Post Contract Award Review (PCAR).

h) The Contractor must maintain the PMP throughout the life of the contract.

i) The Contractor must report on all exceptions, changes, and modifications made to the PMP at the Program Management Reviews (PMRs).

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

j) The Contractor must document exceptions, changes, and modifications to the PMP IAW

CDRL/DID APC-PGM002, Monthly Status Report (MSR).

k) The Contractor must continuously monitor its performance under this contract, including the performance of its subcontractors and major suppliers, by identifying appropriate program measures to monitor the program’s cost, schedule, and technical objectives.

l) The Contractor must prepare and submit a Monthly Status Report (MSR) IAW CDRL/DID

APC-PGM002, Monthly Status Report.

CDRL/DID APC-PGM001 Program Management Plan

CDRL/DID APC-PGM002 Monthly Status Report

C.3.2 Program Management Reviews

a) The Contractor must plan, conduct, and administratively support Program Management

Reviews (PMRs) on a monthly on-line and quarterly in-person basis during the period of performance of this contract. The location for all in-person PMRs will alternate between the

Contractor’s facility and the FAA’s facility.

b) The Contractor’s facility for hosting in-person PMRs must be within the continental United

States (CONUS) unless otherwise directed by the FAA.

c) The FAA reserves the right to increase or decrease the frequency of PMRs. The CO may modify the PMR meeting schedule to accommodate special program needs.

d) The Contractor must present an overall status of the program, including but not limited to programmatic, cost, schedule, technical, performance (Earned Value Management (EVM)), risk register, performance metrics, and contractual status.

e) The Contractor must ensure the participation of the PM, Deputy PM, appropriate PM staff

(e.g., Scheduler, EVM Analyst, Financial Analyst), all functional-area leads, all Control

Account Managers (CAMs), and all Subcontractor/major supplier representatives in all aspects of the PMR, including preparation, conduct, and closure of any resulting action items.

f) The Contractor must schedule the first PMR IAW Section F Deliveries or Performance.

g) The Contractor must prepare and submit agendas for all PMRs IAW CDRL/DID APC-

ADM001, Meeting Agenda.

h) The Contractor must prepare and submit meeting minutes for all PMRs IAW CDRL/DID

APC-ADM002, Meeting Minutes.

i) The Contractor must prepare and submit briefing materials for all PMRs IAW CDRL/DID

APC-ADM003, Program Management Briefing Materials (PMRBM).

CDRL/DID APC-ADM001 Meeting Agenda

CDRL/DID APC-ADM002 Meeting Minutes

CDRL/DID APC-ADM003 Program Management Review Briefing Materials (PMRBM)

C.3.3 Post Contract Award Review (PCAR)

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

PCAR following contract award.

b) The PCAR must be held at the Contractor’s facility within CONUS.

c) The PCAR will occur not later than 30 calendar days after the contract award date, and the

FAA will determine the date for the PCAR.

d) The FAA will coordinate the PCAR agenda with the Contractor, including requirements to submit draft versions of associated artifacts such as the Program Management Plan (PMP), Integrated Program Management Report (IPMR) Format 6 (Integrated Master Schedule

(IMS)), the Contract Work Breakdown Structure (CWBS) Index and Dictionary, the

Organizational Breakdown Structure (OBS) and the Responsibility Assignment Matrix

(RAM), as outlined in Sections C.3.1, C.3.4.1, C.3.4.1.1, and C.3.4.1.2, respectively.

e) The Contractor 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 during the PCAR.

f) The Contractor must ensure the participation of its APC System PM, Deputy PM, all functional-area leads, all Control Account Managers (CAMs), and all Subcontractor/major supplier representative(s) in all aspects of the PCAR. This includes, but is not limited to program management, systems engineering, test and evaluation, deployment, integrated logistics, security, and configuration management) and sub-contractor personnel, if applicable, who are responsible for fulfilling APC System contract tasks.

g) The Contractor must prepare and submit an agenda for the PCAR IAW CDRL/DID APC-

ADM001, Meeting Agenda.

h) The Contractor must prepare and submit minutes for the PCAR IAW CDRL/DID APC-

ADM002, Meeting Minutes.

CDRL/DID APC-ADM001 Meeting Agenda

CDRL/DID APC-ADM002 Meeting Minutes

C.3.4 Program Control

The Contractor must use industry-standard project management processes and practices to track progress and assess the performance of the requirements specified in this contract.

C.3.4.1 Earned Value Management (EVM)

a) The Contractor must use earned value management for integrating, planning, and controlling the cost, schedule, and scope of this contract.

b) The Contractor must establish, maintain, and use an Earned Value Management System

(EVMS) that complies with the latest version of EIA-748 “Earned Value Management

System Standard.”

c) The Contractor must use its EVMS to plan, integrate, and control the project scope, schedule, costs, and resources; measure performance, and identify cost and schedule variances.

d) The Contractor must prepare and submit IPMR Formats 1 through 7 IAW CDRL/DID APC-

PGM003, Integrated Program Management Report (IPMR).

e) The Contractor must prepare and submit a stand-alone draft IPMR Format 6 IMS with the agenda for the PCAR.

f) The Contractor must participate in EVM Surveillance throughout the contract period of performance, as specified in the latest version of the “FAA EVMS Surveillance Guide.”

g) The Contractor must ensure the participation of the PM, Deputy PM, all functional-area leads, and all Control Account Managers (CAMs) in all aspects of the EVM Surveillance

Reviews, including preparation, conduct, and closure of any resulting action items.

CDRL/DID APC-PGM003 Integrated Program Management Report (IPMR)

C.3.4.1.1 Contract Work Breakdown Structure (CWBS)

a) The Contractor must utilize the FAA Standard Work Breakdown Structure to develop and maintain a Contract Work Breakdown Structure (CWBS) that includes all product elements

(e.g., hardware, software, services, data, and facilities) that are the responsibility of the

Contractor as described in this SOW IAW CDRL/DID APC-PGM004, Contract Work

Breakdown Structure Index and Dictionary.

b) The Contractor must use the CWBS as the basis for contract planning, budgeting, reporting program costs, earned value management reporting, and integrated master schedule status to the FAA.

c) The Contractor must prepare and submit a draft CWBS Index and Dictionary with the agenda for the PCAR.

d) The Contractor must maintain the CWBS throughout the life of the contract.

e) The Contractor must not, during the performance of the contract, change the approved

CWBS, associated definitions, or any of the reporting elements without prior written approval from the FAA CO.

f) The Contractor must include the status of any proposed or newly-approved changes to the

CWBS at the PMR, following the respective change.

CDRL/DID APC-PGM004 Contract Work Breakdown Structure Index and Dictionary

C.3.4.1.2 Integrated Baseline Review (IBR)

a) The Contractor must participate in the FAA-conducted Integrated Baseline Review (IBR), which will occur no later than 180 days after Contract Award.

b) The Contractor must support subsequent IBRs after the exercise of significant contract options and incorporation of major modifications.

c) The IBR will be conducted IAW the latest version of the FAA’s “Program-Level Integrated

Baseline Review Guide.”

d) The Contractor must adhere to the process described in Section 3.0 of the FAA IBR Guide and further defined in the latest version of the NDIA’s “Guide to the Integrated Baseline

Review (IBR),” as referenced in the FAA IBR Guide.

e) The Contractor must prepare and submit a stand-alone draft Organizational Breakdown

Structure (OBS) and a stand-alone draft Responsibility Assignment Matrix (RAM) with the agenda for the PCAR.

f) The FAA will review these draft artifacts and discuss the IBR process during the PCAR.

g) The FAA will also provide a full list of the program planning and control artifacts that must be provided by the Contractor for the IBR.

h) The Contractor must ensure the participation of its PM, Deputy PM, appropriate PM staff

(e.g., Scheduler, EVM Analyst, Financial Analyst), all functional-area leads, all Control

Account Managers (CAMs), and all Subcontractor/major supplier representative(s) in all aspects of the IBR, including preparation, conduct, and closure of any resulting action items.

C.3.5 Performance Management

a) The Contractor must establish and maintain a performance management system to ensure that the appropriate metrics are in place to manage, monitor, and report program performance.

b) The Contractor must document its approach and specific performance measures IAW

CDRL/DID APC-PGM001, Program Management Plan.

c) The performance management information must be IAW Attachment J-x, Performance

Requirements Summary.

d) The performance management information must be IAW the Performance Management

Board (PMB) requirements defined in Section H, Special Contract Requirements.

CDRL/DID APC-PGM001 Program Management Plan

C.3.6 Risk Management

a) The Contractor must develop, document, implement, and maintain a joint Contractor/FAA

Risk Management Program that provides an overall strategy and approach for effectively managing cost, schedule, and technical performance risks for the duration of the contract.

b) The Contractor must develop and maintain a Risk Management Plan (RMP) that documents the Risk Management Program IAW CDRL/DID APC-PGM005, Risk Management Plan.

c) The Contractor must maintain the RMP throughout the life of the contract.

d) The Contractor must create and maintain a worksheet documenting all risks, issues, or opportunities identified by the FAA or the Contractor IAW CDRL/DID APC-PGM006, Risk

Identification Worksheet (RIW).

e) The Contractor must prepare and deliver a risk register IAW CDRL/DID APC-PGM007, Risk Register Report (RRR).

f) The Contractor must use the information on the RIW to create the RRR.

g) The Contractor must prepare and deliver the RRR as an attachment to the MSR.

h) The Contractor must document status for all medium and high-risk items in the MSR IAW

CDRL/DID APC-PGM002, Monthly Status Report.

i) The Contractor must status all medium and high-risk items during the PMR and include this status update in the PMR agenda IAW CDRL/DID APC-ADM001, Meeting Agenda.

j) The Contractor must include any risk discussion in the PMR meeting minutes IAW

CDRL/DID APC-ADM002, Meeting Minutes.

CDRL/DID APC-PGM005 Risk Management Plan (RMP)

CDRL/DID APC-PGM006 Risk Identification Worksheet (RIW)

CDRL/DID APC-PGM007 Risk Register Report (RRR)

CDRL/DID APC-PGM002 Monthly Status Report (MSR)

CDRL/DID APC-ADM001 Meeting Agenda

CDRL/DID APC-ADM002 Meeting Minutes

C.3.7 Meetings, Reviews, Audits, and Working Groups

a) The Contractor must use FAA-approved collaboration tools (e.g., Zoom, Microsoft Office

Teams) to conduct all on-line meetings with the FAA. The Contractor can request a list of approved collaboration tools from the CO. The FAA reserves the right to add or remove collaboration tools at any time during the execution of the contract.

b) The Contractor must plan, support, conduct, and participate in working groups that are established to focus on a particular functional area (e.g., Program Management, Systems

Engineering, Human Factors, Integrated Logistics, Test and Evaluation, Deployment).

Working groups will meet as needed and with location (on-site or on-line) and schedule determined by the FAA in order to support the objectives of each working group.

c) The Contractor must plan, support, conduct, and participate in any ad hoc meetings, ad hoc reviews, and ad hoc audits, as requested by the FAA, in order to focus on a specific topic or issue pertaining to the requirements under the APC System contract. Ad hoc meetings, ad hoc reviews, or ad hoc audits may be technical, contractual, or programmatic in nature.

d) The FAA will indicate whether the ad hoc meeting, ad hoc review, ad hoc audit will be held on-line or in-person, either at the Contractor’s facility or the FAA’s facility.

e) The Contractor must, for all in-person meetings the FAA determines are to be held at the

Contractor’s facility, host the meeting at its facility within CONUS unless otherwise directed by the FAA.

f) The Contractor must make available all appropriate personnel, including sub-contractors, who have the requisite knowledge, skills, and experience to support all meetings, reviews, audits, and working groups.

g) The Contractor must prepare and submit an agenda for all meetings, reviews, and audits IAW

CDRL/DID APC-ADM001, Meeting Agenda.

h) The Contractor must be prepared to discuss and address the topic(s) and/or issue(s) outlined in the meeting agenda.

i) The Contractor must prepare and submit minutes for all meetings, reviews, and audits IAW

CDRL/DID APC-ADM002, Meeting Minutes.

j) The Contractor must prepare and submit any necessary presentation materials for all meetings, reviews, and audits in Contractor format, as requested by the FAA.

CDRL/DID APC-ADM001 Meeting Agenda

CDRL/DID APC-ADM002 Meeting Minutes

C.4 ENGINEERING

C.4.1 Engineering Management

a) The Contractor must develop and implement an Engineering Management Program for the definition, development, verification, integration, test, and deliver a comprehensive system and associated services, IAW Attachments J-1, APC System Specifications and Requirements

Technical Specifications and Attachments J.2 Interface Requirements Documents for the

FAA to deploy APC Systems in the National Airspace System (NAS).

b) The Contractor must assign a Lead System Engineer dedicated to the APC System program, who has overall responsibility for planning, executing, and monitoring and controlling all

Engineering work to be performed under this contract.

c) The Lead System Engineer must have the resources and the authority to ensure Engineering execution and must be the single focal point within the Contractor’s activity for all required

Engineering tasks.

d) The Contractor must prepare, support, and participate in meetings, reviews, audits, and working groups with the FAA that directly pertain to or are relevant to the Engineering of the

VoICE APC System solution.

C.4.2 System Engineering

a) The Contractor must, for System Engineering efforts, include all aspects of performance, quality, life cycle costs, maintainability, reliability, schedule, data processing reserves, and future growth requirements for the APC System, ATLG, and APC System Faulted Modules

b) The Contractor must prepare and deliver all CDRL/DIDs identified in Attachments J.1, APC

System Specifications and Requirements.

c) The Contractor must document its System Engineering program IAW CDRL/DID APC-

SE001, System Engineering Management Plan (SEMP).

d) The Contractor must document its approach for hardware development IAW CDRL/DID

APC-SE002, Hardware Development Plan (HDP).

e) The Contractor must document any hardware developed, produced, or modified for the program, including the ATLG and APC System Faulted Modules in the HDP.

f) 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.

g) The Contractor must, for the APC System, ATLG, and APC System Faulted Module components (hardware/software/firmware), conduct design reviews, support system safety assessments, and provide engineering support services.

h) The Contractor must, for any variance from the requirements in the APC System, ATLG, and

APC System Faulted Module Technical requirements attachments J.1 and J.2, justify and submit to the FAA for approval using a Request for Variance (RFV) as identified in Section

C.4.9.

CDRL/DID APC-SE001 System Engineering Management Plan (SEMP)

CDRL/DID APC-SE002 Hardware Development Plan (HDP)

C.4.2.1 Interface Control Documents (ICDs)

a) The Contractor must develop Interface Control Documents (ICDs) for all interface requirements identified in Attachment J.2, APC System Interface Requirement Documents

(IRDs), using FAA-STD-025f as guidance.

b) The Contractor must develop an ATLG Interface Control Document (ATLG-ICD) for all interfaces of the ATLG to internal components and external connections to the APC System under test, using FAA-STD-025f as guidance IAW CDRL/DID APC-SE004, ATLG

Interface Control Document (ATLG-ICD).

CDRL/DID APC-SE003 Interface Control Document (ICD)

CDRL/DID APC-SE004 ATLG Interface Control Document (ATLG-ICD)

C.4.2.2 System Requirements Allocation Document (SRAD)

a) The Contractor must document the architecture used to meet the requirements of

Attachments J.1, APC System Specifications and Requirements and attachment J.2, Interface

Requirements Documents IAW CDRL/DID APC-SE005, APC System Requirements

Allocation Document (SRAD).

b) The Contractor must ensure the SRAD clearly shows both the allocation of APC System requirements to the Contractor HWCIs and CSCIs and how its design satisfies each requirement.

c) The Contractor must document the architecture used to meet the requirements of Attachment

J.1.4, APC System Traffic Load Generator (ATLG) Requirements Document IAW

CDRL/DID APC-SE006, ATLG System Requirements Allocation Document (ATLG-

SRAD).

d) The Contractor must ensure the ATLG-SRAD clearly shows both the allocation of ATLG requirements to the Contractor HWCIs and CSCIs and how the design satisfies each requirement.

CDRL/DID APC-SE005 System Requirements Allocation Document (SRAD)

CDRL/DID APC-SE006 ATLG System Requirements Allocation Document (ATLG-

SRAD)

C.4.2.3 Design Information and Source Code

a) The Contractor must provide the FAA with design information and software source code

(DISC) for APC System-specific (or designated) equipment and software (that the Contractor owns or controls) for operation and maintenance purposes.

b) The Contractor must provide updates to design information and software source code for

APC System-specific (or designated) equipment and software (that the Contractor owns or controls) for operation and maintenance.

c) The Contractor must provide drawing updates and the following design information and software source code for the following activities:

1. Pre-initial Functional Configuration Audit/initial Physical Configuration Audit (Pre-iFCA/iPCA):

a. Executable Object Code (EOC)

i. Load Instructions

ii. Adaptation Data Item Description (ADID)

b. Software Configuration Index (SCI)

i. Including Release Notes

c. Software Environment Configuration Index (SECI)

d. Software Development Plan (SDP)

2. Post-iFCA/iPCA:

a. Executable Object Code (EOC)

i. Load Instructions

ii. Adaptation Data Item Description (ADID)

b. Software Configuration Index (SCI)

i. Including Release Notes

c. Software Environment Configuration Index (SECI)

d. Software Development Plan (SDP)

e. Initial Engineering Change Proposal (iECP)

i. List of Problem Reports fixed

ii. List of Known Issues

3. Post-Functional Configuration Audit/Physical Configuration Audit (Post-FCA/PCA):

a. Executable Object Code (EOC)

i. Load Instructions

ii. Adaptation Data Item Description (ADID)

b. Software Configuration Index (SCI)

i. Including Release Notes

c. Software Environment Configuration Index (SECI)

d. Software Development Plan (SDP)

e. Engineering Change Proposal (ECP)

i. List of Problem Reports fixed

ii. List of Known Issues

d) The Contractor must, for APC System Validation Test Systems (VTS) systems, provide updates to drawing, design information, and software source code as the APC System baseline changes.

e) The Contractor must, for Production Systems, provide updates to drawings, design information, and software source code as the APC System baseline changes.

CDRL/DID APC-SE007 Design Information and Source Code (DISC)

C.4.2.4 Initial System Requirements Review

a) The Contractor must conduct an initial System Requirements Review (iSRR) at the

Contractor’s facility within the continental United States (CONUS), FAA facility, or on-line, as determined by the FAA, IAW Section F, Deliveries and Performance.

b) The Contractor must provide review materials for use during the iSRR IAW CDRL/DID

APC-SE009, Initial System Requirements Review Materials (iSRRM).

c) The Contractor must, at the iSRR, demonstrate an understanding of all requirements of the following Attachment J.1 and Attachment J.2 requirements documents:

J.1.1, APC System Technical Specification

J.1.2, APC System Software Requirements

J.1.3, APC System Security Requirements

J.1.4, APC System Traffic Load Generator Requirements

J.1.5, APC System Faulted Module Requirements

J.1.6, APC System Initial Factory Acceptance Test (iFAT) Technical Requirements

J.1.7, APC Tools Software Requirements

J.2.1, APC System to Analog Radio Control Systems IRD

J.2.2, APC System to FAA Facility Power IRD

J.2.3, APC System to FAA Transport System (GTS) IRD

J.2.4, APC System to FAA Enterprise Audit Record Collection System (FEARCS) IRD

J.2.5, APC System to FAA Enterprise Cryptographic Certificate Management System

(FECCMS) IRD

d) The Contractor must, at the iSRR:

1. Describe the capability of system design and software design and development required to meet all Attachment J.1 and J.2 requirements documents, including

Reliability Maintainability Availability (RMA) and performance;

2. Clearly identify each requirement within all the Attachments J.1, and Attachments J.2 requirements documents that the Contractor believes are associated with the as-is

ATLG and APC System hardware and software used for iFAT activities;

3. Clearly identify each requirement within all the Attachments J.1, and Attachments J.2 requirements documents that the Contractor believes the as-is APC System, ATLG, and APC System Faulted Module hardware and software used for iFAT activities cannot meet without development;

4. Describe the readiness to initiate the iFAT;

5. Demonstrate that processes are in place for the APC System, ATLG, and APC

System Faulted Module engineering and development (i.e., hardware and software) activities;

6. Describe the processes intended to track system requirements allocation relative to

APC System, ATLG, and APC System Faulted Module engineering and development

(i.e., hardware and software) activities;

7. Describe the achievability of the technical requirements and system/cost-effectiveness; and,

8. Describe how the approaches for the preliminary design phase and software development risk reduction activities are appropriately planned.

e) The Contractor must, during iSRR, address the status of the following in preparation for the subsequent design reviews:

1. System Safety Program plan;

2. Human factors analysis and user involvement processes;

3. Configuration Management plans;

4. Quality Assurance plans;

5. Information System Security plan; and,

6. Data Management processes and procedures, as identified in the PMP.

f) The Contractor must document the requirements for the APC System/subsystems, ATLG, APC System Faulted Modules, and the methods to be used to ensure that each requirement has been met IAW CDRL/DID APC-SE008, System/Subsystem Specification (SSS).

g) The Contractor must provide an agenda and minutes IAW the Meeting Support requirements described in Section C.3.1.1.

h) The Contractor must, to successfully complete the iSRR, deliver all documentation and complete all Contractor action items.

CDRL/DID APC-SE008 System/Subsystem Specification (SSS)

CDRL/DID APC-SE009 Initial System Requirements Review Materials (iSRRM)

C.4.2.5 Final Requirements Review

a) The Contractor must conduct a Final Requirements Review (FRR) at the Contractor’s facility within the continental United States (CONUS) FAA facility, or on-line as determined by the

FAA IAW Section F, Deliveries and Performance.

b) The Contractor must develop and provide supporting documentation for the Final

Requirements Review IAW CDRL/DID APC-SE010, Final Requirements Review Materials

(FRRM).

c) The Contractor must, at the FRR, demonstrate an understanding of all requirements in all of the following Attachment J.1 and Attachment J.2 requirements documents:

J.1.1, APC System Technical Specification

J.1.2, APC System Software Requirements

J.1.3, APC System Security Requirements

J.1.4, APC System Traffic Load Generator Requirements

J.1.5, APC System Faulted Module Requirements

J.1.6, APC System iFAT Technical Requirements

J.1.7, APC Tools Software Requirements

J.2.1, APC System to Analog Radio Control Systems IRD

J.2.2, APC System to FAA Facility Power IRD

J.2.3, APC System to FAA Transport System (GTS) IRD

J.2.4, APC System to FAA Enterprise Audit Record Collection System (FEARCS) IRD

J.2.5, APC System to FAA Enterprise Cryptographic Certificate Management System

(FECCMS) IRD

d) The Contractor must, at the FRR:

1. Review the corresponding test results, including a correlation of each requirement tested against the as-is APC System, ATLG, and APC System Faulted Module hardware and software used, of the iFAT activities and identify which requirements successfully passed;

2. Describe the development required for the APC System, ATLG, and APC System

Faulted Modules to meet each requirement within the Attachments J.1 and

Attachments J.2:

a. For the requirements that were not met during the iFAT activities by the as-is

APC System, ATLG, and APC System Faulted Modules;

b. For the requirements that did not fully comply during the iFAT activities with the requirements within the Attachments J.1 and Attachments J.2;

c. For the requirements that may be affected, as the result of iFAT activities that were met by the as-is APC System, ATLG, and APC System Faulted Modules, by the described development associated with 2a and 2b;

3. Describe the capability of the system design and software design and development required to meet Attachments J.1 and Attachments J.2 requirements, including RMA and performance;

4. Describe the readiness to initiate the system preliminary design review;

5. Demonstrate that processes are in place for the APC System, ATLG, and APC

System Faulted Module engineering and development activities;

6. Describe the processes intended to track system requirements allocation relative to

APC System, ATLG, and APC System Faulted Module Engineering and development activities;

7. Describe the achievability of the technical requirements and system/cost-effectiveness; and,

8. Describe the approach to assess the following for the APC System, ATLG, and APC

System Faulted Module Preliminary Design Reviews:

a. Cost versus performance analysis;

b. Identification of system safety considerations and system safety design related requirements;

c. Human factors activities and design considerations to mitigate risks;

d. Identification and ranking of technical risks and mitigation approaches;

e. Verification that the hardware and software design selections have been optimized through trade study analyses;

f. Security considerations and identification of security-related requirements;

g. Reliability, Maintainability, and Availability (RMA) analyses; and,

h. Describe how the approaches for the preliminary design phase and software development risk reduction activities are appropriately planned.

e) The Contractor must, at the FRR, address the status of the following in preparation for the subsequent design reviews:

1. System Safety Program plan;

2. Human factors analysis and user involvement processes;

3. Configuration Management plans;

4. Quality Assurance plans;

5. Information System Security plan;

6. Data Management process and procedures, as identified in the PMP; and,

7. Software Development Plan.

f) The Contractor must provide an updated System/Subsystem Specification (SSS) that incorporates changes since iSRR.

g) The Contractor must provide an agenda and minutes IAW the Meeting Support requirements described in Section C.3.1.1.

h) To successfully complete the FRR, the Contractor must deliver all documentation and complete all Contractor action items.

CDRL/DID APC-SE010 Final System Requirements Review Materials (FRRM)

CDRL/DID APC-SE008 System/Subsystem Specification (SSS)

C.4.2.6 System Engineering Assistance for Validation Test System Updates

a) The Contractor must provide the engineering effort and associated test resources in support of the FAA in the assessment of each Build on the APC System Validation Test Systems

(VTS).

b) The Contractor must, at a minimum:

1. Provide engineering support to collaboratively work through the installation of the

Contractor’s build on the APC System VTS;

2. Analyze any discrepancies identified and documented as Program Trouble Reports

(PTR’s) on the APC System VTS.

3. Discuss the review of the discrepancies (PTR’s) with the FAA.

4. Incorporate the resolution of the discrepancy (PTR) in the APC System development plan;

5. Perform regression testing to verify the resolution to a documented problem (PTR) on the

APC System VTS has been properly incorporated in the system configuration baseline.

6. Provide engineering support to collaboratively work through any issues or questions that arise during the FAA’s validation testing of each software or hardware build. This support may include answers to questions on the Contractor’s design, requirements discussions, and trade-off analyses if workaround solutions are required.

7. Provide remote (i.e., not on-site) support to FAA personnel during FAA conducted validation testing.

8. As requested by the FAA, provide on-site support at FAA locations to assist the FAA in requirements validation efforts conducted on the APC System VTSs.

C.4.2.7 APC System Preliminary Design Review (PDR)

a) The Contractor must conduct a Preliminary Design Review (PDR) at the Contractor’s facility within the continental United States (CONUS), FAA facility, or on-line, as determined by the

FAA IAW Section F, Deliveries and Performance. The intent of the PDR is to ensure the

Contractor’s understanding of the technical requirements and the FAA’s understanding of the

Contractor’s proposed technical solution.

b) The Contractor must conduct separate PDRs for the APC System and the ATLG.

c) The APC System PDR must include APC System Faulted Modules.

d) The Contractor must describe its hardware and software design and demonstrate how it will meet all the requirements contained in Attachments J.1 and Attachments J.2, APC System

Specification requirements.

e) The Contractor must demonstrate how all the Attachments J.1 and Attachments J.2, APC

System Specification requirements are allocated in the Contractor’s APC System, ATLG, and

APC System Faulted Module solution.

f) The Contractor must allocate all functional requirements to individual configuration items

(CIs).

g) The Contractor must describe any changes made to the design from what was contained in the proposal submitted in response to the SIR for this contract and provide a rationale for each change.

h) The Contractor must describe any changes made since the iFCA/iPCA and provide a rationale for each change.

i) The Contractor must identify any questions or request clarifications to requirements during the PDR.

j) The Contractor must be prepared to discuss any potential impact the clarifications or questions and FAA responses may have on its design.

k) The Contractor must, in preparation for the APC System and APC System Faulted Module

PDR, document the design of the system architecture IAW CDRL/DID APC-SE011, System

Architecture Design (SAD).

l) The Contractor must, in preparation for the ATLG PDR, document the design of the ATLG

System architecture IAW CDRL/DID APC-012, ATLG System Architecture Design (ATLG-

SAD).

m) The Contractor must document and provide design review materials IAW CDRL/DID APC-

SE013, Preliminary Design Review Materials (PDRM).

n) The Contractor must present all materials in the PDRM during the PDR.

o) The Contractor must deliver all documentation and complete all Contractor action items to successfully complete the PDR.

p) The Contractor must track the status of all PDR action items in the Monthly Status Report, CDRL/DID APC-PGM002.

CDRL/DID APC-SE011 System Architecture Design (SAD)

CDRL/DID APC-SE012 ATLG System Architecture Design (ATLG-SAD)

CDRL/DID APC-SE013 Preliminary Design Review Materials (PDRM)

CDRL/DID APC-PGM002 Monthly Status Report (MSR)

C.4.2.8 APC System Critical Design Review (CDR)

a) The Contractor must conduct a Critical Design Review (CDR) to present its final technical solution and demonstrate how the requirements will be allocated within the design.

b) The Contractor must describe all changes from what was provided during the PDR and provide a rationale for each change.

c) The Contractor must conduct the CDR at the Contractor’s facility within the continental

United States (CONUS), FAA facility, or on-line, as determined by the FAA IAW Section F, Deliveries, and Performance.

d) The Contractor must conduct separate CDRs for the APC System and the ATLG.

e) The APC System CDR must include APC System Faulted Modules.

f) The Contractor must make available for reference and inspection any applicable hardware, engineering data, specifications, drawings, schematics, design and test documentation, software development files, working papers, and results of studies and analyses.

g) The Contractor must document and provide design review materials IAW CDRL/DID APC-

SE014, Critical Design Review Materials (CDRM).

h) The Contractor must present all materials in the CDRM during the CDR.

i) The Contractor must establish that the final design is IAW all Attachments J.1 and

Attachments J.2, APC System Specification requirements, deliver all documentation, and complete all Contractor action items to successfully complete the CDR.

j) The Contractor must track the status of all CDR action items in the Monthly Status Report, CDRL/DID APC-PGM002.

CDRL/DID APC-SE014 Critical Design Review Materials (CDRM)

CDRL/DID APC-PGM002 Monthly Status Report (MSR)

C.4.3 Human Factors Engineering

C.4.3.1 Human Factors Program and Planning

a) The Contractor must implement a Human Factors Engineering (HFE) Program IAW FAA

HF-STD-004A, Standard Practice: Requirements for a Human Factors Program, Section 4, General Requirements.

b) The HFE Program must consist of planning, analysis, design support, and test and evaluation efforts to ensure that system interfaces maximize safe overall system performance while minimizing lifecycle costs.

c) The Contractor must document the activities, tasks, schedule, organization, levels of effort, design concepts, and test and evaluation efforts that constitute its HFE program per Section

4.5 of FAA HF-STD-004A IAW CDRL/DID APC-HF001, Human Factors Program Plan

(HFPP).

d) The Contractor must provide the status of the HFE program at Program Management

Reviews (PMRs).

e) The Contractor must integrate the HFE effort with other system engineering and specialty engineering disciplines, including software, integrated logistics, performance, reliability, maintainability, availability, security, and safety.

f) The Contractor must support the APC System program by participating in working groups, conferences, and technical interchange meetings that directly pertain to or are relevant to the planning, implementation, and/or conduct of the human factors program.

g) The Contractor must ensure that personnel assigned to the HFE program are qualified Human

Factors specialists through education, training, and experience. The use of certified HF specialists (e.g., Certified Professional Ergonomist, Certified Human Factors Professional) is preferred.

CDRL/DID APC-HF001 Human Factors Program Plan (HFPP)

C.4.3.2 Human Factors Design

The Contractor must apply FAA HF design requirements as identified in Attachment J.1.1, System Technical Specification, and the results of HF studies, analyses, and test and evaluation results, to the iterative design of the system and equipment, software, Computer-Human

Interface (CHI), and procedures.

C.4.3.2.1 Technical Operations Monitor and Control Interface

a) The Contractor must provide a CHI that meets the Technical Operations (TO) Monitor and

Control requirements of Attachment J.1.1, APC System Technical Specification.

b) The Contractor must conduct regular meetings to brief CHI concepts to the FAA Human

Factor Working Group (HFWG) to support the development of the CHI design.

c) The Contractor must reflect the new design in all delivered documentation describing the TO

Monitor and Control requirements.

d) The Contractor must provide prototypes of the design alternatives that can be evaluated by the HFWG. Prototypes must permit interactions by users; activity may be conducted in a laboratory on the actual APC System equipment.

e) The Contractor must conduct Technical Interchange Meetings and prototype demonstrations at most bi-monthly to support the development of the CHI design.

f) The prototype demonstrations must be conducted to show incremental evolution to the final design.

g) The prototype demonstrations must be completed prior to the start of CDR.

h) The Contractor must reflect associated Airway Transportation Safety Specialist CHI requirements in the software specifications and Human Factor Design Checklist.

C.4.3.2.2 Human Factors Engineering Analysis

a) The Contractor must review,…