Reference · built on requestOperator by FibricFacilities & comfort

Meeting Room Reset

Matches room bookings with measured occupancy and proposes standby setpoints, lights off, and a tidy between meetings.

Request accessPricing ↗

About

A meeting room is booked all afternoon, nobody comes, and the room runs cold with the lights on until evening. Another room hosts back-to-back meetings and is never reset. Meeting Room Reset reads room bookings from the room's calendar in Microsoft 365 or Google Workspace, occupancy from sensors over BACnet/IP or LoRaWAN, the zone setpoint, and the dim level of the room's DALI group.

When a booking is under way but the room stays empty, it proposes a standby setpoint and lights off. When one meeting ends and the next begins soon after, it proposes a tidy ticket. When the room is booked and occupied, it proposes nothing. It never edits or cancels a booking.

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

  • Bookings from the room mailbox's calendar view in Microsoft Graph, with start, end, organizer, and whether the event was cancelled
  • Rooms and their capacity, floor, and email address from the Microsoft Graph Places API, or Google Workspace calendar resources
  • Events on a Google Calendar resource calendar within a time window, with recurring events expanded to single instances
  • Occupancy or motion points over BACnet/IP, or motion and occupancy uplinks from LoRaWAN sensors, with their last-seen time
  • The zone's active setpoint and occupancy mode on the room's controller
  • Current dim level and scene state for the room's DALI group, and lamp failure reports from the drivers
  • Open tickets in Jira Service Management or ServiceNow for the same room, so a tidy is not requested twice

Proposed actions

  • Target capability: propose a standby setpoint for a room booked but empty, as a bounded write on the zone's allow-listed point
  • Target capability: propose lights off or a standby scene for the room's DALI group, within the groups on the allow-list
  • Target capability: propose a tidy ticket between back-to-back bookings, naming the room, the gap, and the next organizer
  • Target capability: propose returning the zone and lights to schedule when occupancy is detected or the next booking starts
  • Target capability: propose a weekly list of rooms booked and left empty, by organizer, for the workplace team

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

What you can build

  • Stand a room down when nobody shows

    The room calendar shows a meeting under way; the BACnet/IP occupancy point has read empty since it began. Meeting Room Reset proposes the standby setpoint and the DALI group off, and returns both when the next booking starts.

    With Microsoft Outlook, BACnet / IP, DALI Lighting

  • Reset between back-to-back meetings

    Google Workspace shows two bookings with a short gap and the LoRaWAN sensor shows the first group leaving. The operator proposes a Jira Service Management ticket for a tidy in the gap.

    With Google Workspace, LoRaWAN Network, Jira Service Management

  • Show the workplace team the ghost bookings

    Motion events from Disruptive Technologies sensors show which booked rooms stayed empty all week. The operator proposes a list by organizer and a ServiceNow task to follow up.

    With Disruptive Technologies, ServiceNow

Requirements

  • A Microsoft 365 or Google Workspace connector with read access to room calendars and the room list
  • An occupancy sensor per room, readable over BACnet/IP or as LoRaWAN uplinks
  • A DALI gateway connector with the room lighting groups on its allow-list
  • A work and ticket management connector such as Jira Service Management or ServiceNow
  • Places settings enabled in Microsoft 365, or calendar resources defined in Google Workspace, so rooms can be listed
Authentication
Meeting Room Reset carries no credentials. Bookings, occupancy, setpoints, and dim levels are read through your calendar, sensor, building platform, and DALI connectors, and proposals are written through those connectors and your ticketing connector.

Limits

  • A single motion sensor can miss a still person. The operator waits for both the booking and the sensor before proposing a standby.
  • It never cancels, shortens, or edits a booking, and it never messages the organizer. Bookings are read only.
  • Lighting changes go only to DALI groups on the allow-list. Emergency and egress lighting are never on it.
  • Rooms without a calendar resource, or without a sensor, are listed as unwatched, not guessed at.

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 Meeting Room Reset ↗

Questions and answers

What do you approve for a room?
Each standby setpoint, each lighting change, and each ticket. The proposal shows the booking, the sensor readings since it began, the setpoint and dim level now, and what would be written. Approve, edit, or dismiss. The return to schedule is proposed the same way.
What record is kept per room?
A receipt per proposal: the booking, the occupancy evidence, the point or group written, the value before and after, who approved it, and when the room was returned to schedule. The weekly list of empty bookings is kept, so patterns can be shown to organizers.
Does it touch bookings or people's calendars?
No. It reads room calendars and never writes to them. It does not cancel, shorten, or move a booking, and it sends nothing to the organizer. Any follow-up with people goes through the ticket a person approves.
Ask about Meeting Room Reset

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