RAHVA /TECHNOLOGY·

Independent architecture for industrial data

Rahva captures data directly from the physical behavior of machines — using dedicated sensors and data acquisition devices — and delivers it to the monitoring and analytics platform. This page explains the architecture layer by layer.

Technical consultationView the platform layers
01 / Overall architecture

The data path — from machine to analysis

Path inputMachines and lines that are already in operation — no changes made to them.
Data capture pointSensors capture physical signals of production activity from the equipment.
LAYER 01

Existing machines and production lines

The physical source of data — with no modifications.

LAYER 02

Added sensors

Mounted on equipment to measure status and production activity.

LAYER 03

Data acquisition devices

Collect sensor data and securely transmit it to the platform.

LAYER 04

Rahva IIoT platform

Centralization, processing, and storage of industrial data.

Real-time dataLive production status
Historical dataLong-term production memory
Monitoring, analysis, reportingActionable outputs
ConnectionData reaches the platform via the secure acquisition path — the machine itself is not involved in this path.
OutputDashboards and reports for operators, supervisors, and management — each role has its own view.
02 / Layer descriptions

Each layer's role at a glance

LAYER 01

Machines and lines

Every operating machine generates physical signals of production activity, downtime, and cycles. These signals are where the data begins.

LAYER 02

Sensors

Sensors are installed on the equipment and measure these signals without interfering with machine operation.

LAYER 03

Data acquisition

Data acquisition devices located alongside the line read data from multiple sensors, prepare it, and send it to the platform.

LAYER 04

Platform layer

Incoming data is centralized, processed, and stored; KPIs are calculated and events are recorded.

OUTPUT A

Real-time monitoring

Machine status, production counts, and current downtime — exactly what's happening on the floor right now.

OUTPUT B

Analysis and reporting

History, trends, shift comparisons, and structured reports for management decision-making.

03 / Key architectural principle

Separation of control and monitoring

The key architectural decision behind Rahva is this: the data acquisition layer operates independently of the machine control system. The machine continues to run as is; monitoring is added as a separate, non-intrusive layer.

Machine control layerOutside the data path

  • Existing control and automation system
  • Machine operating logic
  • Current production-floor workflows
  • None of these are changed for data collection

Digital monitoring layerAdded on top

  • Sensors installed on the machine
  • Data acquisition devices
  • Platform, dashboards, and reports
  • Addable and expandable, with no dependency on the control system
04 / Deployment

Deployed alongside production, not in place of it

An independent architecture also simplifies deployment:

No production downtime

Sensors and acquisition devices are installed on operating equipment — there is no need to stop the line.

No automation re-engineering

Since data is collected independently, there is no need to modify or rebuild the existing control infrastructure.

Step-by-step expansion

Start with one machine; the same architecture scales to a line, an area, or the entire factory without structural changes.

Have a technical question about the architecture?

In a brief consultation, our technical team will evaluate how well the architecture fits your equipment.

Talk to the technical team