No-Code Studio
Pump, motor and compressor types with their own nameplate fields.
Mintema is maintenance and condition monitoring software for rotating equipment. It keeps the nameplate, components and history of each machine, watches vibration and temperature, and plans work on condition.
Vibration and temperature trends sit in one tool, nameplates in another and repair history in a third. Without the full picture, machines are overhauled too early or fail without warning.
Every part below is configured in the platform without code: the asset type, its structure, the inspection form and scoring, the work, the sensors and the dashboards. Click a step, or let it play.
Designed in the No-Code Studio: a nameplate section, operating data in kW, flow and head, and a seal-type list.
Pump, motor, seal, impeller and bearings as components, created from a template per model.
Technicians rate each component and record vibration, temperature and leakage as measurements.
Early warnings become planned corrective orders, with the seal or bearing reserved from stock.
Vibration and bearing temperature sensors on each critical pump and motor.
Component condition, critical defects, maintenance backlog and cost trends.
Illustrative configuration on sample data. Your fields, forms, scales and workflows are designed with your team.
One platform and one data model, so the inspection, the work order, the spare part, the sensor and the dashboard all refer to the same asset.
Pump, motor and compressor types with their own nameplate fields.
Vibration and temperature on the component they measure.
Rules that update condition and warn the engineer.
Component ratings with measurements.
Critical seals and bearings with reorder rules.
Planned repairs with the part reserved.
The value is measured in fewer failures, less wasted effort, lower risk and better use of budget.
Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.
Condition-based maintenance services a pump, motor or compressor when its vibration, temperature or other readings show a change, instead of on a fixed calendar, so work happens when it is needed and failures are caught earlier.
Yes. Pump, motor and compressor types are designed in the No-Code Studio with the exact nameplate fields you need.
Any sensor or gateway that can post JSON over HTTPS or publish over MQTT, such as vibration, temperature, current or run-hour sensors.
Yes. Automation rules can set component technical condition and asset health from readings, and notify the responsible engineer.
Yes. Labour, parts and services from work orders post to the asset, so cost per machine is always current.
Vibration, temperature, current, pressure and flow sensors can post readings to the machine or component they measure, and threshold rules raise alerts and work orders.
By planning work from measured condition and history rather than the calendar alone, and comparing cost and failures across machines of the same type.
We will configure this use case on sample data during the call: the asset type, an inspection form with its scoring, a work order type and a rule.