A brief note to explain what Ravello's tool is, what it isn't, and several case studies to illustrate how it produces continuously optimal inventory levels that reduce total costs.

 

What Ravello is:

a compute inventory simulator to evolve inventory positions, resource consumpton, and costs of a pool of servers over a period of time,
a dynamical system-based solver to accurately account for and calculate time and sequence dependent factors, events (e.g., changes to server configurations, software license terms, etc.), and transactions that affect the composition of a pool of servers over time,
a real-time inventory optimizer to find the least-cost way to add capacity by dynamically adjusting when and what rates to add and remove servers from a pool without assuming a fixed-time server refresh schedule (e.g., every 3-years), and
an inventory and cost forecaster for deep, forward-looking insight into key financials, inventory balances and turnover rates for servers/processors/cores, power consumption, and software license and subscription counts by SKU and publisher.

What Ravello is not — yet empowers:

a configuration management tool — but it does enable planners to model configuration changes and their impact on future inventory levels and costs,
a workload placement tool to better use today’s capacity — but it does ensure the inventory that is available for improved utilization is always the ideal composition that achieves the lowest total cost,
SAM software — but it does identify the optimally lowest quantity of required licenses or subscriptions over a contract term without assuming server refresh needs to occur on a fixed-time scheduled,
a TCO calculator —  umm... did we fail to mention how Ravello dynamically solves when and at what rate to optimally refresh servers in real-time without assuming a fixed refresh cycle time?  (Try modeling that with a TCO calculator!) ... or
a TBM application — but it does enable finance, procurement and infrastructure planners to cross-functionally plan and optimize the IT supply-chain to radically reduce future commitments and expenditures in power, datacenter space, and software licenses and subscriptions.

 


 

 
 

Case Study: Resizing a database service

This client's service growth rate for one of their database services has been running well-below the annual rate of server performance improvement.  They are investigating how to shrink their cost structure by substantially reducing perpetual licenses without triggering license repurchases down the road.

Case Study: Reducing software over-provisioning

The client is a technical services company providing transaction processing services to global customers. The client's core transaction processing services utilize a software stack that includes a high level of subscription licensing and are looking for opportunities to reduce those costs as they implement an updated infrastructure.