Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Open Architecture Integration of Disparate Video and Security Systems
1
2
3
4
Ver.
20/10/2014 Creation of document
22/10/2014 Validation
Date
PRYSM SOFTWARE
Object
LH
NM, OB
Creation
LIAM HEATLEY
1
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Contents of Document
What is Open Architecture PSIM ................................................. 3
About Prysm ................................................................................. 6
The importance of Open Architecture PSIM in CCTV
management ............................................................................ 8
AppVision PSIM - what does it do with CCTV? ................................... 10
New feature in AppVision Version 4 - Video black box ..................... 12
Distribution of video images to AppVision client stations .................. 13
How can video be displayed in AppVision PSIM ................................ 14
Open Architecture PSIM in Security & Alarms management .... 15
AppVision PSIM for Alarms Handling – key advantages .................... 17
Open Architecture Building Management .................................. 21
AppVision System Architecture .................................................. 23
AppVision Unfied Video Walls – Hidden Video Clients ...................... 25
Growing your PSIM project – Multiple / regional servers .................... 26
AppVision PSIM Failover Architecture ........................................ 27
What is a redundant server architecture? ........................................... 27
Hardware Configuration ............................................................... 28
Hardware Configuration For Video Black Box Storage...................... 31
Manufacturer SDK Limitations and New Driver Developments 32
Extract for consultants to use in tenders ................................... 33
PRYSM SOFTWARE
LIAM HEATLEY
2
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
WHAT IS OPEN ARCHITECTURE PSIM
PSIM is the most open method of unifying and managing different technologies
and brands for use in security command & control rooms. No PACS or VMS can
provide this level of openness and customisation.
Is it fair that clients pay for their security equipment installations but do not have full
ownership of them to obtain the actual features they want? Or that they can't
deploy the security systems that they want because their control room is tied to a
PACS or VMS and won't work with a competitors system?
Unified management of different brands and systems means installing open
architecture technologies and being able to choose from best of breed, now and
in the future.
PSIM is about simplified handling procedures, geolocalised security events in real
time, and the provision of simple step by step guides to operators as well as post
event forensics and accountability of security personnel.
PSIM provides as standard : Open customization of graphics and procedures, audit
trail of user actions, scalability for multi site projects, failover and redundancy,
alarm and video wall integration irrespective of brand, video analytics integration,
escalation of events and alarms, geolocalisation, GIS, Computer Aided
Despatch and much more
Open architecture means having free access to an SDK for development, as well
as competitive development from a global network of partners, open server and
client scripting, open access to all internal graphics and editors as well as
system Runtime, the ability to customize graphics and screen layout as you want
PRYSM SOFTWARE
LIAM HEATLEY
3
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
them to be.
PRYSM SOFTWARE
LIAM HEATLEY
4
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
If you don’t have a
completely open
architecture system
in your control room
then the chances
are that you aren’t in
charge of how you
use it or what you
can connect to it.
As a result you will be
tied to the
proprietary systems
main features, be
that access control
or video recording.
Only a true PSIM is
open architecture
and can integrate
with any open
security , BMS or
automation
technologies.
AppVision PSIM can
even connect to
other open PSIM’s or
open BMS platforms.
PRYSM SOFTWARE
LIAM HEATLEY
5
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
ABOUT PRYSM
PRYSM was created in 1996 by software engineer Jean-Michel Belin who was
previously the software director of a well known access control manufacturer.
The development was undertaken in partnership with a leading integration
company that was looking for a way to avoid or reduce manufacturer lock in
practices from bundled proprietary software interfaces.
Jean-Michel’s initial goal was to develop a unifying integration system that
managed alarms from mainstream security equipment manufacturers in order
to provide geolocalisation of events in real time and guide operators through
the next step security procedures.
At the time the only GUI (graphic user interface) open integration systems
were SCADA systems, which were used in industrial automation and were
complex and costly to deploy. It was decided to structure AppVision using
similar open tools and techniques but with much simpler methods for GUI
building, system configuration and deployment.
AppVision was first released as a basic alarms management system in 1998,
and underwent several evolutions and rewrites prior to becoming a fully open
PSIM system which it now is.
The AppVision PSIM now is deployed at hundreds of critical infrastructure
projects each year by an ever growing community of support and
development partners around the world. The total number of projects has
reached over 3000 with a mix of project vertical markets and sizes, including
major integration projects that unify security and building automation
technologies for control room management.
Not only is AppVision one of the easiest and most
versatile PSIM technologies to deploy but our
aggressive partner pricing model and extremely
open architecture system is radically different to
many of our mainstream competitors.
PRYSM SOFTWARE
LIAM HEATLEY
6
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
While other PSIM companies now exist, they mostly share a common theme
which is to segment the markets that they target based on high value (and
high profit) to them. At PRYSM, we feel that this provides a disservice to
security integration partners and does not allow installers and clients with
smaller projects to benefit from open architecture systems. As a result, many
smaller and medium sized projects become tied to costly and proprietary GUI
based technologies that are more difficult to
evolve with a project needs.
Rather than use market acceptance pricing
strategy used by most PSIM brands, PRYSM
deliberately uses a democratic pricing
method that offers a low cost licensing
method based on the actual size of the
project (measured in number of connected
systems). This means that in some cases the
AppVision PSIM is between 3 to 10 times
cheaper than other mainstream PSIM’s.
PRYSM SOFTWARE
LIAM HEATLEY
7
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
THE IMPORTANCE OF OPEN ARCHITECTURE PSIM IN CCTV MANAGEMENT
It should not matter what the source of the
video is to be able to manage security in a
unified control room
CCTV systems are now part of everyday life and have become important tools to
keeping us safe from criminals or terror.
As a result of the dramatic growth there are now plenty of well known
manufacturers of CCTV recording systems all competing for projects. Network
video management systems have become increasingly more sophisticated and
some also provide limited integrations to non competing security systems.
Mainstream VMS brands are however not able to integrate with each other, which
poses a major problem for security projects where cameras connected to different
VMS brands have to be seen and used together. Using a VMS (or PACS) as the
integration system in a control room also establishes very high barriers that make it
very difficult and costly to change technologies away from that VMS or PACS in
the future. As a result, the manufacturer “owns the customer” and demands for
product improvements, lower operating or maintenance costs, or system
customisation may be slow and cost more than if the PSIM was the heart of the
control room.
Integrators and consultants have an important choice to make when designing a
project : either they tie CCTV projects to single VMS or NVR brands, or find an open
PRYSM SOFTWARE
LIAM HEATLEY
8
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
architecture system that can integrate with most of the VMS manufacturers.
AppVision open architecture PSIM is deployed inexpensively to provide additional
features that the VMS or NVR platforms cannot manage. Quite simply, in most
cases this means being able to unify different manufacturers in the same control
room. But the advantages don't stop there.
AppVision PSIM is a much more open and customisable technology than you can
imagine. In most cases using AppVision PSIM means it becomes possible to build
the project as the client or the consultant wanted it, and not simply what the VMS
was able to do.











