There are a great number of various data center computing models in play today. Some companies are building new data centers. Some are consolidating old. The use of Co-Location facilities is on rise, and so is modular. And don’t forget the Cloud for some applications. At the end of the day, work is being handled by any number of combinations of data centers, each with gear that needs to be actively managed. The choice of computing platform is usually selected based upon a set of business reasons (such as cost, security, performance, etc). For some reason there is a bit of confusion still about how and why Nlyte’s DCIM offering would be used across all of these styles. Well let me say with a definitive “YES” that Nlyte is the perfect complement to ALL of these styles, and in any combination of them. Let me explain…
Nlyte manages the lifecycle of physical assets for the purpose of capacity planning, resource management and cost containment. Our solution allows any type of physical asset to be described in great detail and in real-time in the context of everything around it, and then each of their lifecycles managed over long periods of time using business process workflows. Nlyte manages change in the physical layer. Nlyte scales to any number of racks, in any number of locations. Your equipment inside a Co-Lo or Modular structure looks like an “in-house” data center when it comes to managing change. Sure the processes are a bit different, but it can and SHOULD be managed pro-actively.
So in terms of data centers, every location counts as one. Have a traditional data center downstairs? It’s a data center. Have you deployed racks inside a Co-Lo? It’s a data center. Have some gear installed inside modular enclosures in your regions? Yup, they count too. You end up with a number of “data centers”, regardless of how they were constructed or financed. Nlyte is the right answer to manage ALL of your assets regardless of where they are installed.
The Nlyte solution fits anywhere there are racks of gear, and is usually acquired by the owners of that gear. In the case of in-house, co-lo and modular, the end-users are the owners of the gear. Sure it’s installed in various types of structures, and in various locations, but the hardware assets are still owned by the end-user. This defines the applicability of Nlyte. Nlyte works with hundreds of customers today that have a mix of in-house and co-lo and modular. For us it’s just standard business.
Perhaps the confusing part is the ‘cloud’. Again, think about who owns the gear. In the case of private clouds, the end-user still owns the gear and hence Nlyte is still a great fit and a perfect complement to in-house data centers. In that case of Public Clouds, Nlyte is still a perfect fit, the only difference being that it is the “Cloud providers” themselves that own the physical assets, so Nlyte is talking directly with many of those Public Cloud providers to show how Nlyte can manage THEIR physical assets. They still have the same issues that end-users do, just at a much larger scale. In fact, they are even more sensitive to asset lifecycles because the economics of that gear are directly related to the profit a Cloud provider can expect. In the Public Cloud business world, provisioning, decommissioning and/or refreshing gear quickly is the name of the game.
Regardless of computing style, Nlyte’s advance asset lifecycle management solution fits the bill!