Please note Below you find explanations (with examples) of the operating principles of date planning and scheduling in PLANTA project as well as descriptions of common application cases and of the behavior under particular settings. The program depictions used here are based on an older software status and are to be regarded functionally only. General information on date, resource, and cost planning in PLANTA project including a calculation matrix can be found here.

Date/Resource Scheduling

Application Cases

Application Cases for Planning Strategies

Premises:

• Active today line, Fix = 0, Planning early, CAP (as far as nothing else is specified)

Description	Adher. to schedule	Adh. to total float	Adher. to capacity
Target	How much overload arises for the employees if the dates are to be adhered to? How much buffer is available?	How much overload arises for employees if the dates are adhered to? How long to tasks last taking account of capacity and requested dates?	How long does a project last with predefined effort and limited capacity (no overload)?
Description of the planning method	Task duration and dates are adhered to. If the task durations are longer than the remaining time horizon, the end date is shifted. Overloads are shown	The project receives a requested end date. The remaining duration of the task is calculated according to the resource effort. Floats are exploited. The overloads are smoothed. End dates are adhered to as far as the remaining time horizon is sufficient for the planned duration of the task.	The duration of a task is determined from Effort Available capacity CAPload profile Option: Planning with max. load/day
Planning	Usually, Planned duration or alternatively Req. start - Req. end are entered (Req. start - Req. end dominates the Planned duration). If no Planned duration has been entered, it is calculated by Req. start - Req. end. Planning without load curves: When inputting the Planned duration of the task, the planned effort of the resource is allocated to the duration evenly. If NO Planned duration of the task is entered, the system calculates the Remaining duration of the task by means of resource effort, CAP load profile and Max. load/day.	Usually, planned duration, or alternatively Requested start - Req. end. If no Planned duration has been entered, it is calculated with Req. start - Req. end. When you enter the Planned duration of the task, the Planned effort of the resource is allocated evenly to the duration. If NO Planned duration of the task is entered, the system calculated the Remaining duration of the task by means of the resource effort, CAP load profile, and Max. load/day Regardless of whether Planned duration has been entered or not, the Remaining duration is extended, as far as the Planned effort cannot be accomplished within the predefined time, or within the available float. The requested date is overrun in consideration of the links if the duration of the tasks is too long.	No input of task duration or TA Req. start/Req. end required. Only input of effort in h for allocated resources. For the parameters, see above.
For tasks with resource assignments:. Extend tasks before MA has reported hours.	In order to extend the task duration in days before hours have been reported, the Planned duration of the task is extended. Alternatively the effort can also be increased if the CAP load profile has been selected. In order to increase the effort, the Planned effort is increased.	Increase of Planned duration, or Planned effort on employee level, provided that the CAP load profile has been selected.	The Planned effort is increased on resource level, provided that the CAP load profile has been selected.
For tasks without resource assignment: Extend tasks without actual start date.	Increase Planned duration on task level.	Increase Planned duration on task level.	Increase Planned duration on task level.
For tasks without resource assignment: Extend tasks with actual start date.	Extend Remaining duration on task level or extend Requested end. New: Remaining duration is calculated depending on the actual date. Remaining duration = Planned duration – Actual duration , whereas: Actual duration = today - Actual start date. As before, open tasks remain with 1 remaining day as a reminder.	Extend Remaining duration on task level or extend Requested end. New: Remaining duration is calculated regardless of the actual date. Remaining duration = Planned duration – Actual duration , whereas: Actual duration = today - Actual date. As before, open tasks remain with 1 remaining day as a reminder.

Application Cases of Date Scheduling without Resources

Objective

• To plan tasks depending on a specified task / work package duration.

Overview 1: Planned duration = 0

Application case	Procedure	Result
Plan task without date	Calculate project	Calc. start = Today, if today’s date is active = Calc. end
Plan task with Requested start	Enter start date in Requested start Calculate project	Calc. start = Requested start = Calc. end
Plan task with Requested start	Enter end date in Requested end	Calc. end = Requested end = Calc. start
Plan task from .... to ....	see overview 2

Overview 2: Planned duration > 0

Application case	Procedure	Result
The task has a runtime in days.	Input of the days in the Planned duration field Calculate project	Task is planned with: Calc. start Remaining duration = Planned duration Calc. end = Start date + Remaining duration
Variant: Runtime with defined start date	Input of the days in the Planned duration field Enter start date in Requested start Calculate project	Task is planned with: Calc. start = Requested start Remaining duration = Planned duration Calc. end = Start date + Remaining duration
Variant: Runtime with defined end date	Input of the days in the Planned duration field Enter end date in Requested end Calculate project	Task is planned with: Calc. end = Requested end Remaining duration = Planned duration Calc. start = Calc. end – Remaining duration
The task has a runtime from .... to .... with defined start and end date (key dates)	Enter start date in Requested start Enter end date in Requested date Calculate project Planned duration has no effect but serves for comparison purposes or is omitted	Task is planned with: Calc. start = Requested start Remaining duration = duration of Req. start up to Req. end in working days Calc. end = Req. end Input in Planned duration is overwritten by the scheduling in accordance with the requested dates
The task is to be shifted if a predecessor is shifted. Runtime either by basic dates or specification in days, Fix = 0	Enter task with start and / or end date and / or Planned duration Link predecessor to task Calculate project	Task is planned with: Start/end dates and Remaining duration according to requirement Shifting of the predecessor causes the task to be shifted.

Behavior of TA Requested Dates and TA Remaining Duration when TA Actual SD is Set

Details

• The TA Remaining duration is calculated via the Requested end of the task if TA Actual start is set.
• If a TA Actual start is set which is later than the Requested start of the task, the Requested end of the task is kept and the Remaining duration is shortened.
• If a TA Actual start is set which is earlier than the Requested start of the task, then for
  • Split = N, the entire task is brought forward and the Requested end of the task is kept. The task Remaining duration is extended.
  • Split = Y the task planned with the Requested start and the Requested end of the task.

Example date scheduling without resources

• Initial situation

• If a TA Actual start is set which is later than the Requested start of the task, the Requested end of the task is kept and the Remaining duration is shortened.

• A TA Actual start is set which is earlier than the Requested start of the task.
• Split = N: The entire task is brought forward and the Requested end of the task is kept. The task Remaining duration is extended.

• Split = Y: * The task is planned with the Requested start and the Requested end of the task.

Application Cases of Date Scheduling with Resources

Time-Related Planning with Task Duration

Provisions

• Planned duration
• Load profiles not used, i.e. the load is distributed evenly over the available period without overloads being taken into consideration.
• Resources are not loaded on non-working days (public holidays, vacations, ...).

Result

• for planning with adherence to schedule
  • Planning along the duration without considering overloads.
  • Where possible, scheduling is carried out as a block, i.e. without interruption. Exception vacation: This resource is not scheduled during vacation.
• for planning with adherence to total float
  • The planning is done along the duration without considering overloads but with utilization float per overloaded resource.
  • If there are hours left to be included in the planning, planning starts at the latest possible point in time. The project requested end date will not be overrun.
• for planning with adherence to capacity
  • Standard: Planning is done without consideration of requested durations and requested project requested end dates, no overloads, no scheduling on non-available days.
    • Exception: If no available capacity is found up to the end of the planning period of the resource, loading starts at the earliest point in time, despite overload (like adherence to schedule).

Example:

• Overload in planning with adherence to capacity with end period earlier than planned duration (provisions: Planned duration = 10 days, Planned effort = 100h, available capacity of the resource per day = 8h). The requirement cannot be fulfilled at any time. The resource is overloaded evenly.

Planning with Requested Dates of the Resource

Planning with TAR Requested Start

Information

• A TAR Requested start only takes effect if it lies just as early or late as the TA Requested start.

Example

• Due to the later TA Requested start TAR Requested start cannot be adhered to..

Example

• Due to the PR Requested start, the task does not start on the TAR Requested start, but instead on the PR Requested start, provided that this is not prevented by other parameters such as links or TA requested dates. As a result of the TAR Requested start lying outside the TA Requested start and TA Requested end, it is not considered by the scheduling.

Information

• If more than one resource is planned, TA Remaining duration applies to all tasks without TAR requested start. Resources that have a Requested start, receive a shortened duration from TA duration– (TAR Requested start – TA Earliest start).
• If the resource has a Remaining effort and a Max. load/day, the Remaining duration of this resource is calculated from Remaining effort / Max. load/day. If the Remaining effort = 0, at least a Remaining duration of 1 applies.
• If the Schedule early is activated for the task and a resource has a remaining TAR Requested start within the TA Calc. start/TA Calc. end, this resource starts on this date, while all others start at the TA Earliest start. The plan for the task will automatically be adherence to schedule.

Example

• As a result of the TAR Requested start, resource R1 has a reduced scheduling duration of 2 days. The effort for 16 hours will be distributed across the two days and the resource is overloaded. For resource R4, scheduling is distributed over three days without overload.

