1
START Let's begin with optimized pipeline placement. Choose one of the scenarios below to see how the route might differ depending on the parameters. NEXT Now that a pipeline gathering system has been determined, it is time to find the most efficient access road network by choosing one of the options below. Scenario P-1 Connect Well Pad Sites to Well Pad Sites Scenario P-2 Avoid Crossing Railway Network During Routing Using the Well Pad Site locations shown at the beginning of the quest, build a trenched pipeline network based entirely on connecting this existing infrastructure. This scenario is modeled after a Greenfield approach, where no consideration is given to any existing pipeline gathering system, roadways, or other assets. The proposed pipeline depicts the most logical and efficient paths as determined by the location of sites and the constructability of the area. The constructability can be seen in the underlying Full Solution raster where alternate paths are shown in blue while the level of constructability ranges from highly recommended (High) to not advised (Low). The white, or hollow, areas within the rasters represent those regions deemed impassible. Scenario P-3 Avoid Construction in Areas Categorized as: Anthropogenic or Environmental Scenario R-1 Connect Well Pad Sites to Well Pad Sites and to All Existing Roadways Scenario R-2 Connect Well Pad Sites to Well Pad Sites and to All Existing Roadways (Avoid Crossing Railways) Scenario R-3 Connect Well Pad Site to Well Pad Site and to Major Roadways Scenario R-4 Connect Well Pad Site to Well Pad Site (Only) Scenario R-5 Connect Well Pad Site to Gravel and Secondary Paved Roadways Scenario R-6 Determine Roadways Along Pipeline Gathering System Using the predetermined Well Pad Site locations, build a pipeline network with the same principles as Scenario P-1 in mind. Well Pad Sites should be connected to one another, as in the previous case. However, this situation requires that construction crossing railways is to be avoided at all costs. Because the railway runs in the middle of the path that would have been most likely to be taken, the Geomancy Decision Engine was unable to connect the upper quadrant with the lower quadrant. Facilities will need to be located accordingly, or the planner will have to determine a new route out of the way of the system. If the Decision Engine were to be utilized for routing around the system entirely, the scope of the study area would need to be much larger than was previously used. Other than the division of the pipeline gathering system as well as increased constructability in some regions, there are no significant differences between P-1 and P-2. As was the case in the previous two scenarios, Well Pad Sites are to be connected to one another. It is presumed that there is no existing pipeline infrastructure. For this instance, however, all areas that have been classified as either Anthropogenic or Environmental are to be removed as potential locations for construction. This data includes locations for Parks/Recreation, Populated Areas, Protected/Endangered Flora/Fauna, and Conservation Regions. Within the Decision Engine, these datasets are changed from a Weight Classification Method of Constant Weight to NoGo. Although the optimal projected path for the pipeline gathering system is not affected too drastically compared to the default Scenario P-1, the locations of previously determined Well Pad Sites are another story. Three sites in the upper quadrant fall within the boundaries of an Environmental zone and had to be eliminated from the overall plan for this case. Determine an efficient network of access roads that connect Well Pad Sites to one another as well as to all existing roadways. This includes Major Roads, Secondary Paved Roads, and Gravel Roads. By making use of the abundant infrastructure nearby, this approach ensures that the smallest amount of construction is required. Sites located within the same block are connected to one another and then to the nearest adjacent roadway. Using the same principles as the previous scenario, connect Well Pad Sites to one another as well as to existing road networks -- this time, connect to only Major Roadways. This method may be ideal for those areas that have budding primary infrastructure, but do not yet have smaller networks. Rather than the resulting network seeking out the nearest roadways initially, it first connects sites in the closest proximity to one another before moving on to establishing a connection with existing infrastructure. This instance follows the same guidelines as Scenario R-1. The main difference, however, is that any access roads generated must not cross railways. In some cases, this would drastically change the landscape of results generated by the Decision Engine -- such as seen in Scenario P-2. In this instance though, the only noticeable difference between this scenario and R-1 is the Full Solution Raster. The area between the railway is eliminated from consideration of construction. In contrast, the access roads themselves do not seem to have been alterred by the avoidance parameter. With the help of the pre-determined Well Pad Sites, find potential locations for access roads that connect only the available sites. This scenario, similar to Scenario P-1, mirrors that of a Greenfield study. There is no existing infrastructure, only site locations. Without similar restrictions for processing as were used in the previous access road examples, this case almost seems to visually mirror pipeline gathering system solutions shown before. Determine an access road network that connects individual sites to either Secondary Paved Roadways or Gravel Roadways. This approach is suitable when Major Roadways are not viable options for connectors and Well Pad Sites may be too far apart to warrant connecting them together. What is interesting to note for this scenario is the lack of "least recommended", or yellow and red colored, regions portrayed in the Full Solution Raster. Because Well Pad Sites need only be connected to existing roadways -- which are sparse in some areas -- the availability of constructable landmass greatly surpasses those regions that would not be sufficient candidates for placement. The previous five situations were analyzed without neccessary consideration for either an existing pipeline gathering system or one to be placed in the near future. This is not an unlikely occurance as often times access to sites is needed ever prior to beginning construction of other features. Geomancy, also, has the ability to use the projected road network as a consideration for pipeline placement. Likewise, it has the dexterity to do the reverse -- creating access roads based on the existing pipeline gathering system. This scenario is an example of that. Using the pipeline network generated by Scenario P-1, roadways have been determined that fall along the pipeline regardless of any other existing infrastructure. The roads, of course, are shown in orange while the gathering system is striped. An Adventure in Determining Smart, Sustainable Pipeline and Roadway Routes Using the Geomancy Decision Engine Well Pad Sites + Pipeline Gathering System (Scenario P-1) YOU Upper Area Lower Area Upper Area Lower Area Map Legend TER_DEM Value High : 18233.1 Low : 8094.61 Pipeline Gathering System and Road Network Solutions: Raster Source Datasets Scenario P-1 Scenario P-2 Scenario P-3 Scenario R-1 Scenario R-2 Scenario R-3 Scenario R-4 Scenario R-5 Scenario R-6 Pipeline Gathering System and Road Network Solutions: Vector There are a variety of datasets and sources that one may utilize to determine potential asset locations. The symbology that distinguishes those shown here can be found below by category in which the data is included. Well Pad Sites Roadway - Gravel Roadway - Paved Roadway - Major Railway Hydrography - Streams Hydrography - Waterway Hydrography - Waterbody Anthropogenic Regions Environmental Areas Depending on your situation, the assets you currently manage, and how far along your team is at in the planning process, determining access roads to your facilities may be the next most logical step in your workflow. If so, proceed on in your journey. If not, please continue to the end of the quest to learn more about this optimization procedure. You made it! As with any method used for optimizing the locations of assets -- whether they are Well Pad Sites, Pipeline Gathering Systems, or the like -- the results produced heavily depend on the area of study, supplemental data, and parameters utilized during site processing. Although the examples shown here are concise in that they merely highlight the production of pipelines and access roads, often times the planning process for a team entails many more features than just these. Where is "here"? Here is the beginning of your journey, where you set out to find the most efficient and logical solutions to your field development needs in the least amount of time possible. Field development planning, on average, requires months to complete with the same amount of time dedicated to determining just one potential route. With the typical approach, seemingly minor setbacks -- such as an expansion of the study area or the inclusion of supplemental data -- can cause not-so-minor issues, delaying the rate of production and setting back deadlines. The Geomancy Decision Engine, however, helps to alleviate, or even eradicate, the need for such lengthy planning times. This ArcGIS toolset allows teams, or even a single user, to produce multiple results in a fraction of the time, often hours or simply days. Geomancy comprises a system for the modeling and analysis of field development at any point in the planning process. It utilizes a variety of weighted factors that represent physical features, survey information, environmental considerations, etc. of a specfied area to optimize the placement of pipeline routes, roads, and facilities/wells. For this study, we will be finding solutions to pipeline placement as well as proposed access roads for the study area below. To do this, Well Pad Site locations were created based on current lease boundaries. Each scenario shown here is based on real-world cases that a team may encounter when planning infrastructure developement. These include Greenfield scenarios, areas that are established, as well as regions that are undergoing development. Please use the center map as an overview of how parameter distinctions and individual situations may affect a route, even if it is based on the same premise. Scenario-specific maps, along with inset maps highlighting the Well Pad Site connections in the Upper and Lower quadrants of the overview, can be found in each step. OPTIMIZATION EXPLORATION ARE HERE Well Pad Sites Full Solution Surface Value High Low The flexibility of the tools avilable in the Geomancy Decision Engine allow the generation of these assets as well as Well Pad Sites (On and Off Lease), Transmission Pipeline, and 3D visualizations. Although these can be created based on datasets where the exact location is known, they can also be produced using generalizations. Specialized tools within the set offer the opportunity to draw features in approximate locations and then find results using this data as a source. This is helpful for situations where an area has been proposed for drilling, but the team is unsure what the overall outcome may entail. In addition to establishing a base solution, formatice solutions like those shown above are useful when back-casting or developing a plan for the system in its entirety, and then constructing individual sections intermittently. Regardless of the general outcome, however, the workflow remains a simple one. The steps shown to the right, as well as below, are those users typically take for Full Field Optimization. Input Surface Datasets Input Supplemental Datasets Determine Constructability Determine Well Pad Sites Generate All Other Results 1 2 3 4 5 First, Surface Datasets are loaded into the project. Although a Digital Elevation Model (DEM) is the only required data, rasters representing Land Cover, Depth, etc. may be included for good measure. Next, any supplemental data available is used to establish a more accurate study area. This material includes any existing infrastructure, land features, areas of importance, areas to be avoided, etc. Once all data to be analyzed for the area has been included, the constructability of the area is determined. This depicts the efficiency of building throughout the region. Well Pad Site locations are generated based on available lease boundaries and constructability. These locations include the pads, units, area searched, and lateral layouts. Finally, prior to generating any reports, all other results may be produced. Optional results include Pipeline Gathering System, Transmission Pipeline, Access Roads, etc. www.integrated-informatics.com

