BU Dashboard Standard — Uniform Single-Page Layout¶
Phase 5 presentation standard (draft for review). Every BUFM is presented as a single-page HTML dashboard with the same layout, so readers move between business units without re-learning the page. The layout mirrors the modeling layers: inputs → outputs → intermediaries → environment.
Layout (3 rows)¶
| Row | Contents | Rule |
|---|---|---|
| 1 — top | Two cards side by side: Model Inputs (left), Model Outputs (right) | inputs = what the operator/market sets; outputs = what the BU answers |
| 2 — middle | Intermediaries: computed values and parameters used inside formulas, plus sanity-check indicators | every number shown here must be re-derivable from row 1 — these are the checking surface |
| 3 — bottom | Environment / external reference cards: FX rate, interest rate (WACC), tax rates, grid/petrol reference prices | values the BU does not control; each card names its source (profile parameter + provenance) |
Below the grid (Phase 5.4+): a button row linking out to spreadsheet-equivalent financials — balance sheet, 12-month P&L — as generated artifacts (per the file-format policy: generated output only, never the modeling source). Buttons appear once those artifacts exist; until then the row is omitted.
Data wiring (how the page is filled)¶
- Row 1 inputs: the BU object's
parameters+inputs(BU object interface), labeled with unit and provenance tag. - Row 1 outputs: the BU object's
query()answers — the standard inquiry set plus unit-specific inquiries. - Row 2 intermediaries: values the calculation exposes for checking (e.g. energy/day, fuel L/day, net investment) — each must re-derive from row 1 within the page's own formula notes.
- Row 3 environment: profile environment/policy parameter groups (FX, WACC, tax, reference prices), each carrying its provenance (e.g.
industry-verify,pending-input).
A dashboard is generated, not hand-written: the engine emits the page from a BU object + profile, so layout drift is impossible and every BU gets the uniform page for free.
Sanity-check indicators¶
Row 2 always includes at least:
- the dominant sensitivity for that BU (rider: daily saving vs petrol; SNS: utilization; BCS: fleet rotation)
- at least one identity check (e.g. price wedge legs sum to H1; energy-in = energy-out × losses) shown as OK/FAIL
Mockup¶
A generated example with the RIDER BU's current numbers: see the chat mockup rendered during review, and decisions/ pages for live examples once Phase 5.4 ships.
Relation to standards¶
- Presentation is the third layer of the unitary core (logic → profile → presentation): all display values are converted from canonical USD/ISO at render time.
- The standard inquiry set (BU object interface) defines what row 1 outputs may contain.