Sovereign On-Premise Agentic AI Workbench using Open-Weight Multimodal LLMs for Confidential Industrial Work
Mangalore Refinery and Petrochemicals Limited (MRPL)
Good pick. Genuinely. Now sit down, because the judges are going to try anyway — and this is what they will try.
Strong pick. The best-framed software problem in this block and the network-cable demo is unbeatable, but the scope is six systems in one — pick the agent loop and real file deliverables as your depth, and be honest about what the router does. Roughly 85–190 teams are expected to go here.
The receipts
Every red flag on this statement, in full. These are the four places it bites.
Exhibit A
Serving several open-weight models concurrently needs real GPU memory, and without access to a capable machine you will demo one small model and quietly drop the routing that the description asks for
It gets worse
The scope spans routing, agents, sandboxing, multimodal ingestion, retrieval and document generation — six substantial systems, and building all six shallowly reads worse than building three properly
Still reading?
Model routing is easy to assert and hard to justify, so be ready to show that your router actually improves outcomes rather than adding a layer that looks sophisticated
And the finisher
Engineering drawings and P&IDs are dense symbolic documents that general vision models read poorly, so the multimodal claim will fail on exactly the input the description highlights
The damage report
Every score this statement earned, and what each one actually costs you.
Feasibility
3/5Buildable. Not comfortably. There is a week in here you have not planned for yet.
Open-weight models, local inference servers, agent frameworks and document generation libraries all exist and compose, but the description asks for model routing, agentic tool use, sandboxed execution, multimodal OCR and RAG together — and running several open-weight models concurrently needs GPU capacity most teams do not have.
Innovation scope
4/5There is something genuinely new here. Do not bury it under another dashboard.
The routing policy, the agent architecture and how you make an air-gapped system genuinely useful rather than merely offline are all undefined, and the description explicitly leaves the model mix and extensibility mechanism to you.
Clarity
4/5The ask is unambiguous, which quietly removes your favourite excuse.
The description is unusually concrete about what must exist — multi-model routing, extensibility, planning and iteration, named local tools, multimodal inputs, real file deliverables, and grounding in organisational documents — even though it sets no performance targets.
Acceptance potential
4/5Strong footing before you have written a line. Try not to waste it.
The problem is real, current and well-articulated, the sovereignty framing lands hard with a PSU judge, and the field will be thinned by the GPU requirement — but the scope is enormous and a team that builds a local chatbot without the agent loop or the file deliverables has answered a fraction of it.
Effort
MassiveA semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.
Model serving and routing, an agent loop with tool calling, a code sandbox, a multimodal document pipeline, a retrieval layer and Office-format generation is essentially rebuilding a commercial AI coding assistant locally.
Demo-ability
EasyEasy to demo — and so is everyone else's. Working is the floor here, not the achievement.
Pulling the network cable and then watching it produce a real Word document from a scanned drawing is a dramatic, self-evident demonstration that needs no explanation.
The demo they will have already seen
Somewhere around 85–190 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.
- Disconnecting the network during the demo is a single physical action that proves the entire sovereignty claim more convincingly than any slide could
- The description names its own benchmark — users should work with it the way they use commercial assistants — which gives you a clear and honest bar to aim at
- Producing an actual Word or Excel file rather than chat text is a modest engineering addition with outsized perceived value for an industrial user
Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.
The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.