Vehicle-mounted reconnaissance system: when deployment time is the design constraint
A reconnaissance system for a tactical vehicle combining the SEG12 sensor, a 4 m pneumatic mast and a pan-tilt positioner, designed to a sub-90-second deployment requirement.

SEG12 · 4 m pneumatic mast · pan-tilt positioner · 4×4 tactical platform
The requirement
Under 90 seconds from the vehicle stopping to a usable image.
That is a performance requirement in the shape of a survivability requirement. On a reconnaissance vehicle the dangerous quantity is the time spent stationary, and every second of set-up is a second of exposure. The customer did not ask for a fast mast. The customer asked for a short stop.
The specification also has a silent second half. A 90-second deployment paired with a five-minute recovery is a 90-second deployment on paper only, because the vehicle is still exposed while it packs up.
The configuration
A SEG12 sensor and a pan-tilt positioner on a 4 m pneumatic mast, on a 4×4 tactical platform.
Each element was chosen against the clock rather than against a datasheet.
The pneumatic mast raises a short column in seconds and adds very little mass at the top of a light vehicle. At 4 m it is a sensible structure rather than a compromise.
The pan-tilt positioner lets the crew search without repositioning the vehicle, which removes the slowest possible way of changing where the sensor is looking.
SEG12 is the choice that most repays explanation, because it was made on a time constant rather than on an image. SEG12 belongs to the uncooled class, and an uncooled thermal imager produces usable imagery almost immediately after power is applied. A cooled sensor of the same generation would need its cool-down first. In a budget of 90 seconds, a cool-down is not one line item among several — it is most of the budget. The sensor was selected for how fast it starts.
What the engineering had to solve
The mast was never the long pole. Break the 90 seconds down and very little of it belongs to raising the mast. It goes to stopping and securing the vehicle, powering up and initialising, and then to the item nobody budgets for.
The image is up before it is usable. A mast on a vehicle is a cantilever standing on springs, and the springs are softer than the mast. The column reaches full height in seconds while the vehicle is still rocking on its suspension, and the picture at that moment is at the correct height and not worth looking at. Shortening the deployment therefore meant shortening what happens after the mast is up: taking the load onto a mechanical lock rather than leaving it on pressure, so the column stops moving instead of slowly finding its level, and settling the platform before the operator needs the image rather than while they are trying to use it.
Nothing fits in 90 seconds if it happens in order. The only way to make the budget was to stop the sequence being a sequence. Power-up and initialisation begin while the vehicle is still slowing. The mast rises while the sensor is starting. Every task moved off the critical path was worth more than making any single task faster, and this is where most of the time was actually recovered.
The road sized the structure, not the wind. At 4 m the wind case is modest. What the folded mast and its mounting see on a cross-country drive is not. The structure and the transit lock were driven by transport loads, and the extended 4 m condition was never the governing case — which is the opposite of what a mast specification usually implies.
Recovery had to cost nothing. No lock at height may require a hand, and nothing may need to be walked around and checked, because both of those turn a fast system into a slow one at the moment it matters most.
The result
Vehicle stop to usable image inside the requirement, with recovery in the same order of magnitude, and no crew member touching the mast in either direction. The design lesson the programme produced is worth more than the figure: on a system specified by deployment time, the fast component is rarely where the time is, and the sensor may be chosen for how quickly it wakes up rather than for what it sees.
Technical discussion and quotation
Tell us the platform and the constraint. Our engineering team answers with a configuration that fits it, usually within two working days.

