Chapter 8

AUTOMATED COMSEC MANAGEMENTAND ENGINEERING

SYSTEM (ACMES)
This chapter explains ACMES and amplifies RBECS issues and
development within ACMES: system description, components and
capabilities, and software management.

SYSTEM DESCRIPTION
8-1. The Automated COMSEC Management and Engineering System
(ACMES)- consists of a hardware and a software system designed to
provide the communications planner the capability to provide
decentralized and automated Communications-Electronics Operation
Instructions (CEOI)/Signal Operation Instructions (SOI) design,
development, generation, distribution and management. Additionally,
ACMES provides the development, generation, distribution and
management of Electronic Counter-Countermeasures (ECCM) (anti-
jamming protection measures) fill variables required by the frequency-
hopping Single-Channel Ground and Airborne Radio System (SINCGARS).
The software portion of ACMES, hosted on the Lightweight Computer Unit
(LCU), is called the Revised Battlefield Electronic Communications-
Electronics Operation Instructions (CEOI) System (RBECS).
8-2. The system can produce the ECCM fill variables to support SINCGARS
in data file and electronic formats. In addition, the system can produce SOI
outputs in either electronic or hard copy (paper) formats. The objective is
to fully utilize the electronic data storage devices (e.g., Automated Net
Control Device (ANCD)) to eliminate the need for hard copy paper SOI (see
Figure 8-1).

1
FM 11-53_____________________________________________________________________________________

Figure 8-1. Paper SOI.

8-3. The employment of the ACMES RBECS software is similar to that of its
predecessor Battlefield Electronic Communications-Electronics Operation
Instruction (CEOI) System (BECS); namely, is similar from Corps through
Brigade and separate Battalion levels. The original system, BECS, was
fielded to provide decentralized SOI and SINCGARS support initially. The
U.S. Army replaced BECS with RBECS, which is discussed in this Chapter.
Table 8-1 shows ACMES functions at various command levels, theater to
battalion.
• Signal Officers at both Corps (G-6) and Division (G-6) (and Separate
Brigade) levels use their LCUs with RBECS to design, develop,
generate and distribute SOIs and SINCGARS frequency-hopping

2
_____________________________________________________________________________________FM 11-53

(FH) data at their respective levels and for subordinate levels, as

appropriate.
• Brigade and separate Battalion units use their LCU with RBECS to
selectively distribute generated SOI and SINCGARS frequency-
hopping data for use at their respective levels and for subordinate
levels.
• Close coordination between Corps and Division Signal planning
staffs using their LCUs with RBECS is required for the design,
development and generation of SOI and SINCGARS frequency-
hopping variables. This will ensure that the communications
systems are as fully utilized as possible allowing for effective and
efficient mission accomplishment (e.g., SINCGARS fill variables
[hopsets] must be coordinated to ensure successful frequency-
hopping communications at all echelons within the Corps).
• The distribution of ANCDs is approximately one ANCD to every two
SINCGARS radios; one ANCD per SINCGARS-equipped aircraft; and
one ANCD per Special Operations Soldier. The number authorized
for a specific unit is dependent upon that unit's MTO&E or TDA.
Additionally, unit Signal officers determine exact distribution within
each unit based on the specific operational and reserve data
requirements of the unit. In general, Signal officers will have
whatever number of ANCDs needed for COMSEC key, FH data, and
SOI management in the field; NCSs will have at least one ANCD for
ready use; and most net operators will share the use of an ANCD
with designated net operators.
• Commanders responsibility for COMSEC is addressed by AR 380-40
(COMSEC Responsibilities of Commanders). The Controlling
Authority (CONAUTH) is the commander who establishes a
cryptographic net. Division and higher commanders have CONAUTH
responsibilities. Within divisions, brigades and battalions,
commanders may be assigned CONAUTH responsibilities depending
upon command policy and operational situations.

Table 8-1. ACMES Functions at Various Command Levels

Command Levels Media Function

Theater1 Disk Generates pairs of operational TRANSEC keys every 30 days

for ICOM &Non-ICOM SINCGARS radios. The J6 (CE)
generates the TRANSEC keys. Generates training TRANSEC
keys every 90 days.

Corps Disk Generates the CUCP (sign/countersign, smoke/pyrotechnic

signals, suffix/expander, hopsets and CEOI/SOI) at corps
level. Receives TRANSEC keys from theater

Division Disk/ANCD Performs division CEOI/SOI generation. Receives TRANSEC

keys, generated CEOI/SOI merged for corps, sign/countersign,
smoke/pyrotechnics, suffixes/expanders and hopsets from
corps.

