Capacity

A 90-day capacity goal can describe three different things in VCF Operations: past demand used by the projection, future warning lead time, or the future period considered by VM rightsizing. They are controlled separately. This article replaces the earlier 90-day capacity procedure, which incorrectly treated Time Remaining thresholds as a historical lookback setting. The Three Meanings of 90 Days Planning question Relevant control What it does not control Should the forecast consider up to 90 days of past demand? Historical Data window, if that value is available in the installed build Alert severity or procurement lead time Should an alert become critical when exhaustion is projected within 90 days? Time Remaining criticality thresholds Historical lookback Should Recommended Size cover demand projected across a 90-day future horizon? The applicable Time Remaining warning/green threshold plus the documented 30-day extension Past-data retention Changing one row does not configure the other two. ...

Correction (August 25, 2026): This article previously treated a 90-day Time Remaining threshold as if it also configured 90 days of historical input. Those controls have different meanings. The original procedure has been retired so it cannot be followed accidentally. Use the corrected follow-up instead: Using a 90-Day Planning Horizon Correctly in VCF Operations The follow-up separates three independent goals: Alerting when capacity is projected to run out within a future planning period. Choosing how much historical demand the projection may consider. Setting the future horizon used for VM Recommended Size calculations. It also corrects the earlier maintenance-window advice. For capacity forecasting, use the product’s projection reset and time-range exclusion controls when you need to disregard anomalous history; do not assume that an alert-maintenance schedule is equivalent to a historical-data exclusion. ...