Neqsim Standards Lookup

NeqSim Standards Lookup

Reference for identifying, applying, and documenting industry standards compliance in every engineering task. All tasks — Quick, Standard, or Comprehensive — must identify applicable standards proportional to task depth.

Standards Identification (MANDATORY First Step)

Before any simulation or analysis, identify applicable standards:

Equipment → Standards Mapping

NeqSim's standards database is in src/main/resources/designdata/standards/. The index file standards_index.csv maps equipment types to applicable standards:

DNV-RP-F109 implementation status

EquipmentDesignKernelRegistry.lookup(StandardType.DNV_RP_F109) exposes a SCREENING kernel for the exact catalogued edition 2021-05+AMD 2025-09. It calculates vertical equilibrium and a transparent absolute-static lateral screen, or checks displacement supplied by an externally validated generalized or dynamic response model. It intentionally excludes licensed generalized-design tables, response generation, environmental-statistics derivation, soil-model qualification, and conformity assessment. Do not report a passing kernel result as DNV certification or clause-complete compliance; report the implemented check scope and retain engineeringApprovalRequired=true.

DNV-ST-F101 pipeline screening

For current DNV-ST-F101 requests, use neqsim.process.engineering.calculation.DnvStF101PipelineDesignKernel with a complete DnvStF101PipelineDesignInput. It preserves operating, incidental, and test pressure; collapse; propagation buckling; local-buckling load interaction; fatigue; temperature/material de-rating; safety class; ovality; fabrication route; and installation strain as distinct checks.

Do not route DNV-ST-F101 to PipeMechanicalDesignCalculator.DNV_OS_F101. That constant is the legacy DNV-OS-F101 screen. Missing structural inputs or unsupported editions must remain blocked, and a calculated result must retain CALCULATED_REVIEW_REQUIRED. Never describe a passing screen as certification or code compliance; require a licensed project copy and independent review.

See docs/process/dnv_st_f101_pipeline_screening.md and the neqsim-capability-map skill.

TR/NORSOK Integration Classes

NORSOK M-506 execution rule

For an explicit NORSOK M-506 calculation, prefer neqsim.process.engineering.calculation.NorsokM506CorrosionDesignKernel. It implements only the unamended 2017 edition, checks Pipeline / AdiabaticPipe / Pipe applicability, retains raw unit-explicit input values, and blocks unsupported or out-of-range cases before the mutable legacy calculator runs. Treat NorsokM506CorrosionAssessment.getProjectedUniformWallLossMm() as rate multiplied by exposure time, not as a specified corrosion allowance or acceptance decision.

The kernel is SCREENING: verify the purchased standard, wetting and water-chemistry basis, localized corrosion, sour service, inhibitor availability, materials selection, and project criteria independently. When feCO3SaturationRatio is enabled, report it as a NeqSim film-factor extension and retain the source chemistry evidence. Standards Norway's May 2026 systematic-review notice is the lifecycle source for the catalogued 2017 edition; do not silently apply this kernel to a later revision.

ISO 5167 execution rule

For an explicit ISO orifice-metering calculation, use neqsim.process.engineering.calculation.Iso5167OrificeMeteringKernel. The registered method supports only unamended ISO 5167-2:2022, paired with ISO 5167-1:2022. It requires an Orifice equipment basis, explicit liquid or gas/vapour service, a supported tapping arrangement, and affirmative single-phase/full-pipe/subsonic/non-pulsating and installation evidence before calculation.

Do not treat geometryAndInstallationVerified(true) as evidence created by NeqSim; retain the inspection and installation record. Keep uncertainty, calibration, straight lengths, plate condition, custody-transfer acceptance, and project metering procedure outside the kernel. Use Standard_AGA3 under an AGA 3/API MPMS 14.3 basis and do not relabel that result as ISO 5167.

DNV-RP-C203 execution rule

For an explicit DNV-RP-C203 basis, use neqsim.process.engineering.calculation.DnvRpC203FatigueDesignKernel. It supports the catalogued 2024-10 edition including amendment 2025-10, rejects additional project amendments, and is a SCREENING S-N/Palmgren-Miner calculation. The caller must supply and verify a controlled single-slope or continuous bi-linear curve, stress spectrum, SCF, thickness factor, other stress-range factor, design fatigue factor, damage limit, and exposure.

