ArcGIS Data Models: Water Utilities - Esri Supportdownloads2.esri.com/support/datamodels/Water Utilities... · 2003-06-04 · Water Utilities ArcGIS ™ Data Models Water Utilities

Water Utilities

ArcGIS™ Data Models

Water Utilities

$50.0088053

DOME2M12/01spPrinted in USA

Arc

GIS

™ W

ate

r Utilitie

s Da

ta M

od

el

ESRI • 380 New York Street • Redlands, CA 92373-8100 • USA909-793-2853 • FAX 909-793-5953 • www.esri.com

™

ArcGIS™ Data Models

9 781589 480308

ISBN 1-58948-030-9

Steve Grise, Eddie Idolyantes,Evan Brinton, Bob Booth,and Michael Zeiler

Grise

, Ido

lyan

tes, B

rinto

n, B

oo

th, Z

eile

r

�� !��

"�� !��!# ��$!�#��"��%��&��!��#��!�� %�� !�� !��'�� %��& ��(� ��#!�� (�� )��!��!�� !��!��) ��!�#��!�� !��)��(�� )�$!��$�� %��(��*#��#��(��+��!�,��)��)-. '�%/��&��)��)��0�-1-2.� )��

"�� !��!# ��#(3�!�!��%��#��!��

�� %��)��!# ��)��4��#��#(3�!�� 5�!�� 6�� !*#��"��"�745�,�"�7��68"�� # )#��)�#��!��)��!��#��(��6�� #(3�!��!��9��:;��12�<��)��)��=>�'�0.1?@9��:;��12�0=>�'�0.1?��4��9��:��4��=�� !��"�!��!��7��4�� #��%��?@��79��:�;��121 �;='AB�00;?="�!��!��7��?��4��79��:��1�1� � =�� #��%��?)��!�(��!��4,��#��!#��)-. '�%/��&��)��)��0�-1-2.� )��

��)��(��)��!�,�� &��)��!��!�#��@��#�� #��!6��)��!��)��!��)��!,��)��!�7�)��!A(3�!�)��!�� )6��(��)��!6�� &��%%%��!� ��!��!� ��!� ��&��

A��!� ��#!� �� &�� &��!�� &�%��

Attribution.p65 12/06/2001, 8:21 AM1

Contents

ACKNOWLEDGEMENTS ............................................................................................................................ v

CHAPTER 1: MODELING WITH THE ARCGIS WATER UTILITIES DATA MODEL ................... 1

Introduction ............................................................................................................... 2

Modeling concepts in ArcGIS Water ............................................................................ 3

Water networks ........................................................................................................... 4

CHAPTER 2: DEPLOYING THE ARCGIS WATER DATA MODEL .................................................... 9

The process of deploying ArcGIS Water ..................................................................... 10

Geodatabase design, tools, and guidelines ................................................................... 13

ArcGIS implementation scenarios .............................................................................. 16

Sharing your geodatabase ........................................................................................... 18

Case Study: Implementing ArcGIS Water ................................................................... 20

ArcGIS Water implementation resources .................................................................... 23

CHAPTER 3: CUSTOMIZING THE ARCGIS WATER DATA MODEL ........................................... 25

Implementing a customized geodatabase with UML ................................................... 26

Customizing the object model .................................................................................... 27

Exporting UML to the Microsoft Repository ............................................................. 40

Creating a schema from the repository ........................................................................ 41

Loading data ............................................................................................................. 50

Modifying the schema in ArcCatalog .......................................................................... 61

Sharing a geodatabase ................................................................................................ 63

CHAPTER 4: BUILDING ANALYSIS MODELS .................................................................................... 67

ArcGIS Water distribution object model .................................................................... 68

ArcGIS sewer/stormwater object model .................................................................... 70

Component technology considerations ....................................................................... 73

CHAPTER 5: LINES DATA MODEL REFERENCE ............................................................................. 77

Water lines ................................................................................................................ 78

Modeling concepts of ArcGIS Water ......................................................................... 79

TOC.p65 12/05/2001, 1:07 PM3

iv • ArcGIS Water Utilities Data Model

CHAPTER 6: EQUIPMENT DATA MODEL REFERENCE .............................................................. 83

Equipment ................................................................................................................ 84

CHAPTER 7: FACILITY DATA MODEL REFERENCE ...................................................................... 95

Facilities ................................................................................................................... 96

CHAPTER 8: FEATURE DATA MODEL REFERENCE .................................................................... 107

Features .................................................................................................................. 108

INDEX ............................................................................................................................................................ 115

TOC.p65 12/05/2001, 1:07 PM4

v

��

The creation of ArcGIS Water Utilities Data Modelhas been a collaborative effort of several ESRIemployees. The writers of the book include BobBooth, Erik Hoel, Mike Zeiler, Steve Grise, EddieIdolyantes, and Evan Brinton. Clint Brownconstantly reminded us about the importance ofthis book and spent time helping us with thecontent.

ESRI is privileged to have an active water/wastewater user group. Led, and often cajoled intoaction by Lori Armstrong of ESRI, this group hasmade a significant contribution to the developmentof ArcGIS Water. Of the many members of ouruser and business partner community we would liketo especially thank the following organizations fortheir ongoing support.

These are some of the water utilities andengineering firms that directly contributed todeveloping the ArcGIS Water data models:

• Azteca Systems, Inc.

• BaySys Technologies, Inc.

• Black & Veatch

• Brown and Caldwell

• Camp Dresser & McKee Inc.

• CH2M HILL

• City of Houston

• City of Phoenix

• City of Kamloops

• City of Portland

• City of Spokane

• Colorado Springs Utilities

• Cucamonga County Water Dept.

• Denver Water Department

• DHI

• Elsinore Valley Municipal Water District

• EMA Services

• Geo Decisions

• Geographic Information Services, Inc.

• George Butler Associates

• Hammond Sanitary District

• Harza Engineering

• Idea Integration

• Imperial Irrigation District

• Johnson County Public Works

• Los Angeles DWP

• Las Virgenes MWD

• Leica Geosystems Ltd.

• Long Beach Water Dept.

• Louisville MSD

• Louisville Water Company

• Metro Water Services

• Miami–Dade Water & Sewer

• Montgomery Water Works and Sanitary Sewer Board

• MW Soft

• Parsons Corporation

acknowledgements.p65 12/05/2001, 1:05 PM5

vi • ArcGIS Water Utilities Data Model

• Philadelphia Water Dept.

• Regional Water Authority

• South Australia Water Company

• Spokane County

• Stoner Associates

• Tyra Strategies

• Union Sanitary District

• Wachs Companies

• Westin Engineering

• Woolpert LLP

acknowledgements.p65 12/05/2001, 1:05 PM6

1

Modelingwith the ArcGISWater utilitiesdata model

1ESRI® ArcGIS™ Water contains aready-to-use data model that can beconfigured and customized for use atwater utilities. A keystone of this newdata model is modeling of waternetworks that capture the behavior ofreal-world water objects such as valvesand lines.

These are the topics in this chapter:

• Introduction

• Modeling concepts in ArcGIS Water

• Water networks

Ch01 Modeling.p65 12/05/2001, 1:12 PM1

2 • ArcGIS Water Utilities Data Model

INTRODUCTION

Water. It’s an essential part of our everyday lives that weoften take for granted. Behind the scenes there are many

people working to ensure that we have a clean, safe,reliable water supply; that wastewater is safely routed,treated, and eventually released; and that stormwater

drainage systems protect human lives, property, and thenatural environment.

Beginning around the time of the industrial revolution,the advent of standards in water, wastewater, and

stormwater utility management led to standardizedconstruction and water treatment practices. This has

resulted in the ability to service many millions of peoplein urban centers without the historical health and

pollution complications of preindustrial society. Butwhile we can now support large urban population centers

unlike anything seen in human history, many of thesewater and sewer systems around the world are reachingthe end of their planned life spans. Today’s challengesinvolve optimizing the use of existing resources andeffectively managing capital improvement budgets to

ensure sustainable service quality.

The ArcGIS Water Utilities Data Model is designed forwater, wastewater, and stormwater utilities that managethese complex systems. By providing a geographically

oriented view of water network systems, ArcGIS Wateraids in visualizing and understanding real-world

engineering and business problems. Built using object–component technology, ArcGIS Water provides a powerfulnew platform for water utility solutions. The goal of thissystem is to provide operational efficiencies and business

benefits that transcend traditional GIS and mappingboundaries. In much the same way as standards

revolutionized water distribution engineering almost 100years ago, ESRI’s goal is to work with our water utility

customers to define a new set of technology standards formanaging geographic information for the next 100 years.

Ch01 Modeling.p65 12/05/2001, 1:12 PM2

Modeling with the ArcGIS Water utilities data model • 3

MODELING CONCEPTS IN ARCGIS WATER

Today’s water and wastewater utilities are realizing thebenefits of geographic information system (GIS)technology for engineering, construction, and opera-tions purposes. The typical requirements of theseutilities reflect business needs to:

� Update GIS databases with as-built data

� Produce standard and custom map products

� Integrate computer-aided design (CAD) drawings intothe GIS environment

� Integrate with other enterprise systems, such as workmanagement systems (WMSs), document managementsystems (DMSs), infrastructure management systems(IMSs), materials management systems (MMSs), andcustomer information systems (CISs)

� Analyze installed network for capacity planning andcapital improvement projects

� Manage operations activities, such as leaks, repairs, andinspections

The ArcGIS Water model supports these typicalbusiness needs by providing an implementation thatfocuses on operations and maintenance portions of thefacility life cycle.

WHO SHOULD READ THIS BOOK

This book is intended for users who implement theArcGIS distribution water and sewer/stormwaterobject models. These users include database designers,data builders, database administrators, analysts, anddevelopers. This book serves as a companion to thewater/sewer/stormwater (UML) object models anddetails the model components and also providesinformation for developing custom applications.

The following topics are discussed in this book:

� Introduction to the ArcGIS Water model.

� Definition of distribution and collection systems andthe design considerations of these systems as they areapplied in ArcGIS.

� Resources and guidelines for implementing instances ofArcGIS Water.

� Deployment scenarios and task-based instruction forevaluating model requirements and implementing acustom geodatabase in the ArcGIS environment.

� Descriptions of the ArcGIS Water model structuresand organization including modeling techniques andnotation in UML.

� Data model reference of the ArcGIS Water modelpresented by thematic group and described in narrativeform at the class level. Each component contains adescription of usage and application within the model.

This book is written assuming that the reader isknowledgeable about water and wastewater domainsand has a functional understanding of ArcGIS.Additional resources are provided in the bibliographyto assist you with developing a basic understanding ofComponent Object Model (COM), Unified ModelingLanguage (UML), and object-oriented database design.

The sample data contained on the ArcGIS WaterCD–ROM is provided courtesy of the MontgomeryWater Works and Sanitary Sewer Board (MWWSSB)of Montgomery, Alabama. The data has been modifiedby ESRI to suit the needs of this book and highlightArcGIS functionality. MWWSSB cannot guarantee thereliability or suitability of this information. Originaldata was compiled and manipulated from varioussources and may not accurately represent the existingdistribution and collection systems as maintained byMWWSSB. The sample data may be updated, cor-rected, or otherwise modified without notification.

Modeling water and wastewater networks

The object technology at the core of ArcGIS 8combines data and application behavior modeling. As aresult, the model not only includes an essential set ofwater object classes and properties, it also includesrules and relationships that define object behaviors.The core object technology and applied Water modelresult in significantly less configuration andcustomization effort for overall implementation persite.

Ch01 Modeling.p65 12/05/2001, 1:12 PM3


In addition, the object model is readily extensible,allowing developers to extend the model, behavior,and user interface of the system with minimaleffort.

TRANSMISSION SYSTEMS

Around the world, the water that we consume forresidential, commercial, and industrial purposesoriginates from a source, usually in the form of alake, river, or underground aquifer. Forcommunities that do not have a local water supply,a transmission network is built to transport the waterfrom the source to the destination communities.Transmission systems are typically composed ofaqueducts, tunnels, connecting devices, andpumping facilities. In a transmission system, all ofthe pipes, devices, and pumping facilities tend to be

large; the network system is relativelysimple; and the networks can spanhundreds of miles as they push waterover continental divides, under oceanchannels, and across deserts topopulation centers.

As the transmission system deliverswater to a community, the transmissionsystem connects with the local waterdistribution system. Usually, there aretreatment plants that ensure waterquality and control the flow of waterinto the distribution system. Manytreatment plants also have adjacentstorage basins and enclosed storagefacilities to provide adequate flowwhen water demand exceeds thecapacity of the transmission system.Typical devices include pumps,

chemical injectors, aerators, motors, and generators.

Design discussion

radial network looped network

There are two primary types of networks: radial andlooped. Radial networks are best represented by streamdrainage and storm drainage networks. Flow always hasan upstream and downstream direction that branchesout/in. Looped networks, on the contrary, frequentlyself-intersect. Water distribution networks are loopednetworks by design to ensure that service interruptionsaffect the fewest customers.

Sewer and stormwater networks are typically radialnetworks, but there are often flow splits and overflowcapabilities to provide additional capacity for times ofpeak network load. Sewer and stormwater networks arealso unique because streets and pavement are speciallydesigned to function as a secondary stormwater systemduring flooding and heavy rainfall.

Radial and looped networks

WATER NETWORKS

Ch01 Modeling.p65 12/05/2001, 1:12 PM4


DISTRIBUTION SYSTEMS

The distribution system typically involves a muchsmaller geographic area, but the complexity of thenetwork is much higher than the transmissionnetwork. Water distribution systems are consideredlooped networks because they are designed to providea continuous flow of pressurized water throughoutthe network, even when some sections of thenetwork are temporarily isolated for repair andreplacement activities. The looping of the networkalso tends to provide for pressure equalizationthroughout the water network. Operating watersystem valves can isolate areas of the waternetwork. The looping of the water mains requiresfittings such as tees and crosses to connect multiplepipes at a junction. Other fittings, such as couplers,bends, and reducers, permit the connection ofseparate physical pipe segments.

Services

Ultimately, water is distributed to residential andcommercial water customers. Often, tapping sleevesare employed to connect ¾" to 1 ½" service pipesto a 6" or larger water main to provide residentialservice. For larger services, tapping sleeves may beused for connecting fire hydrant and fire services,but tees are often used as well. Typically, thesehydrant and fire service connections will have a6–8" diameter to provide enough flow for firesuppression purposes. Most commercial andresidential services are metered for billing purposes.Fire services and fire hydrants are rarely metered.

Water utilities need to classify their networkinventory reporting to distinguish normal systemvalves from hydrant valves when the physicaldevice is the same piece of equipment. Similarly,

large industrial water consumers often own thewater mains and hydrants surrounding theircomplexes. The equipment is exactly the same asother hydrants, but the ownership of the facilitiesis important from a plant accounting and assetmanagement standpoint.

Network management

Water utilities often manage pipe segments in differentways at different times. For example, if a coupler isused to simply connect two short sections of pipe fornew construction and the characteristics of eachphysical pipe are identical, most engineers wouldconsider this to be a single pipe segment. On the otherhand, when an inline renewal is performed and acoupler joins an older piece of 8" steel pipe to a newpiece of 8" PVC pipe, these would be considered twodifferent pieces of pipe. Managing these logical pipesegments, including associations with customerservices and other network features, requires asophisticated GIS application.

Furthermore, the condition of mains is consideredfor logical sections of pipe in water networks. Thecondition of water mains is usually calculated usinga combination of leak and repair information alongwith the estimated life span of pipes according tofactors such as material and installation date. Thephysical condition of sewer mains is usually judgedbetween manholes and linked to a video index. Thecondition of sewer mains is usually determined byoperations staff using internal videos of the sewernetwork and rating pipe conditions according tovisual characteristics.

Ch01 Modeling.p65 12/05/2001, 1:12 PM5


Operations and maintenance

At the operations and maintenance level, valves,meters, hydrants, and other facilities are oftenremoved from the network, for maintenance orstorage, and then later installed in a new geographiclocation. This creates further complications for waterasset management. For accounting purposes, utilitiesdepreciate new facilities from the time these facilitiesare installed in the ground. The manner in whichrecovered materials are depreciated is significantlybetween new and recovered facilities.

From an inspection, maintenance, and repair perspec-tive, the association of all relevant operations activitywith the physical device throughout its life at varioustransient geographic locations is also important.

Customer billing/demand information is important forsystem capacity planning. There are many sophisticatedsoftware products available today to perform complexhydraulic analysis that requires a combination offacility and customer demand data. Water andwastewater utilities need an effective way to performsystem planning through linking the current GISnetwork with consumption data.

SEWER AND STORMWATER NETWORKS

As water is consumed in each home and business,wastewater is introduced via laterals into the sanitarysewer system. The basic physical components of thewastewater collection network are similar to the waterdistribution network.

In a similar way, water enters the stormwater collectionsystem through curb inlets, catch basins, streams,ditches, and culverts. A combined sewer system inter-mixes stormwater runoff and wastewater during peakrunoff periods. Historically, these combined sewerswould flow untreated into rivers, lakes, and oceans.While very few combined sewer systems are being builttoday for environmental reasons, many communitiesare actively separating their sewer and stormwatersystems with massive capital improvement programs.

A key characteristic of most wastewater andstormwater collection systems is that they are almost

