Latest Contributions by JohnAlsup

Hi Mike, it sounds like the Deploy tool may have encountered an issue but did not report an error on changing the datasource. So, did you verify that all the source layers in the map used for publishing were pointing to the correct data source?  Next, did you use the "Electric Network Foundation" map to publish with?  If so, were there any modifications to it? ... View more

Hi Eddy the attributes Pull Through, J-Bars and Unibar can be either added to the structurejunction class or set the alias for an existing field that is not used for junction boxes and assign a domain to it with the appropriate values.  I will be looking at adding these to our base model next week and can email you with how we will do this in the next release of the model. Load Break is a bit more complicated.  So, we have designed our electric data model to allow for traces that can identify load breaking equipment quickly.  For example, return the first load break devices upstream of my point/position.  We do this by assigning the "E:Load Break" network category to the specific asset types in the ElectricDevice or ElectricJunction feature classes.  Given this is a structure, that won't work.  But, if you don't care about these cabinet's being used in traces to find the closest upstream load breaking device, then you can just use an attribute.  But, if you want to find the first upstream load breaking device, we need a feature in the elecricdevice or electricjunction class.  In the Electric Model, notice that we have features that go inside the cabinet that are in the electric device class the Medium Voltage Elbow/Load Break Feed Thru,which would be like a G&W "Multiple Point Junction"  https://www.gwelectric.com/webfoo/wp-content/uploads/JBAR.pdf  ... View more

Hi Eddy. This is a link to the data dictionary for the electric model that may help you. https://solutions.arcgis.com/electric/help/electric-utility-network-foundation/DataDictionary/DataDictionary/  ... View more

Hi Eddy.  What version of the model are you referring to? Also, in the Utility Network, in order to not add potentially hundreds of attributes that are only used for specific asset groups, we use a methodology of "field reuse" where a field is used as X for subtype 1 and as Y for subtype 2.  Since you should only access the data via service and not directly at the database level, the presentation of this can be controlled to display the correct information to the end user (look at the Editor Map we provide). In our latest version of the Electric Model Low Voltage Lighting uses the attribute powermeasure for light size in Watts with the domain "Electric_Light_Watts" assigned to the attribute at the subtype level.  Also, the attribute remotecontrolindicator (looking at it from a database view) is used for Bulb Type and has the domain "Electric_Low_Voltage_Bulb_Type" assigned to it at the subtype level for Low Voltage Lighting.  I would recommend looking at the "Electric Network Editor" map to better understand how field/attributes are used.  Looking at the "Electric Utility Network" map or at the database level will lead to misunderstandings of how attribute are used for specific subtypes/asset groups. ... View more

Hi Damien. The UN and the model we have provided support multiple levels of detail.  The diagrams we have provided thus far, so the maximum detail.  We are working to document multiple levels of detail and the benefits of each level.  Let's take the Tap example.  If you are using esri's Electric Foundation model, no reconfiguration is required to replace the Three Single Phase Taps with a Single Tap.  It all just works out of the box.  Also, you can use a mix of Single Phase Taps and Three Phase taps, no configuration modifications required.   ... View more

esri provides a base model for electric that covers from generation to low voltage services and all the equipment inbetween, including solar, wind and other generation forms and includes the equipment specific to solar, like inverters. The Asset Package rename option can be used to change the names of elements to your local terms as longs as the device is used the same way, for example a Load Breaking device.  The model has been designed to leverage all the capabilities of the utility network and includes extensive documentation and diagrams on proper modeling techniques.  The model was designed to support Balanced and Unbalanced Polyphase systems, multiple frequency systems, support engineering analysis and multiple switching plans. Electric Utility Network Foundation | ArcGIS Solutions for Electric  ... View more

There is sample data using the esri Electric Foundation Model for the Utility Network.  You can find it on the Utility Solutions web site ArcGIS Solutions Deployment Tool | ArcGIS Solutions .  Download the Solutions Deployment tool and it will allow you to load the Sample Data ... View more

Currently the only other tools available are from Business Partners like SSP and RamTech.  In October a new Data Loading Tool should be released by Esri solutions to help perform a simple migration of data from source to target.   ... View more

Hi Eddy. The document you are referring to is specifically for the FME for Electric Data migration to the Utility Network.  There are multiple migration tools and methods that can be employed which have different requirements.  One of the reasons the FME Workbench requires the Unit table is that these Unit records will be converted in to features (devices) and yes, one record per phase is required for devices like Transformers (Delta connected Transformers would have two phases), Fuses, Capacitors and Non-Gang operable switches. ... View more

So, let's take the field addpowerrating in the ElectricDevice feature class, as you have shown.  In the field alias, we comma delimited the alias description with a list of Asset Groups (subtypes).  Now, in the editing map we have provided with the asset package, we use subtype layers.  For each sublayer in the subtype layer, we define the visible attributes and the alias for each attribute.  In this example, the "addpowerrating" attribute would be called "Active Generation" for asset group sublayer "High Voltage Generation", KVAR for asset group sublayers "High Voltage Power Factor Correcting", "Medium Voltage Power Factor Correcting" and "Low Voltage Power Factor Correcting".   Why did we do this?  First, we needed to limit the number of fields being returned from the service (not the database, you shouldn't even think in database terms anymore). Next, a field like KVAR would only apply to capacitors, transformers don't have a KVAR rating, but they do have a KVA rating, so why not use the same field, but use it differently based on asset group (subtype).  This significantly reduces the number of attributes for the class, improving transmission times to the client.   ... View more

The domain you pointed out is correct.  The domain codes are the diameter in inches.  The domain description is the gauge.  Why did we do this?  So that the diameter can be easily used in calculations without having to perform a domain lookup.  For example, a voltage drop uses the resistance of the wire and the diameter of the wire.    ... View more

We have placed the diagrams on a public GITHUB site, https://github.com/Esri/utility-network-modeling.  If you have a GITHUB login, you should be able to access them.   These are not complete yet and we are adding to them over time.  If there are specific diagrams you cannot locate and would like to see, please enter an issue in the GITHUB Repository and we will add it to our list to create. ... View more

my first question is what are you wanting to see from SCADA in the GIS and how do you want to use this information? If just visualizing the volume of water at a point, then I would create an independent point feature class that you would place or create a feature at the location of the SCADA device and then export readings from your SCADA to this point feature class, updating the attribute that contains the reading.  This feature class would not be versioned.  If you are wanting to see the status of devices (valves, etc) that affect flow and you want this information in the utility network, you could create an app that pushes information from the SCADA to the utility network service using the Rest End Point to update the device status attribute in the default version and validate the update.  If you are using a Geometric Network, you would need to writing a similar utility in ArcObjects or python to load the updated data to the feature.   If updating the Geometric Network or Utility Network with information frequently, many features per minute, you could impact performance.  There is a big difference between sensor data like volume of water vs device status information like valve open. ... View more

currently the FME Workbench for electric must move features in some cases to properly build out the assemblies and other complex combinations of features.  The current input is the number of units in decimals and consequently will not work with un-projected data.  We will evaluate how difficult it would be to implement this, but we were told that most (99.9%) of customers would have projected data for the utility data.  Sounds like either you got the one or that information was incorrect.  Ed, how many customers would you be aware of or estimate have non-projected utility data? ... View more