A web application that procurement officials use to input product descriptions and receive recommended Indian Standards, latest versions, and certification requirements.
Ministry of Consumer Affairs, Food & Public Distribution · Department of Consumer Affairs (DoCA) · 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.
Document Intake Parser
Accepts product descriptions, technical specifications, or tender documents as text or file input.
Semantic Matcher
Analyzes the input using semantic understanding to find relevant Indian Standards instead of basic keyword matching.
Allied Standards Finder
Identifies normative references, test methods, terminology, safety, installation, and related product standards.
Version and Amendment Checker
Highlights the latest published version and active amendments of the recommended standards.
Certification Suggester
Suggests mandatory certification requirements such as BIS Product Certification, CRS, and Hallmarking.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will check whether your recommendation engine uses semantic understanding rather than simple keyword matching. They will test if it successfully identifies allied standards, latest versions, amendments, and mandatory certifications from raw text inputs.
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 database or dataset of Indian Standards to train or query against?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The specific supported languages for multilingual input?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The exact integration method or API format for procurement portals?
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.
Needs data you may not get
The system requires access to the complete library of published Indian Standards, amendments, and normative references, which are not provided.
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.
Multilingual Search Interface
Supports multilingual input and natural language queries for procurement officials.
The brief asks for document intake parser. How would you build that?
Decoded from SIH26108 itself — Accepts product descriptions, technical specifications, or tender documents as text or file input. The brief asks for it by name.
The brief asks for semantic matcher. How would you build that?
Decoded from SIH26108 itself — Analyzes the input using semantic understanding to find relevant Indian Standards instead of basic keyword matching. The brief asks for it by name.
The brief asks for allied standards finder. How would you build that?
Decoded from SIH26108 itself — Identifies normative references, test methods, terminology, safety, installation, and related product standards. The brief asks for it by name.
The brief asks for version and amendment checker. How would you build that?
Decoded from SIH26108 itself — Highlights the latest published version and active amendments of the recommended standards. The brief asks for it by name.
The brief asks for certification suggester. How would you build that?
Decoded from SIH26108 itself — Suggests mandatory certification requirements such as BIS Product Certification, CRS, and Hallmarking. The brief asks for it by name.
The brief asks for multilingual search interface. How would you build that?
Decoded from SIH26108 itself — Supports multilingual input and natural language queries for procurement officials. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
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 evaluators will check whether your recommendation engine uses semantic understanding rather than simple keyword matching.
This is the evaluator read for your problem statement, decoded from the brief's own wording.