NEXTIVA 6.

4 VIDEO MANAGEMENT PLATFORM

TECHNICAL SPECIFICATIONS
SECURITY SYSTEM
DIVISION 28 ELECTRONIC SAFETY AND SECURITY
LEVEL 1__28 20 00 ELECTRONIC SURVEILLANCE
LEVEL 2__28 23 00 VIDEO SURVEILLANCE
LEVEL 3__28 23 13 VIDEO SURVEILLANCE CONTROL AND MANAGEMENT SYSTEMS
PART 2 PRODUCTS
2.01

GENERAL
A. All software components shall be part of the manufacturers standard software
product offering.
B. All software components shall be thoroughly tested and proven in reference
installations equal to or greater than the size and/or complexity of the Project.
C. The VMS shall be approved by the US Department of Homeland Security with a
Designation status in the SAFETY Act program.
D.

All software components shall be provided with the availability of a toll-free (US and
Canada) Technical Assistance Program (TAP) from the manufacturer. The TAP shall
allow for immediate technical assistance for the dealer/integrator/installer or for the
end user.

E. Each systems integrator designing, proposing, implementing, supporting or otherwise

participating in the maintenance, enhancement or upgrade of the VMS solution shall
hold factory certification on version being used or upgraded to by the end user.
F. The VMS manufacturer shall offer thedealer/integrator/installer and end user access
to a secure e-support website for Web-based technical information 24x7x365.
G.
2.2

The VMS manufacturer shall offer a variety of Service and Support plans.

VIDEO MANAGEMENT SOFTWARE (VMS) ARCHITECTURE

A. The VMS shall have a flexible, open video, over IP architecture built on accepted
industry standards that facilitate integration with IT infrastructures.
B. The VMS shall have a flexible, open architecture, and be able to migrate from a
single recorder or enterprise site into a multisite system, at any time.
C. The VMS shall have a flexible, open architecture built on accepted industry
standards that supports a Workgroup Microsoft Windows Environment.
D. The VMS shall have a flexible, open architecture built on accepted industry
standards that supports an Active Directory Domain Environment.
E. The VMS shall have a flexible, open architecture built on accepted industry
standards that supports Bi-directional Forest Support for Microsoft Windows
authentication, between a customer AD Forest and Nextiva AD Forest Environment.
F. The VMS shall have a flexible, open architecture built on accepted industry
standards that facilitates DNS/DHCP support for servers.
1

G. The VMS shall have a flexible, open architecture that supports unified workstation
logon, based on Microsoft Windows authentication.
H. The VMS shall be able to be installed in a Virtual Environment and be recognized by
VMware as VMware Ready.
I.

The recorders shall use standard Commercial Off-The-Shelf (COTS) server

technology and storage systems, including Dell, EMC, NetApp and Nexsan.

J.

The VMS shall have a flexible, open configuration architecture that facilitates NAT
Traversing for the Review application, WebReview, Mobile application and Client
Software Development Kit (SDK) connections.

K.

The VMS shall have a flexible, open configuration architecture that facilitates
Firewalls Traversing for the Review application, WebReview, Mobile application and
Client Software Development Kit (SDK) connections .

L. The VMS shall have a flexible configuration architecture that facilitates video
resolution transcoding, in order to stream video in a low bandwidth environment to
the Review, WebReview, Mobile, and Client SDK applications. VMS shall support
streaming video with bandwidth connections as low as 56 kbps.
M. The VMS shall have flexible throttling technology that facilitates video streaming
support for both software and hardware VPN, as well as for Review, WebReview,
Mobile, and Client SDK remote applications connections.
N. The VMS shall support Multiple NIC for Servers from different networks, which allows
Review, WebReview, Mobile, or Client SDK applications to reach the Video LAN.
O. The VMS shall offer redundancy solutions using the Marathon EverRun or VMWare
ESXi platforms. Three possible solutions shall be supported:
1. The solution shall be redundant, using two separate servers, and achieve a fault
tolerant, zero downtime environment.
(a) The solution shall provide a disaster recovery option, using a third separate
server at a secondary location which would assume primary responsibility in
the event of a catastrophic event at the primary location.
2. The solution shall be redundant, using two separate servers, and achieve a high
availability, minimal downtime environment. This design should not result in any
data loss, however may require manual or automatic start of the application on
the secondary server.
P. The VMS shall support multicast capability to allow client applications to receive live
streams from multicast groups through router instead of from camera or Recorder to
provide live streaming continuously even when Recorders or the Server become
unavailable, and to offload both cameras and recorders
Q. The recorder shall offer a redundancy solution using a Recorder Failover feature,
with distributed architecture that allows each subsystem to operate independently,
without affecting video recording or live viewing.

R. The recorder shall offer a redundancy solution using a Dual Recording features, with
distributed architecture that allows each subsystem to operate independently, without
affecting video recording or live viewing.
S.

The VMS shall possess an internal watchdog to detect and recover from the
unlikely occurrence of a system lockup.

T.

The VMS shall provide support for IP (network) cameras from multiple third-party
manufacturers using various codecs, including H.264, MPEG-4, and MJPEG.

U.

The VMS shall not use multiplexing or timed division technology for analog video
recording. All analog camera sources shall be digitally recorded as individual
streams.

V.

The VMS shall be able to support native video motion detection. This operation can
be executed by the edge device, the IP Camera or the server. Enabling motion
detection shall be performed either:
1. On a continuous basis
2. As scheduled for particular times, dates, days, months, etc.
3. For defined areas of interest, defined using an easy-to-use user interface and
simple editing tools
4. At a defined sensitivity level

W.

The VMS Server component shall support software designed for the Microsoft
Windows 2008 R2 or Windows 2012 server platforms (32 or 64 bit).

X.

The VMS Client component shall support Microsoft Windows 7, or Windows 8 (32
or 64 bit) operating systems for workstations.

Y.

The VMS shall be localization-ready and include support for Unicode characters,
including double-byte and extended characters.

Z.

The VMS shall support both single and multi-site deployments.

1. For multisite deployments, a multisite directory shall store information for all sites.
A copy of the multisite directory shall also reside on each site in the multisite
configuration, avoiding any single point of failure. In the event of a multisite
directory disconnection, each user shall still be able to execute multisite
functionality.
2. The VMS multisite system shall have the ability to simultaneously view multiple
cameras (live or recorded), alarms, bookmarks, and investigations, from any site,
with a single sign-on for authorized users.
3. Sites can cross connect as required at any time by a simple configuration with a
passkey.
4. The VMS shall have a flexible, open architecture that allows alarm event and
response creation, whether for a single site or multisite, through an event and
response manager that supports schedules and custom scripts.

