ArcGIS for Water Utilities is an evolutionary step in how Esri’s GIS technology can be deployed at water utilities. Over the last year we’ve had many conversations about how ArcGIS for Water Utilities enables water, sewer and stormwater utilities to take a better approach to meeting their GIS needs. We’ve found one of the most effective ways to communicate the “ArcGIS for Water Utilities Approach” is to compare it with two other approaches to meeting water utility GIS needs we’ve seen – “The Legacy Approach” and the “ArcGIS System Approach”.
Legacy Approach
What we call “The Legacy Approach” to meeting water utility GIS needs was an approach commonly used about 10 years ago. This approach was typified by water utilities building their GIS from the bottom up, often with many projects over a multi-year period. With this approach water utilities were spending a lot of time and money assembling a GIS platform and then creating customizations to perform industry common functions.
By assembling a GIS platform we mean that utilities were typically deploying GIS technology components in a piecemeal way, usually as multiple stages or phases of projects to build out their desktop, web and mobile GIS applications. For example start with a desktop GIS to edit data and create maps, a few years later go to a multiuser editing environment, a few years later start deploying web applications than after that deploy a mobile GIS application. Efforts were often more focused around bringing in pieces of technology (“I’m implementing SDE” “we are deploying ArcIMS”) rather than the applications supported by the GIS technology. With each new piece of technology brought into the GIS platform, the utility would have to modify existing customizations, build new customizations that utilize the new technology, create new workflows and perhaps make schema modifications.
When talking about the Legacy Approach, we’ve had some astute people say, the term “legacy” has a negative connotation to it. Absolutely, it does… today. To be fair, this was a logical approach years ago, but with the advancements of ArcGIS and more broad advancement in information technology, knowledge about deploying GIS in the water utility industry and the financial realities of running a modern water utility this isn’t a viable approach any longer.
The ArcGIS System Approach
About 5 years ago we began seeing more water utilities taking what we call “The ArcGIS System Approach”. This approach was typified by deploying ArcGIS as a single comprehensive system or platform for geo-spatial information at a water utility. This enabled water utilities to meet their general GIS platform needs with a COTS system with all the components designed to work together. Water utilities need to utilize GIS through desktop, web and mobile applications as well as to integrate GIS to other enterprise systems through IT standards and have all applications working off a single authoritative source of data. At a platform level, this is what the ArcGIS System does. Deploying ArcGIS as a platform eliminates the need for the utility to assemble a custom GIS platform in a piecemeal manner.
Implementing ArcGIS as a single geo-spatial platform at a water utility still leaves a gap to meet the needs of an individual water utility. That gap is comprised of industry specific needs and unique organizational needs. Water utilities were bridging this gap by “do it yourself” implementations/customizations, purchasing 3rd party applications that sit on top of the ArcGIS Platform and/or hiring consultants. If you think about meeting the GIS needs of a water utility as project, the ArcGIS System Approach enables water utilities to reduce the cost, time and risk in comparison to the Legacy Approach.
It is important to note that many water utilities used Esri’s water and sewer datamodels as a way to address some industry specific needs, in particular having a geodatabase schema to store water and sewer pipe networks in GIS. The old Esri water and sewer datamodels were both ground breaking and very beneficial for water utility GIS, however their focus on pipe networks caused water utilities to have to build out their own custom schemas to accommodate things like operational data and base mapping.
As we interacted with water utilities that were deploying ArcGIS as platform, we observed that there were common customizations that utilities were creating to meet their industry specific needs or more appropriately their industry common needs. Those customizations are what first drove the creation of the Water Utility Templates which ultimately evolved into ArcGIS for Water Utilities.
ArcGIS for Water Utilities Approach
The “ArcGIS for Water Utilities Approach” is to deploy a focused set of maps and applications that utilize a harmonized information model on top of the COTS ArcGIS platform. The ArcGIS platform meets the general GIS platform needs of a water utility and the ArcGIS for Water Utilities maps, apps and the Local Government Information Model meets industry common water utility needs.
Deploying the COTS ArcGIS platform gives water utilities desktop, web, and mobile GIS applications configured for a water utility as well as the ability to spatially enable other enterprise systems. The COTS platform utilizes a single authoritative source of data and includes ArcGIS Online for cloud based geo-collaboration. So simply put the ArcGIS for Water Utilities maps and apps and the Local Government Information Model are configurations deployed on top of the COTS ArcGIS platform.
The ArcGIS for Water Utilities approach enables water utilities to focus their GIS efforts on meeting true organizational needs through do-it-yourself activities, purchasing 3rd party applications that sit on top of ArcGIS for Water Utilities and/or by engaging consultants. The types of efforts typical to bridge the gap between ArcGIS for Water Utilities and an organization’s unique needs are extending the maps, apps and/or the information model or deploying new maps and apps that utilize the information model.
By following the ArcGIS for Water Utilities approach water utilities can reduce the cost, risk and amount of time it takes to meet organizational GIS needs. Of course to maximize your benefit from ArcGIS for Water Utilities, you must embrace the industry common functionality included in the maps, apps and information model and also have a clear understanding where true organizational needs require additional effort and the effort is worth the cost.
Hello,
I agree that ArcGIS for Water Utilities Approach embraced with common functionality is a very powerful tool for Water Utility organizations and Departments of Water Affairs.
Personally I have experienced with many ArcGIS projects from various Water Utilities, but they all have a common disadvantage. They all lack the concept of Zoning it terms of Hydraulic Zones, Balancing Zones and Head Zones. Having a Water Network organised as GIS layers is fine, but does not give a clue about how the network operates e.g. if a Water Valve is closed, then an area will be isolated etc.
Does ESRI provide this functionality and intelligence to organize a Water Network in zones and apply the zoning theory?
Regards,
Great questions and comments.
Esri does not provide the functionality to derive hydraulic zones/pressure zones. However, some of our Esri Business Partners, such as Innovyze and DHI, provide this specialized analytical functionality through their hydraulic modeling solutions that run on top of ArcGIS for Desktop. These solutions can take the utility network data stored in GIS as one of the input sources for creating a hydraulic model and can also create model outputs that are available as GIS data layers. So the zones created in the hydraulic modeling application can be utilized as a layer in GIS. There has been a major industry trend towards integrated hydraulic modeling and GIS workflows and Esri has recently published a book on the topic called “Hydraulic Modeling and GIS”.
If you are utilizing the geometric network in your geodatabase (which we suggest as a best practice for storing water and sewer data sets in a geodatabase) the functionality is available to you to determine how closing a valve would isolate service down to individual customers rather than across an area. For example when a valve is closed every premise that no longer has water service is identified, if you have district metering area in your GIS or have zoned out your distribution system you can use geo-processing to identify zones out service as well. This can be done either before closing a valve to assess the potential impacts or after closing a valve to do things like notify affected customers during an emergency shut down.
For our field crews we use Iwater’s Inframap software to see which homes are effected by a valve being turned off. They made a very simple interface in their program that goes on a tablet PC for the field crews.
We too are currently working with water network zoning – primarily balancing and pressure zones at this stage. We are struggling through how to automagically define these zones and update when a zone changes – some valves opened, others closed, to change zone boundaries.
I think what this article implies, but does not state explicitly, is that the ArcGIS system approach implements a services oriented architecture (SOA) for building spatially enabled applications and functionality into the water utility enterprise. This is a road that my utility is taking, though the initial emphasis is starting at the enterprise application level; asset and work managament, customer information systems, and financial management systems. GIS as a set of web based services holds great promise for finally integrating spatial technology into the utility, but it will be a long road. I would love to hear more success stories from those who are ahead of us.