Home / PRD / RZ Cockpit Re-skin Mockup
Product requirements · visual prototype

RZ Cockpit Re-skin Mockup

A deliberately small before/after prototype used to judge the industrial instrument-register surface while preserving operational color meaning. It is not a full cockpit, data model, production dashboard or live telemetry endpoint.

Artifact 179-line prototypeColumns Before / AfterSignals IllustrativeData mode SEEDED / SIMULATED

01 Purpose & hypothesis

Test whether a charcoal-green instrument register, thin-line geometry, mono typography and restrained motion improve scanability without changing load-bearing electrical/cooling semantics.

Decision boundary: passing this prototype supports a visual direction only. It does not approve production data, calculations, workflows, accessibility or performance.

02 Users & evaluation questions

Design reviewer

Can compare hierarchy, density, border discipline, typography and motion on identical sample content.

Operations reviewer

Can confirm Feed A blue, Feed B green, trip red and cooling cyan retain the same meanings.

Frontend engineer

Can identify reusable surface tokens without copying prototype-only markup as production architecture.

Accessibility reviewer

Can flag color-only meaning, contrast, reduced motion and responsive gaps before adoption.

03 Scope & non-goals

In scope

  • Two equal content columns.
  • Four KPI labels and authored values.
  • Illustrative two-feed SLD.
  • Seeded CDU return trace.
  • After-only count-up and trace draw.
  • Semantic legend.

Non-goals

  • No real API, engine or authentication.
  • No operational alarm workflow.
  • No complete responsive navigation or site shell.
  • No production calculation assurance.
  • No full parity with datahallAI.

04 Functional requirements

IDRequirementDeterministic check
FR-01Render Before and After columns from the same semantic sample.Both show PUE, IT, GPU, CDU, SLD and cooling trace concepts.
FR-02Keep Feed A blue in both columns.Source, bus and closed breaker use the declared blue.
FR-03Keep Feed B green in both columns.Source and bus use the declared green.
FR-04Let trip severity override Feed B domain color.Open F1B breaker and label are red in both columns.
FR-05Keep the cooling trace cyan in the After column.Trace uses the cooling semantic token.
FR-06Use thin lines and 3 px corners in the After surface.Cards and panels avoid rounded-everything treatment.
FR-07Use IBM Plex Mono/JetBrains Mono instrument typography.After labels and values resolve to declared mono stacks.
FR-08Animate only After values/trace, then hard-settle.Final values equal authored targets within 1.2 seconds.
FR-09Generate trace data deterministically.Reload produces the same SVG path.
FR-10Collapse comparison to one column below 900 px.No comparison grid overflow at 375 px.
FR-11Expose an explicit semantic legend.All four meanings have text labels.
FR-12Link public PRD and Manual.Both resolve without an access gate.

05 Display data & telemetry-like points

These values are visual fixtures. “Source binding” names local markup/code, not a telemetry transport.

DisplayMeaningUnit / valueSemantic colorSource binding
PUEIllustrative facility efficiency KPI.ratio · 1.30Neutral/derived.Authored DOM + data-count
ITIllustrative IT load.MW · 14.26Neutral.Authored DOM + count-up
GPUsIllustrative accelerator count.count · 7,776Neutral.Authored DOM + count-up
CDUIllustrative running/installed count.count · 36/48Cooling context.Authored DOM
PLN-A / bus AFeed A path.state · closedBlue.sld({feedA})
PLN-B / bus BFeed B path.state · closedGreen.sld({feedB})
F1BIllustrative open/tripped feeder.state · TRIPRed overrides green.breaker(..., false)
CDU returnSeeded visual trace.display units · seeded 22–66Cyan in After.seed(46,22,66,11)

06 Determinism & calculation rules

xₙ₊₁ = (9301 × xₙ + 49297) mod 233280valueₙ = 22 + (66 − 22) × xₙ / 233280Seed = 11, sample count = 46. This is a visual pseudo-random trace, not a thermal model.
easedProgress = 1 − (1 − progress)³display = target × easedProgress; final = targetA hard settle prevents screenshots/tests from capturing an intermediate KPI.

07 Visual and interaction contract

After register

  • Charcoal surface, restrained green/cyan signals.
  • Thin borders and square industrial proportions.
  • Mono labels and tabular values.
  • Subtle graticule limited to the instrument frame.

Guardrails

  • No dot-grid hero noise or generic purple accent.
  • No cursor tracking, 3D tilt or bouncy text.
  • No semantic-color reassignment.
  • Motion must not hide the final number.

08 Acceptance criteria

IDAcceptance statementEvidence
AC-01Both columns expose the same primary semantic content.DOM contract.
AC-02Feed A/Feed B/trip/cooling colors match legend labels.Computed-style + SVG assertions.
AC-03F1B remains red in both columns.SVG snapshot.
AC-04Seeded trace path is identical across reloads.Path checksum.
AC-05Animated target values settle to 1.30, 14.26 and 7,776.Timed browser assertion.
AC-06Comparison becomes single-column at 375 px without page overflow.Responsive screenshot.
AC-07Prototype, simulated data and non-production limits are explicit.Copy assertion.
AC-08PRD and Manual links are keyboard reachable and HTTP 200.Link/browser audit.

09 Non-functional requirements

Performance

No framework or network data dependency; bounded SVG generation and a finite animation settle.

Accessibility

Semantic meaning has text labels; reduced-motion support and full shell accessibility are required before production reuse.

Security/privacy

No inputs, credentials, persistence, operational data or write endpoint.

Compatibility

Modern evergreen browsers; core comparison remains readable if animation does not run.

10 Provenance & validation map

EvidenceAuthorityClaim supportedValidation
rz-cockpit-mockup.htmlCurrent prototypeMarkup, styles, fixture values, SVG and animation.Static/browser inspection.
Prototype ManualProject method noteFixtures, algorithms, interpretation and limitations.Documentation gate.
RZ design standardProject visual authorityTypography, line, color and anti-pattern rules.UIUX review.
Production cockpitFuture implementation authorityActual data/workflow parity.Separate frozen contract.

11 Known gaps & release decision

Known implementation gaps

  • The prototype has no standard site navbar/theme/cookie shell.
  • Reduced-motion behavior is not implemented in the prototype.
  • Before/After parity is conceptual, not a machine-checked field schema.
  • The same four fixtures appear once in each comparison column by design; this is comparison parity, not duplicate telemetry.

Decision

Publish as an honest design prototype with public documentation. Do not label it a production cockpit or use its values as engineering evidence. Fix documented gaps under a separate cockpit contract because this task permits link-only cockpit changes.

Open prototypeRead technical manualAll PRDs