Home › Case Studies › Syngene Biotech

Industrial 2025 📍 Bangalore, Karnataka, India

How Syngene Biotech Went From a Man With a Notebook to a Smart System That Never Sleeps

In a pharma lab in Bangalore, seven gas cylinders were being watched by one field engineer walking around with a pen and paper. No alerts. No screen. No alarm. Just a guy checking a dial. We changed that — completely.

7 cylinders · 4 oxygen + 3 CO₂ · Bangalore · 2025

Download the Full Case Study →

Cylinders monitored

Alarm levels per cylinder

Inch HMI screen

Pressure sensors (4–20 mA)

Manual paper reports remaining

The Challenge

THE SENSOR CHALLENGE — What Nobody Talks About

This challenge was hidden but very important.
Each pressure transmitter on the cylinder sends a 4–20 mA current signal. That is the raw signal travelling from the transmitter to the controller panel.
Now here is the important part.
Our controller sequence program is written using voltage values to calculate and display the pressure. This means the controller does not directly understand milliamps — it needs the value in volts to do its job correctly.
So inside the controller, we convert the incoming 4–20 mA signal into 2–10V. The controller then reads that 2–10V value, runs it through the sequence logic, and displays the correct pressure reading on the HMI screen.
The sequence is simple —
Pressure transmitter sends 4–20 mA → signal enters the controller → controller converts 4–20 mA to 2–10V → sequence program reads the voltage → accurate pressure value displayed on HMI screen.

The result:

No live data — the pressure reading was only as fresh as the last time someone physically walked to the cylinder. That could be many hours ago.
No alarm — if a cylinder went critical at night or on a holiday, there was nobody to catch it.
No history — paper reports can be adjusted, lost, or misread. There was no trusted digital record.
No early warning — there was no way to say "this cylinder is getting low, act now before it becomes a crisis."
No single view — to know the status of all seven cylinders, you had to physically walk to all seven locations.

Why This Project Stood Out

This Was Not Just "Install a Sensor and Walk Away"

The four-alarm ladder — smart, not just simple

Most basic systems use one alarm. High or Low. That is it. We designed something smarter here. Each cylinder was given four setpoints — think of it like four speed bumps before a cliff.

50 = Low-Low (danger, act immediately)
70 = Low (warning, start preparing)
90 = High (caution, something is going up)
110 = High-High (critical, stop everything)

The pressure inside a cylinder naturally moves up and down — it oscillates. So if the value is sitting between 50 and 70, the system is watching closely. The moment it touches or crosses 50 going down — the alarm (hooter) fires. Same on the high side. If the value goes above 110 — alarm. If it tries to stay between 90 and 110 — it triggers the High alarm. This gives the facility two warnings before a real problem, not zero.
Think of it like driving — the Low alarm at 70 is the yellow fuel light. The Low-Low at 50 is when the engine starts coughing. You want the yellow light, not the coughing engine.
Two panels, one smart system
We built the system across two panels. Panel one held the main brain — the controller, the HMI screen, and the communication module. Panel two held the input/output module — a 16UI/8UO IP module — which connects to all the sensors and alarms in the field.
Think of Panel one as the control room and Panel two as the field crew. The control room gives instructions, the field crew executes and reports back.
We tried Modbus. It did not work. Here is why.
When we first connected Panel one and Panel two using Modbus, the pressure values were coming in wrong. Numbers were jumping. Readings were inconsistent. It was like two people trying to have a phone call on a bad network — the words are there, but they are all scrambled.
The reason was signal interference. Modbus, in this site-specific wiring setup, was picking up noise from surrounding equipment. The data was getting corrupted in transit.
So we switched to EtherNet/IP. Think of EtherNet/IP as upgrading from a walkie-talkie to a direct phone line. Clean, fast, reliable. The moment we made the switch, the values came in perfectly.

A screen that shows you everything

We installed a 10-inch HMI (touch screen display) with full BMS graphics. Meaning — the operator does not just see numbers. They see a visual picture of all seven cylinders on screen, with live pressure readings, colour-coded alarm states, and hooter status — all on one screen, all the time.
Rajasekar no longer needs to walk to seven cylinders. He looks at one screen.

Who This Case Study Is For

Who Will Benefit From Reading This

Relevant for teams managing

Pharmaceutical manufacturing plants
Biotech research labs
Hospital medical gas supply rooms
Industrial gas storage facilities
Chemical processing units

Relevant Roles

Facility managers and EHS leads
BMS and automation engineers
Lab infrastructure heads
Compliance and audit officers
Controls and instrumentation engineers

What You'll Learn Inside

What You Will Walk Away Knowing

Inside the full case study, you'll see:

Why the pressure transmitter sends 4–20 mA and why the controller converts it to 2–10V — and how the sequence program uses voltage values to display accurate pressure on screen
Why 4–20 mA is the right signal for long cable runs — it does not drop over distance, resists noise, and detects broken wires automatically
How to design a four-level alarm system — Low-Low, Low, High, High-High — for gas pressure monitoring and why four levels are better than one
Why Modbus RTU causes signal interference and how switching to Modbus TCP/IP solved the problem completely
How to build a two-panel BMS system — one panel for the controller and HMI, one panel for the field I/O module — and connect them reliably over Ethernet
What a 16UI/8UO IP module does and how it acts as a remote I/O unit that talks to the main controller over the network
How to build BMS graphics on a 10-inch HMI so any operator sees all seven cylinders — live pressure, alarm states, and hooter status — on one screen
The full journey from a field engineer reading pressure gauges by hand to a fully automated, alarm-driven, 24/7 monitoring system

Business Impact

