Genetec - Omnicast 4.8 Ordering Guide PDF

IP Video Surveillance
Omnicast 4.8
Ordering Guide
Version 1.1 - 9/26/2011
Information contained herein is confidential and proprietary information of
Genetec Inc.
Innovative Solutions
Table of Contents
1
Introduction
1.1
Overview
1.2
Product codes
1.3
Package selection
Omnicast Standard
2.1
Base Package
2.2
Connection licenses
10
2.3
Camera connection
10
2.4
Federation option
10
2.5
Upgrade to Pro or Enterprise
10
Omnicast Pro
11
3.1
Base Package
11
3.2
Connection licenses
12
3.2.1
Camera connection
12
3.2.2
DVR Input
12
3.2.3
Digital inputs and digital outputs
12
3.2.4
Client connection
12
3.2.5
Keyboard connection
13
3.2.6
SDK connection
13
3.2.7
Media Gateway
13
3.2.8
Camera connection for advanced mapping (Plan Manager)
13
3.3
3.4
Server licenses
15
3.3.1
Omnicast Gateway
15
3.3.2
Virtual Matrix
15
3.3.3
Archiver (Omnicast 4.5 and under)
15
3.3.4
Support for virtualization
15
System Features
16
3.4.1
Windows Active Directory
16
3.4.2
Offline archiving
16
3.4.3
Local archiving
16
3.4.4
Camera blocking
16
genetec.com | Omnicast 4.8 | Ordering Guide
3.5
Third-party integrations
17
3.5.1
Access Control
17
a) Software House
17
3.6
Federation option
17
3.7
Upgrade to Enterprise
17
Omnicast Enterprise
18
4.1
Base Package
18
4.2
Connection licenses
19
4.2.1
Camera connection
19
4.2.2
DVR Input
19
4.2.3
19
4.2.4
Client connection
19
4.2.5
Keyboard connection
20
4.2.6
SDK connection
20
4.2.7
Hardware Matrix
20
4.2.8
20
4.2.9
Media Gateway
21
4.2.10
Direct Show Filter connection
21
4.2.11
SNMP Traps plugin
21
4.3
4.4
4.5
System Features
22
4.3.1
22
4.3.2
Camera blocking
22
4.3.3
Remote Live Viewer
22
Failover and redundancy
23
4.4.1
Failover Directory
23
4.4.2
Failover camera connection
23
4.4.3
Windows Clustering Support
23
4.4.4
Virtual Matrix Failover
24
4.4.5
24
Server licenses
25
4.5.1
Omnicast Gateway
25
4.5.2
Virtual Matrix
25
4.5.3
Metadata Engine
25
4.5.4
25
4.6
Bosch VRM
26
4.6.1
Camera connection for Bosch VRM
26
4.6.2
Archiver for Bosch VRM
26
4.7
Federation Options
27
4.8
Auxiliary Archiver Options
28
4.9
29
4.9.1
Access Control
29
a) ACS PRCS (Parking Revenue Control System)
29
b) Access control interface
29
c) GE Picture Perfect
29
d) Hirsch Velocity
30
e) Lenel
30
f) RBH
30
g) Software House
31
h) Southwest Microwave MicroPoint
31
i) Verex
32
Video Analytics
33
a) iOmniscient plugin
33
b) Object Video plugin
33
c) OV Ready camera connection
33
Point of Sales (POS)
34
a) Generic POS Plugin
34
b) Micros POS Plugin
34
Video Walls
35
4.9.2
4.9.3
4.9.4
5
Common Options
36
5.1
Base Package Options
36
5.1.1
Maps and procedures
36
5.1.2
Audio support
36
5.1.3
Web Pack
36
5.1.4
Camera sequence
36
5.1.5
Macros
36
5.1.6
Alarm management
36
5.1.7
Local archiving
37
5.1.8
Offline archiving
37
5.1.9
Database reporting
37
5.1.10
Edge recording and trickling support
37
5.1.11
Time zone support
37
5.1.12
Languages
37
Omnicast Demo Licenses
39
Omnicast SDK
40
SMAs
41
Appendix A Server type
42
10 Appendix B Workstation type
43
11 Appendix C Feature comparison
44
Introduction
1.1
Overview
The following Ordering Guide contains pricing information about version 4.x; please refer to the cover page to
ensure you have the latest Ordering Guide at hand.
The Omnicast pricing structure has changed considerably with the release of Omnicast 4.6, but this new pricing
structure applies to all Omnicast 4.x versions. Some part numbers are only available on specific versions as noted in
the Ordering Guide and price list.
This Ordering Guide explains the different packages together with the different features of each package.
Omnicast 4.x will be available under three different Packages:
Omnicast Standard
Omnicast Pro
Omnicast Enterprise
Please refer to Appendix C for a feature comparison between the different packages.
Together with the basic packages you will find information and various other pricing such as:
SDK
Demo Licenses
1.2
Product codes
Product codes include 3 blocks, defined as follows:
XX - X - XXXXXX
(3)
(2)
(1)
(1) Product identification - Alphabetical
a)
Om : Omnicast
(2) Package:
a)
S: Standard
b) P: Pro
c)
E: Enterprise
(3) Part identification:

