AssetPulse brings your machines, breakdowns, repairs, preventive maintenance and spare parts together in one place. Every intervention is recorded, so you can see what breaks, how often, and why.
A demo environment on a sample plant — access is granted after a short conversation.
AssetPulse is a maintenance management system (CMMS) for manufacturing plants. It replaces notebooks, phone calls and scattered spreadsheets with a single picture: all your equipment and its hierarchy, every breakdown from report to closure, preventive maintenance on schedule, and the spare parts store.
It is not built to be filled in for the sake of a report. Everything is entered as it happens, by the person doing it — the operator reports the breakdown from their phone, the technician records what they replaced, the store sees what went out. The report falls out of the work instead of being a separate job at the end of the month.
Everything a maintenance department needs day to day — without assembling it from separate tools.
All equipment in a plant → line → machine → component hierarchy. Every asset carries its technical data, photos, documentation, spare-part list and its full repair history.
A QR label on the machine opens the right asset on the spot, with no list to search.
An operator reports a breakdown from their phone with a photo in seconds — no phone call, no hunting for someone. Maintenance sees immediately what stopped, since when, and how critical it is.
The report becomes a work order in one click and keeps the link back to it.
From assignment to closure: assignee, step-by-step checklist, parts used, time spent, work done and root cause.
Closing requires describing what was done — which is what keeps the history usable a year later.
Plans with intervals and a day/week/month calendar. Recurring service is created automatically instead of depending on someone remembering.
Templates with ready checklists for identical machines.
Stock by location, minimum levels, requests raised straight from work orders, movements and full history.
It shows what is missing before it is needed, not at the moment of the breakdown.
From purchase request through supplier order to goods receipt, tracking what has arrived and what is still outstanding.
The order goes out to the supplier by email straight from the system.
Sensor readings straight from the controllers plus vibration diagnostics, with alarm thresholds and measurement history.
An alarm from the machine can raise an inspection request by itself.
Reliability metrics, plus reading of the free text in work orders to surface repeating failures and propose concrete preventive maintenance against them.
Every figure links back to the orders behind it and can be checked.
High-voltage, work at height and hot work go through a permit that must be approved before the technician can even start.
An order cannot be closed while its permit is still open.
Larger undertakings — a rebuild, a new line, a relocation — are run with phases, tasks, budget and the work orders attached to them.
Roles from operator to administrator, departments, shifts and permissions that decide who sees and changes what.
Installs as an app on the phone, notifies by push and warns clearly when the connection drops.
Most plants already have a system of sorts — a notebook with the fitters, a spreadsheet with the planner, photos in a group chat and the rest in one person's head. The problem is not missing information; it is that the information sits in five places and none of them reconcile.
The metrics are computed from your own data — not typed in by hand and not rounded by eye.
The daily loop runs through four roles and never asks anyone to enter the same thing twice.
Scans the QR label on the machine or picks it from a list, describes the problem, takes a photo and says whether the machine has stopped. Under a minute, and it needs no training.
Sees every report ordered by criticality and by the state of the machine. Turns it into a work order with an assignee, a due date and a checklist — and, for hazardous jobs, a work permit.
Gets a notification on their phone. Marks the start, works through the checklist, requests parts from the store, uploads photos and finally describes what was done and what caused it.
The closed order extends the asset's history, consumes the parts from stock and feeds the metrics. Nothing is entered a second time for reporting.
Going live does not require stopping production, nor having everything ready on day one.
Assets are uploaded from a spreadsheet — lines, machines and components with the codes you already use. Nothing is typed in by hand.
Reports and work orders come first because they pay off immediately. The store and preventive maintenance follow once there is someone to keep them up.
QR labels are printed from the system and go on gradually, machine by machine, without waiting for the whole plant.
Each company sits on its own database, and the data can be exported to a spreadsheet at any time.
Nothing to install on the office machines. On a phone it is added as an app and opens full screen.
Each plant's data is physically separated, not mixed into shared tables with an owner column.
Bulgarian, English and German — each user picks their own, printed documents included.
Push on the phone, in-app and by email, with quiet hours per user.
Built for a mid-sized plant with a real maintenance department — where the machines number in the dozens, not the hundreds of thousands, and where one missed repair shows up in the schedule.
Sees what is weighing on the plant, where the hours go and which machines eat the budget. Has something to justify a spare or a replacement with.
Dispatches people by priority instead of by whoever called. Knows what is overdue and what is coming this week.
Carries their jobs in their phone, sees the machine's history before walking over, and requests parts without chasing the storekeeper.
Reports a problem in seconds and can then see what happened to it.
Knows what is below minimum and what a repair is waiting on, before it turns urgent.
Gets numbers that survive scrutiny, without waiting for someone to assemble them by hand.
It depends on how tidy the equipment data is. With a spreadsheet of the machines, the first work orders can be running within days. Full coverage with the store, preventive maintenance and labels usually takes a few weeks and is done in stages.
Operators, no. Their part is one screen: pick the machine, describe, photograph. Technicians and planners need a short introduction, typically an hour or two.
The app installs on the phone and opens without a browser, but saving data needs a connection. When the connection drops it says so clearly instead of pretending the entry was saved.
Yes. Assets and spare parts are uploaded from a spreadsheet. Past repair history can be imported if it exists in a structured form.
Each company sits on its own database rather than in shared tables with a company column. A user of one company has no technical path to another's data.
There is no technical limit. Operators who only raise reports are usually the largest group, and that has no effect on how the system runs.
No. It reads the free text of the work orders and proposes. A proposal becomes a maintenance plan only after a person accepts it, and it can be rejected.
The demo environment is a full copy of the system loaded with a sample bottling plant — 64 assets over four levels, maintenance plans, a stocked store and six months of repair history. Everything in it can be clicked and changed, without touching anything of yours.
Access is granted personally, after a short conversation. That way we know who is working in the environment, and we can point it at your own operation — what to show, where to start, and which of your problems would be solved first.
A short message with your company name and what you make. No requirements list needed.
Twenty minutes to understand how maintenance is organised at your plant and what is worth looking at first.
A personal account for the demo environment, in the role you care about — manager, planner, technician or operator.
For a demonstration on your own data, questions about rollout, or a quote.
