---
title: 'Interacting with the production server'
section: 'Reference'
weight: 1
description: How equipment is registered on the IIoT Platform and which telemetry, metering, and lifecycle data flows between the platform and the production server.
related:
  - integration
  - equipment
  - basic-modules/modules
  - architecture/data-collection-layer
---

The production server and the IIoT Platform exchange data in both directions: the production server registers manufactured equipment on the platform, and the platform reports back the operational data needed to monitor reliability throughout the equipment's life cycle.

## Registering equipment on the platform

To register manufactured equipment automatically, the production server transfers its data to the 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 or 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 the unit is linked to.
   - **Consumer category** (industrial, commercial, household).
   - **Resource-supplying organization** — the energy resource supplier.

## Data transfer to the production server

To monitor reliability and analyze equipment operation throughout its entire life cycle, the platform transfers the following data to the production server:

### Regularly transferred parameters

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

- **Session duration** — duration of the 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** — reason the session started:
  - _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 the transferred data.
  - _Daily archive_ — time range of the transferred data.

### Transferring data from the platform to devices

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

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

## Interaction diagram

The block diagram below illustrates the data flow between the platforms and the production server.

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

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

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