A fictional dashboard showing how a non-technical operator could check irrigation-controller health, today’s watering schedule, and recent events from one simple screen.
No action needed. The fictional controller is online, today’s schedule has completed successfully, and no error events are present.
Design goal: one glance should answer, “Is the system okay?”
Many small-business systems fail at the handoff between devices, software, and people. The useful layer is often a simple status view, not another complicated dashboard.
| Zone | Start | Duration | Status |
|---|---|---|---|
| Front Planters | 6:00 AM | 8 min | Completed |
| North Drip Line | 6:12 AM | 12 min | Completed |
| Back Trees | 6:30 AM | 18 min | Completed |
| Time | Event | Result |
|---|---|---|
| 6:00 AM | Front Planters started | Normal |
| 6:08 AM | Front Planters completed | Normal |
| 6:12 AM | North Drip Line started | Normal |
| 6:24 AM | North Drip Line completed | Normal |
| 6:48 AM | Connection health checked | Healthy |
The demo is not about sprinklers. It is about translating a real-world device workflow into a simple operator-facing system: status, schedule, events, and next action.
Public version: fake data and interface pattern. Private version: real credentials, network details, control logic, and client-specific information stay offline.
{
"controller": "Demo Irrigation Controller",
"connection_status": "online",
"remote_access": "healthy",
"last_sync_minutes_ago": 2,
"mode": "automatic",
"rain_delay": false,
"zones": [
{
"name": "Front Planters",
"start_time": "06:00",
"duration_minutes": 8,
"status": "completed"
},
{
"name": "North Drip Line",
"start_time": "06:12",
"duration_minutes": 12,
"status": "completed"
},
{
"name": "Back Trees",
"start_time": "06:30",
"duration_minutes": 18,
"status": "completed"
}
],
"operator_message": "No action needed. System appears healthy."
}