Add/Update Users' Access Information {CACO-1}

This option will link the user to personal access times and one or more profiles. A record must exist in this option for all users to have access on the control unit. All data in this option will be sent to the control unit with {CACO-2}.

A card record must exist in {CACM-2} before the access data for the user can be created.

The data in this option is also generated automatically when the following is done:

A student is registered for a qualification
A personnel member is appointed
An Other user is created

The user can set parameters in {CACC-21} to automatically generate a card and access information for users. A profile is then created according to the default time, as set in {CACC-3 }, and the default profiles, as set in {CACC-6}.

Fields in the option:

Block 1: User Information

The following rules apply:

When a Profile code is linked to a user on this option, the status will automatically be an 'N' in field CBNSTAT; and an 'I' in field CBNINCLUDE. These fields can then will no longer be updated.
If it is a new profile that is added with a status of 'N' and 'I' and the user wants to delete it before it is sent down, the user can delete it on the screen by using this option.
If an 'I'/'N' record was added and sent down, {CACO-2} it will change to 'I' / 'P'.
If the user needs to delete an 'I' / 'P' record in this option. The status will then change to 'E' and 'U'. The record will then be sent down to the security unit as a 'delete' record and the status on field CBNSTAT will change to 'P' but CBNINCLUDE will remain an 'E'.
If all the records for the user per target with CBNINCLUDE are equal to 'E', then the system will create 1 delete record for the target and send it down, after which all the records for the user will be deleted from CBNPSA.

Field	Type & Length	Description
User Type	A1	Identify one of the three types of users, namely (S)tudent, (P)ersonnel or (O)ther.
Number & Name	N9	Enter the student, personnel or other user number of the user. The system validates that it is a valid user and displays the title, initials and surname of the user.

Example:

Block 2: Time Information

This block contains the personal access time that should apply to the user in block 1. The building’s access times take preference over the user’s personal times, except if the user has an override code.If the user has an override code equal to or greater than the override code on the security unit, his/her personal time takes preference over the building’s time.

Field	Type & Length	Description
Day of Week	N1	Enter the day of the week. The system validates that it is a valid day and displays the day name, 1 = Sunday etc.
Time Code	N2	Enter the time code. The system validates that it is a valid time code and displays the open and close time as set up in {CACC-3}.
Override Code	A1	Enter the override code. The system validates that it is a valid override code and displays the code name as set up in {CACC-2}.

Example:

Block 3: Link to Profiles

In this block the security areas (e.g. building) to which this user needs access, is defined.

Field	Type & Length	Description
Profile Code	N6	Enter a profile code. The system validates that it is a valid profile code as created in {CACC-6} and displays the description.
Include/Exclude	A1	Should the area be (I)ncluded or (E)xcluded for this person? This field allows the system user to make a certain profile active or not, for certain periods, without adding or removing it.

Example:

Processing Rules
	No special processing rules.

Date	System Version	By Whom	Job	Description
21-Feb-2007	v01.0.0.0	Bea Swart	t134360	New manual format.
21-Aug-2007	v01.0.0.0	Charlene van der Schyff	t134360	Insert Correct images
12-Mar-2008	v01.0.0.0	Vaughn Dumas	t134360	System owner proof read
19-Aug-2008	v01.0.0.0	Charlene van der Schyff	t151624	Edit language obtained from proof read language Juliet Gillies.