Designer handbook

MDCX ships two Designers that share physics and solution identity: Liquid Cooling (cold-plate) and Immersion Cooling (tank). This page is the operator guide — open a published solution code, configure, then hand off to TCO or USD packages.

1. Which Designer

Every published code loads its own Designer profile — rack count, loop topology, branch flows and 3D geometry all follow ?code=. A future draft code appears as Coming soon on the line overview only; the public Designer refuses to load a draft profile until Admin Publish.

2. Deep links

Minimum required query field: code. Alias is optional convenience.

• /design/liquid?code=L1240C45SUR150
• /design/immersion?code=I400C40ST50
• /tco?code=L1240C45SUR150 — after TCO, primary CTA returns to Designer with the same code.

3. Calculation path

One path only — do not invent parallel calculators:

1. UI updates store state
2. Store holds inputs (IT, cooling, site)
3. EnginecalcAll(input) produces the snapshot
4. Physics shared package @mdcx/physics supplies pure formulas

3D and charts read the engine snapshot only. Catalogs load from monorepo city-data/ and gpu-data/ via adapters.

4. Recommended workflow

1. Pick a solution on product matrix or marketing overview.
2. Run TCO for site economics (city, quantity, utilization).
3. Open Designer from the TCO next-step CTA (carries ?code=).
4. Tune racks / tanks / climate assumptions; review thermal and power tabs.
5. Download reference USD packages from the product page when needed — see USD output spec.

5. Limits & claims

• Marketed numbers must match the claims registry — Designers show engineering targets, not new claims.
• No public pricing in Designers; commercial quotes go through account managers / TCO scenarios.
• PWA install for the Liquid Designer uses the canonical path /design/liquid/.