Works on phones and tablets The entire tool runs in the browser, even on a small screen. Check-in and sign-off are carried out at the machine, not afterwards in the office.
Machines and sub-assemblies Each machine with its own identification, location and status, divided into sub-components such as a feeder, conveyor belt, tank or motor.
Faults and downtime Report what is wrong, who is working on it and how long the machine has been out of action, including a photo of the fault, the diagnosis, the repair and the result.
Preventive maintenance Recurring definitions automatically generate tasks, and the interval advice shows where your actual practice deviates from your plan.
Cleaning and clearance Once repairs have been carried out, a separate cleaning task is required. The machine is only released once this has been signed off.
Reports Per machine, per technician and for management, including total and average downtime and machines experiencing problems.
Self-hosted on your own server Your machine, fault and maintenance data remain within your own environment. No compulsory cloud service and no monthly subscription.

Why this tool?

Downtime costs the most and is the least well documented. In practice, this information is scattered across a whiteboard, a group chat, an Excel file and the memory of the engineer who happened to be there. By the end of the year, it is no longer possible to work out which machine has been out of action for the longest, what the cause was, or whether that maintenance interval is actually correct.

This is rarely down to a lack of willingness. It’s because the log is entered on a PC located two halls away, and by the time that’s done, the engineer is already on to the next machine. That’s why Maintenance Tool works just as well on a phone or tablet as it does on a desktop. The report is submitted right where the fault is, with a photo attached straight away, and signing off a task doesn’t require a detour to the office. It simply runs in the browser, so there’s nothing to install and nothing to update on the devices themselves.

Maintenance Tool records that chain of events at the very moment the work is carried out. A fault is linked to a machine and to the specific component that was actually faulty. The downtime has a start and end time. The repair has a cause, a person who carried it out and photographs. As a result, reporting is not a matter of filling in forms after the event, but simply a summary of what has already been entered.

How it works

From fault report to clearance. Someone reports the fault, specifying the machine, sub-assembly, priority and photos, and initiates the downtime. A technician is assigned and begins work, at which point the status changes to ‘In progress’. Upon completion, the technician records the cause, the work carried out and the completion time, and indicates whether cleaning is required. If so, a separate cleaning task is created for an operator. Only once this has been signed off is the machine released. Every step leaves a trail that you can later view in the machine report.

Preventive maintenance. A maintenance definition describes recurring tasks: the interval, instructions, next due date and person responsible. The scheduler creates tasks based on this and flags up anything that is overdue. Completed work is stored as a separate event, so a new round never overwrites the history. If actual practice consistently deviates from the set interval, this is flagged as a recommendation. You decide whether to accept it.

Roles. The administrator, maintenance manager, technician and operator each have their own interface and their own buttons. Access rights are not only hidden within the interface but are also verified on the server side for every restricted action.

Also included

  • Planning with preventative maintenance, follow-up tasks and manual tasks all in one place, with overdue work given priority.
  • Photos for each step, up to 20 per upload, categorised by fault, diagnosis, repair and result.
  • Backup and restore of the database and attachments in a single file, with a safety backup taken before a restore is carried out.
  • Archiving rather than deleting, so that machines, sub-assemblies and former users remain identifiable in the existing history.
  • Six languages (Dutch, English, German, French, Spanish and Polish), configurable per user, with entered machine data and notes remaining untranslated.
  • System status showing whether the database, storage, migrations, scheduler and backups are in good working order.

What it isn’t

This is deliberately not an ERP system. It does not include stock management, procurement, time tracking or invoicing. The tool does one thing: it records what happens to your machines and makes that information accessible. Anything that doesn’t contribute to this has been left out, because every extra field is a field that won’t be filled in on the shop floor.

It’s also not a service that runs on my servers. You install Maintenance Tool on your own server, which means your machine, fault and maintenance data remain within your own environment. No compulsory cloud, no monthly subscription, no supplier holding your data. You pay a one-off fee for the licence and, optionally, an annual fee for updates.

Nor are there any sensors or links to the control system. The input comes from people, and the tool is designed to ensure that this input is quick and easy: a short title, the correct machine, a photo attached – and that’s it.

Frequently asked questions

Who is this tool intended for?

For technical services and manufacturing companies with their own machinery, which currently keep track of breakdowns and maintenance in Excel, on paper or in a shared folder.

Can there be more than one fault on a single machine at the same time?

Yes. Each fault is dealt with separately. Resolving one does not affect the other.

How is downtime calculated?

Based on the start and end times you record for the fault. As long as no end time has been specified, the downtime continues until the present moment.

Will the recommended interval automatically change my schedule?

No. The warning simply indicates that the set interval differs from actual practice. An authorised user accepts the change deliberately.

In which languages is the tool available?

In Dutch, English, German, French, Spanish and Polish. Each user sets their own language, so a Polish operator and a Dutch manager can both work in the same system, each in their own language. Machine data, descriptions and technical notes entered into the system are not translated.

Does it work on a phone or tablet?

Yes. The tool runs in the browser and adapts to the screen size, so a technician can report a fault, add photos and sign off on a task whilst on site. There’s no need for an app that you have to install or update first.

Where does the tool run?

On your own server. There’s a web installer that deactivates itself after installation, and a cron-compatible scheduler for tasks and automatic backups. You’ll need PHP, MySQL and a cron job – that’s all.

What happens to data from machines or people who are no longer with us?

These are deactivated or archived, not deleted. As a result, the existing history remains accurate and can be restored at a later date.

Where is my data stored?

In your own environment, on the server where you install the tool. Machine, fault and maintenance data never leave your server. No compulsory cloud, no resale, no tracking.

Do I pay a monthly subscription fee?

No. You pay a one-off fee for the licence. Updates are optional and cost 79 euros per year. If you stop paying for them, the tool will continue to work as normal.

Give it a go yourself or apply straight away?

Log in using the demo credentials and click through everything, or request a licence. You’ll receive the installation files, a brief user guide and help with setting up your first machines. Runs on your own server; one-off payment.

Or email me directly at info@siekman.io. You get a reply from me, not from a sales department.