TL;DR:<\/strong><\/p>\n Explore Mestric<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n Povezava starih strojev, or connecting legacy machines to an MES, starts with an honest audit of what each asset can tell you, not what you wish it could tell you. Skip this step and every gateway decision downstream becomes a guess.<\/p>\n Build a minimal asset register before you buy anything. For each machine, record:<\/p>\n Once you know what\u2019s physically available, prioritise the tags that move the needle: overall equipment effectiveness (OEE) components, cycle time, stop reasons, and quality flags. These four data points alone justify most pilot projects.<\/p>\n Probe safely. Read-only sampling and non-intrusive polling let you confirm signal quality without touching machine logic, and you should get sign-off from the machine\u2019s owner or maintenance lead before connecting anything, even passively. A legacy system assessment<\/a> done properly gives you exactly this: a documented picture of what each asset can deliver before a single sensor is wired in.<\/p>\n Point-to-point integration, where each machine gets its own custom link straight into the MES, looks cheap on the first machine and expensive on the tenth. Every new device means a new driver, a new failure point, and a new person who has to remember how it was wired. Maintenance costs multiply roughly in line with machine count, not in line with value delivered.<\/p>\n A dedicated connectivity layer, sometimes called an industrial gateway or connectivity server, solves this by sitting between your machines and everything downstream. It typically handles:<\/p>\n This last point matters more than it sounds. A connectivity layer that speaks native device protocols and outputs OPC UA and MQTT scales far better than wiring each machine directly into whatever system needs it that month. Your MES pulls from OPC UA. Your cloud analytics pulls from MQTT. Neither one waits on the other, and neither one requires a separate integration project.<\/p>\n The operational payoff is a single canonical source of truth. When a new dashboard, a new KPI request, or a new cloud service shows up next year, it consumes the same normalised feed everyone else already trusts.<\/p>\n The honest answer is usually \u201cmore than one,\u201d because your machines are speaking different languages and your consumers have different needs.<\/p>\n Use OPC UA<\/strong> for on-premises MES and SCADA integration. It\u2019s a secure, structured, vendor-neutral standard purpose-built for exposing machine semantics to higher-level systems, and it\u2019s what most MES platforms expect to talk to. Beckhoff\u2019s own OPC UA documentation is a solid technical reference if your controls team wants implementation detail.<\/p>\n Use MQTT<\/strong>, ideally with the Sparkplug B<\/strong> payload specification, for cloud and IIoT streaming. It\u2019s lightweight, built for intermittent connectivity, and handles thousands of publish events without the overhead OPC UA carries.<\/p>\n The harder problem is the machine that speaks neither. Most pre-2010 equipment communicates over Modbus RTU or bare serial links, and bridging those takes a few practical options:<\/p>\n Whichever route you take, get the mapping right the first time. Every register you bring in needs an explicit timestamp source, a defined unit, a scaling factor, and a quality flag showing whether the reading is live, stale, or estimated. Skipping this step is the single most common cause of MES dashboards that look plausible and are quietly wrong.<\/p>\n The edge layer, wherever your gateway physically sits, carries the real governance burden. It needs to buffer readings when the network drops, deduplicate repeated polls, and apply a clear replay policy so a reconnect doesn\u2019t flood the MES with backdated values tagged as current.<\/p>\n Network segmentation is non-negotiable. Keep raw Modbus, serial, and proprietary protocols confined entirely to the OT network, and expose only encrypted OPC UA or MQTT traffic upward to IT and cloud systems. A machine that has never been exposed to the internet should not suddenly inherit that exposure because someone plugged a gateway in over a weekend.<\/p>\n Start read-only. Every signal flows from machine to MES, never the other way, until you\u2019ve proven the pipeline is reliable over weeks, not days. Practitioners across the industry consistently flag enabling remote write-back before that governance is proven as the single largest operational risk in brownfield integration projects, and it\u2019s an easy trap to fall into once a pilot looks successful.<\/p>\n Strokovni nasvet:<\/strong> Treat write-back as a separate project with its own sign-off, not a feature you flip on once the read-only pilot works. The two carry entirely different risk profiles.<\/em><\/p>\n A staged brownfield-to-cloud path<\/a> beats a single cutover every time, because it lets you find problems while the stakes are still small. Four phases cover most projects:<\/p>\n Your pilot checklist should stay tight: pick one to three high-value machines rather than the whole floor, validate that incoming data matches what the machine\u2019s own display or logbook shows, test that dashboards and alarms fire correctly under real conditions, and capture baseline KPIs before you claim any improvement.<\/p>\n Budget drivers worth knowing upfront include gateway licence costs, converter and adapter hardware, wiring and labour for machines that need physical rewiring, engineering hours for driver configuration and tag mapping, and testing time before you hand anything to production. Integrating legacy systems is often the costliest phase of an MES rollout<\/a>, and phased implementation with open standards is the most consistent way to keep that cost from spiralling.<\/p>\n Yes, and for many teams this is exactly where to start before committing capital to a full gateway platform.<\/p>\n Low-code platforms and microcontrollers can enable feasible, low-cost retrofits and proofs of concept<\/a>, provided you\u2019re realistic about their limits. None of this hardware is built for industrial vibration, temperature swings, or 24\/7 duty cycles the way a proper gateway is. Use it to prove the concept and win budget, then upgrade to an industrial-grade gateway once the pilot shows real value and the machine is staying connected permanently.<\/p>\n Running a brownfield pilot in isolation is one thing. Turning it into a permanent, reliable part of your operation without months of extra integration work is another. This kind of platform connects directly to your equipment and tracks the KPIs that matter, performance, downtime, quality parameters, and cost, so a pilot doesn\u2019t stall once it proves itself.<\/p>\n A Mestric\u2122 pilot typically covers the same ground this guide walks through: an asset audit of your priority machines, a connectivity test against your existing OPC UA or MQTT feeds, working dashboards built around your baseline KPIs, and a clear view of where bottlenecks are actually costing you money. Rather than leaving your team to stitch together Node-RED flows and a production MES separately, Such a system gives you a path where the pilot data feeds straight into a system built for the shop floor, with KPI tracking and quality monitoring already built in.<\/p>\n If you have read this far, you likely already have one or two machines in mind worth connecting first. Request an on-site demonstration<\/a> to see on your own equipment what such a pilot could look like before you commit further budget.<\/p>\n The teams that succeed here spend disproportionate time on inventory and data quality before they touch a single dashboard, because a beautiful dashboard fed by wrong data is worse than no dashboard at all. The teams that struggle almost always rushed write-back before governance caught up, or scoped the pilot too broadly and lost months to engineering sprawl instead of proof. Keep the pilot small, measurable, and read-only, and let its results make the case for the wider rollout. Do not let ambition outrun your audit.<\/p>\n \u2014 Andra\u017e<\/em><\/p>\n<\/blockquote>\n For deeper architecture detail, the ScienceDirect paper on OPC UA retrofitting frameworks covers layered integration academically. For protocol specifics, Beckhoff\u2019s OPC UA overview is the clearer vendor reference. For low-cost pilot patterns, the Springer study on legacy PLC integration documents Node-RED and ESP32 approaches with their real-world constraints.<\/p>\n Edge first playbook for plant engineers: run a 1\u20133 machine read only pilot in days to weeks with Node-RED or ESP32, then scale the proven feed into your MES.<\/p>","protected":false},"author":1,"featured_media":1462,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1458","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-learn"],"acf":[],"_links":{"self":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/comments?post=1458"}],"version-history":[{"count":2,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1458\/revisions"}],"predecessor-version":[{"id":1461,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1458\/revisions\/1461"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media\/1462"}],"wp:attachment":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media?parent=1458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/categories?post=1458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/tags?post=1458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nTable of Contents<\/h2>\n
\n
What connecting old machines to a modern system actually involves to a modern system actually involve?<\/h2>\n
\n
![\"Engineers](\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-16618\/1788772106448_Engineers-performing-passive-machine-signal-assessment.jpeg\")
<\/p>\nShould you connect machines one by one or build a connectivity layer?<\/h2>\n
\n
Which protocol should you actually use: OPC UA, MQTT, or Modbus?<\/h2>\n
\n
How do you keep legacy connections from becoming a security risk?<\/h2>\n
![\"OT](\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-16618\/1788772103473_OT-network-segmentation-and-read-only-data-flow.jpeg\")
<\/p>\nWhat does a realistic rollout timeline and budget look like?<\/h2>\n
\n
Can you pilot this without buying industrial hardware first?<\/h2>\n
\n
How Mestric helps you move from pilot to production<\/h2>\n
![\"Mestric\"](\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-16618\/1771068359718_mestric.jpg\")
<\/p>\nAuthor perspective: priorities and common traps to avoid<\/h2>\n
\n
Sources<\/h2>\n
\n
Recommended<\/h2>\n
\n