Working Space Repository

I would go by what the calculator says as they take in to account everything you input to calculate this.  Working space is usually the sum I believe not the largest as it would depend how many jobs are running and using the same repository.

Hi ​@Chris.Childerhose , I think that if we consider the sum of all loads, we may have some stranded capacity. I believe that depending how big the  stranded capacity is, it will not be a big problem, but in some cases, it may become a problem. The colateral effects that I see in considering a very large stranded capacity are:
a) the type of hardware to be used may have to be much larger than necessary, increasing the cost of the project.
b) we will give room for the competition to create some kind of FUD during a negotiation phase with the customer. 
I searched on BP and found the excerpt below, but in this excerpt that talks about calculating the Repo, it does not mention whether or not we should consider the sum of all workloads or the largest workload found to be used as working space (as we use to have this inforamtion for VMCA v11 class).

https://bp.veeam.com/vbr/2_Design_Structures/D_Veeam_Components/D_backup_repositories/repositories%20storage.html#estimating-repository-capacity 

Assuming we have the sum of all workloads for an environment with 5 types of workloads 1PB the front end ea, we would have a total of 500TB destined for working space, on the other hand, if we consider the largest of them, we would have 100TB

here is the size of the Working Space are. for 1PB FE, 20% YoY Growth, 3y forecast to get the working space size.

Thank you Chris!!!