Unify different CCTV and VMS brands in the same video wall
Build custom GIS or maps to easily geolocate the nearest camera to an
event
Use custom navigation bars and icons on maps
Deploy custom and dynamic icons with custom menu options to choose
cameras or drag and drop them onto the video wall
Pop up camera displays on motion detection, access control or other
alarms
Build custom virtual matrices with flexible display options
Single click creation of an event hotpot and manual events logs
Computer aided dispatch : dispatch mobile units to site with drag and drop
(V.4)
.... escalation of events, integration of all other connected systems
.... guided procedures for event and incident handling
.... single click lock down, fire alarm role call lists
The AppVision PSIM video wall system integrates with other AppVision modules or
as a stand alone system.
It unifies different video technologies from most mainstream IP NVR and VMS
manufacturers as well as DVR, NVR, MJPEG, MPEG4, H264, ONVIF and even VLC.
PRYSM SOFTWARE
LIAM HEATLEY
9
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
APPVISION PSIM - WHAT DOES IT DO WITH CCTV?
AppVision PSIM in a CCTV control room is used to guarantee system openness and
unify different CCTV security systems by connecting to the VMS server as well as to
the cameras where needed. It also simplifies management and operational
procedures for operators, since they can learn how to use AppVision rather than a
whole host of different and proprietary systems that would otherwise only work in
silos. This makes it quicker to train new staff.
In some cases, these benefits mean that a reduction in security personnel
becomes possible, and perhaps also a more centralised security approach for
disparate geographical sites that may not need so many manned guards 24/7.
Features
Many of the features that are attributed to the PSIM are dependent on what the
manufacturers SDK facilitates. Some SDK’s are more open than others.
The main CCTV features from AppVision PSIM are as follows :







