2 DRAFT VCS SRD v0 3Aug23.pdf

CAUTION: This document contains competitive, sensitive or other non-public information not intended for disclosure outside official government channels. Do not disseminate this document without the approval of the above signed office. If you received this document in error, please notify the sender by reply email and delete all copies of this document/message.

System Requirements Document

For the

Voice Control Switch Document Number: [2023A0175-T]

Version: 0

Version Date: 3 Aug 2023

Prepared By:

AFLCMC/HBAA

3508 D Ave., Bldg 201W, Room 74 Tinker AFB, OK 73145

Approved By: Approved By:

MARY M. COOLEY, NH-IV, DAF JAMES B. ROBERTS, GS-15, DAF

Chief, ATCALS Sus. & Mod. Branch Director, Programs and Requirements Aerospace Management Systems Division HQ AFFSA

Version: 0, 3 Aug 2023 Page ii of ii

RECORD OF CHANGES

REVISIONS

VERSION# DESCRIPTION DATE APPROVED

0 Original Release 3 Aug 2023

Voice Control Switch

Version: 0, 3 Aug 2023 Page 1 of 12

1. SCOPE

1.1. SYSTEM IDENTIFICATION. The existing United States Air Force (USAF) and United States Navy

(USN) fixed base Voice Control Switch (VCS) is the AN/FSC-127 Enhanced Terminal Voice Switch (ETVS). The USAF and USN are replacing the ETVS under this acquisition effort. The USAF also has a tactical voice switch installed in the AN/MSN-7 Communication Central, the USAF’s mobile air traffic control (ATC) tower. The MSN-7 voice switch is the ProComm 1540. The ProComm switch will be replaced with a tactical version of the ETVS replacement.

1.2. SYSTEM OVERVIEW. The ETVS provides connectivity between an air traffic controller and the radios, telephone lines and other controllers. The ETVS is Time Division Multiplexing (TDM) switch and is approaching 30 years old, causing it to be difficult to maintain. In addition, as the USAF and USN move to Voice over Internet Protocol (VoIP) phone lines, the ETVS requires special converters to remain functional. Finally, the DoD has mandated the replacement of all TDM switches. These factors have contributed to the decision to replace the ETVS with a digital system that meets all ETVS and ATC functionality.

1.3. DOCUMENT OVERVIEW. This System Requirements Document (SRD) provides performance requirements for procuring a replacement for the ETVS and ProComm 1540.

1.4. REQUIREMENTS ORIGIN. Headquarters Air Force Flights Standards Agency (HQ AFFSA) provided two AF1067s, one titled Air Traffic Control Voice Control Switch/ ETVS Replacement dated 6 April 2023 and one titled “MSN-7 Voice Communication Switching System (VCSS) Replacement dated 23 May 2023. This document is based upon those AF1067s, as well as on the ETVS and ProComm (MSN-7 VCSS) specifications.

2. APPLICABLE DOCUMENTS

2.1. GENERAL. The applicable documents listed form a prerequisite to meet the requirements contained within this SRD. Documents marked with an asterisk (*) are specifically called out within subsequent specifications. Documents without asterisks (*) are not specifically called out but are still considered part of the base level requirement unless otherwise specified as

“REFERENCE ONLY”.

2.2. GOVERNMENT DOCUMENTS. The following government documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

2.3. CURRENT SYSTEM TECHNICAL ORDERS. These documents are to be used to determine the current configuration, procedures or anything related to use of the current fielded systems.

Table 2.3 Number Title Date FAA Order 6400.1 Maintenance of Air Traffic Control Communication

Services 31R2-2MSN7-4-1907-1 Voice Communication Switching System, Instruction

Manual, Rev C 3/15/2008

A1000158 CUI: Voice Communication Switching Subsystem (drawing)

5/20/2019

Version: 0, 3 Aug 2023 Page 2 of 12

2.4. GENERAL TECHNICAL ORDERS

