{"id":46387,"date":"2025-01-01T11:11:00","date_gmt":"2025-01-01T10:11:00","guid":{"rendered":"https:\/\/beta.cybus.io\/?p=46387"},"modified":"2025-01-20T20:35:36","modified_gmt":"2025-01-20T19:35:36","slug":"flowsync-next-level-communication-flow-with-connectware","status":"publish","type":"post","link":"https:\/\/www.cybus.io\/en\/flowsync-next-level-communication-flow-with-connectware\/","title":{"rendered":"FlowSync: Next-Level Communication Flow with Connectware"},"content":{"rendered":"\n
\n

FlowSync ensures a closed communication loop where every request receives a reliable, traceable response. By seamlessly integrating event-driven and request-response workflows, it translates between industrial communication protocols like OPC UA methods and HTTP REST, ensuring full compatibility and precise process control. Cybus Connectware introduces FlowSync as part of our mission to provide a secure, flexible and efficient Factory Data Hub.<\/p>\n\n\n\n

Let’s explore the advantages of using this unique feature with Cybus Connectware<\/a>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The challenge: increasing communication complexity and managing process dependencies<\/h2>\n\n\n\n

Manufacturing systems rely on flawless communication between shop floor technologies like PLCs and IT systems such as MES and OEE tools. Cybus Connectware has long been the benchmark for enabling this seamless interaction and continues to set the standard for robust and reliable system communication in industrial environments. However, as workflows become more complex and diverse, the need for advanced synchronization and decoupling has grown \u2013 and that\u2019s exactly what Cybus has delivered. <\/p>\n\n\n\n

Many manufacturing processes depend on causal execution steps, where Step A must be completed before Step B can begin, followed by Step C. Traditionally, ensuring this structured execution required custom logic, extensive manual intervention and individually defined request-response workflows. Each system had to be manually configured to provide feedback, making it difficult to maintain consistency and traceability across all process steps. As workflows become more advanced, manufacturers need a scalable, automated and fault-tolerant synchronization layer that eliminates manual effort to control process execution \u2013 while maintaining flexibility for upgrades and protocol changes.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The solution: Cybus Connectware\u2019s newest feature, FlowSync and its closed communication loops<\/h2>\n\n\n\n

FlowSync extends Cybus Connectware\u2019s industry-leading capabilities by introducing advanced synchronization for even the most demanding manufacturing environments. By enhancing Cybus Connectware\u2019s HTTP and OPC UA server functionalities, FlowSync provides a powerful layer of decoupling and protocol translation, allowing systems to communicate seamlessly and evolve independently.<\/p>\n\n\n\n

At its core, FlowSync ensures a closed communication loop where every request receives a reliable, traceable response. This innovation bridges event-driven and request-response workflows, translating between protocols like OPC UA methods and HTTP REST to ensure complete compatibility and process control. Even in complex scenarios, FlowSync maintains accuracy, transparency and reliability \u2013 eliminating the need for direct system modifications.<\/p>\n\n\n\n

<\/div>\n\n\n\n

A practical example: synchronizing PLCs and MES<\/h2>\n\n\n\n

Consider a PLC that generates production data requiring processing by an MES system with an HTTP REST interface. In the past, tightly coupled communication would have demanded custom modifications to each system.<\/p>\n\n\n\n

FlowSync transforms this process. The PLC sends data via OPC UA, which FlowSync translates into an HTTP REST request for the MES. Once the MES processes the request, FlowSync relays the response back to the PLC, converting it to OPC UA. This bi-directional flow ensures that each system remains decoupled while maintaining reliable and traceable communication. System upgrades or changes on either side no longer risk breaking workflows, as FlowSync bridges the gap.<\/p>\n\n\n

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

About the example:<\/strong> This example demonstrates a complete FlowSync implementation that creates a bridge between an external DNS service and a local endpoint as shown here.<\/a><\/p>\n\n\n\n

<\/div>\n\n\n\n

The benefits of FlowSync \u2013 a summary<\/h2>\n\n\n\n

FlowSync takes Cybus Connectware\u2019s performance to new heights, enhancing reliability, flexibility and efficiency in manufacturing communication:<\/p>\n\n\n\n