Ensmart BMS Academy 📞 +91 99410 42612 Home
Products
Solutions
Knowledge Hub
Company
Contact Get a Demo →
Home Case Studies GHCL Limited
Industrial 2026 📍 Madurai, Tamil Nadu, India

How GHCL's Production Floor Got a Smart HVAC Brain — and the BMS Operator Got a Control Room

A textile production facility in Madurai was running its entire HVAC system on one operator's instinct and memory. EnSmart replaced that with a custom BMS — automated sequences, live HMI visibility, and a full SOP handover. All delivered in under two weeks.

Industrial BMS · Madurai, Tamil Nadu, India · Commenced February 2025 · Completed in Under Two Weeks

Download the Full Case Study →
3
Compressors Automated
1
AHU Controlled
2
Water Heaters Integrated
1
Strip Heaters Integrated
The Challenge

A BMS Operator, Three Compressors, and No Automated Humidity Control

Think of a kitchen with one chef — no timers, no thermometer, no recipe — just one person tasting and adjusting every dish by instinct, alone. If that chef steps away, the kitchen burns. That was the exact situation at GHCL's Madurai production floor before EnSmart arrived. The on-site BMS Operator had one core responsibility every shift: keep the production floor humidity within safe limits. But with zero automation in place, that meant physically walking to each compressor and the AHU, switching them on and off manually, and guessing when to act based on feel and experience. The AHU had no RH feedback, no control sequence, no setpoint — it ran entirely on human judgment. In textile production, humidity is not a comfort setting — it is a quality control variable. Too high and fabric absorbs excess moisture. Too low and static builds. One bad shift of uncontrolled humidity can mean an entire batch of rejected fabric. And the only thing standing between that outcome and the production floor was one person with a switch panel.

The result:

  • The BMS Operator's entire job during production hours was manual humidity management — with no automation, no feedback loop, and no fallback
  • The AHU ran without any RH-based sequence or closed-loop control — purely switched on and off by hand
  • No HMI existed — the operator had no live view of temperature, RH, or equipment status at any point
  • Incorrect compressor switching order could trigger internal protection timers and cause humidity spikes mid-production
  • No written procedure existed — if the regular operator was absent, nobody else knew how to run the system and the floor was left to chance
Why This Project Stood Out

More Than Wiring — This Was a Full System Built from Scratch, Solo

Full Project Ownership
Every stage was executed independently — site survey, I/O count, FBD logic, HMI design, commissioning, and handover. No supervision, no team.
Human-to-Machine Handover
The project did not add automation on top of an existing system. It replaced an entire manual human routine with a purpose-built control sequence. That is not installation — that is transformation.
Temperature and RH-based control sequences were written from scratch using Function Block Diagram (FBD) programming. No off-the-shelf template was used.
Temperature and RH-based control sequences were written from scratch using Function Block Diagram (FBD) programming. No off-the-shelf template was used.
Completed in Under Two Weeks
The full project lifecycle — first site visit to final client sign-off — was closed within two weeks, on time and to full client satisfaction.
Who This Case Study Is For

If Your Facility Still Has One Person Holding the Entire HVAC Together — This Is for You

Relevant for teams managing
  • Textile mills and spinning units
  • Manufacturing plants with humidity or temperature-sensitive production
  • Industrial warehouses with controlled environment requirements
  • Any facility where HVAC is still operated manually shift by shift
Relevant Roles
  • Plant Maintenance Engineers
  • Facility and Operations Managers
  • HVAC Consultants and System Designers
  • BMS Project Managers and Commissioning Engineers
What You'll Learn Inside

The Real Engineering Happened After Go-Live

Inside the full case study, you'll see:

  • How to design a BMS sequence for compressors and AHU using temperature and RH setpoints to stabilise production humidity — step by step
  • Why strip heaters and water heaters were added to the RH control loop — and what happens to fabric quality when you skip them
  • How MODScan was used to validate Modbus communication before client handover — and why skipping this step causes post-live problems
  • What a proper SOP document for a textile mill HVAC system must contain — and why it is the difference between a system that survives staff turnover and one that collapses the moment the original operator leaves
Business Impact

What Changed After EnSmart Took Over from Manual Operation

