Independent schedules

Toggle the independence of schedules to form schedule hierarchies.

If you want to plan for a sub-assembly to be delivered at a time separate from its true need date, then you may want to drive demand for that sub-assembly using a dependent schedule. An example of this is that you are building a rocket and you want to build the second stage to inventory a few months in advance of when the rocket needs the second stage.

You can put this on the same plan as the top-level assembly or on a different plan. Our recommendation for this is to use plans as intelligent ways to group assemblies. If you want to ensure you see the sub-assembly results with the top-level assembly, we recommend you put this on the same plan. If you prefer to build the sub-assembly to stock and it should be organized separately, then you should put the sub-assembly on its own plan and still remove the independent flag.

There is now an Independent flag on schedules (plan inputs). This will always be turned on by default. When on, the schedule will drives its own demand. This means that Autoplan will create more demand for that specific plan. That demand will not be consumed by any other plan.

When it is turned off, the schedule is able to peg up to a different schedule. This can be on the same plan or a different one.

The mBOM for the above part (part A) looks like this:

If we were to schedule part C and turn off its independent flag, it can now get allocated up through the part A chain. A new plan has been created plan 11 with that setup.

Now, looking back at the results on Plan #10.

You can see that the schedule part C, Plan #11 has been allocated to the demand from part B. The date is set to 1/17/24 (from Plan #11). All demand below that part will drive from that date.