Brigade ANCD/Disk Receives the generated CEOI/SOI and other data such as
3
FM 11-53_____________________________________________________________________________________

hopsets and TRANSEC keys from division.

Battalion ANCD/Disk/Paper Receives the CEOI/SOI information and other data such as
& ECCM Fill hopsets and TRANSEC keys from brigade
Device

Note 1: In some situations, theater may not be the highest level of command. In this case, the highest, the
highest level of command (i.e., Corps) will generate TRANSEC keys.

COMPONENTS AND CAPABILITIES

SYSTEM COMPONENTS
4. Hardware. The RBECS software is hosted on a computer system called
the Computer System, Digital (AN-GYQ-73) or Lightweight Computer Unit
(LCU). A dot-matrix type Printer is issued with the LCU (AN/GYK-33A).
National Security Agency (NSA)-produced equipment named the Random
Data Generator (RDG) (AN/CSZ-9) and the Automated Net Control Device
(ANCD) (AN/CYZ-10) are also used to allow full use of the RBECS
capabilities. Note: The ANCD is also referred to as a Data Transfer Device
(DTD). A short description of the system hardware components follows:
• The LCU (see Figure 8-2) is a computer system that may serve as a
host for many application software packages (programs) designed
to provide the user with the means to accomplish assigned
missions, (e.g., RBECS software to generate and distribute SOI and
SINCGARS Radio FH data).
• The LCU printer (see Figure 8-3) is a lightweight dot-matrix type
printer that may be easily transported. This printer can produce a
paper copy of a generated SOI if required.
• The RDG (see Figure 8-4) is used to provide the LCU with the
necessary random data to allow the RBECS software to generate
SOI and/or Transmission Security Key (TSK) fill data. Note: The RDG
is a Cryptographic Controlled Item (CCI). Note: RDGs are authorized
for use only at selected echelons (e.g., Corps, Division, Separate
Brigade) and thus are issued only to those specific echelon
organizational elements.
• The ANCD (see Figure 8-5) is a handheld Personal Computer (PC)-
compatible device. The ANCD is capable of receiving, storing, and
sending SOI data, frequency-hopping (FH) data and COMSEC keys.
8-5. RBECS Software. The RBECS software is unclassified (with the For-
Official-Use-Only protective marking) and consists of a set of 3.5-inch high-
density (1.44 megabyte size) disks. The installed RBECS software requires
approximately six megabytes of hard disk storage space on the host
computer. The using organization's data files require an additional amount
of storage disk space that varies with the size and data needs of the
organization. The RBECS software is designed to operate on any personal
computer (PC) that has Microsoft's Disk Operating System (DOS) Version
3.3 or later installed and being used as the host computer's operating
system. RBECS Version 2.2 along with RBECS Merge for Windows Version
1.0 is compatible with Windows 95/98 operating systems. The software
requires a minimum of 512 kilobytes (524,288 bytes) of available

4
_____________________________________________________________________________________FM 11-53

executable program size (memory space) to be able to properly function

on the host computer. In addition, a random access memory (RAM) drive
must be configured to allow RBECS to generate SOls and the Transmission
Security Keys (TSKS) required by the frequency-hopping SINCGARS radios.
After completion of the generation process and saving of the generated data,
the RAM drive is sanitized using the RBECS Zeroize option. This process is
necessary to meet NSA requirements. Note: The RBECS software provides
the generation of SOI in either U.S. Army, U.S. Marine Corps or Joint Forces
formats to meet their respective requirements. A RBECS training course is
available at Fort Gordon, Georgia. See
http://www.gordon.army.mil/roa/tngsch/JRBECS\JRBECS.HTM for additional
information.
8-6. RBECS Data Transfer Device Software (RDS) software. The RDS
software is unclassified and is pre-installed on ANCDs designated to
provide support with regard to SOIs and FH data for the frequency-hopping
SINCGARS radios.

CAPABILITIES

LCU Computer
8-7. The LCU computer, when operating the RBECS and RDS application
software, provides the user the capability to generate, store, print and/or
electronically transfer both single channel (SC) and frequency-hopping
(FH) information and the Transmission Security (TRANSEC) Key (TSK) for
Electronic Counter-Countermeasures (ECCM) protection. These capabilities
are designed to be more responsive to rapidly changing and highly mobile
conditions on the battlefield.

Note: The Random Data Generator (RDG) provides the required random data to the LCU Computer
operating the RBECS software to allow RBECS to generate SOI and TRANSEC Key data.

