Friday, December 7, 2012

We've Moved

We are now at our permanent home at http://coloadvisors.com/blog - come see our latest posts and what ColoAdvisors can do for your company.

Monday, November 26, 2012

Anatomy of a Cloud


Cloud certainly has become a catch-all phrase, seemingly describing everything from seemingly ubiquitous storage to computing on demand. "Put it in the cloud". I knew it was part of our vocabulary when my mother-in-law said it. In our business of selling services as well as the customers business of purchasing services, we need to understand what "the cloud" can offer, and more importantly, how it stacks up against traditional colocation and network services.

Let's start with some basic terms for the cloud - Public, Private, Hybrid. Public cloud is a service that is open to Internet where a service provider controls the infrastructure, yet the customer controls the provisioning of services. Private, or Enterprise cloud is a dedicated infrastructure for a single client. This still can be, and many times is, open to the Internet, but is a single customer solution. Hybrid describes a scenario where some customer infrastructure interfaces with either a public or private cloud solution, such as when a customer owns the web servers, but the provider owns the network and storage. This scenario generally happens when a customer already has colocation, but wants or needs to retain part of the infrastructure control. Many times Public cloud is described as a scenario where there is no monthly commit, whereas a Private and Hybrid solution has a longer term contract and commit. There is another term to learn when discussing cloud and that is virtualization. Think of virtualization as the ability to transform a computing system or environment, that was run on physical equipment, to a logical or software version of that same equipment or environment. Virtualization is still run on servers, but the servers may be provided by a service provider. Virtualization is a component of the cloud, but is not the cloud itself. We'll discuss this important distinction further on.

The cloud DOES live somewhere. Where does it live? It lives in datacenters and colocation facilities. This is confusing to many people as it sounds like the cloud does not remove you from the physical datacenter environment. Truth be known, this is exactly the case. A cloud provider has network, server, and storage components (and many others) that still reside in a datacenter or colocation. What a service provider is offering a customer is the ability to purchase and provision on demand, purchase in most any quantity, pay for what you use, provide hardware and software refreshes and updates, and provide any break-fix to the physical infrastructure. The exact details will depend on the type of cloud and the provider. The cloud DOES NOT alleviate the datacenter for the provider, but the goal is that it alleviates any burden of datacenter or colocation management from the customer. Amazon servers live in a datacenter. Rackspace servers live in a datacenter. QTS servers live in a datacenter. Hopefully they all live in multiple datacenters, but that will be another blog post. Do not sell or buy the cloud as a move away from the datacenter, but instead as value of not having to manage the infrastructure.

Cloud architectures are inherently redundant, when built correctly. The question becomes whether this redundancy extends beyond one datacenter location. Within a single datacenter a cloud provider will have multiple networks, multiple network equipment with automatic fail-over, multiple servers, redundancy within the servers, and a redundant form of storage. But what happens if the facility has an outage? That is the golden question, which leads us back to Disaster Recovery and Business Continuity, as we have previously discussed and will discuss specific to the cloud in a future blog post.

Let's get back to virtualization. Some providers offer what they call virtualization services, whether branded as cloud or not. Cloud by its nature allows the virtualization of network, systems, and storage. What you need to verify is whether the virtualization or cloud services have self provisioning. Many times, a provider will virtualize and existing computing environment and arrange for transfer of the virtual machines, but may not offer customers the ability to further provision on their own. As a seller, verify what your company offers. As a buyer, find out if self provisioning is a necessity.

These are just the basics. In the next post, we will speak more in-depth about maximizing the cloud.

Tuesday, November 20, 2012

Genesis of a Partner Ecosystem


It amazes me how much money is left on the table. When you think of a client's needs, they really extend very, very far beyond most company's services. Every customer has an intricate infrastructure consisting of IT functions in addition to web functions. IT functions can include voice services, office networks, desktop support, desktop virtualization, VPN/firwall services, and a host of other things not normally offered by colo providers. So why do you care? Simple, you want to make money.

A healthy partner ecosystem takes time and effort to develop  Having a pair of vendors for each potential customer requirement is a great place to start. Our modus operandi has been to start with what you know (and who you know). If you have a contact at another vendor that is reliable, start there. Grab your trusty Excel program and map out the services that vendor can provide. Not sure what you customer needs? Take a look at your own company needs for a start. You'll find your customer has similar infrastructure requirements. A good starting list may be:

Hardware
Network hardware - routers, switches, firewalls, load balancers
Server hardware
Desktop hardware
Office phones and switches
Network
Office to office (including partners)
Office to colo
Office to Internet
Colo to Internet
Managed Services
Managed Backup (or Backup-As-A-Services)
Managed Storage (or Storage-As-A-Services)
Managed network and equipment
Remote hands
Operations and IT support staff
Virtualization
Server virtualization
Desktop virtualization
Voice

