Ensmart BMS Academy 📞 +91 99410 42612 Home
Products
Solutions
Knowledge Hub
Company
Contact Get a Demo →
Home Case Studies ISRO — APEP
Industrial 2025 📍 Aluva,Kochi,India

How ISRO APEP Aluva's Voltas Chiller Plant Went from Manual Switch-Flipping to Intelligent Automation — in One Week

A Voltas controller and chiller plant was already installed. Pumps were already running. But every start, every stop, every handoff — someone had to walk to a panel and do it by hand. EnSmart changed that.

EnSmart delivered controller, software, graphics, and panel — integrated with the existing Voltas system — and gave the BMS operator his desk back.

Download the Full Case Study →
4
Voltas Chillers Automated
1 Week
Full Deployment
0
Manual Trips Required After Go-Live
2 Days
Trial to Full Implementation
The Challenge

The Night Shift Problem — When a Building Depends on One Person's Legs

Imagine a hospital where every time a patient needed medicine, the doctor had to walk to the pharmacy, open the cabinet, count the tablets, and carry them back — personally. No pharmacist. No system. Just the doctor's feet and memory.
That was the reality at ISRO APEP Aluva's chiller plant before EnSmart arrived.
Four Voltas chillers. Condenser pumps. Chilled water pumps. A Voltas controller already installed — hardware in place, wiring done. But the Voltas controller had no BMS automation logic. It could not talk to a central BMS. It could not act on schedules. It could not send alerts. Every start command, every stop command, every sequence — Satish Kumar, the BMS operator at ISRO APEP Aluva, had to physically walk to the panel and operate it by hand.
Morning shift: walk to panel. Start pump. Start chiller. Evening: reverse the process. If a chiller needed switching mid-day — Satish again. If load changed — Satish again. The building was not managed by a system. It was managed by a man's feet.

The result:

  • 4 Voltas chillers installed but operating fully manually — no BMS automation in place
  • Chiller ON/OFF was entirely manual — operator physically present at the Voltas panel every time
  • Pump sequencing required human judgment and physical intervention for every operation
  • The Voltas controller was an island — capable hardware with no connection to a central BMS
  • No remote visibility — the operator could not see Voltas chiller status from his workstation
  • No automated scheduling — cooling ran on human memory, not time or load logic
  • Risk of missed operations during shift changes, leaves, or late arrivals
  • No fault logging — if a Voltas chiller tripped at 2AM, nobody knew until someone walked in and saw it
Why This Project Stood Out

Not a Greenfield. Not a Replacement. A Translation — and That Is Harder.

The translator problem
The Voltas controller already existed — capable hardware doing its job at the chiller level. EnSmart did not rip it out. Like a bilingual coordinator at a railway station who helps a Hindi-speaking traveller communicate with Tamil-speaking staff — EnSmart's DDC controller read the Voltas system's signals and translated them into BMS commands. The Voltas chillers kept running. EnSmart added the brain on top.
Speed under pressure
Week 1: EnSmart prepared the controller and software at their facility — studying the Voltas system's IO, writing the logic, building the graphics. Week 2: Trial on-site at ISRO APEP Aluva. Days 3–4: Full implementation across all 4 Voltas chillers. What a large team might stretch into months, EnSmart executed in days — because preparation happened before boots reached site.
Government-grade reliability
ISRO APEP is not a commercial office. It is a critical government facility. Cooling is not comfort — it is infrastructure. The integration with the existing Voltas system had to work the first time and keep working. Downtime was not an option.
Complete ownership — one vendor
Controller. Software. Graphics. Panel. EnSmart supplied and commissioned all four — on top of the existing Voltas installation. One throat to hold for the BMS layer. No finger-pointing between the chiller vendor, a software vendor, and an integration vendor.
The operator's life changed
Before: Satish Kumar's job was walking to the Voltas panel. After: Satish Kumar's job is monitoring a screen. The EnSmart software commands the Voltas chillers and pumps. He does the thinking. That is what automation is supposed to do.
Who This Case Study Is For

If Your Operator Is Also Your Automation System — This Is For You

Relevant for teams managing
  • Government and defence facilities with other brand chiller plants
  • Industrial facilities with legacy chiller controllers and no BMS integration
  • Pharma and process plants where cooling is mission-critical
  • IT Parks and data centres with manual chiller plants
  • Any facility where chiller and pump operation is currently manual despite hardware being installed
Relevant Roles
  • Facility managers inheriting an existing chiller plant with no BMS layer
  • BMS operators who spend more time at panels than at workstations
  • MEP consultants specifying BMS integration on top of existing chiller brands
  • Project managers evaluating BMS vendors for government sites
  • Energy managers who cannot measure what they cannot automate first
What You'll Learn Inside

The ISRO APEP Aluva Playbook — What EnSmart Did and How

Inside the full case study, you'll see:

  • How EnSmart integrated with the existing Voltas controller without replacing it — the approach explained
  • Why the project was planned in two weeks and why Week 1 never touched the site
  • How 4 Voltas chillers and their associated pumps were sequenced and automated using EnSmart's controller logic
  • What "transferring data from the Voltas controller to EnSmart controller" actually means in wiring and protocol terms
  • How graphics were built so the operator sees Voltas chiller status, pump status, and fault conditions on one screen
  • Why preparation before site visit is the single biggest factor in fast commissioning
  • What the BMS operator can now do from his desk that previously required a physical trip to the Voltas panel
