Military

MANAGEMENT CONTROL

5-1. The NPT, SCC-2, NCS, LENS, and their NMFs operate from a standardized network database. The critical part of long-range planning is initially generating the network database. The corps or the division G6, if establishing a stand-alone division network, sets up network management and control parameters for this process.

5-2. The signal brigade headquarters conducts management and control in an MSE corps network. The division signal battalion headquarters conducts management and control in a stand-alone division MSE network. Within these headquarters, the SYSCON conducts MSE network planning and operation. SYSCON maintains TECHCON of the network and is responsible for-

• Planning, engineering, controlling, and maintaining the network.
• Assigning and reassigning variable network operating parameters.
• Distributing all operating parameters network wide.
• Establishing relationships among network components.

DATABASE DEVELOPMENT

5-3. For signal planners, the supported unit's mission and planning guidance determine the content of the database. Signal planners may prepare one master database from which all missions evolve or prepare individual mission databases to support specific contingencies. The number of databases depends on the differences in force structure, missions, and geographical AO.

5-4. In operation plans (OPLANs), the force commander and staff define each mission, contingency, and exercise. The force signal staff prepares the databases and obtains the following information:

• Active and reserve component forces that require support.
• Radios to be used.
• Available MSE assets and unit information.
• Desired link reliabilities.
• Environmental parameters.
• Desired network-planning factors.
• Subscriber terminals to include-
• Level of authorized precedence.
• Type of authorized subscriber terminal and designation of tactical unit where each terminal will deploy.
• Type of service required by each user/office (for example, progressive conference and commercial network access).
• Preprogrammed conference participants.
• Compressed dial participants.
• Expected joint and allied interface requirements, including units and specific mission requirements.
• Expected geographical AOs.
• Authorized and restricted frequencies by range and type.
• Known competing, civilian emitters that could be in the AO, including grid locations, operating frequencies, and transmit power.
• Potential EW emitters.

5-5. This information is then used to respond to one or more of the following areas.

• Digitized maps.
• High point data.
• PALs.
• Profile lists (including compressed dial lists).
• Preprogrammed conference lists (PCLs).
• Team files.
• MSE frequency management.

5-6. The MSE database includes the global database (GDB), and it-

• Supports a seamless network architecture.
• Provides joint and service interoperability at EAC and ECB.
• Provides an effective communications network for any force projection scenario.

5-7. The GDB identifies joint (Commander-in-Chief (CINC)) level, US Army, US Air Force, US Navy, and US Marine organizations. The GDB manager (GDB MGR) is located with the US Army Signal Center. The GDB includes-

• Nonduplicated PAL sublist numbers.
• Nonduplicated team label identification for switch and control systems.
• Nonduplicated phone numbers.
• Global Standard Profile Matrix (GSPM) 255.

5-8. The NPT can develop the MSE network database, plan and engineer the network, and distribute team information to all appropriate switches. The SCC-2 acts as network status controller, and the NMC within the SCC-2 manages the operation of the TPN after it is initialized and loaded with the database.

DIGITIZED MAP REQUIREMENTS

5-9. The MSE NPT uses two types of map data for its software applications. Both are originally sourced from the National Imagery and Mapping Agency (NIMA) and are available on compact disk-read only memory (CD-ROM).

5-10. The ARC-Digitized Raster Graphics (ADRG) is a digitized picture of paper maps that clearly shows the terrain features (for example, rivers, roads, lakes, hills). They are available in five forms.

• Joint Operations Graphics-Air (JOG-A), 1:250,000.
• Joint Operations Graphics-Ground (JOG-G), 1:250,000.
• Topographic Line Maps (TLM), 1:50,000.
• Tactical Pilotage Charts (TPC), 1:50,000.
• Operational Navigation Charts (ONC), 1: 1,000,000.

5-11. The digitized terrain elevation data (DTED), Level 1, provides the terrain data applied to the digitized map for use in site location and radio system profiling.

HIGH POINT DATA REQUIREMENTS

5-12. High points are developed using the high elevation retrieval option within the network planning-frequency assignment application of the NPT. A user-selected rectangular area, defined by coordinates of its southwest and northeast corners, can be established using appropriate map data. This rectangular area map plot can be divided into five rows of five columns (equaling 25 cells) with up to five high points per cell, so that selected high points may be chosen throughout the original map plot. When selecting high points, a minimum separation value is applied to prevent all high points from being on the same high piece of terrain (for example, single hilltop). With this capability, the NPT can make a map reconnaissance of potential site locations before making the physical reconnaissance.

5-13. Two other NPT software applications support high point refinement. The interactive asset placement (IAP) application searches for high elevation placement for particular radio links at a site that still profiles. The automatic asset placement (AAP) application checks for the centroid of mass of switches that an NC supports and identifies the highest ground within a 1-kilometer area of a selected site.

