The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

Overload Calculation

Initial situation

  • A resource has a maximum capacity of 8 hours per day. There are two projects which load this resource in the following way:
Date Project 1 load Project 1 covered Project 1 overload Project 2 load Project 2 covered Project 2 overload
2/1/2020 8 8 0 8 0 8
2/2/2020 8 5 3 7 3 4

Behavior from S 39.5.28

Information
  • An additional field has been implemented in DT468 (DI065353 Overload) which contains information on the cumulated overload of all projects which load the resource on a particular day. If then an individual scheduling of a project is carried out, the cumulated overload from the project which has just been created contained in the new field is reduced and thus the correct (previously contained) overload is displayed in the project.

Details

  • Initial situation as set out above
  • The respective status for the resources in DT468 is as follows:
Date Maximum capacity Load Overload % utilization
2/1/2020 8 16 8 200
2/2/2020 8 15 7 193,75

  • If you only carry out an individual calculation for project 1, an unloading is carried out internally by the date scheduling, which, however, now also includes a reduction of the cumulated overloads by the overloads of project 1.
Date Maximum capacity Load Overload % utilization
2/1/2020 8 8 8 200
2/2/2020 8 7 4 193,75

  • It can be derived from this, that all yet existing loads of other projects cause an overload on 2/1/2020 (load = overload), i.e. That no other project has covered capacity on 2/1/2020. Hence project 1 disposes of the entire capacity of the resource on this day (8 hours). On 2/2/2020, all other projects load the resource with 7 hours, causing an overload of 4 hours. On 2/2/2020, 3 hours of capacity are already covered and are no longer available for project 1. The available capacity on this day would then be the maximum capacity (8h) - covered capacity (7-4), hence 5 hours.
  • After individual scheduling, we thus receive the following result:
Date Project 1 load Project 1 covered Project 1 overload Project 2 load Project 2 covered Project 2 overload
2/1/2020 8 8 0 8 0 8
2/2/2020 8 5 3 7 3 4

Behavior up to S 39.5.28

Details

  • Initial situation as set out above
  • The respective status for the resources in DT468 is as follows:
Date Maximum capacity Load % utilization
2/1/2020 8 16 200
2/2/2020 8 15 193.75

  • Now an individual calculation is carried out for project 1. In the course of this, this project is first unloaded in scheduling (internally), so that in DT468 only the loads of all other projects (here: Project 2) exist. As a result, DT468 will look like this:
Date Maximum capacity Load % utilization
2/1/2020 8 8 100
2/2/2020 8 7 93.75

  • Here in the data of DT468, it is not apparent that project 2 only disposes of part of the capacity (or no capacity at all on 2/1/2020) of the resource and overload was created for the remaining loads. It is therefore assumed that all capacities have been loaded completely and only have one hour left on 2/2/2020, and no capacity at all on 2/1/2020.
  • Starting from that, project 1 is now planned, which leads to the following result:
Date Project 1 load Project 1 covered Project 1 overload Project 2 load Project 2 covered Project 2 overload
2/1/2020 8 0 8 8 0 8
2/2/2020 8 1 7 7 3 4

  • It can be recognized that too much overload is created while neither project nor resource data have changed.

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl