Brownfield plants rarely have the luxury of starting fresh. Ageing Programmable Logic Controllers (PLCs), mixed vendor devices and patchy data can make improvement feel hard. The good news, you can add real insight quickly by integrating what you already have with small, secure upgrades at the edge. This article shows how gateways, open protocols and better tag structures turn clipboard checks into trusted dashboards, typically within a single maintenance cycle.
Why integrate, not replace
Full system replacement is costly and disruptive. A staged integration approach lets you:
- Preserve proven control assets while adding new visibility.
- Reduce risk by limiting change to the data layer, not core control logic.
- Build a foundation for future upgrades, one line or area at a time.
- Deliver operator and reliability benefits your team can see on shift.
At Triple i, our Automation and Control System Engineering team focuses on fit-for-purpose steps that maintain safety and compliance, planned into your normal maintenance windows.
Speaking a common language: OPC UA and MQTT
Legacy PLCs often use a mix of serial and Ethernet protocols. Two modern options make integration practical
OPC Unified Architecture (OPC UA)
A platform agnostic standard for structured data exchange and contextual models. Useful for secure, point to point communication between PLCs, gateways, SCADA and historians.
Message Queuing Telemetry Transport (MQTT)
A lightweight publish and subscribe protocol. Ideal for moving small, frequent payloads from edge devices to brokers, then on to consumers such as SCADA, historians or cloud analytics.
Secure usage essentials
- Segment operational technology networks from corporate networks, and use firewalls and demilitarised zones where appropriate.
- Enforce TLS encryption, unique certificates and least privilege access on servers, brokers and clients.
- Apply role based authentication for operators, maintainers and integrators.
- Plan patching and firmware updates around your change control process.
- Document data flows, who consumes them and why, to support audits and faster troubleshooting.
These cybersecurity measures align with our Asset Services standards for maintaining process integrity.
Our Process Control and Automation experts configure gateways that translate legacy protocols to OPC UA or MQTT — keeping your core PLC logic unchanged.
Edge analytics that pay back quickly
Edge devices sit close to the process, sampling at high rates and filtering data before it leaves the plant. This reduces network load and delivers actionable signals to operators and reliability engineers.
Common, high value use cases
- Vibration: Detects bearing or imbalance issues by trending overall vibration and band specific metrics. Push alerts into SCADA points operators already monitor.
- Temperature: Watch motor, gearbox or cabinet temperatures for early signs of overload or ventilation issues. Use simple rules first, then add models when you have a stable history.
- Energy: Log power factor, kWh and demand peaks on major loads. Correlate with production rate to find waste without risking throughput.
Design tips
- Sample fast locally, publish summary statistics and exceptions.
- Timestamp at the edge to avoid skew and daylight saving confusion.
- Use deadbands and quality flags to avoid noisy charts and false alarms.
- Keep algorithms transparent so operators understand why an alert fired.
These insights can be easily integrated through our Operational Intelligence platform for faster decision-making.
Tag names that stand the test of time
Data is only useful if people can find, trust and reuse it. A clear, consistent tag structure prevents a data swamp and makes dashboards easier to maintain.
Five rules for long term value
- Follow a hierarchy: Site.Area.Line.Asset.Measure. Example: Newcastle.Mill1.RollStand3.Motor_A.Temp_PT100.
- Use SI units in tag metadata: °C, kW, mm, L, as appropriate.
- Avoid vendor specific abbreviations: Prefer plain terms or a documented short code list.
- Version with care: If you must change a tag, retain a reference to the prior name and effective dates in your glossary.
- Document calculations: Record formulas for derived tags, sample rates and any filtering.
Request our Tag Naming Guide with examples and a glossary template your team can extend.
Case pattern: from clipboard to dashboard in four weeks
Every site is different, however a typical brownfield uplift follows this pattern.
Week 1: Discover and design
- Short onsite review of PLCs, networks and historian use.
- Select one pilot asset, for example a critical pump or conveyor.
- Confirm the data points that matter to operators and reliability.
Week 2: Edge and gateway setup
- Install a protocol gateway to expose PLC data as OPC UA and publish selected topics over MQTT where useful.
- Mount an edge device for vibration, temperature or energy, with safe cable routing and local power.
- Configure TLS certificates, user roles and test connections in a staging area.
Week 3: Tag model and dashboards
- Short onsite review of PLCs, networks and historian use.
- Select one pilot asset, for example a critical pump or conveyor.
- Confirm the data points that matter to operators and reliability.
Week 4: Cutover and training
- Move the gateway into service during a planned window.
- Run tool box training with operators and maintainers on what to watch and how to respond.
- Capture feedback, fine tune thresholds and document the handover.
By the end, operators move from manual clipboard checks to a live dashboard that highlights what needs attention, while reliability teams gain clean history to plan interventions.
Getting started
If your plant is balancing production pressure with legacy systems, start with a small, high impact area. Our Integrated Solutions can help scope an architecture that respects your standards and maintenance windows, then scale the same pattern across lines and sites. Explore Integrated Solutions.
Practical takeaway checklist
- Choose one pilot area with a clear reliability or waste problem.
- Use a gateway to expose legacy PLC data via OPC UA or MQTT, secured with TLS and role based access.
- Add edge analytics for one or two signals that matter, for example vibration and energy.
- Adopt a hierarchical tag naming convention with documented units and calculations.
- Build a simple, role based dashboard first, then iterate with operator feedback.
- Schedule changes within standard maintenance windows and follow your change control process.