About Defense Tech

Defense Tech exam­ines the inter­sec­tion of tech­nol­ogy and defense from every angle and pro­vides analy­sis on what’s ahead.

Tip Us Off

Tip for Defense Tech?

SEND IT!

It’s Confidential!

Archive for May, 2009

Marines vs Taliban

Friday, May 29th, 2009

Marines-fight-AQ-campsLARGE.jpg

One of my Marine bud­dies from 2–5 sent this to me. I thought I’d share it.

A large group of Taliban fight­ers is mov­ing down a ravine in the Korengal Valley, in south­ern Afghanistan, when they hear a hoarse voice call from behind a sand-​​dune in a mock­ing tone, “Yo, muj, did you know that one Marine Marine is bet­ter than ten of you smelly Talib?“ 

Insulted to the quick (though he did indeed smell), the Taliban com­man­der sent ten of his best men over the rocky hill, where­upon a gun­bat­tle broke out imme­di­ately. The gun­bat­tle was short, but vicious, punc­tu­ated by screams of agony and fear in Dari and Pushtu. Then there was silence. 

A moment later, there was a snicker, then the same voice called out, “Bad Muj! Didn’t you know one grunt is bet­ter than any hun­dred so-​​called Taliban fighters?“ 

Furious now, the Taliban com­man­der sent his next best hun­dred men up and over the incline and instantly a ter­ri­ble gun­fight ensued. The sharp chat­ter of M-​​4 fire barked out in coun­ter­point to the dull clat­ter of the Kalashnikovs, inter­spersed with the det­o­na­tions of grenades and screams of agony and fear in Pushtu and Dari. After a full five min­utes of bat­tle, silence reigned heav­ily across the valley. 

A moment later that same mock­ing voice called out, though to be fair to the muj, the grunt was obvi­ously breath­ing at least a lit­tle bit faster. The voice called out, “Bad Muj, silly muj, you have to know that one grunt is bet­ter than one thou­sand sheep-​​loving Taliban!”

(more…)

NorkNuke Raises Persian Threat

Friday, May 29th, 2009

iran-threat.jpg

The direc­tor of the Missile Defense Agency, Lt. Gen. Patrick OReilly, said dur­ing an oth­er­wise pretty dull hear­ing before the House Armed Services strate­gic forces sub­com­mit­tee that the threat to the United States has increased sub­stan­tially with the recent launch by Iran of a small satel­lite and the launch last week of a mid-​​range bal­lis­tic missile.

That caught the ears of the pro­fes­sional con­gres­sional staffers at the Thursday hear­ing, who won­dered what the impli­ca­tions might be, since they were not explored at the hearing.

Some pos­si­ble answers came from the ven­er­a­ble RAND Corporation. It came out with a report about Iran and its rela­tions with the US over the next decade. One of the key rec­om­men­da­tions of the May 19 report, Dangerous But Not Omnipotent: Exploring the Reach and Limitations of Iranian Power in the Middle East, is that the US should back off de-​​escalate in the reports lan­guage on a bilat­eral basis and com­bine that with mus­cu­lar mul­ti­lat­eral efforts tar­geted at Iranian behav­iors that are not accept­able to the inter­na­tional com­mu­nity, such as ter­ror­ism and its devel­op­ment of nuclear weapons. Key to this mul­ti­lat­eral approach would be sup­port from Russia and China, which the report con­cedes is questionable.

One of the most inter­est­ing pol­icy rec­om­men­da­tions con­cerns how the US should com­mu­ni­cate its pol­icy goals. We must issue unam­bigu­ous state­ments about US inter­ests and inten­tions in the region, par­tic­u­larly regard­ing Iraq, the authors say, The mes­sages must be sim­ple and eas­ily under­stood, and the United States must stick to them long enough for them to be taken seri­ously. Among those state­ments should be a pledge that the US will say it has no long term inter­est in occu­py­ing Iraq or estab­lish­ing a per­ma­nent mil­i­tary pres­ence in Iraq.

The 230-​​page report, was com­mis­sioned by the U.S. Air Force in order to accu­rately gauge the strate­gic chal­lenges from Iran over the next decade. If the threat from Iran really has increased sub­stan­tially, as the MDA direc­tor told the sub­com­mit­tee, quickly find­ing answers and imple­ment­ing alter­na­tives to the poli­cies that have failed to deter Iran from devel­op­ing ICBMs and pur­su­ing nuclear weapons for much of the last decade is imperative.

Colin Clark

