Your lighting network shouldn't belong to your CMS supplier

Open integration should create commercial choice

In many traditional deployments, one decision quietly settles several others. The central management system determines which controllers can be used. The controller determines which integrations are practical. Those choices then shape the supplier relationship for the length of the asset life — often fifteen or twenty years.

Lumino is built to support controller-gateway integration using the publicly available TALQ protocol. The significance is not the protocol name itself. It is that the management platform can be separated from the controller supplier, so software and hardware can be procured as two decisions rather than one.

Choose controllers on merit

Where a compatible gateway interface is available, an authority should be able to compare controller options on price, performance, availability, service and suitability for the network — not only on whether the incumbent management system happens to support them.

That is a practical improvement rather than a universal one. Implementations differ, and any new gateway integration needs testing and engineering work before it is put into service. The point is that the work is possible and can be scoped, instead of the answer being that the platform simply does not support the hardware you want.

Migration should not force a wholesale replacement

Replacing a management platform and the field hardware at the same time is expensive, disruptive and difficult to justify while existing equipment is still serving its purpose.

Open interfaces and a clearer separation of responsibilities make a progressive route more realistic: bring the existing estate into Lumino, then introduce new hardware as units are replaced, areas are upgraded or capital allows. Migration still takes planning, data work and testing, and we will be direct with you about the effort involved. It does not have to be a single large replacement programme.

Fewer overlapping systems

Central management and asset management are usually bought separately, licensed separately and reconciled by hand. The same asset exists in both, the records drift apart, and staff time goes into deciding which system is right.

Lumino combines central management and asset-management functions in one operational environment. Control information, asset records, faults and work sit together, which removes duplicated data, duplicated licences and a great deal of manual reconciliation.

Lower operational cost

The economics of connected lighting are usually discussed in terms of hardware cost. In practice, much of the ongoing cost is operational: watching alarms, interpreting faults, correcting inventory, checking energy figures and rebuilding the same reports each month.

Automation, integrated data and Valiciti Operations are intended to reduce that repetitive work — identifying what matters rather than presenting everything, and producing routine reporting without someone assembling it. How much that saves depends on the network, the data quality and the operating model, so we would rather look at your situation than quote a figure.

Independence is not the same as avoiding suppliers

Street lighting is specialist infrastructure and good suppliers create real value. The objective is not to remove suppliers from the picture, or to treat every long relationship as a problem.

The objective is a normal commercial relationship: the authority keeps access to its own data, retains meaningful choice over future hardware and software, and can change one part of the arrangement without unpicking all of it. Suppliers who are confident in their service have little to fear from that. It tends to be the arrangements that depend on difficulty of exit that resist it.