Do not copy licensed curve tables into NeqSim and do not infer that a verification Boolean is the evidence itself. Retain curve/detail selection, environment, fabrication, thickness, weld and SCF basis, structural stress derivation, load combinations, rainflow counting, inspection plan, and accountable approval externally. The older pipeline/riser fatigue methods have inconsistent embedded intercepts and remain legacy estimates, not exact-edition C203 calculations.

DNV-RP-F105 execution rule

For an explicit DNV-RP-F105 basis, use neqsim.process.engineering.calculation.DnvRpF105FreeSpanScreeningKernel. It supports only the catalogued unamended 2025-12 edition for Pipeline and AdiabaticPipe. The kernel evaluates a simply supported Euler-Bernoulli first mode with caller-supplied effective modal mass and axial force, then reports current/wave frequency ratios, reduced velocities, and Keulegan-Carpenter number. Steel outside diameter and hydrodynamic diameter are separate inputs.

Treat the geometry, structural-model, environmental, and project-trigger verification Booleans as attestations whose evidence must be retained externally. Strouhal number, frequency-ratio band, and reduced-velocity limits are caller-controlled escalation triggers, not embedded DNV requirements or acceptance decisions. Keep soil/shoulder stiffness, interacting spans, detailed in-line/cross-flow VIV and direct-wave response, ULS/FLS, fatigue, monitoring, intervention, and conformity open.

PipeMechanicalDesignCalculator.calculateAllowableSpanLength(...) is a legacy fixed-assumption estimate with fallback and cap behavior. Never report that output as current-edition F105 evidence.

DNV-RP-F101 execution rule

For an explicit DNV-RP-F101 basis, use neqsim.process.engineering.calculation.DnvRpF101CorrodedPipelineScreeningKernel. It supports the catalogued 2019-09+AMD:2025-09 edition and only calculates the deterministic isolated longitudinal metal-loss equation under internal pressure. Require externally verified assessment wall thickness, measured defect depth and length, caller-controlled depth allowance, characteristic ultimate tensile strength, internal/external pressures, caller-controlled pressure factor, and isolated-defect applicability.

Treat every verification Boolean as an attestation, not the evidence itself. Keep inspection accuracy and growth derivation, factor selection, interacting/complex defects, combined longitudinal compression, probabilistic methods, crack/dent/gouge/blister or weld damage, repair, fitness-for-service acceptance, and accountable approval external. Do not turn NorsokM506CorrosionAssessment.getProjectedUniformWallLossMm() into RP-F101 defect dimensions.

RP-F101 remaining-strength screening is not DNV-ST-F101 original design. It does not replace pressure containment, collapse, propagation buckling, local buckling, load interaction, fatigue, incidental/test pressure, de-rating, safety class, ovality, fabrication route, or installation strain checks.

DNV-RP-F104 execution rule

For an explicit current DNV-RP-F104 2021-02+AMD:2021-09 basis, use DnvRpF104Co2PipelineEnvelopeScreeningKernel. Require verified project CO2/water limits, other-impurity status, composition/EOS basis, the minimum-pressure interpretation and uncertainty of each supplied single-phase boundary, an ordered operating profile, MAOP, design temperatures, and external integrity/lifecycle review evidence. Negative margins remain calculated findings; missing evidence blocks execution.

Use StandardRegistry.requireRequirementPack(StandardSelection.strictRequirements( StandardType.DNV_RP_F104)) to discover related thermodynamic, hydraulic, corrosion, mechanical, monitoring, and consequence capabilities. The pack does not prove clause coverage. Do not substitute the pure-CO2 critical point, CO2FlowCorrections.isDensePhase(...), or embedded DensePhaseCO2Corrosion values for the project basis. F104 does not replace DNV-ST-F101 structural design or the external fracture, materials, corrosion, construction, safety, operation, and requalification assessments.

DNV-RP-F114 execution rule