Live camera display in PSIM video wall for different VMS or camera sources
Support different VMS/NVR SDK’s as well as ONVIF and MJPEG streams
Camera PTZ through PSIM interface or in CCTV window
Manage dome cameras preset positions from PSIM GUI
Show dome camera preset positions in PSIM GUI
Show dome camera true positions in PSIM GUI (where available from the
VMS or camera)
Receive motion detection alarms and provide next step procedures to
operators
PRYSM SOFTWARE
LIAM HEATLEY
10
Open Architecture Video Surveillance












AppVision Physical Security
Integration Manager
Receive alarms from any other connected alarm system as the trigger to
push nearest CCTV camera to video wall, and provide next step procedures
to operators
Use the video stream from the VMS as the source for video analytics either
within the PSIM or fed to the PSIM from the analytics system
Receive alarm events related to any other connected systems fed into the
VMS (analytics for example)
Retrieve camera playback from the VMS directly into the PSIM unified smart
wall
Create instant icons on PSIM GUI as markers or hotspots that instantly retrieve
the playback the precede the creation of the marker
Display lost camera signal
Provide distributed architecture of access to video to different locations,
and operators based on roles and responsibilities (user profiles).
Provide standard operating procedures “prompts” to guide operators in
security alarm events.
Messaging – provide a method for operators to log important messages or
information instantly and send them to senior staff or maintenance teams
Provide full logs of operators actions and audits of past events
Escalate difficult events automatically or manually to other more senior
operators
Video Black Box server – a full audit of what the operators are seeing in the
video wall at all times, with network access, configurable time delays for
screen recording, search by time and image export. More information
about this on the next page :
PRYSM SOFTWARE
LIAM HEATLEY
11
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
NEW FEATURE IN APPVISION VERSION 4 - VIDEO BLACK BOX
The “video black box” is a dedicated recording server that records what is
displayed on the operators screen so that we can later see what they were
looking at, or at least what was displayed and they should have been looking at.



This is described as a black box, similar to a flight recording device used on
airplanes, but in this case it is the video images that are of interest, rather
than audio.
The video black box features a configurable screen grabber that will record
what is displayed on one of many AppVision client station or video client
station screens.
The images will be stored in individual files of limited time duration, rather
than a completely stitched image, and will be ready for searching or
viewable in a single video stream.
Storage
The Video Blackbox storage is configurable on a network server.
Search feature
 Using the time stamp from other security data in the AppVision PSIM, or from
connected VMS platforms the Senior Security Manager will be able to
search by time and date criteria.
 AppVision PSIM will automatically display the video black box sequence
starting from the time and date that is entered.
Export feature
 The individual files can be exported using the Export button in the AppVideo
