Platform
The platform
Rydya is one product on one data model: the same backend serves web, mobile, desktop and login-free reporting. That single decision explains most of what follows.
- Biomedical engineering
- Hospital operations
- Clinical engineering
- Executive and finance
What is the Rydya platform?
Definition
The Rydya platform
Rydya is a single application over a single data model, serving web, an installable mobile surface, desktop and login-free public reporting from the same backend, so that every module describes the same equipment record rather than its own copy of it.
A suite of modules, each with its own asset table, drifts until what happened to a device depends on which module you ask.
One model has a real cost: you cannot buy just the part you want, and a change to the asset record is a change everything sees. The trade pays because the questions here are cross-cutting: what a device costs is a maintenance, finance and procurement question at once.
How the loop fits together
Report, route, resolve, prove. Everything else on this site is a detail of one of those four.
How one model shows up in practice
Five consequences, each of which would be an integration project in a suite.
One record per physical device, across its whole life
Commissioning, maintenance, calibration, incidents, cost and replacement all attach to the same asset. Its history never restarts when it changes hands.
The same record serves a technician and a director
A phone in a plant room and a board pack read the same rows, with no reporting extract to drift.
Money and maintenance are the same subject
A device that keeps failing and a device that keeps costing are usually the same device, visible only when repair history and cost live on one object.
Evidence is a by-product, not a project
The audit trail is written in the same transaction as the change it records, so the fortnight before an inspection becomes a query.
Scope is enforced once, everywhere
Organisation, location, department, asset, work order and external vendor: one boundary rather than five that mostly agree.
Why the refusals are the architecture
The things Rydya will not do are the load-bearing decisions.
It will not invent a clinical rule
No intervals, no limits, no thresholds, ever. Those belong to your qualified staff and the standards that apply to you.
It will not bend the return-to-service gate
Required tests, passing results, authorised clearance. No override, no demo mode, no convenience path. This is the one part of the platform that is not configurable.
It will not invent money
An unpriced downtime hour reads as unpriced, not as zero or a benchmark. Original amounts are immutable, conversions live separately with rate and timestamp, and estimated never merges with confirmed.
It will not let a record be quietly rewritten
The audit trail has no update or delete path at the database, for any role. Corrections are amendments beside the original, never replacements.
It will not let an offline device decide something is safe
Quarantine and return to service are server authoritative and unavailable offline rather than queued. Refusing is the honest answer.
What runs where
One backend, several surfaces, each with a deliberate job.
| Surface | For | Notes |
|---|---|---|
| Web workspace | Biomedical, quality, finance, management | Density: registers, filters, history, cost. |
| Installable mobile | Technicians in the field | One job at a time. Works with no signal, queued durably. |
| Desktop | Teams who want it out of the browser | The same application, same data model. |
| Login-free reporting | Everyone else | A QR scan, a form, a reference. No account, nothing to install. |
| Webhooks and imports | Your other systems | Signed, retried, dead-lettered. Imports across seven registers. |
Surfaces and what each is actually for
When one model is the wrong choice
If you want a maintenance module alone, or two organisations sharing one device history, this is not the product.
You cannot license a slice: there is no separate maintenance product without the financial records.
Cross-tenant sharing is out of scope. A group is one organisation containing many locations; two genuinely separate organisations sharing one device history is not supported, and no configuration produces it. Service companies and leasing businesses hit this edge most often.
Nothing here is a separate purchase
Every capability on this site is part of the same product: the register, planning, calibration, safety gates, incidents, inventory, procurement, downtime cost, reporting, offline field work, integrations and audit. There are no modules, no editions and no feature flags gating them apart. One product is a claim about architecture, not about completeness: the security page publishes what we have not built, and the integrations page states that no named connectors exist.
Questions
Can we buy only the maintenance part?
No. Rydya is one product on one data model, with no module to license separately. If you genuinely need only a work-order tool, a smaller product will fit better and cost less.
Is the mobile app a different system from the web workspace?
No. One backend and one data model serve web, installable mobile, desktop and login-free reporting. A mobile app with its own schema would be a second system, and second systems drift.
What is the single most important thing to understand about the platform?
That the refusals are the architecture. Rydya will not invent a clinical rule, bend the return-to-service gate, invent money, let a record be quietly rewritten, or let an offline device decide equipment is safe.
Can two separate organisations share a device history?
No. Cross-tenant sharing is out of scope. A group is one organisation with many locations, which is native rather than an upsell; two genuinely separate tenants sharing one device record is not something Rydya does.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us