Mass 3.21 User Guide

MAGOS AREA
SURVEILLANCE
SOFTWARE (MASS)
V.3.21
User Guide
TABLE OF CONTENTS
SUMMARY OF CHANGES ..................................................................................... VII
V3.1 July 2019 ....................................................................................................................... vii
V3.20 January 2020 ............................................................................................................... vii
V3.21 JUNE 2020 .................................................................................................................. vii
1. INTRODUCTION TO THIS GUIDE .................................................................... 8
1.1 Document Layout ....................................................................................................... 8
1.2 About Magos Systems ............................................................................................... 8
1.3 Referenced Documents ............................................................................................. 9
2. INSTALLING MASS ....................................................................................... 10
2.1 System Overview ....................................................................................................... 10
2.2 Installation Prerequisites ............................................................................................ 10
2.3 MASS Internal Permissions........................................................................................ 13
2.4 the Installation Process .............................................................................................. 13
3. GETTING STARTED ...................................................................................... 21
3.1 Launching the Application .......................................................................................... 21
3.2 Setup A Map View...................................................................................................... 21
3.3 Setting Up Sensors .................................................................................................... 23
3.4 Additional Steps ......................................................................................................... 35
4. MAP VIEW GENERAL OPERATIONS ............................................................... 36
4.1 Layers ........................................................................................................................ 36
Page i © Copyright 2017, Magos Systems. All Rights Reserved

4.2 Map Display Options .................................................................................................. 39
4.3 Measurement tool ...................................................................................................... 40
4.4 Adding and Removing User-defined Presets ............................................................. 42
4.5 Miscellaneous ............................................................................................................ 43
4.6 System Health Panel.................................................................................................. 45
4.7 Keyboard Shortcuts .................................................................................................... 47
5. RADAR SENSOR ADVANCED SETTINGS ........................................................ 48
5.1 Radar Operation BackGround .................................................................................... 48
5.2 Adjusting Radar Specific Properties ........................................................................... 48
5.3 Threshold Schemes ................................................................................................... 50
5.4 Adjusting Tracker Parameters .................................................................................... 51
5.5 Adjusting Track Merging Parameters ......................................................................... 52
5.6 Fine Tuning radar Positions ....................................................................................... 53
6. CAMERA SENSOR ADVANCED SETTINGS ...................................................... 56
6.1 Camera Operation BackGround ................................................................................. 56
6.2 Adjusting Camera Behavior Properties ...................................................................... 57
6.3 Fine Tuning Camera Position and View ..................................................................... 59
7. PROFILES AND ZONES ................................................................................. 64
7.1 Zones Logic................................................................................................................ 64
7.2 Creating a Profile ....................................................................................................... 65
7.3 Defining and Editing and testing Alarm Zones ........................................................... 67
7.4 Defining and Editing Coverage Zones ........................................................................ 72
7.5 Profile Scheduler ........................................................................................................ 73
8. MAP VIEW ADVANCED SETTINGS.................................................................. 78
Page ii © Copyright 2017, Magos Systems. All Rights Reserved

8.1 Enabling Map Caching ............................................................................................... 78
8.2 Height Units................................................................................................................ 79
8.3 Overlay ....................................................................................................................... 79
9. CONFIGURATIONS SETTINGS ....................................................................... 80
9.1 System Backup and Info ............................................................................................ 80
9.2 General ...................................................................................................................... 81
9.3 UI Settings.................................................................................................................. 82
9.4 Plugins ....................................................................................................................... 84
9.5 User Management...................................................................................................... 84
10. MASS+AI ..................................................................................................... 87
10.1 MASS+AI system Overview ....................................................................................... 87
10.2 Target Classification Process ..................................................................................... 89
10.3 Target Classes and Sub-Classes ............................................................................... 89
10.4 Target Class Display .................................................................................................. 89
10.5 AI Appliance Configuration ......................................................................................... 90
10.6 MASS+AI Zones ........................................................................................................ 91
11. GPS SENSOR ............................................................................................... 93
11.1 GPS Gateway Server ................................................................................................. 93
11.2 Magos GPS Tracker Application ................................................................................ 93
11.3 GPS Sensor Plugin in MASS Server .......................................................................... 95
12. GLOSSARY .................................................................................................. 98
13. INDEX .......................................................................................................... 99
Page iii © Copyright 2017, Magos Systems. All Rights Reserved

TABLE OF FIGURES
Figure 1: Installation Security Warning ........................................................................................ 14

Figure 2: The Custom Setup window .......................................................................................... 15
Figure 3: Shortcut for the MASS service manager application .................................................... 16
Figure 4: Service Manager Application Menu.............................................................................. 16
Figure 5: MASS Registration and Activation web page ............................................................... 17
Figure 6: License Request successfully sent confirmation .......................................................... 18
Figure 7: Error sending license request message ....................................................................... 19
Figure 8: The Upload License form ............................................................................................. 19
Figure 9: License uploaded successfully ..................................................................................... 20
Figure 10: The Display Map Options menu ................................................................................. 22
Figure 11: The Fit to screen/Home option ................................................................................... 23
Figure 12: The Settings bar – Adding a Radar Sensor................................................................ 24
Figure 13: Edit Mode for adding and editing a Sensor ................................................................ 25
Figure 14: New Sensor List ......................................................................................................... 25
Figure 15: General Sensor Details Tab ....................................................................................... 26
Figure 16: Sensor Location Tab .................................................................................................. 27
Figure 17: Edit Mode Summary Window ..................................................................................... 27
Figure 18: Edit Mode Summary Window ..................................................................................... 28
Figure 19: Targets and Target History display ............................................................................ 29
Figure 20: Target Display with Target info................................................................................... 29
Figure 21: The Settings bar – Adding a Camera Sensor ............................................................. 30
Figure 22: Edit Mode for adding and editing a Camera Sensor................................................... 30
Figure 23: General Camera Sensor Details Tab ......................................................................... 31
Figure 24: Camera Model Info..................................................................................................... 32
Figure 25: Camera Sensor Location Tab .................................................................................... 32
Figure 26: Camera Edit Mode Map View – Setting Rotation Angle ............................................. 33
Figure 27: Camera Edit Mode Summary Window ....................................................................... 33
Figure 28: Camera Info ............................................................................................................... 34
Figure 29: Layers Menu .............................................................................................................. 36
Figure 30: Radar Coverage Diagram .......................................................................................... 37
Figure 31: External Intervention on Camera................................................................................ 38
Figure 32: Alarm Zones on the map view .................................................................................... 38
Page iv © Copyright 2017, Magos Systems. All Rights Reserved

Figure 33: Opacity and Map Color Setting .................................................................................. 39
Figure 34: MASS ruler tool display .............................................................................................. 40
Figure 35: Measurement Window – Initial Stage ......................................................................... 40
Figure 36: Measurement – First point added............................................................................... 41
Figure 37: Measurement after 2 points ....................................................................................... 41
Figure 38: Measured area and Summary ................................................................................... 41
Figure 39: Measurement Summary Window ............................................................................... 42
Figure 40: The Add Preset option ............................................................................................... 43
Figure 41: The Presets section with a newly created preset ....................................................... 43
Figure 42: USER Menu ............................................................................................................... 44
Figure 43: Cursor Position .......................................................................................................... 45
Figure 44: System Health Notification ..................................................................................... 45
Figure 45: System Health Panel Window .................................................................................... 46
Figure 46: System Health Collapsed Notification ................................................................... 46
Figure 47: Radar Sensor Properties............................................................................................ 49
Figure 48: System Configuration Window ................................................................................... 51
Figure 49: Track Merging Configuration ...................................................................................... 53
Figure 50 Fine tuning radar heading and position ....................................................................... 54
Figure 51: System Configuration Window ................................................................................... 58
Figure 52 - Camera Location Wizard .......................................................................................... 60
Figure 53 – Reference Point List for Validation Stage ................................................................. 61
Figure 54 – Adding DTM vertex .................................................................................................. 62
Figure 55 – DTM Editing Menu ................................................................................................... 62
Figure 56 – DTM Vertex Info ....................................................................................................... 62
Figure 57 – Add Profile Window .................................................................................................. 66
Figure 58 – Profile Menu ............................................................................................................. 66
Figure 59: Edit Zone side menu .................................................................................................. 67
Figure 60: Drawing a new zone................................................................................................... 68
Figure 61: Polygon Drawing Auxiliary menu................................................................................ 68
Figure 62: Zone Properties Menu................................................................................................ 69
Figure 63: ALARM ZONES list menu .......................................................................................... 70
Figure 64: Edit Polygons mode ................................................................................................... 70
Figure 65: Polygon Edit auxiliary menu ....................................................................................... 71
Figure 66: Polygon Delete auxiliary menu ................................................................................... 71
Figure 67: Zone Info Panel .......................................................................................................... 72
Figure 68: Coverage Zone Properties Menu ............................................................................... 72
Figure 69: Profile Scheduler configuration page ................................................................... 74
Page v © Copyright 2017, Magos Systems. All Rights Reserved

Figure 70: Scheduler Display Scope Control Bar ................................................................... 74
Figure 71: New Calendar Pop-Up window............................................................................... 74
Figure 72: Calendar List ........................................................................................................... 75
Figure 73: Calendar Edit Sub-Menu ......................................................................................... 75
Figure 74: Profile Scheduler Edit Event Menu ........................................................................ 76
Figure 75: Map source menu ...................................................................................................... 78
Figure 76: MASS local cache progress bar ................................................................................. 78
Figure 77: change Height Units ................................................................................................... 79
Figure 78: System Configuration Page ....................................................................................... 80
Figure 79: System Info Page ....................................................................................................... 81
Figure 80: Web Server Configurations Section ........................................................................... 81
Figure 81: Coverage Zone Properties Menu ............................................................................... 82
Figure 82: General UI Configuration Section............................................................................... 83
Figure 83: Target Options Configuration Section ........................................................................ 83
Figure 84: Add/Remove Plugin Menu ......................................................................................... 84
Figure 85: User Manager page ................................................................................................... 85
Figure 86: Edit User Details menu .............................................................................................. 85
Figure 87: MASS+AI system configuration example ................................................................... 88
Figure 88: Example of a classified Person track representation in the map view ........................ 90
Figure 89: Add/Edit Appliance window ........................................................................................ 91
Figure 90: Edit Alarm Zone menu in AI Enabled MASS .............................................................. 92
Figure 91: Magos GPS APP Settings Screen .......................................................................... 94
Figure 92: Magos GPS APP Main Screen ................................................................................ 94
Figure 93: GPS Manager Plugin Configuration ...................................................................... 95
Figure 94: Add GPS Sensor Menu ........................................................................................... 96
Figure 95: GPS SENSORS List with authorized device ......................................................... 96
Figure 96: GPS Sensor info ...................................................................................................... 96
Figure 97: GPS Sensor Edit Menu ........................................................................................... 96
Figure 98: GPS Tracking Configuration Menu ........................................................................ 97
Figure 99: “Friendly” Target Display in MASS map View ...................................................... 97
Page vi © Copyright 2017, Magos Systems. All Rights Reserved

SUMMARY OF CHANGES
This section lists the changes and updates that have been made to the document since May
2019 (MASS 3.0)
V3.1 JULY 2019
• Added MASS service manager documentation and revised installation procedure in section 2.4
• Added Profile Scheduler feature documentation in section 7.5.
• Added User Management feature documentation in section 9.5
• Added AI documentation in chapter 10
• Added system configuration backup in section in section 9.1
V3.20 JANUARY 2020
• Revised Zones Logic, removed "view zone", added documentation of alarm zone testing and
documented system default profile setting in Sections 7
• Added Language Selection and Cursor Coordinates documentation in section 4.5
• Revised Plugin page see section 9.4
• Added new threshold schemes and full documentation per model in section 5.3
• Refreshed Sensor Edit mode figures, and added Clear DTM option documentation in section 3.3.
• Added Track Merging Documentation in section 5.5
• Refreshed System configuration documentation to include new UI page and https options in
chapter 9.
V3.21 JUNE 2020
• System Health Dashboard – showing critical error messages. Covered in section 4.6.
• GPS Sensors – allowing “Blue-Force” automatic classification within MASS based on GPS position
reported by devices carried by friendly targets. Covered in section 11.
Page vii © Copyright 2017, Magos Systems. All Rights Reserved

1. INTRODUCTION TO THIS GUIDE
This guide is designed to aid users in the installation and operation of MASS (Magos Area
Surveillance System). MASS is a multi-feature command and control software, developed and
designed for use with Magos radar sensors and third party cameras and VMS.
This guide is intended for both MASS administrators and users.
This guide refers to MASS software version 3.0.
1.1 DOCUMENT LAYOUT
This guide is designed for all level of users. For quick installation and setup refer to Chapters 2 &
3, respectively. These cover the minimum operations required for setting up a new MASS
installation in a new site.
Chapter 4 covers MASS operation once the setup stage is complete.
The rest of the chapters contain detailed description of site-setup procedure and MASS
capabilities.
1.2 ABOUT MAGOS SYSTEMS
Magos was established in 2007 to realize its co-founders' vision of bringing advanced radar
technology to the security and perimeter protection and detection market. We are experts in low
cost, low power consumption, high performance radars that can be easily integrated with existing
VMS, PSIM and other control software and automatic PTZ slew-to-cue for an end-to-end cost
effective and easily maintained solution of the customer’s security requirements.
1.2.1 CONTACTING MAGOS SYSTEMS

Please contact us through the following channels:
Medium Details
Email support@magosys.com
Mail Gad Feinstein 13 Office 225,
Rehovot
Israel
7638517
Website www.magosys.com
1.2.2 CONTACTING MAGOS SUPPORT

Support is available to customers who have a trial version of a Magos product or who have
purchased a Magos product and have a valid maintenance contract.
To contact Magos support, send an email to support@magosys.com.
Page 8 © Copyright 2017, Magos Systems. All Rights Reserved

1.3 REFERENCED DOCUMENTS
Additional information on operation and installation of MAGOS radar sensors, including the online
license activation manual may be found on Magos' user manuals page:
• https://partners.magosys.com/portal/downloads/
In addition, various actions required for proper integration of the MASS with 3rd party VMS/PSIM
software are documented in version specific integration manuals. These can be found in the
above link. For a full and updated list of supported 3rd party integrations please refer to the online
"Knowledge Base" at https://partners.magosys.com/portal/wiki

2. INSTALLING MASS
MASS has two components: Server side and client side. This chapter provides a system
overview, specifies the measures needed for enabling installation, namely installation
prerequisites and required permissions, and provides instructions for the installation process.
2.1 SYSTEM OVERVIEW
MASS server is a web based “Server-Client” system. The server-side software is typically
installed on a server/computer that is active 24/7 and can be accessed via Ethernet/LAN by
potential clients. Client software is a browser (typically Chrome) which can run anywhere on the
same network. The browser may be used on the server computer as well.
MASS client side application shows a bird's eye view of the protected area, thereby enabling you
to set up, configure, and monitor all installed sensors and their output.
MASS is a capable command and control software suite which allows real-time event
management. When integrated with a 3rd party VMS engine, events can be logged and replayed
in sync with relevant video streams.
For further details about related software and sensors, see section 1.3, Referenced Documents.
2.1.1 SERVER SIDE

The server side is designed to run on a designated PC at the command and control center of the
protected site. Server-side software is a prerequisite for operating the system.
The software is designed so that server side typically requires one-time configuration on
installation. Once the software installation process is complete and all sensors are connected to
the server side, the rest of the set up process is done from the client via a browser.
2.1.2 CLIENT SIDE

The MASS client side offers a user-friendly and intuitive interface for viewing, managing, and
controlling the various sensors installed.
The client side supports:
• Adding and editing sensors and their features and location.
• Viewing radar sensors' output. The cameras' video output is usually displayed on a VMS
• Manually pointing cameras at desired locations in the protected area.
• Creating and managing zones.
• Activating integrations to 3rd party VMS / PSIM.
2.2 INSTALLATION PREREQUISITES
Before starting the installation of MASS, ensure that your sensors are supported by MASS and
that your system meets the system requirements, as specified in the following sections.

2.2.1 SUPPORTED SENSORS
MASS currently supports the following sensors:
• SR250F – MSA1452A
• SR500F – MS700A
• SR1000F – MSA1231A
• SR500-I – MS964A
• SR1000-I – MSA1251A
• Scepter-C – MSA1241A
• Any ONVIF profile S camera that supports the Absolute Move command
The SR radar sensors and ONVIF cameras are considered “native” to MASS and are referred to
as “sensors” in this manual.
NOTE
Contact Magos support or visit the partners portal for an updated list of supported
Camera models. In case a new model is required and it supports the above
requirements contact Magos Support to add to the supported model list.
2.2.2 SYSTEM REQUIREMENTS

This section specifies the system requirements on both the server and client sides.
2.2.2.1 Server side
Installing MASS on the server side requires:
Name Description
CPU Intel® Core™ i3 or better

RAM 8 GB or more
Network Ethernet 100 Mbit or better
Hard Disk 10 GB or more free space
Operating Microsoft® Windows® 7 Home (64 bit) English
System
Microsoft® Windows® 7 Pro (64 bit) English

Microsoft® Windows® 8.1 Pro (64 bit) English
Microsoft® Windows® 8.1 Enterprise (64 bit) English
Microsoft® Windows® 10 Pro (64 bit) English
Microsoft® Windows® 10 Enterprise (64 bit) English
Microsoft® Windows® Server 2012 (64 bit): Standard and
Datacenter English
Microsoft® Windows® Server 2012 R2 (64 bit): Standard and

Datacenter English
Microsoft® Windows® Server 2016 (64 bit): Essentials, Standard
and Datacenter English
2.2.2.2 Client side
Mass client side requirements are:
Name Description
CPU
Intel® Core™ i3 or better
RAM 4 GB or more
Network Ethernet 100 Mbit or better
Graphics Onboard GFX, AGP or PCI-Express, minimum 1024 x 768 (1280 x 1024
Adapter recommended), 16-bit color or better2
Hard Disk 1 GB or more free

Space
Operating Microsoft® Windows® 7 Home (64 bit)
System
Microsoft® Windows® 7 Pro (64 bit)
Microsoft® Windows® 8.1 Pro (64 bit)
Microsoft® Windows® 8.1 Enterprise (64 bit)
Microsoft® Windows® 10 Pro (64 bit)
Microsoft® Windows® 10 Enterprise (64 bit)
Software Internet Explorer 11 , Google chrome 42 or above, Edge 42 or above
2.2.3 LICENSE
As a customer of Magos Systems a username and password for accessing the Magos Partner
Portal should be assigned to you by the Magos Support team.
It is recommended to login to the Partner Portal, browse to the license management page and
verify that you have an issued license ready for validation.
If you cannot access your account or your account does not include issued licenses contact your
local sales representative or the Magos Support team.

2.3 MASS INTERNAL PERMISSIONS
MASS has several defined permission levels. This section specifies these permissions, as well as
the tasks that require Magos administrator privileges and the methods for setting and editing a
password.
2.3.1 MAGOS PERMISSION LEVELS

MASS allows logging in and operating with either of the following permission levels:
• Administrator - Authorized to view and carry out any task in the MASS system.
The default login for a Magos administrator:
o Username: admin
o Password: password
• User (Guest) – The user can only use the system without performing any changes to the system
configuration. The user account may change display settings available under the User Settings
submenu, and change map display presets under the Presets submenu and control camera.
The default login for a Guest:
o Username: guest
o Password: guest
By default, MASS only has two pre-configured user-accounts, admin and guest. For adding and
managing users refer to 9.5.
2.4 THE INSTALLATION PROCESS
This section contains step-by-step instructions for installing the MASS server application, as well
as for carrying out the measures required for proper operation of the software.
Ensure that you read this section carefully and carry out all specified instructions before
launching the application.
2.4.1 GENERAL
The installation process is divided into the following procedures:
1. Installing the application – Installing the various software components required for running the
MASS server on your computer.
2. Activating and registering the software license– Activating your purchased software, registering the
software, and acquiring the software's license.
NOTE
This chapter refers only to first time installation. For upgrading existing
installation while preserving site data please contact support@magosys.com.

2.4.2 INSTALLING THE MASS SERVER APPLICATION
Download and save the MASS installation file from

https://partners.magosys.com/portal/downloads within the "Software" tab.
NOTE
Downloading the software from Magos portal requires registration and a
username and password. Please contact support@magosys.com
1. Ensure that you have Windows administrator privileges.

2. Run the executable file.
Depending on the security settings of your system, a security warning may pop-up.
Figure 1: Installation Security Warning
3. Click Run (pre-Windows 10 versions) or Run anyway (Windows 10) to continue.

The MASS setup wizard welcome screen appears. Click Next.
4. Review the License agreement, and select the “I accept the license agreement” check box.
5. Click Next to continue.
6. The Custom Setup window will now open.

Figure 2: The Custom Setup window
7. Use the components display to change installation options, or click Browse… to change installation
path.
8. Click Next to proceed to the installation summary window, then click Install.
9. If User Account Control is active on the computer, the Confirm Installation screen appears,
requesting you to confirm the installation of MASS on your computer. This screen appears every
time the server is installed, namely: not only on first installation but also if the server had to be
uninstalled and is later re-installed.
10. Click Finish to exit the wizard. A shortcut for launching the MASS server application is created on
the desktop, called MASS Service Manager.
11. You might be required to restart windows in order to properly run the MASS Service Manager, and
the server manager application.
The MASS server-side application is now installed.

NOTE
If you are running the installation on Windows 10, you are now prompted whether
you want to allow the application to make changes to your system. Click Yes to
confirm.

Figure 3: Shortcut for the MASS service manager application
2.4.3 MASS SERVICE MANAGER APPLICATION

MASS 3.1 and above runs as a Windows service, that automatically starts on system startup. By
default there is no need to run the application after system reset/power up.
In order to manage this service and perform other actions a "Service Manager" application is also
installed.
The service manager is accessible via a shortcut ( ) in the system tray icons menu. If this
icon is not visible for some reason, double click the "MASS Service Manager" shortcut on your
desktop (Figure 3), or run the "ServiceManager.exe" from the installation path (default path is:
"C:\Program Files\MASS3\ServiceManager.exe").
1. Click the tray icon short-cut to open the service manager menu:
Figure 4: Service Manager Application Menu
2. There are several actions available from this menu:

• Start/Stop starts/stops the MASS Server service
• Open MASS Client launches your system default browser and browses to the MASS client page
• Open Config Folder open MASS configuration folder in file explorer
• Help browses to Magos support page
• Exit closes the service manager application. (Note that MASS service will continue to run
regardless of service manager status).

IMPORTANT
MASS service can only be stopped and re-started by a windows user with
administrator privileges. If you are logged on as a non-administrator, exit the
service manager, and click "run as admin" on the shortcut in order to obtain
privileges required for starting and stopping the service.
2.4.4 ACTIVATING AND REGISTERING THE SOFTWARE LICENSE

In order to start the MASS application you must first obtain a valid license file. In case a
permanent license was not issued, a temporary license can be obtained for demo purposes.
Either kind of license is obtained by posting a request to Magos Systems support team, or
accessing the Magos Partners Portal at https://partners.magosys.com/licence (requires portal
username and password).
To activate and register MASS license:

1. Make sure MASS service is running on the server machine – review service status using the
service manager application as explained in 2.4.3.
2. If possible, connect to the internet to allow online registration.
3. Click the MASS icon in the system tray and select Open MASS Client. Alternatively, open your
preferred web browser (it is advisable to use Google Chrome) and enter the address http://[MASS
Server IP Address]:3000.
4. If no valid license file has yet been issued, the browser redirects to the MASS Registration and
Activation web page.
Figure 5: MASS Registration and Activation web page
5. Fill the form, while ensuring that you enter the following:
• Name – company name
• A valid email address – this is the address to which the issued license file will be sent

• Phone number –in case support team need to contact you.
• Number of sensors including radars and cameras – make sure this matches the number of
channels purchased.
• Comments – If this is a demo license request please elaborate on your need here. For permanent
license please enter the PO number or any other means that will assist the support team in
identifying the purchase.
• Select the relevant MAC address from the list – use the MAC address that matches the network
adaptor connected to the radars and potential clients. If in doubt contact Magos support team for
assistance.
IMPORTANT
When selecting a MAC address, verify that the MAC address is of the permanent
adapters, Don’t choose a removable or temporary network adapter.
6. If connected to the internet, click Send Request, and verify that the license request was
successfully sent.
Figure 6: License Request successfully sent confirmation
If the send process failed due to lack of connection to the Internet or for any other reason, an
error message is displayed.

Figure 7: Error sending license request message
7. For "offline" registration, click on Download Request to download the license request file and send
the file to support@magosys.com, or use the online license activation process via the Magos
License Server: https://license.magosys.com/.
Once the support team has processed the license request, a lincense.lic file will be sent to the
email address listed in the request. This could take up to 1 working day.
8. If you have access to the Magos Partners Portal, and you've received an e-mail confirming that a
license has been issues to you follow the instructions in the mail to activate your license using the
license request file you've downloaded in the previous step.
9. Once you receive the license.lic file, login to the MASS server again. The License page should
open automatically. If the license page hasn't opened, you may access it directly by typing <MASS
server IP address>:3000/License in the internet browser address line.
10. Use the Upload license file section to upload the license file by clicking Choose file to browse for
the license file's location on your computer. Alternatively, drag the file to the intended section and
click Upload license.
Figure 8: The Upload License form

Once the license file is successfully uploaded, a Success message will appear including the
link to the login page, allowing you to start working with MASS. In order to proceed to the
client view, click Proceed to MASS.
Figure 9: License uploaded successfully
IMPORTANT
To review your license details, browse to Error! Hyperlink reference not valid..