That list is 2 minutes off the top of my head. There are many other areas where you can find needs. How many questions do you ask your customer about their business and technical needs beyond what you directly offer? If you are already pitching the customer for your own business solution, why not take a few minutes and discuss other areas where they may have needs or can make introductions? The money is there. The question is whether you will get it or someone else.

If your company does not currently have a partner ecosystem, you can still create one yourself. Just make sure you are not violating any company policy by receiving fees from the partners. If your company does have a partner ecosystem, it would behoove you to find out who is a partner and what they can provide rather than just waiting for them to funnel you leads. Need more convincing? This year a friend that is not in sales has already added over $110K to his salary just by pushing hardware and network (non-competing products for his company) to clients - all because he asked a few questions and knew where to direct the customer for answers.

Thursday, November 15, 2012

Wholesale Is Not Retail - Part 2

In Part 1 of this thread we discussed the general differences of Wholesale and Retail and how the lines have been blurred by the providers and customer expectations. In this second part we will discuss the main business ramifications of selling metered power in a retail environment.

The general components of a wholesale deal are comprised of space, power, and cooling. Some providers will separate space to multiple components including the physical computing environment as well as CAM, or Common Area Maintenance charges. For our discussion, we will limit this to the former, but as a buyer, just add these charges together if you are comparing service offerings. Floor space is represented as per Kilowatt charges. This is counter intuitive to many as Kilowatt is an electrical term, but is used to price the floor space or rent component. The reason for this is very simple. Metered power is a pass through charge to the customer and NOT a profit center for the provider. The provider will use the committed amount of power to first determine the size of the footprint, as per our discussion of watts-per-square-foot, and will then use the committed power with their own pricing structure and market rates to determine if the deal is profitable. Remember, you are really only selling space, as a landlord, at this point. Power is paid through you to the electrical company. The third component, cooling, is represented as a PUE charge. PUE is an ever changing number from the point of commissioning of a building and fluctuates based on fill rate, temperatures, etc. In terms of contract negotiation, it is usually a fixed number that describes the price a customer will pay for cooling of the power consumed. If the PUE is 1.5 for the wholesale location, the customer will pay the electrical bill and .5 times the electrical bill for cooling of the electrical. The major debate is whether PUE and cooling charges can be considered a profit center to the provider. Remember, the customer is paying for actual power consumed and therefore the PUE charge is a real cost the provider, which means there is little to no margin and may actually be a loss if the contracted PUE is lower than the actual PUE of the facility.

We can clearly see of the three charges to the customer - floor space, power, and cooling - that floor space is the only charge that carries any potential for margin. There are other variables that will affect cost to the provider and price to the customer, such as the point where power is measured, as well as "break points" of how much power can be offered before the provider must spend to build additional infrastructure, but I think you can clearly see that in wholesale, you are a landlord that is really selling space only. This explains the lean staffing and massive footprints of many wholesale providers.

Let's juxtapose this to a retail environment. In a retail environment  the request for metered power is becoming more prevalent. Minimum power commitments are going as low as 150kW to switch "per breaker" pricing to metered power pricing. Let's look at pricing in such a scenario:

Retail customer XYZ Corp has agreed to 150kW of power in a retail environment, consisting of 30 pairs of 208v-30A circuits, totally 149,760 watts of power. Let's do the math in the old model of per circuit pricing and per square foot floor space pricing. Assuming per circuit pricing is $650 per primary circuit and $300 per redundant circuit, this equates to (30 * $650) + (30 * $300) = $28,500. If floor space is $20/sq ft with a facility power density of 150w/sq ft, this equates to 149,760 / 150 = 998.4, which we will round up to 1,000 sq ft @ $20/sq ft = $20,000. This deal is therefore worth $48,500. Now, a retail environment that only uses a price per kW charge all inclusive @ $300 would equate to 150kW x $300 = $45,000. There is a caveat. *Most* of the time, a savvy buyer will just compare total price, regardless of how you calculate it, so if provider B is quoting $45,000, provider A @ $48,500 obviously needs to explain the pricing delta with a proposed superior offering. In either scenario, the sales rep will most likely be paid on the total deal value, whether it is $48,500 or $45,000. In a wholesale model for the same 150kW, the price may be $150 per kW for the floor space, or $22,500. The power is a pass-through to the client, but let's assume 150 kW @ 12.5 cents/kWh for the 730.484 hours in a month, or (150 * $0.125 * 730.484) = $13,695.64. The PUE cooling charge, assuming full power draw against commit, with a 1.5 PUE facility would be 1.5 * $13,695.6375 = $20,543.46 for a total deal value of $22,500. Wait, you say the math doesn't add up? Remember, the only thing pre-billed each month is the space of $22,500. Power and cooling are post-billed after usage and most likely you will not be paid on either.

