Version 11

User Guide
SecurOS ACS User Guide (UG - EN, build 117 on 7/13/2023).

© Copyright Intelligent Security Systems, 2023.

SecurOS® ("SecurOS") and all respective logos are trademarks of ISS Corp, in the U.S. and/or other countries.

Intelligent Security Systems reserves the right to make changes to both this Manual and to the products it describes. System
specifications are subject to change without notice. Nothing contained within this Manual is intended as any offer, warranty, promise
or contractual condition, and must not be taken as such.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any human or
computer language in any form by any means without the express written permission of the copyright holder. Unauthorized copying
of this publication may not only infringe copyright but also reduce the ability of Intelligent Security Systems to provide accurate and
up-to-date information to both users and operators.
 SecurOS ACS 3 User Guide
Contents

Contents
1 Preface 4
1.1 Scope
........................................................................... 4
1.2 Target
. . . Audience
........................................................................ 4
1.3 Using
. . .This
. . . .Manual
.................................................................... 4
1.4 Getting
. . . .Technical
. . . . . . . . .Support
.............................................................. 4
1.5 Design
. . . .Convention
....................................................................... 5
1.6 Design
. . . .Elements
....................................................................... 6

2 Introduction 7

3 Installing and Configuring System 8

3.1 AMAG
. . .Symmetry
........................................................................ 8
3.2 Bosch
. . . APE
........................................................................ 9
3.3 Configuring
. . . . . . . .ACS
. . . . Module
. . . . . . .in
. . SecurOS
...................................................... 9
3.3.1 Server Part
..................................................................................... 9
3.3.1.1 Event Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.2 Client Part
..................................................................................... 14

4 Working with Module 16

4.1 Monitoring
. . . . . . . .and
. . . .Processing
. . . . . . . . . .Events
..................................................... 16
4.1.1 Event Monitoring
. . . . . . . . . .Table
........................................................................... 17
4.1.2 Unprocessed
. . . . . . .Event
. . . . .Panel
......................................................................... 18
4.1.3 Event Information
. . . . . . . . . . .Panel
.......................................................................... 18
4.1.4 Event Filtering
..................................................................................... 19
4.1.5 Processing
. . . . .and
. . . .Commenting
. . . . . . . . . . .Events
................................................................. 20
4.2 Searching
. . . . . . . Events
.................................................................... 21
4.2.1 Searching
. . . .Events
. . . . . . by
. . .Device,
. . . . . . Marker
. . . . . . .or
. .Camera
......................................................... 21
4.2.2 Searching
. . . .Events
. . . . . . by
. . .Person
. . . . . . or
. . .Card
............................................................... 23
4.3 Monitoring
. . . . . . . .States
. . . . . .and
. . . .Controlling
. . . . . . . . . .Devices
............................................... 24
4.3.1 Controlling
. . . . .Devices
. . . . . . .on
. . .Devices
. . . . . . .Tab
............................................................... 24
4.3.2 Controlling
. . . . .Devices
. . . . . . .from
. . . . Media
. . . . . .Client
............................................................... 25
4.3.3 Controlling
. . . . .Devices
. . . . . . .from
. . . . Map:
. . . . .GUI
................................................................ 26
4.4 Jump
. . . .to. .Event
. . . . . Video
................................................................ 27
4.4.1 Automatic
. . . .Jump
................................................................................. 27
4.4.2 Jump from
. . . . .Monitoring
. . . . . . . . . Tab
....................................................................... 27
4.4.3 Jump from
. . . . .Devices
. . . . . . .Tab
......................................................................... 29
4.4.4 Jump from
. . . . .Search
. . . . . .Tab
.......................................................................... 30
4.4.5 Jump from
. . . . .Map:
. . . . GUI
............................................................................ 31
4.4.6 FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.5 Customizing
. . . . . . . . . .Operator
. . . . . . . .Interface
......................................................... 32

5 Technical Support Information 36

www.issivs.com
 SecurOS ACS 4 User Guide
Preface

1 Preface
This section contains general information about this document, the means of its design and use, as well
as how to get additional technical support for the product.

1.1 Scope
This manual provides general information about the interaction of SecurOS with Access Control
Systems, describes the process of configuring a module, and gives some troubleshooting tips
andrecommendations.

The document also describes an operator's GUI, the process of performing common tasks on
provisioning security.

It is assumed that the user has already physically deployed the security network and installed the
SecurOS software on all computers of this network.

1.2 Target Audience

This manual is designed for SecurOS system installers and administrators. It is assumed the user
hasadvanced computer skills, has practical experience with TCP/IP networking, serial (COM) ports
andgeneral CCTV knowledge.

This document is also intended for the SecurOS system operators, having basic skills of computer.
Recommended for reading after reviewing the main product features in the SecurOS Quick User
Guide.

1.3 Using This Manual