8-8. The LCU is a computer with a keyboard and a Liquid Crystal Display
(LCD). The 10-inch display normally shows 25 80-character lines of
alphanumeric information. The VGA display contains 640 x 480 pixels and
supports 16 levels of shading. The LCU may be used at a fixed
workstation, or may be carried to practically any location. A typical work
station setup might require space for peripheral devices, such as a printer,
printer paper, interface transfer cables, and/or interfaced devices (e.g.,
SINCGARS radios, Automated Net Control Devices, etc.).

5
FM 11-53_____________________________________________________________________________________

Figure 8.2. Lightweight Computer Unit

8-9. A specific set up procedure is not required to operate the LCU. If the
LCU power source provides power within acceptable parameters, the
computer is ready to operate as a stand-alone computer. If the power
source cannot provide power within acceptable parameters (e.g., battery
pack charge is below minimum operational levels), an alternative good
power source must be connected for continued operation of the LCU. A
solution is to replace, with fresh/recharged, batteries in battery pack or
turn off the LCU and recharge existing batteries. The LCU Computer when
operating the RBECS software may interface with and output to one of
three types of printers. The RBECS software configuration may be set to
support either of these printers, Epson-compatible printers and the
Hewlett Packard LaserJet-compatible printers.

LCU Printer
8-10. The LCU printer is a small lightweight dot-matrix printer that has a
print rate of 160 characters per second (CPS) in the "draft" printing mode
and 80 CPS in the "Near-Letter-Quality" printing mode. The printer is
powered by either battery or the LCU power supply. The printer uses a
ribbon to print several hundred pages of legible print. The ribbon is
disposable and is easily replaced. The printer's normal line width is 80
characters. The printer will accept paper widths from 3 to 8.5 inches and
comes with a tractor feed attachment that accepts 8.5 x 11 inch

continuous form, fan fold paper.

Figure 8-3. Lightweight Computer Unit Printer

8-11. The printer uses the provided cables to connect to the LCU's
Centronics parallel interface port. The printer is capable of printing in two
modes, text mode and graphics mode. In the text mode, the printer
interprets each data byte it receives from the computer as an American
Standard Code for Information Exchange (ASCII) character. It then refers to
its character table and prints the dot pattern it finds. In the graphics mode,
6
_____________________________________________________________________________________FM 11-53

however, the data received from the computer directly specifies the dot
pattern that is to be printed. In lieu of the LCU printer, Epson or Hewlett
Packard compatible printers may be used for output.

Random Data Generator

8-12. The RDG (AN/CSZ-9) generates and transfers random data to an LCU
Computer operating the RBECS software. The RDG is a self-contained unit
powered by 5 D-Size 1.5 Volt batteries located beneath the bottom
shelf/foot plate of the unit. Serviceable batteries should be installed prior
to use of the unit.

Figure 8.4. Random Data Generator

8-13. The unit is activated by the On/Off switch on the front panel;
however, the unit does have a "sleep" mode that inactivates the unit when
not in use for an extended period in order to conserve energy drain from
the unit's battery power supply. The unit is provided with a cable that
connects the unit (from its rear panel) to a serial port on the computer
(e.g., LCU).
8-14. The unit also has a low battery light on the front panel to indicate
that the batteries powering the unit are reaching unacceptable power
levels and should be replaced. In addition there are a ready light and an
alarm light on the front panel to indicate the operational status of the unit.
The ready light is illuminated when the unit is powered up and is
operational. The alarm light is illuminated when the unit is powered up and
is not operational. Note: Only one of the ready and alarm lights is
illuminated when the unit is powered up.
8-15. The RDG is a Controlled Cryptographic Item of equipment that when
connected to a computer (e.g., LCU) provides the necessary random data
to the RBECS software in order to generate CEOI/SOI and/or TRANSEC key
fill data to support the frequency-hopping SINCGARS radios.

Automated Net Control Device

16. The ANCD (AN/CYZ-10) is an electronic storage device that is
compatible with personal computers. The ANCD replaces the MX-
10579 and MX-1 8290 ECCM fill devices as well as the common fill
devices (KYK-13, KYX-15, and some functions of the KOI-18).
Because it is programmable, it can provide multiple capabilities.

7
FM 11-53_____________________________________________________________________________________

Figure 8-5. Automated Net Control Device