What Changed After We Were Done

The system never goes home

Before, monitoring stopped when Rajasekar left for the day. Now the system watches all seven cylinders every second — day, night, weekends, and holidays. An alarm fires the moment any pressure crosses a setpoint.

Paper reports are gone forever

Every pressure reading is captured digitally with a timestamp. Nothing to adjust, nothing to lose, nothing to question. The data is always there and always trustworthy.

The team gets warned early, not late

The Low alarm fires at level 70. The dangerous Low-Low level is 50. That gap gives the team time to act before a crisis hits. One alarm gives you a shock. Four levels give you a plan.

Accurate data from a smart signal conversion

The pressure transmitter sends 4–20 mA. The controller converts it to 2–10V and the sequence program reads the voltage to display pressure. No noise errors, no voltage drop over cables, no confusion between a broken wire and a real low-pressure reading.

Audit and compliance become simple

Pharma regulators want logs, records, and alarm event history. The BMS produces all of that automatically. No handwritten reports, no gaps, and no questions during an audit.

Engineer time is freed up

Rajasekar now focuses on real maintenance, inspections, and problem solving — not walking around copying numbers off pressure gauges into a notebook.

Deployment Timeline

How We Built It — Step by Step

Year	Milestone
Phase 1	Site survey, sensor selection, and panel design for 7-cylinder setup
Phase 2	Decision made to use 4–20 mA output on all 7 pressure transmitters and convert to 2–10V at the panel for accuracy
Phase 3	Installation of 7 pressure transmitters on O₂ and CO₂ cylinders
Phase 4	Panel fabrication — Controller + HMI panel (Panel 1) and 16UI/8UO IP I/O panel (Panel 2)
Phase 5	Modbus RTU connection attempted, signal interference and data errors identified
Phase 6	Protocol switched to Modbus TCP/IP, clean and accurate data confirmed across both panels
Phase 7	Four-level setpoint logic programmed (50/70/90/110) for all 7 cylinders, hooter wired and tested
Phase 8	BMS graphics built on 10-inch HMI, full system commissioned and handed over to client

Frequently Asked Questions

Why four alarm levels? Why not just one?

One alarm is too late. By the time a single alarm fires, the situation may already be critical.
The four-level system gives two warnings on the low side and two on the high side. The team gets a Low alarm at 70 — well before the dangerous Low-Low level of 50. That is time to act, time to call someone, time to replace a cylinder. One alarm gives you a shock. Four levels give you a plan.

Why use 4–20 mA and convert to 2–10V? Why not use 2–10V directly?

Three reasons.
First — voltage drops over long cables. A 2–10V signal loses strength over distance. By the time it reaches the controller, the reading is slightly off. 4–20 mA current does not drop over distance. It arrives exactly as it left the sensor.
Second — voltage picks up noise. Motors and electrical panels nearby disturb a voltage signal. The reading drifts. 4–20 mA is much stronger and resists that interference completely.
Third — 2–10V struggles to detect a broken wire. If a cable breaks, the voltage reading becomes uncertain or zero — which the controller cannot clearly separate from a genuine low-pressure condition. With 4–20 mA, the normal minimum is 4 mA. If it drops to 0 mA, you know immediately the wire is broken or the sensor has failed.
So we transmit in 4–20 mA — strong, stable, and fault-detectable. Then we convert it to 2–10V right at the panel so the controller can read it. Best of both worlds.

What is the difference between Modbus RTU and Modbus TCP/IP?

Modbus RTU uses old serial cables. In noisy environments — like a pharma facility with motors and electrical panels nearby — those serial cables pick up interference and corrupt the data. Values jump around and cannot be trusted.
Modbus TCP/IP uses standard Ethernet cables. It has built-in error checking and correction. It is designed for exactly these kinds of noisy industrial environments.
We used Modbus TCP/IP. It worked cleanly from day one.

What does the 16UI/8UO IP module do?

Think of it as a remote helper sitting close to the cylinders.
It collects signals from 16 digital inputs — things like pressure switches and alarm contacts. It controls 8 digital outputs — things like the hooter relay and indicator lights. All of this travels over the network to Panel one's controller, as if everything were in one single cabinet.

Can this system grow to handle more cylinders later?

Yes, easily. The 4–20 mA standard works with almost any pressure sensor. The Modbus TCP/IP network can support more I/O modules. Adding cylinders means adding transmitters, wiring them to available input channels, and programming the setpoint logic. The core system does not need to change.

What does the HMI screen actually show the operator?

A live visual of all seven cylinders. Each one shows its current pressure reading, its alarm state in colour — green is normal, yellow is warning, red is critical — and whether the hooter is active. One screen. Full picture. No walking required.

Download the Full Case Study

Get the Full Syngene Biotech Case Study

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

Download PDF →

This Is What a Real BMS Upgrade Looks Like

The Syngene Biotech story is simple.
A pharma lab had seven critical gas cylinders. They were being watched by one person, with one pen, on a schedule. When that person went home, the cylinders were alone.
We came in and changed that completely.
We used 4–20 mA sensors and converted the signal properly to 2–10V at the panel — because direct voltage transmission is unreliable over distance and in noisy environments. We built two panels — one for control, one for field I/O — and connected them cleanly using Modbus TCP/IP after proving that Modbus RTU could not handle the site conditions. We programmed four alarm levels per cylinder so the team always has time to respond before a real crisis. We built BMS graphics on a 10-inch screen so any operator can see the full picture in seconds.
Before us — one man, seven cylinders, a pen.
After us — one screen, seven cylinders, zero guessing.
That is what we do at Ensmart.

← Back to all case studies