GPCS SIR Section C_DRAFT-20240809.docx

Contents

C-2 Statement of Work GPC System 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 Ground-to-Ground Protocol Converter (GPC) System Program will convert analog voice/signaling to ED-137C compliant Voice over Internet Protocol (VoIP), and back to analog voice/signaling to allow VoIP Voice Communications Systems (VCSs) to communicate with any remaining FAA analog interfaces.

The VoICE program will replace voice switching core infrastructure at select Airport Traffic Control Towers (ATCTs), Terminal Radar Approach Control Facilities (TRACONs), Center Radar Approach Control Facility (CERAPs), and Air Route Traffic Control Centers (ARTCCs) with a modern and supportable Voice over Internet Protocol (VoIP) enabled networked voice communication system.

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

Statements contained in “Notes” do not constitute legally binding requirements but rather are explanatory in nature and are included only to provide context to the associated Statement of Work and Attachment J.1 and J.2 requirements in the applicable sections.

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

The GPC 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, to include Order of Precedence IAW Section H.

Applicable Documents and Acronyms FAA and Miscellaneous Documents

1. 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. In addition, FAA documents, specifications, handbooks, orders, standards, and guidance contained in Sections D, E, F, G, H, and all J attachments are applicable to the extent specified therein.

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

If 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.

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.

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-G-2100H, Electronic Equipment, General Requirements FAA-D-2494B, Technical Instruction Book Manuscript: Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books FAA-D-2494B, Appendix I, Commercial Instruction Books

FAA HF-STD-004A, Standard Practice: Human Factors Engineering RequirementsFAA-STD-025F DOT, Federal Aviation Administration, Standard, Preparation of Interface DocumentationFAA-STD-028C, Contract Training Programs

FAA Order 6000.30G, National Airspace System Maintenance Policy FAA Order 1800.66A, Federal Aviation Administration (FAA) Configuration Management Policy FAA Order 30000.22, Air Traffic Organization Technical Training Management FAA Order 3000.57, Air Traffic Organization Technical Operations Training and Personnel Certification

FAA EVMS Surveillance Guide FAA Standard Work Breakdown Structure Version 5.3, January 2021

MIL-STD-3018, Department of Defense Standard Practice: Parts Management MIL-STD-3034, Reliability Centered Maintenance Methodology MIL-STD-3034A, Notice 1 Reliability-Centered Maintenance (RCM) Process SD-22, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Guidebook

Uniform Code Council, Incorporated/EAN International (UCC/EAN) UCC/EAN Code GS1-128, Bar Code Symbology Standard NFPA-70, National Electrical Code (2023) EIA-748 Earned Value Management System Standard ANSI/EIA-649 Rev. C, National Consensus Standard for Configuration Management (February 7, 2019) ANSI/TechAmerica STD-0016-2011 GEIA-HB-649 Rev A, Configuration Management Standard Implementation Guide (March 1, 2016) 29 CFR 1910 Occupational Safety and Health Standards NFPA 101 Life Safety Code (2024) Sharable Content Object Reference Model (SCORM) Ver 1.2 National Defense Industrial Association (NDIA) Integrated Program Management Division (IPMD), Guide to the Integrated Baseline Review (IBR) - Revision 4 (January 11, 2023)

Sources of Documents

1. Copy of Acquisition Management System (AMS) Policy:

http://FAST.faa.gov 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:

Assist.dla.mil Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The online internet address of http://FAST.faa.gov 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 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 https://www.asq.org/ National Institute of Standards and Technology (NIST) documents can be obtained from:

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

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

https://www.nfpa.org/Codes-and-Standards/All-Codes-and-Standards/List-of-Codes-and-Standards SAE International documents can be obtained from:

https://www.sae.org/ Aviation Industry Computer-Based Training Committee (AICC) can be obtained from:

https://www.aicc.org/ Shareable Content Object Reference Model (SCORM) can be obtained from:

https://www.adlnet.gov/projects/scorm/ Additional E-Learning reference material can be found at:

https://www.adlnet.gov Uniform Code Council, Incorporated/EAN International (UCC/EAN), USS/EAC Code GS1-128, Bar code Symbology Standard can be obtained from:

www.gs1us.org GEIA-STD-0007 can be obtained from:

