Showing posts with label Persistence. Show all posts
Showing posts with label Persistence. Show all posts

Saturday, March 13, 2010

Defeating IEDs/EFPs: Possibilities Part One

I've got a little lull in the workload at the moment (only working partial weekends) so I, though it would be a good time to start following up on a previous post concerning the military concept Persistence, how Persistence relates to IEDs/EFPs, and more specifically what can be done to attenuate the placement and detonation of these 'weapons that wait'.

In this post, I present the general processes an enemy could use to employ what has to be their current weapon of choice. The processes shown are not designed to be all inclusive: They are general enough to capture all the relevant concepts, but are also specific enough to allow me to efficiently propose how and why the enemy's behaviors can be shaped and IED/EFP deployment and effectiveness attenuated (no threat can be completely eliminated).

First, the obvious:

The employment of Weapons That Wait (from this point forward they will be referred to as WTW) I have broken down into two sub-processes: 'Acquisition' and 'Employment'. There were a couple of other ways I could have broken things down, but these will serve my greater purpose. If the enemy does not have a weapon or weapons in hand, they have to first get their hands on it/them.

Now for the less obvious. I have chosen (there are other ways) to break the acquisition process down as follows:

The enemy, once they have a weapon in hand, must complete the Employment process. That process I have chosen to break down as in the flowchart below. (Note: sub-processes of both the Acquisition and Deployment processes can be conducted concurrently but are, obviously, completed sequentially.)

We will return to these processes several times in future posts, but I am planning to next bound the concept of 'Persistence' sufficiently such that when we do return to these processes, we will only be dealing with Persistence as it relates to stopping these WTW.

Wednesday, February 03, 2010

Yeah, "What do I know?"

Updated and Bumped:

Heh.
I've been having a rather unproductive, yet sadly humorous, 'intercourse' over at the DEWLine with a 'true believer' on a mission. Apparently, I know nothing about 'persistence', UAVs, persistent UAVs, ISR, or Heaven knows what else.

NEW:
I am going to of course followup on this topic, but am working something more important for the next couple of days.

As a beginning, I think it would be helpful to first do a top-level characterization of the roadside bomb problem before we tackle any proposed 'solutions'. At first blush the challenge seems similar to a post-launch TBM neutralization scenario, but with an 'Assault Wrecker' model dynamic. I built Assault Wrecker (AW) about a decade ago for a grad school project and found AW helpful in performing several analyses after that. It is based upon the scenarios and model processes described in "To Find and Not to Yield". The model name is a play on the old 'Assault Breaker' concept: i.e. Assault Breaker on steroids. Read up a bit and try to guess how I'll apply old knowledge to the problem at hand.

But remember, according to 'some' I really don't know what I'm talking about.