Skip to main content
Skip table of contents

Scheduling: Use Cases

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 Load profile data field is empty).

  • If the parameter settings deviate, the results may vary accordingly.

Overview and short description of application cases:

No.

Use case

Result

1

Planning with Adherence to Schedule with Several Resources

  • Task with several task resources

  • The Planned duration of the task is predefined.

  • Planning type = adher. to schedule

  • Scheduling carries out the planning along the duration of the task.

  • Scheduling does not prevent overload.

  • Overload will be indicated.

2

Planning with Adherence to Total Float with Several Resources

  • Task with several task resources

  • The Planned duration of the task is predefined.

  • Planning type = adher. 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 not used to compensate possible overload. If there is not sufficient float, resources will be overloaded

  • Resource 1 with overload: Float is used

  • Resource 2 with 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 predefined.

  • Planning type = adherent to capacity

  • Scheduling plans the task without taking the Planned duration of the task into account.

  • Resources are not overloaded.

  • The float of the overloaded resource is used:

  • Resources are not scheduled during non-working days.

4

Resources with Vacation, Planning with Adherence to Schedule

  • Resources with vacation

  • Linear load

  • The duration of vacation is shorter than the task duration.

  • Planning type = adher. to schedule

  • Scheduling carries out the planning block-wise.

  • Scheduling does not plan the resource during its vacation period.

  • On working days, the resource will possibly be planned with overload.

5

Resources with vacation > Task duration, Planning with adherence to schedule

  • Resources with vacation

  • Linear load

  • The duration of vacation is longer than the task duration.

  • Planning type = adher. to schedule

  • The planning is scheduled before or at the start of vacation.

  • The effort is displayed as overload due to the unavailability of the resource on vacation.

  • If the entire task lies within the vacation period, it will be loaded at the calculated start date of the task.

6

Planning with Adherence to Total Float with Vacation

  • Vacation is entered for a resource.

  • Linear Load Profile

  • The duration of vacation is shorter than the task duration.

  • Planning type = adher. to total float

  • Outside the vacation period scheduling carries out the planning block-wise.

  • Available float is used. If the float is exhausted, scheduling will overload the resource.

  • Resource is not planned during its vacation period.

  • The planning is not splitted.

7

Planning with Adherence to Capacity with Vacation

  • Vacation is entered for a resource.

  • Linear Load Profile

  • The duration of vacation is shorter than the task duration.

  • Planning type = adherent to capacity

  • Outside the vacation period scheduling carries out the planning block-wise.

  • Resource is not planned during its vacation period.

8

Planning with adherence to total float with Requested end and Fixing = 0

  • Task with several task resources

  • The Planned duration is predefined.

  • Requested end on a task

  • Set the Fixing parameter = 0

  • The vacation of a resource is shorter than the task.

  • Planning type = adher. to total float

  • Scheduling plans the task on its Requested end.

  • When setting Fixing = 0, the Requested end is exceeded if necessary.

  • No consideration of float and possible overload since the specification of a Requested end causes loading with adherence to schedule.

  • The task is not moved.

8.1

Planning with adherence to total float with Requested end and Fixing = 1

  • Scheduling plans the task on its Requested end.

  • When setting Fixing = 1, the Requested end is adhered to and the task is loaded with adherence to schedule.

  • Float and overloads are not taken into account.

  • The task is not moved.

8.2

Planning with adherence to Requested start on the resource assignment
Task with several task resources

9

Planning with adherence to capacity with Requested end and Fixing = 1
Task with several task resources

  • The fact that the Fixing parameter is set = 1 causes the task to be loaded with adherence to schedule.

  • The task is not extended or moved. Overloads may occur.

10

Planning with adherence to schedule of a task with predecessor, Requested start and Fixing = 0

  • Vacation is entered for a resource.

  • Linear Load Profile

  • The duration of vacation is shorter than the task duration.

  • Task with predecessor and Requested start, Fixing = 0

  • Planning type = adher. to schedule

  • The task does not start at the Requested start but after the predecessor has ended.

  • The vacation of the resource is taken into account.

  • Remaining duration= Planned duration

11

Planning with Adherence to Total Float with Effort > Availability

  • Task with several task resources

  • The Planned duration is predefined.

  • The capacity needed for the required duration exceeds the available capacity.

  • Planning type = adher. to total float

  • Scheduling exploits available float.

  • If no more float is available, the task is planned block-wise at the latest possible point in time.

12

Planning with Adherence to Capacity with Effort > Availability

  • Task with several task resources

  • The Planned duration of the task is predefined.

  • The capacity needed for the required duration exceeds the available capacity.

  • Planning type = adherent to capacity

  • Scheduling exploits available float. Scheduling is postponed until the block can be loaded in. The project end date is possibly exceeded.

  • The resource is not planned during its vacation, the task is not splitted

13

Planning with adherence to total float of a TA with predecessor, Requested end and Fixing = 0

  • Vacation is entered for a resource.

  • Linear Load Profile

  • The duration of vacation is shorter than the task duration.

  • Task with predecessor and Requested start

  • Fixing task parameter = 0

  • Planning type = adher. to total float

  • The task does not start at the Requested start but after the predecessor has ended.

  • The vacation of the resource is taken into account.

  • Remaining duration = Planned duration

  • Float is not exploited since a task with date is always automatically loaded with adherence to schedule.

14

Planning with adherence to total float of a TA with predecessor, Requested end and Fixing = 0

  • Vacation is entered for a resource.

  • Linear Load Profile

  • The duration of vacation is shorter than the task duration.

  • Task with predecessor and Requested start

  • Fixing task parameter = 0

  • Planning type = adherent to capacity

  • The task does not start at the Requested start but after the predecessor has ended.

  • The vacation of the resource is taken into account.

  • Remaining duration = Planned duration

  • Float is not exploited since a task with date is always automatically loaded with adherence to schedule.

15

Calc. start for reporting of several task resources

  • Plan several resources for a task and record hours:

  • as planned

  • earlier than planned

  • later than planned

  • Scheduling plans the resources with their remaining effort from the TAR Actual start on.

  • If the day following the Actual start date is a non-working day, the resource will be scheduled for the next working day.

  • The resource will possibly be overloaded.

16

Reporting on Vacation

  • Several resources are assigned to a task.

  • A resource is on vacation during the entire task duration but he/she reports actual hours worked.

  • Scheduling of resources without vacation is carried out in accordance with standard specifications.

  • The resource who has reported during vacation is scheduled for the first working day following the reporting period.

  • The resource will possibly be overloaded.

17

Task with a resource

  • The resource is on vacation from start to finish of the task

  • Planning type = adher. to schedule, adher. to capacity, or adh. to total float

  • Linear load profile (empty load profile)

  • The resource is unavailable during the entire task duration

  • Scheduling plans the entire remaining effort on the first day of the task duration

  • Depending on the load type, the following behavior results:

    • BLD (Load equals Actual effort/Max. load/day): It is only planned up to the maximum daily load. The rest remains untouched.

    • CAP (adher. to capacity): The remaining effort is planned → this leads to heavy overload on the following day.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.