Emerson Exchange 365

Do you really want to log off the user if they are actively using the application, or simply if they have been idle ? They could be in the middle of something important, and would have to log in again during a very inconvenient moment. I once wrote some scripting to automatically do this based on a dedicated supervisor / administrator name, but it should be done judiciously. I would stick to configuring idle log off for all users.

First complexity is that you cannot easily tell which DeltaV user group a user is in because user groups in DeltaV are actually templates that apply keys, but the application doesn't really keep track of their group beyond that. This is why in the 'about' windows for DeltaV you can see a users keys but not their group.

You thus have to identify what group they are in by virtue of what privileges they possess. In operate, you can use the THISUSER.USER_CAN
[AREA_NAME][LOCK_NAME] parameter to assess whether the user has the lock, however neither area name nor lock name can have a space, so I'm not exactly sure how you would use this feature. A call to Emerson may be in order to get the specifics.
In the past, I have used the [_B_CAN_WRITE_] [_CAN_WRITE_] qualifiers against parameters of known locks to determine if the user has rights to modify the parameter and by virtue of right what group they belong to.

The next complexity is to have a process (most likely in operate or scheduler) watch for user changes. The currently logged in user is read by animating a variable in user.fxg or si_globals.fxg to THISUSER.USERNAME. The on_change event for this variable triggers checking to see if the user is of a particular group as explained above, and records their log in time. A separate event (like a schedule timer) periodically checks (every few seconds) to see if that user is still logged in and whether the new time - initial log in time is longer than threshold.