a)
Alphanumerical: when part number starts with a number, item can be ordered in quantities; otherwise it is a
system wide option.
Version:
The version of the product must be specified on each order, by adding the no charge part number Om-4x,
where x refers to the minor version number (ex. Om-4.7).
1.3
Package selection
The base package must be selected based on the:
Overall camera/analog monitor count
Number of Archivers
Number of client connections
Failover
Federation
Third-party integration (plugins, interfaces, etc.)
Unlimited
ENTERPRISE
PRO
Single server
Alarm management
Audio
I/O on video units
Motion detection
Virtual Matrix
Maps and Procedure
Reporting
Edge recording
Video Trickling
Number of cameras
50
Unlimited scalability
Unlimited client connections
Federation
Failover
Plugin integration
Remote Live Viewer
Video Walls
SNMP Traps
Bosch VRM
Hardware Matrix support
10
5
STANDARD
Multiple servers
Offline archiving
DVR integration
Local Archiving
Camera blocking
Macros
Active Directory
Edge recording
Virtualization
SDK integration
I/O modules
Advanced Mapping
Direct Show Filter
Number of clients
Number of archivers 1
20
Unlimited
The following graph shows the differences between Omnicast Standard, Pro and Enterprise.
100
Unlimited
Omnicast Standard
2.1
Base Package
Overview
Product Code [Om-S-Base]
The Standard package is the entry level package targeted for system with a low camera count which requires a cost
effective solution. The Standard package includes the typical functionalities of a video management system all
included in a single base package. The Standard package is intended to work on a single server installation.
The base Package is mandatory for every Omnicast system.
The Omnicast Standard system can be federated by an Enterprise system.
The Archiver included in the base package cannot be installed on a separate server (single server operation only in
the Standard package).
The Omnicast Standard Base Package is limited to 50 cameras, 1 archiver and 5 clients.
One Omnicast Standard 4.x Base Package is required per Omnicast system
Archiving support (Max. 50 cameras)
1 Gateway
5 client/user connections
Maps/Procedures
Audio Support
Web Pack
1 Virtual Matrix
Camera Sequences
1 Keyboard connection
Alarm Management Module
Database reporting
Time Zone Support
All languages supported
10
2.2
Connection licenses
Overview
A connection license is required and available the following item:
Camera/analog monitor
2.3
Camera connection
Overview
Product Code [Om-S-1C]
No camera connection is included in the base package. A camera connection license is required for each video
channel connected to the system (e.g. IP camera, video encoder or decoder).
For multi-channel video units, a camera connection license is required for each video channel unless the video unit
has the functionality of disabling the video channel at the source.
2.4
Federation option
All Standard systems can be federated into an Omnicast 4.x enterprise system. No cost is associated to this option
for the Standard system.
2.5
Upgrade to Pro or Enterprise

Upgrading from Omnicast Standard to Pro or Enterprise is available. The Standard system will be credited at 100 %.
11
Omnicast Pro
3.1
Base Package
Overview
Product Code [Om-P-Base]
The Pro package is the ideal choice for small system which requires a cost effective solution. The Pro package
includes the standard functionalities of a video management system. More advanced functionalities are offered in
option.
The Omnicast Pro system can be federated by an Enterprise system.
The Archiver included in the base package cannot be installed on a separate server. Additional Archiver licenses are
available for this purpose.
The Omnicast Base Package is limited to 100 cameras, 20 archivers and 10 clients (including the one in the base
package).
One Omnicast Pro 4.x Base Package is required per Omnicast system
Archiving support (Max. 100 cameras per Archiver)
1 Gateway
Maps/procedures
Audio support
Web Pack
1 Virtual Matrix
Camera Sequences
Macros
Database Reporting
Time Zone support
12
3.2
Connection licenses
Overview
A connection license is available and required for each of the following items:
DVR input ( per DVR input NOT per DVR)
Digital inputs and digital outputs (coming from I/O modules)
Client application
Keyboard
SDK
Media Gateway
3.2.1
Camera connection
Overview
Product Code [Om-P-1C]
A camera connection license is required for each video channel connected to the system (e.g. IP camera, video
encoder or decoder).
3.2.2
DVR Input
Overview
Product Code [Om-P-1DV]
The GE DVMRe is the only equipment for which the DVR input can be ordered. The DVR input license needs to
be ordered for each video input on the DVR (NOT per DVR unit).
The DVR input license allows retrieval of the recorded video on the DVR, but doesnt allow recording of the DVR
camera on the Archiver.
3.2.3

Overview
Product Code [Om-P-8IN] [Om-P-8OUT]
A digital input connection or digital output connection is required for each physical input or output contact on an I/O
module. This license is only applicable to I/O module and not to digital input and output on IP video units (IP
cameras, encoders or decoders).
Example of currently supported I/O modules are: Axis P8221 and HWg-Juno 101/404.
3.2.4
Client connection
Overview
Product Code [Om-P-1U]
13
A client connection is needed for each client station that connects to Omnicast regardless of the number of client
application running on the station. The client connection license is for concurrent connections. The Config Tool
client application doesnt require a client connection license.
3.2.5
Keyboard connection
Overview
Product Code [Om-P-1KEY]
A keyboard connection is required for each analog CCTV keyboard connected to the system whether the CCTV
keyboard is connected directly to the client station (Live Viewer) or through an IP encoder/decoder.
USB joysticks dont require a CCTV keyboard connection license.
A Virtual Matrix is needed (included in the base package) to host the keyboard connection.
3.2.6
SDK connection
Overview
Product Code [Om-P-1S]
A SDK connection is required for an application that has been created using the Omnicast SDK. One (1) SDK
connection is needed per concurrent application connection.
Starting from 4.8, the SDK connection is used to license DSF connection. A Direct Show Filter connection takes an
Omnicast managed camera and produces an uncompressed video stream as output. This connection is necessary for
third party application integration such video analytic software One (1) SDK connection is required per machine
and per application (per user) using the DSF which allows unlimited DSF connections.
Ex.: One SDK application running on five (5) stations will require five (5) SDK connections.
3.2.7
Media Gateway
Overview
Product Code [Om-P-1GTW]
A Media Gateway Streaming license is required for each camera that are being streamed be the Media Gateway
service. The Media Gateway package is included with the Media Gateway license. The Media Gateway service
allows streaming Omnicast managed cameras over the web.
Third party software is required. Additional cost is involved.
3.2.8

