USM-Visual Space Manager-ENG
USM-Visual Space Manager-ENG
Spica International
Pot k sejmiscu 33
1231 Ljubljana
Slovenia
E-mail: [email protected]
www.spica.com
Contents I
Table of Contents
3 Main views 21
3.1 Live view
................................................................................................................................... 21
3.1.1 Notifications .......................................................................................................................................................... 23
3.1.1.1 Registration......................................................................................................................................................... 23
3.1.1.2 Alarm ......................................................................................................................................................... 23
3.1.1.3 Toast messages
......................................................................................................................................................... 24
3.1.2 Alarm m anagem ..........................................................................................................................................................
ent 25
3.1.3 Output m anagem ..........................................................................................................................................................
ent 26
3.1.4 Cam era live view
.......................................................................................................................................................... 26
3.2 Alarms
...................................................................................................................................
Overview 27
3.2.1 Alarm details .......................................................................................................................................................... 28
3.2.2 Alarm groups.......................................................................................................................................................... 29
3.2.2.1 Alarm group.........................................................................................................................................................
settings 30
3.3 Alarm/Event
...................................................................................................................................
log 31
3.3.1 View ing recordings
.......................................................................................................................................................... 32
3.4 Project
...................................................................................................................................
Administration 34
3.4.1 Project .......................................................................................................................................................... 35
3.4.1.1 Plan ......................................................................................................................................................... 37
Data points ......................................................................................................................................... 38
Reader data point ................................................................................................................................... 38
Alarm data point................................................................................................................................... 40
Output data point................................................................................................................................... 40
4 Add-ons 43
4.1 Video...................................................................................................................................
surveillance integration 43
4.1.1 Cam era Video..........................................................................................................................................................
Trigger 44
4.1.2 Milestone integration
.......................................................................................................................................................... 45
4.1.2.1 About Milestone
......................................................................................................................................................... 46
Installation ......................................................................................................................................... 47
Example of Milestone .........................................................................................................................................
configuration 48
Add cameras ................................................................................................................................... 49
Set up generic events ................................................................................................................................... 58
Set up recording...................................................................................................................................
rule 60
4.1.3 SeeTec integration
.......................................................................................................................................................... 69
4.1.3.1 About SeeTec......................................................................................................................................................... 70
Installation ......................................................................................................................................... 71
Example of SeeTec .........................................................................................................................................
configuration 72
Add cameras ................................................................................................................................... 73
Set up Netw ork I/O ................................................................................................................................... 76
Create and configure ...................................................................................................................................
alarm scenarios 78
1.1 Introduction
Visual Space Manager (VSM) is an application for a visual survey of events (registrations and
alarms) and management of alarms and doors (outputs) in the Time&Space system. The
application offers live overview of situations which are crucial for every security personnel.
Furthermore, the VSM can be integrated with a video surveillance system, which adds a new
security dimension to Time&Space system.
VSM
This program and accompanying documentation (the software) are copyrighted material,
protected by national legislation and international agreements on protection of intellectual
property. Any unauthorized use or copying of this software is punishable by law. Users are
permitted to make copies of the software solely for backup purposes, and as a protection
against accidental loss or damage of the purchased copy.
By purchasing a copy of the software the user is granted the license to use the software
within the user's organization without time limitations. The user is obliged to comply to the
conditions related to the scope of the license as defined in the purchase documentation
(proposal/order/invoice) at the time of purchase. These conditions are including, but are not
limited to maximum number of users, number of clients, servers, number of administrators,
administrative workstations, computers, locations and similar. Any use beyond these
restrictions is not permitted.
Any use outside user's organization or any commercial exploitation of the software involving
third parties such as lending, renting or selling of the software is not permitted.
Special Terms
Users are obliged to actively protect the software against any unauthorized use or copying,
and prevent access to the software by the public or any third party.
SPICA International does not permit any modification of programs or accompanying
documentation including any modification of the program code or accompanying files.
Warranty Disclaimer
SPICA International has written the software and accompanying documentation with utmost
care and best effort to make it error free. Any eventual error, which would prevent or
significantly hamper the use of the software, should be immediately reported to SPICA
International. SPICA International will act upon such error report with priority and make every
effort to correct the error in the shortest possible time.
However, the software is provided by SPICA International »as-is«, and without any warranty,
express or implied, direct or consequential as to the usability or inability to use the software.
SPICA International does not provide any warranty as to the fitness of this software to any
particular purpose, and is not liable for any errors, known or unknown, of this software.
Cumulative liabilities of SPICA International for any damage caused by this software will be
limited to the purchase price of this software.
Data
SPICA International is not in any way responsible for data maintained with this software. The
user is entirely and solely responsible for data safekeeping, protection against loss and
protection of privacy of personal information.
Modifications of Software
SPICA International continually develops and improves its software products, which are
therefore subject to change without prior notice. SPICA International reserves the right to
freely modify its software products at any time without any prior or special notice and cannot
provide any warranty as to the nature and scope of any particular change. SPICA
International also retains the right to stop further development of a particular product, or to
discontinue a product completely.
In order to meet and surpass the expectations of its users, SPICA International constantly
and systematically collects information about user demands and requirements. This
information plays crucial role in decisions on software product development. Upon user
request, SPICA International will provide information on the status of an individual request or
demand in the context of development planning for the standard products. This information
may include the planned time for the completion of a particular task, if any such time has
been established. Information provided in this way does not make SPICA International in any
way liable for the nature and scope of the actual implementation, licensing policy or time of
delivery. All such information is strictly informal and may change without any notice.
Spica International
Pot k sejmiscu 33
1231 Ljubljana
Slovenia
2.2 Installation
To install the application, start TSSetup.exe (MSSQL) or Setup.exe (Oracle), select VSM
module and follow the installation procedure.
Pre-installation requirements
Important: If using HikVison cameras in the system, also SDK must installed on
workstations along with VSM module. For more information contact Spica's technical support.
Welcom e screen
Installation location
Database type
6. Confirm the installation parameters with Next button and start the installation process.
7. After the installation is completed, see Customizable application parameters chapter for
additional settings.
Server kind - <add key="ServerKind" value="mssql" /> - This parameter defines what
kind of database server (MSSQL/ORACLE) is used in the system.
NLog.config
By default, location of the log files is a sub folder, called Logs in the installation folder (e.g. C:
\Program Files (x86)\Spica\TimeSpace\Visual Space Manager\Logs). Make sure that a current
OS user has read/write permissions for this location.
To set the location or name of the log file, change the following parameters:
To install a new version of the module, simply start and follow the installation procedure.
De-installation
To remove the existing module, got to Control Panel\Programs and Features and select the
Time&Space Visual Space Manager software and choose Uninstall.
2.3 Login
To be able to login in VSM, you need to have a user account with Visual Space Manager Login
permission, given by the Time&Space Manager administrator (for more information see
Time&Space Manager User’s Manual).
Login dialogue
Communication,
Events,
Event groups,
Interface,
Video Surveillance.
File m enu
Note: These settings are related to a specific workstation and not to a project.
2.4.1 Communication
Spica Communication
In order to get notifications about events from Event Collector the communication with Spica
Communication service must be established.
Host - Enter the name or IP of the computer with Spica Messaging Service in the Host field.
Port - Enter the port number used by Spica Messaging Service (by default it is set to 4444)
in the Port field.
Try to reconnect - Specify if the connection is to be re-established automatically after
failure.
Keep alive - This option specifies whether NOOP (short for NO Operation) packets should
be send to the host. This command is used to ensure that the connection is always alive.
Enable communication - Check this field to enable collaboration.
Spica API
In order to get notifications about events and send request to Device Administration Portal
the communication with Spica API must be established.
Address - Enter the name or IP of the computer with Space API and the port number used
by the module in the address field. By default this parameter is set to https://
localhost:1600.
Enable communication - Check this field to enable collaboration.
Note: Space API address should be set if Device Administration Portal is used in the
system.
EC API
In order to send request to Event Collector the communication with EC API must be
established.
Host - Enter the name or IP of the computer with EC API in the Host field.
Port - Enter the port number used by EC API (by default it is set to 2222) in the Port field.
Time out - This parameter tells the application how long to wait for the Central Control
System response after sending data that require the confirmation. If the system does not
respond in the specified time, the operator will get a message.
Note: See Event Collector User's manual for more information about EC API.
2.4.2 Events
Event History
With databases containing several thousands of records, the filtering of data can be time-
consuming. Field Limit history of notification dialogue to allows you to specify the time span
of active history on the notification dialogue. If the limitation is set to (e.g. 7 days), the user
will be able to browse through events that happened maximum 7 days ago.
Other
Show only access events - If you want to skip showing time&attendance events on the
notification dialogues, select this option.
Show only events with data points - If you want live view show only messages from
defined data points, select this option. In other case, all messages (readers, alarms) will be
shown.
Events settings
Alarm groups
Section Alarm groups contains a list of alarm groups that are defined in the Time&Space. For
better visualization, every alarm group can have individual settings for sound and graphic
representation. Use the ... button to load desired sound (wave format) for a specific alarm
group and/or open combo to set colouring of notification message.
To automatically close Event notification window after some time, you have to check the field
Close after and set desired value.
Event groups
Event groups are predefined (Accepted and Rejected) and have the same settings as alarm
groups.
2.4.4 Interface
Common
Use tabbed interface - If option is enabled, plans are shown as tabs on the Live view.
Remember filters - If option is enabled, filter selection is remembered on the views after
the application is restarted.
Language
Select appropriate application language option from the combo box. Currently the following
languages are available:
Arabic (ar),
Bosnian (sr-Cyrl-BA),
Bulgarian (bg),
Croatian (hr),
English (en-GB),
Finnish (fi),
French (fr),
German (de),
Greek (el),
Italian (it),
Lithuanian (lt),
Macedonian (mk),
Polish (pl),
Portuguese (pt),
Romanian (ro),
Russian (ru),
Slovenian (sl),
Turkish (tr),
Ukrainian (uk).
Interface settings
Server parameters:
Camera name - Select the camera that will perform recording from Milestone database.
Port - The port number is set to 1234 (the same number as event port on Milestone side)
to which trigger signal will be sent.
Triggering Expression - The expression which is set to start recording.
Reader/alarm name - Add readers/alarms from Time&Space that will serve as inputs for
the trigger.
Reader triggers
Alarm triggers
Camera name - Select the camera that will perform recording from SeeTec database.
Port - Enter the port number (the same number as digital input on SeeTec side) to which
trigger signal will be sent.
Reader/alarm name - Add readers/alarms from Time&Space that will serve as inputs for
the trigger.
Reader triggers
Alarm triggers
3 Main views
The application has four main views:
Live view - This view is used for visual survey of event notifications, management of
outputs/alarms, live camera view and replaying of recordings.
Alarms Overview - This view is used for the management of alarms.
Alarm/Event log - This view is used for the preview of registration/alarm events and
corresponding videos.
Project Administration - Used for the configuration of project and plan parameters.
Audio - Global setting for enabling/disabling sound effects when registration or alarm
appears.
Visual - Global setting for enabling/disabling visual notification when registration or alarm
appears.
Layout - Arrange open maps in a desired format.
Live view
Note: Restriction by area is applied on this view. This means that a user will see only
notification from the location, he/she is entitled to.
Special section of the view shows live event monitoring for the following events in the
system:
3.1.1 Notifications
3.1.1.1 Registration
Event window shows all relevant information for a specific reader data point. In order to
show this window global property Visual and property Show pop-ups of the selected point
must be checked. Event window will automatically pop-up when an event is detected, or, if
you double click on the data point.
Event window shows information of the last detected event. You can also browse past
events (time range is set in Global settings) on the selected point. Use button to jump to
the first event, buttons and are used to move to the next or previous event. Button
jumps to the last event. If an event on the selected observation point is detected while
browsing, it will pop up. To locate the point to which the event window belongs, use
button. Video replay button is available for an event on the dialogue, if integration with
video surveillance system and recording trigger is set up for a specific reader. Show picture
button is available on the dialogue, if capture picture option is enabled on the terminal.
Registration notification
3.1.1.2 Alarm
Event window shows all relevant information for a specific alarm data point. In order to show
this window global property Visual and property Show pop-ups of the selected point must be
checked. Event window will automatically pop-up when an event is detected, or, if you double
click on the data point.
Event window shows information of the last detected event. You can also browse past
events (time range is set in Global settings) on the selected point. Use button to jump to
the first event, buttons and are used to move to the next or previous event. Button
jumps to the last event. If an event on the selected observation point is detected while
browsing, it will pop up. To locate the point to which the event window belongs, use
button. Video replay button is available for an alarm on the dialogue, if integration with
video surveillance system and recording trigger is set up for a specific alarm. Show picture
button is available for an event on the dialogue, if capture picture on alarm option is enabled
on the terminal.
If the user has appropriate permissions and alarm status is correct, than Acknowledge and
Deactivate actions are enabled.
Alarm notification
Toast m essages
Acknowledge - This option is used only with alarms that are pre-set to be deactivated
automatically. The operator's confirmation does not affect the state of the alarm.
Acknowledge All - This action confirms all alarms, that need confirmation.
Deactivate - An alarm is activated automatically upon the emergence of alarm state on the
terminal. In order to change alarm state to normal, it must be deactivated.
Area - Area tree is used for the classification of controllers (alarms according to some
natural criteria (e.g. geographical location) in Event Collector Manager.
Priority - All priorities, Greater or equal x, where x represents the number of priority (0 is
the highest priority).
Status - All, Enabled alarms and Activated alarms.
Alarm s tab
Open relay - Action temporary opens output by releasing the electrical lock in the
controller. The output remains open only a few seconds.
Open - Action opens the output. The output remains open until the operator returns it into
normal state.
Lock - Action locks the output. The output remains locked until the operator returns it into
normal state.
Normal - Action returns the output into normal state.
Area - Area tree is used for the classification of controllers (alarms according to some
natural criteria (e.g. geographical location) in Event Collector Manager).
Name - Enter the name of the output to perform the search.
Status - All Outputs, Open Outputs, Closed Enabled and Normal Outputs.
Outputs tab
Note: Layout view options do not apply for live camera dialogues.
Enable/Disable alarm - Keep in mind that data on the view is refreshed each time the
alarm's state is changed.
Deactivate - Deactivates the alarm, if triggered.
Show Details - Open alarm's details dialogue.
Print Preview - To generate a report about alarms, choose Print Preview button.
Alarm Groups - Open alarm group manager dialogue.
Area - Area tree is used for the classification of controllers (alarms according to some
natural criteria (e.g. geographical location) in Event Collector Manager).
Group - A group holds the definitions how alarms are processed in the system and are set
in the Event Collector Manager
Status - All, Enabled alarms and Activated alarms. Enabled alarms are coloured green, while
Active alarms are red.
Priority - All priorities, Greater or equal x, where x represents the number of priority (0 is
the highest priority).
Note: The user must have appropriate role permissions to see this view.
Alarm details
Note: Alarm group assigned to a specific alarm cannot be deleted from the system.
General tab
Enable alarm e-mail notifications - By selecting this option alarm email notification is
enabled in Time&Space system.
Sender - Enter the sender's email address of alarm notification emails.
Recipients - Enter the recipients' email addresses of alarm notification emails.
Notification tab
(Event/Alarms), Period, Area, User, Reader, Alarm group, Controller or use the search
field at the top.
Furthermore you can preview recordings made with video surveillance system, if event has
icon in the Recording column. A double click on a specific event which holds recording,
shows a player dialogue. Show picture button is available for an event, if capture picture
on registration option is enabled on the terminal.
The following screen means that recording has been triggered, but the video or specific frame
is not available for replay.
3.4.1 Project
Project is the main entity in VSM module and consists of information about individual plans
and project data points. To open the existing project, select the Open project button from
the ribbon or use a short cut from the File menu, called Recent projects.
If creating a new project, select the New project action from the ribbon. A new dialogue
Add new project will appear, where project name is entered.
Existing project can be renamed with Rename project action from the ribbon.
To delete the existing project select the Delete project from the ribbon.
3.4.1.1 Plan
Plan is a graphical presentation of a specific area and/or floor in the building containing
various plan data points. When the project data point is inserted to a specific plan, it's called
plan data point. The same project data point can be used on the several plans within the
same project.
To add a new plan, select the Add plan button from the ribbon. A new dialogue, called Add
new plan will appear where name, image and plan data points for the map are defined.
To adjust the selected image you can use the following action:
To insert the existing project data points in the opened plan, use Insert option or use Add
option to create project data point and insert plan data point in the same step. There are five
types of plan data points available:
When the configuration of plan is finished, save settings with Save plan action.
Data point, type Reader is connected with a specific reader from the Time&Space system. The
following parameters can be set on the Reader tab:
Icon - Icon represents reader on the map and can be changed if needed by clicking on the
icon button.
Name - Name of the point.
Reader - Select appropriate reader from the list of readers.
Play sound - To enable/disable sound alert when an event has been detected, use Play
sound check box. Global setting Audio can override this setting.
Focus data point - Application can locate and show the point where an event has been
detected. This function can be enabled/disabled by checking Focus data point option.
Pop-up notification - To enable the detection of events on the selected point, check the
field Pop-up notification. Global setting Visual can override this setting.
Trigger live view - If selected, camera live view will be shown when an event happens on
the reader.
Show picture - If selected, picture dialogue will be shown when the event happens on the
reader.
If you want to limit the notifications on a specific point to individual group of users, use
Limitations tab and set up restrictions by Organization hierarchy and/or Unit 1, Unit 2, Unit
3.
Data point, type Alarm is connected with a specific alarm from the Time&Space system. The
following parameters can be set on the Alarm tab:
Icon - Icon represents the alarm on the map and can be changed if needed by clicking on
the icon button.
Name - Name of the alarm point.
Alarm - Select appropriate alarm from the list of alarms.
Play sound - To enable/disable sound alert when an alarm has been detected, use Play
sound check box. Global setting Audio can override this setting..
Focus data point - Application can locate and show the point where an alarm has been
detected. This function can be enabled/disabled by checking Focus data point option.
Pop-up notification - To enable the detection of events on the selected point, check field
Pop-up notification. Global setting Visual can override this setting.
Trigger live view - If selected, camera live view will be shown when an event happens on
the reader.
Show picture - If selected, picture dialogue will be shown when the alarm happens on the
terminal.
Data point, type Output is connected with a specific output from the Time&Space system. The
following parameters can be set:
Icon - Icon represents the output on the map and can be changed if needed by clicking on
the icon button.
Data point, type Combined can be connected with the existing project data points (type
reader, alarm, output or camera). This way one point on the map represents several data
points. The following parameters can be set:
Icon - Icon represents the combined point on the map and can be changed if needed by
clicking on the icon button.
Name - Name of the combined point.
Insert data point - Insert data point to the project and add it to the combined point.
Add data point - Add existing project data point to the combined point.
Delete - Remove the selected data point from the list.
Data point, type Camera is connected with a specific camera from the video surveillance
system. The following parameters can be set:
Icon - Icon represents camera on the map and can be changed if needed by clicking on the
icon button.
Name - Name of the camera point.
Camera - Select appropriate camera from the list.
When camera data point is added to the project, a live view of the camera can be displayed
in Live view.
Note: The list of available cameras corresponds to the configured cameras in video
surveillance settings.
Important: If using HikVison cameras in the system, also SeeTec SDK must installed on
workstations along with VSM module. For more information contact Spica's technical support.
4 Add-ons
To implement the integration with Milestone or SeeTec, the following components must be
installed and configured:
Installation
CameraVideoTriggerService.exe.config
NLog.config
The Local Service user must have write permission in the directory, where log files will be
created.
Milestone
See chapter Example of Milestone configuration for more details on how to configure the
system.
4.1.2.1.1 Installation
To configure Milestone system, to be ready for integration, you need to perform the following
steps:
Note: This example covers the most important parts of configuration for Milestone
Essential+, for other details check Milestone documentation.
1. Navigate to Servers\Recording Servers and select the default server on the list. Right-
click on the server and select Add hardware... option.
Note: In the case of older cameras, you should download and install the Legacy driver
pack.
2. Select one of the available options and proceed with the Next button. This example covers
the Manual option.
3. Specify user name and password if devices are not using the default ones.
6. If camera parameters are correctly set and the camera is on-line, the status is updated to
Success.
7. Change the available options if necessary otherwise proceed to the next step.
8. Select the appropriate camera group from the list and finish the process with the Finish
button.
9. Open camera properties and navigate to Motion tab and disable Motion detection option.
2. Go to Rules and Events and select Generic Events sub-view. Right-click on the view and
select Add New... option. Enter the expression which will be used to trigger the recording on
the specific camera.
1. Go to Rules and Events and select Rules sub-view. Right-click on the view and select Add
Rule... option.
2. Enter the desired name and select option Perform an action on {event}.
3. Click event link in the lower section and select the appropriate generic event from the list.
Generic events
4. Change the available options if necessary otherwise proceed to the next step.
5. Select Start recording on {devices} option and define recording devices by selecting
recording devices link the lower section.
Further on, select the immediately link and enter the value for pre-buffer with - sign.
Note: To use the pre-buffer recording function in the rule, you must enable pre-buffering
on the device being recorded and you must set the pre-buffer length to at least the same
length as specified in the rule.
6. Select Perform stop action after {time} option and define the length of recording by
selecting time link the lower section.
Exem plary architecture overview w ith distributed server functionality and Internet connection
See chapter Example of SeeTec configuration for more details on how to configure the
system.
4.1.3.1.1 Installation
To configure SeeTec system, to be ready for integration, you need to perform the following
steps:
Note: This example covers the most important parts of configuration, for other details
see SeeTec User's Guide.
1. Add a new camera in Configuration Mode by using the Hardware dialogue. Enter the Name,
select appropriate manufacturer and type and enter IP address of the camera.
Note: The list of all supported cameras can be found in document, named SeeTec
Supported Devices.
2. If camera is password protected, enter the appropriate Username and Password to make
camera accessible.
3. Make sure that the Alarm recording option is activated, parameters can be changed to suit
the specific situation.
2. Add one or more inputs, depending on the number of cameras. Change name, port, and
dead time. Ports used in digital inputs must correspond to the ports used in recording
triggers.
Sam ple TCP alarm port for SeeTec Netw ork I/O
Note: The port must be unique, i.e. every camera requires a free TCP port. It is
recommended to use a port number between 10000 and 20000 since they are not used by
other programs in most cases.
1. Create a new alarm scenario (in Configuration Mode by using the Alarm scenarios option)
and select General.
2. Change to the Start menu option and choose the start event by clicking on the Edit button.
The alarm will be triggered by the camera’s TCP signal. Select the input you created for the
SeeTec Network I/O as the start trigger by using the Edit button.
3. In the End dialogue, specify the recording duration in the Maximum server alarm duration
(s) field. The predefined recording time is 30 seconds.
4. In the Server actions area, specify the Pre-alarm duration for camera recording (s). By
using the Edit button, you can enable alarm recording for the camera. You can also start the
alarm recording with multiple cameras.
5. In the Client dialogue you can specify the user(s) that is/are expected to react in case of
alarm, i.e. the user(s) who may see and edit the alarm. In this example, only the
"administrator" user is entitled to see the alarm. The user was added using the Edit button.