The building, the floor, the room and the piece of equipment are already in Ruya. The work order picks them up, so nobody types an address into a description box.
Nobody goes looking for the room. It is on the work order.
The building, the floor, the room and the equipment are already on record. A work order picks them up instead of asking somebody to describe them.
Work Orders is a tab on the building record, sitting next to that building's floor plans, its room data, its projects and its assets. You open the building, you see its work. Nobody starts in a separate system and then works out which site it meant.
Naming a piece of equipment is required before a work order can be saved. That one rule is the difference between a unit with a history you can read and three separate jobs that all say cooling issue.
The building fills itself in, because you raised it from inside that building. Floor and room are chosen from that building's own record rather than typed into a description. A start date and a due date are both required, so nothing gets saved without a day it is expected by.
Status, priority, assignee, category or equipment. Eight columns, every one of them sortable, and you decide which ones you want on screen. What is open on the third floor this week is a couple of clicks, not a report request.
What it is about, who has it, its priority, the room it is in, and four dates: started, due, last updated, finished. The status changes right there on the work order rather than on some other screen.
The same record at four moments. Watch the dates fill in, and watch where the fix ends up.
Supply air is running warm on the third floor. The work order opens against the unit itself, in the room it sits in, with a priority and a date it is expected by. Nothing about where it is had to be typed.
A person, a start date, a due date. The status moves on the work order itself, so the list everyone else is looking at is right without anybody being told.
The technician says what they actually did and attaches a photo of it. Their name and the day go on the message. This is the part that usually lives in somebody's head, or in a text message, or nowhere.
Chilled water valve actuator stuck at 40 percent. Replaced the actuator and the coupling, ran the unit through a full cycle.
ahu7-actuator-after.jpgThe finished date is stamped separately from the date it was due, so you can see both what was promised and what happened. The work order stays on the equipment and on the building, which is where the next person will start.
Four moments on one record. Nothing was re-entered, and nothing about it lives anywhere else.
Most hospitals already run something. The question is not whether the work gets logged, it is whether the log is any use to the next person who opens it.
None of this depends on anybody remembering to fill in the right box.
These are structural, not measured. They describe how the product is built, not results from a customer. Ruya does not publish numbers it has not earned.
Every work order names the unit and the room, so nobody walks a floor looking for the thing that is broken.
Filter to what is open, what is yours, or what is on the floor you are already standing on.
Write it in the thread, attach the photo, move on. It is on the record and it stays there.
Status, priority, assignee, category and equipment are all filters, on the building you are looking at.
The due date and the finished date are separate fields, so the gap between them is visible rather than argued about.
A piece of equipment that keeps coming back shows up as a run of work orders against the same asset.
Every update carries a name and a day. Nothing is reconstructed afterwards from memory.
A photo of the work goes on the update, which is the evidence people usually go hunting for.
The work order sits on the building, beside its floor plans, its rooms, its projects and its binder.
Which is why it is raised from the building record, where the unit and the room already exist.
A work order can be raised by a person, or written for you by a trigger on the maintenance schedule. The piece of equipment it is raised against is an asset on the building. The room it sits in carries its own department and use in the room record, and that room is on the current floor plan for the floor. And the manual and warranty for the unit arrived in the closeout folder of the project that installed it, on the same building.
Healthcare CMMS software is a computerized maintenance management system built for hospitals, used to create, assign, and document work orders for corrective and preventive maintenance. Facilities teams use it to show staff, leadership, and Joint Commission (JC), DNV, or CMS surveyors a complete record of what was fixed, where, by whom, and when. Ruya Work Orders is a software and service solution: every work order is pinned to a building, room, and asset on the floor plan, and Smart Maintenance Triggers open follow-up work orders from failed inspection results automatically.
For work on a building, that is what it is for. The difference is where the record sits. The work order is on the building, next to that building's floor plans, its room data and its project history, and it names the piece of equipment it is about rather than describing it. If you run a larger system for finance, inventory or purchasing, this does not touch that.
No. Naming the asset is required before it can be saved, and that is deliberate. It is the whole difference between a unit with a history somebody can read and three separate jobs that all say cooling issue. If the thing being worked on is not in the asset list yet, it gets added, which is how the asset list stays honest.
Yes. Every work order carries an update thread, and an update can have a photo on it as well as the message. What was replaced, by whom, on what day, with a picture of it. That is the part that normally lives in somebody's phone.
It opens, it gets an owner, it gets worked, and it finishes. The status changes on the work order itself rather than on a separate screen, so the list everybody else is looking at is right without anyone being told. The date it was finished is recorded separately from the date it was due, so you can see both what was promised and what happened.
No. The building and the piece of equipment are what anchor it. Floor and room are there when you want them, and they are chosen from that building's own record rather than typed in, which is exactly what makes them worth filtering on two years later.
There are no per-seat licenses, so including the people who actually do the work does not change what you pay. That matters more here than anywhere else in the platform, because work orders are the module where the most people need to get in.
The one everybody has an opinion about and nobody has the history for. We’ll put it on a building in Ruya with its last few jobs on it, and you can see what the record would have told you. Twenty minutes, with the founder, not a sales rep.
Rashad Mujeebuddin, Founder, Ruya
On your schedule — no prep needed.