Problem Statements Analysis

From what to build to how to build it — our platform helps you understand, plan, and solve SIH 2026 problem statements with complete insights into requirements, solution approaches, technology stacks, architecture, AI/ML, and implementation roadmaps.

Scroll down
01 / SIH 2026

PS: SIH26202

Student Innovation-Ideas focused on the intelligent use of resources for transforming and advancements of technology with combining the artificial intelligence to explore more various sources and get valuable insights.

Description: Student Innovation-Ideas focused on the intelligent use of resources for transforming and advancements of technology with combining the artificial intelligence to explore more various sources and get valuable insights.
Organization: AICTE
Department: AICTE, MIC-Student Innovation
Category: Software
Theme: Smart Automationtd>
Youtube Link: Not provided
Dataset Link: Not provided
Contact info: Not provided

SIH 2026 Problem Analysis & Solution Architecture Dossier

1. Executive Snapshot

This dossier provides a solution architecture and strategic blueprint for SIH26202, an open-theme Student Innovation problem statement under the All India Council for Technical Education (AICTE) [PS]. The problem addresses the fundamental challenge of intelligent resource management by integrating artificial intelligence with heterogeneous, multi-source data streams to generate actionable insights and transform technology adoption [PS].

To fulfill this mandate, we propose ResourcAI: an AI-powered Multi-Source Resource Intelligence & Optimization Platform [INFERENCE]. ResourcAI ingests real-time and historical telemetry across critical resource vectors (e.g., electrical power, water distribution, campus/municipal facility utilization, and waste systems) from IoT sensors, public open-data platforms, weather feeds, and satellite imagery [INFERENCE]. Using time-series machine learning models, automated data harmonizers, and an explainable AI insight engine, ResourcAI detects resource leakages, forecasts peak demand, optimizes dynamic allocation, and provides automated decision support for facility managers and municipal administrators [INFERENCE].

Metadata Field Value
PS Number SIH26202 [PS]
Title Student Innovation-Ideas focused on the intelligent use of resources for transforming and advancements of technology with combining the artificial intelligence to explore more various sources and get valuable insights. [PS]
Organization AICTE [PS]
Department AICTE, MIC-Student Innovation [PS]
Category Software [PS]
Theme Smart Automation [PS]
Deadline 30 September 2026 [PS]
Ideas Counter 1/500 [PS]

Fundamental System Objective: To transform resource management by unifying heterogeneous multi-source data feeds through AI/ML pipelines to predict consumption, detect operational anomalies, optimize dynamic distribution, and provide actionable decision support [INFERENCE].

2. Problem Deconstruction

The problem description provided in the source JSON states:

"Student Innovation-Ideas focused on the intelligent use of resources for transforming and advancements of technology with combining the artificial intelligence to explore more various sources and get valuable insights." [PS]

We decompose this problem statement into six atomic, non-redundant requirements:

  • Req-1: Open-Ended Student Innovation Framework

    • Source Text: "Student Innovation-Ideas..." [PS]
    • Interpretation: The solution must demonstrate novel conceptualization and execution without relying on a pre-packaged or standard commercial template [INFERENCE].
    • Implementation Implication: The product design must solve a tangible, real-world resource optimization problem (e.g., smart campus, industrial park, or urban ward) while remaining extensible [INFERENCE].
    • Confidence Tag: [PS]
  • Req-2: Intelligent Resource Optimization

    • Source Text: "...focused on the intelligent use of resources..." [PS]
    • Interpretation: The system must monitor, analyze, and optimize physical or digital resources (water, electricity, bandwidth, operational equipment, or spatial assets) to prevent wastage and reduce costs [INFERENCE].
    • Implementation Implication: The system must incorporate quantifiable efficiency metrics (e.g., kWh saved, liters of water conserved, operational downtime avoided) [INFERENCE].
    • Confidence Tag: [PS]
  • Req-3: Technological Advancement and Transformation

    • Source Text: "...for transforming and advancements of technology..." [PS]
    • Interpretation: The system must modernize legacy manual resource tracking (e.g., logbooks, reactive maintenance) into automated, event-driven digital workflows [INFERENCE].
    • Implementation Implication: Legacy infrastructure data must be digitized using modern API architectures, microservices, and web/mobile interfaces [INFERENCE].
    • Confidence Tag: [PS]
  • Req-4: Artificial Intelligence Integration

    • Source Text: "...with combining the artificial intelligence..." [PS]
    • Interpretation: Core system capabilities—such as anomaly detection, demand forecasting, or predictive maintenance—must rely on validated machine learning algorithms rather than static heuristic rules alone [INFERENCE].
    • Implementation Implication: The software architecture must include trained ML inference microservices, automated pipeline training, and model explainability modules [INFERENCE].
    • Confidence Tag: [PS]
  • Req-5: Multi-Source Heterogeneous Data Exploration

    • Source Text: "...to explore more various sources..." [PS]
    • Interpretation: The platform must aggregate and correlate data from multiple disparate sources (e.g., live telemetry, geospatial layers, open government data portals, weather APIs, user reports) [INFERENCE].
    • Implementation Implication: Built-in ETL/ELT connectors are required to ingest structured (SQL/CSV), semi-structured (JSON/GeoJSON), and unstructured (text/telemetry) feeds [INFERENCE].
    • Confidence Tag: [PS]
  • Req-6: Actionable Insight Generation & Decision Support

    • Source Text: "...and get valuable insights." [PS]
    • Interpretation: Raw data processing must produce actionable recommendations, alerts, and executive summaries rather than passive visualization dashboards [INFERENCE].
    • Implementation Implication: Implement an automated insight generation engine (combining statistical anomaly scores with natural-language narrative generation) for operational staff [INFERENCE].
    • Confidence Tag: [PS]

3. Stakeholders & User Needs

Stakeholder Goal Current Pain System Need
Facility / Estate Managers (e.g., Campus / Factory Administrators) Minimize resource overheads, optimize utility usage, and prevent unexpected equipment downtime. [INFERENCE] Manual meter readings, disconnected silos between power/water systems, reactive repair after failures. [KNOWN] Unified multi-resource dashboard with predictive anomaly alerts and automated load balancing recommendations. [INFERENCE]
Field Technicians & Maintenance Crews Identify exact fault locations immediately and resolve leakages/outages efficiently. [INFERENCE] Unclear failure sources, delayed notifications, manual logbooks, lack of historical context on mobile devices. [KNOWN] Mobile-friendly alert interface, precise geospatial pinpointing, offline capability, and recommended fix steps. [INFERENCE]
Executive Leadership / Policy Planners (e.g., AICTE, Institutional Directors) Evaluate sustainability compliance, track carbon emissions, and justify resource budgeting. [INFERENCE] Fragmented quarterly spreadsheets, lack of auditing standards, unquantifiable baseline metrics. [KNOWN] Automated ESG compliance reporting, historical trend analysis, ROI/conservation tracking, and predictive budget forecasting. [INFERENCE]
End-Users (Students, Employees, Citizens) Report resource wastage (e.g., running taps, broken lights) and view resource availability. [INFERENCE] No transparent channel to report issues; zero feedback on resolution status. [KNOWN] Low-friction citizen reporting app/portal with automated photo classification and issue tracking updates. [INFERENCE]

4. Requirements Traceability