2.3 VMS INTERFACES

3

A.
B.

The VMS shall support NTSC or PAL video standards interfaces

The VMS shall support third-party IP cameras from at least 10 different
manufacturers, using auto discovery functionality.

C. The VMS shall support a variety of video matrix switcher devices and PTZ cameras
from different manufacturers.
D. The VMS shall be Conformant to the ONVIF Profile S standard for Network Video
Client (NVC). The VMS shall be listed on the ONVIF.org web site list of conformant
NVC products.
E. The VMS shall support H.264, MPEG-4, and MJPEG compression from edge
devices and IP cameras on a camera-by-camera basis.
F. The VMS shall support H.264, MPEG-4, and MJPEG de-compression on the
Workstations.
G. The VMS shall support an asynchronous serial port for the RS-422 or RS-485 signal
levels that can be programmed for data rates of up to 230 kbps.
1. The RS-485 mode shall support 2-wire and 4-wire interfaces.
H. The VMS shall support an unlimited number of RS-232 asynchronous serial ports
that can be programmed for data rates of up to 230 kbps.
I.

The VMS shall support an unlimited number of dry-contact inputs.

J.

The VMS platform shall support an unlimited number of relays outputs.

K. The VMS shall be capable of supporting large organizations with systems at

hundreds of site locations, linked via LAN / WAN connections.
L. The Recorders shall use standard Ethernet connection for video input via
TCP/UDP/IP.
M. The VMS shall operate over a Local Area Network (LAN) / Wide Area Network
(WAN), using a standard Ethernet 100/1000 Base-T connection.
N. The VMS shall support either or both unicast or multicast over the enabled network.
O. The VMS shall transmit video using the UDP/IP or TCP/IP communication protocol.
P. The VMS shall transmit all command and control messages using the TCP/IP
protocol.
Q. The VMS shall generate alerts on disabled camera inputs based on loss of
communication signal or device being off-line.
R. The VMS shall support third-party keyboards via the Service SDK, which can be
used to develop adaptors for any third party CCTV Keyboard. The VMS shall support
the following frame rates on a camera-by-camera basis:
1. NTSC: 30, 15, 10, 7.5, 6, 5, 3.75, 3, 2, 1
2. PAL: 25, 12.5, 8.33, 6.25, 5, 4.16, 3.125, 2.08, 1
S. The VMS shall support the following video resolutions:

1. QCIF
2. CIF
3. 2CIF
4. VGA
5. 4CIF
6. HD720
7. HD1080
8. 2MP
9. 3MP
10. 5MP
11. 10MP
T. The VMS shall support additional PTZ keyboard camera commands such as:
1. Variable speed control of PTZ functionality
2. Manual iris and focus control
3. Call up patterns (store and retrieve)
4. Camera menu commands
5. Auxiliaries/advanced PTZ commands
6. Home position
7. Flip camera 180 degrees
2.4

VMS VIDEO DEVICE SUPPORT

A. The VMS shall support the following Verint/Nextiva Intelligent Edge Device,
Wireless, and IP cameras:
1. Single input encoders and decoders
2. Multiple input encoders:
3. Legacy Wireless edge devices:
B. The VMS shall be ONVIF profile S compliant
C. The VMS shall support third-party IP cameras from at least 10 different
manufacturers, using auto discovery functionality. Cameras supported should be
inclusive of, but not limited to the following brands:
i. Arecont
ii. Axis
iii. Bosch
iv. IQinVision
v. Mobotix
vi. Panasonic
5

vii. Pelco
viii. Samsung
ix. Sony
x. Verint
xi. HIK
xii. Canon
xiii. LG
xiv. XTS
xv. Scallop Imaging
D. The VMS shall support a variety of video matrix switcher devices and PTZ cameras
from different manufacturers.
E. The VMS third-party Analog PTZ cameras support shall be inclusive of but not limited
to the following brands:
1. American Dynamics SpeedDome, Ultra IV and up, SpeedDome Optima, Optima
LT, AD1641M, AD1696B, AD1694
2. Bosch (Phillips) AutoDome, BasicDome, EnviroDome
3. Checkpoint Clarity
4. Covi EVQ-1000
5. Honeywell KD6i
6. GE (Kalatel) CyberDome, CyberScout, Legend
7. Panasonic CS600, CD650, WV-CS574, WV-CS574, WV-CS954, WV-CS964,
WV-CS974
8. Pelco Spectra, DF and DD series, all cameras supporting Pelco P and Pelco D
protocol
9. Vicon Surveyor 2000
F. The VMS shall upoort HID compliant PTZ Joysticks
1. The following models have been tested and qualified
i.

Axis T8311

ii. VideoTec DCZ

G. The VMS shall integrate with the following third party CCTV Keyboards to provide
command and control of associated devices:
1. American Dynamics AD2078, AD 2078A, AD2079, AD2088, AD2089, ADCC0200
(RS-232 Mode ONLY), ADCC0300 (RS-232 Mode ONLY), ADCC1100 Control
Center, ADTTE Touch Tracker
2. Bosch LTC-5136
3. Honeywell KEGS5300, RD-530
4. Pelco KBD300A, 9760
5. Vicon V1411J-DVC , V1300x-DVC
6

H. The VMS shall integrate with the following matrix switches to provide command and
control of associated devices, camera to monitor call up, and access to matrix switch
functionality:
1. American Dynamics MegaPower 2050/1024
2. American Dynamics MegaPower LT: ADMPLT16, ADMPLT32
3. American Dynamics MegaPower 48 Plus: ADMP48-E
4. American Dynamics MegaPower 48: VR48
5. American Dynamics AD2150 System V
6. American Dynamics MegaPower 168
7. American Dynamics MegaPower 3200
8. Bosch LTC8x00
9. Pelco 9740/ 9760
2.5

VMS SERVER COMPONENTS

