HMI software

process controlfor conveyorrotating machinery

Industrial Automation
Product overview
Banalytics' Event Manager evaluates conditions from acquired sensor and DAQ data, and from your processing module's outputs, then triggers Actions, such as Modbus writes, relay control, MQTT publish, or notifications, closing the loop from sensing to automated response without a full SCADA or PLC programming stack.

Problem this solves
Research and DAQ teams need simple automated responses to sensor conditions, such as alarms, relay triggers, or logging start/stop, but full SCADA systems are expensive, vendor-locked, and overkill for one use case.

How it works
Field devices or processing module output → Event Manager evaluates rules (thresholds, patterns, health states) → an Action fires (Modbus write, GPIO relay, MQTT publish, notification, dashboard alarm) → Event History logs the action taken.

Architecture example
Site A (Test Bench): vibration sensor + DAQ → Event Manager → Modbus write to a PLC relay (stop conveyor) on threshold breach.
Site B (Remote Pump Station): pressure sensor → Event Manager → MQTT publish to SCADA and a Telegram alert to the on-call engineer.
All sites → Banalytics Dashboard · Event History · action audit log.

Who this is for
Research, DAQ, and measurement teams;
instrumentation engineers;
plant reliability teams who need conditions to trigger real actions automatically, not just alerts.

Key features
Event Manager rule engine for thresholds, patterns, and health states.
Modbus write actions for controlling relays, valves, and similar devices.
GPIO relay triggers for direct hardware control.
MQTT publish and notification actions for downstream systems and people.
Event History as an audit log of every action taken.
Vendor-independent transport tiers and a locked module-interface contract.

Technical specifications
Supported protocols: Modbus (RTU/TCP) for write actions, MQTT for publish, ZeroMQ for module integration, ONVIF/RTSP/USB for device acquisition, OPC UA, I2C
Rule engine: Event Manager evaluates thresholds, patterns, and health states against acquired data.
Actions: Modbus write, relay/GPIO trigger, MQTT publish, and notification, fired automatically when a rule condition is met.
Audit: Configurable event and action history, with selected events routed to database storage and retained according to the configured retention policy.
Module interface: your rule logic and thresholds are defined per engagement; Banalytics evaluates and acts on them.

Way of work
Phase 0: Technical demo (free). Architecture walkthrough using your own use case, no data required.
Phase 1: PoC (always free). Validate the trigger and action rule logic (Modbus write, relay, MQTT, notification) using mock or replayed data; no real hardware, no device-specific engineering.
Phase 2: Funded Pilot. Connect real devices and actuators and validate rule firing and action execution live. Commercial once a scoped rollout-assistance engagement is purchased, or a custom device/3rd-party software integration is required.
Phase 3: Production. Harden and scale to additional lines or sites; ongoing support agreed separately.