This document is organized in such a way that the user can use both its printed and electronic versions.
In the latter case one can use Adobe Reader's Bookmarks feature as well as cross-reference hyperlinks to
navigate through content. In several topics this manual refers to other SecurOS manuals, which can be
found as separate files on the SecurOS installation CD or downloaded from our website
(www.issivs.com).

To get online help (Microsoft HTML Help) just press the F1 key when running SecurOS. In
administration mode You can get context help for a given object/utility by pressing the F1 key when its
settings window/utility window is open. In operator mode, use the F1 key to open a description of the
active window of the current operator interface or utility.

1.4 Getting Technical Support

If you have any questions after reading this manual, please address them to your system administrator
or supervisor.

www.issivs.com
 SecurOS ACS 5 User Guide
Preface

For any further information you can contact the Intelligent Security Systems Technical Support Team:

Note. For all technical support requests, please open a ticket from the ISS Partner Portal:
https://support.issivs.com. You will need to create an account if you don’t already have one.

· in USA:
Phone: +1 732 855 1111
· in Canada:
Phone: +1 778 929 8565
· in Mexico:
Phone: +52 55 9001 5252
· in Colombia:
Phone: +57 320 303 2849
· in Brazil:
Phone: +55 85 9668 2530
· in Central America and Caribbean:
Phone: +502 5517 8395
· in Argentina/ Paraguay/ Uruguay:
Phone: +54 911 5039 6440
· in Peru/ Bolivia/ Chile:
Phone: +56 9 3261 9893
· in Ecuador:
Phone: +57 312 255 2932
· in Venezuela:
Phone: +57 321 722 0425
· in Europe:
Phone: +380 44 299 0810
· in Dubai:
Phone: +971 4 874 7100
· in Qatar:
Phone: +974 6 677 8309
· in Saudi Arabia:
Phone: +966 54 109 9699

To solve problems faster, we recommend preparing the service information described in the Technical
Support Information Section before addressing the Technical Support Team.

1.5 Design Convention

For representation of various terms and titles the following fonts and formatting tools are used in this
document.

www.issivs.com
 SecurOS ACS 6 User Guide
Preface

Font Description

Used in writing workstation names, utilities or screens, windows

bold type and dialog boxes as well as the names of their elements (GUI
elements).

italic type Used to mark out the SecurOS objects.

bold italic type Used to mark out the elements of homogeneous lists.

Used to mark out macro text and programming code, file names and
monospace their paths. Also it is used to specify the necessary options, to mark
out values specified by the user from the keyboard (manually).

Used to mark out the cross-references within the document and

green
links to the external available ones.

1.6 Design Elements

Warning! Serves to alert the user to information which is necessary for the correct perception of the text set
out below. Typically, this information has a warning character.

Note. Note text in topic body.

Additional Information
Used to display additional information. These type of elements contain, for example, the description of options for
executing a task or reference to additional literature.

www.issivs.com
 SecurOS ACS 7 User Guide
Introduction

2 Introduction
This functionality is available in the following editions: SecurOS Enterprise, SecurOS Premium.

ACS Module provides professional operator working with integrated external ACS and Fire Alarm
systems.

Main feature of the Module allows to associate ACS system objects with SecurOS Cameras to provide
operative events verification. One can also categorize ACS events using set of markers ("Alarm",
"Hardware event", "Access granted" etc.) to make processing, filtering and searching more convenient.

Key features of the ACS operator GUI are the following:

· Displaying ACS events in real time mode and possibility to verify events by associated video
records.
· Viewing photo of the access card holder and detailed information, attached to this access card.
· Searching events, associated with the card holder's passage through check point, monitoring
passage sites.
· Displaying list of all devices of the integrated system and their current state, controlling these
devices.
· Searching events associated with specific devices or events, that have occurred in the field of view
of specific camera.
· Playing archive video associated with the event.
· Customizing operator GUI (one can place Event information panel in any position on the desktop,
specify table columns to display, etc.).

Current version of ACS Module supports integration with Bosch APE, AMAG Symmetry.

www.issivs.com
 SecurOS ACS 8 User Guide
Installing and Configuring System

3 Installing and Configuring System

ACS Module provides interaction with external ACS system. Events, data from personal access cards
and other information is queried from the ACS Server. This information is stored and processed within
SecurOS. Data from ACS Server are transmitted to the SecurOS ACS Server, where Integration object is
created and configured, and then this data are transferred to the Operator Workstations, where they are
processed. ACS device control commands are transmitted, in their turn, from Operator Workstations to
the SecurOS ACS Server, and then to an external system. Structure of the SecurOS ACS Module and
operation scheme are illustrated in the Figure 1.

Warning! When configuring system be sure, that ACS Server time is synchronized with the SecurOS ACS Server
time (see Figure 1). Otherwise Module will be suspended.

Figure 1. Module architecture

3.1 AMAG Symmetry

