Reference · built on requestOperator by FibricFacilities & comfort

Indoor Air

Watches indoor particulate, VOC, and humidity against outdoor air and smoke and proposes recirculation or filtration changes.

About

Indoor Air is for the days when the air outside is the problem. Wildfire smoke, a construction cut next door, or a humid week can push indoor PM2.5, VOC, and humidity past what the ventilation sequence assumes. The operator reads indoor monitors over MQTT or LoRaWAN, or from Kaiterra and Airthings devices, beside outdoor readings from the nearest OpenAQ or AirNow monitor, NASA FIRMS fire detections near each site, and the NOAA HMS smoke product.

When indoor readings track outdoor ones, it proposes what the EPA's guidance for commercial buildings describes: recirculation mode or a closed outdoor intake, a filter change to MERV 13 or the highest rating the unit can hold, and portable cleaners for the rooms that matter. You approve each step. It never sets a damper or a mode on its own.

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

  • PM2.5, PM10, TVOC, CO2, temperature, and humidity samples from indoor monitors, on MQTT topics, LoRaWAN uplinks, or the Kaiterra and Airthings APIs
  • Outdoor PM2.5, ozone, and AQI from the OpenAQ and AirNow monitors nearest each site, with the station each reading came from
  • Active fire detections from NASA FIRMS within a bounding box around each site, with confidence, radiative power, and acquisition time
  • Smoke plume analysis from the NOAA Hazard Mapping System, so a site can be warned before its own sensors move
  • Air handler mode, outdoor-air damper position, and filter differential pressure over BACnet/IP, where those points exist
  • Per-topic freshness and device presence on the broker, so a silent indoor monitor is not mistaken for clean air

Proposed actions

  • Target capability: propose switching an air handler to recirculation or closing its outdoor intake while outdoor PM2.5 exceeds the threshold you set
  • Target capability: propose a filter work order to MERV 13, or the highest rating the unit's fan and slot accept, before a forecast smoke day
  • Target capability: propose portable air cleaners for the rooms whose indoor readings rise first, sized to the room, as an occupant notice
  • Target capability: propose returning the unit to its normal ventilation mode once indoor and outdoor readings fall below the threshold
  • Target capability: propose a humidity setpoint or dehumidification check when indoor humidity stays high while outdoor air is dry

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

What you can build

  • Close the intake before the smoke arrives

    FIRMS detections upwind and an HMS plume over the site come before the nearest AirNow monitor moves. The operator proposes recirculation mode for each air handler over BACnet/IP and a filter check, for your engineer to approve.

    With Wildfire Detection, NOAA HMS Fire and Smoke Product, BACnet / IP

  • Track a smoke day from the inside

    Kaiterra monitors on each floor report PM2.5. When indoor readings rise with outdoor ones, the operator proposes portable cleaners for the floors rising fastest, posted as a notice to your facilities channel.

    With Kaiterra, Air Quality, Microsoft Teams

  • Stage filters where the readings say to

    Filter differential pressure over BACnet/IP and indoor PM2.5 from MQTT monitors show which units are loading. The operator proposes MaintainX work orders for those units first, with both series attached.

    With BACnet / IP, MQTT Broker, MaintainX

Requirements

  • Indoor monitors reporting PM2.5 and humidity, through the MQTT Broker or LoRaWAN Network connector or a Kaiterra or Airthings connector
  • The Air Quality and Wildfire Detection signals, with a location for each site
  • A building management platform connector with the air handler mode and damper points on its list, for mode proposals
  • A CMMS or work-management connector for filter work orders, and a messaging connector for occupant notices
Authentication
Reads indoor monitors through your MQTT broker credentials, LoRaWAN network server key, or the vendor API each monitor connector holds; reads OpenAQ, AirNow, and FIRMS with their free keys; and sends mode and filter proposals through your building and CMMS connectors.

Limits

  • Indoor monitors report the room they sit in. One by the door reads differently from one at a desk; the operator does not average them.
  • It proposes modes and filters. It never commands a damper, fan, or mode, nor judges whether a fan can carry a MERV 13 filter.
  • FIRMS detections are satellite passes, not smoke at your intake. The operator pairs them with HMS and outdoor monitors before it proposes anything.
  • The nearest public monitor may be many kilometres away. Where a site has no outdoor monitor of its own, the proposal says so.

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 Indoor Air ↗

Questions and answers

What does a person approve?
Each mode change, filter work order, occupant notice, and return to normal. The proposal shows the indoor and outdoor readings, the fire and smoke evidence, the unit affected, and the exact change. Approve, edit, or dismiss it.
What record is left?
A receipt per proposal, approved or not: the readings and detections it cited, the mode or filter before and after, who approved it, when it went to the building or CMMS connector, and how to reverse it.
What will it never do on its own?
It never changes a mode, a damper, a setpoint, or a filter, and never sends an occupant notice, without an approval. It reads monitors and public feeds and waits.
Ask about Indoor Air

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.