For an explicit current DNV-RP-F114 2021-05 basis, use DnvRpF114PipeSoilInteractionScreeningKernel. Supply positive pipe diameter and submerged weight, then named route/design-situation cases with externally established non-negative vertical, axial, and lateral demand magnitudes and positive resistance magnitudes on a consistent N/m basis.

Require external evidence for applicability, site investigation, soil interpretation, pipe/interface configuration, installation history, cyclic/drainage/rate/consolidation effects, load-displacement and resistance models, uncertainty/spatial variability, design actions and acceptance criteria, and lifecycle interfaces. A negative margin remains a calculated finding. Never derive F114 resistance from NeqSim soil thermal conductivity, burial heat-transfer inputs, a generic friction coefficient, or submerged weight alone. Keep F109 on-bottom stability, F110 global buckling, F105 free spans, ST-F101 structural design, and conformity external.

DNV-RP-F110 execution rule

For an explicit current DNV-RP-F110 2019-09+AMD:2021-09 basis, use DnvRpF110GlobalBucklingResponseScreeningKernel. Supply positive pipe diameter and structural wall thickness, then named route/design-situation cases containing externally analysed effective force, peak longitudinal strain, peak global displacement, and required feed-in length together with caller-controlled allowable or available values.

Require external evidence for applicability, operating envelope/effective force, pipe properties and as-laid geometry, pipe-soil interaction, imperfections/triggers/design strategy, global structural model, design situations/load combinations, local capacity/strain criteria, uncertainty/sensitivity/buckle sharing, and lifecycle actions. A negative margin remains calculated. Never interpret the force limit as a NeqSim-derived critical-buckling or initiation criterion. Keep F109/F114/F105, every DNV-ST-F101 check, conformity, and accountable approval external.

API 2000 execution rule

For an explicit API 2000 basis, use neqsim.process.engineering.calculation.Api2000TankVentingScreeningKernel. It supports only the catalogued unamended 7th Ed for caller-verified non-refrigerated fixed-roof Tank or SimpleTankFiller service. Supply maximum filling/withdrawal rates, caller-controlled movement ratios, externally established thermal/other normal demands, total emergency demand, rated normal/emergency capacities, their rated pressure/vacuum conditions, tank limits, and one common gas-volume reference state.

Treat the evidence Booleans as attestations, not proof. Keep API demand tables/equations, scenario derivation, vent area and device selection, manufacturer curves, pressure losses, flame arresters, blanketing, external floating roofs, refrigerated storage, installation/testing, and conformity external. An adequate caller-controlled constraint result is not API compliance.

Use these Java classes when a task references Equinor technical requirements, STS0131, TR1965, TR2237, or NORSOK P-002:

TR1965 Gas Scrubber Pattern

GasScrubber scrubber = new GasScrubber("inlet scrubber", feed);
scrubber.run();
scrubber.initMechanicalDesign();
GasScrubberMechanicalDesign design = scrubber.getMechanicalDesign();
design.setInnerDiameter(2.0);
design.setMeshPad(3.0, 100.0);
design.setLaHHElevationM(0.5);
design.setInletDeviceElevationM(1.2);
design.setMeshPadElevationM(2.3);
design.setLiquidEntrainmentLitresPerMSm3(5.0);
design.setLiquidDesignMarginFraction(0.25);
design.setConformityRules("TR1965");
ConformityReport report = design.checkConformity();

STS0131 Blowdown Acceptance Pattern

DepressurizationResult blowdown = simulator.run();
STS0131AcceptanceCriteria criteria = new STS0131AcceptanceCriteria()
  .setTimeToEscapeS(120.0)
  .setEstimatedTimeToRuptureS(300.0)
  .setMaximumPressureAtRuptureBara(15.0)
  .setMaximumRemainingMassKg(500.0)
  .setMaximumEscalatedFireRateKgPerS(2.0);
STS0131AcceptanceResult acceptance = blowdown.evaluateSTS0131(criteria);

Database Query Pattern (Java)

// Query standards values for a specific equipment type
import neqsim.util.database.NeqSimProcessDesignDataBase;
import java.sql.*;

