Feral Jundi

Saturday, February 21, 2009

Podcasts: Jake From COR Speaks with Andy Bearpark, Director of BAPSC

Filed under: Podcasts — Tags: , , , — Matt @ 6:06 PM

 

     Jake speaks with Andy Bearpark, Director General of the British Association of Private Security Companieson Combat Operator Radio. This was an excellent show. Andy was a wealth of information, and that was cool to hear some of the inside scoop on the Montreux Document. That would have been a fun think tank to be a part of, and I am sure the discussions were very interesting.  Here is a link for the document, so readers can check it out.  

    I was also curious what Andy thought about the New America Foundation’s paper called Changing the Culture of Government Contracting. They referenced the Montreux Document in the paper, and I was wondering if there was any collaboration? It certainly influenced the paper, and that is cool.   And to further expand on this excellent document, does Andy expect to see something of an index to pop up that actually rates companies on their performance or adherence to the industry best practices laid down by the Montreux Document? The reason I ask, is that I think it would be healthy for the industry to point out those companies that are doing well, and those that are lacking.

    As for a model for such a thing, I point to the Mo Ibrahim Foundation index on African Governance. Check it out, and I think something like this would be quite useful for this industry.  –Matt

—————————————————————— 

Kaizen: People Will Support What They Help To Create

Filed under: Building Snowmobiles,Industry Talk,Kaizen — Tags: , , , — Matt @ 4:59 PM

    Hey everyone, this is a treat. I wanted to expand on a interesting conversation in the comments section, that I think deserves it’s own home.  This is from the article called The Importance of Shared Reality. –Matt

——————————————————————-  

 Matt

     Been thinking about your post while hiking the Laotian trail–more about that later.  Since we are using the auto industry as a source of metaphor for organizational best practices, I thought we might hyper-link to another–the Saturn Car Company concept.  Remember the original GM logic for creating Saturn–they realized that they had gotten too big, and too bueracratic to compete with the smaller more nimble company’s–like Toyota.  So GM selected 99 people (“the Group of 99”) and turned them loose to identify key founding principles for a new organization (Saturn) and to search the world for the best ideas in all key areas. The group consisted of a functional cross-section of people, including plant managers, superintendents, union committee members, production workers, and skilled tradesmen, as well as 41 UAW locals(which is fascinating because one of their findings was to scrap the Union model) and GM staff from 55 GM plants. 

     The group split into seven coss-functional teams to explore stamping; metal fabrication and body work; paint and corrosion; trim and hardware; heating, ventilation, and air conditioning; and powertrain and chassis. In all, the Group of 99 visited 49 GM plants and 60 other companies around the world (shared reality). They made 170 contacts, traveled two million miles, and put in 50,000 hours of interviews and visits (listening to the guys on the ground). 

     The group’s findings were presented in April 1984. The keys to success identified included ownership by all employees, the assumption of responsibility by all, equality and trust among employees, the elimination of barriers to doing a good job including the union, giving staff the authority to do their jobs, and the existence of common goals. Specific recommendations included the formation of consensus-driven partnerships within work teams as well as between the union and company management. 

     Although initially a mega-success, Higher Headquarters eventually reigned Saturn back in and squashed their entrepenuerial decision-making and management methods, the lesson still stands as a precient model for how a large organization can reinvent itself to stary nimble, and stay competitive.  

     I believe that the Saturn Car Company model is what USSOCOM needs to follow in order to stay nimble and meet the challenges of modern day–I hate to use the word but I have to–assymetrical warfare.

 What think you? –Pete 

——————————————————————- 

