Home › Case Studies › Technopark

IT Park 2024 📍 Trivandrum, Kerala

When the Building Runs Itself, the BMS Operator Finally Gets to Do His Job

Technopark had field controllers and I/O modules already installed across its campus — the hardware was doing its job. What was missing was a software layer that could bring it all together, show it clearly, and let the team actually manage the building instead of just react to it. EnSmart stepped in and delivered exactly that in three weeks.

74 AHUs · 37 CSUs · 16 DFAs · One campus · One platform · Three weeks

Download the Full Case Study →

AHUs integrated

CSUs mapped

DFAs on dashboard

weeks deployment

The Challenge

The hardware was there. The visibility wasn't.

Rahul is the BMS Operator at Technopark, Trivandrum. Every morning he walks in knowing that thousands of people are about to fill those floors expecting cool air, stable systems, and a comfortable working environment. The field controllers and I/O modules installed across the campus were doing their job at the hardware level — AHU-74 was running, CSU-37 was running, DFA-16 was running. But the software that was supposed to show Rahul all of this in one place, alert him when something drifted, and help him make decisions? It was not delivering. The existing vendor software had stopped cooperating — not dramatically, but quietly. Data gaps. No live graphics. No way to see the campus without walking it floor by floor.

The result:

The installed controllers and I/O modules were functional, but the supervisory software was not giving usable visibility into what was happening on each floor
Rahul had no live graphical view of AHU status across zones — checking the system meant physically walking the building
There was no scheduling in place — AHUs ran on manual overrides or fixed timers, consuming energy through the night even when floors were empty
Tenant energy billing was based on estimates and averages, not actual metered consumption — tenants questioned the numbers and the facility team had no clean way to answer
BMS monitoring and tenant billing lived in separate tools with no connection between them

Why This Project Stood Out

A campus already built — just missing the right brain

No rip-and-replace

The existing field controllers and I/O modules stayed exactly where they were. EnSmart integrated with what was already installed. Think of it as giving the building a new operating system without touching the hardware underneath.

BMS and Tenant Billing as one

EnSmart's platform brought building management and tenant billing into a single system. Tenant billing sits inside the platform — not a separate tool, not a separate login. One platform, complete picture.

Custom graphics built for Technopark

Not a generic template. EnSmart built graphical screens that match how Technopark is actually laid out — zone by zone, floor by floor, the way Rahul thinks about the campus every morning.

Scheduling that works without being reminded

AHUs now follow programmed schedules tied to occupancy hours, shift timings, weekends, and holidays. They come on when tenants arrive. They switch off when the last person leaves.

Three weeks from kickoff to live

The entire project — integration, custom graphics, Tenant Billing Software, scheduling, tenant billing setup, and handover — completed in three weeks.

Who This Case Study Is For

If you manage a large building and this sounds familiar, this case study is for you

Relevant for teams managing

IT Parks and SEZs
Multi-tenant commercial campuses
Large office complexes
Government and institutional buildings with multiple tenants

Relevant Roles

BMS Operators
Facility managers
MEP heads and building engineers
Property and campus managers

What You'll Learn Inside

Five things this case study walks you through

Inside the full case study, you'll see:

How to integrate existing field controllers and I/O modules into EnSmart without replacing any hardware
What EnSmart's custom BMS graphics look like when built around a real IT park campus layout
How AHU scheduling cuts energy waste without touching a single physical setpoint on the floor
Why putting tenant billing inside the BMS platform — not as a separate system — changes how your finance and facility teams work together
What a three-week deployment actually looks like, week by week, on a campus this size

Business Impact

What changed for Rahul — and for everyone above him

One screen, full campus

All 74 AHUs, 37 CSUs, and 16 DFAs visible in a live graphical dashboard. Rahul sees the status of every zone from his desk. If something drifts, he knows before a tenant calls.

Schedules running on their own

AHUs follow business-hours programs. No more manual overrides. No more energy wasted cooling an empty floor at midnight.

Tenant billing that tenants trust

Each tenant's energy consumption is metered and reported directly from the Tenant Billing Software. The numbers are real, auditable, and no longer a source of disputes.

Zero new hardware spend

The field controllers and I/O modules that were already installed are still the ones doing the work. EnSmart brought the intelligence layer on top — no hardware budget required.

Rahul's morning is different now

He opens one dashboard. He sees the campus. He knows what is running, what is scheduled, and where to look if something needs attention. He does not walk five floors to find out.

Deployment Timeline

Three weeks. One campus. Fully live.

Year	Milestone
Week 1	Site audit and I/O mapping. EnSmart engineers review the installed controllers and map all existing field points — all AHUs, CSUs, and DFAs — into the EnSmart platform using open protocols.
Week 2	Custom graphics built for Technopark's floor plans. BMS software goes live. Tenant Billing Software configured with energy metering and billing logic assigned and tested zone by zone.
Week 3	AHU schedules programmed and verified. Full handover and training session with Rahul and the facility team. System running independently by end of week.

Frequently Asked Questions

Do we have to replace any of the existing controllers or field devices?

No. Everything installed on site stayed in place. EnSmart integrates with existing hardware using open protocols — BACnet, Modbus, and others. The only thing that changed was the software layer above.

How does EnSmart's BMS connect to controllers from other vendors?

EnSmart uses open industry protocols to read data from any compatible field controller or I/O module. As long as the device speaks a standard protocol, EnSmart can map it, monitor it, and display it.

Is tenant billing really part of the platform, or is it a separate system?

It is part of the platform. At Technopark, BMS monitoring and tenant billing are in the same system — there is no separate billing application. Consumption is measured, calculated, and reported from one place.

What happens if the original vendor software has issues again?

EnSmart operates entirely independently of the original vendor software. The field devices still function on their own. EnSmart simply provides a better supervisory layer — so a vendor software issue no longer takes down your visibility or your operations.

Is three weeks a realistic timeline for a campus this large?

It was for Technopark — 74 AHUs, 37 CSUs, 16 DFAs, custom graphics, and Tenant Billing Software, all live in three weeks. It moves quickly because the hardware is already there. EnSmart builds the intelligence layer on top, not the infrastructure from scratch.

Download the Full Case Study

Get the Full Technopark Case Study

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

Download PDF →

If a campus this size can go live in three weeks, yours can too

EnSmart does not ask you to start over. If you have field controllers and I/O modules already installed — from any vendor — we integrate with them. We bring the BMS software and the tenant billing together into one platform that your BMS Operator can actually use every morning. Rahul manages Technopark from one screen now. If your BMS Operator is still walking floors to check what should be visible from a dashboard, let's talk.

← Back to all case studies