Dsizing
Rebrand underway — the name will change
Sizes a counter-drone system before anyone buys one: sensor placement, coverage, gaps, and a defensible budget range.
The most expensive decision in a counter-UAS programme is made before the tender is written — how many sensors, of what kind, standing where. It is usually made from a vendor's coverage diagram, which assumes flat ground, no clutter and a cooperative target.
Dsizing models the actual site. It takes terrain, structures, the airspace being protected and the threat profile being planned against, then places sensors, shows what is covered and what is not, and produces a budget range with the assumptions written next to it. The output is a document you can hand to a procurement team, and requirements anyone can tender against — including people who are not us.
What it does
Placement against real terrain
Coverage is computed over the site’s own elevation and structures, so the shadow behind a hangar shows up as a gap rather than as an assumption.
Gaps stated, not smoothed
The output names what is not covered and at what altitude. A sizing tool that reports full coverage on every site is a sales tool.
Budget ranges with their assumptions attached
Cost estimates carry the quantities, the tier of equipment assumed, and the integration and civil work that vendor pricing normally omits.
Vendor-agnostic output
It produces capability requirements and positions, not a parts list. The result is tenderable by any supplier.
Capability domains
Products
Start with the problem, not the catalogue.
A scoping session establishes what you are actually trying to achieve, what is already in place, and whether we are the right people for it. If we are not, we will say so.