5-14. Signal planners must consider all METT-T factors when selecting potential high points. The final high point selection is coordinated with senior headquarters SYSCON and the G3. Other weapons and communication systems can have high points as key terrain.

PREAFFILIATION LIST REQUIREMENTS

5-15. The MSE database includes telephone numbers for fielded units contained on the switch PAL. This database contains a unique telephone number for each subscriber position. The database is updated annually according to actual subscriber requirements that allocate a specific type of terminal to each operational subscriber.

5-16. The PAL sublists identify subscribers' numbers and the associated profile service characteristics likely to be affiliated with the network. The signal organization planner, through the US Army Signal Center GDB MGR, manages the development of the PAL. A PAL database can have up to 1,000 PAL sublists (database designators DB000-DB999). Each PAL sublist can contain a maximum of 200 subscribers. Each sublist is developed according to the standard requirements code (SRC) assigned to each unit or entity within a PAL database. The sublist may include command structure or community of interest, such as division main (DMAIN), division tactical command post (DTAC), or division rear (DREAR). PAL sublists are a part of the global PAL (GLPAL) baseline that includes all joint and US military services.

5-17. The doctrinal guidelines for developing a PAL database are shown below.

5-18. Assign unit or telephone prefixes (first part of the phone number) according to the Global Block Numbering Plan (GBNP) approved in June 1995, and subsequently changed or defined by the GDB MGR.

5-19. Assign telephone numbers by using the prefix from the unitlist.dbf and associating a suffix from the suffix.dbf based on the SRC or subscriber template. The subscriber database is created from association and reviewed by the network manager or PAL manager of the specific PAL database. Units should use the subscriber database to develop telephone directories to meet their requirements.

5-20. Ensure a subscriber's telephone number is unique with a profile assigned and placed only on one sublist.

5-21. Develop PAL sublists along task organized lines, depending on requirements. A subscriber's DNVT and MSRT number may appear on different PAL sublists. This depends on the way the network deploys and supports the units.

5-22. Group GLPAL sublists for corps into DB000-DB999 signal technical numbers as shown in Table 5-1.

5-23. Group GLPAL sublists for all other databases into DB000-DB099 signal technical numbers as shown in Table 5-2.

5-25. Do not include data terminal adapter (DTA) numbers in switches on PAL sublists or subscriber databases. The network uses these numbers to communicate between switches. They follow the format of DB99907 (999 is number 000-099 and 07 is standard for all flood search switches).

5-26. Group all signal battalion MSRT numbers on one PAL. This allows the signal numbers needed for network control to activate in the first operational NCS and ensures that signal managers have immediate access to the evolving network. Other MSRT subscribers may use a similar rule, so they may have phone service as soon as they enter the area.

5-27. The NPT can accept a PAL load disk with its PBOOKII software application. Do not use PBOOKII software when modifying and updating a PAL. The PBOOKII software application provides an electronic phone book to support tactical switching. It also supports the 63 and 255 profile matrix standards with version 2.01 and the GDB with version 2.02.

PROFILE LIST REQUIREMENTS

5-28. Profiles provide particular phone service and system features to wire and mobile subscribers. The subscriber's profile defines the level of authorized service to each MSE subscriber. A method of developing profiles is to classify the subscribers by type and/or position. Each subscriber is assigned a permanent profile. This profile can be changed temporarily at the switch; however, this is the exception not the rule. Signal planners must consider area TMD communications support requirements, whereas TMD assets require dial-hold (channel reassignment function) circuits through the MSE network.

5-29. The US Army uses the GSPM 255 0895 matrix, which replaces the earlier Army Standard Profile Matrix 0191. The GSPM 255 0895 matrix-

• Increases profiles from 63 to 255.
• Provides additional profiles to meet evolving subscriber service requirements.
• Includes profiles for joint communications networks.
• Provides direct conversion from the 63 to the 255 matrix.
• Addresses the COMSEC rekey rule "250" limitation.
• Provides 19 subscriber features.

5-30. Six basic groups within the matrix are

• 0 - Wireline subscribers (terminal type-3) DSVT.
• 1 - Mobile subscribers (terminal type-3) MSRT.
• 2 - DNVT subscribers (terminal type-13) DNVT.
• 3 - DTA (terminal type-15).
• 4 - GLU (terminal type-16).
• 5 - Analog/secure terminal unit (STU) (terminal type-248).

5-31. There are 50 subgroups which are categorized by profile and precedence order. The COMSEC rekey rule states that a maximum of 250 mobile subscribers should be assigned on a single rekey ID within a network. All wireline subscribers are assigned to one rekey ID-01. Fourteen mobile groups with unique rekey IDs will assist in preserving the COMSEC limit of 250.