Table 2.4 Number Title Date 00-25-234 General Shop Practice Requirements for the Repair, Maintenance, and Test of Electrical Equipment 10/27/2021

The following general Technical Orders are REFERENCE documents:

31-10-24 Installation Practices, Communications Systems grounding, Bonding, and Shielding 11/15/2011 reinstated

12/09/2019

31Z3-822-2 ATCALS Site Requirements 08/12/2019

2.5. INSTRUCTIONS AND MANUALS

Table 2.5 Number Title Date AFMAN 91-203 Air Force Occupational and Environmental Safety, Fire

Protection and Health (AFOSH) Standards 03/25/2022

AFMAN 11-231 Computed Air Release Point Procedures 11/18/2020

DoDI 4650.01 Policy and Procedures for Management and Use of the Electromagnetic Spectrum

10/17/2017

TM 3-34.43 Materials Testing 04/2015

The following Instructions and Manuals are REFERENCE documents: You are to use the latest date as of the date of proposal

AFMAN17-

1203_AFGM2020-01

Information Technology Asset Management 09/13/2022

AFI 17-101 Risk Management Framework (RMF) for Air Force Information Technology (IT) as amended by Department of the Air Force Guidance Memorandum (DAFGM) to Air Force Instruction (AFI) 17-101, RMF for Department of The Air Force Information for Department of the Air Force Information Technology (IT)

02/05/2020 as amended 06/10/2022

AFI 17-130 Air Force Cybersecurity Program Management 02/13/2020

AFI 63-101/20-101 Integrated Life Cycle Management 06/30/2020

Version: 0, 3 Aug 2023 Page 3 of 12

Table 2.5 (cont.)

Number Title Date AFI 91-302 Air Force Occupational and Environmental Safety, Fire

Protection and Health (AFOSH) Standards 4/18/94

AFMAN 13-204,

Vol 4

Radar, Airfield, and Weather Systems 07/22/2020

AFPD 13-2 Air Traffic, Airfield, Airspace and Range Management 01/03/2019

AFPD 17-1 Information Dominance Governance and Management 04/12/2016

DoDI 8510.01 Risk Management Framework (RMF) for DoD Systems 07/19/22

Public Law No: 113-

SUBCHAPTER II--

INFORMATION

SECURITY

Federal Information Security Modernization Act of 2014

(FISMA 2014)

12/18/2014

2.6. SPECIFICATIONS, STANDARD, ORDERS AND ADVISORY CIRCULARS

Table 2.6 Number Title Date The following Government Standard documents are MANDATORY and REQUIRE COMPLIANCE.

The solution will be tested to or using the following Standards. You are to use the latest date as of the date of proposal.

MIL-HDBK-454C General Guidelines for Electronic Equipment, Note: Particular attention to be given to Guidelines 1, 5, 9, 15 & 66

09/21/2021

MIL-STD-

129R_Chg2

Military Marking for Shipment and Storage 02/18/2014 09/27/2019

MIL-STD-130N

Chg 1

Identification Marking of U.S. Military Property (Notice 1) 12/17/2007 08/26/2019

MIL-STD-1472H Human Engineering 09/15/2020

ANSI/ESD S20.20-

Protection Of Electrical And Electronic Parts, Assemblies And Equipment (Excluding Electrically Initiated Explosive Devices)

MIL-STD-188-124B Grounding, Bonding and Shielding (Notice 4) 12/18/2000 04/04/2013

MIL-STD-2073-

1E_Chg-4

DoD Standard Practice for Military Packaging 04/22/2019

MIL-STD-810H Test Method Standard: Environmental Engineering Considerations and Laboratory Tests

05/18/2022

MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

12/11/2015

Version: 0, 3 Aug 2023 Page 4 of 12

Table 2.6 (cont.)

Number Title Date

MIL-STD-464D Electromagnetic Environmental Effects Requirements for Systems

12/01/20 1012/24/

MIL-STD-882E System Safety (w/Notice 1, 10 Feb 22) 05/11/20

