University Facilities and Space Utilization Dashboard Specification
Specify an operational dashboard combining physical campus IoT occupancy data with class timetabling.
Deploy this template when designing an estates and facilities dashboard to optimize classroom usage and energy loads. It formalizes telemetry data pipelines, heatmap components, and HVAC trigger thresholds.
Role: Principal Smart Campus IoT & Operations Data Specialist
Context
- Campus / Estate Portfolio: {{campus_estate_name}}
- Occupancy Telemetry Network: {{iot_sensor_network}}
- Central Scheduling System: {{timetable_system}}
- Sustainability & Energy Baseline: {{energy_target_benchmarks}}
- Primary Stakeholder Persona: {{facility_manager_persona}}
- Operational Escalation Rules: {{alert_escalation_tiers}}
Task
Produce an actionable dashboard design specification that blends scheduled academic room bookings with live sensor occupancy and environmental telemetry to optimize space utilization and energy consumption.
Method
- Establish spatial hierarchy schemas for {{campus_estate_name}} (campus, building, floor, zone, room).
- Define ingestion rules for real-time telemetry from {{iot_sensor_network}} alongside scheduled rosters in {{timetable_system}}.
- Formulate space efficiency metrics (e.g., seat fill rate, ghost booking rate, idle conditioned space).
- Design energy correlation views measuring kilowatt-hour consumption against {{energy_target_benchmarks}}.
- Draft interactive campus maps and floor-plan heatmaps tailored to {{facility_manager_persona}}.
- Define automation triggers and alert protocols based on {{alert_escalation_tiers}} for HVAC overrides and security alerts.
- Detail edge-case handling for Wi-Fi triangulation dropouts, offline sensor nodes, and emergency scheduling overrides.
Constraints
- MUST NOT present individual device MAC addresses or user-identifiable location tracks.
- MUST account for delayed telemetry packet arrivals up to 15 minutes without breaking aggregations.
- Sensor density assumptions must be clearly documented for each room type.
- All thermal and energy readings must support metric and imperial unit switching.
Output format
Deliver the technical specification structured in four distinct sections:
- Architecture & Telemetry Pipeline Map (max 250 words)
- Core Metric Dictionary (Name, Formula, Data Entities, Target Value)
- UI Viewport Specifications (Executive Estate Overview, Floor-level Heatmap, HVAC Energy Analytics)
- Alert Workflow & Action Triggers (table format: Trigger Condition, Severity, Action Protocol)
Self-review
- Check that {{campus_estate_name}}, {{iot_sensor_network}}, {{timetable_system}}, {{energy_target_benchmarks}}, {{facility_manager_persona}}, and {{alert_escalation_tiers}} are fully integrated.
- Confirm that no personally identifiable tracking mechanics are included.
- Validate that the comparison logic between booked schedules and live occupancy is explicitly defined.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.