https://standards.globalspec.com/std/14215932/geia-std-0007 NDIA IPMD Guide to the Integrated Baseline Review (IBR) can be obtained from:

https://www.ndia.org/-/media/sites/ndia/divisions/ipmd/2023--files/ndia_ipmd_ibr_guide_rev_4_jan1123.pdf?download=1 Precedence of Documents

1. If the requirements of this SOW, Attachment J.1, Attachment J.2, and documents listed in Section.2.1 Applicable Documents are in conflict; the SOW, Attachment J.1, and Attachment J.2 take precedence.

1. Attachment J.3 documents are provided for guidance only.

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

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

VoICE GPC System Acronyms Attachment J.5, VoICE GPC System Acronym List provides the Acronyms and associated definitions used in the SOW for guidance only.

Program Management The Contractor must provide all resources, equipment, materials, and support services necessary to meet the contract requirements.

Program Management Oversight

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

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

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

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 contract requirements, to include oversight over all other functional area leads and/or focal points identified in the contract requirements.

The Contractor must prepare, deliver, and maintain a Program Management Plan (PMP) IAW CDRL/DID GPC-PGM001, Program Management Plan.

The PMP must outline and define how the Contractor will manage, execute, and control the overall requirements of the GPC System contract.

The Contractor must prepare and submit a draft version of the PMP with the agenda for the Post Contract Award Review (PCAR).

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

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

The Contractor must document exceptions, changes, and modifications to the PMP IAW CDRL/DID GPC-PGM002, Monthly Status Report (MSR).

The Contractor must manage and administer all contract actions to ensure compliance with all terms and conditions of the contract and document and address any changes or amendments that may arise during the implementation of this contract.

The Contractor must track, monitor, and report the status of contract activity and contract deliverables to the FAA IAW CDRL/DID GPC-PGM002, Monthly Status Report.

The Contractor must track and monitor the status of all contract deliverables IAW the delivery instructions provided for in the respective CDRL/DID documents.

The Contractor must maintain the accuracy of all Government Furnished Property (GFP) provided by the FAA identified in Attachment J.9, Government Furnished Property and AMS Clause 3.10.3-2 Government Property – Basic Clause (April 2022).

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

The Contractor must document the results of the GFP physical inventory IAW Contract Data Requirements List (CDRL)/Data Item Description (DID) GPC-GFP001, Physical Inventory Report.

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.

The Contractor must prepare and submit a Monthly Status Report (MSR) IAW CDRL/DID GPC-PGM002, Monthly Status Report.

Program Management Reviews

1. The Contractor must plan, conduct, and administratively support Program Management Reviews (PMRs) on a monthly virtual 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.

The Contractor’s facility for hosting in-person PMRs must be within the contiguous United States (CONUS) unless otherwise directed by the FAA.

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.

The Contractor must track, monitor, and report the status of contract activity and contract deliverables to the FAA IAW CDRL/DID GPC-PGM008, Program Management Review Briefing Materials.

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 IAW CDRL/DID GPC-PGM008, Program Management Review Briefing Materials.

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 EVM 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. NOTE: More information regarding the definition and responsibilities of an EVM CAM can be found in ANSI EIA-748D, Earned Value Management System Standard, as referenced in Section C.3.4.1.

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

The Contractor must prepare and submit a meeting agenda IAW Section C.3.7(g) and meeting minutes IAW Section C.3.7(i).

CDRL/DID GPC-PGM008 Program Management Review Briefing Materials (PMRBM) Post Contract Award Review (PCAR)

1. The Contractor must plan, host, provide administrative support for, and participate in the PCAR following contract award.

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

The FAA will determine the date for the PCAR, which is expected to occur not later than 15 business days after the contract award date.

The FAA will coordinate the PCAR agenda with the Contractor, including requirements to submit draft versions of associated to include CDRL/DID GPC-PGM001, Program Management Plan (PMP), CDRL/DID GPC-PGM003, Integrated Program Management Report (IPMR) Format 6 (Integrated Master Schedule (IMS)), CDRL/DID GPC-PGM004, 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.2, and C.3.4.3, respectively.

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.

