I'm not sure I understand exactly what you are looking for, but the SLOs in VMAX3 are the mechanism for controlling data placement. SLO uses FAST VP under the covers to make sure that SLO can deliver on the "promises". You don't need to define how much EFD you want dedicated to a certain workload. You just define that you want that workload to have a "Diamond" SLO and HyperMax will make sure the performance is there (in this case by putting the data on EFD). Each of the defined SLOs has some backend "affinity" settings that define what tiers are available and which ones are avoided. I still haven't seen an absolute answer on whether some of the SLOs will allow data placement in a tier that it doesn't have an "affinity" for but my suspicion is that the answer is "no".  Keep in mind that there is also the option to use the "Optimized" SLO which doesn't have any particular data placement rules beyond "Provide the best performance possible with the resources that aren't dedicated to delivering on specific SLO promises.  Not sure of that helps or if it makes things more cloudy. If you could better define your specific use case we might be able to answer you more clearly in terms that will make sense to your environment.
Hello ,         Can any one tell me how FAST data move is scheduled in VMAX 3 and how to view modify it ? looks like sympotz and symtw doesn't work with  SE 8.1 . If you have any white paper could please share with me ?  Thanks, Hareesh.
FAST schedule on VMAX3