We are currently going on almost 2 years, there are a few things we still need help on.
List item
Shift Scheduling we run currently 3 shifts, is there a way to do shift scheduling without having a production calendar of 20hrs (two 10 hour shifts)?
List item
Is there a user guide for the Change impact informer (what all the columns/rows mean)
Is there a user guide for the Schedule impact report (what all the cloumns/rows mean).
List item
What are something you look at daily/weekly/quarterly for scheduling resources. We have 3 different areas that our âbottle neckâ areas. We are currently using finite schedulingâŚare there some doâs and donâtâs?
List item
What are the inâs and outâs of Resource Collection? Can we do this for shift scheduling and call those resource collection on an operation to have capacity over the collection of resources?
List item
Easy way to see Resource load
List item
Different things that need to be set up that impacts the schedule.
@timshuwy and @NateS I have seen you both post some really good stuff for scheduling. If there is anything that you can help with or share more information on would be awesome.
Resource Collections are just a way to group together disparate resources so you can view them on the same report. They are not used for anything other than giving different views of the schedule.
No there isnât. I donât have the payroll module which adds some functionality that I know nothing about, but the scheduler uses a âcalendar of exceptionsâ hierarchy to determine resource availability. Itâs all spelled out in the PDF linked above.
Itâs worth noting that the scheduler does not extend job operations across âshiftsâ. For example, machines are available all day, but operators are only there for a shift - it will NOT schedule a machine for 18 hrs and a 1st shift operator + a 2nd shift operator. Once it assigns either operator, the job will be split up so that only that operator can work on it. Most of us who have this problem have created âvirtual operatorsâ in order get the schedule correct, but the downside is that the human Employee/Operatorâs calendar means nothing.
Basically it all comes down to resource and material availability. Make sure inventory, MRP, and POâs are all as correct as possible and the scheduler will do OK. As for the rest - we constantly monitor human and machine availability and tweak as needed. People turnover is so high now, we just set the operator group to have about 60% of the actual headcount. Machines need constant repair/PMs, so if you do not use the Maintenance module (with resources linked to the equipment and therefore the schedule) you must make calendar exceptions for the machine downtime.
If I understood the ? properly, the collection is just that - similar resources - so that you can specify the collection/group as the operationâs required resource and the scheduler can/will choose from the collection of resources. If the operation specifies a need for more than 1 resource, it can handle that too. But you can get complicated with âcapabilitiesâ which are the operational differences in resources - but you should consult the PDF for more info.
Check the PDF. There are two good dashboards for this, and a report.
Simply, everything affects it. The whole material procurement process and itâs set up down to Min/Max/Safety stock and lead times per vendor. The number of required resources on the operations - people, machines, capabilities. The job dates, the operational estimates/standards⌠everything. There are so many options at each of these stages - calendars, blocks, scheduling fence, co-dependencies, subassemblies, etc. etc.