So, let's do some simple math. Commission on $48,500 is better than commission on $22,500. Now you see what offering metered power in a retail environment will do to your margins and your commissions.

Tuesday, November 13, 2012

Wholesale Is Not Retail


The terms wholesale and retail have been kicked around the datacenter industry for quite a while now. There used to be a very clear delineation of service, as well as type of customer purchasing the service. Wholesale was large swaths of space and a set amount of power, usually sized by the service demarcation point of the power distribution equipment, along with metered power and lease terms that resembled a real estate transaction. Retail was generally smaller space with set power circuit types, such as 120v-20A or 208v-30A designated by a circuit or whip delivered to a customer environment, as well as a more bundled approach to contracted services. What we have seen in the last few years is a blurring of the lines and a distinct lack of definition of product. Let's take a look at the general differences and why selling to an improperly categorized client can be bad for your company.

Historically, wholesale environments for any product were designed to allow a producer or distributor to sell in bulk to bulk purchasers that, in turn, would resell the services to consumers. This held true for most industries, whether it be groceries or automobiles, etc. The price of the goods was lower, as the bulk buying allowed more goods to be sold at a time, but in turn the level of service received was much lower as the bulk purchaser would be providing any services needed to the consumer. In our grocery analogy, this means the farmers or large scale producers would sell to grocery stores and the grocery store would provide all the services for the consumer, such as cleaning, preparing, staging, pricing of the goods as well as the end checkout, bagging, and other infrastructure. The combination of lower volume purchases by the consumer as well as services provided by the grocer allowed the grocer to add margin into their pricing. The grocer had created a retail offering from their wholesale purchases.

Our industry worked the same way. Datacenters were built by real estate companies (landlords) with large expanses of space and power leased to providers that in turn would de-aggregate the space, power, and cooling and would provide a lower volume product with additional services added to the consumer. And everyone was happy for a while. So what has changed? The biggest change is in the understanding. Nowadays, the wholesale and retail model has been modified as wholesale sellers have started offering retail services directly to the consumer, necessitating the retail supplier to offer wholesale services to compete, effectively adding market competition and squeezing margin, while in many cases not providing a high level of service. Consumers now think of wholesale as a pricing methodology without understanding the service component. Retail providers have been forced to offer wholesale attributes to retail clients, most notably in the form of metered power instead of per circuit pricing.

Why is this bad? Most wholesale datacenter providers have smaller staffs as they are geared toward fewer, but larger clients. For the wholesale datacenter provider, this may mean overworking the staff to accommodate requests normally handled by the retail providers, such as individual circuit installations, cage, cabinet, and suite installations, and fielding questions about services not traditionally offered by wholesale providers. For the consumer, this usually means a much lower support capability, longer lead times, fewer service choices, and a host of related issues. And what about for the retail provider. They are getting the worst of it - increased competition from dissimilar offerings that "look" similar as well as severely eroded margins.

The blurring of these lines will continue. In our next post we'll specifically discuss metered vs. circuit power and what some providers have done to protect erosion in this changing market.

Friday, November 9, 2012

Buyers Don't Purchase On Price


In a meeting with a colocation prospect, he made a point of telling me that "price is all that matters". He emphasized this several more times within the first 5 minutes of the conversation. After finding out his current colocation spend I confidently informed him one of our partners could cut his price by 50%. He was quite happy. I then told him we would stack his equipment in the parking lot behind their building and run an extension cord from a wall outlet the janitorial service normally used for their vacuum cleaner. His expression changed and the meeting almost ended. Slowly he told me he wanted the best price for a "comparable solution" to his current environment. This quickly led to a discussion about the real problems he was facing with his current provider, the challenges he faced in his own operation of the environment, and the concerns about how to handle growth. Once we moved price out of the way, we were able to find the real issues and address each, leading back to an honest deal.

Time and time again we are caught up in this frenzy that a customer buys on price and we sell on price. Do you buy your cars on price only? If so, I know of a 1988 Yugo GV for sale. Or what about your clothes? A 1977 sky blue leisure suit is pretty cheap these days. We do not buy "the cheapest" for the sake of it being "the cheapest" for most of our purchases, so why do we try to sell that way to a customer? The reasons are plentiful, but the one that I continually see is perceived lack of differentiation. If you truly believe your product is a commodity and there is no value proposition, then you need to better understand your company market positioning. "Niche to win" is a common saying among start-ups, but it also holds true for infrastructure. You can create many niche stories to better position your product to the customer. If you do not know your company niches, I strongly suggest spending time with your product and marketing teams. I've not seen a single colocation company where there is not a niche story that positions the product set specific to a market vertical. Even if your solution is identical between one market vertical and another, there is no reason you cannot determine the customer problems solved by your product and why it is right for both verticals.

I use food analogies a lot. Infrastructure is like Mexican food - 7 ingredients arranged 29 different ways. What is the difference between a taco and a tostada? Not much. Your product and customer vertical positioning can be the same - same ingredients arranged in a way specific to the market vertical. Need more? Start off with "Our product is perfect for the medical industry because of ..." and then try "our product is perfect for the banking industry because of ...". The reasons might be similar, but now you have two distinct stories for two verticals. Easy, right?

Wednesday, November 7, 2012

Disaster Recovery Fundamentals


Now that we have defined DR in our last post, let's look at some of the options for creating a DR plan for your business or your customer.

In a disaster situation, both the users AND the data need to be shifted from one computing environment to another. This effectively means there are two DR plans that need to be enacted simultaneously. If you are only providing colocation to the client, then your only role is really to keep the facility from having an outage in the first place. Even with that limited role, it is still very important to speak to your customers about their own DR plans. At a minimum, it shows the customer you care about their business. And perhaps, you can also provide them white label or partner services that are of value to you and your company, as well as your partner ecosystem. Where things get complicated is if your company provides *some* level of managed services, but may not be responsible for the entire computing environment, including network or application. In such scenarios, your company is now part of the customer Operations team and will need to know exactly which services to provide in a DR situation and in which order, as well the triggers that put them in motion and their own feedback loop to the client when their portion of the work is complete. Yes, you are in the middle of a potential panicked situation. The last scenario, and least likely, is that your company provide full Operations support for the customer and owns the entire computing environment, as well as DR plan. This is least likely as the customer almost always owns at least the application and potentially the users, if they are corporate users and not Internet users.

The first half of our solution involves shifting users from one computing environment to another. Shifting Internet users is trivial now thanks to geoloadbalancing technologies that have matured in the last 15 years. In simple terms, this means there are two potential computing environments for the Internet user. The geoloadbalancing system will determine if one environment is available and the other is not available. It will then send Internet users to the available environment. Of course, there are a lot of bells and whistles that will allow tuning based on geography, network latency, computing environment load, and many other factors if both environments are available, but again, that is more of a Business Continuity scenario. For DR, let's just think of it as a light switch where an environment is ON or OFF, with only one environment being ON at a time and Internet users directed to that ON environment. Managed Services and network companies should be selling this capability. The second user scenario involves corporate or VPN users. Remote corporate users many times use VPN clients as a way to connect to a computing environment, usually for access to corporate file servers or email. The good news is that a VPN client can easily accommodate connections to differing computing environments, many times with the ability to automatically try secondary connections if the primary connection fails. This is called "rollever" and just means if computing environment A is not reachable, the VPN client will automatically try to connect to computing environment B. From an infrastructure standpoint, this simply means both computing environment A and computing environment B must have the ability to allow the corporate user VPN connection and to authenticate it. Simple tasks for your IT department. The scenario of an office connecting to the computing environment is very much the same as the VPN user. The only difference is that instead of a VPN client for each user, the office will have one large VPN tunnel that serves all users. In the case computing environment A is not avialable, the router or other VPN device will automatically "rollover" to computing environment B. In reality, the VPN device is continuously trying to connect to both environments and will just use the one that is available.

And now the real work - shifting data from one environment to another. It would be so nice if real time synchronous replication worked perfectly and was cheap, but this is just not the case. The engineers can explain the problems with trying to synchronize data between multiple environments, but from a business perspective, this just means about twice the cost of operation to keep mirrored environments available - twice the hardware, twice the space, twice the power, and maybe if you are lucky, you only have to pay network at one location. Synchronous replication is also more of a Business Continuity plan, so again, let's keep this as DR and the light switch - ON and OFF. In reality, if computing environment B is a physical coloction, the customer will always have the servers on and ready and maybe just not have data replicated. In such a scenario, the DR strategy for the data will be to move it from one location to another. This is usually done with block level replication, meaning chunks of data are transferred. The problem comes with just how much data is to be transferred and how fast it needs to be there. Remember, if computing environment A is down completely, a customer may not have any access to that data. Then how do we do it? By continuously replicating the data to another location. This is known as Storage-As-A-Service or Backup-As-A-Service when using a 3rd party. This is just replication if a client is using their own infrastructure. The data continuously gets backed up, then in a DR situation, is transferred again to computing environment B from the data backup location. Again, this has to be architected based on the amount of data and the time a customer must have it replicated to have computing environment B available. This is your SLA.

Virtualization to the rescue. There are a number of cloud service providers that will allow virtual machines to remain dormant (OFF) and provide a guarantee of how long it will take to turn on each virtual machine. This would be computing environment B. A customer may be able to only pay for storage without colocation or machines and then pay for computing cycles when the virtual machines are powered ON. Think of it - 1,000 virtual machines turning on in less than a minute. We still have the issue of getting the data to the virtual machine, but the customer now can save a massive amount of money for that secondary computing environment. Does your company offer this service? If not, you really should be looking to partner as a cohesive DR plan presented to a client is going to be of more value.

While these are just the basics of DR, hopefully it will provide you with more of an understanding and way to speak with your customer, as well as ideas for partnering in your ecosystem.

Monday, November 5, 2012

Disaster Recovery vs Business Continuity


For many, these terms are synonymous. Is there a difference and does it matter?

The term Disaster Recovery (DR) is as simple a concept as it sounds - how do we recover from a disaster? The problem is there are many methods of DR, each targeting an aspect of a company's overall architecture, from physical or virtual presence  to network, to data, to user experience. It might help if we start with a baseline understanding of what constitutes a disaster. It is widely accepted that disaster in DR means a full, total, and complete outage of a computing environment. For most, this means the facility no longer has the ability to support services of any kind. This is an important distinction because a localized disaster to a single customer computing environment may be corrected with much less effort, which really becomes part of our Business Continuity plan - for example, we utilize redundant power circuits to ensure in the event of a localized power issue affecting one circuit, the computing environment will still be functional utilizing the second power circuit. Business Continuity describes the design consideration as well as functions we perform on a regular basis to ensure a computing environment is accessible.

Confused? Don't be, it is really a simple distinction. DR means there will be downtime from the moment a computing environment becomes unavailable to the time it takes to shift that environment to another computing environment that will take over primary computing duties. Business Continuity means enabling one or more computing environments to continually perform. We put DR strategies into effect for the purpose of shifting an entire computing environment during an outage. We put Business Continuity strategies into effect for the purposes of maintaining some or all operations even during an outage.

The actual solution for either DR or Business Continuity will be tailored to a specific customer, with business and technical requirements driving the architecture and operations. When in discussions with clients, just think of DR as how to get back up after an outage and Business Continuity as how to always stay up and avoid an outage. As you can now imagine, Business Continuity is more extensive planning and usually more expensive in operational cost, but may be appropriate for clients that cannot accept any downtime.

Friday, November 2, 2012

Preparing For Disaster - Site Selection


Hurricane Sandy brings many DR concerns back to the forefront. I've spoken to clients that utilize both East and West coast datacenters to ask about their methodology when choosing each location to mitigate the possibility of outages due to disaster. A series of questions emerged for the initial site selection process:

1) Minimum 1 mile from interstate.
2) Minimum ½ mile from major rail. Commuter rail is less of concern.
3) Not in flight paths AND two miles from major airports and one mile from regional airports.
4) Minimum 500 year flood plain.
5) Note location and capacity of levy or aqueduct system.
6) Surrounding Properties or other tenants may not handle or store any hazardous material, such as gas stations, propane refilling stations, hazardous material storage.
7) Minimum 50 miles from nuclear power plants.
8) Not adjacent to water or communication towers.
9) Minimum ½ mile from major fuel pipelines.
10) Minimum ½ mile from grain elevators.
11) Proximity to fault lines.
12) Emergency Services – (fire, police, and ambulance).

The obvious question is where does one get answers? Let's step through one at a time with the reason for the question and places to get answers.

1) Interstate proximity - The interstate itself obviously doesn't pose a problem as roadways usually do not experience spontaneous combustion. The real danger is in overland freight, namely fuel and dangerous chemicals. The odd thing about this requirement is that you really want a major interstate or freeway close enough to the location so you know there is an ample transportation artery in case you need to get the facility in a hurry, but you don't want it so close to where an explosion or chemical hazard can cause a problem. The Internet mapping sites (Bing Maps, Google Maps, MapQuest, Yahoo! Maps) will show location and a scale, but do not measure distance. This is probably acceptable for most applications with just a screen shot for proof, but if you want more accuracy, use Google Earth. You can plot the colo address and then use the ruler tool to show much more accurate distance "as the crow flies", rather than driving distance which is less accurate.

2) Rail proximity - Major rail means freight rail and has the same concerns as overland freight. In addition, trains tend to weigh a whole lot more than cars, so the idea of a facility with an adjacent track is not too appealing in case of derailment. Again, the easiest methods to find rail information will be to use an Internet map to locate the rail and then Google Earth to verify proximity. But wait, there are many other ways that are more accurate. BNSF and CSX are two of the major rail companies in the US. There are many sites that will give you "system" maps with a general overview, but for specific information, you can contact the company real estate department and obtain detailed maps. If you are not sure of the rail company that operates the rail lines close to you, you can always get track ID or crossing information at most railroad crossings and give those numbers to the rail operator to verify you receive the correct maps.

3) Flight paths - Avoiding the major airline flights paths is for obvious reasons. While such disasters are extremely uncommon, the size, weight, and speed of the plane is only compounded by the avaiation fuel aboard. I'm fortunate to have many pilot friends that are happy to share information. Two excellent resources are VFRMAP and FlightAware. An example for the city of Austin would be to check VFRMAP: (http://vfrmap.com/?type=vfrc&lat=30.195&lon=-97.670&zoom=10), noticing the light blue line with "V xxx" that shows typical airplane routing, then verifying the routes against previously recording flights in FlightAware (http://flightaware.com/live/airport/KAUS). The first few times are duanting with the level of information on each map, but you will get the hang of it. Just a note, the main page of VFRMAP is actually the map. Zoom out on the upper left corner and move the map to your region, then zoom in to the airports. Another pilot friend points out that approach and takeoff procedures for all airports are available via AirNav (http://www.airnav.com/). This will show the acceptable routes in and out. He also brings up an interesting statement in that airplanes do not crash on the actual flight path, they crash on deviations to the flight path. In his humble opinion, the safest place to be is in the actual direct flight path. Food for thought?

4) Flood plain - Electricity and water do not mix well. Whether you believe the flood plain number should be 100 year, 200 year, or 500 year, the research is the same. FEMA provides flood plain maps available for download on the main site. Each map is inexpensive, at usually just a few dollars. Search for your state, then county, then community. You can view each map ahead of time to verify you are purchasing the correct location. The URL for the FEMA flood maps is https://msc.fema.gov/webapp/wcs/stores/servlet/CategoryDisplay?catalogId=10001&storeId=10001&categoryId=12001&langId=-1&userType=G&type=1&future=false

5) Levy system - Electricity and water still do not mix well. Levy and aqueduct infrastructure is sometimes locally supported and sometimes state supported. You can note the location and distance of each system using the same methods as the interstate or rail lines above. Regarding any city plans for reinforcement, etc., your best bet is to search the city websites for "flood" information. Some cities, such as Santa Clara, CA, provide quite a bit of information directly on their site. With other cities you may need to call the city offices to obtain any project information.

6) Hazardous storage - Most Internet mapping systems will allow you to zoom down to street level and will give you the business entity name at surrounding properties. The easiest thing to do is print out a few maps, then drive around and see for yourself what is close to your property. The concerns with hazardous material storage are obvious, and, as most facilities are in industrial parks, businesses such as gas stations are not as much of an issue.

7) Nuclear power - Thankfully, US nuclear power plants are built to an amazing structural integrity level. Whether you believe in the likelihood of a power plant threat, either natural or man made, is not the issue. We are discussing risk mitigation, which means we might as well add large scale hydro as well as coal facilities to this concern. Internet search is your friend. Wikipedia gives you a nice list of power plants (http://en.wikipedia.org/wiki/List_of_nuclear_reactors) that you can plot, then using Google Earth, measure the distance to your facility as the crow flies. Do the same for dams and reservoirs (http://en.wikipedia.org/wiki/List_of_dams_and_reservoirs_in_the_United_States), coal power stations (http://en.wikipedia.org/wiki/List_of_coal_power_stations) and any other power generation that may be of interest.

8) Communication towers - Companies like American Tower own a massive amount of the communication towers in the US. Luckily, they make their tower locations available to the public (http://www.americantower.com/sitelocator/default.aspx). Unfortunately, they are not the only provider. It appears that most customers are not worried about a small rooftop cell site nearly as much as a major tower. You can spot most major towers in rural areas using Internet mapping, but in business or CBD areas, it is more difficult as they are usually not stand alone. For this purpose, I usually rely on detective work or assessing the datacenter area for several blocks in all directions, then crossing that information with Internet search and tower search. It is not foolproof  but will get you in the ballpark. Water towers are up high. Look for them on tops of hills or free standing on huge legs. Either can be seen in aerial maps.

9) Pipelines - Gas pipelines usually refers to natural gas. Again, the Internet is your friend (http://en.wikipedia.org/wiki/List_of_natural_gas_pipelines). Pipeline maps are also available from most local power providers, such as this zoomable map from PG&E (http://www.pge.com/pipelineplanning/). If you cannot find a local provider pipeline map, just call into their HQ and request one. Most likely it is already available, but the nice person there can direct you. Gasoline pipelines are often only located within the refinery property. The next step would be to identify refineries in your area. Again, thank you Internet (http://en.wikipedia.org/wiki/List_of_oil_refineries). Verify property relative size and location using Internet mapping and Google Earth.

10) Grain elevators? Seriously? Yes, to many in the Midwest and east coast, this is truly a risk. I'd never seen one explode, but after viewing a few videos, I understand the risk. First of all, if you are in an industrial park in a major city, there is almost no chance of a close grain elevator. If your facility is rural, then you need to do some checking. Again, the Internet gives us a start (http://en.wikipedia.org/wiki/List_of_grain_elevators), but seems very incomplete. When asked for this info, I cross a few Internet searches with the good old phone book to look up grain companies. Most purchased grain and distributed it, but I was able to ask each where the major grain elevators were located in their area. Not 100% complete, but with enough phone calls and overlapping source information for an area, it was good enough in the eyes of each client.

11) Fault lines and earthquakes - There is a great faultline at Lawrence and 101, but that is the Faultline Brewery and probably not what the customer is asking. Here, in earthquake country, there are several fault lines that are active from time to time. There are many others in the US, but CA seems to have the stigma due to proximity to the tectonic plates. The USGS provides fault and earthquake maps for all regions. Just go to USGS (http://www.usgs.gov/) and search for fault line or earthquake and you can see the regional and national results along with maps.

12) Emergency services - Look up emergency services in your local phone book. Additionally, each state should list red cross and other shelter location for each of their counties, such as this map of shelters for the State of Florida (http://floridadisaster.org/shelters/).

Good luck in assembling your quick list of answers. Contact me if you require help as I am happy to consult to deliver a risk mitigation info packet for your location.

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.

Tuesday, October 30, 2012

All Colo Is Not Created Equal

Time and Time again I hear, "colocation is a commodity". This would imply all service offerings along with all the components that make up each service offering were identical. And this simply isn't the case.

Many are familiar with The Uptime Institute and their data center tier rating where data centers are rated from a Tier I (least redundant) to Tier IV (most redundant, least downtime). The rating system does not allow 1/4, 1/3, or 1/2 points, so many times when we hear of a Tier III facility, it is really Tier II by definition, but the provider feels it warrants a higher rating for various reasons. This question of tier rating is one of the arguments I hear most often between customer and provider or provider to provider comparisons. But does it matter? It most definitely matters in terms of defining our data center and colocation world, but what I mean is 'does it matter to the customer'?

The only way any service offering and comparison of offerings matters to the customer is if the customer has a firm grasp of what they require. This means internal audits of their own infrastructure, project growth, technology changes (such as physical to virtual environments), M&A activity, DR strategy, proximity and more. This is the crux of the issue and will determine why data center tiers and the different colocation offerings will become apparent and will matter. If the customer does not know this information, the Sales team should be able to probe and probably arrange their offering to suit.

 Let's assume there is no such thing as a "good" colo or a "bad" colo. If the customer understands their own requirements, there will just be offerings that are less than what is needed, offerings that are appropriate for what is needed, and offerings that are more than what is needed. Now we can quickly look at those same data center tier ratings and understand how they can help compile a short list of possible providers. We can also, without prejudice, understand that a Tier I facility does not mean it is a "bad" facility, but may mean it is more suited toward lab, dev, or SMB markets and a Tier IV facility does not mean it is a "good" facility, but might mean it is more suited toward big dollar mission critical infrastructure that can bear the expense of the added redundancies.

Within each tier there are many design and aesthetic variables due to building age, data center "generation", as well as more practical components such as power and cooling designs and rack/cabinet/cage layout. A note to the customer - verify all infrastructure and service offerings before you worry about aesthetics. A note to the provider - the customer is initially only going to worry about aesthetics ;)

Monday, October 29, 2012

Datacenter vs Colocation

I hear a lot of clients, as well as providers, use the words datacenter (or data center, or even data centre for our UK friends) interchangeably with the word colocation (co-location/colo). What is the difference or is there one?

The simplest way to think of a datacenter is to think of the actual building structure. This comprises the foundation, walls, roof, and all the core components that give it life, such as power, cooling, and fire suppression. It also comprises common areas, work areas, the restrooms, offices, entry way, etc. Colocation is merely the room within the datacenter where you locate your equipment. These rooms will have sub-systems or extensions of the core power, cooling, and fire suppression, but the main or core components are really still part of the building. Think of the datacenter as your house and the colocation is just one of the rooms. Simple, isn't it?



