SCADA Training: Tasks Distribution
Every software has its best practice(s) of using. For a SCADA software, the best practices are mostly related to tasks segregation. Always keep this in mind while you configure, and you can achieve better system reliability without wasting money to purchase extra high-end equipment or unnecessary modules or plugins that purposely built for stabilize the system performance.
One good example of resource distribution is the evolution of CPU processors. Remember those old days when we used to have only single core processor, with different speed determines the price difference? Nowadays they have expanded to multiple cores, and the numbers are still increasing despite which brand.
Same theory goes to SCADA system configuration. Imagine you have a huge system, polling many data from field devices. What do you think should be the optimum way of configure? Have all the task handled by a single database, or have them distribute among different servers to segregate the SCADA tasks? Well, the latter is always the wise choice.
Let’s have a clearer image by going through this SCADA tasks distribution training. We shall set the example scenario with the following requirements.
Log 32,000 tags into database based on timer.
Configuration for tasks distribution:
Instead of creating one single database, create 32 databases to each log 1,000 tags as per schedule.
Note: Logging all 32,000 tags into one single database is definitely possible, just that it is not the wise way to fully utilize the SCADA system to achieve the best performance, at the same time data delay or loss may occur when the system is overly burdened.
Using 32 databases to log 1,000 tags each can fully avoid such occurrence. In other words, it is similar with having 32 workers to handle the huge job evenly.
Creating 32 databases may sound troublesome, but in fact it is almost as simple as clicking your mouse for 32 times. For Ecava IGX, you don’t need to worry about the table structures in the database, because the SCADA engine will take care of it for you. What you need to do is just link your SCADA server with the databases via connection strings. Then configure the required tags to log into the correspondent database.
By doing this, the risk of delay in logging can be avoided, as well as preventing your database server to be overly burdened. The idea of tasks distribution are mostly useful for periodic tasks.
Download Ecava IGX today and practice the best practice to optimize your system!