Victor-5-1-Ae-Specification Ae Ra0 LT en

victor Web Client
victor Express
victor Unified Client
victor Application Server
victor Enterprise
•••••••••••••••••••••••••••••••••••••••••••••••••••
Unified
Security & Video Management System
Engineering Specification
Version 5.1
American Dynamics makes no representations or warranties with respect to the

contents hereof and specifically disclaims any implied warranties of
merchantability or fitness for any particular purpose. Furthermore, American
Dynamics reserves the right to revise this publication from time to time in the
content hereof without the obligation to notify any person of any such revision or
changes.
NOTE:
The specifier should carefully select the portions
of this document that fit the intended application.
Feel free to consult with American Dynamics
regarding your particular application.
3610-0642-01 A0
victor Unified Security & Video Management System – A&E SPECIFICATIONS
TABLE OF CONTENTS
PART 1 GENERAL 1
1.1 AMERICAN DYNAMICS IP VIDEO SOLUTIONS.................................................................1
1.2 DEFINITIONS:....................................................................................................................... 1
1.3 GENERAL SYSTEM DESCRIPTION.....................................................................................2
1.4 SUBMITTALS........................................................................................................................ 3
1.4.1 Product Data 3
1.4.2 Shop Drawings 3
1.4.3 As-Built Drawings 3
1.5 QUALITY ASSURANCE........................................................................................................ 4

1.5.1 Manufacturer Qualifications 4
1.5.2 Contractor / Integrator Qualifications 4
1.5.3 Licensing 4
1.6 WARRANTY.......................................................................................................................... 8
PART 2 PRODUCTS 9
2.1 DIFFERENTIATED FUNCTIONALITY...................................................................................9
2.2 MANUFACTURED UNITS / MODEL NUMBERS................................................................15
2.3 DESCRIPTION..................................................................................................................... 22
2.4 VMS FUNCTIONALITY........................................................................................................ 23

2.4.1 Event Unification and Physical Merging of victor/C•CURE 9000 Servers 23
2.4.2 System Performance 24
2.4.3 Localization 24
2.4.4 User Authentications (Login Credentials)25
2.4.5 VMS Client Graphical User Interface (GUI) 26
2.4.6 Device Management / Organization 27
2.4.7 Advanced Integrated Mapping 29
2.4.8 Video Live Viewing and Playback 30
2.4.8.1 Surveillance Tracking 31
2.4.8.2 InstantView 32
2.4.8.3 Instant Playback 32
2.4.8.4 Timeline Control 33
2.4.8.5 Still Image Capture 33
2.4.8.6 Mechanical & Digital PTZ 33
2.4.8.7 Call-ups 34
2.4.8.8 Send to Commands 34
2.4.8.9 De-Warp Fish-Eye Cameras 35
2.4.9 Audio Live Listening and Playback 35
2.4.10 Video Search and Export 35
2.4.10.1 Date / Time Search 35
2.4.10.2 Motion Search 36
2.4.10.3 Search Across All Available Storage 36
2.4.10.4 Video Intelligence Analytic Search 37
2.4.10.5 Facial Recognition Analytic Search 38

2.4.10.6 Facial Verification Analytic Search 38
2.4.10.7 License Plate Recognition Analytic Search 39
2.4.10.8 Clip Storage / Export 39
2.4.11 Events and Event Monitoring 41
2.4.12 Scheduling 42
2.4.13 Analog Matrix 43
2.4.14 Virtual Matrix 43
2.4.15 CCTV Keyboard and Controllers43
2.4.16 Reporting 44
2.4.17 Clip Builder 45
2.4.18 Incident Builder 45
2.4.19 Presentation Builder 46
2.4.20 Event Management 46
2.4.21 Object Association 46
2.4.22 Storage Video Vault 47
2.4.23 User Management / Permission Controls 47
2.4.24 Device Discovery 48
2.4.25 Recorder Administration48
2.4.26 Integrated Web Browser49
2.4.27 Data Storage / Encryption 49
2.4.28 Database Backup / Restore 49
2.4.29 Dynamic Bandwidth Management 49
2.4.30 Networking 50
2.4.31 Health Monitoring 50
2.4.32 Help 51
2.4.33 Printers 51
2.4.34 victor Web Client 51
2.4.35 Push-to-Talk 53
2.4.36 Maintenance / Software Upgrades 53
2.4.37 License Manager 54
2.4.38 Software Support Agreement 54
2.5 SYSTEM REQUIREMENTS.................................................................................................55

2.5.1 victor Application Server Physical Server Requirements (victor Only) 55
2.5.2 victor Application Server Physical Server Requirements (Unified) 56
2.5.3 victor Application Server Virtual Server Requirements (victor Only) 57
2.5.4 victor Application Server Virtual Server Requirements (Unified) 58
2.5.5 victor Express and victor Client Physical Workstation Requirements 59
2.5.6 victor Web Client Physical and Virtual System Requirements 60
2.5.7 Supported Video Devices 61
2.5.8 Supported Intrusion Devices 62
2.5.9 Supported Access Control Devices 62
2.5.10 Supported Access Control Devices (Unified) 62
2.5.11 Supported Fire Panels Devices 63
2.5.12 Supported Location-Based Security Devices 63
2.5.13 Supported Point of Sale Systems and Text Streams 63
2.5.14 Supported victor Web Service 64
2.5.15 Supported Building Management Systems 65
2.5.16 Supported Elevator Devices 65
2.5.17 Supported Intercom Devices 65
2.5.18 Supported LDAP 66
2.5.19 Supported Enterprise Architecture 66
PART 3 EXECUTION 67
3.1 EXAMINATION.................................................................................................................... 67
3.2 PREPARATION................................................................................................................... 67
3.3 INSTALLATION................................................................................................................... 67
3.4 TESTING AND CERTIFICATION........................................................................................67
3.5 TRAINING............................................................................................................................ 68
3.6 MAINTENANCE................................................................................................................... 68
PART 1 GENERAL
1.1 AMERICAN DYNAMICS IP VIDEO SOLUTIONS
American Dynamics provides a complete range of open-platform IP Video solutions, that
include IP Cameras/Encoders (“illustra”), Network Video Recorders (“VideoEdge NVR”),
Network Hybrid Appliances (“VideoEdge Hybrid Appliance”), Hybrid Digital Video
Recorders (HDVR), Digital Video Recorders (Intellex and ADTVR), Security Management
software (“victor Application Server,” “victor Express,“ “victor Unified Client”) and iSCSI or
Fiber RAID storage (“iSCSi/Fiber Storage”). Each of these open-platform products can be
specified and installed with supported components from American Dynamics or 3 rd party
manufacturers. This specification deals with the victor Unified Security and Video
Management System. Additional information regarding related product from American
Dynamics can be found at:
 American Dynamics VideoEdge Network Video Recorder
http://www.americandynamics.net/Products/VideoEdge_NVR.aspx
 American Dynamics iSCSI/Fiber Storage Solutions
http://www.americandynamics.net/Products/Network_Video_Storage_Solutions.aspx
 American Dynamics Intellex Digital Video Management System

http://www.americandynamics.net/Products/Intellex_Home.aspx
 American Dynamics Hybrid DVR
http://www.americandynamics.net/Products/Hybrid_Digital_Video_Recorders.aspx
 American Dynamics TVR
http://www.americandynamics.net/Products/digital_video_recorder_home.aspx
 Illustra IP Cameras/Encoders
http://www.illustracameras.com/Default.aspx
http://www.americandynamics.net/Products/Cameras_Home.aspx
 Software House C•CURE 9000
http://swhouse.com/products/software_CCURE9000.aspx
1.2 DEFINITIONS:
A list of industry standard acronyms is provided below:
 ACC Video Codec “Active Content Compression“
 ADDS Active Directory Domain Services
 API Application Programming Interface
 CIFS Common Internet File System
 DHCP Dynamic Host Configuration Protocol
 DVR Digital Video Recorder
 FIBRE Fiber Optic Interface
 FISMA Federal Information Security Management Act
 FoV Field of View
 FPS Frames Per Second
 GbE Gigabit Ethernet (1000 Mbps)
 H264 Video Codec for MPEG4 Part 10
 H264+ H.264 Smart Codec
 HD High Definition (e.g. 720 or 1080 resolution)
 HDD Hard Disk Drive
3610-0642-01 A0 victor 1 of 17
 HDVR Hybrid Digital Video Recorder

 HTTP HyperText Transfer Protocol
 HTTPS HyperText Transfer Protocol Secure
 Hybrid Hybrid Recorder supports Analog and IP Video Inputs
 IntelliZip
Illustra enhanced image & bandwidth compression for H.264 & H.264+
 IP Internet Protocol
 IPFL IP Free License feature for all VideoEdge Bundled Recorders only for
Illustra Pro camera models
 iSCSI Internet Small Computer Systems Interface
 JBOD Just a Bunch Of Disks
 JeOS Just enough Operating System
 LAN Local Area Network
 LDAP Lightweight Directory Access Protocol
 MAS Master Application Server (enterprise system architecture)
 Mbps Megabits per second
 MJPEG Video Codec “Motion JPEG”
 MPEG4 Video Codec defining audio and visual digital data compression
 NIC Network Interface Card
 NVR Network Video Recorder
 PoE Power Over Ethernet
 PTZ Pan - Tilt - Zoom
 RAID Redundant Array of Independent Disks
 RAID-0 Block Level Striping without Parity or Mirroring (Min. 2 Drives)
 RAID-1 Mirroring without Parity or Striping (Min. 2 Drives)
 RAID-5 Block Level Striping with Distributed Parity (Min. 3 Drives)
 RAID-6 Block Level Striping with Double Distributed Parity (Min. 4 Drives)
 RAID-10 (1+0) for Mirroring without Parity and Block Level Stripping (Min. 4 Drive)
 ROI Region of Interest
 SAS Satellite Application Server (enterprise system architecture)
 SAS Serial Attached SCSI (device interface)
 SATA Serial ATA or Serial Advanced Technology Attachment (device interface)
 SDK Software Development Kit
 SNMP Simple Network Management Protocol
 SSA Software Support Agreement
 TB Terra Bytes
 UDP User Datagram Protocol
 VMS Video Management System
 WAN Wide Area Network
 ZipstreamAxis technology that optimizes video stream bandwidth
1.3 GENERAL SYSTEM DESCRIPTION

A complete IP Video Solution consists of some or all of the following nine components:
1. IP Cameras
2. Analog Cameras connected via Analog to IP Encoders for NVR connectivity or
directly connected to Hybrid Recorders
3. Network Video Recorders (NVRs for IP input)
4. Hybrid Recorders (Hybrid for Analog and IP input)
3610-0642-01 A0 victor 2 of 17
5. External Storage (for extended retention of recorded video)

6. Unified Security Monitoring / Management Software Applications
7. Analog DVRs (integrated into the Unified Security Monitoring Application)
8. Integrations to External Systems (e.g., Access Control, Video Analytics, etc.)
9. Video and Event SDK / API (for development of new integrations)
10. Failover / Redundancy / Archive Solution (for high availability)
11. Enterprise Server-Client Architecture (for a solution that scales up and scales out)
12. Centralized Licensing Architecture (for on premise license management solution)
The victor is Unified Security Monitoring / Management Software suite designed for
American Dynamics video products and Software House access control + event
management products. victor is a powerful, flexible, multi-function software solution
designed to simplify the monitoring and management of IP and analog security video. It
also has the capability to incorporate support for other security products such as access
control, intrusion, fire, and location awareness to become a truly unified the security
platform. victor allows a seamless migration path to IP Video, enabling the gradual
upgrade of their security video infrastructure without forcing security officers to switch
between multiple monitoring software applications. victor is built on the latest Windows
7/WPF framework for high performance and a modern, easy-to-use interface. victor is
highly scalable, allowing for connections to and monitoring of hundreds of recorders and
thousands of cameras. victor is available in a single computer (victor Express) or a multi-
computer (victor Application Server) configuration with ability to support deployment as a
MAS-SAS enterprise system. victor is also capable of being utilized in a Unified system
working in unison with Software House C•CURE 9000 access control and event
management software. A thin-client version is available that allows victor Web Client to
be deployed onto any compatible Windows system (including victor Application Server) to
enable multiple users to view/manage both video from VideoEdge recorders and events
using standard web browsers without any required drivers or plug-ins. In addition, ability
to add options for Health Dashboard, Maps, Reporting for BIRS and Retail, plus access
control device setup, personnel and swipe-and-show when victor Application Server is
unified with C•CURE 9000 using your standard web browser.
1.4 SUBMITTALS
1.4.1 Product Data
The following shall be provided:
 Complete product data and technical specification data sheets that include
manufacturer’s data for all material and equipment.
1.4.2 Shop Drawings

Shop Drawings and Schematics: Shall depict the VMS in final proposed “as built”
configuration. The following must be provided:
 Connection diagrams for interfacing equipment.
 List of connected equipment.
 Locations for all major equipment components to be installed under this
specification.
1.4.3 As-Built Drawings
3610-0642-01 A0 victor 3 of 17
At the conclusion of the project, the Contractor shall provide “as built” drawings. The “as
built” drawings shall be a continuation of the Contractor’s shop drawings as modified,
augmented, and reviewed during the installation, check out and acceptance phases of
the project.
1.5 QUALITY ASSURANCE

1.5.1 Manufacturer Qualifications
The VMS shall be developed and manufactured by a reputable Fortune 100 company
with more than 20 years of manufacturing experience in the security industry.
1.5.2 Contractor / Integrator Qualifications

The Contractor shall be a factory authorized and certified installer of the security
equipment supplied in this project and shall have been regularly engaged in the
installation of the type of security equipment, hardware, and software. The contractor
shall be factory trained on the VMS and associated products they propose and shall
submit with their proposal a certificate from the manufacturer indicating their satisfactory
completion of training for the VMS proposed. Proposals submitted without this certificate
shall be considered non-responsive and shall not be accepted.
1.5.3 Licensing
Licensing shall be required for the VMS software. The licensing shall include:
 A software serial number shall be associated with the software and will support the
pre-defined license configuration for the VMS model number. At any time,
additional add-on features and SSA can be purchased for the VMS software
license. Some features are natively supported while others may require installation
of version-compatible driver software to support the optional add-on licensed
feature. VMS shall allow ability to promote multiple standalone VMS sites to
Satellite Application Server hosts for an Enterprise deployment if a VMS Master
Application Server host exists at the site. VMS shall support ability to easily
consolidate and manage a pool of licenses centrally for multiple VideoEdge
Recorders. This shall provide maximum flexibility for on premise license
management with the ability to move licenses between one or more recorders.
 Single local client connection
(victor Express only)
 Number of metered concurrent client connections
(victor Application Server with/without Unified C•CURE 9000, SAS-enabled,
Centralized, victor Web Client integrated, or any of these combinations)
 Number of metered concurrent agent connections
 Number of metered concurrent web client connections
(victor Web Client standalone, victor Web Client integrated victor Application
Server with/without Unified C•CURE 9000, SAS-enabled, Centralized, or any of
these combinations)
 Metered number of licensed clients, agents, and/or web clients shall be easily
increased, and the license version can easily be updated. The online registration
shall auto-generate the updated license for the applicable server and email the file.
 Support for American Dynamics VideoEdge NVR, Hybrid and Micro video
recorders.
3610-0642-01 A0 victor 4 of 17
(20 for victor Express, 300 for victor Application Server with/without Unified
C•CURE 9000, SAS-enabled, Centralized, victor Web Client integrated, or any of
these combinations)
 Support for American Dynamics Intellex DVR video recorders.
(20 for victor Express, 700 for victor Application Server with/without Unified
C•CURE 9000, SAS-enabled, Centralized, victor Web Client integrated, or any of
these combinations)
 Support for American Dynamics TVR video recorders.
(700 for victor Application Server with/without Unified C•CURE 9000, SAS-enabled,
Centralized, or any of these combinations)
 Support for Holis video recorders.
 Support for ExacqVision/American Dynamics HDVR video recorders.
 Optional metered add-on for Dedicated Micros video recorders.
(Metered for victor Application Server with/without Unified C•CURE 9000, SAS-
enabled, Centralized, or any of these combinations)
 Optional add-on for POS (Point of Sale)
 Optional add-on for Unification with Software House C•CURE 9000 Access Control
(Unified victor Application Server with C•CURE 9000 with/without SAS-enabled,
 Optional add-on for Access Control – Kantech Entrapass
(victor Application Server with/without SAS-enabled, Centralized, or any of these
combinations)
 Optional add-on for Access Control – CEM
(victor Application Server with/without SAS-enabled, Centralized, or any of these
combinations)
 Optional add-on for Building Management System – BACnet
 Optional add-on for Elevator – KONE Destination Control
 Optional add-on for Elevator – OTIS Compass Destination Entry
 Optional add-on for Elevator – ThyssenKrupp Destination Dispatch
 Optional add-on for Fire Alarm – Simplex Grinnell 4100
 Optional add-on for Fire Alarm – Zettler/MZX Technology Fire Panel
3610-0642-01 A0 victor 5 of 17

 Optional add-on for Intercom – Commend GE Series
 Optional add-on for Intercom – TOA (AIPhone)
 Optional add-on for Intrusion – DSC PowerSeries
 Optional add-on for Intrusion – DSC Neo ITV2
 Optional add-on for Intrusion – SurGard Alarm Receiver
 Optional add-on for Intrusion – Bosch Alarm Receiver
 Optional add-on for Intrusion – Galaxy
 Optional add-on for Protocol – LDAP
 Optional add-on for Real-Time Locators – Elpas
 Optional metered add-on for web services – victor Web Service
 Optional additional metered add-on for victor Go server – victor Web Service
 Support for victor Unified Clients – Dewarping
(victor Express, victor Application Server with/without Unified C•CURE 9000, SAS-
enabled, Centralized, victor Web Client integrated, or any of these combinations)
 Support for victor Unified Clients – Reporting
(victor Express, victor Application Server with/without Unified C•CURE 9000, SAS-
enabled, Centralized, victor Web Client integrated, or any of these combinations)
 Support for victor Unified Clients – Analog Matrix
 Support for victor Unified Clients – Incident Builder
3610-0642-01 A0 victor 6 of 17
 Optional add-on for victor Unified Clients – Health Monitoring support

 Optional add-on for victor Unified Clients – Map support
 Optional add-on for victor Unified Clients – Record Surveillance window
(victor Express or victor Application Server with/without Unified C•CURE 9000,
SAS-enabled, Centralized, victor Web Client integrated, or any of these
combinations)
 Optional add-on for victor Unified Clients - Virtual Matrix PTZ Keyboard support
 Support for victor Web Client – Access Control Device Setup
(victor Web Client standalone or victor Web Client integrated victor Application
Server with Unified C•CURE 9000, SAS-enabled, Centralized, or any of these
combinations)
 Support for victor Web Client – Personnel
combinations)
 Support for victor Web Client – Swipe-n-Show