This is very straight forward for multi-tenant datacenter (MTDC) environments as there is a single service provider/operator and many customers, each with colocation within the building. Where things get more tricky is when you have an Enterprise datacenter. Many times the Enterprise will own or run the building, as well as utilize space within the building for their compute equipment. At this point, it would seem the datacenter is the colo, but in effect, the same rules apply. The building itself is the datacenter and the equipment room within the building is the colo. Remember, the datacenter itself is comprised of all the ancillary systems and rooms in addition to the equipment room, even if that equipment room is the majority of the total facility.

But what about REIT infrastructures such as 200 Paul in San Francisco or 300 Blvd East in Weehawken? Both buildings provide wholesale offerings to their clients, who in turn provide services to their own clients? This creates a nested solution where the landlord owns the building and the tenants lease from the landlord and sublease to their own clients. The same logic applies as before. The building itself is the datacenter and each room/suite/pod within the building is still colocation. It just happens that provider colocation is split again into colocation for their clients in terms of suite, cage, and cabinet offerings. Think of that same house. All we have done is allowed different rooms to become colocation provider specific, while they lease space in that room to their clients.



This is review for many, but will give us a common building block for our future blogs.

Monday, June 18, 2012

Who am I?

Just a quick intro . I'll be posting about datacenter, network, cloud computing, managed services, and application environments, so probably a good idea to tell you a bit about myself first.

Way back in 1988 I fell into hi-tech through a friend that was a receptionist with Cabletron Systems. They needed a field tech for LAN installations and since my step-father worked in the semi-conductor industry, that made me qualified, right? Luckily it turned out to be pulling cable at the start with only a need for a strong back and the ability to follow directions. Cabletron had a series of products with the MMAC concentrator at the top of the line. Lots of questions asked and I was soon allowed to jump into the console and start configuring them, getting me hooked on networking.

In the early 90's I moved back to SoCal and started working for another cabling/LAN/WAN company called Digital Networks. No, not DEC, but a smaller company with great customers like 3M. Back to punching cable, splicing fiber, installing switches and these crazy WAN communication products called stat-muxes. My LAN training turned into WAN training and with a whopping 56Kbps tie line between locations, I was in network heaven.

By 1994 my landlord in Balboa informed me a wrecking ball was hitting my bachelor pad (above a garage) and I had 30 days to move. I called a recruiter that had an opening at this company called MFS Datanet in San Jose. I headed back up north and took the interview. Luckily, I had been reading networking magazines the week before and was the only candidate that answered properly when asked, "What is ATM"? Apparently everyone else thought it was where you received money. MFS Datanet was the epicenter. MAE East and MAE West were the start of the commercial Internet NAP plays and even as a NOC monkey, I was in the middle of the action. 70 hour weeks and a ton of studying led to Engineering and R&D stints.

In 1996 a mentor moved on to a company called ISI, which was started by one of the lesser known co-founders of Netscape. This is back when Yahoo! had 30 employees and Filo would answer my emails directly :) ISI was the genesis of colocation as we know it today. Early customers included Netscape, Yahoo!, Playboy and a host of web 1.0 heavy hitters (and a few strikeouts). I was a backbone engineer, but wanted to learn more about business. After being engulfed by Global Center, I made the move to Sales Engineering. Global Center was bought by Frontier who was swallowed by Global Crossing. By this time I was in Sales.

1999 rolled around, just as Prince predicted, and a group from Global Center and a group from Digex formed a new managed services company called SiteSmith. Talk about fast moving. SiteSmith was more 70+ hour work weeks and a complete blast, staying at the forefront of managed service offerings. The company was acquired in 2001 by AboveNet Communications, where I stayed in various Sales and Sales Engineering management roles until 2007.

The next 3 years was spent with United Layer and XO Communications. Datacenter, network, managed services - true to form and the core of what I do.

In 2010 I moved to QTS Datacenters to assemble and run their national SE organization as well as assist with Product Development and Marketing functions. If you have never seen a 1.3M sq ft datacenter, it is truly epic in proportion. And if that is not enough, they also have a 1M sq ft facility under 1 roof for a kicker. QTS provides a wide range of products, incorporating all my specialties of datacenter, network, cloud computing, and managed services.

I left QTS in 2012 and am now consulting at an executive level to datacenters and private equity firms regarding market expansion, M&A, and product placement/development. If you have a question of how your company can make money in any of these areas, I am sure I have an answer.