AMAG Symmetry ACS provides wide range of possibilities to control access remotely on the secured
objects of different assignment. Integration with this ACS system allows you to do the following:
· To monitor events and states of the following types of the Symmetry objects: Reader, Reader Group,
Node, Door, Monitor Point, Auxiliary Device, Intrusion area;

www.issivs.com
 SecurOS ACS 9 User Guide
Installing and Configuring System

· To adjust list and type of received events;

· To control ACS objects (from Map: GUI you can control only Door and Reader objects).

All events, available to operator, are listed in the ACS Symmetry object settings in the SecurOS Object
Tree. However, if the event is disabled in Symmetry ACS software settings, you won't be able to receive
this event in SecurOS. Displayed event captions can also be changed in Symmetry software settings, so
text strings, that are displayed in the operator interface, may differ from these ones specified in the ACS
Symmetry object settings within SecurOS.

To provide interaction between subsystems, install XML Open Integration Module in accordance to
AMAG User Guide and configure ACS Module within SecurOS.

3.2 Bosch APE

Bosch APE ACS system can be used individually or as part of integrated solutions for industrial
facilities or security systems.

Key features of integration with Bosch APE are the following:

· Possibility to adjust list and type of received events;
· Possibility to control ACS objects (from Map: GUI, Media Client or ACS: GUI window);
· Monitoring object states (in Map: GUI and ACS: GUI window).

All events, available to operator, are listed in the Bosch APE object settings in the SecurOS Object Tree.
Displayed event captions can also be specified by system administrator in Bosch APE software settings,
so text strings, that are displayed in the operator interface, may differ from these ones specified in the
Bosch APE object settings.

To provide interaction between subsystems, install SDK for Cardholder Data (in accordance with Bosch
GmbH instruction) on the computer, that will interact with APE, and then configure ACS Module
within SecurOS.

Warning! Name of computer, where APE server is installed, can be specified only during SDK software
installation.

To provide interaction between Bosch APE server and ACS Module of SecurOS the shared APEDATA$
directory, located on computer where Bosch APE server is deployed, is used. Ensure that required
directory is created and has read and write access rights.

3.3 Configuring ACS Module in SecurOS

When configuring ACS module in SecurOS you should set up both server and client part. Server part
provides connection with external ACS system, defines set of received events and allows to categorize
them, and also provides links to the SecurOS Cameras. Client (or user) part specifies interface object
settings on the operator workstation.

3.3.1 Server Part

To configure server part of the ACS Module do the following:

1. For proper module operation in the firewall settings open TCP port specified in the settings of the
Database object.
2. Install required software described above on the SecurOS ACS server.

www.issivs.com
 SecurOS ACS 10 User Guide
Installing and Configuring System

3. Create Database object. In its settings select Create new option, specify parameters of the
SecurOS ACS server, then click on Create DB and User button (see Figure 2). Apply object settings.

Figure 2. Database object settings window

4. In settings of the Computer, that represents SecurOS ACS server, then select Database object created
on stage 2 in ACS and Fire Alarm System Database parameter drop-down list (see Figure 3).

www.issivs.com
 SecurOS ACS 11 User Guide
Installing and Configuring System

Figure 3. Computer object settings window

5. Within SecurOS in the ACS group, child to the Computer, that represents SecurOS ACS Server, create
integration object (Bosch APE, AMAG Symmetry, depending on used system). In the created object
settings specify parameters of the ACS server, which will interact with SecurOS (see Figure 4). Apply
new settings, then click on Update configuration button to build ACS object tree within SecurOS.

Figure 4. Root integration object settings window. Connection settings Tab

6. In the integration object settings specify events, you expect to work with. To do this tick checkbox on
the left of event name. Also specify event markers in order to categorize events. For details refer to
Event Markers.

www.issivs.com
 SecurOS ACS 12 User Guide
Installing and Configuring System

7. In settings of the ACS devices, located in the object tree built after configuration downloading, you
can specify Cameras, in field of view of which this object is located (see Figure 5). This allows
operator working with ACS module do not spend time on searching such cameras.

Figure 5. Integration object settings window. List of Cameras

Note. For details of how to jump to the event video refer to Jump to event video.

Warning! To ensure the availability of archive records of critical situations, it is recommended to switch
cameras, in which filed of view the most important ACS objects are located, in continuous recording mode.

If there is a problem when connecting to ACS system or receiving events, you'll see a messages from the
Health Monitor module. Full list of messages is represented in the SecurOS Administration Guide.
3.3.1.1 Event Markers
Each ACS system has its own, quite a diverse set of events (for example, see Figure 6). When working
with Module you can meet a task to specify, which events should be considered as alarm within your
system and which ones require operator response. It also may be helpful to have an ability to categorize
events in order to make it possible to filter and search events. For these purposes, ACS events markers
is provided within SecurOS.

www.issivs.com
 SecurOS ACS 13 User Guide
Installing and Configuring System

Figure 6. Bosch APE object settings window. Events Tab

