Vacancy Status Dashboard¶
Monitoring dashboard — instantiates Persistent Site Framing
Surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view.
A Vacancy Status Dashboard is the archetype's live window: it reads the current state of every site and presents it — vacant, occupied, reserved, blocked, retired — alongside a derived signal of how heavily each region is used, rolled up by the site hierarchy so a viewer can see both the individual spot and the zone at once. Its defining move is that vacancy is made visible as a first-class state, in real time, at a glance: the dashboard exists precisely to defeat the failure where empty sites vanish from view because only occupied ones are modeled. It computes and displays; it does not book, verify, or remember. Whatever the records currently say, the dashboard shows it — and shows the utilization those states imply.
Example¶
A city's parking authority has meters and lots but no way for anyone to see, in the moment, where a space is free — so drivers circle, and planners argue about occupancy from stale monthly reports. The authority stands up a Vacancy Status Dashboard fed by in-space sensors. Each metered space is a tile that flips between free, occupied, and out-of-service; the tiles roll up by block, then by district, into a utilization heat signal — this block runs 95% full at noon, that lot sits at 30%. San Francisco's real SFpark program did exactly this kind of sensing-and-publishing to make on-street availability visible.[1]
The dashboard changes no reservation and issues no ticket; it shows. A driver's app reads "two spaces free on this block," and a planner reads "the district's north edge is chronically saturated while the garage two streets over is half empty" — both from the same live view, without anyone walking the curb.
How it works¶
The dashboard is a read-model over site state plus a rollup. It subscribes to the current status of each site (from the turnover machinery and any sensors), maps each site to a visual state, and computes a utilization signal — fill rate, dwell, saturation — per site and, by aggregating along the hierarchy, per zone, floor, district, or rack row. Two properties define it. Vacancy is explicit: empty is a rendered state, not a blank, so unused capacity is as visible as used. It is derived, not authoritative: the dashboard holds no truth of its own; it is a projection of state that lives elsewhere, so its correctness is entirely inherited from its sources and its refresh latency. It never mutates a site — clicking a tile shows detail, it does not assign.
Tuning parameters¶
- Refresh latency — real-time streaming versus periodic polling. Low latency makes the view trustworthy for moment-to-moment decisions but costs sensing and bandwidth; slow refresh is cheap but strands viewers on stale state.
- Aggregation level — how high up the hierarchy utilization is rolled. High rollups reveal regional patterns but hide individual sites; low rollups are precise but overwhelming at scale.
- State palette — how many distinct states are shown (just free/occupied versus free/reserved/blocked/cleaning/retired). Rich palettes convey nuance but clutter; sparse palettes are scannable but blur real conditions.
- Signal definition — what "utilization" counts (instantaneous fill, time-weighted dwell, peak). The choice shapes what patterns the viewer sees and can mislead if the definition doesn't match the decision.
When it helps, and when it misleads¶
The dashboard's strength is vacancy visibility: it converts empty-and-invisible into empty-and-obvious, so capacity that was being wasted (or hunted for by circling) becomes actionable, and utilization patterns that only a rollup reveals become plannable. It is the archetype's cure for vacancy blindness.
Its failure mode is trusting the projection over reality: a dashboard is only as true as its feed, and a glowing wall of green tiles can be confidently wrong when a sensor sticks or the state feed lags — the viewer sees "free" and drives to an occupied space. A related misuse is treating utilization display as utilization fact, letting a poorly defined signal drive decisions (declaring a zone underused because the metric counts the wrong thing). The guarding discipline is to show data freshness on the face of the dashboard, define the utilization signal to match the decision it feeds, and periodically ground-truth the projection rather than assuming the feed is faithful.
How it implements the components¶
The dashboard fills the archetype's live-visibility components:
site_utilization_signal— it computes and displays how heavily each site and region is used, making vacancy and saturation visible in real time.site_hierarchy_map— it aggregates state and utilization along the site hierarchy so a viewer sees both the individual site and the zone.
It renders current state; it neither stores nor checks it. The durable record of who occupied what — occupancy_relation_record and occupancy_history_ledger — is the Occupancy Ledger's (the dashboard shows the present, the ledger keeps the past). And confirming the displayed state against physical reality — conflict_resolution_rule — is the Site Audit Walkthrough's, its nearest twin (the dashboard passively reflects the feed; the audit actively reconciles it).
Related¶
- Instantiates: Persistent Site Framing — the dashboard is the archetype's live-visibility surface, making vacancy and utilization legible.
- Consumes: Occupancy Ledger — supplies the occupancy state the dashboard projects; site status feeds also come from the turnover machinery.
- Sibling mechanisms: Site Registry · Physical or Virtual Labeling System · Site Map or Plan · Capacity-Fit Matrix · Assignment and Release Workflow · Occupancy Ledger · Site Lineage Tombstone · Site Audit Walkthrough
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Vacancy Status Dashboard operates as ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response because it surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view.
Independent corroboration: The frozen evidence defines Vacancy Status Dashboard as 'Surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Architecture & Urban Planning
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: U.S. Census Bureau, Housing Vacancy Survey documents that urban and housing practice measures vacancy status explicitly over time rather than inferring it from absence. This is direct, mechanism-specific evidence for architecture urban planning as the best-evidenced historical home of the operation—Surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=universal.
Related originating lineages:
- Data Science & Analytics — Data science, analytics, and operational monitoring supplies a parallel or contributing lineage for the mechanism's defining operation: surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view.
- Operations Research — Operations research's allocation, scheduling, optimization, and decision-analysis tradition contributes a separate formative lineage to the mechanism's vacancy status dashboard logic.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—Surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view.—but the adjudicated evidence more directly locates the defining lineage in architecture urban planning.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus architecture_urban_planning). The defining operation is: Surfaces which sites are vacant, occupied, reserved, or blocked — and how heavily each region is used — in one live view. The researched U.S. Census Bureau, Housing Vacancy Survey establishes that urban and housing practice measures vacancy status explicitly over time rather than inferring it from absence. That source therefore supports architecture urban planning as the historical origin. organizational management remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=single_lineage records lineage construction; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] SFpark was a real San Francisco Municipal Transportation Agency program (launched 2011) that instrumented on-street metered spaces with sensors and published real-time availability to help drivers find open spots. It is a concrete case of turning site status into a live, published vacancy signal. withdrawn registry ↩