5-32. The GSPM contains the old profile numbers cross-referenced to the GSPM profile. The US Army Signal Center initially converts all databases to the GSPM profiles. Each signal organization network manager may review each subscriber to determine if the new profile meets the subscriber's requirements. Each group for DSVTs converts to 03, 04, and 06, which translates to 009, 010, and 015, respectively. MSRTs may convert directly to MSRT groups 1-7 from old groups 1-7, or MSRT groups 1-7 for division slots and MSRT groups 8-14 for corps troops. EAC and other databases may only use MSRT groups 1-7.

5-33. Figure 5-1 shows the GSPM. The network manager must complete the profile matrix to initiate the MSE network.

5-36. The different subscriber terminal types within MSE can include-

• Terminal type 3 (DSVT) - identifies the KY-68 or KY-90.
• Terminal type 13 (DNVT) - a TA-1035/U or a TA-1042 with a data port to provide for data input.

Note: DNVTs or MSRTs must connect to a switch and have an individual directory number.

• Terminal type 15 (DTA) - allows data to flow to and from the SCC-2.
• Terminal type 248 - an analog circuit.
• Terminal type 16 (GLU) - enables it to receive and distribute frequency plans and manage the eight radios in the RAU.
• Terminal type 84 (SCC-2 network interface device) - provides the four transmit and four receive lines to the network.

5-37. TLC reduces network traffic during busy periods by efficiently using available switching and transmission resources. TLC restricts trunk access and local calling to class marked subscribers. Subscribers should be class marked for one of the five TLC levels shown in Table 5-38. The switch's TLC restrictions rule how the subscriber's TLC class mark is used in the MSE system. Table 5-6 explains how the switch uses class marks.

Note: A local- or long-loop subscriber or private branch exchange (PBX) trunk attempting a trunk call is returned a line-busy tone. The call is not completed. Time-out actions on sending a line-busy tone is IAW the specific requirements of the particular loop or trunk. (See individual signaling and supervision appendices for details.) A digital in-band trunk signaling (DIBTS) trunk attempting a call is returned a call incomplete (all trunks busy from tandem switch).

5-38. The three security level class marks are security required (R), security preferred (P), and end-to-end (E). In profile development, only preferred and end-to-end are used.

5-39. Security required is used when a subscriber can only complete calls over secure links to approved loops or to a DSVT.

5-40. Security preferred are calls extended as secure, if possible; otherwise, the call is completed in a nonsecure mode. Most terminals are class marked as security preferred. Security preferred is for access to commercial networks and to the DISN.

5-41. End-to-end applies only to DSVTs. DSVT subscribers can only call other DSVT subscribers.

5-42. All five precedence levels can be assigned. The maximum precedence entry specifies the highest precedence level a subscriber may impose on a call. The national command authority (NCA) and/or the theater commander authorize assigning a particular precedence to a user.

5-43. The terminal characteristics entry specifies subscriber terminal characteristics. The three different terminal characteristics are voice (V), multimode (M), and data (D). NCTs and ABCS computer terminals, such as the MCS terminal, using the DSVT are class marked as data if the DSVT is used with MCS only; otherwise, it is class marked "M" for voice and data. Terminals without communication terminals (CTs) and with facsimile are class marked voice only.

