Street Lights Management


Our customer is the main manchester, united kingdom-based totally issuer of a whole lighting fixtures control device that manages protection sports of avenue lights and different associated illumination gadgets everywhere and at any point. The purchaser’s enterprise additionally consists of assembling & selling devices like s6000 socket, external & internal DALI node, and sub-master. The consumer aimed to have a system comprising of four elements:

  1. Nodes (hardware) which become hooked up at each street lightening unit
  2. Sub grasp for a collection of nodes
  3. Masters for a set of sub-masters
  4. Back-workplace devise.

The purchaser also wished to aid the motion sensors and smart town answers by developing an application to manipulate the entire lightning version.

Enlisted are some of the essential demanding situations we faced at the same time as growing this smart machine:

  • Complexity in the knowledge of the existing system evolved the usage of Delphi.
  • Not able to control/communicate with all avenue lights gadgets because the consumer wanted to recognize the nitty-gritty of the applications consisting of set their on/off timings based totally on geographical locations, increase/decrease the brightness degree of each unit/street light primarily based on the need of the area and time duration, and so on. Without visiting and with the ease of dealing with it from the back office.
  • Not able to construct a clean interface to get entry to the lighting community gadgets (nodes and sub-masters) and to perform operations like sending switch degrees.
  • Make the device absolutely computerized so that it does not require any human intervention. At the equal time, the machine must have the ability to perform some of the operations manually.
  • Ability to specify a schedule for switching and the ability to add overrides for a particular length. The gadget has to automatically operate by following the schedules and operate the on and off switches.
  • Seamless connections for smart metropolis answers together with however now not constrained to photosensors, movement sensors. Smart town residents need to have control over switching based totally on their desires.
  • Lack of ability to synchronize statistics with third-party inventories and easily pluggable interface for various inventory structures.
  • Superior reporting and dashboards.
  • Third-party systems need to be able to get entry to the CMS gadget capability.
  • Make the fault-locating technique less difficult for operatives when they visit the site online for fixing the faulty nodes. Also assisting them to perform real-time operations I.E. Switch to the stage, soliciting for measurements to make sure the fault is fixed.
  • The machine developed should keep a track of the overall performance of the operatives and their performance and accuracy of solving the problems.
  • Make a sturdy CMS system such that the third-party CMS and lights networks should effortlessly be included with CMS or doors lighting fixtures networks.
  • Protection is the number one requirement and has to no longer be compromised at any point of verbal exchange.
  • Unable to provide statistics right away whilst something takes place inside the cms device I.E. device creation, data collection, lamp failures.
  • Unable to save Cost in hosting infrastructure.


Tools & Technology

  • ASP .NET
  • MVC
  • C#
  • WCF
  • Web API
  • IIS
  • SSRS reporting
  • Crystal Reports
  • Entity Framework
  • Microsoft SQL Server
  • Google maps
  • Open Street Maps
  • DevExpress dashboard
  • Azure MQTT
  • Azure SignalR
  • Azure App service
  • Azure AD and ADB2C Authentication
  • Azure App services


Shivagya Infosoft has created an intelligent web framework, the “Intelligent Light Management System,” which makes applications easy to reach from anywhere and at any moment through the internet. Google Maps, along with.NET (C#), is well suited for our project with Microsoft products like Azure Cloud services. Our solution includes many features that include but are not limited to:

  • Facility to view each node’s information and manipulate the identical statistics on Google Map and OpenStreetMap with an ability to carry out instructions.
  • Manage inventory of all styles of lighting units bought/acquired from a couple of companies.
  • Various heritage responsibilities to carry out some operations to make the device completely automated i.E. Amassing and reading measurements and elevating faults. Potential to run automatic historical past actions manually the usage of web programs.
  • Manage time zones, schedules, switching regimes, switch groups, masters, sub-masters, nodes & authorization requests with a clean interface.
  • Access to dynamic reviews for faults, community reviews, missing measurement statistics, equal records meter evaluation, lacking size info, node authorization request information, and switching regimes consistent with avenue record.
  • Configurable wealthy dashboard with a graphical representation of the various facts.
  • Make CMS and OLN as TALQ compliant in order that they might easily be on hand with the aid of other CMS structures or OLN networks.
  • Creating switching agencies for accepting instructions from sensors or smart metropolis person’s manual commands.
  • Potential to configure device settings, electronic mail notifications, and fault codes, CRUD operations for all the network and inventory entities, heritage offerings settings, etc.
  • Developing an internet API to provide an interface for third parties to get admission to the CMS device functionalities in a secure manner.
  • Creating cellular programs for supporting operatives within the fault-finding method and making sure matters are working after solving the problem.
  • Measuring the performance and accuracy of operatives in the fault fixing manner.
  • Message degree protection whilst communicating with WCF offerings and rights-based totally WCF technique get admission to.
  • Robust authentication and authorization strategies used.
  • Strong authentication and Authorization methods used.
  • Report data events to third parties i.e. lamp failures.
  • Cloud hosting.


As a leading software development service provider, Shivagya Infosoft developed a complete Lighting Control system. This approach provides the company with a digitally advanced stature for the management of road lights and related lighting systems. This approach lets consumers monitor the comfort of their homes and workplaces dynamically on each individual lighting device.

Shivagya Infosoft developed this multi-purpose application with compelling business benefits which include:

  • Monitoring and controlling switching and dimming
  • Control energy consumption and billing
  • Record faults robotically
  • GPRS and Soap service-based communique with the devices
  • Configuration of 2,18,450+ avenue poles getting controlled with the aid of the software program
  • Tremendous functionalities with Google Map and OpenStreetMap and clean interface for lighting fixtures community illustration
  • Switching regimes that features based on photosensors (daylight) or predefined time
  • Support for accepting switching instructions from movement sensors or smart city user organization
  • Integrations with stock systems for road light control agencies
  • Graphical view of carried out lighting, present-day status, faultiness, and so on.
  • Generate and clean faults mechanically by using analyzing size records
  • Generate consumption records automatically primarily based on switching history
  • The rich dashboard allows in information the conduct of various areas of the machine
  • Began making the CMS system as TALQ compliant
  • Cell application allows operatives to make the fault fixing technique less complicated and provide checking out gear after solving the fault.
  • The gadget presents stats for administrators to measure the performance and accuracy of operatives.
  • The device provides numerous utilities that help carry out a few administrative operations to be able to assist accurately the machine if something goes wrong at the production server.
  • Posting payloads to MQTT and SignalR customers to record information whilst a device is created or deleted or size facts are amassed or lamp failure is reported.
  • Commenced web hosting on cloud services like Azure App offerings.
error: Content is protected !!