The following set of markers is provided within SecurOS:

· Operator response required;
· Alarm;
· Hardware event;
· Access requested;
· Access denied;
· Access granted;
· No markers.

All events, the occurrence of which requires an explicit reaction to the operator, are marked with
Operator response required. For example, when it is necessary to grant access for visitor, who
has no access card. Such events are highlighted in ACS: GUI window in specific color and are
displayed in special Unprocessed events panel, to attract additional attention of the operator. Device,
that generated such event, will be also blinking in the Map: GUI until all events, associated with this
device, are processed.

Events should be marked as Alarm, if they inform about access violation or about other accidents, for
example, smoke. If such events does not have Operator response required marker, it also can be
processed in the ACS: GUI window and will cause blinking of the object in Map: GUI. However, in
contrast to events that require mandatory processing, alarm events are confirmed automatically after a
time period specified in the Alarm expiration timeout parameter. If both Alarm and Operator
response required markers are applied to the event, it will be considered unprocessed until the
decision of the operator.

Apply Hardware event marker to watch switching of device modes, system messages and other
required events. When monitoring events using the operator interface, one can quickly jump to all these
events by selecting pre-installed Hardware event filter.

www.issivs.com
 SecurOS ACS 14 User Guide
Installing and Configuring System

All other markers do not result in highlighting event in operator interface, nevertheless they may be
helpful when filtering or searching events. It also possible to apply no markers to further searching of
this category of events.

To apply necessary marker tick its position in the table.

3.3.2 Client Part

To work with ACS Module on the operator workplace, depending on tasks to be solved, you can
configure any combination of three interface objects — ACS: GUI, Media Client and Map: GUI.

The main application to work with the ACS Module is the ACS: GUI window (see Working with
Module). In this window one can view current events and search for events occurred earlier; control
ACS devices and process events.

To allow operator to view video so he can verify ACS event do the following:
1. In the SecurOS Object Tree select operator's Computer. On the Desktop of this computer create child
ACS: GUI object.
2. Create Media Client object on the same Desktop, as the ACS: GUI object;
3. In settings of this Media Client select to use all Cameras, associated with ACS objects;
4. In ACS: GUI object settings select configured Media Client (see Figure 7).

Figure 7. ACS: GUI object settings window

When configuring object (Window position group of parameters) pay your attention to its proportion
in pixels, as this affects the arrangement of the Event Information Panel. If H parameter is greater than
W one, then panel is located on the top of the window and on the right, otherwise.

If it is not expected to view and search events from ACS objects on the operator workplace, but
supporting the ability to control these objects, you can create and configure only Media Client object.
Operator will be able to control ACS objects from Media Client camera cell (for details refer to
Controlling Devices from Media Client).

www.issivs.com
 SecurOS ACS 15 User Guide
Installing and Configuring System

When an alarm event occurs all Cameras linked with the alarm event source can be automatically
displayed on the Media Client. To make it possible, in the Automatically open alarm video list
(see Figure 7) select Media Client located on the same Desktop as the configured ACS: GUI. When an
event with the Alarm marker appears all Cameras linked with the source of the alarm event (ACS object)
will be displayed on the selected Media Client.

Warning!
1. If Media Client's window is hidden under the other windows at the moment of the automatic jump,
then activate it manually to view the video.
2. When alarm events occur frequently (more than one event in a few seconds) use of the automatic
jump to view video is not recommended.
3. It is recommended to use different Media Client for jumping from ACS: GUI and automatic jump to
view video.

Operator can also view states or control certain ACS objects in relation to the graphic plan of protected
territory. To make it possible place ACS objects on the Map in its settings, then select this map in Map:
GUI settings to display it on the Operator desktop. (see Controlling Devices from Map: GUI).

When configuring User Rights specify access denied ( ) privilege to that ACS objects, controlling of
which is prohibited for the operator (see the User Rights section in the SecurOS Administration
Guide). In this case device control commands will not be displayed for this user for all interface objects
described above.

Notes:
1. In the ACS: GUI window the operator will see all events received via selected ACS Controller
regardless of the User Rights settings.
2. The operator has the ability to process events from all devices.
3. Cameras access to which is denied by the User Rights ( ) will not be displayed in the list when
searching events.

www.issivs.com
 SecurOS ACS 16 User Guide
Working with Module

4 Working with Module

The main application to work with the ACS Module is the ACS: GUI window. This section describes
this window and also illustrates the possibilities to operate Module with the help of Media Client and
Map: GUI standard interface objects.

4.1 Monitoring and Processing Events

To monitor and process new ACS events the Monitoring tab of the ACS: GUI window is used
(see Figure 8).

Figure 8. Monitoring tab of the ACS: GUI window

This tab consists of the following main panels (number in figure matches one in the list):
1. Event Information Panel.
2. Event Processing Panel.
3. Event Monitoring Table.

www.issivs.com
 SecurOS ACS 17 User Guide
