Panels

The operating panels of a model: the fixed cards each unit is run through, arranged once on the model, and how a panel reaches Operate and the View page.

View as Markdown

A panel is a named operating surface of a model: a fixed set of cards, arranged once on the model and drawn identically for every unit of it. It is not a dashboard: no editor opens on it, nothing is composed on a canvas, and the surface a unit is run from is the same and complete on every station. Panels live under Process > Models > model > Visualization > Panels. Arranging one needs the Manage process permission; operating the cards on a unit needs Run procedures.

The Panels folder

Selecting the Panels row opens the folder page ("Operating panels defined on this model. Each one holds for every unit, and each one decides on its own whether the View page carries it.") with one card per panel; clicking a card opens it and the X removes it. The folder is never empty: a model that has declared no panel reads as a single one named Overview drawing the whole card catalogue, and the first edit made on it is what stores it as a row of the model.

Command What it does Greyed when (situation) Not drawn when (role)
Panel (detail bar, folder selected; right-click Add panel) Adds a panel named Panel <n> beside the ones the model has and selects it. A model still reading as the default gets Overview stored first, so the new panel stands beside the surface its units already operate through instead of replacing it. Any unit holds a run, or the runtime is stopped. Without Manage process.

The panel's page

Selecting a panel opens its arrangement: the header ("One operating panel of this model: the cards it draws, in the order it draws them. Every unit of the model carries it."), an Identity card and the arrangement itself. Every change autosaves; a write the station refuses puts the page back exactly as it was.

Identity

Field What it is Values / default Effect
Name What the panel is called on its tree row, on each unit's row under Operate and on its View page entries. Free text; a blank entry is refused and the previous name stays. Panel <n> at creation, Overview for the default. Renames every row that names it.
Icon The mark drawn left of the panel's name on the tree row and on every unit's View page entry. A button showing the current mark (or the word "Icon", or the stored name when the library does not carry it). Pressing it unfolds a grid of the icon library under the card, with a Search by name or tag field ("oven, pump, water"); the first cell is No icon. Choosing a mark applies it and closes the grid; a press outside or on the button closes it too, and the search text stays for the next time. No icon by default. The panel stores the library name of the mark, never a code point. A name the library does not carry draws the fixed panel mark on both rows, so the tree and the View page never disagree.

The panel

The card explains itself: "The surface, in the order it is drawn. Turn a card off to leave it out, and move it to where it belongs. A dashboard card is the empty screen, the way the editor draws it; the other cards are filled with sample readings. A card the unit gives nothing to show is skipped rather than drawn empty."

Under it stands one row per card, in the order every unit draws them. Each row is the card itself, posed with sample readings so the arrangement cannot promise an appearance the unit does not draw: a unit named Sample, the model's first procedure staged, "Running", cycle "2 / 5", one comment, one closed occurrence episode, a five-minute trace of the model's readable channels, and a posed productivity ledger over the model's productive procedures. What the sample supplies is only what a running unit would; the rest (procedures, metadata fields, channels, libraries) is this model's own, so a model that declares none of something shows the card's own emptiness. The whole preview is inert: nothing in it can be pressed.

Control on a row What it does
The checkbox, labelled with the card's name and followed by the card's description Includes the card (on) or leaves it out (off). The row stays in the list either way, dimmed when off.
Height on the page (px) (dashboard rows only) How tall the dashboard stands on the page: 120 to 1200, 320 by default; a value outside the range is refused under the field. "The dashboard scales to fill the box; the page scrolls and the dashboard does not." Disabled while the row is off.
Move this card up / Move this card down Moves the row one place. The first row cannot go up and the last cannot go down; the arrow says so by staying greyed.

When the model's stop interlock is enabled, a fixed row stands first, before every card: Interlock, "The external stop this unit observes, and the way to rearm it. It draws nothing while the unit is normal, so there is nothing to show here either.", marked Always. It is the surface's safety context, not a card, and it is never arranged away (see Automation and the stop interlock).

Leaving every card off is a legitimate panel, and the page says what it means: "Every card is off, so each unit says so on this panel and offers nothing to operate from. The run still starts from another panel of this model, or from a dashboard."

The card catalogue

The catalogue cards stand in this order on a panel that has arranged nothing. Each is drawn for the unit that opens the panel, and a card the station gives nothing to show is left out rather than drawn empty.