Feature overview
Product Code [Om-P-1CAMAP]
This feature allows the users to create and use advanced mapping using Plan Manager in the Live Viewer. Plan
Manager allows maps creation and edition with dynamic content, multi-level and zooming capabilities.
Plan Manager support GIS services like Microsoft Bing. GIS license fees are NOT included.
A advanced mapping camera connection is required for each camera that is displayed on the map. The number of
camera connections for advanced mapping does not have to match the number of camera connection in the system.
It can be equal or lower.
14
This feature is compatible with Omnicast 4.6 and up and requires the installation of a separate package than the
Omnicast installation.
Important: This item requires ordering a minimum one year SMA.
15
3.3
Server licenses
3.3.1
Omnicast Gateway
Feature overview
Product Code [Om-P-1OGW]
Omnicast Gateways can be added to a Pro system for traffic optimization purposes.
Performance
On a high end server, one (1) Gateway can handle a maximum of 150 simultaneous client connections or 300 Mbps
of video throughput (150 Mbps IN / 150 Mbps OUT).
3.3.2
Virtual Matrix
Feature overview
Product Code [Om-P-1VM]
Omnicast Virtual Matrix can be added to a pro system as required. The Virtual Matrix manages camera sequences,
CCTV keyboards, hardware matrices, access control interfaces, macros and VM plugins.
The main reason why an additional virtual matrix would be needed is to manage multiple camera sequences.
Performance
On a high end server, one (1) virtual matrix can handle a maximum 300 Mbps of video throughput (150 Mbps IN /
150 Mbps OUT).
3.3.3

Overview
Product Code [Om-P-1ARC]
This part number is only require when adding Archiver servers to an existing Omnicast 4.5 (or earlier versions)
installation. There is no cost for this part number, but a license file must be issued by Genetec in order to activate
this new Archiver server.
3.3.4

Feature overview
Product Code [Om-P-VIRT]
Virtualization support license is intended for Omnicast systems running in virtual environments. This license is a
system-wide option and covers for all Omnicast servers in the system that could be deployed in a virtual
environment.
The virtual environment supported by Omnicast is VMware.
Note that running in a virtual environment may have performance implications which can invalidate certain design
guidelines recommended by Genetec.
16
3.4
System Features
This section covers the system wide features of the Pro package.
3.4.1

Feature overview
Product Code [Om-P-ACD]
This feature allows system administrators to integrate to Windows Active directory.
3.4.2
Offline archiving
Feature overview
Product Code [Om-P-OffAR]
This feature allows system operators to perform offline backup and then restore of video files associated to system
cameras.
3.4.3
Local archiving
Feature overview
Product Code [Om-P-LA]
Local archiving allows users to perform recording on the different client workstations.
3.4.4
Camera blocking
Feature overview
Product Code [Om-P-CB]
This feature allows system administrators to block the transmission of the video feed of specific cameras for
investigation purposes.
17
3.5
3.5.1
Access Control
a) Software House
Feature overview
Product Code [Om-P-1S]
The Software House integration allows to view live and playback video and handle Omnicast events in C-Cure
9000. The metadata engine plugin is not require for this integration. Only SDK connections are required.
Performance
For video and events in C-Cure 9000, one (1) SDK connection license is require per per C-Cure 9000 server
andone (1) Omnicast SDK connection license must be ordered per C-Cure 9000 client station.
Third Party Software requirement
Third party software is required. The C-Cure 9000 components must be installed on a separate server, additional
cost is involved.
3.6
Federation option
All Pro systems can be federated into an Omnicast 4.x enterprise system. No cost is associated to this option for the
Pro system.
3.7
Upgrade to Enterprise
Upgrading from Omnicast Pro to Enterprise is available. The Pro system will be credited at 100 %.
18
Omnicast Enterprise
4.1
Base Package
Overview
Product Code [Om-E-Base]
Enterprise package is the ideal choice if you plan on benefiting from the full power of Omnicast, as the majority of
the optional features in Pro are included in the base package, as well as the ability to scale thousands of cameras and
the optional failover and intelligent video packages.
The Omnicast Enterprise Package is also required for the head end of a Federation system. The Omnicast Enterprise
Package can federate Omnicast Enterprise systems and Omnicast Pro systems.
The Archiver included in the base package cannot be installed on a separate server. Additional Archiver licenses are
available for this purpose.
Omnicast Enterprise 4.x base package includes the following features:
Archiving support (Max. 300 cameras per Archiver / 100 on Directory Machine)
1 Gateway
Maps/Procedures
Audio Support
Web pack
1 Virtual Matrix
Camera Sequences
Macros
Local archiving
Offline archiving
Database Reporting
Time Zone Support
19
4.2
Connection licenses
A connection license is required for each of the following items:
DVR input (per DVR input and NOT per DVR)
Digital inputs and digital outputs (coming from I/O modules)
Client application connection (per connection or site license)
Keyboard connections
SDK connection
Hardware matrix
Media gateway
Direct show filter
SNMP Traps
4.2.1
Camera connection
Overview
Product Code [Om-E-1C]
A camera connection license is required for each video channel connected to the system (e.g. IP camera, video
encoder or video decoder).
4.2.2
DVR Input
Overview
Product Code [Om-E-1DV]
The GE DVMRe is the only equipment for which the DVR input can be ordered. The DVR input license needs to
be ordered for each video input on the DVR (NOT per DVR unit).
The DVR input license allows retrieval of the recorded video on the DVR, but doesnt allow recording of the DVR
camera on the Archiver.
4.2.3

