AI room inspection for Oracle OPERA Cloud

Overview

An OPERA Cloud task sheet says which rooms an attendant owns today and which reservations sit in them; it does not say what any of those rooms looked like when the attendant tapped Finish this room. The task sheet carries the room list, credits, special instructions and reservation details, and the attendant works it in the Task Companion, setting each room to Clean when the service is done and, at properties that use it, a supervisor sets Inspected afterwards. Oracle's documentation describes images only on Room Maintenance requests, never on the task itself, so the housekeeping photos at an OPERA Cloud hotel usually live in an operations app beside the PMS, or nowhere. RapidEye reads those photos, plus the task sheet, room statuses and reservation dates from OPERA Cloud, and returns one finding per problem: damage new since the last stay, a service that was missed, an item that is gone, a maintenance fault, with the before and after photos side by side and the room and reservation named.

How it works with OPERA Cloud

OPERA Cloud already sorts the day by room status and reservation state, and the Task Companion sequences rooms by that sort: vacant dirty rooms with an arrival due first, occupied stayovers after, due-outs last. RapidEye follows the same categories, because each one says something different about what the photo should show.

• Departure rooms (vacant, Dirty, the departure task). The guest who just left is the one who did whatever the room now shows. RapidEye compares this service's photos to the last set from the same room and attributes anything new, a burn on the desk, a cracked bathroom mirror, a stained headboard, to the reservation that sat between them. A hypothetical 300-room property with 110 departures on a Sunday would get one card per new problem, not 110 galleries to open.
• Stayover rooms (occupied, Dirty or Pickup). The guest is still in the house, so a finding here is about service and about early damage. RapidEye reads the stayover photo for the bed remade over a stained sheet, the untouched bathroom, the bin left full, and for a spill on the carpet that will be a claim if it is still there at departure.
• Rooms set to Inspected. Where the Inspected Status control is on, OPERA Cloud can generate separate task sheets for inspecting rooms already in Clean status. RapidEye reads the same photos the inspector would look at and lists what needs their eyes, so the inspection sheet becomes a list of rooms to walk rather than a list of rooms to hope about.
• Rooms carrying a Room Condition or a maintenance request. Oracle's own examples of a room condition are a minibar removed or an interconnecting door unlocked; a maintenance request is a bulb, a lock, an air conditioning unit. RapidEye holds the photo to that record: the minibar that was supposed to be gone and is back, the request marked resolved whose fault is still visible.
• Do Not Disturb and No Service Required rooms. OPERA Cloud can put these on their own additional task sheets. RapidEye reads whatever photo eventually comes from them, so a room that skipped two services is not also a room nobody has looked at for three days.
• Missing items and brand standard. The second robe, the coffee pods, the remote, the laundry bag, the artwork hung straight. RapidEye knows what a finished room at your property looks like and says when this one is short.

A finding names the room and the spot in it, the kind of problem (damage, cleaning, missing item, maintenance), how serious, the before and after photos, and a suggested next step. It lands in the RapidEye dashboard and, if you want it there, in a Slack channel or the housekeeping office's inbox. What happens in OPERA Cloud afterwards is your decision: a room back to Dirty on the Housekeeping Board, a maintenance request with the image attached, a note on the reservation folio. Photos are the usual input, not the only one. A team that films a walkthrough of each departure, or has scans of its room types, or wants findings scored against its own brand-standards inspection form, gets that set up with us on the first call.

How to connect OPERA Cloud to RapidEye

1. Task sheets generated in OPERA Cloud. Run your day from task sheets, generated for the business date under Inventory, Room Management, Task Sheets. The rooms on those sheets, their statuses and the reservations attached to them are what RapidEye reads; a property that still hands out printed task sheet reports is fine, since the sheets exist in OPERA Cloud either way.
2. Room photos from your attendants or inspectors. If your team already photographs rooms in an operations or inspection app beside OPERA Cloud, RapidEye reads those. If not, a RapidEye capture link opens on any phone with nothing to install: a fixed set of angles per room, lights on, taken before the room status is set in the Task Companion.
3. Add RapidEye as a user in OPERA Cloud. Register a user named Rapid Eye with the email support@rapideyeinspections.com in Oracle Identity Manager, then in OPERA Cloud go to Role Manager, User Management, Manage Users and assign the hubs for the properties you want checked. The Connect button above has the details laid out.

Attendants keep the Task Companion and the same run of rooms. The front desk keeps the Housekeeping Board. The only new habit is the photo, and at most properties that habit already exists somewhere in the stack.

How OPERA Cloud housekeeping runs today: room statuses, task sheets and the Task Companion

Checked against Oracle's OPERA Cloud Services user guide, September 2026.