Card What it shows on a unit What you can do on it Left out when
Run The card's head carries a lamp: Recording, Preparing or Not recording. A Procedure picker ("(none)" plus the model's procedures by name) stages the next start. The lifecycle buttons follow, in this order: Start (accented), Hold, Resume, Stop, Abort, each with its tooltip ("Start the staged procedure on this unit", "Freeze the temporal window; the datalog keeps recording", "Release the hold and carry the window on", "End the run cleanly and freeze it as history", "End the run as aborted; the finalization block still runs"). Stage a procedure and press the command that is ready now; every button reads its own readiness. Hold and Resume are drawn only while the staged procedure is Temporal (or nothing is staged), because only a temporal window can be frozen. A refused command is said on the card, in a caution note; the reasons the station or this unit is not taking run operations (the runtime stopped, the unit latched by its interlock) are said under it. Never.
Metadata "What the next run of “<procedure>” is recorded under. A field marked * is prompted by every procedure." One entry per metadata field the staged procedure prompts, in catalogue order. A sequential field is not an entry box: it shows the prediction of what the counter would compose, with the note "The counter reserves the definitive value at start, so a shared counter may move before then.", or "Reserved at start" while nothing can be predicted. With nothing staged: "Stage a procedure and the fields it prompts appear here." Type the values the next Start consumes. Staging is station-wide, so a value typed here is what every other surface of the unit sees. The staged procedure prompts no field.
Run state Three readouts: State (the run's state, or Preparing while a run is being reserved, or Idle), Cycle ("2 / 5", or Not cycling), Verdict (the verdict of the run under way or the last evidence, or None). Read. Never; the Cycle readout alone is left out while the staged procedure is Instant or Controlled.
Comments The run's comment timeline, headed "Comments · <run>", "Comments · no active run" or "Comments (unavailable)". Add a comment to the active run through the box under the timeline (Run procedures). See Runs and comments. Never.
Occurrences The unit's occurrence episodes, active first, headed "Occurrences", "Occurrences · <n> active" or "Occurrences · outside run" ("· stale" while a refresh failed). Read. Never.
Channels The unit's readable channels on one live chart, each series named by the name in force on this unit, drawn in the colour and the band its channel declares, with the chart toolbar of every chart in the app (see Charts). Zoom, pan, save or copy the picture, toggle series. The model declares no readable channel.
Productivity The unit's produced quantities, rates, yield and outcome ledger over Today and the rolling period. See Productivity. Read. Never.
Single commands "Fire one isolated command on this unit, outside a procedure." Three rows, each drawn only where the model declares the library it fires from: Snapshot (a datalog picker and Capture: "Record one datalog row now as a finished run in Histories"), Evaluate now (a datalog picker, an evaluation picker and Evaluate: "Snapshot one row and judge it against the evaluation now"), Apply recipe (a picker over the model's instant recipes and Apply: "Write the recipe's setpoints once through the funnel (no run recorded)"). Fire the command; the result lands in the action feed ("Snapshot recorded. See Histories.", "Evaluated. The verdict is recorded in Histories.", "Recipe applied."). Capture and Evaluate need Run procedures, a unit that is not busy and not blocked, a running runtime and a complete selection; Apply needs the same except that the unit may be busy, since it reserves nothing. A busy unit shows the note "Snapshot and Evaluate are unavailable while this unit is preparing, running, held or saving. Apply recipe stays available through a run, but not while the interlock is holding the unit: a tripped chain, one waiting to be rearmed and one whose reading is unavailable all refuse it." The model has no datalog and no instant recipe. The Evaluate now row needs a datalog and an evaluation; the Apply recipe row needs an instant recipe.

After the catalogue come the model's dashboards, one row each, named by the dashboard and described by its own description (or "A dashboard of this model, drawn for the unit that opens the panel."). A dashboard is off until you switch it on, unlike the catalogue cards; on a unit it draws the dashboard resolved for that unit, at the height chosen on the row, headed by the dashboard's name. It is left out on a unit when the dashboard is empty or has been deleted.

The pickers of the Single commands card start on the first item of each library and keep your pick while you stay on the unit.

Order, on and off

The arrangement is saved in full on the first change, so the order the page shows and the order saved are the same. A catalogue card the panel holds no row for reads as on, after everything the panel does hold, which is why a panel nobody arranged draws the whole catalogue in catalogue order and why a card a later version adds arrives visible at the end. A dashboard row is the other way round: off until you put it in, and a row naming a dashboard the model no longer has is dropped.

Show on View

Show on View is the switch on the detail bar with the panel selected. It reads the state in force, and its tooltip says what that state does:

State Tooltip
On "Each unit of this model has an entry for this panel in the Visualization list."
Off "This panel is opened from the unit, under Operate. Nothing of it stands on the View page."

On puts one entry per unit of the model in the View page's Visualization column, named Model · Unit · Panel and wearing the panel's icon; the entry opens the panel's cards drawn for that unit. Entries are never reordered, edited or copied on the View page (Copy is refused), and each unit's entry may be filed into the View page's folders on its own. A model with no units puts nothing there. The switch is not drawn for a role without Manage process; it stays drawn and greyed under the engineering lock and the stopped runtime, saying which. What the entries look like is on Unit panels on View.

Remove panel

Remove panel stands in the detail bar's danger cluster with the panel selected, on the tree's right-click menu, and as the X on the folder page's card. It asks first ("Delete panel", "This removes the panel from the model."). The last panel of a model is refused: "A model keeps one panel at least, and this is the only one." After the deletion the selection lands on the model's Panels folder, every unit loses that row, and its entries leave the View page. It needs Manage process and is greyed under the engineering lock and the stopped runtime.

Under Operate and on the View page

Every unit of the model carries one row per panel, before its dashboard rows, under Operate. Selecting it draws the cards over that unit's own run and bindings, under the stage bar the View page uses: the entry name Model · Unit · Panel, the panel's icon, Expand ("Use the whole window"), Full screen ("Full screen (F11)"), and a pill with the unit's activity while a run owns it (Recording, Held, Saving, Preparing, Finalizing). There is no Copy and no Edit: the row draws the arrangement and never arranges it. The cards refresh on their own cadence (every 200 ms on the station's own window, 400 ms on a browser).

A role without Run procedures reads the note "You can watch this unit's run state here, but starting or steering it needs the “Run procedures” permission." and the commands are not drawn. A panel whose cards are all off says "This panel draws no card. Choose its cards on the model's Panels row, under Visualization." The panel stays usable while the station's configuration is locked by a run: operating is never held by the engineering boundary.

The same cards, drawn the same way, are what a View page entry opens.

What a panel does not do

  • It composes nothing freely. A picture of your own is a dashboard of the model, which a panel can then draw as one of its cards.
  • It differs between units in nothing. Every unit of the model draws the same cards in the same order at the same heights; a unit that needs another surface needs another panel of the model, which every unit then carries too.
  • It cannot be copied, reordered or edited on the View page, and it is never in the View page's own folders except as the per-unit entries the switch creates.
  • It never hides the interlock banner, and it never draws a card the unit has nothing to fill.