Individual Activity Manager (IAM)

[Product_Support]

Issue

Individual Activity Manager (IAM)

Environment

• I/NET Seven
• Individual Activity Manager (IAM)

Cause

Individual Activity Manager is designed to automatically disabled tenants if they have been dormant for a user configurable length of time.

Resolution

I/NET displays this editor when you select the Individual Activity Manager Configure button from the Access Control Options editor. The parameters in this editor allow you to enable and configure the Individual Activity Manager (IAM) system. This system monitors specific tenants for individual activity. If an individual of a monitored tenant fails to use their key/card within a specified duration, the individual automatically becomes disabled. The time for these parameters to take effect is the day it is scheduled to start + 24hrs + the duration.

Formula = Start date Midnight + 24hrs + the configured duration = Inactivity duration disable.

Use this editor to specify tenant(s) that this host workstation will monitor for individual activity. You can also specify the duration of inactivity that will cause a user to become disabled.

The tenant selections that you make in this editor are not globalized; therefore, you must visit this editor and select the appropriate tenants on each host workstation that will monitor DPU activity. Caution: An I/NET host workstation can only monitor activity at a DPU if the appropriate tenant is selected in the IAM editor and at least one of the following criteria are met:

• The messages masking you’ve defined for your system allows the host workstation to receive transaction messages from the DPU.
  
  - OR -
   
• The host workstation shares the same file master as another host workstation that receives transaction messages from the DPU and has the appropriate tenant selections. In this case, the DPU activity is globalized daily at 12:30 AM.

An individual can become disabled because of inactivity at "monitored" DPUs, even though the individual has had sufficient activity at un-monitored DPUs. Ensure that your system's message masking or file equalization allows for proper monitoring of DPU activity.

Configure individual activity management as follows:

1. Within the list of tenants, select () each tenant that this host workstation will monitor for activity. You can use the All Yes and All No buttons as necessary to help speed the selection process.
2. Specify the Duration of inactivity that will cause individuals to become disabled.
   1. Choose a duration setting of None, Daily, Weekly, Monthly, or Yearly.
      NOTE: If you choose None, no activity monitoring will be performed.
   2. Choose a Duration Interval setting. The available range for this value varies depending on the duration you specified in the previous step. Regardless of which duration setting you chose, the maximum limit is equivalent to 4 years.
3. Select OK to accept these settings.

The configuration parameters that you select apply to all tenants selected. You can not configure different durations per tenant.

If you would like to exclude specific individuals from activity monitoring, you can use the Individual Parameters Editor to set the individual's IAM parameter to Graced.

Here is an explanation of how the IAM works:

1. Configure IAM in the AC Options editor. If that is off, nothing will happen other than the update of the CurrentMaxIamEventID (described below).
2. A tenant selection is then required for configuration. Every individual in that tenant will have IAM turned On and will automatically be included unless the graced checkbox for IAM in the individual editor is checked. If it is checked, that individual will not be disabled due to IAM.
3. As a day goes along, people make card reads at doors and the transactions are stored in the Events table. Every morning at 12:30am IAM saves the last CurrentMaxIamEventID as the minimum index to check. It checks where the current Events table index is and saves that as the new CurrentMaxIamEventID.
4. It then goes through all of the events between those two indices (starting and stopping points) and looks for individuals that are in the IAM tenants and not graced. It puts those individuals in the IamUser table along with the time and date of the last transaction.
5. Next it runs through a test to see if the individual has been dormant for the specified time that is set for IAM. If it finds any that have passed the expiration, then it will check the Disable checkbox in the Individual table and remove the entry from the IamUser table.

If an operator turns ON the IAM at an arbitrary point after I/NET has been running for a while and accumulates transaction events, only those transactions that occur after turning on IAM will be able to be affected by IAM. No events before the most recent 12:30am rollover will be checked because they are already out of the range of the IAM test.

IT is highly recommended that DCU synchronization is enabled for each access controller. IAM uses the host PC's clock (not the controller clock) to calculate the start time and stop time in the IamUser table. It is possible for the two clocks to get out of sync and cause problems.

To test IAM:

1. Give a minimum of a day and a half before reading test cards after initial setup.
2. Use 4 cards - 2 graced, and 2 non-graced.
3. Set up IAM and then read all 4 cards for reader entry.
4. Wait two days to re-read. 
5. It is not recommended to attempt to speed up the test by altering the PC and controller clocks. Changes are, the IamUser table will get scrambled and require a TAC Software engineer to fix the table.