HERRAMIENTAS DE PRODUCCIÓN AJUSTADA, LEAN MANUFACTURING

Static configuration information, for call processing support, is used to identify individuals and groups that use the system and what services the system must provide to those individuals or talkgroups.

Static configuration information is entered in two places:

• The User Configuration Server (UCS) through the User Configuration Manager (UCM) application. Within this application, records are built for radios, radio users, dispatch consoles, talkgroups, and multigroups.

Parameters that affect the operations of all radios in the system, such as site access denial, are also entered in the UCM.

• The radios through their specific programming software. Static configuration information may be divided into four parts:

• Home Zone assignment for individual and talkgroup IDs

• Identification numbers and aliases for both individuals and talkgroups • Call services and system features allowed for that individual or talkgroup • Valid site settings for each individual and talkgroup

Valid site settings, in conjunction with the “Site Access Denial” setting (see5.1.2 Infrastructure Configuration, page 5-7) play an important role in mobility management when a radio attempts to register or a group member attempts to register to a site.

The static user configuration information is referenced by the system each time a radio attempts to register to a site and/or affiliate with a talkgroup.

Configuration information must be consistent when programming the UCS should be consistent with the configuration information in the radios.

5.1.1.1 Default Records

The system can be configured to allow access to radios when no configuration information is available from the UCS. These radios are assigned a default configuration record automatically on initial system access. This default record gives them a predefined set of call services on the system. If the system is configured to disallow default access, a radio user cannot access the system without first having configuration information programmed in the UCS.

5.1.1.2 Identification Numbers

5.1.1.2 Identification Numbers

ID numbers are one of the key configuration elements that must be entered into the system. Based on the ID numbers that have been entered, the system determines the following:

• Whether or not the individual radio or group is allowed to register at a site. • Which call services the individual radio or group can use

• What system features the individual radio or group can use • Which zone is responsible for controlling the call (for group calls)

5.1.1.2.1 Programming ID Numbers

Individual and group IDs information from the system fleetmap is programmed into the following areas of the system:

• Using the UCM application, all individual and talkgroup IDs are entered in the UCS.

• Using the applicable programming software, each radio is programmed with the system ID, its unique individual ID, and as many talkgroup IDs as needed.

Each console position uses one individual ID.

5.1.1.3 Home Zones

The Home Zone mapping object in the UCM application provides the capability to divide into ranges the total number of individual and talkgroup IDs that can be used in the system and to assign the ranges to the various zones. All of the home zone assignments for groups and individuals are compiled into two home zone maps:

• Individuals to Home Zone • Groups to Home Zone

For example, Zone 1 can be assigned an Individual ID range that can include IDs 1000 - 1999, and a talkgroup ID Range that can include IDs 1-100. Zone 1 becomes the Home Zone to any radio or talkgroup programmed with a corresponding ID from the Zone 1 individual and talkgroup range tables.

The figure below shows the home zone mapping window, which is part of the UCM application. The tabs in this window allow you to modify the individual and group home zone maps to associate a range of IDs with a particular zone. The record creates two tables, one for the individual IDs, and a separate table for the talkgroup IDs.

Figure 5-1 UCM Home Zone Mapping Window

A system with a single zone requires that all individual and talkgroup IDs be assigned to Zone 1. IDs mapped to non-existing zones can not be used.

Home Zone mapping requires that all IDs be accounted for in the ranges used to create a map. Whether the map consists of one range or 2048 ranges, IDs 0 through 16.777.215 must be assigned to the map.

5.1.1.4 Radio Identification

5.1.1.5 Radio User

Table 5-1 Short Subscriber Identity Ranges

ID Type ID Range Description

System 0 Reserved for the system. Individual or

Group

1 to 13.999.999 Available for individual or group short subscriber identities (ISSIs or GSSIs). Each ID can identify a unique group or individual. The same ID cannot be assigned as both an ISSI and GSSI.

Alias 14.000.000 to 14.999.999

Available for alias short subscriber identities (ASSIs).

Alias or Fleet 15.000.000 to 15.999.999

Available for ASSIs or Fleet Short Subscriber Numbers (FSSNs).

System 16.000.000 to 16.777.215

Reserved for the system infrastructure ID, gateway IDs, default records, and other system functions.

5.1.1.5 Radio User

The Radio User object is used to create records that identify all users on the system and their capabilities. The object can also be used to modify existing records. A radio user record includes specific priority levels and access rights for dispatch and interconnect. To configure a radio user, you must know how they access the system and what capabilities they require for this access.

