Empower Your Organization with Pipeline Integrity Data for Organizations

How to create outlook signature

hi my name is Tom Coolidge and I am as DS pipeline industry manager I am facilitating today's webinar along with my colleague Jeff Allen Ezra's global pipeline practice lead welcome to our focus on advanced data management for pipelines this webinar is part of the petroleum and pipeline webinar series I think you'll find our time together today to be interesting informative and helpful now please welcome my colleague Jeff Allen Jeff thanks Tom morning everybody we've got full house this morning probably one of our most well attended webinars so far in the pipeline series so we're really excited about this topic and what we're really going to be going over today is talking about some of the new technology that we've been putting together for managing pipeline data that might be inside a station that might be along a transmission line sort of all along that pipeline supply chain and I'm going to be taking you some some some key tools if you've kind of seen any of our recent presentations you know we really kind of focus on these common operating patterns that we find within organizations and so these are the common patterns and really what we're going to be focusing on today is really on that system of record of that data management pattern that we have so one of the things that we're really focusing on is trying to solve business problems by applying the appropriate pattern and then the patterns then lead us to the underlying ESRI technology so as we're talking to folks in the organization or in the business we're clearly focus on these on these sort of organizational patterns then move our move our solutions into the NC ESRI stack as we look at how GIS is being used across these organizations you know traditionally we've seen this technology start and with the departmental solutions basically in these asset management groups and that's where we've been maintaining the GIS data maintained in the maop traceable very reliable complete really kind of building that system of record that the less the rest of the organism and leverages and then traditionally the largest consumer of that data has been the pipeline integrity groups within these organizations but as we start moving out to the rest of the organization we start seeing more and more demand for a higher fidelity in that data and really what we're trying to do is kind of build that digital twin of those pipeline facilities so we can meet the needs of the rest of the organization and then really when we start talking about the pipeline's you know we have multiple different organizations or mostly different units within many companies that we have to really address so we've got the upstream folks the midstream transmission pipelines all the way down into the facilities and into the downstream and distribution and really what we want to do is pull a set of tools together that allow us to manage pipe anywhere within this whole supply chain in a common geo database with a common set of tools and be able to literally be able to trace anywhere from those upstream gathering lines all the way down to the to the supply chain and be able to haul that all that link together in one cohesive system of record so when we talking about that we really start talking about managing in a single system everything from the well tip to the burner chip or to the meter tip right and all that pipe in between and what we've been doing at ESRI is is really kind of coming up with a way to manage all that pipeline data in a seamless single geo database now there's a lot of different business requirements a lot of different editing workflows that happen through all that supply chain and so sitting on top of that data repository are really two pieces of ESRI technology that allow us to seamlessly manage that data in one central repository one of those pieces of technology is the ArcGIS pipeline referencing and we typically use pipeline referencing in the transmission space and then the new utility network which I'm going to spend quite a bit of time on today showing you and demoing to you which is really to maintain that data that's in that network type of operations that could be distribution that could be gathering it could be inside a facility now one of the other things that's really kind of shifting this landscape of these editing tools is traditionally we've had desktop users connected directly to the back-end database right that client-server architecture that we've been implementing for years both are just pipeline referencing and utility riff utility networks or use this new web services system architecture and so what that allows us to do is is edit the data that's in that back-end database but really kind of leveraging more the power of the server to be able to do that so all those editing requests whether they come from a desktop tool or a web tool or a mobile tool go through that web server and then those edits get applied to the backend database that allows us to do a couple of different things obviously allows us to move that editing experience out into different platforms and I have to recreate the wheel and recreate those applications it also allows us to protect that data better right so as those devices are placing those edits into the back-end database we can kind of protect that data run it through a rule base and make sure everything that's being applied meets all the business requirements of that data as it's being stored in the system of record so this is kind of a shift and you'll see that I'll show you that in the demo of how this is set up but those of us who have traditionally set up these systems with a direct connect to the database when you first start using the newest version of ArcGIS pipeline referencing and utility network takes a little bit of getting used to to be editing web services and and have some of this logic sitting on the web service tier as you're you're editing data in the backend database so I'm going to spend a lot of time today really talking about the new utility network but I really wanted to take a moment to just remind everybody and we've done some previous webinars we'll do some more in the future specific to the pipeline referencing tool so for the user on the phone that might not know what the ArcGIS Python referencing tool is basically what allows us to do it's a it's a number of tools and technologies it allows us to linear referencing on on features within the geo database so from that perspective I can create a route and then I can place linear or point events on top of that route and manage that data that way right we typically see this data management technique used in the transmission operators from a pipeline supply chain perspective now the RS pipeline referencing tool kit comes with a couple of different components it comes with an information model which is set of feature classes and tables that we can enable into many of the industry standard pipeline data models - to enable linear referencing so that comes as a component that you can implement it comes with the desktop tool that's in arcgis pro for editing and maintaining the the routes themselves it also comes with an extension to the server and this really ties into that for a new paradigm of edits going through a server component so we now enable linear referencing capabilities at the server and a web editing application allows users to edit point in linear events along those transmission lines and of course that web application is going to use or highly leveraged that ArcGIS server to place those at its back in that in the backend database so this is pipeline referencing and and this is what we're using in transmission right now and the goal here is to now sort of tie this in to the next application and I'm going to show you which is the ArcGIS network management extension now utility network management extension so this is a new tool again built for pro that allows us to really edit and maintain those network type of scenarios within the pipeline system the goal eventually is to have our chestnut utility network underlaying all the pipe segments from the wellhead through gathering through transmission and distribution and we're in that supply chain we need to have linear referenced objects they would then sit on top of those utility network features and a geo database so think of the utility network if your transmission operator it will most likely maintain your assets all the fittings and features that are under pressure so your pipes your valves your fittings your tees and then your literary reference objects will sit on top of that so I'm going to show you today how we're leveraging this new utility network in the pipeline space because not only can we map those traditional pipeline segments but also start looking at a little more detail about how we map some of the things that's really been difficult or challenging to do in linear effort saying like station pipe and meter stations and compressor stations and and other sort of assemblies that that might have detailed data that we need to support operations a little challenging to do in the linear referencing system I think that's where utility network at least at the pipeline space is really going to find its its first adoption so the tiller network itself provides the ability to model and edit networks using obviously the ESRI platform the platform client specifically I'm going to showing you that any experience in Pro today so again like pipeline referencing this is a new tool designed specifically to work in the ArcGIS pro platform it's really meant to be offer up a better representation or a true representation of those assets in the ground it's been redesigned to be very responsive to editing and analytic capabilities so from a performance perspective it's really been retooled from the ground up and now includes a rule base to really allow us to better maintain and manage the data coming into the system of Records so we can now do things like create a rule that says hey if I have a 12 inch pipe connected to an 8 inch pipe I need a reducer in between be able to up now sort of enforce those business rules as data is being added to the to the database so really you know when we talk about ArcGIS pipeline referencing one of the things we talk about is that information model right those tables and feature classes that are that are enable the ArcGIS Python reference you run and very similar to that in the utility network we have this thing called an asset package and so the asset package are those key features that allow us to maintain the data in the utility network right so you can add all kinds of things to these geo databases but specifically for the utility network there's going to be some key features classes that we're going to put into the geo database to enable this functionality at the shared level there's a couple of different shared feature classes for structures that are shared across a number of different domains and then specifically we've kind of blocked off the domain networks into their kind of higher-level functionality so there'll be a gas and liquid pipeline network domain one for electric facilities they'll have different functionality and different features that are germane to electric networks and the same for water so if you're a pipeline operator you would have those shared structures and then you would implement the gas and liquids pipeline domain into the geo database so if we drill down a little bit further into that into that gas or liquid pipeline domain you'll see a couple different things we've really kind of streamlined the number of features both from from a performance reason and and it's a simplification of the model so underneath there you'll find a couple of key features you'll find devices lines junctions assemblies and sub Network lines right those are the major feature classes that you'll find when you open up this information model and implemented it inside the geo database and you'll see that same thing if you were to say implement the electric domain as well it and has those five major components and then what we're really doing inside the geo database is leveraging asset groups and asset subtypes to really model the different features with inside of there so inside of the inside of the pipeline network we'll find a device for example a sub type of device might be a meter and then the asset type is a coded domain that then further classifies what type of meat it might be so instead of having you know 50 or 60 different feature classes out there we've really kind of boiled the ocean down to these five and then heavily relied on subtyping to be able to split those out so as a user you really don't see that but as an administrator or GIS professional if you were to go behind the scenes into the geo database you'd see this for a collapsing of these these features down to these really kind of core five that the utility network is really responsible for and so for if you want to see that how that was implemented in a larger pipeline data model right if you open up the you PDM 2018 edition you'll see those domain asset classes now so if you were to look at the you PDM 2017 versus 2018 you really see this shift where we will kind of collapse a lot these feature classes down into those domain assets but you'll also still find all the other stuff that doesn't necessarily participate in the utility network so you'll find the pipeline referencing tables the inspection data tables the integrity and compliance tables the asset spectrum tables so all those feature classes and stables and relationships they'll still there but really the key is to look at these sort of oil and gas domain Network tables that's where the real change has been in the UPD of 2018 addition to really support the utility network so there's about five or six different major components that make up the utility network and what I'm going to do is really attempt to take you through and an overview since these five or six different components to show you kind of what the landscape and what are the different functionality that you could you could look for as you're implementing utility at work this thing is pretty big it's been worked on for quite a number of years it's got a lot of functionality to it I don't propose that I could get into everything in an hour but this should give you a good sense of all the different things you can do and and really get you thinking about how you might be implement this within your organization the first part of it I'll show you is really talking about the editing workflows right and so on the editing side really the utility network takes advantage of the core editing workflows that are in our GS Pro right so I'll have all the tools available to me to do things like alignment reshaping vertices dividing all those sort of widgets that are part of the editing workflows are available to me in the utility network as well as a lot of feature panes and ways to set up templates to make editing for your users really easy an example of that might be these group templates so here's an example of a group template from the water domain where they place a hydrant and that hydrant has a gate valve and a lateral and reducing tee all associated with that single single edit so if you think you've been in the pipeline perspective this a good group editing template might be a valve assembly or a launcher receiver assembly where I'm making kind of group templates so that I place that object I'm actually placing five or six different features at the same time then I could modify those for the specific implementation but in inside of my pro project I can kind of build up these group templates and make placing of features or these complicated features a lot easier for my editors now also in that editing workflow you're also going to start looking at the rule base right so inside of that server we now enable a number of different rules that can be enabled against those edits as they're being placed and into the database some of these rules are applied real-time to the editing some are applied after so for example one of my rules might say hey I can only attach this type of of tea to a steel pipeline right that would be a real-time rule with this that I would want to see as I was placing that tea another type of rule might be that edge Junction edge connectivity where I really can't apply the rule until I place the three features and then I can check those three features against the master rule page so the major kind of rules that we have obviously is Junction to Junction connectivity like what what Junction can be attached to what other junctions we have Junction edge connectivity so at the end of a pipeline what type of Junction's what type of features can be attached to it I have my edge junction edge rules again that's the that's the pipe to reducer the pipe kind of example I also have rules for containment and I'll kind of go through what containment is as well but basically it allows me to build up features so about G is within a GIS and then the final rule kind of structural attachment so what large objects from a structural perspective can be attached so for example in a pipeline support can be attached to a pipeline right those rules of the structural attachments and what can be connected to the pipeline features themselves and this is just an example of looking at that in the this is an example of that jug valve I'm sorry edge Junction edge rules so you can see it's it could be pretty detailed in the template package that we deliver with the software we have a number of these rules already set up for you you can edit these rules you can add to them you can remove them so part of the project or probably the process of implementing utility network is to look at these rule bases and then modifying or appropriately for your organization now as we look at these rules or as we apply these rules to the geo database the way we do that is by creating these sort of error layers so if there is an error in any of these rule bases what we do is we create either a point line or a polygon feature in the in the rules layer that you can go back see what what rule then was not applied correctly make that edit and then revalidate against that rule base so let me jump back into my rjs pro project and i'll show you example of those rules and we'll look at some of the editing workflows is actually take if you anything you've seen our pipeline demo we have some transmission lines of gathering lines of offshore lines what I've kind of done is is integrate my utility network demo in with my pipeline demo data set so you'll see now that I have some utility network features in my in my in my map I now just like a location referencing toolbar I get the utility network toolbar right this is sort of a context-sensitive tool that will be turned on as I as I have features from utility network loaded into my into my geo database and so what I'm going to do now is I'm going to zoom in here and one of the things that we've often seen from a pipeline perspective is we'll have a transmission line we'll get to a facility like this tank farm and maybe I have just a polygon representing this site or maybe I actually have the points that represent the tanks inside but what's been really difficult from us or a linear referencing perspective let's actually dive into this tank farm and start mapping out all the facilities with inside of here right so this is from a from a pipeline perspective where I think I see a lot of operators starting to look take their first look at the utility network because to be able to do this type of mapping of the station facilities in these pipeline stations and start to map this stuff obviously Trace is a big functionality here be able to link this to operations so you know if I have a whole bunch of meters or a whole bunch of valve inspections that need to happen inside this station being will obviously map these out and not just have them tied to a single polygon it would be key another advantage here is I can start running say station risk on all these pipes so now I can see you know within this station what is my sort of most risky piece of pipe or assembly within here so I can know my risk mitigation on here as well so this would be example of a larger station but I also think we've got some real use cases you know in line so here's an example where I'm moving down the main line itself and I have some station pipe along that so the red line we represent the transmission lines coming into here and in my ArcGIS pipeline referencing maybe this is my route into my launch or receiver assembly and coming out the other side but I've never really had an efficient way in my linear referencing to sort of go ahead and model you know all this piping inside of the station and and make it make sense from from a network center view so I see the the advantage of being able to now to come off the transmission line trace into this utility network piping the station piping that's here can back out the other side of the station and continue down the transmission line so let me show you how this would work right so if we look over here I've got some feature classes and you're really seeing now that sort of boiling of the ocean I was talking about so we've got assemblies devices and junctions and pipelines and if I open this pipeline junction table up for example you'll see all those sub types right so now I see the couplings the elbows the end caps so I have as many features as I've always had but I'm really using sort of major my making my major features and then using subtypes to kind of organize this within the geo database and I right click on this layer look at the properties and I look at the source you can now see that this is being actually pointed back to that server and the rest endpoint so instead of making a direct connection to that feature glass in the Geo database I'm editing this feature class coming right off the server I can also go in here and start looking at the rule base as well right so if I right click here and look at properties I've got the properties of the utility network I'll just open this dialog up a little bit more here and if I look at network properties I can see I have a cold bunch of data about the network itself but down here you can see I can expand this rules and if I want to expand the junction Junction connectivity I can really easily now review all the rules that are have in the rule base for that type of that type of rule hello again these rules are stored at the server level I'm accessing it here in Pro so I can see all the rules that I have set up and there's geoprocessing tools that allow you to go in and add and edit the real base as needed for your organization and then as I apply the rules and I check the data any errors against those rules are going to be shown here in this utility network layer all right so I'm gonna have any any point errors line errors or polygon errors gonna be showing here as well as any areas that I do editing in that need to be validated so we call those dirty areas right so as I do editing in this in this area it'll tell me all the features or show me a representation all the features that need to be validated against the rule base using the validation tool on top of the utility network so let's go ahead and do a quick edit here I'll show you how easy it is so here I've got a station I've got I've got some facilities coming in here I've got a maybe a take off to a to a customer on the station I'm just going to go ahead and connect all this together so what I'm going to do is go back to the editing tool and I'm just going to hit the standard create tool here and let's go ahead and place a T on that line so I'll search I'll I'll select the T object here and I'll move it back over onto the utility network now you can see I've actually got my snapping turned on but I cannot snap this T to this blue line that's because I have a rule that says only a metal T can be snapped to this metal pipeline so what I'm going to do is gonna go to the editing template here and I'm actually gonna tell pro that I'm placing a metal three-way T as an attribute and you see as I move back now on to the utility network it's going to understand that that's the valid rule in my rule base I'll go ahead and snap that and I'll go ahead and apply that and place that into utility network now from here I can also go ahead and place let's go ahead and put a pizza pipe in here now a piece of station piping and again same idea I'd fill out all the attributes but for now I'm just going to tell it it's coated steel connect it to my new valve and then we'll go ahead and put a flange on the end of that line and then maybe go ahead and put the valve on the other side the customer valves now you can see I've got that dirty area there all right it's telling me to have it run the rule base against all these features so I'm just going to go back to utility Network I'm going to check all those data assets I just applied against the rule base it'll validate all my topology for me and give you the indication that that was successfully validated now one of the last things I want to do is go ahead you can see I don't really know that pipe that's inside of that facility but I know that these two things are connected together so I can now use my node to node connectivity I don't have to sort of build that false piece of pipe between those two features anymore I want to go ahead and from a model perspective go ahead and connect those objects together so again I'm going to go back to utility network and I'm going to hit the modify tool here and I'm going to modify my connectivity I'm gonna select this flange here and I'm going to add this valve I'm gonna go ahead and apply that notice that it's a complete I'll go ahead and validate that and now those all that pipe is now connected together through that station and if I want to see that that point-to-point con activity just go ahead and clear this up I go back to utility network and I hit this view Association tool you can see that dashed line there now I've got those two pieces connected together so now as I as I traced through the network those two things are now connected in the model and I can jump on to this to this customer piping and trace out the other side so I'm sure you kind of send the editing validation rule bases that are going on behind the scenes in the inutility Network so the next thing I want to talk about is this concept of that detail network has of containment and basically what this container allows us to do is is have this ability to really go down to the next level when when we're modeling features within the database so in this example here I might have a point or a polygon representation of a pump station and I want on then now model in all those facilities that are inside of that station right so now I can build a container and that container can now have all those features inside and connect them all together containers can contain other containers right so I can have inside of that station I might have a valve assembly container and that valve assembly has all the details of the the flanges and the fittings and all the things that go inside of that so I can have these sort of hybrids of containers features are geographically placed inside the container or they can look like a somatic so I get that both the ability to sort of place features where they are inside that station or just really kind of represent them in more schematic mode and then those features do all connect back to the larger network topology so as I run a trace or run on my analysis it's actually going to trace into those containers and all those connected objects and back out the other side now we can also set up rules for these containers then I could say what objects can be contained within side of another object so for example I might not be able to place a mainline valve inside a pump station right so I can now set up these rules to say how things could be contained within other things to keep my data clean as I start building these I can also set up rules of what happens when deletions happen so for example I can't if I have a restrict set on right I cannot delete the container until everything else inside and then it's deleted or maybe I want to have a cascade rule that says if I delete the container I delete all the objects inside of it as well so again these are all configurable items within the rule base for can so let me jump back to my demo and we'll go back to that tank farm and again I'll zoom in to this facility and you can see I came in the main line valve here or the main line pipe line and I go into this pump station and I've got three lines coming out to the rest of the rest of the different pumps coming out of this I've got the flanges here but I've got a lot of stuff that goes on inside of this on this pump station as well and a full on a look at that next level of detail I'll go back to the utility network I'll say I want to enter a container I'll select on that container and I'll jump inside so what this will do is open up the container for me and show me all the pipes that I have inside right and here I've laid out those three different pump stations inside of there I've got the meter coming in I've got all the bypass piping the entity's isolation valves the bypass piping into the bypass valves I've got this next level of detail as I enter this station all these things are traceable all these things can be tied to the work order management system if I need to come into the station and do events and they're all tied into this container same ideas I had at that meter station I have you know these valves here they don't look like they're connected anything but I can turn on those connectivity rules and see what's going on inside the station you can see that advanced elf that I've got sort of placed here more schematically is tied into the two flanges on the upstream side and I could then if I wanted to maybe make this whole pump and its bypass valve another container with inside this station so I could dive even deeper down but the nice thing about this is from a mapping perspective when I'm at this level I'm not having to show all that detail or try to draw all that detail I'm just drawing in the station itself and represented on the map even though all those details are behind it so let me show you how easy this is if I go back to my pump station I have a container here at this station building here that I've already placed and what I want to do is I want to add these objects into that inside of that container so I'm going to go back to utility Network toolbar I'm going to hit this modify tool again instead of connectivity this time I'm going to say containment I'm going to select my container and I'm going to go ahead and add the content that I want to be part of that containment all right so I'm going to add that flange I'm going to add that control valve I'll go ahead and apply those I'll make sure that those objects can actually sit inside a container so I'll run the rule base against them to validate that it did I'll clean up that selection and now you can see I've got those I've got those objects if I go in here now and enter this container I can enter in there and see those objects now if at any time I want to view those objects at the mapping level I have this little display content here to rule here too so I can go ahead and even show them at this level so about this level and I want actually want to see the content at the at the higher level that are inside these containers I can use this display content tool to go ahead and show and hide all those details that are that are inside these stations so another kind of big component to the utility network are these terminals and sub networks and basically what these terminals do is allow us on a single feature to really define the connectivity or different rules for an action activity or different what we call ports of how these things are connected right so any of the inside the rule base any of these features these devices can have these terminals associated with them so for example a rule for a valve in this case might be a check valve so when I place a check valve into my into my geodatabase not only do I place wire it's connected but I want to kind of connect it to the pipe line with its highside and low-side so I know the flow of that thing another example might be my pump I place that pump I'm also going to have the law high side and the low side pressure of that as it as it flows into the station so it's really allowing me to get a fine-grained detail on how these how these objects are then placed in this can be extended into the CP objects as well so in my anodes and rectifiers I can have my current in and my current out on my flows what's the inflow what's the outflow what's the high pressure side what's the low-pressure side this allows me to really dictate on those point features how they are actually connected to the pipes on either side of them and then this really then ties in to what we consider sub networks so once I have those objects define say for example my pumps and I'll define the high side and the low side I can now derive a sub Network and a sub wet network is basically think of it as a sort of a live trace where it's it's going in and looking at all the devices and all the lines that are connected to a device and then giving me a polyline representation of those things on the map so in my example and I'll show you the second going back to that pump station I now have subnetwork for my pressure systems and that sub Network shows me all the different features that see the same pressure based on that on how I'll place that pumps those pumps into the system so if we think of this thing from a maop perspective right I can now start looking at within the sub networks all the different objects in that sub network and what the lowest maop pressure might be so not only the sub networks show you geographically all the things that are connected together I can create summary attributes in those sudden networks that can pull a feature or pull an attribute from all the features that are in that sub network and bring it up to the to the to the summary object so in here I could say hey tell me the lowest maop of all these things that are connected to this to this pump or to this compressor so you can think of this now we now have the ability to do sort of maop of system and model and and analyze that using sub networks the other way I can see sub networks being used RCP systems right so those the this start of my CP system might be my rectifier and I can now set a rule on my flanges that say hey the CP system because this flange is insulated it stops so all these objects are electrically connected but the picture flows through here so all my objects inside of here are our other objects are see the same pressure so I can start building up these sub networks to model different real-world scenarios within my pipeline network and so it's a hard concept to explain in slides so I built a bit of a demo for this in this pump station we'll jump back to there so remembered when I was when I zoomed in and went inside of this of this of this pump station I had three different pumps that we looked at I'll just go in here and turn the details on but I already have them on so you can see them so I have the main line coming in obviously that all sees the same pressure I've got a regulator here that drops it down so this all this piping on the top side of these pumps will see the same pressure and then the out coming out of the pumps will see individual pressure systems coming out of there so when I connected these pumps that I connected the terminals of these pumps to the pipe line either side i define names for those for those networks and I can go ahead and see those now if I go back and zoom out a little bit so this makes a little more sense so from a pipeline perspective like all I have all this station piping but if I go the utility network toolbar now and then you look at the sub networks and I do a find I can see all those sub networks that are defined so I've got the overall system pipeline I've got these pressure zones here so let's take a look at pressure zone a I'll go ahead and activate that and what it's going to do is it's going to isolate all those pipes for me that are part of that pressure zone so what it's done is sort of grayed out all the pipes in the background and now I can see all those pipes that are coming out of the pump a and where they connect to in the model right now like I said these are also persisted in the geodatabase as well and that's that final feature class that I've got out here so you can see this pipe subnetwork line layer so I'll turn off my pipes themselves and turn on this sub Network line and now I can see persisted in the geo database so I can now share this out to field users I can share this out to web applications which are a real-time dynamic trace of all the pressure networks that are inside of this of this station so the purple line is my pressures on a-come a pump a pressure zone B is the Green Line pressure zone C's is the blue lines here coming out of pump C I've got the red line which represents the high pressure transmission and then I've also got a black which is that pressure system downstream of the regulator about upstream of the valves inside that pump station so again these are polygon features and if I if I identify one of these on the map you'll see it shows me all those connected features and also gives me some summary objects as well so you can define these summary objects and summary attributes and they are then created as I extend the network so if I added a new piece of pipe downstream of pump a it's automatically going to be added to the pump station a pressure zone and into this summary polyline layer that I can then model and share out so the nice thing about the utility network is these are all simple features so if I go on behind the scenes and I look at what's going on with these points lines and polygons these are simple features in the geo database that I can now share out my portal put them on a web map and use them and all my downstream like sort of system of engagement activities but they're all being maintained and built off of real attributes as I add these attributes to the to the pipeline Network so I've got two more things I want to show you one is now that I have placed all these objects you have a number different option options for being able to trace through these connected objects right trace is really a provides business value to be able to answer questions on you know what happens if we shut this valve off what happens what are all the devices downstream that see the same pressure system or see the same device helps us integrate with things like skate and control rooms do pipeline modeling right these are a lot of the different workflows that we've been looking for from a pipeline perspective that we can now meet with the utility network and there's a number of different types of traces you can do right so the basic isolation traces you can do pressure zone traces you can if you set up your your CP systems you can do traumatic resection or CP zone tracing using all that underlying data that I've been showing you in the database you can also have starting points you can have barriers to the trace so for example I want to trace through through a valve if that valve is closed I want to be able to stop there if it's open I want to continue on and in different ways that you can then put all that stuff together so you can run these traces individually from pro but then there's also these kind of widgets you can call from the server so you can build up these trace configurations and then publish them to your server so the business folks can use them in their day-to-day operations so let me jump back now to the to the demo and I'll show you a quick trace so go back to that pump station I'm on the utility network I'll go ahead and set a starting point for this trace at this takeoff point here and let's just a simple connected trace so I'm going to include the containers so I'm going to go in and out of that those containers and I'll go ahead and hit run now and that you can see all the devices that are connected together from that trace so you can see I did all those editing operation enter that containment connect Avila's all together all those features and all those pipes are automatically connected in the back end through the trace algorithm Traverse ability for example if I want to say my but I don't want to I want to have a barrier for not tracing through closed closed valves so I'm going to put in a conditional barrier on this trace and say the device status of any devices that I run into is closed and now if I run that trace again you're gonna see a run in and I stopped at that closed valve so different ways you can configure these traces obviously there's all kinds of different functionality in here how you output these traces where they go different filter functions you can run and then up here on the toolbar obviously you can see we have a number of different trace types so we can do an upstream trace the downstream trace sub Network and trace connected traces all kinds of interesting things you could run with this data set now that we have a connected model throughout the throughout the tool set now the last bit of functionality I wanted to show you is these diagramming so this is similar to what we use to have for schematics but now the schematics are actually integrated in with the utility network tool so on the utility network tool I have the ability to take that data that I've created and apply that to a schematic network diagram in real time and have those things linked back to the map and so I have all kinds of different options in these schematics I have tree layout smart trees geo schematics all kinds of different ways that I can represent those schematics and then once I have those schematics created I can then go ahead and share those out with your organization through my portal so here what I'll do is I'll jump back to that tank farm and what I did here is I took all the objects you just ran a simple trace to find all the connected objects in this tank farm and then created this simple tree diagram of everything that's inside of that station so you can see that upstream meter this green box represents all the different objects or inside of my container and then you can see I run out to all the different all the different tanks and how they're connected together to the different pipe so that leads me back to my station and say if I select on this tank here and apply that to my map I run back to my map it automatically zooms me and shows me that that object in my diagram is is connected to the object in my map so these things are now forever tied together as I add objects to my to my utility network the schematic is automatically updated and then I can go ahead and export or share those schematics for the rest of the operations and all that all the attributes that I have stored on these objects are available to these objects in my schematic as well so I know I threw a lot at you in the last hour there's a lot those are if you if you kind of look back at my demo and stop and started this presentation at those at those major demonstration points those are kind of the major bits of functionality now with inside those bits I've only touched on a maybe even not a tenth of all the things you can do inside of those components there's a lot more to this so I've added to this presentation a couple of different links that I think are pretty important the first one is to the utility network overview page on on the ESRI site this has a lot of different hyperlinks that allows you to drive down even deeper the separate second link is an overview it's a blog article from the for the product team that also contains a lot of different links to other information about the utility network and then the last one here is a link to the ArcGIS Pro help page and this is really kind of guide you through and is the starting point to what is utility network and then you can actually dive down into all those different things that I showed you today and get more details about this this also be live links will be obviously sending this presentation out to everybody so once you get the presentation you can then you can unfollow these links and get some more information really as far as next steps go you know go ahead and look at that additional content that we've got on the web because a lot more d2 there a lot of people now are looking at software evaluations and demos you know demo of your specific nice use cases if you want a software evaluation if you want a demo if you want to follow up with the next steps please reach out to me and I can I can arrange that either through myself or through your account manager we also have within the ESRI professional services we can do pilot projects proof of concepts full implementations help you with data conversion we all those services work that go along with those as well as engaging with our partners you know we have a lot of partners in the pipeline space this is by no mean and extensive list but these are the partners that have sort of approached us and said that they're interested in being or interested in starting or have already started utility network projects with their customers so I to reach out to partners as well to get help with this and I want to thank you for your time and I'm going to turn it back to Tom we've got about ten minutes left or a little under ten minutes we can take some questions from the audience oh hey thanks Jeff that was that was really good very interesting we do have I'm sure we have more questions than we will to take in the time that's remaining but as you said let's get started on the on the first couple the first question notes that ArcGIS pipeline referencing can work on pods light then continues is there any plan to work on pods original versions especially version four and again this is related to APR yep absolutely so when I was on the Apr slide one of the things I pointed out was the APR information model right these are a core set of tables and feature classes that enable linear referencing within the geo database if you look at information model you're not going to find pipes and valves and fittings you're going to find just the core elements that we need you could take those core elements put them into the pods four pods five information model and wire it up to these to those existing events and start using those existing definitions of objects within APR so APR is not I like to say APR is data model agnostic it can go into any data model it can go into a custom data model it can even be put into older data models and brought forward using that technology okay thanks the second question switches to the utility network does the utility network rules pertain to transmission lines as well they do so we have a we have the rule base that we deliver with the asset package that's posted up to the website has some default rules for distribution gathering and transmission built into it I don't think that they probably are 100% for every organization but it's a really good start there's all ton of rules already built into the rule base to get you started okay continuing with a utility network art I flange etc features also available for transmission pipelines yes so the way that we envision this to to work going forward is that those same features like the lines devices and the junctions whether they sit in their gathering in the transmission or the utility network think of that pipe layer being continuous through all those different segments and then in the transmission world we would then lay on top of that pipe the linear referenced objects so in a sense if if you're familiar with APR the pipe layer becomes APR center line right and then out all the linear objects sit on top of that okay which King well perhaps related to both the question is can rules be applied to the event editor currently they are not so currently the rule base is tied to the utility network so the rules would be based on on applying the let's call them the fittings under pressure right would go through the rule base if there are additional rules that apply to say just the linear reference components class HT a other regulatory layers that might be sitting on top we could apply things like data reviewer checks to be able to make sure that those business rules are being applied but the rule based specifically that I showed today is tied to the chilling network at this point and the features that participate at that layer okay and then perhaps one last question here in this hour and then we'll answer the others and an essay Q can sub networks from different containers be displayed from the geo database at the same time yes so the sub Network polygon or polyline layer that is generated goes inside of those containers as well so as I zoomed in and I showed the sub Network for that that that pipe that was on the high side of the pump if that if that regulator over the upstream regulator and the transmission side was outside of that of that of that container then that black poly line would have can have gone outside the container and up into the transmission system so yes they can they could Traverse inside and outside of those containers as well thanks Jeff we are close to the top of the hour unfortunately we didn't get to all of the questions we we still have some more and we will answer those in an FAQ document that we'll make available to attendees please be aware that a pipeline track will be featured at as Reese petroleum GIS conference and used in may 15 16 2019 more details will be available early in the new year we hope your schedule will permit you to join with the hundreds of users from the pipeline community who will be there thanks again for joining today's webinar have a great day you