Overview
Product Code [Om-P-8IN] [Om-P-8OUT]
A digital input connection or digital output connection is required for each physical input or output contact on an I/O
module. This license is only applicable to I/O module and not to digital input and output on IP video units (IP
cameras, encoders or decoders).
Example of currently supported I/O modules are: Axis P8221 and HWg-Juno 101/404.
4.2.4
Client connection
20
Overview
Product Code [Om-E-1U] [Om-E-1STU]
A client connection is needed for each client station that connects to Omnicast regardless of the number of client
application running on the station. The client connection license is for concurrent connections. The Config Tool
client application doesnt require a client connection license.
User site license
Site license for client connection is available. The site license allows unlimited concurrent client connection to the
system [Om-E-1STU].
4.2.5
Keyboard connection
Overview
Product Code [Om-E-1KEY]
A keyboard connection is required for each analog CCTV keyboard connected to the system whether the CCTV
keyboard is connected directly to the client station (Live Viewer) or through an IP encoder/decoder.
USB joysticks dont require a CCTV keyboard connection license.
A Virtual Matrix is needed (included in the base package) to host the keyboard connection.
4.2.6
SDK connection
Overview
Product Code [Om-E-1S]
A SDK connection is required for an application that has been created using the Omnicast SDK. One (1) SDK
connection is needed per concurrent application connection.
Starting from 4.8, the SDK connection is used to license DSF connection. A Direct Show Filter connection takes an
Omnicast managed camera and produces an uncompressed video stream as output. This connection is necessary for
third party application integration such video analytic software One (1) SDK connection is required per machine
and per application (per user) using the DSF which allows unlimited DSF connections.
Ex.: One SDK application running on five (5) stations will require five (5) SDK connections.
4.2.7
Hardware Matrix
Overview
Product Code [Om-E-HMI]
A hardware matrix connection is required for each physical hardware matrix connected to the system.
A Virtual Matrix is needed (included in the base package) to host the hardware matrix connection.
4.2.8

Feature overview
Product Code [Om-E-1CAMAP]
This feature allows the users to create and use advanced mapping using Plan Manager in the Live Viewer. Plan
Manager allows maps creation and edition with dynamic content, multi-level and zooming capabilities.
21
Plan Manager support GIS services like Microsoft Bing. GIS license fees are NOT included.
A advanced mapping camera connection is required for each camera that is displayed on the map. The number of
camera connections for advanced mapping does not have to match the number of camera connection in the system.
It can be equal or lower.
This feature is compatible with Omnicast 4.6 and up and requires the installation of a separate package than the
Omnicast installation.
4.2.9
Media Gateway
Overview
Product Code [Om-E-1GTW]
A Media Gateway Streaming license is required for each camera that are being streamed be the Media Gateway
service. The Media Gateway package is included with the Media Gateway license. The Media Gateway service
allows streaming Omnicast managed cameras over the web.
Third party software is required. Additional cost is involved.
4.2.10 Direct Show Filter connection

Overview
OBSOLETE - Product Code [Om-E-1DSF]
See SDK Connection for more detail.
4.2.11 SNMP Traps plugin
Overview
Product Code [Om-E-SNMP]
The SNMP Traps plugin converts all events generated by Omnicast into SNMP traps.
A Virtual Matrix is needed (included in the base package) to host the VM plugins.
Performance
A plugin is required per SNMP Traps agent.
Third party software is required. The SNMP Traps agent components must be installed on a separate server,
additional cost is involved.
22
4.3
System Features
This section covers the system wide features of the Enterprise package.
4.3.1

Feature overview
Product Code [Om-E-ACD]
This feature allows system administrators to integrate to Windows Active directory
4.3.2
Camera blocking
Feature overview
Product Code [Om-E-CB]
This feature allows system administrators to block the transmission of the live video feed only of specific cameras
for investigation purposes.
4.3.3
Remote Live Viewer

Feature overview
Product Code [Om-E-PRLV]
This feature allows Live Viewer operator to control the video content of other Live Viewer stations connected to the
system through a graphical representation of the remote stations. The feature is use to create a video wall
application using the Omnicast Live Viewer.
23
4.4
Failover and redundancy
4.4.1
Failover Directory
Feature overview
Product Code [Om-E-1FOD]
The failover directory is intended to protect the Omnicast system from hardware or software failure. One failover
directory option must be ordered for every Directory that is part of a fail-over system. Failover directory works as
a master to slave configuration. The directory designated as the master will be responsible to push the system
configuration to the slave directories after a failover.
One (1) failover directory license includes one (1) Gateway license to be installed on failover Directory machine.
Performance
Failover directory with automatic synchronization should be used for system with 1,000 cameras or less.
For system with more than 1,000 cameras, a single central SQL database server should be used; no database
synchronization is needed in this case.
In synchronized mode, the number of failover directories should not exceed 3.
If more than 3 failover directories are needed (e.g. remote sites), synchronization should be turned off.
4.4.2
Failover camera connection

