Custom IIoT SaaS Platform for Data Acquisition, Traceability and Monitoring
IoT Portal SaaS Project Takeover Critical Infrastructure
From recovery to evolution:
Transforming an industrial IoT gateway into a robust SaaS platform
Redesign of the platform architecture and deployment of new operational modules, carried out without service interruption to ensure the continuity of activities.
Context
SECTOR
Supervision of critical infrastructures (Pipelines, water pipes, ...)
PERIMETER
SaaS/On-premise platform, multi-language, multi-tenant
MISSION
Recovery, maintenance and evolution
The profession of our client leads them to install thousands of sensors in the field. They continuously measure electrical and physical parameters of infrastructures in order to detect any anomalies before they compromise their integrity.
Our client operated a multi-tenant industrial web platform that enabled the centralization, supervision, and analysis of data from sensors deployed in the field, while ensuring complete data isolation between different operators. The platform relied on a data collection engine responsible for communicating with the equipment and transmitting data in real-time.
We have taken over an existing project to ensure its maintenance, sustainability, and the development of new features.
A functional platform requiring technical consolidation
The platform fulfilled its functions, but its architecture greatly limited its scalability. A large part of the business logic, data access, and interactions with third-party services was concentrated in monolithic controllers, making developments complex, testing difficult, and maintenance more risky.
The lack of automated tests made each evolution particularly risky and significantly increased the cost of interventions. Before undertaking the redesign, we had to correct several malfunctions in the existing system, highlighting the concrete impact of technical debt on timelines, maintenance costs, and the platform's ability to evolve.
To these constraints were added the specificities of the IoT ecosystem: heterogeneous devices, synchronization mechanisms specific to each type of sensor, and a high requirement for data coherence and reliability.
Before — inherited architecture
Tightly coupled architecture · Insufficiently separated responsibilities · Monolithic components · Lack of automated testing.
After — restructured architecture
Modular architecture · Separation of responsibilities · Automated quality control · Secure deployments · Asynchronous processing.
Listen
The needs of field operators, administrators, and compliance teams were different. The analysis of usage allowed for the design of features that are truly tailored to operational constraints: complete traceability of alert processing and continuity of the measurement history, including in the event of a sensor failure.
The main constraint of the project was to carry out a complete redesign of the architecture without interrupting the operation of the platform. In an industrial environment, supervision must remain continuously available.
Operational Gains
The project was structured in two phases: redesigning the platform's architecture and then gradually deploying new features on this modernized foundation.
ALERTS & THRESHOLDS
Threshold monitoring setup, automatic alert generation, and complete tracking of their processing through a recorded and commented acknowledgment.
AUTOMATED REPORTS
Generation of dynamic documents, on demand or scheduled, with export and multilingual support.
AUDIT LOGS
Complete and filterable history of user actions, meeting regulatory traceability requirements.
CONFIGURABLE EXPORTS
Customizable exports by tenant
CORRECTIVE ACTIONS
Alert lifecycle management, from their opening to their closure, with integrated tracking for reporting.
MANUAL ENTRY
Continuity of measures in case of sensor failure and complete traceability of data origin.
Résultats
| Before redesign | After redesign | |
|---|---|---|
| Architecture | Monolithic controllers, mixed responsibilities and no genuine service layer | Strict separation, with each component independently modifiable and testable |
| Form security | Limited validation of user input | Centralised validation and standardised security across all user input |
| Interface | Monolithic front-end architecture with no component modularisation | Independent front-end components, each dedicated to a specific business function |
| Quality control | No automated testing · No quality controls · No validation process before deployment | Static code analysis, continuous integration and automated quality control before every release |
| Scalability | Every change to the platform carried a high risk of regression | Controlled development, improved release quality and regular deployments |
| Reporting | N/A | Scheduled or on-demand multilingual reports available in multiple formats |
| Regulatory traceability | N/A | Comprehensive, searchable and filterable audit log that meets industry requirements |
| Field continuity | Gaps in measurement history in the event of sensor failure | Manual data entry available, with the source of each data point fully traceable |
Does your project look like this?
Taking over a fragile existing system, IoT integration, traceability requirements — let's talk about it!