FAQ

You need to log in to Hospitality Suite Secure to activate the new security lines for Operations Connect. See Operations Connect Security for information on security for Operations Connect.

To maintain optimal database performance, the widgets are refreshed every 10 minutes.

In the first release of Operations Connect, you can’t move or resize the widgets. This will come in a future release.

To maintain good performance, the data is refreshed every 10 minutes. So, depending on the last time the data was refreshed, it might not have appeared yet.

Another scenario that may prevent a ticket from appearing in the printed count is if there was no room assigned to the patron.

Operations Connect is designed to highlight problems at specific delivery stages. For that reason, the average stage time is always calculated from the interval of the previous stage. If a stage was skipped in the delivery process, that could affect the average time of a stage because that data isn't considered in the average stage time calculation.

Negative times may appear if trays are advanced through delivery stages out of order. The correct delivery stage sequence is Assembled, Left Kitchen, Delivered, then Picked Up.

Negative values may also appear if a user scans a past meal (a past meal is served after the meal's ended), or if the device’s time and the server time are not synchronized.

If a new ticket is printed, say for a diet order change or room transfers, the old ticket scan may then sit in a delivery stage since it is no longer being advanced through the delivery stages. It is possible, then, to reach the end of a meal service and still see some tickets sitting at different stages throughout the delivery progress bar.