Platform specification

Protocol

MQTT 3.1.1 / 5.0

Security

SSL/TLS

Architecture

Edge + Cloud Server

Database

SQL Server + Local

Sensors

WIO / HY-VT / ETH-A2

Architecture

Acquire on board, view ashore

Field data is acquired and processed locally by an ETH-A2 edge gateway. If the link drops, data is buffered on board and forwarded automatically when it returns. Uplink is MQTT over TLS into the Edge + Cloud Server.

Coverage

Every critical system on board

Main engine

Speed, load, cylinder and exhaust temperatures, lube oil pressure and temperature — abnormal trends surface early.

Generators

Voltage, current, frequency, power and running hours per set, supporting load sharing and maintenance scheduling.

Fuel system

Tank levels, consumption rate, daily and per-voyage totals, cross-checked against flow meters.

GPS / AIS

Position, heading, speed and track on the same time base as engine-room data, so events can be replayed in context.

Environment

Engine-room temperature and humidity, bilge levels, fire and access signals, all under one alarm rule set.

Oil condition

With WIO water-in-oil detection and HY-VT2000 vibration sensing, lubrication and machine health join the same picture.

Design notes

Why it is built this way

Disconnection is normal

Links at sea drop. Acquisition and logic run on board; data is buffered locally and forwarded on reconnect, so a poor satellite window does not leave a gap.

Field first, cloud second

Data comes from HOYAN gateways and sensors, not a generic IoT box. Sensing, gateway and platform from one source means a field problem can be traced end to end.

Encrypted end to end

MQTT over TLS with self-signed or uploaded certificates. Ship operating data is commercially sensitive and should not cross the public internet in clear text.

Want to know how far V-IOT can integrate?

Every ship is a different mix of equipment. Send us your equipment list and existing monitoring setup, and we will assess the integration scope and propose an architecture.