A. Master Server
1. The VMS Master Server shall maintain cohesive operations of all of the
components in the video management system, including the VMS database.
2. The VMS Master Server shall support up to 2,000 cameras and/or encoder
channels on a single recommended Server. Multiple servers may be used to
support a larger number of cameras.
3. A single Master Server shall support up to 100 servers used as Recorders,
Enterprise Storage Manager (ESM) servers, Media Gateways, or Surveillance
Analytics servers.
4. Each individual Master Server shall support a maximum of 80 Review
application workstations simultaneously. To achieve a system configuration
greater than 80 Review application workstations multiple servers may be used.In
a multi server server configuration the maximum number of Review workstations
is unlimited.
5. A single Master Server shall support up to 300 live video tiles simultaneously.
Multiple servers may be used to support an unlimited number of tiles.
6. The Master Server shall be hosted on a COTS computer server, from a leading
manufacturers (including IBM, Lenovo, Hewlett-Packard and Dell); with
processors at minimum speed of 2.8 GHz from a leading manufacturer (including
Intel or AMD); with a hard-disk drive at minimum storage capacity of 250GB; and
a network-interface card with a minimum speed of 1GBPS.

B.

Recorder
1. The VMS Recorders shall be certified with optional EMC storage solutions.
2. The VMS Recorders shall be certified to record in a VMware environment.

3. The VMS Recorder Server shall have the ability to run Master Server functions,
including the Recording and Review applications simultaneously for cost-effective
deployments.
4. The Recorder shall run autonomously, and continue to record once configuration
is received.
5. The Recorder shall offer a fail-over solution, either to another recorder or group
of recorders, dynamically, and without any user intervention.
6. The VMS Recorder Server shall have the ability to simultaneously record 200
streams, at 2CIF @ 30 FPS or 4CIF @ 15 FPS, with an H.264 resolution.
7. The VMS Recorders shall store video on COTS computer server, from a leading
manufacturer (including IBM, Lenovo, Hewlett-Packard and Dell); with
processors at minimum speed of 2.8 GHz from a leading manufacturer (including
Intel or AMD); with a a network-interface card with a minimum speed of 1GBPS.
Hard-disk drive requirements should be identified during the system design
preparations and be aligned accordingly.
8. The recorders shall be capable of supporting the attachment of external storage
devices via SAN, NAS, SAS, iSCSI or Fibre Channel, and other server
manufacturer supported interfaces..
C. Enterprise Storage Manager (ESM)
1. The ESM shall accept video files from multiple recorders for redundant, off-site,
or long-term storage.
2. The ESM shall allow for the support of long-term video storage, using hard drives
as the storage medium. It shall support virtually any central disk storage device,
including disk arrays with iSCSI connectivity,Storage Area Network (SAN) and
Network-Attached Storage (NAS) devices.
3. The ESM shall be capable of offering long-term video storage using COTS
equipment with processors such as Intel or AMD.
D.

Media Gateway Server

1. The Media Gateway Server shall transcode received video from IP cameras or
edge devices at a certain resolution, and then convert, and send a lower
resolution video through a bandwidth limited WAN link.
2. The Media Gateway shall support bandwidth as low as 56 kb/s for remote
viewing through Nextiva WebReview, and 256 kb/s through Nextiva Review.
3. The Media Gateway shall properly packetize video to transverse NATs and
firewalls using IP, with a maximum of 2 ports.
4. The Media Gateway shall support Review application User Priorities, in case
multiple remote requests for video by Review users exceed the bandwidth of the
WAN/LAN link.

5. The Media Gateway shall be capable of running all video transcoding, pass
through, and WAN transport services, using COTS equipment with processors
such as Intel or AMD.
E.

Multisite Server (MSS)

1. The Multisite Server shall maintain a directory of sites that are part of the
multisite configuration. The MSS shall use COTS equipment with processors
such as Intel or AMD.
2. The MSS shall be a central database that contains data required from each site,
for the purpose of sharing resources with other sites. All sites that are part of a
multisite deployment shall join MSS. MSS shall either co-exist on a Master
Server or Recorder, or run on a standalone server if requirement for multisite
deployment consists of 10 sites or more.

2.6

VMS CLIENT COMPONENTS

A. Control Center Client Application

1. The VMS shall provide a Control Center client application, designed for system
administrators to configure cameras, recorders, schedules, users, and system
functions.
2. The PC workstation used to operate the Control Center application shall use
COTS equipment with processors such as Intel or AMD.
B. Review Client Application
1. The VMS shall provide a Review client application, designed for operators to
operate and view live/recorded video.
3. The PC workstation used to operate the Review application shall use equipment
from a leading manufacturer (including IBM, Lenovo, Hewlett-Packard and Dell);
with processors at minimum speed of 2.8 GHz from a leading manufacturer
(including Intel or AMD); with a network-interface card with a minimum speed of
1GBPS; with a hard-disk drive with a minimum capacity of 250GB; with a highend video card with 128MB RAM, 1024 x 768 screen resolution and highest 32bit color quality from a leading manufacturer (including ATI, nVidia and Matrox.)
C. WebReview Client Application
1. The VMS shall provide an ultra thin, secured WebReview client application,
designed for viewing by corporate personnel or other investigators.
i. The WebReview download with ActiveX shall be less than 3.5MB.
2. The PC workstation used to operate the WebReview application shall use
equipment from a leading manufacturer (including IBM, Lenovo, Hewlett-Packard
and Dell); with processors at minimum speed of 2.8 GHz from a leading
manufacturer (including Intel or AMD); with a network-interface card with a
minimum speed of 1GBPS; with a hard-disk drive with a minimum capacity of
9

250GB; with a high-end video card with 128MB RAM, 1024 x 768 screen
resolution and highest 32-bit color quality from a leading manufacturer (including
ATI, nVidia and Matrox.)
D. Mobile Client Application
1. The VMS shall provide a Mobile Client Application via WiFi, 3G or 4G networks
i. The Mobile Client shall have secure login and authentication (RSA
encryption)
ii. The Mobile Client shall utilize live transcoding to low-bandwidth H.264
streaming in 4CIF resolution and lower
2. The VMS Mobile Client Application shall utilize the Apple iOS mobile operating
system
i. The Mobile Client shall feature an interface tailored to the Apple iOS user
experience and allow users familiar with iOS usability to use direct
manipulation and multi-touch gestures similar to other applications
supported on iOS
ii. The Mobile Client shall be featured and accessible for download for use
on Apple iPad or iPhone devices

2.7

