CONTENIDO PROGRAMATICO:

The People/Badges choice under the People menu configures the Toolbar’s People Button to access the People/Badges window, and brings up the following screen. The tabs at the top of the People listing allow you to view the list sorted by LastName, ID or Badge Id.

The ~Individual Permissions tab at the top right shows the doors and shifts for which this individual has been given individual permissions. The Group Name box at the bottom right shows the group(s) to which this person is assigned, and the person will have rights to other doors/shifts as defined for the group

As shown above, the system is displaying a person’s image. You may define up to 9 different images or pictures associated with a person. These are associated with the Index field shown on the screen, which can be set from 1-9. The access control software monitor program displays the index 1 image when the person’s badge is presented at a controller. The associated badge printing software will allow all of the images to be printed on badges. The delete/select image buttons allow you to delete the image or select a new one from the image directory. If you are using images, they must all be collected together into a single directory which must then be selected as the image directory using the directory selection mechanism under the Files/Reports menu item. You can set the image directory from both the Administrative program and from the Monitor program using a similar technique.

The list on the bottom left shows the badge(s) that are assigned to the person. The List on the bottom right shows the groups to which the person belongs. You may use the insert and delete buttons under this list to modify the group

membership for the selected person.

The Insert/Change/Delete buttons under the list of people allow you to manage the entries in the list.

The tabs at the top of the screen have the following functions:

 Name and ID sort the window’s top display in the indicated order. Note that the ID field is a 15 character text field and will sort using text rules, not numeric values.

 Badge ID displays BadgeId values in numerical order in the bottom display area. When a badge is selected in the bottom display area, the

associated person is displayed in the top display area

 GUID displays GUID values in sorted order in the bottom display area. When a GUID is selected in the bottom display area, the associated person is displayed in the top display area.

 Badge Expiration shows badges in the bottom screen, sorted by expiration date (if any). If you have not defined any expiration dates for badges the screen will be empty.

 Expired Badges – this will show badges in the bottom screen that are expired, either because they are past the defined expiration date or they were defined to be count limited and the number of remaining uses has gone to zero. On this tab there is a Delete All button which can be conveniently used to delete all expired badges from the system.

 No Remaining Uses – this will show only badges that are defined to be count limited and which have no more remaining uses available.

The Update Permissions button on the lower right of the screen will do a “Partial Compile” for this person, putting their defined permissions into force. If the Queue checkbox is checked the system will queue the compile to be started when the compile process is not already busy. If the Queue check is not set, the system will attempt to start the compilation interactively.

The Review Permissions button can either review the permissions for the selected individual or can review all permissions looking for redundancies and overlapped permissions.

Here is the Review for a selected individual:

This shows the doors and shifts for which the person is authorized. It also shows the door group from which the permission is derived if applicable. The column on the left shows redundant permissions and possible overlapping permissions. As is explained in an appendix, these do not cause any errors in the system but they do introduce overhead in the compile process and can increase the complexity of the permission scheme making it difficult for people to understand and

administer.

Using the Total button calculates the Redundant and Overlapping shifts for the entire database of people and shows the results for each individual. See the appendix for a further discussion of the significance of these numbers. Here is the screen that is displayed when you Add or Change a record.

The fields are as follows:

 First Name – optional Persons First Name  MI – optional Persons Middle Initial

 Last Name – Persons Last Name – required.

 Area – the area with which this person is associated.

 Unique ID – 15 character alpha numeric – – required and must be unique. The Auto UniqueID button will generate a unique value for this field.

 SSN – optional social security number

 Latch Interval – may be marked to use the default value or a special value. The latch interval is how long the door controller will remain unlatched after an authorized badge is presented to the controller. The usual default is 3 to 5 seconds. If a person requires additional time (because of a handicap, for example) the value may be set in seconds. (Valid only for doors operating in HOST mode).

 Default Image – optional default image file – If this is set to one of the image format types (.jpg, .gif or .bmp) the system will assume that there is an image file for this person with the UniqueID of the person as the file name and the selected image file type as the file type. (e.g., auto_14.jpg, auto_14.gif or auto_14.bmp in the example above).

 The User Defined fields are optional. The Names of the fields can be set for a given installation to any desired character strings using a menu described later in this document.

The list box displays the badge(s) currently assigned to the person. The

Here is the screen that displays when you Add/Change one of the assigned BadgeId values.

 The badge id is the number which will be read when the badge is presented to a reader other than an RC-03 or IPBridge.

 The GUID is the value which will be read by an RC-03 or IPBridge.

 Badge Expires – Check the Expires box if you want to assign an expiration date.

 Active Directory – this is a flag that shows whether or not the credential was imported from the Active Directory. You should not normally make any changes to this setting.

 Count Limited – Check the Count Limited box if you want the badge to be valid for only a limited number of uses. If so, set the Remaining Uses field to the number of permitted uses. NOTE: On the Program Doors Screen there is a field that lets you set a time interval for the Use Count. If the badge is used multiple times within the specified interval, it only counts as one use. This allows you to set a tolerance to prevent counting multiple uses if a person presents the badge by accident multiple times at a door. By setting the time interval to 24 hours, you can allow the badge to be used many times during a single day and only count as one use.

 Badge/PIN – this field defines the sources from which the badge should be accepted.

o Badge – accept the badge number only when read from a proximity reader controller or via a Wiegand device connected to the

o PIN – accept the badge number only when entered as a PIN (Personal Identification Number) from a keypad or other serial device.

o External – accept the badge from an external device connected directly to the ISONAS reader through an RS-232 port.

These fields allow you to directly enter a badgeid and add it to the list of assigned badges without using the insert button. By selecting a reader-controller from the dropdown list, and clicking on the Read From button, the system will populate the badgeID field with the last credential that was presented to that reader-controller. This is intended for use when an enrollment reader is used to assign badges without having to type them in.

The Auto PIN button is available if you are defining a PIN code and have the screen set for Keypad only as shown above. This button will automatically generate a unique PIN code with the specified number of digits (default 4). You may set the number of digits to be in the range 1-9.

HID Badges – ISONAS readers deal with HID badges in two modes.  HIDEnabled

In this mode the ISONAS reader uses all of the data it can read from the card and creates a unique 32 bit number which is the card/badge number that is used by the ISONAS system. This number is always different from the HID “card number” because it includes information from the HID site/facility code.

 AdvancedHIDEnabled

In this mode, the ISONAS reader uses a bit mask to select up to 32 bits from the card information. You can set the bitmask to pick off just the HID Card number if you want to (making the ISONAS card number match the HID Card number) or you can include the HID Card number in the

selected bitmask. In this case the ISONAS card number will differ from the HID Card number by an additive constant. The system enables you to enter the constant once and it will be remembered for future uses.

HIDEnabled Mode

If you enter an HID BadgeID and a HID Conversion Factor the system will calculate how an HID badge will be read by an HID Enabled ISONAS

reader/controller which is configured to read HID badges using the Data Mangle algorithm, which used an exclusive OR function to combine all of the bits of data read from the HID card into a single unique 32 bit integer. The HID Conversion Factor can be determined by pressing the button beside the field to bring up the following screen:

This screen requires that you have one example of an HID badge which has been read by an ISONAS controller. If you enter the two badge numbers the system will calculate the required HID Conversion Factor which you may then use to predict the ISONAS Id values for other HID badges which have not yet been read by an ISONAS reader/controller.

NOTE: At some sites there may be multiple HID Site/Facility codes in use!

A third tab provides access to special badge capabilities:

The Change button under the special badge listing brings up the Special Badges screen which is described later in this document.