Why use Lux Intelligent Cloud Monitoring?

The Lux Intelligent cloud monitoring service allows you to setup and forget your emergency lighting test panels, as you can access all of your emergency lighting fault status and test history on your mobile device or via a web browser.

By using the Lux Intelligent cloud monitoring service you will benefit from:

  • Access status and test history without going to the panel or logger PC.  
  • Receive fault status information quicker, i.e. immediately rather than the next time data is extracted from the logger PC
  • Save manpower collating data and creating reports.
  • Pull all emergency light testing data into one point, even from panels which are geographically spread out.
  • View fault status for the entire network, or individual panels, and generate maintenance reports which are emailed directly to your service engineers containing the device details and fault status.
  • Monitoring of all sites in portfolio, anywhere in the world
  • Easily add/remove sites, networks or panels to your portfolio
  • Share specific sites, networks or panels with colleagues or maintenance partners
  • Live system status from site to device, showing faults, advisories, test and maintenance reports
  • Easily interrogate entire system from site to device
  • 'Any level' test and maintenance report generation from site to device level
  • Data safely stored in the cloud allowing historical reports to be instantly generated based on actual test data
  • Lux Intelligent Cloud and app requires the Lux Intelligent PC Tool, serial-ip converter supplied separately and Lux Intelligent Cloud subscription

Cloud Monitoring Hierarchy

Lux Intelligent has been designed to be simple and intuitive to use for customers monitoring a single panel network, right through to facilities management companies monitoring panels at multiple sites at locations across a wide geographical area.

We have created a standard hierarchy model, onto which customers map their physical emergency lighting test network.  The terminology in this hierarchy is:

  • Device - An emergency luminaire
  • Loop - A data loop with up to 249 devices attached
  • Panel - The emergency lighting test panel, with up to 4 loops
  • Site - A collection of Panels.  A site can represent a number of buildings, but typically customers use Site to represent a building, which in turn has a Panel per floor.
  • Monitoring PC - The PC on which the Logger Tool and Sync Tool are installed.  The Site and Panel names are configured within the Logger Tool on the monitoring PC.  Giving the PC a name helps identify it on a network where there may be multiple monitoring PCs operating at a Location.
  • Location - Used to represent a geographical location, and groups a number of Monitoring PCs.  On smaller networks, there may be only one location, but on larger networks the area may be split up into locations, i.e. a University split up into Campus, or when used in the context of a Facilities Management company Locations may represent Client 1, Client 2, Client 3...

Example Network 1 - University of Life

The diagram below shows a network for a customer monitoring an emergency lighting installation at a fictitious university.  The network has been split up into 2 Locations (North and West Campus), with those locations in turn divided into Sub campus or residential monitoring PCs, and in turn, the Site-level is used to represent Buildings.

Lux Intelligent Cloud Network Single Customer Model

Example Network 2 - Facilities Management Company

The following diagram shows a network of clients which are monitored by the facilities management company.  The individual clients have different network structures, but they are easily mapped to the Lux Intelligent cloud hierarchy model.  All of the data from the disparate client locations are amalgamated into the facilities management companies account, and so can be viewed at a top level, but also drilled down to a specific device at fault with only a few clicks within the mobile app or web browser app.

Emergency Lighting Hierarchy Explaination Diagram