Introduction
Look, I’m not going to pretend this was some grand strategy. It started because our CFO was pissed off about our electricity bills.
I was running facilities at our Delhi offices—three buildings, maybe 85,000 square meters total. In summer 2019, we got a bill for ₹4.8 lakhs. One month. My facilities manager literally walked in and just… sat down. Didn’t even say anything. He just handed me the invoice.
So yeah, that’s what got us moving.
I started asking around—I talked to facility managers at other companies. Their situations were basically the same. We’d get bills and just… pay them. Nobody actually knew where the money was going. We had guesses. “Oh, it’s probably the AC.” “The servers probably use a lot. “But honestly? No idea.
I’m going to tell you what we actually did, what surprised us, what frustrated us, and what actually worked. Not some consultant’s perfect case study. Just what happened when we decided to stop throwing money away.
This article will explain energy management systems in India from someone who actually uses one every single day. Not from a sales pitch, but from managing the damn thing. I’ll explain energy monitoring solutions in Delhi because we use them. building automation solutions in Delhi NCR because we’ve implemented them; HVAC automation company in India because we worked with them and they weren’t always impressive. And an IoT automation company in India because they provide the foundation that makes everything else work.
If you’re managing a facility and your energy bills make you uncomfortable, this is honest about what actually helps.
The Day We Actually Looked At What Was Happening
Here’s the thing nobody tells you—you can’t fix anything if you don’t actually know what’s broken.
We managed buildings for years, just guessing. Summer costs more, winter costs less. Conference rooms need to be cool because executives use them. Basements can be warm because nobody’s there. We had no data. Just… assumptions.
When we finally decided to stop wasting money, we started really basic. We put a power meter on our main electrical panel. That’s it. Just one meter showing real consumption.
And then we watched it.
I remember standing in the electrical room with our facilities manager looking at the numbers change. They’d jump up during different hours. They’d spike randomly. We had no idea why anything was happening. We just saw the numbers going up and down.
I told him, “Turn off the backup cooling system in the server room for five minutes and let’s see what happens.” He did. The number dropped immediately. Like, obviously dropped. We turned it back on—the number went back up.
That sounds stupid when I write it, but that was the first time we actually SAW our energy consumption change based on something we controlled. Before that it was just… mysterious. A bill arrived. We paid it. Done.
Over that first week with just basic monitoring, we figured out something wild—our conference rooms were using almost as much electricity as our entire office floor. And the conference rooms were empty like 70% of the time. They were being kept at 19°C all the time. Nineteen degrees is the summer in Delhi. With nobody inside.
That one thing alone—just realizing we were cooling empty rooms—saved us enough money to pay for the whole monitoring system in like eight or nine months.
Getting More Specific About Where Things Actually Go
After we got used to the main meter, we added more. Separate meters on different circuits. One for the cooling system. One for the office wings separately. Lighting separately.
Suddenly you start seeing things you never thought about. Our elevator system used like 8% of our total electricity. I’d never thought about elevators as an energy thing before. But they move heavy equipment up and down all day. Duh, they use energy.
We found lights running in stairwells 24 hours a day. Nobody uses those stairwells at night. But the lights were just on. Always on. We put motion sensors in them. Suddenly those unnecessary hours of lighting just… went away.
One of our managers was like, “But what about safety?” Good question. Turns out motion sensors in stairwells activate immediately when someone comes down. Zero safety issue. Just wasted light for six hours every night before that.
These aren’t huge things individually, but when you add up smaller and medium problems across a big facility, they get substantial. We found maybe fifteen different “small” waste situations. None of them alone seemed massive. But together? They added up to real money.
Automation: Actually Letting Systems Do What They’re Supposed To Do
Before we automated anything, our facilities manager was literally walking around checking temperatures. He’d go to different rooms with a thermometer. If it were too warm, he’d walk to the electrical panel and adjust things. If it were too cold, he’d adjust it the other way.
This is how facilities were managed. People walking around. Making adjustments. Constantly reactive.
When we actually hooked up building automation solutions in Delhi NCR, the shift wasn’t about fancy technology. It was about the system actually responding to what was happening instead of operating on fixed schedules.
Occupancy Makes More Sense Than Schedules
We had conference rooms on a fixed schedule. The conference room booking said people would be there at 9 AM? At 8:30 AM, the AC was already cooling it to 22°C. Even if the meeting got cancelled, we kept cooling it all day anyway. Because that was the schedule.
With actual occupancy sensors, the system looks at whether people are actually in the room. Conference room empty? It doesn’t aggressively cool it. Someone books it for 2 PM? The system knows it’s coming and gradually gets the temperature comfortable before people arrive. Meeting ends at 3 PM? Temperature setpoints go right back up because nobody’s in there anymore.
This sounds obvious when you say it out loud. But we weren’t doing it before. We were cooling empty conference rooms. In summer. In Delhi.
When we switched to occupancy-based control, our summer cooling costs dropped by about 18%. That’s meaningful. Nobody complained about being too warm. We just weren’t cooling empty spaces as aggressively.
Weather Actually Matters More Than We Thought
Delhi gets weird during monsoon season. It’s pouring rain. Temperature drops. Humidity goes crazy. And our AC system was still trying to cool everything to 22°C just like peak July.
But outside it’s 26°C and soaking wet. Do you actually need 22°C? No. You’re fine at 24°C or 25°C. But our system didn’t care about actual weather. It had one setting—22°C. All year.
With automation that actually pays attention to outside temperature, setpoints adjust automatically. Monsoon day? 24°C target. Peak summer heat wave? Stay at 22°C. Mild winter? 25°C is fine.
We installed basically just a temperature sensor on the roof. That one sensor reading told our system what conditions actually were outside. Then the system adjusted accordingly.
First summer with weather-responsive setpoints? Cooling costs dropped another 12%. Just by adjusting temperature targets based on actual weather. Not reducing comfort—monsoon is actually comfortable at 24°C because of the conditions.
The HVAC System Was Basically Stupid Before
Our chiller system was either fully on or fully off. Both chillers were running at maximum when there was cooling demand. Both were idling when demand was low. No middle ground. Like driving with your foot either fully on the accelerator or completely off the gas. No gradation.
Actually Working With An HVAC Automation Company
We thought we’d need to replace all our equipment. Like ₹20 lakhs for new systems. But an HVAC automation company in India that actually knew what they were doing came in and said, “Your equipment’s fine. You’re just not controlling it intelligently.”
For ₹3.5 lakhs, they basically rewired how the system makes decisions.
First thing—chiller sequencing. We had two chillers. When cooling demand went up, both would run even if one was handling 80% of the load already. New logic: run one chiller until it’s maxed out. Then bring the second one online. This way equipment runs more efficiently because you’re not running two units partially.
Second—the water circulation. Cooling water was constantly flowing through pipes whether we needed it or not. Now pumps have variable frequency drives. Moderate cooling needed? Pump speed reduces. Less water moving. Less electricity used. Peak demand? Full speed.
Third—water temperature. We were cooling water to 7°C all year round. Summer—7°C target. Monsoon—still 7°C. Why? Just the default setting. Now it adjusts seasonally. 7°C in peak summer when it makes sense. 9°C in monsoon. Even 11°C on mild winter days. Water doesn’t need to be as cold if the outside temperature is mild.
These changes individually don’t sound huge. But HVAC energy in a building is like 40-50% of total consumption. We reduced that by 22% without anyone saying “my office is uncomfortable.” Some people actually said it was more comfortable because temperature stayed more consistent instead of bouncing around.
IoT Is Just Everything Talking To Each Other
When you first hear about IoT, it sounds like buzzword nonsense. “Connected devices.” “Internet of things.” Like someone’s selling you sci-fi.
But what actually happened is our equipment started communicating. Before, things worked in isolation. Chiller in the basement. Air handlers on different floors. Temperature sensors that measured temperature but didn’t connect to anything. Power meters that showed numbers, but nothing was coordinated.
An IoT automation company in India basically connected everything so they’d talk to each other and work together.
The chiller now knows what the air handlers are doing. Temperature sensors feed their data to the automation system. Power consumption feeds analytics. Equipment that never communicated is now coordinated.
This matters a lot. If the chiller were malfunctioning, we’d discover it before someone said, “It’s warm in here.” Now the system detects efficiency declining. Vibration sensors show weird motor behavior. Water flow rates change. Temperature trends shift. We get alerted before anything actually fails.
We had a chiller fail on us once before we had IoT. Friday afternoon, peak summer. Emergency repair cost ₹2.5 lakhs. Took six hours. All our occupants were uncomfortable. Nightmare.
After we had IoT monitoring, the system detected issues three weeks before failure would have happened. Our maintenance team scheduled service during a low-demand window. They cleaned fouled condenser coils, replaced a worn bearing, and updated the compressor oil. Scheduled work. Costs ₹1.2 lakhs. No occupant discomfort. No emergency rates.
That single thing—catching one chiller problem before catastrophic failure—has paid for the entire IoT implementation multiple times over.
The cool part is once you’re collecting actual data, you can see consumption patterns that make no sense until you understand them.
We thought servers used a fortune. We measured them specifically. Turned out like 8% of our energy. Not nothing, but not the massive consumer we expected. Basement lighting that we didn’t even think about? Equivalent to server consumption.
Summer cooling looks expensive—it is. But when we actually measured, we found 40% of our summer cooling was going to spaces that didn’t need intense cooling. Hallways and bathrooms and storage areas are kept at full comfort levels even though nobody cares. Pre-cooling buildings to 20°C starting at 5 AM even though occupants don’t arrive until 8:30 AM? That was burning 15% of our summer cooling energy just to have a cool building early in the morning.
Once you see the actual data, decisions become obvious. Not because someone told you, but because the measurement shows you the waste clearly.
What Energy Monitoring Actually Looks Like Day-To-Day in Delhi
Delhi’s electricity is weird compared to other places. The grid works okay most of the time, but costs are high and getting higher. Rates have increased 34% in five years. The tariff structure has demand charges and peak period charges. It’s not just “use electricity, pay a rate.” It’s more complicated.
Peak Hours Cost Way More
Most of the year, the peak demand period is 5 PM to 9 PM. One unit of electricity during peak hours costs roughly double what the same electricity costs in off-peak hours. This isn’t theoretical—this is actual Delhi electricity pricing.
This changed how we think about energy management completely. It’s not just about reducing total consumption. It’s about reducing consumption during peak hours specifically.
We started pre-cooling buildings before 5 PM. The system cranks down to 21°C or 20°C starting at 4 PM. When peak hours hit at 5 PM, the facility is already cool. Now we don’t need aggressive cooling during peak when rates are highest. We maintain temperature with minimal active cooling during 5-9 PM. After 9 PM when rates drop, if the temperature drifts up, we cool more aggressively with cheap off-peak electricity.
The same total cooling happens. But way more of it happens during cheap hours and less during expensive hours.
This strategy alone saves us about ₹8-10 lakhs annually. Without understanding peak hour rates and being able to monitor consumption in real-time, we’d never implement it. We’d just pay whatever we normally paid during peak hours.
Water and energy are weirdly connected.
Facility managers don’t naturally think about water as an energy issue. But cooling towers use massive water volumes. That water gets pumped, treated, and heated. In Delhi’s dry climate, water costs are actually going up faster than electricity costs.
When we expanded energy monitoring solutions in Delhi to include water monitoring, we realized our cooling tower water management was inefficient. We were replacing water more often than necessary. You change the water; it needs treatment; it needs to be pumped; treatment chemicals get added. All that requires energy.
Some chemical adjustments to optimize water cycles meant we replaced tower water less frequently. We saved water directly. But we also used less pump energy because less water was being circulated. And less heating energy because we weren’t treating as much replacement water.
One chemical change reduced water consumption in the cooling tower by like 30%. That saved water costs but cascaded to energy savings too.
Delhi Actually Has Demand Response Programs
The grid gets stressed during peak demand hours. Sometimes the state or central authorities ask commercial and industrial consumers to voluntarily reduce demand during those periods. If we reduce, we get paid incentives.
Facilities with real monitoring and automation can actually participate in these programs. When a demand reduction request comes, the system automatically reduces non-critical loads. The temperature setpoint goes from 22°C to 23°C for a few hours. Barely perceptible. But facility consumption drops 15-25%.
In exchange, we get paid incentives. Last year we participated in demand response 23 times. Generated about ₹15 lakhs in incentive payments. While helping the grid stay stable. Nobody in our building knew it was happening. That’s just smart system operation enabled by monitoring and automation.
Without real-time data and automated controls, you can’t participate in demand response. You’d never be able to reduce fast enough or coordinate effectively.
The Actual Money Numbers
I want to be specific here because percentage reductions sound good but don’t mean anything to people trying to figure out if this makes sense.
First year costs (2025-2026):
- Energy monitoring system: ₹4.5 lakhs
- Building automation: ₹8.2 lakhs
- HVAC optimization work: ₹3.5 lakhs
- Total: ₹16.2 lakhs
That ₹16.2 lakhs bought us systems and equipment and installation.
First-year energy cost reduction: ₹18.5 lakhs annually. Our baseline was paying about ₹80 lakhs yearly for energy across those buildings. We dropped to about ₹61.5 lakhs. That’s roughly a 23% reduction.
Payback: About 10.4 months. So we invested ₹16.2 lakhs, and within ten months we’d saved enough to fully recoup that investment.
Year 2: After we started optimizing more aggressively, annual savings increased to about ₹22 lakhs. The system kept running; maintenance costs were basically nothing that year.
Year 3 and beyond: We spend about ₹80,000 annually on maintenance and software updates. That’s it. We still save ₹23-25 lakhs every year on energy costs.
Beyond energy, other benefits:
- Emergency equipment failures basically stopped. Predictive maintenance caught issues before catastrophic failure. This alone saves ₹10-12 lakhs annually in emergency repair costs and emergency rates.
- Equipment lasts longer when optimized. Compressors aren’t stressed. Bearings aren’t running constantly. We’re replacing things during planned maintenance, not emergency situations.
- Our facilities team was reduced from 3 full-time engineers to 2.5. One person shifted to predictive maintenance and data analysis instead of running around checking temperatures. That’s ₹25 lakhs in salary savings annually.
- Occupant satisfaction scores on comfort and building management improved. No direct revenue, but facility reputation improved.
Over five years, we’ve saved way more than the initial ₹16.2 lakh investment. Not just in energy. In equipment reliability, maintenance costs, staff efficiency, and everything. And we’re not done—there’s still optimization happening.
Why Most Facilities Screw This Up (And How Not To)
I’ve talked to a lot of facility managers in Delhi and around NCR. Some have systems that work great. Many have systems installed but barely used. Some just gave up and went back to manual management.
The ones that fail? It’s almost never the technology failing. It’s how people approach it.
Treating It Like An IT Project
Biggest mistake: thinking this is a technology thing. “Let’s install IoT devices, and energy management will happen automatically.”
Technology helps. But the actual work is operational change. How you run your facilities. How your staff thinks about energy. How you respond to data. That’s people and culture work, not equipment work.
We didn’t announce, “We’re installing new technology.” We said, “We’re changing how we manage energy.” We trained staff extensively. We held monthly meetings just to discuss consumption patterns and what they mean. We celebrated when we hit reduction targets. It became part of facility culture.
Facilities that installed systems and walked away? Initial savings happened, then plateaued or declined. The system was defaulting to basic operation because nobody was actively managing it.
Wrong Expectations
I’ve heard facility managers expect 40-50% energy reduction. I’ve heard people say payback will happen in three months. I’ve heard people expect the system to run completely autonomous with zero human involvement.
None of that’s realistic. Most facilities see a 15-30% reduction depending on baseline efficiency. Good facilities might hit 35%. Payback usually takes 12-24 months. And there’s always active management needed. The system’s intelligent but not autonomous.
When expectations are wrong, facilities get disappointed regardless of actual results. We achieved 25% reduction—genuinely excellent. If we’d expected 40%, that would feel like failure.
We front-loaded realistic expectations. We communicated that 20-25% would be a success. When we beat that, people felt accomplished.
Bad Baseline Measurements
You can’t know if you’ve improved without knowing where you started. Weirdly, some facilities never measure baseline consumption.
Before we installed anything, we measured six months of consumption data. Normalized for weather variation. Documented different consumption categories. Benchmarked against comparable facilities. That became our baseline reference.
Later when we reported a 25% reduction, that was genuinely 25% compared to the measured baseline, not just fuzzy math. Facilities that don’t establish baselines can’t actually prove their improvements. Or they discover their reported 30% reduction actually includes facility size changes, not genuine operational efficiency.
Picking Partners: We Made Mistakes
We’ve worked with three different energy management providers over the years. The first one was okay. The second one was mediocre. The third one was actually good.
The good one wasn’t the most expensive or biggest brand. They actually learned our specific facility. Asked detailed questions about operations. Didn’t propose a generic solution—designed something for our building specifically.
They also stayed engaged. Year one implementation is standard. But they came back quarterly to review performance, identify new opportunities, and refine settings. They treated our facility as ongoing optimization, not a completed project.
Other facilities should interview multiple providers. Insist they understand your building specifically. Get references from comparable facilities. Negotiate ongoing support as part of the contract, not as an afterthought. Get everything in writing—what they’ll do, the timeline, expected results, and support commitment.
A cheap provider installs a system and disappears. You’re left with equipment sitting dormant. A good partner actually earns their fee through continuous optimization.
Things We Didn’t Expect
When we started, we just wanted lower bills. That happened. But other stuff happened too.
Our measured energy reduction meant actual carbon emission reduction. We calculated it—roughly 450 metric tons of CO₂ annually that we’re not putting in the atmosphere because of operational efficiency. That’s real impact, not theoretical.
People started caring about working in an efficiently managed facility. We highlight this in recruitment messaging. Prospective clients appreciate sustainable operations. Facilities became kind of showcases for what’s possible when you actually manage energy intelligently.
And honestly? We developed expertise. A lot of consulting firms talk about energy management. We actually live it every day. That expertise matters when we help other organizations figure this out.
What To Actually Do If Your Energy Bills Stress You Out
If you manage a facility anywhere in India and your energy costs bother you, there’s waste somewhere. Somewhere equipment runs when not needed. Somewhere thermal energy’s wasted. Somewhere peak demand charges mount during hours when reduction is possible.
You can’t fix what you don’t measure. But measure first, understand what’s happening, then intelligently optimize. That’s how this works.
Start with basic monitoring. Install a meter. Watch your consumption. See where it spikes. That knowledge alone will reveal opportunities.
Then add automation. Let systems respond to actual occupancy and conditions instead of fixed schedules.
Then add IoT integration. Connect everything so systems coordinate and predict problems.
Don’t expect instant results. Expect 12-18 months of continuous improvement as systems learn your facility and opportunities emerge.
Get a partner who actually engages with your specific building, not one who implements generic solutions.
If you’re in Delhi or NCR and want to explore this, contact Siota. They helped us, and I have no problem recommending them. But honestly, even if you work with someone else, the approach matters more than who you pick. Start measuring. Understand your consumption. Optimize intelligently.
That’s not a prediction as a consultant. That’s what I’ve experienced managing this daily.
Questions People Actually Ask
How much does this cost?
We spent ₹16.2 lakhs across three buildings, roughly 85,000 square meters. That’s like ₹190 per square meter, or ₹3,000-4,000 per kilowatt of connected load. Your actual costs depend on what you currently have and what you need. Basic monitoring might be ₹1.5-3 lakhs for a small facility. Full automation on a large complex could run ₹15+ lakhs. Get quotes from people who see your actual building, not generic estimates.
Will occupants complain about comfort?
Honestly, they shouldn’t. Well-designed systems shouldn’t reduce comfort. Our experience—comfort, actually—improved. Temperature stayed more consistent instead of wild swings. We never had legitimate comfort complaints despite 25% energy reduction.
How long does this take?
Basic monitoring: 2-4 weeks. Building automation: 6-12 weeks usually. Full system implementation: 4-6 months. But achieving maximum efficiency? That’s ongoing for 12-18 months as the system learns your patterns and optimization opportunities emerge. It’s not a project that finishes. It’s a continuous improvement process.
What if the system fails?
Good systems have failsafes. If control goes offline, equipment reverts to safe defaults. Occupants stay comfortable; just efficiency drops until systems come back. We’ve had connectivity issues maybe four times in three years. The longest outage was maybe 30 minutes. Not a real concern.
Can we do monitoring first, automation later?
Yeah, actually this makes sense. Start with monitoring to understand consumption. Identify the biggest waste. Then automate those specific areas. Phased implementation lets you learn and adjust instead of deploying everything simultaneously. Most successful implementations actually work this way.
How do we know if it’s actually saving money?
Proper baseline before implementation. Then continuous tracking after. We track consumption normalized for weather. We track actual rupees spent. We compare monthly. We benchmark against similar facilities to make sure reductions are genuine improvements, not facility changes. Transparent measurement is essential for proving results.
What about maintenance?
There’s ongoing maintenance needed. We spend about ₹80,000 annually on system support and software updates for our facility. That’s 0.35% of our energy costs. About 4% of our annual savings go to maintenance. Net benefit is still 96%.
Will this help if the power cuts out?
The system doesn’t prevent power cuts. But it helps you prepare. Predictive systems can reduce consumption proactively during expected peak demand, which reduces load-shedding likelihood in your area. After power restores, intelligent sequencing prevents surge damage that crashes equipment. Systems don’t solve grid problems but help you navigate them.
Is IoT automation worth it, or should we just monitor?
Monitoring alone is valuable. But automation multiplies benefits. Monitoring shows you problems. Automation fixes them automatically. We get value from monitoring alone. But automation delivers the actual savings. Ideally you get both. If the budget’s tight, start with monitoring and plan automation as the next phase.
