Home / Manuals / RZ Cockpit Re-skin Mockup
Technical manual · deterministic visual prototype

RZ Cockpit Re-skin Mockup

The engineering and visual basis for the Before/After prototype in rz-cockpit-mockup.html: authored fixture values, semantic color mapping, seeded SVG trace, count-up settle and the limits that prevent it being mistaken for an operational cockpit.

Mode SEEDED / SIMULATEDTrace 46 samplesColumns 2Authority visual only

01 Purpose & engineering basis

The artifact isolates one design question: can an industrial-instrument register improve hierarchy and scanability while retaining electrical and cooling semantic colors? All displayed values are fixtures chosen to keep the comparison stable; they are not calculated from a facility model.

Boundary: visual fidelity is not telemetry validity. PUE, IT MW, GPU count, CDU count, breaker state and trace amplitude have no shared calculation model in this prototype.

02 Fixture register & source binding

FixtureDisplayed valuePurposeSource
PUE1.30Two-decimal derived-KPI typography.Authored markup / count target.
IT14.26 MWTwo-decimal power typography.Authored markup / count target.
GPUs7,776Thousands separator and integer settle.Authored markup / count target.
CDU36/48 runningState ratio fixture.Authored markup.
SLDA/B closed, F1B tripDomain color versus alarm override.sld()/breaker().
CDU return46 seeded pointsStatic versus phosphor trace surface.seed(46,22,66,11).

03 Calculation and animation methodology

xₙ₊₁ = (9301 × xₙ + 49297) mod 233280yₙ = 22 + 44 × xₙ / 233280Seed 11 and 46 samples produce a repeatable visual trace. Units are intentionally not asserted because the algorithm is not a thermal model.
e = 1 − (1 − min(elapsed / duration, 1))³strokeOffset = pathLength × (1 − e)KPI display = target × e; hardSettle = targetTrace duration is 1,400 ms; KPI duration 900 ms; a 1,200 ms hard settle makes the final content deterministic.

04 Semantic color and visual method

SemanticColorRuleWhat may change
Feed ABlue #3b82f6Electrical domain identity.Surface, glow and line weight only.
Feed BGreen #22c55eElectrical domain identity.Surface, glow and line weight only.
Trip/alarmRed #ef4444Status overrides source-domain color.Never reassigned to decoration.
CoolingCyan #2BE8FFThermal/cooling trace.Glow may be restrained.
After surfaceCharcoal/green-mutedInstrumentation character.Contrast and density after testing.

Color is explanatory but insufficient alone. A production adoption must retain labels such as Feed A, Feed B and TRIP plus accessible state text.

05 Worked examples

Example A · F1B trip precedence

  1. F1B belongs to Feed B, whose normal domain color is green.
  2. The breaker is rendered open/tripped.
  3. Alarm severity therefore overrides green.
  4. The arm, X and label render red in both columns.

Example B · deterministic trace

  1. Start with seed 11.
  2. Apply the linear congruential recurrence 46 times.
  3. Map each result to 22–66 display units.
  4. Map samples to a 420 × 90 SVG path.
  5. Reload: path data remains identical.

Example C · hard-settle

  1. PUE begins at 0.00.
  2. Cubic ease approaches 1.30 during 900 ms.
  3. A timeout calls settle() at 1,200 ms.
  4. Final accessible text is exactly 1.30.

Example D · responsive layout

  1. Desktop grid has two equal columns.
  2. Viewport crosses below 900 px.
  3. .cmp becomes one column.
  4. SVG viewBox preserves aspect ratio.

06 Review workflow & verification

  1. Read the visible scope sentence before evaluating aesthetics.
  2. Compare identical concepts, not animation novelty.
  3. Verify semantic colors and red trip precedence.
  4. Wait for hard-settle and capture the After result.
  5. Reload and compare trace path/checksum.
  6. Inspect desktop and 375 px layouts.
  7. Test reduced-motion expectation before any production adoption.
  8. Record accepted tokens and rejected patterns in the design standard.
Do not infer: this prototype does not prove datahallAI integration, alarm correctness, formula parity, keyboard completeness or deploy readiness.

07 Standards & references

08 Glossary, known defects & limitations

TermMeaningLimit
FixtureAn authored value held constant for visual comparison.Not measured or engine-derived telemetry.
Semantic colorColor with a stable operational meaning.Must also have text/shape/state.
Hard settleFinal assignment after animation.Does not itself implement reduced motion.
Seeded traceRepeatable pseudo-random SVG series.No time unit, sensor or thermal equation.
Instrument registerCompact mono, thin-line industrial surface.A visual language, not a control system.

Known limitations: the prototype omits the standard navbar/theme/cookie shell and reduced-motion handling. Its Before and After columns intentionally repeat one CDU fixture each so the comparison uses the same four-value register; this is not a duplicate tile within either column. Implementation gaps are documented rather than silently fixed because the telemetry-doc task freezes cockpit edits to exactly two additive links.

Open prototypeRead product requirementsAll manuals