Working with Module

4. Unprocessed Event Panel.

5. Comment Panel.

Event Processing Panel contains buttons and other controls to process an event. With the help of
Comment Panel operator can create text comment to the event. For details about these panels see
Processing and Commenting Events. Other window elements are described in appropriate sections
below.

4.1.1 Event Monitoring Table

New events, occurred within ACS, are displayed in the Event monitoring table. Data in table is
updated in real time mode and can be processed in accordance with job instructions valid in your
company. Table row can contain the following data and controls (table columns can be set to meet your
work tasks, see Customizing Operator Interface):
· Event name;
· Event date and time;
· Information about access card holder (person);
· Name of the object that generated an event;
· Event status indicator (Unprocessed, Acknowledged, Discarded);
· Comment presence indicator;
· Buttons to jump to live and archive video.

Events in the table are distinguished by font color (see Figure 9):
· yellow — event has to be processed by the operator;
· gray — event has been processed by the operator;
· white — other events.

Figure 9. Event color coding

Data in the event monitoring table can be displayed in two modes:

· Auto-refreshing events.
· Viewing events in manual mode.

Auto-refreshing events
In this mode table is focused automatically on the latest received ACS event (with displaying additional
event data on the information panel, if it is opened). When new event is placed into the table, table
automatically focused on this event and table list is scrolled down. To switch auto-refresh event mode
on click on button.

www.issivs.com
 SecurOS ACS 18 User Guide
Working with Module

Viewing events in manual mode

In this mode Monitoring table is focused on the same event entry until you select another one. This
may be helpful when analyzing situation in details, for example, to view additinal event parameters or
view event video. Focus in the Monitoring table is not shifted even when new ACS event is received.
To switch to this mode, click any event entry in the Monitoring table or click on
button.

4.1.2 Unprocessed Event Panel

Events, that must be processed by operator, are listed in the Unprocessed events panel. This allows
operator to quickly respond to the most important events from ACS without searching them in the main
Event monitoring table or applying additional Filters (see Event Filtering). Entries of the unprocessed
events table contains the same data, as Event monitoring table. To view detailed event information, you
can select an event in any panel.

4.1.3 Event Information Panel

Event information panel contains all data and parameters, that can be helpful when analyzing a
problem or for event processing. Depending on the nature of occurred event, set of parameters on the
panel can vary. To view detailed event data click it in the Monitoring table or in the Unprocessed
events table.

Figure 10. Event information panel

The following parameters, common for all events, are displayed on the panel (number on the picture
matches the number in the list):
1. Event name — name of event, received from ACS system;
2. Event time — time when event occurred within ACS system;
3. Event status — Unprocessed, Acknowledged, Rejected or Requires processing. For details
refer to Processing and Commenting Events;
4. Name of the object, that generated event;
5. Markers of this event;
6. Comment and User name, who commented an event;
7. Number of Cameras associated with device.

www.issivs.com
 SecurOS ACS 19 User Guide
Working with Module

For events associated with the passage, additionally the data of the card owner are displayed
(see Figure 11):

Figure 11. Personal information on Event information panel

1. Photo;
2. Set of access cards belonging to person with their date of validity (at the beginning of the list is the
card that was involved in this event);
3. Company, that employes the card owner;
4. Additional data (set of the parameters depends on used ACS system).

When I jump to event associated with passage of the card owner, data concerning this person are not
displayed. Why?

Maybe, the event occurred recently and the system is not currently able to obtain information about the
owner of the card. Return to this event later, or wait. If an event occurred long ago, but card owner data
is still not there, may be it is impossible to receive data from ACS system. Contact your system
administrator to solve this problem.

4.1.4 Event Filtering

To work with predefined set of ACS events (for example, when it is necessary to monitor only alarm
events or events generated by specified set of ACS objects), you can use Event filters. By default, one
can use three pre-installed filters: all events (no restrictions, all events are displayed in the Event
monitoring table), alarms (only events with Alarm marker), events generated by devices (only events
with Hardware event marker). If pre-installed filters are not enough, you can create your own filter
(for details of Filter creation procedure see Customizing Operator Interface).

To filter events select required Filter from the drop-down list in the upper left corner of the ACS: GUI
window (see Figure 12) and events, displayed in the panels of the Monitoring tab, will match its
settings.

www.issivs.com
 SecurOS ACS 20 User Guide
Working with Module

Figure 12. Selecting event filter

If a Map level is activated in a Map: GUI the object filter of this level can appear automatically. This filter
will display all the ACS objects of the activated Map level.

Warning! Described functionality depends on the settings made by the system administrator for the Map: GUI
(see Administration Guide SecurOS, the Map: GUI topic).

4.1.5 Processing and Commenting Events

When configuring system administrator defines which events must be necessarily processed in ACS:
GUI window, which must be automatically acknowledged after specified time period and also events,
that not require additional processing (for details refer to Event Markers).

