SCADA Host Sofware
Traditionally, SCADA Host software has been the mechanism to view graphical displays alarms and trends. Control from the SCADA Host itself only became available when control elements for remote instruments were developed. These systems were isolated fro the outside world and were the domain of operaors, technicians and engineers. Their responsibility was to monitor, maintain and engineer processes and SCADA elements. With advancements in Ingormation Tecnology (IT) this is no longer the case. Many different stake holdes now require real time access to the data that the SCADA Host software generates. Accounting, maintenance management and material purchaasing requirements are preformed or party preformed from data derived from the SCADA system.
SCADA Systems
SCADA Field INstrumentation
PLCs and RTUs
Remote Communications Networks
Consequently, there is a drive for the SCADA Host to be an Enterprise entity providing data to a number of different users and processes. This has encoraged SCADA Host software development to adopt standards and mechanisms to support interfacing to these systems. It also means that IT, traditionally separated from SCADA systems, is now involved in helping to maintain networks, database interfacing and user access to data.
Many of the initial SCADA Host proucts were developed specifically for the manufacturing environment where a SCADA system resided within a single building or complex, and did not posses many of the telemetry communicaton features required by SCADA systems for geographically distributed assets.
These types of 1 st-generation SCADA Hosts reqired a hybrid PLC or RRTU, called a Front End Driver (FED) or Front End PProcessor (FEP), to be used for handing communications with remote devices. This resulted in anumber of disadvantages as it reqired specialised programing, external to the SCADA software that encapsulates teletry functionality no longer requires these types of hybrid PLCs for communications. They now use software programs called 'drivers' that are integrated into the SCADA Host itself. Software drivers contain the different types of protocols to communicate with remote devices such as RTU and PLCs.
As tecnology developed, SCADA Host software platforms were able to take advantage of many new features. These included the development of integral databases specificallly designed for SCADA Host software requirements, being able to handle thousands of changes a second, for really large systems, yt still comform to standard database interfacing such as Open Database Connectivity (ODBC) and Object linking and Embedding for Databases (OLE DB). These standards are required so that third-party databases can access data from the SCADA Host software. Remote client access to the SCADA Host is another tecnology that has enabled uses to operate and monitor SCADA systems while on the move between or at other locations.
There is a drive towards operatonal safety for SCADA Host systems within the oil and gas industry. 49 CFR 195.446 Control Room Management regulations look at SCADA Host software and how it functions in terms of operations, maintenance and management. It also covers the degree of integration ofthe SCADA system itself and its use of open architeture and standards.
Source: Retyped From SCADA Systems White paper (Mrch 2012) by Schneider Electric Tekementry & Remote SCADA Solutions
SCADA Security
Conclusion of SCADA
About Slave-to- Slave Messaging SCADA
Programmable Logic Controllers (PLCs)
Terminology of PLCs
SCADA Systems
SCADA Field INstrumentation
PLCs and RTUs
Remote Communications Networks
Consequently, there is a drive for the SCADA Host to be an Enterprise entity providing data to a number of different users and processes. This has encoraged SCADA Host software development to adopt standards and mechanisms to support interfacing to these systems. It also means that IT, traditionally separated from SCADA systems, is now involved in helping to maintain networks, database interfacing and user access to data.
Many of the initial SCADA Host proucts were developed specifically for the manufacturing environment where a SCADA system resided within a single building or complex, and did not posses many of the telemetry communicaton features required by SCADA systems for geographically distributed assets.
 |
| SCADA Host Platform |
These types of 1 st-generation SCADA Hosts reqired a hybrid PLC or RRTU, called a Front End Driver (FED) or Front End PProcessor (FEP), to be used for handing communications with remote devices. This resulted in anumber of disadvantages as it reqired specialised programing, external to the SCADA software that encapsulates teletry functionality no longer requires these types of hybrid PLCs for communications. They now use software programs called 'drivers' that are integrated into the SCADA Host itself. Software drivers contain the different types of protocols to communicate with remote devices such as RTU and PLCs.
As tecnology developed, SCADA Host software platforms were able to take advantage of many new features. These included the development of integral databases specificallly designed for SCADA Host software requirements, being able to handle thousands of changes a second, for really large systems, yt still comform to standard database interfacing such as Open Database Connectivity (ODBC) and Object linking and Embedding for Databases (OLE DB). These standards are required so that third-party databases can access data from the SCADA Host software. Remote client access to the SCADA Host is another tecnology that has enabled uses to operate and monitor SCADA systems while on the move between or at other locations.
There is a drive towards operatonal safety for SCADA Host systems within the oil and gas industry. 49 CFR 195.446 Control Room Management regulations look at SCADA Host software and how it functions in terms of operations, maintenance and management. It also covers the degree of integration ofthe SCADA system itself and its use of open architeture and standards.
Source: Retyped From SCADA Systems White paper (Mrch 2012) by Schneider Electric Tekementry & Remote SCADA Solutions
SCADA Security
Conclusion of SCADA
About Slave-to- Slave Messaging SCADA
Programmable Logic Controllers (PLCs)
Terminology of PLCs
Comments
Post a Comment