Home / Solutions
Five solution families, one technical core: reliable acquisition, legible supervision, defensible historisation, and a control layer that only opens once safety has been demonstrated.
01 · Airports
Airfield lighting is the last visual aid before touchdown. Its availability determines the operating category a runway can hold, and therefore the capacity of the airport. We supervise it circuit by circuit and lamp by lamp.
Real-time status of every circuit: on/off, brightness step, output current, voltage, fault, local/remote mode, insulation resistance historised with per-circuit thresholds.
Ingestion of individual lamp data from existing systems — power line carrier or otherwise — with unique identifier, position, type, status and operating hours counter.
At tiers P2 and P3: control per circuit or by pre-set runway configuration, safety interlocks, and management of control ownership between tower, electrical room and standby panel.
Automated reports on availability per lighting system, threshold breach events, supply changeover times — exportable and signed for the authority and for audits.
Consolidated status of every connected airport: active alarms, availability, work in progress, end-of-life equipment, cross-site comparison on standardised indicators.
Controlled lockout regime, per-equipment intervention log, and a mobile field application that works offline with deferred synchronisation for night crews.
No lights, no isolating transformers, no cables, no regulators, no civil works. We are not an airfield lighting manufacturer and we do not become their reseller: that neutrality is precisely what makes our abstraction layer credible. For hardware, we work with your existing suppliers.
02 · Industry
The same requirements as on a runway, applied to a production line: autonomy of the control level, fail-safe behaviour, traceability of every command, and no operational interruption attributable to the deployment.
Study, programming, commissioning and retrofit of programmable controllers. We work on new installations as readily as on ageing estates whose documentation has disappeared — in which case the survey is part of the package.
Migration of obsolete controllers with a parallel running period, and a rollback procedure tested before every cutover and executable in under 30 minutes.
A supervision system designed to be read at three in the morning by an operator whose attention is split: three-tier alarm hierarchy, avalanche suppression by root-cause grouping, contextual alarm help, low-luminance night mode.
Time-series database sized for continuous acquisition, with compression and retention policies per data type.
What shop-floor data actually enables: overall equipment effectiveness computed from verifiable machine states, energy consumption per line, and drift detection on measured quantities before outright failure.
Every recommendation exposes the measurement, the threshold and the trend behind it. A technician must be able to challenge it with their own readings.
Native support for Modbus TCP and RTU, OPC UA client, and digital I/O through a controller. Where a manufacturer's interface is closed or undocumented, the fallback is physical acquisition — less elegant, always available.
Read-only REST API over HTTPS, authenticated and versioned, for your third-party systems. Export to CSV, JSON and signed PDF.
03 · Ports, energy & water
A container terminal, a network of electrical substations or an estate of pumping stations pose the same problem as an airport network: many sites, far apart, heterogeneous, with small technical teams. The answer is the same — a single core, configured per site.
Supervision of terminal power, high-mast quay lighting, gantry cranes and handling equipment. Consolidated alarms and availability tracking per zone.
Supervision of normal and standby supplies, changeover time measured and compared against the maximum permitted, generator sets, UPS units, incomers and outgoing feeders.
Pumping stations, reservoirs, treatment plants: remote acquisition, local buffering of data and automatic resynchronisation after an extended link outage.
04 · OT cybersecurity
Our architectures follow the zones and conduits model of the IEC 62443 series, with a target security level justified per zone. The infrastructure we supervise often falls within the scope of Law 05-20.
Our security requirements in detailNo direct gateway between the operational and office networks. No direct internet exposure of any supervision component or below: all outbound traffic passes through a demilitarised zone under your control.
Remote access is enabled on request, time-limited, named, logged, recorded, and revocable unilaterally by the operator. No permanent tunnel back to the supplier.
Every action, login, configuration change and acknowledgement is timestamped and exported to an external collector, protected against deletion — including by an administrator.
By an independent third party before every commissioning, then annually. Critical and major vulnerabilities block acceptance — this is not an end-of-project formality.
05 · Services
A supervision system lives for ten to fifteen years. The quality of the service contract matters as much as the quality of the software — and that is where local presence stops being a sales argument and becomes something measurable.
| Commitment | Content |
|---|---|
| 24/7 support | Assistance in French and Arabic, technical team based in Morocco, named on-call roster. No offshore first line in a different time zone from yours. |
| Response times | Incident blocking operations ≤ 30 min · major incident ≤ 2 h · routine request ≤ 1 working day. Associated restoration times defined in the service contract. |
| Warranty | Three years on software and supplied hardware. Security patches included at no extra cost for the whole contract duration. |
| Long-term support | Commitment to spare parts availability and support for a minimum of ten years from commissioning. |
| Source code escrow | Source code deposited with a trusted third party, with release clauses in the event of supplier failure. |
| Skills transfer | After training, your teams handle day-to-day operation, site configuration and first-line diagnosis on their own. |
| Quarterly service review | Service indicators, incidents, improvement plan, product roadmap — with you, not for you. |
Day-to-day operation, alarm handling, lockout regime, degraded procedures. Two days, on a simulator before any access to the live system.
Diagnosis, mobile field application, fault-to-equipment correlation, return to service. Three days, including one day in the field.
Site configuration, permissions management, backup and restore, technical supervision, security. Five days.
Next step
Make and age of your regulators, whether an ILCMS is present, the protocol your controllers expose, the operating category you are targeting. With that, one meeting is enough for us to know what is feasible and which tier to start at.
