neqsim-production-network-routing

Screens well rates and arrival pressures for production networks routing wells through manifolds to a host.

4|2|Updated May 31, 2026
One-click install
npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-production-network-routing-equinor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neqsim-production-network-routing
Source: https://github.com/equinor/neqsim-community-skills/tree/main/skills/subsea/production-network-routing
Command: npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-production-network-routing-equinor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers and agents often need a quick, transparent first estimate of how wells flow through manifolds and flowlines to a host platform before committing to detailed multiphase simulation. This Skill provides a dependency-free screening that estimates per-well rates, aggregates manifold rates, and rolls up a host arrival pressure with clear warning flags. ## Core Features & Use Cases - Network Arrival-Pressure Roll-Up: Computes per-well rates via a linear productivity-index inflow, aggregates rates by manifold, and checks arrival pressure against a required minimum with ok/watch/high warnings. - Pressure-Regulated Multiwell Flow: Solves each well's rate from a fixed facility inlet/separator pressure and reservoir pressures, mirroring the NeqSim WellFlowlineNetwork target-endpoint-pressure pattern. - Use Case: Given two wells routed to one manifold with an 8 km flowline and a 90 bara arrival requirement, run the model to get total network rate, minimum arrival pressure, and an overall verdict before escalating to NeqSim PipeBeggsAndBrills for real multiphase hydraulics. ## Quick Start Ask the agent to screen a production network with your well and manifold data and a required arrival pressure, for example: route WELL-A and WELL-B through MANIFOLD-1 to the host and check whether arrival pressure meets 90 bara.

Frequently Asked Questions about neqsim-production-network-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate well flow rates from reservoir pressure and productivity index?▼

Use a linear productivity-index inflow where rate equals PI times the drawdown between reservoir pressure and flowing bottomhole pressure. The ProductionNetworkModel computes this per well and flags wells with no drawdown as high severity.

How do I check if a flowline arrival pressure meets a platform requirement?▼

Subtract the flowline pressure drop (gradient times length) and riser pressure drop from the manifold collection pressure, then compare against the required arrival pressure. Margins below zero flag high, below 10 percent of the requirement flag watch.

Can this screening replace NeqSim multiphase flow simulation?▼

No. It is an educational placeholder with no real IPR, multiphase hydraulics, phase split, or thermal calculation. Any quantitative or design use must be escalated to NeqSim PipeBeggsAndBrills, SimpleReservoir, or the MCP runPipeline and runProcess workflows.

Does the production network screening require NeqSim or other dependencies?▼

No. The model is pure Python with no required packages and runs on Python 3.10 or later. It only reports whether the optional neqsim package is importable via the neqsim_available output flag.

How do I model multiwell flow regulated by a separator inlet pressure?▼

Call regulate_flow_from_inlet_pressure with a target inlet pressure and each well's reservoir pressure and productivity index. Each well's flowing bottomhole pressure is the inlet pressure plus a screening sum of segment pressure drops, and rates follow from the linear inflow.

What are the limitations of a screening-level production network model?▼

It assumes linear inflow, a fixed pressure gradient for flowlines, and the lowest well tubing-head pressure as the manifold pressure. It performs no phase split, temperature, or hydrate checks, so results are only valid as a first-pass screening within stated input ranges.