We have 24 x 7 Operations teams that insist on using generic logons for accessing VMS and security systems. This is primarily due to shift-changes whereby staff leaving shifts not needing to log off and staff staring a new shift not being required to logon. This also eliminates the need to transfer any 'work-in-progress' between shift workers.
However, generic logons are generally frowned upon by IT departments, particularly when systems now are integrated with Microsoft Active Directories. Also of course, the logging of operator activity in the VMS system, has far less value when it is done under a generic user ID. (although individual activity can be sometimes manually reconciled with shift schedules, etc)
Can anyone out there share their experiences with addressing this issue?