Squad Leader's Mini-UAV and PDA?

[milnews.ca]

Spotted this at Canada's public tendering site MERX (http://is.gd/4xIAg):
The Department of National Defence, Defence Research and Development Canada (DRDC), Toronto, Ontario has a requirement to develop and evaluate suitable operator interface technologies that would provide interface requirements to the Canadian Forces for controlling uninhabited vehicles.

It is anticipated that the contractor will develop a system and user manual for the complex synthetic environment in the research test-bed and for prototype interfaces on two handheld devices. The contractor will develop recommendations on the optimal platform, system structure, function allocations, and design to provide users’ needs for both types of operator interfaces.

The period of work is from date of contract award, to March 31, 2011.

More details from the Statement of Work (http://milnewsca.wordpress.com/2009/10/24/files/2009/10/merx-sow-uv-interface-23oct09.pdf) (PDF): Canada's Department of National Defence is looking into a future where section commanders may carry a Sony PlayStation Portable (PSP) or Nokia Internet Tablet to get information from their own tiny unmanned aerial vehicle.

I'm kind of split here: an extra set of eyes can always be useful, but how much more equipment does a squad/section need to take care of? Also, maybe I'm paranoid, but how tempting would it be for over-micromanaging commanders up the line to have one more set of eyes to spy on this way?

A bit more here (http://milnewsca.wordpress.com/2009/10/24/merx-uav-swarm-muav/).

[Schmedlap]

This seems like a good example of "just because you can, it doesn't mean you should."

If the squad leader needs to control his own eyes in the sky, then someone above him isn't doing their job. Why do we need so many layers of command and control and staff positions out the wazoo if, when troops hit the ground, they're flying their own UAV's? I wouldn't have wanted this even as a platoon leader.

We actually had UAVs at the company level (Ravens, if I recall correctly) and they had no use in terms of reconnaissance or surveillance. The range was inadequate, the control box and screen were not reasonable to bring along on a patrol, the picture was too shaky to see anything, and you needed a decent strip of flat ground for takeoffs and you needed someplace soft nearby to land it. We ended up just using them to buzz suspected mortar and sniper positions to see if we could get some guy to shoot at it and give away his position - which worked about one time out of a hundred attempts. It was eventually retired, boxed up, and used as a card table by my armorer. There were also other issues, but I don't know if I would be breaching OPSEC so I'll leave it at that.

[Schmedlap]

Just read over this again and I may have misunderstood the intent. If this is an idea to put a video feed into a small handheld device that a SL carries - and all of the backend work is done by the CO CP or Bn Staff, then that doesn't seem problematic. However, my question is: for what? What is the SL really going to get out of this? If there is a worthwhile use - great.

In regard to higher headquarters "micromanaging" - I never worked well with micromanagers, but a lot of what people complain about really is just enforcing standards. I've heard tales of CSMs using UAVs to check if their subordinates were wearing the proper gear on patrol. While that seems an absurd misuse of an expensive and limited asset, it's not micromanagement. It is just poor judgment. Micromanagement is getting too far into the weeds in regard to "how" to execute a mission, rather than focusing on the five W's. Enforcing standards is not micromanagement.

If you're worried about a UAV watching you because of what your superior will see, then either you are doing something wrong or you have some issues that need to be worked out with your superiors. I always relished the thought of a UAV watching me because I was sick of people living in a palace questioning what we were doing. I wanted them watch so that they would see what was actually happening. Put another way, I wanted them to get a clue. The UAV helped... a little bit.

[Cavguy]

Just read over this again and I may have misunderstood the intent. If this is an idea to put a video feed into a small handheld device that a SL carries - and all of the backend work is done by the CO CP or Bn Staff, then that doesn't seem problematic. However, my question is: for what? What is the SL really going to get out of this? If there is a worthwhile use - great.

In regard to higher headquarters "micromanaging" - I never worked well with micromanagers, but a lot of what people complain about really is just enforcing standards. I've heard tales of CSMs using UAVs to check if their subordinates were wearing the proper gear on patrol. While that seems an absurd misuse of an expensive and limited asset, it's not micromanagement. It is just poor judgment. Micromanagement is getting too far into the weeds in regard to "how" to execute a mission, rather than focusing on the five W's. Enforcing standards is not micromanagement.

If you're worried about a UAV watching you because of what your superior will see, then either you are doing something wrong or you have some issues that need to be worked out with your superiors. I always relished the thought of a UAV watching me because I was sick of people living in a palace questioning what we were doing. I wanted them watch so that they would see what was actually happening. Put another way, I wanted them to get a clue. The UAV helped... a little bit.

Whether it is a help or hindrance depends largely on the personalities in your chain of command. All leader and SOP dependent on whether it is a good or bad thing, IMO. The UAV is a tool that brings great benefits when properly employed, like all tools.

I haven't seen any UAV micromanagement in my experience. Others may vary. I will say the majority of CO's I have seen sometimes overly defer to the individual on the ground, regardless of what they see.

As far as micro UAV's, it's all good until a $50k micro UAV goes down and you have to do the report of survey/loss/recovery mission for it. :eek: Same observations re: screen and ability to use while on the run in alleys. I would support a handheld rover-like capability that would allow the guy on the ground to tune into all the various overhead feeds (Fixed Wing, UAV, JLENS, etc.) when needed. Controlling a bird while in contact is a bridge too far, IMO.

Niel

[MikeF]

is what we need. Very simple with these capabilities.

1. Rover capable so SL can see the battlefield
2. Census capable to collect pictures, DNA, fingerprints, and anthro stuff
3. Text/IM capable
4. BLUFORCE capable- to see friendlies

We can do all of this with off-the shelf technology for pennies on the dollar of creating a new system.

v/r

Mike

[Jason Port]

I always struggle with the idea of another piece of technology, and have to look at it in the context of the cost-benefit - The small UAV at my disposal would be great for looking around corners and I would think reasonably close to mid range. However, as a dismounted trooper -
- I can only cover so much ground before my UAV gathered intel rapidly becomes stale before I can cover the ground.
- I need it when I need it, so the idea of a company controlled UAV makes me just another on the list of people who need it.
- Giving me a handheld for displaying the info may turn this into the compass of 10 years ago - The navigator who uses it periodically and relies on his senses and instincts will do better than the person who stares at it while walking in circles.


As for the Uber iPod, as a defense contractor who builds systems, the iPod app is a great concept, until we actually load it with operational data (locations, report data). At this point the data should become classified, and policy makes this use impossible. (I don't entirely agree with the policy, but how do we solve the issue of the persistent terrorist with a comp sci degree from MIT hacking the application and gathering the blue data - This simply creates a nice juicy target for the next round of indirect fire. . . .

[reed11b]

So many less expensive, less carried-weight ways of doing the same thing. More importantly, is it really a need? 203 launched camera on a parachute, mortar launched disposable LTA UAV etc. If the PDA like device is allready carried, great, if not, do you NEED it? I'm a huge fan of decentrilized assets, but at some point, it becomes a little silly. What's in the middle of the compound, over the high wall may be a valid question for a SL, but do they need a UAV to find out? I do LRS, and I would not want a mini-UAV. meh.
Reed

[IntelTrooper]

I can think of a few situations where I would have loved to have this. Most of them were situations where we had set up a VPB and got reports that x number of insurgents were on the way from a couple hills over to attack us. It would have been nice to send something up that we were in control of to verify/refute the report right away. In our AO in Afghanistan, requesting and getting UAV support within a reasonable amount of time was extremely unlikely, even when we were in contact.

Schmedlap and Cavguy have pointed out some huge drawbacks, though, and unless this system could overcome those, I think it would be a huge, expensive disappointment.

[Schmedlap]

This just popped up as an ad. Why didn't we think of this?

http://googleads.g.doubleclick.net/pagead/imgad?id=CPifi6PoxNTIGhCsAhjvATII7zb-rQj3LLI