Talk of Collaboration

Thursday, May 28th, 2009

china-net-attack.jpg

What would hap­pen if one day the com­put­ers stopped work­ing? That is what we may face when we look at the grow­ing threat posed by the sophis­ti­cated cyber attacks we are cur­rently expe­ri­enc­ing. A 2008 sur­vey of secu­rity insid­ers (man­age­ment, net­work engi­neers and admin­is­tra­tors) in mul­ti­ple infra­struc­ture seg­ments were ques­tioned about the state of infra­struc­ture cyber secu­rity in the U.S., Canada, and Europe. These pro­fes­sion­als indi­cated that mul­ti­ple seg­ments were unpre­pared for cyber attacks. The seg­ments specif­i­cally iden­ti­fied as unready were: water, util­i­ties, oil and gas, telecom­mu­ni­ca­tions, trans­porta­tion, emer­gency ser­vices, chem­i­cal and the ship­ping indus­try. For the pur­pose of this arti­cle crit­i­cal infra­struc­ture is defined as the facil­i­ties, ser­vices, instal­la­tions, capa­bil­i­ties and key resources needed for the proper func­tion­ing of soci­ety. According to Executive Order 13010 signed by President Bill Clinton on July 15th, 1996, crit­i­cal infra­struc­tures includes the following.

Telecommunications

Electrical power systems

Gas and oil stor­age and transportation

Banking and finance

Transportation

Water sup­ply systems

Emergency ser­vices (includ­ing med­ical, police, fire, and rescue)

Continuity of government

The Department of Homeland Security (DHS) inven­tory of our nations crit­i­cal infra­struc­ture includes 68,000 pub­lic water sys­tems, 300,000 oil and nat­ural gas pro­duc­tion facil­i­ties, 4,000 off-​​shore plat­forms, 278,000 miles of nat­ural gas pipelines, 361 sea­ports, 104 nuclear power plants, 80,000 dams and tens of thou­sands of other poten­tially crit­i­cal tar­gets across four­teen diverse crit­i­cal infra­struc­ture sectors.

The Department of Homeland Security (DHS) has begun imple­men­ta­tion of a num­ber of mech­a­nisms in an effort to improve infor­ma­tion shar­ing with crit­i­cal infra­struc­ture own­ers and oper­a­tors. These include:

Homeland Security Information Network (HSIN)

Executive Notification System (ENS)

Critical Infrastructure Partnership Advisory Council (CIPAC)

Homeland Infrastructure Threat and Risk Analysis Center (HITRAC)

National Infrastructure Coordinating Center (NICC)

Protected Critical Infrastructure Information (PCII)

The infor­ma­tion shar­ing per­tains to infor­ma­tion flow­ing between the intel­li­gence com­mu­nity and crit­i­cal infra­struc­ture own­ers and oper­a­tors. Even though these pro­grams are in place and they have made progress, there is more that needs to be done. The cur­rent threat envi­ron­ment requires solid, trusted rela­tion­ships to ensure to suc­cess­ful infor­ma­tion shar­ing and col­lab­o­ra­tion between the pri­vate sec­tor and the gov­ern­ment. That takes time.

Kevin Coleman

Shipbuilding Program is a Mess

Wednesday, May 27th, 2009

aegis.jpg

The Navy’s ship­build­ing pro­gram is a mess. That was the con­sen­sus of sev­eral highly qual­i­fied speak­ers at a recent Washington sem­i­nar spon­sored by the Hudson Institute. And, it was agreed, the cur­rent Navy and con­gres­sional efforts will not rec­tify the sit­u­a­tion.

The fis­cal year 2010 pro­gram recently pre­sented to Congress calls for $14.9 bil­lion in ship­build­ing funds for eight ships:

1 SSN attack sub­ma­rine
1 DDG Arleigh Burke–class destroyer (a restart of that pro­gram)
3 LCS lit­toral com­bat ships
2 T-​​AKE replen­ish­ment ships
1 HSV high-​​speed ves­sel

With a planned aver­age ship ser­vice life of 30 years, this build­ing rate would sus­tain a fleet of 240 ships. This is less than the Navy’s cur­rent 283 ships and far short of the long-​​standing Navy “require­ment” for 313 ships.

The dis­tin­guished speak­ers at the Hudson con­fer­ence on 22 May made it clear that with­out a mas­sive increase in ship­build­ing funds a larger fleet was not achiev­able. Dr. Eric Labs, senior naval ana­lyst at the Congressional Budget Office said that about $25 bil­lion per year for new ships is needed to reach the Navy’s goal.

Now is the time for “hard choices,” Labs said. We “can­not fix prob­lems with sim­ple mea­sures.”  He observed that the ship pro­cure­ment dol­lars being dis­cussed do not include a new class of bal­lis­tic mis­sile defense cruis­ers, and “it is not unrea­son­able” for those ships — now des­ig­nated CG(X) or, if nuclear pro­pelled, CG(X)N, to cost $6 to $7 bil­lion per ship.

Former Secretary of the Navy John Lehman, under whose direc­tion the U.S. fleet had reached almost 600 ships in the 1980s, out­lined a “new look” for the Navy (which will be dis­cussed in a future com­men­tary). With respect to ship­build­ing prob­lems, Lehman blamed the con­stant bureau­cratic growth of the Defense Department, includ­ing the Naval Sea Systems Command, and the lack of “line deci­sion mak­ers” — peo­ple who have the author­ity and respon­si­bil­ity to make key deci­sions. Only then can the con­tin­ual flow of changes be made in ship require­ments and con­struc­tion be halted.

Lehman called for “freez­ing” designs and mak­ing only “block” changes in new con­struc­tion pro­grams.

Congressman Joe Sestak, a retired vice admi­ral, believes that the Navy could carry out its mis­sions with a 240– to 260-​​ship fleet if “we bought cyber­space.” Calling for the devel­op­ment of meth­ods for track­ing every sur­face ship — both mil­i­tary and com­mer­cial, an expan­sion of the Automated Identification System (AIS) now used for large mer­chant ships — and for the con­tin­u­ous loca­tion of sub­marines, he said that such infor­ma­tion could reduce the U.S. Navy’s ship require­ments. 

Still, “own­ing” cyber­space would be expen­sive. And, the only way to under­take such an achieve­ment would be to remove “cyber war” oper­a­tions from the ser­vice bud­gets and con­sol­i­date the effort under a Department of Defense exec­u­tive, accord­ing to Sestak. 

A con­sen­sus of the pre­sen­ta­tions and the ques­tions and com­ments from the audi­ence included the fol­low­ing points:

The Navy’s flip-​​flops on the Zumwalt (DDG 1000) and Burke (DDG 51) pro­grams have hurt the Navy’s image and cred­i­bil­ity of its ship­build­ing pro­gram.
The Navy’s 30-​​year ship­build­ing plan, required by Congress, is unre­al­is­tic and of lit­tle value.
Poor man­age­ment of the Navy’s ship­build­ing efforts have resulted in ship delays and cost over­runs
The Navy has failed to effec­tively “sell” itself as a key fac­tor in America’s political-​​military effec­tive­ness, in part because of the above fac­tors
Ship num­bers do count and the con­tro­ver­sial lit­toral com­bat ship (LCS) is the Navy’s only hope for increas­ing fleet size.
The Navy’s lead­er­ship can fix the pro­cure­ment mess, but must take bold and inno­v­a­tive action, includ­ing demand­ing firm fixed-​​price con­tracts and the use of second-​​tier ship­yards and con­trac­tors to spark competition.

Norman Polmar

Rangers Get Their SCARs

Tuesday, May 26th, 2009

Another SCAR sight­ing folks!

This time — and a nice con­fir­ma­tion of my sourc­ing on the first equip­ping units — its a pic of some Rangers who’d dropped by a NASCAR event this past weekend.

The Joes from 1st Battalion, 75th Ranger Regiment were hon­ored at the Coca Cola 600 at Lowes Motor Speedway in Charlotte, NC, among other ser­vices over the Memorial Day weekend.

Take a close look at this photo and check out what’s strapped over their shoulders…

…and I dig the guy who col­lapsed his SCAR’s stock…
SCAR-rangers.jpg

For the full-​​sized image click HERE

(Gouge: MP)

– Christian

Defense Tech and the Digital Nation

Tuesday, May 26th, 2009

radio-mic.jpg

Good morn­ing folks. Sorry for the delayed post…playing catch up.

I wanted to let you know that I’ll be par­tic­i­pat­ing as a pan­elist on a Live Web chat with Frontline doc­u­men­taries on a new project they’ve launched called “Digital Nation.”

This doc­u­men­tary looks at how dig­i­tal tech­nol­ogy has impacted our daily lives, includ­ing how it has changed the way the mil­i­tary does busi­ness. Today I’ll weigh in on that sub­ject with Lt. Gen. Robert Elder, the com­man­der of 8th Air Force, and Dr. Albert “Skip” Rizzo, direc­tor of USC’s Institute for Creative Technologies and cre­ator of the military’s “vir­tual Iraq” PTSD treat­ment program.

I hope you’ll join us today at 11am EDT for the online chat over at Frontline’s Digital Nation project site.

– Christian

Memorial Day Message

Friday, May 22nd, 2009

In cel­e­bra­tion of Monday’s hol­i­day, I thought I’d pass along a mes­sage from the Army Chief of Staff Gen. George Casey.

Enjoy your week­end folks!

– Christian

Willy Pete in the ‘Stan

Friday, May 22nd, 2009

willy-pete.jpg

Did any­one see this? 

From US CENTCOM:

In response to claims that insur­gents in Afghanistan are not using, nor have access to, white phos­pho­rus (WP) muni­tions, ISAF RC-​​East con­ducted a sum­mary data­base query, by which a total of 44 instances of reported enemy WP inci­dents were uncov­ered and declas­si­fied on 11 MAY 09. Thirty-​​eight of those occurred in RC-​​East and are released in this doc­u­ment. Our research also revealed six WP events that occurred in other ISAF regions; this list is avail­able upon request from ISAF PAO press office at pressoffice@​hq.​isaf.​nato.​int.

Discussion: Three means of white phos­pho­rus use and access by insur­gents can be iden­ti­fied: 1) impro­vised explo­sive devices, 2) indi­rect fire attacks, and 3) ord­nance caches or UXO. It is notable that the enemy has stock­piled and used white phos­pho­rus in attacks since 2003 and as recently as the week prior to this release. It should also be noted that these instances have occurred in nearly every province in RC-​​East, which demon­strates the wide avail­abil­ity of white phos­pho­rus to insur­gents. Finally, it is impor­tant to note that insur­gent stock­piles do not nec­es­sar­ily derive from old Soviet-​​era left-​​behind stocks; the white phos­pho­rus muni­tions found in these 38 events have their ori­gins in a wide range of coun­tries. Also, the vast major­ity of white phos­pho­rus rounds found in listed caches were deter­mined to be in ser­vice­able con­di­tion.

That’s weird, don’t you think? Why would insur­gents use WP rounds? Aren’t they for very spe­cific anti-​​personnel uses? You’d think the bad guys would use the high­est explo­sive power for IEDs, par­tic­u­larly, rather than a quasi-​​chemical round like this. Or maybe it is a sort of “poor man’s” chem­i­cal weapon inso­faras the effects. Not sure, any ideas? 

Here’s more below the break:

(more…)

Schwartz Wish List: Boost F-​​35, Plan NGB

Thursday, May 21st, 2009

This arti­cle first appeared in Aerospace Daily & Defense Report.

U.S. Air Force Chief of Staff Norton Schwartz said increas­ing pro­duc­tion rates for the F-​​35 Joint Strike Fighter and devel­op­ing the next-​​generation bomber are at the top of his wish list of projects to fund if the ser­vice had more money.

Testifying before the House Armed Services Committee on the Air Force’s $160.5 bil­lion fis­cal 2010 bud­get request May 19, Schwartz said ser­vice lead­ers felt they had enough tac­ti­cal air­craft capa­bil­ity despite Defense Secretary Robert Gates’ plans to halt F-​​22 Raptor pro­cure­ment at 187 air­craft.

The Air Force chief said the service’s lead­er­ship believed it was a “pru­dent oppor­tu­nity to accel­er­ate the retire­ment of older air­craft.” The FY ’10 bud­get calls for retir­ing 250 F-​​15s, F-​​16s and A-​​10s, enabling the Air Force to redis­trib­ute more than $3.5 bil­lion over the next six years to mod­ern­ize com­bat air forces into a “smaller but more capa­ble force,” Schwartz and Air Force Secretary Michael Donley told law­mak­ers in joint writ­ten tes­ti­mony.

Schwartz did say more money would make it eas­ier and faster to upgrade remain­ing legacy air­craft and make mod­i­fi­ca­tions to the F-​​22 until the F-​​35 starts rolling off the line in large num­bers.

Schwartz said the Air Force would like to see F-​​35 pro­duc­tion boosted to at least 80 air­craft and per­haps as many as 110 per year before the F-​​16s start retir­ing in large num­bers.

Committee mem­bers, includ­ing Chairman Ike Skelton (D-​​Mo.) and Rep. John McHugh (N.Y.), the senior Republican on the panel, wor­ried about pro­duc­ing and fly­ing an air­craft while it was still being tested.

Donley con­ceded bud­get con­straints com­pelled the Air Force to make some dif­fi­cult calls. If there was more money “we might have made some dif­fer­ent choices,” Schwartz added. But both lead­ers insisted the Air Force was not short-​​changing itself.

The chief of staff said his wish list also included devel­op­ing plans for the future long-​​range strike capa­bil­ity. “We need, through the QDR [Quadrennial Defense Review] and the NPR [Nuclear Posture Review] to get our sec­re­tary of defense com­fort­able with the para­me­ters of what we pro­pose for that platform.”

Read the rest of this story, see who’s call­ing for more laser power, see if it’s a drone or a toy and read the USAF wish list for 2010 from our friends at Aviation Week, exclu­sively on Military​.com.

– Christian

On Again, Off Again FCS

Thursday, May 21st, 2009

fcs-boeing.jpg

It’s ramp­ing up to a thun­der­ing fusilade…

The FCS lobby is load­ing up the bombs, feed­ing the ammo belts and launch­ing the salvos.

While the Pentagon’s offi­cial posi­tion is that the FCS pro­gram will be rad­i­cally restruc­tured and the ground vehi­cle pro­grams killed, Army and indus­try offi­cials are act­ing as if “there’s noth­ing to see here.”

On Tuesday, FCS co-​​prime Boeing released a state­ment say­ing it had com­pleted a “System of Systems Preliminary Design Review” and, guess what, it totally val­i­dated the FCS pro­gram and showed how much bet­ter the Army would be with the entire web of sen­sors, robots, ground vehi­cles and networks.

The SoS PDR is the most com­pre­hen­sive review of the pro­gram to date. It val­i­dated that the designs for all FCS sys­tems and sub­sys­tems, includ­ing the net­work, sen­sors, weapons and manned and unmanned vehi­cles, meet cur­rent require­ments and will func­tion as an inte­grated sys­tem of sys­tems. The review proved that a fam­ily of net­worked sys­tems will pro­vide greater com­bat capa­bil­i­ties, includ­ing enhanced intel­li­gence, sur­veil­lance, and recon­nais­sance capa­bil­i­ties, across the full spec­trum of con­flict.

No way!? So all this talk about vul­ner­a­ble vehi­cles, net­work band­width prob­lems and sched­ule slips is baloney?

And our boy Greg Grant from DoD Buzz reports that Gen. George Casey, the Army’s chief of staff, had a momen­tary bout of hon­esty when he told the SASC this week that he didn’t ask for or want the FCS rejig­ger­ing but he’d been forced to back it.

Asked by SASC chair Senator Carl Levin whether he agreed with Defense Secretary Robert Gates deci­sion to can­cel the FCS vehi­cles, Casey said: I sup­ported it; I did not agree with it. The fun­da­men­tal point of dis­agree­ment, he said, was whether the vehi­cle design included suf­fi­cient pro­tec­tion against IEDs.

Oh, the boxes we get put in…

And yes­ter­day the Pentagon announced a hastily-​​called together press con­fer­ence for today where Army offi­cials would help reporters under­stand the service’s mod­ern­iza­tion pro­gram for Brigade Combat Teams. One won­ders what they would have said had not the presser been can­celled this morn­ing with­out prejudice.

I have always believed that the FCS pro­gram was far too com­plex to exe­cute both tech­no­log­i­cally and fis­cally as a total pack­age but was tai­lor made as a sort of ser­vice “Skunk Works” that could develop the asso­ci­ated tech­nolo­gies for futur­is­tic solu­tions to aging plat­forms and incre­men­tally pop­u­late them within the force. It’s as if you’re work­ing toward that Buck Rogers goal every day know­ing full well you won’t get there but that at least part of the fruits of your labors will be incor­po­rated into forces who need them today.

The Army’s going to need a replace­ment for the Bradley and M1 soon and as the devel­op­ment of the JLTV shows, there’s lots of cut­ting edge solu­tions or just beyond the edge ones that could make the next set of ground vehi­cles more deadly to bad guys and safer for Joes. Or are we at a tip­ping piont here — kind of like the one the Air Force is strug­gling with — where it’s all just a waste of money spent on manned sys­tems. Is it close enough for us to envi­sion robot ground vehi­cles pum­mel­ing enemy redoubts instead of manned ones in the next “generation?”

Maybe so…

– Christian Lowe