Rules based releasing routing stages to operators

Rules like "the previous op needs to be complete / x quantity through". An example is where the last op is packaging. I don’t want my packaging operator to see all of the packaging operations planned. Only the ones that s/he can do, ie the previous operation is complete.

We see Build being perhaps the place to do this, not necessarily putting this into SAP's database, but can - similar to the SAP projects screen where they have dependencies. UDFs or just in Build - having a dependencies tab, where for each op you can list previous ops that have to be complete or at least 1 quantity done. As it might be that in a 10 op routing that op 8 can only be done if 6 and 4 are done, but 5 can be started straight away as can 1. but 10 relies on 9 which relies on 8. and 4 relies on 3 relies on 2 relies on 1:

I really like the drag and drop approach to setting routing up, so to do the dependencies in a similar way would be a bonus. but the functionality is more important than how its specified.

Then on the operators, you wouldn't see ops that you cannot do yet. only able to start them once the dependencies are complete (or started - perhaps a further option, two fields on the op rows - quantity dependencies and complete dependencies - ie once op 1 has done 1 op 2 can do 1 OR once op 1 is complete op 2 can start)