using Overtime: this shall be easy if using resource hourly cost, resource cost periods and resource overtime.
second shifts: this shall be easy if using teams of resources working under different shift calendar, activity calendar shall be the union of all assigned shifts or a 24/7 calendar.
each team work independent of each other
within a team all resources must work together
if all resources must work together that makes a single team
if all resources can work independent of each other then each resource is a team of one
the work distribution can be distributed in order of team execution [most common] or can be fixed-for-teams
team modeling is lacking in many software, in such case a common workaround is to use different activities for each team. This can require trial an error in the most common scenario, when work is done in order of team execution. Say a team 1 works on Monday and Tuesday while team 2 works on Friday and Saturday, if activity can be done by any of the teams within two days if it starts on Monday all work will be done by team 1, if starts on Tuesday some work will be done on Tuesday by team 1 and the remaining by team 2 on Friday.
activity duration: if using activity duration driven by resource production rates and volume of work the software shall do the math.
cost impact: it is a matter of cost loading your what-if scenarios activities and their resources, overtime will come at a cost, reduced production rates on second shift will also come at a cost, the savings in overhead activities can be modeled if using hammocks, hiring plan to account for idle time can be modeled using activity resource production and consumption.
The following post will provide you with some images might give you an idea on how it can be done, the details will deppend on the software you use.
If your software is not capable of dealing with multiple teams working on a single activity or not capable of driving activity duration using resource production rates you might need to work it around using manual methods.
Member for
21 years 8 monthsCALENDARS ARE KEY TO DEFINE
CALENDARS ARE KEY TO DEFINE WORK TIME FOR EACH SHIFT.
USE RESOURCE PERIODS TO ACCOUNT FOR UNIT COST INCREASE WITH TIME.
USE OVERTIME SCREEN TO DEFINE COST OF OVERTIME HOURS [SET A CALENDAR TO DEFINE OVERTIME HOURS]
SIMPLE MATH BUT VERY TEDIOUS IF MANUAL
PAGE 2 OF 2
Member for
21 years 8 monthsusing Overtime: this shall be
The following post will provide you with some images might give you an idea on how it can be done, the details will deppend on the software you use.
If your software is not capable of dealing with multiple teams working on a single activity or not capable of driving activity duration using resource production rates you might need to work it around using manual methods.
Easy but very tedious, good luck.
PAGE 1 OF 2