Integrating Aviot with existing SCADA and PLC systems

A good technical alarm doesn't compete with the SCADA or the PLC running the process: it complements them. The SCADA runs operations 24/7. The technical alarm guarantees that when the SCADA fails, someone finds out. This note covers the most common integration patterns between Aviot and existing industrial automation.

Pattern 1: Aviot as an independent watchdog

Simplest and most recommended to start. Aviot monitors the same variables the SCADA watches but with its own probes and inputs, in parallel, without coupling to the PLC.

Pros:

If the PLC or SCADA fails, Aviot keeps alerting.
No PLC programming changes required.
Meets redundancy requirements demanded by some certifications.

Typical case: poultry farm with a Siemens S7 panel running fans and cooling. Aviot goes in with its own per-room temperature and humidity probes, and reads the panel's auxiliary contacts in parallel.

Pattern 2: Aviot reads PLC signals

The PLC already runs the process logic and has digital outputs reporting state. Aviot reads those outputs as voltage-free digital inputs.

Pros:

Reuses signals the PLC already generates.
Aviot adds the call/SMS/app alerting channel the PLC doesn't have.

Watch out: if the PLC fails, the signals fail with it. Hence good practice is to combine Pattern 1 + Pattern 2 — some variables monitored independently, others read from the PLC.

Pattern 3: Aviot exposes data to the SCADA

The plant's central SCADA wants Aviot's readings alongside everything else. Aviot offers:

REST API with token auth: the SCADA polls readings or subscribes to events.
Webhooks: when an alarm fires on Aviot, it POSTs to the SCADA endpoint.
Scheduled CSV export: for simple non-realtime integrations.

The SCADA doesn't control Aviot — it just reads. Aviot keeps independence to guarantee alerting even when the SCADA is down.

Pattern 4: Aviot integrated with the integrator's platform

In poultry and pig, large integrators (Avícola, Vall, Cobb, etc.) increasingly require digital data in their platforms. Aviot can push:

Historical readings in JSON or CSV via API.
Real-time alarm events via webhook.
Threshold configuration synced with the central platform.

The integrator sees each farm's status without waiting for an audit. The farm meets the contract's digitization requirements.

Wiring best practices

Always isolate Aviot inputs with opto-relays when coming from the PLC, to avoid ground issues.
Use voltage-free contacts, never share commons.
Shield probe pairs if cabling runs near power panels.
Distribute critical inputs across at least two breakers: if one trips, the other stays alive.

What Aviot doesn't do (and shouldn't)

Aviot is an alarm, not control. It does NOT move actuators, does NOT start the generator, does NOT modify process logic. That's the PLC's and SCADA's responsibility. Aviot watches and alerts — that responsibility boundary is what keeps the system independent and certifiable.