8-17. The RDS is one example of applications software for the ANCD that
provides the means to electronically support the user's needs with regard
to SINCGARS radios (see Chapter 3 of this document) and RBECS-
generated SOI. The ANCD will electronically load both ground and airborne
frequency-hopping SINCGARS radios, HAVE QUICK (Radio Transmitter (RT)
1319) radios and store and transfer keying material for the KY-68 device.
The ANCD has the capability to load the Position Lightweight Global
Positioning System (GPS) Receiver (PLGR) (AN/PSN11) with COMSEC keys.
Additionally, it can perform all functions previously available on the KYX-1
5/TSEC and the KYK-1 3/TSEC.2

RBECS Software
8-18. RBECS is designed to decentralize and automate CEOI/SOI
generation. Generating and distributing RBECS CEOI/SOI can be done with
virtually no dependence on NSA. The RBECS is capable of building a
division size CEOI/SOI in 2-5 hours. NSA normally requires 60-90 days and
a manual build normally requires 3-5 days to produce the same CEOI/SOI.
RBECS can respond quickly to a compromise of CEOI/SOI in the field or to
rapidly changing force structures. RBECS can regenerate frequencies and
call signs in 3-5 hours (depending on database size).

CEOI/SOI Development
8-19. Although RBECS automates the generation process, the signal officer
must design the CEOI/SOI on paper first. These basic steps for designing
and developing RBECS CEOI/SOI data are as follows:

• Research and extract data from the MTOE, which authorizes the
use of personnel and equipment.
• Determine the doctrine to be followed.
• Determine what the commander desires.
• Observe and identify the situation.
8
_____________________________________________________________________________________FM 11-53

• Develop a restriction explanation worksheet.

• Determine how many nets and frequencies are required. Use the
current CEOI/SOI as a starting point.
• Develop the Master Net List (MNL).
• Obtain radio frequency authorizations (RFA).
• Develop the separation groups worksheet.
• Design CEOI/SOI net groups.
• Determine suffix and expander lists.
• Determine the share plan for frequencies.
• Determine the share plan for call signs and call words.
8-20. RBECS can be used for frequency and call sign generation in all
frequency bands currently used by the military. Table 8-2 shows the
frequency bands. All frequency assignments are based on the authorized
frequencies of the using organization. The available frequencies are listed
in the current RFA. The initial step in preparing the net/frequency
assignment plan is to identify the unit nets required for command and
control of tactical operations. After all nets are identified, compare the
resulting frequency requirements against the number of frequencies
available. Spare frequencies are available for assignment in most CEOI/SOI
with their use being controlled by major organization’s (controlling
authority) signal officer. If your frequency allocations and assignments are
inadequate, the additional frequencies must be requested through higher
command or area frequency coordinator, or some nets will be required to
share frequencies with other nets. Refer to FM 24-2 for procedures
governing the requisition of frequencies.

Table 8-2. Frequency Bands

Frequency Band Frequency in MHz

Low frequency (LF) .0001 – 1.9999
High Frequency 2.0000 – 29.9999
VHF-FM 30.000 – 87.975
VHF-AM 108.000 – 151.975
UHF 225.000 – 399.975
Extra/Super High Frequency 400.000 – 9999.975

8-21. Fixed frequencies are frequencies that are usually assigned to non-
tactical units. The frequency value is manually assigned and is unique to
the specific net. The frequency value is non-changing for all time periods
of the generation. For example, the MEDEVAC net may be assigned 34.000
MHz and this frequency will never change. Also, 34.000 MHz will not be
assigned to another net. Fixed frequencies do not have any restrictions
assigned and are used on single-channel nets only.
8-22. Restricted frequencies are frequencies that can not be used by
certain nets for various reasons, i.e., power, area restricted. The frequency
9
FM 11-53_____________________________________________________________________________________

value is assigned a letter restriction and if a net has the same restriction
letter assigned to it, then the net will never be assigned the frequency
value for any time period. Restricted frequencies can be either discrete or
common user frequencies.
8-23. RBECS software is designed to recognize up to 16 separate
frequency restrictions (identified by a letter code) per frequency band. As
each restriction is identified, assign it an appropriate entry on the
restriction explanation work sheet. Multiple frequencies (up to the
maximum allowable within any frequency band) can be assigned to a
single frequency restriction letter. The RBECS software is designed to
recognize all 16 of the separate net restrictions (identified by a letter
code) per net. As each restriction is identified, assign it an appropriate
letter code (A-P) and add the code and restriction description to the
restriction explanation work sheet.
8-24. These same frequency restrictions will be used at a later time with
specific radio nets on the master list. When assigning frequencies, nets
and frequencies with the same restriction letter code cannot be matched
together. A reverse logic is used when assigning restrictions. For example,
the letter “A” may be assigned to frequencies that will not be used to
communicate with aircraft (net restriction). Therefore “A” restricted
frequencies will not be assigned nets that have been assigned the “A”
restriction. When an RBECS spectrum manager receive the RFA, he is
required to read and interpret it, extract both external and internal
frequency restrictions, complete a restriction explanation sheet, and
compare frequency restrictions against nets when completing the master
net list.
8-25. Ideally, frequencies are randomly assigned to nets designed to
receive a changing frequency with each change in time period. However,
because of special cases (i.e., MEDVAC) and the lack of available
frequencies and abundance of needed nets some nets must share
frequencies or reuse frequencies. Also, some nets require frequency
separation from other nets to prevent interference.
8-26. The various types of frequency assignments should be considered
when developing the database to generate a CEOI/SOI:

