PRODUCT STATUS
Buying maintenance software means trusting what the vendor tells you. This page states what UR Maintain does today, in the product's own words, including its stated limits.
LIVE TODAY
Reviewed against the application's own engineering documentation in September 2026.
Sign-in runs through Keycloak (authorization code + PKCE) — no password ever touches the application. The app lists the plants you are actually a member of and asks which one you are working in. Site scope is applied on the server, so it is a limit rather than a label.
Assets list with status and site and open into a full record: tag, type, maker, model, serial number, criticality, location and plant. A field nobody has recorded reads “Not recorded” rather than sitting blank. The Scan tab resolves a QR sticker to that machine, so a technician goes from standing at the equipment to its record without typing.
Filing works with the API unreachable: the report is written to the device first. A connectivity strip shows what is waiting and whether the plant has confirmed it, and coming back online pushes it automatically. A plant that refuses a report says so on the device as “Needs review” instead of retrying forever.
Take, start, wait with a reason, resume, report the machine running and finish the report — all of it working offline. A supervisor then verifies and closes. Reporting the machine running is a fact about the equipment and does not move the job, so a line can be back in service at 03:00 and the report written after the shift.
Everything written on a job — notes, waits, diagnostics and handover remarks — is listed back on it, oldest first, with the name of whoever wrote it. The next shift reads the history instead of guessing from the last line.
A parts catalogue with per-bin availability. From a job a technician reserves or issues a part, and the stock ledger shows what moved. A reservation appears as a promise, never as used stock, and an issue that would take a bin below zero is refused with the plant's own figures.
A planner defines a recurring job — for example every two weeks on Monday and Wednesday at 06:00 in Europe/Warsaw — against the machines it covers. The plant generates the work orders itself, exactly once, and holds the local time across a clock change. Editing a plan creates a new revision, so a job generated last month still names the plan it came from.
A planner writes a checklist and publishes a version. A technician starts an inspection pinned to that version, answers its items, and the plant decides which answers count as failures from each item's own rule. The corrective work order is offered as a separate, deliberate action. A published checklist cannot be edited afterwards.
A drawing, manual or procedure stays linked to the machine it describes. Replacing it means uploading a new revision; the old ones stay readable exactly as they were, and exactly one revision is marked current. Downloads come straight from object storage and files never pass through the application.
One field answers about machines, jobs, defect reports, parts and documents — grouped, ranked and scoped to the plant, or to a single machine from that machine's own screen. It tolerates half-remembered codes and misspellings, and results carry the plant, the machine and the revision of the row behind them.
A manager stages a CSV of machines or parts from a legacy system. Every row is judged before anything is written and reported back as valid, warning, error or applied. Applying is safe to repeat, and a row already applied is never written twice. The import never touches an asset tag, a part number, stock levels or money.
The outgoing shift files a handover for the incoming one: the lines it carries, the machine or job each line names, and the rows flagged as needing attention. The incoming shift opens the whole handover — every line, in the order the outgoing shift wrote it — and both the feed and the screen are there. A filed handover cannot be edited or deleted: the tables grant reading and inserting and nothing else, so a correction is the next handover rather than a silent rewrite.
Filing works offline too: a handover written in a dead zone is queued on the device and filed when the plant is reachable.
The application ships with a service worker that precaches its own shell, so a handheld closed in a dead zone opens the application again instead of a blank page, and an /api/ path is never answered out of that cache. Stated limit: no automated test exercises the worker — the browser suite runs the development server, where the plugin registers nothing — so this is described as configured rather than claimed as proven. What is tested today is a full reload with the API unreachable, which proves the application's own offline gate rather than the worker.
Every plant's rows are separated by PostgreSQL row-level security in forced mode, with a runtime role that cannot bypass it. Another plant's record answers as “not found” rather than leaking, and a reference to another plant's site or machine is refused by the database, not by application code that could forget to check.
ALSO LIVE
Everything below is live in the current release.
Search reaches inside a PDF and into scanned drawings: text is read out with OCR, so a component reference or a phrase finds the right document and page, not only its number or title.
Defect reports, the six job commands and photos work offline, and so do inspections, inventory movements, preventive-maintenance commands and shift handovers. Work done in a dead zone is queued on the device and pushed when the plant is reachable.
With no connection the search box still answers about the plant's machines, jobs and parts held on the device, and labels the results as offline.
A manager dashboard shows open work, breakdowns, downtime, preventive-maintenance status and inventory issues, built from the facts recorded on the jobs rather than from decorative numbers.
Changes are recorded in an audit log with actor, timestamp and reason, alongside the immutable stock ledger.
A plant can export its data, and a deletion workflow covers the end of a contract. Data portability is a product feature, not a favour.
Email, push and webhook notifications tell the right people when something changes.
Preventive maintenance runs on running hours and counters as well as on the calendar.
Stock moves between bins and locations as one linked transfer, never as half of one.
Search runs on a per-plant index, so it stays fast as the plant's data grows, under the same row-level isolation.
FOR THE MAINTENANCE OFFICE
Live in the current release, on both editions.
Operators and anyone else on the line report faults without a paid seat: requester accounts are free on every edition and are not counted as users. Scanning the QR sticker on a machine opens a short report form without signing in, so the report names the right machine and lands in the maintenance queue like any other.
A register of equipment under technical supervision (UDT) and of the periodic inspections the law requires — lifting and pressure equipment, electrical measurements — with the last inspection, the next due date and the protocol attached. Alerts warn ahead of the deadline, so an expired inspection is found in the system rather than in an audit.
SEP, UDT and training certificates are recorded per technician with their expiry date and the scanned document. Alerts go out before a qualification lapses, and the auditor's question “who is authorised to work on this?” is answered with one list.
A closed breakdown carries a failure code. The Pareto report shows which causes and which machines cost the most downtime, and MTBF and MTTR are calculated per machine from the recorded jobs — the numbers a maintenance manager takes to the plant director.
A full-screen view for a TV on the shop floor: the queue of open requests, the machines that are down and for how long, and the work in progress. It runs in any browser and refreshes on its own.
Set a minimum stock per part. When a bin falls below it, the part goes onto a requisition list; maintenance reviews the list and exports it for the purchasing department. Simpler than a purchasing module, and enough to end the “we ran out” surprise.
SEE IT FOR YOURSELF
Request a demo and we will walk you through the live application on sample data.
