Reference · built on requestOperator by FibricSafety, security & compliance

Fire Panel Trouble

Groups fire alarm panel trouble and supervisory events by device and cause. Proposes service tickets with priority and history.

Request accessPricing ↗

About

A fire alarm panel raises trouble signals for a ground fault, an open loop, a low battery, a lost communicator, and many other things that are not fires but are not nothing. They print at the panel, scroll on the building platform, and are cleared by whoever is standing there. Fire Panel Trouble reads trouble and supervisory events as your building platform or BACnet gateway exposes them, and groups them by device address and likely cause: one loop fault that trips a run of device troubles is one group.

For each group it proposes a service ticket with the device, the cause, the priority you have set for that class, and the history of the same device. A person files it. The events on the panel are never touched.

This is a reference listing. It documents what Fibric would read from Fire Panel Trouble and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Trouble and supervisory events from the fire panel, with device address and time, through a BACnet gateway or Desigo CC, Honeywell EBI, Metasys, or Niagara
  • Device identities: loop, address, type and location, from the building platform's object tree
  • Restoration events, so a trouble that clears on its own is recorded as transient rather than left open
  • Open and past service tickets for the panel and its devices in MaintainX or ServiceTitan
  • Acknowledgement and reset entries in the platform's audit log, to know who cleared what

Proposed actions

  • Target capability: propose one service ticket per group in MaintainX or ServiceTitan, with device, cause, priority and the device's history, for your approval
  • Target capability: propose a notice to the fire alarm service technician in Teams or Slack for classes you mark urgent, such as a communicator failure
  • Target capability: propose a repeat list of devices that trouble and restore more often than the threshold you set in the period
  • Target capability: propose a weekly panel health summary by panel and trouble class, with open tickets beside each line

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn a loop fault into one ticket

    A run of device troubles on one loop appears in Desigo CC within a minute. The operator groups them under the loop, proposes a MaintainX ticket naming the loop and the affected addresses, and attaches the loop's history.

    With Siemens Desigo CC, MaintainX

  • Chase a failing communicator the same hour

    A communicator trouble on the panel, read over BACnet, is a class you marked urgent. The operator proposes a ServiceTitan job and a Slack notice to the service technician with the panel and time.

    With BACnet / IP, ServiceTitan, Slack

  • Find the detector that troubles every night

    A smoke detector in Honeywell EBI raises and restores a trouble each evening. It appears on the repeat list with dates, so the ticket posted to Teams asks for replacement rather than another reset.

    With Honeywell EBI, Microsoft Teams

Requirements

  • A BACnet or building platform connector exposing the panel's trouble and supervisory events with device addresses, such as Desigo CC, Honeywell EBI, or Niagara
  • A CMMS or field service connector for service tickets, such as MaintainX or ServiceTitan
  • A messaging connector for technician notices, such as Microsoft Teams or Slack
  • Your priority per trouble class, and the threshold for the repeat list
Authentication
Fire Panel Trouble has no login to the panel or any platform. It reads events through the building platform or BACnet connector you have connected, and proposes tickets and notices through your CMMS and messaging connectors.

Limits

  • It sees what the gateway or platform exposes. A panel connected only to a printer or a dialer is not read.
  • Grouping is by device address and time. It names a likely cause; the technician confirms it on site.
  • It never acknowledges, silences, or resets an event on the panel, and never changes the panel's programming.
  • It is not a monitoring station and does not replace the communicator path to the monitoring company.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fire Panel Trouble ↗

Questions and answers

What does the person filing the ticket see?
The grouped events with device addresses and times, the likely cause, the proposed priority, the device's past tickets, and the ticket text. They approve it as written, change the priority or cause, or dismiss the group.
Does it touch the panel?
No. It reads events through the building platform or gateway. Acknowledging, silencing and resetting stay on the panel, done by a person. The operator records who did so where the platform's audit log shows it.
What history does a ticket carry?
Every earlier trouble and restoration for that device address in the period the platform serves, the tickets opened for it, and how they closed. A device with a pattern gets that pattern in the ticket.
Ask about Fire Panel Trouble

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy