Mindlap
← All projects

IoT Monitoring

Switch Sentry

One centralized dashboard for smart-switch runtime, operation counts, connectivity, and usage deviation across every building - monitoring only, no control.

Want the codebase? Get the Git repo emailed to you.

About this project

Switch Sentry is a centralized smart-switch monitoring and operational-compliance platform built end-to-end by the agent factory. Smart switches spread across many buildings are usually managed independently per site, with no consolidated view of what is running, for how long, or how often. Switch Sentry aggregates switch activity into a single dashboard organized by Building, Floor, Zone, and Switch. For each switch it tracks status, last-operated time, ON/OFF operation counts, total ON duration, and connectivity, and it compares actual runtime against a configured expected runtime to surface weekly deviations - over-used, under-used, and repeat offenders. A reporting engine produces weekly, monthly, and custom reports (activity, deviation, and building-wise) exportable to Excel and CSV. It is monitoring and reporting only: it never controls or operates a switch.

Demo

At a glance

3.4h

Agent hours

46M

Tokens

2

Laps

6

Stories

46M

tokens

Codex · 100%

Tokens by stage

Tech Spec

2M

Implement

23M

Code Review

8M

Merge

13M

Pipeline

Stage

Runs

Tokens

Duration

Tech Spec

6

2M

0.5h

Implement

16

23M

1.8h

Code Review

15

8M

0.9h

Merge

5

13M

0.6h

Engines used

Codex

Tokens

46M

Runs

25

Agent hours

3.4h

Success

100%

Agent team

developer

21 runs · 2.4h

17 passed · 4 failed

engineering_manager

20 runs · 1.4h

16 passed · 4 failed

product_manager

1 runs · 0h

1 passed · 0 failed

Artifacts

PRD

markdown

Switch Sentry - Product Requirements Document

Smart Switch Monitoring & Operational Compliance Platform

1. Overview & Problem Statement

Smart switches are often deployed across many buildings and managed independently per site. There is no centralized way to see which switches are on, how long they run, how often they are operated, or whether usage deviates from expectations.

This creates blind spots: equipment runs longer than needed, operational lapses go unnoticed, and there is no consolidated record for reporting or audit.

Switch Sentry provides a single, centralized view of all switches for monitoring, reporting, and compliance - without changing how each building operates its switches locally.

2. Goals & Success Criteria

Product Goals

  • One centralized dashboard for switch activity across all buildings.
  • Track runtime, operation counts, and connectivity for every switch.
  • Flag deviations between expected and actual usage.
  • Produce weekly, monthly, and custom reports, exportable to Excel and CSV.

Success Criteria

  • The monitoring team can answer "which switches are on, for how long, and where" in one place.
  • Deviation reports surface over-used and under-used switches each week.
  • Standardized reports replace manual tracking and support audits.
  • Reduced unnecessary equipment runtime through better visibility.

This platform is for monitoring and reporting only - it does not control or operate switches. Each building continues to operate its switches locally.

3. Users

UserDescriptionWhat they do in the platform
Monitoring AdminCorporate monitoring teamViews the dashboard, runs and exports reports, configures expected runtimes
Property ManagerOperates switches at a buildingContinues operating switches locally; does not use this platform
  • Access: login via Email + OTP.
  • Roles: a single centralized admin role; all users have the same access.

4. Scope

In Scope

  • Centralized monitoring dashboard.
  • Switch activity tracking across multiple buildings.
  • Operation-count tracking and deviation monitoring.
  • Reporting engine with Excel and CSV export.

Out of Scope

  • Any control or operation of switches (monitoring only).
  • Automated deviation alerts and WhatsApp / Email notifications.
  • Energy-consumption integration.
  • Remote audit dashboard, mobile application, AI-based recommendations.
  • Role-based access beyond a single admin role.
  • Any language other than English.

5. Features & Requirements

5.1 Centralized Dashboard

A single dashboard showing all switches organized by Building -> Floor -> Zone -> Switch. For each switch: Building Name, Floor / Zone, Switch Name, Current Status (ON / OFF), Last Operated Time, Number of Operations, Total ON Duration, Device Connectivity Status (online / offline).

5.2 Filtering

The dashboard can be filtered by: Building, Floor, Zone, Date range, Switch type, Deviation status, and Online/Offline status.

5.3 Multi-Building Aggregation

Switch activity from every building is consolidated into one dashboard. New buildings can be onboarded as the portfolio grows.

5.4 Activity Tracking & Sync

Switch activity is collected and stored historically so the platform can show runtime, operation counts, trends, and deviations over time. A Sync Now action is available for on-demand refresh, and a sync/activity history is visible to admins for transparency.

5.5 Operation-Count Tracking

For each switch the platform tracks: number of ON events, number of OFF events, total operation count, frequent-switching detection (configurable threshold), and operational trend analysis.

5.6 Deviation Monitoring

An expected daily runtime is configured per switch (or per switch type / per zone). The platform compares expected vs actual runtime and produces weekly deviation reports covering: switches exceeding allowed duration, under-utilized switches, repeat deviations, and severity-wise deviations.

5.7 Reporting Engine

Generates weekly and monthly reports containing: total ON duration per switch, number of times operated, operational trends, deviations from expected duration, offline device history, and excessive-usage patterns.

5.8 Excel & CSV Export

Export (in .xlsx and CSV) for: weekly reports, monthly reports, raw activity logs, deviation reports, building-wise reports, and custom date-range reports.

5.9 Authentication

Login via Email + OTP, with a single centralized admin role.

6. Operational Benefits

Better operational discipline; reduced unnecessary equipment runtime; improved monitoring visibility; standardized reporting; easier audit tracking; visibility toward energy optimization (actual integration is future scope); faster identification of operational lapses.

7. Assumptions

  • Delivery depends on the availability and accuracy of switch telemetry; upstream outages may cause data gaps.
  • Operation counts and runtime are derived from collected activity and are reliable approximations; very short on/off cycles between collection points may be approximated.
  • Historical logs grow with switch count and retention; storage may need a tier upgrade over time.

8. Future Scope

Automated alerts for deviations; WhatsApp / Email notifications; energy-consumption integration; remote audit dashboard; mobile application dashboard; AI-based operational recommendations.

9. Documentation Deliverables

Administrator user guide; property-manager onboarding guide; architecture & deployment documentation; report & export reference.

Laps & stories

mindlap
AboutFAQPrivacyTerms

© 2026 mindlap