Trying to change the culture-driven patterns of IT spending in the military services by issuing edicts would not work, and should not work, the Pentagon\'s chie...
wfedstaff | June 4, 2015 10:14 am
By Jared Serbu
Reporter
Federal News Radio
Like other federal CIOs, the Defense Department’s chief information officer has some new authority, thanks to an Office of Management and Budget memo issued earlier this month. But DoD’s CIO said she has no intention of managing the military services by edict. And the memo won’t change that.
Among other things, the OMB memo gave agency CIOs full authority over their commodity information technology spending. But Pentagon CIO Teri Takai said DoD is a large enterprise with effective CIOs in each of the military services. She has no intention of telling each service precisely how to allocate their IT dollars.
“I don’t have any illusion that it makes any sense for me to try to control the more than $38 billion we spend,” she said. “That’s a construct that would never work, and it shouldn’t work. The work that’s being done in the services is the real work, and it’s the work that closest to those that need to work done. It’s getting done very, very well. We’d like it to cost a little less, and we’d like it to be less painful, but I think it’s very important for us to know it’s getting done.”
Takai said even if she has the authority to mandate changes to many of the culture-driven IT spending decisions in the military services, issuing those mandates would be a bad idea. In a roundtable briefing with reporters at the Defense Information Systems Agency’s annual conference in Baltimore, she said her job is to understand the needs of the military services and try to meet them in a way that benefits DoD as an enterprise.
“Starting from the belief that no matter how much power you have, you can mandate [culture change], isn’t going to be successful in any sense,” she said. “Having said that, you do have to get to the point where as you establish what the enterprise should do, that there are directives. And in some cases, there are consequences for noncompliance for those things that are really critical.”
Takai said her office will take an active role in the oversight of DoD’s overall IT budget. She said she and her staff are also working on forthcoming directives dealing with information assurance on mobile devices, as well as commercial cloud services. She said those directives would be pivotal for the department, but did not provide details.
Takai spoke with reporters just after she moderated a panel discussion with the CIOs of all four of DoD’s military services at the DISA conference. On the panel, she broached the topic of the Army’s new enterprise email system and the way email addresses on the new system look. Instead of army.mil, users addresses are now within the new mail.mil domain.
The Army designed the system that way because it wanted the DISA-provided service to be a joint enterprise from the beginning, said Lt. Gen. Susan Lawrence, the Army’s CIO.
She also knew going in that even the seemingly small matter of removing individual service identities from email addresses would be a tough sell to some of the other services, she said.
“We earned the title United States Marines, and we are damn proud of it,” said Brig. Gen. Kevin Nally, the Marines’ CIO, as he rose from his chair on the panel. “You can have at whatever dot-mil you want to have, but you’re not changing my culture.”
“I loved the fact that the Marines stood up and stated where they are,” Takai said following the panel. “That’s much better than saying, in the background, ‘she’s crazy and we’re not going to do it anyway.’ And so what we’ve established is an openness to have debates. I picked email addresses deliberately to talk about this morning, because I knew there wasn’t agreement. So the dialogue’s going to be around what the pros and cons are. What’s the benefit to the individual service, versus the pros and cons to an individual who has the ability to move around in DoD? What are the costs of all these email systems? What are the security implications? We’ll continue to have that debate.
Takai said she has no intention of issuing a mandate on enterprise email addressing schemes, nor will she order the rest of the services to get on board with the DISA private cloud email system, as the Army and several combatant commands have. She said she would rather see the services adopt it because they see value in it.
“Remember that enterprise email doesn’t necessarily mean that everybody goes to DISA. We have to get to a common identity management structure, we have to get to a common directory structure, we have to be able to collaborate. That’s really the infrastructure that’s critical here. We’re working with the Navy right now, to say, ‘what does that look like for Navy?’ My preference is to work through the technical details to get to our end objective, because when you do that, you don’t have to dictate. Otherwise, if I dictated something, I’m going to be the bad guy every time somebody’s Blackberry doesn’t work. That doesn’t get you to the end objective.”
Takai said DoD will be able to report back to OMB on the directives in this month’s memo with concrete progress even if she isn’t taking full control of the department’s IT dollars.
“The question that OMB is asking around strengthening the role of the CIO and getting more control over the operations isn’t just me,” she said. “It’s me in combination with the CIOs in the military services. You’re going to see us be able to report on all of these efficiency initiatives, and the second thing they’re expecting from us is better control of our programs. You see that in the techstat reporting and a number of the initiatives that have been laid out in our IT reform.”
RELATED STORIES:
OMB gives agency CIOs more budget authority
Shrinking budgets may be a blessing for DoD IT
Kundra pitches more budget authority for CIOs
Army cloud email a ‘pathfinder’ to enterprise services
(Copyright 2011 by FederalNewsRadio. All Rights Reserved.)
Copyright © 2024 Federal News Network. All rights reserved. This website is not intended for users located within the European Economic Area.