A Technical Computing revolution

Last week I enjoyed hosting a visit in Redmond from Chris Kemp, NASA’s new Chief Technology Officer for information technology. Our discussions were with folks from the Windows Azure cloud computing team, the high-performance computing and large-data folks, and our Extreme Computing Group. I smiled when Chris said he was a fan of the book Total Recall: How the E-Memory Revolution Will Change Everything, written by Microsoft’s Gordon Bell and colleague Jim Gemmell. (I wrote about their research projects in an earlier post, Total Recall for Public Servants.)

Inside Cyber Warfare

One year ago, the buzz across the government/technology nexus was focused on a pair of political guessing games. Neophytes mostly engaged in debating over whom the newly-elected President would name to be the nation’s first Chief Technology Officer. Grizzled Pentagon veterans and the more sober Silicon Valley types wondered instead who would get the nod as President Obama’s “Cyber Czar.”

Way Ahead and Far Behind

Today’s Washington Post has a story on its front page: “Staff Finds White House in the Technological Dark Ages.”

Two years after launching the most technologically savvy presidential campaign in history, Obama officials ran smack into the constraints of the federal bureaucracy yesterday, encountering a jumble of disconnected phone lines, old computer software, and security regulations forbidding outside e-mail accounts.”

“What does that mean in 21st-century terms? No Facebook to communicate with supporters. No outside e-mail log-ins. No instant messaging. Hard adjustments for a staff that helped sweep Obama to power through, among other things, relentless online social networking.”  -Washington Post

Some say that whoever has been responsible for information technology in the White House itself should be fired — but then perhaps the change of Administration just took care of that  🙂 

Overall, this situation is familiar to anyone who has worked in what I call “Big-G  IT” or the information technology of a federal government agency. I’ve argued about its challenges and sub-optimality before: see my previous pieces on “Roadmap for Innovation: From the Center to the Edge,” and more specifically “Puncturing Circles of Bureaucracy.”  In that latter piece back in March of 2008, I wrote about the “the defensive perimeters of overwhelming bureaucratic torpor,” and the frustrating reality within much of Big Government: “Federal employees have an entire complex of bizarrely-incented practices and career motivations, which make progress on technology innovation very difficult, not to mention general business-practice transformation as a whole.”

Here’s the truly frustrating, mind-bending part: it isn’t always true!  Other elements of the White House have cutting-edge, world-class technologies operating day in, day out.

Swap Panetta and Blair: A Modest Proposal

First, a quick story from when I was working in government.

Not long after the initial establishment of a “Director of National Intelligence,” the DNI CIO held an inaugural “DNI Information Sharing Conference” in Denver in the summer of 2006. I was asked to sit on a panel about “Innovation across the Intelligence Community,” representing the Defense Intelligence Agency and sharing the stage with two counterparts, from the CIA and NSA.  Our panel chair was Mr. CJ Chapla, then the Chief Technology Officer (CTO) of the old Intelink Management Office, redubbed “Intelligence Community Enterprise Services,” an office now under the Office of the DNI (ODNI). CJ asked the three of us to describe briefly the goals and projects we were each working on, and in seriatim that’s what we did for 90 minutes or so.

When it was time for questions, the very first audience-member asked: “It seems that each of you are independently working on, and paying for, very similar kinds of technology projects. It would make sense to combine or rationalize the work, so why are you continuing to do it independently?”

DHS Job Opening for Cyber Security CTO

There’s been much press attention to the promised new position of “Federal Chief Technology Officer” in the new Obama Administration, but the government has another vitally important CTO opening, and the job advertisement just got posted.

Agency: Department Of Homeland Security, DHS Headquarters
Sub Agency: National Cyber Security Center
Job Announcement Number: CHCO-08-055DHS
Title: Chief Technology Officer
Salary Range: 117,787.00 – 177,000.00 USD
Series & Grade: [Senior Executive Service] ES-2210-00/00
Duty Location: Washington DC Metro Area, DC

   – USAJOBS.com listing 

 

I received an email last week from a DHS friend quietly asking that I “publicize” the listing once it was posted, which was scheduled to be last week.  I checked for it online Friday – the first day applications were to be accepted – but must have looked too early for I didn’t see it listed.  That’s understandable, given the holidays, so I checked again last night, prompted by a note from Bob Gourley of CrucialPoint, and the listing was live.

The listing has an application deadline of Thursday, January 15, 2009, so if you’re interested in applying you had better get cracking.

Let’s look at a couple of the specific points mentioned in the job announcement.

Some say Obama has already chosen Cyber Czar

I’ll wade into the breach again, of analyzing (and trying to anticipate) some national-security appointments for the new Obama Administration.  Today I must admit that I’m taken with the latest reportage from the U.K. Spectator – a quite conservative publication not usually known for its closeness to the Obama inner circle.

Elbowing for Obama influence between new CTO, new cyber czar

Today’s Friday – usually a big news day in Washington, whether by design (bury bad news late in a deep weekend news hole) or by human error (bureaucrats tried all week to get something done and slipped it in at the deadline).  There should be Obama cabinet announcements today, and meanwhile tech luminaries across the country are sitting by their phones, drumming their fingers and hoping for a call offering them the position of the nation’s first Chief Technology Officer. Norm Lorentz, who was OMB’s first-ever CTO, told C-SPAN this week that “If I were asked, I would serve in a heartbeat.”

My bold decision to withdraw from consideration as Obama’s CTO

To: President-Elect Barack Obama

From: Lewis Shepherd

RE: My Imminent Selection as Chief Technology Officer for the United States

Mr. President-Elect, I am hereby reluctantly but insistently withdrawing my name from consideration as your appointment to the newly created position of Chief Technology Officer for our nation.

No, no, please don’t try to persuade me otherwise. My decision is final.

Analysis: My earlier post about John Brennan being President-elect Obama’s “imminent” selection as CIA director is now a curio, given Brennan’s decision yesterday to withdraw from consideration. 

Like any good intelligence analyst writing a balanced assessment, I had included the caveat that the only thing standing between Brennan and the appointment was the likelihood of a last-minute political squabble or contretemps.

This being Washington we’re talking about, that is precisely what happened. 

Amazon and Microsoft Intersect in the Cloud

So today Werner Vogels, the much admired CTO of Amazon, has a post over at “All Things Distributed” which directly exemplifies his blog’s subtitle (“building scalable and robust distributed systems“).  The post is “Expanding the Cloud” and describes today’s announcement that Microsoft Windows Server is available on Amazon EC2. As he sums it up, “We can now run the majority of popular software systems in the cloud.”

This means two things.  First, we were able to con cajole convince Amazon essentially to host a beta test for something big, which will indubitably become much, much bigger.

WIRED Cracks Cyber-Battle Code

Just a quick note between conflicting conference sessions in different locations around the DC Beltway, to note that WIRED’s premier national-security blogger Noah Schactman may have just cracked the code – or at least “a” code – on where the ongoing dispute over “control of cyber” is heading in national security circles, in his latest DangerRoom post (“Air Force Cyber Command Could Return, with Nukes“).

The dispute has been reported lightly, in places like the NextGov blog (“The Cyber Command Power Play?”), and usually boils down to a perceived battle between the U.S. Air Force and the nation’s Intelligence Community, over control of the increasingly central issue of cyber offense and cyber defense.