Reference · built on requestOperator by FibricSafety, security & compliance

Sprinkler Impairment

Tracks sprinkler valve tamper and supervisory signals against open work orders. Proposes impairment records, fire watch and notices.

Request accessPricing ↗

About

A closed control valve, low air pressure on a dry system, a pump in manual: each raises a supervisory signal at the fire panel or the building platform, and each is an impairment that NFPA 25 expects to be recorded, tagged, and told to the people who need to know. Sprinkler Impairment reads those supervisory and tamper signals from your building platform or over BACnet, and reads the open work orders on the sprinkler system in your CMMS.

A signal with a matching work order is planned work; the operator proposes the impairment record with its start, scope and expected end. A signal with no work order is proposed as an emergency impairment with a fire watch. Notices to the contacts you list are drafted, not sent.

This is a reference listing. It documents what Fibric would read from Sprinkler Impairment 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

  • Valve tamper, low air pressure, low water pressure, pump running and pump trouble supervisory points, over BACnet or through Metasys, Desigo CC, or Niagara
  • Waterflow alarm points, to tell an impairment from a discharge
  • Open and scheduled work orders on sprinkler assets in MaintainX or UpKeep, with planned start and end
  • Existing impairment records, so a signal already covered is extended rather than duplicated
  • Restoration: the supervisory point returning to normal and the work order closing

Proposed actions

  • Target capability: propose an impairment record in your CMMS with system, start time, scope, reason and expected restoration, for the facilities lead to approve
  • Target capability: propose a fire watch assignment when a supervisory signal has no matching work order or outlasts the planned window
  • Target capability: propose notices to the contacts you list, such as the insurer, monitoring company and fire department, as drafts a person sends
  • Target capability: propose closing the impairment record when the point restores and the work order is complete, with the restoration time
  • Target capability: propose a monthly list of impairments by system, duration and cause

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

What you can build

  • Record a planned valve shutdown properly

    A MaintainX work order closes a sectional valve for a tenant fit-out. When the tamper signal appears in Metasys, the operator proposes the impairment record with the work order's window and the draft notices for Teams.

    With MaintainX, Johnson Metasys, Microsoft Teams

  • Put a fire watch on an unplanned closure

    A tamper supervisory over BACnet with no open UpKeep work order is proposed as an emergency impairment, with a fire watch assignment posted to Slack for the shift lead to accept.

    With BACnet / IP, Slack, UpKeep

  • Close the record when the system is back

    The low air signal on the dry system in Niagara returns to normal and the compressor work order in MaintainX closes. The operator proposes closing the impairment with the restoration time and a notice to the same contacts.

    With Tridium Niagara, MaintainX

Requirements

  • A building platform or BACnet/IP connector with the sprinkler supervisory points on its read list, such as Johnson Metasys, Siemens Desigo CC, or Tridium Niagara
  • A CMMS connector with the sprinkler assets and their work orders, such as MaintainX or UpKeep
  • A messaging connector for fire watch and notices, such as Microsoft Teams or Slack
  • The contact list per site for impairment notices, and the fire watch roster
Authentication
Sprinkler Impairment holds no credentials. Supervisory points, work orders and messaging are reached through the connectors you have connected, and every record, watch and notice is a proposal a person approves.

Limits

  • It reads supervisory signals as the panel or building platform exposes them. Panels with no gateway or platform integration are not seen.
  • It is not the alarm monitoring path. Alarm signals still reach the monitoring company by their own route.
  • Notices are drafted only. Who must be told is set by your authority having jurisdiction and insurer; the operator follows the list you enter.
  • It never silences, acknowledges, or resets a signal, and never commands a valve or pump.

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 Sprinkler Impairment ↗

Questions and answers

Who approves an impairment record?
The facilities lead or fire protection contact you name. They see the signal, the matching work order if any, the proposed scope and window, and the draft notices. They approve, adjust the scope, or reject it.
Are the notices sent automatically?
No. Each notice is drafted to the contacts on your list and sent by a person. The operator records who sent it and when, so the impairment record shows the notice trail.
What does the impairment record contain?
System and valve, start and restoration times, planned or emergency, the work order, the fire watch assignment if any, the notices and who sent them, and who approved each step. It is the record NFPA 25 asks you to keep.
Ask about Sprinkler Impairment

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