VMS FUNCTIONS
A. Control Center Client Application
1. The VMS shall have a Control Center graphical user interface (GUI) that allows
the user to efficiently configure and apply the following parameters, and perform
the following procedures:
i. All camera configurations
ii. All recorder configurations
iii. All work schedules
iv. User and access rights and privileges, including rights for multisite
configuration
v. Create schedules and apply them to specific camera groups
vi. Configure cameras and recorders individually, and as a group, in system
components
vii. Preconfigure camera profiles (containing video quality configurations) to
be managed and distributed as required in user defined logical groups
2. The user shall have the ability to add and edit interactive site plans and maps.
3. Control Center shall be controlled by access rights assigned by the system
administrator, including:
i. Full access to all functions
ii. Limited to system configuration only
iii. Limited to Health Check viewing only
4. Control Center shall have the capability to automatically discover and perform
initial IP camera configurations.

10

5. The VMS shall provide a health check single point of control mechanism to
monitor operations and track system performance.
6. The VMS shall provide audit trails of activities performed in the system.
7. Control Center shall have the capability to provide a dashboard, with status
information of each recorder that is part of a Master Server configuration.
B. Review Client Application
1. The VMS shall have a video viewing graphical user interface (GUI) that allows
users to view live video, retrieve recorded video, and export video from a
workstation PC.
2. The VMS Review application shall enable users to manage multiple windows and
perform multiple tasks simultaneously. The VMS Review application includes the
following functionality:
i. The ability to select time preference format: AM/PM or 24H
ii. A quick video query button
iii. Hot function keys
iv. Configurable playback speed in multiple increments up to 100x
v. The ability to retain time between queries
vi. The ability to view live or recorded video in multiple windows, including
video from multiple Digital Video Recorders and multiple sites
vii. Variable speed PTZ camera control (camera dependant)
viii. The ability to lock the PTZ control for a camera, depending on user rights
and priority levels
ix. The ability to take-over a PTZ function, depending on user rights and
priority levels
x. The ability to export video to digital media output devices, such as a CD,
DVD, Blu-ray disk, and USB thumb drive, and to manage the exported
files via an exported queue, depending on user rights.
xi. The ability to submit and manage multiple requests for video
xii. Support for time synchronized video playback on up to 16 windows
simultaneously
xiii. Support for camera groups and maps that provide a video preview of the
camera and alarm indication
xiv. Support for camera presets in a user-defined, multi-level tree structure.
The following guidelines shall apply:
1. Each group has a user-defined name and user-defined contents
2. Cross-site monitor trees are supported for multisite environments
3. A group can contain cameras and/or other groups
4. Users can define multiple levels of groups and maps
5. A camera can be included in more than one group.
11

6. Users can select or drag-and-drop individual cameras to request

video for playback or to open live video windows.
xv. Guard Tours display sequential views of predefined workspaces created
by the operator in the Review application, for specified periods of time.
xvi. Allow to synchronize playbacks video
xvii. Store the recent played video for quick playing
xviii. Support ImmerVision (360 degree panoramic lens) camera viewing
xix. Allow to track an object and to store its tracked coordinates
xx. Allow to designate and object and to view all cameras that the object is in
their field of view
xxi. Support CCTV virtual keyboard to control live and playback videos in a
video wall as well as PTZ cameras
xxii. Ability to select playback played video from a recent playbacks list
xxiii. Support for adaptive remote viewing where cameras can be viewed at
anoptimum bandwidth and resolution setting based upon the clients
specific operational requirements. Adaptive remote viewing supports the
ability to select on-the-fly, multiple levels of viewing quality in any given
camera view window to achieve an economical usage of available
bandwith or depedning on defined triggers, a low resolution view can be
instantly brought up to a higher resolution required to address the event
or provide forensic evidence.
3. The VMS shall allow the user to open, move, and size multiple, independent
video windows as needed, including:
i. Single windows
ii. 2 x 2: 4 (quad) windows, arranged in two rows of two windows each
iii. 5 x1 window, arranged in one large window, surrounded by multiple tiles
iv. 3 x 3: 9 windows, arranged in three rows of three windows each
v. 4 x 4: 16 windows, arranged in four rows of four windows each
vi. A maximum layout of 8x8 windows
vii. Dynamic, flexible, and customizable layouts, including color skinning
viii. Up to 4 screens per workstations, for a maximum of 256 tiles @ CIF/5fps
ix. HD 16:9 support
4. The VMS shall support the ability to preserve aspect ratio.
5. The VMS shall support digital zoom on live or recorded video, without requiring a
video pause.
6. The VMS shall enable/disable video de-interlacing.
7. The VMS shall offer Virtual Matrix capabilities.

12

i. Enable control of CCTV equipment, such as CCTV keyboards and PTZ

cameras, and create virtual matrices to distribute live and recorded
video, audio, and alarms to monitors across Local and Wide Area
Networks (LANs/WANs).
8. Image Toolkit software shall include the following capabilities:
i. Adding the date and time to the image
ii. Adding text annotations to the image
iii. Copying the image to the clipboard so that it can be pasted into other
applications
iv. Printing the image
v. Saving the image to disk in various standard file formats
vi. Adjusting the brightness and/or contrast of the image
vii. Converting a color image to grayscale
viii. Applying filters to the image to smooth or sharpen
ix. Applying edge detection to highlight borders and surfaces of objects
within the image
9. The VMS Review application shall allow users to select any or all video tiles
including live and recorded video for export from a precise user selectable start
and end time with a single mouse click. The user shall also have the option to
rename the target file name.
10. The VMS shall offer Investigation Management capabilities, including:
i. The ability to create an investigation from any multiple remote and local
sites, depending on access rights
ii. The ability to include the following attachment types in the investigation
binder:
1. Live and recorded video
2. Alarm video
3. External files
4. Still images
5. Video currently playing in the workspace
6. Existing investigations
iii. The ability to include explanatory notes in the investigation binder.
iv. The ability to access and edit Investigations, depending on access right
permissions.
v. The ability to perform Investigation Management searches.
vi. The ability to export Investigations and their attachments.
11. The VMS shall provide a default digital certificate (MD5) for signing exported
video clips.
13

12. The VMS shall export an image in Windows Bitmap format.

