Wednesday, October 31, 2012

Why Charge For Floorspace?


I work with quite a number of colocation providers and it still seems there is a mix of how colocation services are priced. In a retail environment, generally the major components are space and power. This has held true since I entered the colocation side of the industry in 1996. Back then, the floor space was considered the critical element as building more space was costly to the provider and most customers had very low power density requirements. Contracts would have one line item for space and another line item for power. So why, 16 years later, do we still see so many providers using the same model, despite colocation having undergone major changes?

The answer is most likely due to conditioning of the product groups, Sales teams, and even the customer. I've heard some providers say floor space is irrelavant now. That statement may hold true in certain circumstances, but we need to define those circumstances.

Each retail colocation facility will have a floor density associated to the colocation space as rated in "watts per square foot". Most people assume this is a power rating, but it actually has more to do with cooling of the power consumed within that space rather than the delivery of power to that space. If a space has a "watts per square foot" of 150, that means that for each given square foot of space used by a customer, the facility can accommodate 150 watts of cooling and power load. In a cage environment the math is simple: a 10 x 10 cage = 100 square feet and at 150 watts per square feet the cage can accommodate 15,000 watts. Simple, right? It gets more complicated in cabinets as each provider may use a different square footage for each cabinet, but for simplicity, let's assume a cabinet equates to 25 square feet. With the same 150 watts per square foot, that equates to 3,750 watts available to that cabinet.

Why does density matter when we are talking about charging for floor space? By knowing the watts a space can accommodate  we can quickly determine if a customer wants to utilize a larger amount of power than the space will accommodate  If so, then the floor space itself does not matter as the customer will always use less space than their power requirements require. If we tell that 10 x 10 cage customer we will sell them 15,000 watts (15 kW) of power and we know their power density requirement is higher than our 150 watts per square foot, then we also know they will not use all the floor space before they use all the power. Now we can just make our contract a single line item for power, inclusive of space.

Where we run into problems with the single line item pricing is if we have a customer that has power density requirements lower than our watts per square foot. I've seen this only once in the last 6 years. The customer was a provider that sold individual cabinets to their own clients. Most of their clients were dev environments that only needed a single 120v-20A circuit per cabinet. That power requirement equates to 1.92kW or 1,920 watts. With a 25 square foot cabinet, that means that each cabinet was really only needing 76.8 watts per square foot. In essence  that customer would have used double the floor space and if we were only charging for power, the provider would lose a lot of usable space. This very antiquated dev model is being replaced by cloud computing now, but there are still some clients out there that use very low density.

Moving to a single line item power pricing model is the way of the future in retail colocation. Just make sure to run your customer density requirements first to verify they need power beyond your own floor density.

No comments:

Post a Comment