When failover archiving is required, failover camera connection licenses must be ordered. The failover camera
connection doesnt include the camera connection license which must be purchased separately. The failover camera
connection license includes both the failover and redundancy archiving options.
The number of failover camera connection must match the total number of cameras the customer wants to protect.
Ex.: If a customer has 200 cameras and wants to protect all the 200 cameras but only 100 at the same time, he needs
to buy 200 failover camera connections. If the customer buys 100 failover camera connections, he will have to
select in advance which cameras he wants to protect.
The recommended scenario is always to protect all the cameras in the system.
Additional archiver servers may need to be deployed in order to failover the cameras.
Performance
The number of cameras that can be handled by a single archiver will vary depending on the performance of the
hardware where the Omnicast application is running. Like a regular archiver, the failover archiver, on a high end
server, can handle a maximum of 300 cameras or 300 Mbps of throughput; whichever comes first.
4.4.3
Windows Clustering Support

Feature overview
Product Code [Om-E-1CST]
Windows Clustering support licenses are intended for systems which use Microsoft Windows Clustering for the
failover mechanism. This license provides an additional Omnicast Directory license for one other node of the
cluster.
24

4.4.4
Virtual Matrix Failover

Feature overview
Product Code [Om-E-1FOV]
Virtual matrix failover is needed to protect a virtual matrix server from hardware or software failure.
Note that Virtual Matrix failover doesnt support VM plugins.
Performance
The failover scheme is 1:N where N should not exceed 3.
4.4.5

Feature overview
Product Code [Om-E-VIRT]
Virtualization support license is intended for Omnicast systems running in virtual environments. This license is a
system-wide option and covers for all Omnicast servers in the system that could be deployed in a virtual
environment.
The virtual environment supported by Omnicast is VMware.
Note that running in a virtual environment may have performance implications which can invalidate certain design
guidelines recommended by Genetec.
25
4.5
Server licenses
The server options allow the addition of Omnicast servers to an enterprise system for additional performance.
4.5.1
Omnicast Gateway
Feature overview
Product Code [Om-E-1OGW]
Omnicast Gateways can be added to an enterprise system for traffic optimization purposes.
Performance
On a high end server, one (1) Gateway can handle a maximum of 150 simultaneous client connections or 300 Mbps
of video throughput (150 Mbps IN / 150 Mbps OUT).
4.5.2
Virtual Matrix
Feature overview
Product Code [Om-E-1VM]
Omnicast Virtual Matrix can be added to an enterprise system as required. The Virtual Matrix manages camera
sequences, CCTV keyboards, hardware matrices, access control interfaces, macros and VM plugins.
The main reason why an additional virtual matrix would be needed is to manage multiple camera sequences.
Performance
On a high end server, one (1) virtual matrix can handle a maximum 300 Mbps of video throughput (150 Mbps IN /
150 Mbps OUT).
4.5.3
Metadata Engine
Overview
Product Code [Om-E-1MDE]
The metadata engine is required to host the metadata plugins. Metadata plugins are presented in the third-party
integration section.
Performance
The number of plugins that can be managed by a single metadata engine server depends on the nature of the plugin.
Some plugins might require more CPU, see third-party integration section for more information on performance.
4.5.4

Overview
Product Code [Om-E-1ARC]
This part number is only require when adding Archiver servers to an existing Omnicast 4.5 (or earlier versions)
installation. There is no cost for this part number, but a license file must be issued by Genetec in order to activate
this new Archiver server.
Performance
26
The number of cameras that can be handled by a single archiver will vary depending on the performance of the
hardware where the Omnicast application is running. A high end server can handle a maximum of 300 cameras or
300 Mbps of throughput; whichever comes first.
The maximum throughput of the Archiver may be increased using Windows 2003 Enterprise R2 64-bit, please
contact Genetec for more information.
4.6
Bosch VRM
4.6.1
Camera connection for Bosch VRM

Product Code [Om-E-1CVRM]
The camera connection for Bosch VRM is required when Omnicast is installed with the Bosch VRM solution. The
camera connection for Bosch VRM doesnt support video recording in Omnicast. The video recording is managed
by the Bosch VRM system and seen as edge recording for Omnicast.
The camera connection for Bosch VRM license is order instead of the regular camera connection license. This is
not an add-on to the regular camera connection license.
Failover camera connections can also be ordered using the Bosch VRM solutions in order to protect the command
and control of the camera. The recording of the camera is not protected by Omnicast in this case since it is managed
by Bosch.
4.6.2
Archiver for Bosch VRM

