Solutions Maintenance analytics
eMaint Explorer
Analytics on top of eMaint X4 maintenance data.
- Status
- In use
- Shape
- Web application
- Built with
- Go · Postgres · pgvector
Actionable Downtime Visibility
A CMMS records everything and explains nothing. The work orders are in there, the charges are in there, the PM schedules are in there — but answering "which assets are actually costing us" means exporting and pivoting until the question goes away.
eMaint Explorer syncs that data out into its own store and puts an analytics layer over it: fleet health scoring and KPI trending across sites and over time.
It also turns the work order history into something usable. Years of closed orders carry the actual solutions — which fix worked, what was replaced, what turned out to be the real cause. That knowledge normally lives with whoever was on shift, and leaves when they do. Here it stays searchable in plain language, so a technician who has never seen the fault can find the last three times somebody solved it.
Capabilities
Related
Vibration and condition monitoring for rotating equipment.
- Collects continuously — Sensor data from plant equipment into object storage.
- Keeps trends readable — Long time series reduced and aggregated so months of data stay legible.
- Warns early — Developing faults surfaced while the repair can still be scheduled.
Prints markdown straight to thermal receipt printers.
- Real formatting — Headings, bold, underline, tables, images, QR codes, paper cuts, and the buzzer, from a plain .md file.
- Any connection — TCP, USB, or serial, with any ESC/POS printer.
- Tunable output — Paper width and line density configurable per job.
- Scriptable — Reads a file or stdin, so it drops into an existing work order flow without glue code.