---
title: Interacting with the production server
description: How equipment is registered on the IoT platform and which telemetry, metering and lifecycle data flows between the platform and the production server.
weight: 2
---

## Registering equipment on the IoT platform

For automatic registration of manufactured equipment, data is transferred from the production server to the IoT platform.

### Data transferred during registration

1. **Telemetry parameters**:
   - **IMEI** — unique device identifier.
   - **ICCID** (optional) — SIM card identifier (relevant for devices with a pre-installed SIM or SIMChip).

2. **Energy metering equipment parameters** (when connected):
   - **Metering device type** (e.g. water, gas meter).
   - **Manufacturer** (name of the manufacturing company).
   - **Device model name**.
   - **Serial number** (if available).
   - **Network address** — ModBUS address.

3. **General metering unit information**:
   - **Metering unit name**.
   - **Consumer** — the organization or object to which the node is linked.
   - **Consumer category** (industrial, commercial, household).
   - **Resource-supplying organization** — the energy resource supplier.

## Data transfer to the production server

The following data is transferred to monitor reliability and analyze equipment operation throughout the entire life cycle:

### Regularly transferred parameters

- **Session timestamp** — date and start and end of transfer.

- **Session duration** — duration of data exchange (in seconds).

- **Battery charge**:
  - _Metrological part_ (in mV) — charge level of the battery responsible for measurements.
  - _Telemetry part_ (in mV) — charge level of the communication module battery.

- **Signal level (RSSI)** — communication signal level (in dBm).

- **Number of retries** — number of unsuccessful communication attempts before the current session.

- **Retry code** — error type for previous failures (e.g. _"No response from server"_).
- **Event ID** — session start reason:
  - _Scheduled_;
  - _Manual start_;
  - _Emergency event_.
- **Communication session status** — transfer result (e.g. _Successful_, _Connection failure_).
- **Archive data**:
  - _Accidents and abnormal situations_;
  - _Status of the shutdown device_ (if any).
- **Archive transfer periods**:
  - _Hourly archive_ — time range of transferred data.
  - _Daily archive_ — time range of transferred data.

### Transferring data from the IoT platform to devices

The platform sends the following commands and settings to the IoT devices:

- **Current time** — to synchronize the device's internal clock with the recording of deviations.
- **Next communication session time** — the scheduled time of the next data exchange.
- **Control commands** (e.g. activation/deactivation of the shutdown device) initiated by the operator.

## Interaction diagram

Below is a block diagram illustrating the data flow between IoT platforms and the production server.

```mermaid
architecture-beta
    group api(cloud)[Data transfer]

    service db1(database)[IoT Platform 1] in api
    service db2(database)[IoT Platform 2] in api
    service server(server)[Production Server] in api

    server:R --> L:db1
    server:L --> R:db2
```