A plant is a small city that nobody treats like one.
Internal roads, yards, high-bay halls, a perimeter to keep lit and a row of switchboards feeding all of it — usually on separate systems, or on no system at all. iLCS puts them on one network, inside the fence.
High-bay lighting under control — installed site
Four jobs, one network.
Each of them is usually bought separately, from a different supplier, with its own portal. On a site they all sit within a few hundred metres of each other.
Roads, yards and car parks
Lighting that follows the shift and the movement instead of the clock: full output where trucks manoeuvre, reduced where nothing is happening, faults reported before the morning walk-round.
Lighting →Halls and warehouses
High-bay and linear luminaires driven over DALI-2 / D4i or 0–10 V, in zones that match the aisles — with the same controllers and the same platform as the outside.
Luminaire nodes →Switchboards and metering
Consumption per department or per section from MID meters, technical alarms on protections and doors, remote switching with local lock-out for whoever is working on the board.
Energy & Infrastructure →Security lighting
Light that comes up where presence is detected, and that can work with the cameras — including on sites where nothing is allowed to leave the fence.
How it runs offline →On an industrial site, "it needs the cloud" is usually a no.
Plant IT does not want another system phoning home, and production does not accept a light that depends on an internet link. iLCS was built the other way round: the decisions are taken on the network itself.
Schedules, dimming, presence reactions and safety fallbacks run on the nodes and on the cabinet controller. A lost link changes nothing on the floor.
The platform can run on your own servers, or a site can be operated entirely locally from an industrial touch panel, with no cloud at all.
One mesh covers the site; the devices talk to each other, not to an operator's network.
High mast over a yard — installed site
What the first project usually is.
The three that recur, and where each one tends to start.
Industrial parks and estates
Internal roads and lots, run by a developer or a consortium. Starts like a municipality: lighting control first, then the cabinets, then the services — flooding basins, weather, air.
Plants and warehouses
Mixed indoor and outdoor. Usually starts from the electrical side — consumption per section — and grows into the lighting, because the network is already there.
Perimeters and secure sites
Lighting that supports surveillance, presence radar on the fence line, local operation with no external connection. Here the requirement is written as a constraint, not as a feature.
We have industrial installations in Europe and in South-East Asia — parks, plants and logistics sites. We do not publish their names or their figures here: the energy results we publish are the ones we measured with a declared baseline, and those come from road lighting.
Ask for a reference →What we ask before quoting.
Six answers are usually enough for a sized proposal.Extent, internal roads, yards and the buildings to be covered — a satellite view with the fence drawn on it will do.
How many, indoor and outdoor, and whether the drivers are DALI-2 / D4i, 0–10 V or neither.
How many, what is inside them, and which lines you want measured separately.
When the site is actually in use — it decides how much there is to gain outside those hours.
Whether data may leave the site, and who is allowed to reach the system from outside.
Meters, BMS, cameras, access control: whatever speaks Modbus or has an API can usually stay.
Start with one building, or one yard.
A single cluster with its own gateway is enough to measure what the whole site would do — and to show plant IT exactly what does and does not leave the fence.