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

Skill Requests MOD009BLA New from DB 39.5.0

Access path

Information

  • In this module, the planning of the resources is displayed sorted by skills. The effort of the individual resources can be replanned or reallocated.
  • If particular skills are planned in projects as resources (so called skill requests), such skills are displayed here as well and their effort is distributed to the individual employee resources.

Access rights
  • Only skills and resources are displayed which the current user is allowed to see according to his/her access rights.
    • This means that the user may have access to a particular skill but not to all resources of this skill. Then only resources which the user is allowed to see are displayed.
    • If the user has access to a particular skill, neither this skill nor the resource assigned to the skill are displayed in the Resources module, even if the user has access to the resource.

Details

  • After opening the module, the required skill must be selected from the listbox. All resources assigned to the skill are grouped by the Primary skill attribute.
  • The utilization diagrams (histograms) show the utilization of the resources by project code. On skill level, the accumulated utilization of all resources assigned to this skill is displayed.
  • The resource utilization is compared in the utilization diagram, the resource utilization is compared with the resource availability (see Legend).
  • The number area below the resource diagrams shows:
    • the planned utilization in % (line 1),
    • the planned utilization in absolute numbers (line 2),
    • the available capacity (line 3).
      • All number specifications are summarized specifications (selected resource + all of its child resources), just like the diagram itself.
      • There is a traffic light implemented on the field with the percentage utilization which switches to red as soon as the overload has been detected (utilization over 100%) (see Legend).
  • You can switch to the Dashboard or Task modules by clicking on the link in the Project or Task fields.

From DB 39.5.12

Distribute resource planning
  • Select the source resource (the resource the effort of which is to be reduced) and expand the tree structure.
  • All projects and tasks for which this resource is scheduled are displayed.
    • The tasks are displayed sorted by their calculated end dates (Calc. end).
  • For the required project, add a new resource to which the effort from the source resource is to be distributed. To do so,
    • right-click on the project and select the Insert New resource context menu command. or
    • click on the plus button.
      • Select the target resource from the listbox in the inserted line in the Resource name field.
        • If you are authorized to access the resources of other departments (controlled via the Resource access parameter), these resources are also available as target resources in the current resource listbox.
  • Enter the effort value to be distributed in the To be distributed field.
  • Click on the Distribute effort button (the button is located at the bottom of the module).
  • Confirm the Distribute resource effort? message with Yes.
  • The effort values of the source and target resource are changed.

Up to DB 39.5.12

Distribute resource planning
  • Select the source resource (the resource the effort of which is to be reduced) and expand the tree structure.
  • All projects and tasks for which this resource is scheduled are displayed.
    • The tasks are displayed sorted by their calculated end dates (Calc. end).
  • For the required project, add a new resource to which the effort from the source resource is to be distributed. To do so,
    • right-click on the project and select the Insert New resource context menu command. or
    • click on the arrow button Pfeile.PNG. (The arrow button is located next to the task name).
      • Select the target resource from the listbox in the inserted line in the Resource name field.
        • If you are authorized to access the resources of other departments (controlled via the Resource access parameter), these resources are also available as target resources in the current resource listbox.
  • Enter the effort value to be distributed in the To be distributed field.
  • Click on the Distribute effort button (the button is located at the bottom of the module).
  • Confirm the Distribute resource effort? message with Yes.
  • The effort values of the source and target resource are changed.

Notes

From S 39.5.23

  • NEW Currently, the distribution of the effort from a resource with a PM_Load profile can only be carried out manually in the Schedule module.
  • If the value to be distributed is too high, the following message appears: The initial value to be distributed has been exceeded.
  • After distribution, the module is refreshed and the current values are displayed.
  • If you mark one or several tasks, only the effort of the resources of the marked tasks is distributed.
  • In the task line in the Remaining effort, Actual effort, Calc. start, and Calc. end, the efforts and dates of the resource assignment are displayed.