1202/10/

MIL-STD-810G Test Methods: Environmental Engineering Considerations and Laboratory Tests

10/31/08

MIL-STD-882D DoD Standard Practice for System Safety 2/10/00

EPA Title III, EPA 550-B-021-001

List of Lists, Consolidated List of Chemicals Subject to the Emergency Planning and Community Right-To-Know Act (EPCRA) and Section 112(r) of the Clean Air Act

04/2022

TM-86-01R Air Force Technical Manual Contract Requirements

(TMCR)

06/01/2020

The following Military Standard documents are REFERENCE documents MIL-HDBK-310 Global Climatic Data for Developing Military Products 06/23/19

MIL-HDBK-419A Grounding, Bonding and Shielding for Electronic

Equipment and Facilities, Volume 1 (Basic Theory) and Volume 2 (Applications) - w/Notice 1, 20 Feb 2014)

12/29/19 8702/20/

*MIL-E-4158E General Requirements for Ground Electronic Equipment 1/11/73

2.7. INTERNATIONAL AGENCY DOCUMENTS

Table 2.7 Number Title Date *ICAO Annex 10 Vol 1Fifth Edition

International Civil Aviation Organization (ICAO) International Standards and Recommended Practices, Aeronautical Telecommunications

(Latest)

2.8. NON-GOVERNMENT DOCUMENTS

Table 2.8 Number Title Date EN 55024 Information Technology Equipment – Immunity

Characteristics – Limits and Methods of Measure (Latest)

EN 55032 Electromagnetic Compatibility of Multimedia Equipment

(Latest)

NFPA-70 National Electrical Code, National Fire Protection Agency

(Latest)

NFPA-77 Recommended Practice on Static Electricity (Latest)

GEIA -STD -0005--1

Rev A

Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-free Solder

Mar 2012

Version: 0, 3 Aug 2023 Page 5 of 12

Table 2.8 (cont.)

Number Title Date

GEIA -STD -0005--2

Rev A

Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems

May 2012

The following practices are REFERENCE documents:

IEEE Std 142-1991 Institute of Electrical and Electronics Engineers, Recommended Practices for Grounding of Industrial and Commercial Power Systems

(Latest)

IEEE Std 1100-

Recommended Practices for Powering and Grounding of Electronic Equipment

(Latest)

IEEE Std 519-2014 Recommended Practice and Requirements for Harmonic Control in Electric Power Systems

(Latest)

*GEIA- HB -0005--1

Rev A

Program Management / Systems Engineering Guidelines for Managing the Transition to Lead-free Electronics

Feb 2016

*GEIA-HB-0005-2 Technical Guidelines for Aerospace and Military Electronic Systems Containing Lead-free Solder

Nov 2007

2.9. SYSTEM REQUIREMENTS

2.10. SYSTEM FUNCTIONAL REQUIREMENTS System functional requirements are identified below within specific topics.

2.11. INTERFACE REQUIREMENTS

Table 2.11 Number Description Requirement IF-1 External power Conditioned via Uninterruptible Power System (UPS)

IF-2 Battery power Sustain Critical Circuits for 20 minutes

IF-3 Tactical power Main power shall be 28-volt direct current (VDC) conditioned via UPS

IF-4

(KPP)

Communication interface Perform ATC voice communication over an IP Wide Area Network (WAN) using VoIP.

IF-5 Interoperability Interface with all FAA and AF Air Traffic Control systems to include communications transport via FTI/FENS and/or AF Network.

IF-6 Voice recording Interface all voice communication with the Digital Analog Voice Recorder (DALR) and with NAS Voice Recorder (NVR), all versions.

IF-7 Lightning System lightning shall be suitable for all control tower and radar room lightning conditions.

Version: 0, 3 Aug 2023 Page 6 of 12

2.12. OPERATIONAL REQUIREMENTS

Table 2.12 Number Description Requirement OP-1 A/G and G/G connection System shall establish duplex connection within 230 msec

OP-2 System reconfiguration System shall reconfigure frequencies and voice channels to controller positions in less than 60 seconds.

OP-3 System reconfiguration – service interruption

System reconfiguration shall result in a service interruption of less than 6 seconds

OP-4 DoD interface Interface with all DoD systems

OP-5

(KPP)

Interoperability Interface with all FAA and AF Air Traffic Control systems to include communications transport via FTI/FENS and/or AF Network.

OP-6

(KPP)

Voice recording Interface all voice communication with the Digital Analog Voice Recorder (DALR) and with NAS Voice Recorder (NVR), all versions.

OP-7 Lightning System lightning shall be suitable for all control tower and radar room lightning conditions.

OP-8 ED-137 Compliance The IP interfaces must be 100% ED-137C to avoid any manufacturer specific modifications that might not allow connections to equipment from other manufacturers. For example, the DASR and STARS ED-137 interfaces have manufacturer modifications that prevent compatibility with ED-137 interfaces from other manufacturers.

OP-9 Analog Interface Analog interfaces/gateways shall be provided to connect to existing legacy analog interfaces.

Gateways/converters may be a separate or intermediate piece of equipment.

2.13. TOWER/RADAR COORDINATION Tower/radar coordination is not required.

2.14. CAPACITY REQUIREMENTS The Tactical system was previously referred to as the x-small system.

Table 2.14 Number Description Requirement CAP-1 Number of positions Large: 75 controller, 1 maintenance

Med: 36 controller, 1 maintenance Small: 9 controller, 1 maintenance Tactical: 3 controller, 0 maintenance

CAP-2 Number of Air-to-Ground (A/G) radios

Large: 100 Med: 50 Small: 20 Tactical: 13

Version: 0, 3 Aug 2023 Page 7 of 12

Table 2.14 (cont.)

Number Description Requirement

CAP-3 Number of Ground-to- Ground (G/G) Lines (to include Land Mobile Radio)

Large: 100 Med: 50 Small: 30 Tactical: 15

CAP-4 Number of A/G Radios per Position

Large: 30 Med: 25 Small: 20 Tactical: 13

CAP-5 Number of G/G lines per Position

Large: 50 Med: 50 Small: 20 Tactical: 15

2.15. ENVIRONMENTAL, SAFETY and OPERATIONAL HEALTH REQUIREMENTS

Table 2.15 Number Description Requirement ENV-1 HAZMAT The use of toxic chemicals, hazardous substances, or ozone depleting chemicals (ODCs) shall be avoided, whenever feasible. EPA Title III, List of Lists, EPA 550-B-21-001, provides a listing of toxic chemicals to be avoided.

ENV-2 MSDS The supplier shall provide copies of Material Safety Data Sheets (MSDS) for all hazardous or toxic materials being supplied at least 120 days prior to the first delivery.

ENV-3 Preferred Materials Recycled, recovered, or environmentally preferable materials shall be used to the maximum extent possible provided that the material meets or exceeds the operational and maintenance requirements, and promotes economically advantageous life cycle costs.

ENV-4 OSHA System shall comply with all OSHA requirements per

AFMAN 91-203.

ENV-5 NFPA-70 (NEC) All electrical systems shall comply with the National Electrical Code (NEC).

ENV-6 Grounding Protection System shall meet the requirements of MIL-STD- 188-124B for grounding, bonding, and shielding though the government will be responsible for providing the appropriate ground rod for the delivered systems.

Version: 0, 3 Aug 2023 Page 8 of 12

Table 2.15 (cont.)

Number Description Requirement

ENV-7 Static protection System shall meet the requirements of NFPA-77 for static electricity.

ENV-8 System Safety System shall meet the requirements of MIL-STD-882E, Section 4

ENV-9 Internal Chassis Ground

A ground terminal or equivalent function shall be provided on all subsystems within the equipment.

The ground terminal shall be located on the input power connector or on the equipment terminal board and shall connect to the internal chassis by means of conductors at least equal in size to one of the power input conductors. Safety grounding within the equipment shall terminate on the ground terminal.

