An AI-powered web platform that lets authorities and Members of Parliament monitor project funds, detect financial anomalies, and view risk-based dashboards for MPLADS works.
MoSPI · Data Informatics & Innovation Division (DIID) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Data Ingestion Pipeline
Collects and processes records related to sanctions, expenditures, cost estimates, and work progress.
Anomaly Detection Engine
Applies machine learning to identify unusual spending patterns, cost overruns, and duplicate works.
Automated Compliance Monitor
Tracks project timelines and flags deviations from established scheme norms.
Risk Alert System
Generates automated warnings for high-risk cases that require intervention.
Role-Based Dashboards
Provides decision-support insights and visual reports for MPs, state authorities, and the ministry.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check whether your system can successfully ingest financial and project data, accurately flag unusual patterns like cost overruns or duplicate works, and display clear dashboards for different administrative roles.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
The exact schema and format of the MPLADS dataset provided by the organisers?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific machine learning models or algorithms required?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Threshold definitions for what constitutes a high-risk alert?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
Each one is quoted from a gap in the brief, not a guess about your team.
No measurable target
The description asks for anomaly detection and risk alerts without specifying any quantitative accuracy or performance target.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for data ingestion pipeline. How would you build that?
Decoded from SIH26102 itself — Collects and processes records related to sanctions, expenditures, cost estimates, and work progress. The brief asks for it by name.
The brief asks for anomaly detection engine. How would you build that?
Decoded from SIH26102 itself — Applies machine learning to identify unusual spending patterns, cost overruns, and duplicate works. The brief asks for it by name.
The brief asks for automated compliance monitor. How would you build that?
Decoded from SIH26102 itself — Tracks project timelines and flags deviations from established scheme norms. The brief asks for it by name.
The brief asks for risk alert system. How would you build that?
Decoded from SIH26102 itself — Generates automated warnings for high-risk cases that require intervention. The brief asks for it by name.
The brief asks for role-based dashboards. How would you build that?
Decoded from SIH26102 itself — Provides decision-support insights and visual reports for MPs, state authorities, and the ministry. The brief asks for it by name.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will check whether your system can successfully ingest financial and project data, accurately flag unusual patterns like cost overruns or duplicate works, and display clear dashboards for different administrative roles.
This is the evaluator read for your problem statement, decoded from the brief's own wording.