We’ve been working with the OPC software interoperability standards since 1996, and it’s easy to forget that others who are new to this space often find the whole discussion around the OPC standard and all the different standards confusing.
In the automation and control world you need to know about problems immediately. If problems are not recognized early enough, they can cause unexpected downtime, damage to machinery or environmental impacts. In other words, these problems can cost you a lot of money.
Fortunately, these days most of us have 24/7 access to email or texting through their laptops and smart phones which has made receiving alarms in a timely fashion much easier than in the past.
Do you need to directly connect data points or variables in different equipment, processes, or software? This concept is commonly referred to as ‘point-to-point bridging,’ and the DataHub bridging capability allows multiple data sources to communicate with each other in real time.
In this second post of our “I Can Do That?” blog series, we’ll help users like you get the most out of your DataHub by understanding the bridging feature in detail and how this feature can often be combined with other features to accomplish some very powerful automation tasks.
OPC has been around as an industry standard since 1996. If you’ve been working in the space very long, you have probably heard all the different acronyms thrown around. If you’re new, well there are different specifications in the OPC software interoperability standards that are used to meet different information integration needs.
In this first post of our “I Can Do That?” blog series, I’ll explore examples of the connections between different OPC standards we hear about from users, ways to address them using OPC Gateway software, and use cases highlighting solutions we’ve seen other users implement successfully.