combinations)
 Support for victor Web Client – Health Dashboard
these combinations)
 Support for victor Web Client – Map
these combinations and add-on for victor Clients – Map support)
 Support for victor Web Client – Retail Reporting
these combinations)
 Optional metered add-on for VideoEdge IP cameras
(Metered for Centralized victor Application Server with/without Unified C•CURE
9000, SAS-enabled, victor Web Client integrated, or any of these combinations)
 Optional metered add-on for VideoEdge Video Analytic channels
 Optional metered add-on for VideoEdge Facial Recognition channels
9000, SAS-enabled, victor Web Client integrated, or any of these combinations,
after purchasing a VideoEdge Face Database Site License)
 Optional metered add-on for VideoEdge Facial Verification channels
3610-0642-01 A0 victor 7 of 17

 Optional metered add-on for VideoEdge License Plate Recognition channels
 Number of centralized VideoEdge IP cameras, Video Analytics, Facial Recognition,
Facial Verification and/or License Plate Recognition licenses can be easily
increased, and the license version can easily be updated. The online registration
shall enable transferring of individual VideoEdge recorder licenses to consolidate
them into a single pool of licenses managed by victor and then it will auto-generate
and email the updated license file.
 For Centralized victor Application Servers, all VideoEdge Bundled Recorders
(running V5.1 or higher) will utilize IPFL (IP Free Licensing) feature to allow Illustra
Pro cameras to be added to the recorders without using any IP camera licenses , so
no VideoEdge IP Camera licenses will be requested for those devices. For
VideoEdge software only products (All versions), they will not utilize IPFL and
requires licenses for all camera devices.
 SSA expiration warning message shall be notified in victor reports and displayed in
the License Manager. In addition, the associated VideoEdge recorders will take on
the same SSA date as their assigned Centralized victor Application Server.
 The detailed license status shall be easily accessible and clearly stated in the VMS
software.
 Major software releases for the VMS will require an updated compatible license file.
An automated online registration shall be available from the manufacturer to
support generation of new or update licenses upon demand, and delivered
electronically via email.
1.6 WARRANTY
Warranty shall be required for the VMS software. The warranty shall include:
 Manufacturer shall provide standard 1 year warranty on all software products.
 Manufacturer or Manufacturer’s partner shall provide software download support
for issues relating to VMS software.
 Manufacturer shall provide software upgrades for 12 months included in the
purchase price of the VMS.
 Additional years of software upgrades (SSA’s) shall be available for purchase
separately. Manufacturer shall offer both standard coverage (8x5) as well as
enhanced coverage (24x7) options.
3610-0642-01 A0 victor 8 of 17
PART 2 PRODUCTS
2.1 DIFFERENTIATED FUNCTIONALITY
The complete specifications of the victor Unified Security and Video Management System
are provided throughout this section. Key capabilities that differentiate the victor VMS
from competitive product are repeated here for the specifier’s convenience:
 VMS solution shall support a single unified installer that enables the ability to install
or upgrade a video management system, access control and event management
system, or a unified security system that supports video, access control, and
associated security devices. On a unified installation, the same single server shall
host both the victor Application Server and a C•CURE 9000 which are licensed for
unification and are running the required compatible versions of software. Share
event notification, utilize a single application service, and a common shared
database is a unique implementation for access control and video system solution.
Installer shall have the option to include or exclude the TeamViewer TM remote
desktop utility during new and upgrade installations.
 VMS solution shall be cyber protected by a manufacturer that takes pro-active
steps to ensure that the products follow secure product development practices,
execute rigorous internal and external testing, have configuration guidelines for
compliancy, and actively monitor for any threats that can impact the solutions in the
field. The products shall adhere to the following:
 FISMA-Ready
 Federation Information Processing Standard (FIPS) 140-2 validated system
when unified with C•CURE 9000/iSTAR
 Physical Access Control System (PACS) approved when unified with
C•CURE 9000
 Backed by a dedicated cross-functional Cyber Protection Team to rapidly
response to any newly discovered threats that could impact the system
 VMS client shall only be restricted to local computer access when using victor
Express, the single computer version of the VMS solution, or multi-computer
access when using victor Application Server.
 VMS client shall support the ability to institute a double password protection that
would require two unique validated sets of credentials before the feature’s
operations can be carried out (video search and retrieve, instant playback, clip
export) to support privacy rights in applicable European markets.
 VMS client shall support dynamically displaying menu items and controls which are
applicable to the system configuration for improved user experience.
 VMS client shall support the simultaneous display and monitoring, in the same
surveillance window, of analog video and IP video from supported recorders:
 VideoEdge NVR
 VideoEdge Hybrid
 VideoEdge Micro
 Intellex DVR
 HDVR*
 TVR*
3610-0642-01 A0 victor 9 of 17
 Exacq Vision Recorders*

 Holis Recorders*
 Various supported 3rd party IP cameras/encoders/recorders with victor add-
on license*
Note: * victor Express does not support HDVR/Exacq, TVR, Holis or any
optional Video integration.
 VMS client installed on a hardware platform meeting the recommended
specification shall support the simultaneous display of up to 64 video streams
across all connected monitors.
 VMS client shall be written with Windows Presentation Foundation (WPF)
technology to maximize the quality and quantity of video displayed on connected
monitors. VMS client shall employ Windows 7 – style menus and tab-based
navigation to ensure ease-of-use for operators.
 VMS client shall provide the ability to view live and recorded video on the same
camera within a single application layout.
 VMS client shall provide a completely user-customizable ‘Site View’: enabling the
organization of cameras, recorders, tours, salvos into user-defined, multi-level
folders, similar to Windows Explorer-style file organization. On a large or distributed
system, a Site will automatically be created in the Site List when a SAS is started.
 VMS client shall support ability to manually track any person or object across
multiple cameras and/or virtual PTZ presets when configured with surveillance
tracking arrows.
 VMS client shall support the completion of a motion search over 1 week of
available recorded analog or IP video of a scene containing an average level of
motion throughout, regardless of codec or resolution of the recorded video, within 2
minutes.
 From any motion search result, VMS client shall allow the user to add additional,
related cameras to the View and shall automatically synchronize the date/time of
the added cameras to the original search result (“Investigate mode”).
 VMS client shall support seamless access to live video during a VideoEdge fail-
over event without any changes on victor. After a fail-over event has been resolved,
recorded video stored on the temporary VideoEdge fail-over recorder shall be
available for search/playback without any changes on victor.
 VMS client shall support seamless search/playback from video that has been
archived by a VideoEdge without any changes on victor.
 VMS client shall have the flexibility to select playback of video and audio steams,
video only streams and audio only streams for the same or different cameras with
search results from VideoEdge recorders. Using object associations, an audio
stream shall be able to be associated with a video stream from a different camera
on the same or different recorders.
 VMS client shall support virtual Pan-Tilt-Zoom control during playback to enhance
the usage of megapixel video.
 VMS client shall support an easy-to-use 3-click Clip Export function and Still Image
Capture for improved investigation tools with ability to specify a custom filename for
the exported clip. Video overlay can be included on snapshots and exported clip
notes shall be attachable for review by the victor Player.
3610-0642-01 A0 victor 10 of 17
 VMS client shall support ability to record the video viewed in the surveillance
window as a video clip when the optional licensed feature for Record Surveillance
Window is enabled for victor Express or victor Application Server.
 VMS client shall include an integrated Web Browser tab that can be combined with
other user interface components (Video Views, Site View, Event Viewer, etc.) into
an Application Layout. The Web Browser tab shall allow operators to continue
monitoring their security system while also receiving weather or news updates from
web-based information sources.
 VMS client shall support the ability to provide Client-to-Client “Push” enabling a
workstation the ability to “push” any layout (e.g. video, alerts, web site, etc.) to
another workstation’s monitor based on roles, security and license settings when
using victor Application Server. The receiving Client shall have the ability to accept
or reject the incoming request.
 VMS client shall support the ability to run in unattended mode as an Agent on the
Unified Security and Video Management System for utilization as a Video Wall
Client based on license settings for victor Application Server when the optional
victor add-on license for Agents is purchased.
 VMS client shall support the ability to have an Event Priority Window to display
Camera Call-Up Actions associated with events in prioritization sequence based on
license settings for victor Application Server when the optional victor add-on license
for Agents is purchased.
 VMS client shall support a Bi-Directional interface to enable ability to easily
integrate with other 3rd party systems over a serial or TCP/IP connection.
 VMS client shall support integration with the American Dynamics MP-48 and MP-
3200 Analog Matrices that will enable bringing in an enterprise analog video
system into an IP video solution with support for analog CCTV keyboard interface
when the optional victor add-on licensed for Virtual Matrix PTZ Keyboard is
purchased.
 VMS client shall support database management tools which enable ability to setup
rules to regulate the archival to provide enhanced support when using a Microsoft
SQL Express database.
 VMS client shall support customized On-Screen Display text within the video panes
in the Surveillance windows.
 VMS client shall support time line filters and a jump to next button for quicker
searchers over longer periods of recorded video.
 VMS client shall support managing recorded video using the storage video vault to
protect any tagged video and/or audio from being data culled.
 VMS client shall support advanced integrated mapping that supports standard
raster and AutoCAD files when the optional victor add-on license for Maps is
purchased. It shall allow creation of one or more layers to organize the objects,
custom map icons, video pop-up when hovering over a camera icon or during an
event, nest maps, map templates, importing C-CURE maps, displaying GIS map
layer and dynamically show animated state changes of any object with field-of-view
cones to identify expected coverage.
 VMS client shall support ability to execute video intelligence analytic searches on
VideoEdge recorders that have the optional VideoEdge add-on license for Video
Analytics. The analytic search types can be conducted on cameras that had
analytic search feature enabled and shall include:
3610-0642-01 A0 victor 11 of 17
 Object Detection
 Direction
 Linger
 Enter
 Exit
 Abandoned/Detected
 Dwell
 Crowd Formation
 Queue Analysis (Length Monitoring)
 Heat Map generation
 VMS client shall support ability to execute video face analytic searches on
VideoEdge recorders that have the optional VideoEdge add-on licenses for Face
Recognition and Verification. The analytic search types can be conducted on
cameras that had analytic search feature enabled and shall include:
 Face Detection
 Face Recognition
 VMS client shall support ability to execute license plate recognition searches on
VideoEdge recorders that have the optional VideoEdge add-on licenses for License
Plate Recognition. The analytic search can be for specific license plates or
unrecognized license plates.
 VMS client shall support edge-based analytic events when VideoEdge recorders
are configured with supported camera models. Edge-based analytic shall include
face and blur detection events.
 VMS client shall support searching on alarm rules that were defined on VideoEdge
recorders.
 VMS client shall support data visualization that enables the ability to easily chart
graphically across timeline all searchable data, send report in email and drill-down
to single events to view patterns for data mining and reporting.
 VMS client shall support dynamic bandwidth management with VideoEdge
recorders by selecting the current bandwidth connection speed, to help optimize
the viewing experience over a WAN environment. For policy management, it shall
also support enforcing the maximum bandwidth allowed based on the Role or
Operator.
 VMS client shall support a health monitoring dashboard to allow access to the
status updates of their systems with ability to easily drill-down flagged items for
identifying root causes when the optional victor add-on license for Health
Monitoring is purchased.
 VMS client shall support de-warping of fish-eye cameras supported by VideoEdge
servers. De-warping is available for panoramic broad views and rectilinear for high
quality view of particular area within the full image. De-warped views can be saved
as part of designated layouts and the <SHIFT> key can be used to select the
desired de-warp area.
 VMS client shall support fish-eye cameras supported by exacqVision VMS
recorders and multi-streams configured on the camera.
3610-0642-01 A0 victor 12 of 17
 VMS client shall support managing all of the information associated for an incident
and/or event, and utilize a template to generate a single report containing video,
still images, report data, report charts, notes, and any externally supported files.
Victor Player shall support playing exported incident package when the optional
victor add-on license for Incident Builder is purchased.
 VMS Client shall support creating single point in time bookmark or bookmark with
begin and end time.
 VMS client shall be localized to support eighteen (18) different languages (Arabic,
Chinese Simplified, Chinese Traditional, Czech, Danish, Dutch, English US, French
Standard, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese
Brazilian, Spanish, Swedish, and Turkish). However, when unified, the native OS
language and application GUI supported will be limited to the thirteen (13) common
between victor and C•CURE 9000 (Arabic, Chinese Simplified, Dutch, English US,
French Standard, German, Italian, Japanese, Polish, Portuguese Brazilian,
Spanish).
 VMS client shall include details to download and view training videos.
 VMS client shall directly connect to supported cameras via multicast when a
VideoEdge NVR becomes inaccessible to ensure continuous video feed.
 VMS server shall auto-detect the host machine’s operating system version and
proceed to install as a native 64-bit application. The ability to run as a 64-bit
application enables victor to support a larger amount of memory to boost overall
performance and capabilities.
 VMS server shall provide detailed license status information that includes current
software version, expiration date, and a detailed feature set matrix.
 VMS server shall support alarm persistence notification to recover cached alarms
from associated VideoEdge recorders that may have lost communication for up to
two weeks.
 VMS server shall support the Update Server feature that allows update packages
for victor Unified Client to be installed onto the server during upgrades and users
can be automatically prompted to upgrade the client application on next boot. In
addition, the Update Server feature will also enable the installation of updated
images for VideoEdge recorders.
 VMS server shall support deployment in a qualified virtual machine environment
(VMWare, Hyper-V).
 VMS server shall allow administrators to manage user roles and profiles using a
native LDAP server interface when the optional victor add-on license for LDAP is
purchased.
 VMS shall support a reporting architecture that can upload data in the Unified POS
format to provide rich investigator tools, including customer present analytic, to
match the data to the relevant synchronized recorded video footage when the
optional victor add-on license for POS is purchased.
 VMS server shall support the ability to allow any VMS client to easily send any
object or tabbed item to any monitor that is either locally attached or across the
network, for example, a monitor of a remote VMS client machine or unattended
video wall when the optional victor add-on license for Agent is purchased.
 VMS system shall allow ability to use any compatible Windows-based machine to
host a web server to enable multiple remote clients to use standard web browsers
to view live/recorded video and events from VideoEdge recorders. It shall allow
3610-0642-01 A0 victor 13 of 17
seamless and simultaneously enable access to multiple recorders and their

cameras located on the same network segment.
 When unified, the VMS client shall support the various third party add-ons to
enable Event Management across Video, Access Control, and associated third
party products that are integrated into either victor or C•CURE 9000 such as
Access, Video, Fire, Intrusion, Real-Time Locator, Building, Intercom, Elevator, etc.
when the optional victor add-on license for the specified integration(s) are
purchased.
 When unified, the VMS client shall display all of the victor’s standard devices along
with integrated C•CURE 9000 and third party objects that will have all actions
written to the victor journal database and activity list for reporting.
 When unified, the VMS client shall support dual-phase acknowledgement for any
events that are captured in the Event Viewer.
 When unified, the VMS client shall support object association to allow any device to
be linked to as many as five other objects. It greatly reduces the time required to
complete reviews as associated objects can all be synchronized during playback.
 When unified, the VMS client shall support the C•CURE 9000 swipe-and-show
feature to monitor traffic on specific readers and auto-display associated pictures of
the cardholders in real-time as they swipe. When using VideoEdge recorders with
facial recognition analytics, the swipe-and-show can be configured to provide
status of whether or not the face of the person at a door is verified against the facial
analytic data enrolled in the database for that access card holder.
 When unified, VMS solution shall support a scalable architecture capable of
deployment in enterprise environments as a large or distributed system. victor
unification with C•CURE allows the ability to configure a site that is part of a “hub-
and-spokes” topology, with the capability to function in a disconnected environment
with complete local command and control.
 When unified or standalone victor Application Server, a single system deployment
in an enterprise environment is capable of supporting up to forty (40) Satellite
Application Servers (SAS) for each Master Application Server (MAS). The satellite
servers provide real-time response for critical operations such as events and
actions, while the master server provides a rolled-up monitoring and reporting
interface.
 When unified or standalone victor Application Server and deployed at the MAS in
an enterprise environment, the Events, Operators and Roles types created at the
MAS in victor will always be global.
 When unified or standalone victor Application Server and deployed in an enterprise
environment, the dynamic view on the MAS will contain all of the SAS’s and the
MAS that the operator has access to, and the dynamic view on the SAS will contain
the MAS and the SAS.
 When unified or standalone victor Application Server and deployed in an enterprise
environment, the VMS client shall be allowed to be installed on a SAS.
 VMS client shall be localized to support eighteen (18) different languages (Arabic,
Chinese Simplified, Chinese Traditional, Czech, Danish, Dutch, English US, French
Standard, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese
Brazilian, Spanish, Swedish, and Turkish). However, when unified, the native OS
language and application GUI supported will be limited to the thirteen (13) common
between victor and C•CURE 9000 (Arabic, Chinese Simplified, Dutch, English US,
3610-0642-01 A0 victor 14 of 17
French Standard, German, Italian, Japanese, Polish, Portuguese Brazilian,

Spanish).
 VMS client shall include details to download and view training videos.
2.2 MANUFACTURED UNITS / MODEL NUMBERS

The Security Management System shall, at a minimum, include one or multiple
VideoEdge NVRs or VideoEdge Hybrid Appliances or Intellex DVRs or HDVRs or TVRs,
one installed version of victor (Express or Application Server) with optional victor Web
Client, and one or more victor Unified Clients. Models numbers are listed below:
victor software base models:
ADVSEXPRS victor Express software base with single local client connection
ADVASC01 victor Professional software base with 1 concurrent client connections
ADVSAS victor Enterprise SAS software base with 1 concurrent client connection
victor Enterprise MAS software base with 1 concurrent client connection

ADVMAS-10
(This model limited to support up to 10 SAS)

ADVMAS-20

ADVMAS-40
victor Web Client standalone software base with 1 concurrent victor Web
ADVWCC01
Client connections
victor Web Client additional concurrent licenses:

victor additional Web Client connections (1-pack) (Web Client)
ADVC-VWC01 (Purchase option for victor Web Client standalone
or integrated vWC with victor Professional or Enterprise SAS)
victor Professional add-on licenses:

