Buyer’s guide to EAM
How to evaluate asset management software without a two-year RFP: the seven questions that actually predict success, and the three that waste everyone’s time.
Security questionnaires, reference architectures, migration templates and honest benchmarks. We would rather you disqualify us early than discover a gap in month four of an implementation.
How to evaluate asset management software without a two-year RFP: the seven questions that actually predict success, and the three that waste everyone’s time.
The 11-day first deployment, phase by phase: discovery, data import, modelling, automation, go-live and admin certification.
MTTR, MTBF, PM compliance and backlog age benchmarks across utilities, transport, manufacturing and public sector.
REST and GraphQL references, webhook event catalogue, SDKs for Python, Node and .NET, and the sandbox environment.
SOC 2 Type II report, ISO 27001 certificate, penetration test summary, DPA, sub-processor list and architecture diagrams.
Field mapping templates for Maximo, Infor EAM, Fiix and MaintainX, plus the validation rules we run before import.
Practical posts on asset registers, maintenance strategy, inspections, sensors and KPIs. Latest: How to build an asset register you can trust.
Read the blogMove the sliders to match your operation. The model is indicative and uses conservative assumptions; your solution engineer builds a validated case from your own history during evaluation.
A CMMS manages maintenance work. Mintema manages the asset as an object — and work orders are one module among many, all sharing one data model.
| Capability | Typical enterprise CMMS | Mintema |
|---|---|---|
| One shared data modelAssets, work, IoT, finance and governance on a single object graph. | Modules ship with their own databases | One model, every module |
| Configured by your peopleHierarchies, workflows, forms and automations without vendor change requests. | Change requests & statement of work | Administrator-owned, certified in the first deployment |
| Multi-entity at row levelOne tenant, unlimited subsidiaries, isolated even through the API. | Separate systems or instances | Native multi-entity tenancy |
| Automation without developersVisual rules with dry-run validation against real history. | Workflow add-ons or custom code | Visual builder plus sandboxed script step |
| Native IoT & telemetryDevices as first-class assets with health, firmware and OTA. | Connectors bolted on | First-class devices, edge buffering |
| Live operations roomsSub-second streaming and NOC mode for control-room teams. | Not a feature | Live rooms, video wall included |
| On-premise & air-gappedContainerised private cloud, on-premise or fully air-gapped. | Vendor-specific options | Same release train, sovereign regions |
| Tamper-evident audit trailField-level log of every human, API and automation action. | Config logs only | Field-level, every source |
| Offline-first field appJobs, checklists and history executed and signed offline. | Limited cache | Full offline with conflict resolution |
A CMMS manages maintenance work. Mintema manages the asset as an object: its hierarchy, telemetry, inspections, costs, governance and the work performed on it. Work orders are one module of the platform, and every module shares one data model, which is why automation, reporting and audit work across all of them instead of stopping at the module boundary.
Yes. Registers, components, locations and documents are imported into the right organisation and asset type, and validated before go-live. Component templates and asset templates speed up repetitive structures, and the scope of historic data is agreed during discovery.
For the vast majority of rules, yes: triggers, conditions, branches, approvals and actions are configured visually and validated with a dry run against real history. When you do need code there is a sandboxed script step plus REST/GraphQL APIs and event webhooks — developers extend the platform instead of maintaining it.
One tenant per group, unlimited entities inside it, isolated at row level in the API — a user scoped to a subsidiary cannot query another subsidiary’s assets even through the API. Licences pool at group level so you are not penalised for modelling your org chart accurately, and contractors get free scoped accounts against assigned work.
The mobile app is offline-first: job plans, checklists, history and drawings are cached, work is executed and signed offline, then synced with conflict resolution. On the device side, edge gateways buffer telemetry locally and back-fill the time series after an outage, so trends have no gaps.
HTTPS with any JSON payload, authenticated by a per-device API key, and MQTT with two-way control widgets. Home Assistant connections are supported, and industrial protocols such as Modbus, OPC UA or BACnet connect through a gateway such as Node-RED. Devices are installed on assets, with install history, simulator profiles and rules on every reading.
Yes. Mintema ships as a containerised deployment for single-tenant private cloud, on-premise or fully air-gapped environments, on the same release train as our multi-tenant cloud. Sovereign regions available in the EU, UK, US, KSA, UAE and Egypt.
It stays yours and portable: full export of assets, hierarchy, work history, documents, telemetry and the audit trail in CSV, JSON and Parquet, on demand or scheduled, plus source code escrow on the Critical Infrastructure plan. Exit assurance is written into the contract — no hostage data, no export fee.
Security questionnaire responses, reference architecture, sample audit export, migration templates and a working session on your own assets.