Questions, answered

It turns the maintenance procedures a plant already has into work orders that appear on their own, get filled in on a tablet by whoever is on shift, and leave a record with times, readings and a name against them. The point is the record: a round that was done and cannot be proved was done is, to an inspector, a round that was not done.

No. The template library ships hundreds of ready-made procedures grouped by industry — opening and closedown rounds, sterilisation logs, vehicle walkarounds, safety inspections — with the readings and tolerances already in them. You pick one, it opens in the editor as a new template, and from that point it is yours: rename it, cut what does not apply, point it at your own machines. During a pilot you get part of the library in full and the rest as summaries; the whole catalogue opens when the account moves onto a plan.

On a canvas. Each question is a node, the line down the page is the order the operator is asked them, and a dashed line means a question is only asked when an earlier answer matches — so "if the reading is out of range, ask what was done about it" is something you draw rather than something you configure. Sections bind to a machine or to a type of machine.

A browser. It is built for a tablet on a shop floor with gloves on — large controls, one form per work order, answers saved as they are typed rather than on a button nobody presses. There is no app to install and no store to get through.

The application is Croatian and English, chosen per person — the buyer and the shop floor often do not read the same one. Library templates are written in English today and can be renamed and rewritten the moment they are yours; more languages are coming.

No. Only staff who need invitations and password resets have one. Operators get a username their administrator creates, and type the organization’s handle beside it when they sign in.

Two roles. An operator sees the work assigned to them and fills it in; an administrator writes procedures, manages the register and reads everything. A work order can be bound to one person or to a team, so a template written once still lands with the right shift.

One. Work orders and equipment belong to a facility, and a procedure written once generates per facility — reporting across all of them is on every edition. What decides the edition is how many facilities there are: Single is one, Multi is four, Group is fifteen, and beyond that we quote it.

Yes, on every edition. A person from another organization can be granted access to yours and carries the role you give them here, not the one they hold at home — an administrator of their own company is an operator in your plant if that is what you granted. They count against your operator accounts while the access lasts.

Nothing is deleted. Everything written during the trial is yours and stays where it is; the account moves onto the edition you agreed and the trial’s tighter ceilings widen to that edition’s. If you decide against it, ask us and the organization is removed.

Yes, in either direction, and moving up raises ceilings rather than turning features on — every edition already does everything, apart from the procedure library and bulk transfer, which Single does not reach. If your plant grows past its edition we tell you in the app first; nothing is switched off and no work is refused while that is being sorted out.

Monthly or yearly, in euro, excluding VAT; a yearly term is charged for ten months rather than twelve. Croatian and EU VAT rules apply as normal, and a VAT-registered business in another member state is invoiced under reverse charge.

Yes — that is what the On-premise & Custom edition is. It has no list price because it does not have one: how many facilities, whose hardware, who administers the database and what response time you need all move the number. Write to us and we will quote it.