{"id":296153,"date":"2024-07-08T11:47:31","date_gmt":"2024-07-08T09:47:31","guid":{"rendered":"https:\/\/amorph.pro\/?p=296153"},"modified":"2024-11-25T11:59:09","modified_gmt":"2024-11-25T10:59:09","slug":"message-brokers-and-smartunifier","status":"publish","type":"post","link":"https:\/\/amorph.pro\/ja\/message-brokers-and-smartunifier\/","title":{"rendered":"Message Brokers and SMARTUNIFIER"},"content":{"rendered":"\n

This is a schema of a Message Broker<\/strong>.  Using it for Industrial Data Connectivity<\/strong> seems to be an unwritten law.  Some would call it \u2018low-brainer\u2019 because the centralization of shopfloor equipment data appears to be as natural as it can be.  Further concepts and approaches like Asset Administration Shell<\/strong>, Unified Namespace<\/strong>, or Digital Twin<\/strong> look as if they were supporting or even requiring this approach.<\/p>\n\n\n

\n
\"This<\/figure>\n<\/div>\n\n\n

Is it because it is good and efficient?  Because it solves all problems of IIoT connectivity?  Because there is no other solution?  Certainly not.  In most cases, it is because a Message Broker<\/strong> is an already existing software component, that cost and still costs a lot of money.  Business economists are calling this Investment Protection<\/strong>.<\/p>\n\n\n\n

Advantages of a centralized data connectivity architecture<\/strong><\/h2>\n\n\n\n

There are multiple explanations web-wide, which describe very well how a centralized architecture such as a Message Broker<\/strong> works. To keep it short and crisp:  Data from different sources are being sent to a centralized software component.  Data conversions, consolidations, transformations, security functions, and protocol conversions are being performed, and, after this, the collected data is being distributed to target systems (like MES) or databases.<\/p>\n\n\n\n

The simple aspect of this approach is that the Message Broker<\/strong> is deployed on a server and can therefore be administered and configured centrally.  However, it is a misconception, that you need to follow a centralized IT architecture to do this efficiently.<\/p>\n\n\n\n

In this context, it is crucial to understand the difference between a centralized IT Architecture<\/strong> and a centralized Enterprise Architecture<\/strong>.  While centralized IT means single-instance deployment (redundant systems to provide higher availability not counted) of (virtual) hardware<\/strong> and software<\/strong>, centralized Enterprise Architecture on the other hand means a central provision of concepts<\/strong> and data governance<\/strong>.  See the difference?<\/p>\n\n\n\n

Differences to a decentralized architecture<\/strong><\/h3>\n\n\n\n

Let us do an exercise on how core functions of a data connectivity solution could be de-centralized.<\/p>\n\n\n

\n
\"This<\/figure>\n<\/div>\n\n\n

This subset function list is an example of a combined centralized and de-centralized functional architecture, which is implemented in SMARTUNIFIER<\/strong>.  All functionality, such as the management of Information Models<\/strong> (e.g. Unified Namespace<\/strong>, Asset Administration Shell<\/strong>, Digital Twin<\/strong>), which is part of an Enterprise Architecture<\/strong>, is centralized and should be.  All other functionality concerning connection and data handling is performed within a de-centralized, wherever deployed, Communication Instance<\/strong>. <\/p>\n\n\n\n

But why?  What is the key advantage of de-centralizing these functions?  It all comes down to performance<\/strong>, availability<\/strong>, stability<\/strong>, and finally scalability<\/strong>.  Connections to communication partners need to be stable, ideally for months and years without any interruption and loss of data.  Set it and forget it!<\/strong><\/p>\n\n\n\n

A decentralized architecture does not care about how many Communication Channels are being configured, and how many assets are communicating to how many business applications.  Leave the bottlenecks to where they always have been, namely to the data sources, data targets, and network components, and not to the connectivity solution.<\/p>\n\n\n\n

Downsides of a centralized architecture<\/strong><\/h3>\n\n\n\n

The picture at the top of this blog is only half of the truth.  To add slightly more realism to this approach, let us add only one detail.<\/p>\n\n\n

\n
\"There<\/figure>\n<\/div>\n\n\n

There is not a single data source, there are multiple.  Adding this to the picture makes something really obvious:  Make no mistake, each Message Broker<\/strong> is a single point of failure<\/strong> and, in addition to that, a bottleneck<\/strong>, nicely positioned between the data sources and the upper-level systems (receivers).  Sure, crucial functionalities of a Message Broker<\/strong> are implemented to prevent data from being lost and to enable data to be transferred asynchronously.  This and all reconnection, mapping, protocol conversion, and more logic blows it up into a humongous<\/strong>, resource-consuming<\/strong>, and expensive piece of business application<\/strong>.  Immediately, an IT architect thinks of load balancing and redundancy \u2013 resulting in additional lines in his or her CAPEX planning sheet.<\/p>\n\n\n\n

Now, let us place the centralized and de-centralized approach side-by-side and watch how data packages are being transferred.<\/p>\n\n\n

\n
\"On<\/figure>\n<\/div>\n\n\n

On the left-hand side, you see the centralized Message Broker<\/strong>, handling data packages, converting shop floor protocols in most cases into one standard like MQTT, queuing the messages, and delivering them to the upper-level business applications.<\/p>\n\n\n\n

On the right-hand side, you see the de-centralized SMARTUNIFIER<\/strong> architecture consisting of multiple Communication Instances<\/strong> with their own data package handling, protocol conversion from shop floor standards to business application standards or with an equipment emulation by providing OPC-UA servers<\/strong> (just as an example) to simulate shop floor equipment.<\/p>\n\n\n\n

And there is even more.  Depending on the content of the data packages, each instance can perform real-time Data Contextualization<\/strong> by collecting relevant data from other sources (e.g. production order information out of an MES), contextualizing it with equipment data (e.g. data of a temperature sensor), and providing this contextualized data (e.g. production orders produced with certain temperatures) to analysis systems.  This is almost impossible for centralized systems as they are currently implemented.<\/strong><\/p>\n\n\n\n

One further aspect:  Once there are more than a handful of data packages the performance<\/strong> bottleneck<\/strong> becomes evident.  Just imagine the Message Broker<\/strong> crashes in case of an unforeseen event, compared to a crashed SMARTUNIFIER Communication Instance<\/strong> (red colored).  In the second case only the data packages (green colored) handled by this one instance may be lost.  All other instances and connections continue completely unaffected.  This is SMARTUNIFIER\u2019s share of stability and availability in Industrial Connectivity.<\/strong><\/p>\n\n\n\n

How a decentralized architecture is implemented<\/strong><\/h3>\n\n\n\n

Everybody who has already implemented a decentralized architecture is now fearing what it needs on the development side.  One critical decision is to use the right development architecture.<\/p>\n\n\n\n

With the SMARTUNIFIER<\/strong> Manager<\/strong>, Mappings<\/strong>, which are configured with the low-code<\/strong> mapping editor, are immediately translated into native executable code, linked into a Communication Instance<\/strong> developer project, compiled (yes, with a real compiler) to an enveloped package, which is optimized solely for the purpose of this data connectivity, using the configured Communication Channels<\/strong>, Information Models<\/strong>, Mapping<\/strong> logic, Data Contextualization<\/strong>, etc.  This specialized Communication Instance<\/strong> can then be deployed using the SMARTUNIFIER Manager<\/strong> to an edge device, cloud service (e.g. AWS), or (virtual) server.  Its one and only \u201craison d\u2019\u00eatre\u201d is to provide connectivity in the most stable, high-performance, and easiest way possible \u2013 decentralized<\/strong>.<\/p>\n\n\n\n

SMARTUNIFIER<\/strong> pioneers this de-centralized approach, ensuring seamless integration across diverse industrial equipment and IT systems.  This innovative architecture eliminates single points of failure, bolstering reliability and performance in industrial connectivity.  All of our customers would sign this immediately.<\/strong><\/p>\n\n\n\n

Downsides of a decentralized architecture<\/strong><\/h3>\n\n\n\n

There are no downsides.<\/p>\n\n\n\n

Wait.  There is one!<\/p>\n\n\n\n

As stated above, a centralized Message Broker<\/strong> is often already in use, sometimes even for decades now.  It is seldom that IT departments want to completely eliminate this piece of investment and OPEX planning artifact.  Though it might be a pain to pay more and more license fees when integrating more and more equipment, the status quo is to be maintained.  Replacing an already existing centralized Message Broker with a decentralized solution?  This is too risky and does not protect our spent investment!<\/strong><\/p>\n\n\n\n

SMARTUNIFIER<\/strong> helps you out in this case.  Nobody prevents you from considering your Message Broker<\/strong> as \u201csouth-side equipment\u201d or a \u201cnorth-side upper-level system\u201d.  Just connect with SMARTUNIFIER<\/strong> and shadow either the equipment or the business application or \u2013 even smarter \u2013 directly connect them bit-by-bit and build a decentralized architecture on-the-fly.  This is being done by many of our customers as a brownfield approach<\/strong>.<\/p>\n\n\n\n

SMARTUNIFIER<\/strong> supports hybrid architectures<\/strong>, so you can smoothly transform one to the other architecture over time, risk minimized<\/strong> and cost-effective<\/strong>.<\/p>\n\n\n\n

Let us sum this all up:<\/p>\n\n\n\n

Smart Industrial Connectivity with SMARTUNIFIER: Performance, Security, and Easy Scaling<\/strong><\/h4>\n\n\n\n

Unmatched Performance and Security: Engineered to excel in demanding industrial connectivity<\/strong> environments, SMARTUNIFIER<\/strong> delivers unparalleled data transfer speeds and robust security protocols. Trust in SMARTUNIFIER<\/strong> to ensure critical operations run smoothly while upholding data integrity.<\/p>\n\n\n\n

Effortless Scalability: As your business expands, so do your industrial connectivity<\/strong> needs. SMARTUNIFIER<\/strong> effortlessly scales to accommodate growing data volumes and complex integration requirements, all without sacrificing efficiency or performance in industrial connectivity.<\/p>\n\n\n\n

Intuitive Interface: Unlike many industrial solutions, SMARTUNIFIER<\/strong> features a user-friendly interface tailored for industrial connectivity.<\/em> Empower your team with the ability to manage and monitor integrations seamlessly, reducing reliance on specialized IT personnel in industrial connectivity.<\/p>\n\n\n\n

Why SMARTUNIFIER Stands Out in Industrial Connectivity<\/strong><\/h4>\n\n\n\n

While competitors offer strong integration capabilities, SMARTUNIFIER<\/strong>‘s decentralized architecture<\/strong> and user-centric design set it apart in industrial connectivity. Say goodbye to centralized bottlenecks\u2014SMARTUNIFIER<\/strong>‘s distributed approach ensures continuous, high-speed data flow in industrial connectivity. Plus, its straightforward interface translates to faster implementation and reduced training times, giving your business a competitive edge in industrial connectivity<\/em>.<\/p>\n\n\n\n

Experience the Future of Industrial Connectivity with SMARTUNIFIER<\/strong><\/h4>\n\n\n\n

SMARTUNIFIER<\/strong> isn’t just a data integration tool; it’s a revolutionary platform designed to future-proof industrial operations and enhance industrial connectivity. Its blend of de-centralization, high performance, scalability, and ease of use makes it the ultimate choice for businesses seeking to elevate their industrial connectivity infrastructure. Embrace the future of industrial connectivity with SMARTUNIFIER<\/strong> and unlock unparalleled efficiency and reliability in your industrial processes. Transform your industrial connectivity with SMARTUNIFIER<\/strong>‘s advanced integration system, and experience seamless data integration, unmatched performance, and effortless scalability for your industrial operations.<\/p>\n\n\n\n

BOOK a demo<\/h3>\n\n\n\n

Ready to boost your Industrial Connectivity<\/em>? Contact us today to explore how SMARTUNIFIER<\/strong> can transform your operations and maximize industrial connectivity efficiency.<\/p>\n\n\n