13. The VMS shall export an image in JPEG (Joint Photographic Experts Group)
format.
14. The VMS shall enable users to open live video windows, relative to the monitor
capacity
i. Support serial or quad view
ii. Allow up to three (3) additional monitors to be configured per Review
client to enable additional viewing capacity
15. The VMS shall enable users to view live video from multiple digital recorders and
sites.
16. The VMS shall enable users to request video from one camera, or a group of
cameras, at a specified date and time, and for a specified duration, including the
following functionality:
i. Drag-and-drop camera selection from the camera tree
ii. Typical calendar control to ease selection of the year, month, and day
iii. Time and duration specification by data entry or by dragging the mouse
over a time range
iv. Video requests default to the last five minutes of video from the selected
camera or group
v. View live or historical alarm events and associated video.
17. The VMS shall support attaching video to documents, such as incident reports,
and ease retrieval of reports and associated video.
i. Exported video format is .AVI
18. The VMS shall support video request processing.
19. The VMS shall support video playback controls, including:
i. Buttons to start and stop playback from the current video position
ii. Buttons to step forward or backward through the video in single time
increments
iii. Buttons to step forward or backward through the video in single frame
increments
iv. Buttons to step forward or backward through the video in multiple frame
increments
v. Button for moving through video in reverse
vi. Ability to cause video to loop continuously
vii. Positioning controls, including a slider bar and buttons to quickly and
conveniently position to the beginning, end, or any other time in the
video clip
viii. Speed control, using a slider bar to control the rate of playback

14

20. The VMS shall support scanning recorded video for activity using an energy
graph that indicates activity levels.
21. The VMS shall support scanning recorded video for motion in all or specific Areas
of Interest, and shall have the ability to set the motion sensitivity and sampling
time.
22. The VMS shall authenticate video, enabling users to verify that the video has not
been modified since it was recorded.
23. The VMS shall have live video windows consistent with video playback windows
in appearance and operation.
24. The VMS shall control PTZ cameras.
25. The VMS shall allow the entire live video window to be a mouse-sensitive area
for PTZ control.
26. The VMS shall provide an optional heads up display (HUD), which supports
layering a PTZ control user interface over the video, providing a visual indication
of the window areas that control zoom, focus, and iris functions.
27. The VMS shall support camera presets by providing a toolbar, or other GUI
method, for working with camera presets when viewing live video from a PTZ
camera.
28. The VMS shall provide the ability to view camera tours through a graphical, iconbased user interface.
29. The VMS shall allow the user to access a calendar view to query by month, day,
and year, and by hour, minute, and second.
30. The VMS shall allow the user to access a hierarchical tree to manage the icons
that represent cameras.
31. The VMS shall allow hovering from the camera list to preview the camera window
in real-time.
32. The VMS shall provide auto-play alarm tiles and workspaces.
33. The VMS shall allow users to pin alarms to tiles, which keeps the alarm on the
tile until it is acknowledged.
34. The VMS shall allow administrators to configure access rights and privileges for
every user. The configured user access rights and privileges will apply when the
user logs on to any workstation.
35. Review application operations shall be able to be restricted. It shall be possible to
restrict or enable the following functionality:
i. Live video
ii. PTZ control
iii. Assigning PTZ priorities for take-over functionality
iv. Digital zoom
15

v. Camera menu
vi. Recorded video
vii. Export video
viii. Investigation management
ix. Alarm notification, alarm viewing, alarm history
x. Cameras
xi. Tours
xii. Salvos
xiii. Maps
xiv. Sites
xv. Remote viewing access
xvi. Remote Viewing maximum bandwidth
xvii. Remote viewing priority
36. The VMS shall allow users to select the following pattern functionalities:
i. Configure PTZ presets
ii. Call-up camera patterns
iii. Record patterns
iv. Stop recording pattern
37. The VMS shall allow users to directly access internal camera menus that comply
with supported protocols.
38. The VMS shall allow users to define, save, and call up PTZ presets, patterns,
and virtual guard tours as supported by the camera manufacturer.
C. WebReview Client Application
1. The VMS shall provide a thin secured client with a look and feel that is consistent
with the Review application for remote video viewing, to reduce training and
improve usability.
2. The WebReview application shall be operational with bandwidth as low as
56kbps.
3. WebReview capabilities shall be:
i. Live and video playback
ii. Display of alarms and auto-play
iii. Bookmarks
iv. Tours, camera presets, PTZ
v. Up to 16 tiles (4X4 layout) support

16

4. WebReview shall permit exporting video clips.

5. Users must log in to access WebReview. User logon is dependent on user rights
and priorities.
6. WebReview shall use the RTSP/RTP protocols to allow secure remote access to
video streaming.
D. Mobile Client Application
1. The VMS Mobile Client shall allow VMS users familiar capabilities, including:
i. Live or playback video viewing (one of more cameras)
ii. Camera selection using filters and favorites
iii. Digital zooming
E. Keyboard / Joysick Access Privileges and Rights
1. Each CCTV keyboard / joysick shall be assigned to a user group. Once assigned
to a user group, the keyboard shall inherit the access and rights as defined for
that user group.
i. Commands, cameras, and monitors shall be available to the keyboard
depending on the user group access rights.
ii. Users will have the ability to lock a PTZ camera in a specific position,
preventing other users from moving the camera to another position.
F. Client Software Development Kit
1. Access Privileges and User Rights
i. The Client SDK shall be controlled by access rights and privileges
assigned by the system administrator, including:
1. Live video
2. PTZ control
3. PTZ priorities
4. Camera menu
5. Recorded video
6. Export video
7. Investigation management
8. Alarm notification, alarm viewing, alarm history
9. Cameras
10. Tours
11. Salvos
12. Maps
13. Sites
14. Remote viewing access

17

15. Remote viewing maximum bandwidth

16. Remote viewing priority
17. Bi-directional bookmarks
18. Activity scan energy graph
19. Audit for SDK client functionality and use
2. Integration with Physical Security
i. The VMS shall have certified integration with Physical Access Control
Systems (PACS)
ii. The VMS shall have certified integration with Physical Security
Information Management (PSIM) systems
G. Analytics Functions
1. The VMS analytics solution shall be a flexible architecture that allows use of
analytics algorithms on IP cameras as well as encoders. The VMS analytics
solution shall provide options for edge based, server based analysis and hybrid
analysis .

2. Edge Analytics processing shall be capable of decompressing and analyzing

behaviors 100% on the edge. Each device shall be capable of multiple analytics
simultaneously
3. Hybrid Analytics processing shall allow the use of tested compatible IP Cameras.
The Hybrid analytics solution shall process video at the edge and send low
bandwidth generic feature data to a central server for behavior analysis. The
central server shall handle up to 400 analytics sensors simultaneously. Each
hybrid analytics sensor shall be capable of simultaneously running multiple
analytics rules per sensor.
4. Server based analytics shall be flexible enough to analyze streams from any
camera being recorded by the VMS system. The Analytics server shall be
capable of decoding and analyzing meta data from up to 120 streams per
physical computing host
5. The VMS analytics shall support the visual Retail Analytics Application (RTA) for
density, people tracking, and counting for statistical analysis.
6. The VMS shall provide the ability to acquire and track an object within a
predefined field of view, on selected cameras.
7. The VMS shall support object-based algorithms, and shall provide the following
functionality:
i. Learn the scene
ii. Detect and track objects
iii. Adapt to a changing outdoor environment