Proposed System Feature Direct Requirement Justification Implementation Detail Confidence Tag
Multi-Source Data Ingestion Engine Req-5 (Explore various sources) [PS] Connects REST endpoints, MQTT IoT topics, Open Government Data APIs (data.gov.in), and OpenWeatherMap APIs into a unified data hub. [INFERENCE] [INFERENCE]
Time-Series Demand & Consumption Predictor Req-2 (Intelligent resource use) & Req-4 (Combining AI) [PS] XGBoost / Prophet ML model forecasting hourly water and power consumption 24–72 hours in advance. [INFERENCE] [INFERENCE]
Automated Anomaly & Leakage Detection Pipeline Req-4 (Combining AI) & Req-6 (Get valuable insights) [PS] Isolation Forest / Autoencoder model detecting statistical deviations in real-time sensor streams (e.g., nocturnal water flow spikes indicating leaks). [INFERENCE] [INFERENCE]
Spatial Resource Mapping & GIS Layer Req-3 (Advancements of technology) & Req-5 (Various sources) [PS] Interactive Mapbox/Leaflet GIS interface superimposing weather radar, building boundaries, and IoT sensor status. [INFERENCE] [INFERENCE]
Natural Language Insight & Action Engine Req-6 (Get valuable insights) [PS] LLM-backed (or template-augmented) natural language summary generator translating sensor anomalies into plain English/Hindi maintenance advisories. [INFERENCE] [INFERENCE]
Offline Field Technician Mobile Web App Req-1 (Student Innovation) & Req-3 (Advancements of technology) [PS] PWA featuring IndexedDB caching and background sync (Service Workers) for low-connectivity environments. [INFERENCE] [INFERENCE]

5. Constraints & Environment Realities

  • Connectivity & Bandwidth: Rural, semi-urban, or dense campus environments across India frequently suffer from high latency, packet loss, or periodic cellular outages [KNOWN]. Continuous cloud dependency for sensor streaming or edge control creates single points of failure [INFERENCE].
  • Hardware Diversity: Telemetry sensors span multiple generations—from legacy MODBUS energy meters to low-cost ESP32/Raspberry Pi microcontrollers and modern LoRaWAN water flow meters [KNOWN]. Interfaces must support REST, MQTT, HTTP POST, and CSV/JSON batch ingest [INFERENCE].
  • Power & Network Instability: Field gateways and edge devices may lose main AC power during localized load shedding [KNOWN]. Edge systems require non-volatile buffering (e.g., local SQLite/S3-compatible buffers) to retain telemetry until restoration [INFERENCE].
  • Language & Digital Literacy: Field staff and junior maintenance technicians operate primarily in regional languages (e.g., Hindi, Tamil, Marathi) [KNOWN]. Complex technical graphs must be augmented with simplified color-coded indicators (Green/Yellow/Red) and local language voice/text summaries [INFERENCE].
  • Budget & Infrastructure Limitations: Academic institutions and small municipalities operate under strict budget constraints [KNOWN]. Recommending proprietary enterprise software (e.g., $50,000/year enterprise licenses) is impractical; the stack must be built entirely on open-source frameworks [INFERENCE].

6. Research Questions

  1. Multi-Source Data Harmonization: How can heterogeneous telemetry (differing sample frequencies, missing timestamps, disparate units) be automatically normalized into a standardized schema without manual ETL maintenance? [INFERENCE]
  2. Predictive Accuracy vs. Compute Efficiency: Which low-overhead ML models achieve acceptable time-series forecasting accuracy (e.g., MAPE < 10%) on constrained server hardware during a 36-hour hackathon build? [INFERENCE]
  3. Data Authenticity in Open Datasets: How can open government data sources (e.g., data.gov.in, NDAP, IUDX) be effectively linked with simulated real-time IoT feeds during live judging without introducing data format mismatches? [RESEARCHED]
  4. Offline Resilience: What client-side storage architecture guarantees zero data loss when field technicians record maintenance actions offline? [INFERENCE]
  5. False Positive Suppression: How can the AI model distinguish between normal operational anomalies (e.g., extended night shifts, campus events) and genuine operational failures (e.g., main pipeline rupture) to prevent alert fatigue? [INFERENCE]

7. Data Requirements & Sources

Data Type Purpose Ideal Real-World Source Hackathon Substitute Access Method Availability Privacy Sensitivity Confidence
Grid / Facility Power Consumption Train power baseline and forecast energy spikes. Smart Meters / DISCOM Feeds (e.g., BSES, BESCOM APIs). [RESEARCHED] Open Datasets (e.g., UCI ElectricityLoadDiagrams) + Synthetic IoT Generator. [RESEARCHED] REST API / CSV / MQTT stream. High (Synthetic) / Med (Open). Low (Aggregated building level). [RESEARCHED]
Water Flow & Pressure Telemetry Identify pipe ruptures, nocturnal leaks, and tank overflows. Ultrasonic Water Meters / SCADA municipal feeds. [KNOWN] Synthetic IoT stream generated via Python script mimicking diurnal urban usage. [INFERENCE] MQTT / WebSockets. High (Synthetic). Low. [ASSUMPTION]
Ambient Weather & Solar Radiation Correlate HVAC/cooling energy spikes with external heatwaves; solar generation context. OpenWeatherMap API / IMD (India Meteorological Dept) feeds. [RESEARCHED] OpenWeatherMap Free Tier API + Historical IMD Datasets. [RESEARCHED] REST / JSON. High (Public Key). Public / None. [RESEARCHED]
Geospatial & Building Footprints Map infrastructure networks, pipe routes, and sensor locations. Bhuvan (ISRO) / OpenStreetMap / IUDX geospatial layers. [RESEARCHED] OpenStreetMap GeoJSON / Leaflet layers for chosen target campus. [RESEARCHED] Vector Tile / GeoJSON download. High (OSM). Public / None. [RESEARCHED]
Public Government Data (Socio-Economic / Utility) Provide macroeconomic context and district baselines. Data.gov.in / NDAP (NITI Aayog) / IUDX APIs. [RESEARCHED] Data.gov.in Open API (Real OGD Key) / NDAP CSV dumps. [RESEARCHED] REST / JSON API (api.data.gov.in). [RESEARCHED] High (Free registration). Public domain. [RESEARCHED]
User Anomaly Reports & Images Fine-tune photo classification for broken taps, damaged solar panels, or exposed wiring. Citizen Crowdsourcing / Helpdesk Ticketing System. [INFERENCE] Custom Mobile PWA user upload + Public Image Datasets (e.g., Kaggle Water Leakage Images). [RESEARCHED] HTTP Multipart POST. High (Curated sample). Medium (Excludes PII). [ASSUMPTION]

Data Categorization Breakdown

  • A. Explicitly Mentioned: Multi-source data streams, resource metrics, AI input feeds [PS].
  • B. Inferred Requirements: Weather data, geospatial GeoJSON overlays, open government baseline metrics, time-series telemetry [INFERENCE].
  • C. Must Be Collected: Synthetic real-time MQTT streams, field technician photo submissions [INFERENCE].
  • D. Synthetically Generated: Scaled 24/7 power grid load profiles, multi-meter water pressure fluctuations [ASSUMPTION].
  • E. Needs Validation: Direct live API access to local municipal SCADA systems (assumed closed/restricted during hackathon) [NEEDS VALIDATION].

8. Existing Solutions & Gap Analysis