• A net may be sufficiently important to warrant a dedicated (sole

user) frequency for its use. The frequency is unique to the
organization and is only used by one net during any time period.
Unlike a fixed frequency, the sole user frequency assigned to the
net changes with each time period. This assignment is reserved for
command and control nets.
• When the number of nets requiring frequencies is greater than the
number of available frequencies, frequency reuse is (common user)
becomes a necessary option. Reuse frequencies are frequencies
that are reused (shared on a noninterference basis) by more than
one net. Nets are selected for inclusion in a reuse plan on the basis
of low operating power, geographic separation, terrain masking,
and other factors permitting the use of the same frequencies on a
noninterference basis.

10
_____________________________________________________________________________________FM 11-53

• Another method of reducing the number of frequencies required is

to share frequencies. A shared frequency is a frequency used by
two or more nets. The sharing nets will receive the same frequency
for a given time period. The can be fixed or discrete. Typical nets
that use shared frequencies are survey nets and weather nets.
8-27. A reuse plan allows nets to reuse (share) frequencies with other nets.
Nets that operate low power radios with short-range communications
requirements and the nucleus of a frequency reuse plan. Nets with long
geographic separation or terrain masking are also considered for
frequency reuse. Suppose that there are three regions (zones) that are
geographically separated form each other and each region contains three
nets. If nets in a zone cannot interfere with nets in another zone, then only
three frequencies are require to satisfy the nine nets. A net in the three
zones can use the same frequency for one time period without causing
problems. In the SOI generation process, the three nets in each zone are
randomly assigned the same three frequencies.
8-28. The following is a list of rules that apply to the design of a reuse plan:

• Neither a retransmission nor the corresponding net can be placed

in a reuse plan.
• All nets within the same class must have the same restrictions.
• The class with the largest number of restrictions should be class 1.
• Frequencies are selected based on the restrictions(s) assigned to
the nets. If nets have no restrictions, frequencies may be restricted
but still assigned. Assigned frequencies cannot include
restriction(s) that included in the net’s restriction(s).
• The zone with the most nets determines the number of frequencies
required to support the entire class:
 Single-channel nets require one frequency per net; therefore, if
the net maximum number is 20 in a zone, then 20 frequencies
are required for the entire class.
 Frequency-hopping nets require two frequencies per net
(manual and cue); therefore, if the net maximum number is 20
in a zone, then 40 frequencies are required for the class and for
frequency hopping.
• All zones within a class will reuse the same frequencies.
• The reuse plan for most army divisions will contain one class with
three to five zones.
• Elements that provide direct support (DS) (i.e., field artillery and
engineers) must be placed in the same zone as the supported
brigade. (No two nets within the same zone are permitted to
receive identical frequencies.)
• Elements that provide (GS) (i.e., chemical, cavalry, MI/CEWI and
signal) should be placed in their own separate zone.
• When selecting nets for reuse, always start at the lowest possible
echelon and work your way up.
8-29. If a net must operate solely in the single-channel mode, the
frequency assigned is the cue frequency. If the net will operate solely in
11
FM 11-53_____________________________________________________________________________________

the frequency-hopping mode, the net is assigned a manual frequency in

addition to the cue frequency. The cue frequency and manual frequencies
required for a frequency-hopping net can also be reused. However, if a
frequency is assigned as a cue frequency it is not available for reuse as a
manual frequency. Because two frequencies are required for a frequency-
hopping net, the number of frequencies used in a SINCGARS reuse plan is
doubled. There is a maximum of 2320 frequencies in the FM band.

8-30. The net Master List is used to enter: net name/description, net ID,
organizational code, restrictions, frequency type, power, reuse class, reuse
zone, and call word/color word requirements. A description of each master
Net List entry is shown in Table 8-3.

Table 8-3. Master Net List Description

