Skip to main content
Event-Driven Automation

If This, Then That.
At Industrial Scale.

Automate your factory without writing code. Our visual Rule Engine lets you define complex logic flows, triggers, and alerts that execute in real-time at the edge.

Why Proxus Rule Engine?

Define logic once, run it where it matters—at the edge, in real time. Proxus Rule Engine listens to UNS topics and executes decisions in milliseconds, without writing custom code if you don’t want to.

  • Event-driven—rules react to data changes instantly; no polling storms.
  • UNS-native—same tags feed dashboards, AI, and rules; no duplicate models.
  • Edge execution—keep safety logic and interlocks running even if the cloud is slow or offline.
  • Low-code and code—start visual, then extend with C# functions for advanced scenarios.

Typical triggers

  • Value/threshold change (temp, pressure, vibration)
  • State transitions (running → stopped, manual → auto)
  • Time window breaches (cycle > takt, downtime > SLA)
  • Derived metrics (OEE drops, SPC violations)
All driven by UNS topics; same inputs drive dashboards and alerts.
Trigger
Tag Value Change
Machine_01.Temp
Value > 90°C
Action 1
Send Notification
Slack & Email
Action 2
Stop Machine
Write PLC: Stop_Cmd

How it works

Rules subscribe to UNS topics. Evaluations run close to the data, and only relevant actions are sent—to alerts, integrations, or control if you allow it.

  1. Pick triggers: tag changes, thresholds, timers, or derived metrics.
  2. Add conditions (and/or), comparisons, time windows.
  3. Attach actions: notify, log, route to integrations, or write to control (governed).
  4. Deploy to the edge for sub-second reaction; keep running offline.
  5. Monitor rule performance and outcomes.

Outputs

  • Alerts (email, chat, SMS)
  • Writes to UNS topics or control (if permitted)
  • Outbound to integrations (Kafka, MQTT, HTTP, DB)
  • Audit logs of decisions
Use the same logic across plants by reusing templates and UNS mappings.

Use Cases

Standardize decision logic across lines and sites without rewriting PLC code.

Safety interlocks

Apply guard conditions and emergency stops at the edge for critical assets.

Quality & SPC

Trigger actions when measurements drift, before bad product accumulates.

Energy optimization

Shut down idle consumers or switch profiles based on demand windows.

Maintenance triggers

Escalate alerts or open work requests when vibration/temperature cross limits.

Security and governance

Rules follow the same guardrails as your data and control policies. Keep critical writes gated; keep everything else read-only and observable.

  • Scoped actions—writes to control are optional and governed; alerts stay read-only.
  • Audit trails—rule executions and outcomes are recorded.
  • Offline resiliency—logic keeps running at the edge; actions replay when links return.

What stays consistent

  • Same UNS topics feed rules, dashboards, and AI
  • Reusable templates across plants
  • Option to keep control paths read-only
Standardize logic without fragmenting configurations.

FAQ

Common questions on latency, safety, and portability.

Does it run at the edge?

Yes. Rules execute close to the data so safety logic continues even offline.

Can I mix visual rules with code?

Yes. Start visual, then call custom C# functions when needed.

How do we prevent unsafe writes?

Keep control actions gated; defaults can be read-only. Approvals and audit logs help enforce policy.

Do we need new tag models?

No. Rules subscribe to existing UNS topics—no duplicate tag dictionaries.

Ready to automate decisions in milliseconds?

Build rules once, run them at the edge, and keep control safe. Reuse the same UNS topics across dashboards and AI.

Read Rule Engine Design See How Edge Keeps Rules Online