The Contractor must ensure the participation of its GPC System PM, Deputy PM, all functional area leads, all 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, configuration management, and sub-contractor personnel, as applicable, who are responsible for fulfilling GPC System contract tasks.

The Contractor must prepare and submit a meeting agenda IAW Section C.3.7(g) and meeting minutes IAW Section C.3.7(i).

Program Control The Contractor must use industry-standard project management processes and practices to track progress and manage performance of the work specified in this contract.

Earned Value Management (EVM)

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

The Contractor must establish, maintain, and use an approved Earned Value Management System (EVMS) that complies with the latest version of EIA-748 “Earned Value Management System Standard.”

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.

The Contractor must prepare and submit IPMR Formats 1 through 7 IAW CDRL/DID GPC-PGM003, Integrated Program Management Report (IPMR).

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

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

The Contractor must ensure the participation of the PM, Deputy PM, all functional area leads, and all CAMs in all aspects of the EVMS Surveillance Reviews, including preparation, conduct, and closure of any resulting action items.

CDRL/DID GPC-PGM003 Integrated Program Management Report (IPMR) Contract Work Breakdown Structure (CWBS)

1. The Contractor must develop and maintain the CWBS in Attachment J.8.2, CWBS, to the control account level as described in this SOW IAW CDRL/DID GPC-PGM004, Contract Work Breakdown Structure Index and Dictionary.

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.

The Contractor must prepare and submit a draft CWBS Index and Dictionary with the agenda for the PCAR, as previously outlined in Section C.3.3 (d).

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

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.

The Contractor must include the status of any proposed or newly approved changes to the CWBS at the PMR, following the respective change, as described in CDRL/DID GPC-PGM008, Program Management Review Briefing Materials, and required under Section C.3.2.

CDRL/DID GPC-PGM004 Contract Work Breakdown Structure Index and Dictionary Integrated Baseline Review (IBR)

1. The Contractor must participate in the FAA-conducted Integrated Baseline Review (IBR), which is expected to occur not later than 120 calendar days after the contract award date.

The Contractor must support subsequent IBRs after the exercise of a major contract modification.

The IBR will be conducted IAW, Attachment J.6 FAA’s “Program-Level Integrated Baseline Review Guide.”

The Contractor must adhere to the process described in Attachment J.6 Section 3.0 and further defined in the latest version of the NDIA’s “Guide to the Integrated Baseline Review (IBR),” as referenced in the FAA’s “Program-Level Integrated Baseline Review Guide”.

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.

The FAA will review these draft artifacts and discuss the IBR process during the PCAR, as specified in Section C.3.3 (d).

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.

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.

The Contractor must prepare and submit a meeting agenda IAW Section C.3.7(g) and meeting minutes IAW Section C.3.7(i).

Performance Management

1. 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.

The Contractor must document its approach and specific performance measures IAW CDRL/DID GPC-PGM001, Program Management Plan.

CDRL/DID GPC-PGM001 Program Management Plan Risk Management

1. The Contractor must develop, document, implement, and maintain a 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.

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

1. The Contractor must maintain the RMP throughout the life of the contract.

1. The Contractor must create and maintain a worksheet documenting all risks, issues, or opportunities identified by the FAA or the Contractor IAW CDRL/DID GPC-PGM006, Risk Identification Worksheet (RIW).

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

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

1. The Contractor must prepare and deliver the RRR as an attachment to CDRL/DID GPC-PGM002, Monthly Status Report (MSR), as outlined in Section C.3.1.

1. The Contractor must report the status for all medium and high-risk items in the MSR, as described in CDRL/DID GPC-PGM002, Monthly Status Report and outlined in Section C.3.1.

1. The Contractor must status all medium and high-risk items during the PMR, as described in CDRL/DID GPC-PGM008, Program Management Review Briefing Materials, and outlined under Section C.3.1.

Meetings, Reviews, and Working Groups

1. The Contractor must use FAA-approved collaboration tools (e.g., Zoom, Microsoft Office Teams) to conduct all virtual 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.

1. The Contractor must plan, support, conduct, and participate in working groups that are established to focus on a particular functional area, including but not limited to Program Management, Systems Engineering, Human Factors, Integrated Logistics, Test and Evaluation, Deployment. Working groups will meet as needed and with location (on-site or online) and schedule determined by the FAA in order to support the objectives of each working group.

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

