It's common in the automation space to just throw out the term "OPC" without any qualifiers when talking about what a software solution supports with respect to open connectivity to other software. But what does "OPC" mean for your specific software solution?
This blog post will discuss how important it is to know what an OPC tunneling solution is actually compatible with when talking about "OPC" since not all tunneling solutions use the same methods.
There’s nothing like knowing that you aren’t alone, and someone else has had the same problems or successes that you have in similar situations. That's just as true in the industrial automation world as it is in life.
This blog post will discuss how the peace of mind garnered from case studies and real-world examples when choosing a tunneling solution can be a deciding factor.
The OPC UA specification is an evolution on the original OPC Classic specifications that has been designed by the OPC Foundation to supplement, but not render obsolete the existing OPC standards such as DA, HDA, & A&E. OPC UA is designed to make enterprise-level integration easier, while ensuring compatibility and interoperability with existing OPC DA, HDA, and A&E servers and clients. OPC expert Marc Holbach gives a seminar on all of the details below.
Collecting data from multiple remote sites or aggregating, as it is generally referred to, is a big part of geographically distributed control operations. Having a macro picture of your operations over all of your locations is key.
And efficient, reliable performance is always a concern. This blog post will discuss performance as it relates to aggregating data from multiple remote sites using a tunneler solution and why it's important for tunneler solutions to support multiple tunnel connections in the same instance.
The more regulated your industry, the more likely it is that you have a cybersecurity team that is extremely vigilant about gaps in security. Traditionally, remote OPC tunneling has generally always required that network firewalls have at least one port open for data transfers to work successfully.
But what if you work in one of these highly regulated industries and your IT/cybersecurity department won't allow you to open any firewall ports for remote data sharing?
This blog post will discuss why it's important for a tunneler solution to support alternatives to the traditional methods of tunneling with open firewall ports to ensure network integrity.
The word tunneling, when it comes to industrial automation and data, typically goes together with OPC. OPC tunneling is generally the most common form of tunneling, but what if your data sources aren't OPC?
What if you have more than just OPC clients and servers in your architecture and those non-OPC data sources have vital information that needs to be collected and shared with your other systems?
This blog post will discuss why it's important for a tunneler solution to support more than just OPC-capable data sources in a diverse control system.
The letters O - P - C get thrown around a lot these days in the context of the industrial automation industry. But it's important to understand that OPC is not a one-size-fits-all standard. There are different specifications under the OPC umbrella and it's not a safe assumption that they are all just compatible with each other because they typically are not.
This blog post will discuss how important it is to know which OPC specifications you have in use and whether the OPC tunneler solution you have or are considering can handle them all.
