SCAIQ™ — a product of Ath Software Solutions Pvt. Ltd.

An architecture built for real time — and for real networks.

SCAIQ™ is a distributed platform of cooperating services — connected by high-performance streaming channels.

SCAIQ™ is a distributed platform of cooperating services — device connectivity (SCAIQ Connect), real-time data engine (SCAIQ Core), alarm engine (SCAIQ Alarms), data logging (SCAIQ Historian), and the web experience (SCAIQ HMI/Studio/Insights) — communicating over high-performance streaming channels.
Design principles

Six decisions that shape everything.

01

Services, not a monolith

Each concern (acquire, process, alarm, log, visualize) is its own service; scale, deploy, and restart independently.

02

Never block the data path

Non-blocking, buffered pipelines end to end; a slow consumer or a burst never stalls acquisition.

03

Expect the network to fail

Every link buffers, reconnects automatically, and delivers idempotently; recovery is designed-in, not bolted on.

04

One source of live truth

Every consumer — alarm engine, historian, every browser session — receives the same ordered, deduplicated stream.

05

Sub-second where it counts

Value-to-screen delivery batched at 200 ms by default.

06

Secure by construction

Authenticated, encrypted channels between services; role-scoped access at the edge of the platform.

The data journey

From field device to browser.

Field device → protocol driver (SCAIQ Connect) → streaming ingest → real-time tag model + expression evaluation (SCAIQ Core) → parallel fan-out: alarm evaluation (SCAIQ Alarms) · history logging (SCAIQ Historian) · live screen subscriptions (SCAIQ HMI) → browser render. Reverse path: audited operator commands → device writes with confirmation feedback.

Topologies

Single-server (all services co-located) · distributed (services across nodes) · multi-site (edge collection + central services).

Frequently asked questions

What are typical latency figures?

Sub-second UI delivery, with 200 ms default batching between the real-time engine and browser sessions.

What if the historian is down?

Buffered store-and-forward pipelines mean acquisition is unaffected — logging catches up once the historian returns.

Can services run on separate machines?

Yes — topology is deployment-time configuration, from single-server to fully distributed.

See SCAIQ™ live.

Bring your toughest SCADA questions. Our engineers will show you real screens, real alarms, and real trends.

Or talk to us directly: +91 84014 22388 ·sales@scaiq.com