IT Support for Manufacturing Companies in Bangalore: A Shop-Floor Buyer's Guide

Most manufacturing IT contracts in Bangalore are written for the wrong building

A 180-person auto-components plant off Tumkur Road ran three shifts. Their AMC vendor, a competent office-IT shop, had signed a 120-device contract in 2024 at ₹1,450 per device per year. Every month the plant manager logged the same two complaints: the shop-floor label printers dropped off the network during the second shift, and the ERP goods-receipt screen froze every time the CNC cell started a new batch.

The vendor kept resolving tickets. Deflection rate looked fine. Nothing was fixed. In March 2025, a label printer failed during a dispatch window and 40 pallets went out with handwritten tags. The customer rejected the shipment at their Pune dock. Cost to the plant: ₹6.8 lakh in rework, transport and a lost quarter of business with that buyer.

The problem was never the ticket response time. It was that nobody had looked at where the cables ran, what generated the electrical noise, or which VLAN the ERP client shared with the SCADA historian. Office-IT thinking, applied to a factory floor, will pass every SLA metric and still cost you a customer.

This piece is about that gap. If you run a manufacturing unit in Bangalore with 20 to 500 staff and you are evaluating IT support right now, the decisions below are the ones that actually determine whether your lines stay up.

Why factory IT breaks differently from office IT

An office has forgiving failure modes. If a switch drops, a manager loses email for eleven minutes and life continues. A plant has unforgiving ones. If the same switch drops and it happens to carry the conveyor PLC's Modbus TCP traffic, the line stops, and every minute of stoppage has a rupee value attached to it that is almost always larger than the annual support cost.

Three structural differences matter.

Environmental hostility. Metal dust, coolant mist, 42°C ambient near furnace areas, vibration from presses, and monsoon humidity. Consumer switches rated for 0-40°C in a sealed air-conditioned room are being installed in unsealed electrical panels. A ₹4,500 8-port unmanaged switch will last three years in an office and eleven months on a press-shop panel.

Long equipment life against short software life. The average CNC controller or injection-moulding machine on a Bangalore shop floor is 12 to 18 years old. The Windows PC bolted next to it is 4 to 7 years old. Your ERP is on a 6-month release cadence. Your firewall firmware has CVEs patched monthly. The support model must keep a 2009 Fanuc controller talking to a 2026 ERP without exposing either.

Nobody owns the boundary. In most plants we walk into, the PLC and drives belong to the maintenance or electrical team, the ERP and network belong to accounts or a part-time IT person, and the CCTV and access control belong to admin. Connectivity between these three islands is nobody's job until it breaks. Then it becomes everyone's emergency.

OT and IT segmentation: what to actually build

Most manufacturing plants do not need a formal Purdue Model implementation. They need to stop IT and OT sharing one flat 192.168.1.0/24 network, which is what we find in roughly six of every ten plants between Peenya, Bommasandra and Nelamangala.

The four-zone model that works for 20-500 staff plants

Notice the direction of cost. The iron on the shop floor does not need to be expensive. It needs to be sealed, DIN-rail mounted, wide-temperature rated (typically -10 to 60°C), and fed from a separate circuit. The intelligence — ACLs, logging, rules — sits one level up.

The rule we follow: no traffic crosses from Enterprise IT to Cell OT. Ever. If a business application needs machine data, it reads it from the DMZ broker. That broker is the only thing both sides are allowed to talk to, and it is configured with a deny-by-default policy where only specific OPC-UA tags and specific source IPs are whitelisted. Six protocols, one direction, one port range.

What this costs at a 100-machine plant

An 80-150 machine plant, two buildings, three shifts, in a Bangalore industrial estate should budget ₹12-22 lakh in 2026 for the segmentation project done properly: industrial switches, DIN enclosures with thermal management, fibre uplinks between buildings (armoured, because you are pulling it through a cable tray alongside 3-phase power), a firewall pair, and the engineering time to map tag flows. Existing Cat6 run badly in the same conduit as VFD cables will need to be replaced — expect ₹180-320 per metre installed for armoured fibre, ₹45-90 per metre for shielded industrial Cat6A with proper earthing.

If that number feels steep, run the other calculation. What does one unplanned shift stoppage cost your plant? For most Bangalore precision-engineering units we work with, the number is ₹90,000 to ₹4.5 lakh per hour depending on the line. The segmentation project pays for itself on avoiding two stoppages a year.

Where we would tell you not to do this