Product Code [Om-E-1AVRM]
The Archiver for Bosch VRM is required when Omnicast is installed with the Bosch VRM solution. This Archiver
doesnt have the ability to record video. Using the Bosch VRM solution, the video recording is done at the edge
using Bosch IP video units and iSCSI storage units. This part number will enable to Archiver to go up to 1,000
cameras per Archiver.
Performance
Because this Archiver doesnt record video, it has the ability to manage up to 1,000 cameras for command and
control on a high end server. No live video redirection shall be done by the Archiver when managing 1,000
cameras. The network should be fully multicast and live streaming should be multicast from the camera/encoder to
the Live Viewer.
Playback video will transit through the Omnicast Archiver. A maximum of 100 Mbps (50 Mbps IN / 50 Mbps
OUT) of playback redirection is supported by the Archiver when managing 1,000 cameras.
27
4.7
Federation Options
Overview
Product Code [Om-E-FES] [Om-E-FED] [Om-E-1FEC]
NOTE: This option should only be used to expand existing Omnicast 4.x system with Federation. New systems
which required Federation options should used Security Center Federation.
An Omnicast Enterprise base package is required to order the federation options.
Users that own an Omnicast system should first upgrade to version 4.0 or up and then order the appropriate quantity
of the following three items:
Federation servers (depends on the number of federation directory/cameras)
Federated directories (for each federated directory)
Federated cameras (for each federated camera)
The Federation feature is version independent. Omnicast systems 4.1 and up can be federated into an Omnicast 4.7
Enterprise package. Not all features will be supported when federating a system of an earlier version.
Performance
The number of cameras that can be handled by a Federated server depends on the number of clients simultaneously
connected to the Federation. Video is redirected by the Federation server. On a high end server, one (1) federation
server can handle a maximum 300 Mbps of video throughput (150 Mbps IN / 150 Mbps OUT).
28
4.8
Auxiliary Archiver Options

Overview
Product Code [Om-E-RSA] [Om-E-1AAC]
An Omnicast Enterprise base package is required to order the Auxiliary Archiver options. Auxiliary Archiver can be
ordered to protect video archiving by recording a camera already managed by an archiver on a different schedule
with a different video quality. This option is not a replacement of the Archiver. It is a complementary option.
Users that own an Omnicast system should first upgrade to version 4.1 or up, and then order the appropriate quantity
of the following two items:
Auxiliary Archiver servers
Auxiliary Archiver cameras
The number of camera connections is a pool of cameras for all the Auxiliary Archivers on the system.
Performance
The number of cameras that can be handled by a single Auxiliary Archiver will vary depending on the performance
of the hardware where the Omnicast application is running.
29
4.9
4.9.1
Access Control
a) ACS PRCS (Parking Revenue Control System)

Feature overview
Product Code [Om-E-1PACS]
The ACS PRCS Plugin allows system users to collect access control events for after the fact investigation
generated by the Parking Revenue Control System from ACS. Every time a transaction (entry, exit, payment,
etc.) is made at an ACS parking gate, the transaction information is sent to Omnicast for video indexation.
A Metadata Engine is needed to host this plugin.
Performance
A plugin is required per ACS PRCS system. The plugin can handle a maximum of 1,000,000 transactions in the
database. The maximum supported event rate is five (5) transactions per second.
Third party software is required. The ACS PRCS components must be installed on a separate server, additional
cost is involved. The integration is based on the ACS Video Integration Module (VIM) interface version 1.0.
b) Access control interface
Feature Overview
Product Code [Om-E-1ACS]
An access control interface license is required for each access control system connected to Omnicast. The access
control interface is not an integration, but a simple interface capable of receiving Pelco ASCII command from an
access control system for camera switching.
A Virtual Matrix is needed (included in the base package) to host the access control interface connection.
c) GE Picture Perfect
Feature overview
Product Code [Om-E-1PPFT]
The GE Picture Perfect Plugin allows system users to collect GE Picture Perfect events for either real time
notification or after the fact investigation.
Performance
A plugin is required per GE Picture Perfect server.
Third party software is required. The GE Picture Perfect components must be installed on a separate server,
30
d) Hirsch Velocity
Feature overview
Product Code [Om-E-1PHRS]
The Hirsch Velocity Plugin allows system users to collect access control events for either real time notification
or after the fact investigation.
Performance
A plugin is required per Hirsch Velocity server.
Third party software is required. The Hirsch Velocity components must be installed on a separate server,
e) Lenel
Feature overview
Product Code [Om-E-1PLEN] [Om-E-1VLEN]
The Lenel Plugin allows system users to collect Lenel events for either real time notification or after the fact
investigation.
The Lenel Video Translator allows Omnicast live and playback video to be displayed in Lenel.
Performance
A plugin is required per Lenel server.
One Lenel Video Translator must be ordered per Lenel server.
Third party software is required. The Lenel components must be installed on a separate server, additional cost is
involved.
f) RBH
Feature overview
Product Code [Om-E-1PRBH]
The RBH Plugin allows system users to collect RBH Axiom V events for either real time notification or after the
fact investigation.
Performance
31
A plugin is required per RBH Axiom V server.

