Description

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 equipment through color graphic displays. All of the components of these systems are integrated through a network, such as Ethernet for fast communications.

This book provides a practical guide to developing the application software for all aspects of the automation system, from the field controllers to the user interface workstations. The focus of the book is to not only provide practical methods for designing and developing the software, but also to develop a complete set of software documentation. Providing tested examples and proceducres, this book will be indespensible to all engineers managing automation systems.

Key Features

  • Clear instructions with real-world examples
  • Guidance on how to design and develop well-structured application programs
  • Identification of software documentation requirements and organization of point names with logical naming system
  • Guidance on best practice of standardized programming methods for SCADA systems

Readership

System Integrators, technologists, engineers, electricians working on SCADA systems and programming

Table of Contents

About the Author

Preface

1. Introduction

Objectives

1.1 SCADA: Convergence of Evolving Technologies

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.6 The Importance of Software Documentation

1.7 Purpose and Overview of This Book

2. The Elements of SCADA Software

Objectives

2.1 Understanding the Elements of SCADA Software

2.2 Typical SCADA System Architecture

2.3 Sample Application: WTP SCADA System

2.4 Getting the Most from Field Data

3. Practical Procedures for SCADA Software Development

Objectives

3.1 Life Cycle of a SCADA Project

3.2 Identifying Process Area Field Signals

3.3 Creating and Documenting Application Databases

3.4 Defining and Documenting the Process Controller Operations

3.5 Designing and Developing the SCADA Application Software

3.6 System Integration and Checkout

3.7 User Operations Reference Manual

4. Documentation for SCADA Systems

Objectives

4.1 SCADA Software Documentation

4.2 Database Reference

4.3 Process Control Logic Descriptions

4.4 Controller Application Program Listings

4.5 SCADA Workstation Application Software Reference

4.6 SCADA User Operations Reference

5. Tagnames and Signal Naming Conventions

Objectives

5.1 Original Signal Tagnames

5.2 Purpose of Standardized Tagnames

5.3 Constructing Tagnames with Phrases

5.4 Tagname and Signal Naming Convention Structure

5.5 Tagname Fragment Dictionaries

5.6 Illustration of Tagname Application

6. Developing the Application Program Databases

Objectives

6.1 Review of Data Types and Databases

6.2 Using Spreadsheets to Create Points List

Details

No. of pages:
246
Language:
English
Copyright:
© 2013
Published:
Imprint:
Elsevier
Electronic ISBN:
9780124170353
Print ISBN:
9780124170001
Print ISBN:
9781493301386

About the author

Stuart McCrady

Stuart McCrady is a Certified Engineering Technologist in the field of Electronics and Physics Engineering, as well as a Certified Professional Educator in the field of technical training for adults. He spent the first two years of his career in electronics, installing and servicing both large mainframe computer systems and small minicomputers. He then shifted to software programming in automation systems. This field of minicomputer programming required developing application software in machine or assembly language, executing at the hardware level. Field devices such as limit switches, pushbuttons, and solenoid valves, were connected to custom designed hardware interface boards installed inside the minicomputers. From the minicomputers of the 1970s to the PLCs and HMIs of today, Stuart has worked with a broad range of technologies using a variety of hardware and software platforms. He was involved in the design and implementation of more than 50 SCADA type projects. As his career progressed, Stuart acquired both more experience and more responsibility in the field of system integration and SCADA systems consulting. Stuart has served as programmer, project leader, project administrator, consultant, department manager, and SCADA system designer. Throughout his career, Stuart strove to establish programming standards and design methodologies that could be applied to any SCADA application. In the mid-1970s, he developed a program design and documentation system which he called FLOCODE, which resembled high level languages such as C, but was written in plain English. The purpose of the system was to allow the programmer to design software using English-like statements using structured programming constructs such as: If-Then-Else and Do-While/Do_Until. He applied this method to his own programming at both the high level language and the machine level language; this design documentation then became the comments and program description once the program was c