Guidelines for Implementing Software-as-a-Service

By Sandra Gittlen | Posted July 27, 2007
While more small businesses are taking to the software-as-a-service model, experts warn that offloading your applications does not mean offloading responsibility.

“It’s important to understand that even if you go with a hosted service, you still have to manage the quality of that application,” says Irwin Lazar, analyst with Nemertes Research.

In the SaaS model, applications are hosted by providers over the Internet and companies are charged for usage rather than ownership. Lazar says the benefit of this approach is that small businesses do not have to spend limited budgets to buy and operate complex infrastructure.

In the financial sector, more than 60 percent of the top 150 U.S. banks use at least one service-based cash management or small-business banking application, and more than 90 percent of community-sized banks (those below $4 billion in assets), use a shared service platform to offer customers Internet or small business banking. Sean O’Dowd, analyst with IDC’s Financial Insights research firm, says SaaS enables banks to forego large upfront capital expenditures, such as licensing and servers, and spread out costs over time, increasing revenue predictability.

SaaS Driven by Savings
Lazar agrees. “What’s driving this move to SaaS is cost. If I’m an IT manager looking at the next version of a productivity suite, I can either buy a license at $200 a seat and have troubleshooting, infrastructure and management costs, or I could subscribe to a service. It’s a no-brainer,” he says.

He points out that the SaaS model is most attractive for commodity applications, such as customer relationship management, human resources, payroll and Web conferencing, not core software, such as programs supporting research and development. “There’s a lot more sensitivity around the company’s crown jewels,” he says.

No matter how common the task, companies must be on their toes when dealing with outsourcers, says Danny Allan, director of security research at Web application security vendor Watchfire Corp. in Waltham, Mass. ““The biggest risk in SaaS is you don’t know how secure the provider is, and internal data is outside the organization,” he says.

Check List: Five Key Considerations
He advises examining five key areas when deciding on an SaaS provider: privacy and security policies; transparency into the provider’s organization; metrics regarding audits and response to security breaches; strong feedback loops; and continuous education for customers.

Organizations should guarantee that authorization and access controls are strong not only between them and the provider, but also among the providers’ other customers that share the infrastructure. Allan admits that this can be difficult to gauge so he recommends asking to see a written policy. “This will tell you whether the organization is mature.”

He also encourages those considering SaaS to write into their contracts that they will have access to testing schedules, software development life cycles, and upgrade and patch deployments. “If you don’t know when they are running upgrades, there is a serious risk of downtime,” he says.

Just as important as transparency is having a backup and exit strategy for data. Tim O’Brien, director of the platform strategy group at Microsoft, says companies need flexibility and insurance built into the SaaS model.

“As your business changes, you may want to bring the application on-premise. You can’t be locked into a certain data set. You need portability and you need to know how you’re going to migrate data [off their servers],” he says. Microsoft has several SaaS offerings, including Dynamics Live and Office Live.

Have a Back Up Plan
He also warns that although there are great promises of “broadband ubiquity,” outages do happen and IT managers must protect themselves from this probability. “You need some measure of local capability behind your firewall to maintain business operations,” he says. “Also, the terms of use between you and the provider become very, very important. You have to lay out what happens if data gets lost or there is downtime.”

O’Brien says another aspect to consider is the provider’s accounting methods. “You should know how the billing mechanism on the back-end works. How are your charged? On a per-transaction basis or monthly?” he says. One of the many advantages of the pay-as-you-go model is the built-in reporting it offers. Everything is metered so companies can see usage trends, he says. With such detail, there is opportunity to negotiate optimal rates.

Before organizations even consider SaaS as an option, they must do some legwork, according to Rachel Lyubovitzky, director at SaaS-vendor KnowledgeSum. IT teams must first inventory all their on-premise applications and tasks and decide what’s core and what’s commodity. They then need to consider how much customization and integration with other software they’ll need for optimal user productivity. Finally, she says IT managers must consider the requirements they have around data ownership, such as security, privacy regulations, and federal and private sector mandates.

Once you approach the provider, Lyubovitzky says it’s important not to get pinned down. “If anything is unclear — data security, compliance or service levels — and you don’t feel 100 percent sure, then just walk away,” she says.

This article originally appeared July 23, 2007 on EarthWeb's Datamation site.

Do you have a comment or question about this article or other small business topics in general? Speak out in the SmallBusinessComputing.com Forum. Join the discussion today!

Comment and Contribute


     

    Get free tips, news and advice on how to make technology work harder for your business.

    Submit
    Learn more
     
    You have successfuly registered to
    Enterprise Apps Daily Newsletter
    Thanks for your registration, follow us on our social networks to keep up-to-date