Grounds and AC return lines shall be separated.

ENV-10 External Chassis Ground

A ground conductor shall be included with the system power conductors and shall connect to the ground terminal of individual units when power is routed externally between individual units of the equipment.

ENV-11 Safety Shielding System protective shields shall be provided to protect personnel from accidental contact with parts in excess of 30V RMS or 30V DC during operation or maintenance actions.

2.16. CYBERSECURITY REQUIREMENTS

Table 2.16 Number Description Requirement CYB-1 Operating System The operating system for all computers shall be fully compatible and required to run on the current Security Technical Implementation Guide (STIG) version from Defense Information Systems Agency’s (DISA).

CYB-2 Highly Secure For Windows based devices, computers and software shall meet the standards for a highly secure environment published by Microsoft which lists the minimum hardware and software requirements at:

https://docs.microsoft.com/en- us/windows-hardware/design/device- experiences/oem-highly-secure.

For Linux devices, computers and software shall meet the following standards:

Confirm SeLinux is enabled.

Operating in enforcing mode.

A targeted policy is being used.

Reference:https://access.redhat.com/documentation/e n- us/red_hat_enterprise_linux/7/html/selinux_ users_and_administrators_guide/index https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-highly-secure https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-highly-secure https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-highly-secure https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-highly-secure https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-highly-secure https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/index https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/index https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/index https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/index

Version: 0, 3 Aug 2023 Page 9 of 12

Table 2.16 (cont.)

Number Description Requirement

CYB-3 BitLocker All computers and software shall function with BitLocker (or equivalent) encryption enabled.

CYB-4 Encryption Level All connections shall meet AES 256-bit or higher-level encryption.

CYB-5 Network CYB-6 User Level Control System/User accounts shall have a minimum of three tiers of access:

• Viewing status only

• Full maintenance functionality

• Administrative access that allows all functionality and assigning of usernames and passwords.

CYB-7 Maintenance Software (if necessary) Any maintenance software shall include user Identification (ID) and password controls to prevent unauthorized access.

CYB-8 Password Complexity All passwords shall meet the below minimum requirements:

• Be at least 14 characters in length

• Must contain at least 1 uppercase, 1 lowercase, 1 number, and 1 special character (~!@#$%^&*_-

• May not contain the account name associated with the password.

• May not contain more than 2 consecutive characters.

• Password complexity filter must be enabled to disallow use of passwords not meeting these requirements.

CYB-9 Hardware Hardware shall meet the performance requirements below for a STIG compliant operating system and installed contractor software:

• Average computer boot/re-boot times less than 2 minutes.

• Response times average less than 2 seconds.

2.17. TACTICAL SYSTEM REQUIREMENTS These requirements are in addition to requirements listed above but only apply to the tactical version of the system for the AN/MSN-7. All other requirements continue to apply.

Version: 0, 3 Aug 2023 Page 10 of 12

Table 2.17 Number Description Requirement TAC-1 Dimension All central processing equipment must fit in a specified footprint of:

Height: 17.5” Depth: 13.75” Width: 17.25”

TAC-2 Power System/UPS shall operate on 28 VDC power.

TAC-3 Vibration System shall maintain full operational capability after being subjected to vibration testing per MIL- STD-810E, Method 514.4, Figure 514.4-4, Table 514.4.

Single Amplitude to .25G Frequency range: 5-300 HZ with sweep rate of 1 octave/min for test purposes) Duration: 2 Hours per axis

TAC-4 Shock System shall be capable of withstanding the following non-operational shocks and remaining fully functional with no signs of damage or material yielding. For the purposes of testing, a half sign waveform shall be used, three shock pulses per axis, (positive and negative), for a total of 18 shock pulses.

I. Vertical Axis:

1. Amplitude: 30 G.

2. Duration: 25 mSec.

II. Longitudinal Axis:

1. Amplitude: 10 G.

