|
POST
|
@Paul_Lalancette Curious, I didn't think you could create a terminal configuration without any valid paths, I'll put that on my list of things to try out tomorrow. You can't modify a terminal configuration once created, and you can't change an asset type's terminal configuration once it has had a configuration. Unfortunately, this doesn't leave you with a lot of options, the easiest of which would be to export your utility network back to an asset package, put the appropriate configuration back into place in the asset package, and to re-deploy your utility network. It looks like you're still prototyping your utility network, so I hope this isn't too much of an inconvenience.
... View more
02-08-2024
07:20 PM
|
0
|
0
|
3237
|
|
POST
|
@MikeMillerGIS ah that's right. So you would create separate winding junction objects contained in the transformer and set up each winding junction object as a controller for the corresponding tier.
... View more
02-08-2024
09:23 AM
|
0
|
0
|
2582
|
|
POST
|
In this scenario your device (or junction object) would need to have three terminals: one for the primary side (the upstream terminal), one terminal for the secondary side, and one terminal for the tertiary side. You would then need to configure that transformer's asset type to be a subnetwork controller for both the distribution tier and secondary tier. The "Station Three Winding - HV->MV-LV" in the latest electric model is pretty close to having this configuration, it just hasn't been configured to be a subnetwork controller for any tiers (and requires the subnetwork controller category). Once you've configured the transformer for this you will see both terminals in the modify subnetwork controller dialog. You would select the distribution tier and secondary terminal to create your MV subnetwork, then you would select your secondary tier and tertiary terminal to create your LV subnetwork.
... View more
02-08-2024
06:55 AM
|
0
|
3
|
2628
|
|
POST
|
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
02-08-2024
06:31 AM
|
2
|
2
|
2638
|
|
POST
|
Because the asset group spans multiple classes there isn't a domain that can be used for this, while you could use the asset group codes directly this may not work well because you may use the same asset group code for different layers. Another option you should consider is making use of network categories to allow you to precisely specify the asset groups/types you want to use for your condition.
... View more
02-07-2024
03:16 PM
|
1
|
0
|
1068
|
|
POST
|
@Paul_Lalancette is the subnetwork name populated on the device? if so, the device is acting as a barrier to the subnetwork. check its attributes and any terminal connections to determine why its stopping tracing (is it active? is it closed? does it have an activate volume?). If the device isn't part of the subnetwork, then your culprit is likely the stormwater line itself. You'll want to look at the attributes and terminal connections of the line to see why its stopping the trace.
... View more
02-07-2024
09:29 AM
|
0
|
1
|
3307
|
|
POST
|
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
02-07-2024
07:35 AM
|
1
|
3
|
2026
|
|
POST
|
Darrin, Here it is: Additional Tools for the Utility Network - Esri Videos: GIS, Events, ArcGIS Products & Industries.
... View more
02-07-2024
07:22 AM
|
1
|
0
|
2042
|
|
POST
|
@DarrinBlaisdell1 This appears to be a duplicate of your previous post (Staging Asset Package to Utility Network leaves da... - Esri Community)
... View more
02-07-2024
06:33 AM
|
1
|
0
|
987
|
|
POST
|
Can you share the logs from the tool? Did you just stage the utility network, or did you also apply the asset package? If your asset package didn't pass validation the tools will usually throw an error and not load data into the asset package, although there will still be some basic schema in the database. For deep diving into issues, you can start to look at the logs, scripts, and files in the AP_Workspace folder that is generated every time you apply an asset package. The first 19 minutes of this presentation from IMGIS describe the asset package tools, with the last half of that focusing on some of the more technical pieces like the AP_Workspace.
... View more
02-07-2024
06:30 AM
|
1
|
2
|
2050
|
|
POST
|
@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
02-02-2024
06:50 AM
|
5
|
1
|
5128
|
|
POST
|
@CodyPatterson yep, those are the archiving fields. So instead of using the tools to unregister the datasets as versioned you will use the tools that @MarceloMarques mentions.
... View more
01-22-2024
09:02 AM
|
0
|
0
|
4802
|
|
POST
|
@CodyPatterson In a perfect world you could restore from backup to before you enabled versioning. Do not attempt to manually remove the columns from the database, since they will cause the database to become out of sync with the system tables in the geodatabse. Instead, you can unregister the dataset(s) as versioned using the same tools you use to register the database as versioned. This will allow the system to remove all the necessary columns, remove any versioning history, and update the corresponding system tables to acknowledge that the data is no longer versioned.
... View more
01-22-2024
08:28 AM
|
2
|
7
|
4834
|
|
POST
|
You can find a discussion and presentations from IMGIS on this topic and the utility network on this thread: Solved: UN for Treatment Plants - Esri Community There was a presentation of BIM and Vertical assets from MMSD at the water user groups meeting last year: (1) 2023 Esri UC Water Utilities Meetup - Esri Community
... View more
01-22-2024
08:25 AM
|
0
|
0
|
1750
|
|
POST
|
@NadiaAlami One other thing to keep an eye out for is whether there are any errors associated with the junction feature. If there is an error with the junction feature (stacked point, invalid terminal configuration, etc) then it can't connect to either line. This leaves the two lines attempting to connect directly to each other, which produces a type 10 error.
... View more
01-22-2024
06:50 AM
|
1
|
1
|
3112
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 hours ago | |
| 1 | 9 hours ago | |
| 1 | yesterday | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
6 hours ago
|