Latest Contributions by RobertKrisher

Those images look like elbows in a junction box. So, if that's what your engineer is interested in modeled you would map them to the appropriate asset type in the medium/low voltage elbow asset group. ... View more

@TóthRóbert  The visible option is used when calculating the association status of a feature or object. Specifically, is used to differentiate visible or hidden content. While this works great with features where we can use this status in display filters to hide content in your containers, as you noted it has much less meaning when applied to non-spatial objects. However, as you noted, you could use this value in network diagrams if you wanted to create some special diagrams that leveraged this value to hide non-spatial objects in your diagrams. ... View more

You can do this through several parameters on your reader (Working with Geodatabase Domains: Writing A Coded Domain (safe.com)). Asset Groups are actually subtypes, so if you make your reader resolve subtypes you will see both the code and the description. Likewise, Asset Types are represented as coded value domains on the asset type field, so if you set your reader to resolve domains you will see both the code and the description. ... View more

Your steps are correct, but there appears to be a problem with the isolation and system subnetwork fields. In those subnetwork name fields must be non-nullable, and they are in the default model. If you made any changes (or dropped and re-added these fields) then that may have set them to be nullable. The easiest way to correct the issue in the asset package is to: create a copy of the table delete all the rows out of the copy set the subnetwork name fields in the copy to be non-nullable (this can only be done on an empty table) append the rows from the original table into the copy delete the original table, and rename the copy table to match the original table ... View more

@Angiex__1 I recommend you tackle this problem in two different ways: The first and most important step to solving this problem, and it's a common problem, is to find yourself a subject matter expert (SME). That is to say that you should find someone in your organization who understands all the terminology in that model and who is familiar with your system (both the GIS and the real-world) and sit down with them and have them help you pick the right names for everything. If you are friends with an engineer or someone who spends a lot of time in the field, they are often an excellent resource for these kinds of exercises. The online data dictionaries also have descriptions for most of their asset groups and asset types, but since every utility company uses their own terminology and slang for their equipment its often difficult to parse that out into some of the industry standard classifications found in that model. Second, let the model guide you. There are rules defined for everything, so if you look at the rules and look at your data (and how you've classified things) and the vast majority of your features don't match, you may have picked the wrong asset group/type. When you're ready to test your mappings I recommend you do a quick prototype of them (using the approach outlined in this presentation from IMGIS). Just map your asset groups and asset types and see how many errors you get. If you get thousands of errors saying that there aren't any rules for the features you've mapped, then you should go back to your SME and see whether the problem is with your data, the mappings, or maybe you just have some weird configurations in your data that you need to account for with additional rules. Finally, if you get stumped this community is a great resource to get answers. You'll find lots of examples in this forum where people have asked how others are modelling specific types of equipment (meters in particular), so if you get stuck and don't see your question already on this forum then start your own thread! ... View more