Pete,

 

    Laos would be a cool country to check out, and I certainly would like to hear those stories. As for your question, I hope I can do it some justice.  It is something that all companies in my industry can learn from, and any ideas about how to better organize and manage a company should be listened to and studied.  The concept of Group 99 is intriguing, and it has certainly kicked in the thought machine within my head. I also wanted to make this answer for you, more reader friendly, and include a historical base as well.  So you will have to pardon the beginning here, because this is me just priming the pump for the reader.   

     The United States Special Operations Command (USSOCOM) or what I will call SOCOM was originally created out of the ashes of Operation Eagle Claw(the failed Iran hostage rescue mission), and I think it is important to look at this first.  The investigation of this incident, chaired by Admiral James L. Holloway III, cited lack of command and control and inter-service coordination as significant factors in the failure of that mission. So this is one side of the story. 

     The other side of the story, is the reality of what the Special Operations Forces (SOF) were up against. Whereas my belief is that the SOF community was getting the short end of the stick well before Operation Eagle Claw, and certainly were aware of these command and control issues. The guy on the ground was not being listened to, which is too bad.  It was classic conventional versus unconventional mindsets, and of course the bigger of the two will win.  So no one of importance or influence was really sold on the concept, and looked upon SOF with skepticism, all while gobbling up budget money for their projects.  “All of my forces are special” was the mindset, “and money needs to go to my tanks, jets, and large scale infantry forces”.  

     And Carter, when confronted with a situation that required a clean and sharp scalpel, to cut those hostages loose from Iranian control, looked to the military to solve his problem. Did they have a developed Special Operations capability, or were they too focused on tanks and planes?  No wonder things failed, but I put that responsibility on the top leaders who were not forward thinking enough to even acknowledge the potential for a situation like what happened in Iran. So this is where SOCOM came from, and what it’s purpose in life is–to prevent another Operation Eagle Claw and effectively manage today’s Special Operations community.

    Then over the years, they have done much to work on the command and control issues and inter-service coordination, and have conducted numerous missions all the way up to the present wars.  But really, the current wars are the true test of the effectiveness of SOCOM, and I think this is why a conversation like this even takes place.  The true test of an organization’s strengths is not when all is well, but when they are tested and pushed to it’s limits.  Much like how does a company like Toyota weather the storm during a bad economy?  

(more…)

Thursday, February 19, 2009

Podcasts: Boots on the Ground, With Guest Jake Allen from Combat Operator

Filed under: Podcasts — Tags: , , , , — Matt @ 12:58 AM

  

Wednesday, February 18, 2009

Technology: War Robots, Ethics, and the Book ‘Wired for War’ by Peter Singer

Filed under: Books,Technology — Tags: , , , — Matt @ 11:24 AM

   What can I say?  We are now having this discussion, and it blows me away.  And as I speak, drones are killing folks in IraqAfghanistan, and Pakistan, and have been doing so for awhile.  The only safety measure is that they are so far not really autonomous.  But what happens when we cut the cord and let some robot or drone operate on it’s own?  What happens if that robot has a glitch and accidently kills the good guys?  Do you charge a robot with manslaughter, are they covered by the Geneva Convention, do we give them full burial honors at Arlington Cemetery when they pass?

  On a side note, I did get a chance to pick up Peter Singer’s book, and I read through it a little.  I will not give a full review, but there were some parts that were interesting.  Especially the section that discussed ground robots, and the first ever drawing of blood in this war by a ground robot.  Basically some soldiers put a Claymore mine on a MARCbot, and drove it into a pack of insurgents and blew them up. The total cost for that kill, about $8,000, plus whatever it costs the military for a claymore.  I think I could make or buy a cheaper Claymore carriage at a hobby store, but still, that field expedient weapon is a whole lot cheaper than launching a Javelin at the enemy. (and if it hurt the enemy and/or saved lives, bravo!)

   The insurgents came up with a similar type deal using a skateboard according to the book.  I guess they made an explosive laden skateboard with motors on the wheels.  The insurgents powered it up, and set it rolling slowly towards a patrol, thinking the patrol would not pay attention to a slow rolling toy.  Luckily the patrol locked on to the thing, because it was moving against the wind.  The total cost of this weapon was way cheaper than the MARCbot, but could have easily succeeded if used properly.

   So with these humble beginnings of ground combat robots, will we one day see a robot that thinks on it’s own?  I do know that the desire for these things is driving the market big time.  With a highly competitive robotics market and a war that is not going away anytime soon, we will begin to see these kinds of autonomous war robots that science fiction, and now academics are talking about.  Good or bad, the future is now. –Matt

