When the planner splits a task for one resource, how do you split the subsequent tasks to build them in drops.
The subsequent task has all of the split Tasks as Predecessors. (I.e., there are dependencies between each of the Split Tasks to the subsequent Task). That is why you can't bring the subsequent Task any further forward than the last of the split Tasks. The consultant team have wrote some custom SQL in stored prodcedure pr_SavePlan_Custom for another customer to split an entire order (i.e., split the Order into multiple Orders where each Order contains all the Tasks in the original order but in smaller quantities). But this customisation only works on Orchestrate being used as a standalone product. You import data from FactoryMaster (FM) to the plan and vice versa so cannot use the custom Save Plan stored procedure. FM won't recognise the new Orders and Tasks created in Orchestrate. Even manually splitting Tasks, Orchestrate is creating new Tasks that do not exist in FM.
E.g., Original Order Number 1234 has steps 10, 20, 30 each with qty of 200. They select the first step and enter 50,50,50 in an attribute to indicate that they want to split three new orders off the original order, each with a qty of 50. The custom Save Plan stored procedure would have created new Orders 1234_1, 1234_2, 1234_3 each with steps 10, 20, 30, each with Task qty of 50 and connected together with dependencies in the same way as steps in the original order. Also KPIs duplicated and reduced to the new quantities in the cloned orders.
Recommended solution is to use MRP parameters (e.g., Max Order Qty) if you use MRP in FM, or manually create multiple smaller Works Orders in FM in the first place. If there are stages in the Process where you need to do larger quantities in one go, you can always batch several of the smaller WOs together at those stages (i.e., plan all the Tasks for Product A together one after another on the same Resource - using Minimise Setup Resource Group planning rule, for example), and use Setup Table in Orchestrate to make sure that Orchestrate only adds one setup time at the beginning of each batch of Tasks of the same product.
Explanation of resource group planning rules | Orchestrate Help Centre