The FIAS protocol suggests that any room which does not receive a Guest Check-in or Guest Check-out message during Database Sync should be considered to be unoccupied. The Niagara driver has termed this behavior Assumed Checkout . The driver keeps a total count of Assumed Checkouts in the Database Sync Summary Details and an example is shown below. More detail on which specific rooms where the occupancy state changed can be found both in the station’s Application Director output or the Job Log view of the Database Sync Job, found by clicking the >> icon in the Job Service
In this example, the Job Count / Listener Count indicates whether any data, which should have been included in the job metrics has escaped. The Room data will still maintain an accurate condition but the driver may not have included every change of state in the
Received GuestIn Count or Received GuestOut Count totals. This could be caused by the Job data structures not being in place before the PMS started sending data. This situation is only likely to occur in heavily loaded
If you observe that rooms are changing their occupancy state to false {ok} after a Database Sync when they were not previously updated by unsolicited data sent normally from the PMS, then you are seeing the Assumed Checkout feature at work.
If you consider this behavior undesirable on a particular site, Assumed Checkout can be disabled by using a property in the Micros Network/Link Config/Database Sync Config. Setting the Rooms Not Seen During Database Sync property to preserve occupancy will disable the effects of the Assumed Checkout feature.