Reference · built on requestOperator by FibricFacilities & comfort

After-Hours Audit

Finds air handlers and zones running outside occupied hours and proposes schedule corrections backed by badge events and holidays.

Request accessPricing ↗

About

Air handlers run at night because a schedule was extended for one event and never put back, because a holiday was not in the calendar, or because a unit was left in hand. After-Hours Audit reads fan status and zone occupancy mode from your controllers over BACnet/IP, the schedules that govern them, badge events from your access control platform, and public holidays for the country the site is in.

Each morning it lists the equipment that ran after the last badge event of the previous evening, or on a holiday, and for how long. Where a schedule is the cause, it proposes the correction within the bounds you set. Where people were badged in, it proposes nothing. You approve every schedule change.

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

  • Supply fan status, run command, and zone occupancy mode on each controller over BACnet/IP, timestamped as the values change
  • Schedules and their current effective state, read through Metasys, Niagara, or Carrier i-Vu where your platform exposes them
  • Credential use from your access control platform: who badged which door and when, and door state events after hours
  • Public holidays for the site's country and subdivision from the Nager.Date holidays endpoint, by year
  • Manual overrides held on fan or occupancy points, where the platform reports a priority array or an operator command
  • Zone temperatures during the after-hours run, so a unit kept on for a reason such as a server room is not proposed for a cut

Proposed actions

  • Target capability: propose shortening an air handler's schedule to the last regular badge-out time, within the bounds you set, for your approval
  • Target capability: propose adding a holiday exception to a schedule when the site was closed and the equipment ran anyway
  • Target capability: propose releasing a manual override that keeps a fan running past its schedule, where the platform allows it
  • Target capability: propose a weekly summary of after-hours run time by air handler and zone, with the badge evidence beside each line
  • Target capability: propose a keep-on exception for equipment that serves spaces badged into after hours, so it is not flagged again

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

What you can build

  • Put a schedule back after an event

    A schedule was extended for a late function and left that way. After-Hours Audit sees the fan running nightly with no badge activity after closing, and proposes the Niagara schedule return to its normal end time.

    With Tridium Niagara, Access Control, Holidays & FX Reference

  • Catch the holiday nobody scheduled

    The holidays feed shows a public holiday, Verkada shows no entries, and BACnet/IP shows every air handler on its weekday schedule. The operator proposes a holiday exception for each schedule before the next one.

    With BACnet / IP, Verkada, Holidays & FX Reference

  • Prove that a night run was needed

    Badge events show a facilities crew on site until midnight. The Metasys fan run is matched to the badges, listed as justified, and no change is proposed.

    With Johnson Metasys, Access Control

Requirements

  • A BACnet/IP connector with the fan status, run command, and occupancy points of each air handler and zone on its read allow-list
  • A building platform connector that exposes schedules and allows schedule changes within bounds, such as Johnson Metasys, Tridium Niagara, or Carrier i-Vu
  • An access control connector that reports credential use with door and time, such as your access control platform or Verkada
  • The country and, where relevant, the subdivision of each site, for the holidays feed
Authentication
After-Hours Audit uses no credentials of its own. It reads controllers, schedules, badge events, and holidays through the connectors you have connected, and proposes schedule changes through the same building platform connector.

Limits

  • Sites without exit readers show the last badge-in, not a badge-out. The operator treats the last event as the last known presence.
  • Schedule changes are proposals, applied only through a platform connector that allows them, within the bounds you set per schedule.
  • The holidays feed carries national and subdivision holidays. Company closures and site-specific days off are entered by you.
  • It does not switch equipment off. A unit found running is reported and its schedule proposed for change; nothing stops until a person acts.

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 After-Hours Audit ↗

Questions and answers

What do you approve each morning?
Every schedule change and every override release. The proposal shows the unit, the hours it ran, the badge events or holiday that make the case, and the exact schedule entry that would change. Approve, edit the new time, or dismiss.
What is kept from each audit?
A receipt per proposal with the readings, the badge evidence, the holiday if any, who approved it, the schedule entry before and after, and how to restore it. The weekly summary is kept too, so you can show how after-hours run time changed.
Does it ever stop a unit on its own?
No. It reads fan status and badge events and proposes schedule corrections. A schedule changes only after approval, through the platform connector, within the bounds you set. It never commands a fan, and it never writes to units you mark as always-on.
Ask about After-Hours Audit

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