——————————————————————-

Military robots must be taught a warrior code

16 Feb 2009

Autonomous military robots must be taught a strict warrior code or they could turn on their human masters, a US report warns.

I, Robot: Military robots must be taught a warrior code

The warnings of a potential revolt, as envisaged by the science writer Isaac Asimov in his chilling I, Robot series of stories, appear in the first major report on robot ethics Photo: 20TH CENTURY FOX

The warnings of a potential revolt, as envisaged by the science writer Isaac Asimov in his chilling I, Robot series of stories, appear in the first major report on robot ethics.

The report, by researchers from the Ethics and Emerging Technologies Group at California Polytechnic State University, was funded by the US navy office of naval research.

Mindful of the US deployment in two major theatres of war, the military is keen to pursue alternatives to manpower, including Terminator-style armed robots.

(more…)

Tuesday, February 17, 2009

Industry Talk: Wired’s Danger Room PR Tips for Blackwater Revisited

   I wanted to resurrect this post from Wired’s Danger Room, to show some interesting ideas for public relations.  I have no clue if Sharon or the gang at Wired has been privately talking with BW since this article, but it is kind of interesting how BW has adopted some of these ideas.  Especially the whole ‘Xe’ thing. –Matt

—————————————————————— 

 Top Ten PR Moves for Blackwater

By Sharon Weinberger 

September 20, 2007   

As the saying goes, free advice and 50 cents will get you a cup of coffee (though it’s probably more like three bucks these days). So, here are my top 10 ideas for “rebranding Blackwater” as a warm, fuzzier merc outfit Private Military Contractor. (By the way, this is PR advice, so I’m not going to touch any policy/operational issues; this is just good old-fashioned spin.)

Personally, I prefer the Blackwater of current incarnation — the one that produces tons and tons of too-awful-to-be-true PR missteps, which in turn produces lots of good news stories and blog posts. But I’m just doing this is as sort of an intellectual exercise in Machiavellian thinking, like musing about how you would commit the perfect crime.

So, in no particular order…..

1) New name, preferably with indecipherable acronym.

It took decades before anyone run an “expose” about SAIC. And most people have already forgotten about it. When was the last time you saw a major article about CSC, or Computer Sciences Corporation (hmm, never). DynCorp and prostitutes? A distant memory.

Let’s face it: Does your typical American know (or care) what ARINC stands for?

Heck no.

The point here is if you want to be a shadowy, low-profile sort of company, start acting like one.

It’s a fine balance here, so no, no, nothing like “Executive Outcomes.” That was too Bond-like. Nothin’ but trouble. Personally, I’m fond of something snooze-worthy like SMS, for “Strategic Management Solutions.” Words like “systems,” “integration,” and “analytics” all work well.

Or heck, just use the acronym.

2) New logo.

Yes, that bear paw is totally awesome cool, if you want teenage boys to love ‘ya as much as they love Teenage Mutant Ninja Turtles. The Press just loooooves that logo (photographers, too!), it just screams “page one.” Choose something like the DARPA logo, that innocuous globe-shaped thingamajig also favored by companies of unknown acronyms. Remember how many problems DARPA had when they went with the masonic temple/eye thing for the Information Awareness Office?

Shadow companies should use forgettable logos. Anybody even know what Anteon’s logo looks like? Does your average American even know what Anteon does?! Of course not.

3) Don’t sell gear with your logo.

Just don’t do it. Trust me on this one.

4) Change colors (this goes with the logo point, perhaps).

Black is just soooo Angelina Jolie from her knife-cutting days. And nothin’ says “spicy mercenary story” like a man wearing wraparound shades and dressed in black. I think a darkish blue would work; still manly, but with a softer edge.

(more…)

« Newer PostsOlder Posts »

Powered by WordPress