Designing SCADA application software a practical approach
Automation systems, often referred to as SCADA systems, involve programming at several levels; these systems include computer type field controllers that monitor and control plant equipment such as conveyor systems, pumps, and user workstations that allow the user to monitor and control the equipmen...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
London ; Waltham, Mass. :
Elsevier
c2013.
London : 2013. |
| Edición: | 1st ed |
| Colección: | Elsevier insights
Elsevier insights. |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627950206719 |
Tabla de Contenidos:
- Front Cover; Designing SCADA Application Software; Copyright Page; Contents; About the Author; Preface; 1 Introduction; 1.1 SCADA: Convergence of Evolving Technologies; 1.1.1 Early Automation Systems; 1.1.2 The Human Interface; 1.1.3 Communications and Integration; 1.2 Basics of SCADA Signal Processing; 1.3 Defining the Scope of SCADA Software; 1.4 Use of Generalized Terminology; 1.5 The Need for Programming Standards; 1.5.1 Need for Design Standards; 1.5.2 Modify or Reprogram; 1.6 The Importance of Software Documentation; 1.6.1 Lifetime of Software Systems; 1.6.2 Upgrades and Revisions
- 1.7 Purpose and Overview of This Book1.7.1 Organized Design and Development; 1.7.2 Complete Software Documentation; 1.7.3 Adherence to Programming Standards; 2 The Elements of SCADA Software; 2.1 Understanding the Elements of SCADA Software; 2.2 Typical SCADA System Architecture; 2.2.1 Field Devices and Signals; 2.2.2 Programmable Process Controller; 2.2.3 SCADA Operations User Workstation; 2.2.4 Communication Network; 2.2.5 SCADA Server Computer; 2.3 Sample Application: WTP SCADA System; 2.3.1 Low Lift or Raw Water Station; 2.3.2 Pretreatment; 2.3.3 Filtration
- 2.3.4 High Lift or Treated Water Station2.3.5 Chemical Systems; 2.4 Getting the Most from Field Data; 3 Practical Procedures for SCADA Software Development; 3.1 Life Cycle of a SCADA Project; 3.1.1 Initial SCADA Project Specifications; 3.1.2 Development of SCADA Project; 3.1.3 Factory Testing and Demonstration; 3.1.4 Commissioning and Site Acceptance Testing; 3.1.5 The Final Step - Documentation; 3.2 Identifying Process Area Field Signals; 3.2.1 Process Areas and PPCs; 3.2.2 Identifying Input and Output Signals; 3.2.3 Organizing Field I/O Signals; 3.2.4 Allowing for Future Expansion
- 3.3 Creating and Documenting Application Databases3.3.1 Developing a Standardized Tagname System; 3.3.2 Creating Points Lists Using Spreadsheets; 3.3.3 A Spreadsheet Illustration; 3.4 Defining and Documenting the Process Controller Operations; 3.4.1 The Initial Process Narrative; 3.4.2 Developing the Detailed Process Logic Descriptions; 3.4.3 Documenting System Operations; 3.5 Designing and Developing the SCADA Application Software; 3.5.1 Developing the Controller (PPC) Application Software; 3.5.2 Developing the SCADA Workstation (SOW) Application Software; 3.5.3 Networking and Interfacing
- 3.6 System Integration and Checkout3.6.1 Controller I/O Signal Checkout; 3.6.2 Testing and Commissioning Process Area Operations; 3.6.3 System Acceptance Test Procedures; 3.7 User Operations Reference Manual; 3.7.1 Purpose of the User Operations Manual; 3.7.2 Structure of the User Operations Manual; 4 Documentation for SCADA Systems; 4.1 SCADA Software Documentation; 4.1.1 Reasons for Developing Documentation; 4.1.2 Components of Software Documentation; 4.2 Database Reference; 4.2.1 Standardizing on Tagname Conventions; 4.2.2 Programmable Controller Database; 4.2.3 SCADA Workstation Database
- 4.3 Process Control Logic Descriptions