Radio user records rely on the replication of data between the User Configuration Server (UCS) and the Zone Database Server (ZDS). For example, if a site is added to a specific zone in the Zone Configuration Manager (ZCM), it cannot be configured as a valid site in the radio user record until the information has been replicated to the UCS. If that site is deleted from the zone, the ZCM user continues to specify it as a valid site for a radio user until the UCS is notified of the deletion.

5.1.1.6 Profiles

A profile is a master list of common attributes or capabilities used by radio users, talkgroups, and multigroups. Creating a profile allows you to enter the information one time and reference the profile from an individual record. One does not have to enter the information separately into each record. You can create a different profile for each type of function and group of users in your system, up to a maximum of 2000 profiles.

Using a profile helps to reduce the amount of data that has to flow through the network between the UCM and the Zone Controller. Profile information includes data that relates to radios, radio users, and talkgroups who perform the same function. For example, all radio users associated with the Fire Department require the same resources, so you can use a profile to create a master file for their records.

A record can have a one-to-one relationship with a profile (up to the 2000 profile limit), or many records can be mapped to the same profile.

5.1.1.6.1 Radio User Capabilities Profile

The Radio User Capabilities Profile object defines access parameters for radio users such as: • Group/Private Call Priority Level

• Announcement Call Enabled • Private Call (PC) Enabled • Group Call Enabled

You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a specific group of radio users. Every radio user is assigned a Radio User Capabilities Profile.

5.1.1.6.2 Radio User Valid Sites Profile

Radio User Valid Sites Profile object is used to define a list of specific sites in the system the radio user has permission to access. Every radio user is assigned a Radio User Valid Sites Profile. You can use a Radio User Valid Sites Profile record to define a set of sites that are common to a specific group of radio users.

5.1.1.6.3 Radio User Interconnect Profile

The Radio User Interconnect Profile object defines interconnect call capabilities for radio users. Every radio user is assigned a Radio User Interconnect Profile. You can use the Radio User Interconnect Profile record to define a set of parameters that are common to a specific group of radio users.

5.1.1.7 Templates

A template provides the means to configure a record that can be applied to radio users who need the same set of system access parameters. Templates consist of a combination of attached profiles and parameters set directly on the record.

5.1.1.8 Configuration Updates

During system operation, updates are sometimes needed to an existing user configuration information. Changes to a radio user configuration are entered in the UCS. Once entered, the changes are copied to the ZDS in each zone during the database replication process. Each ZDS then distributes the applicable Home Zone information to its Zone Controller; the Zone Controller uses this information to populate its Group Home Location Register (GHLR) and Individual Home Location Register (IHLR).

For more information about User Profiles see Radio and Radio User Management.

5.1.1.9 Talkgroup

The talkgroup object consists of information that identifies a group of radios that communicate and interact together on the system. Talkgroup and multigroup IDs are selected from the same range of valid IDs that are available for

5.1.1.9.1 TG/MG Capabilities Profile

5.1.1.9.1 TG/MG Capabilities Profile

The TG/MG (talkgroup/multigroup) Capabilities Profile object defines the capabilities for a talkgroup or

multigroup. You can use the TG/MG Capabilities Profile record to define a set of parameters that are common to a specific talkgroup or multigroup.

Each TG/MG Capabilities Profile contains capability parameters that can be customized per configured profile. Every talkgroup and multigroup is assigned a TG/MG Capabilities Profile. For more information on Talkgroup/Multigroup Capabilities Profiles, see Configuration Management, UCM.

5.1.1.10 Object Group

Object Group allows to identify a group in the Object Call feature. The Object Group number consists of the prefix and the object number, which further consists of two parts – Subject and Instance. This gives the possibility to distinguish between different groups working with the same subject or to distinguish several instances of a subject. For more information see the Object Call manual.

5.1.1.11 Barring of Incoming/Outgoing Calls

The BIC/BOC feature allows to control the permissions of radio users to initiate or receive calls from certain talkgroups. To configure this feature, create a Barring Profile, which specifies the subset of user IDs (SSIs) for which calls will be barred. BIC/BOC can control incoming or outgoing individual calls, group attachment and group call requests. For more information see the Barring of Incoming/Outgoing Calls manual.

5.1.1.12 Multigroup

The Multigroup object is used to create records that identify a group of talkgroups that are the target of multigroup announcements.

5.1.1.12.1 TG/MG Valid Sites Profile

The TG/MG Valid Sites Profile object defines which sites the talkgroup or multigroup has access permission for in the system. Every talkgroup and multigroup is assigned a Valid Site Profile. You can use the TG/MG Valid Sites Profile record to define a set of sites that are common to a specific talkgroup or multigroup.