+-----------------------------------------------------------------------------------+
|                            EXISTING SOLUTIONS LANDSCAPE                           |
+------------------------------------+----------------------------------------------+
| 1. Enterprise BMS (Siemens/Schneider)| Proprietary, $50k+/yr, Siloed, Vendor Lock-in |
| 2. India Urban Data Exch. (IUDX)   | Excellent Data Exchange, No AI Analytics      |
| 3. NITI Aayog NDAP Platform        | Static Historical Data, Zero Live Telemetry  |
| 4. Smart City ICCC Deployments     | High CapEx, Custom-coded, Rigid Rules        |
+------------------------------------+----------------------------------------------+
|                                      GAP IDENTIFIED                               |
| Open-Source, Multi-Source AI Harmonizer & Explainable Predictive Intelligence Engine |
+-----------------------------------------------------------------------------------+
  1. Enterprise Building Management Systems (e.g., Siemens Desigo CC, Schneider EcoStruxure)

    • Description: Proprietary enterprise platforms for monitoring HVAC, power, and lighting in modern commercial complexes [KNOWN].
    • Strengths: Highly reliable, robust industrial protocol support (BACnet, Modbus) [KNOWN].
    • Weaknesses: Prohibitively expensive, vendor lock-in, proprietary closed architectures, lack of multi-source external data integration (e.g., open government feeds) [INFERENCE].
    • Relevance: Benchmarks high-availability SCADA controls [INFERENCE].
    • Gap: Inaccessible to public academic institutions, municipal bodies, and small/medium campuses due to high cost and rigidity [INFERENCE].
    • Source: Official Siemens / Schneider product documentation [1]. Confidence: [KNOWN].
  2. India Urban Data Exchange (IUDX) - SCM & IISc Bengaluru

    • Description: Open-source data exchange platform developed under the Smart Cities Mission to share datasets securely across city departments [RESEARCHED].
    • Strengths: Standardized open APIs (ETSI NGSI-LD), strong security/consent layers, backed by MoHUA and IISc [RESEARCHED].
    • Weaknesses: Serves primarily as a data pipeline/broker; lacks built-in predictive ML analytics and automated anomaly decision engines [INFERENCE].
    • Relevance: Provides the ideal open data protocol standard for resource data ingestion [RESEARCHED].
    • Gap: Leaves a gap for higher-layer intelligent analytics, automated forecasting, and field technician workflow integration [INFERENCE].
    • Source: IUDX Official Portal & GitHub Repositories [2]. Confidence: [RESEARCHED].
  3. National Data and Analytics Platform (NDAP) - NITI Aayog

    • Description: Public data platform consolidating datasets from across central/state government ministries with standardized geographic keys [RESEARCHED].
    • Strengths: Standardized cross-departmental datasets, 5-star data quality standards, high credibility [RESEARCHED].
    • Weaknesses: Hosts static historical data; lacks real-time IoT ingestion and live alerting capacities [INFERENCE].
    • Relevance: Excellent source for baseline contextual data (district-level energy/water infrastructure stats) [RESEARCHED].
    • Gap: Cannot drive real-time operational resource optimization or immediate leakage detection [INFERENCE].
    • Source: NITI Aayog NDAP Portal [3]. Confidence: [RESEARCHED].
  4. Smart City Integrated Command & Control Centres (ICCCs)

    • Description: Centralized municipal monitoring hubs aggregating traffic, waste, and utility feeds across 100+ Indian Smart Cities [RESEARCHED].
    • Strengths: Unified physical control room dashboard, high visibility [RESEARCHED].
    • Weaknesses: Custom-built by system integrators at extreme expense; heavily reliant on human operators watching screens; high rate of false alerts [INFERENCE].
    • Relevance: Illustrates municipal workflow and decision hierarchy [RESEARCHED].
    • Gap: Lacks automated, explainable AI recommendations and lightweight field mobile execution loops [INFERENCE].
    • Source: Ministry of Housing and Urban Affairs (MoHUA) ICCC Guidelines [4]. Confidence: [RESEARCHED].

9. Candidate Solution Approaches

Candidate Approaches Comparison:

+----------------------------+-----------------------------+----------------------------------+
| Approach 1: Static Rules   | Approach 2: DL / CV Heavy   | Approach 3: Hybrid Architecture  |
| (Low Feasibility/Impact)   | (Over-complex / Rigid)      | (OPTIMAL HACKATHON MVP & PROD)   |
+----------------------------+-----------------------------+----------------------------------+
| Threshold Alerts           | Complex Video & Neural Nets | Time-Series ML + Auto-Schema     |
| Dashboard Only             | High GPU Compute Required   | Fast Ingestion + Lightweight XAI |
| High False Positives       | Poor Explainability         | Edge Sync + Actionable Web App   |
+----------------------------+-----------------------------+----------------------------------+

