WMX provides the following LOI overlapping options as system settings:
- disallow by job type
In our shop we do not allow overlapping areas but there are special cases that require to work on jobs inside other job areas. The main job is mainly created to identify and define the overall LOI of the "mini-jobs" to be work inside that extent. Due to the nature of those jobs and to be able to work more efficiently they need to allow overlapping AOIs. So we like to have the option to allow overlapping areas by job type but allowing to overlap with other job types so we can still have the main extent delimited or somehow parent and child jobs be able to share an LOI. Right now we have the main LOI created in job type A and corresponding jobs (job type B) as child jobs but either skipping AOI creation (not desired but the application allows it, which is a big data security flaw) or creating AOI as they are available in the main extent (which delay our operations).