omino Book a presentation Companies usually weigh three types of solution and each has its context. But only one approach closes the whole improvement cycle: from shop-floor reports through maintenance, OEE and analytics to complaints, risk and the action plan with an effectiveness check.
22 criteria across 7 areas · we assess the product core, not custom integrations · for specific products the scope varies by module and version
The boundaries have blurred in recent years and vendors keep adding adjacent features, yet at their core they stay specialized. iDomino has meanwhile grown up: alongside TPM, analytics and the action plan it now carries a full CMMS, shift-level production control, 8D complaints and a risk register.
IBM Maximo · SAP PM · Infor EAM · MaintainX
Siemens Opcenter · Plex · Tulip · Power BI · Tableau
Maintenance (CMMS) · TPM · Production control · Analytics · Complaints · Risk · Action plan
Seven areas, three categories. Each area heading links to the detailed iDomino module page, where the features are documented with screenshots from the app.
| Feature | CMMS / EAM | MES + BI | iDomino Platform |
|---|---|---|---|
| 01 · Maintenance (CMMS) | |||
| Preventive maintenance plan | Calendar, BOM, intervalsCore of the product, intervals by time or counter. | Out of scopeMES can supply status data; the plan lives in another system. | Triggers on machine countersOperating hours, cycles or pieces, with lead time and a calendar fallback 'or every X days'. |
| Asset register, spare-parts store and orders | CMMS/EAM domainAsset, BOM and spare-parts management. | Out of scopeMES works with the product, not the maintenance asset. | Assets, MRO store, orders, stocktakesStrict store permissions, minimum stock, consumption tied to orders. |
| Inspections and legal obligations | By module and versionOften handled by the PM calendar or an add-on. | Out of scope | Deadlines, results, compliance overviewDocuments for the inspector and insurer on the asset card. |
| Technician capacity planning | Usually enterprise modulesThe planning board tends to be a higher edition. | Out of scope | Fund − absences − reservePull planning with a visual overload warning. |
| Fault reporting from the floor | Often via a paid mobile moduleSAP PM / Maximo via Fiori, Innovapptive and others. | No maintenance workflowMES captures machine status but doesn't manage the repair. | QR tag, mobile, kioskAnyone can report without an account; escalation of overdue orders by level. |
| 02 · TPM and operator engagement | |||
| Operator autonomous maintenance | The operator isn't the primary userCMMS targets maintenance technicians. | No TPM processMES tracks performance, not autonomous tasks. | Checklists and a kiosk at the machineChecks, lubrication and start-up tasks with a verifiable history. |
| Escalation of reports to the right team | Work-order workflowRouting by configuration, outside the shop-floor kiosk. | Out of scope | Escalation matrix by event typeResolve myself / Escalate to the team, measured response time. |
| 03 · Shift-level production control | |||
| Shift control and hourly output | Out of scopeCMMS doesn't run production. | Production work-order and dispatchingCore of MES. | Shifts, output, shift handoverPlan vs. actual by the hour, handover with KPIs and open reports. |
| Machine data collection (OPC UA, PLC) | Out of scope | MES domainSCADA, PLC, product genealogy. | Operator output and reportsProduction control runs on shop-floor data. Machine connectivity, batches and part traceability will come with the follow-up MES module, which is on the roadmap. |
| Real-time OEE | No production dataCMMS tracks assets, not line performance. | If the MES layer existsWithout MES data, BI won't compute OEE on its own. | From reported data, no configurationOEE = A × E × Q from pieces, standards and downtime; shift overview and LCD panels on the floor. |
| 04 · Analytics | |||
| Loss Pareto and downtime heatmaps | Just an incident logLoss root-cause analysis is missing. | Requires custom developmentAn analyst has to build the data model. | Out-of-the-box, drill-downTop 10 faults, day × hour heatmaps, aggregation with a cumulative share. |
| Financial impact of losses in CZK | Not available | Custom model in BI | Downtime, scrap and lost profit in moneyMost expensive days, Top 5 savings potential, cost prediction. |
| Reports for every role | Generic report builderEveryone gets the same report. | An analyst has to build itA strength and a weakness at once. | Operator, foreman, management ready-madeEach role has its own view without configuration. |
| AI analysis of recurring problems | Not available | Your own data-science project | AI finds and names recurring problemsCause breakdown by Ishikawa 6M, quantified lost time, a click through to the action plan. |
| 05 · Quality, non-conformities and risk | |||
| Digital audits (5S, LPA, VDA 6.3) ↗ | No formsThe audit as a process isn't part of CMMS. | Out of scopeAudits are done by specialized apps. | AMS module with photo documentationVDA scales, points, corrective actions, AI audit summary. |
| 8D complaints: supplier and customer | Out of scopeSupply non-conformities are handled by a QMS or e-mail. | Out of scope | 8D both ways with a supplier portalNCR and 8D PDF, tracked D3/D6/D8 milestones, itemized costs, a scorecard. |
| Risk register per ISO 9001 ↗ | Out of scope | Out of scope | Risks and opportunities, FMEA per AIAG-VDAP×D matrix, the 4T strategy, actions in action plans, risk-reduction KPI. |
| 06 · Action plan (PDCA) | |||
| Action plan with accountability and deadlines | A work-order isn't PDCAIt tracks task completion, not closing the root cause. | Typically in Excel or Jira / TrelloOutside MES, manually linked to data. | Action levels and escalationImmediate, corrective and preventive actions, costs and savings. |
| Root-cause analysis (5 Whys, Ishikawa) | Not in the CMMS coreMostly free text. | Only in a BI template or plug-inData yes, structured analysis missing. | Structured, linked to the taskFrom reports, audits and analytics in one click. |
| 07 · Implementation and growth | |||
| Time to the first measurable result | 3-12 monthsEnterprise rollout longer, modern CMMS faster. | 3-9 months depending on the data layerDepends on machine connectivity. | 4-8 weeksPilot line within 4 weeks, plant rollout 6-8. |
| Mobile interface for the shop floor | Paid add-onFiori, Innovapptive, Sigga and others. | Dashboard view onlyA BI mobile app, not a workflow. | Mobile, QR reporting, kiosk modeLarge tiles for touch terminals at the machines. |
| New features | Usually a paid dev projectConsultant, partner or in-house development. | Vendor-driven roadmapWaiting for a release, or custom code. | We add it at no extra chargeManufacturing specifics within the subscription; every new feature available to all. |
You usually pay separately for each change, or you wait years for it in the vendor's roadmap. A custom integration requires a consultant or in-house development, and each new version brings further costs.
Development is part of the price. You get new features at no extra charge and automatically once they're ready. If one is missing, we add it to the roadmap and share it with all clients. Features purely specific to your operation we can add through custom development.
A short decision framework with no marketing spin. If your operation falls into several categories at once, a combination makes sense.
Yes, both paths work. Some customers keep their CMMS for asset management and add iDomino as a layer for operators, OEE and the action plan. But we can now also replace a CMMS fully: the Maintenance module covers assets, work orders, the spare-parts store, inspections and technician capacity.
By default we migrate the machine tree, the preventive maintenance plan, the spare-parts store and the last 12 months of fault-report history. Action plans in Excel are imported via a template. Migration is part of onboarding and isn't charged separately.
A pilot line runs within 4 weeks of signing; a full rollout in one plant typically takes 6-8 weeks. We handle multi-plant organizations within 4 months. It depends on how many lines and roles you involve at once and the state of your input machine data.
Each module can be bought on its own. You might start with the Action Plan or Complaints and add other modules later. We can source OEE from your MES, or from shift output in the Production control module.
The interface is designed for exactly this case: large tiles, photo documentation, QR reporting without logging in and a kiosk mode on shared terminals at the machines. Operators are usually onboarded within an hour and use the system from day one.
A pilot on one line is a short-term contract; you end it with no long-term commitment. The decision on a full rollout comes only after evaluating the pilot. We typically see an OEE increase of 3-8 percentage points within 6 weeks; the result depends on the operation's starting state.
The platform runs in the cloud and as an on-premise instance on the customer's private server or in their MS Azure. We support IP whitelisting, SSO and role-based access. Encryption and audit logs meet common enterprise IT requirements.
60 minutes online. We'll show you the platform on your data and compare it with what you use in production today.
Book a presentation