Sector
Field apps and asset records for power utilities
Brihat Infotech builds software for distribution utilities and energy companies. Technicians get work orders on a phone that works without signal, and the control room sees each job close with a location stamp.

Where utility software gets stuck
Job cards are on paper, so an asset has no history once the card is filed. Feeders and substations sit in one system, meter data in another and billing in a third. Signal is weakest where the faults are. A crew that cannot record the job leaves the control room guessing what was done and whether the fault will return. A consumer who complains about an outage speaks to a call centre that cannot see the job in the field. Meter readings and outage reports reach the planners in separate files.
What we build
- Field apps
work orders, checklists and photos that work offline and sync on return to coverage.
- Dispatch
a console that routes jobs to crews and tracks them.
- Asset lifecycle
a record for each asset, reached by scanning its QR code.
- Consumer service
complaints and requests tied to the asset and the job that fixed it.
- Outage and metering
outage management and smart-meter data on the same records.
Systems we connect to
Billing, SCADA, ADMS, meter data and GIS systems. Data from plant and network systems flows one way into ours, with nothing written back.
Rules the work reports against
- CEA metering rules
- State commission tariff orders
- RDSS, the national distribution reform scheme
- CERC grid and settlement codes
The kind of project we run here
A state power distribution utility moved its technicians off paper job cards. We built offline-first field apps, routing of work orders to crews, closure verified by location, QR trails for each asset and a console for dispatchers.
What changes for the people who use it
- Technicians open a job, see the asset's past work and close it with a photo and a location, with or without signal.
- Dispatchers see which crew holds which job and what is waiting.
- Planners read asset history from one record, not from filed cards.
Related services: mobile applications and systems integration.
Questions we ask first
- How does a work order reach a crew today, and how does the closure come back?
- Where do crews work without signal, and for how long at a stretch?
- Which asset types need a record: transformers, feeders, meters, poles?
- Which systems hold billing, SCADA or ADMS data, and which of them may we read?
- Which reports go to the state commission or a central body?
A sensible first module
Field apps with dispatch come first, because they produce the asset history that every later module needs. Consumer service links in next, then outage management and smart-meter data. Each step adds records to the same asset register.
How a project starts
We watch a job from dispatch to closure, then map it. That work happens at your site or at our Noida office, and the map stays with you.
Case studies
Case studies for this sector are on the work page, filtered to energy & utilities.
See work in this sectorTell us how a fault job travels from complaint to closure today.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.