victor additional concurrent client connection (1-pack) (Client)
ADVASC01ADD
(Purchase metered option for victor Professional)
victor additional concurrent client connections (25-pack) (Client)
ADVASC25ADD
victor Command Center additional agent connections (1-pack) (Agent)
ADVCC01ADD
victor additional concurrent web client connection (1-pack) (Web Client)
ADVC-VWC01
(Purchase metered option for victor Professional or Enterprise SAS)
victor Client support for Health Monitoring (Health)

ADVC-VCHEALTH
(Purchase option for victor Professional)
victor Client support for Maps (Maps)
ADVC-VCMAP
3610-0642-01 A0 victor 15 of 17
victor Client support for Recording Surveillance (Record)

ADVC-VCRECSURV
(Purchase option for victor Express or victor Professional)
victor Client support for Virtual Matrix PTZ Keyboard (VMK)
ADVC-VCVMK
victor integration with Point of Sale (POS)

ADVC-POS
victor integration with LDAP (Protocol)
ADVC-LDAP
victor integration for victor GO (1 connection) (Mobile)
ADVC-VGOAPP01
ADVC- victor promotion from Professional to Enterprise SAS (SAS)

APPSERVER (Purchase option for victor Professional)
victor Enterprise SAS add-on licenses:

ADVSASC01ADD
(Purchase option for victor Enterprise SAS)
ADVSASC25ADD
ADVSASCC01ADD
victor additional concurrent web client connection (1-pack) (Web Client)
ADVC-VWC01
(Purchase option for victor Professional or Enterprise SAS)

ADVC-SASHEALTH
ADVC-SASMAP
ADVC- victor Client support for Recording Surveillance (Record)

SASRECSURV (Purchase option for victor Express or victor Enterprise SAS)
ADVC-SASVMK
victor integration with Point of Sale (POS)

ADVC-SASPOS
ADVC-SASLDAP
victor integration for victor GO (1 connection) (Mobile)
ADVC-VGOAPP01
victor Enterprise MAS add-on licenses:

ADVMASC01ADD
(Purchase option for victor Enterprise MAS)
ADVMASC25ADD
3610-0642-01 A0 victor 16 of 17

ADVMASCC01ADD

ADVC-MASHEALTH
ADVC-MASMAP
ADVC- victor Client support for Recording Surveillance (Record)

MASRECSURV (Purchase option for victor Express or victor Enterprise MAS)
ADVC-MASVMK

ADVC-MASLDAP
victor Professional and Enterprise SAS Centralized add-on licenses:

victor promotion to Centralized Licensing for VideoEdge (Centralized)
ADVC-CENTLIC
(No charge option for victor Professional)
victor additional VE IP Camera license (1-pack) (Centralized)
ADVC-VECAM
(Purchase metered option for Centralized victor Professional)
victor additional VE Video Analytic license (1-pack) (Centralized)
ADVC-VEVA
victor VE Face Database Site license (1,000 pack) (Centralized)
ADVC-VEFRDB1000 (Purchase required DB Site License for Centralized victor Professional)
(Required pre-requisite for ADVC-VEFR and/or ADVC-VEFV)
victor additional VE Facial Recognition license (1-pack) (Centralized)
ADVC-VEFR
victor additional VE Facial Verification license (1-pack) (Centralized)
ADVC-VEFV (Purchase metered option for Centralized victor Professional)
(Requires Unified victor/CCURE Server)
victor additional VE License Plate Recognition license (1-pack)
ADVC-VELPR (Centralized)
ADVC- victor promotion to Centralized Licensing for VideoEdge (Centralized)

SASCENTLIC (No charge option for victor Enterprise SAS)
victor additional VE IP Camera license (1-pack) (Centralized)
ADVC-SASVECAM
(Purchase metered option for Centralized victor Enterprise SAS)
victor additional VE Video Analytic license (1-pack) (Centralized)
ADVC-SASVEVA
victor VE Face Database Site license (1,000 pack) (Centralized)
ADVC-
(Purchase required Site License for Centralized victor Enterprise SAS)
SASVEFRDB1K
(Required pre-requisite for ADVC-VEFR and/or ADVC-VEFV)
victor additional VE Facial Recognition license (1-pack) (Centralized)
ADVC-SASVEFR
ADVC-SASVEFV victor additional VE Facial Verification license (1-pack) (Centralized)
3610-0642-01 A0 victor 17 of 17

(Requires Unified victor/CCURE Server)
victor additional VE License Plate Recognition license (1-pack)
ADVC-SASVELPR (Centralized)
victor Unification add-on licenses:

victor Unification with C•CURE 9000 (Unified with Access Control)
(U
ADVC-CC9000
(Purchase No Charge upgrade option for victor Professional only)
(Only SWH dealers can order this option)

(U
ADVC-VSASCC9
(Purchase No Charge upgrade option for victor Enterprise SAS only)

(U
ADVC-VMASCC9
(Purchase No Charge upgrade option for victor Enterprise MAS only)
victor Professional and Enterprise SAS integration licenses:

victor integration with CEM (Access Control)
ADVC-CEM (No charge for victor Professional or Enterprise SAS)
(Not available for Unified victor/C•CURE)
victor integration with Kantech Entrapass (Access Control)
ADVC-ENTRAPASS (No charge for victor Professional or Enterprise SAS)
(Not available for Unified victor/C•CURE)
victor integration with BACnet (Building Management System)

ADVC-BACNET
victor integration with KONE (Elevator)

ADVC-KONE
(Purchase option for Unified victor/C•CURE – Pro or Enterprise SAS)
victor integration with Otis (Elevator)
ADVC-OTIS
victor integration with ThyssenKrupp (Elevator)
ADVC-TKRUPP
victor integration with FireClass Fire Panel (Fire)

ADVC-FIRECLASS
victor integration with MZX Fire Panel (Fire)
ADVC-MZX
victor integration with Simplex Grinnell 4100U/ES (Fire)
ADVC-4100U
victor integration with Commend (Intercom)

ADVC-COMMEND
3610-0642-01 A0 victor 18 of 17
victor integration with TOA (AIPhone) (Intercom)

ADVC-TOA
victor integration with Bosch Alarm Receiver (Intrusion)

ADVC-BOSCHREC
victor integration with DMP (Intrusion)
ADVC-DMP
victor integration with DSC Power Series (Intrusion)
ADVC-DSC
(No charge for victor Professional or Enterprise SAS)
victor integration with DSC Neo ITV2 (Intrusion)
ADVC-ITV2
(No charge option for victor Professional or Enterprise SAS)
victor integration with Galaxy (Intrusion)
ADVC-GALAXY
victor integration with SurGard Alarm Receiver (Intrusion)
ADVC-SURGARD
victor integration with Elpas (Real-Time Locator)

ADVC-ELPAS
ADVC- victor integration with Dedicated Micros Recorders (Video)

DEDICATEDM (Purchase metered option QTY for victor Professional or Enterprise SAS)
victor integration with victor Web Service (Web Service)

ADVC-WEBSERVICE
(Purchase 1,000 metered option for victor Professional only)
victor SSA Model Numbers

ADVEX1SSA SSA victor Express for 1 additional year – Standard Support
ADVEX1SSAE SSA victor Express for 1 additional year – Enhanced Support
ADVS1SSA SSA victor Professional per client license for 1 additional year – Standard
ADVS2SSA SSA victor Professional per client license for 2 additional years – Standard
ADVS1SSAE SSA victor Professional per client license for 1 additional year – Enhanced
ADVS2SSAE SSA victor Professional per client license for 2 additional years – Enhanced
ADVSASSSA SSA victor Ent. SAS per client license for 1 additional year – Standard
ADVSASSSA2 SSA victor Ent. SAS per client license for 2 additional years – Standard
3610-0642-01 A0 victor 19 of 17
ADVSASSSAE SSA victor Ent. SAS per client license for 1 additional year – Enhanced
ADVSASSSAE2 SSA victor Ent. SAS per client license for 2 additional years – Enhanced
ADVMASSSA SSA victor Ent. MAS per client license for 1 additional year – Standard
ADVMASSSA2 SSA victor Ent. MAS per client license for 2 additional years – Standard
ADVMASSSAE SSA victor Ent. MAS per client license for 1 additional year – Enhanced
ADVMASSSAE2 SSA victor Ent. MAS per client license for 2 additional years – Enhanced
ADVC-VECAM-S SSA Centralized per VE IP Camera license (VE Cameras)

ADVC-VEVA-S SSA Centralized per VE Video Analytics license (VE VA)
ADVC-VEFR-S SSA Centralized per VE Facial Recognition license (VE FR)
ADVC-VEFV-S SSA Centralized per VE Facial Verification license (VE FV)
ADVC-VELPR-S SSA Centralized per VE License Plate Recognition license (VE LPR)
ADVC-POS-S SSA for victor integration with Point of Sale (POS)

ADVC-LDAP-S SSA for victor integration with LDAP (Protocol)
SSA for victor integration with CEM (N/C) (Access Control)

ADVC-CEM-S
ADVC-ENTRAPASS-
SSA for victor integration with Kantech Entrapass (N/C) (Access Control)
S
ADVC-BACNET-S SSA for victor integration with BACnet (Building Management System)
ADVC-KONE-S SSA for victor integration with KONE (Elevator)

ADVC-OTIS-S SSA for victor integration with Otis (Elevator)
ADVC-TKRUPP-S SSA for victor integration with ThyssenKrupp (Elevator)
ADVC-FIREC-S SSA for victor integration with FireClass Fire Panel (Fire)
ADVC-MZX-S SSA for victor integration with MZX Fire Panel (Fire)
ADVC-4100U-S SSA for victor integration with Simplex Grinnell 4100U (Fire)
ADVC-COM-S SSA for victor integration with Commend (Intercom)

ADVC-TOA-S SSA for victor integration with TOA (AIPhone) (Intercom)
ADVC-BOS-S SSA for victor integration with Bosch Alarm Receiver (Intrusion)
3610-0642-01 A0 victor 20 of 17
ADVC-DMP-S SSA for victor integration with DMP (Intrusion)

ADVC-DSC-S SSA for victor integration with DSC Power Series (Intrusion)
ADVC-ITV2-S SSA for victor integration with DSC Neo ITV2 (Intrusion)
ADVC-GALAXY-S SSA for victor integration with Galaxy (Intrusion)
ADVC-SUR-S SSA for victor integration with SurGard Alarm Receiver (N/C) (Intrusion)
ADVC-ELP-S SSA for victor integration with Elpas (Real-Time Locator)
ADVC-
SSA for victor integration with Dedicated Micros Recorders (Video)
DEDICATEDM-S
ADVC-WEBSVC-S SSA for victor integration with victor Web Service (Web Service)
3610-0642-01 A0 victor 21 of 17
2.3 DESCRIPTION
VMS is available in three configurations: victor Express which is designed for single
computer installation sites, victor Application Server which is designed for a multi-
computer, multi-site and command center environments, and victor Enterprise which is
designed for large scale solutions. All of these are UL certified and FISMA-ready for
cyber secured solutions.
victor Application Server incorporates an industry-standard relational database that is
used to manage and maintain a single record of authorized users/passwords, associated
recorders/cameras, roles and permissions, aggregated alarm and event journal and
current client license status. In most environments, only one victor Application Server is
required per site, regardless of the number of recorders, cameras connected, and is
licensed for specified number of concurrent client connections and video devices
(unlimited for all AD recorders on victor Application Server). victor Application Server can
be installed on the same PC as victor client for smaller sites or on a separate server(s)
for larger sites.
victor Express is the simplified, single computer version of victor Application Server for
customers that do not require support for multiple client connections and limited number
of VideoEdge and Intellex video recorders.
victor Enterprise is designed to provide a solution that can both scale up and scale out by
utilizing our unique MAS-SAS architecture. A single Master Application Server (victor
MAS) can support up to forty (40) remote Satellite Application Servers (victor SAS) that
provides both global and centralized management for customers with highly distributed
locations and/or extremely large number of edge devices.
victor Application Server and victor Enterprise both include the Server Configuration utility
that is used to manage the services, server components, central SQL database and
settings for that site or system. These hosts can be unified with C•CURE 9000,
Centralized to manage a pool of VideoEdge licenses (exception is MAS), as well as be
integrated with victor Web Client integrated (exception is MAS).
victor Express, victor Application Server and victor Enterprise all utilize the License
Manager utility that is used to update licenses, provide detail information about the
license and SSA status.
victor Unified Client is the user interface for security officers and administrators to monitor
and manage their IP and analog security video system. This software application includes
all interfaces required to view live and recorded video, search for video using
SmartSearch technology, monitor and manage system events and alarms, create and
edit user-defined layouts, views, tours, salvos etc., export clips, view journal reports,
add/delete recorders and other peripherals connected to the system and administer user
accounts and privileges. victor client is freely available and can be installed on as many
PCs as a site requires. Licensing for victor Application Server is based on the number of
concurrent users (clients and agents) accessing the system while victor Express license
is restricted to the single and local victor Unified Client.
victor Player is the standalone video player application that can be exported along with
digitally-verified video clips to enable the playback of exported analog or IP video clips in
native format without requiring the full installation of victor. It is designed to auto-launch
into a virtual environment to eliminate the need to install any software on the playback
Windows computer.
victor Web Client is a web server that can be installed on any compatible standalone
Windows system or on the same machine as victor Application Server. It is designed to
allow clients to use standard web browsers to view live/recorded video from multiple
VideoEdge recorders, control cameras and manage events without the installation of any
3610-0642-01 A0 victor 22 of 17
drivers or plug-ins. These browser clients can have enhanced features by purchasing any
of the available add-on license options for victor Web Client.
All of these applications (victor License Manager, Server Configuration, victor Unified
Client, victor Player) are Windows-based UL certified software.
2.4 VMS FUNCTIONALITY

2.4.1 Event Unification and Physical Merging of victor/C•CURE 9000
Servers
The VMS shall support Software House C•CURE 9000 Swipe and Show to monitor traffic
on specified readers and view card holders pictures in real-time. The VMS shall be able
to support event unification and physical merging of victor Application Server and
C•CURE 9000 servers:
 VMS shall support the ability to co-exist on the same server and share common
resources with the Software House C•CURE 9000 Security and Event
Management Software and must be UL certified software. Both software products
must support the optional add-on unification license to enable co-existence on the
same platform.
 VMS when unified with C•CURE 9000 shall allow events to be acknowledged in
one client and having it be updated in real-time on the other client.
 VMS when unified with C•CURE 9000 shall allow access control alarms to appear
on victor maps, victor event viewer and in victor reports to provide a true cross-
platform two-way seamless integration of video and access control.
 VMS when unified with C•CURE 9000 shall allow various third party add-ons to be
integrated with victor Application Server to enable client-side Event Management
across Video, Access Control and associated third party products that are either
integrated into victor or C•CURE 9000 (e.g. Video, Access, Fire, Intrusion, Building,
Intercom, Elevator, etc.).
 VMS when unified with C•CURE 9000 shall display in the victor device list all of the
integrated objects from C•CURE 9000 and third party objects that support victor
privilege configuration and authorization.
 VMS when unified with C•CURE 9000 shall capture in the victor journal database
and activity list all of the actions on integrated objects to allow the victor report to
support Video, Access Control and associated third party activities. Activity list
context menus shall include viewing context options for the primary alert object as
well as for a related object.
 VMS when unified with C•CURE 9000 shall allow alarms from integrated objects
(e.g. Elpas) to trigger victor events.
 VMS when unified with C•CURE 9000 shall allow the integrated object types,
including any actions/animation and state changes to be displayed in victor maps.
 VMS when unified with C•CURE 9000 shall allow the VMS client to preview and
print badge/card when using supported card printers.
 VMS when unified with C•CURE 9000 shall support simplified roles and privileges
in unified system.
 VMS when unified with C•CURE 9000 shall allow VMS client to utilize Personnel
views configured in C•CURE. Administrators can create custom templates with the
personnel editor to restrict sensitive data from being viewed or edited by other
clients.
3610-0642-01 A0 victor 23 of 17
 VMS when unified with C•CURE 9000 and using from exacqVision HDVR
recorders shall enable C•CURE to support both onboard and USB I/O module dry
contacts to raise event conditions.
 VMS when unified with C•CURE 9000 shall allow Schedules to support Holiday
groups. Both victor and C•CURE can create Schedules that can be seen by both
VMS and AC clients, with periodic, random and granularity options.
 VMS when unified with C•CURE 9000 and using VideoEdge recorders with face
recognition and face verification licenses, the intelligent solution shall utilize
analytics to alert operators. When access is attempted at a door with a camera, the
unified system will intelligently search the database to provide a confidence level
for matching the person’s face against the profile associated with the credentials.
 VMS when unified with C•CURE 9000 and using VideoEdge recorders with face
recognition and face verification licenses, the intelligent solution shall be capable of
being configured to provide frictionless access control.
 VMS when unified with C•CURE 9000 shall support United States English SQL
database with the SQL collation being us-en United States English default option
only.
2.4.2 System Performance

The VMS shall meet the following system performance:
 Each instance of VMS client shall support up to 4 connected monitors
 VMS client installed on a hardware platform meeting the recommended
specification shall support the simultaneous display of up to 64 video streams
across all connected monitors.
 Each instance of VMS client shall support the simultaneous connection of up to 2
supported CCTV or equivalent keyboards
 VMS client shall support the completion of a motion search over 1 week of
available recorded analog or IP video of a scene containing an average level of
motion throughout, regardless of codec or resolution of the recorded video, within 2
minutes.
 VMS client shall ensure constant audio / video synchronization to within ½ a
second for all supported video and audio devices.
 VMS shall support event and message volumes up to a maximum of 5 transactions
per second
 VMS shall support a maximum total database size of 10 GB when running SQL
Express (approximately 10 million records).
 VMS shall support a maximum total database size of 524,272 TB when running
SQL Server Standard Edition (approximately 525,000,000 million records).
 VMS client shall detect and adapt to network congestion when viewing video from
VideoEdge recorders.
 VMS shall support ability to launch the Diagnostic Utility from victor’s Support page.
2.4.3 Localization
The VMS shall meet the following system performance:
 VMS client shall automatically detect and support / display the time / date format
configured in the Windows operating system.
3610-0642-01 A0 victor 24 of 17
 VMS client shall be able to support at least 18 languages. Users shall be able to
select the desired language to display when launching the application. No
additional installation of the application shall be required. The manufacturer shall
make a list of supported languages available on their website. The supported
languages shall include:
 Arabic
 Chinese (Simplified)
 Chinese (Traditional)
 Czech
 Danish
 Dutch
 English (US)
 French (Standard)
 German
 Hungarian
 Italian
 Japanese
 Korean
 Polish
 Portuguese (Brazilian)
 Spanish
 Swedish
 Turkish
 VMS when unified with C•CURE 9000 shall support the native OS language and
application GUI that are common between the two products
 Arabic
 Chinese (Simplified)
 Dutch
 English (US)
 French (Standard)
 German
 Italian
 Japanese
 Polish
 Spanish
2.4.4 User Authentications (Login Credentials)

The VMS shall support the following user authentications (Login Credentials) options:
 VMS client shall have the ability to choose either Windows Authentication for
Domain/Application Server or Basic Authentication to log into victor.
3610-0642-01 A0 victor 25 of 17
 VMS client shall support ability to institute a double password protection that would
require two unique validated sets of credentials before the feature’s operations can
be carried out (video search and retrieve, instant playback, clip export) to support
privacy rights in applicable European markets.
2.4.5 VMS Client Graphical User Interface (GUI)

The VMS shall support the following graphical user interface (GUI) features:
 VMS client shall be written with Windows Presentation Foundation (WPF)
technology to maximize the quality and quantity of video displayed on connected
monitors. VMS client shall employ Windows 7 style menus and tab-based
navigation to ensure ease-of-use for operators.
 VMS client shall provide end users and administrators with functionality in the
following areas:
 Camera Management / Organization
 Video Live Viewing & Playback
 Audio Live & Playback
 Video Overlay of On-Screen Display
 Video / Analytic / Alarm Rule Search & Export
 Still Image Capture
 Event / Alarm Management
 Advanced Integrated Mapping
 Virtual Matrix
 CCTV Keyboard Support
 Reporting
 User Management / Permission Controls
 Recorder Management
 Storage Video Vault
 Dynamic Bandwidth Management
 Integrated Web Browser
 Event Unification (Unified platforms)
 Object Associated (Unified platforms)
 Access Control Device Management / Organization (Unified platforms)
 Elevator Device Management / Organization (Unified platforms)
 Fire Panel and Device Management / Organization
 Intrusion Device Management / Organization
 Maintenance / Software /License Upgrades
 SDK
 VMS client interface shall be an intuitive user interface that is similar to Microsoft’s
Office Application Suite with its easy navigation.
 VMS client shall provide a GUI that minimizes the number of operator mouse
clicks or keyboard strokes and include “right-click” pop-ups with highlighted default
selections for common operations
3610-0642-01 A0 victor 26 of 17
 VMS client interface shall be user-customizable.

 VMS client shall support the ability of the end user to create a customized
application layout for the client software. The client application shall support
multiple application layouts that can be assigned to each role. These layouts shall
also support ability to automatically adjust to accommodate the screen size when
option for auto-fit is enabled.
 Each application layout can have multiple tabs in the same window. The panes
can have multiple tabs so that different objects such as cameras and tours can be
displayed in the same pane. Each pane shall have the ability to be moved to a
specific screen. Double-clicking on the surveillance tab name shall undock and
open it in full-screen mode.
 VMS client shall be able to swap between two surveillance layouts within the
same surveillance tab via back and forward buttons on the tab menu. The layouts
can be created by drag-and-drop, double clicking or viewing cameras, recorders
and call-ups, but vPTZ call-ups are not supported.
 VMS client shall provide a GUI with organized ribbon bar that supports the
expanded feature set for unification of security for video, access control, fire and
intrusion.
 VMS client shall support dynamically display menu items and controls which are
applicable to the system configuration for improved user experience.
 VMS client shall support dynamic views and ability to add recorders directly within
the Recorders dynamic view, and provide details regarding software serial
numbers and SSA expiration dates.
 VMS client shall provide different background theme options, a dark for low-light
environments and a light for higher contrast in brighter environments.
 VMS client shall be able to use the mouse wheel to scroll through all menus.
 VMS client shall be allowed to resize the toolbar on the surveillance tabs and size
changes are saved as part of the layout.
2.4.6 Device Management / Organization

The VMS shall support the following camera management and organizational features:
 VMS client shall provide users both a Device View and a user-defined Site View of
the following system components:
 Recorders (VideoEdge, Intellex, HDVR, TVR,
exacqVision, Holis, and supported
3rd party)
 Workstations
 Cameras
 Monitors
 CCTV Keyboards and Controllers
 General Purpose Devices
 General Purpose Monitoring Points
 Analog Matrices
 Camera Devices
3610-0642-01 A0 victor 27 of 17
 POS Systems and Devices

 BACnet Devices
 KONE Destination Operation Panel or Car Operation Panel
 OTIS Destination Entry Computer
 ThyssenKrupp Destination Dispatch Elevator System
 Bosch Receiver
 SurGard Receiver
 DSC Panels
 Bosch Alarm Point
 DMP Alarm Point
 SurGard Alarm Point
 DSC Partitions
 DSC Zones
 Simplex4100 Fire Panels
 MZX Fire Panels
 eDCM Controllers
 sDCM Controllers
 EIOC Controllers
 S610 Readers
 sPass Readers
 emerald Reader
 KT Controllers
 (iSTAR) Controllers
 (iSTAR) Doors
 (iSTAR) Inputs
 (iSTAR) Readers
 Outputs
 Device icons (e.g. recorders, cameras, doors, readers, inputs, outputs, etc.) in VMS
Client shall provide clear visual indications of whether the devices are online or
offline.
 VMS shall support custom camera names that are alias used by VMS client. It shall
maintain the original camera names assignment associated by the recorder.
 The Site View shall be completely user-customizable, enabling the organization of
devices, tours, salvos into user-defined, multi-level folders, similar to Windows
Explorer-style file organization.
 A Site View folder may contain an object of any type within VMS.
 VMS client shall allow the user to hide, “unpin” or customize the display location of
the Device and Site View panes within their Application Layout.
3610-0642-01 A0 victor 28 of 17
 VMS client shall allow the user to display the recording state and firmware version
of cameras managed by latest versions of VideoEdge software.
 VMS client shall be able to open the health dashboard and device discovery when
right-clicking on recorders in the device list.
2.4.7 Advanced Integrated Mapping

The VMS shall support the following advanced integrated mapping functions when
licensed:
 VMS client shall support maps to allow visual management of a unified security
system. The maps shall be created by importing AutoCAD files (e.g. DWG, DXF)
and standard raster image files (e.g. JPG, PNG).
 VMS client shall be able to support up to 10,000 object/icons (e.g. recorders,
cameras, card readers, doors, etc.) for each map. The icons shall allow for
monitoring object state and locations as they relate to the site.
 VMS client shall be able to restrict displaying only unmapped objects for selection.
 VMS client shall be able to provide a navigation button to easily go back to or
select a specific map from a drop-down menu.
 VMS client shall be able to display health monitoring information on the map icons.
 VMS client shall be able to create single layer, multi-layer, and nested maps with
the ability to turn on/off layers to show/hide the associated icons. Maps images
shall support ability to pan and zoom.
 VMS client shall be able to have maps open in the same tab for easier navigation.
 VMS client shall be able to enable hover over a map icon and have the associated
camera(s) pop-up a live video window. When right-clicking on a map object in view
mode, it shall display that objects standard context menu to enable further
interaction. Support ability to automatically close opened windows when in hover
mode.
 VMS client shall be able to drag-and-drop cameras, tours, salvos onto a monitor
object on the map and have it displayed onto that remote or local monitor.
 VMS client shall be able to include field-of-view cones to identify expected
coverage for devices
 VMS client shall be able to expand a pane to reveal the current virtual matrix
configuration when a camera is dropped onto the pane on a video wall when virtual
matrix is enabled.
 VMS client shall be able to bubble-up alarms and events through numerous layers
of maps to support seamless alert notifications within any map.
 VMS client shall be able to create custom map icons.
 VMS client shall be allowed to customize the annunciation and color of a point on a
map when creating map or map layer templates.
 Maps shall be automatically stored centrally to allow sharing with any VMS client
that is granted permission.
 VMS shall support creation of maps on the MAS and SAS’s on a large or
distributed system. Maps created on the SAS, along with all of the layers and
objects shall be synchronized to the MAS and be available to a MAS client. Maps
3610-0642-01 A0 victor 29 of 17
created on the MAS shall not synchronize to the SAS to allow objects from multiple
SAS’s.
 VMS client shall display GIS map layer.
 VMS client shall support importing C•CURE 9000 maps into victor client in unified
system.
 VMS client shall display current zoom level on maps as a thumbnail window.
 VMS client shall allow maps to zoom in on objects which are in an active alarm
state, and will choose the highest priority alarm if multiple objects are alarming at
the same time.
2.4.8 Video Live Viewing and Playback

The VMS shall support the following live video viewing and video playback functions:
 VMS client shall support the simultaneous display of MJPEG, MPEG-4, H.264,
H.264+, Zipstream, and ACC video streams within a single video view.
 VMS client shall provide a common user interface and functionality associated with
every camera in the system, regardless of the recorder it is connected to or the
video codec used.
 VMS client shall group the available layouts into three types and each one can be
available by setting the preferences via System Values:
 Standard
 Wide Screen
 Portrait
 VMS client shall allow video streams to be displayed in any of the following views
and support three most recent selections:
 1x1 (Single Camera Standard Format)
 2x2 (4 Cameras Standard Format)
 Guard (6 Cameras Standard Format – 1 Large with 5 Small)
 2+8 (10 Cameras Standard Format – 2 Large Top plus 8 Small)
 12+1 (13 Cameras Standard Format – 1 Large Center plus 12 Small)
 1x1 (Single Camera Wide Format)
 1x3 (3 Cameras Wide Format)
 2+3 (5 Cameras Wide Format)
3610-0642-01 A0 victor 30 of 17

 2+2x2 (6 Cameras Wide Format)
 1+3x2 (7 Cameras 1 Portrait Format and 6 Wide Format)
 1x1 (Single Camera Portrait Format)
 3x1 (3 Cameras Portrait Format)
 1+4x2 (9 Cameras 1 Portrait Format and 8 Wide Format)
 VMS client shall also allow the user to create custom video layouts for video
surveillance with ability to display still images into any video pane. All custom
layouts shall be able to be exported and imported for use by any VMS client.
 VMS client shall allow the user to enable video aspect ratio which stretches the
client-side video beyond the original aspect ratio so that letterboxing is not visible in
each pane. When enabled, both widescreen video (16:9) in a standard definition
pane (4:3), and standard definition video (4:3) in a widescreen pane (16:9) will not
have any black space.
 VMS client shall allow the user to create saved views combining a view, with user
selected cameras, tours or PTZ presets.
 VMS client shall be able to name and save different camera window displays as
salvos or fixed views. Names shall be a maximum of 200 characters long.
 VMS client shall provide for each live window pane a popup menu, available via
right mouse click, to access the settings for the pane.
 VMS client shall allow the user to review motion or embedded analytic searches
from stream-based recording with simple “jump to next” result buttons.
 VMS client shall provide the user with time filter that enables the ability to quickly
perform multi-day searches.
 VMS client shall provide the user with ability to customized On-Screen Display text
that is displayed within video panes. The Camera/Recorder color and font size shall
be changed independently of the Date/Time color and font size to allow for clearer
and legible text against various background scenes.
 VMS client shall allow the user to enable or disable the red alert border for the live
video panes.
 VMS client shall be able to rearrange video sources on a multi-pane surveillance
window with pane-to-pane drag-and-drop operation.
 VMS client shall be able to see the source of alarm trigger with Live Video Hit
boxes for any live surveillance in real-time or in timeline view during instant
playback.
 VMS client shall be able to configure a new custom preset that will use, as default,
the Rectilinear dewarp for all fisheye cameras supported by the victor client dewarp
feature.
 VMS client shall be able to provide System Operators ability to enable or disable
motion tracking on Illustra cameras globally (batch edit) or on a per camera basis
(PTZ setting) and Intelligent guard tour functionality.
2.4.8.1 Surveillance Tracking
3610-0642-01 A0 victor 31 of 17
The VMS shall support the following Surveillance Tracking functions:

 VMS client shall be able to start a session to manually track a person or object
across multiple camera panes within the surveillance perimeter.
 VMS shall provide the ability to configure surveillance tracking arrows on a
camera’s FOV that link to another applicable cameras.
 VMS shall allow clients to create a clip of their tracking session.
 VMS shall allow clients to create bookmarks for the cameras in the surveillance
tracking session.
 VMS shall allow clients to drag and drop cameras from the Device List onto a 1x1
surveillance pane during a tracking session, or use the AD2089 keyboard with an
active virtual matrix to create a tracking session by calling up cameras. It can be
carried out without configuring tracking arrows.
2.4.8.2 InstantView
The VMS shall support the following InstantView functions:
 VMS shall provide the ability on a live video stream to easily open a new tab that is
paused for the same camera to quickly setup the display layout for investigative
purposes.
 VMS shall support InstantView to be displayed side-by-side or to send it to another
display monitor.
2.4.8.3 Instant Playback

The VMS shall support the following instant playback functions:
 VMS shall provide the ability to play, fast forward, rewind directly from video
recorded into a recorders database as well as jump to any point in time where the
feature is supported by the recorder. Supported instant playback speeds shall be:
 Fast Forward x16
 Fast Forward x8
 Fast Forward x4
 Fast Forward x3
 Fast Forward x2
 Clock Speed (x1)
 Frame Forwards
 Frame Backwards
 Clock Speed Rewind (x1)
 Fast Rewind x2
 Fast Rewind x3
 Fast Rewind x4
 Fast Rewind x8
 Fast Rewind x16
 VMS client shall provide the ability to quickly jump back to any user-specified date /
time on all visible cameras without interrupting or obscuring video viewing.
3610-0642-01 A0 victor 32 of 17
 VMS client shall provide the user the ability to select some or all of the video panes
in a Saved View and view recorded video on those panes, while simultaneously
displaying Live video on other panes within the same view.
 VMS client shall provide the ability to view a single camera in multiple panes of a
single Video View.
 VMS client shall provide the ability to view live and recorded video on the same
camera within a single application layout.
2.4.8.4 Timeline Control

The VMS shall support the following timeline control scroll bar feature:
 VMS client shall provide the ability to enable the timeline bar on any surveillance
view by selecting the timeline icon.
 The timeline bar shall display a corresponding data stream bar for each media
stream displayed in the surveillance window.
 The navigation control for the timeline bar shall be divided into years, months,
days, hours, minutes and seconds.
 The video control buttons are located in the center of the timeline and can be used
for instant playback, with a vertical bar representing the current time.
2.4.8.5 Still Image Capture

The VMS shall support the following still image capture feature:
 VMS client shall provide the ability to capture an image from any paused video
stream and directly from the raw video stream.
 The captured image can be all or part of the paused stream image.
 The captured image is launched in its own pop-up window in the VMS client. From
there the operator can:
 Save the image in a variety of formats.
 Copy the image to the clipboard.
 Email the image via SMTP.
 Print the image (actual size or fit-to-page)
 Open the image in an external application (e.g. MSPAINT.EXE).
 VMS client shall support video overlay onto snapshots.
 VMS client shall support emailing a snapshot from a camera with the Send Camera
Image Action. It can be triggered from an event and activated on a schedule.
2.4.8.6 Mechanical & Digital PTZ

The VMS shall support the following mechanical and digital PTZ functions:
 VMS client shall be assigned a PTZ control queue that enables specific roles or
individuals to have higher priority over others to support a hierarchical management
schema.
 VMS client shall provide Digital PTZ capability on all connected analog and IP fixed
cameras (Mega-Pixel and standard resolution). Digital PTZ capability shall include
Picture-in-Picture display.
3610-0642-01 A0 victor 33 of 17
 VMS client shall provide virtual PTZ controls that support ability to create virtual
presets, mouse wheel quick zoom for one-touch zoom in or out, and Picture-in-
Picture display. vPTZ shall be utilized on clip streams to enable cropping and
magnifying the video pane during normal surveillance.
 VMS client shall provide three options for controlling analog or IP PTZ cameras:
CCTV keyboard, on-screen display icons and mouse-based drag and point.
 The on-screen display icons for PTZ controls shall include the ability to pan, tilt,
and zoom, adjust the focus and iris of the camera, call preset positions and run set
patterns where the feature is supported by the underlying camera, encoder or
recorder.
 VMS shall enable the user to activate 1 to 96 preset camera positions through a
transparent control diagram overlay on the live video display of the associated
camera. Where supported by the camera.
 VMS shall enable the user to activate 1 to 10 pre-programmable preset sequences
through a transparent control diagram overlay on the live video display of the
associated camera. Where supported by the recorder.
 VMS client shall be able to use virtual PTZ controls on dome cameras during
playback to better utilize the megapixel forensic video.
2.4.8.7 Call-ups
The VMS shall support the following call-up functions:
 VMS client shall provide an interface for operators to define video tours of related
cameras.
 Video Tours shall support user configurable dwell-times.
 A tour may initiate a preset on a camera.
 VMS client shall provide an interface for operators to define video salvos.
 VMS client shall provide an interface for operators to define fixed video views
 A fixed video view may contain a video tour
 VMS client shall provide a call-up list to make the defined call ups easily accessible
to operators.
 All call ups shall have the option of being assigned a user-configurable or auto-
assigned reference number to enable triggering of the call up via a supported
CCTV keyboard.
2.4.8.8 Send to Commands

The VMS shall support the following send to functions when optional victor Command
Center feature is purchased:
 VMS client shall provide ability to use the Send to command to transfer any tabbed
layout or object such as a specific camera, recorder, surveillance window, or web
site onto any accessible monitor on the security network. The credentials of the
recipient shall dictate the ability to access the information sent from another VMS
client system.
 VMS client shall provide confirmation message regarding the Send to command to
provide acknowledgement that the operation was either successful or that the
attempt had failed.
3610-0642-01 A0 victor 34 of 17
 VMS client shall support option to include the video tool bar on the surveillance
windows that are maximized or during the Sent to command to another monitor.
2.4.8.9 De-Warp Fish-Eye Cameras

The VMS shall support the ability to have the VMS client de-warp VideoEdge supported
cameras that use fish-eye lens. Right-click on the fish-eye camera within the pane of the
Surveillance tab will allow access to select the de-warp method.
 VMS client shall support selecting panoramic de-warp for a broad view of the
scene.
 VMS client shall support selecting rectilinear de-warp for a high qualify view of a
region within the full fish-eye image.
 VMS client shall use the shift key to quickly select the region of the image to de-
warp.
 VMS client shall be able to save de-warped views as part of a layout.
2.4.9 Audio Live Listening and Playback

The VMS shall support the following audio live listening and playback functions:
 VMS client shall support playing live and recorded audio streams from supported
recorders.
 VMS client shall provide an on-screen display indication of which cameras have
associated audio streams.
 VMS client shall provide volume control and mute options to manage audio
playback.
 VMS client shall ensure constant audio / video synchronization to within ½ a
second for all supported video and audio devices.
 VMS client shall be configurable to support sending / receiving calls to / from SIP-
enabled devices for bi-directional audio.
2.4.10 Video Search and Export
2.4.10.1 Date / Time Search

The VMS shall support the following date/ time search functions:
 VMS client shall provide an easy-to-use wizard interface to simplify the
configuration of a date/time search across multiple cameras/recorders within a
maximum of three screens.
 The Date / Time search shall allow the user to simultaneously search as many
connected cameras across many different recorders, as specified by the operator.
 VMS client shall allow the user to additionally request any audio associated with
the video on the specified camera(s).
 VMS shall automatically download the first media clip from a successful search and
start playing the video.
 VMS provides ‘direct export’ mechanism from the Surveillance view. The operator
selects a start and end time via the Surveillance view and all on-screen cameras
are exported in a single operation to the specified destination.
 VMS shall provide the VMS client the ability to search across online, near-line
archived and standby fail-over storage from VideoEdge. When the search criteria
3610-0642-01 A0 victor 35 of 17
spans beyond the online forensic video, victor shall continue the search seamlessly
across VideoEdge archived near-line storage. If any VideoEdge fail-over occurred,
victor search will seamless span across the standby storage of any fail-over mode
VideoEdge recorder.
 VMS client shall be able to playback audio streams independently from the video
streams, mix-match them with different cameras from the same or different servers
for search results from VideoEdge recorders.
 VMS client shall include thumbnail search results for those recorders versions that
support it to provide a simplified visual snapshot of the recorded video. The
thumbnails will be spread across the desired specified search time period and can
be drilled down quickly when double-clicking on a particular image.
 VMS client shall include data visualization that enables data from all searches and
reports to be graphically charted as bar charts and timelines. Ability to easily drilling
down through the data to single events for a wider view for analyzing data patterns.
2.4.10.2 Motion Search

The VMS shall support the following motion search functions:
 VMS shall provide a mechanism to search for motion on a particular camera based
on the following criteria:
 Camera
 Start date & time
 End date & time
 Motion search region
 Amount of Motion (% of Region)
 Duration of Motion (0 to 600 seconds)
 Motion Search Sensitivity (where supported by the recorder)
 VMS client shall enable users to select inactive or active regions of interest to
simplify the configuration of the search criteria.
 VMS shall automatically download the first media clip from a successful search and
automatically start playing the video.
 VMS shall download and play clips from further search results as directed by the
operator, and support ability to jump to next and previous clips.
 From any motion search result, VMS client shall allow the user to add additional,
related cameras to the View and shall automatically synchronize the date/time of
the added cameras to the original search result (“Investigate mode”).
 VMS client shall enable the operator to set the sensitivity of the motion search
setting.
2.4.10.3 Search Across All Available Storage

The VMS shall provide the VMS client the ability to search across online, near-line
archived and standby fail-over storage from VideoEdge. When the search criteria spans
beyond the online forensic video, victor shall continue the search seamless across
VideoEdge archived near-line storage. If any VideoEdge fail-over occurred, victor search
will seamlessly span across the standby storage of any fail-over mode VideoEdge
Recorder.
3610-0642-01 A0 victor 36 of 17
 VMS client shall be able to playback audio streams independently from the video
streams, mix-match them with different cameras from the same or different servers
for search results from VideoEdge recorders.
 VMS client shall automatically utilize the operator’s display settings when providing
the video search results. The search results shall also support ability to open in a
dockable new window to avoid interfering with the current layout configuration.
 VMS client shall include thumbnail searches for those recorders versions that
support it to provide a simplified visual snapshot of the recorded video. The
thumbnails will be spread across the desired specified search time period and can
be drilled down quickly when double-clicking on a particular image.
 VMS client shall include data visualization that enables data from all searches and
reports to be graphically charted as bar charts and timelines. Ability to easily drilling
down through the data to single events for a wider view for analyzing data patterns.
2.4.10.4 Video Intelligence Analytic Search

The VMS shall support the following video intelligence analytic search functions:
 VMS shall support the integrated video analytics included with the VideoEdge
recorders.
 VMS shall utilize the information available from VideoEdge to apply the following
Analytic Search criteria on the recorded video:
 Object Detection to locate objects that move into a region of interest for the
first time.
 Object Direction to locate objects moving in a certain direction through a
region of interest.
 Object Linger to locate objects lingering in a region of interest for a minimum
time period.
 Object Enter to locate objects entering a field-of-view through a doorway or
threshold.
 Object Exit to locate objects exiting a field-of-view through a doorway or
threshold.
 Object Abandoned/Detected to locate objects when they become stationary,
then moved or removed, over a set time period.
 Queue Length to identify when a queue reaches a certain length when
searched over a certain time period.
 Crowd Formation to identify when a certain number of people or objects are
found in a region of interest when searched over a certain time period.
 Color Definitions to apply a color filter to further refine analytic searches on
access control and video data for Object Detection, Direction, Linger, Enter,
Exist Abandoned/Removed and Dwell.
 VideoEdge recorders must have one or more analytic channel licensed in order to
support integrated video analytics engine and allow the VMS to apply the Analytic
Search criteria.
 VMS shall support generation of heat maps from cameras which are configured for
motion detection or video analytics on VideoEdge recorders. These heat maps
shall provide a visual representation of analytic activity over time by using
3610-0642-01 A0 victor 37 of 17
translucent colored pixels overlaid on a still camera image to represent how much
activity each pixel “saw”.
 VMS shall support dwell video analytics from cameras on VideoEdge recorders
which capture people that are mostly stationary within a smaller and more defined
ROI for the a predetermined amount of time and percentage overlap. This analytic
is generally utilized in retail to help identify customer activity in a display or end-cap
area.
 VMS shall support dwell video analytics from cameras on VideoEdge recorders
which capture people that are moving around within a larger ROI for the
predetermined amount of time and percentage overlap. This analytic is generally
utilized to help identify loitering in particular areas.
 VMS shall support Add Search as Alarm Rule to create a new alarm rule using the
criteria defined in a specified search. These alarm rules shall display in the Load
Alarm Rule list under the Search and Retrieve Wizard.
 VMS shall support Alarm Persistence Notification to enable ability to receive
cached alarms for up to 14 days in Recover Mode from VideoEdge recorders that
may have lost connection to the VMS server.
 VMS shall support edge-based analytics for VideoEdge supported devices. They
shall trigger analytic events. The current device models and analytics supported
include:
 Illustra Cameras Face Detection
 Illustra Cameras Blur Detection
The latest list of edge-based analytic devices supported by VideoEdge shall be
available in the VideoEdge Release Notes.
2.4.10.5 Facial Recognition Analytic Search

The VMS shall support the following facial recognition analytic search functions:
 VMS site must have the facial recognition database site license and the VideoEdge
recorders must have one or more facial recognition channels licensed in order to
support integrated facial recognition engine.
Face Recognition search criteria on the recorded video:
 Search against up to 1,000 indexed faces per VideoEdge recorder database
for faster identification and investigation.
 Search across the entire enterprise to find facial matches
 Search for inclusion or exclusion of specific persons and visually see the
associated corresponding video.
 Search specific area of interest on the scene
 Search requires specific percentage of an object within the area of interest
 Load pre-existing alert rules configured on the VideoEdge
 Alerts operators to take immediate action when a face is detected
2.4.10.6 Facial Verification Analytic Search

The VMS shall support the following facial verification analytic search functions:
3610-0642-01 A0 victor 38 of 17
 VideoEdge recorders must have one or more facial verification channels licensed in
order to support integrated facial verification engine.
 VMS shall be a Unified victor / C•CURE 9000 system
 VMS shall utilize the information available from VideoEdge and C•CURE 9000 to
apply the following Face Verification search criteria on the live video:
 Automatically provide visual notification when an access card is used by an
unauthorized person.
 Display live video for Swipe-and-Show to provide real-time cross-reference of
access card user.
 Confirm authorized access card user by displaying associated card holder
name under live video.
 VMS can control access control points for authorized personnel.
2.4.10.7 License Plate Recognition Analytic Search

The VMS shall support the following license plate recognition analytic search functions:
 VideoEdge recorders must have one or more license plate recognition channels
licensed in order to support integrated license plate recognition engine.
License Plate Recognition search criteria on the recorded video:
 Support fuzzy matching for similar alpha-numeric characters
 Search for all captured license plates
 Search for inclusion or exclusion of specific license plates
 Sort LPR search results
 Generate thumbnail for any LPR search results
 Generate reports and data visualization for any LPR search result
 Instant review of video associated with any LPR search result
 Save any LPR search result as an alarm rule
 Search LPR alarm entries in the Journal with filter option
 VMS shall support License Plate Management by creating a black-and-white list by
individual or bulk upload license plates for specific cameras for license plate
recognition.
2.4.10.8 Clip Storage / Export

The VMS shall support the following clip storage and export functions:
 VMS client shall allow the user to export clips of video form one or multiple
cameras, across multiple recorders, in a single export.
 VMS client shall allow the user to assign custom name and export clips to a
location of their choice: the client PC, VMS server or an Administrator-specified
network storage location.
 VMS client shall provide the user the option of exporting video clips in their native
format or in an appropriate non-format which can be played using a standard
player.
3610-0642-01 A0 victor 39 of 17
 VMS client shall support attaching clip notes to exported video which shall be
reviewable by victor Player.
 When exporting clips in Native format, VMS client shall provide the user the option
of exporting a player application along with the video clips to ensure that exported
video can be reviewed on any standard PC without installing VMS client.
 VMS shall support exporting “tamper-protected” video clips using dual-
authentication mechanism (password protection and check-sum validation). VMS
Unified Client and Player shall include a “Verify” button to visually demonstrate that
a video clip has not been tampered with.
 VMS shall support scheduling of clip downloads, clip download integration with
victor events and clip expiration features. Include the ability to set default action to
be the Client (now) or Server (now).
 VMS shall support custom watermarking images to be overlaid on for non-native
exported video clips such as AVI/MP4.
 VMS shall allow ability to view the video clip as it is being downloaded from any of
the supported recorders (e.g. Intellex, HDVR, and TVR).
 VMS shall support Direct Clip action to split a clip that is comprised of multiple
streams to its component streams.
 VMS player shall enable the user to playback up to 64 simultaneous video clips
regardless of video codec (MJPEG, MPEG-4, H.264, H.264+, Zipstream or ACC) in
any of the following layouts:
 Single Pane (1x1)
 Single Pane Wide (1x1)
 2+3 (2 large panes, 3 smaller panes)
 2x2
 2x3
 3x3
 3x4 (widescreen video on widescreen monitors)
 4x3 (widescreen monitors)
 4x4
 5x5
 6x6
 8x8
 Guard (1 large pane, 5 small panes)
 12 + 1 (1 large pane, 12 small panes)
 2+8 (2 large panes, 8 smaller panes)
 VMS player shall enable the user to have full video playback controls within
exported clips. Video playback controls shall include:
 Fast Forward x4
 Fast Forward x3
 Fast Forward x2
3610-0642-01 A0 victor 40 of 17
 Clock Speed (x1)

 Frame Forwards
 Frame Backwards
 Clock Speed Rewind (x1)
 Fast Rewind x2
 Fast Rewind x3
 Fast Rewind x4
2.4.11 Events and Event Monitoring

The VMS shall support the following events and event monitoring functions:
 VMS shall support unlimited operator configurable events, including the action-
based trigger of events.
 The system shall provide 8 event priority levels with pre-defined colors and labels.
 The system shall allow an event to be configured to:
 Be sortable by event name, date/time, priority, state, and any other
displayable information.
 Require or not require operator acknowledgment.
 Display an operator-defined text message upon event activation.
 Allow the operator to associate an audio wave file with the event.
 Run imports and exports.
 Run reports and remove report results.
 VMS client shall provide an Event Viewer tab that displays a sortable list of active
alarms or events within the system. The Event Viewer tab shall have the ability to
be incorporated into an Application Layout with other tabs (Video Surveillance tabs,
Site View, Device View, etc.) or to occupy all of one connected monitor.
 VMS shall be configurable to display all events (alarms) in color based on the user-
specified priority of the event.
 VMS shall support audible alarm annunciation at operator workstations (operator
configurable audio (WAV) files associated with alarms).
 VMS shall be able to trigger one or more individual preset actions in the response
to system events (or alarms) enabling users to automatically position cameras on
relevant areas of interest.
 VMS shall be able to trigger one or more fixed views in the response to system
events (or alarms) enabling displays of up to 64 cameras to be automatically
presented on specified single or multiple monitors, including Virtual Matrix
monitors, to easily show all the video related to the event.
 VMS Event Viewer tab shall be capable of displaying the following features:
 System clock.
 Date/time when the event was received by the server
 Count of the active events.
 Clear event.
3610-0642-01 A0 victor 41 of 17
 Clear all events

 Event action message (automatically display selected message for event).
 VMS Event Viewer tab shall provide the ability to view video associated with an
event within the same GUI.
 Event related video shall by default begin displaying video 30 seconds prior to the
time of the event.
 VMS Event Viewer shall provide VMS client standard video controls (FFW, RW,
Frame forward, etc.) to easily review video prior to the pre-alarm time and after the
post-alarm time without leaving the Event Viewer tab.
 VMS Event Viewer shall provide filtering to enable ability to exclude events that are
restricted from acknowledgement, and switch the event to a non-grouped flat view.
 VMS Event Viewer shall include displaying the local time of the recorders
(VideoEdge, Intellex) which triggered the alerts to allow the VMS client to easily
support systems that span multiple time zones.
 Events configuration shall allow the user to enable “Event Breakthrough” which
shall bring the Event Viewer tab to the forefront of a user’s Application Layout when
a specified event occurs.
 VMS shall allow configuration of events to be created in a flow chart format, quickly
viewed and events cloned from one device to another via a simple drag-and-drop
method for simplified event configuration.
 VMS shall allow configured events to be quickly viewed and events cloned from
one device to another via a simple drag-and-drop method for simplified event
configuration.
 On a large or distributed system, events configured on the MAS shall be global to
enable all events to be synchronized to all SAS’s.
 VMS shall allow configured events to send email when a specified event occurs.
 VMS shall allow configuring firmware flash action on iSTAR door control on
schedule time.
 VMS server shall support software triggered external camera alarms from
exacqVision recorders. They can be called and paired to alarms and events in a
victor-only or Unified victor / C•CURE 9000 system.
 VMS shall allow the attachment of a text file or web link to enable the procedure to
be viewed and read for specific events.
2.4.12 Scheduling
The VMS shall support the following scheduling functions:
 VMS shall provide users with ability to manage the execution of events or journal
triggers which are to be activated only during specified time ranges in a scheduler.
 VMS shall allow ability to select and build schedules by Day, Week (Sunday-to-
Saturday), Work Week (Monday-to-Friday), and Month using the schedule editor’s
calendar control.
 Schedules are assigned to actions through the Event/Schedule Setup editor.
 When a schedule is active (current date/time is within the specified time interval),
only the associated events shall be triggered while all others will not be triggered.
Alerts will continue whether or not the schedule is active.
3610-0642-01 A0 victor 42 of 17
 VMS shall dynamically update the status of all schedules on the schedule show all
page.
 VMS shall support ability to specify a clearance schedule individually for each
personnel record within the personnel editor when the victor Application Server is
unified with C•CURE.
2.4.13 Analog Matrix

The VMS shall support the following analog matrix functions:
 VMS client shall provide users with ability to add one or more MP3200 or MP48
matrix switches to the victor system.
 Each matrix can specify one or more workstations to which they are serially
connected.
 The analog matrix editor will allow configuration of satellite connections on
supporting matrices.
 Analog matrix feeds which are coupled to recorder feeds can be described in the
editor to allow playback.
 The analog matrix editor will allow configuration for playback channel.
 The analog matrix editor shall auto-assign input pseudo-numbers and gives the
user the ability to manually edit these auto-assigned values.
 Once added to the system the matrices will be available for inclusion in a virtual
matrix profile so they can be controlled from a particular workstation via an
attached keyboard.
 VMS shall provide users with ability to update the analog matrix configuration by
importing an EasyCPU (.mpcpu) file.
2.4.14 Virtual Matrix

The VMS shall support the following virtual matrix functions when licensed:
 VMS client shall allow the user to configure the system as a Virtual Matrix –
controlling which cameras, tours or salvos are displayed in each pane of each
monitor connected to the Client.
 Virtual Matrix control shall be via CCTV keyboard or PC keyboard and mouse.
 VMS client shall allow for the creation of an unlimited number of Virtual Matrix
profiles. Each Profile shall have its own unique name, camera pseudo-numbering,
salvo pseudo-numbering and monitor pseudo-numbering scheme for maximum
flexibility of system configuration.
 VMS client shall allow sending call-ups (cameras, tours, etc.) to specific virtual
matrix monitors using the right-click “Send To” surveillance command.
 The Virtual Matrix Editor shall auto-assign camera pseudo-numbers and gives the
user the ability to manually edit these auto-assigned values.
 The Virtual Matrix Editor shall include a “Preview” function that visually displays
how the video panes will be numbered across all defined monitors.
 The Virtual Matrix Editor shall auto-assign video pane numbers across all defined
monitors and shall allow the user to manually modify these assignments – including
defining a fixed start number for each monitor.
3610-0642-01 A0 victor 43 of 17
 VMS client shall display the Virtual Matrix camera number on the video pane when
active to overcome naming limitations from newer USB joysticks and gamepads.
2.4.15 CCTV Keyboard and Controllers

The VMS shall support the following CCTV keyboard and controller functions:
 VMS client shall support PTZ, Virtual Matrix and video control using the following
CCTV keyboards and controllers in addition to the system keyboard:
 American Dynamics – ADD2088
 American Dynamics – AD2089
 American Dynamics – ADCC1100
 American Dynamics – ADTTE
 Axis – 295 Video Surveillance Joystick
 Axis – T8311 Video Surveillance Joystick
 ExacqVision – VM Desktop Model 100-590-2130
 Gamepads – X-input Compatible Models
 Pelco – KBD300A
 ShuttlePro – v2
2.4.16 Reporting
The VMS shall support the following reporting functions:
 VMS shall be capable of displaying a log of all activity that occurs in the system,
from object state changes and operator logon/logoff to video alert information.
 VMS shall provide a scrolling list of lines or tiles showing current activity on the
system.
 VMS shall display activity in real-time as data is being transmitted by connected
cameras and recorders.
 VMS shall allow for a “freeze” function that permits an activity to be selected and
temporarily prevents the display of subsequent activities which would push the
selected activity off the screen.
 VMS shall provide reports on the following:
 All System Messages
 All Configuration Changes
 State Changes
 Operator Login
 System Activity
 System Error
 Video Alarms
 Video Clip Access
3610-0642-01 A0 victor 44 of 17
 Objects Created
 Objects Deleted
 Objects Changed
 References Added
 References Removed
 Uptime of VideoEdge Recorders (V5.1 and higher)
 Video Start and End Times for VideoEdge Cameras (V5.1 and higher)
 Video Duration for VideoEdge Cameras (V5.1 and higher)
 VMS shall, for every operator logged into any Client, log which every video search
that is executed, including which cameras were searched over what date/time
period.
 VMS shall, for every operator logged into any Client, log all video exports, including
the camera names and the start and stop date/time of the video clips exported.
 VMS shall allow sending email of journal reports and visualizations.
2.4.17 Clip Builder

The VMS shall support the following clip building functions:
 VMS shall be capable of editing video clips by easily adding clips via drag-n-drop
into a timeline for cropping, cutting, and splitting for multiple clip files at once.
 VMS shall allow users the ability to create smaller clips from existing clips, and then
stitch them together to build an incident clip from all supported recorder and
camera types.
 VMS shall be capable of adding the edited clips to an incident report or for export.
2.4.18 Incident Builder

The VMS shall support the following incident building and reporting functions when
licensed:
 VMS shall be capable of providing a template for creating an incident report.
 VMS shall allow users to combine all motion and/or analytic alerts search results
into a single video clip.
 VMS shall allow users to manage all of the information and collect the data into the
incident report. It shall include, but not limited to the following:
 Recorded Video Clips with integrated audio
 Recorded Video Clips
 Still Images
 Report Data
 Report Charts
 User Inputted and Edited Notes
 Supported External Files
 VMS shall allow users to export the incident report using templates.
 VMS shall support for centralize storage of incident templates.
3610-0642-01 A0 victor 45 of 17
 VMS shall support creating secure incident export package and playback in victor
player. Exported incidents can also be viewed using third party applications that
support the media types.
 VMS shall support creating video bookmark either single point in time or with begin
and end time.
 VMS shall support the listening of integrated audio in both the Incident Builder and
Clip Builder applications.
 VMS shall support Incident Locker that allows administrators, investigators and
users with allocated permissions to lock / unlock incidents. When enabled, it
prevents making further changes to the incident while allowing all of its components
to be viewed and exported.
 VMS shall support the ability to enforce specifying an alternative username and
password credentials for accessing clips / incidents to prevent direct access via
Windows.
2.4.19 Presentation Builder

The VMS shall support the following presentation building functions when licensed:
 VMS shall support three timelines to manage the organization of the video, image
and documents files for the presentation.
 VMS shall utilize the Incident Builder outputs and be capable of combining the
video clips, images and documents and exporting them as either a Incident
Presentation or Report Export. The victor Player can also be exported alongside
both of these.
 VMS shall include by default three report templates (BOLO, Media Clip Report,
Blank) as well as provide ability to support any custom templates.
 VMS shall be capable of verifying any exported packages to ensure valid chain of
custody from the original export date.
2.4.20 Event Management

The VMS shall support the following event management functions:
 VMS shall support dual phase acknowledgement with the ability to acknowledge an
event, investigate the incident to determine what occurred, and then log a message
either as a predetermined drop-down or user input field to ensure a seamless event
workflow.
 VMS shall support using motion meta-data or embedded video intelligence to
provide a bounding box that indicates what caused the alarm to be fired for easy
visual identification within the Event Viewer.
 VMS shall support ability to customize how individual events are configured with
regard to Acknowledge and Clear options that are assigned to event priorities.
 VMS shall support an Event Viewer that enables the user to acknowledge and/or
clear events individually or collectively by group. When the event is acknowledged,
it shall be automatically removed from the Active pane and then added to the
Acknowledged pane for further review.
 VMS shall support event configurations for all objects in all SAS’s under the MAS
Event Setup on a large or distributed system. It shall support Configure All on the
MAS to synchronize to all SAS’s, as well as configuration of specific objects.
3610-0642-01 A0 victor 46 of 17
2.4.21 Object Association

The VMS shall support the following object association functions:
 VMS shall support ability to allow any device within the security system (e.g.
camera, door, etc.) to be linked to as many as five other objects. It shall utilize
linking of unrelated victor objects with the intent of enabling incident building
capability.
 Object associated within the VMS shall enable a Review option on the context
menu of associated objects which will open a guard view that displays the source
and associated objects. The association will be made with the Reports, Event
Viewer and Activity List to simplify the task of reviewing events in the Event Viewer
and objects in the maps. Hovering over the device icon on the map and clicking on
the event could call-up associated video cameras and automatically synchronize
the playback to the time of the event for easier investigation.
 VMS client shall support associated video with any device. The camera context
menu in the device list shall include a “view associated video” option where a
camera/door has other cameras associated to it.
2.4.22 Storage Video Vault

The VMS shall support the following storage video vault functions:
 VMS shall provide the ability to protect media on VideoEdge recorders from being
data culled, by tagging the associated video and/or audio files. The vaulted items
can be reviewed and/or exported from victor, and their vault status can also be
changed to allow the files to be overwritten by VideoEdge.
 VMS shall provide the ability to dynamically define the percentage of an available
storage volume for use as the video vault without impacting any recorded video or
requiring formatting of volumes.
2.4.23 User Management / Permission Controls

The VMS shall support the following user management and permission control functions:
 VMS shall protect access to objects via role based security permissions.
 VMS shall provide the following four pre-configured roles to facilitate easy initial
system configuration:
 Administrator – Full system access
 Power User – High level access but the users cannot edit users and roles or
add new devices to the system
 Investigator – Secured user who can manage searches, clips and camera
views. No access to device level features
 Guard – Basic access. Users can primarily view information but not modify
settings
 Viewer – Basic View only role.
 VMS shall allow further user defined roles to be created and customized to the
user’s needs.
 VMS shall provide ability to simplify role assignments and configure access to
types and objects through bulk configuration.
 For any individual user or group of users, the Role Editor shall allow the user to
control users’ access to any of the following functions:
3610-0642-01 A0 victor 47 of 17
 Disable or enable access to any of the Menu-Ribbon bar functions, including

Video Search, Events Web Browser, etc.
 Disable or enable access to export clips as non-native AVI/MP4
 Add, edit or delete any object from the system (e.g., cameras, recorders,
keyboard, clips, folders, etc.)
 Display / hide any camera, recorder, keyboard, monitor or other object in the
system
 Operate manual PTZ controls on an analog or IP PTZ camera
 View recorded video on any connected camera or recorder
 Listen to audio on any connected camera
 Execute Time/Date or Motion searches on selected cameras or recorders
 Export video from selected cameras or recorders
 Within VMS, objects shall be displayed to the operator based on his/her assigned
operator privilege. The operator shall only be able to monitor/command those
objects for which he or she has been assigned privilege.
 When an operator logs out of a workstation and a new operator logs on, the objects
displayed on the workstation screen shall be dynamically updated to display only
those objects for which the new operator has privilege and utilize their default
workstation layout.
 VMS client shall allow the association of a default Application Layout to each
defined Role, so that when an operator assigned to that role logs into any VMS
client, the default Application Layout is displayed.
 VMS shall allow operators to be created and associated with a Windows Logon
account.
 VMS shall support single sign on of users using the Windows account of the logged
on user.
 VMS shall allow administrators to option to use the LDAP to search Active
Directories over IP networks to administer user roles and profiles from a single
centralized LDAP server.
2.4.24 Device Discovery

The VMS shall support the following device discovery functions:
 VMS shall provide a device discovery tool that can be used to discover American
Dynamics recorders (VideoEdge NVR and Hybrid, Intellex, HDVR, TVR and Exacq
Vision) and their associated cameras on the victor network. victor Express will be
limited to support VideoEdge and Intellex recorders.
 VMS shall allow ability to set separate preferences for each supported device type
by configuring the system level device discovery settings.
 VMS shall support initiating device discovery mode and providing an interface that
automatically separates discovered cameras, configured cameras and ignored
cameras for each discovered recorder.
2.4.25 Recorder Administration

The VMS shall support the following recorder administration functions:
3610-0642-01 A0 victor 48 of 17
 VMS shall provide an interface to allow the user to add, edit or delete recorders
(VideoEdge NVR and Hybrid, Intellex DVR, HDVR, TVR, Exacq Vision, and any
purchased/supported add-on video devices) to / from the system. victor Express
will be limited to support VideoEdge and Intellex recorders.
 VMS shall provide an interface to configure the VideoEdge NVR and Hybrid
recorders using the native web administration page.
2.4.26 Integrated Web Browser

The VMS shall support the following integrated web browser functions:
 VMS client shall include an integrated Web Browser tab that can be combined with
other user interface components (Video Views, Site View, Event Viewer, etc.) into
an Application Layout. The Web Browser tab shall allow operators to continue
monitoring their security system while also receiving weather or news updates from
web-based information sources.
 Access to the Web Browser tab can be restricted via roles and permissions.
2.4.27 Data Storage / Encryption

The VMS shall support the following data storage and encryption functions:
 All programmed information, as well as transactional history, shall be automatically
stored in the database for later retrieval and backup. VMS shall support
configurations where the VMS database(s) may be installed on a hard drive on
VMS, on an independent database server, or in an existing corporate database
server.
 VMS shall allow activity history to be written to a database. The system shall have
the capacity to store a minimum of 50 million transactions. There shall be a method
of backing up the activity history on external media and then restoring and
replaying it.
 VMS shall support AES 256-bit encrypted communications between server and
VMS client.
 VMS shall support TLS encryption connections to VideoEdge to enable capability
to encrypt all RTSP communication between the VMS client and VideoEdge
recorders.
2.4.28 Database Backup / Restore

The VMS shall support the following database backup and restore functions:
 VMS shall provide a means to collect, save and restore the system data. VMS can
back up an existing Tyco database or restore a database from a specified folder
location for the system SQL instance.
 VMS shall provide this utility within the existing Server Configuration application.
 VMS shall provide ability to create and restore VideoEdge configuration backup
files from the victor Unified client.
2.4.29 Dynamic Bandwidth Management

The VMS shall support the following dynamic bandwidth management functions:
 VMS client shall allow the user to select from the status bar the bandwidth from the
client to the VideoEdge recorders to utilize the frame dropping and transcoding of
3610-0642-01 A0 victor 49 of 17
resolution for optimal viewing experience for VMS clients connecting from remote
locations with narrow bandwidth deployments:
 TCP (or else UDP)
 VPN
 LAN Connection (100/1000 Mbps)
 High-Speed Broadband (10 Mbps)
 Broadband (5 Mbps)
 Low-Speed Broadband (1 Mbps)
 Fractional T1 (512 Kbps)
 Narrowband (256 Kbps)
 Modem (128 Kbps)
 VMS client shall receive native video stream that may be modified by the
VideoEdge recorder in an attempt to provide it at a lower data rate that can be
consumed within the constraints of the victor surveillance pane’s dimension and
connection capability. VideoEdge supports frame dropping, transcoding, image
smoothing, selectable data rates, and prioritizing of frame rate or resolution when
deployments are over a WAN with narrow bandwidth access by remote VMS
clients.
 VMS client shall monitor and provide system performance information on the status
bar:
 CPU Usage
 Available Free Memory
 Available Free Disk Space
 Network Usage for Individual NICs and Total Usage
2.4.30 Networking
The VMS shall support the following networking functions:
 VMS shall support the use of Ethernet networks as the communications path
between VMS server or client and supported recorders such as Intellex and
VideoEdge. The communications between VMS server and the supported
Recorders shall be encapsulated in a TCP/IP network/transport layer.
 VMS client shall allow the Administrator to control which network port VMS shall
use for video transport in a Wide-Area-Network environment.
2.4.31 Health Monitoring

The VMS shall support a health monitoring dashboard that will enable the victor Unified
Client to quickly identify the status of the devices on their system when licensed.
Identifying the cause can be achieved by drilling down through flagged items.
 VMS health dashboard shall offer the status of system recorders (e.g. Normal,
Reboot, Protection Status - Monitor, Protection Status - Failover, Alarm Recovery
Completed, and Sensor Alarm).
 VMS health dashboard shall offer the status of Recorder Storage (e.g. Normal, No
Volumes, Volumes Missing, Volume Corrupt, Volume Failed, New Volume, volume
Re-added, Unhealthy Disk, Disk Temperature, Raid Degradation, and Disk Full).
3610-0642-01 A0 victor 50 of 17
 VMS health dashboard shall offer the status of system camera alerts (e.g.
Unknown, Normal, and Video Loss).
 VMS health dashboard shall offer the status of video channel storage alerts (e.g.
Normal, Maximum Retention, and Minimum Retention).
 VMS health dashboard shall show the health of all enterprise-wide supported
devices when monitoring at the MAS on a large or distributed system. The states
will be correct when launched and will be dynamically updated.
 VMS health dashboard shall be able to exclude disabled devices to eliminate non-
applicable items and clear false offline camera alerts.
 VMS health dashboard shall display devices within tabs on device view for
improved organization.
 VMS health dashboard shall display a summary of the active health alerts in the
system.
 VMS health dashboard shall provide date and timestamp of the alerts/malfunctions
that occurred to confirm time of failures.
 VMS health dashboard shall be able to remove Intellex cameras from the Devices
and Sites tab.
 VMS health dashboard shall be able to have option to flag camera alerts as its
parent recorder alerts.
 VMS health dashboard shall be able to report up to three streams of Video Stream
Failure and Dark Frame Detection for each camera for victor Unified Clients.
 VMS health and alert dashboard shall retrieve data stored on the victor Application
Server to allow both victor Unified Client and victor web client to retrieve past alerts
to determine accurate recorder and camera status.
2.4.32 Help
The VMS shall support the following help functions:
 VMS shall provide access to help topics, which define the functions and operation
of the program.
 VMS GUI shall provide easy access to the program version information.
 VMS shall include link to download and view training video of VMS features.
2.4.33 Printers
The VMS shall support the following printer functions:
 VMS shall support report printing. The report printer(s) may be connected directly
to the client PC, or shared over a network. VMS shall support as report printer(s)
any printer for which a printer driver exists within the host operating system.
2.4.34 victor Web Client

The VMS shall support the following web solutions:
 VMS shall be able to choose victor Web in the latest Unified installer, as well as
standalone installer to setup a compatible Windows system as the victor Web
Client portal for a standalone host or an existing victor Application Server host.
3610-0642-01 A0 victor 51 of 17
 VMS web client solution shall support standard web browsers to view live/recorded
video from one or multiple VideoEdge recorders without the need to install any
drivers or plug-ins.
 VMS web client solution shall support dock-view video and help section for
improved user experience. Dockviews shall also remember selected object.
 VMS web client solution shall support PTZ control, fixed views, camera tours,
salvos, sites, clips, event monitor, event setup, diagnostics, video search, text
stream search, logs, event timeline, devices, dock able views, and health
monitoring.
 VMS web client solution shall support snapshots, building out PTZ support with
preset, pattern and sequence.
 VMS web client solution shall support accessing cameras from multiple VideoEdge
recorders without requiring to logging in/out of each individual VideoEdge recorder
(different IP addresses) for seamless user experience.
 VMS web client solution shall support any of the following video layouts:
 1x1 (Single Pane)
 1x2
 1x3
 1 + 4x2
 1+5 (Guard)
 2x1
 2x2
 2x3
 2+3
 3x1
 3x3
 VMS web client solution shall support victor scrub for local playback controls at 1x
speed, similar to YouTubeTM control.
 VMS web client solution shall support bandwidth-efficient “virtual camera” streams
that enable a user to setup specific camera views on a multi-pane layout (e.g. 2x2)
that will delivery it as a single stream to the clients.
 VMS web client solution shall support multiple default accounts that provide
different levels of permission.
 VMS web client solution shall have the ability to support Access Control Device
Setup, Personnel and Swipe-n-Show when the victor Application Server is unified
with C•CURE 9000.
 VMS web client solution shall have the ability to support Health Monitoring. The
dashboard shall be dynamically populated with VideoEdge recorders and their
cameras when logging into victor Web as a victor Application Server operator user
account. Heath status for up to three individual streams of Video Stream Failure
and Dark Frame Detection for each camera. It shall supporting viewing a snapshot
from a camera along with its health details.
 VMS web client solution shall have the ability to support Maps and one or more
Maps exists on victor Application Server.
3610-0642-01 A0 victor 52 of 17
 VMS web client solution shall have the ability to support Retail Reporting. It shall
also be able to generate a report for a camera that includes health details with
snapshots (V5.1 and higher VideoEdge recorders).
 VMS web client solution shall dynamically include VideoEdge recorders and
cameras when they are added, and sites when they are created by the VMS client.
 VMS web client solution shall support launching a monitor view of cameras and/or
tours onto an external video output of a VideoEdge Hybrid spot monitor.
 VMS web client solution supports viewing real-time POS text streaming that is
configured on the VideoEdge recorder. Text Stream Search shall support option to
set number of seconds before and after the transaction search.
 VMS web client solution for Windows shall be able to support at least 6 languages.
Users shall be able to select the desired language to display when launching the
application. No additional installation of the application shall be required. The
manufacturer shall make a list of supported languages available on their website.
The supported languages shall include:
 English (US and GB)
 French
 German
 Italian
 Spanish
 VMS web client solution shall support recorded video searches on LPR alarms
provided that there are License Plate Recognition analytic channel licenses being
utilized on the VideoEdge recorders.
 VMS web client solution shall support recorded video searches on Perimeter
Protection alarms.
 VMS web client solution shall support Operators to login as a victor Application
Server Operator to view text streams, saved Views, Tours, and custom layouts
within the web client GUI,
 VMS web client solution’s Event Monitor page will receive notification alarms with
associated video for LPR and Perimeter Protection alerts.
 VMS Web LT base solution shall by default be included on the VideoEdge
recorders (V4.6 and higher) which are running SuSE Linux Enterprise Server.
2.4.35 Push-to-Talk
The VMS shall support the following broadcast audio communication:
 VMS shall offer operators a push-to-talk feature that will allow audio to be
broadcasted to VideoEdge recorder which, in turn, can then transmit it to speakers
or a PA system.
2.4.36 Maintenance / Software Upgrades

The VMS shall support the following maintenance and software upgrades:
 Software updates for the VMS software suite (Express or Application Server,
Unified Client, Player) shall be supported from any fast and reliable connection,
whether it is executed over the LAN, WAN or internet.
3610-0642-01 A0 victor 53 of 17
 Deployment of software updates for the VMS software (Unified Client, Player) and
VideoEdge images (NVR, Hybrid) shall be easily deployed using the Update
Server. The victor Unified Client shall be automatically prompted for upgrade when
they are setup to be notified when newer software is available from the Update
Server running on the victor Express or Application Server. The victor Unified
Client, with appropriate credentials, shall also be able to easily upload newer
VideoEdge firmware to the recorders when newer images are available on the
Update Server.
 Installer for the software updates for the VMS software suite (Express or
Application Server, Unified Client, Player) shall automatically include the installation
of any newly required pre-requisite software and/or database updates.
 Software updates shall generally not require a restart or reboot of the VMS server.
2.4.37 License Manager

The VMS shall utilize the License Manager application for license management and
status:
 License Manager shall support victor Web Client (standalone), victor Express,
victor Professional, and/or C•CURE 9000 deployments.
 License Manager shall provide overall license information, software status, port
information, SSA expiration dates, and overall details for individual software
versions and licenses installed on the local host.
 License Manager shall be automatically installed during any new or upgrade
installation for victor Web Client (standalone), victor Express, and victor Application
Server (victor Professional, C•CURE 9000 and Unified victor / C•CURE).
 License Manager shall be utilized to generate a XML file that captures the system
information details. This file is required for license registrations.
 Registration to receive license updates for the VMS software shall be supported
from any fast and reliable connection, whether it is executed over the LAN, WAN or
internet. Updated licenses for the same or newer versions of software shall be
automatically generated online and immediately delivered via e-mail when product
is under warranty or valid Software Support Agreement contract.
 License Manager shall be utilized to apply licenses to the host. When a new or
updated license file is applied, it shall not require a restart or reboot of the VMS
server, but only a restart of the applicable services and application.
 For Centralized Licensing sites, the License Manager shall be used to assist in
transferring compatible recorders to use centralized licensing.
2.4.38 Software Support Agreement

The VMS shall support the following software support agreements:
 Annual Software Support Agreements shall be available for all software products.
The maintenance agreement shall provide customers with updates and technical
support for their applicable software products.
 For a Centralized victor Application Server, the applicable VideoEdge licenses that
were successfully transferred over and/or added to the victor license file shall be
incorporated into the victor Software Support Agreement.
3610-0642-01 A0 victor 54 of 17
2.5 SYSTEM REQUIREMENTS

The VMS shall support the following system requirements:
2.5.1 victor Application Server Physical Server Requirements (victor Only)

victor only
Standalone Enterprise Enterprise
victor Only SAS MAS
Physical victor Application Server Quad- vAS Host vAS Host vAS Host
Monitor
Win7 (Pro/Ent) (Latest SP) 64-bit 1 64-bit 1 64-bit 1 n/a
Win8 (Pro/Ent) (Latest SP) 64-bit 1
64-bit 1
64-bit 1
n/a
Win10 (Pro/Ent) (Latest SP) 64-bit 1
64-bit 1
64-bit 1
n/a
Operating
Win2008 R2 (Latest SP) n/a 64-bit 1
64-bit 1
64-bit 1
System
Win2012 (Latest SP) n/a 64-bit 1 64-bit 1 64-bit 1
Win2012 R2 (Latest SP) n/a 64-bit 1 64-bit 1 64-bit 1
Win2016 (Latest SP) n/a 64-bit 1 64-bit 1 64-bit 1
SQL Express 2008 R2 64-bit 1 64-bit 1 64-bit 1 n/a

SQL Express 2012 64-bit 1
64-bit 1
64-bit 1
n/a
SQL Express 2014 64-bit 1 64-bit 1 64-bit 1 n/a
SQL SQL Express 2016 64-bit 1

64-bit 1
64-bit 1
n/a
Database SQL Server 2008R2(Std/Ent) 64-bit 1
64-bit 1
64-bit 1
64-bit 1
SQL Server 2012 (Std/Ent) 64-bit 1 64-bit 1 64-bit 1 64-bit 1
Xeon Xeon Xeon Xeon

CPU Intel Processor E5-1603 E5-1603 E5-1607 E3-1240
2.8 GHz 2.8 GHz 3.0 GHz 3.3 GHz
RAM System Memory 16 GB 16 GB 16 GB 24 GB
NIC Gigabit Ethernet    
(2) (2) (2)
NVIDIA NVIDIA NVIDIA
Quadro Quadro Quadro 600 Integrated
Video Graphics
600 600 (2) 1GB Onboard
(2) 1GB (2) 1GB GDDR3
GDDR3 GDDR3
Physical Quantity (1) HDD 2 (1) HDD 2 (2) HDDs 2 (2) HDDs 3
HDD Primary (9000 Runtime) 500 GB 2 500 GB 2 500 GB 2 500 GB 3
Secondary (Data Backups) n/a n/a 500 GB 2 500 GB 3
Optical DVD+/-R Dual-Layer    
USB 2.0 or 3.0    
I/O Keyboard/Mouse    
3610-0642-01 A0 victor 55 of 17
(4) (4) (4)

Monitor Wide-Screen 
1080p 1080p 1080p
1
Recommended Operating System and Database
Supported OS include Windows 7 SP1 (64-bit Unified), Windows 8 SP1 (64-bit
Unified), Windows 10 (64-bit Unified), Windows Server 2008 R2 (64-bit Unified),
Windows Server 2012 (64-bit), Windows Server 2014 (64-bit)
2
Enterprise Drives (SATA 7,200 rpm)
3
Enterprise Drives (SAS 15,000 rpm)
2.5.2 victor Application Server Physical Server Requirements (Unified)

victor + C•CURE 9000
Unified victor/C•CURE Standalone or Standalone or
Physical victor Application Server Enterprise SAS Enterprise SAS Enterprise MAS
(L,M,N) (P,Q,R,R+,S+,T)
Win7 (Pro/Ent) (Latest SP) 64-bit 1 n/a n/a
Win8 (Pro/Ent) (Latest SP) 64-bit 1 n/a n/a
Win10 (Pro/Ent) (Latest SP) 64-bit 1 64-bit 1 n/a
Operating
Win2008 R2 (Latest SP) 64-bit 1
64-bit 1
64-bit 1
System
Win2012 (Latest SP) 64-bit 1 64-bit 1 64-bit 1
Win2012 R2 (Latest SP) 64-bit 1 64-bit 1 64-bit 1
Win2016 (Latest SP) 64-bit 1 64-bit 1 64-bit 1
SQL Express 2008 R2 64-bit 1 n/a n/a

n/a n/a
n/a n/a

n/a n/a
Database SQL Server 2008R2(Std/Ent) 64-bit 1 64-bit 1 64-bit 1
SQL Server 2012 (Std/Ent) 64-bit 1 64-bit 1 64-bit 1
Xeon Xeon Xeon

CPU Intel Processor E5-1607 E3-1240 E5-2450
3.0 GHz 3.3 GHz 2.1 GHz
RAM System Memory 16 GB 24 GB 24 GB
NIC Gigabit Ethernet   
(2)
NVIDIA Quadro Integrated Integrated
Video Graphics
600 Onboard Onboard
(2) 1GB GDDR3
Physical Quantity (2) HDDs 2 (2) HDDs 3 (2) HDDs 3
HDD Primary (9000 Runtime) 500 GB 2 500 GB 3 1TB 3
Secondary (Data Backups) 500 GB 2 500 GB 3 1TB 3
3610-0642-01 A0 victor 56 of 17
Optical DVD+/-R Dual-Layer   

USB 2.0 or 3.0   
I/O Keyboard/Mouse   
(4)
Monitor Wide-Screen  
1080p
1
Recommended Operating System and Database
Supported OS include Windows 7 SP1 (64-bit Unified), Windows 8 SP1 (64-bit
Unified), Windows 10 (64-bit Unified), Windows Server 2008 R2 (64-bit Unified),
Windows Server 2012 (64-bit), Windows Server 2014 (64-bit)
2
Enterprise Drives (SATA 7,200 rpm)
3
Enterprise Drives (SAS 15,000 rpm)
2.5.3 victor Application Server Virtual Server Requirements (victor Only)

victor Only
victor Only
Enterprise Enterprise
Virtual victor Application Server Standalone
SAS MAS
Virtual VMware ESXi 5.5   
Server 4 Hyper-V Manager 6.1   
Win2008 R2 Server (Latest

64-bit 1 64-bit 1 64-bit 1
SP)
Operating Win2012 Server (Latest SP) 64-bit 1 64-bit 1 64-bit 1

System Win2012 R2 Server (Latest
64-bit 1 64-bit 1 64-bit 1
SP)
Win2016 Server (Latest SP) 64-bit 1 64-bit 1 64-bit 1
SQL Express 2008 R2 64-bit 1 64-bit 1 n/a

SQL Express 2012 64-bit 1 64-bit 1 n/a
64-bit 1
n/a

64-bit 1
n/a
Database 5 SQL Server 2008R2(Std/Ent) 64-bit 1
64-bit 1
64-bit 1
CPU Cores 4 4 4
CPU
CPU Reservation 7 GHz 7 GHz 7 GHz
RAM Memory Reservation 24 GB 24 GB 24 GB
(1) (1) (1)
NIC Dedicated Ethernet
1 GbE 1 GbE 1 GbE
Video Graphics   
HDD Primary Storage
1 TB 2 1 TB 3 1 TB 3
Reservation (9000 Runtime)
Secondary Storage 1 TB 2 1 TB 3 1 TB 3
3610-0642-01 A0 victor 57 of 17
Reservation (Data Backups)

USB 2.0 or 3.0   
Monitor Wide-Screen   
4
The pre-requisite for running VMS in a virtual environment is that the resource pools
have been preconfigured for VMware or Hyper-V.
5
For Large systems, it is recommended that the Microsoft SQL Server is running on a
separate physical server or VM environment.
2.5.4 victor Application Server Virtual Server Requirements (Unified)

victor + C•CURE 9000
Unified victor/C•CURE Standalone or Standalone or
Enterprise SAS Enterprise SAS Enterprise
Virtual victor Application Server MAS
(L,M,N) (P,Q,R,R+,S+,T)
Virtual VMware ESXi 5.5   

Server 4 Hyper-V Manager 6.1   
Win2008R2 Server (Latest 64-bit 64-bit 64-bit

SP)
Operating Win2012 Server (Latest SP) 64-bit 1 64-bit 1 64-bit 1

System Win2012R2 Server (Latest
64-bit 1 64-bit 1 64-bit 1
SP)
Win2016 Server (Latest SP) 64-bit 1 64-bit 1 64-bit 1
SQL Express 2008 R2 64-bit 1 64-bit 1 n/a

64-bit 1
n/a
64-bit 1
n/a
SQL Express 2016 64-bit 1 64-bit 1 n/a
SQL
Database 5 SQL Server 2008R2
64-bit 1 64-bit 1 64-bit 1
(Std/Ent)
CPU CPU Cores 4 4 4

CPU Reservation 7 GHz 7 GHz 7 GHz
RAM Memory Reservation 24 GB 24 GB 24 GB
(1) (1) (1)
NIC Dedicated Ethernet
1 GbE 1 GbE 1 GbE
Video Graphics   
HDD Primary Storage 1 TB 2
1 TB 3
1 TB 3
Reservation (9000
Runtime)
3610-0642-01 A0 victor 58 of 17
Secondary Storage
Reservation (Data 1 TB 2 1 TB 3 1 TB 3
Backups)
USB 2.0 or 3.0   
Monitor Wide-Screen   
4
The pre-requisite for running VMS in a virtual environment is that the resource pools
have been preconfigured for VMware or Hyper-V.
5
For Large systems, it is recommended that the Microsoft SQL Server is running on a
separate physical server or VM environment.
2.5.5 victor Express and victor Client Physical Workstation Requirements
(High Performance)
Standard Desktop
(Quad-Monitors)
(Dual-Monitors)
(Single Monitor)
(Dual-Monitors)
Basic Desktop
victor
Performance
Performance
Workstation
Workstation
Workstation
Unified Client
and
victor Express 6
Win7 (Pro/Ent) (Latest SP) 64-bit 1 64-bit 1 64-bit 1 64-bit 1 64-bit 1

Operating
Win8 (Pro/Ent) (Latest SP) 64-bit 64-bit 64-bit 64-bit 64-bit
System
Win10 (Pro/Ent) (Latest SP) 64-bit 64-bit 64-bit 64-bit 64-bit
Core Core Xeon Xeon (2) Xeon

CPU Intel Processor I3-4150 I5-3550 E5-1603 E5-1603 E5-2620
3.5 GHz 3.3 GHz 2.8 GHz 2.8 GHz 2.0 GHz
4 GB 4 GB 4 GB
RAM System Memory 4 GB 4 GB
(12 GB) 9 (12 GB) 9 (16 GB) 9
NIC Gigabit Ethernet     
Intel HD (1) (1) (2) (2)
4400 NVIDIA NVIDIA NVIDIA NVIDIA
Graphics Card Model
(Integrated) Quadro Quadro Quadro Quadro
Video 7 K620 K620 K620 K620
2 GB 2 GB (2) 2 GB (2) 2 GB
GFX n/a
GDDR3 GDDR3 GDDR3 GDDR3
Physical Quantity (1) HDD 2 (1) HDD 2 (1) HDD 2 (1) HDD 2 (1) HDD 2
HDD
Primary Storage 250 GB 2 500 GB 2 1 TB 2 1 TB 2 1 TB 2
Optical DVD+/-R Dual-Layer     
USB 2.0 or 3.0     
I/O Keyboard/Mouse     
(1) (2) (2) (4) (4)
Monitor 8 Max Resolution (Max QTY)
2560x1600 2560x1600 2560x1600 2560x1600 2560x1600
3610-0642-01 A0 victor 59 of 17
6
victor Express will automatically install the victor Unified Client, therefore must be
installed on a client-based system. 32-bit OS are not recommended and no longer
supported starting from V5.1 and higher.
7
Recommended graphics card shall be NVIDIA brand with onboard memory for best
performance. AMD Radeon/Firepro Adapters are fully supported with minimum
recommended AMD adapters (Radeon R9 270 or FirePro V4900). Integrated Intel HD
Adapters are supported for Single Monitor platforms with minimum recommended Intel
adapter (HD4400).
8
Recommended monitor resolution shall support resolution of camera models which will
be monitored on the client machine. Only 2 monitors per display adapter have been
validated with each monitor requiring 512MB of onboard memory (total 1TB for dual
monitors per display adapter).
9
Recommended for systems running Unified victor/C•CURE 9000.
 For sites with up to 200 active analog or IP camera connections, VMS shall support
installation and operation of both VMS client and server applications on any of the
specified workstations / operating system.
 For sites with greater than 200 analog and/or IP camera connections, VMS server
application shall be installed on a separate dedicated server.
2.5.6 victor Web Client Physical and Virtual System Requirements

Workstatio
Workstatio
Physical
Physical
victor Web Client
Virtual
Virtual
Server
Server
(Installed on Standalone host
n
n
that is not the victor Application Server)
Virtual VMware ESXi 5.5 n/a  n/a 

Server 4 Hyper-V Manager 6.1 n/a  n/a 
Win7 (Pro/Ent) A
(Latest SP) 64-bit 64-bit n/a n/a
Workstation
Operating Win8 (Pro/Ent) A (Latest SP) 64-bit 64-bit n/a n/a
System
Win10 (Pro/Ent) A (Latest SP) 64-bit 64-bit n/a n/a
Win2008 R2 Server A (Latest SP) n/a n/a 64-bit 64-bit
Server Win2012 Server A
(Latest SP) n/a n/a 64-bit 64-bit
Operating
System Win2012 R2 Server A
Win2016 Server A
Core 1 Core 1
CPU Intel Processor I3-4150 CPU I5-3550 CPU
3.5 GHz Core 3.3 GHz Core
4 GB 4 GB
RAM System Memory 4 GB 4 GB
Reservation Reservation
NIC Gigabit Ethernet    
Graphics Card Model    
Video
GFX 512 MB 512 MB 512 MB 512 MB
Physical Quantity (1) HDD (1) HDD (1) HDD (1) HDD
HDD
Primary Storage 250 GB 250 GB 250 GB 250 GB
3610-0642-01 A0 victor 60 of 17
Optical DVD+/-R Dual-Layer    

USB 2.0 or 3.0    
I/O Keyboard/Mouse    
Monitor Max Quantity Wide-Screen 1080p 1080p 1080p 1080p
A
victor Web Client supports two types of installation options. When installed on a host
that does not have victor Application Server installed on it, then IIS and ARR are not
required on the host. However, if victor Application Server exists on that host, then both
IIS (Internet Information Services) and ARR (Application Request Routing) are required
to successful setup of victor Web Services for victor Web Client support.
a. Two Dedicated Hosts: (victor Web Client and victor Application Server):
 Host #1: The victor Web Client installer will include all of the required pre-
requisites to setup the dedicated vWC host. This host will require a valid
license file, so use (a) the unique software serial number that was included with
the victor Web Client order and (b) the XML file generated from the License
Manager to register online to receive the license file for host #1.
 Host #2: The victor Application Server installer will include all of the
required pre-requisites to setup the dedicated vAS host. In addition, IIS
(Internet Information Services) and installation of licensed add-on victor Web
Services are all required. This host will require valid license file, so use (a) the
unique software serial number that was included with the victor Application
Server order with add-on victor Web Services and (b) the XML file generated
from the License Manager to register online to receive the license file for host
#2.
b. Single Integrated Host: (Combined victor Application Server and victor Web
Client):
 Single Integrated Host: The victor Application Server installer will include
all of the required pre-requisites, and then IIS (Internet Information Services),
ARR (Application Request Routing) and installation of licensed add-on victor
Web Services are all required. After vAS is properly configured, launching the
victor Web Client installer will include all of the required pre-requisites to
enable the vWC functionality. This single integrated host will require a valid
license file, so use (a) the unique software serial number that was included with
the victor Application Server order with add-on victor Web Services plus add-
on victor Web Client, and (b) the XML file generated from the License Manager
to register online to receive the license file for single integrated host. Please
note that for a combined host, Windows 7 is not supported.
2.5.7 Supported Video Devices

The VMS shall support the following video recorder hardware on a victor-only or Unified
victor / C•CURE 9000 system:
 Intellex Digital Video Recorder V3.2 to V5.02
 VideoEdge Network Video Recorder V5.1 and earlier
 VideoEdge Hybrid Appliance Recorder V5.1 and earlier
 VideoEdge Micro Recorder V5.1 and earlier
 Hybrid Digital Video Recorder
 TVR Video Recorder V2.22 to V2.60.04 (TVR-V2, TVR-LT)
3610-0642-01 A0 victor 61 of 17
 ExacqVision Video Recorder V5.0 to V8.0

 Holis Video Recorder
 Dedicated Micros Video Recorder*
 When unified, the video license option shall be enabled on the victor license file.
Note1: * Add-on metered option for VMS server license is required. Refer to
integration release notes for latest supported models and versions.
Note2: victor Express is limited to metered VideoEdge and metered Intellex
recorder support only, and does not support optional Video integrations.
2.5.8 Supported Intrusion Devices

The VMS shall be capable of supporting the following intrusion hardware on a victor-only
or Unified victor / C•CURE 9000 system:
 DSC PowerSeries*
 DSC Neo ITV2*
 SurGard System II*
 Bosch Receiver*
 DMP*
 Galaxy*
 When unified, the intrusion license option shall be enabled on either the victor or
C•CURE 9000 license file.
Note1: * Add-on option for VMS server license is required. Refer to integration
release notes for latest supported models and versions.
Note2: victor Express does not support optional Intrusion integrations.
2.5.9 Supported Access Control Devices

The VMS shall be capable of supporting the following access control hardware on a
victor-only system:
 CEM AC2000 * V6.3+
 CEM AC2000 Airport * V6.6+
 CEM AC2000 Lite * V6.4+
 eDCM Controllers* All Versions Supported by CEM
 EIOC Controllers* All Versions Supported by CEM
 Readers * All Versions Supported by CEM
 Kantech Entrapass* V6.01 Corporate/Gold Edition
 KT 1/100/400 Controllers* All Versions Supported by Entrapass
 DSC PowerSeries* PC1864 (Intrusion Panel for KT-400)
 Readers* All Versions Supported by Entrapass
Note2: victor Express does not support optional Access Control integrations.
3610-0642-01 A0 victor 62 of 17
2.5.10 Supported Access Control Devices (Unified)

The VMS shall be capable of supporting the following access control hardware on a
Unified victor / C•CURE 9000 system:
 Software House C•CURE 9000* V2.61 (SA/SAS/MAS) & victor V5.0/5.1
V2.60 (SA/SAS/MAS) & victor V4.9.1
V2.51 (SA/SAS/MAS) & victor V4.8.1/4.9
V2.50 (SA/SAS/MAS) & victor V4.8SP1
V2.4 (SA/SAS/MAS) & victor V4.7.1/4.8
V2.4 (SA/SAS/MAS) & victor V4.6
V2.3 (SA/SAS/MAS) & victor V4.5/4.5.1
V2.2 (Standalone) & victor V4.4
V2.2 (Standalone) & victor V4.3
V2.1R2P1 (Standalone) & victor V4.3
V2.1R2P1 (Standalone) & victor V4.2.1
 iSTAR * All Versions Supported by C•CURE
 Readers* All Versions Supported by C•CURE
 Unification requires that the unified installer license option shall be enabled on both
the victor and C•CURE 9000 license files.
Note2: victor Express does not support optional Unification.
2.5.11 Supported Fire Panels Devices

The VMS shall be capable of supporting the following fire panel hardware on a victor-only
or Unified victor / C•CURE 9000 system:
 Simplex Grinnell* 4100U / ES
 MZX Technology* MZX / Zettler
MZX Consys 20.2+ & MX Speak 5.2
 When unified, the fire panel license option shall be enabled on either the victor or
Note2: victor Express does not support optional Fire integrations.
2.5.12 Supported Location-Based Security Devices

The VMS shall be capable of supporting events from the following location-based security
hardware on a victor-only or Unified victor / C•CURE 9000 system:
 Elpas*
 When unified, the Elpas license option shall be enabled on either the victor or
3610-0642-01 A0 victor 63 of 17
Note2: victor Express does not support optional Real-Time Location integrations.
2.5.13 Supported Point of Sale Systems and Text Streams

The VMS shall be capable of supporting the Unified POS format on a victor-only or
Unified victor / C•CURE 9000 system when licensed. The rich investigator tools shall
include a new customer present analytic to match the data to relevant forensic video
captured during the same time period.
 The VMS shall support the integration with Raw POS transaction data from a
Unified POS system.
 The VMS shall support ability to schedule import of POS Transaction and
Exception Reports for automated POS import. POS Transactions can be imported
directly and POS Exceptions have to have a matching template already created
using the manual import tool before the process can begin.
 The VMS shall support the utilization one or more cameras from VideoEdge
recorders which are associated with terminals.
 The VMS shall support a victor text stream search that provides a means of
searching text from configured VideoEdge recorders. The two types of supported
text streams are:
 Date and Time Used to return all text values within a define time period
 Advanced Used to search for specific text values within defined
parameters and filters set on VideoEdge and victor.
 The VMS shall support Text Stream rules that allow the ability to fine tune a Text
Stream search. User defined rules may be used to filter search results and ability to
add multiple rules or use no rules for searches.
 The VMS shall support selection of rules that are predefined on the recorders.
These rules can be applied on victor’s Search and Retrieve wizard.
 The VMS shall support defining and applying Text Stream rules in victor client as
part of the Search and Retrieve wizard.
 The VMS client shall support viewing near live text streams preview with
associated video from VideoEdge recorder. The video shall be able to be aligned
with transactions to allow investigation through victor’s investigation tools.
 The VMS shall support ability to use Text Stream rules to configure alarms. This
can be extremely useful when setting up your victor system to flag an alarm when
any sales transactions exceeds a particular value (e.g. over $100) or when any
sales transaction is voided.
 The VMS shall support Text Streams from VideoEdge NVRs, VideoEdge Hybrid,
and Intellex DVR recorders.
 The VMS shall support Rule Groups to define a set of rules that must be met in
order to trigger an alarm. These rules shall be based on Boolean logic (OR or
AND).
Note1: * An add-on option for VMS server is required. Refer to the release notes
for latest supported models and versions.
Note2: victor Express supports optional Point of Sale integrations.
3610-0642-01 A0 victor 64 of 17
2.5.14 Supported victor Web Service

The VMS shall be capable of supporting the following web service when connecting to
the system running the Microsoft Internet Information Services (IIS) Web Server on a
victor-only or Unified victor / C•CURE 9000 system:
 victor Web Service*
 The VMS shall support ability to connect with victor using an approved integrated
web service.
 Each login operator account via web browser shall be counted as a metered value
on the victor license file.
 When unified, the victor Web Service license option shall be enabled on either the
victor or C•CURE 9000 license file.
Note2: victor Express does not support optional victor Web Service integrations.
Note3: victor Web Client will require the victor Application Server host to have
victor Web Service properly installed and licensed.
2.5.15 Supported Building Management Systems

The VMS shall be capable of supporting the following building management system on a
victor-only or Unified victor / C•CURE 9000 system:
 BACnet*
 When unified, the building management system license option shall be enabled on
either the victor or C•CURE 9000 license file.
Note2: victor Express does not support optional Building Management Systems
integrations.
2.5.16 Supported Elevator Devices

The VMS shall be capable of supporting the following elevators on a Unified victor /
C•CURE 9000 system:
 KONE*
 Otis*
 ThyssenKrupp*
 For the unified system, the elevator license option shall be enabled on either the
victor or C•CURE 9000 license file.
Note1: * An add-on option for VMS server is required and must be on a Unified
victor / C•CURE 9000 system. Refer to the release notes for latest
supported models and versions.
Note2: victor Express does not support optional Elevator integrations.
2.5.17 Supported Intercom Devices

The VMS shall be capable of supporting the following intercoms on a victor-only or
3610-0642-01 A0 victor 65 of 17
 Commend*
 TOA (AIPhone)*
 When unified, the intercom license option shall be enabled on either the victor or
Note2: victor Express does not support optional Intercom integrations.
2.5.18 Supported LDAP

The VMS shall be capable of supporting LDAP protocol on a victor-only or Unified victor /
C•CURE 9000 system:
 LDAP*
 When unified, both LDAP and Import Watcher license options shall be enabled on
either the victor or C•CURE 9000 license file.
Note2: victor Express does not support optional LDAP protocol.
2.5.19 Supported Enterprise Architecture

The VMS shall be capable of supporting an Enterprise architecture on a victor-only or
 Enterprise*
 The VMS shall offer an Enterprise solution that supports customers who require a
solution that offers ability to seamlessly scale up and scale out.
 The VMS shall require the addition of a new Master Application Server (victor MAS)
to the existing site. Each MAS shall be configured to support up to 10 or 20 or 40
Satellite Application Servers (victor SAS) across the enterprise. The MAS server
shall meet or exceed the specified system requirements.
 The VMS shall offer the ability to promote any existing standalone VMS servers to
Satellite Application Servers (SAS) which meet the system requirements for an
enterprise server.
 The Enterprise VMS shall support a single login to manage the entire Enterprise.
 The Enterprise VMS shall provide a centralized global administration for the entire
Enterprise.
 The Enterprise VMS shall provide a centralized global monitoring for the entire
Enterprise.
 The Enterprise VMS shall provide a centralized global reporting for the entire
Enterprise.
 The Enterprise VMS shall provide global objects for the entire Enterprise. For
victor-only, the objects shall include recorders, cameras, call-ups and video
layouts.
 When unified, the Enterprise license option shall be enabled on both the victor and
C•CURE 9000 license files.
3610-0642-01 A0 victor 66 of 17
for latest details and system requirements.
Note2: victor Express does not support promotion to a Satellite Application Server.
3610-0642-01 A0 victor 67 of 17
PART 3 EXECUTION
3.1 EXAMINATION
 Submission of a proposal confirms that the contract documents and site conditions
are accepted without qualifications unless exceptions are specifically noted.
 The site shall be visited on a regular basis to appraise ongoing progress of other
trades and contractors, make allowances for all ongoing work, and coordinate the
requirements of this contract in a timely manner.
 The systems must be inspected before installation, and shall be free of any cosmetic
defects or damage.
3.2 PREPARATION
 Prior to installation, the VMS system and network shall be configured and tested to
meet the specified requirements in accordance with the manufacturer’s instructions.
3.3 INSTALLATION
 The VMS must be installed, programmed, and tested in accordance with the
manufacturer’s instructions.
 In order to ensure a complete, functional VMS, for bidding purposes, where
information is not available from the Owner upon request, the worst-case
condition shall be assumed.
 Interfaces shall be coordinated with the Owner’s representative, where
appropriate.
 All necessary back boxes, racks, connectors, supports, conduit, cable, and
wire must be furnished and installed to provide a complete and reliable VMS
installation. Exact location of all boxes, conduit, and wiring runs shall be
presented to the Owner for approval in advance of any installation.
 All conduit, cable, and wire shall be installed parallel and square with building
lines, including raised floor areas. Conduit fill shall not exceed forty percent
(40%). All wires shall be gathered and tied up to create an orderly installation.
 Starting from V5.1, all victor products can only be installed on 64-bit Windows
Operating Systems.
 The VMS vendor must also be able to offer Professional Services that would deploy
trained personnel to assist with the installation and programming of the VMS.
3.4 TESTING AND CERTIFICATION

 The Contractor shall demonstrate the functionality of the VMS upon completion of
installation, documenting the result of all tests and providing these results to the
Owner. The VMS shall be tested in accordance with the following:
 The software shall be entered into VMS computer systems and debugged. The
Contractor shall be responsible for documenting and entering the initial
database into the system. The Contractor shall provide the necessary blank
forms with instructions to fill in all the required data information that will make
up the database. The database shall then be reviewed by the Contractor and
entered into the system. Prior to full operation, a complete demonstration of the
3610-0642-01 A0 victor 68 of 17
computer real-time functions shall be performed. A printed validation log shall

be provided as proof of operation for each software application package. In
addition, a point utilization report shall be furnished listing each point, the
associated programs utilizing that point as an input or output and the programs
which that point initiates.
 Upon satisfactory on line operation of the system software, the entire
installation including all subsystems shall be inspected. The Contractor shall
perform all tests, furnish all test equipment and consumable supplies
necessary and perform any work as required to establish performance levels
for the system in accordance with the specifications. Each device shall be
tested as a working component of the completed system. All system controls
shall be inspected for proper operation and response.
 Tests shall demonstrate the response time and display format of each different
type of input sensor and output control device. Response time shall be
measured with the system functioning at full capacity. Computer operation shall
be tested with the complete data file.
 The Contractor shall maintain a complete log of all inspections and tests. Upon
final completion of system tests, a copy of the log records shall be submitted as
part of the as-built documentation along with a letter of certification to indicate
that the tests have been performed, and all devices are operational
 The system test shall be witnessed by the Authority Having Jurisdiction. Any
deficiencies noted during the testing must be corrected.
 A letter of certification shall be provided to indicate that the tests have been
performed, and all devices are operational.
 The Owner’s representative shall accept the system.
3.5 TRAINING
 The Contractor shall provide a competent trainer who has extensive experience with
the installed systems and in delivering training to provide the instruction. As an
alternative, the Contractor may propose the use of factory training personnel and
coordinate the number of personnel to be trained.
 The VMS vendor must also offer training at multiple training facilities and option for
onsite training.
3.6 MAINTENANCE
 Preventative Maintenance Agreement during Warranty: As a separate price item, the
Contractor shall provide preventative maintenance during the warranty period.
Maintenance shall include, but no be limited to:
 Labor and materials, at no additional cost, to troubleshoot the VMS software.
 Labor and materials, at no additional cost, to provide test and adjustments to
the VMS software.
 Regular inspections.
 Preventative Maintenance Agreement: As a separate price item, the Contractor shall
provide a complete Maintenance Agreement for a period of 12 months after the
conclusion of the warranty period. The Maintenance Agreement shall include, but not
be limited to:
 Labor and materials, at no additional cost, to troubleshoot the VMS software.
3610-0642-01 A0 victor 69 of 17
 Labor and materials, at no additional cost, to provide test and adjustments to

the VMS software.
 Regular inspections.
 The Contractor shall offer an American Dynamics Software Support Agreement
(SSA) in order for American Dynamics Technical Support Specialists to reactively
troubleshoot any system problems. The SSA also entitles the customer to receive
software updates and allow for online registrations for licenses.
END OF SPECIFICATIONS
3610-0642-01 A0 victor 70 of 17

Victor-5-1-Ae-Specification Ae Ra0 LT en

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

Victor-5-1-Ae-Specification Ae Ra0 LT en

Uploaded by

Copyright:

Available Formats

victor Web Client

American Dynamics makes no representations or warranties with respect to the

1.3 GENERAL SYSTEM DESCRIPTION.....................................................................................2

1.5 QUALITY ASSURANCE........................................................................................................ 4

2.2 MANUFACTURED UNITS / MODEL NUMBERS................................................................15

2.4 VMS FUNCTIONALITY........................................................................................................ 23

2.4.10.5 Facial Recognition Analytic Search 38

2.5 SYSTEM REQUIREMENTS.................................................................................................55

3.4 TESTING AND CERTIFICATION........................................................................................67

 American Dynamics Intellex Digital Video Management System

 HDVR Hybrid Digital Video Recorder

1.3 GENERAL SYSTEM DESCRIPTION

5. External Storage (for extended retention of recorded video)

1.4.2 Shop Drawings

1.4.3 As-Built Drawings

1.5 QUALITY ASSURANCE

1.5.2 Contractor / Integrator Qualifications

(victor Application Server with/without Unified C•CURE 9000, SAS-enabled,

 Optional add-on for victor Unified Clients – Health Monitoring support

(Metered for Centralized victor Application Server with/without Unified C•CURE

 Exacq Vision Recorders*

seamless and simultaneously enable access to multiple recorders and their

French Standard, German, Italian, Japanese, Polish, Portuguese Brazilian,

2.2 MANUFACTURED UNITS / MODEL NUMBERS

ADVASC01 victor Professional software base with 1 concurrent client connections

victor Enterprise MAS software base with 1 concurrent client connection

victor Enterprise MAS software base with 1 concurrent client connection

victor Enterprise MAS software base with 1 concurrent client connection

victor Web Client additional concurrent licenses:

victor Professional add-on licenses:

victor Client support for Health Monitoring (Health)

victor Client support for Recording Surveillance (Record)

victor integration with Point of Sale (POS)

ADVC- victor promotion from Professional to Enterprise SAS (SAS)

victor Enterprise SAS add-on licenses:

victor Client support for Health Monitoring (Health)

ADVC- victor Client support for Recording Surveillance (Record)

victor integration with Point of Sale (POS)

victor Enterprise MAS add-on licenses:

victor Command Center additional agent connections (1-pack) (Agent)

victor Client support for Health Monitoring (Health)

ADVC- victor Client support for Recording Surveillance (Record)

victor integration with LDAP (Protocol)

victor Professional and Enterprise SAS Centralized add-on licenses:

ADVC- victor promotion to Centralized Licensing for VideoEdge (Centralized)

(Purchase metered option for Centralized victor Enterprise SAS)

victor Unification add-on licenses:

victor Unification with C•CURE 9000 (Unified with Access Control)

victor Unification with C•CURE 9000 (Unified with Access Control)

victor Professional and Enterprise SAS integration licenses:

victor integration with BACnet (Building Management System)

victor integration with KONE (Elevator)

victor integration with FireClass Fire Panel (Fire)

victor integration with Commend (Intercom)

victor integration with TOA (AIPhone) (Intercom)

victor integration with Bosch Alarm Receiver (Intrusion)

victor integration with Elpas (Real-Time Locator)

ADVC- victor integration with Dedicated Micros Recorders (Video)

victor integration with victor Web Service (Web Service)

victor SSA Model Numbers

ADVC-VECAM-S SSA Centralized per VE IP Camera license (VE Cameras)

ADVC-POS-S SSA for victor integration with Point of Sale (POS)

SSA for victor integration with CEM (N/C) (Access Control)