Latest Contributions by JohnAlsup

‎04-15-2024

Is this a partitioned domain network? Is this an Electric domain network?

‎03-21-2024

The Device status of open or closed on a subnetwork controller feature has no impact for what is downstream of it, as the subnetwork starts at the downstream terminal. Open or Closed only impact the path through the device.

‎03-18-2024

When we changed the Lifecyle status, I would not advise adding any values to it. I would add needed values to the Construction Status domain. This will keep the lifecycle status field in the network index. Adding values to it will probably end up moving it out of line.

‎03-18-2024

As with any change to a model, it could impact your implementation. Some changes are more important than others. In this case the Lifecycle Status and Construction Status changes are significant to make those changes. But, if those are the only changes from the model V2 that you feel are important enough to include, you could just add those changes.

‎03-18-2024

Hi Jugen. Feel free to keep asking questions. It helps me add to our documentation. Why have a Separate Asset Groups for each Voltage Level of Service? First, is cartoghraphic. In Most cases, you don't want to draw High Voltage Service when you are zoomed to a scale that draws the majority of the Transmission or Subtransmission system. You would only want to display services when zoomed in to a large scale. The same would apply to the other voltage classes as well. Why not one Service asset group? I typically would not want to see Low Voltage Services if I am only interested in High or Medium Voltage classes of service. Also, by using a separate asset group, you can uncheck or check the display very quickly to make them visible or not visible. We try to a void using an extra attribute for rendering due to the expense. Also, I can use categories at the asset type level. So, If I wanted a summary of the kM of Circuit/Subnetwork and wanted to exclude services, I can use a network category to accomplish that. And because Network Categories use Asset Group and Asset Type, which are imbedded in the network index, this yields the best performance.

‎03-15-2024

There are many different names for the same equipment, sometimes the name differences are not just language, but tradition. Grounding wires in Transmission are also called Static Wires or Shield Wires. They are all the same thing. That's why we support renaming asset groups and asset types via the D_Rename table during apply. In this case, the wire you are referring to we have called the asset group for this High Voltage Static Wire found in the Electric Line class. We also duplicated this in the structure line class as asset group Static Wire. They are used basically the same way. As for communications, you can apply the Communications asset package on top of the Electric Foundation, just use the Single Cable configuration in communications. The just add a few rules to allow the Static Wire to contain Strands and a few other rules.

‎03-14-2024

yes, you could go in to production with creating the associations between poles and equipment. However, you could also use a tool found in the Utility Network Package toolbox called Create Utility Network Associations. This will create the association between existing poles and any equipment found close to it.

‎03-13-2024

That diagram is way out of date. You are correct, there is no Structure Line asset group or asset type called Duct. Ducts are in the StructureEdgeObject class.

‎03-12-2024

In our Electric Foundation model, we dropped the ElectricDevice Unit table several years ago, when non-spatial support was released with the Utility Network. There are several draw backs to a related table. 1) Phase will not be maintained by the system 2) These related objects will not be returned in any trace. 3) These related objects will not be included in an export subnetwork 4) These units cannot be used in any network summaries If you don't care about any of the above, then yes you could use a related table. However, you will have to include the related table in the publishing map.

‎03-08-2024

you can certainly add the field, but keep in mind that adding a lot of fields could affect editing performance. Also, are you going to use this field in trace summaries or trace filters, if so it will need to be a network attribute.

‎03-07-2024

The value in the field ratedpower is relative to the subtype/asset group. For asset group MV Transformer, ratepower is volt amps or VA. The domain description may say kVA, but the value is in the least common unit, which is volt amps.

‎03-04-2024

If you look at the fields defined in the editor map, the field designtype is aliased as Fuel Type. You could use the field offpeakload and alias it as "Fuel Quantity" and assign it a range domain. This way you avoid adding extra fields. Or add a field and assign it a range domain.

‎03-04-2024

can you provide the full asset package?

‎02-26-2024

I would also pay attention to the codes you would use for asset types and where possible do not use an existing asset type code that has a different description. Yes, Asset Type codes are specific to each asset group, but when viewing the data in a non-subtype group layer it can get a little confusing to the user.

‎02-20-2024

Hi @RobertKrisher , yes you would need to use code in the SDK similar to ProSnippets Geodatabase · Esri/arcgis-pro-sdk Wiki · GitHub to get the domain assigned to the subtype (asset group) and then you may need to evaluate the asset type if you are using a combined voltage field. As there is no phase to phase voltage to a single phase line. This is why in our Electric Foundation model we provide two fields, one for phase to phase voltage and another for phase to neutral voltage.

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by JohnAlsup

Re: How to solve this issue with the multiple subnetwork controllers

Re: Multiple Subnetwork Controllers Error

Re: Questions about modifying EUNF v1

Re: Questions about modifying EUNF v1

Re: Questions on Electric Utility Network Foundation Solution

Re: Questions on Electric Utility Network Foundation Solution

Re: Are Attachments to Poles a necessity in an Electric Utility Network?

Re: Structure Line, Asset group electric duct?

Re: Electric Device Unit Table use case

Re: Electric - Electric Device, Asset Group Low Voltage Generation, field "Rated Power"

Re: Electric - Electric Device, Asset Group Low Voltage Generation, field "Rated Power"

Re: Field for "Fuel Capacity" in electric device, low voltage generation, Generator LV

Re: D_Rename faulty application on given names

Re: Adding asset types after migration

Re: How to read the units of the attribute value from the table

Re: 14 Million Associations - Best way to load to ...

Re: Migrating Pole–Conductor Relationships to Stru...

Re: Migrating Pole–Conductor Relationships to Stru...

Re: Migrating UN from one geodatabase to another g...

Re: Subset of Data to UN

Electric Generation and Transmission

European Utility Network Community (UNC)