In the industrial automation industry, more and more companies are looking for progressively better tools to enable their employees to gain insights and improve their business decisions.
In this blog post, we discuss how KPIs and how they’re generated can empower your employees to make smart business decisions to improve your company’s performance results.
Today’s automation professional is tasked not only with continuous improvement of the automated processes he or she is responsible for, but also doing it with less resources and a lower budget. Labor is expensive and over-tasked.
With all of the core business tasks an engineer faces today, they simply may not have the time to sift through the all of the options available in the marketplace for gathering “business intelligence”.
A key buzz term used in the front office of many companies, business intelligence needs on the automation side of an enterprise are centered around Industrial applications. While business intelligence tools are great at dealing with counts and currencies, automation processes need that and more.
In this blog post, we’ll discuss the three main reasons to have a business intelligence solution and, also, the three key ways that Dream Report delivers nicely on the greater needs of hybrid industrial/business data analytics requirements to provide business intelligence for making key decisions regarding a process to save time, money and expenses.
Knowledge is power and knowing the current state of your underlying server hardware for your process can be very powerful indeed. Keeping a pulse on information like CPU usage, available memory, memory consumption by a process and whether or not critical process are still running can be the difference between hours of downtime with thousands of dollars in lost production and being able to proactively avoid any downtime.
The following short video blog demonstrates step-by-step how easy it is to use the Cogent DataHub to monitor vital system statistics on your servers that can be shared in real-time via supported client interfaces such as OPC DA and OPC UA or even send email/SMS notifications.
The heart of any control system is the computers and servers that run your automation software. For example, when PLCs talk to AC drives over Ethernet, the drives will shut down if they lose communications for more than a second, sometimes even milliseconds. Drives shutdown = Line shutdown = Plant shutdown. What IT calls a blip for plant operations can mean downtime, scrapped product and even your company’s reputation due to missed delivery deadlines.
Traditionally, server maintenance and upkeep is the role of IT. However, when these systems go down, it affects operations (OT) with different pains than IT sees on the business side. IT has systems to monitor their own assets, on the standards they need for the business, but they need the OT side to expand monitoring of their own systems and self-reliance in order for OT to meet operational needs, while bringing in IT as a resource.
This blog post will discuss how to get information about health of servers and PCs that runs the automation software OT users need without having to rely solely on IT.
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.
