No. A typical representative SCADA application is controlling the process automation in real-time: machines are started, driven and stopped by Operators from the SCADA screens with very high safety expectations.
Response times expected are around 50 to 200 ms. This is why there is no disk access in the information process chain, everything is done in memory except for off-line historization into files. A typical SCADA application is typically including technologies optimized to cover:
- Device integration
- Data collection
- Real-time in-memory database
- Event Detection
- Alarm Monitoring
- Akcnowledge control points for safe automation
- Historical data storage
- Graphical WYSIWYG screen design and animation configuration
- Real-time and historical trending charts
- Real-time Graphical Animation and Scripting
- Supervisory and Security Scripting
- Program or process parameter download to machines
- Machining or Recipe execution with real-time PLC integration
- Integration with other applications and SQL Databases
Some applications of SCADA systems are nevertheless less demanding in functionnality just using the data collection and GUI. This is the case for application that just READ data from machine and process equipments and display infoirmation with limited response time requirements. When customers and users are understanding the capability and limitations of Web technology, it is possible to:
- collect machine data and process information using Machine Integrator
- process data using Machine Integrator scripts and standard operations configured with Process Builder
- display machine data and process information into Function Interpreter generated screens using standard Apriso Controls and Charts or JavaScript custom controls.