Business Impact

What Changed the Morning After Go-Live at ISRO APEP Aluva

Zero manual trips to the Voltas panel for routine operation
All 4 Voltas chillers and their pumps start and stop on schedule or on software command. Satish Kumar's daily walk to the plant room became a glance at a screen.
Full remote visibility — 4 Voltas chillers on one dashboard
Status, fault, run-hours, on/off state — all visible in real time from the EnSmart BMS workstation. What was invisible before is now logged, timestamped, and accessible.
Fault detection without physical inspection
If a Voltas chiller trips, the EnSmart BMS knows in seconds. An alert goes out. The operator does not discover a problem two hours later by walking past the plant room.
Reduced dependency on a single operator
When Satish Kumar is on leave, the system still runs. Automation does not take leave. The shift handover is now a software check, not a physical walkthrough of the Voltas panel room.
Foundation for energy optimisation
You cannot optimise what you cannot control. Now that the Voltas chillers are under EnSmart BMS command, scheduling, load-based sequencing, and run-hour balancing across all 4 units are all possible — next phase ready.
One-week deployment proves repeatability
ISRO APEP Aluva is now a reference site for Voltas chiller BMS integration. If EnSmart can commission this in a critical government facility in one week, the methodology is proven for any industrial or institutional site across India.
Deployment Timeline

Two Weeks. Four Voltas Chillers. One BMS Operator Who Can Now Sit Down.

YearMilestone
Aug-25 Week 1 EnSmart studies the Voltas controller IO and signal architecture. DDC controller programmed, BMS software logic written, and operator graphics built at EnSmart's facility. Panel fabricated and tested. No site visit yet — full preparation off-site.
Aug-25 Week 2, Days 1–2 EnSmart controller and panel installed at ISRO APEP Aluva. Data integration from the Voltas controller begins — signals mapped, wiring connected, communication verified. Trial run on all 4 Voltas chillers and pumps with EnSmart engineer on-site.
Aug-25 Week 2, Days 3–4 All 4 Voltas chillers fully automated under EnSmart BMS. Pump sequencing live. Graphics commissioned — chiller status, pump status, fault alarms all visible on screen. Satish Kumar trained on the new software interface.
Aug-25 End of Week 2 Full implementation complete. ISRO APEP Aluva Voltas chiller plant live under EnSmart BMS control. Manual panel operation retired.
Frequently Asked Questions

Frequently Asked Questions

The Voltas controller and chillers were already installed. Did EnSmart replace them?
No. EnSmart's approach is integration first. The Voltas chillers kept running. EnSmart's DDC controller was connected on top — reading signals from the Voltas system, and adding the automation logic that was missing. The Voltas hardware was retained. EnSmart added the intelligence.
What exactly does "transferring data from the Voltas controller to EnSmart controller" mean?
Think of it like this: the Voltas controller was speaking — but nobody was listening and acting on what it said at the BMS level. EnSmart's controller listened, understood the Voltas signals (pump run status, chiller fault, on/off feedback), and then added the missing brain — the logic that says "if it is 9AM and cooling load is active, start Pump 1, wait 30 seconds, start Voltas Chiller 1." That is the automation that was missing.
How were 4 Voltas chillers and pumps automated in just one week?
Because EnSmart prepared everything before reaching site. The controller was programmed, the logic was written, and the graphics were built at EnSmart's facility during Week 1 — after studying the Voltas system's IO. Week 2 on-site was installation, connection, and commissioning — not starting from scratch. Preparation is the real project. Site work is the final act.
What does the BMS operator see now that he could not see before?
On one screen: which Voltas chillers are running, which pumps are on, run hours for each unit, fault status, on/off command history, and scheduling. Before: Satish Kumar walked to the Voltas panel to check. After: one EnSmart screen tells him everything. He issues commands from his chair.
What was EnSmart's scope on this project?
Complete BMS scope — DDC controller, BMS software, operator graphics, and field panel. EnSmart supplied, installed, programmed, and commissioned all four elements at ISRO APEP Aluva — integrated with the existing Voltas chiller and controller installation. Single-vendor accountability for the BMS layer.
Is this relevant to other facilities with Voltas or other OEM chiller plants and no BMS integration?
Yes — exactly. Many facilities across India have Voltas, Blue Star, Carrier, or other brand chillers installed with no BMS automation on top. The operator is doing the chiller's thinking manually. ISRO APEP Aluva is a direct reference for how to bridge that gap quickly, without replacing existing equipment, using EnSmart's integration methodology.
Download the Full Case Study

Get the Full ISRO — APEP Case Study

See how EnSmart helped ISRO — APEP deliver this project — full methodology, system architecture, and measurable outcomes inside the PDF.

Download PDF →

ISRO APEP trusted EnSmart to automate their Voltas chiller plant at Aluva. We delivered in one week.

If your facility has Voltas chillers — or any OEM chiller brand — running without BMS automation, a BMS operator doing manual panel work, or a chiller plant that depends on one person showing up every shift — the ISRO APEP Aluva project is your reference. EnSmart brings the controller, the software, the graphics, and the panel. We integrate with what you already have. We make the operator's walk unnecessary. And we do it on a timeline that respects your operations.