Industries
Biomedical maintenance companies
A maintenance company is judged on two things it usually cannot prove: how fast it responded and whether the work was really done. Your engineers know both. Your clients ask at renewal. The gap between those two facts is where contracts are lost by companies that were doing a good job.
- Biomedical engineering
- Executive and finance
- Field technicians
What is different about a service company?
You sit on the other side of the relationship every other page here describes, and your evidence is your product as much as the repair is.
Everywhere else on this site, the vendor is the party being measured. Here you are the vendor, and the asymmetry works in your favour only if you are the one with the records. A client with a good equipment system will arrive at renewal with your response times measured from their side. If your answer is a recollection, you will lose an argument you deserved to win.
The second difference is that your engineers work across organisations you do not control. They travel between client sites, often with no signal in the plant rooms where the equipment lives, and they are the only people who know what actually happened. Whatever they do not record at the point of work is gone.
The third is that your commercial model is built on work that is difficult to observe. A client cannot see effort. They can see a device that came back and a report that arrived, and if the report is thin, the effort might as well not have happened.
How Rydya works for a service business
Your engineers record at the point of work, offline if necessary, and the record is the evidence you hand over.
Evidence is captured where the work is
Checklists, readings, photos and notes on the phone, in the plant room, offline, queued durably. Not written up in the van afterwards from memory, which is where the detail that would have proved your case gets lost.
Response and completion are timestamped as they happen
When the job was raised, acknowledged, attended and cleared. These are the numbers you are judged on, recorded by doing the work rather than reconstructed for a meeting.
The procedure version travels with the result
What was done, against which version of the procedure. Improving your procedures stays safe, and work done two years ago remains interpretable when somebody asks about it.
Photos are real bytes, not filenames
Stored, permission-checked and audited on download. A photograph of the condition at the moment of work is frequently the difference between a supported claim and an argument you cannot finish.
The trail is append-only
Hash-chained, written in the same transaction as the change. Which is worth something precisely because it means you cannot tidy it either, and a client's auditor knows that.
Why the renewal conversation turns on records rather than work
Because your client cannot observe the work, only its traces, and a company with thin traces looks identical to one that did less.
The client's biomedical lead defending your contract internally is in a difficult position. They believe you are good. Asked to demonstrate it, they have invoices and an impression. Meanwhile finance has a number for what the contract costs. The lead is arguing quality against arithmetic, without evidence, and they will lose often enough that it is worth fixing.
What changes that conversation is unglamorous: response times measured from real jobs, completion evidenced with photos and readings, and a history that shows the same device stopped failing after you changed something. None of that is extra work. It is the work, recorded at the moment it happened rather than described later.
This is also why offline matters more here than in most segments. Your engineers are in basements and plant rooms by definition. A tool that needs signal to record has decided not to be used where your evidence is generated.
Read this before assuming a fit
Rydya is one organisation per tenant, and cross-tenant sharing is out of scope. If your model needs your engineers to work inside each client's own separate Rydya tenant, that is supported through the external vendor scope: they see the work orders they are engaged on and nothing else. What Rydya does not do is federate a device history across two organisations, and it has no billing, invoicing or contract-management module. It is better to establish that now than during an implementation.
When to use your own tenant, and when to work in the client's
It depends on who owns the equipment record, and it is worth deciding deliberately rather than drifting into an answer.
If your clients each run their own Rydya organisation, your engineers can be given the external vendor scope inside theirs: they see the jobs they are engaged on and nothing else, enforced on the server rather than by hiding menus. The equipment history belongs to the client, which is usually correct, and your evidence lands directly where the client will look for it.
If your clients do not run Rydya, you can run your own organisation covering the estates you maintain. You then hold the register and the history, and the client receives exports and reports rather than access. That is a different commercial posture, and it has a real implication worth naming: when a client leaves, the question of whose record it was becomes a live one. Decide that at the start, in the contract, rather than at the end.
Questions
Can our engineers work inside our clients' Rydya accounts?
Yes, through the external vendor scope: they see the work orders they are engaged on and nothing else, enforced by server-side permission checks and row level security. This is the scope most systems forget entirely, which is how vendor access usually becomes a shared login with far more reach than anyone intended.
Our engineers work in basements with no signal. Does that work?
Yes, for the observation work: my work, scan, checklists, readings, notes and photos, queued durably so they survive the app closing or the battery dying. Safety-critical actions such as quarantine and return to service stay online by design, because an offline device cannot establish that equipment is safe. Given where plant rooms are, a tool needing signal has decided not to be used where your evidence is made.
Does Rydya handle our invoicing and contracts?
No. There is no billing, invoicing or contract-management module, and none is planned in current scope. Rydya manages the equipment work: the jobs, the evidence, the timestamps, the history and the cost records. If you are looking for a field-service business system, this is not that, and it is better to know before an implementation than during one.
If we run our own tenant, who owns the equipment history?
Whoever the contract says, and that is worth settling at the start rather than at the end. If you hold the register, your clients receive exports and reports rather than access, and the question of whose record it was becomes live the day a client leaves. Rydya does not federate a device history across two separate organisations, so the commercial answer has to come first.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us