Integrating Lynx Systems as Part of Your NFPA 72^® Solution

Emergency Communications Systems (ECS)

ECS – Chapter 24 of the NFPA 72® covers Emergency Communications Systems (ECS).

24.5.16 Visual Notification

• 24.5.16.1 Where audible notification is provided, mass notification systems shall also provide visual notification information to serve the deaf or hard of hearing and for high noise areas
• 24.5.16.2 The visual notification required by 24.16.1 shall be accomplished using visual notification appliances.
• 24.5.16.3 In addition to the visual notification appliances required by 24.16.2, textual, graphic, or video displays shall be permitted.
• 24.5.16.4 Transmission of visual notification and messages shall be simultaneous to audible notification and messages.

The LynxNetMessenger HDMI interface, LynxStrobe light, LynxLED sign, and LynxMessenger Popups are ideal solutions for visual notifications.

24.5.18 Textual and Graphical Visual Appliances

• 24.5.18.1 Textual and graphical visual notifications appliances shall be permitted to be used for primary or supplemental notification.

The LynxNetMessenger HDMI interface, LynxLED sign, and LynxMessenger Popups are ideal examples of textual and graphical visual notifications.

24.5.20* Video Alerting

• Video display systems that provide alerts and messages to video appliances shall be permitted to be used to supplement mass notification.

The LynxNetMessenger HDMI interface can turn any HDMI monitor into a video alerting system. The LynxNetMessenger passes through any HDMI source until and alert is activated. Then, the LynxNetMessenger switches the source to a Lynx alarm.

24.5.22 Interfaces

• Any abnormal condition that would prevent reliable emergency operation of any interfaced systems shall be announced both audibly and visibly as a trouble signal at the affected control locations.

All Lynx hardware and software devices are fully supervised. Supervision alarms can be sent to any Lynx output devices.

24.7* Distributed Recipient Mass Notification Systems (DRMNS).

24.7.1* Overview

• Distributed recipient mass notification systems (DRMNS) shall not be used in lieu of required audible and visual alerting mass notification systems but shall be integrated with mass notification systems wherever possible.

Lynx hardwired input boxes and network APIs make it easy to add an additional layer of notifications to any existing system.

24.7.2* Targeted Recipients.

• The DRMNS shall be capable of sending alert messages to target individuals.

24.7.5* Delivery Methods.

• The DRMNS shall be capable of sending alert messages to end users (recipients) via multiple delivery methods.
• LynxMessenger popups, SMS text messages, VIOP, traditional phone dialing, email, and Lynx Alerts app push notifications can be sent to targeted individuals.

24.11.1* Emergency Command Center for Emergency Communications Systems.

24.11.6* Other Systems.

• The Emergency Command Center shall be capable of interfacing with and controlling other notification systems, such as telephone dialers, tone alert systems, computer network alerting systems, pagers, facsimile machines, textual devices, and other visual control signs, as determined by the emergency response plan.

Lynx hardwired input boxes and network APIs make it easy to add an additional layer of notifications to any existing emergency command center.

24.11.7 Inspection, Testing, and Maintenance.

• Inspection, testing, and maintenance shall be performed on a periodic basis, as described in chapter 14, to verify and ensure proper system operation and readiness.

The LynxClient software has a monthly and impromptu test feature, making it easy to test 20 or 20,000 software panic buttons. A report is generated that lists all the passes, failures, and untested machines. The Lynx hardware has a test mode that can be enabled from the web interface, so the administrator doesn’t even need to leave his office to let the end user test their hardware.