When importing assemblies into Orchestrate from FactoryMaster (FM), Orchestrate will allow you to plan the sub levels but will not plan the top level to start, once all sub-levels are completed and finish in time for the shipping date set in FM. It seems to ignore the sub-levels and plans the top level when it wants to and not as it should. This applies even when setting the manufacturing Lead Time in FM so the top level has one day manufacture time and a date one day different to all sub-levels.
Ideally it should plan the top level first and then plan the sub-levels so they all finish before the top level is due to commence.
Also, if you manually try to move the top level to where it should be, the plan moves all the lower levels at the same time.
When you close the first operation in FactoryMaster (FM), i.e. complete first operation line in the top level assembly works order, it looses the blue link.
So we have a sub level which needs to be tagged to another operation. As soon as we completed the first operation in the top level it loses the blue link.
You cannot link a lower level works order (sub-assembly) to an operation midway in the top assembly works order. For example, when you have a group of works orders with assembly components, you would expect the works orders of the assembly components too have a deadline date before the works order of the manufactured part when imported into Orchestrate:
10144.00 - MA part required date: 09/07/2020
10144.01 - assembly component required date: 08/07/2020
10144.02 - assembly component required date: 08/07/2020
10144.03- assembly component required date: 08/07/2020
10144.04- assembly component required date: 08/07/2020
10144.05- assembly component required date: 08/07/2020
10144.06- assembly component required date: 08/07/2020
Making a change in FM to a route for an assembly either at the top or lower level and then import this into Orchestrate seems to corrupt the assembly associations and plan each works order in the assembly as an individual assembly in its own right. Hence the top level is planned to complete before the lower levels. FactoryMaster development team do not do anything in FM to remove associations between works orders (unless possibly a works order is updated with a new assembly structure) so the issue is more likely to be with how Orchestrate import the data from the views. This is working as designed.