Operational data for Sewer and Storm Events

All,

I am working on some data model updates for the Local Government Information Model and wanted to get some feedback from the community.  We currently model basement backups in the ssBackupEvent Feature Class and an overflowing manholes in the ssOverflowEvent Feature Class.  We want to provide additional layers for other events, but before we create a series of additional layers, I wanted to asked if it is better to model all events like these in a single layer with a domain for the event type or as individual layers. Below is the list of events we want to add to the LGIM, to provide even more operational data.  Post a comment and let us know what you think is the best way to model this information.

Overland Flooding

Street Flooding

Drainage Issue/Backup

Catchbasin Overflowing

Flood Debris

Catchbasin Clogged

Manhole Cover Off

Evidence of Surface Flooding

This entry was posted in Water Utilities. Bookmark the permalink.

Leave a Reply

3 Comments

  1. monodh says:

    I work for a small municipality, and we are still a bit new to the local government model (as we are trying to move that way slowly…). However with regards to water or sewer back up events and overflows, we treat them as one layer and within the layer there is a field to identify the type. For example, in our case it’s called a “water system failure event”, and then there are many different types from there. I think that often those events/ problems are linked (like a back up, blockage causes a flood, so it might not be two seperate events), thus I htink have it as one layer with a domain for the event type.
    I am not an expert on this though, so good luck!
    Thanks :)

  2. carrierkh says:

    I like the idea for one layer but what about possibly using subtypes in conjunction with domains, so based on the chosen subtype you can have different domains based on the subtype chosen just in case the values vary slightly from one subtype to another?

  3. Mike Miller says:

    Thanks for the comments. I like the idea of a Failure Event or maybe it is just Event. Then an Event Type field which set different domain based on subtype. Let me play around with it and see if it works. My only fear with one layer is if there is unique data that different events need to capture and store.