Geomancy Decision Engine YOU ARE HEREintegrated-informatics.com/templates/files/geomancy-scenarios.pdf · START Let's begin with optimized pipeline placement. Choose one of the scenarios

Embed Size (px)

Citation preview

Page 1: Geomancy Decision Engine YOU ARE HEREintegrated-informatics.com/templates/files/geomancy-scenarios.pdf · START Let's begin with optimized pipeline placement. Choose one of the scenarios

START Let's begin with optimized pipeline placement. Choose one of thescenarios below to see how the route might differ depending on the parameters. NEXT Now that a pipeline gathering system has been determined, it is timeto find the most efficient access road network by choosing one of the options below.

Scenario P-1 Connect Well Pad Sites to Well Pad Sites

Scenario P-2 Avoid Crossing Railway Network During Routing

Using the Well Pad Site locations shown at thebeginning of the quest, build a trenched pipelinenetwork based entirely on connecting this existinginfrastructure. This scenario is modeled after a Greenfield approach, where no consideration is given to any existing pipeline gathering system, roadways, or other assets. The proposed pipelinedepicts the most logical and efficient paths as determined by the location of sites and the constructability of the area. The constructability canbe seen in the underlying Full Solution raster where alternate paths are shown in blue while the level ofconstructability ranges from highly recommended (High) to not advised (Low). The white, or hollow, areas within the rasters represent those regions deemed impassible.

