Rules & Automation

Turn device data into automated operational action.

Build rules in a visual editor, with no code. Combine metrics, parameters and calendar conditions to automatically send commands, raise notifications or update device parameters.

Book a DemoTalk to an Expert

Vision Smart Platform rule engine: metric, threshold and calendar conditions triggering commands, notifications and group actions
No codeA visual builder with predefined operators
Any scopeThe same rule model on one device or a whole group
Under controlPrioritize, pause and resume automation without deleting it

Rules that turn data into action.

The logic that runs your infrastructure lives in the platform, not in a script somewhere. Conditions read what devices report and how they are configured; effects act back on them. Both are configured in the same visual editor, without writing or deploying custom code.

Visual rule builder
Conditions, logical blocks and effects assembled in one modal, with a live JSON preview of what the rule will evaluate and execute.
Metric and parameter conditions
Compare reported values or configuration fields using the operators defined in Administration: greater than, less than, is, is not.
Time and calendar logic
Minute, hour, day, day of week, month and year operators, plus Holiday and IsHoliday, tied to the legal-holidays register.
Nested AND/OR blocks
Group conditions into blocks and combine them logically, for scenarios a single comparison cannot express.
Commands as effects
Send a command to one device or to a whole group, change a parameter, or raise a notification.
Priority and status
Every rule carries a name, a description, a priority and an active or inactive status, so operations can order and pause automation without deleting it.

Three kinds of input, one condition language.

A condition can read what the device reports, how it is configured, and where the clock and the calendar stand — all combined with the same set of operators.

Metrics
What the device reports
  • Reported values, with their data type and unit of measurement
  • Compared with greater than, less than, is, is not
  • The same metric definition across every device of that version
Parameters
How the device is configured
  • Custom fields inherited from model and version
  • Local values set on the individual device
  • Usable as placeholders inside the rule itself
Time & calendar
When it applies
  • Minute, Hour, Day, DayOfWeek, Month and Year
  • IsLeapYear for date arithmetic
  • Holiday and IsHoliday, read from the legal-holidays register

What a rule can do.

Effects run when the conditions evaluate true. They act on the platform registry and on the field, through the same integration chain a manual command would use.

Command to a device
Execute a command template on the device that triggered the rule, with its parameters already filled in.
Command to a group
Apply the same action to every member of a device group, in one step.
Notification
Raise a notification for the operators who need to know that the condition occurred.
Parameter change
Write a new value into a device parameter, so the next evaluation starts from the updated configuration.

Every rule is readable before it runs.

The builder shows the logic as you assemble it and how the engine will evaluate it, so automation stays visible and inspectable before activation. Conditions, blocks, effects and the JSON the engine reads are all on the same screen.

NameEvening dimming profile
Priority1
StatusActive
Conditions
AND
MetricIlluminanceless than12
OperatorHourgreater than21
OR
OperatorIsHolidayistrue
OperatorDayOfWeekisSunday
Effects
CommandSet dimming levelonGroup · Main boulevard
NotificationEvening profile appliedtoOperations
JSON preview
Condition
{
  "and": [
    { "metric": "illuminance", "op": "lt", "value": 12 },
    { "operator": "Hour", "op": "gt", "value": 21 }
  ]
}
Effect
{
  "command": "setDimming",
  "target": { "group": "main-boulevard" },
  "params": { "level": 40 }
}

Illustrative example. The field names, operators and sections are the ones the rule builder exposes.

Automation you can operate.

Rules are operational objects, not deployments. They are listed, ordered, paused and audited like everything else in the platform — by the people who run the infrastructure, not by the people who built it.

Device or group
The same modal defines a rule on an individual device or on a group. A group rule applies to every member, so a fleet-wide behaviour is one object, not one per device.
Priority
Rules carry an explicit priority, so the order in which they are evaluated is a configuration choice rather than an accident of creation order.
Active or inactive
A rule can be paused and resumed without being deleted, and its status is visible in the rule list next to its name, description and priority.
Scheduled jobs
Alongside event-driven rules, scheduled jobs run on Quartz cron expressions and are bound to a functional module — for example the automatic clean-up of stored metrics and commands.

Let the platform handle the routine decisions.

Bring us a scenario you handle manually today — a threshold, a schedule, an escalation. We will build it as a rule in the visual editor and show you the JSON the engine evaluates.

Discuss your project