try (Connection conn = NeqSimProcessDesignDataBase.createConnection()) {
    String sql = "SELECT * FROM api_standards "
               + "WHERE EQUIPMENTTYPE = ? AND STANDARD_CODE = ?";
    PreparedStatement stmt = conn.prepareStatement(sql);
    stmt.setString(1, "Separator");
    stmt.setString(2, "API-12J");
    ResultSet rs = stmt.executeQuery();
    while (rs.next()) {
        String spec = rs.getString("SPECIFICATION");
        double minVal = rs.getDouble("MINVALUE");
        double maxVal = rs.getDouble("MAXVALUE");
        String unit = rs.getString("UNIT");
    }
}

Database Query Pattern (Python / Jupyter)

# Query via mechanical design classes
separator.initMechanicalDesign()
design = separator.getMechanicalDesign()
design.setDesignStandardCode("NORSOK-P-001")
design.setCompanySpecificDesignStandards("OperatorA")
design.readDesignSpecifications()
design.calcDesign()
print(design.toJson())

CSV Column Reference

All standards CSV files share this schema:

results.json — standards_applied Schema

Every task's results.json should include a standards_applied array:

"standards_applied": [
  {
    "code": "NORSOK P-001 Rev 5",
    "scope": "Separator sizing — K-factor and retention time",
    "status": "PASS",
    "design_value": 0.13,
    "limit": "0.12–0.15 m/s",
    "unit": "m/s",
    "clause": "Table A-1"
  },
  {
    "code": "API 617 8th Ed",
    "scope": "Compressor surge margin",
    "status": "PASS",
    "design_value": 12.5,
    "limit": ">10%",
    "unit": "%",
    "clause": "Section 2.6"
  },
  {
    "code": "DNV-ST-F101",
    "scope": "Pipeline wall thickness",
    "status": "INFO",
    "design_value": null,
    "limit": null,
    "unit": null,
    "clause": "Not applied — onshore pipeline"
  }
]

Required Fields

Status Values

Risk & Safety Standards Quick-Reference

Risk Assessment (ISO 31000 / NORSOK Z-013)

NeqSim classes in neqsim.process.equipment.failure:

Safety Instrumented Systems (IEC 61508 / IEC 61511)

Fire & Depressuring (API 521)

Risk Proportionality by Task Scale

Gas Quality Standards

NeqSim has extensive gas quality standard implementations in neqsim.standards.gasquality:

Oil Quality Standards

In neqsim.standards.oilquality:

Typical Standards by Task Type

Type A — Property Calculation

• ISO 6976 (gas properties), GERG-2008 (compressibility)

Type B — Process Simulation

• NORSOK P-001 (process design), API 12J (separators), API 617 (compressors), TEMA (heat exchangers)

Type C — PVT Study

• ISO 6976, GPA 2145, ASTM D86/D2887 (oil characterization)

Type D — Standards Compliance

• Direct application of the requested standard

Type E — Feature Implementation

• Standards that the new feature must implement

Type F — Mechanical Design

• ASME VIII (vessels), DNV-ST-F101 (subsea pipe), NORSOK L-001 (piping), API 5CT (casing)

Type G — Workflow / Field Development

• NORSOK Z-013 (risk), ISO 31000 (risk management), NORSOK P-001 (process), company TRs

Post-Simulation Standards Check Pattern

After running a process simulation, check key results against standards:

# Example: Check separator K-factor against NORSOK P-001
k_factor = separator.getInternalDiameter()  # Get from results
# Look up limit from standards database
if k_factor < 0.12 or k_factor > 0.15:
    print("WARNING: K-factor outside NORSOK P-001 range (0.12-0.15 m/s)")
    standards_status = "FAIL"
else:
    standards_status = "PASS"

Workflow Integration

1. Phase 0 (Setup): Identify task type → look up applicable standards from mapping table above
2. Phase 1 (Scope): List standards in task_spec.md under "Applicable standards"
3. Phase 2 (Analysis): Use standards values as design inputs and validation limits
4. Phase 2 (Results): Populate standards_applied array in results.json
5. Phase 3 (Report): Standards compliance table auto-rendered in Word/HTML report