I’ve got 20 years of life safety plans in my own files.
Floor plans live in email threads, shared drives, and a binder on the third shelf. Ruya keeps one current set per building in PDF, DWG, and Revit, with every prior revision preserved underneath it.
Priced per building, not per seat. Every consultant you invite is included.
Five things every hospital floor plan has to do. Open one to see it in the record.
View, measure, and annotate PDF, DWG, and Revit on a phone, a tablet, or a desktop. No CAD seat for the facility tech, and no waiting until someone is back at their desk.
Every floor plan lives with its building, not in a system-wide folder tree. A new director on Campus 4 opens the building and sees what they need on day one.
The current version is one click. Every prior revision sits preserved underneath it, timestamped and attributable to whoever made the change.
Assets, vendor records, and inspection history link back to the room they live in on the floor plan. Open the room and see everything attached to it.
Architects, life safety consultants, and contractors get access to the buildings they are contracted for, and nothing else in the portfolio. Nothing sits on your hospital network, there is no second account in your IT system, and access ends when the contract does.
A wall moves. Today that starts an email chain that can run three months. In Ruya it starts a tracked request.
Submit an update request against a specific building, floor, and room. Attach the change order, the photo, the punch-list item, whatever triggered it.
Please change the door swing from the hallway to the inside of infusion. I put comments on the PDF.
The source files get updated in CAD, Revit, and PDF, then queued for consultant review. You can see where the request sits without asking anyone.
Please change the door swing from the hallway to the inside of infusion. I put comments on the PDF.
They review and upload directly inside Ruya. No inbox drops, and no asking which PDF you meant. The version lands in the set the moment it is approved.
Life safety sheet needs to match the new door swing on the infusion suite.
The new version becomes the current set. Every prior version stays. Everyone who needs to know is notified automatically, so nobody waits and nobody wonders.
Includes the main plan and all reference plans
Automatic notifications go out at every step. No one waits on an email, and no one has to ask where a request stands.
Please change the door swing from the hallway to the inside of infusion. I put comments on the PDF.
Nothing here is exotic. It is the ordinary week of a facilities team, before and after the floor plan has one home.
They ran 100+ buildings on a three-month email chain. They rebuilt the update cycle on Ruya.
Measured across MyMichigan Health’s active floor plan updates. Prior baseline: 12 to 24 weeks per update on the email workflow. Current: 2 to 6 weeks on Ruya.
Open the building on a phone and pull the floor plan where you are standing. No laptop, no CAD seat, no call to the office.
Measure and annotate the plan directly. PDF, DWG, and Revit all open natively, so the file you have is the file you can use.
Every prior revision is preserved and timestamped. When someone asks what changed and when, the answer is in the record.
A running count of active floor plan updates per building. No one has to maintain a spreadsheet to tell you where things stand.
Each update carries its own cycle time, so slow handoffs are visible while they are still fixable.
Every architect, consultant, inspector, and surveyor you grant access to is included. Growing the bench does not grow the bill.
Access covers the buildings and folders they are contracted for. Nothing else in the portfolio is visible to them.
Revisions go straight into the Update Request Process, not to whoever they happened to remember.
No hospital login, no VPN, no IT ticket, and no second identity to deprovision when the contract ends.
I’ve got 20 years of life safety plans in my own files.
I really like the ease of how the process works. This has been so helpful on my end.
It seamlessly brings facility information into the modern era — access is incredibly simple, without extra plugins or downloads. We can’t imagine going back.
Everything else in Ruya is anchored to it. One plan, every team, every building.
The per-room data layer in Building Data carries cost center, ICRA level, AHU zone, and smoke compartment for every room on the plan. The per-building project trail in Project Files syncs the set as renovations close out. The closeout-to-closet trail in Assets and the per-building vendor record attach to the room they live in. And when a JC surveyor opens the audit binder, the life safety plans they read are the same current version your team is looking at.
Hospital floor plan software is a system that maintains a single current set of floor plans, including architectural, life safety, and as-built plans in PDF, DWG, and Revit, for every building in a health system, with every prior revision preserved and every change tracked. Facilities teams use it to give staff, contractors, and surveyors one verified answer to “which floor plan is current” during renovations, inspections, and Joint Commission (JC), DNV, or CMS surveys. Ruya Floor Plans is a software and service solution: the platform keeps one current set per building on any device with no CAD seat, and the Ruya team handles floor plan updates through a tracked four-step process.
PDF, DWG, and Revit, natively. Viewed, measured, and annotated on a phone, a tablet, or a desktop, with no CAD seat and no plugins. It is built for field use, not desk use.
Every update runs through four tracked steps. The request is initiated by the facility manager, architecture and space updates are made by the Ruya team, your life safety consultant or architect of record reviews and uploads, and the requestor is notified when the new set is delivered. Every prior version is preserved, and the current version is always one click.
Yes. Their access covers only the specific buildings and folders they are contracted for, with no second account in your IT system. They upload revisions directly inside the Update Request Process, and the version becomes part of the current set the moment it lands.
A document management system treats a floor plan as a file. Ruya treats it as a building artifact, tied to floor, room, asset, vendor, inspection record, and active permit. The Update Request Process exists because changing a hospital floor plan is not like changing a contract or a policy.
No. Ruya reads what your architects produce in CAD and Revit. Your design team keeps their tools, and your facilities team gets a viewer, an update workflow, and one current set across every building.
Onboarding includes organizing, fixing, and uploading your existing floor plans, with in-person surveys and CAD updates where needed. A typical multi-campus rollout starts with one building as a proof, expands to the rest of the campus, then to the next campus.
Pick the one with the most updates in flight. We’ll load its floor plans into Ruya and walk through them live. Twenty minutes, with the founder, not a sales rep.
Rashad Mujeebuddin, Founder, Ruya
On your schedule — no prep needed.