Latest Contributions by MikeMillerGIS

‎12-11-2019

The link system is down, we are currently working on it

‎12-11-2019

Gareth, This issue was found internally(so there is no bug number to track it) a few weeks ago. It will be resolved in 2.5/10.8 release.

‎12-05-2019

You need to install the solutions deployment tool - ArcGIS Solutions Deployment Tool | ArcGIS Solutions

‎12-04-2019

Great suggestion. Updated data dict attached

‎12-02-2019

UPDM and the Gas Pipe Utility network configuration was made with material as the Asset Types to build rules to control which types of pipes, fittings, etc can be connected. Do you not require rules by material in your implementation?

‎10-07-2019

You are now required to add the UN layer to the editing map. Details can be found here. Deploy the network editor—ArcGIS Help | ArcGIS Solutions for Electric We forgot to add this note to the release notes.

‎10-03-2019

Are you loading the sample data? We have seen issue with parallel processing. You can set it to 1 in the environment variables of the tool or run this in the python window prior to running apply asset package. arcpy.env.parallelProcessingFactor = 1

‎09-17-2019

IIF was monkeypatched in the msscriptcontrol. I believe you need to do & inside it. I have never tested this. The logic may not work and you might need a second expression statement that fires after this one. Which is <The Edited Field> & [OBJECTID] IIF([SYSTEM]=Potable, "DW" & [OBJECTID], IIF([SYSTEM]=Non-Potable, "RW" & [OBJECTID], IIF([SYSTEM]=Sewer, "SS" & [OBJECTID])))

‎08-28-2019

If you look at the feature classes, can you verify the features where appended? You can try the import association again, you will need to modify the AP_workspace folder that was created. In there, open the main.py and remove calls prior to the import associations call. Using the python command prompt, run that by file.

‎08-28-2019

Could you share the entire message? What version of pro/untools?

‎08-22-2019

David, This is currently not possible. I can log the issue, but we are not really adding new features to the AA at this point, mainly focusing on bug fixes and ensuring it works with future versions of ArcMap

‎07-23-2019

That is correct

‎07-23-2019

Just keep track of your additions. Also, you do not have to update once you settle on a starting point. You can extend your version with our changes if you need them. The models are going to change just like software does and as the software it sits on top of does. Feeder feed feeder: This would be using a step down transformer as controller for a subnetwork. Correct on item 4

‎07-23-2019

I will log an issue to move the Relationship classes into the Feature Dataset. Looks like just an oversight. We would prefer to move the tables into the feature dataset also, but the GDB does not support that at the moment. We do not have a workflow that describes the editing process, but these diagrams describe their use: https://storymaps.arcgis.com/stories/c957d7a091be4b1e942b5c82883f6f66 https://storymaps.arcgis.com/stories/903a7b52bd644b05897395e2ccc00400

‎07-23-2019

Great questions. The next few releases are focusing on the following 1: Extending the sample data to include subnetworks for all tiers and feeder feed feeders in the distribution tier. This will help us round out the rules and ensure we have the categories and other properties set appropriately. 2: Providing the ability to rename key components. We are close to finishing a new exciting capability in the asset package to rename items during application. This could be to simply rename an asset group to a new asset group and all UN properties are shifted to the new name or provide a localization like experience where the model can be converted to another language. 3: Allow deploying a subset of the asset package. The first release will be focused on reducing fields, code values in domains and a few other things, but we want to keep extending it to provide the ability to remove Asset Groups someday. 4: Adding new tables and classes for inspections and other activities. 5: Adding to the list of workflows. We do not plan to change the Asset Group and Asset Types like with did in version 3, but there will be changes as we keep driving the model and gathering feedback from the community. Thank you for your feedback so far and please keep sharing it with us.

Online Status	Offline
Date Last Visited	3 hours ago

My Ideas

Latest Contributions by MikeMillerGIS

Re: Electrical Utility Network Foundation data model diagram

Re: Subnetworks not showing as dirty following edits

Re: Where is the ArcGIS Solutions Button?

Re: Water Distribution Model Data Dictionary

Re: Esri Utility Network Configuration and Data Loading Tools Status

Re: missing Electric Utility Network Layer (id 950) in the latest release of Electric Asset Package release 3.2?

Re: UN MODEL for Electrical

Re: Attribute Assistant

Re: Apply an asset package error message

Re: Apply an asset package error message

Re: If you’re using the Attribute Assistant, we need your help!

Re: Electric Utility Network Foundation related tables not part the feature dataset

Re: Utility Network Foundation Roadmap

Re: Electric Utility Network Foundation related tables not part the feature dataset

Re: Utility Network Foundation Roadmap

Re: Asset Package - Change Asset Type Domain for a...

Re: Pipeline Isolation Subnetwork Confusion

Re: Published UN webmap showing coded domain value...

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

Re: Water UN Data Cleanup

European Utility Network Community (UNC)