The platform

Every module. One data model. Nothing to integrate.

Assets, inspections, work orders, spare parts, sensors, rules, control rooms, dashboards, reports and AI all share the same asset record, the same permissions and the same audit trail. A sensor reading can start a rule, an inspection, a work order and a board report without a single integration project.

See use cases
The modules

Everything an asset-intensive organisation runs on

Grouped the way the work flows: build the asset model, operate day to day, orchestrate live operations, then gain insight and optimise.

Build

Operate

Orchestrate

Insight & Optimize

See it connect

One reading, every module it touches, no integration project

This is what one data model means in practice. Press play and follow a single sensor reading through the platform.

  1. T+0 sIoT & devices

    A tilt sensor on Bearing B2-West posts 0.93°

  2. T+1 sAutomation Studio

    The threshold rule matches three consecutive readings

  3. T+2 sOperations rooms

    A Critical, Structural broadcast reaches three control rooms

  4. T+40 minInspection workflows

    An engineer files a special inspection rating the bearing C4

  5. T+55 minAsset hierarchy

    On approval, the bearing and span become Restricted; lanes follow

  6. T+2 hWork orders

    A P1 job is planned with drawings and defect photos attached

  7. Next dayDashboards & reports

    The executive board shows one more restricted structure

  8. AlwaysAudit trail

    Every step above is on the record, in order, with who or what caused it

Illustrative sequence on sample data.

Why one platform

The real cost of asset software is the integration between tools

Buying a CMMS, an inspection app, an IoT portal, a procurement tool and a BI product means five data models, five security models and an integration layer nobody owns. Mintema puts one model under all of them.

One record, every view

An asset carries its structure, condition, inspections, work, parts, readings, documents and cost in one record.

Automation reaches everything

A rule can react to a reading, a status, a date or a field on any asset, and act across the platform.

Configured, not customised

Asset types, forms, inspections, workflows, rules, dashboards and reports are configured by your team.

One security model

One organisation tree, one set of permissions, one two-factor sign-in, one audit trail.

Built for large data

Server-side grids, indexed fields and typed tables keep the platform fast at enterprise volumes.

Arabic and English

Every module works in Arabic and English with right-to-left layouts.

Compare & start

Three ways to run asset operations

CapabilityPoint solutionsTraditional CMMS / EAMMintema
Asset modelHow deep the register goes. Different per tool Fixed levels Unlimited component tree
New asset classesWhat it takes to add one. Another tool A vendor project Designed in the No-Code Studio
InspectionsWhat drives condition. A separate app Fixed checklists Your forms and scoring drive condition
Failure impactWhat happens to dependants. Unknown Manual Cascades and rolls back
Spare partsWhere stock lives. In the ERP Add-on module Stores and purchasing linked to work
SensorsWhere readings go. A vendor portal Add-on On the asset, driving rules
AIHow questions are answered. None Add-on chatbot Governed assistant with sources
LanguageFor Arabic-speaking operators. Varies English-first Native Arabic and English
Getting started

From kickoff to live operation

A typical first phase. Scope and timing are agreed with you during discovery.

  1. Weeks 1-21

    Model

    Organisation tree, asset types, component templates and roles configured with your team.

    • Organisation tree agreed
    • Asset types designed
    • Roles and permissions
  2. Weeks 3-42

    Load

    Your register imported and validated, documents attached, positions checked on the map.

    • Validated import
    • Documents linked
    • Map review
  3. Weeks 5-63

    Inspect and maintain

    Inspection types, work order types and approval chains configured and tested.

    • First inspections approved
    • Work orders live
    • Spare parts set up
  4. Weeks 7-84

    Operate

    Sensors connected, first rules and control rooms live, dashboards assigned.

    • Rules in production
    • Rooms online
    • Handover to your administrators
FAQ

The platform, answered

Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.

No. Modules are switched on per need. Many organisations start with the register and inspections, then add work orders, supply chain and IoT.

Yes. Grids are paged and filtered on the server, designed asset types get their own typed and indexed tables, and the platform has been load-tested with tens of thousands of structures and their components.

Yes. Asset types, forms, inspection types, scoring methods, workflows, rules, dashboards and reports are configured without code by your administrators.

Yes. Every module works in Arabic and English with right-to-left layouts.

Mintema covers the same core: register, inspections, work orders, inventory and purchasing. It adds standards-based condition, impact cascades, IoT, a command center, built-in BI and a governed AI assistant on one data model, configured without code.

SEE IT ON YOUR OWN DATA

Every module,
one conversation.

A solution engineer will walk one of your assets through the whole platform: register, inspection, work order, spare part, sensor and dashboard.

Talk to sales