Reference · built on requestOperator by FibricHospitality & guests

Out of Order

Compares rooms held out of order with the work orders behind them, and proposes returning fixed rooms to sale or holding faulty ones.

Request accessPricing ↗

About

Rooms stay out of order after the repair because nobody told the front desk. Other rooms are sold with a fault engineering already knows about. Out of Order reads the rooms held out of order or out of service in your property management system, the work orders behind them in your maintenance system, and the room's own readings over BACnet/IP where the building has them.

When a work order closes and the room's readings look normal, it proposes returning the room to inventory. When a work order opens on a sellable room, or a reading shows a fault, it proposes holding the room. The rooms manager approves both.

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

  • Rooms out of order or out of service through the hsk module in OPERA Cloud, with the reason and return date on each
  • Maintenance windows of type OutOfService, OutOfOrder, or OutOfInventory through GET /operations/v1/maintenances in apaleo
  • Resource states Dirty, Clean, Inspected, OutOfService, and OutOfOrder through resources/getAll in Mews
  • Work orders by asset and status in MaintainX, UpKeep, or Limble, including WORK_ORDER_STATUS_CHANGE and completion events
  • Zone temperature, fan status, and alarms for the room over BACnet/IP, timestamped as they change
  • Housekeeping room condition, so a room is proposed for sale only once it is clean or inspected

Proposed actions

  • Target capability: propose returning a room to inventory, with the closed work order and the readings that support it, for the rooms manager to approve
  • Target capability: propose an out-of-service or out-of-order hold in OPERA Cloud, or a maintenance window in apaleo, for a room with an open fault
  • Target capability: propose a housekeeping task to clean and inspect a room before it returns to sale
  • Target capability: propose extending a hold whose work order is overdue, with a note to the maintenance lead
  • Target capability: propose a daily list of rooms held with no open work order, for someone to explain or release

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

What you can build

  • Release the room the day the repair closes

    The MaintainX work order on the air handler closes, the room's BACnet/IP temperature settles, and housekeeping marks it inspected. The operator proposes ending the OPERA Cloud out-of-order record that afternoon.

    With MaintainX, BACnet / IP, Oracle OPERA Cloud

  • Hold the room engineering already knows about

    UpKeep opens a work order for a failed shower valve on a room still for sale. The operator proposes an apaleo maintenance window of type OutOfOrder until the order's due date.

    With UpKeep, apaleo

  • Find the holds nobody owns

    Each morning, rooms held out of service in Mews with no open Limble work order are listed for the rooms manager, with how long each has been held.

    With Mews, Limble CMMS

Requirements

  • A property management connector that exposes and accepts out-of-order and out-of-service status: Oracle OPERA Cloud, apaleo, or Mews
  • A maintenance connector with work orders linked to rooms as assets, such as MaintainX, UpKeep, or Limble
  • Optionally, a BACnet/IP connector with the room's temperature, fan, and alarm points on its read allow-list
  • A mapping from room numbers to maintenance assets and to BACnet/IP objects, kept by you
Authentication
Out of Order has no credentials of its own. Room status is read and proposed through your property management connector, work orders through your maintenance connector, and readings through the BACnet/IP connector's read allow-list.

Limits

  • Mews does not allow the OutOfOrder state to be set through its API. There the hold is proposed to a person to set by hand.
  • A closed work order is the signal. A repair done off the record does not release the room.
  • Readings over BACnet/IP cover what the building instruments. A cracked mirror shows up only in the work order.
  • It never releases a room that housekeeping has not marked clean or inspected.

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 Out of Order ↗

Questions and answers

What does the rooms manager approve?
Every return to inventory and every new hold. The proposal shows the room, the work order and its status, the latest readings if any, and housekeeping's condition. Approving a return ends the hold in the property management system; approving a hold creates it.
What record is kept per room?
A receipt for each hold and each release: the work order, the readings, the housekeeping condition, who approved it, the change made in the property management system, and how to reverse it. The daily list of unexplained holds is kept as well.
Can it put a room back on sale by itself?
No. A room returns to inventory only after a person approves, and only once. It never edits a work order, never changes a room's readings, and never releases a room housekeeping has not cleared.
Ask about Out of Order

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