Our Automation Vendor Can’t Fix Our Network Issues: When You Need More Than Just Controls Expertise

Your automation vendor did a great job installing your new SCADA system. The controls work beautifully. The HMIs display exactly what you need to see. The PLCs communicate with all the right sensors and actuators. Everything on the plant floor works as promised.

Then the network switch fails, and suddenly, half your plant can’t communicate. You call your automation vendor. They send someone out who can tell you that the PLCs have lost connectivity, but when you ask them to diagnose the network issue, they’re out of their depth. “We do controls, not networking,” they say.

So now you’re stuck. You need SCADA system support, but you’re discovering that automation expertise and IT infrastructure expertise are two very different things. And unfortunately, you need both.

The Skills Gap Nobody Talks About

Automation vendors are experts at their craft. They understand process control, industrial protocols, and how to configure systems to manage complex manufacturing processes. They can program a PLC to maintain precise temperature control or coordinate the timing of multiple production steps.

What they typically don’t have deep expertise in:

• Network architecture and troubleshooting
• Switch configuration and VLANs
• Firewall rules and security
• Wireless infrastructure
• Integration with business systems
• Backup and disaster recovery for IT infrastructure

Meanwhile, traditional IT providers understand networking, security, and infrastructure but they’re often intimidated by industrial systems. They don’t want to touch anything connected to production because they don’t understand the implications.

This creates a gap right in the middle of your critical infrastructure. Your SCADA system sits at the intersection of automation and IT, and problems in either domain can bring it down.

Why This Matters More Than Ever

Ten years ago, this gap was smaller. Industrial control systems were often completely isolated from the rest of your network. They ran on proprietary protocols over dedicated cabling. The automation vendor’s scope ended at making the controls work, and that was sufficient.

Today’s manufacturing environment is different:

• Everything connects to Ethernet. Modern PLCs, HMIs, and SCADA systems use standard networking protocols. That means they depend on the same switches, routers, and network infrastructure as the rest of your business.
• Data needs to flow everywhere. Your ERP system needs production data. Your maintenance team needs equipment health metrics. Management wants dashboards showing real-time performance. All of this requires reliable network connectivity.
• Remote access is essential. Vendors need to dial in for support. Engineers need to access systems from home during emergencies. Operators might need to monitor systems from multiple locations. This requires VPNs, firewall rules, and secure remote access for all IT functions.
• Cybersecurity is critical. Your SCADA system might be running on older operating systems that can’t be easily patched. It needs to be protected by network segmentation, firewall rules, and monitoring of all things that require networking expertise.

The Classic Scenarios Where This Breaks Down

Scenario 1: The Switch Failure

A network switch fails on the plant floor. Your automation vendor can identify that PLCs have lost connectivity, but they can’t diagnose why the switch failed, whether it’s a configuration issue, or what the proper replacement procedure is. Meanwhile, production is down.

Scenario 2: The Bandwidth Issue

Your SCADA system starts running slowly. HMI screens take forever to load. The automation vendor checks the server and says everything looks fine on their end. But nobody’s looking at network utilization, Quality of Service settings, or whether other traffic is saturating the network.

Scenario 3: The Remote Access Problem

You need to give a vendor remote access to your SCADA system for troubleshooting. Your automation vendor says, “Just give us VPN access.” But your IT team (if you have one) is concerned about security. Nobody knows how to set up secure, limited access that satisfies both the functional need and security requirements.

Scenario 4: The Integration Failure

Your new SCADA system needs to communicate with your ERP. The automation vendor says their system is configured correctly and can communicate over the network. Your ERP vendor says their system is fine. But data isn’t flowing. The problem is in the network layer firewall rules, routing, or protocol issues and neither vendor wants to own it.

What Proper SCADA System Support Actually Requires

Supporting modern industrial control systems effectively requires a partnership between automation expertise and IT infrastructure expertise. Here’s what that looks like in practice:

Network Architecture

Someone needs to design and maintain a network architecture that:

• Provides reliable, redundant connectivity for critical control systems
• Implements proper segmentation for security
• Ensures adequate bandwidth and low latency for real-time communications
• Includes proper documentation so problems can be diagnosed quickly

This is IT work, but it requires understanding industrial requirements. Standard office networking practices don’t always apply when you need deterministic response times for process control.

Monitoring and Alerting

Industrial systems need monitoring at multiple levels:

• The automation vendor monitors the health of the control systems themselves
• IT monitors network performance, switch health, and overall infrastructure
• Both need to coordinate when alerts fire so issues can be diagnosed quickly

Security Implementation

Securing SCADA systems requires both types of expertise:

• Automation vendors understand what ports and protocols the systems need
• IT experts implement firewalls, network segmentation, and monitoring to allow required communications while blocking threats

Troubleshooting and Support

When something goes wrong, you need rapid coordination:

• Is it a control issue or a network issue?
• Who needs to be on the call?
• What diagnostic tools and data are needed?
• What’s the escalation path if the issue spans both domains?

Building the Bridge

If you’re dealing with this gap in your organization, here are practical approaches:

• Document the boundaries clearly. Get your automation vendor and IT support on the same page about where their responsibilities begin and end. In writing. With specific examples.
• Create communication channels. When something goes wrong, your automation vendor and IT support need to be able to talk to each other quickly. Don’t make your plant manager play intermediary.
• Invest in network documentation. Document your industrial network thoroughly: what devices exist, how they’re connected, what protocols they use, and what IP addresses are assigned. Both your automation vendor and IT support should have access to this documentation.
• Consider managed network infrastructure. Having IT professionals who specialize in industrial networking can bridge the gap. They understand both the networking side and enough about industrial systems to communicate effectively with automation vendors.
• Plan for remote support. Set up secure remote access procedures in advance. Don’t wait until you have an emergency to figure out how vendors will access your systems.

The Cost of Leaving This Gap Unaddressed

When automation and IT don’t work together effectively, you end up with:

• Extended downtime. Issues that should take 20 minutes to resolve take hours because you’re trying to coordinate multiple vendors who are pointing fingers at each other.
• Security vulnerabilities. Automation vendors might recommend practices that create security risks. IT might implement security measures that break industrial functionality. Nobody has the full picture.
• Integration failures. Projects to connect your SCADA system to business systems stall out because nobody owns the integration layer.
• Lack of visibility. You can’t get the data you need from your production systems because nobody can make the connections work reliably.

Moving Forward

If you’re currently caught between an automation vendor who doesn’t do networking and an IT provider who won’t touch your production systems, you’re not alone. This is one of the most common gaps in manufacturing IT.

The solution isn’t choosing one or the other. It’s finding or building a bridge. That might mean:

• Finding manufacturing IT services with hands-on production experience that can work directly alongside your automation vendor
• Training your internal staff to handle the networking aspects of industrial systems
• Working with an integrator who has both automation and networking expertise

The key is recognizing that modern SCADA system support requires both skill sets. Your automation vendor is critical for the controls expertise. But without solid IT infrastructure support underneath, even the best-designed control system will have reliability issues.

When you get this right, you’re not constantly dealing with finger-pointing between vendors. Issues get diagnosed and resolved quickly because the right expertise is available when needed. And your production systems have both the functionality and the reliability they need to keep your plant running.