Proxus turns raw telemetry into actions. By running logic directly on the Edge Gateways, teams can react quickly even when the network is unstable.
Core Components
Automation in Proxus is built on two primary pillars:
Rules Engine
Watch tags and detect conditions or anomalies.
Actions & Notifications
Send alerts or trigger workflows when a rule fires.
How It Works
Automation Logic Pipeline
download
Ingestion
Gateways
schema
Mapping
UNS Context
rule
Evaluation
Rules Engine
notifications_active
Reaction
Actions
- Ingestion: Data arrives from industrial assets via Gateways.
- Mapping: Raw data becomes meaningful through Device Profiles and the Unified Namespace (UNS).
- Evaluation: The Rules Engine checks incoming packets against conditions or anomaly models.
- Reaction: If a rule triggers, one or more Actions run, such as sending an alert or filtering noise.
Why Edge-First Automation?
Cloud rules are useful, but some automation needs to happen close to the source. Proxus runs logic locally:
- Reliability: Safety-critical alerts can still trigger if the internet is down.
- Performance: Local processing keeps response times low.
- Cost: Filter and process data before it leaves your facility.