Latest Contributions by RobertKrisher

Don't worry about digitized line direction for your water distribution data because flow is derived from your water/pressure sources and these systems are so looped that almost all your flow is indeterminate (so digitized direction is meaningless). For terminal assignments, you just need to make sure you don't have more than one line assigned to the same terminal, and that your upstream terminal always point towards your pressure/water source. If terminals are not properly set you will not get topology errors, you will get subnetwork errors (because pressure zones are interconnected when they aren't designed to be). Sewer/stormwater is a completely different situation. Because these systems are not heavily looped and rely on gravity, customers have historically relied on the digitized direction of lines to manage flow. We will allow you to drive analysis using sources and sinks, but in 3.3 we also introduced an option to trace upstream/downstream using digitized line direction. By default, the utility network doesn't rely on the digitized direction for upstream/downstream analysis, instead it uses sources and sinks. You can deep dive into water modeling on the Learn ArcGIS Utility Network for Water Utilities learning path. ... View more

If your class has subtypes, make sure that you assign the domain to the appropriate subtype as well. The easiest way to handle this is to use the Assign Domain to Field gp tool, since it lets you select all the subtypes at once. ... View more

The relationship isn't strictly necessary, as long as you as you maintain primary/foreign keys. I also discuss the perils of joining your CIS data with your GIS features, exercise extreme caution with this because once you calculate it you need to maintain it (which doesn't work well for large customer bases). A dynamic lookup approach on a well-indexed, non-versioned table is more sustainable for a large dataset. The beauty of popups is that they are configured at the subtype layer in maps, and that they are different for every map. You would only configure the customer information popup on something like a transformer (electric) or service point (electric, gas, water), and not on something like a switch (electric) or valve (gas, water). ... View more

When you trace the subnetwork, how many features are selected? If it's just the controller then you need to review the connections to your controller and your network attributes to see why the trace is stopping. If your tier has phase propagation and your device doesn't have phase, then none of the features downstream of the controller will become energized. If your controller, or what it's connected to, match one or more of your condition barriers (device is open, lifecyclestatus isn't 'in service' or 'proposed remove', etc) then the trace will stop on those features. ... View more

Identifying an asset as critical is typically done by either having an attribute that idetnifyies the feature as critical, or it is known that certain pieces of equipment/asset types (system valves, pumps, etc) are critical to the network infrastructure. Adding a field to the model and populating it during data conversion is a good approach. If you needed to take this attribute to the next level and use this attribute for some more advanced forms of analysis like identifying critical valves to perform isolation or counting the number of critical devices in a pressure zone, you could also configure a network attribute for critical assets and assign this field from your various classes to be a network attribute. ... View more