Demand control ventilation is meant to open the outdoor-air damper as a room fills and ease it back as the room empties. In practice a CO2 sensor drifts, a damper minimum is set by hand at commissioning, and a conference room runs at its Monday setting all week. CO2 Ventilation reads zone CO2 from the building management platform over BACnet/IP or from LoRaWAN sensors, sets it against each air handler's outdoor-air damper command and position, and checks the outdoor reading from the nearest AirNow or OpenAQ monitor.
When a zone sits high in CO2 with the damper at minimum, or low with the damper wide open, it proposes a damper minimum or a ventilation setpoint change that stays at or above the design minimum in your sequence. You approve it. It never moves a damper itself.
This is a reference listing. It documents what Fibric would read from CO2 Ventilation 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
Zone CO2 in parts per million from analog input objects over BACnet/IP, with each object's status flags and reliability
CO2 uplinks from LoRaWAN sensors on your network server, or co2 events from Disruptive Technologies sensors sent at each heartbeat
Outdoor-air damper command and position feedback on each air handler, and the ventilation or DCV setpoint where the controller exposes it
Supply fan run state and the occupied or unoccupied mode of each zone, so a high reading in an empty room is judged differently
Outdoor ozone and PM2.5 from the nearest AirNow or OpenAQ monitor, since more outdoor air is not always cleaner air
The design minimum outdoor-air rate you record for each zone, which no proposal may go below
Proposed actions
Target capability: propose raising the damper minimum or the ventilation setpoint for a zone whose CO2 stays high while the damper sits at minimum
Target capability: propose easing a damper held wide open while the zone reads low and outdoor air is poor, never below the design minimum
Target capability: propose a sensor check when a zone's CO2 reads flat for days, or disagrees with a neighbouring zone on the same air handler
Target capability: propose a schedule change where a zone's CO2 rises before its occupied mode starts, or falls long before it ends
Target capability: propose a notice to your facilities channel when outdoor PM2.5 is high and a damper is open, for a person to decide
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Find conference rooms stuck at minimum outdoor air
Zone CO2 over BACnet/IP climbs through every meeting while the damper command stays at its minimum. The operator proposes a higher minimum for that zone, with the CO2 series attached, for your controls technician to approve.
Battery LoRaWAN CO2 sensors in classrooms report through your network server. The operator pairs each sensor with its air handler in Niagara and proposes ventilation setpoint changes where readings and damper position disagree.
When the nearest AirNow monitor reports high PM2.5, the operator proposes a notice for every damper commanded above its minimum, so a person decides whether to ease it before more smoke comes in.
A building management platform connector over BACnet/IP, or a Niagara, Metasys, or Desigo CC connector, with read access to zone CO2, damper, and setpoint points
LoRaWAN CO2 sensors on a network server the LoRaWAN connector can read, for zones the building platform does not measure
The Air Quality signal with each site's location, so the nearest outdoor monitor can be chosen
The design minimum outdoor-air rate for each zone, from the mechanical drawings or the commissioning report
Authentication
Reads CO2, damper, and setpoint points through the read allow-list of your BACnet/IP or building platform connector, reads sensor uplinks through your network server's scoped API key, and reads AirNow and OpenAQ with their free keys.
Limits
It works from CO2 as a proxy for occupancy. Zones with no CO2 sensor, or a sensor mounted in a return duct, get fewer checks.
No proposal goes below the design minimum you record. It does not compute that minimum from ASHRAE 62.1; an engineer supplies it.
It proposes setpoint and minimum changes. It does not write to a damper, override a sequence, or change a fan speed.
Outdoor readings come from the nearest public monitor, which may be some distance from the intake. A disagreement is flagged, not resolved.
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.
Each setpoint, damper-minimum, schedule, and sensor-check proposal. You see the zone, the CO2 and damper readings behind it, the outdoor reading, the design minimum on record, and the exact value proposed. Approve, edit the value, or dismiss.
What record is left?
A receipt per proposal: the readings used, the design minimum it was checked against, the value before and after, who approved it, and how to restore the previous value. Dismissed proposals are kept with the reason given.
Will it ever move a damper or change a setpoint on its own?
No. It reads points and writes nothing without an approval. An approved change is sent once through the building connector, and only to points that connector allows. A proposal below the recorded design minimum is never raised.
Ask about CO2 Ventilation
Ask about the capabilities and requirements in this listing.
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