By now, I’m sure you’re aware of the Cogent DataHub v8 release. Since announcing the release date, we have had many good questions from existing users like you.
This blog post will address the most common questions we have received and provide the answers you need to plan your DataHub V8 migration.
You may have heard about the upcoming release of Cogent DataHub Version 8 on March 1. The new features in Version 8 are focused on enabling the Cogent DataHub to deliver high-quality data communication – secure, fast, and fully integrated within the plant and beyond.
In this blog post, to give you a bit more insight into what you can expect, I will provide further details on each of the new features.
In the Operations Technology or OT world that most of our users live in, it’s normal to have multiple versions of Windows and systems that may not always be setup consistently but we have to make it all work anyway. Connecting OPC clients and servers when the Windows computers are not on the same version, not in an Active Directory or, using older terminology, a domain, and having everything work well takes skill, and keeping it secure involves a lot of details.
In this blog post, our team asked me to explore with you the details involved to assist you with better understanding Windows Security and to converse more productively with your IT Team. I’ll also share how you can learn more about how to make things easier on yourself through the use of OPC UA or with Tunneling.
It's common with OPC for users to not realize that it is the OPC client that typically defines how quickly the OPC server should poll or send requests to the underlying control devices and equipment the server is communicating with.
This blog post will discuss how important it is for an OPC tunneling solution to have some level of control over this frequency of polling in order to maximize efficient usage of your precious bandwidth.
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.
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.
