Although previously vRealize Operations did a good job of reporting capacity remaining and forecasting time remaining, this was under the requirements that demand and/or supply were changing at a relatively steady and predictable rate. However, if sudden changes to supply or demand weren't counted, vRealize Operations would often readjust violently, throwing off the time remaining calculation completely for what could potentially be a one-off event.

An example of this would be the implementation of a large VM commissioning or migration project that may have added 100 VMs to a cluster on one day. vRealize Operations would then adjust the trend line to compensate for the dramatic growth, rather than analyzing if this growth was a common event.

Capacity trending has been greatly improved, with new algorithms that can detect major changes in the environment. The first time vRealize Operations observes a major change in the environment, it will assume that this is part of a cycle, and as such, the time remaining will not be affected. However, once vRealize Operations determines that this event was not a cyclical environment change, it will then be considered an offset, and the time remaining will be accurately updated accordingly.