Mechanical Design Standards in NeqSim

NeqSim catalogs standards that may be relevant to process-equipment design. Catalog inclusion is not a statement that every requirement or calculation in a published standard has been implemented. The matrix below reports the calculation evidence that currently exists in NeqSim.

Maturity definitions

Maturity	Meaning
`CATALOGUED`	Standard identity, edition metadata, category, and equipment applicability are available, but no standard calculation is exposed.
`SCREENING`	A preliminary engineering calculation is available with the boundary stated in the matrix. It is not a conformity assessment.
`VALIDATED`	The stated calculation range has independent numerical validation and controlled regression evidence.
`QUALIFIED`	A controlled implementation and evidence package has been released for a stated use. Accountable engineering approval is still required.

No current entry is classified as VALIDATED or QUALIFIED. Existing calculations remain useful for preliminary screening, but project criteria, purchased standards, vendor data, and engineering review remain governing.

Current support matrix

The table between the generated markers is produced by StandardSupportAudit.generateMarkdownTable(). A regression test fails if the published table and the source catalog diverge.

Typed standard selection

New code can select an explicit edition and any project amendments without depending on the registry’s process-wide version overrides:

StandardEdition edition = StandardEdition.of(StandardType.API_12J, "8th Ed",
    Arrays.asList("Project amendment A", "Corrigendum 1"));
mechanicalDesign.setDesignStandard(StandardSelection.strict(edition));

Strict selection fails closed with a StandardSelectionException when the entry is catalog-only, its calculation is not connected to the registry, the equipment context is missing, or the standard is not listed for that equipment type. The exception exposes a machine-readable reason so applications do not need to parse its message. StandardRegistry.assessApplicability(...) provides the same applicability decision without creating a standard.

StandardSelection.legacy(...) is available for migrations that need an explicit edition while retaining the permissive factory behavior. It may create a metadata-only DesignStandard; it does not add calculation support.

Process-global setVersionOverride(...) and clearVersionOverrides() are deprecated. New code should retain a StandardEdition in each StandardSelection, then call StandardRegistry.requireDesignKernel(selection) when an executable implementation is required. The require call distinguishes missing kernel support from an unsupported edition. See the typed-kernel migration guide for a staged compatibility path.

Consolidated design kernels

EquipmentDesignKernel<I, O> extends the existing typed engineering-calculation contract with the implemented standard, audited maturity, and structured applicability. Kernels must not mutate their input or a ProcessSystem. Compatibility adapters defensively copy legacy mutable calculators.

StandardRegistry.getDesignKernel(...) returns an explicit lookup status. API 617, API 610, API 521, API 526, and API 12J have connected adapters and return IMPLEMENTED; standards that have not been adapted return NOT_IMPLEMENTED, never an empty or implied success. Each kernel returns an immutable assessment snapshot and always requires engineering review because its maturity remains SCREENING. Unsupported editions fail closed as EDITION_NOT_IMPLEMENTED until separately implemented and validated.

The API 521 adapter defensively copies the mutable protected-item basis, requires at least one complete credible scenario, selects the governing rate, and records the sizing and accumulated pressure checks. The API 526 adapter accepts an explicitly unit-tagged required area and reports an inadequate result when a single standard orifice cannot cover it. These adapters do not establish scenario completeness or qualify valve construction, installation, reaction loads, flare-network effects, or vendor certification.

The API 617 adapter defensively copies a compressor-casing configuration before evaluating pressure containment, hydrotest, flange-rating, nozzle-load allowance, and thermal-growth screens. The API 12J adapter uses explicitly unit-tagged cut diameter together with K-factor and liquid residence time. Passing either result is not a package, vessel, or performance certification.

How to interpret the registry

StandardRegistry.createStandard(...) remains backward compatible. The factory class shown in the matrix records what it currently creates; it does not prove that the resulting class implements the selected edition. StandardRegistry.getMappedImplementationClass(...) allows applications and audits to inspect that mapping without constructing equipment or accessing the design database.

The API 610 pump screen remains available through PumpMechanicalDesign. The consolidated PumpApi610DesignKernel is a pure adapter over the same calculator, so existing callers are not removed or redirected. The generic legacy factory still creates a base DesignStandard; executable kernel support is exposed explicitly through StandardRegistry.getDesignKernel(...).

Engineering boundary

Treat CATALOGUED entries as discovery metadata only.
Treat SCREENING results as preliminary design information with the stated boundary.
Do not infer certification, code compliance, vendor acceptance, or construction readiness.
Record the purchased edition, project amendments, input provenance, and accountable approval outside the current legacy registry.

See the engineering capability statement for the broader process-to-engineering workflow and its qualification boundary.