• Follow all instructions in this documentation.
  • Keep this documentation for reference.
  • Always include this documentation in the product.
  • Make sure to back up all data before updating the software to avoid data loss.
  • The display of alarms in Siveillance Control provides clarity and support in critical situations and therefore only ever complements the actual approved alerting. Siveillance Control is not covered by system certification of the alarm system. All control elements of the connected alarm system must therefore either be operated permanently in parallel mode at a continuously staffed location or it must be ensured that appropriate standby functions of an approved system control panel are activated in the event of failure.
  • If two different management systems (for example Siveillance Control, GMA-Manager and Operation Scheduler) share the same OIS site to communicate to the same subsystem (for example SIGMASYS) both are equal rights consumers for OIS.
    If now the connection to one management system is closed (either by fault or last client has logged off), OIS will keep the connection to the subsystem, because there is still a consumer of that connection available and so the responsibility is not returned to the control panel.
    To avoid such unwanted situations especially with Operation Scheduler, which doesn’t have an own message interface for alarms and SIGMASYS, which is following a dedicated responsibility concept, you have to set up the configuration with separate OIS instances (site) for each management system.
  • Carry out a system test where you can trigger all detectors and then calmly check the reaction of the system and the displayed data.
  • After a restart, the states in Siveillance Control and the alarm systems must be checked for parity and plausibility.
  • Data privacy: We would like to point out that personal data (for example user IDs, email addresses and telephone numbers) may be stored in this system, for example in OPSs and operator logs. Appropriate care and confidentiality must be taken when using and securing such data.
  • Familiarize yourself with the alarm system commands and their effects as they are not described in this manual.
  • The system can only be as good as the data supplied to it! The entries made by the data supplier or user are checked for correctness and plausibility where possible, however there may be erroneous or incorrect entries. For example, it lies within the responsibility of the operator to decide if an alarm is to be recorded manually for an emergency call by phone or to ascertain whether actions that cannot be performed by Siveillance Control have actually been carried out.
  • Although computer viruses are not a major threat in Linux systems, you should nevertheless check the reliability of data media and files when importing data.
  • The usage of alerting services such as email, fax or SMS is no substitute for transmission equipment to the fire department or police.