Hi,
In DOP structures there may be many shop orders connected through structure relationships. If the machine shop resources are finite, upon creating a finite schedule for the shop orders, the relationship between respective parent DOP orders has to be respected also. APB is capable of doing it. The planners are able to schedule DOP header ( demand header) , forward , backward, drag-n-drop or insert : where in any case, the operation relationships, DOP order relationships( structure relationships) and the resource constraints are respected.
Can you share the experiences in using this functionality ( pros and cons). How often this functionality is used?
On the other hand when it comes to Operation Blocks, APB is capable of loading operation block as single object ( along with its operations) but APB does not keep the operation block scheduled space in the resource exclusively for the operation block. The operations in the block can freely schedule in the resource timeline if there are no resource restrictions. When planner execute drag and drop scheduling , the operations can be scheduled anywhere in the timeline ( as if any other individual operations). In short, operation block is not considered in APB finite scheduling.
Is this a big gap in APB finite scheduling. How restrictive an operation block should be in finite scheduling?
example:
Laster cutter resource is used to cut metal sheets
Lets say there are 10 shop order operations to cut different parts from mild steel metal sheet
15 shop order operations to cut different parts from carbon fiber sheet.
lets say the first 10 operation grouped as operation-block-1 and the second 15 as operation-block-2
It is highly likely that the block 1 has to perform together ( operations in Parelli or sequential ) then block 2. This can NOT be done in APB ( automatically, the user has to manually create this schedule).
Is this functionality greatly missed? or something good to have?
Thanks in advance
Saman
