A platform that takes readings from pollution and groundwater sensors at construction sites and factories, and files them with the government automatically. It's built for the company that makes and installs the sensors. It also gives every site a live dashboard, alerts and a record of everything ever sent.
08
RudraClouds
Compliance automation · IoT
2
Regulators, in two states
3
Reporting endpoints, filed automatically
0
Readings typed in by hand
Pollution and groundwater sensors whose readings were being typed into government portals by hand. I built all of the software, from device ingestion and the database to scheduled filing, the dashboard and the infrastructure. Manual entry is gone: filing now runs on its own across two regulators in two states, and every submission is kept as proof.
What it is
The problem
In Delhi, construction sites over 500 square metres have to report dust levels to the pollution regulator continuously. In Haryana, factories drawing groundwater have to report their usage the same way. Miss it and you get fined or shut down.
Someone in operations was typing those readings into two government websites by hand, and every gap between entries was a hole in the compliance record.
Why it was hard
Each regulator has its own website, format and schedule. One replies "success" whether it accepted your reading or rejected it, so you have to look inside the answer. Another documents a field with a typo, and you have to copy the typo or your data is ignored.
Every reading becomes a permanent government record under the customer's name, so there's no practice mode. I built a stand-in copy of each regulator to develop against instead.
What I built
All of the software: receiving readings from devices in the field, the database, the scheduler that does the filing, the website and the infrastructure.
The first version was written for the Delhi regulator. When the second arrived, I rebuilt it so each agency is just a description stored in the system. Adding a third is now filling in a form, not writing new code.
I also caught a quiet bug where a site set to report every fifteen minutes was reporting every thirty, because of a timing difference of a few milliseconds. Nothing errored. The only symptom would have been a regulator's letter months later.
Failed filings retry the same window instead of skipping it, and only move on once the regulator confirms receipt. A device missing its site details doesn't send at all, because an anonymous reading in a permanent record is worse than none.
Where it landed
Manual entry into government portals is gone. Filing now runs on each regulator's schedule, unattended, across two agencies in two states and three endpoints. Every submission is kept with what was sent, what came back and when, so compliance can be proved rather than claimed.