Scenario P-3 Avoid Construction in Areas Categorized as: Anthropogenic or Environmental

Scenario R-1 Connect Well Pad Sites to Well Pad Sites and to All Existing Roadways

Scenario R-2

Connect Well Pad Sites to Well Pad Sites and to All Existing Roadways (Avoid Crossing Railways)Scenario R-3

Connect Well Pad Site to Well Pad Site and to Major Roadways

Scenario R-4 Connect Well Pad Site to Well Pad Site (Only)

Scenario R-5 Connect Well Pad Site to Gravel and Secondary Paved Roadways

Scenario R-6 Determine Roadways Along Pipeline Gathering System

Using the predetermined Well Pad Site locations, build a pipeline network with the same principles as ScenarioP-1 in mind. Well Pad Sites should be connected to one another, as in the previous case. However, this situation requires that construction crossing railways is to be avoided at all costs. Because the railway runs in the middle of the path that would have been most likely tobe taken, the Geomancy Decision Engine was unable to connect the upper quadrant with the lower quadrant.Facilities will need to be located accordingly, or the planner will have to determine a new route out of the way of the system. If the Decision Engine were to be utilized for routing around the system entirely, the scopeof the study area would need to be much larger than was previously used. Other than the division of the pipeline gathering system as well as increased constructability in some regions, there are no significantdifferences between P-1 and P-2.