18

iv. Ignore environmental changes including rain, hail, wind, swaying trees,
and gradual light changes
v. Classify objects
vi. Detect tripwire events
vii. Detect multi-line tripwire events
viii. Detect enters, exits, appears, disappears, inside of, loitering,
leave behind, and taken away events
ix. Detect scene change events
x. Create object size and size change filters
8. The VMS shall be able to combine object tracking with object classification,
allowing detection of specific objects in a region of interest, while ignoring other
object types.
9. The VMS shall support alarm generation and other actions, based on the VMS
rule engine for when an object is detected, classified, and tracked.
10. The VMS shall support 3rd party facial recognition analytics and initiate an alarm
event when a specific face is recognized from a user deined pre-configured list
during a live video feed or in post event forensic analisys.
11. The VMS shall support 3rd party License Plate Recognition analytics and initiate
an alarm event when a specific licence number is recognized from a user defined
pre-configured list during a live video feed or in post event forensic analisys.
H. Virtual Matrix
1. The VMS shall automatically distribute live and recorded video to video walls
(analog or digital) via decoders across dispersed user locations in a bandwidthefficient manner, effectively replacing the most commonly used features of legacy
cross-point matrices.
2. The VMS virtual matrix shall have the ability to send alarms and events, live and
recorded, across multiple sites.
3. The Virtual Matrix shall have the capability to interface with video walls via a
CCTV keyboard connected to a decoder.
4. The Virtual Matrix shall have the ability to play back a video sequence on an
analog monitor when an alarm or event is activated. The length of the playback
sequence shall be configurable, and may include pre- and post-video. This can
also be done across multiple sites.
5. The Virtual Matrix shall have the capability of creating camera sequences with
the following functionality:
i. Each sequence shall support up to 100 cameras.
ii. Each camera in the sequence shall have its own individual dwell time,
from 1 to 60 seconds.
iii. Each entry in a sequence shall have the capacity to trigger camera
presets.
19

iv. Multiple users shall be able to view the same camera sequence
simultaneously. Users viewing the same sequence simultaneously can
pause and re-start the sequence without affecting other viewers.
v. Operators shall be able to use an integrated CCTV keyboard to control
pan-tilt-zoom, iris, focus, dome relays, and dome presets to an analog
monitor.
vi. The VMS shall enable users to assign cameras to monitors by attaching
any adapted CCTV keyboard using the following methods:
1. Select a camera from the camera tree in the Control Center onto
an associated monitor
2. Enter a camera number from the keyboard
3. Enable the user to switch between monitor views on the analog
monitors by using the specified keyboard buttons for multiple
cameras
4. Provide a function to start a tour that can be programmed
through the CCTV keyboard
vii. The VMS shall support
comprehensive features:

camera

tours,

including

the

following

1. Configuration functionality enabling authorized users to view and

modify camera tour definitions
2. Configuration functionality to enable authorized users to take
over or lock out other lower priority users
3. Multiple camera tour and salvos creation
4. Multiple camera support for each camera tour
5. Preset and dwell time definitions supported for each camera
6. Dwell time definition for all cameras in a single operation
7. Multisite support using the Verint HDR1800
viii. The VMS shall have the ability for keyboard users to call up a camera to
their local monitors from any site.
ix. The VMS shall have the ability to call up a camera from the Review
application to a physical monitor using a send to monitor function.
I.

Event Management
1. The VMS shall have a rule-based engine with powerful analytics capabilities that
provides the following actions as responses to events and behaviors, including
events that occur on one site and responses triggered on another site:
i. Automatic event notification
ii. Video distribution
iii. Process activation
2. Triggering responses shall be addressed on the following:
i. when an event occurs
20

ii. When two events occur within a specific time span

iii. When two identical and consecutive events occurs without another
specific event occuring between the two
iv. When one event occurs without another event within a specific time span

3. The automated responses to behaviors shall be:

i. Trigger an alarm with 20 different alarms priority, assigned to different
users or monitors
ii. E-mail notification
iii. Assign a camera to a monitor
iv. Change output relay state
v. Call a camera preset
vi. Run a camera pattern
vii. Record on event
viii. Invoke an external application
ix. Generate Web feed item
x. Output alarms to the Client SDK interface
J.

Video Recording
1. The VMS Recorder shall be capable of performing multiple tasks simultaneously,
and, provided hardware configuration and software setup guidelines are followed,
no task shall interfere with any other task.
2. The VMS shall be able to perform the following tasks simultaneously:
i. Digitizing and compressing video, and calculating digital signatures for
video authentication
ii. Writing video to files on local hard disks and maintaining an accurate
index of the stored video files
iii. Deleting older video files as needed, freeing up space to record newer
video files
iv. Selectively transferring recorded video to long-term storage media
3. The VMS shall be capable of supporting dual streaming live or recorded video in
different resolutions or frame rates.The VMS shall be capable of performing the
following tasks related to alarms:
i. Executing video image analysis algorithms, including activity detection
and video loss detection
ii. Receiving signals from alarm inputs and generating alarm messages
iii. Processing alarm response instructions including calling, changing
recording modes, and controlling alarm relay outputs
21

iv. Forwarding alarms to a Review workstation, analog video monitor, or

video wall
4. The VMS shall be capable of performing the following tasks and shall support the
following recording modes:
i. Continuous recording. In the simplest mode, the Digital Video Recorder
units must record video 24 hours per day, 7 days per week, or as per
user defined schedules.
ii. Event recording.
iii. Augment the recording quality based on an event.
5. The VMS shall be capable of supporting scheduled recording, enabling system
administrators to:
i. Establish recording schedules based on hours of the day and days of the
week
ii. Specify the times during which each camera will be recorded, along with
the recorder settings to be used during each period, including the frame
rate, resolution, and quality settings
iii. Define alarms or event responses, including instructions to trigger
recording specified cameras at specified frame rates, and quality
settings. Alarm responses shall include the following recording
capabilities:
1. Start recording camera not currently being recorded.
2. Supplement continuous scheduled or event recording by
changing the recording mode or triggering recording of the same
camera, on a different recorder in a different video format. For
example, the VMS may be configured to record cost-effective,
low frame rate video during non-alarm periods, and then start
recording on high frame rate real-time recorders in response to
alarm events.
iv. Selectively copy video to long-term storage or redundancy on archiving
storage. System administrators shall be able to determine whether video
will be retained on long-term storage media, for each continuous or
scheduled recording instruction.
v. Automatically retain video on long-term storage media when video is
recorded as part of a defined response to an alarm event.
vi. Perform activity recording. The VMS shall support an event recording
mode designed for handling activity detection events during periods
when frequent activity is expected, but does not constitute an alarm
event. Activity detection events shall be handled internally by the Digital
Video Recorders instead of triggering an alarm response. This mode
preserves online video storage space by only retaining video in which
activity has been detected.
6. The VMS shall be capable of supporting multiple recorders, including the ability
to:
i. Add, modify, and remove recorders from the system
22