1. The FAA will indicate whether the ad hoc meeting or ad hoc review will be held virtually or in person, either at the Contractor’s facility or the FAA’s facility.

1. 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 the CONUS unless otherwise directed by the FAA.

1. 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.

1. The Contractor must prepare and submit an agenda for all meetings and reviews identified as requiring an agenda IAW CDRL/DID GPC-ADM001, Meeting Agenda.

1. The Contractor must be prepared to discuss and address the topic(s) and/or issue(s) outlined in the meeting agenda if an agenda is required.

1. The Contractor must prepare and submit minutes for all meetings and reviews identified as requiring minutes IAW CDRL/DID GPC-ADM002, Meeting Minutes.

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

Engineering

1. The Contractor must develop a comprehensive system in support of the development and delivery effort IAW Attachments J.1, GPC System Specifications and Requirements Technical Specifications and Attachments J.2, Interface Requirements Documents.

The Contractor must provide associated services in support of the development and delivery effort IAW Attachments J.1, GPC System Specifications and Requirements Technical Specifications and Attachments J.2, Interface Requirements Documents.

GPC System Hardware Development The Contractor must conduct hardware design and development in accordance with Section C 4.5 Systems Engineering and the processes established in the Government approved CDRL/DID GPC-SE001, Systems Engineering Management Plan (SEMP) and the Government approved CDRL/DID GPC-SE002 Hardware Development Plan.

GPC System Software Development

1. The Contractor must conduct software design and development in accordance with VoICE GPC System Software Requirements Document, Attachment J.1.2.

1. The Contractor must conduct software design and development for tools in accordance with VoICE GPC System Tool Software Requirements Document, Attachment J.1.7.

GPC System Integration, Assembly, Test and Checkout (IAT&C) The contractor must conduct System IAT&C in accordance with the processes established in the Government approved SEMP. Integration and Checkout Testing (INCO) must be conducted in accordance with Section 3.6 of the VoICE GPC System Test & Evaluation Requirements, J.1.9 and the Government approved CDRL/DID GPC-TES001, Contractor Master Test Plan.

Engineering Management

1. The Contractor must develop and implement an Engineering Management Program for the definition, development, verification, integration, test, and delivery of a comprehensive system and associated services meeting the requirements in Attachments J.1, GPC System Specifications and Requirements Technical Specifications and Attachments J.2, Interface Requirements Documents.

The Contractor must assign a Chief System Engineer dedicated to the GPC System program, who has overall responsibility for planning, executing, monitoring, and controlling all Engineering work to be performed under this contract.

The Chief 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.

The Contractor must assign a Lead Software Engineer, dedicated to the GPC System program, who has overall responsibility for controlling and coordinating all software engineering work to be performed under this contract.

The Contractor must assign a System Security Manager, dedicated to the GPC System program, who has overall responsibility for controlling and coordinating all system security work to be performed under this contract.

The Contractor must prepare, support, and participate in meetings, reviews, and working groups with the FAA that directly pertain to or are relevant to the Engineering of the VoICE GPC System solution as outlined in Section C.3.7, Meetings, Reviews, and Working Groups.

System Engineering

1. The Contractor must, for System Engineering efforts, include all aspects of performance, quality, life cycle costs, maintainability, reliability, schedule, data processing reserves, verification methods, and future growth requirements for the GPC System, GPC Traffic Load Generator (GTLG), and GPC System Faulted Modules.

The Contractor must prepare and deliver all CDRL/DIDs identified in Attachments J.1, GPC System Specifications and Requirements.

The Contractor must document its System Engineering program IAW CDRL/DID GPC-SE001, System Engineering Management Plan (SEMP).

The Contractor must document its approach for hardware development IAW CDRL/DID GPC-SE002, Hardware Development Plan (HDP).

The Contractor must document any hardware developed, produced, or modified for the program, including the GTLG and GPC System Faulted Modules in the HDP.

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, for the GPC System, GTLG, and GPC System Faulted Module components (hardware/software/firmware), conduct design reviews, support system safety assessments, and provide engineering support services.

