Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


02:58 PM
Connect Directly

Navy CIO Details IT Cost Cuts

The Navy will consolidate applications and data centers, mandate enterprise licensing, improve IT governance, pursue cloud computing, and take other steps to cut IT costs 25% over five years.

14 Most Popular Government Mobile Apps
Slideshow: 14 Most Popular Government Mobile Apps
(click image for larger view and for slideshow)
In order to meet an order to cut its business IT budget by 25% over the next five years, the Navy will look to application consolidation, data center consolidation and optimization, mandated enterprise licensing, improved IT governance, and perhaps cloud computing, according to Navy CIO Terry Halvorsen.

Halvorsen had said in June that Navy IT managers would see "ruthless" internal cost cuts due to orders from the top, and Navy undersecretary Robert Work earlier this month revealed that the plan was to cut IT spending by a quarter in the coming years. Such a drastic cut, Halvorsen said, will require that the Navy do IT in a fundamentally different way than it has in the past, and to take risks where previously it may have been risk averse.

"We will not hit that target by doing the same things we do today more efficiently," Halvorsen wrote in a blog post published Wednesday. "A cut of this magnitude requires a fundamental shift in our IT business model. It will require taking risks and doing things that would have been considered too risky or too controversial in the past."

Consolidating and optimizing the Navy's data center and software strategies and improving governance, Halvorsen wrote, will reduce complexity and cut costs.

All told, the Navy is now running more than 2,000 applications on its current enterprise networks, including multiple versions of the same software. For example, the Navy has between seven records management systems alone. "We must look at these applications and question whether a unique requirement is worth the cost of multiple applications performing the same function, or whether an application is worth keeping if it's not widely used," Halvorsen wrote. A number of those apps, he added, will be eliminated.

Along with the app consolidation effort, the Navy also will mandate enterprise licensing. The Navy has set up enterprise contracts for Microsoft software, and more are on the way. "We must require purchasing via enterprise licenses with no waivers granted," he wrote. "Allowing waivers led us to where we are today with multiple versions of software." In concert with the enterprise-licensing mandate, the Navy also will look to prevent customization of software and even possibly change business processes rather than customizing software to fit pre-existing processes.

Apps aren't the only thing that will be consolidated and managed better under the Navy plan: Data center and storage consolidation and optimization will form a key part of the savings. Currently, the Navy has between 140 and 150 data centers that Halvorsen said "are not optimally located." The Navy has closed seven data centers this year, and plans by the end of 2013 to have fewer than 100 data centers, with more cuts planned after that.

Earlier this year, Halvorsen said that the first data centers likely to go would be mid-sized data centers that service only one command or function. Improvement of the Navy's data standards will be another piece of this effort.

In order to make that happen, though, the Navy will have to stop data center growth. Last week, Halvorsen placed a moratorium on the purchase of new data storage capacity with limited exceptions, building on the White House's Federal Data Center Consolidation Initiative and an earlier order from the deputy chief of naval operations for naval dominance to stop spending on new data centers and servers.

Halvorsen wrote that he'll also be placing increasing emphasis on improved and more centralized IT governance in order to "enable the department to act more like an enterprise," but he admitted that this plan might run up against some cultural resistance. "Not everyone will like the result," he wrote.

The four prongs of Halvorsen's strategy don't stand alone, and the Navy is looking for other savings opportunities as well. For example, it's considering commercially provided email, creating a public-private venture to operate Navy data centers, client virtualization, and increased use of cloud computing.

At the 2011 InformationWeek 500 Conference, C-level executives from leading global companies will gather to discuss how their organizations are turbo-charging business execution and growth--how their accelerated enterprises manage cash more effectively, invest more wisely, delight customers more consistently, manage risk more profitably. The conference will feature a range of keynote, panel, and workshop sessions. St. Regis Monarch Beach, Calif., Sept. 11-13. Find out more and register.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...