The U.S. Environmental Protection Agency (EPA) announced it is awarding more than $16 million to Alaska’s drinking water and clean water revolving...
Utilities throughout the country are implementing computer-based technologies in an integrated manner to help streamline many design, planning, maintenance, and analysis applications. And the acronyms AM/FM-GIS (automated mapping/facilities management) and SCADA (supervisory control and data acquisition) are appearing at an increasing rate in the language of the water and wastewater community.
Today's open system computer architecture allows for this multi-application integration. Of course, cost savings and maximizing use of resources are primary driving forces. Utilities, vendors, and consultants must take time to plan systems integration based on a thorough study of needs and a clear organizational consensus prior to implementation of solutions. Preparation of a detailed strategic automation master plan document followed by an implementation plan document is the first step. Involvement of users and teamwork among all participants is a must that requires priority attention during the entire systems integration project. Complex integration projects can yield real benefits, but time for sufficient planning must be allocated.
Much has been written about integration of computer systems. However, the tendency to discuss the characteristics and virtues of the myriad of computer industry standards perhaps has been too common. There is a confusing array of standards for all aspects of hardware and software. Different standards are being sponsored and supported by different groups in the computer industry. What they have in common is their goal to provide improved interoperability between different manufacturers of hardware and software. To a large extent this interoperability has been successful and vendors are now producing systems that can be considered open. An open system is one in which the user does not know or care precisely which computer he or she may be accessing, or just what software is running. The user is just concerned with the application. No emphasis is placed here on how interoperability is accomplished. Rather the focus will be on
In the 1970s and into the early '80s, SCADA vendors built many of their own system components. This was because commercially available man-machine interface (MMI), networking, and telemetry hardware were not available to provide data acquisition, display and control tasks. Because of the revolutionary increase in the cost-to-performance ratio of personal and minicomputers, and the maturation of a number of broadly-accepted local area network (LAN) and wide area network (WAN) products, vendors have migrated from proprietary hardware to the use of industry-standard equipment. Consequently, today's SCADA host computer and its associated MMI are suitable for integration with other computer applications.
SCADA vendors also are moving toward providing products with open systems compliant software. From the user's point of view, the degree to which the various software modules contribute to overall interoperability is an important aspect of a vendor's offering. Oftentimes it is also the most difficult to determine. For many years SCADA vendors have been using industry (but not necessarily open systems compliant) standard operating systems. Today systems are being sold with a variety of proprietary and nonproprietary modules including
The software layer that does the input/output (I/O) scanning, trending, alarming, and closed or open loop control can be thought of as the SCADA applications layer. This layer is typically proprietary and may remain so for some time since this software is what distinguishes one vendor from another. In the electrical distribution and energy management industry, many basic control algorithms are standard from one vendor to the other. To-date there has been some work to attempt to standardize typical water system control functioning, but nothing has been successfully commercialized.
Characteristics of Integrated Systems
A primary characteristic of most successful implementations is that they were preceded by a careful analysis of the organization's needs and capabilities. Following the needs analysis phase detailed master plans were prepared.
SCADA and AM/FM-GIS integration differs with each organization. That is why a master plan is critical.
This model allows for the information in an existing computer environment to be left in its native system. For example, the SCADA data would reside in the format originally designed by its system supplier. Access to data through a variety of system integration techniques can build a comprehensive system that most effectively meets the needs of the total user base. By taking advantage of advances in relational database management systems (RDBMS), utilities are implementing systems that maintain data on the AM/FM-GIS database while maintaining other applications on separate databases. Spatially-related data links are used to tie the various data together. Using this technique results in computer system solutions that emulate, as well as complement, the way organizations operate. For example, integrated systems should
There are pros and cons to integrating computer applications. The handling of information within a utility is a process. As with any process, there are multiple alternative designs, each with advantages and disadvantages. Advantages of integrated systems include
If a user wants to obtain (or upgrade to) an open systems-compliant SCADA system, suppliers who can meet the need are available.
Why Should SCADA and AM/FM-GIS Be Integrated?
Both SCADA and AM/FM-GIS applications are geographically referenced database sets. Many vendors and consultants present the argument that it is instinctively obvious that data from closely related applications should be integrated. Without a thorough study of specific needs, the costs and benefits of coupling two or more applications will not be known. However, we do know that the cost of labor, energy, regulatory compliance, construction, employee benefits, and just about everything else a utility uses is rising, except for the cost of applied technology. A few examples serve to illustrate this:
The driving forces for integration of SCADA with AM/FM-GIS are cost containment, improved service to customers, and better protection of our environment. These are the same forces that drive virtually any project that a utility pursues. A distinguishing factor that the implementation of technology has is its effect on the people and the organization from the perspective of training necessary to use and accept the technology, and also the potential to redefine job roles and responsibilities. This "re-engineering" of the organization's way of doing business has real efficiency and cost benefits.
The types of data provided by AM/FM-GIS and SCADA systems are quite different. AM/FM-GIS systems contain massive amounts of data, all referenced geographically and all relatively static in nature. SCADA systems, on the other hand, generate large quantities of data that are dynamic in nature since the systems they monitor and control are always changing. The nature of SCADA's data acquisition and control functions fit into the category of "real time." Since the system's database is constantly being updated, its structure is tailored for fast access and is typically hierarchical in nature.
The typical AM/FM-GIS system provides a seamless interface to Structured Query Language (SQL)-compliant database products. Most SCADA vendors also have the ability to map data to SQL databases, which is depicted in the center oval of our GeoSCADA model. From this location, near real-time and historical data from the SCADA, plus the facility-related information from the AM/FM-GIS system, is available to the utility's various data users. Today these types of applications may include
Information as an Asset
Some utilities have taken the approach that information, particularly AM/FM-GIS type data, is a tangible asset, and updating that information involves a capital expenditure. The same logic could be applied to historical SCADA-acquired information. The useful life span of such data is generally considered to be 20 years or more. Mapping-related data may have a life of 50 years or more.
Many examples exist of utilities forced to use outdated and/or inaccurate maps, as-built drawings, or water consumption data. Virtually every AM/FM-GIS project implementation involves some technique for correcting the existing data set. The time and, therefore, the costs of updating can be very high. However, costs associated with using inaccurate data for planning or design work can be many times higher. If data is not up-to-date or accurately maintained, then every tine a design project is started, the information must be validated. Worse yet, costly field construction corrections may need to be made. And without complete information a utility cannot monitor and report the environmental impacts of its actions properly.
Establishment of an integrated AM/FM-GIS SCADA system should be considered a capital expenditure. As such, projects involving complex information systems don't have to compete with operating expanse budget line items that may be based on a tight tax base and revenue stream.
Open Systems Compliant Specifications
Numerous published and accepted computer systems standards exist. These come in many forms: mapping, networking, electrical interface specifications, mechanical packaging specifications, communication protocol specifications, etc. Some standards are "official," others are "de facto." If a utility wants to upgrade an existing computer system or implement a new one, its written specifications should call for open system compliant hardware and software. If staff do not have the time, experience, or knowledge to prepare such specifications, a qualified consultant should be engaged. The standards are confusing and some vendors have self-serving interpretations.
The following obstacles to success have been identified by utility staffs from their experiences in planning and implementing AM/FM-GIS and SCADA projects.
An integrated information system of any type, by definition and function, crosses departmental lines. The list of obstacles suggests this is an important factor. That is why the first step in any implementation scenario is to prepare a strategic plan. Many techniques are used in automation planning, but any planning process should be designed to gain consensus across departmental boundaries involved. In general, the first planning phase should include six steps (Fig. 3).
Each project is different because each utility has different needs, goals, and constraints. However, certain specifics always should be addressed:
Set realistic expectations and be patient. Complex integration projects can take several years to complete. It's best to set up a series of "quick wins." Define interim solutions that will allow a few files to be transmitted, reports written, or maps plotted. Build on these successes incrementally.
Take advantage of the planning and implementation phases of the project as opportunities to rethink the way the organization works. Often departmental and individual roles and responsibilities are set up based on the information they have. With more information available to more people, more possibilities are available to the organization.