We have engineered several capabilities with various resources. That said for the foreseeable future, some of the resources assigned within broadly applied capabilities are tied up for specific use (so capacity still needs to be available, but we cannot have any production tied to it but the specific parts that are running indefinitely).
Is there a way to “inactivate” the resource within the capability so that it is essentially invisible to MRP or some other way to ensure that those resources’ capacities are not considered for anything else, WITHOUT having to re-engineer our capabilities entirely? It was quite the project to get the capabilities configured, and we’d prefer to not have to play with the set up of the capabilities themselves - just make certain resources invisible for a period of time.
Thank you EpiBrains!
What we did for resources, but they did not have capabilities, was to have a resource group with zero hours on the work week and then transferred the resources there so MRP would not see them.
If you already have a job scheduled on the resource, I would lock that job which in turn will lock the resource. MRP will just see that there is no time on the resource and will skip right over it. Handling that resource manually through the job would be the easiest way in my opinion.
You can set the priority on the resources in each capability group so those resources are not (or are very unlikely to be) selected by MRP. I believe the Scheduling Technical Reference has an example of this. The priority you’d need to use is something like 99999.