Zero Manual Switching
All three compressors and the AHU now operate automatically on RH and temperature-based sequences. The BMS Operator no longer makes a single manual switching decision during production hours.
Production Humidity Now Controlled
The BMS Operator's core responsibility — keeping humidity stable during production — is now handled entirely by the BMS. Relative humidity is actively managed around the clock with no human intervention required.
RH Stabilised Through Heater Integration
When relative humidity rises above threshold, the water heaters and strip heaters activate automatically to compensate. Moisture-related fabric damage during production is now prevented by the control loop — not by a person walking the floor.
BMS Operator Empowered, Not Replaced
The BMS Operator went from manually chasing humidity across the production floor to monitoring everything from one HMI screen. Live temperature, RH readings, and equipment status — visible at a glance, from one place.
Complete SOP Handed Over
Full operating documentation was delivered at handover. Any new operator assigned to the system can read the SOP and run the floor confidently from day one — no dependency on one person's memory.
Deployment Timeline

From First Site Visit to Final Handover — Under Two Weeks

YearMilestone
Week 1 Site inspection · I/O point count · BMS panel selection · Panel fabrication · Controller wiring · I/O module termination · FBD logic development · HMI screen design · Point-to-Point field verification · MODScan communication validation
Week 2 Live commissioning · BMS operator training · Setpoint tuning · Final handover · SOP documentation delivered · Client signed off
Frequently Asked Questions

Frequently Asked Questions

Why were heaters added to an HVAC cooling system? Doesn't that defeat the purpose?
This is one of the most common surprises for anyone seeing a textile mill BMS sequence for the first time. Think of it like a car's climate control — on a cold rainy day, your car blows warm air not to heat the cabin, but to remove moisture from the windscreen. The goal was never just temperature. It was always humidity. At GHCL, when the compressors cool the production floor, the air temperature drops — and cooler air holds less moisture, which raises relative humidity. The water heaters and strip heaters are brought into the loop specifically to counteract that RH rise. They are not fighting the compressors. They are working with them to hold RH steady. Remove the heaters from the loop and you lose humidity control entirely — and with it, fabric quality.
Why does the BMS use three compressors instead of one large unit?
Think of it like driving on a motorway. You do not floor the accelerator from zero to top speed in one go — you shift gears progressively. Running three staged compressors gives the BMS the ability to step cooling capacity up or down in response to actual floor conditions. Compressor 1 handles base load. Compressor 2 cuts in when conditions demand more. Compressor 3 is the heavy artillery — activated only when the floor is genuinely under thermal stress. This staged approach protects the compressors from short-cycling, reduces wear, and gives the control sequence precision that a single large unit cannot offer.
The BMS Operator was already managing this manually. Why did the facility need automation?
Because a person is not a system. Think of a hospital where one nurse manually checks every patient's vitals by walking room to room — no monitor, no alarm, no record. The nurse may be skilled and dedicated, but the moment they are sick, on leave, or simply in another part of the floor, patients are unmonitored. That was the exact risk at GHCL. The BMS Operator knew the equipment well — but that knowledge lived in one person's head, with no documentation, no backup, and no visibility for anyone else. The BMS does not replace the operator's expertise. It captures it, codifies it into a sequence, and makes it run reliably every shift — regardless of who is on duty.
What does the HMI actually give the BMS Operator that they did not have before?
Before the HMI, the operator's only feedback was walking to each piece of equipment and observing it directly — or noticing a problem on the production floor after it had already happened. That is reactive management. Think of the difference between a pilot flying blind and a pilot with a full instrument panel. The aircraft does not change. The information available to the pilot does — and that changes every decision they make. The HMI gives the BMS Operator live temperature readings, live RH levels, equipment run status, and alarm visibility from a single screen. Problems are seen before they become production issues. Setpoints are adjusted without touching a single switch. The operator is no longer chasing the environment — they are commanding it
What happens if the BMS loses power or a sensor fails mid-production?
This is exactly the kind of question an SOP is designed to answer — and it is why handover documentation matters as much as the BMS itself. Think of an SOP like the emergency checklist a pilot runs before takeoff. It does not assume everything will go right. It prepares the operator for when something goes wrong. The SOP delivered at GHCL's handover covers manual override procedures, sensor fault responses, and escalation steps — so that any operator on any shift can respond to an abnormal condition without guessing. The BMS handles normal operations automatically. The SOP handles the exceptions.
Download the Full Case Study

Get the Full GHCL Limited Case Study

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

Download PDF →

Built by EnSmart. Proven on the Production Floor.

This project was designed, programmed, commissioned, and handed over by a single EnSmart engineer — from the first site visit to the final SOP document. No templates. No supervision. No shortcuts. If your facility is still running HVAC on one person's judgment and memory, EnSmart can change that — in days, not months.