The Contractor must, for any variance from the requirements in the GPC System, GTLG, and GPC System Faulted Module Technical requirements in Attachments J.1, GPC System Technical Specification, and J.2, GPC System Software Requirements, justify and submit to the FAA for approval IAW CDRL/DID GPC-CMP002, Request for Variance (RFV) as identified in Section C.4.12.5.2, Variances.

Interface Control Documents (ICDs)

1. The Contractor must develop Interface Control Documents (ICDs) for all interface requirements identified in Attachment J.2, GPC System Interface Requirement Documents (IRDs), using FAA-STD-025F DOT, Federal Aviation Administration, Standard, Preparation of Interface Documentation as guidance IAW CDRL/DID GPC-SE003, Interface Control Document (ICD).

The Contractor must develop an GTLG Interface Control Document (GTLG-ICD) for all interfaces of the GTLG to internal components and external connections to the GPC System under test, using FAA-STD-025F, DOT, Federal Aviation Administration Standard, Preparation of Interface Documentation as guidance IAW CDRL/DID GPC-SE004, GTLG Interface Control Document (GTLG-ICD).

The Contractor must specify in the GTLG Interface Control Document (GTLG-ICD), for each component of the GPC System, detailed information about the protocol used for obtaining component health/status information.

The Contractor must specify in the GTLG Interface Control Document (GTLG-ICD), for each component of the GPC System, detailed information of each health/status item associated with the component (including the data types associated with the item and the frequency of item health/status reporting).

The Contractor must specify in the GTLG Interface Control Document (GTLG-ICD), for each component of the GPC System, detailed information about the protocol used for collecting component log messages.

The Contractor must specify in the GTLG Interface Control Document (GTLG-ICD), for each component of the GPC System, detailed information about the protocol used for authentication with the component.

The Contractor must specify in the GTLG Interface Control Document (GTLG-ICD), for each component of the GPC System, detailed information about the protocol used for command/control of the component.

The Contractor must support technical interchange meetings, as ordered by the FAA, in support of the integration with the GFP provided GTLG, including meeting participation, delivery of technical presentations, performing data analysis, and providing action item responses The Contractor must develop a CDRL/DID GPC-SE005, FAA Remote Monitoring System (RMS) Interface Control Document (RMS-ICD) for all interfaces of the GPC Management Subsystem (GPCMS) external connections to the FAA RMS using FAA-STD-025F, DOT, Federal Aviation Administration Standard, Preparation of Interface Documentation as guidance IAW CDRL/DID GPC-SE005,RMS Interface Control Document (RMSRMS-ICD).

System Requirements Allocation Document (SRAD)

1. The Contractor must document the architecture used to meet the requirements of Attachments J.1, GPC System Specifications and Requirements and attachment J.2, Interface Requirements Documents IAW CDRL/DID GPC-SE006, GPC System Requirements Allocation Document (SRAD).

The Contractor must ensure the SRAD clearly shows both the allocation of GPC System requirements to the Contractor Hardware Configuration Items (HWCIs) and Computer Software Configuration Items (CSCIs) and how its design satisfies each requirement.

The Contractor must document the architecture used to meet the requirements of Attachment J.1.4, GPC System Traffic Load Generator (GTLG) Requirements Document IAW CDRL/DID GPC-SE007, GTLG System Requirements Allocation Document (GTLG-SRAD).

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

Design Information and Source Code

1. The Contractor must provide the FAA with design information and software source code IAW CDRL/DID GPC-SE008, Design Information and Source Code (DISC) for GPC System-specific (or designated) equipment and software (that the Contractor owns or controls) for operation and maintenance purposes, including but not limited to equipment for repair of the GPC system, all support and test equipment, and any special test equipment, GTLG, and Faulted Modules.

The Contractor must provide updates to design information and software source code IAW CDRL/DID GPC-SE008, Design Information and Source Code (DISC) for GPC System-specific (or designated) equipment and software (that the Contractor owns or controls) for operation and maintenance, including but not limited to equipment for repair of the GPC system, all support and test equipment, and any special test equipment, GTLG, and Faulted Modules.

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

1. 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. Product Baseline Index (PBLI)