As was the case in the previous two scenarios, Well Pad Sites are to be connected to one another. It is presumedthat there is no existing pipeline infrastructure. For thisinstance, however, all areas that have been classifiedas either Anthropogenic or Environmental are to be removed as potential locations for construction. This data includes locations for Parks/Recreation, Populated Areas, Protected/Endangered Flora/Fauna, and Conservation Regions. Within the Decision Engine,these datasets are changed from a Weight Classification Method of Constant Weight to NoGo. Although the optimal projected path for the pipeline gathering system is not affected too drastically compared to the default Scenario P-1, the locations ofpreviously determined Well Pad Sites are another story.Three sites in the upper quadrant fall within the boundaries of an Environmental zone and had to be eliminated from the overall plan for this case.

Determine an efficient network of access roads thatconnect Well Pad Sites to one another as well as to all existing roadways. This includes Major Roads, Secondary Paved Roads, and Gravel Roads. By making use of the abundant infrastructure nearby, thisapproach ensures that the smallest amount of construction is required. Sites located within the same block are connected to one another and then to the nearest adjacent roadway.

Using the same principles as the previous scenario,connect Well Pad Sites to one another as well as toexisting road networks -- this time, connect to only MajorRoadways. This method may be ideal for those areas that have budding primary infrastructure, but do not yethave smaller networks. Rather than the resulting network seeking out the nearest roadways initially, it first connects sites in the closest proximity to one another before moving on to establishing a connectionwith existing infrastructure.

This instance follows the same guidelines as Scenario R-1. The main difference, however, is that any access roads generated must not cross railways. In some cases, this would drastically change the landscape ofresults generated by the Decision Engine -- such as seen in Scenario P-2. In this instance though, the onlynoticeable difference between this scenario and R-1is the Full Solution Raster. The area between the railway is eliminated from consideration of construction.In contrast, the access roads themselves do not seem to have been alterred by the avoidance parameter.

With the help of the pre-determined Well Pad Sites, findpotential locations for access roads that connect only the available sites. This scenario, similar to Scenario P-1,mirrors that of a Greenfield study. There is no existinginfrastructure, only site locations. Without similar restrictions for processing as were used in the previousaccess road examples, this case almost seems to visually mirror pipeline gathering system solutions shown before.

Determine an access road network that connectsindividual sites to either Secondary Paved Roadwaysor Gravel Roadways. This approach is suitable when Major Roadways are not viable options for connectorsand Well Pad Sites may be too far apart to warrantconnecting them together. What is interesting to note for this scenario is the lack of "least recommended", oryellow and red colored, regions portrayed in theFull Solution Raster. Because Well Pad Sites needonly be connected to existing roadways -- which aresparse in some areas -- the availability of constructablelandmass greatly surpasses those regions that wouldnot be sufficient candidates for placement.

The previous five situations were analyzed withoutneccessary consideration for either an existingpipeline gathering system or one to be placed in thenear future. This is not an unlikely occurance as oftentimes access to sites is needed ever prior to beginning construction of other features. Geomancy,also, has the ability to use the projected road networkas a consideration for pipeline placement. Likewise,it has the dexterity to do the reverse -- creatingaccess roads based on the existing pipelinegathering system. This scenario is an example ofthat. Using the pipeline network generated by Scenario P-1, roadways have been determined thatfall along the pipeline regardless of any other existinginfrastructure. The roads, of course, are shown in orange while the gathering system is striped.

An Adventure in Determining Smart, SustainablePipeline and Roadway Routes Using the

Geomancy Decision Engine

Well Pad Sites+ Pipeline Gathering System (Scenario P-1)

YOU

Upper Area Lower Area Upper Area Lower Area

Map Legend

TER_DEMValue High : 18233.1

Low : 8094.61

Pipeline Gathering System and Road Network Solutions:

Raster

Source Datasets

Scenario P-1Scenario P-2Scenario P-3Scenario R-1Scenario R-2Scenario R-3Scenario R-4Scenario R-5Scenario R-6

