Connecting 20-Year-Old PLCs to Modern Cloud Dashboards

Manufacturing plants often run production equipment for 20-30 years. Your PLCs (Programmable Logic Controllers) work perfectly - but they can't talk to modern analytics platforms. This creates a visibility gap: production happens in real-time, but you only see results hours later via manual reports.

This guide explains how to close that gap without replacing equipment that still works.

The Legacy Integration Problem

A typical factory floor:

• Controllers from Allen-Bradley or Siemens, installed between 1995 and 2010
• Older industrial protocols such as MODBUS, often over serial cables with no network port
• Data you can only see on the screen next to the machine

Meanwhile, your management team wants:

• Real-time production dashboards (accessible from office/mobile)
• Defect rate tracking by shift/operator
• OEE (Overall Equipment Effectiveness) metrics
• Predictive maintenance alerts

How the Connection Works

A small industrial computer, called an edge gateway, sits next to the equipment. It reads the controllers the same way the machine's own screen does, and sends that data securely to a cloud platform. Your team opens the dashboards from the office or a phone.

1. The edge gateway. A fanless industrial PC mounted in the control cabinet. It reads each controller about once a second and stores the data locally if the network drops, so nothing is lost. The hardware typically runs $300-$800 per gateway.

2. The cloud platform. It keeps every reading with its time, so you can compare shifts, lines and months, and it calculates the numbers management asks for.

3. The dashboard. A small number of screens that show what is happening on the floor right now.

What Gets Measured

Before anything is built, we map which values inside each controller hold the data you care about: parts made, defects, whether the machine is running, idle or in error, and temperatures. From those, the platform:

1. Keeps the full history for every line and shift
2. Calculates OEE, which combines availability, performance and quality into one score
3. Spots sudden jumps in defect rate
4. Sends a text or email when a machine goes into an error state

Security Considerations

Older controllers were never designed with security in mind. The connection must:

• Keep production equipment on its own network, separate from office systems
• Let the gateway read the controllers, while nothing outside can reach them
• Encrypt everything sent to the cloud
• Make the gateway and the cloud prove their identity to each other

Never expose PLCs directly to the internet.

Where the Value Comes From

For example, in a plant with $2M in annual production:

• Defect Cost Reduction: 2% improvement on $2M annual production = $40K/year
• Downtime Reduction: Predictive maintenance catches issues 30% faster = $25K/year
• Labor Efficiency: Eliminate 2 hours/day manual reporting = $15K/year

Annual Savings: $80K

Your own numbers will differ, so we measure them during discovery. Every phase has a fixed price approved in writing before work starts.

Common Pitfalls

1. Reading the Machines Too Often

Older controllers are slow. Reading them once a second is plenty for a dashboard. Asking more often can slow the controller down and adds nothing you can act on.

2. Ignoring Network Outages

Factory networks drop. The gateway must store at least a day of data locally and catch up when the connection returns, so no production data is lost.

3. Dashboard Overload

Don't build dashboards with 50 real-time charts. Focus on:

• Production count (parts/hour trending)
• Defect rate (current shift vs. target)
• Machine state (running/idle/error)

Save detailed analysis for historical reports.

Implementation Timeline

Based on typical 5-line manufacturing plant:

• Week 1-2: On-site survey, mapping what each controller records, network assessment
• Week 3-4: Gateway installation and testing the connection to each machine
• Week 5-8: Building the cloud platform and alerts
• Week 9-10: Dashboard creation and operator training
• Week 11-12: Production rollout and monitoring

When NOT to Integrate

Legacy integration doesn't make sense if:

• Your equipment is already scheduled for replacement (< 2 years)
• You're already capturing data via SCADA/MES
• Production volume doesn't justify ROI (< $500K annual output)

In those cases, wait for hardware refresh or use simpler manual reporting.

Next Steps

If you have production equipment that "works great but is invisible," integration can unlock significant value. Start with:

1. List your equipment: Make, model and age of each controller
2. Identify key metrics: What do you actually need to see?
3. Calculate ROI: Use defect/downtime costs from last 12 months

Then schedule a consultation to design your specific architecture.

---

About the Author: Arturas Katutis has 30 years of systems integration experience, including projects connecting legacy financial systems (equally ancient as your PLCs) to modern cloud platforms. He applies the same enterprise-grade patterns to industrial environments.