This solution is the premier solution that provides remote monitoring and management through the OneVue cloud-based application. Unique to this solution, all devices connect to OneVue over an Ethernet network to send their current status to and download settings from OneVue.
Site Survey completed by Primex: the first step to ensure system coverage. A Primex engineer analyzes the facility to provide recommended device install locations.
Pre-Install Requirements form submitted to Primex: completed form must be submitted to Primex prior to installation. Failure to meet these requirements or not providing complete and accurate information may affect system coverage and result in installation delays and additional costs.
Critical Notification Event input source identified: either by a Critical Notification Panel or integration with third-party system. Hardwired cable length between Transmitter and input source cannot exceed 1000 ft. (304.8 m).
OneVue configuration requirements gathered: includes Critical Notification events (default presets or customization), InfoBoard naming convention, display settings (InfoBoard Groups), Users, Alert Rules, Reports, and NTP Servers.
OneVue network requirements met: details the network port and firewall requirements that allow Primex network devices to communicate over a facility's network to OneVue. Commonly verified with IT staff.
Ethernet connection available at each device install location: to allow devices' connection to OneVue, all devices must be connected to an Ethernet network at their install location. InfoBoards can connect to a PoE network or an Ethernet network if powered by AC power.
To avoid system disruption during a power outage, use of an external backup supply for all PoE switches or an emergency generator for AC power is strongly recommended by Primex, especially for circumstances involving Critical Notifications during an emergency.
When installing a new system or adding new devices, learn about what should be considered to ensure a seamless installation.
GPS time source
GPS Receiver needs to “see” three satellites in the sky above before it will send a time signal to the Transmitter. If the GPS Receiver has a 360° view of the sky, the process may take only 15 minutes or as many as several hours. The length of time is dependent on the location (if the unit does not have a full view of the sky, due to wall or window installations, building “shadows”, etc.) weather conditions (clear or overcast) time of day, and other similar environmental factors.
NTP time source
If the Transmitter is receiving its time source from the optional NTP configuration, it sends requests to the NTP server at defined intervals.
The Transmitter does not transmit time data until it has received valid time information from a time source. Once the Transmitter receives a time signal, the Transmitter sets its internal clock to the received time. The Transmitter then begins to transmit its internal time once every second. The Transmitter continually monitors its time source connection and updates its internal clock with the time data it receives.
If installing devices after a Transmitter's initial 8 hour power-on, there are three options to ensure a device receives a time update during installation.
Install devices between 39 minutes past the hour and 6 minutes after the next hour and devices receive a time update when powered on. For example, between 9:40 AM and 10:05 AM.
Install the devices at any time of the day. Devices will receive a time update at the next 39 minutes after the hour.
Power-cycle the Transmitter. It will then transmit for 8 consecutive hours and devices receive a time update when powered on.
When an InfoBoard is powered on it automatically initializes its setup and searches for a time signal from a Transmitter.
When receiving time from a Transmitter, an InfoBoard's receiver turns on to search for a time signal every 10 minutes on the 5's (5, 15, 25, 35, 45, 55 minutes) of the hour.
When configured to receive time from a NTP time source, an InfoBoard connects daily, at a system scheduled time, to a NTP server to receive a time update.
Installation must be completed in the order detailed below.
Install external components.
GPS Receiver and external antenna.
Mount Transmitter and establish connections.
Antenna, GPS, Ethernet, and AC power.
Configure Transmitter with ODC app.
Transmitter primary settings configured and device is added to OneVue.
Wire Transmitter Contact Closure Terminal Block.
Dependent event input source; either Critical Notification Panel or third-party system.
It's recommended to test a Critical Notification Event during this step with a configured and operating InfoBoard. Validate each of the five events are successfully activated and displayed on the InfoBoard.
Configure each InfoBoard with ODC app.
During configuration, each InfoBoard is added to OneVue.
Validate signal coverage at each planned InfoBoard install location.
Prior to installing InfoBoards, verify at each location there is adequate signal coverage using an ICOM IC-R6 Handheld Communications Receiver.
If signal coverage is not adequate and device relocation is required, install cabling as needed at final install location.
Trigger a critical notification event and visually validate each InfoBoard displays the event. Once completed, initiate an All Clear event, visually validate the event is displayed. After the All Clear event has ended (default 5 minutes), verify the InfoBoards returned to displaying synchronized time.
Verify each Transmitter and InfoBoard has checked-in to OneVue.
During the ODC app configuration, the devices were added to OneVue. This step verifies the devices established a network connection and checked-in to OneVue.
Complete OneVue configuration.
Account time synchronization settings: verify Time Zone and NTP servers (if applicable).
InfoBoard Groups: each InfoBoard is assigned to an InfoBoard Group. An InfoBoard Group sets the display settings and general message for all of its assigned InfoBoards. By default, each InfoBoard is assigned to the Default InfoBoard Group.
Users: add users and assign their Roles and Device Classes.
Alert Rule: create an Alert Rule and add Transmitters. Alert Types include Unresponsive, Time Sync Failure, and Critical Error.
Reports: create reports. Report types include Transmitter Warning-Alarm State Report, Clocks-InfoBoard Warning State Report, Critical Notification Event History Report, User Report, User Role Report, and User Alert Rule Report. The School Calendar Report and School Schedule reports apply to InfoBoard scheduled countdown timer use.