Starting the Software

  • The software has been installed.
  • The Siveillance Control server has been started.
  • The hostname and the site name of the engineering server are known.
  • The client and server require a network connection. The alarm systems to be configured must be connected to this network.
  • The corresponding certificates have been installed in the installation phase.
  1. If you log in for the first time, enter the following address in the address bar of your browser:
    https://[Hostname]:8443/login
  • The login page appears in the language selected in the browser.
  1. Enter the following login data:
  • User: Enter your username.
  • Password: Enter your password.
  • Language: Select a language.
  1. Click Download Launcher.
  • A ZIP file is being downloaded.
  1. Open the file explorer and find the zipped folder.
  1. To unzip the entire folder, right-click and select Extract All, and then follow the instructions.
  1. Double-click the folder to open it.

To quickly access the Siveillance Control client, create a shortcut to the SiveillanceControlLauncher.exe file on your desktop.

  1. Double-click the SiveillanceControlLauncher.exe file to start the client.
  • The launcher immediately starts to download the Siveillance Control application.
  1. In the login dialog, enter the following data:
  • User: Enter the username to log in with.
  • Password: Enter your password.
  1. Click Log In.
  • If the username or password are incorrect, the login button is grayed out for ten seconds and you are unable to log in.
  • After three unsuccessful login attempts, an alarm message is generated in the Events/Messages perspective and is distributed to all workstations.
  1. In the login dialog, select a workstation.
  1. Click Start.
  1. If you log in for the first time, complete the following steps:
  • In the Change Password dialog box, enter a new password.
  • Retype the password to confirm it.
  • Click Finish.

Starting the Software as a Standard User

You can log in to the running client using a standard user that is available by default in Siveillance Control. This standard user is able to access only a subset of the client's features due to its limited permissions. The standard user permissions can be easily configured according to the customer's needs. For more information refer to: Creating Authorization Rules.

After switching to the standard user, your workstation can be used for informational purposes, preventing unauthorized usage of it. Due to the limited permissions of the standard user, the following perspectives are available in the engineering client:

  • Engineering
  • Events/Messages
  • Operator Log

To log in as a standard user, you have the following options:

  • The engineering client is displayed.
  1. In the menu bar, select File > Log off and click OK.
  1. In the menu bar, select File > User Login. For more information on how to switch users and user groups, refer to: Switching Users.
  • The system switches to the standard user of the Standard user group.
  1. To check the standard user's permissions, click System Engineering > Users > Standard > standard in the User and Authorization Management perspective.

Exiting the Software

  • Time-critical alarms can still be processed by another operator.
  • Time-critical alarms can still be processed by a supervisor, if you are the last user logging off.
  1. You have the following options to exit Siveillance Control:
  • In the menu bar, click the following symbol:
  • In the menu bar, click File > Exit.
  1. Confirm with Yes.

Loss of Connection: What to do?

When the connection is closed, no messages are received.

Responsibility for operation is thus passed to the alarm systems in order to ensure reliable alerting.

If the connection between a client and the server goes down temporarily, the client tries for 30 seconds to restore the connection automatically. After this time, a notice window is displayed. If the communication error window appears, restart the software.

If the connection is not restored after restart, contact the network administrator.