How to read the fleet board
The fleet board lists every saved site with its working height, current wind, the next hour the odds reach 40%, the worst odds across your shift and a GO, WATCH, STOP or UNKNOWN lamp. This guide explains each column and control.
ON THIS PAGE
Steps
Open /fleet while signed in
Go to /fleet. If you are signed out you see "Fleet board." with a sign-in form instead. Signed in on a plan without the board, you see a lock reading "The fleet board is on Ops." The board is part of Ops and Enterprise, though where the paywall is switched off for the deployment every account can open it.
Set the shift window
At the top, next to SITE SHIFT, two selects choose the start and end hour in site-local time. The default is 06:00 to 18:00. Every site is judged only on its shift hours from now onward. The choice is stored in this browser, so it does not follow you to another device.
Filter and refresh
The "Filter fleet lamps" select shows All sites, STOP, WATCH, GO or UNKNOWN. The Refresh button reloads every site; nothing refreshes by itself, and a site is also reloaded when you save its rule. The summary strip shows counts of STOP, WATCH, GO and UNKNOWN, how many sites you hold out of your plan limit, and the time last updated in UTC.
Read a row
Each row has the site name with its rule beneath it, the asset height in metres, the current wind at that height, the first shift hour when odds reach 40% with the odds beside it, the highest odds in the shift with the shift hours, and the lamp with a short reason. A mobile phone shows the same as a list of lamp cards.
Open a site or edit its rule
Click a row, or press Enter on it, to open /app for that site with its height and limit already set. The pencil button at the end of a row, or "Edit rule" or "Set a rule" on a phone, opens the rule editor. Clicking a column header sorts by it, and a second click reverses the order.
Tip: The board loads 4 sites at a time, so a large fleet fills in gradually.
01What the board is for
The board answers one question for many sites at once: which one needs attention first? Each site is evaluated against its own saved rule: the metric, the direction, the threshold, the working height and the source document. The result is a lamp and a sort order. Its subtitle reads "One packet per asset. Sorted by the next bad hour." It does not decide anything for you. It compares a modelled forecast with the number you typed.
02The columns
SITE shows the name and, beneath it, the rule label with the metric word "gust" or "speed", the comparison and the threshold in your unit, or "No rule". ASSET HEIGHT shows the working height and an EXTRAPOLATED badge when it is below 10 m or above 180 m. NOW · AT HEIGHT shows the current wind with the word gust or mean and the hour. NEXT P ≥ 40% shows the first shift hour at or over 40%, or "No crossing", "UNKNOWN" or a dash where no rule exists. MAX P / SHIFT shows the highest odds and the shift hours, with "ens" and a height when the ensemble level differs from the site height. LAMP shows the word and the reason. There is no member-count column.
03How the lamp is decided
The lamp is calculated in your browser from the shift hours. STOP appears when the primary forecast reaches the limit in any shift hour, or when the ensemble odds reach 70% in any shift hour. WATCH appears when the odds reach 40%, or the primary forecast is within 5 mph of the limit. GO means neither held for the whole shift. UNKNOWN covers no rule, no forecast, no ensemble, or no shift hours. There is no smoothing or memory: each load starts fresh, and exactly 40% counts as WATCH while exactly 70% counts as STOP.
04Sorting
By default rows are ordered by the earliest hour at which odds reach 40%, then by lamp, STOP first, then by higher peak odds. Sites with no crossing sit lower. Because the sort looks at the ensemble, a site can be STOP because the primary forecast reaches the limit and still sit below a site with an earlier ensemble crossing. Use the header clicks to sort by name, next crossing, peak odds or lamp instead.
05Height and levels
The current wind is read at each site's working height, interpolated between the model levels at 10, 80, 120 and 180 m, and extrapolated outside 10 to 180 m with a badge. The ensemble odds are read at the nearest level the ensemble offers. Gust odds are always for 10 m. When the ensemble level is not the site height, the row says so with "ens" and the level in metres.
06Adding sites and plan limits
The board shows sites you saved on /account, in the Saved sites section. The empty board says "No sites on the board yet." and offers an Add a site button that goes to /account#sites. Ops holds up to 100 sites and Enterprise 500. The count in the summary strip shows how many you use. The board also loads two things per site: seven days of wind and three days of ensemble, so odds only exist for about the next three days.
07If something looks wrong
UNKNOWN with "No rule set" means open the pencil and name the limit. "Forecast unavailable" or "Ensemble unavailable" means a data request failed; press Refresh. "No forecast hours in the shift window" usually means the start and end of the shift are equal, so no hours fit. Missing data never counts as calm. If STOP shows while the odds read low, the primary forecast has reached your limit on its own.
Questions
How is the fleet board different from the instrument?
The instrument at /app reads one place in depth, with maps, the fan and the models. The fleet board reads all your saved sites in one table, each against its own rule and shift. Clicking a row takes you from one to the other.
How is the next bad hour found?
It is the first hour inside the shift when the ensemble odds are 40% or more. The sort uses that hour first. A site can show a STOP lamp because the primary forecast reaches the limit even if no ensemble hour reached 40%, in which case it is ordered lower.
Can each site have its own shift?
No. One shift window applies to the whole board and is stored in your browser. It is not saved on your account, not synced between devices, and alerts do not use it.
Why does a site show UNKNOWN?
The row gives the reason: no rule, forecast not loaded, ensemble not loaded, or no shift hours. Some hours missing while others have odds does not make it UNKNOWN; only a full lack of odds does. Missing data is never treated as calm.
Does the board tell me to go or stop work?
No. The lamp compares a modelled forecast with the limit you set from your own document. The footnote on the board says the thresholds are site-set, not statutory. The call remains with the person responsible on site.