Third party software is required. The RBH Axiom V components must be installed on a separate server,
g) Software House
Feature overview
Product Code [Om-E-1PSHCC] [Om-E-1S]
The Software House Plugin allows system users to collect C-Cure 9000 events for either real time notification or
after the fact investigation.
The Software House integration also allow to view live and playback video and handle Omnicast events in CCure 9000. The metadata engine plugin is not required for this integration. Only SDK connections are required.
Performance
For the C-Cure events in Omnicast, one (1) plugin is required per C-Cure 9000 server.
For video and events in C-Cure 9000, one (1) SDK connection license is require per per C-Cure 9000 server
andone (1) Omnicast SDK connection license must be ordered per C-Cure 9000 client station.
Third party software is required. The C-Cure 9000 components must be installed on a separate server, additional
cost is involved.
h) Southwest Microwave MicroPoint
Feature overview
Product Code [Om-E-1PSWM]
The MicroPoint plugin is an access control plugin that integrates Southwest Microwaves MicroPoint perimeter
fence protection system to Omnicast. The MicroPoint Plugin allows system users to collect perimeter breach
events for either real time notification or after the fact investigation.
Performance:
A plugin is required per MicroPoint Master Processor Module (PM). One MicroPoint system may be composed
of multiple PM for which one is identified as the master.
Third Party Software requirement:
Third party software is required. The MicroPoint components must be installed on a separate server and
configured separately, additional cost is involved.
i) Verex
32
Feature overview
Product Code [Om-E-1PVRX]
The Verex Plugin allows system users to collect Verex Monitor xL events for either real time notification or after
the fact investigation.
Performance
A plugin is required per Verex Monitor xL server.
Third party software is required. The Verex Monitor xL components must be installed on a separate server,
33
4.9.2
Video Analytics
a) iOmniscient plugin
Overview
Product Code [Om-E-1PIOM] [Om-E-1IOS]
The iOmniscient Plugin allows system users to collect video analytic events for either real time notification or
after the fact investigation.
One license is required per plugin and one additional license is required per camera. A Direct Show Filter
connection needs to be ordered separately in order to get the video stream to the iOmniscient server.
Performance
A plugin is required per iOmniscient server. Multiple iOmniscient plugins can run on the same metadata server.
A total maximum of 100 cameras should be managed by one metadata server.
Third party software is required. The iOmniscient components must be installed on a separate server, additional
cost is involved.
b) Object Video plugin
Overview
Product Code [Om-E-1POBV] [Om-E-1OV]
The Object Video Plugin allows system users to collect Object events for either real time notification or after the
fact investigation.
One license is required per plugin and one additional license is required per camera. A Direct Show Filter
connection needs to be ordered separately in order to get the video stream to the Object Video server.
Performance
A plugin is required per Object Video system. One Object Video system may be composed of multiple servers.
The Object Video plugin communicate with the Object Video daemon.
Third party software is required. The Object Video components must be installed on a separate server, additional
cost is involved.
c) OV Ready camera connection
Overview
Product Code [Om-E-1OVR]
34
The OV Ready camera connection enables management of video units supporting the OV Board analytic engine.
This license enables rules configuration and analytic event management from Omnicast.
No Metadata Engine server or plugin is needed with the OV Ready camera connection license.
The video unit supporting OV Ready protocol are the following:
Pelco IXE20C, IXE20DN
4.9.3
Point of Sales (POS)
a) Generic POS Plugin

Overview
Product Code [Om-E-1PGPOS] [Om-E-1GPOS]
The Generic POS plugin is intended to provide a bridge between Omnicast and third-party POS systems. The
Generic POS plugin works in collaboration with other POS plugin (ex. Micros POS) or can be used by
Professional Services to build a custom integration with third-party POS systems, additional cost involved.
The Generic POS plugin doesnt provide the integration to POS system by itself.
Third party software is required. The POS system components must be installed on a separate server, additional
cost is involved.
b) Micros POS Plugin
Overview
Product Code [Om-E-1PMPOS] [Om-E-1MPOS]
The Micros POS plugin provides an integration with Micros 9700 POS systems. The Micros POS plugin
retrieves the transaction logs from the POS system and links those transactions to Omnicast recorded video. No
real-time alert are generated by the plugin based on transaction logs. The purpose of the plugin is to conduct
after the fact video searches based on POS transaction logs.
Performance
The Micros POS plugin is the driver communicating with the Micro 9700 system. One (1) plugin is required per
POS server. One (1) Micro POS check lane connection must be ordered per POS terminal. The Micros POS
plugin requires the Generic POS plugin which is included in every order of the Micro POS plugin.
Third party software is required. The POS system components must be installed on a separate server, additional
cost is involved.
35
4.9.4
Video Walls
Overview
Product Code [Om-E-AVM] [Om-E-HVM] [Om-E-5VWCT] [Om-E-10VWCT]
Video wall plugins are plugins that integrate with video walls and remote desktop system. The following types of
plugins are available as client plugins:
Barco Transform A video wall plugin
Barco Transform H video wall plugin
Barco Cottus Viewer plugin
Barco plugin allows the control of the video content of a Barco wall. Barco wall plugins are sold per wall. A wall is
composed of one Barco controller and one or multiple display panels. An Omnicast Virtual Matrix is required for
the Barco plugin to operate. A free of charge Virtual Matrix plugin must also be installed.
Barco Cottus Viewer plugin allows to remote desktop to Cottus client stations. Barco Cottus Viewer plugin licenses
are sold per either 5 or 10 pack licenses. One license is needed per Cottus client station.
36
37
Common Options
5.1
Base Package Options

Below is the description of the options available in the different base packages.
5.1.1
Maps and procedures

Feature overview
Included in all base packages
This feature allows users to display HTML maps and alarm procedures in the Live Viewer application. This is used
when end users wish to display custom site maps in the Omnicast Live viewer application. Maps can be configured
to be interactive or with animations.
5.1.2
Audio support
Feature overview
This feature enables system wide 2-way audio for both listening and recording. Typical usage is with intercom
applications.
5.1.3
Web Pack
Feature overview
This feature allows Web Live Viewer and Web Archive Player connections. Each connection requires a client
license.
5.1.4
Camera sequence
Feature overview
Camera sequence allows users to configure a list of cameras to be displayed in cycle in a single tile within the Live
Viewer or single analog monitor.
A Virtual Matrix is needed (included in the base package) to host the camera sequences.
5.1.5
Macros
Feature overview
Available in Pro and Enterprise base packages only
This feature enables the usage of macros in the system
A Virtual Matrix is needed (included in the base package) to host the macros.
5.1.6
Alarm management
Feature overview
38

