Home / PRD / CDU Mini-BMS
Product requirements · liquid-cooling controls simulator

CDU Mini-BMS

A verifiable product contract for the five CDU architectures, thirteen signal tiles, six coherent scenarios, P&ID interaction and operator-learning workflow in cdu-mini-bms.html. The cockpit is an engineering simulator, not a live controller or approved cause-and-effect matrix.

Architectures 5Signals 13Scenarios 6Data mode SIMULATED

01 Purpose & problem

Liquid-cooling operators must correlate a plant symptom with its physical path and dependent signals. A static P&ID explains topology; a point list shows values. This cockpit combines them without implying field connectivity.

Outcome

Let a user select an architecture, observe a stable baseline, inject one bounded fault, trace propagation, and state an appropriate investigation sequence.

Product truth

Every displayed value is attributable to a type baseline, scenario delta or labelled derived formula. Simulation, limitations and source basis stay visible.

02 Users & decisions

PersonaDecision supportedPrimary evidenceSuccess
Critical-facility operatorIdentify the first safe investigation path.Alarm banner, affected tiles, P&ID state.Names cause, consequence and next inspection.
Liquid-cooling engineerCompare placement/capacity architectures.Type selector, capacity, flow, temperature and pressure basis.Separates architecture inputs from dynamic readings.
Commissioning engineerTurn behavior into deterministic checks.Signal mapping, scenarios, pause/step and reset.Reproduces every AC without private knowledge.
LearnerUnderstand CDU fault propagation.Guided walkthrough and Manual formulas.Explains why multiple readings move together.

03 Scope & non-goals

In scope

  • In-rack, in-row, sidecar, L2L end-of-row and L2A baselines.
  • Thirteen instrument/state tiles and linked P&ID bubbles.
  • Normal, leak, pump failure, filter clog, hot-water and low-flow scenarios.
  • Trend drill-down, guided walkthrough, pause, step, speed and reset.

Non-goals

  • No BACnet/Modbus/PLC connection or write-back.
  • No pump curve, hydraulic network, fluid-property or HX sizing solver.
  • No vendor alarm set-points or safety trip authority.
  • No historian, acknowledgement, work order or audit trail.

04 Functional requirements

IDRequirementDeterministic check
FR-01Expose five CDU type selectors.Each selection changes caption and all authored type baselines together.
FR-02Expose six scenario selectors.Exactly one has aria-pressed=true; Normal is reset state.
FR-03Declare the cockpit as simulated.Visible copy and machine-readable data mode agree.
FR-04Render facility and technology loops on one P&ID.HX, pumps, filter, manifold, racks and sensor tags remain labelled.
FR-05Bind thirteen tiles to stable tag IDs.Tile label, unit, reference band and value are present.
FR-06Derive total flow from specific flow and capacity.FT-01Σ equals LPM/kW × kW within display rounding.
FR-07Derive return temperature from supply plus ΔT.TT-02 arithmetic matches the Manual.
FR-08Evaluate every numeric tile against its declared band.NORMAL/WARN/ALARM text accompanies color.
FR-09Let explicit scenario state override a conflicting numeric band.Leak and filter states latch on their dedicated tiles.
FR-10Set overall state to the worst active tile severity.ALARM outranks WARN, which outranks NORMAL.
FR-11Show coherent leak propagation.Leak active, level/pressure/flow fall together.
FR-12Show coherent pump-failure propagation.Pump A stops, N+1 is lost, flow and dP fall.
FR-13Show coherent filter-clog propagation.Filter and loop dP rise while flow falls and ΔT rises.
FR-14Show hot facility-water propagation.Supply temperature and HX approach rise together.
FR-15Show low-flow propagation.Flow/dP fall while ΔT rises.
FR-16Open a trend from a tile or P&ID tag.Current, min/avg/max, samples, unit, band and source are readable.
FR-17Provide a guided cause-to-response walkthrough.Steps identify cause, signal propagation, consequence and response.
FR-18Provide pause, single-step, speed and reset controls.Controls affect simulation time only; type/scenario basis stays stable.
FR-19Support keyboard operation and Escape close.Selectors, bubbles, tiles and overlays operate without a pointer.
FR-20Preserve site theme, mobile nav, cookie and explanation services.Shared scripts load with no non-asset console error.
FR-21Link the cockpit, PRD and Manual bidirectionally.Public URLs resolve and labels are explicit.

05 Data model & telemetry points

Ranges are simulator presentation bands, not commissioned alarms.