interface.
PRYSM SOFTWARE
LIAM HEATLEY
12
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
DISTRIBUTION OF VIDEO IMAGES TO APPVISION CLIENT STATIONS
Each AppVision PSIM client station can connect to
whatever VMS its needs to be talking to
AppVision client stations connect individually, directly to the VMS or cameras using
the network + proprietary (or ONVIF / MJPEG) protocol as the communication
method. This is the most efficient way to communicate with lower image latency
and less use of network bandwidth (which would be much higher if AppVision
downloaded all video streams and events in real time in order to redistribute them
again to AppVision clients).
Changing camera FPS or resolution
VMS platforms manage the image quality for both stored and displayed images
from cameras. In some cases it is possible for the PSIM to send commands to the
VMS to modify the video camera resolution that is streamed to the PSIM video wall.
As such, the PSIM does not re package or modify the cameras recorded or
displayed images (which otherwise may have legal implications on the validity of
the video recording).
The PSIM can also send commands to the VMS or even to the camera directly to
request a video stream in a lower resolution format. Where the VMS or camera
supports this, the PSIM can display the lower resolution format in the AppVision
video client wall.
PRYSM SOFTWARE
LIAM HEATLEY
13
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
HOW CAN VIDEO BE DISPLAYED IN APPVISION PSIM
There are 4 main methods for displaying
video walls using AppVision.
1. Standard video monitors or HD
television screens – streamed via
hidden AppVision client stations.
Commanded remotely from any
connected AppVision client stations.
2. Dedicated video wall technologies
AppVision PSIM deployed at
such as Planar, Barco, Eyevis –
Marseille Police CCTV control room (can also
be viewedremotely
on Youtube) from
streamed via hidden AppVision client stations. Commanded
any connected AppVision client stations.
3. Miniature video display opened as part of the AppVision graphic user
interface. The screen space is split into window pane format. This can be
opened and closed by the operator using a control button and may also be
drag and dropped into the main video wall.
4. Incrusted video window that displays a permanent video window within the
custom graphic user interface, such as a map or building layout.
In all cases cameras can be drag and dropped into the video wall display.
AppVision supports a range of different video system drivers including ONVIF,
MJPEG, VLC, VMS / NVR / DVR, H264, MPEG4 (AVI)
PRYSM SOFTWARE
LIAM HEATLEY
14
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
OPEN ARCHITECTURE PSIM IN SECURITY & ALARMS MANAGEMENT
The security industry is awash with hundreds of different systems manufacturers
around the globe, some are more well-known than others. But what is the use in
having such a large selection if the control room system that is deployed does not
allow for the possibility of using them. This is what we mean by open architecture
and best of breed.
Best of breed as well as open architecture mean that the customer retains the
maximum level of choice, so that new technologies can be added to a security or
building management project at any point during the projects life cycle.
Proprietary systems do not offer this choice, since they exist mainly to support their
own branded product range, which in essence restricts choice to other brands.
We all know major manufacturers with software systems that meet this description.
The AppVision PSIM was developed as an open system so that it can be used to
manage different manufacturers and a vast array of different types of systems.
Clearly no PSIM will have integrated every manufacturer, but there must be clear
procedures and reasonable pricing in place to build these drivers as they are
required by client projects.
Everybody expects a PSIM or security management system to be able to manage
fire or intruder alarm systems, which AppVision does of course. Since AppVision was
first introduced in 1996 we have integrated systems such as :















Fire alarms
Intruder alarm panels
Access control panels and software
Perimeter fencing systems
Buried cable systems
Infra red systems
Ground based radar systems
Building automation systems using Modbus, Bacnet, KNX, OPC DA, OPC AE,
Ascii and OBIX
Telephone systems
Physical barriers such as gates, security doors, rising bollards
Intercoms
CCTV (see video chapter)
Noise detection (gunshot and scream)
Temperature monitoring
TV and audio control (infra red scanners using Modbus over IP)
PRYSM SOFTWARE
LIAM HEATLEY
15
Open Architecture Video Surveillance