This feature enables the usage of the Omnicast alarm functionalities.
5.1.7
Local archiving
Feature overview
Available in Enterprise base package only (option in Pro)
Local archiving allows users to perform recording on the different client workstations.
5.1.8
Offline archiving
Feature overview
Available in Enterprise base package only (option in Pro)
This feature allows system operators to perform offline backup and then restore of video files associated to system
cameras.
5.1.9
Database reporting
Feature overview
This feature allows system administrators to run system and user activity reports.
5.1.10 Edge recording and trickling support

Feature overview
Edge recording support provides the ability to retrieve recorded video from the edge devices using the Omnicast
Archive Player. This feature can be used to protect recorded video during a network outage. Video trickling
support adds the ability to automate the transfer of the edge recorded video to the Archiver. Units supporting edge
recording and trikcling are the following:
Axis cameras equipped with a SD/SDHC slot
Bosch video units with internal hard drives, USB port or iSCSI recording capabilities
Genetec Protocol partners which have implemented edge recording
GE SymDec, SymSafe and SymSafe Pro series (edge recording only)
5.1.11 Time zone support
Feature overview
This feature allows the Omnicast system to run in a multi time zone environment where the cameras, the clients
and/or the servers are located in multiple different time zones.
5.1.12 Languages
Omnicast supports the following languages which are available in all the packages.
39
English
French
Arabic
Czech
Dutch
German
Italian
Japanese
Korean
Persian
Portuguese
Russian
Simplified Chinese
Slovak
Spanish
Thai
Traditional Chinese
40
Omnicast Demo Licenses

In order to demonstrate the software capabilities, integrators can purchase demo licenses that include:
4 camera connections
2 client connections
1 SDK connection
1 Virtual Matrix
Additional special features are available on demand. Demo licenses are available for a period of one year, and are
automatically renewable after that period.
41
Omnicast SDK
Overview
The Omnicast SDK enables software developers to customize their video surveillance solution by creating valueadded applications that run in Omnicast or develop integrations to third party systems. By offering a wide range of
functions that power Omnicasts Live Viewer and Archive Player applications, the SDK provides a complete set of
live viewing, archive retrieval and archive playback capabilities. For a complete list of available functions, please
refer to the SDK help file.
Technology
Omnicasts SDK consists of a collection of ActiveX components exposing a wide range of functionalities found in
the Omnicast solution. Software developers can create either HTML based application using VBScript or Jscript, or
Win32 based applications using Visual Basic, C, C++ or C#. The SDK can also be used to create macros for use
within Omnicast.
Contents
Everything you need to start developing new applications is included with the purchase of the Omnicast SDK. The
kit includes:
SDK package which includes libraries, code samples, tutorials and documentation
Access to Genetec Technical Assistance Centre (GTAC) Online Knowledge Base
Omnicast Enterprise, Full Featured, Not For Resale License
o
4 SDK connection
4 cameras connection
2 clients connection
42
SMAs
See SMA documentation of Channel Partner Portal for:
SMA pricing
SMA policies
Upgrade packages
Warranty issues
43
Appendix A Server type

See Omnicast System Requirements on Genetecs Website at http://www.genetec.com.
44
10 Appendix B Workstation type

See Omnicast System Requirements on Genetecs Website at http://www.genetec.com.
45
11 Appendix C Feature comparison

See Omnicast Feature Breakdown on Genetecs Website at http://www.genetec.com
46

Genetec - Omnicast 4.8 Ordering Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Genetec - Omnicast 4.8 Ordering Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

IP Video Surveillance

Upgrade to Pro or Enterprise

Digital inputs and digital outputs

Camera connection for advanced mapping (Plan Manager)

Archiver (Omnicast 4.5 and under)

Support for virtualization

Windows Active Directory

genetec.com | Omnicast 4.8 | Ordering Guide

Digital inputs and digital outputs

Camera connection for advanced mapping (Plan Manager)

Direct Show Filter connection

SNMP Traps plugin

Windows Active Directory

Remote Live Viewer

Failover and redundancy

Failover camera connection

Windows Clustering Support

Virtual Matrix Failover

Support for virtualization

Archiver (Omnicast 4.5 and under)

genetec.com | Omnicast 4.8 | Ordering Guide

Camera connection for Bosch VRM

Archiver for Bosch VRM

Auxiliary Archiver Options

a) ACS PRCS (Parking Revenue Control System)

b) Access control interface

h) Southwest Microwave MicroPoint

b) Object Video plugin

c) OV Ready camera connection

Point of Sales (POS)

a) Generic POS Plugin

b) Micros POS Plugin

Base Package Options

Maps and procedures

genetec.com | Omnicast 4.8 | Ordering Guide

Edge recording and trickling support

Time zone support

Omnicast Demo Licenses

Appendix A Server type

10 Appendix B Workstation type

11 Appendix C Feature comparison

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

(3) Part identification:

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

Upgrade to Pro or Enterprise

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

Digital inputs and digital outputs

genetec.com | Omnicast 4.8 | Ordering Guide

Camera connection for advanced mapping (Plan Manager)

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

Archiver (Omnicast 4.5 and under)

Support for virtualization

genetec.com | Omnicast 4.8 | Ordering Guide

Windows Active Directory

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide

genetec.com | Omnicast 4.8 | Ordering Guide