AR-Based Vocational Training Simulator for Industrial Safety in Jharkhand's Mining & Manufacturing Sector

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   The description cuts off mid-sentence at the third of five promised safety domains, so two required training domains are missing from the statement entirely and you are guessing at part of the scope

2. It gets worse

   AR content authoring is far slower than teams expect — two genuinely interactive modules with correct sequencing and failure handling is days of work that produces no code and no algorithm

3. Still reading?

   Santali TTS and digital content resources barely exist, so audio narration in that language is hand-recorded work you must plan for rather than an API call

4. And the finisher

   Certification without comprehension is exactly the problem the statement describes, so an assessment engine that just asks four multiple-choice questions has recreated the failure it exists to fix

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  4/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  The statement deliberately removes the expensive dependency by specifying mid-range Android with no headset, and ARCore with Unity AR Foundation handles plane detection and world anchoring well enough on that hardware — everything else is app engineering with the only genuine constraint being how much AR content you can author in the time.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  The expected solution prescribes the deliverable precisely down to two modules, an assessment engine, QR certificates, two named languages, offline operation and an admin dashboard, so your latitude sits in the instructional design of the modules rather than the product definition.

• Clarity

  4/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  The deliverable is stated unusually concretely, right down to the Android version, the absence of a headset and the submission artifacts, but the description is visibly truncated mid-sentence at the third safety domain, so two of the five domains it promises to enumerate are simply missing from the text.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  A genuine hidden gem — the statement itself removes the headset cost barrier, the demo puts the judge inside the product, the DGMS fatality figures give it an unarguable impact story, Santali support is a differentiator essentially nobody else will attempt, and it is filed under Blockchain and Cybersecurity where no one will look for it.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  AR content authoring is the real cost here — two complete interactive modules with correct sequencing and failure states, plus an assessment engine, certificate issuance and verification, two-language localisation, offline packaging and an admin dashboard, and none of the 3D and interaction content can be generated quickly.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  The judge holds the phone and walks the training in the room they are actually standing in, which is participatory rather than observed, and the certificate they earn at the end is a physical takeaway from the demo.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 290–500 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The statement explicitly rules out headsets and targets mid-range Android, which removes the cost barrier that normally makes AR training statements unbuildable and means your demo runs on a phone the judge already owns
• The impact case is quantified by the sponsor with DGMS fatality figures and the observation that a large share involved workers with under thirty days of orientation, so your motivation section is evidence-backed rather than asserted
• Santali localisation in Ol Chiki is a real differentiator that almost no competing team will attempt, and it directly serves the tribal workforce the statement is about