Events that require processing are placed on the Unprocessed events panel, and also highlighted with
yellow font on the Monitoring and Search tabs.

To process an event, select it on the event table (on Monitoring or Search tab or on Unprocessed Events
panel), then analyze an event and make a decision to acknowledge ( button) or
discard ( button) it. Note that the event status cannot be changed in future.

Figure 13. Event processing panel

Event that has both Alarm and Operator response required will be automatically set to
"Acknowledged" after time period, specified by system administrator, expires.

www.issivs.com
 SecurOS ACS 21 User Guide
Working with Module

Processed events are marked with the gray font and the (Acknowledged) and the (Discarded)
icons. Event status is also displayed on the Event Information Panel and in search result list.

You can comment any event received from ACS Module. This may be helpful for further event
processing, when it must be shown to senior manager or when it is necessary to attract an attention. For
example, in order to export a video clip with the event for long term storage. To write a comment, select
event on the Monitoring or Search tab, type required text string in the Comment panel and click on
on the right of the text field. Commented events are marked with an icon. If you place mouse
pointer over this icon, you can see comment text. If an event has several comments, you can view all of
them on Event Information Panel.

4.2 Searching Events

Sometimes may be a situation, when it is necessary to view events, that have occurred some time ago.
For example, to check if any devices have turned on or through what doors specified person passed.
You can solve these tasks on the Search tab of the ACS: GUI window using the following search
features:
· Searching Events by Device, Marker or Camera.
· Searching Events by Person or Card.

After required events are found, you can work with them in the same way, as on the Monitoring tab
(see Monitoring and Processing Events).

4.2.1 Searching Events by Device, Marker or Camera

This search option can be especially helpful if it is necessary to view events of specific type (for
example, events that have Alarm or Hardware event markers) or events, generated by specific ACS
device.

www.issivs.com
 SecurOS ACS 22 User Guide
Working with Module

Figure 14. Search by Devices or Cameras

To view events generated by specific objects, events having specific markers or events, that have
occurred in field of view of specific Camera do the following:
1. Select the Search by Devices or Cameras on the Search tab.
2. Specify time period in the From and To text boxes.
3. Define search conditions:
· To search events generated by specific Devices, select Device option and tick required objects in the
drop-down list.
· If you need to find events, that occurred in field of view of specific Cameras, select Camera option,
then tick required Cameras in the drop-down list. All events from all devices associated with
specified cameras will be displayed in the search result (how to associate Camera with Device
see Server Part section).
4. Specify event Markers, if you want to find events of specific types or leave this box empty to find all
events. If several Markers are specified, then events that have at least one of them will be displayed
in search results.
5. Click on Search button and work with found events in accordance with your tasks.

www.issivs.com
 SecurOS ACS 23 User Guide
Working with Module

4.2.2 Searching Events by Person or Card

When analyzing low violation events or suspicious situations, occurred within secured area, a necessity
to track person movement or to monitor sites where suspicious access card was applied may be raised.

Figure 15. Search by Name or Card

To view all events, associated with Person or Card within required time period do the following:
1. Select the Search by Person or Card on the Search tab.
2. Specify time period in the From and To text boxes.
3. Define search conditions:
· To search all events associated with specific Person, select the Name option, then select required
person name in the drop-down list. To speed up searching, enter part of the name of the card owner
in the the search text box. Only names that contain entered string, will be displayed in the list.
· To search all events, associated with any card, select the Card option and enter card number (or part
of number). All events, associated with appropriate card numbers will be displayed in the list.
4. Click on Search button and work with found events in accordance with your tasks.

www.issivs.com
 SecurOS ACS 24 User Guide
Working with Module

4.3 Monitoring States and Controlling Devices

Besides processing ACS events, operator can have a task to monitor ACS object states (for example, if
door is opened or if fire alarm sensor is on), and also task to control these objects.

Operator can monitor device states and control them using the following interface objects:
· ACS: GUI window (see Controlling Devices on Devices Tab).
· Media Client (see Controlling Devices from Media Client).
· Map: GUI (see Controlling Devices from Map: GUI).

4.3.1 Controlling Devices on Devices Tab

This tab is intended for monitoring ACS device states, checking unprocessed events and controlling
objects.

Appearance of the tab is presented in Figure 16.

Figure 16. Devices tab

By default, all devices that you can monitor from given ACS: GUI window are listed in the table. You
can sort devices in accordance with your tasks — by device name (sort by default), its state or number
of device's unprocessed events. To sort events in the required way click on required column in table
header.

To send device a command, select entry with required object, then click required command in the
context menu.

www.issivs.com
 SecurOS ACS 25 User Guide
Working with Module

Figure 17. ACS Symmetry device commands

To find any device type its Name (or part of the name) in the Search by Device Name or ID. To
remove all devices from the table, exclude devices with specified states or specified types, select
required parameter from the Filter by Device Type of State drop-down menu.

