Hi Dogboy 49,
Let me give you a clear picture what the scenario is
FG has four operations OP2,OP6,OP10 and OP20.
"Required overlapping " is done for OP2,OP6 and OP10 and also move times maintained to achieve start-start relationship.
The first two operations OP2 and OP6 are assembly operations and at FG level they are just maintained as dummy operations with 1 sec machine time to send it to APO.We have assigned the assemblies at OP2 and OP6 so that we recieve FG's demand.
We have individual operations at Assembly level with same resource as in FG operations 2 and 6 , so when we receive demand at assembly heuristics will generate planned orders considering assemblies PDS.
We want that OP2 at FG and Operation at assembly 1 should start at same time .Since both are exactly the same operations.Currently it is not happening the same .
Current situation
E.g.
OP2
Activity start date - 2016-01-22 09:26:00
Activity end date - 2016-01-22 09:26:29
Demand at Assembly 1
We are observing dependent demand with end date 2016-01-22 and time 09:26:00.Here we want that when we run the heuristics it should create order with start date at 2016-01-22 and time 09:26:00 and end after considering the process time.The start duration of the planned order should be the same at FG's OP2 activity start date and time.
But standard heuristics will backward schedule and create the order earlier and finish it on the Dependent demand date.
Thanks
Debasis Nanda