3. GETTING STARTED
Once the server-side software is installed and running, you can access MASS from any web-
browser supporting device, provided that both the server running machine and the client side are
connected the same LAN.
This chapter covers the basic necessary steps for initial setup of your site and is designed as a
"quick start" guide. For a more detailed coverage of all MASS features review the next chapters.
Most of the setup steps are only performed during the site setup, and in the event a sensor needs
to be changed or moved.
3.1 LAUNCHING THE APPLICATION
To launch MASS:
1. Before accessing the MASS server, ensure that your license is updated (see section 2.4.4,
Activating and Registering the Software License, on page 17), and that MASS service is running on
the server machine (see section 2.4.3).
2. Access the client view:
• If you are running the client side on the same computer as the server: http://localhost:3000, or Click
the MASS icon in the system tray icons menu and select Open MASS Client.
• If you are running the client side on another computer: http://[MASS SERVER IP ADDRESS]:3000,
where [MASS SERVER IP ADDRESS] is the IP address of the computer running the MASS server
application (for example, for 192.168.1.207 IP address, use: http://192.168.1.207:3000 ).
The MASS login screen appears, prompting you to provide your credentials.
3. When accessing MASS for the first time you must login as the administrator.
 Username: admin
 Password: password
3.2 SETUP A MAP VIEW
The first step when setting up a protected site is to place the map / satellite picture of the area as
a background on top of which targets, sensors, and areas are displayed, and saving the site
location as home-screen.
This ensures the map view will return to the area of interest after each editing phase, and new
sensors will be placed in the area of interest. If no default view is defined, new sensors are
placed at [0,0] coordinates, which is off the west coast of Africa.
The map is automatically acquired from online mapping engines.
3.2.1 SELECTING THE MAP IMAGE SOURCE
To select the map image source:

1. Ensure that the device running the MASS server software is connected to the Internet, because
most maps must be downloaded in real-time. If no internet connection is available, contact Magos
support for obtaining an offline accessible map.

2. On the top right of the screen, move the mouse cursor over the icon (or tap it when using
touchscreen platforms) to open the Display Options menu.
Figure 10: The Display Map Options menu
3. Select the requested map source from the following options:

• Bing Map – Displays a satellite picture of the interest zone
• Open Street Map – Displays a standard line plot map
• Google Map – Displays a satellite picture of the interest zone
• Local Map – Used for displaying the map that is stored in the local cache on the server; Use this
option when the device running the server is not connected to the Internet. For instructions on
creating a local cache on the server and performing map caching, see section 8.1, Enabling Map
Caching.
3.2.2 HOME SCREEN SETTING

By default, when you enter the Mass, the map you see fits your screen, meaning that all sensors
monitored by your system are displayed on the map, regardless of their layout.
.
1. Click the icon on the left hand side of the Map view. If connected to the internet, type the
address of the site. Otherwise, type in Lat. Long. Coordinates in decimal, north east format (e.g.
"40.748502°, -73.985652°" will take you to the Empire State Building in Manhattan).
2. Right click the icon and confirm the change of your Home map in the prompt window.
3. Click Yes to confirm.

4. Click on icon to open the side menu, expand the user settings menu and the Click Fit to
screen/Home to toggle the display mode between "fit-to-screen" and your home screen. This
selects the default display mode (whenever display is refreshed).
Figure 11: The Fit to screen/Home option
5. You can now navigate to the Home screen at any time by left-clicking on the icon on the map.
6. In order to view the entire site, click on the icon on the map. This will set the zoom and pan to
include all defined sensors.
3.2.3 BASIC MAP NAVIAGATION

The displayed map is always oriented with the north pointing to the top of the screen. MASS
offers a simple and intuitive interface for map navigation.
• Panning: To move the map, press the Ctrl key while clicking and dragging the map to the
requested position. In touchscreen systems use two fingers for dragging the map to the requested
position.
• Zooming: To zoom in or out use the mouse scroller (scroll up to zoom in/scroll down to zoom out)
or click on the or buttons (on the left hand side of the map view) for zooming in or out
respectively. In touchscreen systems use standard two finger gestures for zooming in or out.
3.3 SETTING UP SENSORS
This process of positioning and configuring a sensor is required for receiving a correct picture of
the state of the protected area. Because the software displays the radar detections and tracks on
the map relative to their respective positions on the map, inaccurate positioning will result in
misleading readings. Furthermore, the positioning of the cameras relative to the radars (and to
the map) must be accurate, otherwise the automatic camera cueing will not function as expected
and as a result, target verification (through video stream) will not be possible.

The actions in this section require admin privileges as they affect the MAS server settings.
3.3.1 PREPARATIONS
Ensure the following "checklist" is complete in order to allow a swift and error-free setup
procedure:
1. Connection: make sure all sensors are powered and connected to the network before starting this
phase. Ethernet link to each sensor may be tested using PING, Magos' Radar Manager Application
for radar sensors or ONVIF Device Manager for cameras.
2. Sensor details: Make sure the IP addresses and MAC addresses of all sensors are known, and
listed.
3. Sensor locations: If possible verify GPS position of each of the sensors. In addition measure the
installation height relative to protected area ground level.
4. Sensor heading: For radars, measure (using a compass) or estimate the direction in which the
radar is facing relative to the north.
5. ONVIF account usernames and passwords required to access PTZ control for each camera sensor
6. Make sure there is an accessible tool for viewing camera video stream (such as a VMS, camera
webpage or ONVIF device manager)
3.3.2 ADDING A RADAR SENSOR

This section describes the necessary basic steps required to set up a radar sensor in the MASS.
For more details on how to calibrate sensor position and modify sensor behavior refer to chapter
4.
Setting up Radar identification details:
1. Click the icon to display the Settings bar.
Figure 12: The Settings bar – Adding a Radar Sensor
2. To add a Radar, move the cursor over the RADARS menu and click the icon.
The Edit Mode window now opens with the Edit Radar Sensor pane on the left hand side.

Figure 13: Edit Mode for adding and editing a Sensor
MASS Server continuously scans for Magos radars and ONVIF devices that are connected on the
same network
3. To select an auto-detected sensor: click the icon (bottom left of the screen next to the
Discovered heading) to expand the list of auto detected sensors. A list of all auto-detected sensors
that are not yet defined on the server. Review either the Name or MAC column, or the IP Address
column to locate to desired radar. Ensure that the Type column lists the sensor as RADAR and
that radar model matches the Model column.
Figure 14: New Sensor List

The New Sensor List includes the following data:
• Name or MAC – MAC address of the radar sensor or ONVIF name of the ONVIF device
• IP address - The sensor's IP address.
• Model – Model name.
• Version – for radar's only this include the DSP FW version of the radar.
4. In case sensors are not online during the setup stage, or auto-detection failed, you can manually
add the sensor by filling the General sensor details tab (top left of the edit mode screen). If sensor
was selected in the previous step, just replace the default values in the Name and Color fields.
Figure 15: General Sensor Details Tab
This Tab includes the following fields:

• Enabled – On/Off button – make sure it is set to on for working with a connected sensor. If sensor
is disconnected or offline, switch to off to avoid error messages.
• Name – Any text that will be used to identify the sensor within the MASS client view (e.g. "Radar1"
or "South East Corner Radar"). Default value is the MAC address of the sensor.
• IP Address – the IP address of the radar (4 numbers between 0-255, separated by dots).
• Model – The model of the sensor – pick the model from the dropdown list. BY default contains the
auto-detected model.
• Color – Pick a color representing the Radar sensor on the map and all targets associated to it.
Either pick from the color pallet or type in a custom color code in 2 bytes hex RGB format - total of
6 hexadecimal digits (e.g. FF0000 is 255 red, 0 green, 0 blue).
Assign a position to the radar:
5. Switch to the "Location" tab on the top left of the edit mode window, and fill in the sensor location
data.

Figure 16: Sensor Location Tab
• Latitude – in decimal format, north is positive.

• Longitude – in decimal format, east is positive.
• Azimuth – Rotation angle relative to the north.
• Height – Sensor installation height relative to the monitored area ground level.
Alternatively, if geographic coordinates of the sensors are unkown, use the map view within the Edit
mode window on the right hand side to visually place the radar. Drag and drop the icon on the
estimated position of the sensor or use Ctrl+→/Ctrl+/Ctrl+↑/Ctrl+↓ for moving the radar
location (use Ctrl+Shift+[Arrow] for finer steps). Use Ctrl+[ or Ctrl+] to rotate the radar.
Save changes and exit edit mode:
6. When done click on the Save button (top left) to save changes made locally, then click Finish on
the center bottom of the Edit Mode window (if changes haven't been saved a warning window
appears). The Edit Mode window will close, display will return to the Map view and a confirmation
window will appear.
Figure 17: Edit Mode Summary Window
Additional sensor properties and radar location calibration methods are covered in chapter 4.

NOTE
When adding a new sensor, you can view the existing sensors as a reference. In
order to view existing sensors expand the Existing Sensors list and check the
preferred sensors' box in the select column.
3.3.3 RADAR SENSORS IN THE MAP VIEW

1. The newly added sensor is now displayed in the Map View indicated with the icon (for full list
of icon variations refer to 4.1). It is also listed in the settings menu under the RADARS submenu
(click on the icon to expand the list of radars).
• Sensor info: click on icon next to the radar name in the list, to display Sensor info (name,
model, IP address and error status) on the bottom left of the settings menu
Figure 18: Edit Mode Summary Window
• Remove sensor: click on the icon next to the radar name in the list, to remove the sensor from
MASS
• Edit Sensor: click on the icon next to the radar name in the list to return to Edit Mode and
change sensor settings.
Radar command and control in the map view:

2. The Map view displays all targets as white dots. Target movement path (track) is indicated with a
white line. Once target detection stops, the entire track is moved into the "history layer" and will be
displayed in gray in the map view (see Figure 19).

Figure 19: Targets and Target History display
3. A single click on the track head (of either a "live" target or one from the history layer) will open the
Target Info window, displaying target speed, distance from detecting sensor, confidence level and
detection source (radar name). Double click on track head, or clicking on the icon will re-direct
the nearest camera to start auto-tracking the selected target.
Figure 20: Target Display with Target info
3.3.4 ADDING A CAMERA

This section describes the necessary basic steps required to set up a camera sensor in the
MASS. For more details on how to calibrate sensor position and modify sensor behavior refer to

chapter 6.
Setting up Camera identification details:
Figure 21: The Settings bar – Adding a Camera Sensor
2. To add a camera, move the cursor over the CAMERAS menu and click the icon.
The Edit Mode window now opens with the Edit Camera Sensor pane on the left hand side.
Figure 22: Edit Mode for adding and editing a Camera Sensor
MASS Server continuously scans for Magos radars and ONVIF devices that are connected on the
same network
3. To select an auto-detected sensor: click the icon (bottom left of the screen next to the
Discovered heading) to expand the list of auto detected sensors. A list of all auto-detected sensors
that are not yet defined on the server. Review either the Name or MAC column, or the IP Address
column to locate to desired camera. Ensure that the Type column lists the sensor as CAMERA and

that camera model matches the Model column. Refer to Figure 14 for more details about the data
in the new sensor list.
4. In case sensors are not online during the setup stage, or auto-detection failed, sensor can be
manually added by filling the General sensor details tab (top left of the edit mode screen). If sensor
was selected in the previous step, just replace the default values in the Name and Color fields.
Figure 23: General Camera Sensor Details Tab

This Tab includes the following fields:
• Enabled – On/Off button – make sure it is set to on for working with a connected sensor. If sensor
is disconnected or offline, switch to off to avoid error messages.
• Name – Any text that will be used to identify the sensor within the MASS client view (e.g. "Camera"
or "South East Corner Camera"). Default value id the ONVIF device name of the sensor.
• IP Address – the IP address of the radar (4 numbers between 0-255, separated by dots).
• UserName: ONVIF profile username (make sure user has PTZ control permissions).
• Password: ONVIF profile password.
• Model: The model of the sensor – pick the model from the dropdown list. By default contains the
auto-detected model. If your camera model is not found in the dropdown contact Magos support to
add the camera model to the known model list. After selecting the model, hover with the mouse
over the icon for full info on exact hardware and firmware versions of the supported model. If
these details do not match the hardware and firmware versions of the installed camera contact
Magos support team.
• Color: Pick a color representing the camera sensor on the map and all targets associated to it.
Either pick from the pallet or type in a custom color code in 2 bytes hex RGB format - total of 6
hexadecimal digits (e.g. FF0000 is 255 red, 0 green, 0 blue).
• Field of View: roughly the desired field of view in meters, meaning how meters will fit into the width
of the camera view. This setting controls the desired zoom level. If targets seem too small to you,
decrease the value such that the camera zooms in more and screen width contains less “meters”. If
the camera zooms in too much and targets are left out of the frame increase this value. For first
time settings it is recommended to leave the default value.

NOTE
The icon next to the model will be highlighted in orange whenever extra
steps are required through the camera configuration web-interface for proper
operation with MASS, as shown in the example.
Figure 24: Camera Model Info
Assign a position to the camera:
5. Switch to the "Location" tab on the top left of the edit mode window, and fill in the sensor location
data.
Figure 25: Camera Sensor Location Tab
• Latitude – in decimal format, north is positive.

• Longitude – in decimal format, east is positive.
• Azimuth – Rotation angle relative to the north.
• Height – Sensor installation height relative to the monitored area ground level.
• DTM – clear all camera DTM information – see section 6.3 for more details on DTM.
6. In order to set location, fill in the Latitude and Longitude with the geographic coordinates of the
camera. Alternatively use the map view within the Edit mode window on the right hand side to
visually place the radar. Drag and drop the icon to the estimated position of the sensor or use
Ctrl+→/Ctrl+/Ctrl+↑/Ctrl+↓ for moving the camera location (use Ctrl+Shift+[Arrow] for finer
steps).

7. In order to determine the camera azimuth open an external tool for viewing the camera video
stream. Double click on a landmark visible in the map view to point the camera to that location.
Use the Ctrl+[ or Ctrl+] or drag and drop the orange "angle meter" in the map view to adjust the
Azimuth parameter until the camera video stream is centered on the landmark. You can now verify
correct position and angle by dragging and dropping the camera FOV triangle to a second
landmark. For more details on camera position calibration refer to section 6.3.
Figure 26: Camera Edit Mode Map View – Setting Rotation Angle
8. When done click on the Save button (top left) to save changes made locally, then click Finish on
the center bottom of the Edit Mode window (if changes haven't been saved a warning window
window will appear.
Figure 27: Camera Edit Mode Summary Window

Additional camera sensor properties and camera location calibration methods are covered in
chapter 6.
3.3.5 REVIEWING AND CONTROLING THE CAMERA IN THE MAP VIEW

1. The newly added sensor is now displayed in the Map View indicated with the icon. It is also
listed in the settings menu (click) under the CAMERAS submenu (click on the icon to expand
the list of radars).
• Sensor info: click on icon next to the camera name in the list, to display Sensor info (name,
model, IP address and error status) on the bottom left of the settings menu
Figure 28: Camera Info
• Remove sensor: click on the icon next to the camera name in the list, to remove the sensor
from MASS
• Edit Sensor: click on the icon next to the camera name in the list to return to Edit Mode and
change sensor settings.
• Auto Tracking: click on the / to toggle camera auto-tracking mode on or off respectively.
When on, camera will automatically track any targets that have been reported by one of the radar
sensors.
Camera command and control in the map view:

The map view constantly indicates the camera field of view with a semi-transparent triangle with the
same color that was assigned to the camera. This triangle can be drag and dropped to any location
on the map in order to direct the camera to the desired location. If auto-tracking was enabled, this
will also pause auto-tracking for a short while.

3.4 ADDITIONAL STEPS
This chapter can be considered as a "quick-start" guide allowing the reader to quickly place
sensors and review their output and basic MASS functionality. For a complete site setup there
are several additional steps that might be required. Please follow the list below according to the
requirements of your site:
• Fine tuning and calibrating radar location and detection performance: See chapter 5.
• Fine tuning and calibrating camera location: See chapter 6.
• Setting up areas of interest and their priority– alarm zones and coverage zone: See chapter 7
• Advanced map settings: creating a local cache of the map and additional map controls: See
chapter 8
• Additional Configuration options: See chapter 9
• Basic user operations, system behavior description and routine SW operation that does not require
administrator privileges: See chapter 4

4. MAP VIEW GENERAL OPERATIONS
This chapter covers the basic operations available to the end user when operating the MASS. All
the actions covered in this chapter have no effect on server-side application and only affect the
current view on the client side. This chapter is designated for end users and operators and
covers routine actions required for operating the MASS once the site configuration and setup
stage is complete.
4.1 LAYERS
This section describes the various viewable layers. Map view is composed of several "layers"
each includes a different set of visual aids that can be displayed on top of the map view.
Move the cursor over the button on the top right of the map view, to open the layers menu:
Figure 29: Layers Menu

Layers menu is divided into 2 sections:
• Source Map menu – for choosing the source of the map (see section 3.2.1)
• Display Menu – for selecting which layer to display.
The items in the display menu are the various layers. Click the checkbox next to them to make this layer
visible/invisible.
The included layers are:

• Targets: This layer includes the target paths as detected by the radars. Targets are represented as
curved lines with a round head. The round head indicates the current target location and the "tail"
indicates the path travelled by the target since it was detected.
• Targets History: This layer includes the target paths of targets that are no longer detected by the
radars. Once a target is no longer detected by the radar it will be removed from the Targets layer
and added to Targets History. The line and head representing the target will change color
according to the color settings chosen in the system configuration (See section 4.1).
• Radars: This layer displays the radar sensor location on map. Radars are indicated by the
icon, where the color is user configurable via the sensor edit mode (see section 3.3.2). Icon
behavior:
o When radar is connected and communicating with the MASS, a round "halo" is constantly
flashing around the icon.
o When radar is not communicating with the MASS for any reason, the halo is not displayed, and
the icon changes to .
o When radar is disabled via the sensor edit mode (see 3.3.2), halo is not displayed, and the
icon changes to .
o Upon setup, in edit mode only, when radar is first defined and communication was not yet
established with it, the icon displayed is .
• Radar Coverage: Displays the estimated coverage area as a semi-transparent grey oval shape.
The white lines are spaced every 100m radially, relative to the radar location. Clicking on a radar
sensor name in the RADARS menu, within the Settings side menu.
Figure 30: Radar Coverage Diagram

• Cameras: This layer displays the camera sensor location on map. Cameras are indicated by the
icon, where the color is user configurable via the sensor edit mode (see 3.3.2). Icon behavior:
o When camera is set to auto-track the icon changes to .
o When camera is disabled via the sensor edit mode (see 3.3.4), the icon changes to .
o When camera is not responding to MASS communication attempts, the camera icon changes
to .
o Upon setup, in edit mode only, when camera is first defined and communication was not yet
established with it, the icon displayed is .
• Cameras FOV: Displays the Field Of View (FOV) triangle (or trapezoid see 6.2) on the map. The
center of the triangle's base is located where the camera was pointed. The vertex opposing the
triangle base is the camera location. The triangle is filled with a semi-transparent color matching the
color assigned to the camera sensor. Whenever a camera is "externally moved" using a SW other
than the MASS (e.g. VMS or camera web-interface) the FOV triangle will change color to red and a
notification window will appear on screen warning that camera is currently not controlled by MASS.
Click and Drag on the camera FOV will point the camera to the point where the FOV was dragged.
To disable visual warning use the UI Setting menu in the system configuration (see section 9.3.1).
Figure 31: External Intervention on Camera
• Alarm Zones: Displays the alarm/view polygons defined in the currently active profile. See chapter
7 for more info on zones. Alarm/View zone polygons are displayed as a dashed orange line on the
outline of the polygon. If a Zone is defined as an Alarm Zone, whenever an alarm is triggered (by a
target entering the zone) the polygon will momentarily flash in orange. The same occurs when zone
is clicked in the Alarm Zones menu within the settings side menu.
Figure 32: Alarm Zones on the map view

• Coverage Zone: Displays the coverage polygons defined in the currently active profile. See
chapter 7 for more info on zones. Coverage Include or Exclude zone polygons are displayed as a
solid green or red (respectively) line on the outline of the polygon. The polygon will momentarily
flash in when zone is clicked in the Alarm Zones menu within the settings side menu.
• DTM: Displays the DTM of currently selected camera. To switch between DTMs select the desired
camera from the CAMERAS menu within the settings side-bar or click on the desired camera icon
in the Map View. For more information on DTM see section 6.3.
• Overlay: Displays the overlay layer. For more information on overlay, see 8.3.
4.2 MAP DISPLAY OPTIONS
This section describes how to modify Map display options for better visibility and user
convenience.
4.2.1 OPACITY & MAP COLOR

1. On the top left of the page, click the button to open the Settings menu on the left of the
screen.
1. Expand the USER menu > User settings.
2. Use the slider control next to the Opacity option to adjust opacity level of the map layer. Left most
is minimum opacity (map layer is "solid"). Rightmost is maximum opacity – only the background
color is seen.
3. Click the color selection menu ( ) to choose background color for the map.
4. Use the slider control next to the Map Color option to adjust color level of the map layer. Left most
is maximum color (map layer is in original colors). Rightmost is minimum color – map is displayed
in grayscale.
Figure 33: Opacity and Map Color Setting

4.3 MEASUREMENT TOOL
The measurement tool is an auxiliary site-planning and target management tool, which allows
distance measurements on top of the Map View.
1. On the right side of the screen there is a ruler icon , move the mouse over the icon to open the
measurement tool.
2. A window “Measure distances and areas” will be opened.
Figure 34: MASS ruler tool display

3. Click on “create a new measurement”.
4. The measurement window will open – click Create New Measurement to start marking a
measurement area
Figure 35: Measurement Window – Initial Stage

5. Every click on the map will add a measurement point (a vertex of the measured area polygon)
6. The coordinates of the last added point appear in the Measurement Window.

Figure 36: Measurement – First point added
7. As of the second point, the path distance (length of the line connecting the measurement points) is
also displayed in the measurement menu.
8. As of the third point, the area of the polygon defined by the measurement points is also displayed in
the measurement window.
Figure 37: Measurement after 2 points
9. Click on “Finish measurement” and a summary will appear on spot. You can close this window
using the X button on the top right.
Figure 38: Measured area and Summary

10. At any time you can click on the measured area to re-open the measurement summary window.
11. To delete the measured area click “Delete” on the bottom right of the measurement summary
window.
Figure 39: Measurement Summary Window
4.4 ADDING AND REMOVING USER-DEFINED PRESETS
Presets are pre-defined location and zoom level settings of the map view. When the protected
site is too large to be included conveniently in a single view, presets can be used to manually
navigate the view between the various areas of interest, while still retaining a high zoom level that
allows the desired discretion level of details.
To add a user-defined preset:
1. Open the main menu by clicking the icon on the top left of the screen. The Settings bar
appears.
2. Move the cursor over the PRESETS menu and click the . Icon to add a new preset.

Figure 40: The Add Preset option
3. The Add Preset dialog box will open.

4. Enter a name of your choice and click Save.
The newly created preset - in the example below is now displayed under the Presets menu.
NOTE
Preset name must not contain spaces or “–“ (Hyphen-minus).
Figure 41: The Presets section with a newly created preset
To remove a user-defined preset:
1. Open the main menu by clicking the icon on the top left of the screen, The Settings bar
appears.
2. Expand the PRESETS menu to open the presets list.
3. Move the cursor over the preferred preset and click the icon to delete the preset.
4. When prompted whether you are sure you want to delete the selected preset, click Yes.
The deleted preset will be removed from the Presets section.
NOTE
If Display Mode is set to "Fit To Screen" (see 3.2.2) whenever the page is
refreshed the display will revert to the "Fit to Screen" mode in which the map is
centered such that all sensors are included in the view.
4.5 MISCELLANEOUS
4.5.1 SOUND

Mass allows sound notification for a new detected track.
To enable or disable sound open the setting side bar by clicking the icon and expand the
USER menu.
Click the Sound option to toggle sound On /Off.
When enabled, a sound notification will be played whenever an Alarm zone becomes activated.
To configure the sound played use the system configuration page. Refer to 9 for more details.
4.5.2 LANGUAGE
As of MASS 3.20 there is multi-language support for all system menus and text messages.
Language can be set via the USER menu in the settings side bar:
Figure 42: USER Menu

Click the down arrow next to the selected language value to choose from available languages.
When changing language a pop-up window will alert the user the page needs to be refreshed.
Click OK to proceed.
NOTE
Language setting is user specific. Default language for all users is English.
Changing language for administrator, for example, does not apply to other
users. To change default User Interface language use the system
configuration page, as described in 9
4.5.3 CURSOR COORDINATES

On the bottom left hand side of the map, cursor current position relative to the map is constantly
displayed in WGS-84 format.

Figure 43: Cursor Position
4.6 SYSTEM HEALTH PANEL
MASS includes a system-health module that monitors connection and proper operation of all
system sub-components and sensors. These include plug-ins, AI-Appliances, GPS Sensors,
radars and cameras. The system-health is not an error log and will only display currently active
errors. Once error is resolved it will automatically be removed from the health panel.
System health notifications are displayed on the top right of the map view whenever they occur.
Figure 44: System Health Notification
The system health panel can then be access by clicking on the notification tab ( ). This will open the
System Health Panel window as shown in Figure 48.

Figure 45: System Health Panel Window
The System Health panel is divided to 2 sections. The left-hand side is a “tree”-view of system
components (radars, plug-ins, AI Appliances, Cameras and GPS Sensors). Errors encountered in
one or more of the subcomponents will be displayed next to them in red as shown in Figure 48.
The right-hand side of the panel is a table list of all active errors. Each error includes a
timestamp, error type (affected component), Name of the subcomponent, error message and the
error ID.
User can dismiss each error by clicking the button next to it.
User can also filter dismissed errors from the system-health panel by clicking the
on the bottom right. This allows focusing only on newly occurred errors and dis-regarding pre-
known errors already handled.
Finally, once all existing errors are dismissed by the user, the notification bar in the map view will
collapse as shown in Figure 49. As long as the error is still active the system can always be
accessed by moving the mouse cursor over the collapsed notification and tab and clicking it.
Figure 46: System Health Collapsed Notification

4.7 KEYBOARD SHORTCUTS
MASS contains many useful keyboard shortcuts detailed in the table below.
Shortcut Purpose Context
<CTRL> + Direction arrow Move sensor to arrow Radar and Camera wizard
direction in large steps
<CTRL> + <SHIFT> + Direction Move sensor to arrow

Arrow direction in small steps
<CTRL> + [ or Rotate sensor CCW or CW in

<CTRL> +] large steps
<CTRL> + <SHIFT> + [ Rotate sensor CCW or CW in

small steps
<CTRL> + <SHIFT> + ]
<PgUp> Increase or decrease zoom Map Display, a camera

of camera in current look selected
<PgDn>
<Up> , <Down> , <Left> , Move camera up, down, left

<Right> and right respectively

5. RADAR SENSOR ADVANCED SETTINGS
This chapter describes additional features available for further fine tuning the radar sensor
performance and location.
5.1 RADAR OPERATION BACKGROUND
Radar performance can be divided into 2 stages: detection and tracking.

The detection stage occurs once per sweep. Each sweep the radar compares momentary
returned signal level to a nominal threshold level. If the returned signal from a given point in the
observed area exceeds this threshold, a detection is declared and passed on to the tracker. The
threshold level is a critical element in this stage – too high and targets will not be detected, too
low and too many detections will reach the tracker, resulting in possible false alarms.
The "tracker" is the name of the logic responsible for collecting momentary detections from each
radar sensor, represented as "dots" on the map with alt/long coordinates, and trying to connect
them into a coherent line or track. The tracker is in charge of filtering out false alarms (detections
caused by background noise etc.) and nuisance alarms (detections caused by in-animate
physical objects such as a tree swinging in the wind). The second important function of the
tracker is to track; that is to maintain a coherent measurement over time of each detected target
whether it maneuvers, momentarily disappears, or unites with another target.
In addition to the above, another factor to be taken into account is avoiding cross-interference
between radars. Since all the sensors share the same frequency band, adjacent units, or units
that are directed at each other might transmit the probing signal at the same time resulting in
inferences and multiple false detections. This can be avoided by synchronizing the sensors and
allotting different time slots to each sensor.
5.2 ADJUSTING RADAR SPECIFIC PROPERTIES
Detection related settings and synchronization settings are individual per radar sensor. The
following steps describe them:
NOTE
In current version this operation is only available for Magos Support
personnel.
Open the Radar Properties Page:

2. Expand the RADARS menu and click the icon to open the Edit Mode menu.
3. In the Edit Radar Sensor section switch to the Properties Tab

Figure 47: Radar Sensor Properties
Changing Detection Parameters:

NOTE
Magos radars factory defaults are optimized for the most generic purposes. It is
not recommended to change these settings without first consulting with Magos
support. However as radar performance greatly depends on the monitored area,
which tends to greatly vary in some scenarios, factory defaults could be modified
to optimized performance.
4. Threshold scheme: use the dropdown menu to choose the "threshold scheme" that best matches
the radar and the observed terrain as described in 5.3.
5. Threshold Factor: This parameter adjusts the thresholds over the entire monitored area. Enter a
number or click the spinner arrows to adjust the field value. A positive number will increase the
thresholds and results in reduced sensitivity. Increase the value to reduce false alarm rates; A
negative number will decrease thresholds and results in increased sensitivity. Decrease value to
improve detection performance.
Synchronize Radars:
To avoid cross interference between radars use the synchronization feature.
NOTE
Timing parameters greatly vary between radar models. Consult with Magos
support if you are unfamiliar with recommended settings per your model.
6. First enable the synchronization by selecting Enable from the Sync dropdown menu.
7. Adjust the Sweep Time and Slot values: Assign a different Slot offset to each adjacent radar, and
ensure that overall Sweep Time value is equal or greater than the Slot Time. E.g. For SR500-I,
minimal slot time is 100ms, minimal Sweep time is 400ms. To sync 3 radars, assign slots 0, 100
and 200 to each of the radars respective. The total allotted time is 0-300ms which is below the
Sweep Time, so sweep time can remain at the default value of 400ms.

8. Finally, click on the Save button (top left) to save changes made locally, then click Finish on the
center bottom of the Edit Mode window (if changes haven't been saved a warning window
window will appear.
5.3 THRESHOLD SCHEMES
A threshold scheme is custom tailored threshold level per range. The thresholds are used to filter
non-relevant detections generated by clutter and thus reducing the chances that the tracker will
declare a valid target based on detection generated by clutter/non-relevant targets.
Threshold schemes are model specific, and nominally the default threshold scheme per model
should provide the best results. However in some extreme cases, where the observed terrain
defers from the normal scheme of operation, radar performance in terms of target detection
probability or in terms of nuisance alarm rate can be further optimized by modifying the threshold
scheme. This section covers the various available schemes per model.
5.3.1 SR500F AND SR250F THRESHOLD SCHEMES

• Normal – Default Threshold scheme for this model. Suites most terrains and scenarios.
• OpenField – In this scheme radar becomes more sensitive (compared to Normal) in close ranges.
Use this scheme in clutter/nuisance free environments, or in order to improve radar detection
performance in ranges up to 200 meters.
• Urban – In this scheme radar becomes less sensitive (compared to Normal) in all ranges. Use this
scheme in cluttered (urban or fauna/flora rich) environments, or in order to reduce nuisance alarms.
5.3.2 SR500I AND SR250I THRESHOLD SCHEMES

• Urban – Default Threshold scheme for this model. Suites most terrains and scenarios.
• OpenField – In this scheme radar becomes more sensitive (compared to Urban) in close ranges.
Use this scheme in clutter/nuisance free environments, or in order to improve radar detection
performance in ranges up to 190 meters.
5.3.3 SCEPTER-C
• OpenField – In this scheme radar becomes more sensitive (compared to Normal) in all ranges but
mostly in short ranges. Use this scheme in clutter/nuisance free environments, or in order to
improve radar detection performance in ranges up to 250 meters.
• Urban – In this scheme radar becomes less sensitive (compared to Normal) in all ranges. Use this
scheme in cluttered (urban or fauna/flora rich) environments, or in order to reduce nuisance alarms.
• Tangent – radar is more sensitive than Normal in short ranges (up to 150m), and less sensitive
above that. Found to be optimal in relatively cluttered environment for detecting tangent
approaching threats.
5.3.4 SR1000F

• Low – In this scheme radar becomes more sensitive (compared to Normal) in all ranges but mostly
in short ranges (up to 230 meters). Use this scheme in clutter/nuisance free environments, or in
order to improve radar detection performance.
• High – In this scheme radar becomes less sensitive (compared to Normal) in all ranges but mostly
in short ranges (up to 300m). Use this scheme in cluttered (urban or fauna/flora rich) environments,
or in order to reduce nuisance alarms.
• Short – Radar becomes more sensitive than Normal in short ranges up to 230m.
• Short Low – most sensitive configuration – radar becomes more sensitive compared to Low in
short ranges up to 230.
5.4 ADJUSTING TRACKER PARAMETERS
In order to declare a valid target there are numerous criteria that the collection of detection
(called "hypothesis") must meet. While default parameters have been optimized to suite almost
all scenarios, in some cases there is room for site-specific optimization. Tracker parameters are
global and apply to all the sensors in the system. The following steps describe the process of
viewing and changing these parameters:

2. Click on the icon next to the USER menu to access the System Configuration window.
Figure 48: System Configuration Window

3. Scroll down and locate the Tracking Parameters section
4. Adjust parameters as follows:
• Min Distance: in meters. Adjust this to define minimum distance an undeclared target must travel
before it will be detected (this distance is measured from first detection up to current track head).
Value is in meters. Increase this value to reduce nuisance alarms caused by semi-static singular
objects (poles/trees swinging in the wind etc.). Decrease this value to shorten detection times and
increase probability of detection for weak targets. Default value is 7 meters. Nominal range is 3-10
meters.
• Min Detections: The value sets the minimum number of collected detections before a track
becomes valid. Value is an integer number, unit less. Increase this value to value to reduce
nuisance alarms caused by high-clutter areas (e.g. a wind gust across a line of bushes might result
in a consecutive row of detections). Decrease this value to increase probability of detection for
weak targets. Default value is 5. Nominal range is 4-10 detections.
• Target Velocity: This parameters affects several tracking parameters choose one of the following
using the dropdown menu:
• Fast (default): Track targets up to 25 m/s. Tracker is optimized to accommodate fast-moving
targets.
• Slow: Track targets up to 10 m/s. Tracker is optimized to handle slow and weak targets (e.g.
tangent walk or crawlers).
5. Click Save on the bottom of the screen to apply any changes made.
6. When done click Close on the bottom of the screen, or click on the Magos logo on the top left to
return to the main Map View.
5.5 ADJUSTING TRACK MERGING PARAMETERS
In some scenarios, e.g. when several radars cover the same area, or when extremely large
targets (boats, trucks) are observed, it is advantageous to merge nearby target reports into a
single track report and thus avoid multiple events generated by single target. This is can be
achieved by enabling Track Merging and adjusting the relevant parameters.


Figure 49: Track Merging Configuration
9. Scroll down and locate the Track Merging section

• Enable Track Merging: Allow track merging. Enabled by default. Disable this when target
separation performance is in-adequate or if full reports are desired from each of the radars
detecting the same target.
• Merge from same radar: Allow merging of tracks detected by the same radar. Enabled by default
this will limit multiple tracks reports on a single large target (such as a boat or a large truck).
Disable this when target separation performance is inadequate.
• Max Position Difference (m): default value is 20 meters. Adjust the minimum distance
requirement for merging 2 tracks.
• Max Velocity Difference (m/s): default value is 10 meters per second. Adjusts the minimum
velocity difference requirement for merging 2 tracks.
• Split Threshold (%): In order to avoid "jittering" effect the criteria for splitting 2 merged tracks
varies from the criteria for merging 2 separate tracks. This parameter adjusts the hysteresis
between these 2 criteria. Increase value when "jittering" occurs in merging.
5.6 FINE TUNING RADAR POSITIONS
The location and heading of radar sensors has to be accurately calibrated to ensure accurate
tracking and cueing of the cameras at tracked targets.
Prior to starting this procedure, it is recommended to measure the heading and GPS location of
each radar, and fill them in the appropriate fields as described in section 3.3.2. This will provide a
rough starting point for each sensor which will make fine tuning the position easier.
To calibrate radar positions:

1. For accurate calibration, the general approach is to use tracks of a target moving along well
recognized terrain landmarks, and aligning the track history/live reports with the actual landmarks
seen in the map. This stage is easier if Track History Timeout is changed to 3600 seconds (when
done, return to default value of 60 sec) – see section 9.3.2 for instruction on how to change history
settings.
Figure 50 Fine tuning radar heading and position
2. Figure 50 shows an example of the calibration process. In the left image, the radar is misplaced by
roughly 40 meters and rotated by five degrees. The calibration process in this case includes first
rotating the sensor on the map until the track lines are parallel to landmarks (in our case, roads),
and then shifting the radar till the landmarks coincide (in this case, the radar was shifted till tracks
around the roundabout matched exactly to the roundabout in the map). Follow the steps described
in section 3.3.2 to adjust radar position.
NOTE
In the position calibration process, it is highly recommended to start with rotating
the radar until the tracks are parallel to landmarks, and then shift the radar for
perfect match.
General tips:
3. In our case, the tracks were drawn by random traffic. If traffic is not available, a human target,
walking or driving, has to trace the tracks along visible landmarks. Then the process can be
completed.
4. Repeat this procedure with all other radars. If two or more radars have overlapping coverage areas,
after fine-tuning the first radar position, the other radars can be positioned by moving them so that
the reported target track overlaps that of the first radar (as long as the target is reported by both
radars).
5. To view the output of more than one radar sensor while in Edit Mode locate the desired sensors in
the Existing sensors list and check the checkbox next to it - see Figure 14.

6. If not enough visible landmarks are available or accessible for targets, first fine-tune camera
position (see section 6.3), set camera to auto-track, and then adjust radar position such that the
tracks are aligned with the camera FOV triangle on the map and appear in the middle of the picture
in the camera video stream.

6. CAMERA SENSOR ADVANCED SETTINGS
This chapter describes additional features available for further fine tuning the camera sensor
performance and location.
6.1 CAMERA OPERATION BACKGROUND
This chapter explains the general mechanisms control camera movement in the MASS. It does
not include actual instructions on how to adjust parameters, these are covered in the next sub-
sections.
6.1.1 CAMERA MODEL

Magos is in close contact with all leading PTZ camera manufacturers to ensure that models
comply with the ONVIF Profile-S standard, and specifically support the absolute move command
and additional commands. Magos also studies the zoom profile of each camera model and stores
the information in the MASS configuration file. However there are numerous models in the
market, and if the desired/installed camera model is not in the supported camera model list, it is
recommended to contact Magos support team so that it can be added, or use the generic profile.
6.1.2 RESOURCE SCHEDULER

Camera auto-queuing is governed by a mechanism called "Resource Scheduler". The resource
scheduler manages camera allocation to targets and constantly re-examines priorities.
User has the ability to control some of these priorities via the "Alarm Zone" severity setting (see
section 7.3).
The camera allocation governing algorithm is complex due to numerous technical constraints.
However the basic logic is as follows:
• Manual Move / Manual Target Selection: receives top priority. If user manually moved the camera
or directed it to track a target, the resource scheduler will "yield" this camera in most scenarios.
• Alarm Zone Severity – if 2 targets share the same camera and are located in separate alarm
zones, the target in the alarm zone that has higher severity will be tracked most of the time.
Severity can supersede Manual Move or Manual target selection if severity value exceeds 10.
• "Wait" Duration – the more time the target is un-tracked by a camera, the more priority it receives. If
camera is otherwise occupied, once it becomes available it will be queued to the target that has
been waiting the longest duration (since last time it was tracked, or since it was first reported if it
has never been tracked). "Wait" duration can supersede Severity (and even manual user
intervention) when the less "severe" target has been "waiting" for very long periods of time (several
minutes, depends on specific scenario).
• Slew-to-Cue time – whenever the camera has to choose between 2 targets that have the same
priority (according to the above criteria) it will first track the target it can "reach" faster – that is that
target that is closer to its current field of view. Slew-to-Cue time can supersede "Wait" duration
when selecting between 2 potential targets of the same severity: when one of the targets is much
closer to the FOV of the camera, even if it has been "waiting" for less time that the further target it
might be selected first.

Exceptions:
• One exception to the above rules is external intervention mechanism that is used to avoid conflicts
with external 3rd party tools for moving the camera. Whenever a camera is moved by such an
external tool (e.g. ONVIF device manager, VMS software or camera web interface) MASS will
declare an "External Intervention" event and the camera will not be accessed by MASS until a
certain time period has expired. See section 4.1 for more info on MASS behavior during external
intervention
• A second exception to these rules is the "Target Tracking Time" parameter (see section 6.2 to
change this setting). This value is used to prevent race-conditions whenever 2 targets of the same
severity "compete" on the same camera. For example, if value is set to 5 seconds, and 2 targets of
the same severity have the same "Wait" period, the camera will be directed to one of them
(arbitrarily chosen) and will stay on that target for at least 5 seconds before it will be re-directed.
• Another exception to the above rules is manual move timeout. If user manually moved the camera
to a certain point, while this is considered a high priority constraint, if enough time has expired and
no new move commands were issues, the manual move command constraint will expire and
camera is re-commissioned to auto-track targets.
6.2 ADJUSTING CAMERA BEHAVIOR PROPERTIES
To enable disable auto target tracking:

2. Click the / icon next to the CAMERAS menu heading to enable /disable (respectively)
auto-tracking for all cameras
3. Click the icon to expand the cameras list, then on the / icons to toggle camera auto-
tracking mode on or off respectively.
To modify auto-tracking behavior:


Figure 51: System Configuration Window
3. Scroll down and locate the Camera Tracking section

• Show Camera Projection: Toggles between "camera projection" trapezoid and FOV triangle in the
Map view. The Camera Projection represents the estimated ground area seen in the video
according to camera position, current PTZ setting and ground levels. The FOV triangle represents
the direction to which the camera is pointed, triangle base is the maximum viewable range
(depends on tilt setting, camera height and ground level height) and base width represents the
angular field of view of the camera.
• Manual Move Timeout: Adjust this value to increase auto-tracking disable duration after each
external camera move command or manual move command from within the mass. For examples, if
changed to 30 seconds, then every time a camera is manually moved, it will stay in place for at
least 30 seconds before it can be re-assigned to auto-tracking.
• Target Tracking Time: Increase this to increase the duration each target is tracked before the
camera is assigned to track a different target.
• PTZ Move Timeout: Some camera models that do not support full ONVIF protocol require a
minimum time between PTZ commands. Use this value to adjust the minimum time period
according to the specific camera model used. It is recommended to consult with Magos support
team when adjusting this parameter.
• Intercept Accuracy: Some camera models that do not support full ONVIF protocol do not
accurately report their current position when polled. Increase this value to match camera
inaccuracy and ensure proper operation of the resource scheduler. It is recommended to consult
with Magos support team when adjusting this parameter.

6.3 FINE TUNING CAMERA POSITION AND VIEW
The location and heading of camera sensors must be accurately calibrated to ensure that the
video feed from the camera will include the target at any time.
Prior to starting this procedure, it is recommended to measure the GPS location and installation
height of each camera, and fill them in the appropriate fields as described in 3.3.4. This will
provide a rough starting point for each sensor which will make fine tuning the position easier.
IMPORTANT
It is extremely important that camera is perfectly leveled when installed.
Otherwise, if installed with a tilt, camera will be looking too low or too high
when auto-queued to a given position depending on the pan angle it was
directed to.
Camera calibration includes fine tuning of several parameters: Location and heading (required for
accurate pan commands), desired zoom level (required for accurate zoom commands) and
installation height and monitored area ground height (required for accurate tilt commands).
The following steps include instructions on how to easily calibrate and fine-tune the various
parameters.
To tune heading and location:
1. Ensure that you have access to an external tool that allows manual operation of the camera and
video feed display.
2. After setting up the camera, re-enter the Camera Edit Mode, and switch to the location tab (see
3.3.4 for instructions).
3. Click the Validate Location button to start the camera Location Wizard.
4. Step 1 – adjust position, height and azimuth (rotation angle) in the same manner that was
described in 3.3.4 – if this was already done proceed by clicking Next

Figure 52 - Camera Location Wizard
5. Step 2 – setting up reference points:
• Click Add reference point. The point indicator ( ) now appears in the center of the map.
• Drag and drop the indicator to a known and visible landmark on the map.
• Using the external tool prepared in step 1, manually direct the camera such that the landmark
selected on the map is centered in the middle of the video frame.
• Click Lock.
• Repeat the above for 4 or more points. As more points are added, camera initial location on the
map view might change since the wizards constantly recalculates the exact camera position and
adjust accordingly.
• Once enough points are added you will be able to click Next to proceed to the validation stage.
6. Step 3 – Validating points. Click on each of the points in the list and verify in the camera video feed
that camera has been moved to the correct position. If validation fails on one of the points, return to
the previous stage by clicking Back. Click on the icon next to the erroneous point and repeat
the above steps.

Figure 53 – Reference Point List for Validation Stage
7. When done camera FOV can also be clicked and dragged in the map view to various landmarks to
ensure that position and heading is properly aligned. At this stage disregard zoom and tilt – this
means you have to manually adjust the zoom or tilt levels until the desired landmark is seen in the
camera video feed.
8. When done click Next to exit the wizard and update camera position.
9. Click Save then Finish to exit edit mode and return to the map view.
To tune desired zoom level:
1. Each camera model has its own "zoom profile", that is, a list of FOV angles corresponding to
various zoom levels. By choosing the correct model as specified in section 3.3.4 you can ensure
that zoom parameters are properly calibrated.
2. The next step is to adjust desired field of view. Start with a wide field of view (default value is 70)
ensure that targets appear roughly in the middle of the screen, and then decrease the number to
improve visibility of targets.
To tune height and ground levels (DTM):

In some sites, ground level changes radically within the camera coverage area. For example the
camera will probably be aiming too high above ground when auto-queued at a target walking in a ravine
or a bottom of a cliff, or too low when tracking a target at the top of a nearby hill. In addition, while it is
recommended that camera installation will be level, some tilt error is expected at all sites.
To overcome this difficulty, the MASS allows the user to manually calibrate ground levels. The DTM
settings are individual per camera, and must be repeated for every camera defined in the MASS.
1. During DTM tuning it is recommended to turn-off camera auto-tracking. See section 3.3.4 for
instructions.

2. Click the desired camera icon in the Map View, or choose the camera from the CAMERAS list in
the Settings side bar.
3. Click and drag the camera icon to point the camera to the position in the map that needs to be
tuned.
4. Click on the icon at the bottom left of the Map View.
5. This creates a new "DTM vertex" – currently indicated with a red dot on the map view, at the
location to which the camera was pointed:
Figure 54 – Adding DTM vertex
6. In addition, the DTM Editing menu pops-up at the bottom left of the screen:
Figure 55 – DTM Editing Menu
7. Click on the menu, and adjust the point altitude - either type a number or use the up/down arrow
key. At this stage it is recommended to verify in the camera video feed that the picture is centered
on ground level.
8. When done adjusting, click the icon to save, or the to discard this vertex.
9. Repeat stages 4 to 8 for every location in the monitored area in which the camera is not aligned to
ground level.
To view edit or delete DTM vertexes:
10. Display the DTM layer via the Layers menu (see section 4.1).
11. For every point added a vertex is displays. Vertexes are connected with blue lines. Click on the
vertex representing the desired dot. A small menu appears next to it indicating coordinate and
defined ground level.
Figure 56 – DTM Vertex Info
12. Click to delete the point.

13. Click to edit this vertex. This will bring the camera to the selected vertex position. Repeat steps
4-8 to edit this vertex. Note that when the DTM editing menu appears it will contain the previous

value set for this vertex.
To reset all DTM vertexes for a given camera:
14. Use the option in the Edit Camera Location menu as described in 3.3.4.

7. PROFILES AND ZONES
Profiles are a set of user-defined zones. Depending on use-cases, several profiles can be
defined in the system, and switched between when required.
"Zones" are user-defined polygons that can be used to control system behavior based on
geographic location of targets or potential targets.
The following sections explain the zones' logic, how to create and edit these zones and how to
define profiles.
7.1 ZONES LOGIC
There several types of areas:

• Alarm Zone: In terms of radar operation, alarm zones have no effect. Alarm zones are not
assigned per sensor and are defined per the entire system. Regardless of alarm zone definition, the
radar will continue tracking target within or outside the alarm zone, and these targets will be
displayed on screen. The alarm zone is used to filter alarm/events going out to the various plug-
ins/integrated systems. Any target entering an alarm zone or originating within one will generate an
event, assuming the target meets the various filters applied to the zone (confidence level and target
classification in MASS+AI systems). The "event" is propagated to external software (if integration is
enabled), and uses vocal and visual means within the client computer to attract the user's attention.
Alarm zone events act as "Sticky bits" – once a target has entered an area it will stay "alarmed" and
not issue new events until a certain timeout has expired since the last target was detected. This
means that if a track momentarily breaks, or a second target enters the same alarm zone, no
second event will be generated. This timeout can be adjusted in the Timeout field described in the
following section.
• Coverage Zone: Coverage zones define the areas in which the sensor will operate. As such,
coverage zones are assigned per one or more sensors and apply only to these. Anything outside
the sensor coverage will be filtered. For radar this means that no target tracking is attempted
outside the coverage area. For a camera this means that during auto-tracking the camera will not
be assigned to track targets outside its coverage area. Coverage zones can either be "include" or
"exclude" zones. The sensor coverage area is the union of all the "include" zones to which it is
assigned, minus the union of all the "exclude" zones. If no include zone is assigned to a sensor the
entire world is considered to be within its coverage (minus any "exclude" zones defined).
The above define logic could be confusing. Following are a few tips and use cases designed to
improve the intuition about these:
• For cameras:
• Use coverage "include" zones to define the area in which the camera is effective. For example, if
camera's effective range is 500m above which targets are too small, define a near-circle polygon
centered on the camera with radius of 500m.
o Use coverage "include" zones in places where you want the camera to auto-track. For example
if multiple Alarm zones defined within camera range and a specific camera is designated to
service only one of them, place coverage include zone only on that area.

o Use coverage "ignore" zones to limit the areas where the camera does not have line of sight. For
example, if camera is installed next to a large tree, mask the entire area hidden using coverage
ignore zone.
• For radars:
o Use coverage "exclude" zones to filter out areas in which radars is ineffective due to: busy traffic
(such as busy roads etc.), high clutter (large clusters of bushes or trees) or where there is no line
of sight to the radar (e.g. behind walls/hills etc.).
o Use coverage "include" zones in case the monitored area is relatively small compared to sensor
coverage, and most of the sensor coverage area is highly cluttered by vegetation or busy traffic.
• Alarm Zones:
o Use alarm zones in areas where target presence is considered an event that requires logging
and monitoring. Do not use alarm zones outside the protected perimeter.
• For Example, if the protected site is surrounded by a fence and radar/camera detection capabilities
extends beyond the fence:
o If the area outside the fence is relatively "quite" with no frequent traffic, then extend radar and
camera coverage zones to include the area outside. This way the system will have an early
warning and better chance to detect and track potential threats. Make sure the Alarm zone
relates only to the perimeter inside the fence to avoid the occasional nuisance alarm.
o If the area outside the fence is relatively "noise" with frequent traffic/lots of vegetation, then
exclude it from the sensors coverage zones to avoid over-working the camera by tracking
irrelevant targets.
7.2 CREATING A PROFILE
Before defining zones it is recommended to create a profile which is a collection of zones. MASS
has a predefined "Generic" profile that by default doesn't contain zones. User can either add
zones to this profile or define a new profile. There is no limit on the number of profiles defined.
To create a new profile:

1. Open the main menu by clicking the icon on the top left of the screen.
2. To create a new profile: Move the cursor over the PROFILES menu and click the icon;
3. Alternatively copy an existing profile by first activating it: expand the PROFILES list and check the
desired profile; then move the cursor over the profile name and click the icon.

Figure 57 – Add Profile Window
4. Enter desired profile name in the pop-up window, and click Save
5. The new profile is now selected. Any new zone added, or any zone edited will apply to this profile.
6. To switch between profile, expand the Profiles list in the Setting side menu and click on the profile
to be activated.
7. To delete a profile, expand the Profiles list in the Setting side menu, move the cursor over the
profile name, and click the next to it. Click Yes in the confirmation pop-up window.
7.2.1 SETTING A DEFAULT SYSTEM PROFILE

System default profile is the profile system reverts to automatically when profile scheduler is used
and no profile has been scheduled.
Default system profile cannot be deleted. To delete a default profile, first select a new default
profile.
To define a default system profile:

1. Open the settings side bar by clicking the icon on the top left of the screen.
2. Expand the PROFILES menu.
Figure 58 – Profile Menu
3. Make sure the desired profile is currently active by clicking on it - the check-box next to the profile

name will be checked.
4. Click the icon on the right hand side of the profile name to set it as default
5. In the profile menu the icon will now appear on the left hand side next to the profile name,
indicating it is the default system profile.
7.3 DEFINING AND EDITING AND TESTING ALARM ZONES
MASS supports an unlimited number of zones, which can be added by following the instructions
described in this section.
IMPORTANT
Prior to defining zones, ensure that the Alarm Zones check box in the Layers
menu is selected (see section 4.1) - otherwise the zones will not be visible.
In addition, Alarm Zones cannot be defined before a sensor (camera or radar)
has been added.
To define and edit Alarm Zones:
2. Make sure that the requested profile is currently active.
3. Move the cursor over the ALARM ZONES menu and click the icon to add a new zone.
In the Map View the edit the zone editing options will appear.
Figure 59: Edit Zone side menu
4. Click Draw a polygon ( ) to draw a new zone

a) Click the map at the location of the polygon that defines the zone of interest. Each click
adds a vertex to the polygon.
During this stage the polygon, as defined by the vertexes (mouse clicks), is temporarily
filled in semi-transparent purple, solid purple lines define the borders of the polygon, and
the dashed line represents the next border-line that is to be drawn.

Figure 60: Drawing a new zone
At any stage while drawing, before clicking on the first point and closing the polygon,
you can select an option from the auxiliary menu:
 Finish – click for finishig drawing the zone
 Cancel – Discards all vertexes drawn
 Delete last point – Discards the last vertex drawn (can be used repeatedly up to the first
vertex)
Figure 61: Polygon Drawing Auxiliary menu

b) When finished, click the first point of the polygon. The mouse cursor's shape changes
from cross-hair ( ) to a point hand ( ) icon when moved over the first point, to
indicate that this operation closes the polygon.
Once the polygon is complete, the entire polygon "flashes" in white, line color changes
to light blue with no-fill.
Proceed to the next step in order to edit the zone properties.
5. While in Zone Edit mode, move the mouse over the requested zone (currently filled with semi-
transparent blue), and click it to open the Zone properties menu on the bottom left side of the
screen.

Figure 62: Zone Properties Menu
NOTE
In places where two or more zone polygons overlap each other, right-clicking the
polygon opens a pop-menu with the list of overlapping zone names, allowing you
to select the zone to be edited.
This menu contains the following options:
• Name – User-defined name for the zone. By default, the system assigns an arbitrary name to each
zone.
• Severity – Set Severity for the zone. Severity affects the Resource Scheduler decision when
several targets need to be tracked with limited amount of camera. See section 6.1.2 for more info.
• Timeout – The number of seconds to wait since the last target left the alarm zone and before "re-
arming" the alarm trigger. E.g. if set to 5, then if a target appears within the area and then
disappears, then next alarm event will be issued only if a new target is reported more than 5
seconds after the first one disappeared.
• Threshold – A numeric value between 0 and 1, typical value is 0.75. This is the track confidence
threshold for declaring an alarm in this zone. A higher value will reduce False and Nuisance alarms.
A lower value will increase sensitivity.
• Save – Saves all changes made. For a newly defined polygon this operation turns the polygon into
an applicable zone, thereby changing its fill color from light red to green.
• Cancel – Discards all changes made for the zone. For newly defined polygons this operation
deletes the entire polygon, while or existing/pre-defined polygons all changes made since the
polygon was last saved are discarded.
6. Click Save to finish and add the zone.

7. The newly zone will be added to the ALARM ZONES list in the main menu.

Figure 63: ALARM ZONES list menu
Editing Zones:
screen.
9. Expand the ALARM ZONES menu to open the zones list.
10. Move the cursor over the preferred zone and click the icon to edit the zone or the to delete
the zone.
11. To edit the vertex positions or add new vertexes to existing polygons, click the icon from the
Edit Zones side menu in editing mode:
• All zones are now displayed with semi-transparent red fill color polygons. The edges are marked
with dashed blue lines and the pre-defined vertexes are indicated by small white squares. In
addition, semi-transparent white squares appear on the center of each edge.
Figure 64: Edit Polygons mode

• To move the position of an existing vertex, click and drag the white square indicating the vertex's
position to the requested new position.
• To add a vertex, click and drag the semi-transparent squares from the center of the requested edge
to the requested position of the new vertex.
Use any of the options in the auxiliary menu available while in this mode.
Figure 65: Polygon Edit auxiliary menu
• Click Save when done applying the requested changes.
Alternatively, you can discard your changes by using either of the following options:
• Revert to the previous state by clicking Cancel.
• Delete fully-drawn polygons (whether newly defined or existing), by clicking the icon and then
clicking the zones to be removed.
When in this mode, an auxiliary menu is available.
Figure 66: Polygon Delete auxiliary menu
Reviewing and Testing Zones:
screen.
13. Expand the ALARM ZONES menu to open the zones list.
14. Move the cursor over the desired Zone name and click the icon to edit the zone or the to open
the Zone Info pane showing all the settings defined for this zone.
15. Use the ON and OFF buttons in the info panel to emulate an alarm generated by this zone. Clicking
the ON button will cause the alarm zone to continuously flash and an Alarm Sound will be played
(see section 4.5.1). In addition if any plugin is enabled, this will trigger the corresponding event in
that plugin (see section 9.4).

Figure 67: Zone Info Panel
7.4 DEFINING AND EDITING COVERAGE ZONES
To create/edit/review a Coverage Zone repeat the steps defined in 7.3 for Alarm Zones. With the
following exceptions:
1. Use the Coverage Zones menu instead of Alarm Zones.
2. Colors: When first created the zone is light blue. After saved the zone will be either green bordered
with semi-transparent light green fill (for include Zone) or green bordered with semi-transparent
light grey (for exclude zone).
3. While in Zone Edit mode, move the mouse over the requested, and click it to open the Zone
Properties menu on the bottom left side of the screen.
Figure 68: Coverage Zone Properties Menu
This menu contains the following options:

• Name – User-defined name for the zone. By default, the system assigns an arbitrary name to each
zone.
• Type – Choose Include or Exclude according to desired type.
• Attached Sensors – A list of all the sensors defined in the MASS. Click the check box next to the
sensors to attach them to this zone.

• Save – Saves all changes made. For a newly defined polygon this operation turns the polygon into
an applicable zone, thereby changing its fill color from light red to green.
• Cancel – Discards all changes made for the zone. For newly defined polygons this operation
deletes the entire polygon, while or existing/pre-defined polygons all changes made since the
polygon was last saved are discarded.
7.5 PROFILE SCHEDULER
As of MASS 3.1 a new "Profile Scheduler" feature has been introduced. This feature allows
creation of automatic time-based profile-switching events. This is useful for sites in which
required coverage and level of protection in several zones changes regularly during the day, or
between days of the week; for example if operator does not wants targets to be tracked on the
access road to the site during the day since traffic is allowed there, but after work hours the
access road becomes part of the secured area.
7.5.1 PROFILE SCHEDULER ENTITIES AND TERMS

The profile scheduler is based on 2 entities:
• Event – a given period of time with a given start time, end time (or duration) and recurrence
pattern. For example: "4th of July" Occurs on the 4th of July, starts at 00:00 and has a 24h duration,
or "Workday Shift" , occurs every Monday to Friday, starts at 08:00 AM and ends at 05:00 PM.
• Calendar – a collection of any number of events. A Profile Scheduler calendar is associated to a
profile.
Using these 2 entities, along with the profiles described in 7.2 it is possible to control the coverage and
alarm behvaior of the security system according to zones and schedule.
A simple example would be to setup a "day profile" and "night profile". The day profile will exclude areas
in which traffic is allowed during the day. The night profile will include these areas using extended
coverage and alarm zones. In this scenario 2 calendars will be setup in the profile scheduler: "Work
Hours" and "Off Work Hours", and these will be assigned to "day" and "night" profile, respectively.
Finally events will be added to each of the calendars to cover the entire week schedule of the site.
7.5.2 DEFINING A PROFILE SCHEDULE

Prior to creating a schedule it is recommended to define the various desired Profiles.
To access the Profile Scheduler:
1. Open the main menu by clicking the icon on the top left of the screen
2. Move the mouse over the PROFILES sub-menu, and click the icon next to the menu title.
3. The Profile Scheduler configuration page will open

Figure 69: Profile Scheduler configuration page
4. The profile scheduler default view is a calendric view containing 1 week contacting the current date.
5. To browse forwards or backwards in the calendar, use the controls on the top left. Click
Today to return to current time.
6. To switch calendric view to list view, or change the displayed scope use the display scope control
bar on the top right. Available Scopes are day, week and month.
Figure 70: Scheduler Display Scope Control Bar
To add and edit Profile Scheduler Calendar:

7. Click the on the top left next to the Calendars list title. This will open the New Calendar pop-up
window:
Figure 71: New Calendar Pop-Up window
8. Type calendar name and click Add

9. The new calendar now appears in the Calendars List on the top left of the screen:

Figure 72: Calendar List
10. Click the next to the calendar name in the list to expand the calendar sub-menu.
Figure 73: Calendar Edit Sub-Menu
11. This menu allows editing the Calendar:

• Use the drop down box to assign a profile to the calendar
• Select Color – click to change the color of the calendar and all events assigned to it
• Enabled – check or un-check the checkbox to activate/deactivate the calendar
• Delete – click to delete the calendar
• Rename – click to assign a new name to the calendar
To add/edit an event within a calendar:

12. Locate calendar name within the calendar list on the top left, and click the icon next to it.
Alternative, click and drag the icon to the desired time and date in the calendric view, then click on
it.
The Edit Event window will pop-up:

Figure 74: Profile Scheduler Edit Event Menu
13. This menu contains the following options:

• Name: Event name, for user reference
• Start: Start time and date. Click to modify. For recurrent events start date cannot be selected –
event will start recurring from current time forward.
• End: End time and date. Click to modify. For recurrent events start date cannot be selected
• Duration: Click to modify event duration (alternative to specifying end time).
• Recurrent: Click to open weekly recurrence pattern, then select days of the week on which the
event recurs.
• Delete: deletes the event
• Save: Click to apply changes and close the window
• Close: Click to close without saving changes
14. Repeat the above steps to add additional calendars and events.
15. Alternatively the calendar view has full click and drag interface for moving events to desired
position and changing duration by clicking and dragging the bottom of the event box.
7.5.3 ADDITIONAL NOTES

Following are a few "Profile Scheduler" tips and rules that might assist when creating a calendar:
1. Recurrence – Maximum recurrence period is once week. Events that repeat themselves bi-weekly,
once per month or once per year need to be added manually.
2. First time – When adding a new recurring event, the recurrence pattern will appear in Profiler
Scheduler view starting from current date forward as default. This sometimes means that after
adding the event, while in "day" or "week" view the event will not be seen in the current view (only
after browsing to future dates). To avoid this, when first defining the event drag it one week
backwards (or manually choose an earlier start date) before defining it as a recurring event.
3. Multiple Events – In case multiple events occur at the same time, the event with the latest start
time that is currently "active" will supersede. For example, if there is a recurring event for "Work
Hours" Starting at 8 AM and ending at 5 PM, and a new event is added for "4th of July" starting at
8:01 AM, colliding with the "Work Hours" event and associated to a different calendar and profile,

then as of 08:01 AM on the 4th of July, the profile associated to the 4th of July will be applied to the
system.
4. Sunday-Monday- Events that extend from the end of one week to the start of the next one are not
supported. In case there is a need to define a given calendar and profile to apply from Sunday night
up to Monday morning it must be split into 2 events – one from Sunday night up to midnight and the
other from Monday midnight up to Monday morning.
5. Manual Over-ride – at any given time Administrator level users can over-ride the automatically
applied profile and apply their own selection. This selection will remain in place until the start of the
next event in the Profile Scheduler, at which time the system will revert back to automatic profile
selection based on the pre-defined schedule.
6. No-Event – When no event is defined in the profile scheduler at a certain period of time it will
automatically revert to "Generic" profile as default until the start of the next event.

8. MAP VIEW ADVANCED SETTINGS
8.1 ENABLING MAP CACHING
The MASS map interface is based on online mapping engines. However, if internet access is
restricted on the server, MASS map view can use locally stored maps.
In order to use these local maps, the local cache must first be created, using a computer on
which MASS is installed and that has at least temporary internet access.
To enable map caching:

1. Ensure that the server is connected to the Internet.
2. Click the icon at the top right corner of the screen.
Figure 75: Map source menu

3. In the top part of the layers menu, use the radio button control to select the map source from which
local cache will be created.
4. On the top left of the page, click the button to open the Settings menu.
5. Open the OPTIONS menu and click on Create cache
6. A confirmation window will pop up; click Yes to start caching the maps.
7. Local caching takes several minutes depending on selected source and internet link quality. During
the caching process a progress bar is displayed:
Figure 76: MASS local cache progress bar
8. Once caching is complete, repeat steps 2-3 and select "Local Map" to switch to the locally created
cache. For details, see section 3.2.1 Selecting the Map Image Source.

8.2 HEIGHT UNITS
This parameter affects the units of the Location→Height and General→Field of View fields in the
Edit Camera menu (see section 3.3.4) as well as the Location→Height field in the Edit Radar
Sensor menu (see section 3.3.2)
screen.
2. Expand the USER menu > User settings.
3. Click Height Units to toggle between Meters units or Feet units.
Figure 77: change Height Units
8.3 OVERLAY
The overlay feature allows the user to display a second graphic layer on top of the map displayed
in the Map View. This is useful when online maps are not up to date, or when wishing to add
more details/features to the map.
Displaying the map overlay is done using the layers menu.
To create MASS compatible overlay files from an existing image, contact Magos Support team.

9. CONFIGURATIONS SETTINGS
The MASS system configuration is a collection of user configurable settings including web server
port, and configuration of various supported plug-ins.
NOTE
Mass must be restarted in order to apply some of the changes made in the
system configuration. In this case, user will be prompted to restart the service
via a popup window.
In order to open the Mass system configuration:
2. Move the cursor over the USER menu, and click on the button.
3. The Mass System Configuration page will open.
Figure 78: System Configuration Page

4. To return to the Map View, click the Close button at the bottom of the screen, or click on the on
the top left of the page.
There are 3 tabs in the system configuration page. These are described in the following sections.
9.1 SYSTEM BACKUP AND INFO
Site setup including sensor positioning, alarm zone definitions, profiles, schedules etc. includes a
lot of user specific data.
This data is stored on the MASS server and is labeled as "Current System Configuration". It is

recommended to keep a backup copy of this data in case of data corruption, server failure etc.
Click on the button, at the top right of the screen to download the entire
system configuration in a compressed file. This file can then be used to restore all system data.
This file is also includes system logs that might be useful for the Magos Support team when
trying to resolve an issue.
Next to the Download Configuration, click the icon to reach the system info page:
Figure 79: System Info Page

This page includes data about:
• Computer – the computer running the client
• Server – the computer running the MASS server
• License – license information
9.2 GENERAL
The general tab, within the system configuration page, includes the following options:
9.2.1 WEB SERVER:
Figure 80: Web Server Configurations Section

• Http Port: default value is 3000. Defines the port through-which clients access the server.
• Enable Https: use this to enable secure client-server authentication. This requires that server
certificate files will be uploaded to the client.
• Redirect unsecured: automatically redirects unsecured client login attempt to https when Https is
enabled.
• Https Certificates: click to open the Upload HTTPS Certificates menu:
Figure 81: Coverage Zone Properties Menu
• Click next to the key/pem file or srt file to open windows file explorer and choose the
files. When done click Upload Certificates.
• UI Default Language: Click the drop down menu and choose default UI language for all users.
Users can then override the default value using the User Settings menu, as described in 4.5.2
9.2.1 CAMERA TRACKING

See section 6.2.
9.2.2 TRACKING PARAMETERS

See section 5.4.
9.2.1 TRACK MERGING PARAMETERS

See section 5.5.
9.3 UI SETTINGS
The general tab, within the system configuration
9.3.1 GENERAL UI OPTIONS

Figure 82: General UI Configuration Section
• Show Radar Animation: Use this to disable/enable "heartbeat" animation in the client view. In
systems with multiple sensors (over 30 radars) it is recommended to disable this animation to
improve client performance.
• Show External Intervention: Use this to disable/enable external intervention pop-up warning when
MASS detects that camera has been moved by an external source. See 3.3.5 for more information.
• Alarm Sound: Choose the alarm sound played whenever an alarm zone is activated. Use the
to test the selected sound.
9.3.2 TARGET OPTIONS
Figure 83: Target Options Configuration Section
• Target Head Colors: Defines a color for the circle representing current target position.
• Target Tail Color: Defines a color for the line representing the path travelled by a live target
• Target History Color: Defines the color of the line representing the path travelled by a target that
is no longer detected.
• Target History Opacity: Defines the opacity level of target history lines. Valid values are between
1 (solid) to 0 (invisible).
• Target History Timeout (Sec): Number of seconds during which target history will be displayed
after it is no longer detected.
• Maximum History Size: Maximum number of target tracks to be retained in history. Use this to
limit amount of tracks saved and improve visibility/performance in "target" loaded scenarios.

9.4 PLUGINS
MASS software has been integrated with various applications and software. The integrations
between Mass and the various applications typically require defining settings both on Mass and
the integrated software.
Each section of the Plugins page is covered in the integration-specific manual.
To access the plugins page from MASS, and add a plugin:
3. The Mass System Configuration page will open, click the Plugins tab.
4. Click on the bottom right of the screen

5. Choose the plugins to enable from the list of available plugins in the Add/Remove Plugins Menu
Figure 84: Add/Remove Plugin Menu

The plugin specific menu will now appear in the Plugins tab. Proceed with plugin
configuration according to the integration manual.
9.5 USER MANAGEMENT
As of MASS 3.1 the MASS offers an interface for managing user accounts.
To Access the User Management Page:
2. Move the cursor over the USER: menu title, and click the icon to open the User Manager
page:

Figure 85: User Manager page
3. The User Manager screen includes the following:

• Main users table including role and username per each user defined. Table can be sorted by
clicking the icon next to the column title.
• Add User button for adding a new user
• Search option for easy location of users
• Edit button per user in the table, for editing user details
• Delete button per user in the table, for deleting the user
To add/edit users:
4. Click the icon to add a new user or the icon to edit an existing user.
5. This opens the "Edit User Details" menu on the right hand side of the screen:
Figure 86: Edit User Details menu

6. Fill the following fields:
• Username
• Password
• Confirm Password (re-type the new password).
• Role choose appropriate role.
7. Click Save on the bottom right of the menu to save changes and close the menu.

NOTE
At least one user with Admin privileges must be defined at all times.

10. MASS+AI
As of MASS 3.1, the software support integration with Magos proprietary AI appliance allowing
automatic target classification and class-based target and alarm filtering.
This application requires a designated server running the AI software, labeled "MASS+AI
Appliance". For more info about the MASS+AI solution contact Magos at: info@magosys.com
For instructions on how to setup the AI appliance itself, refer to the MASS+AI appliance user
guide at https://partners.magosys.com/portal/downloads (browse to the "Documentation" Tab).
This chapter covers the required settings and new features available in an "AI-Enabled" MASS
version.
10.1 MASS+AI SYSTEM OVERVIEW
The MASS+AI solution relies on dedicated servers running the AI target classification software.
The general concept is that once MASS has automatically directed a camera to a suspect target,
the video from target is then sent to the AI server. The AI server runs state-of-art image
processing algorithms to identify the target within the video frame, and classify it.
Target classification data is then sent to the MASS for further processing.
The MASS runs dedicated algorithm for merging the target video classification with the target
locations reported by the radar.
When properly setup, the result is that targets identified by the radar are automatically classified
and can then be filtered to screen out nuisance alarms caused by animals for example, or allow
advance zone monitoring capabilities (e.g. – allow only human traffic in a specific zone).
In terms of HW configuration, the MASS server software itself can either run on the same server
HW running the AI, or on a separate server. AI servers have a limited number of supported video
channels, and hence in some sites more than one AI server is required.
The following diagram illustrates a typical HW configuration and connection scheme:

Figure 87: MASS+AI system configuration example
In this instance, there are several AI servers, and MASS is running on a separate server.
Connection diagram is as follows:
• PTZ Cameras – connected to:
• Third party VMS/DVR for recording and real-time display,
• MASS server – to receive PTZ command
• AI Servers – to stream video into the server for further processing.
• Radar sensors – connected to:
• Radars are connected only to the MASS server, for transferring detection data and received
configuration commands.
• Third Party DVR/VMS Server – connected to:
• Cameras – to receive video streams
• MASS server – to receive alarms and log them in sync with video
• AI server – to receive target classification data in video format.
• Client Computer – for server-client and user interface.
• AI servers – connected to:
• Cameras
• MASS server – control interface and streaming video classification data
• VMS Server
• MASS Server – connected to:
• AI Servers
• Cameras – for PTZ control only
• Radars
• VMS Server – for sending alarms

• Client – for displaying user interface
10.2 TARGET CLASSIFICATION PROCESS
In an AI enabled MASS system, the target (and alarm) generation process slightly varies from a
non-AI system.
The process is as follows:
• Radar sensors detect a target
• At this stage, depending on user preferences and definitions, the target will be declared and
displayed on the Map View as a "non-classified" target (assuming user has not applied target class
filtering).
• The MASS Resource Scheduler chooses a camera and sends a PTZ command to direct it to the
position of the suspect target
• The MASS Resource Scheduler instructs the AI server to start processing the video stream from
the assigned camera.
• The AI server runs the classification algorithm and sends the MASS classification results (class and
estimated location within the video frame)
• The MASS runs a correlation algorithm to try and match classification information with the radar
reported targets
• If successful the target is now classified, and if user has not filtered the specific target class it will
be displayed in the Map View.
10.3 TARGET CLASSES AND SUB-CLASSES
The target classification algorithm is extremely complex and the resulting raw classification data
is very diverse.
For simplicity, the MASS user interfaces grouped the numerous classification objects into 4
possible groups:
• Person – including only human targets
• Bike – including bicycles and motor-cycles
• Vehicle – including cars, trucks, buses, trains, airplanes and boats
• Animal – including birds, cats, dogs, horses, sheep, cow, elephants, bears, zebras, giraffes and
other wild-animals
10.4 TARGET CLASS DISPLAY
The 4 target classes are displayed in the map view by assigning a color to the track line (indicating the
entire tracked path of the target) and replacing the track head with a class related icon:

Figure 88: Example of a classified Person track representation in the map view
• Person: green track line, with the icon as track head

• Vehicle: orange track line, with the icon as track head
• Bike: blue track line, with the icon as track head
• Animal: magenta track line, with the icon as track head
Target class is also displayed in the target info window when clicking on the track.
10.5 AI APPLIANCE CONFIGURATION
The first step in setting up a MASS+AI system is configuring the AI appliances connected to the
MASS server (even if MASS is running on the same server HW as the AI appliance).
Prior to this step ensure that:
• MASS has Ethernet connection to the AI server (or running on the same machine)
• Both MASS and the AI server are connected to the cameras
• All required camera sensors have been setup in the MASS, and are set to auto-tracking
• AI server IP address is known (see the AI Appliance user manual for details on server network
discovery methods)
To Define a new AI Appliance:

1. Open the main menu by clicking the icon on the top left of the screen
3. In the System Configuration window locate the "AI Appliances" tab (top left) and click on it.
NOTE
AI Appliances tab is only enabled in MASS+AI versions. If you have purchased
an AI enabled version of MASS and do not see this tab contact Magos Support
team.
4. Click the icon to add a new AI appliance to the system.
Figure 89: Add/Edit Appliance window
5. The Edit/Add appliance window offers the following actions:

• Name define a name to the AI appliance used
• IP define the IP address of the AI appliance.
• Enabled check or uncheck to enable/disable the appliance
• Cameras lists all the camera sensors defined in the system. Check the checkbox next to each
camera to assign it to the AI Appliance (consult with the AI Appliance user manual for details on
max allowed cameras per AI Appliance).
• Delete – Remove the appliance
6. The Edit/Add appliance menu can always be accessed via the AI Appliances tab in the system
configuration page by clicking the next to the appliance name.
7. Additional info listed per Appliance:
• Connection Status appears as "Connected/Disconnected" below the appliance name
• Number of Assigned Cameras appears on the right edge of the screen next to the appliance
name:
8. When done click Save at the bottom of the screen, and close to return to the MASS map view.
10.6 MASS+AI ZONES
In an AI enabled MASS installation zone logic slightly changes from the logic described in 7.1.
In terms of Coverage Zones there is no difference at all.
In terms of Alarm/View zones following are the differences:
• When no alarm zone is defined in the system, all targets are displayed by default within the defined
coverage zones of the sensors.

• If at least one Alarm/View zone is defined in the system, only targets in this zone will be reported.
• If target filtering is applied within a zone, only targets that has been successfully classified will be
reported
To Apply Target Class Filtering in an Alarm/View Zone:
2. Move the cursor over the ALARM ZONES menu and click the icon to add a new zone, or
expand the menu, and click the next to an existing alarm zone to edit it.
3. On the bottom left of the screen the Edit Alarm Zone menu opens:
Figure 90: Edit Alarm Zone menu in AI Enabled MASS

4. Check the "Fliter by type" check box and check/uncheck the various classes to include/exclude
them from the alarm zone.

11. MASS GPS SENSOR “BLUE FORCE”
As of MASS 3.21.0 MASS supports the new “Blue Force” feature. The feature allows automatic
classification of “friendly”, predefined, targets in the MASS to avoid un-necessary alarms. For
example, this feature can be used to filter alarms caused by routine patrols of the security
personnel within the monitored area while maintaining protection against unwanted perpetrators.
The feature relies on GPS location readings from a device carried by the authorized
personnel/vehicle and correlates those to track location reported by the radar.
This feature requires 3 modules:
• GPS Gateway Server – a computer with the “GPS Gateway Server” installed on it.
• MASS Server – running MASS 3.21.0 or above, with network access to the GPS Gateway server
• Magos GPS Tracker application – an android device with a GPS sensor, running the Magos GPS
Tracker application, with network access (cellular or WiFi) to the GPS Gateway Server.
The following sections will review the 3 modules.
11.1 GPS GATEWAY SERVER

• Download and install the Magos GPS Gateway Server SW from the Magos partners portal:
https://partners.magosys.com/portal/downloads/
• Using the Windows Services panel ensure that the “MAGOS-GPS-Gateway” service is running
• Ensure that port 44300 is accessible, and that there is network access to the MASS server.
There are no specific HW requirements on the host machine. Operating system should be Windows 8
and above.
No additional configuration is needed.
11.2 MAGOS GPS TRACKER APPLICATION
Currently the HW requirements for the end device is that it is an Android machine with a GPS sensor.
In some cases, other OS and end devices might be supported – contact Magos Support team for more
information.
• Download and install the GPS Tracker Application Apk file from the Magos partners portal:
https://partners.magosys.com/portal/downloads/
The application requires permission to access device location.
• Run the App and tap the settings button ( ) on the top right of the screen.

Figure 91: Magos GPS APP Settings Screen
• Fill the fields as follows:

o IP: IP Address of the GPS Gateway Server.
o Port: use 44300. If this port is taken contact Magos Support for information on how to change
the GPS Gateway port.
o MASS ID: reserved.
o User Name: Any string that will be used to identify the person carrying this device on the
MASS
• Tap on the “back” ( )button to the main application screen.
Figure 92: Magos GPS APP Main Screen
• Tap the “Enable radio button to turn on the location reporting to the GPS gateway.

• The Screen includes the following indicators:
o Location Source: Should be “GPS+NETWORK+PASSIVE” for cellular devices or
“GPS+PASSIVE” for non-cellular devices
o Server status: “Connected” when location reporting is enabled and server is accessible;
“Disconnected” (red) when location reporting is enabled but server cannot be reached;
“Disconnected” (grey) when location reporting is disabled
o Target Location and Accuracy: Coordinates and location measurement accuracy as reported
by the location module in the device.
11.3 GPS SENSOR PLUGIN IN MASS SERVER
Once GPS Gateway server is installed and the GPS application has been installed on one or
more devices, the final step is enabling and configuring the GPS plugin within the MASS
software.
To Enable the GPS Plugin:
3. Click the Plugins tab, then click on the bottom right of the screen.
4. Check the GPS Manager plugin and click .
Figure 93: GPS Manager Plugin Configuration
5. The GPS Manager plugin configuration menu now appears in the Plugins tab.
6. Type the IP address of the GPS Gateway server in the Server WS url field.
7. Click the radio button to enable the plugin.
8. Click on the bottom of the screen and return to the MASS map view.
To Authorize GPS users as “friendly” targets:

10. To add a Radar, move the cursor over the GPS SENSORS menu and click the icon.

Figure 94: Add GPS Sensor Menu
11. The Add GPS Sensor menu will open. This menu lists all the devices that are currently connected
to the GPS Gateway server and are not yet authorized as “known” sensors (meaning devices that
have the Magos GPS Application installed and running)
12. Click the next to add each connected device to the “Known” sensors list, then click Yes. The
device will be removed from the candidates list, and will now appear under the GPS SENSORS list
in the settings bar.
Figure 95: GPS SENSORS List with authorized device
13. The GPS sensor information can now be accessed by moving the mouse over the sensor name
and clicking the button. Sensor info includes Name, State (Enabled/Disabled) and Status
(Connected/Disconnected).
Figure 96: GPS Sensor info
14. The GPS sensor can be edited moving the mouse over the sensor name and clicking the
button. The sensor can be enabled/disabled by clicking the Enable radio button. Click Save to
apply changes made.
Figure 97: GPS Sensor Edit Menu

15. To delete the GPS sensor for the list of known sensors, move the mouse over the sensor name and
click the button. Click Yes to conform in the pop-up menu.
To Configure GPS tracking Behavior:

18. Scroll down to the GPS Tracking section:
Figure 98: GPS Tracking Configuration Menu
19. The GPS Tracking configuration options include:

• Show Friendly Targets: When disabled, radar tracks that were correlated with a known
GPS sensor will not be displayed in the map view.
• Investigate Friendly Targets: Enable/Disable camera cueing on targets identified as
“friendly”.
• Alarm on Friendly Targets: Enable/Disable alarm event when a friendly target enters an
alarm zone.
• GPS Target Timeout: Elapsed time in seconds between sensor disconnection from the
Gateway until the GPS target will disappear from the MASS map view (and target will no
longer be declared as “friendly”).
• GPS Error Factor: This error factor is used when associating radar target with the GPS
location report. Larger value allows for larger difference in location between the radar track
and the GPS location when correlating the tracks and declaring a target as friendly.
Default value is 2.
“Friendly” Targets in the MASS map view:

20. If the Show Friendly Targets option is enabled in the GPS Tracking configuration options, then a
“friendly” target will be displayed in the MASS view as a radar track, with a different color (as
configured in the UI Settings tab in the System Configuration page) and the GPS Sensor name
next to the target head, as shown in Figure 99.
Figure 99: “Friendly” Target Display in MASS map View

12. GLOSSARY
Camera panning. A horizontal camera movement, in which the camera points left or right from a fixed
location such as a tripod.
Camera tilt. A vertical camera movement, in which the camera points up or down from a fixed location
such as a tripod.
Magos administrator. The highest permission level in MASS. A Magos administrator is authorized to
view the entire system and to carry out certain tasks that involve making changes to the
system.
Map caching. The process used for storing the map data locally on server. Such a configuration is ideal
for installations where the server’s connection to the Internet is of low bandwidth or non-
existent.
PTZ Auto-tracking. http://www.networkwebcams.com/ip-camera-learning-center/2008/06/16/cctv-ptz-

auto-tracking/
PTZ. http://www.networkwebcams.com/ip-camera-learning-center/2008/07/08/glossary-term-pan-tilt-
zoom-ptz/
Panning. http://www.networkwebcams.com/ip-camera-learning-center/2008/07/08/glossary-term-pan-
tilt-zoom-ptz/
PTZ Slew to Cue. “Slew to Cue” refers to the integration of a radar or other target detection device,
which instruct and electro-optic or infra-red surveillance PTZ camera where to point.
The detection sensor - a radar, in the case of MASS - is designed to detect the target
and pinpoint its location, then transmit that information to the PTZ camera which in turn
auto-tracks, identifies and recognizes the target. Slew to cue is considered the best
solution for long 24/7 security and surveillance, due to a radar's ability to provide 360-
degree coverage and detect vehicle-sized targets up to 40km away for marine, ground
or aerial targets day or night, even in bad weather conditions. The day/night PTZ
surveillance cameras can then recognize and identify the targets that are detected.
Tracks. Lines indicating the movement course (track) of a currently active target. The black dot at the
end of the line indicates the most current position of the target, as detected by the
radar. The color of the line matches the color assigned to the sensor that reported the
track.
Zooming. Zooming is the process of adjusting the focal length of a camera lens to make a subject
appear close or far away, based on the setting. Zooming is carried out by using a zoom
lens, as opposed to a fixed focal length (prime) lens.

13. INDEX
Area Properties menu options
integration with MASS, 10
area name, 69, 72
ONVIF profile S camera
cancel, 69, 72
supported hardware, 11
save, 69, 73
Open Street map, 22
Bing map, 22
panning, 23
camera
possible map sources
positioning cameras relevant to radars,
Bing map, 22
23
Google map, 22
Google map, 22
local map, 22
local map, 22
Open Street map, 22
Magos administrator
vertexes
login details, 13
adding a vertex, 71
MASS server application installation
adding by mouse clicks, 67
security warning, 14
discarding all vertexes, 68
resolving (pre-Windows 10 versions),
14 discarding the last vertex drawn, 68
resolving (Windows 10), 14 editing vetex positions, 71
Milestone zooming, 23

Mass 3.21 User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mass 3.21 User Guide

Uploaded by

Copyright:

Available Formats

MAGOS AREA

SUMMARY OF CHANGES ..................................................................................... VII

V3.1 July 2019 ....................................................................................................................... vii

V3.20 January 2020 ............................................................................................................... vii

V3.21 JUNE 2020 .................................................................................................................. vii

1. INTRODUCTION TO THIS GUIDE .................................................................... 8

1.1 Document Layout ....................................................................................................... 8

1.2 About Magos Systems ............................................................................................... 8

1.3 Referenced Documents ............................................................................................. 9

2. INSTALLING MASS ....................................................................................... 10

2.1 System Overview ....................................................................................................... 10

2.2 Installation Prerequisites ............................................................................................ 10

2.3 MASS Internal Permissions........................................................................................ 13

2.4 the Installation Process .............................................................................................. 13

3. GETTING STARTED ...................................................................................... 21

3.1 Launching the Application .......................................................................................... 21

3.2 Setup A Map View...................................................................................................... 21

3.3 Setting Up Sensors .................................................................................................... 23

3.4 Additional Steps ......................................................................................................... 35

4. MAP VIEW GENERAL OPERATIONS ............................................................... 36

4.1 Layers ........................................................................................................................ 36

Page i © Copyright 2017, Magos Systems. All Rights Reserved

4.3 Measurement tool ...................................................................................................... 40

4.4 Adding and Removing User-defined Presets ............................................................. 42

4.5 Miscellaneous ............................................................................................................ 43

4.6 System Health Panel.................................................................................................. 45

4.7 Keyboard Shortcuts .................................................................................................... 47

5. RADAR SENSOR ADVANCED SETTINGS ........................................................ 48

5.1 Radar Operation BackGround .................................................................................... 48

5.2 Adjusting Radar Specific Properties ........................................................................... 48

5.3 Threshold Schemes ................................................................................................... 50

5.4 Adjusting Tracker Parameters .................................................................................... 51

5.5 Adjusting Track Merging Parameters ......................................................................... 52

5.6 Fine Tuning radar Positions ....................................................................................... 53

6. CAMERA SENSOR ADVANCED SETTINGS ...................................................... 56

6.1 Camera Operation BackGround ................................................................................. 56

6.2 Adjusting Camera Behavior Properties ...................................................................... 57

6.3 Fine Tuning Camera Position and View ..................................................................... 59

7. PROFILES AND ZONES ................................................................................. 64

7.1 Zones Logic................................................................................................................ 64

7.2 Creating a Profile ....................................................................................................... 65

7.3 Defining and Editing and testing Alarm Zones ........................................................... 67

7.4 Defining and Editing Coverage Zones ........................................................................ 72

7.5 Profile Scheduler ........................................................................................................ 73

8. MAP VIEW ADVANCED SETTINGS.................................................................. 78

Page ii © Copyright 2017, Magos Systems. All Rights Reserved

8.2 Height Units................................................................................................................ 79

8.3 Overlay ....................................................................................................................... 79

9. CONFIGURATIONS SETTINGS ....................................................................... 80

9.1 System Backup and Info ............................................................................................ 80

9.2 General ...................................................................................................................... 81

9.4 Plugins ....................................................................................................................... 84

9.5 User Management...................................................................................................... 84

10. MASS+AI ..................................................................................................... 87

10.1 MASS+AI system Overview ....................................................................................... 87

10.2 Target Classification Process ..................................................................................... 89

10.3 Target Classes and Sub-Classes ............................................................................... 89

10.4 Target Class Display .................................................................................................. 89

10.5 AI Appliance Configuration ......................................................................................... 90

10.6 MASS+AI Zones ........................................................................................................ 91

11. GPS SENSOR ............................................................................................... 93

11.1 GPS Gateway Server ................................................................................................. 93

11.2 Magos GPS Tracker Application ................................................................................ 93