We understand that our systems are at the core of your infrastructure, and that they must run consistently and with resilience, providing robust performance that can be relied on. That's why we have designed every component of our system to take this into account; it's an obligation we take very seriously.
To start, configuration and trend data in each system is backed up weekly, independent of any other backups your network administrators may have implemented. But more importantly, the system's performance doesn't rely at all on this data; rather, it constantly profiles its configuration and environment and can dynamically and quickly rebuilds databases when needed.
The system also includes powerful failsafe protection for unforeseen instances. Should there ever be a signal loss, all cooling units will be turned on to their maximum and alert messages distributed. For some period of time this might use more cooling than necessary, but over-temperature situations will be avoided. And each system can be manually overridden, for those times, if ever, that you want to control the system yourself.
Security is an important part of every Vigilent system. The servers are built upon open source code that has been extensively scrutinized in the public domain. The administration console can be accessed from a web browser, but is designed to run only within the firewall; all communications through the portal are password protected, and utilize web authentication.
Sensor nodes are also designed to run inside the firewall, and utilize authentication with 128-bit encryption. In addition, they are designed for a low-power environment, which means their signals cannot travel far. Furthermore, they utilize frequency hopping, which makes locking onto a signal hard to accomplish, and temporary.

Deploying a Vigilent system is straightforward and fast. Its mesh-based network sensors can be added almost anywhere, and the network automatically configures itself for each ne node. Servers are "boot-and-run"; turning the system on launches an auto-configuration application.
Vigilent systems are designed to grow with your needs and deployment goals. You can start as small as you need and expand or grow over time. The system is insensitive to the square footage covered, and the network can easily be extended with mesh-based sensors that are easy to add; the network dynamically reconfigures itself to match configuration updates.
The AI engine is independent of the network or physical configuration, building a cause-and-effect map that doesn't care about where nodes are located or how a building is laid out, but rather determines the input-output relationships of all network elements. This means that the Vigilent system or service you buy today can grow and adapt to your evolving needs.
Firewall – Network technology that filters traffic to a device or subnet, blocking access of unauthorized requests while permitting authorized communications to be transmitted.
Commissioning – A start-up process of assuring that all of the components of a Vigilent system are installed, tested and operated according to design goals, and the site profiled by the AI engine.
Open Source Software – At once both a method and a philosophy governing a transparent, collaborative and community-based development approach for computer software.
The failsafe protections in Vigilent systems provide multiple levels of assurance that your site will be protected. If a signal loss from sensors or controllers is ever detected, alert messages are rapidly dispatched and cooling units are throttled to their maximum to avoid over-temperature situations.