Home   |   Contact us      Company  |  Product  |  Solutions  |  Customers  |  Partners  |  News  |  Events  |  Customer Portal

Scense Architecture

The graphic below demonstrates a simplified picture of a scalable IT environment based upon the Scense solution. The picture gives a schematic overview of the communication between user and Scense (using Scense Client), and IT operator and Scense (using Scense Explorer) at runtime.
The Scense Engine Object and Database form the heart of the Scense system. The Scense Engine Object receives the commands from the Scense Client en communicates these with the database.

Explanation of Terminology

Fat Client
If used for the first time, applications are installed by Scense copying the necessary files from the central repository to the workstation. If used before, the application is directly started, activated from a central repository, and runs on the desktop.
Thin Client
Applications run on a Terminal Server.
Scense Client
Program that communicates with the user. It shows the applications to which the user has access, and advises the user how to keep the computer 'clean and fast'.
Scense Engine Object
Collects data from the Scense Database, for example for the logon data of User X, being a member of group A.
Scense Database
Contains authorization information per application and per user type. Also contains the actions that have to be executed at different moments, e.g. logon, application installation, logoff.
Scense Explorer
Program through which the IT department can communicate with the Scense Database. The IT department can e.g. modify what user groups have access to what applications, or modify the actions that have to be executed at every specific moment during a user session.