OPERA Cloud is Oracle Hospitality's cloud property management system for hotels, sold to properties, according to Oracle's product pages, of various sizes and complexities, with a dashboard of more than thirty preconfigured tiles covering front desk, revenue, inventory and housekeeping. Housekeeping lives under Inventory and Room Management, and it is built on one thing: the room status. According to Oracle's OPERA Cloud documentation (oracle.com), the room status is the current cleaning status of the room, and six values are possible depending on which OPERA Controls the property has switched on.

Status definitions as documented by Oracle. The right-hand column is what each status proves on its own, before any photo is read.

Two more things ride beside the room status. The housekeeping status (Vacant or Occupied) is what the attendant found, and when it disagrees with the front office the room becomes a Skip discrepancy (checked in but found empty), a Sleep discrepancy (shown vacant but there is luggage in it) or, with the right control, a Person discrepancy on guest count; the front office resolves those by checking someone in or out. And at End of Day, OPERA Cloud rolls statuses forward on its own, updating occupied and vacant rooms according to the Update Occupied Room Status and Update Vacant Room Status controls, which is why a room can be Dirty on Tuesday morning without anyone having touched it.

The task sheet

According to Oracle's documentation, task sheets inform room attendants about their daily work assignments: a list of rooms assigned to each attendant, special instructions about specific rooms, and related reservation details. They can be auto-generated or created by hand for the current or next business date, and the number of rooms on each sheet is set by housekeeping credits, which divide the day's effort between attendants and can be configured per room, per task, or as a room-and-task rule with extra credit rules for travel, specials and inventory items. With Housekeeping Task Scheduling on, a limited-service or extended-stay property can schedule which task a room type gets on which day, though a departure room always gets the departure task. Additional sheets can be generated for Do Not Disturb rooms and No Service Required rooms, for turndown, and, with the Inspected Status control, for inspecting rooms already in Clean status. A manager assigns an attendant to each sheet, adds sheet-level and room-level instructions, moves rooms between sheets, and can prioritise a room so it surfaces first in the companion. The sheets are then either printed as task sheet reports or opened in the Task Companion, and the Attendant Console watches progress from the office: time taken per room, completion percentage, credits done, and whether an attendant is on a break. Oracle notes that creation and deletion of task sheets is tracked in the changes log and purged after 30 days.

What the attendant taps in the Task Companion

The Task Companion is OPERA Cloud's mobile housekeeping screen, installed on a phone as a web app by scanning a QR code from the desktop side menu, or run on a tablet from Manage Task Sheets. Oracle's documentation says it replaces the need to generate and distribute task sheet reports. The run for one room, as documented, goes like this.

1. Open the assigned task sheetThe summary shows the total rooms allocated, a count per room status, the room numbers, and the sheet instructions. Rooms are sequenced by auto-priority: vacant, Dirty, arrival, VIP, queue first.
2. Start, or SkipStart begins the room. Skip moves on. View Reservations shows the arrival, stayover or departure details; View Traces shows and resolves department traces; Do Not Disturb marks the room and skips it; Request Assistance sends a General or Emergency notification; On-break pauses the timer.
3. Room detailsPreferred service time and room-specific task instructions appear. A timer may count up or down, depending on the Task Companion Timer control.
4. Maintenance RequestsCreate, view or update a maintenance request for the room: a reason code, remarks, an assignee. This is the one object in OPERA Cloud that Oracle documents with images: on the desktop screen there is an Add Image button, and requests with images show an icon in search results. Resolved requests are purged 90 days after resolution.Images live here, and only here
5. Room StatusOnce the task is complete, select a status: Inspected, Clean, Pickup or Dirty. Housekeeping Status sets Vacant or Occupied, which is how a Skip or Sleep discrepancy gets raised from the floor.
6. Finish this roomThe room leaves the list and the companion advances to the next room in sequence.

Steps as documented by Oracle for the Task Companion. The highlighted step is the only one that carries an image.

Does OPERA Cloud take photos of the room during housekeeping?

Not as documented. Oracle's Task Companion pages (the phone web app and the tablet Task Sheet Companion) list every action available to an attendant, and none of them is a photo: reservations, traces, Do Not Disturb, assistance, breaks, maintenance requests, room status, finish. The Housekeeping Board, Room Discrepancies, Room Conditions and Attendant Console pages describe statuses, remarks and timings, not images. The single place images appear in the housekeeping documentation is the Room Maintenance request, and those are purged 90 days after they are resolved. So Clean in OPERA Cloud means an attendant finished the run, and Inspected means a supervisor stood in the room; neither carries a picture of the room, and the pictures your team does take live in whatever operations app sits beside OPERA. That is exactly the seam this integration works in: OPERA Cloud supplies the room list, the statuses and the reservation each room belongs to, the photos come from wherever your team takes them, and RapidEye is the part that reads every photo against every status and tells you where they disagree.

Oracle OPERA Cloud integration FAQ