Pipeline Gathering System and Road Network Solutions:

Vector

There are a variety of datasets and sources that one may utilize to determine potential asset locations. The symbology that distinguishes those shown here can be found below by category in which the data is included.

Well Pad SitesRoadway - GravelRoadway - PavedRoadway - MajorRailwayHydrography - StreamsHydrography - WaterwayHydrography - WaterbodyAnthropogenic RegionsEnvironmental Areas

Depending on your situation, the assets you currently manage, and how far along your team is at in theplanning process, determining access roads to your facilities may be the next most logical step in your workflow. If so, proceed on in your journey. If not, please continue to the end of the quest to learn more about this optimization procedure.

You made it! As with any method used for optimizing the locations of assets -- whether they are Well Pad Sites, Pipeline Gathering Systems, or the like -- the results produced heavily depend on the area of study, supplemental data, and parameters utilized during site processing. Although the examples shown here are concise in that they merely highlight the production of pipelines and access roads, often times the planning process for a team entails many more features than just these.

Where is "here"? Here is the beginning of your journey, where you set out to find the most efficient and logical solutions to your field development needs in the least amount of time possible. Field development planning, on average, requires months to complete with the same amount of time dedicated to determining just one potential

route. With the typical approach, seemingly minor setbacks -- such as an expansion of the study area or theinclusion of supplemental data -- can cause not-so-minor issues, delaying the rate of production and

setting back deadlines. The Geomancy Decision Engine, however, helps to alleviate, or even eradicate, the need for such lengthy planning times. This ArcGIS toolset allows teams, or even a single user, to produce multipleresults in a fraction of the time, often hours or simply days. Geomancy comprises a system for the modeling and

analysis of field development at any point in the planning process. It utilizes a variety of weighted factors that represent physical features, survey information, environmental considerations, etc. of a specfied area to

optimize the placement of pipeline routes, roads, and facilities/wells.For this study, we will be finding solutions to pipeline placement as well as proposed access roads for the study area

below. To do this, Well Pad Site locations were created based on current lease boundaries. Each scenario shownhere is based on real-world cases that a team may encounter when planning infrastructure developement. These

include Greenfield scenarios, areas that are established, as well as regions that are undergoing development.Please use the center map as an overview of how parameter distinctions and individual situations may affect a route,even if it is based on the same premise. Scenario-specific maps, along with inset maps highlighting the Well Pad Site

connections in the Upper and Lower quadrants of the overview, can be found in each step.

OPTIMIZATION EXPLORATIONARE HERE

Well Pad Sites

Full Solution SurfaceValue High

Low

The flexibility of the tools avilable in the Geomancy Decision Engine allow the generation of these assets as well as Well Pad Sites (On and Off Lease), Transmission Pipeline, and 3D visualizations. Although these can be created based on datasets where the exact location is known, they can also be produced using generalizations. Specialized tools within the set offer the opportunity to draw features in approximate locations and then find results using this data as a source. This is helpful for situations where an area has been proposed for drilling, but the team is unsure what the overall outcome may entail. In addition to establishing a base solution, formatice solutions like those shown above are useful when back-casting or developing a plan for the system in its entirety, and then constructing individual sections intermittently. Regardless of the general outcome, however, the workflow remains a simple one. The steps shown to the right, as well as below, are those users typically take for Full Field Optimization.

Input SurfaceDatasets Input SupplementalDatasets DetermineConstructability DetermineWell Pad Sites GenerateAll Other Results

1 2 3 4 5

First, Surface Datasets are loaded into the project. Although a Digital Elevation Model (DEM) is the only required data, rasters representing Land Cover, Depth,etc. may be included for good measure.

Next, any supplemental data available is used toestablish a more accurate study area. This materialincludes any existing infrastructure, land features,areas of importance, areas to be avoided, etc.

Once all data to be analyzed for the area has beenincluded, the constructability of the area isdetermined. This depicts the efficiency of buildingthroughout the region.

Well Pad Site locations are generated based onavailable lease boundaries and constructability.These locations include the pads, units, areasearched, and lateral layouts.

Finally, prior to generating any reports, all otherresults may be produced. Optional results includePipeline Gathering System, Transmission Pipeline,Access Roads, etc.

www.integrated-informatics.com