One benefit of GIS technology is that utilities can tracktheir assets by geographic location. Network assets, likemost other infrastructure owned by businesses, can bedepreciated for tax accounting purposes. The specificamount of depreciation allowed depends on the originalvalue of the equipment, how long the facilities have been inthe ground, and the tax boundary area that the facilities arelocated in. Having an accurate record of facilities managedwith a GIS provides a more accurate inventory of existingfacilities and an automated way to maintain these recordsas a by-product of map maintenance activities. From a GISsystem design standpoint, it is important to understandhow the exact same piece of physical equipment (i.e., thesame 10" valve) can be considered differently from an assetmanagement standpoint, depending on if the valve is usedas a normal mainline valve or as a hydrant valve. You shouldconsider asset management in your geodatabase design andalso any special rules that your utility may require for assetmanagement.

Design discussionWater modeling requires consideration of facilitiesas assets.

Design discussionConsider the requirements for logical andphysical segmentation of pipe networks forfacilities management.

ArcGIS allows you significant flexibility with the logicaland physical segmentation of your pipe networks. Insteadof relying on traditional arc–node topology, ArcGISprovides a set of network features: simple junctions, simpleedges, complex junctions, and complex edges. The ArcGISdocumentation describes the network feature classes inmore detail, but the key point is that you have manyoptions for implementing a more flexible topology modelwithout having to write complex applications to manageyour data.

Ch01 Modeling.p65 12/05/2001, 1:12 PM6


always gravity fed. Sewer systems are generally con-nected at manholes to provide for rudimentary flowcontrol and connection of pipes at different eleva-tions. This key distinction results in modeling waternetwork elevations with fittings and valves, whilesewer network elevation information is captured atthe ends of pipe segments.

Water flows downhill in sewer systems in what iscommonly referred to as a radial network. This meansthat water entering the system at any one point willtravel the same network path to reach a treatmentfacility, discharge point, or retention pond. At lowpoints in topography, lift/pumping stations are used topush water over hills and other obstacles. These forcedmain networks are almost identical to comparablewater distribution facilities, so there is significantmodeling overlap between the systems as a result.

During the lifetime of a particular valve, hydrant, or similarfacility, the individual piece of network equipment may beinstalled in one location. This equipment may eventuallybe removed for maintenance and storage for a period oftime. This process can be repeated for the same piece ofequipment several times during its lifetime. From an assetmanagement standpoint, an accurate accounting fordepreciation purposes is important. It is also important tolink historical maintenance, repair, and inspection data todetermine when the equipment has reached the end ofits reliability curve.

Most network analysis software products will requirecustomer consumption/demand information for systemmodeling. Usually, this information is stored in a utility’scustomer information system. Being able to link customerdemand to network features via customer connectionpoints is valuable for network analysis and thematicmapping purposes. The model introduces a specialnonmaterial feature class called a lateral point to define aphysical location on the network that represents a singlerecord in the customer information system. This featureclass was created to handle the various types ofcustomer account records. It is anticipated that updatesto the Customer Information System (CIS) and GIS maybe several weeks or months out of step with each otherfor most utilities, so any implementation that integrates aCIS and a GIS at your utility should be developed basedon your specific needs.

Eventually, sewer systems terminate at treatmentfacilities or outfalls into natural watersheds. While thepurpose and composition of these treatment plants isvery different than treating potable water, there arestrong similarities between the kinds of devicespresent in sewer structures and water structures from aGIS modeling perspective.

Common characteristics

All water systems have basic supporting features thatdo not actively participate in the distribution ofwater. Casements, vaults, meter boxes, SCADAsensors, sampling stations, and cathodic protectiondevices perform important functions, but the networkcould function without these pieces of equipment.

Design discussionDevices such as hydrants and valves are oftenmoved to different locations during their life span.

Consumption data from customer billingsystems is often required on networks forexternal modeling purposes.

Design discussion

Ch01 Modeling.p65 12/05/2001, 1:12 PM7


Visualizing operations data, such as leaks, repairs,maintenance, and inspections, is important for assessingpipe/facility conditions and prioritizing capital improve-ment projects. For example, water main segments thatexceed a certain number of leaks per unit of lengthshould automatically be replaced. Many nongraphicalasset management systems can handle this simple task.The value of GIS is the ability to see patterns in the datasuch as areas of moderate pipe condition, where thereare multiple pipes running down the same street orcrossing the same intersection. What might appear to beareas of low priority without a map can easily beidentified as high-priority areas when the network isvisualized using GIS. As a result, utilities can moreeffectively utilize capital improvement budgets.

Design discussionLinking operations data to GIS networks isimportant for assessing pipe quality andprioritizing improvement projects

Beyond the basic network information, the ArcGISWater model can easily be extended to include a fullrepresentation of customer information databases,operations databases, and asset databases. The coremodel, however, simply provides the ability to linkthe features in the geodatabase to external systemsvia an external system identifier since most modernutilities already have systems to support thesebusiness needs.

Ch01 Modeling.p65 12/05/2001, 1:12 PM8

9

Deploying theArcGIS Waterdata model

ArcGIS Water provides a large set ofcomponents that you can use to implementyour data model. The ArcGIS Water model canbe deployed with no modifications or can behighly customized to fit your system’s specificrequirements.

Topics discussed in this chapter:

• The process of deploying ArcGIS Water

• Implementation resources

• Geodatabase basics

• Defining your geodatabase requirements

• Selecting an implementation process

• ArcGIS deployment scenarios

2

Ch02 Deploying.p65 12/05/2001, 1:14 PM9


THE PROCESS OF DEPLOYING ARCGIS WATER

This chapter provides a conceptual overview of theprocess of deploying ArcGIS Water, beginning with anoutline of the process, then discussing each of thestages in more detail. The chapter ends with twoscenarios for implementing custom geodatabases. Atseveral points in this chapter you will be referred tothe books Modeling Our World, Using ArcCatalog, andBuilding a Geodatabase for more information. You mayfind it useful to have these books at hand forreference.

The core of ArcGIS for Water is a set of objects thatyou use to create sophisticated models of your watersystem. With these objects you create a geodatabasethat stores geographic features and tables as objectswith behaviors and relationships. You use the desktopapplications ArcMap™ and ArcCatalog™ to view,edit, and manage your geodatabase. You use theincluded map templates, layers, and styles to symbolizefeatures and create maps of your facilities for a varietyof purposes. You can use all of the powerful functionsin ArcGIS to build your own maps, layers, and styles,as well.

Deploying ArcGIS Water

The process of deploying the Water model unfolds inthree stages, each of which has several steps. In thefirst two stages, you design and implement ageodatabase. In the third stage you make thegeodatabase available for use.

Stage I: Planning and design1. Evaluate your water system.

2. Compare your system to the Water data model.

3. Extend and customize the Water objects to fit yourneeds.

4. Create a logical model using Water objects torepresent your system.

Stage II: Creating a geodatabase1. Export the UML model of the system to a

repository.

2. Use CASE tools in ArcCatalog to create an emptygeodatabase.

3. Load data into the geodatabase.

Stage III: Sharing your geodatabase1. Create connections to the database.

2. Use layers to symbolize features.

3. Use maps for specific tasks.

4. Use connections to control access.

Each of the stages of deploying ArcGIS Water isdiscussed in greater detail in the next three sections.

Planning and design

In this stage you need to rigorously examine yourexisting system and the processes that it mustsupport for your organization. It will be helpful tolist the components of your system and group themaccording to their properties and functions.

Compare the objects in your system to the Waterobjects using this book and the object models thatare distributed with ArcGIS Water. Identify theareas where your system matches the Water modeland where they do not match.

Differences might include attributes of water featuresthat you do not store but that are present in the objectmodel, attributes that you wish to store that are notincluded in the object model, subtypes of objects thatdo not occur in your system or that you do not wantto differentiate, objects that are not modeled in theArcGIS Water system that you need to represent, andrelationships or rules that you wish to model that arenot included in the Water model.

Once you’ve identified how well and where theexisting model fits your needs, you can customize it.You can use a UML modeling tool like Visio®

Enterprise to extend the model where necessary. Ifyou choose to customize in UML, you will create alogical model of your water system using the existingobjects and your customized objects.

You can also skip the UML modeling step (and thefirst step of Stage II) if the Water model conformswell to the model of your system. In this case, you canuse one of the sample repositories that come withArcGIS Water to create an empty geodatabase.

You will find more specific information about theplanning and design stage in the ‘Geodatabase design,

Ch02 Deploying.p65 12/05/2001, 1:14 PM10

Deploying the ArcGIS Water data model • 11

tools, and guidelines’ and ‘ArcGIS implementationscenarios’ sections of this chapter.

In Chapter 3 you will find a tutorial that covers theentire process of deploying ArcGIS Water, frommodifying a UML diagram, to loading data, to creatinga catalog, and symbolizing data with layers.

Creating a geodatabase

In this stage you take a logical model of ageodatabase and transform it into a real workinggeodatabase. The geodatabase model is a genericmodel for geographic information that supports awide variety of object relationships and behavior.ArcGIS Water is a set of geodatabase objects withbehaviors and relationships appropriate formodeling water and wastewater/stormwaterfacilities.

You can use these objects out of the box orcustomize them to more closely model your facility.

The model you use could be a highly extendedcustom model that includes many new objects ofyour own design, or it could be a slightly pareddown version of one of the models included withArcGIS Water. In either case, you will export theUML to a Microsoft Repository so the ArcCatalogSchema Creation Wizard can interpret your designinto a geodatabase.

You can use one of the sample repositories to makea geodatabase that matches the Water modelexactly, or you can create a custom geodatabase byselectively choosing which objects in the repositoryare created in your geodatabase.

Once you’ve created an empty geodatabase with aschema that matches your logical model, you willload data into it. You can also use the CASE tool toapply a schema and create relationships in ageodatabase into which you’ve imported data.

Scenarios 2 and 3 in the ‘ArcGIS implementationscenarios’ section of this chapter discuss scenarioswhere you create a geodatabase schema from arepository.

The steps for creating a schema from a repositoryare covered in Chapter 3, ‘Customizing the ArcGISWater data model’.

Create UML

Shapefiles

Coverages

Import data

Generate schemawith wizard

Apply UML toexisting data

Geodatabase

MSRepository

Creating a geodatabase from a UML model

Custom feature designed in UML, extending theArcGIS Water data model

MyMain: CustomDistribution Main

Attributes ofMyMains

Domain of Values forMyMains

Connectivity Rules forMyMains

CustomBehavior:

Calculate Flow

Geodatabase

Object class

Feature class

Point

Line

Polygon

Edge Junction

Geodatabase data model ArcGIS Water data model

Ch02 Deploying.p65 12/05/2001, 1:14 PM11


Sharing a geodatabase

In this stage you make the data in your geodatabaseavailable for use.

ArcCatalog and ArcMap are the two mainapplications you and others in your organizationwill use to work with your geodatabase.

ArcCatalog lets you manage your database, publishlayers with standardized symbology throughout yourorganization, load data, and create versions of yourgeodatabase. You make the data in your geodatabaseavailable by placing maps and layer files—whichreference the data in the database—in sharedfolders for your system’s various types of users. Youcan control access to data by creating password-protected connections to your database.

Layer

PersonalGeodatabase

FolderConnection

Map

DatabaseConnection

Build catalogs to organize your data, maps, and layers. Placemaps or layers for specific tasks in shared folders on yournetwork.

ArcMap allows you to edit your data whilemaintaining network connectivity, trace throughthe network with a variety of tools, and createmaps tailored to specific jobs.

ArcGIS Water includes samples of the maps, layers,styles, and toolbars that you can use to interactwith and share the data in your geodatabase.

If you create a multiuser geodatabase in anArcSDE™-managed commercial relational databasemanagement system (RDBMS) like Oracle®,Informix®, IBM® DB2®, or SQL Server™, there aremore ways to share your geodatabase. You canmake data available to users through customapplications developed using ArcObjects™, or theArcSDE C or Java™ Client APIs, or through yourRDBMS’s SQL interface. You can even serve yourgeodatabase to the Web using ArcIMS® software.

Adding a LateralLine feature to the water network in a mapwith custom editing toolbars

Edit Tool Toolbar

Ch02 Deploying.p65 12/05/2001, 1:14 PM12


GEODATABASE DESIGN, TOOLS, AND GUIDELINES

ArcGIS Water includes water- and wastewater/stormwater-specific geodatabases that may beimplemented as is or used as a framework fordesigning a custom geodatabase implementation. Todetermine how to best implement the Water model,you should be familiar with the database designrequirements for your organization. This sectionprovides basic guidelines and techniques forcreating a geographic database design andimplementing that design.

Implementation options

Designing a geodatabase is a critical process thatrequires planning and revision until you reach adesign that meets your requirements. Once you havea design, there are two main ways you can createthe geodatabase. One technique is to load existingshapefile and coverage data into one of the samplegeodatabases and create or modify database itemswith ArcCatalog. Another technique is to useUnified Modeling Language (UML) and Computer-Aided Software Engineering (CASE) tools to designand create a custom geodatabase schema, create thegeodatabase from the schema, and then load yourdata. Regardless of the method you choose, thegeodatabase that you create can be refined later,using ArcCatalog or UML and CASE tools.

Design guidelines

The structure of the geodatabase—feature datasets,feature classes, topological groupings, relationships,and other elements—allows you to designgeographic databases that are close to their logicaldata models.

The following are general guidelines for the designprocess:

1. Model the user’s view of the data.

Identify the organizational functions of the dataand determine the data needed to support thesefunctions. Organize the data into logicalgroupings.

2. Define objects and relationships.

Identify and describe the objects, specifyingobject relationships. Build the logical data model

with the set of objects, knowing how they arerelated to one another.

3. Select geographic representation types.

Represent discrete features with points, lines, andareas. Characterize continuous phenomena withrasters. Model surfaces with triangulated irregularnetworks (TINs) or rasters.

4. Match the logical model to geodatabaseelements.

Match the objects in the logical data model toobjects in a geodatabase. Determine thegeometry types of discrete features. Specifyrelationships between features. Implementattribute types for objects.

5. Plan the geodatabase structure.

Organize the geodatabase into feature classesand feature datasets. Consider thematicgroupings, topological associations, anddepartmental responsibility for data.

The first three steps develop the conceptual model,classifying features based on an understanding ofdata required to support the organization’sfunctions and deciding their spatial representation.The last two steps develop the logical model,matching the conceptual models to ArcGISgeographic datasets.

The ArcGIS Water object model presented inChapters 4–8 provides a working model for thisexercise. These chapters and the data modeldiagrams (electronic copies are available in the DataModels folder, where ArcGIS Water is installed)can be marked up and used in your design process.

Designing with CASE tools

CASE tools and techniques automate the process ofdeveloping software and database designs. You canuse CASE tools to create new custom objects andto generate a geodatabase schema from a UMLdiagram.

Object-oriented design tools can be used to createobject models that represent your custom objects.

Ch02 Deploying.p65 12/05/2001, 1:14 PM13


You can use these models to create a COM objectthat implements the behavior of the custom objectas well as the database schema where these customobjects are created and managed.

The steps for creating custom objects are:

1. Design the object model using UML.

2. Export the model to the Microsoft Repository.

3. Generate stubcode and implement behavior.

4. Create a geodatabase schema for the customobject.

For details on Steps 1 to 3, see Modeling Our Worldand Exploring ArcObjects.

Strategies for using CASE tools for schema design andgeneration

Two general strategies exist for using UML andCASE tools to design and create your geodatabase.The first strategy involves using UML to define allof the schema for the geodatabase, generating thatschema, then populating the schema with data.

The second strategy takes the opposite approach. Itinvolves creating the schema by importing existingdata into your geodatabase, building geometricnetworks, then using CASE tools to apply yourUML model to the existing data.

You can use a combination of the two strategies ifyour UML model describes a larger schema thandefined when you imported your existing data.Once your schema has been created, you can modifyit by modifying your UML model, then reapplyingthe model to your geodatabase schema using theSchema Creation Wizard. Alternatively, you can usethe schema management tools in ArcCatalog tomodify your geodatabase schema.

Example: modeling a gate valve

There are many different methods of modelingreal-world objects. The following example showsthe steps needed to model a common water systemcomponent, a gate valve, and shows how it can bemodeled in the Water model.

First, you need to define the gate valves in yoursystem. This could include a physical descriptionand an explanation of its mechanics. Forexample:

A gate valve is designed to start or stopthe flow of water within a distributionnetwork using a simple gate mechanism.Gate valves are operated by transverselymoving a solid plate into the waterway toisolate flow. When open, the gate ismoved completely out of the waterway,significantly reducing the resistance toflow.

Once a gate valve is defined, describe how a gatevalve is used in your system; provide anysignificant details related to the component. Forexample:

Gate valves are intended to be either fullyopen or fully closed. They are not intended tothrottle flow by being partially open. Gatevalves are critical to the water system forallowing the stopping and redirection flow toallow system maintenance, flow routing in caseof emergency, or to isolate system failures.Gate valves may be motorized and controlledremotely.

Next describe the processes that a gate valveparticipates in. For example:

Routine maintenance and valve turningprograms exercise and monitor the gatevalve to ensure proper operatingcondition of the valve and system. Thegate valve participates in processes formaintenance, inventory, analysis, andSCADA.

From the previous descriptions, list theinformation required to support the definedprocesses.

• Direction to turn the valve stem to close thevalve

• Number of turns required to close the valve

• State of the valve (open/closed)

Ch02 Deploying.p65 12/05/2001, 1:14 PM14


• Normal valve state (normally open/normallyclosed)

• Is the valve operational?

• Is the valve motorized?

• Valve identifier

• Location of the valve

• Municipal area where the valve is located

• Diameter of the valve

• Manufacturer of the valve

From this information, we can compare this gatevalve to the Water model and componentreference.

By comparing the above descriptions and usagewith the data model reference section, we can seethat a gate valve can be modeled as a SystemValvein the ArcGIS Water model. As there are othervalves in the utility that can also be representedas a SystemValve—such as butterfly valves—wewill model the gate valve as a subtype ofSystemValve.

Ch02 Deploying.p65 12/05/2001, 1:14 PM15


ARCGIS IMPLEMENTATION SCENARIOS

In the previous sections we discussed the process ofdeploying ArcGIS Water and some implementationoptions. There are two general scenarios forimplementing ArcGIS Water:

1. Use the Water geodatabase with minorcustomization in ArcCatalog.

2. Implement a new geodatabase containing asubset of the objects generated by the WaterUML.

There are many implementation options. Theprocess you choose is dependent on your databasedesign and level of customization. Twoconsiderations that will influence your decision arewhether you will store custom objects in thegeodatabase and whether you intend to create ageodatabase from scratch. If either of these is thecase, you will probably choose scenario 2 or 3. Youmay use some or all of the described methods,depending on your requirements. The booksModeling our World and Building a Geodatabaseprovide directions for designing and implementingcustom geodatabases.

The first step is always to design the geodatabase.The book Modeling Our World is the guide to helpyou design your geodatabase. Once this design iscomplete, you can proceed down the path that bestsuits your situation.

Scenario 1: Implementing ArcGIS Water from ageodatabase

Implementing a system using the templategeodatabase is a quick and easy method ofimplementation when little or no modifications ofthe Water model are required.

Establish a data model

To begin, install ArcGIS Water, then, as with allimplementation processes, determine the datamodel requirements for your system. If analysis ofyour logical data model shows that the ArcGISWater data model fits your needs as is or may onlyrequire minimal customization, then this process issuggested.

If the geodatabase schema and the components ofthe Water model fit your design, you can load yourexisting data directly into the Water geodatabase.

Refine the geodatabase using ArcCatalog

You can use ArcCatalog to continue defining yourgeodatabase by establishing how objects in thedatabase relate to one another. This is the simplestand most direct method of implementing ArcGISWater.

Using ArcCatalog you can establish relationshipsbetween objects in different object classes, addattributes, and associate them with domains. Youcan continue to use the geodatabase managementtools in ArcCatalog to refine or extend a maturedatabase throughout its life.

In some cases the data you have to load onlyaccounts for part of your design. In this case, youcan use the tools provided in ArcCatalog to createthe schema for feature datasets, tables, geometricnetworks, and other items inside the database. Youcan then load the existing data and create new datawith editing tools in ArcMap. ArcCatalog provides acomplete set of tools for designing and managingitems you will store in the geodatabase.

These relationships and domains may be part of theschema that CASE tools generate, but often youwill want to further refine what is generated byCASE to meet your geodatabase design.

What to do

To implement your data model from thegeodatabase, the following steps are required:

1. Install ArcGIS and the Water template.

2. Create the logical data model.

3. Build the physical database model.

4. Use ArcCatalog to edit the schema.

5. Load your data into the geodatabase.

6. Deploy the geodatabase.

Ch02 Deploying.p65 12/05/2001, 1:14 PM16


Scenario 2: Implementing ArcGIS Waterfrom a repository

In many cases, a subset of components of theWater model will be sufficient for yourimplementation. You can create your geodatabasefrom the repository if this is the case.

The Water model is contained in the ArcGIS WaterUML. This model is a diagram that shows a designplan for a geodatabase. The design itself can bestored in a DBMS (either Access or SQL Server) asa Microsoft Repository, which can then be read byArcCatalog to create a schema for your geodatabase.The repository contains a hierarchical list of all theobjects (tables or feature classes) showing theirinheritance relationships as well as subtypes,domains, default values, relationships, andconnectivity rules.

ArcCatalog contains tools to read the MicrosoftRepository. The Schema Creation Wizard guides youthrough the process of creating new feature classes,tables, and other pieces of your geodatabase. Thewhole geodatabase schema can be read directly fromthe repository. Once the wizard is finished, you willhave schema for your design ready to be loadedwith data.

Just as when implementing from the Watergeodatabase, you can use ArcCatalog to establishnew relationships between object classes, newattributes and domains, and connectivity rules forobjects participating in geometric networks.

To implement your data model from the MicrosoftRepository containing the data model, thefollowing steps are required:

1. Install ArcGIS and the Water template.

2. Create the logical data model.

3. Build the physical database model.

4. Use ArcCatalog CASE tools to create schema andcode referencing an existing repository.

5. Use ArcCatalog to edit the schema.

MSRepository

ArcGIS CASETools Subsystem Custom

Object

GeodatabaseSchema

COM CodeGenerator

GeodatabaseSchema

Generator

3rd PartyCASE

UML ObjectModel

You can generate custom object code, as well as yourgeodatabase schema, with the CASE tools in ArcCatalog.

6. Load your data into the geodatabase.

7. Deploy your geodatabase.

Generating code

The CASE tools thematic group of ArcGIS hastwo parts: the Code Generation Wizard and theSchema Creation Wizard. The Code GenerationWizard allows you to create custom COM objectsfor each component of your geodatabase.

For more information on the ESRI object modeland generating code for your custom objects usingthe Code Generation Wizard, see Modeling OurWorld and Exploring ArcObjects.

Ch02 Deploying.p65 12/05/2001, 1:14 PM17


SHARING YOUR GEODATABASE

Once you’ve built your geodatabase, you will needto make it available to people in your organizationwho use the data. These people may work with ageodatabase in different ways. Engineers may createand edit alternative versions of the database duringthe design process, analysts may model flows ortrace connected parts of the network, customerservice representatives may update customerinformation, and managers may quality checkchanges. You can give people access to theinformation they need, with the tools they need,through ArcCatalog and ArcMap.

Work flow and security

Multiuser geodatabases support versioning so youcan create multiple versions in your database toallow multistage work flow processes or provideread-only access to some users. You can createconnections to different versions for differentclasses of users, and you can use usernames andpasswords with these connections to control accessto the geodatabase.

For more information about versioning yourdatabase, see Building a Geodatabase. For moreinformation on creating connections to folders andgeodatabases, see Using ArcCatalog.

You can also control access to the geodatabasethrough your file system-level security. Layers arelightweight files that provide a shortcut to data andalso define how that data will be symbolized. Byplacing sets of layers tailored for specific groups ofusers in shared folders on your network, you canorganize the data that is available for each group.

Layers also allow you to display data with aconsistent set of symbols across an organization.Everyone who adds a layer to their map will see thedata symbolized in the same way.

A set of sample layers with predefined symbologyfor the objects in the Water model is included inthe Layers folder of the Samples folder, locatedwhere you installed ArcGIS Water. You can createyour own layers and symbols in ArcMap. For moreinformation on layers, see Using ArcMap.

Tools for specific tasks

The main tool for viewing, editing, and analyzingdata in a geodatabase is ArcMap. ArcMap is highlycustomizable, and it allows you to save yourcustomization, as well as layers of data, to maps.You can easily add the specific tools and dataneeded for a particular task to a map; for example,a digitizer might use a map with a simple set ofediting tools tailored for digitizing, an analystmight use a map with trace and flow-modelingtools, and an engineer might use a comprehensiveset of CAD-like tools for design.

Creating a password-protected connection to theDesignPlans version of the CityGeodatabase for a cityengineer

Maps and layers can be stored in different locations onyour network, so you can use file system-level security tocontrol access to your data. If Sue in Engineering hasaccess to the folder F:\Layers, she can add the Parcelslayer to the map she is making.

Ch02 Deploying.p65 12/05/2001, 1:14 PM18


You can create maps with specific layouts fordifferent purposes. Maintenance maps couldshow a section of the network, with detailedinsets showing the valves and pipes includedin a particular job.

Map with custom toolbars for editing tasks

Field map designed to show a detailed view ofa construction area with a larger view of selectedsurrounding network features

Presentation map combining utility data with raster imagery, usingtransparency, measured grids, and inset data frames

You can make very simple maps with justthe necessary tools and data forspecialized tasks, or you can make veryelaborate maps with complex layouts forpresentations.

Sample maps of utility data with Watersymbology and custom layouts areinstalled in the Maps folder of the WaterSamples folder, where ArcGIS Water isinstalled.

For more information about creating mapssee Using ArcMap.

Ch02 Deploying.p65 12/05/2001, 1:14 PM19


In the previous sections we discussed databasedesign and some general methods for implementingArcGIS Water. In this section we will examine ingreater detail the process of implementing ArcGISWater from a Microsoft Repository.

This case study reviews the implementation frominstallation to deployment and directs you toreferences and task descriptions for each step in theprocess. This scenario was selected because itcontains tasks common to most methods ofimplementation.

The first six chapters of this book provide a goodexample of how to organize a logical data modelfor a water/wastewater utility and how todocument the functions and the attributesassociated with water/wastewater features. Usethis book and the Visio diagrams in the ModelDiagrams folder to see the relationships betweenobjects in the system and to get detailedinformation about specific objects.

Step 1: Install ArcGIS Water.

Run the installation program to install thecomponents of ArcGIS Water on your system. Theprogram provides you with installation instructionsand prompts you for required information.

Step 2: Create a logical data model.

There are several steps in creating a logical datamodel.

Data assessment

Complete an assessment of your utility systemmodeling needs. To do this, document how yourdata is currently represented, then define the datacomponents required to adequately model yoursystem to support the process of your organization.

Define model components

Define the components required to adequatelymodel the real-world objects of your system.

Construct data model

Build a logical data model based on your findings.Use the ArcGIS Water model as a guide for

determining the objects, attributes, and classes foryour design.

Constructing a logical data model is an interactiveprocess and an art that is acquired throughexperience. While there is no single correct model,there are good models and bad models. It isdifficult to determine when your data requirementsare correctly modeled and complete, but anindication that you are coming close is when youcan answer “yes” to the following questions:

• Does the logical data model represent all datawithout duplication?

• Does the logical data model support yourorganization’s business rules?

• Does the logical data model accommodatedifferent views of data for distinct groups ofusers?

For more information about creating a logical datamodel, see Modeling Our World.

Step 3: Build a physical database model.

The physical database model defines the databaseschema, class structure of objects, and how rulesand relationships are implemented. The physicaldatabase model is built from the logical data modeland is generally constructed by a relational databasespecialist.

The geodatabase is a physical implementation ofdata that allows a structure similar to the logicaldata model. As such, most physical database modelsare directly supported by the existing framework ofthe geodatabase. In most cases, the logical datamodel is directly implemented into thegeodatabase—greatly simplifying the traditionaltask of physical database modeling.

Step 4: Determine customization requirements.

Compare your logical data model and physicaldatabase model to the Water model to determineyour customization requirements. The results ofyour comparison will show which of the Watermodel classes, subtypes, attributes, relationships,and domains are applicable for your data model.

CASE STUDY: IMPLEMENTING ARCGIS WATER

Ch02 Deploying.p65 12/05/2001, 1:14 PM20


Define which rules and behaviors must be createdthrough customization of the geodatabase orthrough custom applications built using thegeodatabase framework.

For more information about customizing ageodatabase, see Building a Geodatabase andModeling Our World.

Step 5: Generate a custom geodatabase.

Use the ArcCatalog Schema Creation Wizard tocreate the geodatabase schema and code from anexisting repository.

ArcCatalog uses CASE tools to read the MicrosoftRepository database you created using the UMLmodeling software. The wizard guides you throughthe process of creating new feature classes, tables,and other pieces of your geodatabase.

During the schema generation process, you will bepresented with a hierarchical list of all of the row,feature, and network feature types in therepository. Many of the objects and featurescontain subtypes with attribute domains anddefault values.

If the schema you are generating contains attributedomains, you can view the properties for thesedomains, but you cannot modify them.

For more information about generating ageodatabase from a repository, see Building aGeodatabase, Using ArcCatalog, and Modeling OurWorld.

Step 6: Edit the water schema using ArcCatalog.

Use ArcCatalog to modify the schema of yourgeodatabase and add behavior. No programming isrequired when you use the data management toolsin ArcCatalog.

Using ArcCatalog you can add behavior to thegeodatabase by creating object classes, subtypes,validation rules, relationships, and a geometricnetwork.

A step-by-step tutorial for this process is availablein the book Building a Geodatabase, Chapter 2,‘Quick-start tutorial’.

Step 7: Load your data into the schema.

In case of a versioned database, an edit session isrequired to insert new records into the table orfeature class to ensure that the networkconnectivity and version information is managedcorrectly. This data loading operation is performedwith the Object Loader Wizard in ArcMap.

For more information on the Object Loader, seeBuilding a Geodatabase, Chapter 12, ‘Editing yourgeodatabase’.

The following is an example of how the ObjectLoader works. You have generated your schemausing the CASE tool Schema Generation Wizard(see Step 5), and you have a simple junction featureclass called MeterBox and a table called Meter.MeterBox and Meter participate in a one-to-manyrelationship class. MeterBox has the attributesMeterID, Height, and Width. Meter has theattributes Serial_No. and Age and the embeddedforeign key MeterID, which relates the meter to itsmeter box.

In your shapefile database, you have maintainedyour meter boxes and meters in a single shapefilethat has the attributes MeterID, Height, Width,Serial_No., and Age. You can use the Object Loaderto take the data in that shapefile and split itbetween the MeterBox feature class and the Metertable while maintaining the relationships betweenthe meter and its meter box.

Use the Object Loader to load the shapefile intothe MeterBox feature class, matching the MeterID,Height, and Width fields from the shapefile withthose in the feature class. Repeat the process,loading the shapefile into the table (only theattributes will be loaded), matching Serial_No.,Age, and MeterID. Since the objects in MeterBoxare related to objects in Meter by the embeddedforeign key MeterID, the relationships will bemaintained during the data loading process.

Importing data

It is likely that you already have data in variousformats, such as shapefiles, coverages, INFO™tables, and dBASE® or other database tables, thatyou will want to store in a geodatabase. You may

Ch02 Deploying.p65 12/05/2001, 1:14 PM21


also have your data stored in other multiusergeographic information system data formats such asArcStorm™, Map LIBRARIAN, and ArcSDE. Youcan use tools in ArcCatalog to import data fromthese formats into your geodatabase.

Importing data into a geodatabase does not dependon having a schema in the geodatabase, so you canimport any data into any geodatabase. Thiscontrasts with loading data, which involvesmatching the attributes of the data to be loadedwith the feature class or table schema you defined.

When you import data into the geodatabase, boththe geometry and attributes are imported, thoughyou can choose to drop or rename attributes. All orsome of the feature classes from a coverage can beimported into an integrated feature dataset, andseveral shapefiles with the same spatial extent canalso be imported into the same feature dataset.

Once you have imported your data into thegeodatabase, you can use ArcCatalog to furtherdefine your geodatabase. ArcCatalog contains toolsfor building geometric networks and forestablishing subtypes, attribute domains, and so on.

To learn how to move your existing data into thegeodatabase, see the book Building a Geodatabase,Chapter 4, ‘Migrating existing data into ageodatabase’.

Step 8: Share your geodatabase.

Some users of your geodatabase will work with thewhole geodatabase directly in ArcCatalog andArcMap. Others may add selected layers from apublic folder to maps, while others may simplyopen predefined maps to complete their tasks. Thekey to effectively distributing your data across anorganization is to build specialized catalogs of datafor yourself or other users of your GIS, by makingconnections in ArcCatalog to databases or tonetwork drives or folders where data, maps, orlayers are stored.

In case of an ArcSDE geodatabase, you make aconnection to the geodatabase to provide access toa version. You can also create layers referencingselected feature classes in a version when you don’twant to provide access to all of the data in aversion. If necessary, you can password-protectlayers based on geodatabase connections.

You can share a personal geodatabase by placing itin a shared folder on your network, and you cancontrol access to the data through your file system-level security.

For more information on creating layers andconnections see Using ArcCatalog. For moreinformation on creating maps see Using ArcMap.

Ch02 Deploying.p65 12/10/2001, 2:47 PM22


To assist with your implementation, the ArcGISWater model provides a domain-specificgeodatabase as well as the components of itsdatabase design and implementation. Examplesfrom various stages of the geodatabaseimplementation process are included to allow youto begin implementation and customization at alevel appropriate to your needs.

The components include:

• The Water database schema and logical datamodel presented in static analysis diagrams

• A data model reference of objects represented inthe logical data model describing the relation ofentities to real-world objects

• A Water geodatabase modeled in UML

• A Microsoft Repository created from the ArcGISWater UML

The Water model contains many objects that areshared between water and wastewater/stormwaterimplementations. Most of the differences betweenthe objects used in these different implementationsoccur at the subtype level. For your convenience inimplementing ArcGIS Water, the functionallyrelated objects are grouped together, with separatestatic analysis diagrams, UML models, repositories,and geodatabases for water and wastewater/stormwater.

The previous chapters reviewed the geodatabasedesign and data model schema. They also describedhow real-world objects are represented within themodel. In this chapter you learned how to design ageodatabase that meets your database designcriteria. In Chapter 3, ‘Customizing the ArcGISWater data model’, you will customize an object,then create a new geodatabase.

ARCGIS WATER IMPLEMENTATION RESOURCES

Ch02 Deploying.p65 12/05/2001, 1:14 PM23

Ch02 Deploying.p65 12/05/2001, 1:14 PM24

25

��

��

��

��

Photograph © Frank Quirarte

The ArcGIS Water data model is designed tobe customizable and extensible. Although youcan use the existing model as it is provided,there are advantages to customizing themodel before you create your geodatabase.

This chapter will show you how to create ormodify classes of objects in the model, andhow to create a custom geodatabase.

The topics discussed in this chapter are:

• Adding a class in UML

• Setting the properties of a class

• Creating subtypes in UML

• Exporting to a repository

• Creating subtypes in ArcCatalog

• Loading data

• Sharing a geodatabase

Ch03 Customizing.p65 12/06/2001, 8:50 AM25


IMPLEMENTING A CUSTOMIZED GEODATABASE WITH UML

In the previous chapter you learned how toimplement ArcGIS Water using two scenarios:

• Customizing an existing personal geodatabase

• Implementing a custom geodatabase from aMicrosoft Repository

The recommended approach of implementingArcGIS Water, creating your data model design inUML, is presented as a tutorial in this chapter.

Advantages of starting with the UML

There are several advantages of creating your objectmodel in UML. The UML modeling processprovides a structure and context that supportsrigorous design of a system and results in a workingblueprint of that system. Using the Water UML andreference material as a guide you can easily evaluateyour utility’s existing database design and create anobject model that meets the requirements of yourutility and enhances how your data is represented.

Designing your data model in UML also gives youdesign-level control over the attributes and datatypes that you use. This makes it easier to matchexisting data types, which makes data loading easierand faster. Finally, it lets you add behavior andcreate custom objects to fit your utility’s needs.

Ch03 Customizing.p65 12/07/2001, 12:58 PM26

Customizing the ArcGIS Water data model • 27

CUSTOMIZING THE OBJECT MODEL

ArcGIS Water can be customized by modifying theArcGIS Water template in UML format and throughthe ArcCatalog interface. In this chapter you willcreate a new class, associate an interface with theclass, and create subtypes to represent types offeatures. These same techniques can be used tocreate new subtypes of existing objects or to addattributes to existing objects. In this exercise youwill become familiar with the powerful techniqueof implementing a custom data model using UML.You will also learn how to customize a Watergeodatabase through the ArcCatalog interface.

In order to demonstrate the process of creating anew object class, this tutorial uses a copy of theArcGIS Water object model called Tutorial1(located in the Tutorial folder), from which theLateralLine class has been removed.

Evaluating the model

After comparing your utility’s logical data modelwith the Tutorial1 object model, you find that theTutorial1 model generally suits your purpose.However, you find two places where the Tutorial1

model needs to be extended to meet your needs. Inyour water system, water mains deliver water tocustomers through pipes called laterals. TheTutorial1 model lacks a class to specifically modelsuch pipes. You decide to create a new LateralLineclass instead of creating a subclass ofPressurizedMain or new class of MainLine (whichhave attributes that you don’t need for the purposeof modeling laterals). Because you have differenttypes of customers that are served by several typesof lateral lines, you will create subtypes of theclass to model the laterals in your system.

You also notice that the Tutorial1 model does notinclude subtypes of the Hydrant class. Your utilitymodels hydrants as wet-barrel or dry-barrelhydrants, so you decide to create subtypes to modelthese types of hydrants.

Now that you’ve evaluated the model andidentified where it needs to be extended, the nextstep is to add your changes to the UML model.These changes will be reflected in the geodatabaseyou create.

Excerpt from Tutorial1.vsd showing the relationship of the class WaterLine to WaterLine and ESRI Complex Edge Feature



Extend the model by adding a class

You will need a copy of Visio Enterprise to extendthe model.

1. Start Visio Enterprise and open theTutorial1.vsd document (in the Tutorial folder).

From the UML diagram in Tutorial1.vsd, you cansee that there already exists a class calledWaterLine. WaterLine is a type of ESRI complex-edge feature.

You will derive the LateralLine class from theWaterLine class. This way, a LateralLine will be atype of complex-edge feature that inherits all ofthe properties of the WaterLine class and hasadditional attributes of its own.

2. In the UML Static Structure Stencil, click Classand drag a new UML class onto the diagram.

3. Use the same technique to add a newgeneralization to the diagram.

Your diagram should look like this:

Don’t worry that the new class box has threesections while the other class boxes have two. TheWater UML objects have suppress operationsturned on to make the diagram easier to read. Youcan right-click on a class to toggle suppressoperations on or off.

4. Double-click Class1. In the UML PropertyEditor, type the name for the new class,LateralLine, and check the IsLeaf box.

5. Click the Attributes tab and click New.



6. Type “LocationDescription” in the Name field,scroll down the Type dropdown list, and clickesriFieldTypeString. Click OK.

You’ve set the first attribute of LateralLine, astring field that will hold a description of thefeature’s location. Now you’ll set another attribute.

7. Click New.

8. Type “Diameter” in the Name field, scroll downthe Type dropdown list and clickWDomainMainDistributionDiameter, then type“1” for InitialValue. Click OK.

You’ve now created the two attributes that yourLateralLine class will have, in addition to thosethat it will inherit from WaterLine.

9. Click OK.



Now you need to show that LateralLine inheritsproperties from WaterLine.

10. Click the triangular end of the generalizationand drag it onto one of the connection pointsof WaterLine.

11. Click the other end of the generalization anddrag it onto one of the connection points ofLateralLine.

12. To check that the relationship is made, double-click LateralLine and click the Attributes Tabon the UML Property Editor.

LateralLine now has many attributes: those youassigned plus those it has inherited. You can modifyor delete inherited attributes if they areinappropriate for your new object class.

13. Click Cancel.

Now you will add an interface to the new objectclass. Adding an interface in the UML model willcreate a COM interface for the object so you candirectly access the object from an application.

14. Click LateralLine to select it, then copy it usingthe Ctrl-C key combination. Paste a copy of theobject with the Crtl-V key combination.

15. Click and drag the new object, Class1, to theright of LateralLine.



16. Double-click Class1. Type “ILateralLine” in theName field, click the Stereotype dropdown list,and click Interface.

Now you will change the types of the interface’sattributes.

17. Click the Attribute tab, clickLocationDescription, and click Edit.

18. Click the Type dropdown list and click BSTR,then click OK.

19. Click Diameter and click Edit.



20. Click the Type dropdown list and click long.Click OK.

21. Click OK.

22. In the UML Static Structure Stencil, clickRefinement and drag a new UML refinementonto the diagram between LateralLine andILateralLine.

23. Connect the arrow end of the refinement toILateralLine and the other end to LateralLine.

You’ve created the LateralLine class that you needto make the Tutorial1 model match your utilitysystem. The next step is to create subtypes ofLateralLine to model the types of laterals that existin your system.

At this point, you can continue using the Tutorial1Visio diagram, or you can open the Tutorial2 Visiodiagram in the Tutorial2 data folder.



Extend the model by adding subtypes

Now you have the classes LateralLines andHydrants. You want to add subtypes to each ofthese, as there are six kinds of LateralLines andtwo kinds of Hydrants. Subtypes are created inmuch the same way that object classes are, but theresults of creating a subtype are different. Eachobject class that you create is represented by a newobject type in your geodatabase (for example, afeature class). Creating subtypes of an object classdefines different kinds of features within a givenfeature class. Subtypes are particularly usefulbecause they provide a way to implement differentdomains, relationships, and connectivity rules forfeatures that are otherwise very much alike. AHydrant LateralLine, for example, could beconnectable to a Hydrant and have one set ofacceptable diameters and material types, while aDomestic LateralLine could be connectable to ameter and have a different set of acceptablediameters and material types.

If you have closed Visio Enterprise since the laststeps, start it again now. If you choose to use theTutorial1 document that you’ve modified, skipStep 1. The Tutorial2.vsd document should be thesame as the Tutorial1 document you modified, butwith the LateralLine class moved to the right inorder to make room for you to add subtypes.

1. Open the Tutorial2.vsd document (installed inthe Tutorial2 data folder).

2. In the UML Static Structure Stencil, click Classand drag a new UML class onto the diagram.

3. Use the same technique to add a new BinaryAssociation to the diagram.

4. Double-click Class1 and type “Domestic” in theName field.

5. Click Attributes and click New.



6. Type “Subtype” in the Name field, click the Typedropdown list and click esriFieldTypeInteger,then type “1” for InitialValue. Click OK.

7. Click OK.

In the Water model the subtype field is inheritedfrom abstract classes, where it is stereotyped as theSubtypeField (in this case, from WaterLine). Youcould also define the subtype field on a concrete-class-by-concrete-class basis, so for example,LateralLines could use a different subtype fieldthan PressurizedMains. If you use different subtypefields you will need to stereotype each one asSubtypeField for each class. A class may onlycontain one field that is stereotyped asSubtypeField.

8. Click one end of the binary association and dragit onto a connection point on Domestic.

9. Click the other end of the association and drag itonto a connection point on LateralLine.

10. Double-click the binary association.



11. Type “Subtype” in the Name field, and clickOK.

You must use the keyword Subtype to name theassociation.

You have created a subtype of the LateralLineobject class. To complete your model, you wouldneed to create five more subtypes to represent theother kinds of laterals in your utility. These havebeen created for you in the Tutorial3 Visio UMLdiagram.

12. Close Tutorial2 and open Tutorial3.

Now you will create a subtype of Hydrant. Youwant to model two types of hydrants. You’ll createone of the subtypes in UML and the other throughArcCatalog. Ordinarily, if you were using UML todesign your system, you would create all of theobjects you need before exporting the model to arepository and creating the geodatabase. However,there may be times that you wish to add newsubtypes or relationships after you’ve built yourgeodatabase—for example, if your utility beginsusing a new piece of equipment that wasn’tincluded in the original design. Fortunately, you cando this easily through ArcCatalog. Be aware thatelaborating upon your model in ArcCatalog does notupdate your Visio diagram or the repository.

1. Click the Go To Page dropdown list and clickArcGIS Facility.

The object model contains a Hydrant class withdefined interfaces. You’ll create a subtype ofHydrant for this exercise.

2. In the UML Static Structure Stencil, click Classand drag a new UML class onto the diagrambelow Hydrant.



3. Use the same technique to add a new binaryassociation to the diagram.

4. Double-click Class1 and type “WetBarrel” in theName field.

5. Click the Attributes tab and click New.

6. Type “Subtype” in the Name field, click the Typedropdown list and click esriFieldTypeInteger,then type “1” for InitialValue. Click OK.

7. Click OK.

8. Click one end of the binary association and dragit onto a connection point on WetBarrel.

9. Click the other end of the association and drag itonto a connection point on Hydrant.

10. Double-click the association.



11. Type “SubType” in the Name field. Click OK.

You have a WetBarrel hydrant subtype. The nextstep will be to modify the HydrantLateral subtypeso the default diameter matches the default barreldiameter of hydrants.

Specifying default values and domains

Default values allow you to speed the data entryprocess and reduce errors when a given subtype offeature consistently has a given value. In theArcGIS Water UML, LateralLine has a diameterattribute that has a default value of 1. Thisdiameter attribute is drawn from a predefinedcoded value domain calledwDomainMainDistributionDiameter. You can usecoded value and range domains with subtypes torestrict the values that can be entered when editingfeatures in your geodatabase.

Before you change the default value forHydrantLaterals, you will examine the availablevalues in this domain.

1. Navigate to the ArcGIS Domains in the VisioUML Navigator.

2. Double-click the domain namedwDomainMainDistributionDiameter.

3. Click Attributes.

In a coded value domain, each permissible code andvalue pair is specified as an attribute of thedomain. You can add coded values to the domain byadding additional attributes. Field types and mergeand split policies are also specified as attributes.

You do not need to add another value to thisdomain—the barrel diameter of Hydrants is drawnfrom the same domain.

4. Click OK.



5. Click the Page Selector dropdown list and clickArcGIS Line.

You see the LateralLine class and its six subtypes.The lower-right subtype is HydrantLaterals.

6. Double-click HydrantLaterals.

7. Click the Attributes tab, then click New.

8. Type “Diameter” in the Name field, scroll downthe Type dropdown list and clickwDomainMainDistributionDiameter, then type“10” for InitialValue. Click OK.

9. Click OK.



The Diameter attribute of the HydrantLateralssubtype now has a default value of 10.

The other subtypes of LateralLine use the samedomain but have a default value of 1. In practice,this means that someone creating a new LateralLinefeature in the geodatabase could choose to create aHydrantLaterals feature, and the default diameterwould be 10 inches. The other attributes wouldhave the same default values inherited fromLateralLine.

Note that this is a default value only, so the personcreating the lateral could click the value in theAttributes dialog box and choose another valuefrom a dropdown list of the domain.

Connectivity rules

Connectivity rules are a way for you to specifyhow features may be connected in your network.You can use connectivity rules to prevent editingerrors from being introduced into yourgeodatabase. For example, you could use aconnectivity rule to specify that Hydrants mustconnect to HydrantLaterals. Someone editingyour geodatabase would not be able to mistakenlycreate and save a Hydrant that was connected toa DomesticLateral.

Creating a connectivity rule involving a subtypewill preclude any other types of connectionswith that subtype. For example, if you onlycreated a single connectivity rule for Hydrantsand HydrantLaterals, these subtypes couldconnect to each other but not to anything else—which would not be very useful for putting outfires. If you choose to use connectivity rules, youmust specify rules for all subtypes in yournetwork that may be connected to each other.

A good way to design connectivity rules for anetwork is to draw matrix diagrams for thesubtypes of all pairs of feature classes, thenindicate which subtypes are connectable.

For each connectable pair of subtypes, create aconnectivity rule.

Attributes of a newly created LateralLine of subtypeHydrantLaterals. All values are derived from the defaultsfor LateralLine, except Diameter.

Valve:Line Matrix LinesValves SubtypeA SubtypeB SubtypeCSubtype1 X X XSubtype2 X XSubtype3 X



Now you’re ready to export the UML diagram ofyour water system to a repository. This will make itavailable to the ArcCatalog Schema CreationWizard, which you will use to generate a newgeodatabase schema.

1. In Visio, click UML and click Export.

2. Click Browse and browse to the folder whereyou will create the repository.

If you use the Repositories folder in the ArcGISWater installation folder, you can choose to exportto an existing repository, or you can create a newrepository.

3. Create a new repository by typing“MyRepository” in the File name text box. ClickOpen.

4. You will be asked whether to create the newrepository. Click Yes.

Visio converts the UML diagram into a repository.This may take several minutes.

5. When the process is finished, quit Visio.

You can save a second or third object model into anexisting repository under a new name. However,this can take a bit longer than creating a newrepository. Overwriting an existing model in arepository with one of the same name can takemuch longer than creating a new one.

EXPORTING UML TO THE MICROSOFT REPOSITORY



CREATING A SCHEMA FROM THE REPOSITORY

The following section shows, in detail, how to generate acustom geodatabase from an existing repository. Theexample uses one of the sample ArcGIS Waterrepositories, but the process would be the same if youcustomized the UML model and created your ownrepository.

After creating the repository, start ArcCatalog. In thistutorial you will create a personal geodatabase, but youcan also generate an ArcSDE geodatabase schema. InArcCatalog, connect to the directory where you want tocreate the geodatabase. Connect to this directory, byselecting File>Connect to Folder from the ArcCatalogMain menu. Select the drive and directory folder you wantto connect to and then click the OK button.

There are two options from which you can choose whenrunning the Schema Wizard:

Option 1: Creating a Dataset and Spatial Referencebefore running the Schema Wizard. This optionallows you to specify a new spatial reference, if you arecreating new datasets. It also allows you to use an existingdataset and spatial reference before running the SchemaWizard.

Option 2: Setting a Spatial Reference while runningthe Schema Wizard. This option allows you to specify anew spatial reference using the default datasets available inthe water models. It also allows you to specify a newspatial reference using your own datasets from yourcustomized model while running the Schema Wizard.

Add the Schema Wizard to an existing toolbar

1. In ArcCatalog, right-click any of the toolbarsand click Customize.

2. Click the Commands tab and click CASE Tools inthe Categories list.

3. Click and drag the Schema Wizard icon from theCommands list onto an existing toolbar, thenClose the Customize dialog box.

The Schema Wizard button is shaded gray when you closethe Customize dialog box.

Option 1: Creating a dataset and spatial referencebefore running the Schema Wizard

1. In the Catalog tree, click the folder, then right-click, point to New, and click PersonalGeodatabase. Type a name for your personalgeodatabase and press Enter.

2. Right-click the geodatabase, point to New, andclick Feature Dataset.

3. Type a name for the new feature dataset in yourpersonal geodatabase. The new dataset namesmust correspond to the names in the water orcustomized models.



For example, create two dataset names, WaterDistribution Features and Water Distribution Network,that correspond to the dataset names from the water oryour customized model. Be sure to create the SpatialReference for each dataset.

4. Click Edit in the Spatial Reference section.

All of the feature classes in a feature dataset mustshare the same spatial reference. You can use thecoordinate system of an existing dataset (forexample, a land base coverage) to set the spatialreference. Be sure that the extent of the dataset isthe same as or greater than that of all of thefeature classes that you’ll load into the dataset.

5. Select or import a coordinate system for yourdataset.

For more information about setting a spatialreference, see Building a Geodatabase and UsingArcCatalog.

Once the spatial reference is set, the next step is to startthe Schema Wizard so you can create the geodatabaseschema.

6. Click the geodatabase in the Catalog tree.

Clicking the geodatabase activates the Schema Wizard andallows you to import the repository you created from theUML model.



7. Click Schema Wizard to start the Case SchemaCreation Wizard.

8. A brief introduction to the wizard appears.Click Next.

9. Click Browse and navigate to the repository youcreated. In most cases you will not have to entera username and password unless you specifiedone while exporting the UML model.

10. Click Next.

A repository may contain several object models.

11. Click the object model you created in therepository, click Next.

The wizard begins importing the objects. This maytake several minutes, depending upon the size of yourobject model. After the wizard finishes with the objectimport, you will be able to select the objects that youwant to import into your feature dataset.



13. In the Schema Wizard form, you can highlightan object and modify the object’s classproperties.

You can click an object and then select the Propertiesbutton, or simply double-click the object, to open theobject’s Properties dialog box. The Schema Wizard allowsyou to modify an object’s properties before importing theobject into the feature dataset.

12. The Schema Wizard allows you to choose fromUse default values or Use values from previousrun. Make a selection and click Next. ThisSchema Wizard form only displays if you areusing a repository from a previous run.

The Schema Wizard form shows your objects in a treeview. By default, all of the datasets in your object modelare selected and have check marks next to them. You canuncheck the check boxes to unselect any dataset that youdo not want to add to your geodatabase. Click the plusand minus signs located next to the dataset to expand andcontract the tree view. The dataset displayed in redindicates the spatial reference exists within the dataset.



The Schema Wizard creates the feature classes, tables, andother objects you defined in your object model. This maytake several minutes.

16. Double-click the dataset to view its contents.

Your dataset now contains the objects (feature classes,tables, relationships, and a geometric network) that weredefined in your object model and generated by the CaseSchema Creation Wizard.

Option 2: Setting a Spatial Reference whilerunning the Schema Wizard

1. In the Catalog tree, click the folder, then right-click, point to New, and click PersonalGeodatabase. Type a name for your personalgeodatabase and press Enter.

2. Click the geodatabase in the Catalog tree.

Clicking the geodatabase activates the Schema Wizard andallows you to import the repository you created from theUML model.

14. If you are satisfied with the object’s properties,click OK. Examine and change any otherobjects, then click Next.

15. The Schema Wizard presents a summary of thefeature and object classes you’ve chosen tocreate. Click Finish. A log file summary isgenerated, which can be viewed immediately.The log file summary, “Schema Wizard Log”, isalso saved in your Temp folder.



6. Click Next.

A repository may contain several object models.

7. Click the object model you created in therepository, click Next.

The wizard begins importing the objects. This may takeseveral minutes, depending upon the size of your objectmodel. After the wizard finishes with the object import,you will be able to select the objects that you want toimport into your feature dataset.

8. The Schema Wizard allows you to choose fromUse default values or Use values from previousrun. Make a selection and click Next. ThisSchema Wizard form only displays if you areusing a repository from a previous run.

3. Click Schema Wizard to start the Case SchemaCreation Wizard.

4. A brief introduction to the wizard appears.Click Next.

5. Click Browse and navigate to the repository youcreated. In most cases you will not have to entera username and password unless you specifiedone while exporting the UML model.



9. Select a dataset and set the Spatial Reference foreach dataset in the Catalog tree.

You can click a dataset and then select the Propertiesbutton, to open the dataset’s Properties dialog box. Youwill need to select each dataset and specify the SpatialReference.

10. Click Edit in the Spatial Reference section.

The Schema Wizard form shows your objects in a treeview. All of the datasets in your object model are selectedand have check marks beside them by default. You canuncheck the check boxes to unselect any dataset that youdo not want to add to your geodatabase. Click the plusand minus signs located next to dataset to expand andcontract the tree view.



12. In the Schema Wizard form, you can highlightan object and modify the object’s classproperties.

You can click an object and then select the [objectname] Properties button or simply double-click theobject to open the object’s Properties dialog box. The Schema Wizard allows you to modify an object’sproperties before importing the object in the featuredataset.

13. If you are satisfied with the object’s properties,click OK. Examine and change any otherobjects, then click Next.

All of the feature classes in a feature dataset mustshare the same spatial reference. You can use thecoordinate system of an existing dataset (for example,a land base coverage) to set the spatial reference. Besure that the extent of the dataset is the same as orgreater than that of all of the feature classes thatyou’ll load into the dataset.

11. Select or import a coordinate system for yourdataset.

For more information about setting a spatial reference,see Building a Geodatabase and Using ArcCatalog.

If you are satisfied with the dataset spatial referenceproperties, click OK.



15. Double-click the dataset to view its contents.

Your dataset now contains the objects (feature classes,tables, relationships, and a geometric network) thatwere defined in your object model and generated bythe Case Schema Creation Wizard.14. The Schema Wizard presents a summary of the

feature and object classes you’ve chosen tocreate. Click Finish. The Schema Wizardgenerates a log file summary, which can beimmediately viewed. The log file summary“Schema Wizard Log” is also saved in yourTemp folder.



LOADING DATA

At this point you have a choice of two strategies forloading your data. The choice is due to performanceconsiderations and hinges on balancing speed ofloading data against maintaining certain custom featurebehavior.

One strategy is to delete the geometric network fromyour feature dataset and load your data with theArcCatalog Simple Data Loader, then rebuild thenetwork and reapply the database schema. Anotherstrategy is to keep the network and use the ArcMapObject Loader to load your data. Each has advantagesand disadvantages.

The first strategy allows you to load features muchmore rapidly, though it has the disadvantage ofrequiring you to reapply your database schema.

This will not work for feature classes that have customobjects with custom object creation behavior becausethe object creation behavior will not be triggered. Forexample, you might have a customWaterStructure:TreatmentPlant object with a classextension to create aNetworkStructure:TreatmentPlant object and relate itto the WaterStructure in a composite relationship,whenever a WaterStructure feature is created. If youwere to load the WaterStructure features with strategy1, as simple features, this behavior would not betriggered and the NetworkStructures would not becreated or correctly related to the WaterStructurefeatures. You would need additional custom scriptingtools to create the NetworkStructures and implementthe relationships.

Create UML

MSRepository

Geodatabase

Delete anynetworks

Generate schemawith the Schema

Generation wizard

Shapefiles

Coverages

ArcCatalog

Use the Simple DataLoader in ArCatalog to

load data.

ArcCatalog

Use the Build GemetricNetwork wizard to buildany required networks

Re-apply UML withthe Schema

Generation wizard

Register the dataas versioned

Data loading strategy 1—using the Simple Data Loader



The second strategy is to use the Object Loaderwithin an ArcMap edit session. This strategy willwork for these feature classes, but it requires thedatabase to have a geometric network and beregistered as versioned before the objects areloaded. This process can be very slow (as much as7–9 seconds per feature loaded).

ArcCatalog

Create UML

MSRepository

Geodatabase

Compress thedatabase

Register dataas versioned

Use the Object Loaderin an ArcMap edit

session to load data.

ArcCatalog

Generate schemawith the Schema

Generation wizard

Shapefiles

Coverages

Data loading strategy 2—using the Object Loader

For more information about the performance trade-offs involved in loading and using network featuredata, see the ESRI Technical Paper “Multiuser GISSystems with ArcInfo 8: Guidelines for designingand implementing multiuser GIS databases inArcInfo 8”. This paper and the latest databaseperformance enhancement tips can be found atArcOnline:

http://arconline.esri.com.



The next step is to load your existing data into theempty feature classes and tables. The steps forstrategy 1, using the Simple Data Loader, to loaddata from ArcCatalog are presented below.

Loading simple feature data with ArcCatalog

In order to speed the data loading process, you willfirst delete the geometric network made by theSchema Creation Wizard.

1. In the Catalog tree, right-click the geometricnetwork and click Delete.

2. Click Yes.

Deleting the geometric network resets all of thefeature classes in the geodatabase schema to besimple features (points and lines) instead ofnetwork features (edges and junctions) and removesall connectivity rules and class extensions. Becausethey don’t have custom behavior or networkconnectivity, simple features can be loaded muchfaster than custom network features.

After you’ve loaded all of your data, you willrebuild the network and reapply the schema. Thiswill transform the simple features into networkfeatures, and reconnect any class extensions andbehavior.

3. In the Catalog tree, right-click the feature classand click Load Data.

4. Click the browse (folder Icon) button, navigateto and select the input data you want to load.After selecting the datafile, you will see thedatafile displayed in the Input data field.



5. Click the Add button to add the data to the Listof source data to load window.

Selecting the file from the List of source data toload window will activate the Remove button.

6. Click Next.

7. In the Simple Data Loader form, the radiobutton ‘I do not want to load all features into asubtype’ will be active. All other fields aredisabled. Click Next.

8. For each target field in the list, click thematching source field and match the fields anddata types.

One important step in creating your water model isto duplicate the data types of the fields that existin your existing data. This will ensure a smoothdata load transition from source to target fields.

9. After matching all the data types, click Next.



10. If the source coverage or shapefile containsonly features of the type that you’re loading,you can use the default option, Load all of thesource data. Click Next and you’ll be presentedwith a summary of the data loading operation.

Sometimes you will want to load only a selectedgroup of features from your source data into agiven feature class. This would be the case if youhave been using a single coverage feature class orshapefile to hold several types of featuresdifferentiated by an attribute.

11. If you want to load selected features, click‘Load only the features that satisfy a query’.Click Query Builder.

The Query Builder allows you to select whichfeatures to load based on the values of one or moreattributes.

12. Double-click the field you want to query, clickan operator (such as the equals sign), thendouble-click a value of that field in the Uniquesample values list.

Clicking Clear will clear the query, and clickingVerify will verify the query you create.

13. Click OK, then click Next on the Simple DataLoader.

14. The data loader shows a summary of the dataloading operation. Click Finish.

When you click Finish, the data loading operationbegins. A status bar at the lower-left corner of the



ArcCatalog window shows the number of objectsbeing loaded into the feature class.

15. Repeat the process to load the rest of yourfeature classes.

Rebuild the geometric network

Once you’ve loaded all of your data into thegeodatabase, use the Build Geometric NetworkWizard to rebuild your network.

1. Right-click the feature dataset, click New, andclick Geometric Network.

2. Click Next.

3. Click the first option, to build the network usingexisting features.



4. Click the check boxes to turn on the featureclasses that will participate in the geometricnetwork. Click Next. You’ll be warned that thestate of these features will be reset to“Enabled”. Click OK.

5. Click Yes to create complex edge features. Checkthe feature classes that you want to be complexedges (all Water Lines inherit from ComplexEdge Feature, so check all of the line featuresclasses). Click Next.

The Build Geometric Network Wizard allows you tosnap features together if they’re within a snappingtolerance. It also allows you to define sources andsinks, and assign weights in your network. You can’tdo these things through UML.

6. If your features are precisely located, click No.Click Next.

7. Click No if you don’t want to create sources andsinks. Click Next.



8. Click No if you do not want to assign weights toyour network. Click Next.

9. Review the summary and click Finish.

The wizard builds the geometric network.

Reapply the geodatabase schema

Now you will reestablish connectivity rules and anyclass extensions or custom feature behavior, ifpresent.

Use the steps that you initially used to create theschema from the repository.

Register objects as versioned

If you are using versioning in your ArcSDEgeodatabase, you will now register your objects asversioned.

1. In the Catalog tree, right-click the featuredataset, feature class, or table you want to beversioned, and click Register as Versioned.

Loading custom objects

If you have custom objects with custom objectcreation behavior, you may choose to use thismethod, which is the strategy 2, mentioned above.

First, use strategy 1 to load as much as you can ofthe data that doesn’t have custom object creationbehavior.

Loading data with ArcMap

You can use ArcMap to load object data into ageodatabase during an edit session. If you areloading data into an ArcSDE geodatabase that willbe versioned, after you create the schema, registerthe dataset as versioned.

1. In the Catalog tree, right-click the featuredataset, feature class, or table you want toregister as versioned, and click Register asVersioned.



Add Data

You do not need to perform step 1 for personalgeodatabases.

2. Start ArcMap and click the Add Data button onthe Standard toolbar.

3. Navigate to the empty feature class and add it toArcMap.

4. Right-click over a toolbar and click Customize.

5. Click the check box to turn on the Editortoolbar.



6. Click the Commands tab, and click DataConverters.

7. Click and drag Load Objects onto the Editortoolbar. Close the Customize dialog box.

In order for you to use the Load Objects buttonyou will need to start an Edit session.

8. Click Editor and click Start Editing.

9. Select the feature class in the Target dropdownlist.

10. Click Load Objects.

The Object Loader Wizard appears.

From this point, you use many of the same steps toload data with the ArcMap Object Loader Wizard thatyou would use to load data with the Simple DataLoader. One notable addition is that you have theoption to use snapping and validation rules with theObject Loader. You will be prompted to choosewhether to snap the input features using the Editor’scurrent snapping environment and whether to usevalidation rules to validate the features you load.

Snapping is useful when you have some featuresalready loaded and on the map and you want tomake sure that the new features snap to the existingfeatures. If your features are already preciselylocated with respect to the existing features, you donot need to snap them.

11. Repeat the process to load other feature classes.



If you use Strategy 2 and the Object Loader, thefeatures that you load into the versioned ArcSDEgeodatabase will be loaded into the delta tables of thefeatures classes, not the base tables. Once the data isloaded, compress the database in ArcCatalog. Notethat if you are using ArcSDE, additional tuning stepsare usually required at this point. One very importantstep for improving your database performance is to runthe ArcSDE command �� to update the databasestatistics for each feature class that you loaded datainto.

For the most current ArcInfo™, ArcGIS Water, andgeodatabase performance information and tips, see theArcOnline Web site. One great resource is the ESRITechnical Paper “Multiuser GIS Systems withArcInfo 8: Guidelines for designing and implementingmultiuser GIS databases in ArcInfo 8.” This paper canbe found at ArcOnline:

http://arconline.esri.com.



MODIFYING THE SCHEMA IN ARCCATALOG

After you have loaded your data and used yourgeodatabase for some time, you may find that youneed to modify the geodatabase schema. Forexample, your utility might begin using a new pieceof equipment that was not included in the originalschema; now you need to add it to the geodatabase.

You can use ArcCatalog to create a new geodatabaseschema or to modify an existing geodatabaseschema. For more information about designing ormodifying a geodatabase schema with ArcCatalog,see Building a Geodatabase.

Add a subtype with ArcCatalog

In this example, you will add another subtype ofHydrant to your geodatabase.

1. Navigate the Catalog tree to the Hydrant featureclass.

2. Right-click Hydrant and click Properties.

3. Click the Subtypes tab on the Feature ClassProperties dialog box.

The WetBarrel subtype that you added throughUML appears in the Subtypes list. You’ll addanother subtype for the new, Drybarrel, type ofHydrant that your utility has begun to use.

4. Click the cell below the 1, in the Code column,and type “2”. Press the Tab key and type“DryBarrel”.



5. Click the cell beside Barrel Diameter in theDefault Value column. Click the number 10,delete it, and type “8”. Click OK.

Now there are two subtypes of Hydrant. Someoneediting this geodatabase may now create WetBarrelHydrants, with a default BarrelDiameter of 10, orDryBarrel Hydrants, with a default diameter of 8.

You can use ArcCatalog to create new featureclasses and new tables, and to add attributes toexisting feature classes or tables. You can alsocreate and edit relationships and domains, inaddition to default values.

If you use ArcCatalog to modify your geodatabaseschema, it is a good practice to update your UMLmodel so that your blueprint of the geodatabasereflects its current structure.

Note: if you don’t update the UML (and therepository), any customization that you add throughArcCatalog would be lost, should you reapply thegeodatabase schema.



SHARING A GEODATABASE

Once you have created a geodatabase and added data, youneed to make it available to people in your organizationwho use the data. You can create connections to thegeodatabase itself, or create layer files that point to thegeodatabase, or create maps that contain all the layers auser would need for a task.

Creating an SDE connection

The most direct way to make the contents of a multiusergeodatabase available is to create SDE® databaseconnections. Users can open and view the geodatabase inArcCatalog through these connections and add datadirectly to maps.

1. In the Catalog tree, double-click the DatabaseConnections Folder.

2. Double-click Add SDE Connection.

3. Type the name of the Server where your ArcSDEgeodatabase is located in the Server text box.

4. Type the name of the process running on theSDE server that allows connections to thespatial data in the Instance text box. If you arerunning ArcSDE on a Sybase® or SQL ServerRDBMS, type the name of the database in theDatabase text box.

5. Type the username and password for yourRDBMS. Click Test Connection. You will benotified whether the connection information iscorrect. If it is, click OK. If not, correct theinformation.

For more information about creating connections todatabases, see Using ArcCatalog.

If your geodatabase is a personal geodatabase, youcan share it by placing it in a shared folder on yournetwork. You do not need to create connections topersonal geodatabases.

Making folder connections

Another way to distribute data across yourorganization is to place maps and layers in a sharedfolder on your network. The people in yourorganization with file system-level access to thatfolder can use the documents you place there. Youcan make it easy for them to use the maps andlayers by creating folder connections in theirCatalogs.

1. In ArcCatalog, click the Connect to Folderbutton.



2. Navigate to the shared folder on the network.Click the folder and click OK.

3. The connection appears in the Catalog tree.

You can place layers, maps, or data in such a shared folder, and they can be used just as if theywere in a folder on a local drive.

Creating layers

Once you have a place on your network for them,the next task is to create some layers. You cancreate layers in ArcCatalog and in ArcMap.

1. In ArcCatalog, navigate to a feature class.

2. Right-click the feature class and click CreateLayer.

3. Navigate to the folder where you want to savethe layer, type a name for the layer, and clickSave.

The new layer is created in the folder. Now anyonewith access to the folder can use the data.

Layers created in this way use a randomly assignedunique symbol for each subtype present in thefeature class. You can change the symbols for eachsubtype in the layer.



Changing the symbology of a layer

You can change the symbology of a layer in ArcMapor in ArcCatalog. ArcGIS Water comes with anumber of predefined water and wastewatersymbols in the ArcGIS Water style. You’ll use thisstyle to change a symbol for the LateralLine Layer.

1. In ArcCatalog, navigate to the folder where yousaved the layer, right-click the layer and clickProperties.

2. Click the Symbology tab.

The Value Field is Subtype by default. Each of thesubtypes has a symbol beside its name. You’llchange the symbol of one of the subtypes, using asymbol from the ArcGIS Water style.

3. Double-click the line symbol beside the Firesubtype.

4. Click More Symbols.

5. Click ArcGIS Water to turn on the Water style.



6. Scroll down the list of symbols. The ArcGISWater symbols have been added to the bottomof the list. Click the Fire Lateral Line symboland click OK.

7. The FireLateral symbol is changed on the LayerProperties dialog box. Click OK.

Sharing maps

Another way to share your geodatabase is withmaps. Like layers, maps store information abouthow to draw features, but they can store it formultiple layers. They can also store otherinformation, for example, a layout, multiple dataframes, scale-dependent drawing rules, spatialbookmarks, and custom toolbars.

You can use maps to maintain standardized layoutstyles throughout an organization or to providetools and data for specific tasks to specific sets ofusers.

There are two main ways to share data with maps,depending on how you save the map. Maps andlayers contain a reference, like a Windows®

shortcut, to the data that they show. You can savemaps with relative pathnames or absolutepathnames to data. Saving a map with relativepathnames lets you send a folder containing themap and its data to someone who doesn’t haveaccess to your local network. Saving a map withabsolute pathnames lets you distribute copies of themap across your network while referring to data ina centralized location. ArcMap saves maps withabsolute pathnames by default, but the ArcGISWater sample maps use relative pathnames, so theywork, regardless of where they and the sample datawere installed on your computer.

1. Navigate to the Maps folder in the Samplesfolder where ArcGIS Water is installed.

2. Double-click the MWWSSBUtilities.mxd samplemap.

This map shows water, wastewater, and land baseinformation for part of the Montgomery WaterWorks and Sanitary Sewer Board. The data is storedin the sample geodatabases.

For more information about maps and layers, seeUsing ArcCatalog and Using ArcMap.


67

Buildinganalysismodels

The ArcGIS Water data model is a collectionof several dozen object types that serve theneeds of the water and wastewater utilitymarkets. These objects represent commonoutside plant and facilities managementdomain objects.

The organization and structure of the modelis described. These are the topics discussedin this chapter:

• Water and wastewater views of the datamodel

• Water model thematic groups

• Naming conventions and model thematicgroups

4

Ch04 Building analysis models.p65 12/05/2001, 1:21 PM67


ARCGIS WATER DISTRIBUTION OBJECT MODEL

water lines

water features

water distribution

MeterBoxVault

ValveVault

InspectionLeak

MaintenanceRepair

WaterFeature

Water-Structure

Spatial-Operations-

RecordLineProtector

Anode Thrust-Protection

ScadaSensor

Feature

Underground-Enclosure

Casing

AccessTunnelCasement

ConduitBridgeProtectiveTunnel

AnchorBlockingDeadman

Kicker

Complex-Edge-

Feature

MainLine

Pressurized-Main

LateralLine

GravityMain

WaterLine

**

UML diagram keyis a type of

is associated with

1..*

Geodatabase feature classes provide a simple or topologicalstructure to features.

Abstract feature classes define a common set of propertiesshared by inherited feature classes.

Implemented feature classes are instances of the feature classtype. They may or may not represent custom features withspecialized behavior.

is composed of

Abstractfeature class

Geodatabasefeature class

Implementedfeature class

list of subtypes...

multiplicity

EnclosedStorage-Facility

ProductionWellPumpStationStorageBasin

TreatmentPlant

CommercialDomestic

FireHydrantLaterals

IndustrialIrrigation

CarrierInlineStorageTransportPipe

AirReleaseBlowOffBypass

ChemicalInjectionDistributionMain

InterconnectPipeBridge

SamplingStationTransmissionMain


Building analysis models • 69

water facilities

ArcGISFacility

Simple-Junction-Feature

WaterFacility

ManholeLateralPoint

ValveCatchBasin

Cleanout

CleanoutFlushingStructure

LampHole

Fitting

BendCap

CouplingCross

ExpansionJointOffset

ReducerRiser

SaddleSleeve

TapTee

WeldWye

Pump

AxialFlowCentrifugal

JetRotaryScrew

TurbineReciprocating

Meter

FlowTubeFlume

MagneticModifiedVenturi

MultijetOrificePlate

PropellerProportional

SonicTurbineVenturi

WeirDischarge-

Point

ControlValve

AirAirGap

AirReleaseAtmosphericVacuum

CombinationDoubleCheck

Pressure VacuumReducedPressure-

BackflowRPZ

SimpleCheckVacuum

VacuumBreakerVacuumRelease

System-Valve

BallButterfly

ConeGatePlug

DischargeStructureDiversionChamber

DiversionPointJunctionChamber

LiftStationProductionWellPumpStationSplitManholeStorageBasinTideChamber

TreatmentPlant

water equipment

Object

ArcGIS-Equipment

Operations-Record

Analysis-Point Barrel

BarScreen Regulator TideGate Warehouse-EquipmentMotor StandBy-

PowerChemical-

Injector

Warehouse-Pump

Warehouse-Meter

Warehouse-Valve

FlowTubeFlume

MagneticMeterTurbine

ModifiedVenturiMultijet

OrificePlatePropeller

ProportionalSonic

VenturiWeir


JetReciprocating

RotaryScrew

Turbine

Warehouse-ControlValve

AirAirGap



PressureVacuumReducedPressure-

BackflowRPZ

SimpleCheckVacuum


Warehouse-SystemValve

BallButterfly

ConeGatePlug

*

object model

Network-Structure



water lines

water features

sewer / stormwater

MeterBoxVault

ValveVault

InspectionLeak

MaintenanceRepair

WaterFeature

Water-Structure

Spatial-Operations-

RecordLineProtector

Anode Thrust-Protection

ScadaSensor

Feature





TreatmentPlant

Casing

AccessTunnelCasement

ConduitBridgeProtectiveTunnel

AnchorBlockingDeadman

Kicker

Complex-Edge-

Feature

MainLine

Pressurized-Main

LateralLine

GravityMain

WaterLine

ForcePipeBridgePressureVacuum

CollectorCulvert

InlineStorageInterceptor

InvertedSiphonOpenChannel

OutfallOverflowTunnel

CombinationCommercial

DomesticIndustrialIrrigation

**

UML diagram keyis a type of

is associated with

1..*

Geodatabase feature classes provide a simple or topologicalstructure to features.

Abstract feature classes define a common set of propertiesshared by inherited feature classes.

Implemented feature classes are instances of the feature classtype. They may or may not represent custom features withspecialized behavior.

is composed of

Abstractfeature class

Geodatabasefeature class

Implementedfeature class

list of subtypes...

multiplicity

ARCGIS SEWER/STORMWATER OBJECT MODEL



water facilities

ArcGISFacility


WaterFacility

ManholeLateralPoint

ValveCatchBasin

Cleanout

CleanoutFlushingStructure

LampHole

Fitting

BendCap

CouplingCross

ExpansionJointOffset

ReducerRiser

SaddleSleeve

TapTee

WeldWye

Pump


JetRotaryScrew

TurbineReciprocating

Meter

FlowTubeFlume

MagneticModifiedVenturi

MultijetOrificePlate

PropellerProportional

SonicTurbineVenturi

WeirDischarge-

Point

ControlValve

AirAirGap



Pressure VacuumReducedPressure-

BackflowRPZ

SimpleCheckVacuum


System-Valve

BallButterfly

ConeGatePlug




TreatmentPlant

water equipment

Object

ArcGIS-Equipment

Operations-Record

Analysis-Point Barrel

BarScreen Regulator TideGate Warehouse-EquipmentMotor StandBy-

PowerChemical-

Injector

Warehouse-Pump

Warehouse-Meter

Warehouse-Valve

FlowTubeFlume

MagneticMeterTurbine

ModifiedVenturiMultijet

OrificePlatePropeller

ProportionalSonic

VenturiWeir


JetReciprocating

RotaryScrew

Turbine


AirAirGap



PressureVacuumReducedPressure-

BackflowRPZ

SimpleCheckVacuum



BallButterfly

ConeGatePlug

*

object model

Network-Structure



ANALYSIS MODELS

While there are many common real-world objects inwater, wastewater, and stormwater systems, thecommon aspects of these objects become even moreapparent when you begin to group the commonproperties and names of the objects in an analysismodel. The analysis model provides a logicalgrouping of common properties of objects in aninheritance tree. A separate analysis model has beenprovided for both water and wastewater/stormwater networks. While the diagrams split themodel into network domains, this section describesthe entire inheritance model within each thematicgroup.

The process of building an analysis model

In simple terms, an analysis model can be created bystarting with the core ArcGIS object classes and aset of named, real-world objects to be modeled.The creation of the analysis model often beginswith a top-down approach, where the list ofnetwork objects is conceptually divided into logicalgroups. The key characteristic of these groups isthat they share common properties and/or behav-iors. For example, fittings can be grouped togetherbecause they all connect pipes to other pipes.Valves can be grouped together because theyconnect pipes and they have the ability to controlthe flow of water in the network. After a basicgrouping of objects is established, you can begin toidentify more specific similarities between objects.During the process, new classes are identified andsome classes are merged. The final result is a set ofbase classes, intermediate classes, leaf classes, andrelationships.

By defining the properties of each leaf class,common properties appear. For instance, bothwater and gravity mains have material as a property.Rather than duplicate each property in all objects, ahigher-order class is created to contain the commonproperties. This process ultimately results in a setof intermediate, often abstract, classes that modelthe system. The creation of an analysis model is aniterative process that requires both top-down andbottom-up analysis to define the structure of theobject model.

The objects and model are defined using a subset ofthe Unified Modeling Language (UML). Basicresources for UML concepts, rules, notation, andsyntax are required. Guidelines for using the modelwithin ArcCatalog software are also important.

Subtypes

Decisions about subtyping classes are important foryour implementation. For instance, if objects in agrouping have different properties to the point thatthey cannot be grouped together, you need to splityour object into two classes. Examples of this arewater system valves that can be opened and closedto control flow in the network and altitude valves,which open and close automatically when water ina tank goes above and below defined thresholds.While both valves control the flow of water, theyare different enough that two classes were requiredin the model.

Fittings, on the other hand, have been lumped intoa single class in the model. A set of subtypes isused to distinguish the different types of bends,couplers, and reducers. In general, you should tryto lump your objects into fewer classes whereverpossible since there are performance advantages tolumping objects together.



COMPONENT TECHNOLOGY CONSIDERATIONS

LINE THEMATIC GROUP

These are some of the line objects in ArcGISWater.

ComplexEdge

Feature

WaterLine

MainLine LateralLine

Pressurized-Main GravityMain

Complex edges are the base class for all networklines. The WaterLine class was created as a generaltop-level class for any type of network line. Inother words, all classes beneath the WaterLine classwill contain the properties of this feature class.

The inherent behavior of complex edges is verydifferent than the traditional ArcGIS topologymodel. The ArcGIS system automatically maintainsthe relationships between complex edges, anyattached devices, and other edges so you can choosehow to physically segment your network.

For instance, you may choose to physically segmentsewer pipes between manholes since, among otherthings, it is important to capture InvertElevationdata on mains where they connect with manholes.This can only be captured for the starts and ends ofgravity mains so sewer/stormwater networksshould be segmented at manholes. At the same time,

you may not find it necessary to physically segmentsewer pipes at fittings and lateral connections.Once your network is in place, you can move agravity main and any attached laterals and fittings,and other portions of the network will automati-cally move with it.

As with most of the thematic groups discussed inthis document, a common set of properties isdefined in a top-level abstract class. All of theseproperties are inherited by all subclasses beneathWaterLine.

EQUIPMENT THEMATIC GROUP

The Equipment thematic group contains a largenumber of feature classes that do not have a spatialrepresentation. While these aspatial features may besurprising at first glance, there are three importantreasons for the ArcGISEquipment classes:

1. To model a physical device separately from itslocation in the ground using theWarehouseDevice pattern. For example, a valveobject is associated with a valve network featurewhile the valve is in the ground. If the valve isreplaced by another valve and put into storage, itis valuable to maintain the inspection andmaintenance history for the valve and tocontinue to track the physical device in awarehouse or in a truck.

It is also important to track the physical devicefrom an asset management standpoint. When/Ifthe valve is used again, the value and deprecia-tion of the asset is significantly different from anew valve. This WarehouseDevice pattern alsoprovides a flexible way to extend the coresystem for work order and work managementsystems. The designer can create general materialrequests that can be satisfied at the supply chainand/or as-built stages of network constructionwith specific information such as SerialNumber.There is a complex model elaboration beneaththe abstract WarehouseEquipment class thatdescribes this pattern in detail.

2. To provide a mechanism to record maintenance,inspection, and repair records that do not requirea physical location on a map. For instance,hydrant inspection records do not need to be



displayed graphically since they exist for a givenhydrant. Leaks, on the other hand, do need aphysical location along a water main. As a result,two classes are implemented in differentthematic groups:

� OperationsRecord, inheriting from classObject, for nongraphical records such asinspections

� SpatialOperationsRecords, inheriting fromclass Feature for graphical features such asleaks

3. To track miscellaneous facilities such as genera-tors, pumps, and motors that are important froman operations/maintenance perspective but aretypically not placed in a GIS.

FACILITY THEMATIC GROUP

The Facility thematic group includes all networkpoint facilities such as valves, manholes, andfittings. It also contains other junctions includingpump stations and storage basins. Key to theJunction classes are the relationships to aspatialEquipment objects as described above.

ArcGISFacility

Simple junctions are the basic connecting devices inany network. The most significant aspect ofjunctions is that by default they do not result in thephysical segmentation of ComplexEdges. Thedesigner and/or user of a system can choose how tophysically segment the network.

FEATURE THEMATIC GROUP

The Feature thematic group is composed of spatialfeatures that support water networks but do notparticipate in the geometric network. In otherwords, they do not transmit or control the flow ofwater in the network. At the highest level, anabstract WaterFeature class contains properties thatare similar to the other top-level network classes.

DESCRIBING THE OBJECTS

The following diagram shows how the objects arepresented within the data model reference chaptersof this book. The objects are shown in a UML stylebut are represented differently than the UML

models and static analysis diagrams. Propertiesinherited by abstract classes are shown shadedwithin the object and provide clarity for availableproperties and a reference to the abstract classesfrom which the properties are inherited.

The model is represented within a Visio® diagramand can be immediately exported from Visio toMicrosoft® Repository using the Visio UML ExportWizard. The ArcGIS Computer-Aided SoftwareEngineering (CASE) Tool Wizard is used to build aninstance of the mode within a geodatabase.

The following chapters describe the individualclasses and model components.



Object class interface

«refines»

Features and objects in ArcGIS can inherit behavior and properties from one another.

ArcGIS is comprised of objects in a software component framework built on MicrosoftCOM. ArcGIS COM objects use type inheritance to propogate properties and behavior.

This example of the LateralLine class shows how interface inheritance is applied by theCOM objects in ArcGIS.

Interfaces of the object class. Interfaces areshown in the format +/-"propertyname":

"datatype", where +/- indicated if a property ispublic or private.

How objects inherit

+LocationDescription : BSTR+Diameter : long

«Interface»ILateralLine

Properties are shown in the format+/- "propertyname": "datatype",where +/- indicates whether aproperty is public or private.

Normally, the properties of ancestorclasses are not shown for a class in aUML diagram. They are shown hereto clarify the concept of typeinheritance.

Type hierarchyfor lateral lines

Complex-Edge-

Feature

LateralLine

WaterLine

+LocationDescription : esriFieldTypeString+Diameter : esriFieldTypeInteger

LateralLine

+AdministrativeArea : esriFieldTypeString+OperationalArea : esriFieldTypeString+Status : esriFieldTypeInteger+WaterType : esriFieldTypeString+FlowMeasurementID : esriFieldTypeString-Type : esriFieldTypeInteger = 0+FacilityID : esriFieldTypeString+InstallDate : esriFieldTypeDate+Material : esriFieldTypeString

Properties of the WaterLineabstract feature class.

Properties of the LateralLinecreateable feature class.

Object class



77

Linesdata modelreference5

Lines are sets of collection and distributionpipes. Lines have the following characteristics:strength, pressure rating, durability, resistanceto corrosion, inner smoothness, ease oftapping, and the ability to maintain waterquality.


• Abstract feature classes of the linethematic group

• Water lines

• Wastewater lines

Ch05 Lines.p65 12/05/2001, 1:22 PM77


WATER LINES

The assorted types of pipes used in the transmissionand distribution of water (both treated andwastewater/stormwater) are generically termedlines. In general, lines have the followingcharacteristics: strength, pressure rating, durability,resistance to corrosion, inner smoothness, ease oftapping, and ability to maintain water quality.

ComplexEdge

Feature

WaterLine

MainLine LateralLine

Pressurized-Main GravityMain

The water distribution and the sewer/stormwatermodels share the same collection of classes in theirLines thematic groups. Differences between thetwo are limited to the permissible subtypes that areassociated with the various classes. For example,the types of GravityMain in the water distributionmodel are limited to Carrier, InlineStorage, andTransportPipe. In the sewer/stormwater model, thecollection of types is much larger for GravityMainand includes subtypes such as Collector, Culvert,and OpenChannel.

In the following description we will note thedifferences of this sort when appropriate.

WaterLine

The root level of the Lines thematic group is theWaterLine abstract class. The WaterLine class is asubclass of the generic geodatabaseComplexEdgeFeature. Being a subclass, it willinherit the behavior of the ComplexEdgeFeature,most notably, the ability to participate in geometricnetworks.

ComplexEdge

Feature

WaterLine

FlowMeasurementID

Material

WaterType

AdministrativeAreaFacilityID

InstallDateLifecycleStatus

OperationalAreaSubtype

WorkorderID

The WaterLine abstract class defines the followingattributes:

• AdministrativeArea: string—A general-purposestring that is used to store information such asthe name of the municipality/owners.

• FacilityID: string—The line facility identifier.

• FlowMeasurementID: string—The flowmeasurement identifier of the line.

• InstallDate: date—The date the line was installed.

• LifecycleStatus: string—The status of the line.

• Material: string—The material of the line.

• OperationalArea: string—A general-purposeattribute that records information such as thebasin or pressure zone of the line.

• Subtype: integer—A general attribute that is usedto store subtypes. The actual subtypes will bespecified in descendants of this class.

Ch05 Lines.p65 12/05/2001, 1:22 PM78

Lines data model reference • 79

MODELING CONCEPTS OF ARCGIS WATER

LateralLine

A lateral line is a small-diameter pipe that runs fromthe main line to the customer premises. LateralLineis a concrete class. The types of lateral lines areCombination, Commercial, Domestic, Fire,HydrantLateral, Industrial, and Irrigation.

The LateralLine class defines the followingattributes:

• LocationDescription: string—The description ofthe lateral line connection location.

• Size: integer—The size of the lateral line.

• WaterType: string—The type of water found inthe line. These types are CombinedWastewater,PotableWater, RawWater, ReclaimedWater,SaltWater, Sewage, StormRunoff, andWastewaterEffluent. Note that many of thesetypes will not apply to a water distributionsystem. They exist, however, because this classis shared with the sewer/stormwater model.

• WorkorderID: string—The identifier of the workorder that is associated with the installation ofthis line.

WaterLine

LateralLine

LocationDescriptionSize

Ch05 Lines.p65 12/05/2001, 1:22 PM79


MainLine

A main line is a large-diameter pipe that carrieswater from the source through the network.MainLine is an abstract class.

WaterLine

MainLine

ExteriorCoatingJointType[2]LiningTypePipeClassRoughness

The MainLine class defines the following attributes:

• ExteriorCoating: string—The exterior pipe coatingof the main line.

• JointType[2]: string—The joint type of each endof the main line. The joint types (implementedas a coded value domain) are CM, FL, MECH,PO, RCCB, SOL, and WELD.

• LiningType: string—The lining type (interiorcoating) of the main line.

• PipeClass: string—The class rating of the mainline.

• Roughness: double—The roughness coefficient ofthe main line.

GravityMain

A gravity main is a type of main line that isunpressurized and relies on gravity to move thewater through the main. GravityMain is a concreteclass. For the water distribution model, the typesof gravity mains are Carrier, InlineStorage, andTransportPipe.

For the sewer and stormwater model, the types areCollector, Culvert, InlineStorage, InvertedSiphon,Intercepter, OpenChannel, Outfall, Overflow, andTunnel. A collector is a pipe that collects andtransports wastewater to a treatment plant ordisposal system. Service laterals connect tocollectors. Outfalls are the conduit leading to thefinal disposal point or area for wastewater anddrainage. Outfalls discharge into a receiving waterbody, such as a stream, river, lake, ocean, or othersurface, or groundwater. An open channel is achannel open to the environment that transmits rawwater and drainage. Tunnels are used to transmitwater through mountains or deep below theground. Tunnels are generally created in bedrockand may contain features such as pipes and conduitswithin the tunnel. An overflow connects a chamberor pipe to another part of the system or outfallduring overload conditions or peak flows.

GravityMain

BarrelCountCrossSectionShapeDownstreamInvertMeasurement[2]NominalSizeSlope

WaterLine

MainLine

Pressurized-Main

Ch05 Lines.p65 12/05/2001, 1:22 PM80

Lines data model reference • 81

GravityMain defines the following properties:

• BarrelCount: integer—The number of barrelsassociated with the gravity main.

• CrossSectionShape: string—The cross section shapeof the gravity main. The cross section shapes forthe water distribution model are Rectangle,Trapezoidal, Semicircle, Ellipse, and Circular.For the sewer and stormwater model, the shapesare Circular, Horseshoe, Oblong, and Unknown.

• DownstreamInvert: double—The invert elevation(interior bottom) of the downstream end of themain.

• Measurement[2]: double—The measurement of thegravity main.

• NominalSize: double—The nominal size of thegravity main.

• Slope: double—The slope of the gravity main.

PressurizedMain

A pressurized main is a type of main line that ispressurized. PressurizedMain is a concrete class.There are numerous types of PressurizedMains inthe water distribution model; they includeAirRelease, BlowOff, Bypass, ChemicalInjection,DistributionMain, Interconnect, PipeBridge,SamplingStation, and TransmissionMain.

Transmission mains are large-diameter pipelines(24" or larger) that carry large quantities of rawwater long distances from their source to a watertreatment plant, then to the distribution gridsystem. Transmission mains generally run in a ratherstraight line from point to point. Lateral lines arenot attached to transmission mains.

Distribution mains are average-diameter pipes(4"–20") that transport potable water fromtransmission lines and redistribute it throughout anarea. Lateral lines attach directly to distributionmains.

The other types of pressurized mains are sometimestermed minor lines. The assorted minor lines arecommonly used to attach various devices to thedistribution network.

GravityMain

WaterLine

MainLine

PressurizedMain

DepthDiameterGroundSurfaceTypePressureRating

For the sewer and stormwater model, the types areForce, Pressure, PipeBridge, and Vacuum.

PressurizedMain defines the following properties:

• Depth: integer—The depth of the pressurizedmain.

• Diameter: integer—The diameter of thepressurized main.

• GroundSurfaceType: string—The type of theground surface over the pressurized main.

• PressureRating: string—The pressure rating of thepressurized main.

Ch05 Lines.p65 12/05/2001, 1:22 PM81

Ch05 Lines.p65 12/05/2001, 1:22 PM82

83

Equipmentdata modelreference6

Equipment are the features in a water orwastewater system that do not have anassociated geometry or position. Instead, theirlocations are determined by their relationshipswith other explicitly positioned features such asnetwork structures.


• Abstract classes of the Equipmentthematic group

• Equipment objects

Ch06 Equipment.p65 12/05/2001, 1:24 PM83


EQUIPMENT

Equipment are the features in a water or wastewatersystem that do not have an associated geometry orposition. Instead, their locations are determined bytheir relationships with other explicitly positionedfeatures such as network structures. Equipmentfeatures do not directly participate in the activenetwork (i.e., geometric network). Instead, thefeatures that they are associated with participate inthe network.

One key distinguishing aspect of many types ofEquipment is that they may, from time to time, beremoved from the field and placed in warehouses,where they await being placed back in the field.

In ArcGIS Water, the water distribution and thesewer and stormwater models generally share thesame collection of classes in their Equipmentthematic group. Differences between the two arefew, but in the following description, we will notethe differences of this sort when appropriate.

Object

ArcGIS-Equipment

Warehouse-Equipment

Warehouse-Valve

Standby-Power


Warehouse-Hydrant

Operations-Record

Analysis-Point

MotorTideGate AirGap

Chemical-Injector

Surge-ReliefTank

Warehouse-Meter


Warehouse-Pump

BarScreenAerator

Aerator

Regulator

Ch06 Equipment.p65 12/05/2001, 1:24 PM84

Equipment data model reference • 85

AnalysisPoint

Analysis points are locations along the systemnetwork that are linked to external applicationsused for modeling or system analysis.

Object

AnalysisPoint

NetworkOIDRecordIDRecordedValueSubtype

The AnalysisPoint class defines the followingattributes:

• NetworkOID: integer—A general attribute thatmay be used in a user-customized networksolution.

• RecordID: string—A general-purpose string that isused to store the client-specified recordidentifier of the analysis point.

• RecordedValue: integer—The recorded value ofthe analysis point.

• Subtype: integer—The type of the analysis point.

ArcGISEquipment

The root level of the Equipment thematic group isthe ArcGISEquipment abstract class, which is asubclass of Object.

Object

ArcGIS-Equipment

EquipmentIDInstallDateLifecycleStatusManufacturerModelNetworkOIDSerialNumberStatusSubtype

ArcGISEquipment abstract class defines thefollowing attributes:

• EquipmentID: string—A general-purpose stringthat is used to store the client-specifiedidentifier of the equipment.

• InstallDate: date—The date of equipmentinstallation.

• LifecycleStatus: string—The status of theequipment.

• Manufacturer: string—The manufacturer of theequipment.

• Model: string—The model of the equipment.


• SerialNumber: string—The serial number of theequipment.

• Subtype: integer—A general attribute that is usedto store subtypes. The actual subtypes will bespecified in descendants of this class.

Ch06 Equipment.p65 12/05/2001, 1:24 PM85


OperationsRecord

Operations records contain information that links therecord to aspatial data and processes, such as workorders, historical data, or management operations.

Object

OperationsRecord

IDLocationDescriptionNetworkOIDRecordDateSubtype

The OperationsRecord class defines the followingattributes:

• ID: string—A general-purpose string that storesthe client-specified identifier of the operationsrecord.

• LocationDescription: string—The description ofthe operations record location.


• RecordDate: date—The operations recordreference date.

• Subtype: integer—The type of the operationsrecord.

Aerator

An aerator is a holding or treatment pond thatspeeds up the natural process of biologicaldecomposition of organic waste by stimulating thegrowth and activity of bacteria that degradeorganic waste via aeration.

Object

ArcGISEquipment

Aerator

IndividualTrayAreaRiserCountTotalTrayAreaTrayCount

The Aerator class defines the following attributes:

• IndividualTrayArea: string—The area of eachaerator tray.

• RiserCount: string—The number of risers in theaerator.

• TotalTrayArea: string—The total area of all theaerator trays.

• TrayCount: string—The number of aerator trays.

Ch06 Equipment.p65 12/05/2001, 1:24 PM86


AirGap

An air gap is used for protecting against backflow.Air gaps are acceptable in all cross-connectionsituations and for all degrees of risk.

Object

ArcGISEquipment

AirGap

GapMeasureOutletDiameter

The AirGap class defines the following attributes:

• GapMeasure: string—The distance between theeffluent source and the accepting container.

• OutletDiameter: integer—The diameter of theeffluent pipe.

ChemicalInjector

A chemical injector is used to add a chemical(e.g., chlorine-containing gas or liquid) to treated oruntreated water.

Object

ArcGIS-Equipment

Chemical-Injector

ChemicalType

The ChemicalInjector class defines the followingattribute:

• ChemicalType: string—The type of chemical usedby the injector.

Ch06 Equipment.p65 12/05/2001, 1:24 PM87


Motor

Electric motors are the prime power source forpumps in a municipal water system. Electric motorshave smooth power output and high startingtorque, thus making them well suited for beingdirectly connected to centrifugal pumps. Motors aregenerally powered by alternating current (AC).

Object

Motor

AveragePowerUsagePeakPowerUsagePhasesRatedPowerRPMVariableSpeedVoltage

ArcGIS-Equipment

The Motor class defines the following attributes:

• AveragePowerUsage: string—The average amountof power consumed by the motor.

• PeakPowerUsage: string—The peak power usage ofthe motor.

• Phases: string—The number of motor phases(typically, one or three).

• RatedPower: string—The power consumed by themotor.

• RPM: integer—The motor rotations per minute(RPM).

• VariableSpeed: string—A property that representswhether the motor is variable speed.

• Voltage: integer—The voltage of the motor.

StandByPower

Standby power is an alternative power source thatcan be used when the primary power source fails.

Object

StandbyPower

PhasesVoltageAmperage

ArcGIS-Equipment

The StandByPower class defines the followingattributes:

• Phases: string—The number of phases (typically,one or three) provided by the standby power.

• Voltage: string—The voltage of the standbypower.

• Amperage: string—The amperage of the standbypower.

Ch06 Equipment.p65 12/12/2001, 11:50 AM88


SurgeReliefTank

A surge relief tank is a piece of equipment used toabsorb pressure increases in the water system. Surgerelief tanks provide a buffer against throttlingwithin the system by accepting water into a tankthrough a pressure valve.

Object

SurgeReliefTank

PressureSettingCapacity

ArcGIS-Equipment

The SurgeReliefTank class defines the followingattributes:

• Capacity: string—The capacity of the surge relieftank.

• PressureSetting: string—The amount of pressure atwhich the valve controlling the surge relief tankopens.

WarehouseEquipment

WarehouseEquipment is an abstract class that factorscommon attributes of various types of waterequipment that, at various times, are either placedin the field or are returned to a warehouse forservicing. These types of equipment do not possessa spatial representation; instead, they are associatedwith other structures that exist in the field.

Warehouse-Equipment

WarehouseIDWarehouseStatusWarrantyDate

ArcGIS-Equipment

The WarehouseEquipment class defines thefollowing attributes:

• WarehouseID: string—The warehouse identifier ofthe equipment.

• WarehouseStatus: integer—The status (coded valuedomain) of the equipment; these types includeInService, InTransit, InWarehouse, and Retired.

• WarrantyDate: date—The date that the warrantyexpires on the equipment.

Ch06 Equipment.p65 12/05/2001, 1:24 PM89


WarehousePump

A warehouse pump is a piece of equipment thatmoves, compresses, or alters the pressure of a fluid,such as water or air, being conveyed through anatural or artificial channel. Pump types includeAxialFlow, Centrifugal, Jet, Reciprocating, Rotary,Screw, and Turbine.

Warehouse-Equipment

WarehousePump

InletDiameterDischargeDiameter

RatedFlowRatedPressureTotalDynamicHead

ArcGIS-Equipment

The WarehousePump class defines the followingattributes:

• DischargeDiameter: integer—The diameter of thepump discharge (outlet).

• InletDiameter: integer—The diameter of the pumpinlet.

• RatedFlow: integer—The rated flow of the pump.

• RatedPressure: integer—The rated pressure of thepump.

• TotalDynamicHead: integer—The vertical distancefrom the elevation of the hydraulic grade line onthe inlet side of the pump to the hydraulic gradeline on the discharge side of the pump.

WarehouseMeter

A warehouse meter is a piece of equipment that isused to measure water consumption (volume). Thevarious meter types are Compound, Current,DetectorCheck, Magnetic OrificePlate, Pito,PositiveDisplacement, Proportional, Sonic, andVenturi. In sewer and stormwater systems, you alsofind Flume and Weir types.

Warehouse-Equipment

WarehouseMeter

DiameterFlowRangeMeasurementDate

ArcGIS-Equipment

The WarehouseMeter class defines the followingattributes:

• Diameter: integer—The diameter of the meter.

• FlowRange: string—The flow range of the meter.

• MeasurementDate: date—The date of the lastmeter measurement.

Ch06 Equipment.p65 12/05/2001, 1:24 PM90


WarehouseHydrant

A warehouse hydrant is a piece of equipment thatenables fire fighters to attach fire hoses to thedistribution network. Hydrants also have secondaryuses that include flushing main lines and laterals,filling tank trucks, and providing a temporary watersource for construction jobs.

Warehouse-Equipment

Warehouse-Hydrant

BarrelDiameterMainValveTypeNozzleDiameter[4]OutletConfigurationSeatDiameter

ArcGIS-Equipment

The WarehouseHydrant class defines the followingattributes:

• BarrelDiameter: integer—The diameter of thebarrel of the hydrant.

• MainValveType: string—The type of valve usedwith the hydrant.

• NozzleDiameter[4]: integer—The diameter of eachof the four possible nozzles on the hydrant.

• OutletConfiguration: string—The configuration ofthe hydrant outlets.

• SeatDiameter: integer—The diameter of thehydrant seat.

WarehouseValve

WarehouseValve is an abstract class that factors thecommon attributes of the two fundamental typesof warehouse valves.

Warehouse-Equipment

Warehouse-Valve

Diameter

ArcGIS-Equipment

The WarehouseValve class defines the followingattribute:

• Diameter: integer—The diameter of the valve.

Ch06 Equipment.p65 12/05/2001, 1:24 PM91


WarehouseSystemValve

A warehouse system valve is a piece of equipment thatis fitted to a pipeline or orifice in which the closuremember is either rotated or moved transversely orlongitudinally in the waterway so as to control orstop the flow. Additionally, warehouse systemvalves may be used to regulate pressure, isolate,throttle flow, prevent backflow, and relievepressure. The types of system valves include Ball,Butterfly, Cone, Gate, and Plug.

Warehouse-Equipment

WarehouseValve


BypassValveClockwiseToCloseCurrentlyOpenMotorizedNormallyOpenPercentOpenPressureSettingRegulationTypeTurnsToClose

The WarehouseSystemValve class defines thefollowing attributes:

• BypassValve: boolean—A property that indicateswhether the valve has a bypass valve.

• ClockwiseToClose: boolean—A property thatindicates whether the valve stem should beturned clockwise to close the valve.

• CurrentlyOpen: boolean—Indicates that the valveis currently open.

• Motorized: boolean—A property that indicateswhether the valve is motorized.

• NormallyOpen: boolean—Indicates that the valve isnormally open.

• PercentOpen: integer—Indicates the percent avalve is open.

• PressureSetting: string—The pressure setting ofthe valve.

• RegulationType: string—Indicates how the valve isregulated

• TurnsToClose: integer—The number of turnsnecessary to close the valve.

WarehouseControlValve

A warehouse control valve is a piece of equipment thatis fitted to a pipeline or another piece ofequipment’s orifice and is used to control the flowof water. A control valve may be used to controlwater flow into a tower when the tower is not highenough to accept the full system pressure. A controlvalve may also be used to automatically shut offwater flow when the water level in an elevatedtank (or Tower) reaches a preset elevation. Thevalve will open again when the pressure on thesystem side is less than that on the tank side.

Types of control valves represented include AirGap,AirControl, AirRelease, Altitude, BackflowControl,Combination, AtmosphericVacuum, DoubleCheck,PressureVacuum, ReducedPressureBackflow, RPZ,SimpleCheck, Vacuum, VacuumBreaker, andVacuumRelease.

Warehouse-Equipment

Warehouse-Valve


The WarehouseControlValve class does not define anyadditional attributes.

Ch06 Equipment.p65 12/12/2001, 12:13 PM92


Barrel

A barrel is the cylindrical part of a manholebetween the cone and the shelf. Barrels are onlyfound in wastewater and stormwater systems.

Object

Barrel

BarrelShapeCoatingMaterialDiameterLifecycleStatusMaterialRoughness

The Barrel class defines the following attributes:

• BarrelShape: integer—The shape of the barrel.

• CoatingMaterial: string—The coating material ofthe barrel.

• Diameter: integer—The pipe diameter of theassociated pressurized main.

• LifecycleStatus: string—The status of the barrel.

• Material: string—The material the barrel is madeof.

• Roughness: integer—The roughness coefficient ofthe barrel.

BarScreen

A bar screen is a set of parallel bars, either verticalor inclined, that is placed in a sewer or otherwaterway to catch debris. Bar screens are onlyfound in wastewater and stormwater systems.

Object

ArcGIS-Equipment

BarScreen

CleaningMechanismScreenMaterialScreenThicknessSpacingSize

The BarScreen class defines the following attributes:

• CleaningMechanism: string—The mechanism usedto clean the debris from the bar screen.

• ScreenMaterial: string—The type of material thebar screen is made of.

• ScreenThickness: double—The thickness of the barscreen.

• SpacingSize: string—The spacing between the barsin the bar screen.

Ch06 Equipment.p65 12/05/2001, 1:24 PM93


Regulator

A regulator is a device that is used in combinedsewer systems to control or regulate the diversionflow.

Object

Regulator

MaxPercentOpen

SensorTypeMeasurement[2]

ArcGIS-Equipment

The Regulator class defines the following attributes:

• MaxPercentOpen: double—The maximumpercentage that the gate can be opened on theregulator.

• Measurement[2]: integer—The two measurements(horizontal and vertical extents) defining thesize of the regulator.

• SensorType: string—The type of sensor used in theregulator.

TideGate

A tide gate is a device used in sewer and stormwatersystems that is suspended from a free-swinginghorizontal hinge and is usually placed at the end ofa conduit, discharging into a body of water with afluctuating surface elevation. This piece ofequipment is also termed a backwater gate, flapgate, or check gate.

Object

TideGate

MaxPercentOpenMaterial

Measurement[2]ToppingElevation

ArcGIS-Equipment

The TideGate class defines the following attributes:

• Material: string—The type of material the tidegate is made of.

• MaxPercentOpen: double—The maximumpercentage that the tide gate can be opened.

• Measurement[2]: integer—The two measurements(horizontal and vertical extents) defining thesize of the tide gate.

• ToppingElevation: integer—The topping elevationof the tide gate.

Ch06 Equipment.p65 12/05/2001, 1:24 PM94

95

Facilitydata modelreference7

Facilities are features that are used in thetransmission and distribution of water, sewer,or stormwater and are commonly used to joinvarious water lines together. Facilities havegeometric positions and participate in theactive network.


• Abstract classes of the Facility thematicgroup

• Classes of the Facility thematic group

• Description of facility objects

Ch07 Facility.p65 12/05/2001, 2:00 PM95


FACILITIES

Facilities are features that are used in thetransmission and distribution of water (or sewerand stormwater) and are commonly used to joinvarious water lines together. Facilities havegeometric positions and participate in the activenetwork (the geometric network).


ArcGIS-Facility

WaterFacility

Valve

SystemValve

Manhole

Discharge-Point

ControlValve

Hydrant

Network-Structure

Meter

Clearwell

Pump

LateralPoint

Fitting

CatchBasin

Sampling-Station

Ch07 Facility.p65 12/05/2001, 2:00 PM96

Facility data model reference • 97

ArcGISFacility

The root level of the Facility thematic group is theArcGISFacility abstract class. The ArcGISFacilityclass is a subclass of the generic geodatabase simplejunction feature. Being a subclass, it will inherit thebehavior of the simple junction feature, mostnotably, the point geometric representation and theability to directly participate in geometricnetworks.


ArcGISFacility

AdministrativeAreaFacilityIDInstallDateLifecycleStatusLocationDescriptionOperationalAreaRotationSubtypeWorkorderID

The ArcGISFacility abstract class defines theseattributes:

• AdministrativeArea: string—A general-purposestring that is used to store information such asthe name of the municipality/owners.

• FacilityID: string—The user-specified identifierof the facility.

• InstallDate: date—The date the equipment wasinstalled.

• LifecycleStatus: string—The status of the facility;types are Proposed, Active, Abandoned, andInactive.

• LocationDescription: string—The description ofthe facility connection location.

• OperationalArea: string—A general-purposeattribute used to record information such as thebasin or pressure zone that the facilityparticipates in.

• Rotation: double—The rotation of the symbolrepresenting the facility.

• Subtype: integer—A general attribute used to storesubtypes. The actual subtypes will be specified indescendants of this class.

• WorkorderID: string—The identifier of the workorder associated with the installation of thisfacility.

NetworkStructure

Network structures are used for a variety of purposeswithin a water distribution system. These purposesinclude equalizing supply and demand, increasingoperating convenience, leveling out pumpingrequirements, minimizing power costs, providingwater in the event of pump or supply failure, andproviding large quantities of water for fightingfires.

The primary types of water network structures areenclosed StorageFacilities, PumpStations,TreatmentPlants, and ProductionWells.

The Primary types of wastewater networkstructures are DiversionChamber,JunctionChamber, PumpStation, StorageBasin,TreatmentPlant, DischargeStructure,DiversionPoint, ProductionWell, SplitManhole,TideChamber, and LiftStation.

Structures may either be enclosed or open and maycontain either raw or treated water.


NetworkStructure

NameNetworkUsageOperationalDateReferenceIDSourceWaterStructureOID

ArcGISFacility

Ch07 Facility.p65 12/05/2001, 2:00 PM97


The NetworkStructure class defines the followingattributes:

• Name: string—The network structure name.

• NetworkUsage: string—The usage of the structure;types include Raw, Potable, Treated, Storm,WastewaterEffluent, Reclaimed, and Other.

• OperationalDate: date—The date the structurebecame operational.

• ReferenceID: string—A general-purpose string thatstores a key to reference information.

• Source: string—The source entering the structure.

• WaterStructureOID: integer—A general attributethat may be used in a user-customized networksolution.

WaterFacility

The WaterFacility class is an abstract class thatfactors common properties found in the water- andwastewater-specific facilities. (Recall that facilitiescorrespond to junction features within the activewater network.)


WaterFacility

ElevationWaterType

ArcGISFacility

The WaterFacility class defines the followingattributes:

• Elevation: double—The elevation of the waterfacility.

• WaterType: string—The type of the water foundin the water facility. These types areCombinedWastewater, PotableWater, RawWater,

ReclaimedWater, SaltWater, Sewage,StormRunoff, and WastewaterEffluent. Notethat many of these types will not apply to awater distribution system. They exist, however,because this class is shared with the sewer/stormwater model.

Fitting

The Fitting class represents the facility found at thejoint between two lines where a transition of somesort must occur. In order to cut down on thenumber of network feature classes and improvegeometric network performance, we have chosen torely on subtypes here to differentiate the differenttypes of fitting-related classes.

Fitting types include Bend, Cap, Cross, Coupling,ExpansionJoint, Offset, Reducer, Riser, Saddle,Sleeve, Tap, Tee, Wye, and Weld.

WaterFacility

Fitting

Diameter[4]JointTypeMaterial

The Fitting class defines the following attributes:

• Diameter[4]: integer—The size of each of thefour possible orifices on the fitting.

• JointType: string—The joint type of the orificeson the fitting. The joint types (implemented as acoded value domain) are CM, FL, MECH, PO,RCCB, SOL, and Weld.

• Material: string—The material that the fitting ismade of. The types of material include ACP,PCPP, RCP, TRUSS, VCP, ABS, PE, RPM, RTR,STL, CIP, DIP, PVC, and Brass.

Ch07 Facility.p65 12/05/2001, 2:00 PM98


LateralPoint

A lateral point represents the location of theconnection between the customer and thedistribution system.

WaterFacility

LateralPoint

AccountIDCriticalCustomer

ArcGISFacility

The LateralPoint class defines the followingattributes:

• AccountID: string—The account identifier of thelateral point.

• CriticalCustomer: boolean—A Boolean value thatrepresents whether the lateral point is associatedwith a critical customer.

Hydrant

A hydrant enables fire fighters to attach fire hoses tothe distribution network. Hydrants also havesecondary uses that include flushing main lines andlaterals, filling tank trucks, and providing atemporary water source for construction jobs.

Hydrants have an association with aWarehouseHydrant object. The warehouse hydrantcontains the key inventory/warehouse-relatedproperties, while the Hydrant facility class isintended primarily to represent the position andconnectivity of the warehouse hydrant. Certainwarehouse hydrant properties are cached within thehydrant, namely, each of the five that are found onthe Hydrant class itself (but not including thoseinherited from its ancestors in the model).

WaterFacility

Hydrant

BarrelDiameterMainValveTypeNozzleDiameter[4]OutletConfigurationSeatDiameter

Warehouse-Hydrant

0..1

ArcGISFacility

The Hydrant class defines the following attributes:

• BarrelDiameter: integer—The diameter of thebarrel of the hydrant.

• MainValveType: string—The type of the valveused with the hydrant.

• NozzleDiameter[4]: integer—The diameter of eachof the four possible nozzles on the hydrant.

• OutletConfiguration: string—The configuration ofthe hydrant outlets.

• SeatDiameter: integer—The diameter of thehydrant seat.

Ch07 Facility.p65 12/05/2001, 2:00 PM99


Manhole

A manhole is a facility that is used to allow access towater lines. There are two primary types ofmanholes: standard manholes and drop manholes. Astandard manhole is an opening in a sewer allowingaccess operators or equipment. It may also be calledan access hole or maintenance hole. Drop manholeshave a line entering the manhole at a higherelevation than the main flow line or channel (hencethe “drop”). Drop manholes themselves come intwo varieties: inside drop and outside drop. Insidedrop manholes route the higher-elevation flowdown through the manhole barrel. Outside dropmanholes route the flow to the main manholechannel outside of the manhole. Being a facility, amanhole plays the role of a junction on the activenetwork.

WaterFacility

Manhole

AccessDiameterAccessTypeGroundTypeHighPipeElevationInteriorDropInvertElevationWallMaterial

ArcGISFacility

The Manhole class defines the following attributes:

• AccessDiameter: integer—The diameter of themanhole access hole.

• AccessType: string—The access type of themanhole.

• GroundType: string—The ground surface typesurrounding the manhole. Surface types includeGrass, Concrete, Soil, and Pavement.

• HighPipeElevation: double—The elevation of thehighest pipe connected to the manhole.

• InteriorDrop: boolean—The diameter of the barrelof the hydrant.

• InvertElevation: double—The bottom elevation (orinvert) inside the manhole.

• WallMaterial: string—The material the manholewall is made of.

Meter

A meter is a facility that is used to measure waterconsumption (volume). Being a facility, a meterplays the role of a junction on the active network.Meters are also much like hydrants as they alsohave an associated warehouse object, namely, aWarehouseMeter.

The various water meter types are Compound,Current, DetectorCheck, MagneticOrifice, Pito,PositiveDisplacement, Proportional, Sonic, andVenturi. In sewer and stormwater systems the metertypes are Flume, Magnetic, ModifiedVenturi,MultiJet, OrificePlate, Propeller, FlowTube,Proportional, Sonic, Turbine, Venturi, and Wier.

WaterFacility

Meter

DiameterFlowRangeMeasurementDate

Warehouse-Meter

0..1

ArcGISFacility

The Meter class defines the following attributes:

• Diameter: integer—The diameter of the meter.

• FlowRange: string—The flow range of the meter.

• MeasurementDate: date—The date the lastmeasurement was recorded for the meter.

Ch07 Facility.p65 12/05/2001, 2:00 PM100


ClearWell

A clear well is an enclosed tank that is associatedwith a treatment plant. Clear wells are used to storefiltered water of sufficient capacity to prevent theneed to vary the filtration rate with variations indemand. Clear wells are also used to providechlorine contact time for disinfection. Pumps areused to move the water from the clear well to thetreatment plant or to a distribution system.

WaterFacility

ClearWell

CapacityDepthDiameter[2]OperatingMaxOperatingMinStationID

ArcGISFacility

The ClearWell class defines the following attributes:

• Capacity: string—The capacity of the clear well.

• Depth: integer—The depth of the clear well.

• Diameter[2]: string—The planform size of theclear well.

• OperatingMax: string—The maximum operatingdepth of the water within the clear well.

• OperatingMin: string—The minimum operatingdepth of the water within the clear well.

• StationID: string—The station identifier of theclear well.

Pump

A pump is a facility that moves, compresses, oralters the pressure of a fluid, such as water or air,being conveyed through a natural or artificialchannel. Pumps are also much like hydrants andmeters as they also have an associated warehouseobject (WarehousePump).

Pump types include AxialFlow, Centrifugal, Jet,Reciprocating, Rotary, Screw, and Turbine.

WaterFacility

Pump

InletDiameterDischargeDiameter

RatedFlowRatedPressureTotalDynamicHead

Warehouse-Pump

0..1

ArcGISFacility

The Pump class defines the following attributes:

• DischargeDiameter: integer—The diameter of thepump discharge (outlet).

• InletDiameter: string—The diameter of the pumpinlet.

• RatedFlow: integer—The flow rating of the pump.

• RatedPressure: string—The pressure rating of thepump.

• TotalDymanicHead: string—The measurment ofthe total dynamic head generated by the pump.

Ch07 Facility.p65 12/05/2001, 2:00 PM101


SamplingStation

A sampling station is a facility that is used forcollecting water samples. Sampling stations may bededicated sampling devices, or they may be otherdevices of the system where a sample may beobtained.

WaterFacility

Sampling-Station

StationID

ArcGISFacility

The SamplingStation class defines the followingattributes:

• StationID: string—The identifier of the samplingstation.

Valve

A valve is a facility that is used to control the flowof water through the system. The Valve class isabstract and factors the common attributes foundin the two concrete types of valve: the systemvalve and the control valve.

WaterFacility

Diameter

Valve

ArcGISFacility

The Valve class defines the following attributes:

• Diameter: integer—The diameter of the valve.

SystemValve

A system valve is a facility that is fitted to a pipelineor orifice in which the closure member is eitherrotated or moved transversely or longitudinally inthe waterway so as to control or stop the flow.System valves are used to regulate pressure, isolate,throttle flow, prevent backflow, and relievepressure.

System valve types include Gate, Plug, Ball, Cone,and Butterfly. These specific types may be classifiedas isolation valves.

Isolation valves are designed to start and stop theflow of water within the distribution network (andisolate portions of the network for maintenance orrepair). Isolation valves are the predominant typeof SystemValve installed in a distribution network.They are commonly intended to be either fully openor fully closed. They are not intended to throttleflow by being partially open.

A gate valve is an isolation valve (which is modeledhere as a system valve) that is used to preventwater flow via a simple gate mechanism. Gate

Ch07 Facility.p65 12/05/2001, 2:00 PM102


valves may be motorized (and remotely controlled),and they may also have small bypass valves. Gatevalves are not installed in locations where theyneed to be frequently operated due to the timerequired to open and close them.

A butterfly valve is similar to a gate valve but usesa disk that is rotated ninety degrees to control theflow of water. Butterfly valves operate easier underlarge pressures and volumes of water than standardgate valves, and are thus found on larger pipes.However, because the butterfly valve disk stays inthe water path even when the valve is open, thevalve creates a higher resistance to flow (i.e.,pressure loss) than a gate valve. Additionally, if itbecomes necessary to clean a main by using pigs orswabs, the butterfly valve would block theoperation. Butterfly valves can be operated quickly,increasing the risk of serious water hammer.

WaterFacility

Valve

SystemValve

BypassValveClockwiseToCloseCurrentlyOpenMotorizedNormallyOpenPercentOpenPressureSettingRegulationTypeTurnsToClose


0..1

The SystemValve class defines the followingattributes:

• BypassValve: boolean—Represents whether thesystem valve has a bypass valve.

• ClockwiseToClose: boolean—Represents whetherthe stem is turned clockwise to close the systemvalve.

• CurrentlyOpen: boolean—Whether the system valveis currently open.

• Motorized: boolean—Whether the system valve ismotorized.

• NormallyOpen: boolean—Whether the system valveis normally open.

• PercentOpen: integer—The percentage the systemvalve is open.

• PressureSetting: string—The pressure setting ofthe system valve.

• RegulationType: string—The regulation type usedon the system valve.

• TurnsToClose: integer—The number of turnsrequired to close the system valve.

ControlValve

Control valves are a set of valves that operate inspecial ways. There are three fundamental types ofcontrol valves: backflow control, air control, andaltitude. A backflow control valve is a controlvalve designed to prevent water from flowing inthe reverse direction. Essentially, backflow controlvalves allow flow in only one direction—thenormal flow direction. Backflow control valves areopen in the direction of normal flow and closedwith the reversal of flow. Backflow control valvesare commonly found near pump stations andreservoirs. Air control valves are control valvesthat are used to either relieve the system of trappedair or vacuums that may develop. Finally, analtitude valve is a control valve that controls waterflow into a tower when the water level dropsbelow a threshold. Altitude valves automaticallyshut off water flow when the water level in anelevated tank (or tower) reaches a preset elevation.A pressure reducing valve is a system valve with ahorizontal disk for automatically reducing waterpressures to a preset value. A pressure relief valveis a system valve that opens automatically whenwater pressure reaches a preset limit to relievestress on a pipeline. Pressure relief valves are used

Ch07 Facility.p65 12/05/2001, 2:00 PM103


to protect against rapid increases in pressure (i.e.,water hammer). A pressure sustaining valve is asystem valve that automatically sustains waterpressures at a preset value. A pressure sustainingvalve is similar to a pressure reducing valve butgoverns the pressure on the upstream rather thanthe downstream flow.

Types of control valves represented include AirGap,AirControl, AirRelease, Altitude, BackflowControl,Combination, AtmosphericVacuum, DoubleCheck,PressureVacuum, ReducedPressureBackflow, RPZ,SimpleCheck, Vacuum, VacuumBreaker, andVacuumRelease.

WaterFacility

ControlValve

Valve


0..1

The ControlValve class does not define anyadditional attributes.

Cleanout

A cleanout is a sewer and stormwater-specificfacility that is used as an opening in a collectionsystem for inserting tools, rods, or snakes whilecleaning a pipeline or clearing a stoppage. Cleanouttypes include two-way cleanouts, which aredesigned for working a snake into the pipe in eitherdirection. Two-way cleanouts are commonly foundin laterals or near a property line.

WaterFacility

Cleanout

AccessDiameterAccessMaterialDepthFrameMaterial

ArcGISFacility

The Cleanout class defines the following attributes:

• AccessDiameter: integer—The access diameter ofthe cleanout.

• AccessMaterial: string—The material that theaccess point is made of.

• Depth: double—The depth of the cleanout.

• FrameMaterial: string—The material that theframe is made of.

Ch07 Facility.p65 12/05/2001, 2:00 PM104


DischargePoint

A discharge point is a sewer and stormwater-specificfacility where wastewater drainage is dischargedfrom the system. A discharge point may be locatedat the terminus of an outfall or modeled in place ofan outfall.

WaterFacility

DischargePoint

AverageDischargeDiameterDischargeIDPeakDischarge

PermitNamePermitID

ArcGISFacility

The DischargePoint class defines the followingattributes:

• AverageDischarge: string—The average amount ofwater discharged at the discharge point.

• Diameter: integer—The diameter of the dischargepoint.

• DischargeID: string—The identifier of thedischarge point.

• PeakDischarge: string—The peak discharge amountat the discharge point.

• PermitID: string—The identifier of the dischargepoint permit.

• PermitName: string—The name associated withthe discharge point permit.

CatchBasin

A catch basin is a chamber or well used with stormor combined sewers to receive runoff into thecollection system. Catch basins are used as a meansof removing debris and solids that could enter thecollection system. Catch basins may also be modeledas curb inlets or stormwater inlets.

WaterFacility

CatchBasin

AccessDiameterAccessMaterialAccessTypeInvert

ArcGISFacility

The CatchBasin class defines the followingattributes:

• AccessDiameter: integer—The diameter of theaccess location on the catch basin.

• AccessMaterial: string—The material the accesslocation on the catch basin is made of.

• AccessType: string—The type of access for thecatch basin.

• Invert: integer—The invert elevation of the catchbasin.

Ch07 Facility.p65 12/05/2001, 2:00 PM105

Ch07 Facility.p65 12/05/2001, 2:00 PM106

107

8 Featuredata modelreference

Features are spatial entities in water, sewer,and stormwater systems that do notparticipate in the active network—effectively,traces and other network operations do notincorporate these entities.


• Abstract classes of the Feature thematicgroup

• Features

Ch08 Features.p65 12/05/2001, 2:02 PM107


Features are spatial entities in water, sewer, andstormwater systems that do not participate in theactive network—effectively, traces and othernetwork operations do not incorporate theseentities.

FEATURES

Feature

WaterFeature

Line-Protector

Casing

Spatial-Operations-

RecordWaterSource

Anode

Underground-EnclosureScadaSensor

Thrust-Protection

Ch08 Features.p65 12/05/2001, 2:02 PM108

Feature data model reference • 109

WaterFeature

The root level of the Feature thematic group is theWaterFeature abstract class. The WaterFeature classis a subclass of the generic geodatabase feature.Being a subclass, it will inherit the behavior of thefeature, most notably, a spatial representation. Itcannot, however, participate in geometricnetworks.

Feature

WaterFeature

AdministrativeArea

FacilityIDInstallDate

OperationalAreaSubtype

WorkorderID

Elevation

LocationDescription

WaterType

The WaterFeature abstract class defines thefollowing attributes:

• AdministrativeArea: string—A general-purposestring used to store information such as the nameof the municipality/owners.

• Elevation: float—The elevation of the waterfeature.

• FacilityID: string—The user-specified identifierof the feature.

• InstallDate: date—The date the feature wasinstalled.

• LocationDescription: string—The description ofthe water feature location.

• OperationalArea: string—A general-purposeattribute used to record information such as thebasin or pressure zone that the featureparticipates in.

• Subtype: string—A general attribute used to storesubtypes. The actual subtypes will be specified indescendants of this class.

• WaterType: string—The type of water found inthe water feature. These types areCombinedWastewater, PotableWater, RawWater,ReclaimedWater, SaltWater, Sewage,StormRunoff, and WastewaterEffluent.

• WorkorderID: string—The identifier of the workorder that is associated with the installation ofthis feature.

UndergroundEnclosure

UndergroundEnclosure is a general-purpose class that’sintended to house various types of aspatialequipment found in a water system. Theunderground enclosures allow access to and provideprotection of facilities and equipment in the watersystem. The contained equipment does notparticipate in the network—their relationship tothe underground equipment is via peer-to-peerassociations. The types of underground enclosuresare MeterBox, ValveVault, and Vault.

WaterFeature


CoverMaterialCoverTypeDepthFrameMaterialFrameTypeInvertElevationMeasurement[2]

The UndergroundEnclosure class defines thefollowing attributes:

• CoverMaterial: string—The material comprisingthe cover of the underground enclosure.

• CoverType: string—The type of undergroundenclosure cover.

Ch08 Features.p65 12/05/2001, 2:02 PM109


• Depth: double—The depth of the undergroundenclosure.

• FrameMaterial: string—The material comprisingthe underground enclosure frame.

• FrameType: string—The type of the undergroundenclosure frame.

• InvertElevation: double—The invert elevation ofthe underground enclosure.

• Measurement[2]: integer—The dimensions of theunderground enclosure.

ScadaSensor

The SCADA sensor is a feature that’s used toremotely measure the status of networkcomponents as part of a supervisory control anddata acquisition (SCADA) system. SCADA systemsprovide alarms, responses, data acquisition, andcontrol for collection and distribution systems.Operators use the SCADA system to monitor andadjust processes and facilities.

WaterFeature

ScadaSensor

CurrentValueIDMeasurementType

The ScadaSensor class defines the followingattributes:

• CurrentValue: string—The current value beingregistered by the SCADA sensor.

• ID: string—The identifier of the SCADA sensor.

• MeasurementType: string—The type ofmeasurement recorded by the SCADA sensor.These measurement types are Amperage,ChlorineResidual, ChlorineTankWeight, Depth,DischargePressure, Elevation, Flow, Pressure,SuctionPressure, TankLevel, Temperature,Turbidity, Velocity, Voltage, and WellLevel.

SpatialOperationsRecord

The spatial operations record is a feature that’s usedto represent an operations record tied to ageographic location. These records may or may notbe directly associated with another line or facilityin the system. For example, a spatial operationsrecord may be used to record the exact locationalong a line where a repair occurred. The types ofspatial operations records are Leak, Maintenance,Repair, and Inspection.

WaterFeature

SpatialOperations-Record

IDNetworkOIDRecordDate

The SpatialOperationsRecord class defines thefollowing attributes:

• ID: string—The identifier of the spatialoperations record.


• RecordDate: date—The date when the operationoccurred.

Ch08 Features.p65 12/05/2001, 2:02 PM110


WaterStructure

The water structure is a larger feature that’s used tohouse, or logically group, other equipment in awater system. The water structure is similar to thenetwork structure but differs in that it does notparticipate in the active network. The types ofwater structures are EnclosedStorage,ProductionWell, PumpStation, StorageBasin, andTreatmentPlant.

WaterFeature

WaterStructure

OperationalDate

The WaterStructure class defines the followingattribute:

• OperationalDate: date—The date the waterstructure became operational.

LineProtector

LineProtector is an abstract class that’s used withinthis model to group together other concrete classesthat are used to protect other water lines.

WaterFeature

LineProtector

The LineProtector class does not define anyattributes.

Ch08 Features.p65 12/05/2001, 2:02 PM111


Casing

The casing is a line protector that surrounds orencloses a water line in order to protect it fromphysical damage or other ground-basedcontaminants. Casings are used when installingwater mains under railroad tracks, major highways,and other obstructions. Types of casings areCasement, ConduitBridge, ProtectiveTunnel, andAccessTunnel.

WaterFeature

LineProtector

Casing

DiameterMaterialRecordedLength

The Casing class defines the following attributes:

• Diameter: integer—The diameter of the casing.

• Material: string—The material the casing is madeof.

• RecordedLength: double—The recorded length ofthe casing.

Anode

An anode is a feature (specifically, an electricalmechanism) that’s applied to system components forthe prevention of rust, pitting, and the corrosionof metal surfaces that are in contact with water orsoil. A low-voltage current is applied to the wateror soil in contact with the metal, such that theelectromotive force renders the metal componentcathodic. Corrosion is concentrated on the anodesinstead of on the associated (and protected) watersystem components. This type of corrosion mayoccur in copper, steel, stainless steel, cast iron, andductile iron pipes.

WaterFeature

LineProtector

Anode

AnodeCountMaterialWeight

The Anode class defines the following attributes:

• AnodeCount: integer—The number of anodes atthe geographic location.

• Material: string—The material comprising theanode.

• Weight: string—The weight of the anode.

Ch08 Features.p65 12/05/2001, 2:02 PM112


ThrustProtection

The ThrustProtection class represents a type of lineprotector that’s used to prevent pipe movement.Thrust protection is commonly implemented asthrust blocks (masses of concrete material) that areplaced at bends and around valve structures. Thetypes of thrust protection include Anchor,Blocking, Deadman, and Kicker.

WaterFeature

LineProtector

Thrust-Protection

The ThrustProtection class does not define anyattributes. It is expected that attributes will beadded to this class during configuration.

Ch08 Features.p65 12/05/2001, 2:02 PM113

Ch08 Features.p65 12/05/2001, 2:02 PM114

Index

A

Aeratordescription 86

Aerator classattributes of 86description of 86

Air gapdescription 87

AirGap classattributes of 87description 87

AltitudeValve 92, 103Analysis points

description 85AnalysisPoint class

attributes of 85Anode

description 112Anode class

attributes 112ArcCatalog

adding attributes 16adding behavior 21changing the symbology of a

layer 65connectivity rules for objects

17creating a geometric network

21creating a layer 64creating object classes 21creating relationships 21creating subtypes 21creating the schema 16creating validation rules 21customizing an ArcGIS Water

geodatabase 27domains 16, 17functionality 12geodatabase management tools

16modifying the schema 21, 61new attributes 17

ArcCatalog (continued)providing access to information

18reading the repository 17refining the geodatabase 13registering objects as versioned

57relationships 16, 17using the Simple Data Loader

52viewing the geodatabase 63working with the geodatabase

22ArcCatalog Simple Data Loader

50ArcGIS Water

analysis modelscreating 72describing the objects 74description 72Equipment subsystem 73Facility subsystem 74Feature subsystem 74Line subsystem 73modeling decisions 72represented within Visio 74

business needs 3data model 11deploying

creating a geodatabase 10planning and design 10sharing your geodatabase 10

implementationoptions 13scenarios 16

implementation resourcescomponent reference 23database schema 23Microsoft Repository 23UML 23

implementingfrom a repository 17, 20

installing 20performance information and

tips 60Repository samples 41style 65symbology 65

ArcGIS Water (continued)UML 17users 3

ArcGIS Water Repositories 41ArcGIS Water sample maps 66ArcGIS Water style 65ArcGISEquipment abstract class

attributes of 85description 85

ArcGISFacility abstract classattributes of 97description 97

ArcIMS 12ArcInfo

performance information andtips 60

ArcMap 57ArcGIS Water style 65change the symbology of a layer

65customization 18functionality 12loading object data 57mentioned 18using the Object Loader 51working with the geodatabase

22ArcMap Object Loader 50ArcObjects 12ArcOnline Web site 60ArcSDE 12

additional tuning steps 60C API 12importing data from 22

ArcSDE geodatabase 22, 41, 57database performance 60performance information and

tips 60register your objects as

versioned 57update the database statistics

60ArcStorm

importing data from 22Asset management 7Attributes 10

Index.p65 12/05/2001, 2:05 PM115


B

Bar screendescription 93

Barreldescription 93

Barrel classattributes of 93

BarScreen classattributes of 93

Building a Geodatabase 21

C

CASEto design geodatabase schema

13Case Study

implementing ArcGIS Water 20CASE Tool 44, 48

modifying an object 44, 48CASE Tools subsystem

Code Generation Wizard 17generating code 17

Schema Creation Wizard 17, 21Casing

description 112Casing class

attributes of 112subtypes of

AccessTunnel 112Casement 112ConduitBridge 112ProtectiveTunnel 112

Catalogs of data 22Catch basin

description 105CatchBasin class

attributes of 105Changing the symbology of a layer

65Chemical injector

description 87ChemicalInjector class

attributes of 87Class extensions

removing 52

Clear welldescription 101

ClearWell classattributes of 101

Coded value domaindefined 37

COM 75COM object 14Component Object Model (COM)

3Components included 23Connect to Folder button 63Connections 12, 18, 22

building catalogs of data 22creating 63file system-level access 63

Connectivity rules 39design 39use of matrix diagrams 39

Control access 18Control valves

description 103Controlling access

file system-level security 18ControlValve class


AirGap 104AirRelease 104Altitude 104AtmosphericVacuum 104BackflowControl 104Combination 104DoubleCheck 104PressureVacuum 104ReducedPressureBackflow

104RPZ 104SimpleCheck 104Vacuum 104VacuumBreaker 104VacuumRelease 104

Coordinate system 42, 48. SeeSpatial Reference

Coveragesimporting data from 21

Customer information systemlinking to 7

D

Data 64distributing your data

shared folder 63Data assessment 20dBASE

importing data from 21Design guidelines 13Digitizing tools 18Discharge point

description 105DischargePoint class

attributes of 105Distributing your data 22, 63,

64. See also Sharing yourgeodatabase

Distribution systemscharacteristics 5

DistributionMain 81Domain

adding coded values 37specifying

default values 37

E

Equipment subsystem. See alsoArcGIS Water: analysismodels: Equipmentsubsystem

overview 84ESRI Technical Paper

Multiuser GIS Systems withArcInfo 51, 60

Exploring ArcObjects 17Exporting UML to the Microsoft

Repository 40

F

Facilitiesdescription 96

Facilities subsystem overview 96Facility subsystem. See ArcGIS

Water: analysis models:Facility subsystem

Index.p65 12/05/2001, 2:05 PM116

Index • 117

Feature package overview 108Feature subsystem. See ArcGIS

Water: analysis models:Feature subsystem

Featuresdescription 108

Fitting classattributes of 98description 98subtypes of

Bend 98Cap 98Coupling 98Cross 98ExpansionJoint 98Offset 98Reducer 98Riser 98Saddle 98Sleeve 98Tap 98Tee 98Weld 98Wye 98

G

Geodatabasecreating 11, 16, 18, 21, 22,

42, 48file system security 18generating a custom geodatabase

21importing data 21modeling flows 18performance information and

tips 60reapplying the schema 57serving 12trace connectivity 18versions of 18

Geodatabase data model 11Geodatabase design process

design guidelines 13designing with CASE tools 13example: modeling a gate valve

14

Geodatabase design process(continued)

implementation options 13ways to create the

geodatabase 13Geodatabase model 11Geometric network

Build Geometric NetworkWizard 55

assign weights 56define sources and sinks 56snap features together 56

deleting 52rebuilding 55

GravityMaindescription of 80subtypes of

Intercepter 80InvertedSiphon 80TransportPipe 80

GravityMain abstract classattributes of 80subtypes of

Carrier 80Collector 80Culvert 80InlineStorage 80OpenChannel 80Outfall 80Overflow 80Tunnel 80

H

http://arconline.esri.com 51, 60Hydrant. See also

WarehouseHydrant classdescription 99

Hydrant classattributes of 99

I

Importing data 21vs. loading data 22

INFO tablesimporting data from 21

Instance text box 63

J

Java Client API 12

L

Lateral 79, 80, 81, 99Lateral point

description 99LateralLine

attributes of 79description 79subtypes of

Commercial 79Domestic 79Fire 79HydrantLateral 79Industrial 79Irrigation 79

LateralPoint classattributes of 99

Layers 12, 22, 63, 64creating 64defined 18

Line subsystem. See also ArcGISWater: analysis models:Equipment subsystem

characteristics 78overview 78

LineProtector abstract classattributes 111description 111

Loading data 21ArcCatalog Simple Data Loader

50ArcMap Object Loader 50ArcSDE

additional tuning steps 60update the database statistics

60deleting the geometric network

52example of how the Object

Loader works 21loading custom objects 57loading existing data 52loading selected features 54removing class extensions 52

Index.p65 12/05/2001, 2:05 PM117


Loading data (continued)removing connectivity rules 52requirements 51simple features

lack of custom behavior 52network connectivity 52

strategies for 50versioned databases 51vs. importing data 22within an ArcMap edit session

51Logical data model 11

compare logical models to theArcGIS Water model 20

creating 20determining customization

requirements 20

M

MainLine abstract classattributes of 80description of 80

Making folder connections 63Connect to Folder button 63file system-level access 63

Manholedescription 100

Manhole classattributes of 100

Map LIBRARIANimporting data from 22

Maps 12, 19, 22, 63, 64, 66absolute pathname 66custom toolbar 66data 66data frames 66for presentations 19layout 66providing tools 66relative pathnames 66scale-dependent drawing rule

66showing specialized tasks 19spatial bookmarks 66standardized layout 66

Meter. See also WarehouseMeterclass

description 100

Meter classattributes of 100subtypes of

Compound 100Current 100DetectorCheck 100FlowTube 100Flume 100Magnetic 100MagneticOrifice 100ModifiedVenturi 100MultiJet 100OrificePlate 100Pito 100PositiveDisplacement 100Propeller 100Proportional 100Sonic 100Turbine 100Venturi 100Wier 100

Microsoft Repository 11, 21Modeling Our World 14, 16,

17, 20Motor class

attributes of 88Motors

description 88

N

Network connectivity 12Network management 5Network structures

description 97Network types

looped 4radial 4

NetworkStructure classattributes of 98subtypes of

DischargeStructure 97DiversionChamber 97DiversionPoint 97JunctionChamber 97LiftStation 97ProductionWell 97PumpStation 97SplitManhole 97

NetworkStructure class(continued)

subtypes of (continued)StorageBasin 97TideChamber 97TreatmentPlant 97

O

Object inheritance diagram 75Object loader

snapping 59validation rules 59

Object Loader Wizard 59Object Model

associating an interface 27creating a new class 27creating subtypes 27customizing 27defining model components 20extending the model

adding a class 28adding subtypes 33use of subtypes 33with Visio Enterprise 28

modifying with the CASE Tool44, 48

Object models 10Objects

of a utility system 20subtype 23use of subtypes 33

Operations 6linking to data 8

Operations recordsdescription 86

OperationsRecord classattributes of 86

P

Passwords 18, 63Pathnames

absolute 66relative 66

Personal geodatabase 22, 41controlling access 22file system-level security 22

Index.p65 12/05/2001, 2:05 PM118

Index • 119

Personal geodatabase (continued)performance information and

tips 60Physical database model 20PipeBridge 81Pressure sustaining valve 104PressurizedMain

description 81PressurizedMain abstract class


AirRelease 81BlowOff 81Bypass 81ChemicalInjection 81DistributionMain 81Interconnect 81PipeBridge 81SamplingStation 81TransmissionMain 81

Pump 90, 91, 100, 101. See alsoWarehouse Pump class

description 101Pump class


AxialFlow 101Centrifugal 101Jet 101Reciprocating 101Rotary 101Screw 101Turbine 101

R

RDBMS’s SQL 12Regulator

description 94Regulator class

attributes of 94Relationships 10Repository 17. See also Export

UML to the MicrosoftRepository

Rules 10

S

Samples 12layers 12, 18maps 12, 19, 66repositories 41styles 12toolbars 12

Sampling stationdescription 102

SamplingStation classattributes 102

SCADA sensordescription 110

ScadaSensor classattributes of 110

Schema Creation Wizard 11, 17,21, 40

Schema generation 21Services

characteristics 5Sewer and stormwater networks

characteristics 6network assets 6network segmentation 6supporting features 7types 6

Sewer/stormwater object modeldiagram 70

Shapefilesimporting data from 21

Shared folderdata 64layers 64maps 64

Shared folders 12Sharing a geodatabase 12, 18,

22, 63ArcSDE geodatabase 22

connecting to 22password-protected layers 22

create layer files 63create maps 63performance information and

tips 63personal geodatabase 22

Sharing maps 66

Simple featurescustom behavior and network

connectivity 52Spatial operations record

description 110Spatial reference 42, 48SpatialOperationsRecord class


Inspection 110Leak 110Maintenance 110Repair 110

Standby powerdescription 88

StandByPower classattributes of 88

Subtypekeyword 35

Subtype field 34inherited 34

Subtypes 10Surge relief tank

description 89SurgeReliefTank class

attributes of 89System valve

description 102SystemValve. See also

WarehouseSystemValveclass

SystemValve classattributes of 103subtypes of

Ball 102Butterfly 102Cone 102Gate 102Plug 102

T

ThrustProtection classattributes of 113description 113

Tide gatedescription 94

Index.p65 12/05/2001, 2:05 PM119


TideGate classattributes of 94

Tools 18CAD 18digitizing 18editing 18flow-modeling 18trace 12, 18

Trace 12, 18Transmission systems

characteristics of 4TransmissionMain 81

U

UMLdefining objects and models 72exporting to a repository 40

UML modelupdating 62

UML modelingadvantages of 26

UML modeling software 10, 21UndergroundEnclosure class

attributes of 109description 109subtypes of

MeterBox 109ValveVault 109Vault 109

Unified Modeling Language(UML) 13

Username 18, 63Using ArcCatalog 18, 22, 42,

48, 66Using ArcMap 18, 19, 22, 66

V

Valvedescription 102

Valve abstract classattributes of 102

Visio diagrams 20Visio Enterprise 10, 28

W

Warehouse control valvedescription 92

Warehouse hydrantdescription 91

Warehouse meterdescription 90

Warehouse pumpdescription 90

Warehouse system valvedescription 92

WarehouseControlValve classattributes of 92subtypes of

AirControl 92AirGap 92AirRelease 92Altitude 92AtmosphericVacuum 92BackflowControl 92Combination 92DoubleCheck 92PressureVacuum 92ReducedPressureBackflow

92RPZ 92SimpleCheck 92Vacuum 92VacuumBreaker 92VacuumRelease 92

WarehouseEquipment abstractclass

attributes of 89description 89

WarehouseHydrant classattributes of 91

WarehouseMetersubtypes of

Current 90Proportional 90

WarehouseMeter classattributes of 90subtypes of

Compound 90DetectorCheck 90Flume 90Magnetic OrificePlate 90Pito 90

WarehouseMeter class (continued)subtypes of (continued)

PositiveDisplacement 90Sonic 90Venturi 90Weir 90

WarehousePumpsubtypes of

Centrifugal 90Jet 90Reciprocating 90

WarehousePump classattributes of 90subtypes of

AxialFlow 90Rotary 90Screw 90Turbine 90

WarehouseSystemValveattributes of 92

WarehouseSystemValve classattributes of 92subtypes of

Ball 92Butterfly 92Cone 92Gate 92Plug 92

WarehouseValve abstract classattributes of 91description 91

Water distribution object modeldiagram 68

Water structuredescription 111

WaterFacility abstract classattributes of 98description 98

WaterFeature abstract classattributes of 109description 109

WaterLine 28attributes of 78description 78

WaterStructure classattrributes of 111

Web 12, 51, 60Work flow and security 18

Index.p65 12/05/2001, 2:05 PM120

Documents

ArcGIS Data Models: Water Utilities - Esri Supportdownloads2.esri.com/support/datamodels/Water Utilities... · 2003-06-04 · Water Utilities ArcGIS ™ Data Models Water Utilities