Approach 1: Rule-Based IoT Aggregator & Basic Dashboard

  • Mechanism: Simple threshold triggers (e.g., IF flow_rate > 50 L/min THEN trigger_alert) connected to an open-source React dashboard via HTTP endpoints [INFERENCE].
  • Problem Fit: Low. Fails to satisfy the explicit AI integration requirement (Req-4) [PS].
  • Accuracy Potential: Poor. High false-positive rates due to static threshold rigidity during legitimate peak hours [INFERENCE].
  • Complexity: Very Low [INFERENCE].
  • Cost: Negligible [INFERENCE].
  • Explainability: High (simple rules) [INFERENCE].
  • Hackathon Feasibility: 100% (Can be built in <10 hours) [INFERENCE].
  • Production Feasibility: Low (Doesn't provide true intelligence) [INFERENCE].
  • Risks: Disqualified by judges for lacking meaningful AI implementation [INFERENCE].

Approach 2: Deep Learning & Computer Vision Heavy Monitoring Platform

  • Mechanism: Continuous video surveillance analysis via YOLOv8 for equipment damage/leaks + Deep LSTM autoencoders for multi-sensor time-series prediction [INFERENCE].
  • Problem Fit: Moderate, but overly complex and compute-heavy [INFERENCE].
  • Accuracy Potential: High in controlled environments; brittle under real-world noise [INFERENCE].
  • Complexity: High. Requires cloud GPU instances and heavy video processing pipelines [INFERENCE].
  • Cost: High (GPU compute overhead) [INFERENCE].
  • Explainability: Low ("Black-box" neural network outputs) [INFERENCE].
  • Hackathon Feasibility: Medium-Low. Video processing pipelines and LSTM fine-tuning are prone to live demo failures [INFERENCE].
  • Production Feasibility: Medium. Too costly for rural or resource-constrained deployments [INFERENCE].
  • Risks: High risk of inference latency, thermal throttling on edge devices, and demo failures during time limits [INFERENCE].

Approach 3: Hybrid Architecture — Semantic Data Harmonization + ML Time-Series Forecasting + Explainable AI (XAI) + Edge Offline Sync (RECOMMENDED)

  • Mechanism: Lightweight tabular ML (XGBoost/LightGBM for time-series forecasting, Isolation Forest for anomaly detection) combined with an automated data harmonizer (connecting data.gov.in, OpenWeather, and MQTT streams) and an explainable LLM/template narrative generator for maintenance advisories [INFERENCE].
  • Problem Fit: Perfect. Fully satisfies Req-1 through Req-6 [PS].
  • Accuracy Potential: High (90%+ accuracy on time-series anomaly detection with minimal tuning) [INFERENCE].
  • Complexity: Balanced. Uses fast tabular models and standardized REST/MQTT microservices [INFERENCE].
  • Cost: Minimal (Runs efficiently on standard CPU cloud instances / free-tier services) [INFERENCE].
  • Explainability: High (SHAP feature attribution + plain-language natural language summaries) [INFERENCE].
  • Hackathon Feasibility: Excellent. Fully buildable and demonstrable by a 4–6 student team in 36 hours [INFERENCE].
  • Production Feasibility: High. Highly scalable, cloud-native, and edge-resilient [INFERENCE].
  • Risks: Low. Managed via clear simulation fallback scripts [INFERENCE].

10. Recommended Approach & Why

We select Approach 3 (Hybrid Architecture) as the winning strategy [INFERENCE].

Why Alternatives Were Rejected:

  1. Rejection of Approach 1 (Rule-Based System): While trivial to implement, it fails to satisfy the problem statement's explicit mandate for artificial intelligence [PS]. Static thresholds produce extreme false-positive rates in variable environments (e.g., high water usage during campus sports meets flagged as leaks), undermining user trust [INFERENCE].
  2. Rejection of Approach 2 (Deep Learning / CV Heavy): Deep neural networks (LSTM / Transformers / Dense CV pipelines) introduce unnecessary compute overhead, high latency, and black-box outputs [INFERENCE]. In resource management, facility managers require explainable reasoning (e.g., "Pump #3 flagged due to 35% current draw spike uncorrelated with pressure output") rather than opaque probability scores [INFERENCE]. Furthermore, streaming multiple HD video feeds in hackathon conditions creates unnecessary failure points [INFERENCE].

Why Approach 3 Wins:

  • Strict Alignment: Solves all explicit [PS] requirements: intelligent resource optimization, multi-source ingestion (data.gov.in, weather, IoT), AI forecasting, and actionable insight generation [INFERENCE].
  • Demo Reliability: Tabular ML models (XGBoost, Isolation Forest) train in seconds and infer in milliseconds on standard CPU instances, guaranteeing instantaneous response during live judging [INFERENCE].
  • Explainability: Incorporates SHAP values and natural language generation, directly fulfilling the "get valuable insights" mandate [PS].
  • Feasibility: Allows clean division of labor among a 4–6 student team (2 Backend/ML engineers, 2 Frontend/GIS developers, 1 IoT/Data simulator, 1 System Architect) [INFERENCE].

11. Technical Architecture

+---------------------------------------------------------------------------------------------------+
|                                     RESOURCAI SYSTEM ARCHITECTURE                                 |
+---------------------------------------------------------------------------------------------------+

[ LAYER 1: DATA INGESTION & SOURCES ]
  +-----------------------+  +-----------------------+  +-----------------------+  +-----------------------+
  | IoT Telemetry Stream  |  | Open Govt Data (OGD)  |  |  OpenWeatherMap API   |  | Citizen Report Mobile |
  | (MQTT / HTTP Telemetry|  | (api.data.gov.in REST)|  | (Temp, Humidity, Rain)|  |  (Photo, Location, Tx)|
  +-----------+-----------+  +-----------+-----------+  +-----------+-----------+  +-----------+-----------+
              |                          |                          |                          |
              +--------------------------+------------+-------------+--------------------------+
                                                      |
                                                      v
[ LAYER 2: INGESTION & HARMONIZATION GATEWAY ]
  +-------------------------------------------------------------------------------------------------+
  | FastAPI Ingestion Router / EMQX MQTT Broker (Data Schema Harmonizer & Validator)               |
  +-------------------------------------------------------------------------------------------------+
                                                      |
                                                      v
[ LAYER 3: STORAGE & EVENT STREAMING ]
  +-------------------------------------+    +------------------------------------------------------+
  | TimescaleDB / PostgreSQL (Relational|    | Redis Cache (Live Sensor Telemetry Pub/Sub Buffer)   |
  | & Time-Series Sensor Logs + GIS)    |    |                                                      |
  +------------------+------------------+    +--------------------------+---------------------------+
                     |                                                  |
                     +--------------------------+-----------------------+
                                                |
                                                v
[ LAYER 4: AI / ML PROCESSING PIPELINE ]
  +-------------------------------------------------------------------------------------------------+
  |  +------------------------------+  +-------------------------------+  +----------------------+  |
  |  | XGBoost / Prophet Predictor  |  | Isolation Forest Anomaly Engine|  | XAI / Natural Lang.  |  |
  |  | (24-72h Demand Forecasting)  |  | (Leak / Outage / Spikes)      |  | Insight Synthesizer  |  |
  |  +------------------------------+  +-------------------------------+  +----------------------+  |
  +-----------------------------------------------------+-------------------------------------------+
                                                        |
                                                        v
[ LAYER 5: API & APPLICATION SERVER ]
  +-------------------------------------------------------------------------------------------------+
  | FastAPI Backend Services (REST / WebSockets / JWT Auth / Role-Based Access Control)            |
  +-------------------------------------------------------------------------------------------------+
                                                        |
                                                        v
[ LAYER 6: PRESENTATION & CLIENT DASHBOARDS ]
  +---------------------------------------+             +-------------------------------------------+
  | Web Operations Center (Next.js 14,   |             | Field Technician Mobile App (PWA, React,  |
  | Mapbox GIS, Recharts Analytics)       |             | IndexedDB Offline Sync, Service Workers)   |
  +---------------------------------------+             +-------------------------------------------+

Detailed Data Flow Narrative

  1. Ingestion Step: IoT telemetry (simulated via Python/MQTT or physical ESP32 nodes) transmits temperature, voltage, water flow, and pressure readings at 5-second intervals to an EMQX/FastAPI ingestion endpoint [INFERENCE]. Simultaneously, asynchronous background workers pull ambient weather data from OpenWeatherMap and regional baselines from api.data.gov.in [RESEARCHED].
  2. Harmonization & Storage Step: Incoming payloads enter the Schema Harmonizer, which validates data types, injects ISO timestamps, converts units to standard SI (e.g., kWh, Liters/min), and writes to TimescaleDB (PostgreSQL time-series extension) [INFERENCE]. Hot sensor state is published to Redis for sub-second UI updates via WebSockets [INFERENCE].
  3. AI Inference Loop: Every 60 seconds (or on event triggers), the ML service pulls the last 60 minutes of sensor telemetry from Redis/TimescaleDB [INFERENCE].
    • Isolation Forest evaluates feature vectors (flow rate, delta pressure, hour of day) to calculate anomaly scores [INFERENCE].
    • XGBoost predicts expected demand for the next 24 hours based on historical trends, weather forecasts, and calendar events [INFERENCE].
    • If an anomaly score exceeds a dynamic threshold (e.g., > 0.75), the XAI Insight Synthesizer combines model feature attribution scores (SHAP) with a rule-augmented template to generate a plain-text advisory (e.g., "Warning: Pipe Sector B3 shows 42% unexpected nocturnal flow increase, indicating a downstream leak.") [INFERENCE].
  4. Action & Notification Step: The FastAPI backend pushes WebSocket alerts to the Operations Web Dashboard and dispatches an automated SMS/Push notification to field maintenance personnel [INFERENCE].
  5. Field Mobile Execution Step: Field technicians receive the ticket on their PWA. If offline, the ticket details, geospatial pipe maps, and resolution forms are accessed via client-side IndexedDB [INFERENCE]. Upon completing the repair, the technician uploads a photo and status update; sync occurs automatically when network connectivity is restored [INFERENCE].

12. Technology Stack

Layer Selected Technology Why Chosen Alternative Considered Why Alternative Rejected
Frontend Framework Next.js 14 (React / TypeScript) Server-side rendering for high performance, excellent UI components (Shadcn UI, TailwindCSS), native PWA support. [INFERENCE] Angular / Vue.js Slower prototyping during hackathon; smaller ecosystem for rapid UI components. [INFERENCE]
GIS Mapping Mapbox GL JS / Leaflet Smooth vector tile rendering, custom GeoJSON layering for pipe/grid networks, offline tile caching. [RESEARCHED] Google Maps API Strict rate limits, costly API billing, proprietary license restrictions. [INFERENCE]
Backend Framework Python FastAPI Asynchronous execution, native OpenAPI docs, seamless integration with Python ML/data science libraries. [INFERENCE] Node.js (Express) Express requires external Python child process spawns to execute ML inference, introducing latency. [INFERENCE]
Time-Series Database TimescaleDB (PostgreSQL) Combines standard SQL relational capabilities with hypertable time-series optimizations; handles Millions of data points easily. [RESEARCHED] InfluxDB Unfamiliar SQL variant (Flux query language), harder to perform complex relational joins during a hackathon. [INFERENCE]
In-Memory Cache & Stream Redis High-speed pub/sub messaging for live WebSocket updates and sub-millisecond caching of hot sensor states. [KNOWN] Memcached Lacks pub/sub capabilities and complex data structures (hashes, sorted sets). [INFERENCE]
AI / ML Ecosystem Scikit-learn, XGBoost, SHAP Fast training times, proven time-series tabular performance, robust feature attribution for explainability. [KNOWN] PyTorch / TensorFlow Excessive model size, slow training on CPU, high setup overhead during hackathons. [INFERENCE]
IoT Broker EMQX / Mosquitto MQTT Standard lightweight IoT communication protocol, low bandwidth overhead, ideal for poor networks. [KNOWN] HTTP REST Telemetry HTTP headers introduce massive data overhead per 5-second sensor packet. [INFERENCE]
Containerization & Hosting Docker & Docker Compose Guarantees multi-container local stack reproducibility across student laptops and cloud VMs. [KNOWN] Manual OS Setup Risk of environment mismatches ("works on my machine" issues) during live judging. [INFERENCE]

13. AI/ML Justification

+----------------------------------------------------------------------------------+
|                            AI/ML MODULE SPECIFICATION                            |
+---------------------+-----------------------------+------------------------------+
| AI Component        | 1. Demand Predictor         | 2. Anomaly Engine            |
+---------------------+-----------------------------+------------------------------+
| Primary Objective   | 24-72h Resource Forecast    | Real-Time Leakage Detection  |
| Algorithm / Model   | XGBoost / Prophet           | Isolation Forest             |
| Core Input          | Historical telemetry + Temp | Flow, Pressure, Delta-time   |
| Expected Output     | kW / Liter curves + bounds  | Anomaly Score (0.0 to 1.0)   |
| Why AI Over Rules?  | Handles non-linear weather  | Adapts to dynamic seasonal   |
|                     | and calendar interactions   | baseline changes             |
| Primary Failure     | Outlier weather events      | Sensor drift / freeze        |
| Oversight           | Operator manual override    | Human field verification     |
+---------------------+-----------------------------+------------------------------+

Module 1: Time-Series Demand & Consumption Predictor

  1. Exact Problem AI Solves: Predicts hourly electricity and water consumption 24 to 72 hours in advance to optimize pump scheduling and battery storage [INFERENCE].
  2. Input: Hourly historical consumption (kWh/Liters), day of week, hour of day, holiday flag, ambient temperature (°C), humidity (%) [INFERENCE].
  3. Output: Hourly predicted consumption curve with upper/lower 95% confidence intervals [INFERENCE].
  4. Why Simpler Rules Fail: Static linear rules cannot account for multi-variable interactions (e.g., ambient heatwave combined with weekend campus occupancy drops) [INFERENCE].
  5. Data Required: Minimum 30 days of hourly consumption telemetry (synthetically scaled for hackathon) [ASSUMPTION].
  6. Evaluation Metric: Mean Absolute Percentage Error (MAPE < 8%), Root Mean Square Error (RMSE) [INFERENCE].
  7. Failure Action: Falls back to historical 7-day rolling average consumption curve [INFERENCE].
  8. Training: Pre-trained on baseline dataset prior to hackathon demo; updated periodically [ASSUMPTION].
  9. Fine-Tuning: Not required during demo [INFERENCE].
  10. RAG: Not required [INFERENCE].
  11. Computer Vision: Not required [INFERENCE].
  12. Speech Processing: Not required [INFERENCE].
  13. Forecasting: Yes (time-series forecasting) [INFERENCE].
  14. Human Oversight: Facility manager can override automated pump schedule recommendations [INFERENCE].

Module 2: Multi-Sensor Anomaly & Leakage Detection Engine

  1. Exact Problem AI Solves: Detects subtle equipment anomalies, water pipeline breaches, and electrical line loss in real time [INFERENCE].
  2. Input: Rolling 15-minute sensor vectors (water flow rate, water pressure, line voltage, current draw, power factor) [INFERENCE].
  3. Output: Anomaly Score ($0.0$ to $1.0$) + SHAP feature importance ranking [INFERENCE].
  4. Why Simpler Rules Fail: Fixed threshold alerts fail during changing operational phases (e.g., nocturnal maintenance vs nocturnal pipe rupture look identical under simple flow limits) [INFERENCE].
  5. Data Required: Multi-sensor time-series logs containing both baseline normal usage and injected failure states [INFERENCE].
  6. Evaluation Metric: Precision, Recall, F1-Score (> 0.90), False Positive Rate (< 3%) [INFERENCE].
  7. Failure Action: If model output is uncertain ($0.45 < \text{score} < 0.60$), marks alert status as "Pending Field Audit" rather than triggering automated shutoff [INFERENCE].
  8. Training: Isolation Forest trained on clean baseline data [INFERENCE].
  9. Fine-Tuning: Unsupervised anomaly scoring [INFERENCE].
  10. RAG: Not required [INFERENCE].
  11. Computer Vision: Not required [INFERENCE].
  12. Speech Processing: Not required [INFERENCE].
  13. Forecasting: No (Real-time detection) [INFERENCE].
  14. Human Oversight: Mandatory human approval before dispatching field maintenance teams or initiating remote valve shutoffs [INFERENCE].

Where AI Should NOT Be Used:

  • User Authentication & Role Management: Standard JWT and RBAC protocols MUST be used. Never use AI for access control decisions [INFERENCE].
  • Raw Sensor Threshold Safety Limits: Hardware safety triggers (e.g., immediate electrical surge circuit breaker trip at >440V) MUST rely on deterministic hardware/rule triggers, NOT ML models [INFERENCE].
  • Database CRUD Operations: Use standard relational database queries, not LLM-generated SQL queries in critical paths [INFERENCE].

14. Data Architecture & Offline/Low-Network Design

TimescaleDB Schema (PostgreSQL Extension)

-- Core Telemetry Hypertable for Time-Series Ingestion
CREATE TABLE sensor_telemetry (
    timestamp TIMESTAMPTZ NOT NULL,
    sensor_id VARCHAR(64) NOT NULL,
    resource_type VARCHAR(32) NOT NULL, -- 'WATER', 'ELECTRICITY', 'SOLAR'
    location_id VARCHAR(64) NOT NULL,
    flow_rate DOUBLE PRECISION, -- Liters/min
    pressure DOUBLE PRECISION,  -- PSI
    voltage DOUBLE PRECISION,    -- Volts
    current_draw DOUBLE PRECISION, -- Amps
    power_kw DOUBLE PRECISION,   -- kW
    raw_payload JSONB
);
SELECT create_hypertable('sensor_telemetry', 'timestamp');

-- Anomaly Log Table
CREATE TABLE anomaly_alerts (
    alert_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    created_at TIMESTAMPTZ DEFAULT NOW(),
    sensor_id VARCHAR(64) REFERENCES sensor_telemetry(sensor_id),
    anomaly_score DOUBLE PRECISION NOT NULL,
    severity VARCHAR(16) NOT NULL, -- 'LOW', 'MEDIUM', 'HIGH', 'CRITICAL'
    xai_explanation TEXT NOT NULL,
    status VARCHAR(32) DEFAULT 'OPEN' -- 'OPEN', 'DISPATCHED', 'RESOLVED'
);

Offline & Synchronization Architecture

+-----------------------------------------------------------------------------------+
|                        OFFLINE FIELD TECHNICIAN SYNC FLOW                         |
+-----------------------------------------------------------------------------------+

  [ FIELD MOBILE PWA ]
          |
          +---> Active Internet Connection? 
          |         |
          |         +--- YES ---> Submit Direct via HTTPS REST ---> [ FASTAPI BACKEND ]
          |         |
          |         +--- NO  ---> Write Ticket to Local IndexedDB Cache
          |                           |
          |                           v
          |                     Background Service Worker
          |                     (Listens for 'online' Event)
          |                           |
          |                           v
          |                     Re-establish Connection
          |                           |
          |                           v
          |                     Bulk Push Queued Requests to /api/v1/sync/batch
          |                           |
          v                           v
  [ SERVER DB ] <--- Apply Idempotent Upsert & Resolve Conflicts via Last-Write-Wins
  • Local Storage: Client PWA utilizes IndexedDB (via dexie.js) to store pending maintenance logs, photo data URLs, and cached geospatial vector tiles [INFERENCE].
  • Conflict Resolution: Every client transaction generates a local UUID and client timestamp. The server applies Last-Write-Wins (LWW) with idempotent processing based on transaction UUIDs [INFERENCE].
  • Bandwidth Reduction: Telemetry payloads use compact JSON key names and optional GZIP compression. Background polling uses HTTP conditional headers (If-None-Match / ETag) to prevent redundant data transfer over cellular links [INFERENCE].

15. Security, Privacy & Governance

  • Personal & Location Data Protection: System telemetry captures institutional and municipal asset metrics. Personal Identifiable Information (PII) is restricted to maintenance staff contact info, which is encrypted at rest using AES-256 [INFERENCE].
  • Authentication & Authorization: Secure JWT token authentication with strict Role-Based Access Control (RBAC) [INFERENCE].
    • Roles: SUPER_ADMIN, FACILITY_MANAGER, FIELD_TECHNICIAN, PUBLIC_CITIZEN [INFERENCE].
  • Data Encryption: TLS 1.3 enforced for all in-transit API and MQTT communication. Sensitive environment credentials managed strictly via .env secrets [INFERENCE].
  • Data Retention & Auditing: Immutable audit logging for all control actions (e.g., remote pump shutdown, valve alteration). Retention policies auto-archive granular 5-second raw telemetry after 90 days into aggregate daily summaries to minimize storage overhead [INFERENCE].
  • Liability Disclaimer & Regulatory Validation: Crucial Governance Requirement: The system is an operational support tool [INFERENCE]. Automated shutoff recommendations require explicit human approval for safety-critical infrastructure [INFERENCE]. The prototype output does not constitute certified legal compliance documentation without independent audit verification [INFERENCE].

16. MVP Scope (Hackathon Build)

+-----------------------------------------------------------------------------------+
|                                 MVP SCOPE MATRIX                                  |
+--------------------------------------------------+--------------------------------+
|                   IN SCOPE                       |          OUT OF SCOPE          |
|              (Must & Should Build)               |      (Future / Production)     |
+--------------------------------------------------+--------------------------------+
| * Multi-Source Ingestion (MQTT + Weather + OGD)  | * Physical SCADA PLC Hardware  |
| * Real-time Anomaly Engine (Isolation Forest)    | * Satellite Imagery Pipelines  |
| * 24h Demand Forecast (XGBoost)                  | * Automated Billing Systems    |
| * GIS Mapbox UI with Live Piping/Grid Status     | * Proprietary BMS Integrations |
| * Field Technician PWA with Offline Sync         | * Multi-Tenant SaaS Billing    |
| * Plain-Language XAI Maintenance Summaries       | * Custom Hardware PCB Design   |
+--------------------------------------------------+--------------------------------+

In Scope (MUST & SHOULD BUILD for 36-Hour Hackathon)

  • Live Ingestion Gateway: Functional FastAPI REST and MQTT ingestion server handling simulated multi-meter streams [INFERENCE].
  • Open Data Integration: Live feed connector fetching real datasets from data.gov.in (OGD API) and weather telemetry from OpenWeatherMap [RESEARCHED].
  • AI Processing Engines:
    1. Isolation Forest model running anomaly scoring on live flow/power streams [INFERENCE].
    2. XGBoost model predicting 24-hour resource demand curves [INFERENCE].
    3. Feature attribution (SHAP) producing plain-language fault summaries [INFERENCE].
  • Web Operations Dashboard: Next.js dashboard with interactive Mapbox spatial visualizer, live Recharts metrics, and anomaly alert queue [INFERENCE].
  • Mobile Field App (PWA): Mobile interface enabling field technicians to view alerts, record fixes, and demonstrate offline queuing + auto-sync [INFERENCE].

Described Only / Out of Scope (DO NOT BUILD DURING HACKATHON)

  • Direct hardware SCADA/PLC serial wire integration (Simulated realistically via software scripts) [INFERENCE].
  • Commercial automated billing and payment gateway processing [INFERENCE].
  • Real-time satellite imagery downloading and heavy computer vision processing [INFERENCE].
  • Enterprise multi-tenant SaaS subscription billing layers [INFERENCE].

17. Live Demo Simulation Plan

To ensure a seamless, reliable demonstration during SIH judging without relying on brittle external hardware or live municipal SCADA feeds:

+-----------------------------------------------------------------------------------+
|                            LIVE DEMO SIMULATION ENGINE                            |
+-----------------------------------------------------------------------------------+

  [ TELEMETRY SIMULATOR SCRIPT ]
        |
        +---> Mode 1: Normal Diurnal Baseline (Simulates 100 Smart Meters)
        |
        +---> Mode 2: INJECT WATER PIPE LEAK (Simulates 40 L/min nocturnal spike)
        |
        +---> Mode 3: INJECT POWER SURGE (Simulates HVAC phase imbalance)
        |
        v
  [ REAL FASTAPI INGESTION ENDPOINT ] ---> [ REAL ML INFERENCE ] ---> [ REAL DASHBOARD ]
  1. IoT Sensor Telemetry Simulator: A Python script (simulator.py) generates multi-sensor MQTT data mimicking 100 smart water and power meters across a campus footprint [INFERENCE].
    • Interactive Trigger: The team can click a button on a hidden demo panel to "Inject Water Leakage" or "Inject Electrical Phase Loss" [INFERENCE].
    • Honesty Assurance: Clearly explain to judges: "The telemetry feed is simulated via realistic stochastic models, but the ingestion pipeline, ML inference, database writes, and dashboard UI run on live production code." [INFERENCE]
  2. Government Open Data Feeds: The platform connects directly to api.data.gov.in using an active OGD API key to pull real district-level historical baseline data, demonstrating genuine multi-source exploration [RESEARCHED].
  3. Weather Feed Integration: Uses live OpenWeatherMap API calls targeting the competition city (e.g., New Delhi) to adjust current cooling demand baselines [RESEARCHED].
  4. Offline Synchronization Demonstration:
    • Step A: Load the Field App on a mobile browser or tablet [INFERENCE].
    • Step B: Turn on "Airplane Mode" in front of the judges [INFERENCE].
    • Step C: Submit a ticket resolution form and photo upload; show the PWA notifying "Saved to Offline Queue" [INFERENCE].
    • Step D: Disable "Airplane Mode"; show the background worker auto-flushing the queue to the backend and updating the main Operations Dashboard in real time [INFERENCE].

18. Implementation Roadmap

+-----------------------------------------------------------------------------------+
|                        SIH 2026 IMPLEMENTATION TIMELINE                           |
|                        Target Deadline: 30 September 2026                         |
+-----------------------------------------------------------------------------------+

  [ PHASE 1: RESEARCH & ARCHITECTURE ]  ---> July 15 - August 05, 2026
  - Requirements freezing & OGD API key registration
  - Data schema standardization & Docker stack initialization

  [ PHASE 2: CORE ML & BACKEND BUILD ]  ---> August 06 - August 25, 2026
  - Train XGBoost forecasting & Isolation Forest models
  - Develop FastAPI ingestion, TimescaleDB models, & MQTT broker

  [ PHASE 3: FRONTEND & PWA DEVELOP ]   ---> August 26 - September 15, 2026
  - Next.js Web Dashboard & Mapbox GIS pipeline build
  - Field Technician PWA with IndexedDB offline sync

  [ PHASE 4: TESTING, SIM & DEMO DRY-RUN]---> September 16 - September 30, 2026
  - Chaos testing, offline sync validation, & demo rehearsal
  - Final SIH Submission & Presentation Polish
  • Phase 1: Architecture & Data Pipeline Setup (July 15 – August 05, 2026)
    • Register API keys (data.gov.in, OpenWeather, Mapbox) [RESEARCHED].
    • Define TimescaleDB schemas and set up Docker environment [INFERENCE].
  • Phase 2: Core ML Engine & Backend Ingestion (August 06 – August 25, 2026)
    • Train XGBoost consumption model and Isolation Forest anomaly detector [INFERENCE].
    • Build FastAPI ingestion microservices, Redis caching, and WebSocket alert streams [INFERENCE].
  • Phase 3: Web Dashboard & PWA Development (August 26 – September 15, 2026)
    • Implement Next.js 14 Web Operations Dashboard with Mapbox GIS visualizer [INFERENCE].
    • Build Field Mobile PWA with Service Worker offline queueing [INFERENCE].
  • Phase 4: Integration, Testing & Demo Dry-Run (September 16 – September 30, 2026)
    • Conduct simulated end-to-end stress tests and offline sync validation [INFERENCE].
    • Finalize slide deck, record video walkthrough, and submit dossier before September 30, 2026 deadline [PS].

19. Testing & Validation Plan

Test Category Test Objective & Methodology Pass Criteria Target Metric
Functional Ingestion Push 1,000 simulated MQTT sensor payloads/sec to FastAPI ingestion gateway. [INFERENCE] Zero dropped packets; 100% written to TimescaleDB. [INFERENCE] Latency < 100ms. [INFERENCE]
AI Anomaly Detection Inject synthetic pipe leak anomalies into flow streams. [INFERENCE] Model successfully flags leak with correct SHAP attribution. [INFERENCE] Precision > 92%, Recall > 90%. [INFERENCE]
False Positive Suppression Feed legitimate high-usage spikes (e.g., scheduled campus irrigation). [INFERENCE] Model suppresses false alerts by correlating with calendar/irrigation schedule data. [INFERENCE] False Positive Rate < 3%. [INFERENCE]
Offline Sync Reliability Submit 20 maintenance tickets in PWA under simulated network loss, then restore connection. [INFERENCE] All 20 queued records auto-sync without duplicates or loss. [INFERENCE] 0% Data Loss. [INFERENCE]
GIS Map Performance Render 500 spatial pipe nodes and sensor markers simultaneously on Mapbox canvas. [INFERENCE] Smooth interactive zooming/panning without UI freeze. [INFERENCE] > 55 FPS render speed. [INFERENCE]
Security Audit Execute unauthorized REST API calls without valid JWT token. [INFERENCE] System returns HTTP 401 Unauthorized instantly. [INFERENCE] 100% Access Control Block. [INFERENCE]

20. Risk Register

Risk Likelihood Impact Severity Mitigation Strategy
Public Open Data API Outage / Rate Limit Medium Medium Moderate Local caching in Redis/TimescaleDB of all fetched data.gov.in historical baselines; offline JSON fallback files. [INFERENCE]
Overfitting in Anomaly Detection Medium High High Train Isolation Forest on diverse synthetic noise profiles; combine statistical scoring with dynamic baseline thresholds. [INFERENCE]
Live Demo Network Instability High High Critical Run entire stack locally via Docker Compose on the host laptop; use local localhost endpoints so web/mobile demos do not require external internet. [INFERENCE]
Poor Field PWA Offline Sync Low High High Use Dexie.js for IndexedDB management; implement background sync tasks with explicit fallback "Manual Sync" UI button. [INFERENCE]
Judges Question AI Necessity Medium High High Prepare clear side-by-side comparison during demo showing how static rules fail on variable diurnal data while ML succeeds. [INFERENCE]

21. Cost & Scalability

Hackathon Prototype Cost

  • Cloud Hosting: $0 (Runs locally via Docker Compose on student laptops) [INFERENCE].
  • Database & Cache: $0 (Open-source TimescaleDB & Redis community editions) [KNOWN].
  • APIs: $0 (Utilizes free-tier OpenWeatherMap, free Mapbox public token, and free data.gov.in OGD developer key) [RESEARCHED].
  • Total Hackathon Cost: ₹0 / $0 [INFERENCE].

Production Deployment (e.g., Large Academic Campus or Municipal Ward)

  • Cloud Infrastructure (AWS/GCP): ~₹8,000 - ₹15,000 / month ($100 - $200/mo) for managed Kubernetes cluster, PostgreSQL TimescaleDB instance, and Redis cache [INFERENCE].
  • IoT Gateways & Hardware: ~₹1,500 per smart meter node (ESP32 + RS485 Modbus converter + Flow/Power CT clamps) [KNOWN].
  • Scalability Strategy: Microservices architecture allows horizontal auto-scaling of the FastAPI ingestion gateway during high-traffic telemetry periods. TimescaleDB hypertable chunking maintains sub-second query performance even across billions of historical sensor records [INFERENCE].

22. Differentiation

+-----------------------------------------------------------------------------------+
|                            WHY RESOURCAI WIN IN SIH                               |
+-----------------------------------------------------------------------------------+
| Feature                    | Generic Submissions      | ResourcAI Platform        |
+----------------------------+--------------------------+---------------------------+
| Multi-Source Integration   | Single sensor feed only  | IoT + Weather + OGD APIs  |
| AI Capability              | Static threshold rules   | XGBoost + Isolation Forest|
| Insight Engine             | Raw charts only          | Explainable XAI Summaries |
| Field Connectivity         | Requires continuous internet | PWA with IndexedDB Sync|
| Architecture Transparency  | Opaque black-box code    | Open-Source Modular Stack |
+-----------------------------------------------------------------------------------+
  1. Multi-Source Ingestion vs. Single-Silo Tools: While generic hackathon projects read from a single mock database, ResourcAI actively correlates live telemetry with real government datasets (data.gov.in) and ambient weather inputs, fulfilling Req-5 [PS].
  2. Explainable AI (XAI) vs. Opaque Models: Instead of displaying an unhelpful "Error Code 500" or raw anomaly probability, ResourcAI generates plain-language operational summaries (e.g., "35% abnormal pressure drop detected in Block B, unexplainable by weather or schedule"), directly satisfying Req-6 [PS].
  3. Resilient Offline Execution: Most student projects fail when internet connectivity drops. ResourcAI's PWA maintains full operational workflow capability offline, demonstrating field-readiness [INFERENCE].

23. Future Scope

  • Integration with Bhuvan (ISRO) Satellite Feeds: Incorporating satellite imagery layers for wide-area thermal mapping, urban heat island tracking, and open reservoir water storage estimation [RESEARCHED].
  • Automated Demand Response & Battery Storage Optimization: Connecting predictive energy models directly to smart microgrid battery inverters to automatically store cheap off-peak power and discharge during peak tariff hours [INFERENCE].
  • Automated Maintenance Dispatch Integration: Extending the PWA into a complete Computerized Maintenance Management System (CMMS) featuring automated spare part inventory tracking and AI worker route optimization [INFERENCE].

24. Assumptions & Open Items Log

Consolidated Assumptions

  • [ASSUMPTION-1]: Sensor telemetry can be synthetically generated using verified stochastic diurnal profiles during the hackathon build without sacrificing architectural validity.
  • [ASSUMPTION-2]: A 30-day baseline dataset is sufficient to train a high-accuracy tabular XGBoost forecasting model for demo purposes.
  • [ASSUMPTION-3]: Evaluators appreciate local Docker Compose execution to guarantee demo stability over unpredictable venue Wi-Fi.

Consolidated Open Items (Needs Validation)

  • [NEEDS VALIDATION-1]: Verification of exact real-time bandwidth limits on municipal LoRaWAN gateways in semi-urban deployment zones.
  • [NEEDS VALIDATION-2]: Direct API access protocols for specific local municipal SCADA networks (assumed restricted; simulated for hackathon).

Final Recommendation

Build ResourcAI—an open-source, hybrid AI multi-source resource intelligence platform combining FastAPI, TimescaleDB, Next.js 14, XGBoost, Isolation Forest, and an offline-first PWA [INFERENCE].

Recommended Stack

  • Frontend: Next.js 14 (TypeScript), TailwindCSS, Mapbox GL JS, PWA (Dexie.js IndexedDB) [INFERENCE].
  • Backend: Python FastAPI, EMQX MQTT Broker, Celery background workers [INFERENCE].
  • Database & Cache: TimescaleDB (PostgreSQL) + Redis [INFERENCE].
  • AI/ML: XGBoost, Isolation Forest (Scikit-learn), SHAP [INFERENCE].

Biggest Dependency

Access to reliable weather and government open data API keys (data.gov.in OGD key) [RESEARCHED].

Biggest Risk

Venue Wi-Fi instability during live judging [INFERENCE]. (Mitigated by embedding full local execution inside Docker Compose) [INFERENCE].

Biggest Technical Challenge

Achieving real-time, low-latency automated schema normalization across disparate data sources (MQTT streams vs REST JSON) [INFERENCE].

First 5 Actions

  1. Form team role split (2 Backend/ML, 2 Frontend/GIS, 1 Data/Sim, 1 Lead) [INFERENCE].
  2. Register for free API keys on data.gov.in, OpenWeatherMap, and Mapbox [RESEARCHED].
  3. Initialize git repository with Docker Compose template containing PostgreSQL/TimescaleDB, Redis, and FastAPI [INFERENCE].
  4. Develop the Python multi-sensor synthetic telemetry script (simulator.py) [INFERENCE].
  5. Train baseline Isolation Forest model on sample time-series data [INFERENCE].

Validation Before Coding

Verify that api.data.gov.in returns clean JSON responses for target utility datasets using the team's registered API key [RESEARCHED].

Buildability Score /100

92/100 (Highly buildable and demonstrable by a focused 4–6 student team in a 36-hour hackathon window) [INFERENCE].

Confidence

High Confidence (Solution aligns with all explicit [PS] rules and incorporates verified open-data research) [INFERENCE].

Research Sources

  1. Siemens Desigo CC Building Management System Documentation

    • URL: https://www.siemens.com/global/en/products/buildingtechnologies/building-management/desigo.html [1]
    • Source Type: Official Product Documentation
    • Supported Claim: Commercial BMS platforms are proprietary, high-cost, and siloed from open data portals.
    • Reliability: High (Official Vendor Documentation).
  2. India Urban Data Exchange (IUDX) Open Platform Architecture

    • URL: https://iudx.org.in/ [2]
    • Source Type: Official Portal & Open Source Repository (MoHUA / IISc)
    • Supported Claim: IUDX provides standardized open API specifications (ETSI NGSI-LD) for Indian smart city data exchange.
    • Reliability: High (Government & Academic Initiative).
  3. National Data and Analytics Platform (NDAP) - NITI Aayog

    • URL: https://ndap.niti.gov.in/ [3]
    • Source Type: Official Government Portal
    • Supported Claim: NDAP hosts standardized historical public datasets from 46+ Indian ministries with uniform geographic spines.
    • Reliability: High (Official NITI Aayog Platform).
  4. Data.gov.in - Open Government Data (OGD) Platform India

    • URL: https://data.gov.in/ [1.1]
    • Source Type: Official Open Data Portal
    • Supported Claim: Offers public REST APIs (api.data.gov.in) providing access to thousands of Indian government datasets across energy, water, and infrastructure sectors.
    • Reliability: High (Official Government Open Data Portal).
  5. Integrated Command and Control Centres (ICCC) Guidelines - Smart Cities Mission

    • URL: https://smartcities.gov.in/ [3.5]
    • Source Type: Ministry Policy Document
    • Supported Claim: ICCCs serve as central municipal operational hubs but face data integration bottlenecks across proprietary subsystems.
    • Reliability: High (Ministry of Housing and Urban Affairs).
02 / What our

DEVELOPERS SAY

" 30M+ Google Gemini tokens went into researching, analyzing, and understanding all 233 SIH problem statements to make them easier to explore and solve. "
Satyam Kumar
Satyam Kumar
CEO , Full Stack Developer
" The platform makes SIH problem statements much easier to understand. Having everything from the problem details to the procedure in one place. "
Rishabh Ranjan
Rishabh Ranjan
COO , Content Writer
" Oh, you got ads? Well, we need to make money too! But, you can use our platform to help you win SIH and take home the prize money. "
Himanshu Kumar
Himanshu Kumar
CMO , Product Reviewer
03 / Are You

READY TO
BUILD?

Get in touch if you need help bringing your ideas to life, or simply have an interesting idea you'd like to talk through. I'm always open to a conversation and exploring new possibilities together.