neqsim-pipeline-and-terminal-networks

Pipeline and Terminal Networks

When to use this

• Solve a gas gathering, ring-main, trunkline, or export network with fixed-pressure or demand boundaries.
• Optimize well IPR, choke, compressor, pump, regulator, or routing decisions already represented by network elements.
• Schedule pressure, rate, availability, and quality nominations over multiple periods.
• Track linepack and composition response to time-varying gas sources.
• Blend crude assays and schedule tank receipts, inventory, and cargo loading.
• Use the dedicated transient two-fluid network when the case needs gas-liquid pipe inventory states.

Do not substitute the field-development NetworkSolver or a Manifold for LoopedPipeNetwork without checking the question. They are distinct APIs. Use a Manifold for stream routing in a conventional process flowsheet; the network package solves its own node-edge model.

Well/SURF hydraulic fidelity

For campaign #4228, extend the detailed neqsim.process.equipment.network.LoopedPipeNetwork graph instead of creating a competing SURF solver. Review docs/fielddevelopment/SURF_NETWORK_INTEGRATION.md and coordinate equipment/design with neqsim-subsea-and-wells and the field-development agent. Use NetworkPipe.setHydraulicModelType for PIPE/MULTIPHASE_PIPE edge overrides (DARCY_WEISBACH, BEGGS_BRILL, TWO_FLUID); select NEWTON_RAPHSON and inspect getHydraulicModelStatus plus getTwoFluidModel().getSteadyStateConvergenceReport(). Changing fidelity preserves identity and geometry. This is steady-state composition; it does not qualify mixed-fidelity transients or directly bind a live WellSystem. Use NetworkHydraulicModelComparison to replay selected canonical edges with both Beggs-Brill and two-fluid hydraulics. Its normalized position/pressure/temperature/ holdup/phase-velocity profiles include segmented terrain routes, and compareMeshSensitivity evaluates selected edges on detached meshes without changing the caller topology. Inspect every convergence status and mass-balance residual; these comparisons are integration evidence until independently qualified. Use FieldNetworkTopology for stable production/injection node, edge, tag and port identity over that same graph. Its typed addChoke, addPump, addPumpDifferentialPressure and addCompressor methods create the existing canonical network elements atomically; they do not add a second solver. Rebind external equipment and fluids after JSON replay, and distinguish synthetic conservation/runtime evidence from qualified pump/compressor maps or field hydraulics. For screening design and cost, pass that same topology to SubseaProductionSystem.createSurfDesignBasis or estimateSurfCosts. The immutable FieldNetworkSurfDesignBasis reads typed equipment counts and exact canonical edge geometry without rebuilding hydraulics; the estimator prices physical line edges separately while retaining length-weighted summary getters. Use NetworkDecisionVariable.pipeDiameter with SubseaProductionSystem.createSurfCapitalCostObjective for deterministic all-discrete hydraulic/CAPEX screening. The optimizer rejects incomplete enumeration and mixed continuous/discrete searches. Register SURFCostEstimator.LineDesign by canonical edge ID with SubseaProductionSystem.setLineDesign when route-specific OD, wall, material, installation, rigid/flexible and insulation inputs are available. Rigid designs are checked against hydraulic ID and reuse existing pipeline mechanical screening; they are not current-edition DNV, vendor or AFC qualification. Use the typed LineDesign.insulation(MaterialType, thicknessMm) overload plus thermalBoundary for physical steady heat-transfer input, then call SubseaProductionSystem.applyLineThermalDesigns on the same topology. The legacy string insulation overload is cost metadata only. Flexible lines require an explicit qualified U-value. Add the returned createMinimumOutletTemperatureConstraints constraints to the existing optimizer; they fail closed without converged thermal state. Uniform design input must not replace an existing route-dependent U/ambient profile. Attach complete DnvStF101PipelineDesignInput and DnvRpF109OnBottomStabilityInput objects to LineDesign when structural and stability screening is required. Evaluate them with assessDnvStF101LineDesigns and assessOnBottomStabilityLineDesigns; all material, fabrication, load, environmental and soil values remain explicit project inputs outside the hydraulic topology. Treat results as review-required screening, never conformity, independent verification or AFC approval. For exact staged rigid-route studies, pass complete LineDesign alternatives to createLineDesignDecisionVariable and add createLineDesignScreeningConstraints to the existing NetworkOptimizer. One selection transaction updates canonical hydraulic ID, wall, thermal, material/installation/cost and attached screening input while preserving the edge hydraulic model. Candidate indices are categorical, minimum-temperature requirements must be invariant, and flexible/vendor designs are outside this contract. Never combine this selector with a second diameter variable on the same edge or treat a passing screen as qualified design. For coherent direct, brownfield and redundant-loop line-ups, register named FieldWellNetworkProcessUnit.RouteConfiguration options on the existing process-unit adapter. configuration.<selector>.selection is a categorical ProcessAutomation input: one write atomically assigns exact zero/one availability to the complete controlled edge set and preserves all per-edge hydraulic models. Do not emulate a multi-edge line-up with independent availability actions; that permits partial configurations during candidate application and restoration. The same selector works for live WellFlow injection networks. Update a zone's lifecycle boundary through WellFlow.ReservoirLayer.setReservoirPressure(...) so the layer pressure and its reservoir stream remain synchronized; do not change the public pressure field alone in a repeated coupled calculation. Register configured rotating-equipment maps with FieldNetworkTopology.addPumpWithCurve(...) and addCompressorWithChart(...) so the existing Pump/Compressor remains the chart owner under the canonical edge identity. ProcessModel.getPower(...) includes solved pump/compressor demand inside standalone LoopedPipeNetwork and wrapped FieldWellNetworkProcessUnit equipment; use that total for shared host-power evidence and fail closed on non-finite map results. Registration requires an enabled map before graph mutation, and a chart-backed compressor calculation failure must remain infeasible rather than falling through to simplified polytropic physics. Recheck chart availability and the equipment's solved() contract for every mapped calculation. Finite forward results from a failed pressure-target speed search are not accepted operating points; rejected results must invalidate power and clear stored thermal state. For repeated quasi-steady field-to-host studies, reuse the live model and evaluator but sample constraints again after each reservoir boundary or host-limit update. The ten-well FieldToFacilityOptimizationAcceptanceTest exercises moving separator, scrubber and shared-power limits without rebuilding topology or maps. Frozen evidence describes its original calculation only; it is not acceptance of a later period. Its mapped injection utility is not a live injector, and prescribed pressure steps are not a reservoir forecast. Use FieldWellNetworkProcessUnitTest for the separate live two-zone injection period case: synchronized layer/stream pressure updates, allocation and fracture checks, fresh shared-power rejection/recovery, and original-boundary rate/power restoration. Its shared-reservoir acceptance case also composes production and live injection with one SimpleReservoir. Keep reservoir advancement outside steady candidate evaluations: sample current host limits first, transfer the converged well rates (not the production inlet placeholder rate) to the reservoir streams, and advance inventory once per accepted period. Preserve identical ordered component slates for the reservoir's component-wise balance, and synchronize injection-layer pressures with the reservoir owner afterward. Do not also advance the same reservoir through a second network forecast. The example is a synthetic explicit quasi-steady conservation check, not a qualified forecast or liquid-injectivity law; persisted lifecycle revalidation remains owned by #4188/#3154. The dedicated TwoFluidPipeNetwork already owns storage-node transients; do not replace it. Live well/injection coupling must reuse WellSystem/WellFlow physics.