ii. Perform failover of recorders

iii. Perform dual recording from one camera source
iv. Apply global recorder settings or edit existing individual recorder
properties
v. Define recording modes: centralized and distributed
vi. Associate cameras, recorders, and schedule assignments
7. The VMS shall support failover recording.
i. The failover recorder shall act as a hot standby, ready to take over the
functions of a primary Recorder. No action from the user shall be
required.
8. The VMS shall support dual recording.
9. The VMS shall offer redundant recording which covers: Continuous recording
during a recorder server failure (and access to recorded video) and or Recording
in two different locations to address a catastrophic event by providing a
simultaneous recording by two recorders, with independent (non-shared) video
storageEnterprise Storage Manager (ESM)
i. The VMS shall offer ESM servers for supporting long-term or off-site
storage to any central disk storage device. It shall support any central
disk storage device, including disk arrays with iSCSI connectivity and
Storage Area Network (SAN) devices.
ii. The VMS ESM shall dynamically delete (groom) extraneous video from
hard drives to make space for newer incoming video, based on specific
retention parameters, while recognizing and preserving video clips
marked by the system as important.
iii. The VMS shall seamlessly locate any requested video stored on disks or
ESM servers, from any Review workstation.
iv. The VMS ESM shall automatically copy requested video from near online
storage to online (disk) storage, easing video playback. When the user
has finished reviewing the video, the VMS ESM shall retain the online
copy of the video to expedite processing of any subsequent requests for
the same video.
K. Alarm Configuration
1. The VMS shall process alarms from a variety of alarm sources. Each type of
alarm source shall have an OFF state (normal) and an ON state (triggered).
The VMS shall monitor the state of alarm sources and generate alarm messages
based on state changes.
2. The VMS system components shall provide alarm contacts to receive signals
from electrical devices. Contacts are configurable as normally open or normally
closed.

23

3. The VMS shall be capable of generating an alarm based on video image

analysis, detecting activity through motion detection or object recognition in the
areas of interest, or directional vectors. The absence of activity shall correspond
to the OFF state of the alarm source; when activity is detected, the state of the
alarm source shall be ON.
4. The VMS shall be capable of providing a way to define the areas of interest for
activity detection for specific cameras.
5. The VMS shall be capable of enabling configurable activity detection sensitivity.
6. The VMS shall be capable of generating alarms when video loss is detected from
the devices due to lost camera signals.
L. Alarm Responses
1. The VMS shall be able to configure scheduled alarm sources and responses,
depending on the time of day and/or day of the week.
2. The alarm response shall consist of various types of instructions, to be executed
by the VMS in response to an alarm message that can be generated by an alarm
source.
3. The VMS shall support recording instructions for starting recording, or changing
the recording mode, for one or more cameras connected to one or more
Recorders.
4. The VMS shall support relay output instructions for controlling the state of one or
more alarm relay outputs on Recorders, or other system components such as
edge devices or IP cameras.
5. The VMS shall trigger contact closures on edge devices or IP cameras that are
hardware equipped with this capability.
6. The VMS shall be able to display text messages to users at the alarm monitoring
station.
7. The VMS shall be able to display/send an alarm message to the Application
Programming Interface for the Client SDK.
M. Video Storage Recorder Management
1. The VMS shall be capable of managing online recorder storage. Storage shall be
intelligently managed so that the video most likely to be requested by users will
be retained online.
2. The VMS shall be capable of immediate storage on local hard disks.
3. The VMS shall be capable of circular overwrites, and online storage on the
recorder units shall be managed on a continuous circular overwrite basis.
4. The VMS shall be capable of event recording and selective online storage.
5. The VMS shall be capable of retaining non-event video online for a minimum
amount of time, depending on the recorder hard disk space.

24

6. The VMS shall be capable of retaining video online after transferring it to longterm storage (ESM). Video shall be retained online on the recorder to support
immediate playback, even if the video has been successfully copied to long-term
storage media.
N. Managing Long-Term Storage and Archiving
1. The VMS shall support automatic long term storage with the ESM.
2. Long-term storage shall be implemented using separate storage attachments.
3. The VMS shall support multiple long-term storage devices.
4. The VMS shall be capable of independent operations between storage servers.
5. The VMS shall be capable of immediate transfer to long-term storage.
6. The VMS shall support the ability to catch up after storage server downtime. If a
storage server must be taken out of service temporarily for maintenance, the
VMS shall retain video designated for long-term storage online on Recorders.
When the storage server is placed back in service, it shall transfer video data to
long-term storage faster than the rate at which new video is being recorded.
7. The VMS shall be capable of variable retention times, i.e., it shall support the
segmentation of cameras into groups based on the video retention requirements,
so that video is retained for some cameras longer than for others.
O. Archived and Bookmarked Video
1. The VMS shall allow disks to be reserved for video archiving.
2. The VMS shall support copying bookmarked video to the appropriate archive
storage media, and ensure that the video will not be overwritten or deleted for the
specified number of days.
3. The VMS shall allow any video clip attached to an investigation to be
automatically archived. The default video retention time shall be 60 days. This
retention period can be modified by the system administrator.
4. The VMS shall allow database queries to find reports, view reports, and export an
HTML page with the ability to attach video clips and still images to a report.
P.

Health Check
1. The VMS shall provide a Health Check application for live monitoring and
detailed system performance metrics on system components, including all
server-side software applications, including video recorder software.
2. The VMS shall provide a Health Check application for live monitoring and
detailed system performance metrics on edge devices, and IP cameras.
3. The VMS shall be capable of exporting performance analysis results.
4. The VMS shall offer a user interface designed to enable the management of the
following:
i. System logs
25

