The Elements OnGuard Connector® facilitates local security control of the site while supporting centralized management and monitoring. So corporate systems have the flexibility to run OnGuard on-premises at their headquarters while satellite offices or branches are secured by Elements.

Customers running OnGuard who want to deploy security at remote sites may choose to connect Elements:

  • If there is no established network between corporate and remote sites, but an internet connection is available.
  • When they want a quick and easy deployment option with reduced overhead, costs, and system complexity.
  • To provide a level of autonomy to the remote sites with managing daily activities through a streamlined, easy-to-use interface while transferring pre-existing cardholders to Elements and then having Elements events flow back to OnGuard.

Architecture

Architecture diagram

Callout

Description

1

The Connector runs in the OnGuard environment. Internet access is required to allow OnGuard to communicate with the OpenAccess server and Elements.

2

Using a supported web browser, manage the Connector from the Lenel Console.

3

Cardholders and credentials are transferred from OnGuard to Elements on a default or user-defined schedule.

As scheduled, the Connector ensures that remotely managed cardholders and credentials in Elements match per the rules defined in the Connector. If a cardholder or credential should be available in Elements and it is not, then the Connector adds it. If a cardholder or credential should not be available in Elements and it is, then the Connector removes it.

4

Events are pulled from Elements into OnGuard. All events are pulled in and sent into OnGuard via the OpenAccess API. The event type and event ID originating in Elements are sent to OnGuard via the OpenAccess API, mapped to existing OnGuard events where appropriate. Elements events without a corresponding OnGuard event are sent as a generic event.

Prerequisites

The Connector is built on the OpenAccess platform. Before using the Connector,

  • Make sure the LS Message Broker service is installed and running on the OnGuard server.
  • Make sure the LS OpenAccess service is installed and running on the OnGuard server.
  • The administrator needs an OpenAccess account and password.
  • The administrator needs a database account and password.

Download the Elements OnGuard Connector Administration Guide PDF.

Configuration

Configuration for the Connector is done on the System Options page in the customer portal and in the Lenel Console.

  1. Download the Elements OnGuard Connector.

  2. Install the Connector according to the Administration Guide provided with the download.

  3. In Elements, on the Marketplace page under OnGuard Connector in the customer portal, generate an Elements key to be used.
  4. Launch the Lenel Console and select the Elements Connector card.
  5. On the Sites page, configure a new site by adding the key that was generated in Elements. Once configured, details of the Elements system can be viewed.
  6. On the Cardholders page, configure a transfer of cardholders and credentials from the OnGuard system to the Elements system.
  7. The server running the Elements Connector service must be able to communicate outbound to:
    • remotemanagementservice.elementssecure.com:443
    • lenelpilot.b2clogin.com:443
    • portal.elementssecure.com:443


Training videos:




© Carrier. All Rights Reserved.