Up to S 39.5.23

  • If the value to be distributed is too high, the following message appears: The initial value to be distributed has been exceeded.
  • After distribution, the module is refreshed and the current values are displayed.
  • If you mark one or several tasks, only the effort of the resources of the marked tasks is distributed.
  • In the task line in the Remaining effort, Actual effort, Calc. start, and Calc. end, the efforts and dates of the resource assignment are displayed.
  • Legend: Histogram

    From DB 39.5.15

    Symbol Meaning Color Comment
    CodeADB14.png Planned load (remaining load) of the resource(s) in projects The color of the bar is determined by the code of the projects.
    CodeADB14.png Code A
    CodeBDB14.png Code B
    CodeCDB14.png Code C
    CodeDDB14.png Code D
    CodeEDB14.png Code E
    The code is defined in the Project Core Data module of the respective project.
    The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
    ActDB12.png Actual load of the resource(s)   The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, in turn stem from the working time recording of the resources (DT472).
    KapLinieDB15.png Available capacity of resource(s)   The values for histogram bars are calculated from the Available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
    The limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
    GrundlastLinieDB15.png Basic load of resource(s)   The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet.
    The limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.

    From DB 39.5.14

    Symbol Meaning Color Comment
    CodeADB14.png Planned load (remaining load) of the resource(s) in projects The color of the bar is determined by the code of the projects.
    CodeADB14.png Code A
    CodeBDB14.png Code B
    CodeCDB14.png Code C
    CodeDDB14.png Code D
    CodeEDB14.png Code E
    The code is defined in the Project Core Data module of the respective project.
    The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
    ActDB12.png Actual load of the resource(s)   The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, in turn stem from the working time recording of the resources (DT472).
    KapLinieDB14.png Available capacity of resource(s)   The values for histogram bars are calculated from the Available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
    The limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
    GrundlastLinieDB14.png Basic load of resource(s)   The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet.
    The limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.

    From DB 39.5.12

    Symbol Meaning Color Comment
    CodeADB12.PNG Planned load (remaining load) of the resource(s) in projects The color of the bar is determined by the code of the projects.
    CodeADB12.PNG Code A
    CodeBDB12.PNG Code B
    CodeCDB12.PNG Code C
    CodeDDB12.PNG Code D
    CodeEDB12.PNG Code E
    The code is defined in the Project Core Data module of the respective project.
    The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
    IstHisto.png Actually incurring load (actual load) of the resource(s)   The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
    KapLinie.png Available capacity of the resource(s)   The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
    NEWThe limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
    GrundlastLinie.png Basic load of resource(s)   The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet.
    NEWThe limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.
    Faktor4.png Factor 4 of resource(s)   The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
    Faktor5.png Factor 5 of resource(s)   The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

    From DB 39.5.8

    Symbol Meaning Color Comment
    CodeHisto.png Planned load of the resource(s) in projects The color of the bar is determined by the code of the projects.
    A.png Code A
    B.png Code B
    C.png Code C
    D.png Code D
    E.png Code E
    The code is defined in the Project Core Data module of the respective project.
    The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
    IstHisto.png Actually incurring load (actual load) of the resource(s)   The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
    KapLinie.png Available capacity of the resource(s)   The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
    NEWThe limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
    GrundlastLinie.png Basic load of resource(s)   The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet.
    NEWThe limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.
    Faktor4.png Factor 4 of resource(s)   The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
    Faktor5.png Factor 5 of resource(s)   The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

    Up to DB 39.5.8

    Symbol Meaning Color Comment
    CodeHisto.png Planned load of the resource(s) in projects The color of the bar is determined by the code of the projects.
    A.png Code A
    B.png Code B
    C.png Code C
    D.png Code D
    E.png Code E
    The code is defined in the Project Core Data module of the respective project.
    The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
    IstHisto.png Actually incurring load (actual load) of the resource(s)   The values for the histogram bar are taken from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
    Kap.png Available capacity of resource(s)   The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
    GrundlastAbDb8.png Basic load of resource(s)   The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load value defined for the resource in the Resource Data Sheet.
    Faktor4.png Factor 4 of resource(s)   The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
    Faktor5.png Factor 5 of resource(s)   The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

    Legend: Bar diagram (project/proposal/resource)

    From DB 39.5.14

    Symbol Meaning Color Comment
    WunschDB14.png Task requested dates   Requested start and Requested end of a task are defined in the Schedule module.
    KalkPRVGDB14.png Calculated dates of the selected resource for the selected task in the selected project Upper bar part:
    The color of the bar is determined by the code of the respective project
    For the meaning of the individual code colors, see the histogram legend.

    Lower bar part:
    KalkDB12.PNG Uncritical task
    CalcCritDB12.PNG Critical task
    Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.




    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
    ActDB12.png Calculated dates of the selected resource for the selected task in the selected project The bar is white hatched. Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the working time recording of the respective resource (DT472) or edited manually.
    Puffer.png Latest task dates   Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if Calc. end of a task is later than its Latest end.

    From DB 39.5.12

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task are defined in the Schedule module.
    KalkPRVGDB12.png Calculated dates of the selected resource for the selected task in the selected project Upper bar part:
    The color of the bar is determined by the code of the respective project
    For the meaning of the individual code colors, see the histogram legend.

    Lower bar part:
    KalkDB12.PNG Uncritical task
    CalcCritDB12.PNG Critical task
    Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.




    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
    ActDB12.png Actual dates of the selected resource for the selected task in the selected project   Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
    Puffer.png Latest task dates   Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if Calc. end of a task is later than its Latest end.

    From DB 39.5.11

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task are defined in the Schedule module.
    KalkPRVG.PNG Calculated dates of the selected resource for the selected task in the selected project Upper bar part:
    The color of the bar is determined by the code of the respective project
    For the meaning of the individual code colors, see the histogram legend.

    Lower bar part:
    VGKalk.png Uncritical task
    CriticNew.PNG Critical task
    Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.




    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
    Ist.png Actual dates of the selected resource for the selected task in the selected project   Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
    Puffer.png Latest task dates   Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if Calc. end of a task is later than its Latest end.

    Up to DB 39.5.11

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task are defined in the Schedule module.
    KalkPRVG.PNG Calculated dates of the selected resource for the selected task in the selected project Upper bar part:
    The color of the bar is determined by the code of the respective project
    For the meaning of the individual code colors, see the histogram legend.

    Lower bar part:
    Unkritisch.png Uncritical task
    kritisch.png Critical task
    Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.



    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
    Ist.png Actual dates of the selected resource for the selected task in the selected project   Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
    Puffer.png Latest task dates   Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if Calc. end of a task is later than its Latest end.

             PLANTA project









     
    • Suche in Topic-Namen

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