• If the task is scheduled with Sched. early and with adherence to schedule, the TA Requested start will be ignored.

Example

• Since the task is scheduled late and adherent to schedule, TAR Requested start is ignored. The resource is scheduled on three days.

• If the task is adherent to total float or capacity and scheduled lately, a resource with a TAR Requested start is only adjusted up to this date; while all others are adjusted as before at the TA Earliest start.

Example

• Although resource R1 is overloaded, the adjustment of the resource is not carried out at the PR Requested start, but only up to the TAR Requested start.

• If a task has started, the resource which has a TAR Requested start will start on this date; while all others have the same start as before. For splitting, the maximum of TAR Requested start and link date is applicable to the Earliest start.

Example

• Resource R1 has a TA Actual start on 10/16/08, but only starts with the remaining loading at the TAR Requested start. This is determined by parameter DI001112 Split. = Y in window 9. This only takes effect if the task has started but not yet ended.
• Resource R8 starts, as before, at the ‘today’ line.

Planning with TAR Requested End

Information

• If only one resources is assigned, the task ends (TA Earliest end) on the TAR Requested end if date-oriented planning is used, provided that there is no overload and the TAR dates are within the TA dates. Otherwise, TA duration = Planned effort / Max. load/day. For example, in loading with adherence to capacity, the TA is also extended.
• If more than one resource is planned, the task duration applies; the resource with a TAR Requested end receives a shortened duration of TA Remaining duration – (TA Earliest end – TAR Requested end).
• If the resource has a TAR Requested end, it ends on this date if date-oriented planning is used; all others end on the TA Earliest end.
• If Sched. late is set for the task, it automatically becomes adherent to schedule if a TAR Requested end has been assigned.
• If the task is adherent to float or capacity, and Schedule early is set, then any resource with a TAR Requested end will be smoothed up to this date. All others are adjusted at the TA Latest start + TA Remaining duration.

Planning with TAR Requested Start and TAR Requested End

Information

• If the resource has a TAR Requested start and a TAR Requested end and no Max. load/day, in planning with adherence to schedule the duration is detected from the requested dates.
• For loading with adherence to capacity, the TA is also extended.

Notes

• TAR requested dates are only considered by the scheduling if they lie within the TA requested dates. If the TAR requested date is outside the TA requested dates, it has no effect on scheduling, as planning does not lead to the desired aim at this point in time. This also applies if a task is shifted, for example as a result of a link, so that the TAR requested dates do not lie within the TA Calk. start/TA Calc. end.
• If no TA requested dates exist, TAR requested dates are only considered within the TA Calkc start/TA Calc. end.

Example 1

• TA Requested start 06/01/08 TA Requested end 08/31/08
• TAR Requested start 09/10/08, TAR Requested end 09/15/08
• Result: TAR requested dates are ignored.

Example 2

• A link shifts the above-mentioned task as follows:
  • TA Requested start 09/051/08 TA Requested end 10/5/2008
  • The TAR requested dates remain unchanged:
  • TAR Requested start 09/10/08, TAR Requested end 09/15/08
• Result:
  • The previous planning of the TAR requested dates are ignored.
  • Planning of the TAR does not have to be done from 09/10 - 09/15/08.

Overview of Application cases

Overview

• Planning with adherence to schedule with linear load profile

Application case	Procedure	Result
Plan resource without dates	Assign resource to task Enter effort Calculate project	TAR Calc. start = TA Calc. start TAR Calc. end / TA Calc. end Resource duration = task duration
Plan resource with Requested end	Assign resource to task and enter effort Enter end date in Requested end of the resource (TAR Requested end) Calculate project	TAR Calc. start = TAR Calc. end duration TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task.
Plan resource with TAR Requested end	Assign resource to task and enter effort Enter end date in Requested end of the resource (TAR Requested end) Calculate project	TAR Calc. start = TAR Calc. end duration TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task.
Plan resource from .... to ....	Assign resource to task and enter effort Enter start or end date in resources (TAR Requested start/Requested end) Consider task date limits Calculate project	TAR Calc. start = TAR requested start TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task.
Plan resource with Requested start	Assign resource to task and enter effort Enter start date in Requested start of the resource (TAR Requested start) Calculate project	TAR Calc. start = TAR requested start TAR Calc. end = TAR Calc. start + duration Note The planning time of the resource is possibly shorter than the length of the task.

• Planning with adherence to total float

