Automation Studio

Let the routine checks run themselves

Draw a rule once: when this happens, check that, then do this. Mintema runs it on every change, every sensor reading and every schedule, so overdue work, expiring dates and alarms never slip through.

All modules
Capabilities

Automation that understands assets

Generic workflow tools do not know what a component, a condition or a sensor is. Mintema rules do, so they are quicker to build and safer to run.

Draw the rule

Connect a trigger, conditions and actions on a visual canvas. Read it like a diagram.

Triggers that matter

A status or condition change, a date coming up, a sensor reading, a device going offline.

Scheduled checks

Run a check every morning, every Monday or every month, and send one summary instead of fifty alerts.

Alert the right people

Notify a person, a role or a team, by app notification, email or control-room message.

Update the asset

A rule can change an asset’s condition or health score when a limit is crossed.

Every run on record

See what each rule did, when and why. Test any rule by running it manually.

See it live

Four rules teams build in their first week

Each one is a trigger, a condition and an action. Pick one to see how it works.

Pick a ready-made rule

Illustrative rules on sample data. Run counts are examples.

How it works

How a rule works

  1. 01

    Choose when

    Pick the event: a change, a date, a reading, or a schedule.

  2. 02

    Add conditions

    Only continue if, for example, the asset is critical or the reading is above a limit.

  3. 03

    Choose what happens

    Write the message in Arabic and English, pick who receives it and how urgent it is.

  4. 04

    Switch it on

    The rule runs on its own from then on, and every run is recorded.

Deep dive

Why rules beat reminders

One message, not fifty

Summaries instead of alert storms

A scheduled check collects everything it finds and sends one clear message, such as "14 assets overdue for inspection", with the list attached.

  • One summary per check
  • Limits on alerts per rule
  • Any schedule you like
312 MATCHES FOUNDOne row per overdue assetAggregatecap: 1 per personMESSAGE · MONDAY 07:00312 assets are overduefor inspection in your region.SEE THE LISTRegion manager 1SENTRegion manager 2SENTRegion manager 3SENTRegion manager 4SENTRegion manager 5SENTRegion manager 6SENT
One message, not fiftyIllustrative
Speaks your language

Rules that understand your assets

Conditions use the fields your teams already know: criticality, condition, region, sensor values. No scripts, no mapping.

  • Asset and part fields
  • Sensor values
  • Arabic and English messages
RUN HISTORY07:00Overdue inspectionsAsset · 3 recipientsSENT02:14Sensor thresholdAsset · 3 recipientsCRITICAL01:48Asset out of serviceAsset · 3 recipientsSKIPPED00:30Device offlineAsset · 3 recipientsRETRY23:10Overdue inspectionsAsset · 3 recipientsSENT22:02Sensor thresholdAsset · 3 recipientsSENTRUN DETAIL · 02:14TRIGGERReading receivedTilt 0.93° on Bearing B2CONDITIONAbove limit × 3Branch: YesACTIONBroadcast · CriticalRooms A and BACTIONNotify on-call role3 peopleDuration 1.4 s · logged 02:14:09
Speaks your languageIllustrative
Safe to trust

Automation you can rely on

Every run is recorded with its result. You can test a rule by hand before switching it on, and rules cannot loop endlessly.

  • Run history
  • Manual test runs
  • Built-in safeguards
RULE · TEMPERATURE ALERTTriggerConditionActions plug into the same canvasNotifySame canvas and run logAVAILABLEEmailSame canvas and run logAVAILABLEBroadcastSame canvas and run logAVAILABLECreate work orderVia the extension pointROADMAPWebhookVia the extension pointROADMAP
Safe to trustIllustrative
Business value

What automation is worth

Every rule replaces a check someone had to remember. Multiply that across hundreds of assets and dozens of people.

Hours saved every week

Checks for overdue work, expiring dates and offline devices run on their own.

Nothing slips through

Rules never forget, never go on leave and never miss an email.

Faster response

Critical changes reach the right people the moment they happen.

Owned by operations

The people who know the process build the rules, without waiting for IT.

How it usually works
With Mintema
01Monitoring
Someone checks a report on Monday.
A rule checks every morning.
02Alerts
Fifty emails, one per record.
One summary with the list.
03Logic
Scripts written by IT.
Visual rules owned by operations.
04Proof
Nobody knows if it ran.
Every run recorded.
FAQ

Automation, answered

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

No. Rules are drawn on a visual canvas.

Changes to assets and their parts, approaching dates, sensor readings, devices going offline and scheduled checks.

Send app notifications and emails, message the control room and update an asset’s condition or health score.

Scheduled checks send one summary, and each rule has a limit on how many messages it sends.

Related modules

IoT & devices

Sensors on the assets they measure, with alerts the moment something goes wrong.

 Command center

Alerts to your control rooms by severity, with every response on record.

 No-Code Studio

Create your own asset types, forms and approvals without code or developers.
IoT & devices Command center
BUILD ONE WITH US

Your rules,
running live.

Tell us the check your team does by hand every week. We will build it as a rule with you during the call.

Talk to sales