If you run a single-line, single-shift fabrication unit with 25 staff, one PLC, and everything in one room, full segmentation is overkill. You need a decent managed switch, a separate VLAN for the machine, a UPS on the panel, and someone who answers the phone at 7am when shift one starts. That is a ₹1.8-3.2 lakh job for the hardware and a support contract on top. We will tell you that directly rather than sell you a Purdue Model diagram.

Ruggedised endpoints: what survives a shop floor

The standard advice is to buy industrial PCs. That is correct in some places and a waste of money in others. Here is how we split it.

Where an industrial PC earns its price

Control-room HMI stations, machine-mounted operator terminals, weighing and batching stations, and any PC within two metres of a press, moulding machine or welding cell. In these positions, the failure drivers are vibration, conductive dust, and temperature cycling. Industrial panels from Advantech (TPC-1251T, roughly ₹1.1-1.5 lakh for a 12-inch touch unit in 2026) or Siemens SIMATIC IPC (₹1.4-2.2 lakh) survive where a ₹38,000 business desktop dies in fourteen months.

We have replaced enough dead office PCs on press-shop walls to know the arithmetic. If a desktop lasts 14 months and an industrial panel lasts 7 years, the industrial panel is cheaper even at four times the price, before you count the downtime.

Where a ruggedised laptop or tablet is the right answer

Supervisors walking the floor with a checklist, quality inspectors doing in-process checks, and maintenance teams logging breakdowns at the machine. A Panasonic Toughbook FZ-55 (₹2.1-2.8 lakh in 2026) or a Dell Latitude 5430 Rugged (₹1.9-2.4 lakh) with an IP53 rating and a hot-swap battery changes how a shift supervisor works. The alternative — paper logbooks transcribed into ERP three days later — costs you traceability you will need the day a customer audit arrives.

If budget is tight, a mainstream business laptop with a rugged case (Pelican 1085, ₹9,500-13,000) and a 3-year accidental damage warranty (₹18,000-26,000 add-on) gets you 70% of the benefit at 40% of the cost. What it does not survive is a fall onto a concrete floor from waist height, which is why we only recommend this for supervisors who mostly stay on walkways, not the ones climbing onto machines.

Barcode, label and vision hardware

Zebra ZT411 industrial label printers (₹95,000-1,30,000) at each dispatch bay, wired, not wireless, with a dedicated VLAN and a static IP. Wireless label printers on a plant floor are a recurring support cost; Bluetooth pairing drops mid-shift, and dispatch staff will not troubleshoot it. Zebra MC3300 handheld scanners (₹55,000-78,000 each) with a charging cradle at each station. These are the devices that decide whether your ERP transaction data is real or approximate.

Uptime across shifts: the SLA conversation nobody wants to have

An office SLA of "response within 4 business hours" is meaningless to a plant running 6am to 10pm. Your second shift starts at 2pm; your third at 10pm. Your support window needs to cover the transition points, because that is when line handovers happen and when problems are discovered.

What the coverage tiers should look like

Do not buy 24x7 on 120 devices. Buy it on the 12 devices that matter — the ERP application server, the network core, the firewall pair, the SCADA server, the label printer at the main dispatch dock. Everything else can be extended-hours. This is how you keep the monthly cost in a sane range while still covering the assets whose failure stops the plant.

We list the coverage options and what each one includes on our clients page, which is worth a look if you are comparing us against another provider.

The on-site question

Remote support handles a lot in 2026 that it could not in 2018. Firewall rules, ERP patches, AD changes, backup verification, endpoint alerts — all doable from anywhere. What remote support cannot do is reseat a loose SFP in a panel on the shop floor, replace a failed industrial switch at 11pm on a Sunday, or trace a cable that a maintenance contractor cut last week while installing a new air line.

For a Bangalore manufacturing plant, the practical model is a provider with a reasonable on-site radius. If your plant is in Peenya, the provider should be based within 15-25 km or accept that a 2-hour on-site commitment is aspirational on a Friday evening with Outer Ring Road traffic. Ask for the physical address of the engineers who will respond, not the sales office.

ERP integration on the factory floor

The common ERP pattern in Bangalore manufacturing is Tally Prime for smaller units, SAP B1 or Zoho Books in the middle, and SAP S/4HANA or Oracle NetSuite above 300 staff. All of them have to talk to shop-floor systems, and the integration design is where plants quietly lose data integrity.

The three integration patterns we see

