Latest Contributions by RobertKrisher

For medium and large sized utilities a lot of this detail is stored and maintained inside external asset management systems (Cityworks, SAP, Maximo, and WAM are the ones I've seen the most).  Related data you're going to be using in things like collector is going to be captured in related tables (the example packages have inspections done this way).  Other misc related data can be stored in flat tables and then either related or joined to the source data as needed.  I wouldn't recommend having these joins and relates in your day-to-day editing displays since they'll impact performance, but having specific views that pull in several aspects of this data at a time is pretty typical. ... View more

I'd recommend take a look at the different types of input connectors ( Input connectors—Real-time Data Feeds and Sensors (10.6) | ArcGIS Enterprise  ) that GeoEvent server offers.  These can allow you to pull data from other systems using flat files, web calls, and many other methods.  It sounds like you're trying to extract information from some kind of SCADA system, depending on the software being used to store the data you may be able to use certain apis or products to accomplish this.  As an example, if the data is being stored in OSIsoft's PI Historian, they have a product that allows you to publish real time feature layers from your SCADA data that can be read directly by the GIS. ... View more

When you first apply the asset package it should also create all of database sequences, even if you don't load the data.  I'd recommend you either run the database sequence tool ( Create Database Sequence—Data Management toolbox | ArcGIS Desktop  ) and create the "WaterDevice_10_seq" that this expression is expecting.  If that doesn't work you can always identify and disable any attribute rules that are making calls to database sequences using the disable attribute rules tool ( Disable Attribute Rules—Data Management toolbox | ArcGIS Desktop  ). Hope that help! ... View more

Kylie - I'll be attending the Esri UC if you want to have a follow up conversation about this. My area of interest is in the Utility space where we're dealing with the constraints imposed by Branch versioning feature services.  In terms of editing, one of the biggest constraints around this is that any versions (and therefore edits) created against a given feature service can only be seen within that feature service.  So if I set up a separate feature service for Collector (or web editors) that only exposes a subset of the data to my editors, then when the data is being reviewed / cleaned for posting the reviewer will be limited to seeing the same amount of data. This becomes incredibly important when you have field personnel collecting a subset of required information and require back office personnel to do a lot of the heavy lifting to get the data prepared.  The way I handle this right now is by just using client side configuration to use settings on the layers (definition queries, field visibility, field highlighting, etc) to control these behavior.  The challenge with the client-side constraints is that they are easily bypassed by advanced or malicious users.  By enforcing these constraints at a service level I am able to safeguard against this. ... View more

Excellent!  Since you're already using a topology builder that gets you half the way there, just find all the regulators with a pressure differential between their high side and low side and set terminals accordingly.  This solution works for simple regulator stations with a single regulator, but for situations where there are multiple regulators working in parallel and/or series the logic gets increasingly complicated. ... View more

While I love the idea of using hosted feature layer views the limitation of only being able to use them on hosted feature layers definitely limits how I can use this right now.  Any idea on when / if there will be support for something like this with feature services? ... View more

While the workbench either shows how or allows you to extrapolate how to do the majority of the conversion, one of the biggest items not shown is how to derive the subnetwork controllers for systems and pressure zones.  This is problematic for a few reasons. Te biggest issue is that this means that all the station regulators in your model will create three ambiguous connectivity errors (type 9, more than one rule exists). In order to resolve this error you need to properly identify associate the inlet and outlet terminals with their corresponding mains, typically inferred by a pressure differential between the mains on a regulator but in cases where there are two (or more) regulators working in a station only the low-side regulators will have a pressure differential. Once the inlet/outlet associations for each regulator have been defined each downstream regulator must be assigned a subnetwork named based off of all the other regulators it is connected with for the pressure system. I've typically relied on python scripts to do this after-the-fact, but given that without the terminal associations most networks won't build I would have expected to see it included in the workbench. ... View more

Rajesh,   To be clear, I don't work for or represent Esri with anything I do.  I'm just another GIS developer dealing with a lot of the same questions right now.  I would recommend you reach out to Esri about schematics, I haven't heard about any tools for converting schematics into diagrams. ... View more

Rajesh,   That's a great question for you to take to your Esri representative.  Because getting from your current model to the new telco model will require performing a data conversion you could begin putting this on your road map.  If you wanted to be an early adopter you could begin by standing up an environment to get familiar with one of the models that has been released (electric, water, or gas) along with the tools and workflows provided by the application.  If you were to start standing up a sandbox now that would give you approximately one year to get familiar with the Utility Network and begin planning for how you will adopt it going forward. ... View more

Good news / bad news on this one.  The bad news is that (as you know) POWER BI only supports lat/long.  The good news is that if you can convince your GIS guy to add columns to your table that have those values you can pull them in via sql.  Unfortunately Sql server doesn't have a way to do this on the fly via a query (see thread here: https://community.esri.com/thread/122469 ).  But your GIS guy should be able to whip up a python script that could recalculate these values periodicaly. One additional note, it looks like you're hitting whats know in SDE as the 'base table', you should talk to your GIS guy to make sure that you're querying the 'versioned views' for the table, that way you're always getting the most up to date version of the data. ... View more

Esri just posted a blog about how this feature was added ( https://www.esri.com/arcgis-blog/products/maps-power-bi/mapping/whats-new-in-arcgis-maps-for-power-bi-may-update/  ). ... View more

If you search for untools and nothing shows up, hit the refresh button and try searching again.  I run into that issue pretty frequently when setting up a new machine to do UN work.   Fortunately Esri documented this as a 'note' in their steps 😃 ... View more

Ed,  Did you bounce Pro after closing the map?  With the new architecture of pro (64-bit asynchronous) I've often found that locks can be pretty sticky and the only way to clear them is to bounce the whole application.  Also, if anything goes wrong while standing up an asset package I've typically found it to be easier and more reliable to scrap the whole database then to try and recover it. -Robert ... View more

The Telco model has not yet been released.  Last I heard it was scheduled to be released sometime around either the UC or the end of the year (2018). ... View more