A START OF A BEAUTIFUL A START OF A BEAUTIFUL “RELATIONSHIP”“RELATIONSHIP”

Mike Morris, GISPMike Morris, GISPRick Ehlin, GISPRick Ehlin, GISP

City of Noblesville UtilityCity of Noblesville UtilityIGIC Conference 2011IGIC Conference 2011

Let’s Fix Your RelationshipLet’s Fix Your Relationship

City of NoblesvilleCity of Noblesville

Located in Hamilton CountyLocated in Hamilton County Population of 51,969 (2010)Population of 51,969 (2010) Approximately 33 sq mi.Approximately 33 sq mi. Noblesville is in the No. 10 spot in the book, “Best Places to Raise Your Family: The Top 100 Noblesville is in the No. 10 spot in the book, “Best Places to Raise Your Family: The Top 100

Affordable Communities in the U.S.”Affordable Communities in the U.S.”

Noblesville UtilitiesNoblesville Utilities

Class 4 Wastewater UtilityClass 4 Wastewater Utility Approx. 16,400 CustomersApprox. 16,400 Customers 453 Miles of Sanitary and Storm Pipe453 Miles of Sanitary and Storm Pipe 5 million gallons per day5 million gallons per day Activated Sludge PlantActivated Sludge Plant 23 Lift Stations23 Lift Stations

CITYWORKS CITYWORKS by Aztecaby Azteca

Cityworks is an Enterprise GIS- based Cityworks is an Enterprise GIS- based Asset Management System.Asset Management System.

It has the ability to do the following:It has the ability to do the following:• Work Orders (address or feature specific)Work Orders (address or feature specific)• Service Requests (address or feature specific)Service Requests (address or feature specific)• InspectionsInspections• Storeroom Storeroom • Manage equipment, contractors, employees, Manage equipment, contractors, employees,

etc.etc.

WHY RELATIONSHIP TABLES?WHY RELATIONSHIP TABLES?

Modify existing GIS LayersModify existing GIS Layers

Add fields (AssetID) to all layersAdd fields (AssetID) to all layers Breakup layers into individual layersBreakup layers into individual layers

• Sanitary line file had to be split into Sanitary line file had to be split into gravity lines, force mains, interceptor, gravity lines, force mains, interceptor, etc.etc.

• Storm structures “Other” file needed to Storm structures “Other” file needed to be broken up into flapgate, cleanout, be broken up into flapgate, cleanout, etc.etc.

AssetID field is the field Cityworks uses to link AssetID field is the field Cityworks uses to link assets (features) to work orders.assets (features) to work orders.

Create new GIS layersCreate new GIS layers

Plant BuildingsPlant Buildings Fences for plant and lift stationsFences for plant and lift stations

Attribute fields createdAttribute fields created• Bldg_Name and AssetID most importantBldg_Name and AssetID most important• Important to get naming correctImportant to get naming correct

Convert existing Access tables to Convert existing Access tables to ExcelExcel

Needed to bring data not currently in Needed to bring data not currently in GIS in geodatabase tables.GIS in geodatabase tables.• PumpsPumps• HVACHVAC• FansFans• ValvesValves

Access database used by plant Access database used by plant operatorsoperators

Needed to convert to excelNeeded to convert to excel

Access to ExcelAccess to Excel

All assets in one access databaseAll assets in one access database Data was very inconsistentData was very inconsistent Assets needed to be split up into individual Assets needed to be split up into individual

typestypes

The naming convention used for the AssetID field was to The naming convention used for the AssetID field was to start with a building code HW (headworks), EF (effluent start with a building code HW (headworks), EF (effluent pump station)….the second part was asset type HVAC, AC pump station)….the second part was asset type HVAC, AC (air compressor), PUMP…the final part was a description of (air compressor), PUMP…the final part was a description of equipment type EFFL1 (effluent pump motor #1), RAW4 equipment type EFFL1 (effluent pump motor #1), RAW4 (raw sewage pump #4). The name that is in the (raw sewage pump #4). The name that is in the LocationID field is simply the AssetID for our Maint_Building LocationID field is simply the AssetID for our Maint_Building layer.layer.

The RelateID is the AssetID of the “Parent” asset.The RelateID is the AssetID of the “Parent” asset.

The “Parent” and “child” analogy was used to The “Parent” and “child” analogy was used to clarify relationships between two assets.clarify relationships between two assets.

In Arc Catalog right click on the file geodatabase In Arc Catalog right click on the file geodatabase (.gdb) you want the new table to be located in (.gdb) you want the new table to be located in and go to new and go to new Table. Once you select this a Table. Once you select this a new box will open up…the naming convention we new box will open up…the naming convention we used to this was maint_air_compressor. used to this was maint_air_compressor.

Create .gdb table fieldsCreate .gdb table fields

Load data from excel into .gdb Load data from excel into .gdb tabletable

Right click on the .gdb table you want to Right click on the .gdb table you want to load the data into. Select Load load the data into. Select Load Load Load Data.Data.

Creating a Relationship TableCreating a Relationship Table

Can only be done in ArcInfo or Can only be done in ArcInfo or ArcEditorArcEditor

ESRI help menu is great sourceESRI help menu is great source

In ArcCatalog, right- click on the In ArcCatalog, right- click on the geodatabase that contains your tablesgeodatabase that contains your tables

Go to NewGo to New Click Relationship ClassClick Relationship Class

Name your Name your relationship classrelationship class

Select the table or Select the table or feature class that is feature class that is the origin (parent)the origin (parent)

Select the Select the destination table or destination table or feature class feature class (child)(child)

Select the type of Select the type of relationshiprelationship

We used a Simple We used a Simple (peer to peer) (peer to peer) relationshiprelationship

ESRI gives good ESRI gives good definition of bothdefinition of both

Label the Label the relationship from relationship from the parent table to the parent table to the child tablethe child table

Label the Label the relationship from relationship from the child table to the child table to the parent tablethe parent table

CardinalityCardinality

One-to-one: One parent object can relate to only One-to-one: One parent object can relate to only one child object. For example a parcel can only one child object. For example a parcel can only have one legal descriptionhave one legal description

One-to-many: One parent object can relate to One-to-many: One parent object can relate to multiple child objects. For example a building multiple child objects. For example a building can have multiple pumpscan have multiple pumps

Many-to-many: One parent object can relate to Many-to-many: One parent object can relate to multiple child objects as well as one child object multiple child objects as well as one child object can relate to multiple parent objects. For can relate to multiple parent objects. For example a property can have many owners and example a property can have many owners and an owner can own many properties. an owner can own many properties.

Select the primary Select the primary field for the parent field for the parent tabletable

Select the foreign Select the foreign key field for the key field for the child tablechild table

Examples of relationshipsExamples of relationships

Pump (child) is related to the building Pump (child) is related to the building (parent)(parent)

Motor (child) is related to a pump (child/ Motor (child) is related to a pump (child/ parent) which is related to a building parent) which is related to a building (parent)(parent)