Graphics configuration

A graphic provides a visual display of an access control area, can simulate actions including: doors opening and closing, readers scanned, intrusion zones enabled, etc., report on current conditions, and include buttons for implementing area-wide controls, such as turning on video surveillance and triggering threat level actions. A graphical representation of reality enables operational personnel to respond quickly to threats in real time.

Target media

Prior to Niagara 4.9, no custom Px graphics ran in a browser (required by the web UI). Instead, they used the Java Web Start applet, which ran outside of the browser. The release of Niagara 4.9 replaced Web Start with Java Web Launcher for Px graphics that still require an external applet. Other Px graphics support HTML5, which runs in a browser.

The Graphic Editor supports two client-side, Px Target Media technologies:

HxPxMedia are designed for the web UI. Three widgets render in a browser using HTML5: LiveVideoPlayer, Control Panel and CameraWidget. The remaining widgets: PanTiltJoystick, ZoomSlider, MouseDownButton and VideoMultistreamPane require Web Launcher and render outside of the browser.
WorkbenchPxMedia are designed for the Workbench interface. When used in the web UI, all widgets require the Web Launcher (applet).

The Graphic Editor advises you if you use a feature in a widget that is not supported by the target technology.

Consider carefully the basic capabilities and limitations of each technology. Obviously, a mobile phone is limited as to what it can usably display when compared to a graphic viewed in a web browser running on a computer. Keep this in mind, and test your views in all target media as you develop them.

The Niagara Graphics Guide documents in detail the capabilities of Hx and Px graphics. The Niagara Video Framework Guide documents the videoDriver module and palette.

Summary steps

Configuring a graphical representation of a facility begins by hiring a graphics artist to create a set of three-dimensional images to represent the building, including all areas, such as the parking lot or garage, to be monitored. The images should be readily recognizable as belonging to the facility, looking down from above each floor.

Figure 5. A 3D image of a floor in a building

The screen capture shows an image of a single floor in a building with overlaid controls for visually monitoring access control.

The general process of creating presentation views for access control follows these general steps:

Create a view
Creating a view sets up a canvas on which to construct a representation of your facility. This view establishes a relationship between a Px file and one or more components of various types, such as folders, doors and readers.
Add widgets
A widget is a graphic visualization of an access component. You add widgets to the canvas.
Bind your data to the widgets
Data binding passes data collected from the access components to the widgets. These bound data objects animate (update) the widgets in real time.
Create a nav file
A .nav file sets up a customized tree structure so that users can easily access your views. You edit the .nav file using the Nav File Editor and assign a particular nav file to a user in the user’s profile (using the User Manager view).
Create and distribute a report
Reports display and deliver data to online views, printed pages, and for distribution via email.