In our use case we typically require a "lead" and a "mate/hand" to join on certain incident types.
It's my understanding requirement groups associated to the incident type would be a good solution.
When reviewing the documentation
https://learn.microsoft.com/en-us/dynamics365/field-service/multi-resource-scheduling-requirement-groups it appears we can set a characteristics and categories to help narrow down who should attend.
We have utilized characteristics and a proficiency model such as:
Characteristic: Electrical
Proficiency: Lead, Qualified, Hand, Mate
We have some resources with electrical - lead and some with electrical - mate.
I can't see how we would utilize the proficiency level in the resource categories, it looks as though we can only select the high level characteristic of Electrical.
Should we be using groups rather than proficiency models to split leads/qualified etc.?