2. Duration: 30 mSec.

III. Transverse Axis:

1. Amplitude: 15 G.

2. Duration: 15 mSec.

TAC-5 Altitude Non-operational (transport): -100ft to 45,000 ft Non-operational (storage): -100ft to 9,200 ft Operation: -100ft to 9,200 ft

TAC-6 Descent rate Descent rate of 10,000 ft/min in accordance with MIL- STD-810E, Method 500.3, Procedure I, II, and III.

TAC-7 Temperature System shall be qualified for the following temperature range:

Operational: 40°F - 88° F Non-operational: -4°F - 140°F

TAC-8 Salt Atmosphere No evidence of rust or corrosion when exposed to salt and fog atmosphere in accordance with MIL-STD- 810, Method 509.3, Procedure I.

Version: 0, 3 Aug 2023 Page 11 of 12

Table 2.17 (cont.)

Number Description Requirement

TAC-9 Fungus Able to withstand exposure to the species of fungi specified in MIL-STD-810.

TAC-10 Sun exposure Surface colors shall not fade. Paint and coatings shall not crack. Items such as gaskets or any other materials shall not show signs of deterioration over a period of ten years.

TAC-11 Mobility System shall be capable of withstanding conditions of Type IV mobility as designated in MIL-STD-1784 (USAAF) on highways and unimproved cross-county terrain with no disassembly required.

TAC-12 Humidity XX% in accordance with MIL-STD-810E, Method 507.3, Procedure III, except for temperatures above 27 °C, where relative humidity shall be based upon a dew point of 27 °C.

TAC-13 MOPP Gear Touch Entry Devices shall be capable of being activated and fully utilized while the operator is in Mission Oriented Protective Posture Gear Level 4.

2.18. MISCELLANOUS REQUIREMENTS

Table 2.18 Number Description Requirement MISC–1 Scalability/modularity Ability to increase system capacity by 15% from original configuration MISC-2 Primary crash notification Single button activation w/visual indicator of conferencing group w/2-way communication and receive only functions up to 15 users.

MISC-3 Secondary crash notification Single button activation w/visual indicator of conferencing group w/2-way communication and receive only functions up to 100 users.

MISC-4 Select-to-Lockout The Navy requires the option to configure radio keying for Select-To-Lockout (STLO). This feature provides a visual indication to controllers when a single-frequency approach (SFA) has been selected and locks out other operators from selecting that frequency. Other users are prevented from selecting and using the frequency until the first user is finished and deselects the transmitter. Pre-emption rights can be assigned to allow a supervisor, or other designated operator, to take control of the frequency with STLO.

MISC-5 Touch Entry Device Size System shall utilize touch screens that are no larger than A”x B” x C” in towers and no larger than X” x Y” x Z” in RAPCONs to accommodate existing infrastructure. Exact dimensions will be specified later.

Version: 0, 3 Aug 2023 Page 12 of 12

2.19. KEY PERFORMANCE PARAMETERS (KPP)

There are 3 Key Performance Parameters (KPPs) identified within the requirements above.

These are requirements IF-4, OP-5, and OP-6. These requirements are of the highest importance and are expected to be the basis for the new VCS system. All other requirements are Key System Attributes (KSAs) and shall be considered of equal ranking below the ranking of the KPPs.

2.20. OPEARTIONAL RELIABILITY AND MAINTAINABILITY

Table 2.20 Number Description Requirement ORM-1 Operational Availability > 99.8%

ORM-2 Mean Time Between Critical Failures (MTBCF) (hrs)

> 6,000

ORM-3 Mean Repair Time (MRT) (hrs) ≤ 0.5 ORM-4 Mean Time to Restore Service

(MTTRS) (hrs) ≤ 6.0

ORM-5 MaxRT (hrs) ≤1.5 MaxRT (hrs) ORM-6 Fault isolation/detection 100% ORM-7 Scheduled maintenance Once/Qtr, 2 hrs complete, < 0.5 hrs downtime