4.3.2 Controlling Devices from Media Client

You can control ACS device from Camera cell of the Media Client (only if ACS device is associated with
this Camera). To do this right click to call camera cell context menu, then select required device and,
further, required command (see Figure 18).

Figure 18. Controlling ACS devices from Media Client

www.issivs.com
 SecurOS ACS 26 User Guide
Working with Module

4.3.3 Controlling Devices from Map: GUI

ACS devices can be controlled from the Map: GUI, if this possibility is defined by system administrator.
On the Map: GUI all devices are displayed as icons, that specifies device type. Icon caption will contain
the following:
· Object name.
· Current object state.

When any event that requires to be processed occurred, then object icon on the Map: GUI starts
blinking. You can process such events in the ACS: GUI window, see Processing and Commenting
Events.

To send a command to ACS device from Map: GUI, right click on the device icon, then select required
action in the context menu (see Figure 19).

Figure 19. ACS devices on Map: GUI

www.issivs.com
 SecurOS ACS 27 User Guide
Working with Module

4.4 Jump to Event Video

When processing ACS event, it often necessary to view live video from cameras, in field of view of
which this event occured (for example, to ensure that person has applied his access card to the card
reader). In order to analyze a problem, it also could be necessary to view archive video when an event
itself is captured. Depending on the currently used operator interface tool, you can jump to video using
one of the following methods:
· Automatic Jump.
· Jump from Monitoring Tab.
· Jump from Devices Tab.
· Jump from Search Tab.
· Jump from Map: GUI.

4.4.1 Automatic Jump

With certain settings of the operator interface (see Client Part) it is possible to automatically jump to
viewing live video when events with the Alarm marker occur in the system. If this feature is configured
by the administrator, then the video from all Cameras linked with the event source, will be automatically
displayed on the selected Media Client when such event will occur.

Warning! If Media Client's window is hidden under the other windows at the moment of the automatic jump,
then activate it manually to view the video.

4.4.2 Jump from Monitoring Tab

To jump to live video from Cameras, in field of view of which an event occurred, do the following
(see Figure 20):

· Double click on required event in the table, click on (Open live video) button or select the
same command from entry context menu. On Media Client, associated with this ACS window, all
Cameras in live mode will be placed on the All devices View.
· Drag-and-drop an event to the Media Client camera cell. All Cameras, in field of view of which an
event occurred, will be placed on the current View in live mode. Cameras will be placed in cells
ordered from the one that event was drag-and-dropped to.

www.issivs.com
 SecurOS ACS 28 User Guide
Working with Module

Figure 20. Jump to live video

To jump to archive video from Cameras, in field of view of which an event occurred, do the following:

· Click on (Playback event video) button or select the same command from entry context menu
(is called by right click), see Figure 21. On Media Client all Cameras in field of view of which an event
occurred, will be placed on the All devices View. Cameras will be turned to archive mode and
archive pointer will be positioned on the event time stamp.

www.issivs.com
 SecurOS ACS 29 User Guide
Working with Module

Figure 21. Jump to archive video

4.4.3 Jump from Devices Tab

To go to the cameras, the Device is visible for, double click on the device's entry in the table or select
Open live video command from entry context menu (is called by right click). Media Client, associated
with ACS: GUI object window, will display all cameras that monitor given Device. To display such
cameras minimal layout will be used. One can also drag-and-drop device to the Media Client and place it
in any camera cell. In this case all cameras associated with this Device will be shown in Media Client. By
this, currently used View will not be changed.

www.issivs.com
 SecurOS ACS 30 User Guide
Working with Module

Figure 22. Jump to video from Devices tab

4.4.4 Jump from Search Tab

To jump to video from Cameras, in field of view of which an event occurred, do the following:
· Double click on required event in the table, click on Playback event video or select the same
command from entry context menu. All Cameras, in field of view of which this event occurred, will
be placed on the All devices View on the Media Client. Cameras will be turned to archive mode and
archive pointer will be positioned on the event time stamp.
· Drag-and-drop an event to the Media Client camera cell. All Cameras, in field of view of which this
event occurred, will be placed in archive mode on the current View. Archive pointer will be
positioned on the event time stamp. Cameras will be placed in cells ordered from the one that event
was drag-and-dropped to.
· Click on Open live video button or select the same command from context menu. On Media Client,
associated with this ACS window, all Cameras in live mode will be placed on the All devices View.

www.issivs.com
 SecurOS ACS 31 User Guide
Working with Module

Figure 23. Jump to video from Search tab

4.4.5 Jump from Map: GUI

To view video provided by cameras associated with device, drag-and-drop device's icon from Map: GUI
to camera cell of any Media Client, located on the same Desktop (see Figure 24).

Figure 24. Jump to video from Map: GUI

www.issivs.com
 SecurOS ACS 32 User Guide
Working with Module

4.4.6 FAQ

Not all Cameras, in f ield of view of which an event was captured, are displayed on the Media Client.
Why?