AppVision Physical Security
Integration Manager
Video analytics
Vending machines
Wifi hotspot monitoring and geolocaisation
Network security monitoring
PRYSM SOFTWARE
LIAM HEATLEY
16
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
APPVISION PSIM FOR ALARMS HANDLING – KEY ADVANTAGES
AppVision PSIM is the most open integration system for unifying different
technologies and brands for use in security command & control rooms. No PACS or
VMS can provide this!
Scalability and multiple site projects
AppVision PSIM is be able to manage and integrate projects that cover large
geographical zones with the following abilities :
- VPN communications over large distances
- Sharing of real time data between different PSIM servers or client stations
- Manage different time zones
- Roles based user connections that restrict access and features based on
roles and responsibilities for different operators
- Floating workspace, where operators may connect to their dedicated
client stations and roles from any PSIM client station
Ability to seamlessly integrate different types of systems and different
manufacturers
- AppVision is able to seamlessly unify and manage : CCTV/VMS, Access
control, Intruder Alarms, Fire Alarms, Perimeter Protection (fence detection,
buried cable, infra red, ground based radar), Intercom systems, Building
automation so that they can be seen together in real time
- A range of different system manufacturers for each product category will
be supported
- AppVision PSIM also has an SDK for development by certified third party
developers, for new driver integrations
- It is possible to create interactions between all connected systems based
on triggers and cause and effect
- Triggers will also start appropriate standard operating procedures to guide
security personnel on incident handling
PSIM integration methods
AppVision PSIM offers a range of different integration techniques for driver
developments, that include:
- integrations using manufacturers SDK’s or API’s
- OPC, Modbus, KNX, ESPA, Bacnet or Ascii inputs
- Any SQL type database
- Open SDK available to new development partners
PRYSM SOFTWARE
LIAM HEATLEY
17
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Open architecture protocol drivers for automation and building management
systems.
AppVision PSIM can also connect to building automation and energy
management systems, but can also connect to Building Management
systems using a range of different drivers that support the following protocols :
-
ONVIF,
BACNET,
OPC DA and AE,
MODBUS,
KNX,
OBIX,
ASCII
ESPA (e.g. paging & nurse call system protocol)
NMEA (radar and GIS protocol)
PRYSM SOFTWARE
LIAM HEATLEY
18
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
List of mainstream AppVision PSIM Features :
-
Open architecture integration to any open systems
Integration of different security systems manufacturers
Unified management of different manufacturers
Alarms management and handling
Provide standard operating procedures “prompts” to guide operators in
security alarm events.
Easy geolocalisation of events and navigation of sites and security assets
on custom maps
Audit trail of all user actions
Scalable for multi site / national infrastructure projects
Redundancy back up with automatic failover
Video analytics supported natvely as well as through external systems
Roles based custom GUI for operators based on security levels
Escalation of alarms to senior operator
Automatically send SMS and email of events
Manual log events seen on cctv
Live camera display in PSIM video wall for different VMS or camera sources
Support different VMS/NVR SDK’s as well as ONVIF and MJPEG streams
Camera PTZ through PSIM interface or in CCTV window
Manage dome cameras preset positions from PSIM GUI
Show dome camera preset positions in PSIM GUI
Show dome camera true positions in PSIM GUI (where available from the
VMS or camera)
Receive motion detection alarms and provide next step procedures to
operators
Receive alarms from any other connected alarm system as the trigger to
push nearest CCTV camera to video wall, and provide next step
procedures to operators
Use the video stream from the VMS as the source for video analytics either
within the PSIM or fed to the PSIM from the analytics system
Receive alarm events related to any other connected systems fed into the
VMS (analytics for example)
Retrieve camera playback from the VMS directly into the PSIM unified
smart wall
Create instant icons on PSIM GUI as markers or hotspots that instantly
retrieve the playback the preceeds the creation of the marker.
Display lost camera signal
Provide distributed architecture of access to video to different locations,
and operators based on roles and responsibilities (user profiles)
PRYSM SOFTWARE
LIAM HEATLEY
19
Open Architecture Video Surveillance
-
AppVision Physical Security
Integration Manager
Messaging – provide a method for operators to log important messages or
information instantly and send them to senior staff or maintenance teams
Provide full logs of operators actions and audits of past events.
Escalate difficult events automatically or manually to other more senior
operators
Video Black Box server – a full audit of what the operators are seeing in the
video wall at all times, with network access, configurable time delays for
screen recording, search by time and image export
Maintenance module for connected systems
PRYSM SOFTWARE
LIAM HEATLEY
20
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
OPEN ARCHITECTURE BUILDING MANAGEMENT
As we saw earlier in this
document, AppVision
supports the most widely
used building automation
protocols that exist in a
modern building :
BMS / BAS protocols supported by AppVision
-
ONVIF,
BACNET,
OPC DA and AE,
MODBUS,
KNX,
OBIX,
ASCII
ESPA (e.g. paging & nurse call system protocol)
PRYSM SOFTWARE
LIAM HEATLEY
21
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
As such, it is entirely possible to deploy AppVision in direct connection to systems
that support these protocols, or even indirectly using input – output relays that act
as protocol converters.
These protocols can be used in AppVision to
connect to a vast array of different
technologies for energy management or
building automation, without the need for
additional management software.
Where a dedicated BMS / BAS software is
already in place then it should equally be
possible to identify a suitable protocol for data
sharing, or alternatively develop a driver to achieve this. For example, a driver to
support the Honeywell Tridium Niagara software was already developed by Prysm,
which enables AppVision to receive real time events and alerts from the Tridium
platform.
Other BMS systems can also be integrated.
PRYSM SOFTWARE
LIAM HEATLEY
22
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
APPVISION SYSTEM ARCHITECTURE
Single Server Architecture
This project proposal is based on a proposal for a single server and 15 client
stations. A single redundant server license with failover option is included. See
chapter below.
A single server infrastructure is suited for the centralised management of
connected systems that are managed within the same control room or reliable
and rapid VPN.
In the following diagram you can see how AppVision would be structured in a
single server architecture model.
PRYSM SOFTWARE
LIAM HEATLEY
23
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Light client V4 / 2014
Client
stations
Redundant
Server
AppVision
Server
AppVision
2 way comms
Compatible VMS servers
-can be a mix of brands on same
project
1
2
PRYSM SOFTWARE
3
2 way or 1 way comms
Alarms and Incidents
2 way comms
depending on choice of system
Access control
…
LIAM HEATLEY
Other :
-intercom
- Gunshot
- BMS
- I/O relays
….
24
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
APPVISION UNFIED VIDEO WALLS – HIDDEN VIDEO CLIENTS
Another aspect of AppVision PSIM is the ability to use AppVision client stations in video walls. This
takes the video feeds from connected VMS / NVR or cameras and displays them in AppVision client
stations. The client stations can be used solely with the purpose of sending the unified streams to
dedicated video screens or HD television screens.
A hidden AppVision client station is
connected over IP to other client
stations at the operator console.
The operator can remotely drag and
drop cameras as well as control
them in the video wall
IP Network
AppVision Server
PRYSM SOFTWARE
AppVision Failover Server
LIAM HEATLEY
25
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
GROWING YOUR PSIM PROJECT – MULTIPLE / REGIONAL SERVERS
Additional (and autonomous) PSIM servers are generally added to the system where it is necessary
for different control centers to be autonomous from each other, such as in regional control rooms
for Police authorities. In such cases, it is essential that each control room continues to function even
in the event of a network failure between the PSIM primary server and client stations. Where
regional autonomy is required, it is safer to look at a more distributed architecture using multiple
server stations.
PRYSM SOFTWARE
LIAM HEATLEY
26
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
APPVISION PSIM FAILOVER ARCHITECTURE
WHAT IS A REDUNDANT SERVER ARCHITECTURE?
2 or more AppVision servers are installed : the main server plus the back up (or
redundant) server(s). Here, 2 types of configuration are possible depending on the
sub systems to be managed :
- the sub systems accept multiple connections
- the sub systems accept only a single connection
In the 1st case a live redundant connection may be possible: this means that the 2
servers are active, while the client stations are connected to the main server. In
case of a system falldown on the main server the clients will automatically connect
to the back up server and continue to function with no reboot needed.
In the 2nd case only the main server is active. The back up server is simply
synchronised with the main server so that it can reboot in case of a main server
system falldown. As with the 1st case, all clients will connect to the back up server
and continue to run normally. The client stations will redirect their connections to
the back up server when this server reboots.
More redundant servers could also be included, as can additional main servers (at
additional license cost).
As you can see in the diagram, you can deploy a redundancy method with
failover so that clients and sub systems connect to the backup server in case of
Primary server failure.
Failover means getting AppVision client stations as well as all other connected sub
systems, such as alarm panels, VMS platforms etc to switch servers in the case that
the main server fails.
PRYSM SOFTWARE
LIAM HEATLEY
27
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
HARDWARE CONFIGURATION
System configuration is dependent of what you are going to do with your PSIM?
There is no one size fits all configuration for a PSIM project. There are hundreds if
not thousands of small stand alone AppVision projects using simple low capacity
PC systems to centralise alarm or access control management. These projects
typically do not use much system memory or require sophisticated graphics cards.
However, as the number of systems being managed grow, or with more use of
high resolution graphics and CCTV / video integration then your system
configuration will need to be more robust and also become distributed.
Video and high resolution graphics such as Autocad can use a lot of PC resources
and are incremental based on how many graphics and live camera streams are
to be displayed at any one time on the same PC server or client. The safest way to
manage these is with dedicated graphics cards and a distributed architecture
(several AppVision client machines), in particular for managing video walls with
AppVision.
We have successfully tested the AppVision central kernel server to 10’s of
thousands of alarm inputs.
For very large installations with hundreds of thousands of inputs it is also possible to
install AppVision sub servers with the goal of avoiding overload of the central
server.
PRYSM SOFTWARE
LIAM HEATLEY
28
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Here is a system configuration that can be used :
Name
Description
CPU
Dual Core Intel Xeon, minimum 2.0 GHz
RAM
Minimum 2 GB
Network
Ethernet 100Mbit
Graphics
Adapter if used
as client
Onboard GFX, AGP, or PCI-Express, Full HD, 16-bit colour
Or Matrox multi screen adapter for video walls
Hard Disk Type
E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)
Hard Disk Space
1 TB free (depends on recording settings)
USB
Spare USB 2.0 or higher for AppVision dongle
Serial port
Spare serial port
Drives
CD/DVD RW
Operating System
• Microsoft® Windows® 8 Enterprise (64 bit)
• Microsoft® Windows® 8.1 Enterprise (64 bit)
• Microsoft® Windows® 8 Pro (64 bit)
• Microsoft® Windows® 8.1 Pro (64 bit)
• Microsoft® Windows® 7 Ultimate (64 bit)
• Microsoft® Windows® 7 Enterprise (64 bit)
• Microsoft® Windows® 7 Professional (64 bit)
• Microsoft® Windows® Server 2012 (64 bit)
• Microsoft® Windows® Server 2008 R2 (64 bit)
• Microsoft® Windows® Server 2008 (64 bit) SP2
Software
Microsoft® .NET Framework.
PRYSM SOFTWARE
LIAM HEATLEY
29
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Remember though that the technical requirements on a pc server or client station
will vary enormously depending on the purpose for which it used.
Client stations are used mainly for 2 purposes:
Your choice of system configuration may depend on how you will use the client
stations.
1. Dedicated client stations to provide access to the AppVision server, display the
operator PSIM management console (free sitting system) and graphic interface,
access control management, video integration control, all custom commands,
logs, audits, reports etc
2. Hidden clients / For smart wall screen management :
Here you will need dedicated graphics cards with good internal memory.
The AppVision smart video client manages a screen or set of screens BUT is
controlled remotely via dedicated client stations using virtual cctv matrix
interfaces for camera drag and drop or layout changes.
For permanent visualisation of cctv cameras using the AppVideo module it is
generally recommended to connect 12 cameras per AppVision client station.
Most other equipment systems do not require the same level of pc RAM, graphics
card and processor resources.
PRYSM SOFTWARE
LIAM HEATLEY
30
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
HARDWARE CONFIGURATION FOR VIDEO BLACK BOX
STORAGE
This module would require a dedicated server for storage of the images that are
recorded.
Name
Description
CPU
Dual Core Intel Xeon, minimum 2.0 GHz
RAM
Minimum 2 GB
Network
Ethernet 100Mbit
Graphics
Adapter if used
as client
Onboard GFX, AGP, or PCI-Express, Full HD, 16-bit colour
Or Matrox multi screen apapter for video walls
Hard Disk Type
E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)
Hard Disk Space
1 TB free (depends on recording settings)
USB
Spare USB 2.0 or higher for AppVision dongle
Serial port
Spare serial port
Drives
CD/DVD RW
Operating System
• Microsoft® Windows® 8 Enterprise (64 bit)
• Microsoft® Windows® 8.1 Enterprise (64 bit)
• Microsoft® Windows® 8 Pro (64 bit)
• Microsoft® Windows® 8.1 Pro (64 bit)
• Microsoft® Windows® 7 Ultimate (64 bit)
• Microsoft® Windows® 7 Enterprise (64 bit)
• Microsoft® Windows® 7 Professional (64 bit)
• Microsoft® Windows® Server 2012 (64 bit)
• Microsoft® Windows® Server 2008 R2 (64 bit)
• Microsoft® Windows® Server 2008 (64 bit) SP2
Software
Microsoft® .NET Framework.
PRYSM SOFTWARE
LIAM HEATLEY
31
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
MANUFACTURER SDK LIMITATIONS AND NEW DRIVER DEVELOPMENTS
The development of new drivers for systems is dependent on obtaining a software
development kit (or similar) from the equipment manufacturer.
When choosing your equipment or sub system supplier (such as VMS) you should
always check if an SDK is available, free of charge for projects and new driver
developments.
The existence of the SDK is no guarantee that it possesses the same abilities as a
competitor’s SDK, as strategic choices may lay behind what the manufacturer
wants to allow a PSIM to integrate. For example, some VMS SDK’s do not allow live
camera, playback display or PTZ to be seen or managed in the PSIM.
Although we have a standard estimated tariff for new drivers, Prysm has to
evaluate the driver development and provide a cost for integration based on the
SDK.
Where the SDK has not yet been provided to us (but will be available) then Prysm
will best guess the cost based on past experience for the development to be
completed subject to revision once the SDK is on our possession.
PRYSM SOFTWARE
LIAM HEATLEY
32
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
EXTRACT FOR CONSULTANTS TO USE IN TENDERS
These extracts can be used for tender document creation by consultants.
Scalability and multiple site projects
The PSIM will be able to manage and integrate projects that cover large
geographical zones with the following abilities :
- VPN communications over large distances
- Sharing of real time data between different PSIM servers or client stations
- Manage different time zones
- Roles based user connections that restrict access and features based on
roles and responsibilities for different operators
- Floating workspace, where operators may connect to their dedicated
client stations and roles from any PSIM client station
PSIM integration methods
The PSIM will offer a range of different integration techniques in any driver
developments that include:
- integrations using manufacturers SDK’s or API’s
- Ascii feeds
- Any SQL type database
- Open SDK available to new development partners
Open architecture protocol drivers for automation and building management
systems.
The PSIM will also be able to function fully as or in connection to Building
Management systems using a range of different drivers that support the
following protocols :
-
ONVIF,
BACNET,
OPC DA and AE,
MODBUS,
KNX,
OBIX,
ASCII
VLC
PRYSM SOFTWARE
LIAM HEATLEY
33
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Pricing methods
The pricing method used by the PSIM manufacturer should be based on the
size of the project with the actual net benefit to the customer in that this
method reduces the cost of the PSIM licenses and maintenance contract for
smaller projects, and any increases in license cost will be a reflection on the
true size of the project.
International Support
It will be possible or already exist for training and certification of support
partners for the PSIM around the globe.
Best of breed, vendor neutrality and avoidance of manufacturer lock-in
The PSIM brand manufacturer will not also be a system manufacturer (video
management, access control, alarms or similar) in order to guarantee the
freedom to choose best of products now and in the future without fear of
being tied to single source brands.
Open SDK / driver development
The PSIM manufacturer will provide a free of charge SDK and documentatioin
for driver development (subject to NDA if required) to any party that seeks to
develop a driver for an existing or future PSIM project. Support for the SDK
including training will be available at commercial rates.
PRYSM SOFTWARE
LIAM HEATLEY
34
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
List of Maintream PSIM Features :
Integration of different security systems manufacturers
Alarms management
Standard Operating Procedures
Unified management of different manufacturers
Open architecture
Easy geolocalisation of events and navigation of sites and security assets on
custom maps
SOP’s & Incident management for security operators
Audit trail of all user actions
Scalable for multi site / national infrastructure projects
Redundancy back up with automatic failover
Video analytics supported natvely as well as through external systems
Roles based custom GUI for operators based on security levels
Escalation of alarms to senior operator
Automatically send SMS and email of events
Manual log events seen on cctv
Live camera display in PSIM video wall for different VMS or camera sources
Support different VMS/NVR SDK’s as well as ONVIF and MJPEG streams
Camera PTZ through PSIM interface or in CCTV window
Manage dome cameras preset positions from PSIM GUI
Show dome camera preset positions in PSIM GUI
Show dome camera true positions in PSIM GUI (where available from the VMS
or camera)
Receive motion detection alarms and provide next step procedures to
operators
Receive alarms from any other connected alarm system as the trigger to push
nearest CCTV camera to video wall, and provide next step procedures to
operators
Use the video stream from the VMS as the source for video analytics either
within the PSIM or fed to the PSIM from the analytics system
Receive alarm events related to any other connected systems fed into the
VMS (analytics for example)
Retrieve camera playback from the VMS directly into the PSIM unified smart
wall
Create instant icons on PSIM GUI as markers or hotspots that instantly retrieve
the playback the preceeds the creation of the marker.
Display lost camera signal
Provide distributed architecture of access to video to different locations, and
operators based on roles and responsibilities (user profiles)
Provide standard operating procedures “prompts” to guide operators in
security alarm events.
PRYSM SOFTWARE
LIAM HEATLEY
35
Open Architecture Video Surveillance
AppVision Physical Security
Integration Manager
Messaging – provide a method for operators to log important messages or
information instantly and send them to senior staff or maintenance teams
Provide full logs of operators actions and audits of past events.
Escalate difficult events automatically or manually to other more senior
operators
Video Black Box server – a full audit of what the operators are seeing in the
video wall at all times, with network access, configurable time delays for
screen recording, search by time and image export
Maintenance module for connected systems
PRYSM SOFTWARE
LIAM HEATLEY
36