Post on 03-May-2023
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
Federal Aviation
Administration
U.S. Department of Transportation
Federal Aviation Administration
Technical Specification for
Ground-to-Ground Protocol Converter
(GPC) System
Draft
March 15, 2021
Focal Point
Air Traffic Organization (ATO) - Technical Operations
Air Traffic Control (ATC) Communications Services
Voice Switching and Recording Team, AJM-315
Federal Aviation Administration
800 Independence Avenue SW
Washington, DC 20591
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
ii
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
iv
Contents 1 INTRODUCTION ...............................................................................................................1
1.1 Scope ................................................................................................................................1
1.2 Document Overview ........................................................................................................1
1.3 System Overview .............................................................................................................1
2 APPLICABLE DOCUMENTS ...........................................................................................3
2.1 Government Documents ..................................................................................................3
2.1.1 Specifications ...........................................................................................................3
2.1.2 Standards ..................................................................................................................3
2.1.3 Other FAA Documents ............................................................................................3
2.1.4 Federal Regulations..................................................................................................4
2.1.5 Other Federal Documents ........................................................................................4
2.2 Non-Government Documents ..........................................................................................4
3 REQUIREMENTS ..............................................................................................................6
3.1 Functional Requirements .................................................................................................9
3.1.1 GPC Call Functions .................................................................................................9
3.1.2 GPC Analog Signaling Function............................................................................17
3.1.3 GPC Transition with VoIP VCS ............................................................................24
3.1.4 Security ..................................................................................................................24
3.1.5 Maintenance and Testing Functions ......................................................................24
3.1.6 Configuration .........................................................................................................27
3.1.7 Time Source ...........................................................................................................32
3.1.8 System Expansion ..................................................................................................33
3.1.9 Status Monitoring and Control ...............................................................................34
3.1.10 Ground-to-Ground Protocol Converter Management Subsystem (GPCMS) ........40
3.1.11 Software/Firmware Maintenance ...........................................................................42
3.2 Performance Requirements ............................................................................................43
3.2.1 Voice Channel Performance ..................................................................................43
3.2.2 Ethernet Performance .............................................................................................48
TABLE OF CONTENTS
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
v
3.2.3 System Startup .......................................................................................................49
3.2.4 Call Performance Requirements ............................................................................50
3.3 Interfaces ........................................................................................................................56
3.3.1 GPC System to G/G Interfaces ..............................................................................56
3.3.2 GPC System to Government Transport System .....................................................56
3.3.3 GPC System to Power ............................................................................................56
3.4 Reliability, Maintainability, and Availability ................................................................56
3.4.1 Reliability ...............................................................................................................56
3.4.2 Availability.............................................................................................................58
3.4.3 Maintainability .......................................................................................................59
3.4.4 GPC System Redundancy ......................................................................................60
3.5 Design Requirements .....................................................................................................61
3.5.1 Physical Design Requirements...............................................................................61
3.5.2 System Size and Capacity ......................................................................................75
3.5.3 Human Factors .......................................................................................................76
3.6 Software .........................................................................................................................76
4 VERIFICATION REQUIREMENTS ...............................................................................77
4.1 Responsibilities For Verification ...................................................................................77
4.1.1 Verification Methods .............................................................................................77
4.2 Specialized verification requirements ............................................................................78
5 ACRONYMS AND ABBREVIATIONS .........................................................................79
6 GLOSSARY ......................................................................................................................84
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
vi
Figures FIGURE 1-1. CONCEPTUAL SYSTEM DIAGRAM OF THE FAA’S VOICE ...........................................2
FIGURE 3-1. GPC SYSTEM FUNCTIONAL DIAGRAM .......................................................................6
FIGURE 3-2. GPC CONFIGURATION #1 - END-TO-END IP ENABLING OF LEGACY VCSS ................7
FIGURE 3-3. GPC CONFIGURATION #2 - IP ENABLING TO A LEGACY VCS ....................................8
FIGURE 3-4. GPC CONFIGURATION #3 - ANALOG ENABLE IP VCS ...............................................8
FIGURE 3-5. EXISTING FAA LEGACY SS CIRCUIT WITH ANALOG BRIDGE ..................................12
FIGURE 3-6. GPC APPLICATION FOR SS WITH ANALOG BRIDGE ..................................................13
FIGURE 3-7. GPC APPLICATION FOR SS WITH GPC PROVIDED FOCUS ........................................13
FIGURE 3-8. GPC APPLICATION FOR SS WITH VOIP VCS FOCUS ................................................14
FIGURE 3-9. G/G MEASUREMENT PATHS FOR GPC SYSTEM ........................................................54
FIGURE 3-10. ELECTROSTATIC DISCHARGE TEST WAVEFORM ....................................................74
Tables TABLE 3-1. RTP EVENTS ............................................................................................................10
TABLE 3-2. CALL PROGRESS AND SIGNAL TONES ........................................................................23
TABLE 3-3. GPC SYSTEM EVENT MESSAGES ...............................................................................36
TABLE 3-4. FREQUENCY RESPONSE CHARACTERISTICS ...............................................................44
TABLE 3-5. INTERMODULATION DISTORTION ..............................................................................45
TABLE 3-6. LONGITUDINAL BALANCE .........................................................................................46
TABLE 3-7. GAIN TRACKING LINEARITY......................................................................................46
TABLE 3-8. GPC SYSTEM OPERATIONAL ENVIRONMENTS ........................................................51
TABLE 3-9. TRAFFIC LOADS.........................................................................................................52
TABLE 3-10. SETUP/TEARDOWN THROUGHPUT TIMING REQUIREMENTS DURING TRAFFIC LOADS
.............................................................................................................................52
TABLE 3-11. GPC SYSTEM CRITICAL FAILURE PARAMETERS ......................................................57
TABLE 3-12. GPC SYSTEM ENVIRONMENTAL REQUIREMENTS ....................................................71
TABLE 3-13. ELECTROMAGNETIC COMPATIBILITY REQUIREMENTS .............................................71
TABLE 3-14. ELECTROSTATIC DISCHARGE FAILURE CRITERIA ....................................................73
TABLE 3-15. VOLTAGE AND CURRENT LIMITS FOR ELECTROSTATIC DISCHARGE TESTING .........73
TABLE 3-16. RANDOM VIBRATION EXPOSURE FOR GPC SYSTEM IN ACCORDANCE WITH MIL-
STD 810G ............................................................................................................75
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
1
1 INTRODUCTION
1.1 Scope
This specification contains the technical requirements of the Federal Aviation Administration
(FAA) for the National Airspace System (NAS) Ground-to-Ground Protocol Converter (GPC)
System. This specification cites Government and non-Government standards, orders,
handbooks, and other pertinent documents to ensure the GPC System will possess the
necessary functional performance and interface requirements essential to the NAS.
1.2 Document Overview
Section 1 (this section) describes the scope of this specification, gives an overview of this
specification, and gives an overview of the GPC System. It is intended to be descriptive in
nature and contains no binding requirements.
Section 2 lists the documents that are cited within subsequent sections as a part of binding
requirements.
Section 3 lists system requirements, which includes references to Interface Requirements
Documents (IRD) where applicable.
Section 4 contains verification requirements.
Section 5 lists Acronyms and Abbreviations.
Section 6 provides a Glossary.
1.3 System Overview
Figure 1-1 shows a high-level, conceptual system diagram with the proposed elements of the
FAA’s planned Voice over IP Communication Enterprise (VoICE) shaded in blue. This
specification covers the Ground-to-Ground Protocol Converter (GPC) element, where the GPC
is utilized to translate voice and signaling between the FAA’s legacy Ground-to-Ground (G/G)
interfaces and VoIP (ED-137) G/G interfaces.
SECTION 1: INTRODUCTION
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
2
Figure 1-1. Conceptual System Diagram of the FAA’s VoICE
ED-137
Telephone
Protocol
A/G
Protocol
Converter
Legacy
A/G
Interface
A/G
Protocol
Converter
ED-137
Radio
Protocol
Notes:
1. Protocol Converters can be
placed where Legacy Analog
Interfaces reside and an IP
connection is available.
2. If any analog interfaces reside
at a VoIP VCS facility, Protocol
Converters can also be placed
there.
3. For G/G Protocol Converters,
the Legacy VCS box could also
represent Legacy Telephone
Circuits (e.g. On Airport Phone
Systems/Analog Circuits).
ED-137
Radio
Protocol
ED-137
Telephone
Protocol
VoIP Voice Communication
Systems (VCS s)
A/G
Protocol
Converter
G/G
Protocol
ConverterED-137
Radio
Protocol
ED-137
Telephone
ProtocolG/G
Protocol
Converter
Legacy
VCSsPoint-to-Point
Legacy G/G Trunk
ED-137
Radio
Protocol
Legacy
G/G
Interface
Legacy
A/G
Interface
Point-to-Point
Legacy A/G Trunk
Legacy
Radios
(up to 8)
Legacy
A/G
Interface
Legacy
Radios
(up to 8)
A/G
Protocol
Converter
ED-137
Radio
Protocol
ED-137
Radio
Protocol
IP
Radios
(up to 8)
A/G
Protocol
Converter
A/G
Protocol
Converter
ED-137
Radio
Protocol
Legacy A/G
Interface
Legacy
Local
Radio
Legacy
VCSs
Legacy
VCSs
Legacy
A/G
Interface
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
3
2 APPLICABLE DOCUMENTS The following documents form a part of this specification to the extent specified herein. In case
of any discrepancy between these documents and specific requirements of this specification,
this specification must be considered the superseding document unless otherwise directed by
the government.
Copies of government documents may be obtained as directed by the contracting officer.
Copies of non-government documents are generally available in technical libraries or may be
obtained from their originators.
When the requirements of this document and referenced applicable documents are in
conflict, this document has precedence over all documents referenced herein.
If either two or more referenced applicable documents are in conflict or two or more sections
of this document are in conflict, the GPC System program office must be notified to resolve the
conflict.
2.1 Government Documents
2.1.1 Specifications
a. FAA-G-2100H, Electronic Equipment, General Requirements (May 9, 2005).
2.1.2 Standards
a. HF-STD-001B, Human Factors Design Standard (December 30, 2016).
b. FAA-STD-019f, Lightning and Surge Protection, Grounding, Bonding and Shielding
Requirements for Facilities and Electronic Equipment (October 18, 2017).
c. MIL-STD-461G, Requirements for the Control of Electromagnetic Interference
Characteristics of Subsystems and Equipment (December 11, 2015).
d. MIL-STD-1472G, Human Engineering (January 17, 2019).
e. FAA-STD-054, Use of Selective Signaling Standard for Voice Communication Systems,
March 12, 1996.
f. IEEE-STD-823-1989, Methodologies for Specifying Voice Grade Channel Transmission
Parameters and Evaluating Connection Transmission Performance for Speech Telephony.
2.1.3 Other FAA Documents
a. FAA Order 8040.4B, Safety Risk Management (May 2, 2017).
SECTION 2: APPLICABLE DOCUMENTS
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
4
b. FAA Order 3900.19C, Occupational Safety and Health Policy (March 11, 2019).
c. TBD, GPC to Analog Interphone Interface Requirements Document (IRD).
d. TBD, GPC System to FAA Facility Power Interface Requirements Document (IRD).
e. TBD, GPC System to Government Transport System (GTS) Interface Requirements
Document (IRD).
2.1.4 Federal Regulations
a. Title 29 CFR Part 1910, Occupational, Safety and Health Standards.
b. Title 29 CFR Part 1926, Occupational Safety and Health Administration, Labor.
c. Title 47 CFR Part 15, Radio Frequency Devices.
d. Title 47 CFR Part 68, Federal Communications Commission Description of Standard
Regulations Program Connection Configuration.
e. FPMR 101-42, Utilization and Disposal of Hazardous Materials and Certain Categories of
Property.
2.1.5 Other Federal Documents
a. MIL-HDBK-454B, General Guidelines for Electronic Equipment (April 15, 2007).
2.2 Non-Government Documents
a. ANSI/IPC-T-50M, American National Standards Institute (ANSI) Terms and Definitions
for Interconnecting and Packaging Electronic Circuits (May 2015).
b. ANSI/TIA-464-C, Telecommunications - Multiline Terminal Systems - Requirements for
Private Branch Exchange (PBX) Switching Equipment, October 2002, with Addendum 1
June 2004.
c. EUROCAE Document ED-137C Interoperability Standards for VoIP ATM Components
Volume 2: Telephone (March 2019).
d. EUROCAE Document ED-137C Interoperability Standards for VoIP ATM Components
Addendum 2 to Volume 2: FAA Legacy Telephone Interworking (March 2019).
e. IEC 61000-4-2 ed2.0 b:2008, Electromagnetic Compatibility (EMC) – Part 4-2 Testing and
Measurement Techniques – Electrostatic Discharge Immunity International
Electromechanical Commission (December 9, 2008).
f. IPC-2221B, Generic Standard on Printed Board Design (November 2012).
g. ITU-T Recommendation P.862, Perceptual Evaluation of Speech Quality (PESQ): An
objective method for end-to-end speech quality assessment of narrow-band telephone
networks and speech codecs (February 2001).
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
5
h. ITU-T Recommendation P.862.1, Mapping function for transforming P.862 raw result
scores to MOS-LQO (November 2003).
i. NFPA 70, National Electrical Code (NEC), National Fire Protection Association (2020).
j. NFPA 70E, Standard for Electrical safety in the workplace (2018).
k. GR-63-CORE, NEBS Requirements: Physical Protection, Issue 5 (December 2017).
l. IEC 60950-1, Information Technology Equipment - Safety - Part 1: General Requirements,
2.2 Edition, May 2013.
m. RFC 2544, Benchmarking Methodology for Network Interconnect Devices, March 1999.
n. RFC 3261, SIP: Session Initiation Protocol, June 2002.
o. RFC 3372, Session Initiation Protocol for Telephones (SIP-T): Context and Architectures,
September 2002.
p. RFC 3398, Integrated Services Digital Network (ISDN) User Part (ISUP), to Session
Initiation Protocol (SIP) Mapping, December 2002.
q. ITU-T Recommendation G.711 – Pulse Code Modulation (PCM) of Voice Frequencies,
November 1988.
r. ITU-T Recommendation G.729 – Coding of speech at 8Kbit/s using conjugate structure
algebraic-code-excited linear-prediction (CS-ACELP), Annex A: Reduced complexity
8Kbit/s CS-ACELP speech codec, June 2012.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
6
3 REQUIREMENTS The Ground-to-Ground Protocol Converter (GPC) System is comprised of two (2) fundamental
elements, the Ground-to-Ground Protocol Converter (GPC) and the GPC Management
Subsystem (GPCMS), which are highlighted in blue in Figure 3-1. The Focus element (or GPC
Focus) is applicable to certain configurations as specified herein. A GPC System can contain
multiple GPC elements and multiple GPC Focus elements (Foci). The GPCMS contains the
Local Manager and the GPC Network (LAN) equipment for the GPC System.
The GPC System will support interfaces for Ground-to-Ground communications that provide
protocol translation between Legacy Voice Communication Systems (VCSs), Legacy G/G Trunk
Resources, and Voice over IP (VoIP) VCSs.
GPCMS
Local
Manager
GPC
Network
Legacy
VCS
VoIP
VCS
Legacy
G/G
Trunks
*GPC*Focus
(As Applicable)
*Note: A GPC System
can contain multiple
GPCs and multiple GPC
Foci (as applicable)
Figure 3-1. GPC System Functional Diagram
Each GPC has one analog interface to a Legacy G/G Trunk and one VoIP interface to a user
agent, termed the Destination User Agent, in accordance with ED-137C Volume 2, Addendum 2.
The Destination User Agent may be a Controller Working Position (CWP), gateway, or Focus. A
Focus can be internal to the GPC System, referred to as a GPC Focus, or external and hosted by
SECTION 3: REQUIREMENTS
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
7
a VoIP VCS, referred to as a VoIP VCS Focus. The requirements included in this document only
pertain to components within the GPC System.
The GPC VoIP interface will support one ED-137C Volume 2 Addendum 2 call type to the
Destination User Agent. In the event that the Destination User Agent is functioning as a GPC
Focus, the Focus will operate in accordance with ED-137C Volume 2 Addendum 2.
Requirements within this document will take precedence over similar, or conflicting
requirements included in a referenced section of the ED-137C documents.
The GPC will operate in three configurations. GPC Configuration #1 will provide “End-to-End
IP Connectivity” to Legacy VCSs. As shown in Figure 3-2, this configuration will support GPC
to GPC communications, via VoIP connectivity. The GPCs will be local to the Legacy VCS
facilities and provide the required analog interfaces to the Legacy VCSs.
Figure 3-2. GPC Configuration #1 - End-to-End IP Enabling of Legacy VCSs
GPC Configuration #2 will provide “IP Enabling” to a Legacy VCS. As shown in Figure 3-3, the
GPC is local to a Legacy VCS and is connected to the analog interface of the VCS. IP
connectivity provided by the GPC in this application will provide a Legacy VCS access to the
Wide Area Network (WAN) for communicating with a VoIP VCS.
GPC
RX Audio
TX Audio
Legacy
VCS
Legacy Voice Switch Facility
ED-137C
Analog Voice &
Signaling
GPC
TX Audio
RX Audio
Legacy
VCS
Legacy Voice Switch Facility
Analog Voice &
Signaling
ED-137C
Signaling Signaling
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
8
Figure 3-3. GPC Configuration #2 - IP Enabling to a Legacy VCS
GPC Configuration #3 will provide “Analog Enabling” to a VoIP VCS. As shown in Figure 3-4,
the GPC is local to a VoIP VCS and is connected to an analog trunk leaving the facility. Analog
connectivity provided by this GPC configuration will provide access to a Legacy VCS.
Figure 3-4. GPC Configuration #3 - Analog Enable IP VCS
The requirements written in this specification as “GPC” apply to all configurations of the GPC.
In addition, any system requirements that apply to more than just the GPC will be written as
“GPC System”.
GPC
RX Voice
TX Voice
Legacy
VCS
Legacy VCS Facility
ED-137C
VoIP (ED-
137)
VCS
ED-137C
Signaling
Analog Voice &
Signaling
GPC
RX Audio
TX Audio
VoIP (ED-
137C) VCS
Analog Voice &
Signaling
Legacy
VCS
VoIP VCS Facilty
ED-137C
Signaling
Analog Voice &
Signaling
RX Audio
TX Audio
Signaling
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
9
3.1 Functional Requirements
Note: For all requirement references to sections of the ED-137 documents, refer to the ED-
137 Clarification Matrix in the appendix of this specification for specific applicability of
each requirement (ED-137 Clarification Matrix will be provided in a later release of this
Specification).
a. The GPC must translate between a single VoIP interface and a single analog interface (voice
and signaling).
b. The GPC must meet the requirements for interfacing with a SIP User Agent in accordance
with ED-137C Volume 2 Addendum 2.
c. The GPC must meet the requirements for interfacing with a Legacy VCS (GPC analog
interface) in accordance with the GPC to Analog Interphone IRD.
d. The GPC must support only one analog interface to a Legacy G/G Trunk and only one VoIP
interface to a Destination User Agent.
3.1.1 GPC Call Functions
This section covers the GPC requirements for the messaging and signaling necessary for each
call type.
a. The GPC must, when a conference capability is required, support configuration with a Focus
as the Destination User Agent.
b. The GPC must, for GPC to GPC communications at the VoIP Interface, support a GPC as the
Destination User Agent.
c. The GPC must, for GPC to GPC communications at the VoIP interface, only accept call
establishment requests from the configured Destination User Agent (GPC).
d. The GPC must subscribe as a called party to a configured Focus in accordance with section
6.1.1 of ED-137C Volume 2.
e. The GPC must support State and Membership Notifications through incoming subscriptions
in accordance with section 4.2.2 of ED-137C Volume 2 Addendum 2.
f. The GPC must subscribe to the configured Focus in accordance with section 6.8 of ED-137C
Volume 2, to receive Conference and Call State Notifications.
g. The GPC must, upon receipt of signaling or call progress tone at the analog interface (in
accordance with Table 3-2), send the corresponding RTP Event Code at the VoIP interface in
accordance with Table 3-1.
h. The GPC must, upon receipt of an “Off Hook” RTP Event from the Focus, stop sending
Ringback call progress tone in accordance with section 3.1.2.4.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
10
i. The GPC must, when Caller ID is received at the Analog Interface, send Caller ID at the
VoIP Interface using standard SIP messaging for mid-call transactions in accordance with
RFC 3372 and RFC 3398.
j. The GPC must support Caller ID in accordance with GPC Analog Interphone IRD section
3.2.2.6.
Table 3-1. RTP Events
Signaling/Call
Progress Tones
Event Name RTP Event Code
Address Signaling DTMF digits “0-9” 0-9
DTMF digit “*” 10
DTMF digit “#” 11
DTMF digits “A-D” 12-15
Signaling Hook/Flash 16
Ring On 19
Ring Off 20
Off Hook1 64
Call Progress
Tones
Dial Tone 66
Ringing/Ringback Tone 70
Busy Tone 72
Hold 76
Recorder Warning Tone 83
Override 248
Trunk Busy/ Reorder
Tone,
Error/ Prohibited
249
Trunk Lockout1 250
Notes:
1. RTP Events are in addition to what is in section 4.2.3 of
ED-137C Volume 2 Addendum 2.
3.1.1.1 Dial Selective Call Function
FAA Dial Selective calls utilize address signaling to selectively communicate between multiple
positions on an analog trunk. The GPC’s Dial Selective Call Function will include receiving RTP
Event address digits from a VoIP user agent and relaying them at the analog interface.
Conversely, the GPC will also be capable of receiving analog address digits at the analog
interface and establish RTP connectivity directly with the dialed endpoint or relay the received
digits to a Focus.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
11
a. The GPC must support Dial Selective calls in accordance with section 5.0 of ED-137C
Volume 2 Addendum 2.
3.1.1.1.1 VoIP VCS Initiated Dial Selective Call
a. The GPC must, upon call establishment with the Destination User Agent for Dial Selective
calls, initiate the call at the analog interface in accordance with section 3.1.2.
b. The GPC must, upon receipt of a "Pause" character (*) RTP Event (per Table 3-1) in the
dialing sequence at the VoIP interface, pause dialing at the Analog Interface until the pause
timer expires.
c. The GPC must permit configuration of the pause timer, from 1 to 180 seconds in increments
of 1 second (TBR).
d. The GPC must, upon receipt of a "Wait" character (#) RTP Event (per Table 3-1) in the
dialing sequence at the VoIP interface, suspend dialing at the Analog Interface until a trigger
is detected. Note: Trigger includes, as a minimum, detection of dial tone, Wink, or off-
hook at the Analog Interface.
3.1.1.1.2 Legacy VCS Initiated Dial Selective Call
a. The GPC must, upon call initiation at the analog interface for Dial Selective calls, establish
two-way RTP connectivity with a Focus in accordance with standard SIP messaging methods
detailed in RFC 3261.
b. The GPC must, upon receipt of call address digits at the analog interface for Dial Selective
calls, send call address signaling digits as RTP Events to the connected Focus, in accordance
with section 4.2.4 of ED-137C Volume 2 Addendum 2.
c. The GPC must, upon receipt of a legacy initiated Dial Selective call, send Ringback call
progress tone in accordance with section 3.1.2.4 at the analog interface until the call is
answered or abandoned.
3.1.1.1.3 GPC to GPC Dial Selective Call
a. The GPC must, upon call initiation at the analog interface for Dial Selective GPC to GPC
communication, establish two-way RTP connectivity with the GPC Destination User Agent
in accordance with standard SIP messaging methods detailed in RFC 3261.
b. The GPC must, upon inbound call establishment with at the VoIP interface for Dial Selective
GPC to GPC communication, initiate the call at the analog interface in accordance with
section 3.1.2.
c. The GPC must, upon receipt of call release signaling at the analog interface for Dial
Selective GPC to GPC communication, terminate the call at the VoIP interface.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
12
d. The GPC must, upon call termination at the VoIP interface for Dial Selective GPC to GPC
communication, send call release signaling at the analog interface.
e. The GPC must, upon receipt of call address digits at the analog interface for Dial Selective
GPC to GPC communication, send call address signaling digits as RTP Events at the VoIP
interface.
3.1.1.2 Selective Signaling Function
FAA Legacy Selective Signaling (SS) circuits/trunks, as shown in Figure 3-5, are conferenced
together utilizing a centralized analog bridge. Each SS analog trunk is configurable to use
selective dialing and/or voice signaling with a required conference capability. The analog bridge
relays received audio and/or SS digits over each connected legacy analog trunk. Each called
operator is notified of an incoming call by visual and audible indications in accordance with
VCS specifications. Supervisory signaling is not supported with SS calls. Further details
regarding legacy SS circuit operation are available in FAA-STD-054.
Analog
Bridge
Legacy
VCSLegacyTrunk
Legacy
VCSLegacyTrunk
Legacy
VCSLegacyTrunk
Legacy
VCSLegacyTrunk
Figure 3-5. Existing FAA Legacy SS Circuit with Analog Bridge
There are three applications that the GPC System will support for SS and are dependent upon the
FAA’s migration plans for SS, which will be determined later. In the first application, as shown
in Figure 3-6, the GPC will be integrated with a VoIP VCS for access to an existing analog
bridge.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
13
VoIP VCS
CWPLegacy
VCSLegacy
Trunk
Legacy
VCSLegacy
Trunk
Legacy
Trunk
ED-137C
Telephone
Protocol
Analog
Bridge
CWP
VoIP VCS
CWP CWP
Focus
ED-137C
Telephone
Protocol
GPC
Figure 3-6. GPC Application for SS with Analog Bridge
In the second application, as shown in Figure 3-7, the GPC System will provide a GPC Focus to
host the circuit, replacing the existing analog bridge. The GPC will provide connectivity for a
Legacy VCS to the GPC Focus. In this application, the GPC Focus will act as the centralized
point of the circuit, hosting communications directly to/from multiple Legacy VCSs via GPCs.
Legacy
VCSLegacy
TrunkGPC
ED-137C
Telephone
Protocol
Legacy
VCSLegacy
TrunkGPC
ED-137C
Telephone
Protocol
Legacy
VCSGPC
ED-137C
Telephone
Protocol
Legacy
VCSGPC
ED-137C
Telephone
Protocol
GPC
Focus
Legacy
Trunk
Legacy
Trunk
Figure 3-7. GPC Application for SS with GPC Provided Focus
In the third application, as shown in Figure 3-8, a VoIP VCS will provide a Focus to host the SS
group. This application occurs when a VoIP VCS is added to an SS group requiring a Focus. A
GPC Focus will not be utilized when a VoIP VCS is part of an SS Group. In this application, the
VoIP VCS Focus will host communications directly to/from multiple CWPs and multiple Legacy
VCSs, via GPCs.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
14
VoIP VCS
VoIP VCS
CWP
Legacy
VCSLegacy
Trunk
Legacy
VCSLegacy
Trunk
CWP
CWP
CWP
Focus
ED-137C
Telephone
Protocol
ED-137C
Telephone
Protocol
GPC
GPC
ED-137C
Telephone
Protocol
VoIP VCSCWP
CWP
ED-137C
Telephone
Protocol
Figure 3-8. GPC Application for SS with VoIP VCS Focus
a. The GPC must support SS calls in accordance with section 6.0 of ED-137C Volume 2
Addendum 2. Note: Subsection 6.4 of ED-137C Volume 2 Addendum 2 does not apply to
this requirement and is identified as N/A in the ED-137 Clarification Matrix found in
the appendix of this specification (ED-137 Clarification Matrix will be provided in a
later release of this Specification).
b. The GPC must, for SS calls, support a Focus as Destination User Agent.
c. The GPC System must, for SS calls, provide the option for a GPC Focus that supports SS
calls in accordance with section 4.2 of ED-137C Volume 2.
d. The GPC System must, for SS calls, support at least 40 GPC Focus elements, one for each SS
circuit.
e. The GPC must, for SS calls, establish a Gateway Pre-connection to the configured Focus in
accordance with section 8.3 of ED-137C Volume 2 Addendum 2.
f. The GPC Focus must, for SS calls, support simultaneous communications with at least 15
GPCs.
g. The GPC Focus must, for SS calls, operate in accordance with section 6.6 of ED-137C
Volume 2.
h. The GPC Focus must, for SS calls, support dynamic Focus Group Member List creation in
accordance with section 6.1.1 of ED-137C Volume 2.
i. The GPC Focus must, for SS calls, support sending and receiving RTP Events in accordance
with section 4.2.3 of ED-137C Volume 2 Addendum 2.
j. The GPC must, for a SS analog interface, prohibit generating busy tone at the analog
interface.
k. The GPC must, for a SS analog interface, prohibit generating ringback tone at the analog
interface.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
15
3.1.1.2.1 Voice Initiation
All endpoints configured to support voice signaling on a SS circuit will have constant audio
connectivity to the host of the circuit (Focus or Analog Bridge). When audio is sent to the host of
a SS circuit, it will be relayed to all active audio connections (RTP pre-connections and analog
trunks). A GPC receiving audio at the analog interface will relay that audio at the VoIP interface,
and vice versa. Call answer is signified by the receipt of response audio sent by the answering
position.
a. The GPC Focus must, upon receipt of voice page audio for SS calls, distribute the voice page
audio to all connected GPCs, excluding the GPC from which it received the audio.
3.1.1.2.2 SS Digit Initiation
a. The GPC Focus must, upon receipt of a SS call address digit RTP Event from a GPC, relay
the call address digit RTP Event to all connected GPCs in accordance with section 4.2.3 of
ED-137C Volume 2 Addendum 2, excluding the GPC from which it received the digits.
b. The GPC must support receipt and relay of SS call address digits on an active SS call to
request another user join the call.
c. The GPC Focus must support receipt and relay of SS call address digits on an active SS call
for requesting another user join the call.
3.1.1.3 Non-Selective Call Function
FAA Non-Selective calls provide point-to-point communications without address signaling. A
Non-Selective Call initiated by a Legacy VCS to the GPC results in the GPC establishing RTP
connectivity to a preconfigured called party, consisting of either a CWP, Focus, or another GPC.
A Non-Selective Call initiated by a VoIP VCS to the GPC results in the GPC establishing
connectivity to the legacy VCS.
a. The GPC must support Non-Selective calls in accordance with section 7.0 of ED-137C
Volume 2 Addendum 2.
3.1.1.3.1 VoIP VCS Initiated Non-Selective Call
a. The GPC must, upon call establishment with the Destination User Agent for Non-Selective
calls, initiate the call at the analog interface in accordance with section 3.1.2 of this
specification.
3.1.1.3.2 Legacy VCS Initiated Non-Selective Call
a. The GPC must, upon call initiation at the analog interface for a Non-Selective call, establish
two-way RTP connectivity with the configured Focus.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
16
b. The GPC must, upon Manual Ring (re-ring) signaling at the analog interface for a Non-
Selective call, send a Ring On RTP Event in accordance with section 4.2.3 of ED-137C
Volume 2 Addendum 2.
c. The GPC must, upon termination of Manual Ring (re-ring) signaling at the analog interface
for a Non-Selective call, send a Ring Off RTP Event in accordance with section 4.2.3 of ED-
137C Volume 2 Addendum 2.
3.1.1.3.3 GPC to GPC Non-Selective Call
a. The GPC must, upon call initiation at the analog interface for Non-Selective GPC to GPC
communication, establish two-way RTP connectivity with the GPC Destination User Agent
in accordance with standard SIP messaging methods detailed in RFC 3261.
b. The GPC must, upon inbound call establishment at the VoIP interface for Non-Selective
GPC to GPC communication, initiate the call at the analog interface in accordance with
section 3.1.2.
c. The GPC must, upon receipt of call release signaling at the analog interface for Non-
Selective GPC to GPC communication, terminate the call at the VoIP interface.
d. The GPC must, upon call termination at the VoIP interface for Non-Selective GPC to GPC
communication, send call release signaling at the analog interface.
3.1.1.4 Voice Function
FAA Voice calls pass initiating user audio immediately to the respective destination, typically
routed to a CWP loudspeaker as a voice page. A receiving user can answer an incoming voice
page to begin a two-way conversation. To support this functionality, the GPC will establish and
maintain two-way RTP connectivity to a statically, preconfigured Focus hosted by a VoIP VCS.
This will enable the GPC to distribute audio sent by an initiating CWP from a Legacy VCS
through a VoIP VCS Focus to the endpoints (and in the opposite direction) without truncating
voice audio.
a. The GPC must support Voice calls in accordance with section 8.0 of ED-137C Volume 2
Addendum 2.
b. The GPC must, for Voice call GPC to GPC communication, establish a Gateway Pre-
connection with the GPC Destination User Agent. Note: The Gateway Pre-connection is
established between both GPCs and remains active indefinitely prior to any voice call
initiation by the Legacy VCS.
3.1.1.5 Override Function
FAA Override calls are higher priority, non-selective calls that are auto-answered at the far end.
The call being placed results in connection to the called party, even if the called position has an
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
17
active call in progress. The GPC will be preconfigured with a Destination User Agent that could
be a CWP or VoIP VCS Focus. The GPC will establish and maintain RTP connectivity with the
Destination User Agent.
a. A GPC must support Override calls in accordance with section 9.0 of ED-137C Volume 2
Addendum 2.
3.1.1.5.1 VoIP VCS Initiated Override Call
a. The GPC must, upon call establishment with the Destination User Agent for Override calls,
initiate the call at the analog interface in accordance with section 3.1.2 of this specification.
3.1.1.5.2 Legacy VCS Initiated Override Call
a. The GPC must, upon call initiation at the analog interface for Override calls, establish two-
way RTP connectivity with the configured destination user agent. Note: The destination
user agent may be either a CWP or VoIP VCS Focus.
3.1.1.5.3 GPC to GPC Override Call
a. The GPC must, upon call initiation at the analog interface for Override GPC to GPC
communication, establish two-way RTP connectivity with the GPC Destination User Agent
in accordance with standard SIP messaging methods detailed in RFC 3261.
b. The GPC must, upon inbound call establishment at the VoIP interface for Override GPC to
GPC communication, initiate the call at the analog interface in accordance with section 3.1.2.
c. The GPC must, upon receipt of call release signaling at the analog interface for Override
GPC to GPC communication, terminate the call at the VoIP interface.
d. The GPC must, upon call termination at the VoIP interface for Override GPC to GPC
communication, send call release signaling at the analog interface.
3.1.2 GPC Analog Signaling Function
a. Reserved.
3.1.2.1 Supervisory Signaling
Supervisory signaling includes E&M, Loop, SF, and Duplex (DX) signaling configurations.
3.1.2.1.1 E&M Supervisory Signaling
GPC E&M supervisory signaling is configurable for Type I, II, or V, supporting either dial
selective or non-selective calls.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
18
a. The GPC must, for Dial Selective calls, support E&M supervisory signaling in accordance
with section 3.2.2.1 of the GPC to Analog Interphone IRD.
b. The GPC must, for Non-Selective calls, support E&M supervisory signaling in accordance
with section 3.2.2.1 of the GPC to Analog Interphone IRD.
c. The GPC must support E&M Type I signaling in accordance with sections 3.2.2.1, 3.2.2.3.4
and 3.2.2.4.4 of the GPC to Analog Interphone IRD.
d. The GPC must support E&M Type II signaling in accordance with sections 3.2.2.1, 3.2.2.3.4
and 3.2.2.4.4 of the GPC to Analog Interphone IRD.
e. The GPC must support E&M Type V signaling in accordance with sections 3.2.2.1, 3.2.2.3.4
and 3.2.2.4.4 of the GPC to Analog Interphone IRD.
f. The GPC must support E&M call procedures in accordance with section 3.2.1 of the GPC to
Analog Interphone IRD.
3.1.2.1.2 Loop Supervisory Signaling
Loop supervisory signaling is configured for either ground start or loop start with 20 Hz ring
signaling, for dial selective and non-selective calls.
a. The GPC must, for Dial Selective calls, support Loop supervisory signaling in accordance
with section 3.2.2.1 of the GPC to Analog Interphone IRD.
b. The GPC must, for Non-Selective calls, support Loop supervisory signaling in accordance
with section 3.2.2.1 of the GPC to Analog Interphone IRD.
c. The GPC must support Ground Start call procedures in accordance with section 3.2.1 of the
GPC to Analog Interphone IRD.
d. The GPC must support Loop Start call procedures in accordance with section 3.2.1 of the
GPC to Analog Interphone IRD.
e. The GPC must upon receiving a Hook/Flash RTP event on the VoIP interface per Table 3-1,
generate Hook Flash signaling on the analog interface in accordance with GPC to Analog
Interphone IRD section 3.2.2.4.2.
3.1.2.1.3 Single Frequency (SF) Supervisory Signaling
Single Frequency (SF) supervisory signaling for Non-selective calls is configured for either
Tone-on-Idle (TOI), Tone-on-Active (TOA), or Tone Burst (TB). Dial selective calls only use
TOI.
a. The GPC must, for Dial Selective calls, support SF-TOI supervisory signaling in accordance
with section 3.2.2.3.5 and 3.2.2.4.5 of the GPC to Analog Interphone IRD.
b. The GPC must, for Non-Selective calls, support SF-TOI supervisory signaling in accordance
with section 3.2.2.3.5 and 3.2.2.4.5 of the GPC to Analog Interphone IRD.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
19
c. The GPC must, for Non-Selective calls, support SF-TOA supervisory signaling in
accordance with section 3.2.2.3.5 and 3.2.2.4.5 of the GPC to Analog Interphone IRD.
d. The GPC must, for Non-Selective calls, support SF-TB supervisory signaling in accordance
with section 3.2.2.3.5 and 3.2.2.4.5 of the GPC to Analog Interphone IRD
e. The GPC must support SF call procedures in accordance with section 3.2.1 of the GPC to
Analog Interphone IRD.
f. The GPC must support SF Tone Burst call procedures in accordance with section 3.2.1 of the
GPC to Analog Interphone IRD.
g. The GPC must, for Non-Selective calls, support Tone Burst signaling for manual re-ring
outbound at the analog Interface.
h. The GPC must, for Non-Selective calls, support Tone Burst signaling for manual re-ring
inbound at the analog Interface.
i. The GPC must, for Override calls, support SF-TOI supervisory signaling in accordance with
section 3.2.2.3.5 and 3.2.2.4.5 of the GPC to Analog Interphone IRD.
3.1.2.1.4 PABX Duplex Signaling (DX)
a. The GPC must, for Dial Selective calls, support Duplex (DX) supervisory signaling in
accordance with sections 3.2.2.3.6 and 3.2.2.4.6 of the GPC to Analog Interphone IRD.
3.1.2.2 Non-Supervisory Signaling
3.1.2.2.1 20 Hz Ring
20 Hz ring signaling for Non-Selective calls may be configured on both inbound and outbound
analog interfaces.
a. The GPC must, for Non-Selective calls, support 20 Hz ring signaling in accordance with
section 3.2.2.3.1 and 3.2.2.4.1 of the GPC to Analog Interphone IRD.
b. The GPC must support 20 Hz call procedures in accordance with section 3.2.1 of the GPC to
Analog Interphone IRD.
c. The GPC must, for 20 Hz ring signaling, support manual re-ring outbound at the analog
interface.
d. The GPC must, for 20 Hz ring signaling, support manual re-ring inbound at the analog
interface.
3.1.2.2.2 Voice Signaling
Voice signaling may be configured for Selective Signaling calls or Voice calls.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
20
a. The GPC must support voice signaling in accordance with section 3.2.2.3.3 and 3.2.2.4.3 of
the GPC to Analog Interphone IRD.
b. The GPC must support voice signaling call procedures in accordance with section 3.2.1 of
the GPC to Analog Interphone IRD.
c. The GPC must detect incoming voice levels at or above the specified voice activated switch
(VOX) detection threshold level specified in section 3.2.1.10.
d. The GPC must declare incoming trunk seizure when incoming trunk audio levels exceed the
VOX detection threshold for at least the configured VOX attack time specified in section
3.2.1.10.
3.1.2.3 Address Signaling
Address signaling for Dial Selective calls consists of DTMF and Dial Pulse (DP). In addition, the
GPC is configurable for wink start, immediate dial, or dial tone for signaling address digits. Dial
tone from the far end may or may not be provided for GPC outbound calls. For inbound calls,
generation of dial tone is a GPC configurable parameter.
a. The GPC must, for Dial Selective calls with Loop signaling, generate DTMF digits for
outbound calls in accordance with sections 3.2.2.2 and 3.2.2.4.2 of the GPC to Analog
Interphone IRD.
b. The GPC must, for Dial Selective calls with E&M signaling, generate DTMF digits for
outbound calls in accordance with sections 3.2.2.4.4 of the GPC to Analog Interphone IRD.
c. The GPC must, for Dial Selective calls with SF TOI signaling, generate DTMF digits for
outbound calls in accordance with section 3.2.2.2 of the GPC to Analog Interphone IRD.
d. The GPC must, for Dial Selective calls with SF TOI signaling, generate DP digits for
outbound calls in accordance with section 3.2.2.2 of the GPC to Analog Interphone IRD.
e. The GPC must, for Dial Selective calls with Loop signaling, detect DTMF digits for inbound
calls in accordance with sections 3.2.2.2 and 3.2.2.3.2 of the GPC to Analog Interphone IRD.
f. The GPC must, for Dial Selective calls with E&M signaling, detect DTMF digits for inbound
calls in accordance with section 3.2.2.3.4 of the GPC to Analog Interphone IRD.
g. The GPC must, for Dial Selective calls with SF TOI signaling, detect DTMF digits for
inbound calls in accordance with section 3.2.2.2 of the GPC to Analog Interphone IRD.
h. The GPC must, for Dial Selective calls with SF TOI signaling, detect DP digits for inbound
calls in accordance with section 3.2.2.2 of the GPC to Analog Interphone IRD.
i. The GPC must, for Dial Selective calls, support Senderize outbound address signaling by
accumulating all valid address digits before seizing the analog interface to transmit the digits.
j. The GPC must, for Dial Selective calls, support Cut-Through outbound address signaling by
transmitting each digit at the analog interface as received at the VoIP interface.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
21
k. The GPC must, for Dial Selective calls, support Wink Start signaling in accordance with
section 3.2.2.1 of the GPC to Analog Interphone IRD.
l. The GPC must, for Dial Selective calls, support Immediate Dial signaling in accordance with
section 3.2.2.1 of the GPC to Analog Interphone IRD.
m. The GPC must, for Immediate Dial signaling, permit adjustment for the start of address digit
transmission in the range from 70 to 1000 ms, in increments of 10 ms.
n. The GPC must, for Dial Selective calls, support Dial Tone in accordance with section 3.2.2.1
of the GPC to Analog Interphone IRD.
o. The GPC must, when glare is detected on the analog interface, allow the incoming seizure to
take precedence.
3.1.2.3.1 Addressing on Selective Signaling Trunks
Address signaling on the Legacy VCS Trunk interface consists of Selective Signaling (SS) digits.
Voice paging on the SS trunk does not preclude address digits from being dialed on the trunk.
a. The GPC must, for SS calls, generate SS address digits at the analog interface in accordance
with section 3.2.2.4.7 of the GPC to Analog Interphone IRD.
b. The GPC must, for SS calls, receive SS address digits from the analog interface in
accordance with section 3.2.2.3.7 of the GPC to Analog Interphone IRD.
c. The GPC must support Senderize outbound address signaling for SS calls.
d. The GPC must support Cut-Through outbound address signaling for SS calls.
e. The GPC must support audio Cut-Through operation for voice paging at the analog interface.
3.1.2.4 Call Progress Function
a. The GPC must support enabling and disabling of Call Progress Tones at the analog interface.
Note: Call Progress Tones are enabled/disabled as a group, not individually.
b. The GPC must, upon receipt of a RTP Event from the VoIP interface (in accordance with
Table 3-1), send the corresponding call progress tone at the analog interface in accordance
with Table 3-2.
c. The GPC must, for all call progress tones in Table 3-2, have a repetition pattern tolerance of
less than or equal to 10%.
d. The GPC must permit adjustment of the relative level of each call progress tone over a range
of +3 to -27dB from the nominal level.
e. The GPC must, for non-supervisory outbound/supervisory inbound signaling (e.g., FSX),
provide Error/Prohibited tone per Table 3-2 at the Analog Interface for ten (10) seconds if no
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
22
call termination signaling is received at the Analog Interface within 30 seconds of call release
at the VoIP Interface.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
23
Table 3-2. Call Progress and Signal Tones
Call Progress
and Signal Tones Hz (+/-0.5 Hz) Repetition
Pattern Nominal Level
Dial Tone 350+440 None, Steady
Tone -9 dBm0
Busy 480+620 500 ms on,
500 ms off
-19 dBm0
Ringback 440+480 .8 sec to 1.2
sec on, 2.7
sec to 3.3 sec
off
-15 dBm0
Override (OVR) 440 200 ms, once
at call
connection
-9 dBm0
Trunk Lockout 300+700 None, Steady
Tone
-19 dBm0
Trunk Busy 480+620 250 ms on,
250 ms off
-19 dBm0
Hold 480 50 ms on,
9950 ms off
-16 dBm0
Error/Prohibited
(Reorder)
480+620 250 ms. On,
250 ms off
-19 dBm0
Recorder Warning 1400 500 ms on,
14.5 s off
-16 dBm0
DTMF Digits: 0-9
*
#
A-D
Per ANSI/TIA-
464C, Sections
7.1.4 and 7.1.5
Per
ANSI/TIA-
464C,
Sections 7.1.4
and 7.1.5
-19dBm0
Notes: None
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
24
3.1.3 GPC Transition with VoIP VCS
TBD.
3.1.4 Security
Note: This section will be provided separately of this Specification.
3.1.5 Maintenance and Testing Functions
This section covers the functions for performing fault detection, diagnostics, testing, and
maintenance. The actual monitoring of these functions is covered in section 3.1.9, Status
Monitoring and Control.
3.1.5.1 Fault Detection
a. The GPC System must automatically perform system diagnostics during power up to detect
faults.
b. The GPC System must automatically perform system diagnostics during system operation to
detect faults.
c. The GPC System must ensure that fault detection does not interfere with system operations.
d. The GPC System must provide the option to disable fault detection when a GPC is brought
out of service for maintenance activities.
e. The GPC System must report all detected faults to designated workstations and to
maintenance log simultaneously.
f. The GPC System must ensure that data paths include error detection mechanisms to ensure
the integrity of received messages.
g. The GPC System must perform hardware fault and failure detection and isolation to the line
replaceable unit (LRU) level.
h. The GPC System must provide fault isolation through the designated use of automatic on-
line fault isolation, Built-in Test Equipment (BITE), and Built-in Test (BIT).
i. The GPC System must detect and identify on-line faults down to two or less LRUs in 95% of
all failures.
j. The GPC System must detect and identify on-line faults down to one module in 90% of all
failures. Note: Refer to Glossary for definition of module.
k. The GPC System must detect and identify all faults with a confidence of at least 99.9%.
l. The GPC System must automatically remove visual and audible alerts from all equipment
receiving the indication when the fault conditions are corrected.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
25
3.1.5.2 Diagnostics
a. The GPC System must permit designated workstations to initiate automatic diagnostic
testing.
b. The GPC System must permit designated workstations to initiate manual diagnostic testing.
c. The GPC System must provide diagnostics for self-testing, failure detection, and isolation in
the on-line mode.
d. The GPC System must permit designated workstations to conduct end-to end connectivity
diagnostic tests for legacy analog interfaces.
e. The GPC System must permit designated workstations to conduct end-to end IP quality
diagnostic tests for Ethernet based connections.
f. The GPC System must provide diagnostics for self-testing, failure detection, and isolation in
the off-line mode.
g. The GPC System must provide diagnostic test results to designated workstations.
h. The GPC System must permit printing of diagnostic test results by designated workstations.
3.1.5.3 Maintenance Workstation Function
a. The GPC System must provide maintenance workstations that support full capabilities of
maintenance function.
b. The GPC System must permit any workstation to be used to perform maintenance functions.
c. The GPC System must provide the maintenance function displays, alarms, and special test
equipment required for fault detection, fault localizing and system restoration.
d. The GPC System must permit workstations, alarms, displays and special test equipment to be
mounted in equipment racks.
e. The GPC System must permit the maintenance workstation function to request, control,
display, store, and transfer (to removable media) on-site system tests and test results.
f. The GPC System must provide a maintenance workstation function that permits the selection
of reports and displays based on the defined GPC System LRUs.
g. The GPC System must provide maintenance workstations that permit any authorized
maintenance user to perform the installation of required security patches, malicious code
signatures updates, and spam protection updates, whenever new releases are available.
h. The GPC System must provide maintenance workstations that allow an authorized
maintenance user to control when software/firmware updates are downloaded to the GPC
System.
i. The GPC System must provide maintenance workstations that allow an authorized
maintenance user to control when software/firmware updates are installed on the GPC
System.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
26
j. The GPC System must provide maintenance workstations that allow an authorized
maintenance user to update the Access Control List (ACL).
k. The GPC System must provide maintenance workstations that allow an authorized
maintenance user to update the Domain Name System (DNS) database.
l. The GPC System must provide maintenance workstations that allow an authorized
maintenance user to perform real-time configuration updates.
3.1.5.4 System Test Point Access
a. The GPC System must, for all GPC System equipment, provide test points in accordance
with FAA-G-2100H sections 3.2.4 and 3.3.5.1.9 to interconnect test equipment.
b. The GPC System must provide access for connecting test equipment to digital resources for
local and remote (if applicable) testing.
c. The GPC System must provide access for connecting test equipment to analog resources for
local and remote (if applicable) testing.
d. The GPC System must provide monitor access for connecting test equipment to digital
resources for local and remote (if applicable) testing.
e. The GPC System must provide monitor access for connecting test equipment to analog
resources for local and remote (if applicable) testing.
f. The GPC System must ensure that all test points are readily accessible without disassembly
of equipment.
g. The GPC System must provide Ethernet switches that support port mirroring.
3.1.5.5 Maintenance Logging Function
a. The GPC System must provide a maintenance log that contains the following information:
1. The GPC System must provide a maintenance log that contains faults detected by the
fault detection features.
2. The GPC System must provide a maintenance log that contains results of diagnostics
originated by a user.
3. The GPC System must provide a maintenance log that contains system restoration
activities.
4. The GPC System must provide a maintenance log that contains reconfiguration activities.
b. The GPC System must provide a time stamp for each entry in the maintenance log
synchronized with an external NTP time source.
c. The GPC System must time stamp entries in the maintenance log with a granularity of one
second.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
27
d. The GPC System must provide a maintenance log that is capable of storing at least 90 days
of maintenance history.
e. The GPC System must, when the maintenance log file storage limit is reached, overwrite the
oldest stored records.
f. The GPC System must prohibit the modification of system maintenance log entries.
g. The GPC System must provide a hard copy printout of the maintenance log upon request by
authorized maintenance personnel.
h. The GPC System must provide a soft copy file of the maintenance log upon request by
authorized maintenance personnel.
i. The GPC System must provide the soft copy log file in a method conducive to storage on
removable media.
j. The GPC System must provide the soft copy log file in a format compatible with Microsoft
Windows Office suite of products (.csv, .xls or similar).
k. The GPC System must provide the soft copy log file in such a format as to permit sorting and
searching of maintenance log entries.
3.1.6 Configuration
a. The GPC System must ensure that all reconfigurations are only performed by authorized
personnel at a designated workstation.
b. The GPC System must, for each GPC, provide the capability for a user to assign, modify, and
view a user-defined alphanumeric logical identifier string of at least 20 characters.
c. The GPC System must permit configurations of all parameters necessary for the GPC to
connect to any analog resource defined in this specification.
d. The GPC System must permit configurations of all parameters necessary for the GPC to
connect to any IP resource defined in this specification.
e. The GPC System must permit configurations of all GPC parameters such that the GPC can
update its IP Address.
f. The GPC System must ensure that the execution of configuration does not, in any way,
interrupt G/G communications in progress, except in the case that an individual GPC is being
configured and G/G communications is in progress at that GPC.
g. The GPC System must permit authorized personnel to force configuration of any GPC(s).
h. The GPC System must prevent remote users from making any changes to the local GPC
System via an IP connection.
i. The GPC System must permit authorized personnel to reset configuration of any GPC(s) to
factory default.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
28
3.1.6.1 Configuration Database
a. The GPC System must provide centralized storage of configuration data for its associated
facility. Note: This can be accomplished using one or more instances of a centralized
storage mechanism (e.g., an architecture using both an online and an offline database).
3.1.6.1.1 Configuration Database Management
a. The GPC System must permit authorized personnel access to the configuration database in
order to perform the following functions, at a minimum:
1. The GPC System must permit authorized personnel access to the configuration database
for modifying configuration data.
2. The GPC System must permit authorized personnel access to the configuration database
for storing configuration data.
3. The GPC System must permit authorized personnel access to the configuration database
for copying configuration data.
4. The GPC System must permit authorized personnel access to the configuration database
for deleting configuration data.
b. The GPC System must provide storage for management of the configuration database and
backups of the configuration database.
c. The GPC System must include a log of all changes made to the configuration database.
d. The GPC System must maintain the log of changes for each configuration database for a
minimum of 180 days without any loss of data.
e. The GPC System must include recovery utilities or procedures that allow authorized users to
recover a corrupted (or otherwise lost) configuration database.
f. The GPC System must define a set of configuration validation rules such that all configurable
parameters are checked against the range of their acceptable input, to include both the design
of the GPC System and the limits defined in this specification.
g. The GPC System must perform validation of all user-defined configuration changes against
the configuration validation rules.
h. The GPC System must ensure, prior to any configuration change being executed, that the set
of configuration changes being made at that time are a valid configuration per configuration
validation rules.
i. The GPC System must ensure that any error identified during the validation process is
reported to the workstation making the change(s).
j. The GPC System must prevent conflicts between multiple users simultaneously modifying
configuration data base.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
29
k. The GPC System must support manual backup of database by authorized personnel, such that
this backup can later be used to recover from a corrupted (or otherwise lost) configuration
data base.
l. The GPC System must support manual backup of configuration database by authorized
personnel to a soft copy file.
m. The GPC System must support manual configuration database restoral from a previously
saved backup by authorized personnel.
n. The GPC System must, in the case where multiple configuration data base repositories are in
use, provide a visual indication that identifies which configuration database is currently in
use.
o. The GPC System must permit the GPC System configuration to be backed up.
p. The GPC System must permit the GPC System configuration to be restored from a backup, to
facilitate the restoral of the GPC System from any corrupted/failed state within the GPC
System MTTR interval.
q. The GPC System must permit GPC configurations to be created off-line and downloaded to
the operational system as part of the configuration database.
r. The GPC System must permit authorized personnel to display the current physical
configuration of the GPC System.
s. The GPC System must permit authorized personnel to modify the configuration database to
classify each circuit installed in the system such that it starts up from the power off condition
in the online state.
t. The GPC System must permit authorized personnel to modify the configuration database to
classify each circuit installed in the system such that it starts up from the power off condition
in the maintenance state.
u. The GPC System must permit the development of physical configuration report defining the
hardware configuration of GPC System.
v. The GPC System must permit authorized personnel to print the entire delineated
configuration database structure with the current populated contents of each field.
3.1.6.2 Reconfiguration Items/Function
3.1.6.3 Configuration Set Creation and Editing
a. The GPC System must permit authorized personnel to create GPC configuration parameter
sets.
b. The GPC System must permit authorized personnel to modify GPC configuration parameter
sets.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
30
c. The GPC System must permit authorized personnel to store GPC configuration parameter
sets.
d. The GPC System must permit authorized personnel to delete GPC configuration parameter
sets.
e. The GPC System must permit authorized personnel to copy GPC configuration parameter
sets.
f. The GPC System must provide on-screen reports showing the content of GPC configuration
parameter sets.
g. The GPC System must permit authorized personnel to print reports showing the content of
GPC configuration parameter sets.
h. The GPC System must permit authorized personnel to “copy, cut and paste” procedures or
similar on-line aids to reduce repetitive data entry in assembling GPC configuration
parameter sets.
i. The GPC System must provide a soft copy file of GPC configuration parameter sets upon
request by authorized personnel through the workstation.
j. The GPC System must provide the GPC configuration data set on removable media format.
k. The GPC System must provide the GPC configuration data set in a format exportable to
Microsoft Windows Office suite of products.
l. The GPC System must permit GPC configuration parameter subsets to be applied to multiple
GPCs as applicable.
m. The GPC System must permit GPC configuration parameter subsets to be applied to
individual GPCs.
3.1.6.4 GPC System Configuration
a. The GPC System must continually retain the most recent configuration of each resource
indefinitely in non-volatile memory on the corresponding resource.
b. The GPC System must, upon restart of any resource, recover with the last configuration
loaded.
3.1.6.4.1 Invocation of Configuration
a. The GPC System workstation must permit authorized personnel to invoke GPC configuration
parameter sets.
b. The GPC System must, if the data sets are valid, initiate the configuration.
c. The GPC System must examine GPC configuration parameter sets before initiating them to
ensure that they are valid (e.g., file may be corrupted or may call for resources that are not
installed or are excluded from the physical configuration file).
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
31
d. The GPC System must, if errors are found, report them to the initiating operator and suspend
the configuration process without affecting any system resources, and prompt operator to
terminate or continue process.
e. The GPC System must ensure that any offline data set is validated prior to loading to GPC.
f. The GPC System must provide the configuration status to the initiating workstation and all
affected workstations.
g. The GPC System must prevent the interruption of service during configuration on those
GPCs and external interfaces not affected by the configuration.
3.1.6.4.2 Configuration Status
a. The GPC System must report the status of any configuration in process to the initiating
workstation.
b. The GPC System must, at a minimum, provide the following configuration status:
1. The GPC System must provide the configuration status, “Configuration Initiated”.
2. The GPC System must provide the configuration status, “Configuration In Progress”.
3. The GPC System must provide the configuration status, “Configuration Complete”.
4. The GPC System must provide the configuration status, “Configuration
Fault/Failure”.
5. The GPC System must provide the configuration status, “Configuration Resource
Violations”.
3.1.6.4.3 Recovery
a. The GPC System must permit the initiator of the configuration to initiate recovery
procedures.
b. The GPC System must permit other designated workstations to initiate recovery procedures.
c. The GPC System must permit the use of manual recovery methods to recover from any
failure of the configuration process.
3.1.6.4.4 Configuration Timing
a. The GPC System must include the time required to perform any on-line validation necessary
to ensure successful completion of the configuration in the measurement of configuration
times.
b. The GPC System must require no more than one minute to prepare configuration data,
measured from the time configuration is invoked by the operator to the time that the GPC
System requests the first GPC acknowledgment of configuration or to the time that the GPC
System performs the configuration, for resources that do not require acknowledgment.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
32
c. The GPC System must, unless otherwise configured, interrupt service for no more than two
seconds at each GPC being reconfigured, measured from the time the operator initiates
configuration to the time the new configuration is ready for use.
3.1.6.4.5 Simultaneous Configuration
a. The GPC System must ensure that simultaneous configurations of independent GPCs by a
single workstation is a configurable feature to prevent common component errors.
b. The GPC System must ensure that simultaneous configurations of the same GPCs are
prohibited.
3.1.6.4.6 Maintenance State Operations
a. The GPC System must permit authorized maintenance personnel to configure resource(s) to a
maintenance state, such that resources in a maintenance state are functionally segregated
from resources in an operational state.
b. The GPC System must permit authorized maintenance personnel to run diagnostics on a
resource in a maintenance state.
c. The GPC System must permit authorized maintenance personnel to individually assign the
maintenance state to redundant elements.
d. The GPC System must, when any device is in a maintenance state, suppress alarms but not
diagnostics.
e. The GPC System must permit authorized maintenance personnel to reinstate any device back
into service from a maintenance state.
f. The GPC System must, for any component with redundant network interfaces, permit
authorized maintenance personnel to individually enable/disable each network interface to
and from a maintenance state.
3.1.7 Time Source
a. The GPC System must have an internal time-of-day reference clock that maintains year,
month, day, hour, minute and second.
b. The GPC System must have an internal time-of-day reference clock that is configurable to
synchronize with a GFE GPS time system.
c. The GPC System must have an internal time-of-day reference clock that is configurable to
synchronize with a GFE Network Time Protocol (NTPv4) time system.
d. The GPC System must present all time in Universal Time Coordinated (UTC).
e. The GPC System must allow authorized maintenance personnel to manually set the time of
day for each GPC System component.
f. The GPC System must synchronize internal clocks within a period of no greater than every
24 hours with the GFE time system.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
33
g. The GPC System must synchronize all components to less than or equal to 100 ms of the
GFE time system.
h. The GPC System must ensure that each component maintains its own time-of-day in the
absence of the external time source input by having a maximum drift not to exceed 6 seconds
in a 24-hour period.
i. The GPC System must, upon power up, synchronize with the GFE time system within 2
minutes.
3.1.8 System Expansion
3.1.8.1 General Requirements
a. The GPC System must be expandable up to a maximum size of TBD GPCs.
b. The GPC System must be expandable in increments of one GPC at a time.
c. The GPC System must ensure that modules used to expand the system are connectorized.
d. The GPC System must be designed to allow trained government personnel using only
common tools, without wire wrap or soldering, to install expansion modules.
e. The GPC System must be designed to allow trained government personnel using only
common tools, without wire wrap or soldering, to remove expansion modules.
f. The GPC System must ensure that software changes are performed by only authorized
maintenance personnel.
g. The GPC System must ensure, to the extent that software changes are required to affect
system expansion, that they are limited to the editing or substitution of static data such as
maps, tables, or files, and not executable software.
h. The GPC System must ensure, to the extent that software changes are required to affect
physical configuration, that they are limited to the editing or substitution of static data such
as maps, tables, or files, and not executable software.
i. The GPC System must ensure, to the extent that software changes are required to affect
system size reduction, that they are limited to the editing or substitution of static data such as
maps, tables, or files, and not executable software.
j. The GPC System must, to the extent that software changes are required to affect system
expansion, permit software changes to be accomplished on site by authorized maintenance
personnel through configuration.
k. The GPC System must, to the extent that software changes are required to affect physical
configuration, permit software changes to be accomplished on site by authorized
maintenance personnel through configuration.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
34
l. The GPC System must, to the extent that software changes are required to affect system size
reduction, permit software changes to be accomplished on site by authorized maintenance
personnel through configuration.
m. The GPC System must require no more than 60 minutes of clock time for trained personnel
to install, excluding carpentry, cable pulling, administrative activities and logistical activities,
any expansion module.
n. The GPC System must require no more than 60 minutes of clock time for trained personnel
to remove, excluding carpentry, cable pulling, administrative activities and logistical
activities, any expansion module.
o. The GPC System must prohibit the process for installation of a GPC to restrict operations of
other GPCs.
p. The GPC System must prohibit the process for configuration of a GPC to restrict operations
of other GPCs.
q. The GPC System must prohibit the process for removal of a GPC to restrict operations of
other GPCs.
r. The GPC System must ensure that only resources in the offline state are permitted to be
removed from the data base through configuration.
s. The GPC System must ensure that each device installed in the GPC System initializes to an
offline mode.
3.1.8.2 Interfaces
a. The GPC System must permit authorized maintenance personnel to install new interface(s) in
the system for operational use through reconfiguration.
b. The GPC System must permit authorized maintenance personnel to remove interfaces
through reconfiguration.
3.1.9 Status Monitoring and Control
a. The GPC System must provide monitoring of real-time system status to designated
workstation(s).
b. The GPC System must provide reporting of system status and failures to designated
workstation(s).
c. The GPC System must ensure that the results from BIT and indication of equipment failures
are provided for display at the workstations authorized to receive the information.
d. The GPC System must monitor the health of data paths between the GPC System and
external systems, including alternate/backup data paths.
e. The GPC System must update system status at a minimum of every 15 seconds.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
35
f. The GPC System must provide aural and visual alarms indicating the failure status of
equipment and interfaces.
g. The GPC System must ensure that failures are categorized, prioritized, and stamped with
time of detection in terms of Universal Time Coordinated (UTC).
h. The GPC System must provide an indication at the workstation, when the workstation has
lost network connectivity.
i. The GPC System must provide a visual method at the workstation for users to determine that
the workstation has become unresponsive.
3.1.9.1 Event and Fault Lists
a. The GPC System must provide, for display to the user, an event list of the last 72 hours of
system events as described in Table 3-3
b. The GPC System must support, at a minimum, the event messages and severity assignments
defined in Table 3-3.
c. The GPC System must allow the names of the events listed in Table 3-3 to be configurable
by authorized personnel.
d. The GPC System must allow the severity assigned in Table 3-3 to be configurable by
authorized personnel.
e. The GPC System must permit authorized personnel to access the event list from any
workstation.
f. The GPC System must provide the display of the event list in chronological order.
g. The GPC System must permit authorized personnel to select which event classes (e.g.,
Critical, Major, or Minor) are displayed at any workstation.
h. The GPC System must permit authorized personnel to print the event list from any
workstation.
i. The GPC System must display event list information in summary form with each event
presented on a single line of the display, truncating any characters in the event message that
do not fit on a single line of the display.
j. The GPC System must display event list information in color coded format consistent with
fault severity classifications.
k. The GPC System must automatically and continuously update the event list such that the
most recent event appears at the top of the display unless a search or sort is in place.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
36
Table 3-3. GPC System Event Messages
NOTE: TABLE 3-3 IS PRELIMINARY
Event Message Severity
Startups
System Startup Major
GPCMS Startup Major
GPC Startup Major
Configuration
Configuration Initiated Major
Configuration Successful Major
Configuration Unsuccessful Critical
Configuration Completed with Errors Major
Configuration Cancelled Major
Modularity and Growth Major
Alarms/Alerts
Over-Temp Critical
Over-Temp Return to Normal Major
PTT Confirmation Timeout Major
Maintenance Log Overwrite Critical
Maintenance Log Status Major
Failure Critical
Equipment status change Major
Equipment recovery Minor
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
37
Event Message Severity
Placeholder for Each Type of
Protocol Converter
Logon/Logoff
Remote Logon/Logoff (in) Valid Major
Normal Logon/Logoff (in) Valid Major
Logon Denied Major
Logon Failed Major
Logoff Forced-New Operator Major
Logoff Forced-WS Off-line Major
Unauthorized Access Attempt Critical
Archive Status
Maintenance Log Major
Database Major
Security Event
Account Mgmt (creation, activation,
modification) Minor
Account Mgmt (creation, activation,
modification) Major
Login Denied Major
Login Limit Reached Major
Session Lock Major
Auto Logoff Minor
Access Denial Major
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
38
Event Message Severity
Administrator Actions Minor
Malicious Code Protection Major
Integrity Protection Major
Resource Degradation/Exhaustion Major
Audit Record Processing Failure Major
Audit Record Capacity Major
Notes:
1. The names of the events listed is the default and would be configurable by
authorized personnel.
2. The severity assigned is the default classification and would be configurable by
authorized personnel.
3.1.9.2 Alarms
a. The GPC System must provide audible and visible alarms to indicate the detection of event,
when an alarm was configured for that event.
b. The GPC System must provide volume adjustments for audible alarms (one volume
adjustment for each workstation or other location at which audible alarms occur).
c. The GPC System must permit audible alarms to be enabled and disabled by authorized
personnel, for each location at which audible alarms occur.
d. The GPC System must, upon automatic recovery of event, discontinue the audible alarm for
that specific event.
e. The GPC System must, upon automatic recovery of event, maintain the visual indication
until the event is acknowledged.
f. The GPC System must prohibit an audible alarm from being provided as notification of
automatic recovery of event.
g. The GPC System must allow audible alarms to be definable based on event severity.
h. The GPC System must provide audible and visible alarms to signal system overheat
conditions that would lead to equipment damage or fire.
i. The GPC System must provide the audible and visual alarms to the designated workstations.
j. The GPC System must permit authorized personnel to assign alarm status as critical, major or
minor to events.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
39
1. The GPC System must, for events classified as critical, provide a unique continuous
audible alarm and a visual indication.
2. The GPC System must, for events classified as major, provide a unique brief audible
alarm and a visual indication.
3. The GPC System must, for events classified as minor, provide a unique brief audible
alarm and a visual indication.
k. The GPC System must permit authorized personnel to silence the current critical alarm sound
without affecting the visual alarm or any future alarms.
l. The GPC System must require acknowledgement of the events classified as critical prior to
the halting of audible alarm, unless the event was tied to a failure that can automatically
recover.
m. The GPC System must require no acknowledgement of the events classified as major.
n. The GPC System must require no acknowledgement of the events classified as minor.
o. The GPC System must, upon acknowledgement by any workstation, silence the alarm(s) at
only that workstation.
p. The GPC System must support the use of IP based alarms (e.g., SNMP V3).
3.1.9.3 GPC Front Panel Controls and Indicators
TBD.
3.1.9.4 Traffic Data Collection and Analysis
a. The GPC System must provide online communication traffic data collection.
b. The GPC System must provide offline communication traffic data analysis.
c. The GPC System must ensure that communications traffic data collection, and analysis does
not interfere with or degrade the performance of any GPC System communication process.
d. The GPC System must collect communications traffic data that includes, at a minimum, the
following information:
1. The GPC System must collect communications traffic data that includes whether call was
blocked.
2. The GPC System must collect communications traffic data that includes whether call was
disconnected unexpectedly.
3. The GPC System must collect communications traffic data that includes call duration.
4. The GPC System must collect communications traffic data that includes call processing
times.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
40
e. The GPC System must provide formatted traffic data records using data coding containing, at
minimum, GMT and communication traffic information with a time-stamp accurate to within
0.01 second of the occurrence of the recorded event.
3.1.9.4.1 Traffic Data Collection
a. The GPC System must collect traffic data continuously as the events occur.
b. The GPC System must provide a traffic log that is capable of storing at least 45 days of
history.
c. The GPC System must, when the traffic log file storage limit is reached, overwrite the oldest
stored records.
d. The GPC System must provide a soft copy file of the traffic log upon request by authorized
personnel.
e. The GPC System must provide the soft copy log file on removable media format.
f. The GPC System must provide the soft copy log file in a format compatible with Microsoft
Windows Office suite of products.
3.1.10 Ground-to-Ground Protocol Converter Management Subsystem (GPCMS)
a. The GPCMS must be functionally independent of other GPC System fundamental elements,
such that the loss of the GPCMS or of GPCMS network connectivity will not impact the
operations of GPCs.
b. The GPCMS must be upgradeable without impacting operation of GPCs.
3.1.10.1 Performance Management
a. The GPCMS must provide network performance statistics for total bandwidth utilization of
each GPC System IP network interface.
b. The GPCMS must provide network performance statistics for latency between GPC and its
IP endpoint.
c. The GPCMS must provide network performance statistics for error counts for each individual
GPC IP connection.
d. The GPCMS must provide network performance statistics for redundancy path operational
status.
e. The GPCMS must provide network performance statistics for packet loss for each individual
GPC IP connection.
f. The GPCMS must provide validation of communication connectivity (i.e., ping) between all
defined GPC System devices to the GPCMS.
g. The GPCMS must provide a check of the ability of all defined GPC System devices to send
automatic status notifications, at a minimum of once per every two minutes.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
41
h. The GPCMS must perform capacity management in at least the following areas: Memory,
CPU, DSP, Disk Space, and Network Interface Controller (NIC) I/O.
i. The GPCMS must provide performance alerts, when any component exceeds a preconfigured
percent of utilization, in at least the following areas: Memory, CPU, DSP, Disk Space, and
Network Interface Controller (NIC) I/O.
j. The GPCMS must, for any component with redundant network interfaces, monitor and report
network traffic degradation on either interface during operations.
k. The GPCMS must, for any component with redundant network interfaces, provide
performance statistics of packets received on each interface.
l. The GPCMS must perform component polling, at a minimum of once per every two minutes,
in at least the following areas: Memory, CPU, DSP, Temperature, and Network Interface
Controller (NIC) I/O.
3.1.10.2 Account Management
a. The GPCMS must be capable of permitting an administrator to determine the level of access
to the GPC System functions.
3.1.10.3 Configuration Management
a. The GPCMS must monitor and assign all network access addresses to each network
component in the GPC System.
b. The GPCMS must assign a group of network access addresses for the GPC System.
c. The GPCMS must maintain a log of all available network access addresses that are
assignable to the GPC System.
d. The GPCMS must maintain a log of all assigned network access addresses by the GPC
System.
3.1.10.3.1 Baseline Management
a. The GPCMS must provide hardware/firmware baseline configuration control of GPC System
devices.
b. The GPCMS must provide configuration status accounting of GPC System devices.
c. The GPCMS must provide software baseline management of GPC System devices.
3.1.10.4 Graphical User Interface (GUI)
a. The GPCMS must provide a GUI/application at the maintenance workstation for status
monitoring of analog connections.
b. The GPCMS must provide a GUI/application at the maintenance workstation for status
monitoring of IP connections.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
42
c. The GPCMS must provide a GUI at the maintenance workstation for GPC System
configuration.
d. The GPCMS must, in the event of a failure, provide a GUI at the maintenance workstation
that displays and identify the failed equipment and its relationship to the system.
e. The GPCMS must automatically remove visual alerts from all equipment receiving the
indication when the fault conditions are corrected.
f. The GPCMS must provide GUIs that permit the performance of the maintenance and testing
capabilities defined in section 3.1.5.
g. The GPCMS must provide a GUI that permits the display of a realtime summary status of the
entire GPC System, including all elements, on a single screen.
h. The GPCMS must provide a summary status display that is fully viewable, even while no
user is logged in.
i. The GPCMS must provide a summary status display that is fully viewable, even while a
session lock is in place.
j. The GPCMS must display at the workstation a unique color and indicator combination for
the current operational mode (e.g., online, offline, maintenance) of each component.
k. The GPCMS must provide a GUI, to be accessed by authorized maintenance personnel, that
includes a control to simultaneously display a summary of the status of each GPC System
element subgroup, including GPCs, with at a minimum the last 4 events of the events list.
l. The GPCMS must, when simultaneous display of status and events is selected, permit
scrolling of the events list.
Note: Additional GUI requirements specific to the GPC System will need to be added.
3.1.11 Software/Firmware Maintenance
The Software/Firmware download requirements in this section will be conducted at the GPCMS
workstation.
a. The GPC System must support Software/Firmware download(s) to each GPC System
component.
b. The GPC System must support Software/Firmware download(s) to configurable groups of
GPC System components.
c. The GPC System must ensure that software/firmware download can be performed without
any impact to ATC operations.
d. The GPC System must ensure, for software/firmware upgrades, that all components have
memory to store a minimum of two software/firmware versions.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
43
e. The GPC System must, in the event of software/firmware download failure, provide an
indication of the failure.
f. The GPC System must, in the event of software/firmware download failure, ensure the
software/firmware version that was in effect prior to the download remains in effect.
g. The GPC System must permit authorized maintenance personnel to perform a query to
receive all critical application software versions, and OS revisions, and latest security patch
versions of any GPC System component.
h. The GPC System must permit authorized maintenance personnel to verify the integrity of
GPC System component software/firmware.
i. The GPC System must permit authorized maintenance personnel to save, to electronic output
report, the results of the software/firmware version query.
j. The GPC System must, upon the installation of a new GPC System component, ensure that
the current version of the software/firmware on the component is reported to the GPCMS.
3.2 Performance Requirements
3.2.1 Voice Channel Performance
This section covers voice channel performance requirements for the GPC. The interfaces for the
GPC System are further illustrated in Figure 3-9. Automatic Gain Control (AGC) (section
3.2.1.15) will be utilized in performance measurements as stated in the requirements of this
section.
3.2.1.1 Background Noise
a. The GPC must ensure that the combined hum and noise level of any single, analog voice path
measured at any analog output, with both analog end(s) (input and/or output) of the path
properly terminated and set to the nominal level at that Transmission Level Point (TLP), does
not exceed 16 dBrnC for the C-message weighted noise and 35 dBrn for the 3 kHz flat noise.
b. The GPC must ensure that the background noise, when measured at the interface with
external equipment with analog end(s) (input and output) of the analog path properly
terminated, does not exceed 20 dBrnC0 for the C-message noise and 40 dBrn for the 3 kHz
flat noise.
c. The GPC must, for receive voice path, permit background noise test to be performed with the
Automatic Gain Control (AGC) enabled.
3.2.1.2 Idle Channel Noise
a. The GPC must ensure, with any analog input terminated in the nominal impedance, that the
noise measured at the associated analog output does not exceed 23 dBrnC0.
b. The GPC must, for receive voice path, permit idle channel noise test to be performed with the
AGC enabled.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
44
3.2.1.3 Impulse Noise
a. The GPC must ensure that the peak level of impulse-type noise generated within the GPC,
when measured on a single idle voice path, does not exceed one hit within a 30-minute
period above a level of +47 dBrnC0.
b. The GPC must, for receive voice path, permit impulse noise test to be performed with the
AGC enabled.
3.2.1.4 Crosstalk Between Channels
a. The GPC must ensure that the crosstalk coupling loss between the analog paths of an
independent VF circuit is greater than or equal to 72 dB. Note: This would include TX and
RX audio on the same four-wire connection.
b. The GPC must, for receive voice path, permit crosstalk between channels test to be
performed with the AGC disabled.
3.2.1.5 Frequency Response
a. The GPC must ensure that the frequency response for all frequencies between 300 and 3000
Hz is within -1.0 to +1.0 dB of the 1000-Hz amplitude level measured at the voice channel
analog output.
b. The GPC must ensure that the test input signal is at the standard test tone level of 0dBm0.
c. The GPC must, to protect other services from interference, due to frequencies that are above
the voice band, ensure that the signal applied to GPC analog interfaces does not exceed the
limits specified in Table 3-4.
d. The GPC must, for receive voice path, permit frequency response test to be performed with
AGC disabled.
Table 3-4. Frequency Response Characteristics
Frequency, kHz Maximum Power Below Zero
Transmission Level Point, dB
3.955 to 4.005 -28 (15 dB below - 13 dBm)
4.0 to 10.0 -16
10.0 to 25.0 -24
25.0 to 40.0 -36
Above 40.0 -50
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
45
3.2.1.6 Intermodulation Distortion
a. The GPC must, when measured with the four-tone test method, which involves the
transmission of four equal level tones (856, 863, 1374, 1385 Hz) at a given composite level
of -13 dBm0, ensure that the intermodulation distortion parameters in a voice circuit do not
exceed the values given in Table 3-5.
b. The GPC must, for receive voice path, permit intermodulation test to be performed twice.
c. The GPC must, for receive voice path, permit the first intermodulation test to be performed
with the AGC disabled.
d. The GPC must, for receive voice path, permit the second intermodulation test to be
performed with the AGC enabled.
Table 3-5. Intermodulation Distortion
Connection Decibels below received power (max), dB
R2*
Legacy VCS input to trunk 45
*R2 is the average of the power level in the 503 to 537 Hz and 2223 to 2257
Hz bands expressed in dB below the received power level.
3.2.1.7 Harmonic Distortion
a. The GPC must ensure that the total harmonic distortion in a voice circuit produced by the
second and third harmonics of a 1004-Hz test tone at -13 dBm injected at the input of the
GPC interface is at least 45 dB below the test tone at the analog output point of measurement.
b. The GPC must, for receive voice path, permit harmonic test to be performed twice.
c. The GPC must, for receive voice path, permit the first harmonic test to be performed with the
AGC disabled.
d. The GPC must, for receive voice path, permit the second harmonic test to be performed with
the AGC enabled.
3.2.1.8 Longitudinal Balance
a. The GPC must ensure that over the frequency range of 300 Hz to 3000 Hz, the longitudinal
balance conforms to the specifications of Table 3-6.
b. The GPC must, for receive voice path, permit longitudinal balance test to be performed with
AGC disabled.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
46
Table 3-6. Longitudinal Balance
Frequency, Hz Minimum Balance, dB
300 58
500 58
1000 58
2200 53
3000 53
3.2.1.9 Gain Tracking Linearity
a. The GPC must ensure that the linearity of each transmission path through the GPC is such
that, for a 1004 Hz sine wave signal, the gain of the GPC tracks the gain of a 0 dBm0 input
signal as specified in Table 3-7.
b. The GPC must, when a 6 dB change occurs, ensure that the output level settles in accordance
with Table 3-7 within 50 ms from the instant of input level change.
c. The GPC must, for receive voice path, permit gain tracking linearity test to be performed
with AGC disabled.
Table 3-7. Gain Tracking Linearity
Input Level, dBm0 Gain Deviation (max), dB
+3 to -37 ± 0.5
-37 to -50 ± 1.0
3.2.1.10 VOX Operation
a. The GPC must, on any interface using voice activated switch (VOX), ensure immediate
activation of the circuit upon receipt of incoming voice, without distortion of incoming
speech.
b. The GPC must, on any interface using VOX, ensure immediate activation of the circuit upon
receipt of incoming voice, without suppression of incoming speech.
c. The GPC must permit authorized maintenance personnel to adjust the VOX detection
threshold from -50 dBm to +3 dBm at the input to the interface in 1 dB increments.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
47
d. The GPC must permit authorized maintenance personnel to adjust the VOX detection
threshold on a per circuit basis.
e. The GPC must permit authorized maintenance personnel to adjust the VOX attack time from
10 to 500 ms configurable in 10 ms increments.
f. The GPC must permit authorized maintenance personnel to adjust the VOX release time
from 100 to 5,000 ms configurable in 10 ms increments.
g. The GPC must, on any interface using VOX, ensure activation of the circuit upon receipt of
incoming voice at or above the specified VOX detection threshold level.
3.2.1.11 Speech Quality
a. The GPC System must provide a minimum Mean Opinion Score - Listening Quality
Objective (MOS-LQO) score of 4.0 for G.711 voice coding, in accordance with ITU-T P.862
and P.862.1 for all voice communications.
b. The GPC System must provide a minimum Mean Opinion Score - Listening Quality
Objective (MOS-LQO) score of 3.5 for G.729a voice coding, in accordance with ITU-T
P.862 and P.862.1 for all voice communications
c. The GPC System must, for connection between the GPC System VoIP Interface and the GPC
Legacy Trunk Interface, provide a minimum MOS-LQO score of 4.0 for G.711 voice coding
in accordance with ITU-T P.862 and P.862.1, when measured from the GPC System VoIP
Interface to the GPC Legacy Trunk Interface.
d. The GPC System must, for connection between the GPC System VoIP Interface and the GPC
Legacy Trunk Interface, provide a minimum MOS-LQO score of 4.0 for G.711 voice coding
in accordance with ITU-T P.862 and P.862.1, when measured from the GPC Legacy Trunk
Interface to the GPC System VoIP Interface.
e. The GPC System must, for connection between the GPC System VoIP Interface and the GPC
Legacy Trunk Interface, provide a minimum MOS-LQO score of 3.5 for G.729a voice
coding in accordance with ITU-T P.862 and P.862.1, when measured from the GPC System
VoIP Interface to the GPC Legacy Trunk Interface.
f. The GPC System must, for connection between the GPC System VoIP Interface and the GPC
Legacy Trunk Interface, provide a minimum MOS-LQO score of 3.5 for G.729a voice
coding in accordance with ITU-T P.862 and P.862.1, when measured from the GPC Legacy
Trunk Interface to the GPC System VoIP Interface.
3.2.1.12 Voice Coding
a. The GPC must support PCM A-law voice coding according to ITU-T G.711 and ED-137C,
Volume 2.
b. The GPC must support PCM μ-law voice coding according to ITU-T G.711 and ED-137C,
Volume 2.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
48
c. The GPC must support voice coding according to ITU-T G.729a CS-ACELP, Annex A.
3.2.1.13 Voice Packetization
a. The GPC must support voice packet sizes of 10, 20, and 30 ms.
3.2.1.14 Transmission Plan
a. The GPC must ensure that audio adjustments can be made on analog signals entering or
leaving the GPC unit.
b. The GPC must have all gains set to 0 dB as the factory default level.
c. The GPC must support adjustment of audio levels per the GPC to Analog Interphone IRD.
d. The GPC must use a test tone level of -9dBm relative to the 0TLP.
3.2.1.15 Voice Level Regulation
Automatic Gain Control (AGC) is required for audio received on the GPC analog interface to
ensure that voice is at a proper nominal level before being converted to VoIP.
a. The GPC must provide a receive AGC for voice received on the analog trunk to maintain
voice at a nominal level from the trunk.
b. The GPC must permit enabling of AGC.
c. The GPC must permit disabling of AGC.
3.2.1.16 Hybrid Balance
a. The GPC must, for a two-wire-trunk interface, ensure the GPC meets mandatory hybrid
balance requirements in ANSI/TIA-464-C paragraph 6.4.1 for standard interface off premise
station (OPS).
3.2.1.17 Return Loss
a. The GPC must, for a two-wire interface, ensure that a minimum echo return loss of 18 dB
and a minimum single-frequency return loss of 12 dB.
b. The GPC must, for delays over 10 ms, ensure that two-wire-trunk connection has the Talker
Echo Path Loudness Loss (TEPLL) versus Talker Echo Path Delay (TEPDC) relationship(s)
on or to the right of the curves presented for Class A1 systems in Figure 12 and Figure 13 of
IEEE-STD-823-1989.
c. The GPC must permit return loss test to be performed with AGC disabled.
3.2.2 Ethernet Performance
a. The GPC System must provide an Ethernet test capability that allows for testing of each
network path in the GPC System.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
49
b. The GPC System must, for each network path of the GPC System, provide the capability to
test network throughput per RFC 2544, section 26.1, up to the maximum rated throughput of
the network path for at a minimum, the following frame sizes: 64, 128, 256, 512, 1024, 1280
and 1518 bytes.
c. The GPC System must, for each network path of the GPC System, provide the capability to
test back-to-back frames per RFC 2544, for at a minimum, the following frame sizes: 64,
128, 256, 512, 1024, 1280 and 1518 bytes.
d. The GPC System must, for each network path of the GPC System, provide the capability to
test frame loss per RFC 2544, up to the maximum rated throughput of the network path for at
a minimum, the following frame sizes: 64, 128, 256, 512, 1024, 1280 and 1518 bytes.
e. The GPC System must, for each network path of the GPC System, provide the capability to
test latency per RFC 2544, section 26.2, up to the maximum rated throughput of the network
path for at a minimum, the following frame sizes: 64, 128, 256, 512, 1024, 1280 and 1518
bytes.
Note: The Internet Engineering Task Force (IETF) has a defined test methodology to
address the issues of performance verification at the Layer 2 and 3 levels. FAA will use
RFC 2544, Benchmarking Methodology for Network-Interconnect Devices, as the
requirements and procedures for testing throughput (performance availability), latency
(transmission delay), back-to-back frames (link burstability), and frame loss (service
integrity).
3.2.3 System Startup
a. The GPC System must perform a system startup upon initial installation. Note: After a
system is initially installed, the power can be applied to each component for startup.
Once all of the components have been powered up, the configuration may be applied for
full system functionality.
b. The GPC System must, for each network-accessible system component, generate a
component startup event indicating that the component is ready for operational use.
c. The GPC System must provide full call functionality in less than or equal to ten (10) minutes
after power is applied. Note: This includes all critical functions required to make and
receive G/G calls.
d. The GPC must provide full unit functionality in less than or equal to five (5) minutes after
power is applied.
e. The GPCMS must provide full system functionality in less than or equal to twenty (20)
minutes after power is applied. Note: Full system functionality includes all critical
functions (e.g., G/G call functionality) as well as system status, monitoring, logging, and
control.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
50
f. The GPC System must return to the individual configuration settings that were in use prior to
the restart (e.g., due to loss of power, soft reset).
Note: Requirement applies to complete system startup and individual component
startups/restarts.
Note: Workstation and server components not directly in audio path would retain
permanent configuration settings, however, ephemeral sessions such as user desktop
environment sessions, user SSH sessions, and non-daemon/non-service program sessions
could be reverted to initial state. Components directly in audio path would retain
configuration settings needed to re-establish the communication capabilities available prior
to the loss of power. For example, ephemeral active calls would be disconnected at the time
of power loss, but once the component has power restored, the component automatically
restores the capability to accept/place the same types/quantity of calls as if the power loss
had not occurred. Need to restore configurations but not states.
g. The GPC System must automatically perform diagnostics on all functional areas on system
startup. Note: Functional areas are to include G/G and data communications.
h. The GPC System must report the results of startup diagnostics to all designated workstations.
i. The GPC System must ensure that the configuration database and operational programs are
available after system startup. Note: Databases and operational programs necessary for
functional operation are automatically started when a component is powered up.
j. The GPC System must be able to return a single LRU to service without requiring a system
restart.
k. The GPC System must be able to restart a single LRU through a manual control without
requiring a system restart.
l. The GPC System must, upon restoration of main power, start automatically without requiring
any operator intervention (e.g., to activate power switch, load software, or reset processors).
Note: Upon power up (after initial installation and configuration) components will
automatically startup and function operationally, without dependencies on other
components.
3.2.4 Call Performance Requirements
3.2.4.1 Call Blocking Probability
a. The GPC System must ensure that no incoming G/G call is blocked for any reason other than
the unavailability or prior occupancy of an external (non-GPC System) resource.
b. The GPC System must ensure that no outgoing G/G call is blocked for any reason other than
the unavailability or prior occupancy of an external (non-GPC System) resource.
c. The GPC System must ensure that incoming G/G calls meet or exceed the allowable delay
limits stated in section 3.2.4.2 for all traffic conditions.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
51
d. The GPC System must ensure that outgoing G/G calls meet or exceed the allowable delay
limits stated in section 3.2.4.2 for all traffic conditions.
3.2.4.2 Throughput Timing Requirements
Note: All references to VoIP Interfaces are at the GPC System level, which is at the
demarcation point of the GPC System to the network (includes GPC LAN components).
a. The GPC System must meet the performance requirements for the operational environments
shown in Table 3-8.
b. The GPC System must meet the throughput timing requirements specified in Table 3-10,
subject to the traffic loads shown in Table 3-9.
c. The GPC System must consider all specified response times in Table 3-10 to be applicable as
“end to end" measurement points with reference to the GPC System external equipment
interfaces.
d. The GPC System must, for transactions originating at a legacy trunk interface, base the
beginning of the throughput timing interval as the receipt by the GPC System of the complete
information needed to service the transaction.
e. The GPC System must, for transactions originating at the network interface, base the
beginning of the throughput timing interval as the receipt by the GPC System of the complete
information needed to service the transaction.
f. The GPC System must, for transactions terminating at a legacy trunk interface, base the end
of the throughput timing interval as the latest event having timing totally dependent on GPC
System performance.
g. The GPC System must, for transactions terminating at the network interface, base the end of
the throughput timing interval as the latest event having timing totally dependent on GPC
System performance.
Table 3-8. GPC SYSTEM Operational Environments
Sizing Parameter Initial No. Required
Minimum1 Maximum
Inter- facility Legacy Trunk
Interfaces2
1 TBD
Notes:
1. The data under “Minimum” represents a generic Minimum System, but does
not preclude zero for any item. The contract schedule defines exact sizing for
each site.
2. Inter-facility Interfaces are defined as Legacy Trunk Interfaces and ED-137
VoIP Interfaces.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
52
Table 3-9. Traffic Loads
NOTE: TABLE 3-9 NEEDS UPDATING FOR GPC SYSTEM
Function Grade of
Service
Holding
Time,
s1
Erlangs
(PBH)
Calls/ Hour
During
PBH 2
Erlangs
(PBM)
Calls / Minute
During PBM 2
Inter-facility calls,
(GPC System VoIP
Interface to GPC
Legacy Trunk
Interface)
Non-
blocking 20 0.1 18 .33 1
Inter-facility calls,
(GPC Legacy Trunk
Interface to GPC
System VoIP
Interface)
Non-
blocking 20 0.1 18 .33 1
Notes:
1. Holding times have an exponential distribution.
2. Call arrival rates have a Poisson distribution.
Table 3-10. Setup/Teardown Throughput Timing Requirements During Traffic Loads
NOTE: RESPONSE TIME VALUES IN TABLE 3-10 BELOW ARE PRELIMINARY
Type of Event
Max. Response Time, msec1,2,3
Percent of Event Completions
95% 99.9% 99.99%
GPC System VoIP Interface to/from GPC Legacy Trunk
Interface (section 3.2.4.2.1.1)
GPC VoIP Interface Call Placement 100 150
GPC Legacy Trunk Interface Call Placement 100 150
GPC VoIP Interface Call Acceptance 100 150
GPC Legacy Trunk Interface Call Acceptance 100 150
GPC VoIP Interface Call Release 100 150
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
53
Type of Event
Max. Response Time, msec1,2,3
Percent of Event Completions
95% 99.9% 99.99%
GPC Legacy Trunk Interface Call Release 100 150
GPC VoIP Interface OVR Call Placement 100 150
GPC Legacy Trunk Interface OVR Call Placement 100 150
GPC VoIP Interface OVR Call Acceptance 100 150
GPC Legacy Trunk Interface OVR Call Acceptance 100 150
GPC VoIP Interface OVR Call Release 100 150
GPC Legacy Trunk Interface OVR Call Release 100 150
Voice Delay, GPC VoIP Interface -to- GPC Legacy Trunk
Interface
40 50
Voice Delay, GPC Legacy Trunk Interface -to- GPC VoIP
Interface
40 50
Notes:
1. All timing parameters exclude network delays.
2. Response times are based on a packetization interval of 10 ms at the external interface.
Please note that the 10 ms packetization requirement is for testing purposes, but the GPC
will need to support packet sizes of 10, 20 or 30 ms per section 3.2.1.13.
3. Response Times apply to all Voice Coding requirements in section 3.2.1.12.
3.2.4.2.1 G/G Performance
The following G/G performance requirements define the measurement of the parameters
specified in Table 3-10 subject to the traffic loads shown in Table 3-9.
Figure 3-9 illustrates the interfaces for the GPC System performance path requirements
described in this section, which are associated with events defined in Table 3-10.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
54
Figure 3-9. G/G Measurement Paths for GPC System
3.2.4.2.1.1 GPC System VoIP Interface to/from GPC Legacy Trunk Interface
Refer to Figure 3-9 and Table 3-10.
3.2.4.2.1.1.1 Call Placement/Acceptance/Release
a. The GPC System must meet the response time specified in Table 3-10 for Call Placement,
when measured from the instant that Call Placement messaging is present at the GPC System
VoIP Interface to the instant that Call Placement signaling is present at the GPC Legacy
Trunk Interface.
b. The GPC System must meet the response time specified in Table 3-10 for Call Placement,
when measured from the instant that Call Placement signaling is present at the GPC Legacy
Trunk Interface, to the instant that Call Placement messaging is present at the GPC System
VoIP Interface.
c. The GPC System must meet the response time specified in Table 3-10 for Call Acceptance,
when measured from the instant that Call Acceptance messaging is present at the GPC
System VoIP Interface, to the instant that Call Acceptance signaling is present at the GPC
Legacy Trunk Interface.
d. The GPC System must meet the response time specified in Table 3-10 for Call Acceptance,
when measured from the instant that Call Acceptance signaling is present at the GPC Legacy
Trunk interface, to the instant that Call Acceptance messaging is present at the GPC System
VoIP Interface.
e. The GPC System must meet the response time specified in Table 3-10 for Call Release,
when measured from the instant that Call Release messaging is present at the GPC System
VoIP Interface, to the instant that Call Release signaling is present at the GPC Legacy Trunk
Interface.
f. The GPC System must meet the response time specified in Table 3-10 for Call Release,
when measured from the instant that Call Release signaling is present at the GPC Legacy
GPC
System
TX Voice
RX Voice
Signaling
ED-137
VoIP Interface
(Includes LAN Equipment)
Legacy
Trunk
Interface
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
55
Trunk Interface, to the instant that Call Release messaging is present at the GPC System
VoIP Interface.
g. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Placement, when measured from the instant that OVR Call Placement messaging is present
at the GPC System VoIP Interface, to the instant that OVR Call Placement signaling is
present at the GPC Legacy Trunk Interface.
h. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Placement, when measured from the instant that OVR Call Placement signaling is present at
the GPC Legacy Trunk Interface, to the instant that Call Placement messaging is present at
the GPC System VoIP Interface.
i. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Acceptance, when measured from the instant that OVR Call Acceptance messaging is
present at the GPC VoIP interface, to the instant that OVR Call Acceptance signaling is
present at GPC Legacy Trunk Interface.
j. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Acceptance, when measured from the instant that OVR Call Acceptance signaling is present
at the GPC Legacy Trunk interface, to the instant that OVR Call Acceptance messaging is
present at GPC System VoIP Interface.
k. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Release, when measured from the instant that OVR Call Release messaging is present at the
GPC System VoIP Interface, to the instant that OVR Call Release signaling is present at the
GPC Legacy Trunk Interface.
l. The GPC System must meet the response time specified in Table 3-10 for OVR Call
Release, when measured from the instant that OVR Call Release signaling is present at the
GPC Legacy Trunk Interface, to the instant that OVR Call Release messaging is present at
the GPC System VoIP Interface.
3.2.4.2.1.1.2 Voice Delay
a. The GPC System must meet the response time specified in Table 3-10 for one-way voice
delay, when measured from the instant voice messaging is present at the GPC System VoIP
Interface, to the instant that voice audio is present at the GPC Legacy Trunk Interface.
b. The GPC System must meet the response time specified in Table 3-10 for one-way voice
delay, when measured from the instant that voice audio is present at the GPC Legacy Trunk
Interface, to the instant that voice messaging is present at the GPC System VoIP Interface.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
56
3.3 Interfaces
This section provides a list of the external interfaces supported by the GPC System. Select
external interfaces requirements are covered herein and others are defined in the pertinent
Interface Requirements Documents (IRDs).
3.3.1 GPC System to G/G Interfaces
a. The GPC must interface with legacy trunks in accordance with the GPC to Analog
Interphone IRD.
3.3.2 GPC System to Government Transport System
a. The GPC System must interface to the FAA Transport System as described in the GPC
System to Government Transport System IRD. Note: To be provided later.
3.3.3 GPC System to Power
a. The GPC System must connect to the government provided power in accordance with the
GPC System to FAA Facility Power IRD. Note: To be provided later.
3.4 Reliability, Maintainability, and Availability
3.4.1 Reliability
3.4.1.1 Reliability - General
a. The GPC System must preclude the propagation of a failure to other resources, devices,
components, or assemblies.
b. The GPC System must limit the impact of the failure of individual components to single
functions.
c. The GPC System must, limit the impact of the failure of individual components to single
resources.
d. The GPC System must automatically switchover to designed redundant equipment as
available in the event of a failure.
e. The GPC System must be designed with no single point of failures (no failure can degrade
more than one GPC at a time or affect the entire GPCMS).
f. The GPC System must have a system Mean Time Between Critical Failure (MTBCF) of
greater than 50,000 hours.
g. The GPC System must base a Critical Failure on the cumulative number of G/G resources
with a Loss of Service as defined in Table 3-11.
h. The GPC System must not allow a failure of the GPCMS to affect operation of any GPC.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
57
Table 3-11. GPC System Critical Failure Parameters
GPC System Sizing per Number
of G/G Resources
GPC System Critical Failure
Min. Cumulative G/G Resources with
Loss of Service1
1 to 10 2
11 to 20 3
21 to 30 4
31 to 40 5
41 to 50 6
51 to 60 7
61 to 70 8
71 to 80 9
81 to 90 10
91 to 100 11
101to 110 12
111 to 120 13
121 to 130 14
131to 140 15
141 to 150 16
Greater than 150 Based on 10% of number of G/G
Resources2
Notes:
1. A “Loss of Service” is defined as any of the following:
a. Interruption exceeding 300 ms in a G/G communication in progress.
b. Failure to meet the throughput timing specified in Table 3-10 by more than
200%
2. When percentage of # of G/G Resources is not an integer (has a decimal or fraction),
number must be rounded up to the next whole number (i.e., 11.2 would become 12)
3.4.1.2 GPC Reliability
a. The GPC must have an MTBF of 43,800 hours or greater when calculated to include any
equipment required for the operation of that resources (e.g., if the resource requires an
interface card and a chassis then the MTBF of both needs to be taken into account to
calculate an MTBF of 43,800 hours or greater for the resource itself).
3.4.1.3 GPCMS Reliability
a. The GPCMS must, at each site, have an MTBF of 20,000 hours or greater.
b. The GPCMS must have a Mean Time Between Critical Failure (MTBCF) of greater than
50,000 hours.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
58
c. The GPCMS must base a Critical Failure on the loss of any of the following functions; login
capability, configuration capability, maintenance functions, security functions, status
monitoring and control functions (e.g., real-time status), database validation capability, or
database transition from off-line to online capability.
3.4.1.4 Software Reliability
a. The GPC System must ensure that software has fault avoidance reliability characteristics.
b. The GPC System must ensure that software has fault detection reliability characteristics.
c. The GPC System must ensure that software has fault tolerance reliability characteristics.
d. The GPC System must ensure that software has fault containment reliability characteristics.
3.4.2 Availability
3.4.2.1 GPC System Availability
a. The GPC System must use inherent availability to drive the reliability and maintainability
requirements for the GPC System.
b. The GPC System must ensure that the specified availability is achieved through system
design.
c. The GPC System must demonstrate system availability by using reliability and
maintainability parameters obtained from analysis, test, and similar components/systems.
d. The GPC System must meet the inherent availability A(i), for each GPC System function.
A(i) = MTBCF(f) / [MTBCF(f) + MTTR(f)] where: A(i) = inherent availability, inclusive of
hardware failures caused by software; MTBCF(f) = mean time between critical failures as
defined in Table 3-11: GPC System Critical Failure Parameters; MTTR(f) = mean time to
repair as defined in 3.4.3.3.
e. The GPC System must exhibit an inherent availability A(i) of at least 0.99999.
3.4.2.2 GPCMS Availability
a. The GPCMS must use inherent availability to drive the reliability and maintainability
requirements for the GPCMS.
b. The GPCMS must ensure that the specified availability is achieved through system design.
c. The GPCMS must demonstrate system availability by using reliability and maintainability
parameters obtained from analysis, test, and similar components/systems.
d. The GPCMS must meet the inherent availability A(i), for each GPCMS function. A(i) =
MTBCF(f) / [MTBCF(f) + MTTR(f)] where: A(i) = inherent availability, inclusive of
hardware failures caused by software; MTBCF(f) = mean time between critical failures as
defined in 3.4.1.3.; MTTR(f) = mean time to repair as defined in 3.4.3.3.
e. The GPCMS must exhibit an inherent availability A(i) of at least 0.99999.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
59
3.4.3 Maintainability
3.4.3.1 LRU Replacement
a. The GPC System must permit all modules and equipment to be completely removable from
their enclosure without excessive disassembly.
b. The GPC System must allow the replacement of any LRUs without removal of adjacent
LRU(s).
c. The GPC System must allow the replacement of any LRUs without removal of any cabling
not associated with the replaced LRU.
d. The GPC System must allow maintenance actions on any LRUs without impacting the
operation of any redundant LRU(s).
e. The GPC System must ensure that no maintenance action requires the simultaneous labor of
more than two persons.
3.4.3.2 Maintenance Design
a. The GPC System must ensure that all ON-OFF switches are visually and physically
accessible.
3.4.3.3 Time to Repair
a. The GPC System must, excluding administrative and logistical time, exhibit a Mean Time To
Repair (MTTR) less than or equal to 30 minutes for any single corrective maintenance
actions, including time required for fault localizing, repair, test, and restoration to service.
b. The GPC System must, excluding administrative and logistical time, require less than or
equal to 90 minutes for any single corrective maintenance action, including time required for
fault localizing, repair, test, and restoration to service.
c. The GPC System must, excluding administrative and logistical time, require less than or
equal to 15 minutes for Floor Replaceable Units (FRUs), including time required for fault
localizing, repair, test, and restoration to service.
d. The GPC System must support an GPCMS client suitable for installation as an FRU on the
Operations Room Floor.
3.4.3.4 Preventive Maintenance
a. The GPC System must require a preventive maintenance interval of greater than or equal to
six months.
b. The GPC System must ensure that preventive maintenance does not require service
interruption on more than one GPC at a time.
c. The GPC System must ensure that preventive maintenance requires less than or equal to 30
minutes of scheduled downtime for any operational communications resource.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
60
d. The GPC System must, excluding administrative and logistical time, ensure that preventive
maintenance requires less than or equal to 2 hours per visit, regardless of system size.
e. The GPC System must count any failure to any function used in operations that occurs during
a preventive maintenance action, as corrective maintenance.
3.4.3.5 Replacement of Consumables
a. The GPC System must ensure that consumable or items subject to high failure rate (e.g., light
bulbs, filters or cartridges) do not cause service interruption or require de-soldering to
replace.
3.4.4 GPC System Redundancy
a. The GPC System must, for all Active/Standby components, automatically switch to the
redundant equipment upon detection of a failure.
b. The GPC System must, for all Active/Standby components, ensure that automatic switchover
to failed equipment is prohibited.
c. The GPC System must, for all Active/Standby and Active/Active components, permit manual
switching to redundant equipment by authorized maintenance personnel.
d. The GPC System must, for all Active/Standby and Active/Active components, ensure that
manual switchover to failed equipment is prohibited.
e. The GPC System must, for all Active/Standby components, switch to the redundant
equipment without degrading system performance.
f. The GPC System must, for all Active/Standby components, ensure that the automatic
switching time to restore any function is no more than 1 minute.
g. The GPC System must, for all Active/Standby components, ensure that the manual switching
time to restore any function is no more than 1 minute.
h. The GPC System must warn and require confirmation to proceed when an attempt is made to
manually disable a redundant network interface if the other network path is faulted.
3.4.4.1 Exercising of Redundant Equipment
a. The GPC System must, for all Active/Standby and Active/Active components, permit
authorized maintenance personnel to disable individual redundant network or audio paths
internal to the facility in order to verify operation.
b. The GPC System must, for all Active/Standby and Active/Active components, permit
authorized maintenance personnel to disable all redundant network or audio paths internal to
the facility, for either redundant path, to verify operation.
c. The GPC System must, for all Active/Standby components, ensure that reverted switching is
prohibited, when failed redundant equipment recovers.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
61
d. The GPC System must, for all Active/Standby and Active/Active components, permit
authorized maintenance personnel to re-enable individual redundant network or audio paths
internal to the facility in order to verify operation.
e. The GPC System must, for all Active/Standby and Active/Active components, permit
authorized maintenance personnel to re-enable all redundant network or audio paths internal
to the facility with one command in order to resume normal operation.
3.5 Design Requirements
3.5.1 Physical Design Requirements
This section provides the physical (electrical and mechanical) design requirements that apply to
all GPC equipment, unless otherwise noted.
a. The GPC System must, with all associated cables connected, fit into a standard 19" wide rack
panel opening.
b. The GPC height must be no more than TBD inches.
c. The GPC System components must weigh no more than TBD pounds each.
3.5.1.1 Electrical Requirements
3.5.1.1.1 Electric Power
a. The GPC System must, when ac power is applied within a range of 0 to 230 VAC, sustain no
damage to equipment, which includes being fully operational when power is restored to the
specified operating voltage of 120 VAC +10 / -15 percent.
b. The GPC System must sustain transient AC power interruptions of up to 20 ms without
degradation of operations.
c. The GPC System must sustain transient AC power interruptions of up to 20 ms without
interruption of operations.
d. The GPC System must provide a power switch to remove power from each unit.
e. The GPC System must comply with the GPC System to FAA Facility Power IRD. Note: To
be provided later.
3.5.1.1.2 Power Supplies
a. The GPC System must, for power supplies that are LRUs, ensure that each power supply has
a front-panel ON-OFF switch.
b. The GPC System must ensure that each power supply contains electronic circuitry to prevent
damage caused by external short circuits.
c. The GPC System must ensure that the power supply recovers immediately upon the removal
of external short circuits.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
62
d. The GPC System must ensure that the electronic short circuit protection circuit allows
removal or addition of electronic modules of capacitive loads without causing any circuit
protection devices to operate or induce any other side effects.
e. The GPC System must ensure that the electronic short circuit protection circuit allows
electronic modules of capacitive loads to be switched ON or OFF without causing any circuit
protection devices to operate or induce any other side effects.
f. The GPC System must, for power supplies that are LRUs, ensure that each power supply
includes circuitry to report status via the network to designated workstations.
g. The GPC System must ensure that the power supplies allow power-on installation or removal
of GPC System plug-in assemblies without degradation to the GPC System or any GPC
System assembly.
h. The GPC System must, for power supplies that are LRUs, ensure that each power supply
provides current output measure status indication via the network to designated workstations.
i. The GPC System must, for power supplies that are LRUs, ensure that each power supply
provides voltage output measure status indication via the network to designated workstations.
3.5.1.1.3 Grounding Systems
a. The GPC System must provide a grounding system that prevent cross-coupling through the
ground system.
b. The GPC System must use centrally located grounding to prevent ground loops and shared
impedance-coupling paths.
c. The GPC System must use separate grounding networks as necessary for the AC power
ground.
d. The GPC System must use separate grounding networks as necessary for the chassis ground.
e. The GPC System must use separate grounding networks as necessary for the signal ground.
f. The GPC System must use separate grounding networks as necessary for the trunk circuit
ground.
g. The GPC must provide a chassis ground terminal on the rear of the unit.
h. The GPC System must provide grounding in accordance with 5.6.6 of FAA-STD-019f.
i. The GPC System must provide grounding and bonding in accordance with FAA-STD-019f,
FAA-G-2100H, NFPA 70, and NFPA 70E.
j. The GPC System must provide shielding in accordance with FAA-STD-019f, FAA-G-
2100H, NFPA 70, and NFPA 70E.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
63
3.5.1.1.4 Surge Protection
a. The GPC System must provide transient protection for all signal, data, and control lines; both
at facility entrance and at entrance to all electronic equipment in accordance with 5.2.5.2 and
5.6.3 of FAA-STD-019f.
3.5.1.2 Mechanical Requirements
3.5.1.2.1 Module Removal and Insertion
a. The GPC System must permit removal of all removable modules and printed circuit
assemblies without causing damage to the modules, printed circuit assemblies, or any other
equipment.
b. The GPC System must permit the removal of each module while system power is on without
damage to equipment or interruption of service on remaining modules.
c. The GPC System must permit the insertion of each module while system power is on without
damage to equipment or interruption of service on remaining modules.
d. The GPC System must ensure that all modules are plug-in type modules where practicable
and have positive locking mechanisms to prevent loosening.
e. The GPC System must use mechanical means (interlocks or keys) to prevent insertion or
connection of plug-in modules that are incorrectly oriented.
f. The GPC System must ensure that plug-in modules are standardized to permit
interchangeability of like modules without alignment or adjustment.
g. The GPC System must avoid the splitting of a single function across more than one module.
h. The GPC System must use equipment that is designed to use modular construction.
i. The GPC System must, to the extent that software or firmware changes are required to repair
an LRU, ensure that operations are only affected on the LRU being repaired.
j. The GPC System must be able to return a single LRU to service without requiring a system
restart.
k. The GPC System must ensure the each LRU complies with weight and size limits specified
in paragraph 5.2.2.2 of HF-STD-001B for repair or replacement of that LRU by one person.
3.5.1.2.2 Printed Circuit Assemblies
a. The GPC System must ensure that terminology and definitions are in accordance with ANSI
IPC-T-50.
b. The GPC System must ensure that alignment, where required, is possible using standard
tools.
c. The GPC System must ensure that alignment adjustment mechanisms are accessible without
disassembly of the printed circuit assembly.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
64
d. The GPC System must ensure that printed circuit assemblies are manufactured in accordance
with paragraph 3.2.2.1 of FAA-G-2100H.
e. The GPC System printed circuit assemblies must conform to the requirements of IPC-2221.
f. The GPC System must prohibit wire wrap on all printed circuit boards.
3.5.1.2.3 Cabinet and Frame Requirements
3.5.1.2.3.1 Cabinet and Frame Construction
a. The GPC System must ensure that equipment room cabinet(s) and frames do not exceed a
height of 82.25 inches (2.07 meters), a width of 24 inches (0.61 meters), and a depth of 36
inches (0.92 meters).
b. The GPC System must ensure that the loading conditions of each fully equipped cabinet and
frame does not exceed an average weight distribution greater than 200 lb/ft2.
c. The GPC System must ensure that the structural strength and rigidity of the cabinets, frames,
and consoles are such that normal handling in loading, shipping, unloading, and setting into
position for installation will not result in any damage to the equipment.
d. The GPC System must ensure that removal of equipment or modules or interchanging of
equipment modules does not cause any deformation to the cabinets and frames.
e. The GPC System must ensure that the structural strength and rigidity of all cabinets are
independent of any strength or rigidity provided by access doors.
f. The GPC System must ensure that removable components do not exceed the weight limits
specified in HF-STD-001B paragraph 5.2.2.2 for male and female maintainers.
g. The GPC System must ensure that the cabinet and frame construction meets the anchoring
requirements for the seismic zone in which the equipment is located and the requirements in
paragraphs 3.3.5(b) and 3.3.5.7 of FAA-G-2100H.
h. The GPC System must ensure that the equipment is designed and installed to be free of
mechanical hazards that may injure personnel (sharp projections, unguarded moving parts),
in accordance with paragraph 3.3.5.4 of FAA-G-2100H.
3.5.1.2.3.2 Cabinet and Frame Prewiring
a. The GPC System must ensure that all cabinet wiring is provided with chafing protection in
addition to the individual wire or cable insulation jackets.
3.5.1.2.3.3 Cabinet and Frame Convenience Outlets
a. The GPC System must provide at least two ac convenience outlets for each cabinet or frame
(i.e., for use by technicians to power tools, test equipment, during maintenance operations).
b. The GPC System must ensure that the ac convenience outlets are independent of the primary
power source for the equipment within the cabinets and frames, and in accordance with
3.1.1.1.1.f in FAA-G-2100H.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
65
3.5.1.2.3.4 Cable Entrance and Exit
a. The GPC System must provide access for interconnecting cables to enter through the top and
bottom of the equipment cabinet.
b. The GPC System must allow direct cabling through the side walls of cabinets, at least 6
inches above the floor, within a subsystem where distance is considered a critical factor in
circuit performance.
c. The GPC System must ensure that the use of direct cabling does not preclude the installation
of additional frames, card cages, or other such items that may be required for future
expansion.
3.5.1.2.3.5 Distribution Points
a. The GPC System must provide distribution point(s) to facilitate the interconnection of all
Government IDF cables to the government equipment distribution frame(s).
b. The GPC System must provide distribution points that accommodate all interface
requirements.
c. The GPC System must provide distribution points that accommodate the capacity of the
system ordered for the site, including all built-in expansion.
3.5.1.2.3.6 Ventilation and Cooling
Note: Ideally the FAA would prefer to not have fans for ventilation.
a. The GPC System must ensure that each cabinet requiring forced ventilation contains its own
silent fan blower system that requires no external ducts.
b. The GPC System must ensure that equipment does not malfunction with access doors and
plates open, and drawers extended for servicing, for up to 8 consecutive hours.
c. The GPC System must take in air from the bottom of the cabinet.
d. The GPC System must permit cabinet air intake from either below a raised floor or from
floor level, by simple removal of cover plates or baffles.
e. The GPC System must, for each cabinet requiring air ventilation, provide uniform air filters
that are replaceable using only common hand tools.
f. The GPC System must ensure that ventilation exhaust openings are through the top of the
cabinet.
g. The GPC System must direct the exhaust upward and away from personnel and other
equipment.
h. The GPC System must ensure that the exhaust outlet openings do not interfere with or be
obstructed by cable routing.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
66
i. The GPC System must, for each cabinet requiring forced ventilation, report to the
maintenance function any condition that would cause a ventilation problem (e.g., blower
failure, clogged filters).
3.5.1.2.3.7 Overheat Warning
a. The GPC System must provide warning devices in each separate cabinet to indicate when the
temperature exceeds the maximum safe operating temperature for the equipment within the
cabinet.
3.5.1.2.4 Interconnection Cables
a. The GPC System must provide interconnection cables that are compatible with both under
floor and overhead distribution and cable facilities provided by the government.
b. The GPC System must ensure that all interconnection cabling permits accessibility to
equipment for test, maintenance, and replacement.
c. The GPC System must comply with 3.3.1.4.10 of FAA-G-2100H and the National Electric
Code, NFPA-70, for cabling and wiring.
d. The GPC System must supply plenum-rated interconnecting cables in accordance with
NFPA-70 articles 300-22 (c) and NIST Special Publication 800-53 .
e. The GPC System must provide labels for all interconnection cables with mechanically
produced (i.e., not hand written), flag-type labels at both end points of the cable, uniquely
identifying their point of origin and destination (i.e., the connector identifier and distribution
point), the signals being conducted on the cable, and the manufacturer’s part number.
f. The GPC System must provide interconnection cables that are color coded (with the
exception of green) according to function.
3.5.1.2.4.1 Connectors
a. The GPC System must ensure that all connectors furnished on the equipment for making
external connections are clearly identified on the plug-in side by labels descriptive of their
specific function and by the proper reference designation.
b. The GPC System must ensure that cable connectors (non-RJ-45) are mechanically keyed to
prevent incorrect installation and hookup.
c. The GPC System must use differentiating methods (e.g., color, colored tags) on RJ-45
connectors to minimize incorrect installation and hookup.
d. The GPC System must ensure that incorrect installation and hookup of any connection does
not cause equipment damage.
e. The GPC System must ensure the mating connector part (connector or plug) that is
electrically energized contain female contacts.
f. The GPC System must ensure that all cable connectors are mechanically retained in place.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
67
g. The GPC System must provide all connectors for making external connections to
Government cables (e.g., IDF signal cables).
h. The GPC System must ensure that signal cable connectors for making connection to
Government IDF cables are solder-less, quick-disconnect terminal blocks or mass
termination connectors.
3.5.1.2.4.2 Cable-End Terminations
a. The GPC System must ensure that signal cable end terminations are solder-less, quick-
disconnect terminal blocks or mass termination connectors.
b. The GPC System must provide power cable terminations that are screw-type terminal blocks,
pressure contact terminal blocks, or locking connectors.
3.5.1.2.4.3 Power Cables
a. The GPC System must ensure that all ac power cables and wiring within the GPC System are
isolated from sensitive voice and signaling circuits.
b. The GPC System cabling must include all junction boxes, fittings, and distribution equipment
(switches and circuit breakers from government power source to the GPC System primary
power panel).
3.5.1.2.5 Nameplates and Product Marking
a. The GPC System must ensure that the identification of GPC System units are in accordance
with 3.3.3.1 of FAA-G-2100H.
b. The GPC System must ensure that all equipment that presents a potential safety hazard to
personnel is marked with appropriate warning labels or placards, in accordance with Title 29
CFR Part 1910.145, paragraph 3.3.5.5 of FAA-G-2100H, and paragraph 5.10.16 of FAA HF-
STD-001B.
3.5.1.2.6 Materials
a. The GPC System must ensure that no material used on or in the GPC System contains
asbestos, polychlorinated biphenyls (PCBs), mercury, lead paint, Class 1 ozone-depleting
substances, HCFC-22, HCFC-141b, or HCFC-142b.
b. The GPC System must ensure that the selection of materials is consistent with economically
producing a system that performs its specified functions with ruggedness and durability.
3.5.1.2.6.1 Recycled Material
a. The GPC System must ensure that all electrical, electronic, or electromechanical parts used
in the GPC System are new.
b. The GPC System must permit recycled metals or plastic to be used for mechanical or
structural parts as appropriate.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
68
3.5.1.2.6.2 Toxicity
a. The GPC System must be constructed from materials of low toxicity, not having dangerous
gasses due to fires or toxic effects when used under specified environmental conditions for
operating and non-operating equipment contained within this specification.
3.5.1.2.6.3 Glass
a. The GPC System must ensure that all glass used in the equipment is shatterproof, clear, and
free of distortion at all viewing angles.
3.5.1.2.6.4 Fungus a. The GPC System must ensure that the materials chosen are non-nutrient to fungus and
insects, flame resistant, non-hygroscopic, and not adversely affected by the environmental
conditions specified herein.
3.5.1.2.6.5 Plastics
a. The GPC System must ensure that transparent plastics used in displays, selectors,
backlighting, and related applications do not warp, soften, discolor, or otherwise be degraded
in appearance or physical properties due to heat buildup encountered in normal operation.
3.5.1.2.7 Color and Finishes
a. The GPC System must provide all equipment racks and cabinets that are fully painted on all
exterior surfaces and corrosion protected on all interior surfaces (painting permitted).
b. The GPC System must ensure that all surfaces are prime painted in a neutral color.
c. The GPC System must ensure that the finish is a baked enamel paint or equivalent.
d. The GPC System must ensure that all exterior surfaces are free from burrs and sharp edges.
3.5.1.2.8 Materials, Processes, and Parts
3.5.1.2.8.1 Dissimilar Metals
a. The GPC System must ensure that dissimilar metals are not used where they will degrade or
cause deterioration to the assembled parts.
b. The GPC System must, when dissimilar metals are used, ensure that they are coated or
protected to inhibit or prevent degradation to other parts and assemblies.
3.5.1.3 Electronic Equipment Assembly Requirements
a. The GPC System must assemble electronic equipment in accordance with 3.2.2.1 of FAA-G-
2100H.
3.5.1.4 Government-Furnished Property Usage
a. The GPC System must only require the use of government-furnished property as indicated in
this specification.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
69
3.5.1.5 Safety
a. The GPC System must comply with Occupational Safety and Health Administration (OSHA)
safety requirements defined in FAA-G-2100H, paragraph 3.3.5, except 3.3.5.d.
b. The GPC System must apply system safety engineering principles in accordance with 3.3.5
of FAA-G-2100H.
c. The GPC System must comply with safety requirements defined in IEC 60950-1, paragraphs
1.6.2, 1.7.11, 2.1.1.7, 2.6.3.4, 4.2.3, 4.2.4, 4.2.5, 4.5.1, 5.1, 5.2, and 5.3.
d. The GPC System must comply with the personnel safety requirements of Title 29 CFR Part
1910, Occupational Safety and Health Standards.
e. The GPC System must apply system safety engineering principles throughout the design,
development, manufacture, test, checkout, operation, and maintenance of the GPC System in
accordance with the following requirements of MIL-HDBK-454B, Guideline 1: Safety
Design Criteria - Personnel Hazards, Guideline 3: Flammability Guideline 8: Electrical
Overload Protection, and Guideline 45: Corona and Electrical Breakdown Prevention.
f. The GPC System must comply with the personnel safety requirements of Title 29 CFR Part
1926, Occupational Safety and Health Administration, Labor.
g. The GPC System must comply with the personnel safety requirements of FAA Order
3900.19C Occupational Safety and Health Policy.
h. The GPC System must comply with the personnel safety requirements of the National Fire
Protection Association Standard 70 (NFPA 70), National Electrical Code and NFPA 70E,
Standard for Electrical Safety in the Workplace.
i. The GPC System must comply with provisions of Chapters 5.10 and 5.11 of HF-STD-001B
requirements for Personnel Safety and Environment.
j. The GPC System must ensure that the acoustic noise levels generated by the assembled and
peripheral equipment do not exceed the specifications of paragraph 3.3.6.1 of FAA-G-
2100H.
3.5.1.5.1 Hazardous Materials
a. The GPC System must be free of asbestos, polychlorinated biphenyls (PCBs), lead, mercury,
class one ozone-depleting substances, HCFC-22, HCFC-141b, and HCFC-142b, with the
exception of mercury that may be present in the liquid crystal displays (LCD) of computer
monitors with quantities not to exceed 60 milligrams, and lead that is used in the manufacture
of computer circuit boards and monitors.
b. The GPC System must minimize the production of hazardous waste as defined in FAA-G-
2100H, paragraph 3.3.5.6.
c. The GPC System must limit personnel exposure to hazardous materials to levels permitted by
Title 29 CFR Part 1910, Subpart Z - Toxic and Hazardous Substances.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
70
d. The GPC System must ensure that the disposal of hazardous materials is in accordance with
the Resource Conservation and Recovery Act, and FPMR 101-42, Utilization and Disposal of
Hazardous Materials and Certain Categories of Property.
e. The GPC System must ensure that the use of hazardous materials in the design, manufacture,
and installation of the GPC System complies with Title 29 CFR Part 1910 Occupational
Safety and Health Standards.
f. The GPC System must ensure that the handling of hazardous materials is in accordance with
Title 29 CFR Part 1910, Occupational Safety and Health Standards; FAA Order 8040.4,
Safety Risk Management; and Title 29 CFR Part 1910.1000, Air Contaminants.
g. The GPC System must ensure that components containing potentially hazardous materials to
employees are identified per Title 29 CFR Part 1910.1200, Hazard Communications.
h. The GPC System must furnish with the equipment a material safety data sheet (MSDS) for
each hazardous chemical used by the GPC System equipment in accordance with Title 29
CFR Part 1910.1200.
i. The GPC System must ensure that reserve power supplies do not vent hazardous or corrosive
gases into the atmosphere.
3.5.1.6 Environmental
a. The GPC System must, when subject to the non-operating conditions, return to operation
without degradation of performance.
b. The GPC System must not sustain any damage or deteriorate in functional performance after
it has been exposed and tested to the environment described in section GR-63-CORE section
4.1.1.1 and 5.1.1.1, Low-Temperature Exposure and Thermal Shock.
c. The GPC System must not sustain any damage or deteriorate in functional performance after
it has been exposed and tested to the environment described in section GR-63-CORE section
4.1.1.2 and 5.1.1.2, High Relative Humidity Exposure.
d. The GPC System must not sustain any damage or deteriorate in functional performance after
it has been exposed and tested to the environment described in section GR-63-CORE section
4.1.1.3 and 5.1.1.3, High-Temperature Exposure and Thermal Shock.
3.5.1.6.1 Temperature, Humidity, and Altitude
a. The GPC System must comply with the environmental requirements of Table 3-12.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
71
Table 3-12. GPC System Environmental Requirements
Condition
Ambient Temperature
Degrees Centigrade,
(Degrees Fahrenheit)
Relative
Humidity
% RH
Altitude, ft (m)
Operating 1 +10 to +40
(+50 to +104)
5 to 80 non-
condensing
0 to 10,000
(0 to 3,048)
Non-operating 2 -40 to +703
(-40 to +158) 5 to 934
0 to 50,000
(0 to 15,240)
1. The condition is the range within which the facility air conditioning system
is permitted to operate. It, therefore, represents the allowable operating heat
sink condition to which the GPC System must dissipate the waste heat.
2. Equipment should be packaged for transport and storage.
3. Temperature ramp times, dwell times, and cycles per GR-63-CORE
sections 5.1.1.1 and 5.1.1.3.
4. Humidity ramp times, dwell times, and cycles per GR-63-CORE sections
5.1.1.2
3.5.1.7 Electromagnetic Compatibility
a. The GPC System must ensure that all equipment is compliant with Class B digital devices
per Title 47 CFR Part 15.
b. The GPC System must ensure that equipment meets the MIL-STD-461G requirements and
those listed in Table 3-13.
Table 3-13. Electromagnetic Compatibility Requirements
Detailed Requirements
CE102, conducted emissions, power leads, 10 kHz to 10 MHz
CS101, conducted susceptibility, power leads, 30 Hz to 150 kHz
CS114, conducted susceptibility, bulk cable injection, 10 kHz to 200 MHz
CS115, conducted susceptibility, bulk cable injection, impulse excitation
CS116, conducted susceptibility, damped sinusoid transients, cables and
power leads, 10 kHz to 100 MHz
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
72
Detailed Requirements
RE102, radiated emissions, electric field, 10 kHz to 18 GHz
Note – Ground Navy Fixed levels
RS101, radiated susceptibility, magnetic field, 30 Hz to 100kHz
RS103, radiated susceptibility, electric field, 2 MHz to 40 GHz
3.5.1.8 Power Line EMI Reduction Requirements
a. The GPC System must ensure that all interconnections between the GPC System and external
systems comply with Section 4.8, 5.6.7.4, 5.6.7.5 of FAA-STD-019f.
3.5.1.9 Electrostatic Discharge Immunity
a. The GPC System must incorporate protection against damage arising from electrostatic
discharge from personnel using the GPC System.
b. The GPC System must incorporate protection against damage arising from electrostatic
discharge from personnel servicing the GPC System.
c. The GPC System must sustain no equipment malfunctions at severity level 1 as specified in
Table 3-14 when subjected to ESD pulses having the waveform in Figure 3-10 and the
maximum current and voltage limits specified under Level 1 in Table 3-15.
d. The GPC System must sustain no equipment malfunctions at severity level 2 as specified in
Table 3-14 when subjected to ESD pulses having the waveform in Figure 3-10 and the
maximum current and voltage limits specified under level 2 in Table 3-15.
e. The GPC System ESD testing must be performed on a fully operational GPC System
handling the communications test load described in Table 3-9.
f. The GPC System ESD test generator must simulate the human body contact model defined in
paragraph 6 of IEC-61000-4-2.
g. The GPC System must use a direct-injection test method for testing GPC System equipment,
with the air discharge method available as an additional method for insulated devices as
defined in IEC-61000-4-2.
h. The GPC System must use IEC-61000-4-2 as guidelines for test simulators, test method
selection, test point selection, and the number of test trials.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
73
Table 3-14. Electrostatic Discharge Failure Criteria
Severity Level Effect
0 Temporary disturbances with no lasting effects, such as an audible
click or flicker on a video screen.
1
All functions perform as designed during exposure, but one or more
may go beyond specification tolerance (e.g., call setup delay). All
functions return automatically to within normal limits.
2
One or more functions do not perform as specified during the
exposure, but system returns automatically to normal after exposure is
removed.
3
Indicated as machine error to user and must be corrected by manual
retry or system restart (e.g., processor locks up); Loss of calls in
progress, but system returns to idle state.
4
Critical non-recoverable error, loss or corruption of stored data,
operational safety is affected, power cycling necessary to restore
service, equipment damage requiring repair or replacement.
Table 3-15. Voltage and Current Limits for Electrostatic Discharge Testing
Level Simulator voltage, kV Discharge current, A
Direct injector Air discharge IPeaka I30b I60b
1 6 15 22.5 12.0 6
2 8 20 30.0 16.0 8
a. Within ± 10%
b. Within ± 30%
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
74
Figure 3-10. Electrostatic Discharge Test Waveform
3.5.1.10 Vibration and Shock
a. The GPC System must ensure that for shipment, proper packaging techniques are
implemented to prevent damage from transportation vibration and shock.
b. The GPC System must suffer no harm when exposed to the random vibration environment
given in Table 3-16. Note: High volume commercial products (not including developed
products) do not require testing at the LRU level. Their design and manufacturing
processes should be considered qualified by field experience.
c. The GPC System must ensure that for unpackaged bench handling, the hardware can
withstand a 4-inch pivotal drop and a 1-inch (free) drop from any probable direction.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
75
Table 3-16. Random Vibration Exposure for GPC System in accordance with MIL-STD 810g
Frequency, Hz Level
20-1000 0.006 G2/Hz
1000-2000 -6 dB/octave
Overall 3.0 G rms
The random vibration is assumed in each of the
three mutually orthogonal axes at the mounting of
the assembly. (VS4995)
3.5.1.11 Earthquake
a. The GPC System must be designed to operate continuously during waveform testing per
Section 5.4.1, "Earthquake Test Methods" of GR-63-CORE for Earthquake Risk Zone 4.
b. The GPC System must sustain operation immediately before and after each axis of waveform
testing per Section 5.4.1, "Earthquake Test Methods" of GR-63-CORE for Earthquake Risk
Zone 4, without replacement of components, manual rebooting, or human intervention.
3.5.2 System Size and Capacity
3.5.2.1 System Capacity
a. The GPC System hardware configuration must be scalable up to a maximum of TBD GPC
units per site.
b. The GPC System hardware configuration must be scalable based on the number of
workstations required.
3.5.2.1.1 External Interfaces
3.5.2.1.1.1 G/G Interfaces
a. The GPC System must be configurable with one legacy trunk up to the maximum number of
legacy trunks supported.
b. The GPC System must support at least TBD legacy trunks.
3.5.2.1.2 Workstations
a. The GPC System must be configurable from two workstations up to the maximum number of
workstations supported.
b. The GPC System must support at least TBD workstations per facility.
c. The GPC System must provide desktop workstations as identified by the government at the
time of order.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
76
d. The GPC System must provide rack-mountable workstations as identified by the government
at the time of order.
3.5.2.1.2.1 Workstation Printers
a. The GPC System must provide at least 2 networkable system printers for use by
workstations, as ordered by the government.
b. The GPC System must provide printers that support local network connectivity interface as
directed at time of order
c. The GPC System must provide printers that can be connected via USB as directed at time of
order.
3.5.2.2 Installation Space Requirements
3.5.2.2.1 Maintenance Position
a. The GPCMS must require no more than an area of 3 feet by 3 feet (desk top) for
workstations/system terminals required for the maintenance position.
b. The GPCMS must, as ordered by the government, provide workstations/system terminals that
are rack-mountable with the rest of the system central equipment.
c. The GPCMS must ensure that other equipment required by the maintenance position (e.g.,
test point access, duplicate position equipment, indicators, power supply monitoring and
service points), fit within the space allocated.
3.5.2.2.2 Central Equipment Floor Space
a. The GPC System central equipment must include all equipment necessary to support GPC
System operations except for maintenance workstation.
3.5.2.2.3 Separation of Equipment
a. The GPC System must permit workstations/system terminals to be located up to 1000 cable
feet away from the central equipment.
b. The GPC System must, as ordered by the government, provide workstations/system terminals
that can be remoted as much as 10,000 cable feet away from the central equipment. Note:
The supporting infrastructure will be provided by the contractor or the Government as
directed at time of order.
3.5.3 Human Factors
TBD.
3.6 Software
Note: Software requirements will be covered in a separate J-1 document.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
77
4 VERIFICATION REQUIREMENTS
4.1 Responsibilities For Verification
a. Each requirement of the GPC System specification must be verified by one or more of the
following verification methods as indicated in the Verification Requirements Traceability
Matrix. Note: The Verification Requirements Traceability Matrix will be provided later.
4.1.1 Verification Methods
a. TEST (T): Verification that is accomplished, with or without instrumentation, through
systematic exercising of the application item under appropriate conditions with collection,
analysis, and evaluation of quantitative data. Acceptability of the item is determined by the
comparison of the data with pre-established quantitative criteria, requirements, and
occurrences.
b. DEMONSTRATION (D): Verification that is accomplished by operation, adjustment, or
reconfiguration of items performing their designed functions under specific scenarios. The
items may be tested and quantitative limits of performance monitored, but only observational
data rather than actual performance data are required to be recorded for verification.
Demonstration does not require any actions beyond those identified in Test Steps of the Test
Procedure.
c. INSPECTION (I): Verification that is accomplished by a visual examination of the item,
reviewing descriptive documentation, and comparing the appropriate characteristics with
predetermined standards to determine conformance to requirements without the use of
laboratory equipment or procedures.
d. ANALYSIS (A): Verification that is accomplished through use of one or more of the
following analysis techniques to prove that an item meets specified requirements. Analysis
techniques include Mathematical representation such as math models, algorithms, and
equations; Charts; Graphs; Circuit diagrams; Data reduction/recording; and Representative
Data which may include data collected from previous or other equipment and system
verifications.
e. GOVERNMENT DISCRETION (X): The Government has discretion on whether to conduct
verification of that requirement during the identified phase.
f. NOT APPLICABLE (N/A): Verification methods do not apply. Indicates that the item is not
anticipated as a test verification requirement.
SECTION 4: VERIFICATION REQUIREMENTS
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
78
4.2 Specialized verification requirements
a. All GPC System components that connect to common carrier facilities must be registered
with the Federal Communications Commission in accordance with Title 47 CFR part 68 and
with 800.170 of NFPA-70.
b. All GPC System equipment subject to FCC rules and regulations as set forth in 47 CFR part
15 must be tested and certified to those standards.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
79
5 ACRONYMS AND ABBREVIATIONS
0TLP zero transmission level point
A/G Air-to-Ground
AGC Automatic Gain Control
ac/AC Alternating Current
A(i) Inherent Availability
ANSI American National Standards Institute
APC Air-to-Ground Protocol Converter
ATC Air Traffic Control
ATCS Air Traffic Control Specialist
ATM Air Traffic Management
ATSS Airway Transporation System Specialist
BIT Built-in Test
BITE Built-in Test Equipment
CFR Code of Federal Regulations
CMT Corrective Maintenance Time
CODEC Coder/Decoder
CPU Central Processing Unit
CS-ACELP Conjugate Structure Algebraic Code Excited Linear Prediction
CWP Controller Working Position
ºC Degrees Celsius
dB Decibel
dBa Decibels Acoustical
dBm dB above 1 mW
dBm0 dB at TLP
SECTION 5: ACRONYMS AND ABBREVIATIONS
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
80
dBrnC dB above reference noise, C-message weighted
dBrnC0 dB above reference noise, C-message weighted, at 0 TLP
DP Dial Pulse
DSP Digital Signal Processor
DTMF Dual Tone Multi–frequency
dc/DC Direct current
DX Duplex
ESD Electrostatic Discharge
EMI Electromagnetic Interference
E&M Ear and Mouth
EUROCAE European Organization for Civil Aviation Equipment
FAA Federal Aviation Administration
FCC Federal Communications Commission
FRU Floor Replaceable Unit
GFE Government-furnished equipment
G/G Ground-to-Ground
GHz Gigahertz
GPC Ground-to-Ground Protocol Converter
GPCMS GPC Management Subsystem
GUI Graphical User Interface
HF Human Factors
Hz Hertz
IA Indirect Access
IC Intercomm
IDF Interemediate Distribution Frame
IETF Internet Engineering Task Force
IP Internet Protocol
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
81
IRD Interface requirements Document
kHz kilohertz
LAN Local Area Network
LQO Listening Quality Objective
LRU Line Replaceable Unit
lb/ft2 Pound-force per square foot
MHz Megahertz
MOS Mean Opinion Score
ms Millisecond
MSDS Material Safety Data Sheet
msec Millisecond
MTBF Mean time Between Failures
MTBCF Mean Time Between Critical Failures
MTTR Mean Time to Repair
mW Milliwatt
NAS National Airspace System
NIC Network Interface Controller
NFPA National Fire Protection Association Standard
NTP Network Time Protocol
OSHA Occupational Safety and Health Administration
OVR Override
PABX Private Automatic Branch Exchange
PBH Peak Busy Hour
PBM Peak Busy Minute
PCB Polychlorinated Biphenyls
PCM Pulse Code Modulation
PSTN Public Switched Telephone Network
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
82
PTT Push-to-Talk
RFC Request for Comments
rms Root Mean Square
RTP Real Time Protocol
RTQC Real Time Quality Control
Rx Receive
sec Second
SIP Session Initiation Protocol
SS Selective Signaling
SF Single Frequency
TB Tone Burst
TIA Telecommunications Industries Association
TIA/EIA Telecommunications Industry Association / Electronic Industries Association
TL Transmission Level
TLP Transmission Level Point
TOA Tone on Active
TOI Tone on Idle
Tx Transmit
UTC Universal Time Coordinated
V Volts
VA Volt-amperes
VCS Voice Communication System
VF Voice Frequency
VoICE Voice over IP Communication Enterprise
VoIP Voice over Internet Protocol
VOX Voice–Operated Switch
VRTM Verification Requirements Traceability Matrix
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
83
WAN Wide Area Network
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
84
6 GLOSSARY
Activate - to set in motion; cause to function or act. See also “key(ing)”.
Active Call or Position Active Call - a call (placed or received) under the control of position
operator, and to which they are conversant.
Address - a character or group of characters that identifies a register, a specific part of storage,
or some other data source or destination, to refer to a device or an item of data by its address.
Ai - a measure of availability from a design perspective. The formula for inherent availability is
equal to the calculated mean time between failure (MTBF) divided by the sum of the MTBF plus
the mean time to repair (MTTR) or Ai = MTBF/(MTBF+MTTR).
Air Traffic Control (ATC) - refers to the tactical aircraft safety separation service and to
organize and expedite the flow of traffic.
Air Traffic Management (ATM) - the composite process ensuring the safe, efficient and
expeditious movement of aircraft. Air traffic control and traffic flow management are
components of the air traffic management process.
Any – One, some, every or all without specification or identification.
Assembly - a number of parts or subassemblies or any combination thereof joined together to
perform a specific function and capable of disassembly.
Assign - a configuration action that provides specific A/G, G/G communication connectivity
capabilities and other communication feature capabilities to air traffic control and ancillary
positions.
Audio Delay - the length of time it takes sounds to traverse a circuit.
Audio Routing - a function that allows for establishment of different output paths through the
system for incoming audio. Paths may include routing to operator position loudspeaker(s) or
headset / handsets. Audio routing may be accomplished manually or automatically.
Auditable Event - Identification of events which are significant and relevant to the security of
the information system and are deemed to be adequate to support after-the-fact investigations of
security incidents.
SECTION 6: GLOSSARY
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
85
Background Mode - In a multi-program system, the condition under which low-priority
programs are executed. The execution of data processing operations that are secondary to real-
time voice switching and control.
Background Noise - Noise level present on a connected voice circuit.
Backup - a provision for an alternate means of operation in case the primary means is not
available.
Baseline - The approved, recorded configuration of one or more configuration items, that
thereafter serves as the basis for further development, and that is changed only through change
control procedures.
Blocking - the inability of a telecommunications system to establish a connection due to the
unavailability of paths.
Busy - a condition that exists when a called position has an active call in progress and a full CA
queue. A call processing tone that is generated when the above condition exists at a called
position (G/G only).
Call - a demand to set up a communication connection.
Call Features - Call forwarding, call monitoring, supervisory recording, headset or loudspeaker
call routing, call queuing with caller identifications, etc. Types of calls are made in certain
modes with certain features invoked; for example, an interphone (type), indirect access (mode),
override (feature) call that is monitored (feature) and recorded (feature) by the calling party’s
supervisor.
Call Modes - Direct access, indirect access, and voice call.
Call Progress Tones - a tone provided by a telephone switch or Legacy VCS that informs the
calling party of the progress of a call. Common progress tones are dial tone, ringback tone, busy
tone, and error tone.
Call Release - the function of ending a G/G call. In addition, the time interval from sending
equipment a signal to close down the call to the time a “free condition” appears and the system is
ready for another call.
Call Setup - in a telecommunications system the process of establishing a call by creating a
connection between stations.
Call Types - Intercom and interphone.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
86
Calling Line Identification or Caller ID - a feature whereby a call source is automatically
identified to the called position.
Capacity Management - a system’s ability to monitor individual components for utilization and
capacity.
Catastrophic Failure - Failure that is both sudden and complete.
Channel - a communication path providing one-way or two-way transmission between two
terminations.
Circuit - (1) A network providing one or more closed paths. (2) An interconnection of
electrical/electronic elements. (3) A conductor or system of conductors through which an
electrical current is intended to flow (e.g., SS-4 tone burst, DTMF tone burst, dial pulse train).
Commercial Standard - Standard established by a commercial organization or corporate entity
governing design, development, documentation, control, manufacture, production, testing, etc.,
of its commercial and internal products.
Commercial-Off-The-Shelf - is a product or service that has been developed for sale, lease or
license to the general public and is currently available at a fair market value.
Communications Resource - as used in this document, a G/G voice circuit.
Complete Failure - Failure resulting from deviations in characteristics beyond specified limits
such as to cause complete lack of the function.
Conference Calling - a feature that connects three or more parties together into one G/G call.
Configuration - The arrangement of a computer system or network as defined by the nature,
number, and the chief characteristics of its functional elements. The functional or physical
characteristics (or both) of systems hardware/software.
Configuration Map - a correspondence set between hardware elements and software elements
based on their chief functional and physical characteristics in an arrangement that provides
communications assignments and capabilities through applications of operational and service
classmarks (also see Program Control).
Configuration Plan - a set of assignments of A/G and/or G/G communications resources and
control features for an operator position(s) by authorized access levels, which changes the
connectivity and functionality at the position(s) upon execution of a configuration plan. A
configuration plan is also known as a “map”.
Connectivity - An established circuit.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
87
Corrective Maintenance Time (CMT) - the elapsed time required to restore a system to a
specified level of performance.
Critical Failure - a failure that is likely to result in the system or subsystem inability to perform
the required functions.
Critical Power Distribution System (CPDS) - that portion of a facility electrical distribution
and generation system that provides power to the equipment operating in support of critical air
traffic control functions or services.
Crosstalk Index - The probability, expressed in percent, of a system user hearing one or more
intelligible crosstalk words during a call. In the Bell System, for the Loop Plant, the
recommended performance objective for network planning and equipment design is that a 0.1%
crosstalk index not be exceeded for 99% of the loops in the plant.
Cut Through - The process of dialing a called party via the seized legacy trunk, by sending each
address digit as collected.
Demonstrated Technology – non prototype mature operational technology which exists and has
existed in the marketplace which known reliability.
Database - a collection of data fundamental to the operation of a system or enterprise. Database
usually connotes a systematized collection of data that can be immediately accessed and
manipulated by a system for a specific purpose. Data Bank describes any collection of data that
may or may not be interrelated or immediately accessible by a system.
Database Integrity Verification Application– Is a database integrity verification application to
validate compliance with data base development rules.
dBm - a logarithmic measure of a power with respect to a reference power of milliwatt (one one-
thousandth of a Watt). dBm = (10) log (P/0.001 Watt)
dBm0 - a logarithmic measure of power (in dBm) at the Zero Transmission Level Point (0TLP)
to produce the same power in dBm at another point in the circuit using a 1.0 KHz tone.
dBmC0 - The test tone 1000 Hz power level measured at the 0TLP using a “C” message
weighting network.
dBrn - a logarithmic measure of power with respect to a reference power of one picowatt (-90
dBm), used for noise tests. 0 dBm = 90 dBrn or dBrn = (10) log (P /10-12 Watt)
dBrnC - a logarithmic measure of power relative to a noise reference of -90 dBm as measured
with a noise meter weighted by a special frequency function called C-Message Weighting. The
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
88
interfering effect of noise given in dB above a noise reference of -90 dBm at 1.0 KHz measured
with a C-message filter.
dBrnC0 - Noise measured in dBrnC and referred to the 0TLP.
Deactivate - to inhibit, block, or disrupt the action of.
Decibel (dB) - a logarithmic measure of the ratio between two powers. dB = (10) log (P2/P1)
Degradation Failure - Failure that is both gradual and partial.
Diagnostics - conducting a test or series of tests on a device, system, or subsystem to obtain data
that will be analyzed to determine the source of a problem.
E&M - a signaling method for transferring supervisory and control information over a trunk
circuit using the signal circuits “E” and “M” leads. The “E” lead transmits into the trunk circuit
and the “M” lead transmits into the signal circuit.
Erlang - a unit of telephone switch traffic intensity measured in number of arrivals per mean
service time. For carried traffic measurements, the number of erlangs is the average number of
simultaneous connections observed during a measurement period.
Error - an abnormal operation of software, hardware, or human activity.
Event Log - a time-stamped record of system changes in alert messages, security events, mode
and state changes.
Execution Stage – The stage of reconfiguration that invokes a specific command.
External Stations - refers to an operator position on a PBX or a Legacy VCS at another facility.
Facility-Level Reconfiguration - a change of communication assignments and control
capabilities wherein the modification or changeover occurs with respect to facility maps (also see
Facility Backup and Reconfiguration).
Failure - the event, or inoperable state, in which any item or part of an item does not, or would
not, perform as previously specified.
Fault - an abnormal operation of hardware or software.
Fault Indication - a visual or audio alert indicating that a fault has occurred.
Floor Replaceable Unit (FRU) - a LRU that, for functional purposes is located on the
operational floor of an ATC facility (e.g., Operator Position equipment inclusive of controller
interface equipment) .
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
89
Functionality - The characteristics of one or more equipment whose configuration provides the
capability to perform specified activities.
Functional Path - The set of physical items/equipment necessary to initiate, sustain, and
terminate operation of a given function (e.g., radio, IC, or IP).
Glare -The condition that occurs when a trunk is seized at both ends simultaneously where the
incoming seizure takes precedence.
Gradual Failure - Failure that could be anticipated by prior examination or monitoring.
Ground-to-Ground (G/G) - voice transmissions over IC, IP, or OVR using the VCS, external
networks, or using outside phone lines.
Hold/Suspend - The capability of suspending a call in progress while placing or answering
another call.
Hook Flash - momentarily depressing (up to eight tenths of a second) the hook flash button of a
telephone instrument can initiate various services such as calling the attendant, conferencing
calls, transferring calls and answering a call coming in on a line equipped with call waiting.
Human/System Interface - See Man/Machine Interface.
Idle - not being used, but ready or selected (a.k.a. not keyed).
Idle Channel Noise - Noise level present on an unconnected voice circuit.
Immediate Dial – the most basic protocol. In this technique, the Legacy VCS goes off hook,
waits for a finite period of time (for example, 200 ms), then sends the dial digits to the far end.
Industry Standard - Standard established by authority of a professional, technical, or industrial
organization (association, institute, society, etc.) such as ANSI, EIA, or IEEE.
In-Service Circuits - Those time-shared circuits of the system which achieve a desired grade of
service. The failure of one or several will not make the system inoperative, but may degrade the
service during peak load.
Intelligible Crosstalk - The speech signal transferred from one voice channel to another which
is sufficiently understandable under pertinent circuit and room noise conditions that meaningful
information can be obtained by the disturbed party.
Interface - a mechanical or electrical link connecting two or more pieces of equipment together.
Intermediate Distribution Frame - a distributing frame used to terminate in-house cabling.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
90
Interphone - Communications between controllers at different facilities utilizing legacy G/G
trunks. Refers to operator position-to-legacy analog trunk or legacy analog trunk-to- operator
position calls.
Key(ing) - as used in this document, to activate PTT signaling in order to transmit over a
selected radio(s). In telephony a switch, or representation of a switch on a touch entry display,
that commands a system to set up a communications path.
Keypad – an interface (a group of keys) that allows for a user to input data to a computer or
other electronic device. Key functions may be permanently or dynamically assigned to device
operations.
Latching - a function that either is or emulates a pushbutton that locks in the down position upon
a first touch, and requires a second touch to release the locked condition. The desired activation
is in effect for the time the button is in the locked position.
Latency - is a time delay between the moment an audio transmission is initiated, and the
moment one of its effects begins or becomes detectable.
Legacy - an FAA system that is currently in operation in the NAS.
Line - a family of equipment and devices designed to provide users with access to a choice of
communication services and features. A physical channel between the position equipment and
G/G and the main frame.
Line Circuit - The circuitry required to terminate, convert, and provide transmission,
supervisory and control signals at the position side of the interconnection networks, and at the
position and/or equipment end instruments. This circuitry can be divided between actual
network terminations and position equipment terminations. This includes all circuitry that
interfaces the position with the interconnection networks and the common control.
Line Replaceable Unit (LRU) - Any system item that is replaceable at the organizational
maintenance level without using any special tools level to restore the operation after a failure.
Also known as Lowest Replaceable Unit.
Loop-Back Testing - a standard telephone test procedure involving accessing the circuit at any
test access point and sending test signals down the line. The test signals are returned (looped
back) to the test access point where diagnostics are then performed on the returned test signals.
The loop-back points are located progressively further away from the test access point until
either the fault has been detected or the entire circuit has been tested.
Loop Closure - a communications path that joins an originating position back to itself through
one or more operator positions.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
91
Main Distribution Frame - a distributing frame used to terminate leased and Government-
owned long-line facilities on the one side and cable pairs for line and trunk equipment terminals
associated with a switching system on the other side. The main distribution frame is the
interface point used for associating any outside line or trunk with any desired equipment terminal
or with any other outside line or trunk. It usually serves as a test point between in-house and
outside plant cabling.
Main (or Standby Units) - Units that are operationally critical and are redundantly integrated
into the system to achieve a high degree of reliability.
Maintenance State - An GPC in the maintenance state is operating in the online state in all
ways, except that resources in a maintenance state are functionally segregated from resources in
an operational state.
Maintenance Data Terminal (MDT) - an external device that can interface to and access the
RMMS via a NAS managed subsystem or RMMS processor.
Maintenance Log - a time-stamped record of system health, LRU configuration, fault
indications, failure history, and diagnostic results.
Maintenance Position - A common console area configured to allow activities specific to
performing maintenance activities (e.g., test point access, duplicate operator position equipment,
duplicate workstation equipment, printer equipment, indicators, power supply monitoring and
service points, etc.). (also see Ancillary Position).
Man/Machine Interface - (Pertaining to station control and data acquisition). The operator
contact with equipment governed by ANSI IEEE C37. MIL-STD-1472 is recommended as a
reference for use in the design and evaluation of the man/machine interface.
Manual Ring - a selective signaling arrangement that consists of a manual ring (re-ring),
generated by the calling party, to alert a specific station on a multidrop circuit in which all
stations receive the ringing signal.
Map - To establish a correspondence between the elements of one set and the elements of
another set. A correspondence set between elements of one set and elements of another.
Maximum Corrective Maintenance Time - that value of maintenance downtime within which
a specified percent of all maintenance actions must be completed.
Mean Talker Level - Specified at -13.9 dBm0, which is 0.9 dBm less than the maximum voice
frequency (VF) signal (average more than 3 seconds) on a standard VF channel and 2.1 dBm
more than the VF channel interface standard.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
92
Mean Time Between Failure (MTBF) - a basic measure of reliability for items: the mean
number of hours during which all parts of the item perform within their specified limits, during a
particular measurement interval under stated conditions.
Mean Time to Repair (MTTR) - a basic measure of maintainability. The formula is equal to
the sum of Corrective Maintenance Times (CMT) divided by the total number of failures for a
system. MTTR is also a measure of direct labor to correct unscheduled system or equipment
outages. It excludes logistics and administrative time (e.g. travel time, time waiting for spare
parts or test equipment, record keeping time).
Mission Critical Component - a hardware component responsible for processing or routing
VoIP traffic (e.g., Operator Position, A/G and G/G Interfaces, Proxy server, Conference server).
Mode - a possible, customary, or preferred way of doing something.
Modular - The extent to which hardware/software is composed of discrete components such that
a change to one component has minimal impact on other components.
Module - a limited aggregate of LRUs, data, and contiguous codes that performs independent
functions. Typically, modules are used repeatedly in the construction of the system.
Monitor - To listen in on the communications of another controller.
Multiple - Providing more than one connection at a common point.
Multi-drop Trunk - a dedicated trunk shared by three or more positions at two or more
facilities.
Network Call – a VoIP call over any Ethernet protocol.
Network Element (NE) - is hardware equipment that is addressable and manageable. NEs
provide support or services to the user and can be managed through an element manager.
Network Interface – the Internet Protocol (IP) interface to the Government Transport System.
Non-Blocking - a capability of the network such that the total number of available transmission
paths is equal to the number of ports. Therefore, all ports can have simultaneous access through
the network.
Non-Developmental-Item (NDI) - is an item that has been previously developed for use by
federal, state, local, or a foreign government and for which no further development is required.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
93
Non-Latching - a feature which either is or emulates a pushbutton that requires an operator to
provide continuous touch action to maintain the desired pushbutton activation. The activation is
terminated by the release of touch action on the pushbutton.
Non-Selective: This term refers to point to point communications where no address signaling is
required or provided. No ability to selectively call a position on the circuit is provided.
Off-Hook - One of several line/trunk supervisory signals. Normally a line/trunk state change of
idle-to-off indicates a request for service.
Off-Line - an equipment condition wherein equipment is operating independently, or is
disconnected from, the primary system and not available for ATC use.
Off/Out of Service State - a state in which equipment is not available to perform
communications functions.
On-Line - (1) An operating condition wherein input data enters the system directly from the
point of origin or in which output data is transmitted directly to where it is used. (2) The
operations of a functional unit that are under continuous control of a central or main processing
unit.
On/In Service State - a state in which the system or equipment is under power, is available to
perform communications functions, and is not undergoing maintenance.
Open Format - a published specification for storing digital data, usually maintained by a non-
proprietary standards organization, and free of legal restrictions on use.
Operational Communications Resource – a G/G circuit supporting ATC operations.
Outgoing Supervision Signal – A communication line that is used to carry the transmit control
signal (e.g., M-lead).
Outlier - Data point which is not typical of the rest of the data; it may lie three or four standard
deviations or further from the mean of the sample.
Outpulsing - Pulsing from a sender.
Overlapping – To coincide in part with; have in common with.
Override (OVR) - a call feature whereby a call being placed results in connection to the called
party, even if the called position has an active call in progress.
Override Call Chaining – a situation where party A overrides party B who is overriding party
C, etc.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
94
Private Automatic Branch Exchange (PABX ) - a private automatic telephone switching
system that provides for transmission of calls to and from the public switch telephone network,
and private switched or dedicated telephone networks.
Partial Failure - Failure resulting from deviation in characteristics beyond specified limits, but
not such as to cause complete lack of the required function.
Party - a person or group of persons who participate in a G/G call or conference; the person
under consideration.
Peak Busy Hour (PBH) - a value for the most traffic, in call attempts, during a single hour.
Peak Busy Minute (PBM) - a value for the most traffic, in call attempts, during a single minute.
Peripheral Equipment - subassemblies or devices provided by subcontractors or vendors to
perform a specific function. Examples may include uninterruptible power supplies and fiber
optic communications equipment.
Performance-Based Airspace - regulatory definition of performance requirements in airspace.
Performance Controls – a system’s ability to limit the use of individual component resources
and provide alerts when configured limits have been exceeded.
Physical Map - a correspondence set of the functional and physical characteristics of hardware.
Plenum Rated - a type of cabling that is fire retardant and approved for use in air returns.
Private - a non-conferencing communications circuit, that when it is in-use by the first caller,
prohibits anyone else from joining the call.
Push-to-Talk (PTT) - a method of communication over a speech channel in which transmission
occurs in only one direction at a time; while talking the talker is required to keep a switch
activated (continuous touch action).
Pulsing - The signaling over the communication path of signals representing one or more
address digits required to set up a call.
Real Time - the actual time during which a process or event takes place. Real time processing
indicates that data is processed by a system as soon as it is entered.
Real Time Quality Control (RTQC) - Real time quality control is the on-line capability of fault
detection, isolation, and reporting in real time.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
95
Reconfiguration - a change of communication assignments and control capabilities through the
modification of the invoked configuration map or through a changeover from one map to
another. Reconfiguration can take place at the position, sector, area, and facility levels.
Recovery - restoration or return to proper operation.
Redial - a call function that dials the number of the previous call placed.
Release - the process of ending a G/G call.
Remote Access - Access that involves communications across physical facility boundaries.
Resource – a resource is a service (e.g., G/G circuit) that can be used or assigned. Resources
include transmission lines, switching systems, data processing devices, security processes, or
transmission capacity.
Resource Analysis – the ability to monitor the health and volume of traffic throughout a system.
Return Loss - the return loss at an impedance discontinuity on a two-wire line is the ratio,
expressed in decibels, of the level of incident signal to that of its reflected signal. The return loss
on a four-wire line is the insertion loss measured between transit and receive pairs with the far
end terminated as specified. Echo return loss is a weighted average (on a power basis) of the
return loss at all frequencies in the range 500 to 2500 Hz. Single-frequency return loss is the
lowest non-weighted return loss in the 0.2 to 3.2 KHz band.
Reverted - to return to a former condition.
Ringback - a tone that indicates to a caller that a ringing signal is being applied to a called
station.
SS-1/SS-4 Dial Digits – Tone sequences used to represent 2 and/or 3 digits dialed in a FAA
Selective Signaling system to provide speed dial connections between facilities throughout the
NAS.
Screen - the portion of a terminal or monitor upon which information and controls are displayed.
Secure State - a condition in which a system is protected from the activities of unauthorized
access and the unauthorized activities of trusted agents.
Select - An action at an ATC or ancillary position touch entry display or interactive display
which results in the activation of an A/G communication connectivity at that position.
Selective: This term refers to address signaling to selectively communicate between multiple
positions configured to communicate on an analog trunk. point to point communications where
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
96
no address signaling is required or provided. No ability to selectively call a position on the
circuit is provided.
Selective Signaling (SS) – a network control process in which signaling information relating to a
multiplicity of circuits (trunks), is conveyed over a separate single channel by addressed
messages. Selective signaling system #7 ("SS7") is the primary system used for interconnection
of telephone systems. SS7 sends packets of control information between VCSs.
Sender - Equipment that generates and transmits signals in response to information received
from another part of the system.
Senderize – The process of collecting all address digits required to dial a called party and then
sending all digits sequentially via the seized legacy trunk.
Service Circuits - Those time-shared circuits of the system which achieve a desired grade of
service. The failure of one or several will not make the system inoperative, but may degrade the
service during peak load.
Simultaneously - occurring or operating at the same time; concurrently.
Single Point Failure - a failure of a single item which has the effect of failing an entire function
or functionality.
Signaling - With respect to telephone switching systems; the transmission of address and other
switching information between stations and central offices, stations and switching entities, and
between switching entities.
Site - Any location where equipment is to be supplied or installed.
Site-Specific - pertaining to something that is confined to, or valid for, a particular facility.
Sound Pressure Level (SPL) - An acoustical intensity expressed in decibels above a reference
level of 0.0002 dynes/square cm.
Specialist - an operator or maintainer of a system. Examples include Air Traffic Control
Specialist (ATCS), a traffic management specialist, or an Airway Transportation System
Specialist (ATSS). Also referred to as users.
Speed Dial - the ability to recall and apply a prerecorded sequence of digital entries. This must
include, but not be limited to, alphanumeric entries. It may include other information, such as,
line selection, etc.
Standard - Regularly and widely used, available, or supplied; definite rule for measurement of
quantity, weight, extent, value, or quality as established by authority.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
97
Standards-based - ISO or ANSI standardized software language including but not limited to C,
C++, C#. The standards elements consist of the core language and standard libraries of functions
are used to develop application code
Subassembly - Two or more parts that form a portion of an assembly or a unit replaceable as a
whole, but having part or parts that are individually replaceable.
Subsystem - a combination of sets, groups, etc., that performs an operational function within a
system and is a major subdivision of the system.
Sudden Failure - Failure that could not be anticipated by prior examination or monitoring.
Supervisory Signaling - Supervisory signals are signals used to indicate or control the states of
circuits involved in a particular connection. A supervisory signal indicates to equipment, to an
operator, or to a user that a particular state in the call has been reached and may simplify the
need for action.
Suspend - to cause to cease or bring to a stop or stay for a period of time.
System - The equipment, hardware/software or subsets of two that fulfill the functional
requirements of this document.
Telecommunications - communicating over a distance by telephone and radio including the
transmission, reception, and switching of signals.
Telephone Position Circuit - All circuitry required to permit the telephone instrument or
headset to access all voice transmission paths terminating at the position.
Toll Quality - the audio transmission at the quality level of an ordinary long distance telephone
call. Toll quality is measured using the PCM64 standard or ITU-T P.800 standard, which utilizes
mean opinion scoring of four or five points out of five, points possible.
Tone Suppression Filter – function that performs the removal of any tones in the receive audio
at the operator position.
Traffic Log - a time-stamped record of A/G and G/G call traffic, call status, switch loading,
voting per radio.
Transmission Level Point - a signal-measuring point, defined during the transmission system
design, where a signal level is specified in relative, but not absolute, terms. 0TLP refers to the
zero transmission level point which, in contemporary design practices, is an arbitrary reference
along a transmission path. The transmission level at any other point is the nominal design gain
(or loss) in decibels relative to zero transmission level at 1.0 KHz.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
98
Trunk – an analog communication channel between two Legacy VCSs. A two-wire or four-
wire circuit that can be a leased or a Government-owned transmission facility connecting a
Legacy VCS with external or remote equipment. The analog trunk will normally include the
protection and isolation equipment when leased facilities are used.
Trunk Circuit - The circuitry being controlled by a Legacy VCS to directly connect with
another Legacy VCS.
Trunk Group - a number of trunks that can be used interchangeably between two or more
Legacy VCSs.
Trunk Multi-Point - a dedicated trunk that is shared by three or more positions, at two or more
facilities.
Unit - An assembly or any combination of parts, subassemblies, and assemblies mounted
together, normally capable of independent operation in a variety of situations.
Unmonitored - a radio that is assigned but for which the RX has been deselected at all positions
having the assignment.
Unwanted Tones - spurious audio at levels potentially damaging to human hearing according to
29 CFR 1910.95.
Usability (Ease of Use) - the perceptual and physical characteristics of the human-system
interface; includes general issues regarding the ability of users to operate the system as well as to
read, detect, access, and manipulates information.
Voice Call - a call mode wherein initial circuit connectivity is always to the loudspeaker at the
called position. Prior to answering, the called party must switch the connection (single touch
action) to his or her headset. Voice calling is an overlay mode, that is, it can be used in
conjunction with direct access or indirect access modes. Also known as group alerting.
Voice Call Circuit - a special connectivity path for processing voice calls to selected
loudspeakers.
VOX - any interfaces to control voice connectivity based upon the magnitude of audio-frequency
energy in the transmitted signal (e.g., voice call).
VOX Detection Threshold- the level at which VOX threshold must be broken to declare a
seizure.
VOX Attack Time - the duration that the VOX level must exceed the VOX threshold to declare
a valid seizure.
DTFAWA-12-C-00063 Part III, List of Documents, Exhibits, and Other Attachments
03/15/2021 Attachment J-X, VoICE GPC Technical Specification
FAA Announcement No.
693KA8-21-RFI-GPC-02
Attachment 01
99
VOX Release Time - the duration that the audio level must be below the VOX threshold before
declaring a release.
Winking - a visual signal interrupted 60 times per minute with a 95:5 on:off ratio.
Wink Start – the most commonly used protocol. In this technique, the Legacy VCS goes off-
hook, waits for a temporary off-hook pulse from the other end (which is interpreted as an
indication to proceed), then sends the dial digits.
Workstation - a personal computer (PC) to perform supervisory and maintenance functions.
Zip Tone - a 0.2 second burst tone.