Every street. Lit right.
Every pole. Every lumen.
Register every pole, turn complaints into work orders, and close them on time. Connect your controllers when you’re ready.
One platform for the whole network. Self-host it, or let us run it.
OpenSLMS is a maintenance app first. Register your poles and panels, then run their upkeep. Complaints, night patrols, preventive plans, and telemetry alarms all raise work orders that your crews start, hold, and resolve. Connect controllers later, or not at all. New to it? Read the playbook’s street light maintenance guide.
SL-0186 · Fort Road
A resident scans the label on pole SL-0186. No sign-in, no app. They get WO-1042 to track it.
Due time is the time raised plus the SLA. Overdue jobs are emailed once, to the technician and their supervisors.
Name, location, and type are all it needs. Add asset tags, make and model, warranty, and pole details when you have them, or import a whole ward from CSV.
Luminaires, poles, feeder panels, and controllers, each with its own specs, the maker’s contacts, and warranty papers.
Status, assignment, checklist, notes, photos, and parts used. A job can’t be resolved without saying what fixed it.
See a work order’s historyParts issued to a job come off the shelf. Received, returned, scrapped, and counted stock all add up, and nothing goes below zero.
Explore sparesSLA met, mean time to repair, repeat failures, technician workload, low stock, and warranty claims. Every table exports to CSV.
Explore the reportAdministrators run everything. Supervisors assign, plan, and close. Technicians work the jobs assigned to them and run patrols.
Each asset’s condition follows its open jobs, so the register is never out of date.
Technicians hear when a job is assigned to them. Overdue jobs are sent once to the assignee, and as a list to supervisors.
Connect OpenSLMS to the AI assistant you already use, over MCP. Ask about overdue jobs, a feeder panel’s night, or the spares to reorder, and raise or update work orders in plain language. It works as you, with your role’s permissions.
Which jobs are overdue?
ASK OPENSLMSThree. WO-62 on Sargam Marg and WO-64 on Corporate Road are lights not working that nobody has picked up; both passed their 48-hour SLA. WO-74 on Aurobindo Society Road is on hold for a driver. Assign the first two tonight, and check the driver delivery for the third.
SOURCE: WORK ORDERSAsk in plain language. Get the overdue jobs, why each is stuck, and what to do next, from the AI assistant you already use.
EXPLORE WORK ORDERSFind the panel that missed its dimming step, with the readings behind it, before it costs another night.
EXPLORE FEEDER READINGSSee which spares are at or below their reorder level, and which are well stocked, in one answer.
EXPLORE SPARES
MCP supported
Choose a network. See the view that fits it.
Map feeder panels and poles to the wards you manage, coloured by condition: in service, faulty, or under repair.
Follow each feeder panel from sunset to sunrise: when it switched on, when it dimmed, and when it didn’t.
A QR label on every pole opens a report page with the pole filled in. No sign-in, no app, and a number to track it.
Set a plan once. Each feeder panel gets its own inspection job, with a checklist, every time the plan falls due.
Turn complaints, patrol marks, and alarms into work orders. Assign them, track the parts, and close them on time.
05 / A FEW THINGS TO KNOW
The details, without the jargon.
OpenSLMS is open source street light management and maintenance software. It keeps every pole and feeder panel in one register and on a map, reads feeder panels over MQTT, and runs the maintenance behind them: work orders, complaints, night patrols, preventive plans, and spares. The open source edition is free to self-host for personal, evaluation, and non-commercial use, and OpenSLMS Cloud runs it for you. See pricing.
No. OpenSLMS is a maintenance app first. Register your equipment, and run its upkeep with work orders from complaints, night patrols, preventive plans, and your own staff. Connecting a controller for readings is a later, optional step for each piece of equipment. Once connected, its alarms raise work orders too. The playbook explains why and when to connect your lights.
Print a QR label for each pole. Scanning it opens a public report page with the pole already filled in; no sign-in or app needed. Without a label, residents describe the place or share their location. They can add a photo and get a work order number to follow the repair. If the pole already has an open job, the report joins it instead of opening a second one. See the playbook on handling resident complaints.
OpenSLMS is designed around city wards, highways, campuses, townships, and industrial estates.
Through AI Connect, an MCP connector on OpenSLMS Cloud. Add it to an AI assistant such as Claude, sign in with your OpenSLMS account, and ask about your network in plain language, or have the assistant raise and update work orders. It works as you: it sees and changes only what your role allows.