Net Number Net Number (NET NUM) is the first column of the matrix. The number increases
in sequential order as you proceed down the list. This number is used as the
reference number for each of the nets when entering Net Groups, Separation
groups, Call Sign Sharing Plan, Call word Sharing Plan, and Frequency Sharing
Plan. Up to 9999 nets may be entered in the list. These nets may be entered in
command echelon (corps, division, brigade, etc.).
Net Name/Description The Net Name/Description column is used to enter the description for the nets to
be included into the completed SOI. The description of the type of net, i.e., 1st
BDE CMD. Up to 9999 net names, each up to 16 character long may be entered
into a RBECS database. The following characters may be used as part of the net
name: letters a-z, digits, 0-9, &, (,), - and/. You should leave blank lines to allow
insertion of additional units if required. Also adding spares to the list should be
considered.
Net ID The Net ID is used to enter the three-digit number (000-999) to be used as a Net
ID with SINCGARS radios (in frequency-hopping mode). The Net ID number is
used in the SINCGARS radio as an identifier. It designates the frequency within
the hopset on which to start hopping. You should allow for spare ID. A
suggestion for reserving Net ID follows:
• 000-099 reserved for Theater/Joint level
• 100-299 reserved for Corps/Service
component Level
• 300-999 reserved for division and
lower/Service component Headquarters level
Call Sign1 In the Call Sign column enter whether or not the net is to receive a call sign
(enter ‘yes’ or ‘no’). A call sign is a three-character combination of letter-number-
letter used to identify a command, activity unit or element is establishing and
maintaining communications. All units and nets are to receive call signs with the
exception of certain administrative nets, i.e., Range Control or MEDEVAC.
Organization Code The Organization Code (OC) column is used to provide identification to groups of
nets within the organization or to echelons of other organizations. The OC will
permit the reuse of Net ID between organization code at least two numbers
apart. The use of an OC provides the means to identify net groupings within a
database to assists in database manipulation, such as the merging of data
between databases. There may be a maximum of nine (1-9) organization codes
used within an RBECS database.
Restrictions The Restrictions column is used to enter the restriction codes that have been
12
_____________________________________________________________________________________FM 11-53

placed on the net. Up to 16 restrictions may be applied to a given net. These

restrictions are entered using the letters in the range A-P. Each letter identifies
the explanation of how the net is to be restricted. For example, ‘A’ may indicate a
net must be able to communicate with aircraft, thus requiring frequency
assignments that allow that to occur. The use restriction codes can influence the
frequency assignment process.
Frequency Band The frequency (FREQ) column is used to enter the frequency band to be used by
the net. Specify the band using L (LF), H (HF), F (FM), A (AM), U (UHF) or E
(SHF/Extra) for radio frequency spectrum. An entry of N (no frequency) is
permissible. If a fixed frequency is required for the net, enter the value in MHz.
The fixed frequency value must be also entered into the correct band when n the
frequency input section.
Power Level The Power Level (PW) column is used in the frequency assignment process to
ensure a frequency matching the designated power level code or a higher one
assigned to each net.
• 1 for Very High power level authorized for use
• 2 for High power level authorized for use
• 3 for medium power level authorized for use
• 4 for Low power level authorized for use
Reuse Class In the Reuse Class (REUSE CL) column enter the number the net may be
assigned to as part of a reuse plan. A class is a grouping of up to 30 zones. The
total frequency requirement for a class equals the number of nets in the largest
zone. The class may be a number 1-20. All nets within a class must have the
same power requirement and restrictions. You must enter a zone if a class is
entered.
Reuse Zone In the Reuse Zone (REUSE ZN) column enter the zone number the net may be
assigned to as part of a reuse plan. A zone is a group of nets in which an
assigned frequency cannot be repeated within that group for the same time
period. Each zone can contain 200 nets. The zone may be a number 1-30.
Call Words In the Call Word (CW) column [enter 15 for a 15-letter dictionary CW, 5 for a 5-
letter dictionary CW, U for user-defined dictionary CW, a N for no CW], type in a
fixed CW (assigned for all time periods) for each net, or a C for a color word
dictionary color word.
Note 1: The call sign column may also be used to identify participating unit (PU) satellite nets by placing a
‘P’ in the column. Then a satellite PU number may be generated for those designated nets. No other
columns (besides Net Name/Description and Call Sign (‘P’)) should be used for these type nets.

8-31. A separation plan provides a frequency separation between nets. A

