Skip to content
Mesonify

Module

Rules

Detect problems early. Monitor vibration, temperature, and pressure in real time - and act before failures happen.

Request a demoAll modules
Rules DeviceTracked valueStateRESETEXPORTCREATE RULERuleDeviceTracked valueFires whenTriggeredCycle time too longPress 2Cycle timeAbove 3.5 s2 timesBearing runs hotCNC 3TemperatureAbove 70 C1 timeSpindle load highCNC 3Spindle loadAbove 85 %Not yetBelt vibrationConveyor 1VibrationAbove 4.5 mm/s3 timesAir pressure lowPaint boothPressureBelow 5.5 barNot yetCoolant level lowCNC 4Coolant levelBelow 20 %1 timeMotor draws highMixer 4Power drawAbove 42 kWNot yet1-7 of 2420Rows Per Page

What it does

Threshold logic

Watch any tracked value with conditions you define: above, below, equals or true-false comparisons.

Captured at the point of work

Values recorded when technicians complete scheduled events trigger rules instantly, closing the loop from device to work order.

Pre-configured rule events

The generated fault or activity arrives ready to action, with name, type, priority, classification and description preset.

Deadlines on alerts

Each rule event carries a completion deadline in days and is flagged red when it slips.

Checklists included

The corrective procedure ships with the alert as a step-by-step checklist with info text and files.

Trigger tracking

A filterable rule register shows how often each rule has fired and when it fired last.

How it works

  1. Pick the value

    One rule watches one tracked value on one device: a pressure, a temperature, a count of hours, a text state or a yes and no flag.

  2. Set the comparison

    Greater than or less than for numbers, equals or not equals for text, is true or is false for flags, against the comparison value you choose.

  3. Prepare the response

    The event the rule will create is written in advance: name, Fault or Activity, classification, group, priority, whether files are required at completion, description and checklist.

  4. Let it fire

    The value arrives when a technician completes scheduled work, or from another system through the API. If the comparison holds, the event is created and lands in the queue.

Condition monitoring

Where the values come from

A rule is only as good as the reading behind it. Three routes bring readings in, and all three trigger the same rules.

  • Sensors on the machine

    Temperature, vibration, pressure, flow or level sensors on IO-Link, PROFINET or Modbus, read by your gateway and sent to Mesonify.

  • Technicians at the job

    A value written down when a scheduled event is completed is checked against the rules the moment it is saved.

  • Systems you already run

    Anything that can call the REST API can send readings for a device: one endpoint, one API key.

Whichever route a value takes, the rule compares it against the threshold you set and creates the job you prepared.

  • IO-Link
  • PROFINET
  • Modbus

Part of

CMMS, Maintenance Management

See the platform

Works with

Modules are switched on per customer. Start with the ones you need and add the rest when you are ready.

See Rules running on your own plant.

Ask for a demo with your own devices, parts and jobs.

Request a demoAll modules