Development of a Low-Cost Precision Guidance and Smart Electronic Fuze System for a 155 mm Artillery Shell
Ministry of Defence (MoD) · Miscellaneous · Hardware
The hardware is controlled, the test conditions are inaccessible and the accuracy claim cannot be evidenced by anyone competing, so this is not a realistic pick for a student team however strong their engineering background.
What it actually is
This statement asks teams to convert a conventional 155 mm artillery shell into a precision-guided munition by designing a guidance kit, flight control system and multi-mode fuze to a stated accuracy target, with deliverables including a system architecture, CAD models, control algorithms and a proof-of-concept prototype.
What to build
Not provided. This is a request for a munitions guidance and fuze design package, and writing out a build specification, sensor selection, actuation approach or control design for it would be producing weapons design content regardless of the hackathon framing. The strategic assessment below is offered on the basis of the published statement alone, so this entry can be evaluated alongside the rest of the dataset without supplying that material.
Smallest thing that wins the room
Not provided, for the same reason.
How crowded this one gets
A guess, projected from the 2025 statements — the last year where both the submission counts and the winners were published.
Quieter than 88% of the 226 · #29 of 226 by expected field
Few teams are likely to go here. The best odds on the board come from statements like this.
Why: defence, intelligence and space bodies drew small fields; hardware halves the field a software statement gets.
This is a guess, not a fact
Nobody has published 2026’s numbers yet. This is an analysed estimate from last year’s pattern, so please do not take it as the truth — check the live counter on the SIH portal before you decide anything. The range covers the middle half of likely outcomes, so one statement in two lands outside it. Entry closes at 500 ideas per statement, so no range goes past that — a statement that reaches the cap fills and shuts rather than drawing an unlimited crowd. The model reads only three things a team can see before choosing — software or hardware, the theme, and what kind of body posted it — and those explain about a quarter of the variation in last year’s field sizes (R² 0.25 on held-out statements). Trust the band more than the number, and the ordering more than either. It cannot see how good your idea is, which is the part that actually decides it.
The scores
The number is the shorthand. The line under it is the reason.
Acceptance potential
1/5For a student team this is unanswerable in practice: the hardware is inaccessible, the test conditions cannot be reproduced, and the deliverable that would matter — evidence of the stated accuracy — has no path to existing, so submissions can only be paper architectures.
Feasibility
1/5There is no route for a student team here regardless of technical ability — the base hardware is controlled ordnance that cannot be obtained, there is no accessible facility to test high-acceleration launch survival, and no artillery range is available to demonstrate or measure the accuracy target the statement sets.
Innovation scope
2/5The subsystems, the fuze modes, the accuracy target, the constraints and the deliverable list are all enumerated in the statement, so the system is largely specified.
Clarity
5/5Precisely written — it states the accuracy target, the compatibility constraint with existing shell hardware, the environmental survival conditions, every required deliverable and the engineering disciplines expected, leaving no ambiguity about what is wanted.
Effort
MassiveA guided munition programme spanning mechanical design, actuation, embedded electronics, control, power and environmental qualification is defence development work measured in years and funded procurement rather than a hackathon deliverable.
Demo-ability
HardThe stated performance can only be evidenced by live firing on an instrumented range, which no participating team can access, so nothing demonstrable in a hackathon setting bears on the claim the statement asks you to make.
In its favour
- Green flag: The statement is unusually precise about its requirements and constraints, so there is no ambiguity about scope for anyone assessing whether it is a realistic pick
- Green flag: The sponsor is a T1 defence manufacturer with genuine domain expertise, so the panel would be well qualified to evaluate serious work in this area
Against it
- Red flag: The base hardware is controlled ordnance and cannot be obtained, purchased or worked on by a student team under any framing, so the physical prototype the statement prefers has no route to existing
- Red flag: Verifying the stated accuracy requires live firing on an instrumented artillery range, which is not accessible to participants, so the central performance claim cannot be evidenced at any stage
- Red flag: High-acceleration launch survival is a stated constraint and testing it needs specialist facilities, meaning the environmental qualification that determines whether any design is viable cannot be attempted
- Red flag: Every submission will therefore be a paper architecture with no build and no test data, which is a weak position against a panel that develops this hardware professionally
What you will be writing
- defence ordnance development
- restricted-access hardware
- live-fire range qualification
- high-acceleration environmental testing
- Defence systems development
- Ordnance engineering
Prior art to read before you start
guided munition development · defence hardware qualification
Analysed by Claude Opus. Every score above is a judgment call with its reasoning attached — kindly cross-check this against the official statement on the SIH portal before your team commits to it.