Open where it matters: the driver, the field bus, your systems.
A platform you cannot leave is not a platform. iLCS uses standard interfaces towards the luminaire, takes in third-party devices over the usual field protocols, and hands your data to your own systems in formats you already read.
Site gateway — installed site
Downwards, sideways and upwards.
Interoperability is not one property. It matters in three different places, and a system can be open in one and closed in the others — so we list them separately.
Standard sockets, standard drivers
This is the level where a closed system traps you into one catalogue of luminaires. Ours does not.
The protocols a site already speaks
The cabinet controller is the site integrator: what it can read, the platform can store, chart and alarm.
Your data, in your tools
Including the export you would use on the day you decide to leave. That is the point of it.
A connector, not a custom project each time.
Each source is wrapped in a connector that extracts, converts units and loads into one data model. Periodically, on an event, or on request.
The gateway or the cabinet controller talks to the device in its own protocol, on site.
Units, scales and timestamps are converted so a reading means the same thing wherever it came from.
Everything lands in one history with a place, a time and a unit — which is what makes cross-service reports possible.
Out through the API, the stream or the export — and onto the same map as the lighting.
The nodes run on our mesh, and that is the point.
Our luminaire nodes speak standard interfaces towards the luminaire, so any D4i driver from any manufacturer works. On the radio side they run our own mesh, and they do not share it with another vendor's controllers.
Because the network has to be fast
Reaching every device in real time, deciding a lighting class at the roadside and applying it across a group in milliseconds needs the radio, the routing and the firmware designed together. A generic control network cannot do it, which is why nobody does adaptive lighting on one.
What actually protects you
Not interchangeable radios — a standard socket, a D4i driver, an open API and an export in standard formats. Those keep your luminaires, your data and your next tender free, which is what a lock-in clause is really about.
And everything above it is open
The field network is ours; the interfaces around it are not. Modbus, M-Bus, OPC-UA, LoRaWAN and OCPP come in; REST, MQTT, Kafka, ODBC, SFTP and standard exports go out.
Name the system you need to talk to.
A GIS, a BMS, an ERP, a city platform, a meter you already own. We will tell you which interface fits, and whether it is configuration or development.