Latest Contributions by RobertKrisher

The challenge with trying to just use the append tool is that you're typically going to have to do a fair amount of translation to get from your current model to the target model.  This means that if you want to use GP tools to accomplish this you will likely need to go through several iterations of deriving new feature classes that slice and dice your data in different ways, along with translating values between the source and target domains. If you have the data interop license available I'd recommend you check out the sample workbenches Esri has provided that allow you to do these operations using FME / Data Interop. Because you're an Electric client you'll also need to consider how you're going to handle the fidelity of your data, and you may need to also introduce code to handle the creation of any additional connection points or terminals you need. If this seems like its too much work Esri has a large network of partners and a Utility Network specialty program specifically designed to get you in touch with a company who can help talk you through the process or do some / all the work for you. ... View more

Mark,   That definitely seems like a bug (I'm assuming a manual test would also fail), if you haven't already logged a bug with Esri I'd definitely do that.  Each terminal on an emergency valve should definitely be able to act as its own isolation controller.  Are you going to be at GeoConX? ... View more

RJ,   You are correct.  Fortunately OSIsoft also has a RESTful API available that allows for querying out data from the PI system (my guess is you would want to use the StreamSet objects: StreamSet  ).  Managing all the configuration / mapping between OSIsoft and the GIS model as well as Geo Enriching the data streams from PI (adding geometries and other information from the GIS features) should all be doable via the GeoEvent server without any need to write code, but it will still take a fair bit of work to develop the set of inputs / processors / outputs to achieve this.  There are a number of reasons why OSIsoft has a product for doing this (and that product does leverage the GeoEvent server) and most of them have to do with a) making is easier to set up and maintain the mappings between the two systems and b) making the solution more scaleable by introducing some components to manage the demand on the OSI infrastructure. -Robert ... View more

Damien,   Duct / Duct, Duct Bank / Duct, and Duct / Cable associations are managed through containment.  That is to say each duct would have a containment association with the cable it contains and each duct back or duct  would have containment associations with its corresponding ducts (sub-ducts are allowed in this model, finally).  Unfortunately there are no products or extensions build around conduit management for the utility network yet so if you want cross sections you'll need to develop something yourself. Thanks, Robert ... View more

Anna,   I'm familiar of several instances where customers who aren't using PI have leveraged the GeoEvent server to process and store SCADA data inside the GIS.  You'll still need to develop something on your end to relay data to the GeoEvent server. ... View more

OSIsoft PI actually has a product that allows you to do this, so I'd recommend you start there ( PI Integrator for Esri ArcGIS  ).  It is possible to write your own solution to do this using GeoEvent Server and some other components from OSIsoft, but it would require a fair amount of work. ... View more

As long as each row is referencing a different terminal you should be fine.  Is it possible that the other valve were each referencing different terminals and this latest valve has two or more rows referencing the same terminal? ... View more

I've run into strange behavior like this occasionally, one of the things I do as habit now is whenever I'm standing up an environment I always bounce Pro after staging the utility network and once against after applying the asset package. ... View more

Can you post a screenshot of where the update stops in the circuit?  The most likely causes are things like not setting a terminal connection or accidentally setting a value on a feature that stops tracing (i.e. setting a device to be open or a junction/device/line to not be in service). ... View more

If you had a way to match up your non-spatial table with a spatial source you could use geoprocessing tools to achieve this, but if that line you're trying to create is the one that was deleted out of SDE than you may be out of luck there.  If you were just trying to get the geometries for one or two features you may be able to go back to source drawings for the area or infer its shape based off of some stationing or linear referencing system (if you have one), but all of these approaches can be fairly difficult. ... View more

I've included a copy of the service definition and the ArcGIS Pro Web Map definition.  I thought about including the web map definition from a map created in ArcGIS Enterprise, but it behaves exactly as you described 😃 ... View more

Michael,   I just revisited this and @ 10.6.1 with ArcGIS Pro 2.2.1 I lose domains and subtype descriptions in my map document definition in a shared web map even if I symbolize using only the subtype field.  If I look at the map definition I can see that the domains element is blank (even though the field has domains) and even though the type has an id its still unrecognized as a subtype by the map (I wouldn't the order would matter, but the id is typically at the beginning of the json element but for a pro web map its located at the end). "types": [           {             "name": "Anode",             "domains": {                            },             "templates": [               {                 "name": "Anode",                 "prototype": {                   "attributes": {                     "assetgroup": 15,                     "assettype": 0,                     "rotation": 0,                     "insulatordevice": 0,                     "ownedby": 1,                     "cpsubnetworkname": "Unknown",                     "depth": 0,                     "terminalconfiguration": "Default",                     "devicestatus": 1,                     "accessible": 1,                     "maintby": 1,                     "lifecyclestatus": 3                   }                 },                 "drawingTool": "esriFeatureEditToolPoint"               }             ],             "id": 15           }, ... View more