Skip to main content

IoT

Seeing what happens in the field, as it happens

A successful IoT project does not begin with the choice of a sensor, but with the question: what decision will this measurement make possible?

The problems we address

What brings you here

You discover the breakdown when production stops

Nothing measured beforehand: no temperature, no vibration, no hour counter. The failure is simply endured.

Readings are manual and far apart

Someone walks round once a day to read a level or a temperature. Between two rounds, nobody knows.

The cold chain cannot be proven

In a dispute, there is no timestamped record of the temperature during transport.

The network is unstable on site

Solutions that assume a permanent connection lose data at the first outage.

Deliverables

What you receive

  • IoT consulting and feasibility study
  • End-to-end design of connected solutions
  • Sensor integration and instrumentation of existing equipment
  • Edge gateways with local buffering
  • Telemetry platform and real-time monitoring
  • Rules engine and automatic alerts
  • Predictive maintenance based on the measurements
  • Energy monitoring and asset tracking
  • Web and mobile IoT dashboards
  • Integration with ERP, CMMS and reporting tools
  • Device fleet management and remote updates

Benefits

What it concretely changes

Interventions triggered by measurement

A threshold crossed creates a work order automatically instead of waiting for the next inspection.

A record that stands up

Timestamped measurements, retained: the proof exists in the event of a dispute or an audit.

Collection continues without a network

The gateway stores locally and catches up on reconnection. No data is lost to an outage.

Connectivity cost under control

The radio technology is chosen against real volume and coverage, not by default.

Features

What we can do in this area

  • Device registry with a unique identity and provisioning
  • Digital representation of the equipment (current and desired state)
  • MQTT ingestion secured by mutual authentication
  • Rules engine: thresholds, missing signal, correlations
  • Downlink commands to the equipment
  • Time-series storage with a retention policy
  • Device health monitoring and loss-of-communication alerts
  • Remote firmware deployment with signing
  • Integration APIs and webhooks
  • Logging and observability across the fleet

Our approach

How we go about it

  1. Use case and decision

    What decision or action should the measurement trigger? Without a clear answer, we do not fit a sensor.

  2. Site survey

    Radio coverage, available power, environmental constraints, access for maintenance.

  3. Instrumented pilot

    A small number of pieces of equipment over a set period, to validate the measurement and the whole chain.

  4. Scaling up

    Bulk provisioning, an installation procedure, and training for the maintenance teams.

  5. Operations

    Fleet monitoring, asset management, updates, and replacement of devices at end of life.

Architecture

How it is built

IoT architecture is designed end to end, from the sensor through to the business application. Each layer has its own security and resilience constraints.

  1. Field

    Sensors and equipment, power supply, mechanical protection, environmental conditions.

  2. Acquisition

    Microcontrollers, or existing controllers queried over Modbus or OPC-UA rather than replaced.

  3. Edge

    A gateway with a local buffer, reliable timestamping and a store-and-forward mechanism.

  4. Transport

    Ethernet, Wi-Fi, BLE, Zigbee, LoRaWAN, NB-IoT, LTE-M, 4G/5G, private network or satellite as the need dictates.

  5. Platform

    MQTT broker, idempotent ingestion, rules engine, time-series storage, command handling.

  6. Operations

    Dashboards, alerts, integration with CMMS, ERP and reporting.

  7. Security

    A unique identity per device, X.509 certificates, mTLS, secure boot, signed firmware, rotation and revocation.

Diagram

The full chain, layer by layer

Each layer has its own security and resilience constraints. The diagram scrolls horizontally on a small screen.

Architecture IoT de bout en bout, du capteur à l’application métierCinq étages : terrain (capteurs, microcontrôleurs et automates), passerelle edge avec mise en tampon, réseau de communication, plateforme (broker MQTT, moteur de règles, stockage de séries temporelles) puis exploitation (alertes, tableaux de bord, intégration ERP, GMAO et BI). Un canal descendant renvoie les commandes et la configuration vers la passerelle.1 · TERRAIN2 · EDGE3 · TRANSPORT4 · PLATEFORME5 · EXPLOITATIONCOMMANDES ET CONFIGURATION (VOIE DESCENDANTE)Capteurs etéquipements4-20 mA · I²C · ModbusMicrocontrôleurset automatesModbus · OPC-UAPasserelle edgeBuffer · store-and-forwardRéseau decommunicationLoRaWAN · NB-IoT · Wi-FiBroker MQTTet ingestionmTLS · X.509 · QoS 1Traitement etmoteur de règlesDéduplication · seuilsStockage deséries temporellesRétention · agrégatsAlertes etnotificationsE-mail · SMS · webhookTableaux de bordtemps réelWeb · mobileIntégrationERP · GMAO · BIAPI REST · webhooksTRANSVERSE — IDENTITÉ PAR APPAREIL · mTLS · ROTATION DE CERTIFICATS · OTA SIGNÉ · JOURNALISATION · SUPERVISION DE FLOTTE
Architecture de référence. Le choix exact des composants dépend du volume de données, de la couverture réseau disponible, de la criticité et du budget : nous cadrons ces arbitrages avant toute réalisation.

Technologies

Relevant technologies

  • MQTT
  • Mosquitto
  • Node-RED
  • Modbus
  • OPC-UA
  • LoRaWAN
  • NB-IoT
  • LTE-M
  • Zigbee
  • ESP32
  • Arduino
  • Raspberry Pi
  • C embarqué
  • Python
  • Node.js
  • Socket.io
  • PostgreSQL
  • TimescaleDB
  • InfluxDB
  • Redis
  • RabbitMQ
  • Grafana
  • Docker
  • TLS / mTLS
  • X.509
  • Sentry

Frequently asked questions

Frequently asked questions

IoT and connected solutions

Do our existing controllers have to be replaced?
Rarely. Most industrial controllers already expose their data over Modbus or OPC-UA. We query them rather than replace them.
Which radio technology should we choose?
None suits every case. The choice depends on range, power consumption, data volume, available coverage, acceptable latency and cost. We settle it after the site survey.
What happens if the network goes down?
The gateway keeps collecting and stores locally. On reconnection it resends the missing messages; ingestion is idempotent, so any duplicates are discarded.
How do you secure the devices?
Each device has a unique identity and its own certificate. There is never a shared key across all the equipment. Certificates can be revoked individually.
Can you supply the hardware?
We specify suitable hardware and work with suppliers. You can buy it directly, which keeps you the owner of the fleet.

Africa Tech Services

A project around “IoT”?

A first thirty-minute conversation, with no commitment. We will tell you plainly whether we are the right partner — and if not, we will point you elsewhere.