separation plan is used when operating more than one net within a
communications van or close proximity to other nets or when mutual
frequency interference may result between radios. A separation plan is
designed to allow these nets to communicate simultaneously without
mutual interference. Frequency assignment separation requirements
include cosite, retransmission, and other nets such as alternates.
8-32. A Separation plan provides separation for up to 999 separation
groups. Each group can contain up to 12 nets (1 base and 11 others). One
desired and one required frequency value of separation are selected for all
nets in the group. See TM-11-7021-263-13&P for the specifics on making a
separation plan. The following item should be considered before
constructing a separation plan:

13
FM 11-53_____________________________________________________________________________________

• Determine whether enough frequencies are available for using a

separation plan.
• Determine required and desired frequency separation.
• Determine whether the nets being considered for the separation
plan are also in a reuse plan
• Determine whether the separation problem can be resolved by
other means such as terrain, masking, antenna remoting, or low
power use.
8-33. If FM transmitters operating on different frequencies are situated in
the same locale, it is not unusual for mutual interference problems to
result. To effectively reduce these interference problems, the software
adheres to the following basic standards
• Frequencies are not assigned with an exact separation factor of
5.750 or 23.000 MHz to collocated nets.
• Frequencies are not assigned that are on the order of the second
harmonic. For example, the frequency setting of 30.000, 32.650,
and 35.000 MHz will possibly interfere with radios using 60.000,
65.300, and 70.000 MHz respectively.
8-34. A net group worksheet is used to organize into operation groups the
nets in the master net file. Net groups are typically designed for the
command and staff echelon and battalions or comparable elements. The
net group worksheet also forms the basis for the generation of SI extract
pages by RBECS. On the worksheet, REBECS software will use the Net
Group Number to identify each net group rather than spelling out the Net
Group Name each time. The Net Group Name is limited to 20 characters
describing the net. The Net Type refers to the formatting of CEOI/SOI [i.e.,
1= Standard (Army) format, 2= USMC format (units/call signs), 3= USMC
format (nets/freqs), 4= Joint format, 5= Air Kneepad]. The item number is
used to identify Net Groups within the final CEOI/SOI
8-35. Up to 999 net groups can be created. The nets are entered into a net
group by using the Net Number (NET NUM). These NET NUMs are entered
into a table. A maximum of 52 nets may be entered into a net group (104
nets for air kneepad net group type) that becomes the CEOI/SOI extract
after frequencies and call signs are assigned to the nets. The last position
in the net group is normally used for admissions nets such as Range
Control, MEDEVAC, STOP BUZZER, etc. During the generation of call signs,
RBECS attempts last-letter uniqueness unless the net is in a call sign share
group or was previously assigned a call sign in a previous net group. Last-
letter unique call signs only apply to the first 26 nets requiring last-letter
unique call signs. Each net, requiring last letter uniqueness, must be
identified with a “Y” when entering this net into a net group. When
entering net groups into RBECS, an All Nets Assigned” option is available.
This option creates a printed list of nets that have not been assigned to
any net group.
8-36. A suffix is a two-digit number used in conjunction with a call sign to
indicate a specific position, mission, or function of a net. An expander is a
single letter used with a call sign/suffix to identify a sub-element of the
position, mission, or function identified by the suffix. The suffix and
expander lists are not fixed lists common to all organizations, but vary
14
_____________________________________________________________________________________FM 11-53

according to specific requirements of the organization. However, the same

suffix and expander are at all echelons of he using organization, i.e.,
division, by individuals/stations having like positions, functions, or titles.
RBECS randomly assigns suffixes and expanders simultaneously for each
time period.
8-37. Expanders may have more than one meaning and are normally listed
in alphabetical order or the most commonly used are listed first followed
by the remainder in alphabetical order. It is recommended that you plan
for spares when creating this list. And expander list can contain a
maximum of 26 (A-Z) expander descriptions. A blank expander list table is
located in TM 11-7021-263-13&P. To create the expander list:
• Identify all expander requirements
• Develop up to 20-character alpha/numeric description for each
requirement.
8-38. RBECS allows the user to assign multiple net numbers into a
frequency share group. All nets within the same frequency share group are
assigned the same frequency for each time period. Up to 999 frequency
share groups may be created as part of a frequency sharing plan. Use the
NET NUM for the Master Net List to enter the net. There is a limit of 9999
nets (all nets in the Master Net List) in a single group.
8-39. All nets within the same call sign or call word share group are
assigned the same call sign or call word for each time period. Use the NET
NUM to enter a net into the group. Up to 999 sharing groups may be
entered into a call sign or call word sharing plan. There is no limit to the
number of nets within a group. A separate share group must be created
for call signs and for call words. Normally, if nets share cal signs they
would also share call words.
8-40. The Signal section is responsible for identifying requirements for the
construction of loadsets to support SINCGARS radios that are employed by
their organization. These loadsets, once defined, are then constructed
using the RBECS software, are saved to file, and distributed to subordinate
organizational units or elements for follow-on distribution to and use by
respective SINCGARS radio users. The construction of SINCGARS loadsets
is defined by the SINCGARS radio user and is primarily based upon the
identification of the SINCGARS nets that the radio user is required to
enter/monitor.
8-41. For example, the Commander of an Infantry Battalion would normally
be a member of several frequency-hopping SINCGARS nets. In one of the
Commander's SINCGARS radios there could be the requirement to have
the Brigade Command Net, Brigade Operations Net, Battalion Command
Net, Battalion Operations Net, and the Brigade Retrans Net loaded. Radio
operators will normally load all six preset channels on the SINCGARS radio
with operational Net lDs and TEKS. If a requirement to perform an OTAR
arises, then all stations involved with the OTAR must load a KEK (stored in
the ANCD) into preset channel 6 on the SINCGARS radio with an
appropriate Net ID. The loadset for this particular Commander's SINCGARS
radio would be constructed like the sample shown in Table 8-4.

