High Pressure Low Pressure Routing

summary netx's high pressure low pressure routing scenarios enable rapid screening of constraned well to separator routing options to enable a rapid solution, pressure drops across surface lines and variable choke settings are not considered solution fundamentals and methodology netx wells are connected to wells modeled in prodx, and when a scenario is ran, the foundational vlp/ipr will be taken from the most recent day of production wells can be configured to be fixed (i e leave the well at it's current routing / wellhead pressure) or optimize (i e allow the routing / wellhead pressure of the well to change during optimization) the optimization's objective function is maximizing cash flow, which is based on the wells' optimization settings in prodx wells which are shut in or cannot compute vlp/ipr for the latest day will be held constant with the values reported in docid\ jnogjwoaowkpzzaho3pkp separators are configured with operating pressures which translate directly to the wellhead pressures used in vlp sensitivities the initial well routing is assumed to be what is defined in the scenario's topology all wells will compute nodal analysis at all separator operating pressures configured in the network, but the final routing and deltas are based off of the scenario's original topology 1 to n separators can be configured in the network typically at least two (high pressure and low pressure) make the most sense however, there is some utility in configuring a single compressor network to evaluate constrained operation to decide if any wells should be shut in separators have constraints for max oil rate, water rate, liquid rate, and gas rate that will be strictly considered during optimization any wells exceeding these constraints across the possible solution will be shut in by the optimizer (while maximizing cash flow) the well > separator routing problem is solved using scip ( https //www scipopt org/ potential drawbacks in reality, there is pressure drop between the well and separator, which is ignored in this scenario type this scenario type ignores any flexibility to manage well performance by manipulating choke position