Modify Scheduler/Optimiser to support job/location based constraints e.g. security checks

Modify scheduler so that additional location/resource related constraints are checked when scheduling work.

Some locations will have location specific constraints that are not directly related to the work being undertaken but are general restrictions that are applied to anyone attending the site.

The scheduler should take these constraints into account when deciding if a job can be assigned to a resource.

This RFE proposes a new set of location based constraints that are applied.

This constraint would be added once to the location and would then be applied to any job that was created for that location with no further intervention from the users.
This constraint should be automatically applied to all child locations.

If the optimiser is being used to schedule jobs to engineers then it must also honour these constraints.

Where a client has a number of contracts for these estalishments there could be a lot of jobs every day that require this additional checks being requested.

The constraints being described are UK specific but Vetasi believe that other countries/organisations will apply similar constraints.

If an inappropriate person attended one of these sites then it could lead to severe embarrassment, significant financial loss or potential personel/corporate criminal prosecution in the event of the person behaving inappropriately.

It is possible to replicate some of this behaviour using other technologies e.g. specific response/job plans or specific work zones to include the restrictions.

There is potential for lots of response plans/job plans to be managed to ensure that the restriction is added in
• There is a significant danger that the restriction could be missed leading to the constraint not being applied
• Signficant additional costs in managing the additional plans/work zones