ACM Automation – SCADA Experts

Are SCADA systems off

the shelf?
Listening to those selling SCADA systems may lead us to think this technology is on the
shelf waiting to be applied. This equivalent to saying that a gas processing plant is on the
shelf waiting for an application. True, SCADA is proven technology. However, there are
many steps to implementing a SCADA system and lots of things that can go side ways.

This is as true today as it was a in the 1990’s. SCADA systems these days are expected to
do a lot more. To run more applications; to appear as simple as an internet browser; to be as
fast as a T1 link on the Internet; to be as user friendly as MS-Word or Excel; to be more
robust than Windows NT, to have full database migration capabilities; to be easy to upgrade
plus be license free.

However, since SCADA systems often interface to 3rd party hardware, to end devices
talking Field Bus, to Corporate LAN systems talking through firewalls, and to Business
systems (I.e. SAP), the “smarts” required to interface to outside systems have increased
dramatically as well. This is over and above traditional issues of getting the basic things
done such as populating the P&IDs, understanding the user requirements, and creating a
Tag Database.

The matrix below provides a high level overview of the interrelationship between SCADA
tasks and SCADA equipment. (See page 2 for a sample of the unique factors that must be
considered in implementing a successful SCADA system.)

Sub-
Task Description Host RTU
Systems

Applications / Complex Calculations definition x x

Communications Interface Drawings x x x

Data Flow Mapping (overview / data table strategies) x x x

Detailed logic Descriptions (Text/logic dwgs/matrice) x x

Sorry. The rumour is not true. SCADA systems are no more

“off the shelf” than gas processing plants.
For more information about SCADA systems, contact Murray Macza, V.P. Sales and
Marketing via email at Murray.Macza@acm.ab.ca or call 264-9637.

ACM Automation Inc. Suite 825, 906-12th Ave SW Calgary, Alberta T2P 3T5
Telephone: (403) 264-9637 Fax: (403) 264-6671 Web: www.acm.ab.ca
 ARE SCADA SYSTEMS OFF THE SHELF ? Page 2

The checklist provides a general list of steps involved in implementing a SCADA system.
It is meant to illustrate the need for each SCADA system to be viewed as a unique project with unique parameters.

DETAILED DESIGN SCOPE OF WORK

Task Description SCADA Host RTU Sub-Systems Comments

Administration, Clerical x x x

Applications / Complex Calculations Definition x x Can be a project unto itself. Applications residing in the SCADA Host can consume large effort and costs.

Communications Interface Drawings x x x Multiple vendors can extend this task.

Data Flow Mapping (Overview / Data Table Strategies) x x x Requires a complete understanding of all users of the SCADA system.

Detailed Logic Descriptions (Text/Logic Dwgs/Matrix) x x Normally required at the RTU level. Can be a huge time consuming activity and become redundant or unmanageable if changes are incurred throughout the project.

Electrical / Power / Grounding Drawings x x x Requires vendor information on each piece of equipment and a grounding strategy.

Enclosures / Panels / Consoles x x x Requires consideration of area classifications and the environment.

Graphic Screen Development( Layouts/Navigation) x Operations normally need to be involved early in the design phase.

Installation Drawings x x x Electrical and Civil engineering need to involved.

Instrument Loop Drawings x x Will the project benefit from Automated Loop drawings or are they manually generated?

P&ID's provide the base source of information and need to be extremely accurate showing current tag names and symbols in order that accurate logic descriptions and database
P&ID Population Markups x x
listings can be developed.

Plot Plan Cable Routing x x Does the SCADA system reflect cable routing information in the SCADA database? Potential cost savings on drawings.

Power Systems / UPS Systems x x x Power & UPS systems are often not defined accurately for size or connections. Field (I/O) cards can not drive heavy loads (I.e. small lamps are now considered a large load).

Many SCADA teams involve personnel with varying cultural backgrounds in engineering and work processes. Forecasting and tracking progress can be a challenge. Often the
Project Management x x x
scope changes as the details of the project are discovered or new scope is added.

Reports (Operations, Engineering, Business) Definition x Can be a project unto itself. Many users involved with unique needs and wants. Sort out the minimum requirements.

Normally required at the RTU level. Requires a complete understanding of the P&ID's and the facility operation. Requires a completed HAZOP and SIL study for those
Shutdown keys (HAZOP, SIL Studies) x x
facilities covered under OSHA 1910. Safety Systems are often part of SCADA system projects.

System Over / Architecture Drawings x x x Defined in the concept phase. Future requirements need to be considered (I.e. future expansion, business change).

Provides the base tool that the rest of the development team draws information from. Essential that this is accurate and that a management of change program be implemented
Tag Database Development x x x to ensure all users of the database have the same version. Scope changes have ripple effect on all SCADA engineering levels usually starting with the Tag Data Base. Is a
database tool required or does Excel work for this project?

Third party vendors normally provide special packages for things like leak detection, cathodic monitoring, chemical injection, etc. The operation of this equipment or systems
Vendor Coordination x x x
needs to be determined and the interface requirements defined upfront.

Procedures (Operating, Safety, Business) x Procedures form part of the logic design for RTUs and tools in the SCADA Host. These provide essential knowledge of operation similar to P&ID's.
x
Documentation (Project, Design, Vendor) x Well organized documentation provides essential maintenance information.
x
Network configuration descriptions for those devices on F.O. x Networks and addressing scheme strategies will save headaches when scope changes occur.
x
System Design Document x A confirmation document by the SCADA developers to confirm their understanding to the purchaser.
x

ACM Automation Inc. SCADA Implementation Checklist www.acm.ab.ca