The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>AnwendungsFunktionen >DateScheduling

Date, Resource Scheduling and Cost Planning

Please note

  • The functionality of date and resource planning and scheduling in PLANTA has not changed essentially compared to previous PPMS releases. In order to gain profound knowledge of this and other topics, see the documentation under Date, Cost, Resource Scheduling and Cost Planning 3.8.0.5.
    • The program depictions used here refer to the software status of version 3.8.0.5 and are to be regarded functionally only. We make every endeavor to make a current version of this documentation available to you as soon as possible.
  • A description of cost planning and scheduling for PLANTA project releases up to 39.5.0 can be found under Cost and Budget Planning up to DB 39.5.0.

Basic Terms of Scheduling

Date scheduling For description, see here
Time scheduling For description, see here
Planning horizon For description, see
here here
Planning horizon is one of the key terms of scheduling and describes the period in which resources are available for scheduling in projects. The planning horizon of a resource is defined with the Start period and End period parameters in the Resource Data Sheet module.
Capacity scheduling For description, see here
Capacity adjustment For description, see
here here
Information
  • In capacity scheduling, the resources are planned according to their availability. This may lead to date delays. The most important parameters that enable capacity adjustment are:
  • Capacity scheduling uses the earliest and latest dates as key dates for capacity scheduling. As a result of capacity scheduling, the durations and dates are recalculated and can be shortened or extended.
  • During capacity adjustment, the capacity scheduling tries to only load the source up to the Max. load/day value within the available duration. If this is not possible, the remaining effort is loaded equally throughout the available duration, also if this causes periods to be overloaded.

Details when using the CAP load profile
  • The Max. load/day value is a requested limit which may be exceeded if necessary.
  • If no Max. load/day has been set, the whole available capacity can be scheduled.
  • An overrun of the Max. load/day limit is not yet an overload, since an overload is only detected on the basis of the available capacity of a resource. Only if the availability is overrun, the resource has overload.
  • The capacity scheduling works with the Max. load/day parameter as follows:
  • The duration of the capacity adjustment used in the capacity scheduling is calculated from Effort/ Max. load/day.
  • This duration is the initial value for capacity scheduling.
  • During capacity adjustment, capacity scheduling tries to only load the resource up to the Max load/day value within the calculated duration. If this proves to be impossible, the remaining effort will be loaded uniformly throughout the available interval, even if this causes the resources to be overloaded in these periods.

Example: Planned effort of the resource assignment = 100, Max. load/day = 5
The capacity scheduling calculates the duration of the resource assignment as follows: 100/5 = 20 days. This is the base for further calculation (capacity adjustment, etc.)
In the following constellations, no capacity adjustment takes place, even if the checkbox is activated.
  • Tasks with a BLD resource assignment are always planned with adherence to schedule. No capacity scheduling is done for them.
  • Resources with Man load profile are loaded with adherence to schedule. No capacity scheduling is done for them.
  • Task requested dates prevent capacity adjustment for the respective task, provided that Requested start and/or Requested end are entered on the task. They take priority over the Planning early parameter, which means that the task is loaded with adherence to schedule and total float. In the case of planning with adherence to capacity with load profile CAP, the task may be extended if there is an overload.
  • For tasks with Fix parameter on the task
  • For tasks with Actual start or Actual end, no capacity scheduling takes place. If you want the rest of a task that already has an Actual start to be adjusted after all, it must be splitted. This is done by activating the Splitting parameter.

The capacity adjustment for tasks with deactivated Planning early checkbox is done reversely, i.e. starting with the Latest start / Latest end of the task toward the Earliest start / Earliest end of the task.
If the effort specified for a task is so high that it cannot be planned in any period, then the Adjustment limit parameter comes into effect.
Planning strategies For description, see
here here
PLANTA project distinguishes three planning strategies:
  • planning with adherence to schedule: Tasks are loaded in without regard for the availability of capacity or any tasks which have already been loaded in. No capacity adjustment takes place.
  • planning with adherence to total float: If there is insufficient capacity for a task, it may be moved around within its total buffer time. If sufficient free capacity is available, the task is loaded. If not, the task is loaded in at the latest possible dates (TA LSD/LED). The project end date (PR Req. end or PR LED) will not be overrun due to capacity shortage.
  • planning with adherence to capacity: A capacity shortage will cause tasks to be moved until sufficient free capacity is available. The PR requested ED is not taken into account.

The planning strategy is set by the planning type project parameter.
An important factor for capacity adjustment is the remaining capacity per day. It is calculated from the avail. capacity * Load limit % - Util.
Remaining capacity is available capacity which has not yet been planned.

Calculation Matrix for Dates, Costs, and Budgets in PLANTA project 39.5

Module Action Calculation
Schedule (Project) Scheduling button in the menu bar or the menu item of the same name DS + CS + BRRC
Budget (Project) Recalculate button DS + BS + CoS + BRRC
Status Create baseline, Create status report, Create final report buttons DS + BS + CoS + BRRC
Portfolio Update portfolio button BS + CoS + BRRC
Portfolio Period Update portfolio button BS + CoS + BRRC
Portfolio Status Reports Create status report button Summarization project status reports
Schedule (Program) Scheduling button in the menu bar or the menu item of the same name DS + CoS + BRRC
Budget (Program) Recalculate button DS + BS + CoS + BRRC
Status Create baseline, Create status report, Create final report buttons DS + Summarization project status reports
Replanning Replanning button
Replanning incl. portfolios button 		DS + BS + CoS + BRRC
DS + BS + CoS on portfolio yearly tranches + BRRC
Legend:
Calculation type Variant Subvariant CalculationSorted ascending
BRRC     Calculation benefit, revenues, risks, opportunities
CoS = Cost scheduling From resource (manual = 0)
From years (manual = 1) 		  Summarization costs from resource utilization to CTGr/year and CTGr/Project
Summarization from year/CTGr to project/CTGr
BS = Budget scheduling Project
Portfolio
Program 		  Summarization years to project and TPR on parent projects
Summarization project years to portfolio
Summarization: Projects to program
DS = Date scheduling Manual cost planning = 0


Manual cost planning = 1 		CS + CP = Capacity scheduling with cost planning = 1
CS + CP = Capacity scheduling with cost planning = 0 		Time scheduling + Capacity scheduling + Cost scheduling + BRRC
Time scheduling + Capacity scheduling + BRRC

Time scheduling + Capacity scheduling + BRRC
Attachments Attachments
Topic attachments
I Attachment History Size Date Comment
Pngpng Grundlast.png r1 22.9 K 2013-03-26 - 17:59  
Pdfpdf L0472-00002579.pdf r1 5032.1 K 2010-08-05 - 13:22  
Pdfpdf TerminRechnung.pdf r1 5032.1 K 2012-05-11 - 10:52  

         PLANTA project







 
  • Suche in Topic-Namen

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