f. Engineering Change Proposal (ECP) i List of Problem Reports fixed ii List of Known Issues The Contractor must, for GPC System Validation Test Systems (VTS) systems, provide updates to drawings, design information, and software source code as the GPC System baseline changes, including but not limited to equipment for repair of the GPC system, all support and test equipment, and any special test equipment, GTLG, and Faulted Modules.

The Contractor must, for Production Systems, provide updates to drawings, design information, and software source code as the GPC System baseline changes, including but not limited to equipment for repair of the GPC system, all support and test equipment, and any special test equipment, GTLG, and Faulted Modules.

CDRL/DID GPC-SE008 Design Information and Source Code (DISC) Initial System Requirements Review

1. The Contractor must conduct an initial System Requirements Review (iSRR) at the Contractor’s facility within the contiguous United States (CONUS), FAA facility, or virtually, as determined by the FAA, IAW Section F, Deliveries and Performance.

The Contractor must provide review materials for use during the iSRR IAW CDRL/DID GPC-SE009, Initial System Requirements Review Materials (iSRRM).

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, VoICE GPC System Technical Specification J.1.2, VoICE GPC System Software Requirements J.1.3, VoICE GPC System Security Requirements J.1.4, VoICE GPC System Traffic Load Generator Requirements J.1.5, VoICE GPC System Faulted Module Requirements J.1.6, VoICE GPC System Vendor PDP iFAT Verification Requirements Traceability Matrix (VRTM) J.1.7, VoICE GPC System Tool Software Requirements J.1.8, VoICE GPC System Test & Evaluation Requirements J.1.9, VoICE GPC System Support System Diagram & Documentation J.1.10, VoICE GPC Management Subsystem (GPCMS) Requirements for Government Server Platform Integration J.1.11, VoICE GPC Management Subsystem (GPCMS) Requirements for Government Workstation Platform Integration J.1.12, VoICE GPC System Requirements for Government Network Platform Integration J.1.13 VoICE GPC System Human Factors Design Tailored Checklist J.2.1, VoICE GPC System to Analog Interphone IRD J.2.2, VoICE GPC System to FAA Facility Power IRD J.2.3, VoICE GPC System to Government Transport System (GTS) IRD J.2.4, VoICE GPC System to FAA Enterprise Audit Record Collection System (FEARCS) IRD J.2.5, VoICE GPC System to FAA Enterprise Cryptographic Certificate Management System (FECCMS) IRD 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 GPC System, GTLG, and GPC System Faulted Module hardware and software used for initial Factory Acceptance Test (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 GPC System, GTLG, and GPC 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 GPC System, GTLG, and GPC System Faulted Module engineering and development (i.e., hardware and software) activities;

6. Describe the processes intended to track system requirements allocation relative to GPC System, GTLG, and GPC System Faulted Module engineering and development (i.e., hardware and software) activities;

7. Describe the achievability of the technical requirements and system/cost-effectiveness while demonstrating how the activities are achievable in the Integrated Master Schedule (IMS); and,

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

The Contractor must, during iSRR, address the status of the following as they relate to the GPC System, GTLG, and GPC System Faulted Modules in preparation for the subsequent design reviews:

9. CDRL/DID GPC-SAF001, System Safety Program Plan (SSPP);

10. Human factors analysis and user involvement processes;

11. CDRL/DID GPC-CMP001, Configuration Management Plan (CMP);

12. CDRL/DID GPC-QSP001, Quality System Plan (QSP);

13. CDRL/DID GPC-SEC001, System Security Plan (SSP); and,

14. Data Management processes and procedures, as identified in the CDRL/DID GPC-PGM001, Program Management Plan (PMP).

The Contractor must prepare and submit a meeting agenda IAW Section C.3.7(g) and meeting minutes IAW Section C.3.7(i).

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

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

1. The Contractor must conduct a Final Requirements Review (FRR) at the Contractor’s facility within the contiguous United States (CONUS) FAA facility or virtually as determined by the FAA IAW Section F, Deliveries and Performance.

The Contractor must develop and provide supporting documentation for the Final Requirements Review IAW CDRL/DID GPC-SE010, Final System Requirements Review Materials (FSRRM).

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, VoICE GPC System Technical Specification J.1.2, VoICE GPC System Software Requirements J.1.3, VoICE GPC System Security Requirements J.1.4, VoICE GPC System Traffic Load Generator Requirements J.1.5, VoICE GPC System Faulted Module Requirements J.1.6, VoICE GPC System Vendor PDP iFAT Verification Requirements Traceability Matrix (VRTM) J.1.7, VoICE GPC System Tool Software Requirements J.1.8, VoICE GPC System Test & Evaluation Requirements J.1.9, VoICE GPC System Support System Diagram & Documentation J.1.10, VoICE GPC Management Subsystem (GPCMS) Requirements for Government Server Platform Integration J.1.11, VoICE GPC Management Subsystem (GPCMS) Requirements for Government Workstation Platform Integration J.1.12, VoICE GPC System Requirements for Government Network Platform Integration J.1.13, VoICE GPC System Human Factors Design Tailored Checklist J.2.1, VoICE GPC System to Analog Interphone IRD J.2.2, VoICE GPC System to FAA Facility Power IRD J.2.3, VoICE GPC System to Government Transport System (GTS) IRD J.2.4, VoICE GPC System to FAA Enterprise Audit Record Collection System (FEARCS) IRD J.2.5, VoICE GPC System to FAA Enterprise Cryptographic Certificate Management System (FECCMS) IRD The Contractor must, at the FRR:

1. Review the corresponding test results and all PTRs, including a correlation of each requirement tested against the as-is GPC System, GTLG, and GPC System Faulted Module hardware and software used, of the iFAT activities and identify the state of each requirement (i.e., successfully passed or failed);

2. Describe the development required for the GPC System, GTLG, and GPC 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 GPC System, GTLG, and GPC 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 GPC System, GTLG, and GPC 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 GPC System, GTLG, and GPC System Faulted Module engineering and development activities;

6. Describe the processes intended to track system requirements allocation relative to GPC System, GTLG, and GPC 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 GPC System, GTLG, and GPC 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.

The Contractor must, at the FRR, address the status of the following as they relate to the GPC System, GTLG, and GPC System Faulted Modules in preparation for the subsequent design reviews:

9. CDRL/DID GPC-SAF001, System Safety Program Plan (SSPP);

10. Human factors analysis and user involvement processes;

11. CDRL/DID GPC-CMP001, Configuration Management Plan (CMP);

12. CDRL/DID GPC-QSP001, Quality System Plan (QSP);

13. CDRL/DID GPC-SEC001, System Security Plan (SSP);

14. Data Management process and procedures, as identified in the CDRL/DID GPC-PGM001, Program Management Plan (PMP) and,

15. CDRL/DID GPC-SW002, Software Development Plan (SDP).

The Contractor must prepare and submit a meeting agenda IAW Section C.3.7(g) and meeting minutes IAW Section C.3.7(i).

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

CDRL/DID GPC-SE010 Final System Requirements Review Materials (FSRRM) System Engineering Assistance for Validation Test System Updates

1. The Contractor must provide the engineering effort and associated test resources in support of the FAA in the assessment of each Build on the GPC System Validation Test Systems (VTS).

The Contractor must, at a minimum:

1. Provide engineering support to collaboratively work through the installation of the Contractor’s build on the GPC System VTS;

2. Analyze any discrepancies identified and documented as Program Trouble Reports (PTR’s) IAW with Section C.6.8 Program Trouble Reporting (g) on the GPC System VTS.

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

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

5. Perform regression testing to verify the resolution to a documented problem (PTR) on the GPC 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 GPC System VTSs.

GPC System Preliminary Design Review (PDR)

1. The Contractor must conduct a Preliminary Design Review (PDR) for the GPC System at the Contractor’s facility within the contiguous United States (CONUS), FAA facility, or virtually, 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.

The GPC System PDR must include GPC System Faulted Modules.

The Contractor must conduct a separate Preliminary Design Review (PDR) for the GTLG, as ordered by the FAA, at the Contractor’s facility within the contiguous United States (CONUS), FAA facility, or virtually, as determined by the FAA IAW Section F, Deliveries and Performance. The intent of the GTLG PDR is to ensure the Contractor’s understanding of the technical requirements and the FAA’s understanding of the Contractor’s proposed technical solution.

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

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, GPC System Specification requirements.

The Contractor must demonstrate how all the Attachments J.1 and Attachments…