navigate openesc close
Book a demo

Municipal engineering, smart city programs, digital transformation offices

Specify a platform that is still current in ten years.

Engineering and smart city teams have to justify the investment, pick a technology that outlives the tender, and avoid adding one more platform to a stack that is already siloed.

What stalls an engineering decision

I want a solution that will still be relevant in ten years.
  • The investment has to be defended

    Council wants the number before the project, not after. A system that measures neither energy nor maintenance leaves the business case resting on a vendor estimate.

  • Choosing a technology that will last

    The network standard chosen today has to still be supported halfway through the life of the fixtures. Betting on a closed protocol turns the next phase into a replacement.

  • One more platform, one more silo

    Lighting, parking, traffic and environmental sensors each arrive with their own portal and their own data model. The data never joins up.

Illustrative interface
Dimonoff | SCMS
Online
99,4 %
Faults
3
Energy today
412 kWh
Groups
18

Dimming profile, tonight

Open alarms

NodeIssueAge
RME-04812Lamp failure14 min
RME-01197Power fault1 h 20
RTM-00934No response3 h 05

What gets specified

1,000,000
Nodes or sensors per system
1 platform
Lighting, sensors and third-party nodes
6-18 months
Signature to full operation

Laval: 37,000 luminaires on one platform

Laval converted 37,000 streetlights and connected the lighting platform to the Oracle asset, Intelight traffic and Esri GIS systems already in place. Savings of $2.75M CAD and 15 million kWh a year, 10,607 t of CO2 avoided, payback in five years.

37,000Connected luminaires

Laval, Canada

Laval converted 37,000 street lighting fixtures under a $34.5 million contract and connected the lighting platform to the asset management, traffic and GIS systems the City already ran.

Read the case study

The three questions at this table

Technical

How does the platform integrate with the systems we already run?

Integrations in production include ArcGIS/Esri, Oracle EAM, Azure, PowerBI, Grafana, Intelight MAXVIEW 2.0 and Parknet/Parquery. A bidirectional REST API covers the rest. Laval runs the lighting platform alongside the Oracle, Intelight and Esri systems it already had.

Financial

How do we demonstrate the value of the program?

On measured data. In Laval, converting 37,000 streetlights returns $2.75M CAD and 15 million kWh a year, avoids 10,607 t of CO2 and pays back in five years. LED conversion cuts energy by 50 to 70% and truck rolls by 30 to 40%.

Operational

What happens as the network grows or standards change?

One system manages up to 1,000,000 nodes or sensors in real time. Wi-SUN, DigiMesh, LTE-M, Ethernet and cellular coexist natively in the same network, and third-party NB-IoT or LoRaWAN sensors can join it too. Firmware is updated over the air across the fleet, with a change notice and customer approval.

Bring us the spec you have to write.

A deployment of 10,000 to 50,000 luminaires takes 6 to 18 months, in phases. Send your network constraints and your GIS and asset systems and we will map them to what already runs.

Book a demo