Table 8-4. Sample Loadset

15
FM 11-53_____________________________________________________________________________________

SINCGARS Hopset Net Name Net TRANSEC TRANSEC TEK/KEK

Radio Generation Identifier Key Name Key Name
Channel Level Number
1 1 1-27 IN BN 410 1 TSK-52.A TEK-52.A
CMD
2 1 FIRE 511 1 TSK-52.A TEK-52.A
Support
3 1 2-27 IN BN 442 1 TSK-52.A TEK-52.A
CMD
4 1 2nd BDE 401 1 TSK-52.A TEK-52.A
CMD
5 1 1-45 AVN 933 1 TSK-52.A TEK-52.A
CMD
6a 1 1-27 IN BN 406 1 TSK-52.A TEK-52.A
OPS/INT
Note: A key encryption key (KEK) must be loaded into the channel six of the SINCGARS radio for
over-the-air-rekeying operations.
8-42. Loadset Updates. The responsible Signal section personnel using the
RBECS and RDS Software as appropriate maintain loadset data. Loadset
data is updated with new replacement key data when appropriate (before
the current key(s) expire), are saved to file and are distributed to users
(e.g., via ANCD) so that they are in place and available for loading into the
SINCGARS radios at the appropriate key-changeover time. In addition, the
Signal sections should have several sets of Loadsets with associated keys
already constructed and distributed (or available for expeditious
distribution) and immediate use when necessary (e.g., a compromise of
key data).
8-43. Loadset Revisions/Creation. Existing Loadsets may require revision
when the required net content changes (e.g., unit reassignment or
attachment). In addition, new Loadsets may have to be constructed
(created) to meet new requirements (e.g., a new task force organization is
created).
8-44. The reference document for the RBECS/RDS system is Technical
Manual TM 11-7010-263-13&P titled Computer System, Digital (AN/GYQ73)
(Automated COMSEC Management and Engineering System (ACMES) -
Phase 1) Operator's, Unit, and Direct Support Maintenance Manual
(including Repair Parts and Special Tools List). The TM consists of three (3)
volumes. Note: This TM includes the RBECS and RDS Software Operating
Procedures.

SOFTWARE MANAGEMENT
8-45. The RBECS software is managed by the Office of the Program
Manager (OPM), Joint Tactical Area Communications System (JTACS),
(SFAE-CM-JTC-CMS), Fort Monmouth, New Jersey 07703-5506. Requests for
distribution and any recommended changes to the RBECS software should
be directed to that organization. An RBECS Software Configuration Control
Board meets periodically to consider changes to the fielded version of the
software. Upon approval by the Board, the changes to the software are
made and OPM-JTACS distributes the updated/revised version of the
RBECS software and installation instructions to authorized users.

16
_____________________________________________________________________________________FM 11-53

8-46. The RDS software is also managed by the Office of the Program
Manager (OPM), Joint Tactical Area Communications System (JTACS),
(SFAE-CM-JTC-CMS), Fort Monmouth, New Jersey 07703-5506. Requests for
distribution and any recommended changes to the RDS software should be
directed to that organization. An RDS Software Configuration Control
Board meets periodically to consider changes to the fielded version of the
software. Upon approval by the Board, the changes to the software are
made and OPM-JTACS coordinates the installation of the updated/revised
version of the RDS software into the ANCDs of the authorized users.

17