Reference · built on requestOperator by FibricFacilities & comfort

Filter Change

Watches filter pressure drop and fan run hours and proposes replacement work orders before airflow falls.

Request accessPricing ↗

About

A loaded filter raises the resistance across the bank. The fan works harder to hold airflow, or airflow falls and the zones behind it drift. Filter Change reads the differential pressure across each filter bank and the supply fan's status and run hours over BACnet/IP, and compares the pressure with the final resistance you set for that filter.

As a bank approaches its limit, it proposes a replacement work order in your CMMS with the pressure trend attached, and checks that the filters are in stock. If they are not, it proposes the purchase order. Where units come due in the same week, it proposes one visit. You approve each order.

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

  • Differential pressure across each filter bank, read as an analog input over BACnet/IP, with its Status_Flags and Reliability
  • Supply fan status and run-hours accumulators on each air handler, or fan run state where no counter exists
  • Fan speed command on units with a variable-speed drive, so a rising speed at constant airflow is seen as loading
  • Open work orders and scheduled maintenance for the same asset in Fiix, UpKeep, MaintainX, or Limble
  • Filter part numbers, sizes, and quantities on hand in the CMMS parts list or in inFlow Inventory or Zoho Inventory
  • The initial and final resistance for each filter type, from the filter maker's data you enter per air handler

Proposed actions

  • Target capability: propose a replacement work order in your CMMS when a bank nears its final resistance, with the pressure trend attached
  • Target capability: propose a meter reading of fan run hours against the air handler asset in the CMMS
  • Target capability: propose a purchase order or a stock reservation when on-hand filters fall short of the replacements due this month
  • Target capability: propose grouping air handlers due in the same week into one work order, so a technician makes one round
  • Target capability: propose a sensor check when the pressure reading sits flat while the fan runs, or its Reliability reports a fault

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

What you can build

  • Replace on pressure, not on the calendar

    A bank on a dusty loading dock loads faster than the quarterly plan. The pressure trend crosses the threshold early, and Filter Change proposes a Fiix work order with the trend, weeks before the scheduled visit.

    With BACnet / IP, Fiix

  • Order filters before the visit

    Several air handlers come due in the same week. The operator checks inFlow Inventory, finds a size short, proposes the purchase order, and proposes a single MaintainX work order for the round.

    With Tridium Niagara, MaintainX, inFlow Inventory

  • Catch a sensor, not a filter

    The pressure on one unit has read the same value for a month while the fan ran. Rather than a filter order, the operator proposes an UpKeep work order to check the pressure transmitter.

    With BACnet / IP, UpKeep

  • Keep run hours in the CMMS

    Fan run hours read from the controller are proposed as meter readings on the Limble asset, so preventive tasks on the air handler run on hours, not guesses.

    With Limble CMMS

Requirements

  • A BACnet/IP connector with a differential pressure point across each filter bank and the supply fan status point on its allow-list
  • One CMMS connector: Fiix, UpKeep, MaintainX, or Limble CMMS, with the air handlers as assets
  • A parts list with filter part numbers per air handler, in the CMMS or in an inventory connector such as inFlow Inventory
  • The final resistance per filter type, taken from the filter maker's data
Authentication
Filter Change carries no credentials. It reads pressure and fan points through your BACnet/IP connector and writes work orders, readings, and purchase orders through the CMMS or inventory connector under that connector's scopes.

Limits

  • It needs a pressure sensor across the bank. An air handler with no differential pressure point is judged on run hours alone.
  • The final resistance comes from the filter maker's data you enter. The operator does not decide when a filter is spent.
  • Stock counts are as current as the CMMS or inventory system. A part consumed but not logged still shows as available.
  • It proposes work orders, readings, and orders. It does not change fan speed, setpoints, or alarm limits.

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 Filter Change ↗

Questions and answers

Who approves a filter order?
Each work order, meter reading, and purchase order. The proposal shows the unit, the current and final resistance, the fan hours, the filters needed, and what is on hand. Approve it, change the date or quantity, or dismiss it. A dismissed unit is proposed again only when its pressure rises further.
What record does a replacement leave?
A receipt for every proposal: the pressure trend, the threshold used, the stock check, who approved, and what was written to the CMMS or inventory system. Closed work orders keep the readings that triggered them, so the next interval can be judged from data.
What will it not do without approval?
It never files an order, places a purchase, or edits a controller without approval. It does not change fan speed or setpoints, and it does not mark a filter as changed; the technician closes the work order and the pressure reading confirms it.
Ask about Filter Change

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