Agencies not yet sold on software as a service
- By Jason Miller
- Jan 16, 2008
Industry experts expect the federal government will move more aggressively to buying software as a service during the next two years, but agency officials warned that there are huge security and culture questions that need to be answered first.
Software as a service is a burgeoning trend in the commercial marketplace, but agencies have yet to take full advantage of it, experts say.
The concept of software as a service is not necessarily new — it is similar to managed services or application service provider offerings. In this case, users buy access to a specific platform used by many different companies or agencies at the same time. Users also buy software through a subscription fee or each time they use it as opposed to buying the license and maintenance.
“Software as a service is growing in acceptance, but it is slow,” said Richard Colven, vice president of Input at the Software As A Service conference sponsored by the Software and Information Industry Association, Input and the Information Technology Association of America in Washington. “The consensus is that this is something agencies are moving toward, but there is a huge educational challenge because many people don’t understand the fine print.”
Colven said Input surveyed 66 federal executives and found many are hesitant to move to this model immediately, but see it happening in time.
Colven and others said examples of software as a service in government include human resource and financial management Line of Business shared service providers.
“We are familiar with hosted services such as EDS and the Navy-Marine Corps Intranet,” said Curt Kolcun, Microsoft’s vice president for the federal division. “There also are data centers and other services running in the cloud. The platform on the Internet must be the same one the end customer or host partner runs.”
Colven said Input estimates that agencies will spend about $34 million on software as a service in fiscal 2008, but spending will increase to $74 million in 2009 and $95 million in 2010.
Input’s survey found that federal executives believe the desktop is one of the most likely places that software as a service will find a home.
But Kevin Carroll, the former program executive officer for the Army’s PEO Enterprise Information Systems office, said the Army is skeptical about software as a service.
“The Army and others want to know why industry is doing this,” he said. “When we have done lease/purchase cost analysis, it is always cheaper to buy so we need to understand the return on investment to pay for the service.”
Fred Schobert, chief technology officer for the Federal Acquisition Office’s Integrated Technology Services (ITS) office at the General Services Administration, said this concept presents security and funding challenges, too.
“How do we present software as a service to our 135 customers and ensure they know it is secure?” Schobert said.
He said agencies must certify and accredit their systems and the vendors providing the software would, too.
Schobert added that many agencies don’t think they can do pay-as-you-go model because they have fixed funding.
But Aneesh Chopra, Virginia’s secretary of technology, said software as a service opens the door to broader collaboration on application development and more reuse of existing components.
“Software as a service is critical to lower development costs,” he said.
Chopra said Virginia agencies are using this concept to build a one-stop portal for citizens starting new businesses so they don’t have to fill out forms asking for duplicative information more than once.
Schobert said agencies need to understand that the software as a service is flexible enough to meet their needs, secure enough to protect their data and cost effective.