This Page

has been moved to new address

Green SaaS is for Real - Green eDiscovery is Next !!

Sorry for inconvenience...

Redirection provided by Blogger to WordPress Migration Service
----------------------------------------------------- Blogger Template Style Name: Snapshot: Madder Designer: Dave Shea URL: mezzoblue.com / brightcreative.com Date: 27 Feb 2004 ------------------------------------------------------ */ /* -- basic html elements -- */ body {padding: 0; margin: 0; font: 75% Helvetica, Arial, sans-serif; color: #474B4E; background: #fff; text-align: center;} a {color: #DD6599; font-weight: bold; text-decoration: none;} a:visited {color: #D6A0B6;} a:hover {text-decoration: underline; color: #FD0570;} h1 {margin: 0; color: #7B8186; font-size: 1.5em; text-transform: lowercase;} h1 a {color: #7B8186;} h2, #comments h4 {font-size: 1em; margin: 2em 0 0 0; color: #7B8186; background: transparent url(http://www.blogblog.com/snapshot/bg-header1.gif) bottom right no-repeat; padding-bottom: 2px;} @media all { h3 { font-size: 1em; margin: 2em 0 0 0; background: transparent url(http://www.blogblog.com/snapshot/bg-header1.gif) bottom right no-repeat; padding-bottom: 2px; } } @media handheld { h3 { background:none; } } h4, h5 {font-size: 0.9em; text-transform: lowercase; letter-spacing: 2px;} h5 {color: #7B8186;} h6 {font-size: 0.8em; text-transform: uppercase; letter-spacing: 2px;} p {margin: 0 0 1em 0;} img, form {border: 0; margin: 0;} /* -- layout -- */ @media all { #content { width: 700px; margin: 0 auto; text-align: left; background: #fff url(http://www.blogblog.com/snapshot/bg-body.gif) 0 0 repeat-y;} } #header { background: #D8DADC url(http://www.blogblog.com/snapshot/bg-headerdiv.gif) 0 0 repeat-y; } #header div { background: transparent url(http://www.blogblog.com/snapshot/header-01.gif) bottom left no-repeat; } #main { line-height: 1.4; float: left; padding: 10px 12px; border-top: solid 1px #fff; width: 428px; /* Tantek hack - http://www.tantek.com/CSS/Examples/boxmodelhack.html */ voice-family: "\"}\""; voice-family: inherit; width: 404px; } } @media handheld { #content { width: 90%; } #header { background: #D8DADC; } #header div { background: none; } #main { float: none; width: 100%; } } /* IE5 hack */ #main {} @media all { #sidebar { margin-left: 428px; border-top: solid 1px #fff; padding: 4px 0 0 7px; background: #fff url(http://www.blogblog.com/snapshot/bg-sidebar.gif) 1px 0 no-repeat; } #footer { clear: both; background: #E9EAEB url(http://www.blogblog.com/snapshot/bg-footer.gif) bottom left no-repeat; border-top: solid 1px #fff; } } @media handheld { #sidebar { margin: 0 0 0 0; background: #fff; } #footer { background: #E9EAEB; } } /* -- header style -- */ #header h1 {padding: 12px 0 92px 4px; width: 557px; line-height: 1;} /* -- content area style -- */ #main {line-height: 1.4;} h3.post-title {font-size: 1.2em; margin-bottom: 0;} h3.post-title a {color: #C4663B;} .post {clear: both; margin-bottom: 4em;} .post-footer em {color: #B4BABE; font-style: normal; float: left;} .post-footer .comment-link {float: right;} #main img {border: solid 1px #E3E4E4; padding: 2px; background: #fff;} .deleted-comment {font-style:italic;color:gray;} /* -- sidebar style -- */ @media all { #sidebar #description { border: solid 1px #F3B89D; padding: 10px 17px; color: #C4663B; background: #FFD1BC url(http://www.blogblog.com/snapshot/bg-profile.gif); font-size: 1.2em; font-weight: bold; line-height: 0.9; margin: 0 0 0 -6px; } } @media handheld { #sidebar #description { background: #FFD1BC; } } #sidebar h2 {font-size: 1.3em; margin: 1.3em 0 0.5em 0;} #sidebar dl {margin: 0 0 10px 0;} #sidebar ul {list-style: none; margin: 0; padding: 0;} #sidebar li {padding-bottom: 5px; line-height: 0.9;} #profile-container {color: #7B8186;} #profile-container img {border: solid 1px #7C78B5; padding: 4px 4px 8px 4px; margin: 0 10px 1em 0; float: left;} .archive-list {margin-bottom: 2em;} #powered-by {margin: 10px auto 20px auto;} /* -- sidebar style -- */ #footer p {margin: 0; padding: 12px 8px; font-size: 0.9em;} #footer hr {display: none;} /* Feeds ----------------------------------------------- */ #blogfeeds { } #postfeeds { }

Friday, October 2, 2009

Green SaaS is for Real - Green eDiscovery is Next !!

I was contacted by Chirs Thorman today about a study that he conducted to determine whether or not SaaS(Software-as-a-Service) really saves any trees and has a smaller carbon footprint (and some of you thought that I didn't care) than traditional one-site alternatives (your own server and network). Well, as it turns out, Mr. Thorman concluded that SaaS is 93% greener than what he calls "on-premise software". Good job Chris. So now, all of you anti-SaaS ecologically challenged people will have to start buying carbon credits from us more ecologically conscience SaaS greenies.... Click Here to see Mr. Thurman's Blog Post.

And, applying Mr. Thorman's basic theories to the "tree hating / paper wasting" litigation services / eDiscovery industry will create carbon footprint saving multiples vs. current SOPs that will turn some green heads. Litigaion services and eDiscovery coupled with SaaS may present one of the biggest opportunies within the Global 2000 to create a small carbon footpoint.

It's time for eDiscovery to go green!!

The full text of Mr. Thorman's blog post and study is as follows:

In case you haven’t heard (or aren’t obsessively following IT trends like we are), the great trend in software is the evolution from traditional “on-premises” software (e.g. client/server software installed at the office) to Software as a Service (SaaS) (i.e. web-based applications that are managed in the vendors’ data center and accessed “on-demand” through a web browser).

Given what’s at stake for software companies in either camp, debating the merits of each model has led to some fiery discourse. We thought we’d fan the flames by introducing another angle: which model is “greener;” that is, better for the environment.

Understanding the Models

On-premise software is what most people think of when they think of a software system. You pop in a CD or download a big file from the Internet and the install begins. Files are copied to your computer and/or a server machine, where they are stored and run. Because the client and server software components are both doing a lot of computations, a fair amount of power is required.

With SaaS, there is no local installation of software because the vendor manages all the code and the data in their data center. Users access the system through a web browser and its primary role is to present the user interface – not a very computationally intensive function.

On-Premise Energy Consumption

Now let’s dig into the power consumption of the on-premise model. We’ll use the example of a typical physician practice, since electronic medical records (EMR) software is a market we know well. The “On Premises” side of the graphic below illustrates a four-physician medical practice, running EMR software on their own in-house server.

The HP ProLiant DL server, one of the most commercially popular servers on the market today, will consume 7,008 KW of server energy per year. That’s running 24 hours a day, 365 days a year.

In addition, each user is using a Dell desktop 546, Dell’s most popular starter desktop. A single 546 Dell desktop will consume 600 KW of energy a year, running 8 hours a day for 250 days a year (an average work year).

A four-physician practice will consume 9,408 KW of power each year just to run EMR software on-premise. Each user will personally consume 2,352 KW of power each year.

SaaS Energy Consumption

Now let’s see how the energy consumption of SaaS software stacks up. Rackspace, one of the largest providers of cloud computing hosting services, lists the Dell PowerEdge 2950 III as one of it’s most popular server choices. And since a data center would have a redundant server in addition to the PowerEdge, our SaaS applications are powered by two of these servers.

Running 24 hours a day for 365 days a year, the total energy consumption for these two Dell servers running SaaS applications would be approximately 6,570 KW/yr each, or 13,140 KW/yr total.

However, in a modern SaaS data center there are economies of scale that enable the software vendor to run many customers on the same server (or small number of servers). The first way they might do this is to develop a “multi-tenant” architecture. That is, much like many people can share the same apartment building, SaaS customers can share the same software application and server. Extending the analogy, each SaaS user has their own passwords and permissions just like each tenant in an apartment building has their own set of keys.

Running this server in a SaaS data center allows the SaaS EMR vendor to tens or hundreds of customers on one server. When a new customer goes line with the application, the incremental computing requires – an power consumption – increase only marginally.

How does this affect energy consumption by our physicians?

Now our physicians are only using 131.4 KW (1/100th) of the Dell PowerEdge server energy each year because of the multi-tenant architecture. Also, because SaaS applications require less computing power on the client, the physicians are able to switch to more efficient Dell netbooks, which only consume 120 KW of power each per year.

Using SaaS, our four physician practice now only consumes 611.4 KW per year running their EMR software. That’s 152.85 KW per year, per physician.

That’s an 93% reduction in overall energy consumption for a four physician practice using SaaS EMR software over on-premise software!

Beyond Power Consumption

Power consumption isn’t the only area where we found that SaaS is greener than on-premises. Here are a few more considerations.

Remote IT support. Whether or not your IT support is in-house, they’re going to consume energy traveling to and from an office to perform maintenance and fix problems. Since there really isn’t much of anything to maintain at the office, SaaS vendors are able to provide remote IT support, reducing travel and CO2 emissions.

Less frequent replacement of PCs. Given that SaaS applications just require a web browser on the client machine, you really don’t need a very powerful PC. SaaS customers can keep their old machines in place or get a longer life from any new machines they buy. This compares to on-premises software, where customer will often upgrade hardware to support the computing resource requirements of new client software.

Telecommuting. Accessing on-premise software remotely is typically slower and more technologically complex than a SaaS application. With SaaS applications accessible from any computer with an Internet connection, employees can work remotely, saving fuel and energy costs in the process.

Labels: , , ,

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

Links to this post:

Create a Link

<< Home