Engineering with NeqSim

Engineering is a distinct NeqSim topic. Process simulation predicts how a modeled facility behaves. Engineering uses those results to establish governing cases, select dimensions and ratings, verify constraints, document assumptions, and prepare controlled deliverables for review and handover.

The software workflow for cases, iterative design, discipline calculations, safety evidence, coordinated packages, qualification gates, and revision impact is implemented. Individual methods and results remain preliminary or review-required unless the required project, vendor, independent-validation, safety-lifecycle, and authority evidence has been supplied and accepted for the declared purpose.

Start here

Resource	Use it for
Current Engineering Capabilities	The implemented APIs, discipline scope, qualification gates, deliverables, and lifecycle workflow available now
Engineering Guide	A practical, gated path from a validated process model to a review-ready package
Design Cases and Governing Envelopes	Controlled case definitions, metrics, isolated execution, limits, and governing-value selection
DEXPI Engineering Guide	Selecting, generating, validating, and qualifying DEXPI Plant, Process, Proteus, and pyDEXPI exchanges
Engineering Deliverables and Handover	Coordinated packages, registers, DEXPI, CFIHOS, approvals, manifests, and revisions
Engineering Simulator Foundations	Core concepts: isolated cases, provenance, readiness, uncertainty, and verification
Process-to-Engineering Simulator	Closed-loop case execution, sizing, application of selected dimensions, reruns, and convergence
Complete Offshore Engineering Study	A full-facility executed example with discipline calculations and handover artifacts

Engineering workflow

flowchart TD
    A["Validated process model"] --> B["Controlled design cases"]
    B --> C["Governing envelopes"]
    C --> D["Sizing and ratings"]
    D --> E["Hydraulic and dynamic reruns"]
    E --> F["Constraints and safety verification"]
    F --> G["Deliverables, review, and handover"]

The process model remains the physics source. Engineering calculations operate on isolated copies so selected design variables can be applied and evaluated without mutating the original model. The resulting package retains its input basis, governing case, method identity, units, warnings, uncertainty, constraints, and approval state.

Core API map

Purpose	Primary API
Governed project, design basis, standards, evidence, and approvals	`EngineeringProject`, `EngineeringDesignBasis`, `NorsokOffshoreEngineeringBuilder`
Executable cases and envelopes	`EngineeringDesignCase`, `EngineeringCaseRunner`, `EngineeringDesignEnvelope`
Closed process/design loop	`EngineeringDesignLoop`, `ProcessToEngineeringSimulator`, `ProcessToEngineeringDesignBuilder`, `EngineeringDesignModule`
Policy-driven discipline configuration	`EngineeringAutoConfigurationPolicy`, `EngineeringAutoConfigurator`
Typed discipline calculations	`EngineeringCalculationModule` and the calculation classes under `neqsim.process.engineering`
Canonical model and deliverables	`EngineeringGraph`, `EngineeringDeliverableCompiler`
Multi-area and shared-system execution	`ProcessModelEngineeringSimulator`, `EngineeringSharedSystemPolicy`
Controlled-pilot qualification	`ProductionVerticalSliceSimulator`, `ProductionVerticalSlicePreflight`
Production-readiness assessment	`EngineeringProductionReadinessAssessment`, `EngineeringProductionReadinessBasis`
Portable model package and revision impact	`NeqSimModelPackage`, `ModelChangeEvent`, `GeneralizedImpactAnalyzer`

Documentation by engineering activity

Basis, cases, and convergence

Topic	Documentation
Controlled case definitions and governing metrics	Design Cases and Governing Envelopes
Process design workflow	Process Design Guide
Explicit design framework and constraints	Design Framework
Isolated deterministic case execution	Engineering Simulator Foundations
Iterative sizing and process/design convergence	Process-to-Engineering Simulator
Numerical health and engineering closure	Numerical Health and Engineering Closure
Current implementation and workflow selection	Current Engineering Capabilities

Equipment and discipline engineering

Discipline	Documentation
Equipment and mechanical	Mechanical Design, Design Standards, Equipment Datasheets
Piping and pipelines	Topside Piping Design, Pipeline Mechanical Design, Piping Route Builder
Valves and instruments	Valve Mechanical Design, Instrument Design
Electrical and drivers	Electrical Design, Motor Mechanical Design
Wells and subsea	Well Mechanical Design, SURF and Subsea Equipment
Utilities and energy	Engineering Utilities, Exergy Analysis

Safety and operability

Engineering cases and dimensions must be checked together with the facility’s control and safeguarding response. NeqSim provides calculation and evidence structures for relief, blowdown, flare, ESD, HIPPS, SIS, dynamic safe-state verification, consequence analysis, and reliability. Scenario credibility, safeguards, SIL targets, and acceptance remain controlled engineering decisions.

Topic	Documentation
Safety systems	Safety Documentation
Risk, reliability, and SIS integration	Risk and Reliability
Governed scenario and design-loop integration	Process-to-Engineering Simulator
P&ID control and safeguarding synthesis	P&ID Design Synthesis
HAZOP, LOPA, and draft SRS traceability	HAZOP and LOPA to Draft SRS Handoff
NCS ESD/HIPPS verification	NOG-070, SIL, and STS-0131 ESD

Deliverables, exchange, and handover

Topic	Documentation
DEXPI workflow selection and qualification	DEXPI Engineering Guide
Package layers, issue workflow, and consumer checks	Engineering Deliverables and Handover
Canonical engineering graph and DEXPI	DEXPI Engineering Generation
End-to-end artifact and approval workflow	Process Model to Engineering Workflow
Controlled engineering data handover	CFIHOS 2.0 Engineering Handover
Controlled-pilot qualification	Engineering Production Vertical Slice
Evidence and production readiness	Process-to-Engineering Production Readiness, Industrial Method Qualification

Change management

A design is not complete when the first package is generated. NeqSim can retain revision identity, represent a model change as an event, traverse engineering dependencies, and identify calculations, documents, validations, and approvals that have become stale.

Topic	Documentation
Controlled change events	Model Change Events
Dependency-derived impact scope	Model Impact Analysis
Portable integrity-protected model packages	Process-to-Engineering Simulator
Revision-aware package generation	Process Model to Engineering Workflow

Executable learning path

Review Current Engineering Capabilities, then use the Engineering Guide to choose the appropriate workflow and gates.
Run the focused process_to_engineering_simulator.ipynb example for the closed design loop.
Run the complete_offshore_process_engineering_study.ipynb example to see a multi-discipline facility package.
Use the Process Model to Engineering Workflow when moving from a single ProcessSystem to governed multi-area delivery.
Run the engineering_production_qualification_workflow.ipynb before claiming that preliminary results are qualified for a controlled engineering purpose.

Engineering status boundary

NeqSim can calculate, organize, trace, and validate engineering evidence. It does not grant approval, make a HAZOP or LOPA decision, replace vendor guarantees, perform independent verification, or declare a design fit for construction. Production-readiness and handover contracts therefore fail closed when required evidence or accountable review is missing.