Direct database polling. A .NET service running somewhere polls the ERP database every 30 seconds and writes to a text file that a shop-floor application reads. Simple to build, and the single most common source of phantom inventory in Indian plants. When the ERP is patched or the SQL server restarts, the service silently fails and no one notices for days. We have seen three weeks of unposted goods receipts at a Mangalore-based unit.

Middleware brokered. An integration engine — MuleSoft, Boomi, or an in-house service — sits between ERP and shop floor, handles retries, queues messages, and raises alerts. More robust. Requires someone to own it. Cost: ₹6-18 lakh for the initial build, ₹1-3 lakh annual maintenance.

API-first. Modern ERPs, especially SAP S/4HANA and Oracle Fusion, expose and consume APIs directly. Any new shop-floor system you buy in 2026 should be evaluated on whether it can be an API client, not on whether it can write to a database. If a vendor's machine-monitoring tool only supports ODBC connections, that is a signal about their engineering quality.

The real-world gotcha: time

Every plant we support has faced this. The PLC clock drifts. The shop-floor PC has different NTP settings. The ERP server is in Singapore. The label printer timestamps in local time while the printer queue writes UTC. Result: batch records that do not reconcile and traceability reports that quality auditors reject.

Fix it once, properly. A local NTP server on the DMZ (a small industrial PC running chrony, ₹45,000-70,000) that syncs to an external pool and serves time to every device that logs anything. Then a written policy that all shop-floor systems run in a single timezone and format. This is a half-day of work that saves you weeks over a year.

The legacy controller problem, honestly

You have a Mitsubishi FX series PLC from 2008 on line 3. The programming laptop that can talk to it runs Windows XP, and it is sitting in a dusty cupboard because it is the only machine with the right COM port and the vendor software that will not install on anything after XP SP3.

This is the single most under-supported area of factory IT in India, and it is also where most support providers quietly check out.

The choices, in order of how we actually recommend them

Air-gap and document. If the PLC is not networked and only needs occasional programming, do not fix what is not broken. Get the programming laptop, image its disk, store a copy, put it in a locked cabinet, and set up a secondary laptop with the same software as a spare. Cost: ₹18,000-35,000 for a refurbished laptop plus the software licence transfer, and a few hours to build images.

Isolate on its own switch with a NAT. If the PLC needs to send data to a supervisory system, put a managed switch (₹22,000-35,000) between the PLC and the rest of the world and do port-level one-to-one NAT so the downstream side only sees one IP. This keeps the flat legacy protocol off your main VLAN without touching the PLC.

Protocol gateway. A device like an HMS Anybus X-gateway (₹65,000-1,20,000) or a Softing gateWay (₹80,000-1,50,000) translates Modbus RTU or Profibus DP into OPC-UA or EtherNet/IP. This is the clean answer, and it is also the one that requires you to know the exact PLC model and firmware.

Virtualise the legacy. Keep the old programming environment in a virtual machine running on a modern host, with a USB-to-serial adapter passed through. This works about 60% of the time; the other 40% fails on timing-sensitive dongles or hardware keys. Do not buy a server for this without testing first.

Replace the controller. Sometimes the correct answer. A 2007 S7-300 with a failing power supply is not a support problem; it is an end-of-life decision. Replacement is ₹2.5-6 lakh for small cells and takes the line down for at least one shift. Plan it during a scheduled shutdown, not on a Tuesday when the power supply finally dies.

What we do not recommend is exposing a legacy PLC through a VPN directly to the internet so your vendor in Pune can support it. That is a breach waiting to happen, and in 2026, with CERT-In's incident reporting requirements and the DPDP Act in force, an exposure that leaks customer or employee data is a legal problem on top of an operational one.

A failure story worth reading twice

A 140-person sheet-metal and fabrication unit in an industrial area north of Bangalore, running press brakes, laser cutting and powder coating, had a single flat network. All 47 PCs, 6 laser machines, 3 press brakes, 4 CNCs, the paint-line conveyor PLC, the ERP server, the CCTV NVR and the access control system shared one /24.

In August 2024, a maintenance contractor plugged a personal laptop into a wall port to charge his phone. The laptop came with a pirated Windows 10 build loaded with a Monero miner and a worm that scanned for SMB. It found the ERP server's unprotected file share within 90 seconds.

What happened over the next 40 hours:

• The miner consumed CPU on the ERP server, and the laser operators started seeing 40-60 second delays on job loading.
• The worm replicated to the CCTV NVR and the access control system.
• A backup job started during the incident copied encrypted ERP data to tape.
• The paint line's conveyor PLC rebooted twice due to network stack flooding.