Contact your system administrator and check whether you have the access rights to these Cameras, and
whether these cameras were selected to work with this Media Client. Also check whether these Cameras
are associated with ACS device in its settings.

When you drag-and-drop event or device to the Media Client, then Cameras are placed in cell beginning
from that one, where event or device was drag-and-dropped to. Currently used layout of the Media
Client is not changed by this. If there are too many Cameras, associated with this Device, then may be
currently used layout cannot arrange all of them. In this case drag-and-drop event/device to the first
cell of the View or switch to greater layout.

When jumping to event video "No records" message is displayed in the Media Client camera cell. Why?

May be, this Camera did not record video when event occurred. In this case archive record is missing.
Archive also can be deleted if it is expired or archive drives are being cleaned up in "ring mode". If you
jumped to video of event, that occurred not long ago, may be archive file is not loaded to video storage
yet and cannot be played.

4.5 Customizing Operator Interface

Each operator can customize appearance of the ACS Module in accordance to his own preferences. In
addition, the operator can configure the list of events displayed in the Event monitoring table
according to its objectives. For example, events with certain markers or generated by certain objects.

Customizing is performed with the help of the following operations:

· Configuring Event List to Display in Monitoring Table.
· Configuring Windows, Panels and Table Columns.

Configuring Event List to Display in Monitoring Table

When working with large ACS systems or when work objectives are distributed between some
operators, can rise the necessity to view not all events, but only events generated by certain objects or
with certain markers. In this case operator can configure event filter in accordance to his tasks.

To create new filter or edit any of existing, click on button and specify required parameters in
the displayed window (see Figure 25).

www.issivs.com
 SecurOS ACS 33 User Guide
Working with Module

Figure 25. Filter editor

When selecting custom filter in the Monitoring tab all events, received from objects, and have at least
one of the markers specified in the filter, will be displayed.

Configuring Windows, Panels and Table Columns

Depending on performed tasks, different configuration of the windows and panels on the Desktop may
be required to operator.

Event information panel can be detached from the ACS: GUI window and placed in that position of
the desktop, where it will be most convenient to use (see Figure 26). To do this, drag the mouse over the
panel header or click on (Open panel as separate window) button. To integrate panel back to the
ACS: GUI window click on (Dock panel) button or move panel on the panel to its initial location
(see Figure 26).

www.issivs.com
 SecurOS ACS 34 User Guide
Working with Module

Figure 26. Moving Event Information Panel

If displaying of additional information is not required, the panel can be completely hidden with a
button. To reopen the panel, click on button again.

When working with Monitoring tab you can hide or change size of the Unprocessed events panel with
the help of separator ( button, see Figure 27).

Figure 27. Changing size of the Unprocessed events panel

Comment panel can be hidden by clicking on button. It may be especially helpful when working
with window which vertical size in small or when commenting events is not provided by object's
workflow.

When working with event tables or devices, you can hide columns, which data is not required to
display. To do this, right-click on table header and clear checkboxes of the required parameters
(see Figure 28).

www.issivs.com
SecurOS ACS 35 User Guide
Working with Module

Figure 28. Adjusting table columns

www.issivs.com
 SecurOS ACS 36 User Guide
Technical Support Information

5 Technical Support Information

Current section contains service information that is necessary on addressing to Intelligent Security
Systems Technical Support.

Note. Collected data have to be send to the Intelligent Security Systems Technical Support Team (see Getting
Technical Support).

To ensure quick technical support, prepare the following technical information:

Warning! Data in items marked by "*'' are necessary to report.

1. (*) User (customer) name to address to.

2. (*) Organization name.
3. (*) User (or organization) contacts: phone, e-mail.
4. Name of a personal Intelligent Security Systems manager (on Intelligent Security Systems authorized
partner case). Otherwise, give the following data:
· Company where the hardware and software components were purchased.
· Actions proposed to solve the problems announced by a partner from whom the product was
purchased.
5. (*) Problem description.
6. (*) Actions results in the problem.
7. List of changes which result to the problem in case of applying after some changes in system
settings/configuration.
8. System and diagnostic information on computer and SecurOS system configuration obtained from
the SystemInfo utility (see SecurOS Administration Guide for detailed information about utility).
If it is impossible to run the utility provide the following information:
· (*) Guardant keys identifiers and Dallas code;

Note. Equipment Dallas code can be found by the Hardware Report Utility (see SecurOS Administration
Guide for detailed information about utility).

· (*) name and version of the installed Intelligent Security Systems company software.
· total number of video servers and monitoring (operator) workstations in the system;
· operating system (name and service pack version).
9. Another useful information, if possible. For example:
· computer equipment configuration.
· central processors load.
· main and virtual memory used volumes.
· network load.

www.issivs.com
 SecurOS ACS 37 User Guide
Technical Support Information

· network and network neighborhood configuration.

www.issivs.com