| Access Control |
|
 | Users are assigned to workstations by Lab Assistants through Dashboard application. |
|
|
 | Unattended workstations can be locked to prevent unauthorized user access. |
|
|
 | Locking can be integrated with user sign-in or performed independently. |
|
|
 | Users will be warned several minutes before their user session times out, so they can complete their job before the workstation gets locked. |
|
|
 | "Strict", "Liberal" and "None" locking modes can be specified on the system level and overwritten on the Room, and Workstation levels. In "Strict" mode, a workstation gets locked when user signs out and unlocked when user signs in. In "Liberal" mode, a workstation gets unlocked when user signs in but is doesn't get locked when the user signs out. In "None" mode, locking is not integrated with user sign-in. |
|
|
 | Dashboard may be integrated with card-readers to speed up sign-in process. |
|
|
 | Sign-in data is saved to access log. Access logs can be searched to find users who occupied a particular workstation at a particular time or to find workstations that have been occupied by a particular user. |
|
|
 | Violators can be added to the Alert List. Once a violator from the Alert List tries to sign-in, Lab Assistant will get a warning. |
|
|
 | Threat levels can be associated with each Alert List entry to allow for a policy that prescribes different actions for different types of violators. |
|
|
| User registration |
|
 | In case the lab occupies multiple rooms, Lab Assistants can see the occupancy of all the rooms and redirect incoming users to under-occupied facilities. |
|
|
 | The entire room can be marked as reserved for a class. The instructor who delivers the class can indicate whether she/he permits other users to occupy remaining workstations. |
|
|
| Wait Lists |
|
 | In case there are no workstations available for sign-in, users can be added to waitlist. |
|
|
 | Users can choose wait-listing criteria such as "wait for any machine in the room", "wait for a machine of a particular type", or "wait for a particular machine". |
|
|
 | Lab Assistants get notified once the possibility to assign a waitlisted user to a machine arises. |
|
|
| Maintenance |
|
 | The system keeps the list of maintenance issues associated with workstations. |
|
|
 | Once a new open issue is submitted, Technicians get notified by e-mail. |
|
|
 | Each Technician can view the list of currently open issues. |
|
|
 | Lab personnel can search the issue database specifying various search criteria. |
|
|
 | Each issue can be ranked by severity, type, priority, and status. Custom values of these criteria can be added during the system installation. |
|
|
 | Technicians can mark workstations unavailable for user sign-in. |
|
|
 | Lab personnel can collaborate on issues by adding notes. Once a new note gets submitted, issue creator and all technicians get notified by email. |
|
|
| Lab Supervision and Payroll |
|
 | Lab Managers can view the current status of the lab through Manager Dashboard. |
|
|
 | Lab Assistants must register with the system when they start and end their shifts. |
|
|
 | Payroll data is calculated based on Lab Assistant rate and attendance records. |
|
|
 | Payroll data can be exported in the form easy to submit to HR department. |
|
|
| Concurrent License Management (Software Metering) |
|
 | System can enforce a policy permitting only a limited number of users in the entire lab to use a particular application. That allows for purchasing a limited number of concurrent software licenses and still installing software on all the machines in the lab. |
|
|
 | Alternatively, the system can be set up to work in "info-only" mode, when it registers violations of concurrent license terms without shutting down the application. |
|
|
 | System can prevent users from running a particular application such as file exchange clients, games, or instant messengers. |
|
|
 | System allows managed applications to be deployed in different file system locations on different machines. |
|
|
| Surveillance |
|
 | System allows to decrease the maximum number of concurrent users at runtime. |
|
|
 | Security Administrators can take screenshots of user display. |
|
|
| Classroom Control |
|
 | Security Administrators can view the list of processes run on each workstation. |
|
|
 | Security Administrators can kill processes running on user workstations. |
|
|
| Reporting |
|
 | Security Administrators can send messages to workstations. |
|
|
 | The system can present transactional data as reports in tabular and graphical form. |
|
|
 | Each report allows user to set a detailed search/filtering criteria. |
|
|
 | Lab occupancy reports show how many workstations were occupied by users on a particular day of the week or on a particular hour of the day. |
|
|
 | Workstation availability reports show how many workstations were available for user registration. |
|
|
| Configuration |
|
 | Downtime report shows how well workstations have been maintained and how reliable is a particular type of equipment. |
|
|
 | Waitlist reports can tells if there is a deficit of any type of equipment. |
|
|
 | Out-of-the-box installation provides Lab Assistant, Supervisor, Technician, Administrator, and Security Administrator roles. Each role has a set of tasks associated with it. |
|
|
 | Roles/Tasks breakdown can be adjusted to match employee roles in the client's organization. |
|
|
 | One person can have multiple roles. Administrator can set up a default role for each person. |
|
|
| System Features |
|
 | The System allows for setting up a different "skin" to fit your corporate look & feel standards. |
|
|
 | The System allows to configure a number of business rules in assess control, maintenance and security administrator areas to meet your business process requirements. |
|
|