PointMeaningUnit / bandState semanticsSource binding
FT-01Specific secondary flowLPM/kW · 1.0–1.5Low/high band state.TYPES.flow + SCEN.flow
FT-01ΣTotal secondary flowLPMDerived display.FT-01 × capacity
TT-01Supply temperature°C · 17–45Band state.TYPES.supply + SCEN.supply
TT-02Return temperature°CDerived display.TT-01 + ΔT-01
ΔT-01Loop temperature riseK · 8–12Band state.TYPES.dT + SCEN.dT
PDT-02Secondary-loop differential pressurebar · 0.5–3.0Low/high band state.TYPES.dP + SCEN.dP
PT-01System pressurebar · 2–6Low band under leak.TYPES.sysP + SCEN.sysP
LT-01Reservoir level% · 45–70Low band under leak.56 + scenario level delta
P-01Duty/standby pumpsstateN+1 / N, no standby.Scenario pump flags
PDT-01Filter conditionstate / dPCLEAN / CLOG.Scenario filter flag
LSH-01Leak detectionDRY / LEAKLEAK is ALARM.Scenario leak flag
TT-ΔHX approachK · 3–7 or n/aHigh under hot facility water.Type architecture + scenario
AT-01Chemistry summaryPG25 stateStatic simulated state.Authored cockpit constant

06 Calculation & state rules

totalFlow_LPM = specificFlow_LPM_per_kW × capacity_kWreturnTemperature_C = supplyTemperature_C + deltaT_KExample In-Row Normal: 1.30 × 300 = 390 LPM; 32 + 11 = 43°C.
display = typeBaseline + scenarioDelta + bounded sinusoidoverall = max(tileSeverity), where ALARM > WARN > NORMALFull calculation basis and worked examples: CDU Mini-BMS Manual.

07 UX, state & accessibility

Operating sequence

  1. Select architecture.
  2. Confirm Normal baseline.
  3. Correlate tile and P&ID.
  4. Inject one scenario.
  5. Read worst-state banner.
  6. Walk cause to response.
  7. Reset.

Required states

  • Selected controls expose aria-pressed.
  • Color always has text/state equivalent.
  • Focus is visible; controls meet 44 px target.
  • Reduced motion disables non-essential animation.
  • At 375 px no page-level horizontal scroll occurs.

08 Acceptance criteria

IDGiven / when / thenEvidence
AC-01Given each type, when selected, then capacity, supply, ΔT, specific flow, dP and pressure equal the authored type object.Automated five-type matrix.
AC-02Given Normal, when the type is In-Row, then total flow is 390 LPM and return is 43°C before bounded display variation.Unit assertion.
AC-03Given Leak, then LSH-01 alarms and LT-01/PT-01/FT-01 move in the declared direction.Scenario snapshot.
AC-04Given Pump A fail, then duty state and redundancy loss agree.Scenario snapshot.
AC-05Given Filter clog, then flow falls while dP/ΔT rise and overall is ALARM.Scenario snapshot.
AC-06Given Hot facility water, then TT-01 and TT-Δ rise without changing type capacity.Scenario snapshot.
AC-07Given Low flow, then FT-01/PDT-02 fall and ΔT rises.Scenario snapshot.
AC-08Given L2A, then HX approach reports n/a.Type snapshot.
AC-09Given any tile, keyboard activation opens a labelled trend and Escape closes it.Browser E2E.
AC-10Given a fault, walkthrough steps preserve cause → propagation → consequence → response order.Browser E2E/text contract.
AC-11Given pause/step/reset, state transitions are deterministic and do not mutate type inputs.Browser E2E.
AC-12Given dark/light and 375/1440 px, no critical accessibility issue, console error or horizontal overflow occurs.Axe/layout screenshots.
AC-13Given cockpit/PRD/Manual links, all resolve as public HTTP 200 pages.Link audit.

09 Non-functional & security requirements

Reliability & performance

  • Repeated reloads yield identical engineering inputs.
  • Animation work pauses when the page is not visible where practical.
  • Core text/formulas remain useful without animation.
  • No external operational dependency is required.

Security & privacy

  • No credentials, write endpoint or user-entered HTML.
  • No production tag/value or personal telemetry is collected.
  • Shared cookie control remains active.
  • Errors do not expose filesystem or internal service details.

10 Provenance & verification map

EvidenceAuthorityUseRequired verification
cdu-mini-bms.htmlCurrent implementationTYPES, SCEN, TILES, interactions.Static contract + browser flow.
CDU Mini-BMS ManualProject engineering basisEquations, examples, tag mapping, limitations.Formula/source preservation test.
CDU Checklist and Selection GuideExisting RZ referencePlacement, chemistry and maintenance context.Human technical review.
Vendor manuals / approved SOOSite authorityReal limits, trips and response.Required before field use.

11 Risks, dependencies & release gate

Known risks

  • Users may mistake smooth animation for live telemetry.
  • Illustrative bands may be copied as site set-points.
  • Specific-flow input can be mistaken for a hydraulic solution.
  • L2A heat rejection may be read as fully modelled.

Release gate

  • All FRs and ACs map to executable or visual evidence.
  • Simulation and limitations remain visible.
  • Exact cockpit diff contains only PRD/Manual links.
  • PRD, Manual, hubs, search, sitemap and llms.txt agree.
  • Dark, light, mobile, keyboard and console gates pass.
Dependency: any transition to a live BMS requires a new frozen contract covering protocols, authentication, authorization, freshness, write safety, approved set-points and site cause/effect.
Open CDU Mini-BMSRead technical manualAll PRDs