5-44. The MS compatible entry specifies whether a subscriber in the data mode is compatible with the AN/TYC-39 (yes [Y] or no [N], and has access privilege for record traffic users with the CT (AN/UGC-144).

5-45. The NRI entry is only for the KY-90, and all subscribers have access by dialing the KY-90 phone numbers. The NRI is given a precedence to support contingencies.

5-46. The progressive conference entry specifies whether the subscriber is authorized to initiate a progressive conference (Y or N). With this authority, the subscriber may dial the selected subscribers for his conference. A conference call can have a maximum of 14 subscribers. The PCL must be loaded in the switches with subscribers needing this service.

5-47. The call forwarding entry specifies whether the subscriber can forward incoming calls to another terminal (Y or N). Do not confuse call forwarding with call transfer. Call transfer is transferring a connected call to another number and is not an MSE capability.

5-48. The commercial network access entry specifies whether the subscriber is authorized to initiate calls to commercial networks (Y or N).

5-49. The EUB class mark specifies essential users terminated at an NCS or LENS for bypass to another NCS if the subscriber's parent NCS cannot provide call processing because of processor failure (Y or N).

5-50. Compressed dialing lists (CDLs) allow selected subscribers to quickly dial frequently called people. The compressed dialing entry specifies whether the subscriber is authorized to use the compressed dialing feature. A zero shows that the subscriber cannot use compressed dialing. A digit (1-5) indicates that the subscriber can call anyone on the same CDL. There are five compressed dialing lists each containing up to 80 subscribers. Each entry is assigned a number between 20 and 99, which then becomes the compressed dialing number. Figure 5-2 shows a CDL.

5-51. Zone restriction lists (ZRLs) may be permissive or restrictive. ZRLs either allow a subscriber access to anywhere in the network or restrict access to certain areas. The restrictive list is for routine users only and limits them to calls within the corps network. Changes to this list are made at the NPT and sent by technical message to the NCS/LENS.

5-52. MSE wire subscribers may be class marked for direct access service (DAS). An NCS or LENS can have up to 60 assigned subscribers, and a SENS can have up to 10 subscribers. DAS can be assigned as a paired operation, where subscriber A can only call subscriber B and vice versa. DAS can also be assigned as a one-way operation, where subscriber A can only call subscriber B, but subscriber B can call any MSE subscriber. One-way operation is mainly used; it can also be used as the initiator of a preprogrammed conference. When a DAS subscriber initially connects to a switch, he must contact the switch operator and provide the directory number to which he desires direct access. Once the operator programs the switchboard, service is automatically provided. When the subscriber no longer requires DAS, he must contact the switch operator to disconnect this service.

5-53. The rekey ID 1 entry is valid with wireline DSVT-like devices only. Rekey IDs 2-23 are used for MSRTs only. Rekey IDs 24 and 25 are not assigned in the GSPM 255. Each ID (1-25) identifies the rekey variable of a DSVT-like net (recommended maximum of 90 terminals).

• Net IDs A and B are not used.
• Bar truck access and bar call were added with the GSPM 255.
• The network manager must use the GSPM 255 to assign profiles to subscribers.

Note: The NPT using the PBOOKII software application supports both the 63 and the 255 profile matrix. The subscriber list management (SLM) application of the NPT can manage the subscriber database, including the PAL, CDL, and ZRL.

PREPROGRAMMED CONFERENCE LIST REQUIREMENTS

5-54. Authorized PCL members can initiate a conference call with members of the PCL list (Figure 5-3). There can be a total of 20 PCLs numbered from 20 to 39, and each list can contain up to 14 subscribers. It is also possible to have four PCLs with a maximum of five subscribers each if there are enough bridge terminal cards in service at the switch. At the top of each list, YES or NO is circled to indicate whether security is required for the conference list. A YES entry requires a loop key generator (LKG) per instrument per call. Each DSVT/MSRT (whether security is circled YES or NO) requires an LKG per instrument per call. Therefore, the standard for programmed conferences should be DNVT telephone numbers and a security NO entry. Multiple conferences outside the standard will degrade service at the NCS.

5-55. There are 20 corps common PCLs numbered 20 through 39. Only coordination with and aproval of the corps signal office can change these PCLs. Any temporary change for a particular exercise does not require a change to the tactical standing operating procedure (TSOP), but it does require a change to the tactical standing operating procedure (TSOP) but it does require updating a work sheet for that period. Table 5-7 shows an example of the corps PCL assignment.

TEAM LABEL DATA FILE REQUIREMENTS

5-56. The US Army Signal Center enters team label data into the team label data file (TLDF). The signal organization network manager or PAL manager for that database validates the TLDF. All teams are included in the TLDF. All MSE signal teams are assigned team labels according to the global team labeling scheme (Figure 5-4.) Table 5-8 shows the resulting corps standard team designation chart, which is used for team C2. Table 5-9 shows an example of the 1st Division's team labels.

FREQUENCY MANAGEMENT REQUIREMENTS

5-61. Table 5-12 provides AN/GRC-226 signal-to-interference ratios. This data represents operation at the highest (1,024 kbps) data rate. The data assumes a signal level at the terminal to the receiver unit at -88 dBm. Signal-to-interference ratios corresponding to various frequency separations between the received signal and the interference signal are given. The data applies to operation in either frequency Band I or III, respectively.

5-66. The SHF radio AN/GRC-224(P) operates in a single frequency band. This band is 14,500 to 15,341 MHz and is divided into eight subbands. The subbands are paired to each other for the assignment of transmit and receive frequencies. The frequency manager selects the SHF frequency band when preparing the open LOS radio link project. Table 5-13 shows SHF and channel allocations for bands L and M. Band L is assigned to switches and Band M is assigned to LOS radio terminals. The following values characterize the performance of the SHF radio relative to the system communications margin computation.

• Maximum transmitter power at the antenna, operating at 4,096 kbps: +13 dBm.
• Transmitter and receiver are located directly at the antenna; therefore, no cable loss.
• Receiver sensitivity, operating at 4,096 kbps: -77 dBm. No quantitative data is available on the SHF radio's signal-to- interference performance. Table 5-14 shows estimated SHF radio signal-to-interference ratios. This estimated data is used until more accurate data can be provided.

5-67. The antennas can operate at either vertical or horizontal polarization. The NPT selects the antenna polarization for each LOS radio link by either an automatic or a manual mode.