Application case	Procedure	Result
Plan resource without dates	Assign resource to task Enter effort Calculate project	TAR Calc. start = TA Calc. start TAR Calc. end / TA Calc. end Resource duration = Task duration If float is required, the task duration or the planning period of the resource can be extended.
Plan resource with Requested start	Assign resource to task and enter effort Enter start date in resources (TAR Requested start Calculate project	TAR Calc. start = TAR requested start TAR Calc. end = TAR Calc. start + duration Note The planning time of the resource is possibly shorter than the length of the task. If float is required, the task duration or the resource load can be extended backward.
Plan resource with TAR Requested end	Assign resource to task and enter effort Enter end date in resources (TAR Requested end) Calculate project	TAR Calc. start = TAR Calc. end duration TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task. If float is required, the task duration or the resource load can be extended forward.
Plan resource from .... to ....	Assign resource to task and enter effort Enter start or end date in resources (TAR Requested start/Requested end) Consider task date limits Calculate project	TAR Calc. start = TAR requested start TAR Calc. end of the resource = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task. no float exploitation by the resource within the task period.

• Planning with adherence to capacity

Application case	Procedure	Result
Plan resource without dates	Assign resource to task Enter effort Calculate project	TAR Calc. start = TA Calc. start TAR Calc. end = TA Calc. end Note Planning time of the resource = task duration If float is required, the task duration or the planning time of the resource can be extended.
Plan resource with Requested start	Assign resource to task and enter effort Enter start date in resources (TAR Requested start) within the calculated start and end dates of the task. Calculate project	TAR Calc. start = TAR requested start TAR Calc. end = TAR Calc. start + duration Note The planning time of the resource is possibly shorter than the length of the task. End dates are possibly not considered.
Plan resource with Requested end	Assign resource to task and enter effort Enter end date in resources (TAR Requested end) within the calculated start and end dates of the task. Calculate project	TAR Calc. start = TAR Calc. end duration TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task. Start dates are not considered.
Plan resource from .... to ....	Assign resource to task and enter effort Enter start or end date in resources (TAR Requested start/Requested end) Consider task date limits Calculate project	TAR Calc. start = TAR requested start TAR Calc. end = TAR Requested end Note The planning time of the resource is possibly shorter than the length of the task. Float is used if necessary. End date is not considered.

Effort-Oriented Planning

Objective

• To plan commitments for employees, depending on the effort.

Requirements:

• Planning with adherence to schedule:
  • Field Load profile = CAP
  • Max.load/day field is filled with a value > 0
  • Resource assignment with planned hours
• Planning with adherence to total buffer and capacity:
  • Field Load profile = CAP
  • Resource assignment with planned hours
  • Optional: Field is filled with a value > 0

Details

• The Remaining duration is calculated
• Planning with adherence to schedule:
  • Remaining duration = planned hours / max. load
  • The effort (planned hours) is distributed across the calculated duration
• Planning with adherence to total float
  • The Remaining duration is dependent on the available capacity of the basic period (value from resource data sheet) and on the available float of the time scheduling.
  • The effort (planned hours) is distributed across the calculated duration
• Planning with adherence to capacity:
  • The Remaining duration is dependent on the available capacity of the basic period (value from the resource data sheet). Loading in takes place without overloads.
  • The effort (planned hours) is distributed across the calculated duration

Note

• Optionally, the Max. load/day parameter may also be used for planning with adherence to total float and capacity. The Remaining duration will be calculated as for planning with adherence to schedule.

Example: Planning with adherence to schedule

• Max. load/day = 5.5 hours
• Planned hours = 60 hours
• Remaining duration = 60 / 5,5 = 10,9 days, rounded = 11 days since calculation only works with whole days.
• Distribution of hours: 10 days @ 5.5 hours, 1 day @ 5 hours

Example: Planning with adherence to total float

• Max. load/day = empty
• Planned hours = 60 hours
• available capacity of the basic period = 8 hours – 10% basic load = 7.2 hours
• Remaining duration = 60 / 7,2 = 8,3 days, rounded = 9 days since calculation only works with whole days. If the resource is overloaded, the remaining duration will be extended up to the point where the overload no longer occurs
• Distribution of hours:
• without overload: 8 days @ 7.2 hours, 1 day @ 2.4 hours
• with overload: dependent on the Remaining duration. Cannot be determined in advance because of capacity adjustment.

Application Examples

Information

• A few application examples are provided below to illustrate the relationship between different factors that influence scheduling.

Notes

• Unless stated otherwise, the examples are based on the settings of the standard installation and the linear load profile. (= The DI001452 Load profile data field is empty)
• If the parameter settings are different, the results may vary accordingly.

Examples

• Overview and short description of application cases:

No.	Application case	Result
1	Planning with adherence to schedule with several resources Task with several task resources The Planned duration of the task is preset. Planning type = adherent to schedule	The planning is carried out by the scheduling along the duration of the task. Overload is not prevented by scheduling. Overloads are not displayed.
2	Planning with adherence to total float with several resources Task with several task resources The Planned duration of the task is preset. Planning type = adherent to total float	Scheduling carries out the planning along the duration of the task. Scheduling does not prevent overload. The float of overloaded resources is used to prevent possible overloads. If there is not sufficient float, resources will be overloaded Resource 1 with overload: Float is used Resource 2 without overload: Starts at the earliest start date.
3	Planning with adherence to capacity Task with several task resources The Planned duration of the task is preset. Planning type = adherent to capacity	The planning of the task by the scheduling is carried out without consideration of the Planned duration of the task. Resources are not overloaded. The float of overloaded resources is used: Resources are not planned on non-working days.
4	Resources with vacation, planning with adherence to schedule Resource with vacation Linear load The vacation duration is shorter than the task duration. Planning type = adherent to schedule	The planning is carried out in a block by the date scheduling. The resource is not planned by the scheduling during its vacation. On working days, the resource is possibly planned with overloads.
5	Resources with vacation < task duration, planning with adherence to schedule Resource with vacation Linear load The vacation duration is longer than the task duration. Planning type = adherent to schedule	The planning is carried out by the date scheduling before or, the latest, at the beginning of vacation. Due to the unavailability of the resource, the load is marked as overload during vacation. If the entire task is during vacation, loading begins on the calculated start date of the task.
6	Planning with vacation Vacation is entered for a resource, Linear load profile The vacation duration is shorter than the task duration. Planning type = adherent to total float	The planning by scheduling is carried out in a block outside the vacation time. Available float is used. If the float s used, the resource is overloaded by the scheduling. The resource is not planned during vacation. The planning is not splitted.
7	Planning with adherence to capacity with vacation Vacation is entered for a resource, Linear load profile The vacation duration is shorter than the task duration. Planning type = adherent to capacity	The planning by scheduling is carried out in a block outside the vacation time. Available float is not planned during vacation.
8	Planning with adherence to total float with Requested end and Fix = 0 Task with several task resources. The Planned duration is preset. Requested end on a task Fix TA parameter = 0 The vacation of a resource is shorter than the task. Planning type = adherent to total float	The planning of the task is carried out by the scheduling at the Requested end. By setting the Fix parameter = 0, the Requested end is overrun if necessary. No consideration of float and possible overload since it is loaded with adherence to schedule due to the input of a Requested end. The task is not moved.
8.1	Planning with adherence to total float with Requested end and Fix = 1 Task with several task resources. The Planned duration is preset. Requested end on task Fix TA parameter = 1 The vacation of a resource is shorter than the task. Planning type = adherent to total float	The planning of the task is carried out by the scheduling at the Requested end. By setting the Fix parameter = 1, the Requested end is met and loaded with adherence to schedule. No consideration of float and overload. The task is not moved.
8.2	Planning with adherence to total float with TAR Requested start Task with several task resources Tasks with FS-relationship Tasks without resource, with Planned duration Last task with 2 resources without Planned duration with Requested start CAP load profile Max. load/day =7,2h Planning early = N TAR Requested start of resource 1< TAR Requested start of resource 2 Planning type = adherent to total float	The task planning is carried out from the PR Requested start or from TODAY. The last task is planned as late as possible, hence at the Requested end of the project. The Requested start on the last task cannot be met due to Planning early = N.
9	Planning with adherence to total float with Requested end and Fix = 1 Task with several task resources. The Planned duration is preset. Requested end on task Fix TA parameter = 1 Planning type = adherent to capacity	Using the Fix = 1 parameter, the task is loaded with adher. to capacity. Overloads may occur.
10	Planning a task, which has a predecessor, with adherence to schedule, Requested start and Fix = 0 Vacation is entered for a resource Linear load profile The vacation duration is shorter than the task duration. Task with predecessor and Requested start, Fix = 0 Planning type = adherent to schedule	The task does not start at the Requested start, but after the predecessor has finished. The vacation of the resource is taken into consideration. Remaining duration = Planned duration
11	Planning with adherence to total float with effort > Availability Task with several task resources The Planned duration is preset. The capacity required for the desired duration exceeds the available capacity Planning type = adherent to total float	The scheduling uses available float. If there is no more float available, planning is carried out in a block at the latest time possible.
12	Planning with adherence to capacity with effort > availability Task with several task resources The Planned duration of the task is preset. The capacity required for the desired duration exceeds the available capacity. Planning type = adherent to capacity	Scheduling uses available float. Scheduling is delayed until loading in is possible in a block. Possibly the project end date is exceeded. The resource is not planned during vacation, the task is not splitted
13	Planning with adherence to total float of a task with predecessor, Requested end and Fix = 0 Vacation is entered for a resource Linear The vacation duration is shorter than the task duration. Task with predecessor and Requested start Fix TA parameter = 0 Planning type = adherent to total float	The task does not start at the Requested start, but after the predecessor has finished. The vacation of the resource is taken into consideration. Remaining duration = Planned duration Float is not used since a task with date is always loaded with adherence to schedule automatically.
14	Planning with adherence to capacity of a TA with predecessor, Requested end and Fix = 0 Vacation is entered for a resource. Linear The vacation duration is shorter than the task duration. Task with predecessor and Requested start Fix TA parameter = 0 Planning type = adherent to capacity	The task does not automatically end at the Requested end, but after the predecessor has finished. The vacation of the resource is taken into consideration. Remaining duration = Planned duration Float is not used since a task with date is always loaded with adherence to schedule automatically.
15	Calc. start when several task resources report Planning of several resourcen to one task and reporting of hours: just as planned earlier than planned later than planned	The resources are planned with their remaining effort from the TAR Actual start by the scheduling. If the day after the Actual start is no working day, the resource is planned on the next working day. The resource is possibly overloaded.
16	Reporting during vacation several resources are assigned to a task. A resource is on vacation over the complete task duration, however he/she reports hours.	The planning of the resources without vacation is carried out by the scheduling according to the default specifications. The resource which has reported during vacation is planned for the first working day after the report. The resource is possibly overloaded.

Information

• Below, the application cases specified above are displayed in detail with examples.

Planning with Adherence to Schedule with Several Resources

Objective

• Impact of planning with adherence to schedule with several resources on time scheduling

Details

• A project is created with several tasks and several task resources.
• The Planned duration of the tasks is preset or calculated from Planned effort / Max. load/day.
• The planning type is always adherent to schedule.
• The resources are planned with the CAP load profile.

Information

• * The planning is carried out by the scheduling along he duration of the task.
• Overloads are marked and won’t be distributed.
• The resources are planned by the scheduling according to PR Requested start.

Example

• The project starts on 10/31/08
• Resource R1 is planned in TA 01 with overload due to insufficient availability:

Notes

• In order for the scheduling not to overload the resources, the CAP load profile is required. In this case,
  • the available float can be used optimally for planning with adherence to total float
  • the project can be moved according to the available capacity for planning with adherence to capacity.

Planning with Adherence to Total Float with Several Resources

Objective

• Impact of planning with adherenc eto total float with several resources on time scheduling

Details

• A project is created with several tasks and several task resources.
• The Planned duration of the tasks is preset.
• Planning type is adherent to total float.

Information

• The available float is used resource-related by the scheduling if necessary.
• A resource with overload is moved by the scheduling according to the available float.

Example

• A project starts as planned on 11/25/08
• Resource R1 has sufficient free capacity in CW48. An overload occurs. The available float is used and the Calc. start is moved.
• The loading of resource R2 without overload remains unchanged. Calc. start for resource R2 starts on the earliest start date.
• The duration of task TA 01 is extended:

Planning with Adherence to Capacity with Several Resources

Objective

• Impact on the capacity planning of the time scheduling

Details

• A project is created with several tasks and several task resources.
• The Planned duration of the tasks is preset.
• The planning type is adherent to capacity.

Information

• Resources are planned without overload by the date scheduling
• In the case of resource shortage, the task is extended even beyond the Requested end.

Example

• PR Requested start: 10/31/2008
• PR Requested end: 12/31/2008
• Planning is carried out by the scheduling without considering the task duration.
• No overloads are created.
• Resources are not scheduled on days on which they are unavailable.

Example

• The PR Requested end of the project specified above is brought forward to 12/19/08 in order to simulate a resource bottle neck.
• Resources are planned by the scheduling without overload as required.
• The PR Requetsed end is overrun by 6 days:

Planning with Adherence to Schedule with Vacation

Objective

• To show the impact of vacation on the time scheduling when planning is carried out with adherence to schedule.

Details

• Vacation is entered for a resource.
• The planned editing period of the task does not lie completely within the vacation of the resource.
• Planning is carried out with adherence to schedule.

Information

• Scheduling is carried out along the task duration.
• Vacation is taken into consideration.
• Scheduling is possibly carried out with overloads.

Example

• Resource R2 has four days of vacation in CW45:

• Resource R2 is not planned by the scheduling during vacation. The load of resource R2 is decreased in the week of vacation CW45 accordingly, the effort of the remaining weeks is increased.
• Overloads are displayed.

Vacation Longer than Task Duration

Objective

• To show the impact of vacation that is longer than the task duration on the time scheduling.

Details

• The planned processing period of the task lies completely within the vacation of the resource.
• Planning is carried out with adherence to capacity and with linear load profile.

Information

• Planning is carried out by the scheduling at the time available for the task.
• Planning is carried out on the first day of vacation.

Example

• The vacation of resource R2 starts before the end of task TA 01 and extends completely across the duration of task TA 02.

• Planning of resource R2 for task TA 01 is carried out up to the start of the vacation.
• For task TA 02, it is carried out completely at the start of the vacation, as the whole task falls within the vacation period. The resource is overloaded.

Planning with Adherence to Total Float with Vacation

Objective

• To show the impact of resource planning with adherence to total float with vacation on the time scheduling

Details 1

• Vacation is entered for a resource.
• The planned editing period of the task does not lie completely within the vacation of the resource.
• Planning is carried out with adherence to total float with a linear load profile.

Information

• Planning is carried out along the duration of the task taking account vacation and float, if available.
• If the float is used up, it is overload.
• Resources are not scheduled during vacation.

Example

• Resource R2 is on vacation in CW 46 and is not scheduled during this time.
• As the available capacity is insufficient even when the float is used, resource R2 is overloaded:

Planning with Adherence to Capacity with Vacation

Objective

• To show the impact of planning with adherence to capacity with resource vacation on date scheduling.

Details

• Vacation is entered for a resource.
• The planned editing period of the task does not lie completely within the vacation of the resource.
• The available capacity of the resource is greater than the required capacity.
• The Planned duration of the task is preset.
• Planning with adherence to capacity is used with a linear load profile.

Information

• Resources are planned by the scheduling with adherence to capacity.
• Resources are overloaded if there is not sufficient capacity due to the preset duration.
• Resources are not scheduled during vacation.

Example

• Planning is carried out by the scheduling along the duration of the task, taking account of vacation.
• Resource R2 is not scheduled during its vacation in CW 48.
• Scheduling of R2 is carried out with overloads due to the specified duration:

Planning with Adherence to Total Float with Task Requested ED and Fixing = 0

Objective

• To show the impact of planning with a non-fixed Requested end on date scheduling.

Details

• The Planned duration of the task is preset.
• The task has a Requested end.
• DI009480 Fix TA parameter = 0
• Planning is carried out adherent to total float and with linear load profile.

Information

• The initial task duration is retained.
• Resources are not scheduled during vacation, which can be seen for R2 in CW 48 in the example below.
• Float times are ignored since loading is carried out with adherence to schedule due to the set Requested end. Scheduling is carried out with overloads, if necessary.
• TAR Calc. end 12/11/08 is later than the Requested end 12/05/08 if this cannot be prevented due to the task duration.

Example

• Due to the preset task duration, the Calc. end is later than the Requested end
• The deviation from the Requested end is displayed for task TA 01.
• Resource R1 is overloaded.
• Resource R2 is not scheduled during its vacation in CW 48.

Planning with Adherence to Total Float with Task Requested ED and Fixing = 1

Objective

• To show the impact of planning with a fixed Requested end on time scheduling.

Details

• The task has a Requested end.
• DI009480 Fix TA parameter = 1, the task is therefore fixed to the date.
• Planning type is adherent to total float.

Information

• TA Requested end is not moved.
• Resources are not scheduled during vacation.
• An overload is scheduled if required.
• A long duration of a task with fixed Requested end may lead to the Calc. start being earlier than the Calc. start of the project. Calc. start of the project is thereby brought forward. This only applies if the ‘today’ line is not active.

Example

• TAR Calc. end corresponds to the Requested end
• The task duration is not extended.
• The resource is overloaded.
• Resource R2 is not scheduled during its vacation in CW 46.

Note

• Task dates with Fix parameter = 1 have a similar effect to actual dates, i.e. they are not shifted by the active ‘today’ line if Requested start or Requested end are entered.

Planning with Adherence to Total Float with TAR Requested SD

Objective

• To display the impact of planning with adherence to total float of TAR Requested start on time scheduling

Details

• Scheduling of several tasks.
• Several task resources are assigned to a task with Requested start.
• The task resources have different TAR Requested start.
• Planning type is adherent to total float.

Information

• Resources are overloaded if necessary.
• Resources are not scheduled during vacation.
• The planning of the resources is carried out on the TAR requested dates, as far as they lie within the period from Calc. start to Calc. end.

Example

• Scheduling loads in the resources for the time available.
• Resources R3 and R4 are overloaded:

Notes

• The TA Requested start with fixing has a higher priority for scheduling than the TAR Requested start.
• In the case of planning with adherence to float and late planning, Requested start dates are ignored and Requested end dates are taken into consideration.

Planning with Adherence to Capacity with Requested ED and Fixing = 1

Objective

• To show the impact of planning with adherence to capacity with Requested end without fixing on date scheduling.

Details

• The task has a Requested end.
• DI009480 Fix TA parameter = 1
• The planning type is adherent to capacity.

Information

• The Requested end is not overrun by the scheduling.
• Floats are ignored.
• Scheduling is carried out with overloads, if necessary.
• Resources are not scheduled during vacation.

Example

• Float is ignored since due to Requested end with _Fix parameter = 1 loading is carried out with adherence to schedule.
• Overloads are scheduled so that the Requested end can be met:

Planning with Adherence to Schedule of a TA with Predecessor, Requested SD, and Fixing = 0

Objective

• To show the impact of planning of a task with adherence to schedule with predecessor, Requested end with Fix parameter = 0 on date scheduling.

Details

• Several task resources are assigned to a task with predecessor and non-fixed Requested start.
• The planned editing period of the task does not lie completely within the vacation of the resource.
• The processing of the predecessor takes longer than planned.
• The planning type is always adherent to schedule.

Information

• Scheduling may also shift the task and plan resources with overloads.
• The deviation from the Requested start is displayed.
• Resources are not scheduled during vacation.

Example

• The predecessor takes longer than planned.
• The successor starts later, the task duration is not extended. The task is scheduled with overloads.
• The deviation from the Requested start is displayed for task TA 02 by the interval between the triangle and the start of the bar.
• Resource R2 is not scheduled during its vacation in CW 49.

Planning with Adherence to Total Float of a TA with Predecessor, Requested ED and Fix = 0

Objective

• To show the impact of planning with adherence to total float for a task with predecessor, Requested end and Fix parameter = 0 on date scheduling.

Details

• Several task resources are assigned to a task with predecessor and non-fixed Requested end.
• Planning type is adherent to total float.

Information

• Scheduling shifts the task if the predecessor takes longer than planned.
• The deviation from the Requested end is displayed.
• The resource is overloaded, if necessary.
• Resources are not scheduled during vacation.

Example

• Task 01 is linked to task 02 via an FS link.
• Since task 01 is delayed, task 02 is shifted beyond its Requested end. A deviation of 17 days is displayed.
• The resources are planned with overload.
• Resource R2 is not scheduled during its vacation in CW 48.

Planning with Adherence to Capacity of a TA with Predecessor, Requested ED, Fix = 0

Objective

• To show the impact of planning with adherence to capacity of a task with predecessor, Requested end and Fix parameter = 0 on date scheduling.

Details

• Several task resources are assigned to a task with predecessor and non-fixed Requested end.
• Planning is carried out with adherence to capacity and with linear load profile.

Information

• Scheduling shifts the task if the predecessor takes longer than planned.
• The deviation from the Requested end is displayed.
• If necessary, the resource is overloaded since the Requested end causes the planning to be carried out with adherence to schedule.
• Resources are not scheduled during vacation.

Example

• Task 01 is linked to task 02 via an FS link.
• Since task 01 is delayed, task 02 is shifted beyond its Requested end. A deviation of 24 days is displayed.
• The resources are planned with overload.
• Resource R2 is not scheduled during its vacation in CW 48.

Planning with Adherence to Total Float Higher than the Availability

Objective

• To show the impact of planning with adherence to total float with effort higher than availability on date scheduling.

Details

• The Planned duration of the tasks is preset.
• The effort is higher than the availability of the resource in the planned processing period.
• Planning is carried out with adherence to total float and with linear load profile.

Information

• The float of the overloaded resource is used:
• Scheduling is carried out at the latest possible point in time.

Example

• The Planned effort of 150h within 15 days exceeds the available capacity of the resource. Task 01 is therefore scheduled at the latest point possible:

Planning with Adherence to Capacity with Effort Higher than the Availability

Objective

• To show the impact of planning with adherence to capacity with effort higher than the availability on date scheduling.

Details

• The Planned duration of the tasks is preset.
• The effort is higher than the availability of the resource in the planned processing period.
• Planning is carried out with adherence to capacity and with linear load profile.

Information

• Resources are not scheduled during vacation.
• Scheduling shifts the task until it can be planned in a block. This means that the project end date may also be moved.
• Scheduling evenly distributes the effort within the Planned duration across the task duration. The resource is overloaded.
• The float is ignored, the task duration is not extended.

Example

• Scheduling shifts the task until it can be planned in a block.
• Resource R2 is not scheduled during its vacation in CW 45.
• Resource R1 is overloaded.
• PR Requested end is overrun:

Note

• If the CAP load profile is used, available float is taken into consideration.

Work Reporting of Several Task Resources

Objective

• To show the impact of work reporting with planning with adherence to schedule without requested dates and with several resources on date scheduling.

Details

• Several task resources with CAP load profile are assigned to a task.
• No TAR Requested start and Requested end set.
• The planning type is always adherent to schedule.
• Split parameter = Y

Information

• Calc. start of the task and all task resources is shifted to the next working day after the latest work reporting.
• Late work reporting can thus lead to a shift of the Calc. end.

Example

• Resource R2 is on vacation in CW 49.
• Dates before reporting of hours:

• After reporting to 11/10/08 by R1 and carrying out a date scheduling, the Calc. start of task 01 is shifted from 11/04/08 to 11/10/08:

Work Reporting on Vacation

Objective

• To show the impact of hours reported on vacation on time scheduling.

Details

• Several task resources are assigned to a task.
• A resource is on vacation for the whole task duration and reports actual hours for the vacation period.
• The resources are planned with a linear load profile.

Information

• Resources are not scheduled during vacation.
• Resources that report hours for the vacation period receive the remaining effort on the next working day after reporting. The resource may be overloaded.
• Scheduling of resources without vacation is carried out in accordance with regular planning.

Example

• Resource R8 is on vacation from 11/05/08 to 12/16/08. The total effort for task 01 is scheduled on the first day of the vacation and the resource is overloaded:

• Hours are reported during the vacation period. At task and task-resource level, scheduling reduces the reported hours from the remaining effort and overload.
• The remaining effort is scheduled on the day after work reporting:

Planning with Adherence to Schedule with CAP

Information

• Planning with specification of the TA Planned duration or Max. load/day with optimized task loading.
• If no Planned duration is specified, the TA Remaining duration is calculated from
  • Max. load/day set: TA Remaining duration = TAR Remaining effort / Max. load/day
  • Max. load/day not set: TA Remaining duration = max. (TA Planned duration - TA Actual duration or 1)
• The available capacity is planned for each day, if it is not restricted by a Max. load/day or Min. load/day. The loads on individual days may differ.
• If no Max. load/day has been set, and if it is possible to plan in the total effort within the unused capacity, the Remaining duration may be reduced. This can lead to very high daily loads.
• If it is not possible to plan in the total effort within the available capacity, the overload is distributed equally across all load records to days on which the resource is working.

Note

• Even with due-date oriented planning, the resource-capacity will be optimized within the TA Remaining duration. Practical experience has indicated that by simply setting "CAP" in conjunction with planning with adherence to schedule, overloads can be significantly reduced. This positive effect is found particularly when the deployment of individual employees is being planned.

Example

• The Sample10 project is planned as follows:
  • Parameters: PR Priority = 1, TAR Remaining effort with 50h with load profile = CAP
  • PR Requested start 1/24/20, no PR Requested end, TA Remaining duration 10 days, hence float up to the end of the planning horizon.
    • Since TA Remaining duration is too short for TAR Remaining effort, the Max. load/day will be overrun However, no overload incurs.

• If TAR Remaining effort is too high, the resource will be overloaded.

• If no Remaining duration, no Max. load/day, and no TA requested dates are preset, the total load is loaded on one day. The resource is overloaded.

Note

• If the PR or TA has requested end dates or the TA has a Remaining duration and the resource cannot be planned within this period, the overload is distributed evenly across all load records on the resource’s working days within the specified period if planning is carried out with adherence to schedule.

Planning with Adherence to Total Float with CAP

Objective

• Planning with adherence to total float by presetting the TA Planned duration or the Max. load/day with optimized load

Details

• TA Remaining duration is calculated just as with date-oriented planning, but it may be extended up to the end of the total float time or the planning horizon if there is insufficient capacity.
• TA Calc. start is moved to the first day with remaining capacity, provided that its start is yet earlier than the TA Latest start. Otherwise, TA Calc. start = TA Latest start applies.

Example

• The Adherent to total float+CAP project is planned as follows:
  • Parameters: PR Priority = 1, TAR Remaining effort with 50h with load profile = CAP
  • PR Requested start 1/24/20, PR Requested end 2/14/20, as a result there is float up to this date, TA Planned duration 10 days.
  • Max. load/day = 4 h results in TA Remaining duration of 50/4 = 12,5, hence 13 days. Due to the Project Requested end, the scheduling can extend the task up to the end of the float. (Remaining buffer = number next to the project bar.)

• If the Remaining effort is increased, the task is extended up to the end of the float at most, the Max. load/day is overrun.

• Without a Max. load/day, the resource is scheduled with the maximum load per day specified in DI000804 Def. max. load in the resource data sheet.

Note

• If the Remaining effort cannot be planned within the remaining capacity of the float since the float is too small, the overloads are distributed evenly across the loading period.

Planning with Adherence to Capacity with CAP

Information

• The resources are loaded independent of one another, and calculated durations and dates are summarized to the task.

Notes

• If the resources assigned to a task include some with CAP and some without, then the CAP resource assignments take precedence, i.e. the TA duration is determined from the CAP resource assignments. The non-CAP resources are planned on the basis of the calculated TA duration and no resource capacity adjustment is carried out for them.
  • Exceptions:
    • Remaining effort = 0 (CAP is not considered in the calculation of the TA duration)
    • MAN load profile (cf. respective section).
• When planning with adherence to schedule and total float is carried out with CAP, overloads are distributed equally across the resource’s working day on all the load records.

Example

• The Adherent to capacity+CAP project is planned as follows:
  • Parameters: PR Priority = 1, TAR Remaining effort with 30h with load profile = CAP
  • PR Requested start 1/24/20, PR Requested end 2/7/2020, as a result there is float up to this date, TA Planned duration 5 days.
  • Max. load/day = 4 h results in TA Remaining duration of 50/4 = 7,5, hence 8 days. Due to the Project Requested end, the scheduling can extend the task up to the end of the float. (Remaining buffer = number next to the project bar.)

• If the TAR Remaining effort is increased, the PR Requested end is overrun, the Max. load/day is considered.

MAN Load Profile

Information

• Load records of MAN resources have an effect similar to that of an actual date. The planning data is fixed and is not moved by scheduling.
• Actual dates do not change the MAN planning either.

• Example
  • Non-agreement of Calc. start and Actual start
    • MAN planning on 11/04
    • Actual load, e.g. of a CAP resource on 11/05
    • Result:
      • Calc. start 11/04
      • Actual start 11/05

• Load sequence in scheduling: Actual date, MAN, CAP, TAR Requested start/Requested end_, all other load profiles.

Example

• The MAN project is planned as follows:
  • Parameters: PR Prio = 1, TAR with load profile = MAN and load records (sum = 24h), no TA Remaining duration
• TA Req. start/Req. end are considered as long as the MAN dates are not infringed. In comparison to the MAN period, you can shift the Calc. start of the task forward (= earlier) and the Calc. end backward (= later).
  • If no TA requested dates are set, the task starts at today’s date and ends with the last MAN planning.
  • In a task without Remaining duration but with TA Requested start and TAR with MAN load profile before the Requested start, the TA Requested start is not considered. Calc. start is the earlier MAN planning.

• In a task with TA Requested start before the first MAN load record, the task starts at the TA requested start. The resource is planned for the MAN date.

• The TA can, e.g., be extended for example by planning with CAP resources. The duration of the task is not reduced by CAP planning. The minimum task duration is the timescale of the MAN dates.
  • When planning with MAN resources, resource dates override the other planning requirements. This also applies for the project key dates.
  • As soon as a MAN resource is assigned to a task, scheduling of the resources is based on the TA requested date and not on the PR requested date. The project basic dates are thus overrun.
  • As far as no TA Requested start has been set, the task starts at the PR Requested start.

Only CAP resources	CAP & MAN resources
TA with Remaining duration 5 d and resource with CAP and Remaining effort = 15h. PR Requested start on 01/06/20, i.e. later than TA Requested start on 01/03/20. The TA starts at the PR Requested start. The resources are planned on the CAP date which is the PR Requested start	Planning of a MAN resource, retention of a CAP resource. The TA starts at the TA Requested start, not at the PR Requested start. The planning of the CAP resource starts at the TA Requested start CAP date, which is the TA Requested start and not at the PR Requested start. The MAN resource is planned for the dates of its load records.

• Requested dates on the task resource are ignored under MAN.
  • In a task with TA Requested start before the first MAN load record and TAR Requested start on the MAN resource before the first load record, but after the TA Requested start, the task starts at the TA Requested start. The resource is planned for the MAN date. TAR Requested start is not taken into account.

• This does not automatically make the task adherent to schedule as soon as a MAN resource has been assigned to it. The TA can be shifted until it reaches MAN dates.
• The Active today line, which can be controlled by the administrator via the DI000158 Active today line, does not shift dates planned with MAN.
• Links: take effect until they reach MAN dates. (e.g. for multiple resource planning with MAN and CAP)
  • The impact when one resource is set with MAN and others with different load profiles for Hammock tasks or BLD, is similar to that described above.
    • The dates of the MAN planned resources are not shifted.
• Duration Hammock task or Summary task MAN period
  • Earliest start MAN first date
  • Latest end MAN last date
• In the case of several resources with MAN, the earliest and latest dates of all MAN resources are used to plan the TA.
• Via TA Req. start, the task can only start earlier than the earliest MAN planning.
• As a result of TA Req. end, the task can only start earlier than the latest MAN planning.
• Splitting parameter = Y: The parameter has no effect on MAN resources. For resources not planned with MAN, this parameter has the same effect as before.
• Load records of MAN resources can only be deleted manually.

Details of new behavior for reporting hours

• Planned hours of the MAN load profile that are before the first update report are deleted and not distributed to future loadings.
• Reporting of hours worked with a different value than planned do not affect the other load records.
• Update reports do not change the scheduled hours.
• Hours planned for task resources using the MAN load profile are not shifted by scheduling.

Objective

• Specifically preset loads per day.

Procedure

• The user chooses the MAN load profile for the resource and enters the required loads in the Rem. load field in existing load records. This generates a discrete load distribution. It is also possible to set up new load records.
• Appropriate module designs permit loads to be entered in the Gantt chart, directly below the bars. If the load is being displayed in summary form on a less detailed time scale (e.g. by week), then after the values have been input they are automatically distributed across the individual days.

Example

• The weekly loads below the bars or the daily loads below the resource assignments can be edited.

Typical application in practice:

• Free capacity load distribution across the task duration.
• Manual distribution of loads to achieve capacity adjustment.
• Project meetings on fixed dates

Procedure

• The MAN load profile is set manually for the resource.
• Effort is entered in the Rem. effort field in the load record.
• The old value in the Rem. load of the load record is retained and can be changed manually.
• TAR Remaining effort = the sum of the R load values for all the associated load records, i.e. the loads are cumulated upwards.
• The TA Remaining duration = 0, if an actual end date is set.

• In resource assignments with MAN load profile:
  • If no TA actual start is set:
    • Duration from the first up to the last load record
  • If no TA actual start is set:
    • If no TA actual end is set:
      • Split = No
        • Duration from the first work reporting date up to the last load record
      • Split = No
        • Duration from the first up to the last load record without actual load
    • If TA actual end is set:
      • Remaining duration = 0

Note

• An entry overrides the calculation (not in the case of tasks with subprojects)

Notes

• Date shifts can result in the weekly loads shown under the bar being different from those shown previously. This is because loads are stored to the day but are only shown to the nearest week.
• For MAN resource assignments, no capacity adjustment is carried out. Such tasks are loaded in on an adherense to schedule.

Objective

• To show the behavior of manually scheduled dates in update reporting.

Details

• Planned hours of the MAN load profile which are earlier than the first hour reported are deleted.
• Reporting of hours worked with a different value than planned do not affect the other load records.
• Planned hours that are earlier than the last reported hours are not distributed to future loadings.
• Update reports do not change the scheduled hours.
• Hours planned for task resources using the MAN load profile are not shifted by scheduling.

Notes on duration changes

• Changes to the TA Planned duration or TA Remaining duration has no mutual influence if there are actual dates. The TA Planned duration is retained (initial value for comparison purposes) and the TA Rem. duration is obtained by calculation. If it is required to change the duration of the task, there are two possibilities:
  • Manual entry of new load records, following on from the existing ones. In the next calculation of the schedule, a new TA Remaining duration is determined.
  • Empty the Load profile data field, change the TA Planned duration, CS. After this, specify the new loads.

Notes on redoing manual load requirements

• Clear the Load profile field for the resource planned with MAN and run CS.
• Enter a new load profile and run CS.

BLD Load Profile (Basic Load)

Information

• The Basic load (BLD) load profile can be used to distribute loads evenly across the entire float time of a task. In doing this,
  • the daily load can be specified (via Max. load/day) or
  • the daily load can be calculated from the Remaining effort.
• This load profile is used for resource employment planning for accompanying activities. E.g.
  • basic load tasks (e.g. 1h/day for service activities) or basic load projects
  • project management (e.g. 1 hour/day throughout the entire duration of the project, or 100 hours distributed across the entire project duration)

Peculiarities of the BLD load profile

• If TA Remaining duration is specified, it will be taken into account.
• If a BLD load profile is assigned to a task and no TA Remaining duration is available, the Remaining duration of the task is calculated by the TA Earliest start (= TA Calc. start) up to the TA Latest end (= TA Calc. end).
• If a value is entered in the Max. load/day field, the Remaining effort = Max. load/day * Remaining duration is calculated.
• If a value is entered in the Max. load/day field, the Remaining effort is distributed evenly over the Remaining duration ( Behavior as without load profile: linear load distribution).
• Tasks with a BLD resource assignment will always be planned with adherence to schedule. Capacity adjustment will therefore not be applied to them.
• Resources are not scheduled on their vacation.
• The task can be stretched across the complete project duration if the Hammock task parameter has been activated (e.g. for project management or basic load projects).
  • With the help of links, a Hammock task can be extended across particular project tasks. For example, the link predecessor can be the Project kick-off milestone and the successor can be the End of planning phase milestone. The hammock task will be stretched between these two tasks if it is connected to both tasks by links.

Example 1 Project management task

• For project management, a load of 1 hour/day is planned in over the entire duration of the project. For this purpose, 1 hour is entered in the Max. load/day field, and the Hammock task checkbox is activated.

Example 2 Project management task

• For project management, 100 hours are planned, distributed evenly over the entire duration of the project. For this purpose, no entry is made in the Max. load/day field, and 100 hours are entered in the Remaining effort field and the Hammock task checkbox is activated.

Example construction planning

• For TA KON load-bearing structure, 80 hours are planned over a period of 15 days (Remaining duration).

• If this TA is to use the complete float time, BLD will be used for resource assignment and the Hammock task is activated. The task can now last 38 days instead of 15. This means that the task uses up its buffer completely. Scheduling then ignores the planned duration of 15 days.

• If the predecessor tasks are delayed, the duration of task 2110 will be reduced accordingly.

Example PPMS Standard:

• The project is planned with PR Requested end up to 05/31/09, adherent to capacity
• TA Meeting is a hammock task, resource planning 0,6h/day, BLD load profile

Note on effort oriented planning:

• Without specification of Remaining effort, PPMS can only calculate a duration if
  • TA = Hammock task
  • BLD load profile is used in conjunction with
  • specification of the daily load (Max. load/day)
• The duration of the hammock task is determined by
  • PR Requested end or
  • PR Calc. ED, if it is later than PR Requested end
• The duration of the hammock task can also be influenced by connecting it to a successor TA, which has a defined Requested end, e.g. a milestone with Requested end.

• The duration calculation for effort controlled tasks (here TA 02, 03, 04) is carried out with the help of the following parameters:
  • CAP load profile
  • Daily load (Max. load/day)
  • Remaining effort
• If there are no other restrictions by dates, successor, etc., then the task with the highest effort is calculated first since it has the lowest float.
• In CAP the TA duration only serves to calculate the schedule outline?. I.e. within the calculated duration, the resource is planned where there is availability. If no availability can be found up to the end of the resource calendar, planning is carried out at the earliest possible date after the end of the planning horizon. In the above mentioned example, hence on 06/01/09 (=1 working day after the end of the project)

Planning with Adherence to Total Float and SS Link

Objective

• The duration of a task is extended because of overload, provided that float times are available.

Details

• Planning with adherence to total float
• Two tasks are linked to each other via an SS link.
• Both TA have an FS link to Milestone 1.
• Resources are scheduled with CAP load profile.
• Both tasks are planned with
  • Remaining duration = Calculated by setting effort / available capacity per day

Information

• The float determined by the date scheduling are used.
  • The durations of the task are automatically increased up to the end of the float period only, in order to avoid this overload. In this example, the duration of the TA 01 task is extended up to Milestone MS 1.

• Behavior of the date scheduling
  • Time scheduling determines the earliest and latest dates.
  • The float is always determined on the basis of the difference between earliest and latest start dates or end dates.
  • The latest start date of TA 01 is determined on the basis of Milestone MS 1 and task TA 02. The links are adhered to.
  • If Requested end and Requested start is deleted by MS 1 (link to TA 02 is maintained), then the Requested end of the project function as a float limit.

FAQs on Date Scheduling

Working Time Reporting during Vacation

FAQ - Question/Answer

• Question: Can a resource record working hours for a day on which he/she is really on vacation, i.e. for a day for which Work = N is entered?
• Answer: Yes. Here, Work = N is ignored.

The Effect of Capacity Adjustment on Other Projects

Information

• If the impact on other projects is to be considered in the capacity adjustment, then all affected projects which have a lower priority than the one of interest must be included in the calculations. The Replanning (Calculation of all Planning Objects) does this automatically.

Capacity Adjustment Appears to be Incorrect

FAQ - Question/Answer

• If the results of a capacity adjustment run appear incorrect, or if there are still overloads in the utilization diagrams, this is often merely a problem of visualization since PLANTA project plans on a daily basis and the utilization diagrams are often viewed in weekly format only.
  • Remedy: view the utilization diagrams in daily format.

Inexplicable Overload in Planning with Adherence to Capacity

FAQ - Question/Answer

• A resource shows high overloads even though it is supposed to have been planned in with adherence to capacity. What checks should be carried out?
  • Is the Adjustment by effort code or Adjustment by costs set to Y for the resource? If adjustment is set to N then there will be no capacity adjustment for the resource, but instead the calculations will be planned with adherence to schedule.
  • Do all projects to which the resource is assigned have a priority greater than the value for Adherent to total float up to Priority (see the model parameters)? Projects for which this does not apply will be planned on adherence to schedule or buffer, and may cause resource overloads.
  • Have requested dates or actual dates been entered for any of the tasks to which the resource is assigned? When these are taken into account by the scheduling procedures, they may prevent capacity adjustment. * If the task lies beyond the planning horizon of the resource, the system assumes that there is unlimited capacity, but the loading will nevertheless be defined as an overload.
• Certain tasks may continue to cause overloads although all of the above points are met. What else should be checked?
  • These tasks may lie beyond the planning horizon for the resource. The system then assumes there is then unlimited capacity, but the loading in will nevertheless be defined as an overload.
  • The load (per period) can be so large, that the available capacity is not sufficient in any period.
  • Summary tasks and hammock tasks cause planning of resources with adherence to schedule. This also applies in some cases for structure tasks. For more information, see the corresponding sections.

Example

• For a task with Planned duration of the task = 10 days, an effort of 100 hours is entered. This corresponds to a load of 10 hours/day. For an employee resource, however, the available capacity is only 7.75 h. As a result, the task duration would have to be extended to 13 days.
• Remedy:
  • enter the CAP load profile for the affected tasks in the Resource assignment to task.
    • In planning with adherence to total float, the TA float is used.
    • Set the planning type to Adherent to capacity. As a result, as much capacity as available in the period is used when loading in and the duration is extended for the task until the entire effort is loaded in.
• A resource is loaded in with adherence to capacity, but many gaps remain in which nothing is loaded in. Here, remedial action is taken by entering the CAP load profile in Resource assignment to task. Enter CAP for all resource assignments of the task. This will achieve optimal utilisation of the resource. However, it should be noted that doing this may extend or shorten the prescribed task durations.

Overload with Planning with Adherence to Capacity and Different Load Profiles

FAQ - Question/Answer

• A task loads in resources for different lengths and apparently overloads a resource unnecessarily.

Details

• Planning with adherence to capacity
• Planned duration = 10 days
• Planned effort 100 hours
• No requested dates
• A resource with CAP load profile is loaded in without overload and for longer than 10 days.
• A resource with a linear load profile (i.e. the load profile field is empty) is loaded in for the specified 10 days and is overloaded.
• The following behavior is desired:
  • A resource with CAP is optimized and scheduled without overload.
  • A resource with linear load is also scheduled with overload in accordance with the Planned duration specifications.

Example

• R1 is scheduled without overload from 11/25 - 12/12/08.
• R8 is scheduled and overloaded for the specified duration of 10 days.

Capacity Adjustment and Task Requested Dates

FAQ - Question/Answer

• Tasks are moved by capacity adjustment, although task requested dates are set for successor tasks.
• This is only the case when planning with adherence to capacity with Fix parameter = 0.

Examples

• TA 100 is overloaded.
• Planning with adherence to schedule: TA Requested start is considered. Overload of 42 hours is indicated.

• Planning with adherence to total float TA Requested start is considered as well.

• Planning with adherence to capacity: Capacity adjustment of TA 100 moves TA 200, although the latter has a TA Requested start. The deviation from TA Requested end of TA 100 is indicated as a date delay in the bar for TA 100.

• If a TA Requested start. is set for TA 200 with Fix parameter = 1, the requested date of TA 200 is adhered to. The deviation from TA Requested end of TA 100 is indicated as a date delay in the bar for TA 100.

Unexpected Overload from Planning with Adherence to Capacity with CAP

FAQ - Question/Answer

• In spite of using planning with adherence to capacity with CAP, overloads still appear.
• The following points should be checked in this case.
  • When using planning with adherence to date and total float: All TA Requested start and TA Requested end are deleted. Otherwise, these tasks will be scheduled on an adherence to schedule.
  • Actual dates available? Tasks with a TA Actual start will be loaded in on a date-oriented basis (i.e. their remaining requirements). If appropriate, please work with Split = Y, so that the remaining resource requirement can be subject to capacity adjustment.
  • In the Resource Data Sheet, set Adjustment = Y for the respective resource.
  • Check the planning horizon. Ensure that resource periods have been set up for all the periods where capacity adjustment is to be applied. This is carried out in the Start period and End period fields in module 001343 Resource Data Sheet. There is no availability data and thus no adjustment for period for which period records are no longer available. But: do not make the planning horizon excessively long (e.g. 4 years). This costs unnecessary computation time, but usually does not yield any results of practical value.
  • Check the available capacity: Where appropriate, use Max. load/day in the resource assignment for a task to ensure that a 'mammoth task' does not tie up an employee's entire capacity for week after week, but only imposes a load of, say, 3 hours per day.
  • When planning with project structures: The project priorities must be set for subprojects in a way that causes them to be scheduled with adherence to capacity.
  • Sched. late for tasks to be calculated with adherence to capacity can deliver results in capacity scheduling which differ from those delivered by the Schedule early standard parameter and should therefore be avoided.

Task Requested Dates are Ignored

FAQ - Question/Answer

• The tasks are not planned at the TA Requested start which is earlier than today’s date.

Details

• The project has no Requested start.
• The task has a Requested start that is before today’s date.
• The task is scheduled from today’s date and before the TA Requested start.
• Background: Scheduling starts the calculation from the PR Requested start and if this does not exist, as of the earliest realistic date, today’s date.

Example

• TA Requested start 10/08/08
• Calc. start is the current date, 10/23/08

Notes

• Via the Fixing parameter = 1, the effect of the today line can be switched off, i.e. the task is scheduled for the task requested date in the past.

Planning of the Resource is far Beyond the Requested Dates

FAQ - Question/Answer

• In planning with adherence to capacity, a resource with overload is planned far outside the requested dates.

Details

• A special case for multi-calendar calculation with different non-working days for task and resource.
• Parameters:
  • Planning with adherence to capacity
  • PR Requested start/Requested end is preset
  • TA Requested start / Requested end, and Planned duration are not preset.
  • A resource with a linear load profile is assigned to the task.
  • The normal company calendar has defined the period from Good Friday 04/10/09 up to and including Easter Monday 04/13/09 as non-working days.
  • The resource
    • has only defined the period from Mar. 26 up to and including March 28th, 2005 as non-working days.
    • is planned with a Planned duration of 10 h.
    • has not yet been scheduled for all of March.

Examples

• There is no Planned duration preset for the task, therefore scheduling assumes one day as the value for the Planned duration and Remaining duration.
• The resource is scheduled on two days outside the project requested dates on 04/10/09 and 04/14/09, as the task does not have any requested dates. In this case, the project requested date is used for information only.
• Scheduling copies the working days of the company calendar for the calculation of the TA Remaining duration. This indicates only one working day for the period from Good Friday 04/10/09 up to and including 04/13/09.
• The resource a preset Planned duration of 10 h. The work cannot be completed on one day with a specified daily availability of 7.2 hours. The resource is scheduled on the basis of the resource calendar and can work for two days in the aforementioned period from Good Friday from Good Friday 04/10/09 up to and including 04/13/09., while the company calendar-dependent task only indicates the duration of one day.
• As a result, the
  • task duration one working day as per company calendar and
  • resource planning without overload restrictions are met.
• This behavior is desired for the multi-calendar calculation. Different resources have different availabilities and are planned accordingly.

Note

• If this behavior is not desired, a requested date or sufficient Planned duration can be set for the task. In this case, date scheduling is based on this data when planning resources.

Capacity Adjustment and Maximum Links

FAQ - Question/Answer

• When capacity adjustment is applied, it can happen that maximum links are ignored.
• This is a topic which is currently the subject of research for the definition of results at universities.

Inexplicable Float when Planning with CAP

Problem

• After capacity scheduling, a project has an inexplicable float.

Details

• After date scheduling, the latest end dates of the tasks are after (later than) the requested end date of the project,
• Capacity dates are earlier than the PR Requested end.

Cause

• This problem only arises in planning with CAP load profile if date scheduling has already resulted in an overrun of the PR Requested end. The subsequent use of CAP planning can cause the TA durations, and hence the entire project, to be shortened to such an extent that it eventually becomes possible to meet the PR Requested end, on the basis of the capacity available.
• If the Earliest start / Earliest end bar is made visible from the Invisible window and a time scheduling is carried out, this behavior becomes evident.

Notes

• Capacity scheduling applies the earliest and latest dates from date scheduling as key dates for capacity adjustment. Capacity adjustment recalculates the durations, which may be shortened and may thus bring forward the times/dates, which can then result in buffers that are not immediately identifiable.

Example

• For a TA Planned duration of 10 days and Planned effort = 16h (with CAP), date scheduling will start by assuming a 10 day throughput time. However, if it is possible to plan the 16 hrs into 2 days, the duration will be reduced by 8 days, and an additional buffer of 8 days would then be indicated.

Remedy

• Instead of using TA durations and CAP, it is better to only use CAP with max. load. If, as in the above example, 16h are to be distributed over 10 days, it is more expedient to set Planned effort = 16 and max. load = 1,6 and Planned duration = 0.

FF Links and Capacity Adjustment

Problem

• If in planning with adherence to capacity, 2 tasks are connected by an FF 0 link, they will be treated as FS 0, if
  • the successor task has a resource with the CAP load profile
  • the successor has a TA Planned duration = 0.

Cause

• Movement of the successor due to capacity adjustment
• The CAP load profile requires an initial duration for the adjustment. This duration is usually the TA Planned duration.
• For an FF link, the following calculation is performed:
  • Detect the end date (Earliest end) from the end date of the predecessor.
  • Detect the start date (Earliest start) from Earliest end duration.
  • If duration = 0, this means that Earliest start = Earliest end
• Capacity adjustment with CAP load profile now carries out the adjustment by working forwards from this ESD.

Work-around

• The successor has a TA Planned duration = 0.

Notes

• An FF link conflicts with planning with adherence to capacity, because a task which is loaded with adherence to capacity may be delayed or stretched out (CAP) up to the end of the planning horizon, and does not have to finish at the time implied by the FF link.
• Under the conditions set out above, only an SS or SF link is meaningful; these result in the following calculation. E.g. SS:
  • Earliest start successor = Earliest start predecessor
• Capacity adjustment starts from the Earliest start and moves or stretches the task to achieve a complete adjustment, regardless of the predecessor task’s end date.

Processing of Regular Projects/Basic Load Projects

FAQ - Question/Answer

• How can I effect that
  • regular projects are processed in good time.
  • Basic load projects are treated subordinately.

Details

• Initial situation:
  • The tasks of the projects are planned in good time with Planning early
  • Basic load projects
    • have a load from 01/01 to 12/31 of the respective year
    • the tasks are planned with Planning late with adherence to capacity
    • The resources have the CAP load profile
  • As a result, the resources at the end of the year are completely planned, and resources are not planned between today’s date and the end of the year.

Example

• It is desired that the basic load is loaded evenly and without overload instead of being loaded all at once at the end of the year.

Example

Information

• The CAP load profile in connection with the Planning with adherence to capacity planning strategy enables the load of the resources with respect to their capacities.
• Here, PLANTA is oriented towards the available capacity of the resource.
• The Linear load load profile loads the resources with the same number of hours per, however, it is not used for load adjustment. For this reason, it is not suitable for the Load without overload requirement.

Procedure

• An option for solving the above mentioned requirement is the following:
  • The regular projects are planned as before.
  • The basic load project(s) is (are) planned with:
    • Planning early
    • Planning with adherence to capacity
    • Lower project priority than the regular projects in DI001015 PR Prio.
    • The tasks receive no Planned duration.
    • The resources receive a maximum load per day, e.g. 4 hours

Example

• Due to the higher project priority of the regular projects are loaded first. The basic load project and its tasks are only loaded later.
  • Possibly, the resources will not be loaded at the end of the year.
  • If you move / extend the regular projects, the basic load project is also moved:

Example

• If there are still remaining capacities available after you have planned the regular projects, then they are used up to the defined maximum load per day by the basic load project.
• Planning with adherence to capacity prevents overloads. The requested date of the basic load project is possibly overrun. As a result, the resource planning which is too high becomes visible and respective measures can be derived, e.g. to increase the maximum working time per day for the tasks of the basic load project or move tasks to the following year.

Example

Moved Loadings

Problem

• For the periods of a resource assignment, recorded hours are loaded at a wrong point in time.

Cause

• The system calendar and the resources have different start periods. Recommendation: The system calendar starts earlier and ends later than the resource calendar. The system calendar should start no later than from the date of the first posting.
• It has occasionally happened that an incorrect loading-in date was determined due to the deviating number of resource and calendar working periods.

Work-around

• If this problem arises, correct loading in can be achieved by setting the same date for start periods of the system calendar and of the resources.

Negative Load in the Utilization Diagram

Details

• In utilization modules, the utilization diagram starts below the zero line for individual resources.
• If the Summarize periods resource parameter = Y, the negative utilization of the resource or a child resource is retained, even though load records with a negative actual load were deleted.

Example

Cause

• Software

Procedure/Workaround

• Open the required resource in the Resource Data Sheet module.
• Change parameter Summarize periods to N
• Save.
• Change parameter Summarize periods to Y
• Save.
• Carry out a replanning.
• Close PPMS and then open it again:

Behavior of TA Update Report Date After Deletion of TA Actual ED

Details

• If an Actual end is removed, scheduling initializes the date for update reporting and then recalculates it.
• The date for work reporting is determined from the maximum from Actual start and the last work reportings of the resource assignments.

Example

• Initial situation

• Task 1 now receives a TA Actual start and a TA Actual end. Result of scheduling

• If the TA Actual end is emptied, scheduling has the following results:
  • The date for update reporting is deleted and the task is given a remaining duration of 7 days according to the actual duration.

Planning of TA Calc. SD by milestones

Details

• Successor tasks start on the day of the Predecessor calc ED if:
  • Duration = 0
  • TA Requested end not set.
  • Link time interval = 0

• Successor tasks start on the day of the _Predecessor calc ED + 1 if the following applies to the successor task:
  • Duration = 0
  • TA Requested end is set.
  • Link time interval = 0
  • or
  • Duration > 0
  • Link time interval = 0

Incorrect Calculation of the Level Field

Problem

• Different calculation of the Level field.

Details

• If project structures are manipulated in a module, and if then a scheduling run is performed in this module, the levels may not be calculated in the correct sequence.

Cause

• As part of the scheduling procedures, the software always carries out a sort by level and PR Requested end. As neither a level nor a PR Requested end exists is available for the subprojects, the projects are potentially not sorted and calculated individually in the usual sequence at first. This leads to the determination of a different level.

Work-around

• After the 2nd scheduling run and each subsequent one, the levels will be calculated correctly.
• If the calculations are done in a module which only performs them for the main project, e.g. the project data sheet module, the levels will be determined correctly as well.
• In the case of complete replanning, the levels will also be determined correctly.

Note

• This behavior can lead to different analyses, if report details are selected or sorted using the Level field.

Sched. Early = N Has no Effect on Tasks with Subprojects

Problem

• Planning early = N has no effect on tasks with subprojects.

Cause

• In the case of tasks with subprojects, the duration and position of the task is defined by the subproject. If, for example, a task has a TA Requested start in the subproject, then this TA Requested start should be adhered to. However, this contradicts to the idea < with the intention of Planning early = N in the parent task. Consequently, a parent task will always be planned with Planning early = Y.

Work-around

• Each task can be forced into the late position by having a predecessor for which Planning early = N is set. To do so, you can e.g. create a milestone task with Planned duration = 0, Planning early = N and a link: FS time interval = 0 to the task which is to be planned late.
• The same effect can be achieved by setting Planning early = N for all the tasks in the subproject which have no predecessors.

Notes

• Once a subproject has been started (i.e. there is an entry for its PR Actual start), the effect of Planning early = N can again be forced by splitting the task.
• Requested dates for a task in the subproject will again disrupt any attempt to move the project to the latest possible dates.

Set Project Status 9 for Archiving

Objective

• Optimum representation of costs and effort when projects or subprojects receive PR status 9 Projects to be archived.

Notes

• All dependent projects and subprojects are to be set to status 9 at a particular point in time.
• If this is not possible, only projects that do not have any active subprojects are to be set to status 9.
• It is advisable to first calculate the whole project before setting it or its subprojects to status 9 after unloading. This updates the cost and effort data to the current situation.