The Myth of Chargeback

 

Cash Register

Cash register by the National Cash Register Co., Dayton, Ohio, United States, 1915.

Imagine a world where every aspect of a project gets charged correctly. Where the massive amount of compute time for a given project gets labeled into the proper department and billed correctly. Where resources can be allocated and associated to the projects that need them. It’s an exciting prospect, isn’t it? I’m sure that at least one person out there said “chargeback” when I started mentioning all these lofty ideas. I would have agreed with you before, but I don’t think that chargeback actually exists in today’s IT environment.

Taking Charge

The idea of chargeback is very alluring. It’s been on slide decks for the last few years as a huge benefit to the analytics capabilities in modern converged stacks. By collecting information about the usage of an application or project, you can charge the department using that resource. It’s a bold plan to change IT departments from cost centers to revenue generators.

IT is the red headed stepchild of the organization. IT is necessary for business continuity and function. Nothing today can run without computers, networking, or phones. However, we aren’t a visible part of the business. Much like the plumbers and landscapers around the organization, IT’s job is to make things happen and not be seen. The only time users acknowledge IT is when something goes wrong.

That’s where chargeback comes into play. By charging each department for their usage, IT can seek to ferret out extraneous costs and reduce usage. Perhaps the goal is to end up a footnote in the weekly management meeting where Brian is given recognition for closing a $500,000 deal and IT gets a shout-out for figuring out marketing was using 45% more Exchange server space than the rest of the organization. Sounds exciting, doesn’t it?

In theory, chargeback is a wonderful way to keep departments honest. In practice, no one uses it. I’ve talked to several IT professionals about chargeback. About half of them chuckled when I mentioned it. Their collective experience can best be summarized as “They keep talking about doing that around here but no one’s actually figured it out yet.”

The rest have varying levels of implementation. The most advanced ones that I’ve spoken to use chargeback only for physical assets in a project. If Sales needs a new server and five new laptops for Project Hunter, then those assets are charged back correctly to the department. This keeps Sales from asking for more assets than they need and hoping that the costs can be buried in IT somewhere.

No one that I’ve spoken to is using chargeback for the applications and software in an organization. We can slice the pie as fine as we want for how to allocate assets that you can touch but when it comes to figuring out how to make Operations pay their fair share of the bill for the new CRM application we’re stuck. We can pull all the analytics all day long but we can’t seem to get them matched to the right usage.

Worse yet, politics plays a big role in chargeback. If a department head disagrees with the way their group is being characterized for IT usage, they can go to their superiors and talk about how critical their operation is to the business and how they need to be able to work without the restrictions of being billed for their usage. A memo goes out the next day and suddenly the department vanishes from the records with an admonishment to “let them do their jobs”.

Cloud Charges

The next thing that always comes up is public cloud. Chargeback proponents are waiting for wide-spread adoption of public cloud. That’s because the billing method for cloud is completely democratic. Everyone pays the price no matter what. If an AWS instance is running someone needs to pay for it. If those systems can be isolated to a specific application or department then the chargeback takes care of itself. Everyone is happy in the end. IT gets to avoid blame for not producing and the other departments get their resources.

Of course, the real problem comes when the bills start piling up. Cloud isn’t cheap. It exposes the dirty little secret that sunk-cost hardware has a purpose. When you bill based on CPU hour you’ll find that a lot of systems sit idle. Management will come unglued trying to figure out how cloud costs so much. The commercials and sales pitches said we would save money!

Then the politics start all over again. IT gets blamed because cloud was implemented wrong. No protesting will fix that. Then comes the rapid costs cutting measures. Shutting off systems not in use. Databases lose data capture for down periods. People can access systems in off hours. Work falls off and the cloud project gets scrapped for the old, cheaper way.

Cloud is the model for chargeback that should be used. But it should be noted that we need to remember those numbers need to be correctly attributed. Just pushing a set of usage statistics down without context will lead to finger pointing and scrambling for explanation. Instead, we need to provide context from the outset. Maybe Marketing used an abnormally high amount of IT resources last week. But did it have anything to do with the end of the quarter? Can we track that usage back to higher profits from sales? That context is critical to figuring out how usage statistics affect things overall.


Tom’s Take

Chargeback is the stick that we use to threaten organizations to shape up and fly right. We make plans to implement a process to track all the evil things that are hidden in a department and by the time the project is ready to kick off we find that costs are down and productivity is up. That becomes the new baseline and we go on about our day think about how chargeback would have let us catch it before it became a problem.

In reality, chargeback is a solution that will take time to implement and cost money and time to get right. We need data context and allocation. We need actionable information and the ability to coordinate across departments. We need to know where the charges are coming from and why, not just complaining about bills. And there can be no exceptions. That’s the only way to put chargeback in charge.

 

My Buzzword Security Blanket

If you’ve been following the networking world for a while, you’re probably getting sick of hearing the words cloud and fabric.  The former is something of a nebulous term used to describe all manner of strange things.  Hosted e-mail, hosted websites, hosted storage, infrastructure as a service (IAAS), software as a service (SAAS), virutal machine hosting, and so on.  Every major networking and server player has some sort of cloud-based strategy.  Yet, when I think of clouds, I think of the little white fluffy things I put on network diagrams when I denote a section outside my control that I don’t really care about, like a WAN frame relay section or the Internet.  So when I hear about providers telling me to move “to the cloud”, I laugh.  I think about hosted Hotmail account I’ve had for 13 years.  Or the services like Dropbox that I’m starting to use for many things now.  But I don’t think of them as cloud services, per se.  Just software that is useful.

Fabric is another overused term, especially in the datacenter.  Fabric is the term that describes connecting nodes in the network together in a meshed-type of environment, like a rug or a shirt.  The resulting output is termed fabric.  This term used to be very popular with the storage people back in the day.  Now that the storage network has been unified with the server network the term seems to be leaking into our little world.

With all this in mind, I tweeted a little joke a week or so ago:

And then people came out of the woodwork.  Someone suggested I make it borderless to be compliant with Cisco’s Borderless Networks initiative.  A couple of people told me that I should send them one.  Greg Ferro even thought it was a good idea.  So, after a little shopping with my wonderful wife this past weekend, we came up with this:

Pretty, isn’t it?  I thought the bears added a little something.  Also, no stitching on the edges so it really is “borderless”.  This is my Buzzword Security Blanket.  I’m going to carry it with me everywhere I go.  Anytime someone talks to me about “Cloud this” or “Fabric that”, I’m going to curl up with my blanket and wait until all the mean people leave me alone.  I think of my nice secure data centers where my packets can cozy up with their Buzzword Security Blankets at night, safe and sound and right where I want them to be, protected from the evil in the cloud.  And when someone carries on about the new exciting fabric options in their strategies, I’ll nuzzle my Buzzword Security Blanket against my cheek and remind myself that it’s all the fabric I’m ever going to need.

Who knows?  If this takes off, I could do a whole line of baby-themed networking buzzword items.  Let me know what you think.