The core desalination technology of the platform: a semi-permeable membrane driven by pressure, with recovery, salt rejection, energy and concentrate all derived by real engines.
- Active
- Available
Save, organize and restore your calculations.
Keep sync and organize your saved records.
Skid-packaged desalination sized from a stated duty and a stated membrane basis: product demand, feed and concentrate by salt conservation, and the array that carries the design flux. A packaging architecture, not a different process — the membranes are still RO.
Skid-packaged desalination sized from a stated duty and a stated membrane basis: product demand, feed and concentrate by salt conservation, and the array that carries the design flux. A packaging architecture, not a different process — the membranes are still RO.
This entry describes an application and packaging architecture. The treatment process inside it is documented separately — see the related technologies below. Nothing on this page states a standard capacity, because capacity follows from the design basis rather than from the packaging.
Separation mechanism and feed window. Inherits RO feed compatibility exactly. A small plant on a feed a large plant could not treat will not treat it either — the package changes the footprint, not the separation.
What the process produces. Product flow and quality follow the stated duty and the stated product TDS target. No recovery, flux, staging or envelope is chosen by the tool.
Energy. High pressure, same as RO. A smaller array is not a lower-energy process.
Where this technology normally sits in a treatment train. The steps either side of it are documented in the Library as separate entries.
The parameters an engineer actually sets, and why each one drives the design. EngiMetric does not assume any of them.
| Parameter | Why it matters |
|---|---|
| Community demand basis or a direct product flow | One or the other. Neither is defaulted, because a guessed population fabricates the whole chain. |
| Feed TDS and product TDS target | Salt conservation and the required rejection both need them. |
| Plant recovery | Splits the feed into product and concentrate. Your decision. |
| Design flux, element area, elements per vessel, array stages | The membrane basis. Nothing here is assumed to be a typical value. |
Industry maturity and commercial status describe the technology itself. EngiMetric support and quantitative modeling describe what this platform does with it — and those two are read from the engineering registry at build time, so they cannot drift from the code.
These capabilities are registered in the EngiMetric execution registry. Each one runs a deterministic engine, so every result is reproducible from the inputs you supply.
Every tool below exists and is live. EngiMetric does not duplicate a formula here — the calculation lives in the tool, and this page links to it.
Demand-first: the plant is sized from the duty you state, and the sizing composes the existing demand, mass-balance and array engines rather than repeating their formulas.
EngiMetric does not model the packaging itself — there is no container, skid or transport model in the Plant Designer. What the designer carries is the contained treatment process, configured exactly as it would be for a central plant.
EngiMetric does not publish a bibliography of external literature for catalogued technologies. Where a figure is required, it is entered by the engineer from a datasheet or a published reference, and it is labelled as an input.