ii. System alerts

iii. Audit trail
iv. Performance
v. Recorder sanity, through a dashboard Redirection to various outputs,
such as Windows event logs and e-mail
5. The VMS shall be capable of capturing real-time performance analysis.
Q. Maps
1. The VMS shall support the mapping functionality, where digital maps are used to
represent the physical location of cameras and other devices throughout the
surveillance system.
2. Maps shall have the ability to contain hyperlinks used to create a hierarchy of
interlinked maps.
3. The mapping functionality shall be able to import maps from any graphical
software supporting BMP, JPEG, or GIF image formats.
4. Once a map is integrated, it can be viewed in the Review application.
R. Audio
1. The VMS shall support including audio in the video stream. The VMS supports
unidirectional synchronized audio support for live and playback video, and allows
for the following functions:
i. Exporting audio together with the video
ii. Audio support with the Virtual Matrix
iii. Audio support using the Client SDK
iv. Compression modes, including: PCM, ULAW, GSM, depending on the
edge device capabilities
S. Client Software Development Kit (SDK)
1. The VMS shall provide the ability to develop custom applications to access and
control the system using an Application Programming Interface (API). Complete
documentation of the API shall be available, and API features shall include:
i. Access Control Systems integration to generate alarms and events in the
VMS system.
ii. Command and Control Systems integration.
iii. Custom Review application development.
iv. Virtual Matrix operations, such as displaying live or playback video on
analog monitors.
v. Playing live video or query recorded video from cameras in a client
application.
vi. Querying the alarm list from the VMS system, acknowledging VMS
alarms, and subscribing to alarms to receive them in real time.
26

vii. PTZ commands supported in the service SDK are available in the Client
SDK.
viii. Calling up camera patterns from the Client.
ix. Accessing camera menus via the Client.
x. Streaming HD to the Client.
xi. Streaming MJPEG to the Client.
xii. Event Notification to Client, such as Video Lost, Motion Detection, and
Input Relay notifications.
xiii. Triggering contact closures on any user-specified Verint edge device or
IP camera whose hardware is equipped with this capability.
xiv. A Verint Direct Show filter interface shall be available to display live and
playback video.
xv. The interface shall be functional for any type of codec used (Verint, Axis,
etc.).
xvi. PTZ overlay support.
xvii. Digital Zoom support.
T. Camera Tampering Detection
1. The VMS shall support the Camera Tampering Detection resident on the edge
devices. The VMS shall monitor the following types of tampering alerts
communicated by the edge devices:
i. Camera blocked fully or partially
ii. Out of Focus (OoF) or Camera Defocus, where the image becomes
blurred because the camera is being defocused

27

 2011 Verint Systems Inc. All Rights Reserved Worldwide.

Unauthorized use, duplication, or modification of this document in whole or in part without the written consent of Verint
Systems Inc. is strictly prohibited. By providing this document, Verint Systems Inc. is not making any representations
regarding the correctness or completeness of its contents and reserves the right to alter this document at any time without
notice. Features listed in this document are subject to change.
Verint Systems Inc. does not warrant, guarantee or make any representation regarding the use or the results of the use of
the information, links, tools, and materials in terms of the accuracy, reliability, quality, validity, stability, completeness,
currentness, or otherwise of its content or products. The entire risk as to the use, results and performance of information,
links, tools and materials provided or referenced herein is assumed by the user. Verint Systems Inc. shall not be liable for
damages resulting from the use, misuse or unlawful use of the information, links, tools, and materials contained or
referenced herein.
The Verint Systems Inc. products are protected by one or more of the following U.S., European or International Patents:
USPN 5,659,768; USPN 5,689,442; USPN 5,790,798; USPN 6,278,978; USPN 6,370,574; USPN 6,404,857; USPN
6,510,220; USPN 6,724,887; USPN 6,751,297; USPN 6,757,361; USPN 6,782,093; USPN 6,952,732; USPN 6,959,078;
USPN 6,959,405; USPN 7,047,296; USPN 7,149,788; USPN 7,155,399; USPN 7,203,285; USPN 7,216,162; USPN
7,219,138; USPN 7,254,546; USPN 7,281,173; USPN 7,284,049; USPN 7,325,190; USPN 7,424,715; USPN 7,466,816;
USPN 7,478,051; USPN RE40,634; and other provisional rights from one or more of the following Published US Patent
Applications: US 11/394,408; US 11/771,499; US 11/396,514; US 11/772,440; US 11/565,943; US 11/565,946; US
11/565,948; US 11/540,739; US 11/540,086; US 11/541,313; US 11/541,252; US 11/540,282; US 11/529,947; US
11/540,785; US 11/540,736; US 11/540,904; US 11/540,353; US 11/608,340; US 11/608,350; US 11/608,358; US
11/567,808; US 11/692,983; US 11/693,933; US 11/693,923; US 11/693,828; US 11/567,852; US 11/608,440; US
12/015,621; US 11/540,322; US 11/924,201; US 11/616,490; US 11/621,134; US 11/752,458; US 11/712,933; US
11/824,980; US 11/729,185; US 11/804,748; US 11/831,260; US 11/395,992; US 11/359,319; US 11/359,195; US
11/359,357; US 10/832,509; US 11/742,733; US 11/831,257; US 11/831,250; US 11/691,530; US 11/479,267; US
11/529,942; US 11/768,349; US 11/540,281; US 10/633,357; US 11/693,899; US 11/479,056; US 11/529,132; US
11/540,320; US 11/037,604; US 11/529,842; US 11/540,171; US 11/478,714; US 11/529,946; US 11/868,656; US
11/776,659; US 11/090,638; US 11/410,004; US 10/771,315; US 10/771,409; US 11/540,900; US 11/528,267; US
12/118,781; and other U.S. and International Patents and Patents Pending.
VERINT, the VERINT logo, ACTIONABLE INTELLIGENCE, POWERING ACTIONABLE INTELLIGENCE, WITNESS
ACTIONABLE SOLUTIONS, STAR-GATE, RELIANT, VANTAGE, X-TRACT, NEXTIVA, ULTRA, AUDIOLOG, WITNESS,
the WITNESS logo, IMPACT 360, the IMPACT 360 logo, IMPROVE EVERYTHING, EQUALITY, CONTACTSTORE, and
CLICK2STAFF are trademarks or registered trademarks of Verint Systems Inc. or its subsidiaries. Other trademarks
mentioned are the property of their respective owners.

28