Direct cost: ₹4.2 lakh (forensic team, two days of emergency support, replacement of the NVR, factory reset of all machine HMIs). Indirect cost: three weeks of degraded production, an audit finding that nearly lost them a Tier-1 automotive customer, and a two-month project to fix what should have been fixed years earlier.

The permanent fix took 5 weeks and cost ₹17.8 lakh in total: segmentation into four zones, replacement of 11 unmanaged switches, an industrial firewall (FortiGate 90G in a sealed enclosure, roughly ₹92,000 plus installation), port security on every access jack, 802.1X for staff devices, a proper patch panel with documentation, and an ERP share permission audit that should have happened in 2019.

No part of that fix was exotic. It was just IT support designed for a factory rather than for an office, delivered by people who had walked a shop floor before.

Power, monsoon and the Bangalore-specific realities

Bangalore's industrial estates have particular problems, and if you are signing an IT support contract in 2026, they need to be part of the conversation.

Power quality. Even with a stable grid connection, industrial areas see significant voltage fluctuation when large loads switch. IT equipment needs online double-conversion UPS systems, not line-interactive. For a 48U rack with network gear and a server pair, budget ₹85,000-1,60,000 for a 6-10 kVA online UPS with 30 minutes of runtime. Line-interactive units at ₹25,000-45,000 look cheaper and fail your equipment three years sooner.

Monsoon and cabling. Between June and October, cable trays that run outdoors or through semi-open sheds take on water. Cat6 in a tray with a standing water pool sees capacitance changes that cause intermittent link drops — the kind that no ping test reproduces because the tray drains by the time you arrive. Get your outdoor cabling in conduit or armoured, and inspect your trays before June.

ISP lead times. For a factory in an industrial estate, expect 10-21 working days for a new fibre leased line from the major operators, and 4-8 weeks for a second provider on a different route. Do not assume a single ISP is enough. If your ERP is cloud-hosted and your primary ISP goes down, your production stops. Dual WAN with automatic failover (a FortiGate 90G handles this natively, or a dedicated SD-WAN appliance at ₹35,000-1,20,000) is the minimum for a plant that depends on an ERP.

GST on support contracts. IT AMC and managed services attract 18% GST. Hardware attracts GST at the applicable slab, usually 18% for IT gear but 28% for some categories. If you are buying a bundle, get the invoice broken out so you can claim input tax credit correctly. Some vendors quote a single lump sum; you want the split.

CERT-In and DPDP. CERT-In's 2022 directions require incident reporting within 6 hours of noticing a cyber incident. If your plant is breached via an exposed legacy system, you are on the clock immediately. The DPDP Act, now in its implementation phase, adds obligations around personal data of employees and any customer data in your systems. Factory IT is in scope. If a support provider does not mention these in the contract, they are behind.

What managed IT support for a Bangalore plant actually costs

We are going to give you ranges and stop hedging. These are 2026 numbers, GST excluded, for a Bangalore manufacturing unit.

What is not in that table, and should be, is your own staff time. Most plants we onboard have an internal person spending 60-80% of their week on IT instead of on their actual job. If that person costs ₹6 lakh a year, you are already spending the equivalent of a managed contract in internal effort before you count downtime.

The right answer may still be internal-plus-a-few-critical-services. A 60-person welding and fabrication unit that we support keeps an internal IT person for day-to-day and uses us for the network, firewall, backup and ERP integration work. That split costs less than a full managed contract and works because the internal person knows the plant and we handle what needs specialised depth.

Choosing a provider: the questions that separate real from rehearsed

Ask these, and listen to the answers, not the marketing deck.

"Who is the engineer who will respond to an on-site call, and where is that engineer based?" If the answer is vague, so is the SLA.

"Show me a plant you currently support with a segmented OT network. Walk me through the zone design." A provider who does manufacturing support will have this at hand. A provider who mostly does offices will describe it in generic terms.

"What is your escalation path when a legacy PLC on the shop floor loses communication after an ERP patch?" This is the question that separates support providers. The answer should mention the vendor of the integration layer, the specific logs, and how they will involve the ERP partner if it turns out to be an ERP-side change.

"Have you worked with Honeywell, Rockwell, Siemens or Mitsubishi support channels?" If your plant runs machines from any of these vendors, your IT provider needs to know how to interface with their field service without stepping on the warranty.

"What is your onboarding process for a new contract, and how long does it take?" Any provider willing to take over your 140-device plant in one week is either overstaffed or not doing the work. A real onboarding takes 4-8 weeks: documentation, credential handover, testing every backup, walking the floor, meeting shift supervisors, and mapping every asset to a physical location.

If you have read this far and want to talk specifics, get in touch — but bring your asset list, your shift pattern and your last three months of downtime causes with you. That conversation is fifteen minutes, not a two-hour presentation.

Common mistakes we see plants make

Treating the shop floor as a home for old office PCs. The PC that was retired from accounts last year is not appropriate to control a paint-line operator terminal. If it just barely runs Office, it will not run an HMI reliably in an unsealed panel.

Buying industrial PCs where a business PC would do. The QC lab, the dispatch office, the store room — these are all fine with normal desktops. Only the actual machine-side positions need industrial hardware.

Letting the OEM of your machines install their own network. Machine OEMs optimise for their machine, not for your plant. We have seen a laser cutter shipped with a default IP of 192.168.1.50 collide with the plant's flat network after every install. Reserve a dedicated IP range per machine class before the OEM arrives.

Skipping the electrical earthing audit. Shielded cable and industrial switches do nothing if your earthing is not proper. Spend ₹35,000-70,000 on a proper earth-pit inspection and remediation before you buy any industrial networking gear.

Assuming the plant internet connection is fine because the office is fine. They often come in on the same line and the shop-floor cabinet sits three hops away on a long-run copper cable. Test from where the machines actually are, not from the conference room.

Buying a firewall and not managing it. An unmanaged FortiGate with default rules is a fake security posture. Budget for the annual subscription (typically ₹25,000-60,000 for the models used in mid-size plants) and the managed hours to actually tune it.

FAQ

How much does IT AMC cost for a manufacturing plant in Bangalore?

For a plant with 20-50 staff and 20-35 devices, expect ₹28,000-55,000 per month in 2026 for a managed contract that includes on-site support during operating hours. Add 18% GST. Multi-shift plants with 120-250 staff typically run ₹1,10,000-2,20,000 per month. The variance is driven by shift coverage, number of critical assets, and whether OT network management is in scope or billed separately.

Can an office IT support company handle our factory?

Sometimes, on the enterprise IT side. Very rarely on the OT side. The differences in cable routing, environmental ratings, protocol handling, and legacy controller support are significant enough that most office-focused MSPs will either skip these questions or agree to things they cannot deliver. Ask for a reference plant of similar size and visit it.

Do we need a separate network for our CNC machines?

If you have more than two machines with a network connection, yes. A separate VLAN is the minimum; a separate physical switch and a firewall rule set is the correct answer. Flat networks where machine controllers share a broadcast domain with office PCs are the leading cause of production-hour incidents we investigate.

How long does it take to migrate our plant to a proper IT setup?

A full segmentation and modernisation for a 100-150 machine plant takes 6-12 weeks of coordinated work, with the heaviest disruption in the first four weeks. Most of the work happens without stopping production; the only genuine downtime windows are for switch cutovers, which we schedule during planned shutdowns or low-load hours. Cutting over a plant network on a Tuesday morning is how you lose a customer.

What about Windows 10 end-of-support on shop-floor PCs?

Windows 10 support ended in October 2025. If you still have shop-floor PCs on it (and we find plenty in 2026), you have three choices: upgrade to Windows 11 where the hardware supports it, replace the hardware, or isolate those PCs from the network entirely with a written risk acceptance. Continuing to run internet-connected Windows 10 in an unpatched state in 2026 is not a decision that survives a customer audit.

Do we need cybersecurity specifically for the shop floor?

Yes. The 2024 incident we described earlier started when someone plugged an infected laptop into a wall port. A shop-floor-specific security posture includes network segmentation, port security, endpoint detection on any Windows-based HMI, monitoring for abnormal traffic between zones, and a tested incident response plan that includes your OT team. The tooling cost is usually ₹3-8 lakh one-time and ₹1.5-4 lakh annually for a mid-size plant in 2026.

What to do this week

Print this article. Walk your shop floor with it. For every machine that has a network cable, write down what it connects to, which switch, and where that switch is physically. In most plants, this exercise alone surfaces one device that has been unmanaged for years and one switch nobody can identify.

Then do two things. First, model your downtime cost per hour — you need this number before any vendor conversation, because it decides what you can afford. Second, call your current support provider and ask the five questions above, specifically the one about the segmented plant reference. If they come back with names, credible sites, and detailed answers, you are likely in good hands. If they hedge, you know what to do.

Talk to us if you want a comparison against how we would handle it. Bring the asset list you just wrote.