ENGIN Solver · Deterministic engineering computation | ENGINPILOT
PLATFORM / 04 — ENGIN SOLVER

Deterministic computation, so the answer is the same every time you ask.

ENGIN Solver evaluates governing engineering relations against the asset record. It returns a number, the equation that produced it, the inputs it used, and the uncertainty around it — the same evidence an engineer would attach to a hand calculation.

STATUS DESIGN PARTNER · PUMP AND THERMAL RELATIONS DEMONSTRABLE
METHOD
Governing equations, not fitted curves
DIMENSIONS
Checked at parse time
UNCERTAINTY
Propagated, never discarded
OUTPUT
A result plus its derivation
01 — THE CALCULATION RECORD

A result is never delivered alone

Every solver call returns a record, not a value. The record names the relation, cites its reference, lists the inputs with their own provenance, and stamps the result. An engineer can reconstruct the calculation by hand from what is on the screen.

02 — MODEL LIBRARY

Published relations, each with a citable reference

The library holds established engineering relations, not learned approximations. A relation is admitted only with a reference an engineer can look up and a stated range of validity.

DOMAIN
RELATION
REFERENCE
RANGE OF VALIDITY
Rotating
Affinity laws · Q ∝ N
ISO 9906
±20% of rated speed
Thermal
ε-NTU effectiveness
ASHRAE Handbook
Single-phase, no fouling step
Fluid
Darcy–Weisbach
Crane TP-410
Re > 4,000
Structural
Miner's rule accumulation
ASME BPVC VIII-2
Elastic regime only
Electrical
Motor loss segregation
IEEE 112 Method B
Balanced supply, >25% load
03 — DIMENSIONAL SAFETY

A unit error fails loudly, not quietly

Every quantity in the solver carries its dimensions. A calculation that mixes bar with kPa, or head with pressure, is rejected before it runs. The alternative — a plausible wrong number, correctly formatted, delivered with confidence — is the failure mode that costs equipment.

The rejection names the offending term and the dimensions that clashed, so it is a diagnosis rather than an error code.

// duty point check · CH-02 chilled water pump
H_required = dp / (rho * g)
dp = 2.43 bar
rho = 997 kg/m³
g = 9.81 m/s²
→ 24.8 m · dimensions consistent
// same expression, kPa substituted silently
H_required = dp / (rho * g)
dp = 243 kPa
→ REJECTED AT PARSE
term dp resolves to kPa
relation declares bar
no implicit conversion applied
04 — UNCERTAINTY

Near a limit is reported as near a limit

Measurement uncertainty propagates through every step of the calculation. When the resulting band touches a constraint, the solver says so — it does not round to a comfortable single figure and let the engineer assume margin that is not there.

CLEARBand sits wholly inside the limit — reported as a value
NEARBand touches the limit — reported as indeterminate against it
BREACHBand sits wholly beyond — handed to PhysicsNET as a violation
05 — REPRODUCIBILITY

Every result is pinned to what produced it

Re-running a calculation from two years ago returns the two-year-old answer, because the solver version, the relation revision and the input snapshot are all part of the record. A result that cannot be reproduced is not evidence.

SOLVER VERSION
2.8.1

Pinned per calculation. Upgrades never rewrite past results.

RELATION REVISION
ISO 9906 · r3

Superseded revisions retained so old work stays reconstructable.

INPUT SNAPSHOT
SNAP-88214

The exact sensor values and asset state at the moment of the call.

DETERMINISM
BIT-EXACT

No sampling, no seeds, no drift between runs.

06 — WHERE IT SITS

Layer four of seven

The solver computes. It does not decide. Everything it produces continues upward into PhysicsNET for validation before it can reach an engineer as a recommendation.

RECEIVES FROM
Digital twin — current asset state EIG — design basis and geometry Telemetry — measured inputs with tolerance
EMITS TO
PhysicsNET — candidate actions Digital twin — reconciled state Calculation record — full derivation
GUARANTEES
Deterministic — no stochastic component Dimensionally checked before execution Reproducible against any past snapshot

Run the solver against a calculation you already trust.

Technical evaluations usually begin by reproducing an existing hand calculation, so the derivation can be checked line by line against work your team already signed.