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

Schedule MOD0099AN

Access path

From DB 39.5.13

Up to DB 39.5.13

  • Project (Idea, Proposal) panel Schedule

    • Information

    • The Schedule module is the central and most important module in project planning and controlling in PLANTA project. * In this module, you can
      • create and edit tasks (work loads) (graphically or in table form)
      • schedule tasks
      • define and edit task parameters, e.g. define particular tasks as milestones
      • Structure tasks
      • connect tasks via links and thus generate a network cycle
      • assign resources to tasks and plan effort
      • etc.

    Module Variants

    From DB 39.5.10

    show... hide
    Base Tasks are displayed with links and all resource assignments. In window 2, all dates and a wide range of task parameters are listed.
    • New tasks, links, and resources can be created and edited.
    • This module variant is loaded first by default.
    Note: To avoid performance impairment when copying tasks or resource assignments, please make sure that this very module variant is selected and not the with loads module variant.
    Print A variant of the Schedule optimized for printing is displayed.

    Customer schedule Only tasks for which the Customer schedule checkbox is activated are displayed.

    Short version
    • Tasks are only displayed with links (no resource assignments).
    • In window 2, only requested dates, calculated dates, and milestones are displayed.
    • Tasks and links can be created.
    In the schedule of ideas and proposals, this variant is loaded instead of Base by default.

    Milestone trend/master milestone trend Displays the current status and the status from the status report for each milestone/master milestone. Changes are displayed graphically in the Gantt chart.

    Milestones/master milestones Here, all tasks that are defined as milestones or master milestones are displayed.
    With todo items Tasks are displayed including todo items and assigned resources.
    • Cost details on the resource assignment (also on load level) are hidden by default and can be displayed by the user if necessary.
    • New todo items can be created and edited.
    • Further resources can be assigned to the tasks.
    With request process steps All tasks are displayed with assigned request process steps. The variant can only be used if the Request component is employed.
    Entire schedule
    • Tasks are displayed with all assigned data areas (resources, revenue and cost resources, loads, links, todo items, task documents).
      • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
      • New resources, revenue and cost resources, links, todo items, task documents can be created and edited.

    Dates view This module variant is equal to the Short version module variant. The only difference is that this module variant contains more information in window 2.
    With loads The resources are displayed with their load records.
    • Cost details are available on load level, but they are hidden by default. They can be displayed by the user if necessary.

    To avoid performance impairment when copying tasks or resource assignments, you have to make sure not to select this module variant but the Base variant.

    Quality Gates NEW Shows quality gates with the todo items to be completed if they have been specified in the respective portfolio by the portfolio manager for the selected project.
    If the selected project has no quality gates but master milestones as gates, they will be displayed in the module variant.

    SAP WBS Elements Displays the SAP WBS element column additionally, in which the task assignment of tasks to the SAP WBS elements is done. For the procedure, see here.

    From DB 39.5.9

    show... hide
    Base Tasks are displayed with links and all resource assignments. In window 2, all dates and a wide range of task parameters are listed.
    • New tasks, links, and resources can be created and edited.
    • This module variant is loaded first by default.

    Note: To avoid performance impairment when copying tasks or resource assignments, please make sure that this very module variant is selected and not the with loads module variant.
    Print A variant of the Schedule optimized for printing is displayed.
    Customer schedule Only tasks for which the Customer schedule checkbox is activated are displayed.
    Short version
    • Tasks are only displayed with links (no resource assignments).
    • In window 2, only requested dates, calculated dates, and milestones are displayed.
    • Tasks and links can be created.
    Milestone trend This module variant has been merged with the master milestone trend variant.
    Milestone trend/master milestone trend Displays the current status and the status from the status report for each milestone/master milestone. Changes are displayed graphically in the Gantt chart.
    Milestones/master milestones Here, all tasks that are defined as milestones or master milestones are displayed.
    With documents For documents, see the Schedule complete variant
    With todo items Tasks are displayed including todo items and assigned resources.
    • Cost details on the resource assignment (also on load level) are hidden by default and can be displayed by the user if necessary.
    • New todo items can be created and edited.
    • Further resources can be assigned to the tasks.
    With request process steps All tasks are displayed with assigned request process steps. The variant is only used when employing the Request component.
    Entire schedule
    • Tasks are displayed with all assigned data areas (resources, revenue and cost resources, loads, links, todo items, task documents).
    • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
    • New resources, revenue and cost resources, links, todo items, task documents can be created and edited.
    Dates view This module variant is equal to the Short version module variant. The only difference is that this module variant contains more information in window 2.
    With loads
    • The resources are displayed with their load records.
    • Cost details are available on load level, however, they are hidden by default and can be displayed by the user if required.
    To avoid performance improvement when copying tasks or resource assignments, you have to make sure that you have not selected this module variant but the Basis module variant.
    SAP WBS Elements NEW Displays the SAP WBS element column additionally, in which the task assignment of tasks to the SAP WBS elements is done. For the procedure, see here.

    From DB 39.5.0

    show... hide
    Base Tasks are displayed with links and all resource assignments and loads. In window 2, all dates and a wide range of task parameters are listed.
    • New tasks, links, and resources can be created and edited.
    • This module variant is loaded first by default.
    Note: To avoid performance impairment when copying tasks or resource assignments, you have to make sure that this very module variant is selected and not the with loads module variant.
    Print A variant of the Schedule optimized for printing is displayed.
    Customer schedule Only tasks for which the Customer schedule checkbox is activated are displayed.
    Short version
    • Tasks are only displayed with links (no resource assignments).
    • In window 2, only requested dates, calculated dates, and milestones are displayed.
    • Tasks and links can be created.
    Milestone trend This module variant has been merged with the master milestone trend variant.
    Milestone trend Displays the current status and the status from the status report for each milestone. Changes are displayed graphically in the Gantt chart.
    Master milestone trend Displays the current status and the status from the status report for each master milestone. Changes are displayed graphically in the Gantt chart.
    Milestones/master milestones Here, all tasks that are defined as milestones or master milestones are displayed.
    With documents Tasks are displayed with task documents. New documents can be created and edited.
    With todo items NEW This module variant is not new. In the course of renaming open items to todo items, the name of the module variant has been adjusted.
    • Tasks are displayed with todo items and the resources assigned to them.
    • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
    • New todo items can be created and edited.
    • Further resources can be assigned to the tasks.
    With request process steps All tasks are displayed with assigned request process steps. The variant is only used when employing the Request component.
    Entire schedule
    • Tasks are displayed with all assigned data areas (resources, revenue and cost resources, loads, links, todo items, task documents).
    • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
    • New resources, revenue and cost resources, links, todo items, task documents can be created and edited.
    Dates view This module variant is equal to the Short version module variant. The only difference is that this module variant contains more information in window 2.
    With loads NEW
    • The resources are displayed with their load records.
    • Cost details are available on load level, but hidden by default. They can be displayed by the user if necessary.
    Note: To avoid performance impairment when copying tasks or resource assignments, you have to make sure that this module variant is not selected but the Base variant.

    Up to DB 39.5.0

    show... hide
    Base Tasks are displayed with links and all resource assignments and loads. In window 2, all dates and a wide range of task parameters are listed.
    • New tasks, links, and resources can be created and edited.
    • This module variant is loaded first by default.
    Print A variant of the Schedule optimized for printing is displayed.
    Customer schedule Only tasks for which the Customer schedule checkbox is activated are displayed.
    Short version
    • Tasks are only displayed with links (no resource assignments).
    • In window 2, only requested dates, calculated dates, and milestones are displayed.
    • Tasks and links can be created.
    Milestone trend Displays the current status and the status from the status report for each milestone. Changes are displayed graphically in the Gantt chart.
    Master milestone trend Displays the current status and the status from the status report for each master milestone. Changes are displayed graphically in the Gantt chart.
    Milestones/master milestones Here, all tasks that are defined as milestones or master milestones are displayed.
    With documents Tasks are displayed with task documents. New documents can be created and edited.
    With open todo items
    • Tasks are displayed with tasks and assigned resources.
    • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
    • New todo items can be created and edited.
    • Further resources can be assigned to the tasks.
    With request process steps All tasks are displayed with assigned request process steps. The variant is only used when employing the Request component.
    Entire schedule
    • Tasks are displayed with all assigned data areas (resources, revenue and cost resources, loads, links, todo items, task documents).
    • Cost details on the resource assignment also on load level are hidden by default and can be displayed by the user if necessary.
    • New resources, revenue and cost resources, links, todo items, task documents can be created and edited.
    Dates view This module variant is equal to the Short version module variant. The only difference is that this module variant contains more information in window 2.

    Show legend... Hide legend

    Legend: Project

    From DB 39.5.15

    MMSbigDB14.png Gates MMSbigDB14.png Gate without date delay
    MMSredbigDB14.png Gate with date delay
    HMSDB14.png Main gate/main milestone     		Gates are master milestones of planning objects.
    Without date delay means: Total float 0
    With date delay means: Total float < 0

    Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
    QG.png Quality Gates   Quality Gates are the items given from the portfolio and are only displayed in planning objects if they are assigned to this planning object in the portfolio to which the planning object belongs.
    WunschDB14.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
    KalkPRDB14.png Calculated dates The color of the bar is determined by the code of the planning object.
    CodeADB14.png Code A
    CodeBDB14.png Code B
    CodeCDB14.png Code C
    CodeDDB14.png Code D
    CodeEDB14.png Code E     		Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item.
    In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
    ActDB14.png Actual dates The bar is white hatched. The background color depends on the Code of the planning object. Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
    Verzug.png Date delay   A date delay occurs if the calculated end date (Calc. end) of the planning horizon is later than the requested end date (Requested end).
    The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
    AOBAus.png external links AOBAus.png outgoing
    AOBEin.png incoming     		 

    From DB 39.5.14

    MMSbigDB14.png Gates MMSbigDB14.png Gate without date delay
    MMSredbigDB14.png Gate with date delay
    HMSDB14.png Main gate/main milestone     		Gates are master milestones of planning objects.
    Without date delay means: Total float 0
    With date delay means: Total float < 0

    Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
    QG.png Quality Gates   Quality Gates are the items given from the portfolio and are only displayed in planning objects if they are assigned to this planning object in the portfolio to which the planning object belongs.
    WunschDB14.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
    KalkPRDB14.png Calculated dates The color of the bar is determined by the code of the planning object.
    CodeADB14.png Code A
    CodeBDB14.png Code B
    CodeCDB14.png Code C
    CodeDDB14.png Code D
    CodeEDB14.png Code E     		Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item.
    In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
    ActDB14.png Actual dates The bar is white hatched. The background color depends on the Code of the planning object. Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
    Verzug.png Date delay   A date delay occurs if the calculated end date (Calc. end) of the planning horizon is later than the requested end date (Requested end).
    The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).

    From DB 39.5.12

    MMSbig.png Gates MMSbig.png Gate without date delay
    MMSredbig.png Gate with date delay
    HMS.png Main gate/main milestone     		Gates are master milestones of planning objects.
    Without date delay means: Total float 0
    With date delay means: Total float < 0

    Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
    QG.png Quality Gates   Quality Gates are the items given from the portfolio and are only displayed in planning objects if they are assigned to this planning object in the portfolio to which the planning object belongs.
    Wunsch.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Program Core Data).
    KalkPRDB12.PNG Calculated dates The color of the bar is determined by the code of the planning object.
    CodeADB12.PNG Code A
    CodeBDB12.PNG Code B
    CodeCDB12.PNG Code C
    CodeDDB12.PNG Code D
    CodeEDB12.PNG Code E     		Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item.
    In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
    ActDB12.png Actual dates   Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
    Verzug.png Date delay   A date delay occurs if the calculated end date (Calc. end) of the planning horizon is later than the requested end date (Requested end).
    The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).

    Up to DB 39.5.12

    MMSbig.png Gates MMSbig.png Gate without date delay
    MMSredbig.png Gate with date delay
    HMS.png Main gate/main milestone     		Gates are master milestones of planning objects.
    Without date delay means: Total float 0
    With date delay means: Total float < 0

    Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
    Wunsch.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Program Core Data).
    Kalk.png Calculated dates The bar color is defined by the code of the planning object.
    A.png Code A
    B.png Code B
    C.png Code C
    D.png Code D
    E.png Code E     		Calc. start and Calc. end of a planning object are determined in the calculation of the schedule of the respective planning object.
    In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
    Ist.png Actual dates   Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
    Verzug.png Date delay   A date delay occurs if the calculated end date (Calc. end) of the planning horizon is later than the requested end date (Requested end).
    The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).

    Legend: Task

    From DB 39.5.15

    Symbol Meaning Color Comment
    WunschDB14.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical     		Calc. start and Calc. end are calculated by clicking on the calculation button 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 be critical as well.
    MSDB14.png / MMSDB14.png Milestones/
    Master milestones         		MSDB14.png / MMSDB14.png Without delay
    MSredDB14.png / MMSredDB14.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end     		Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    ActDB12.png Actual dates The respective bars are white hatched if the Splitting parameter is deactivated, and gray hatched if the parameter is activated. Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or by setting it manually.
    Puffer.png Latest dates   Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if the Calc. end of a task is later than its Latest end.
    Ueberlappung.PNG Overlapping   Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
    KalkExtDB12.PNG Calculated dates of the external tasks KalkExtDB12.PNG Uncritical
    KalkExtredDB12.png Critical     		Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button 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 be critical as well.
    SammelExtVGDB14.png Calculated dates of the external summary tasks    
    MSextDB12.png / MMSExtDB12.PNG Milestones/master milestones of the external summary tasks MSextDB12.png / MMSExtDB12.PNG Without delay
    MSextRedDB12.png / MMSextRedDB12.png With delay
    		Without delay means: Total float 0
    With delay means: Total float < 0
    AOBAus.png External link AOBAus.png outgoing
    AOBEin.png incoming     		 

    From DB 39.5.14

    Symbol Meaning Color Comment
    WunschDB14.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical     		Calc. start and Calc. end are calculated by clicking on the calculation button 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.
    MSDB14.png / MMSDB14.png Milestones/
    Master milestones         		MSDB14.png / MMSDB14.png Without delay
    MSredDB14.png / MMSredDB14.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end     		Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    ActDB12.png Actual dates The respective bars are white hatched if the Splitting parameter is deactivated, and gray hatched if the parameter is activated. Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or by setting it manually.
    Puffer.png Latest dates   Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if the Calc. end of a task is later than its Latest end.
    Ueberlappung.PNG Overlapping   Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
    KalkExtDB12.PNG Calculated dates of the external tasks KalkExtDB12.PNG Uncritical
    KalkExtredDB12.png Critical     		Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button 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.
    SammelExtVGDB14.png Calculated dates of the external summary tasks    
    MSextDB12.png / MMSExtDB12.PNG Milestones/master milestones of the external summary tasks MSextDB12.png / MMSExtDB12.PNG Without delay
    MSextRedDB12.png / MMSextRedDB12.png With delay
    		Without delay means: Total float 0
    With delay means: Total float < 0

    From DB 39.5.12

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical     		Calc. start and Calc. end are calculated by clicking on the calculation button 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.
    MSDB12.png / MMSDB12.png Milestones/
    Master milestones         		MSDB12.png / MMSDB12.png Without delay
    MSredDB12.png / MMSredDB12.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end     		Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    ActDB12.png Actual dates   Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
    Puffer.png Latest dates   Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if the Calc. end of a task is later than its Latest end.
    Ueberlappung.PNG Overlapping   Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
    KalkExtDB12.PNG Calculated dates of the external tasks KalkExtDB12.PNG Uncritical
    KalkExtredDB12.png Critical     		Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button 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.
    SammelExtVGDB12.png Calculated dates of the external summary tasks    
    MSextDB12.png / MMSExtDB12.PNG Milestones/master milestones of the external summary tasks MSextDB12.png / MMSExtDB12.PNG Without delay
    MSextRedDB12.png / MMSextRedDB12.png With delay
    		Without delay means: Total float 0
    With delay means: Total float < 0

    From DB 39.5.11

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    VGKalk.png Calculated dates of the tasks VGKalk.png Uncritical
    CriticNew.PNG Critical     		Calc. start and Calc. end are calculated by clicking on the calculation button 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.
    MSgreen.PNG / MS.PNG Milestones/
    master milestones         		MSgreen.PNG / MS.PNG Without delay
    MSred.PNG / MMS_krit.PNG With delay
    MS_erl.PNG / MMS_erl.PNG With actual end     		Without delay means: Total float 0
    With delay means: Total float < 0
    Sammel.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule that consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    Ist.png Actual dates   Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
    Puffer.png Latest dates   Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if the Calc. end of a task is later than its Latest end.
    Ueberlappung.PNG Overlapping   Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
    ExtTAUncrit.PNG Calculated dates of the external tasks ExtTA.PNG Critical
    ExtTAUncrit.PNG Uncritical     		Calc. start and Calc. end of the external tasks are calculated by clicking on the calculation button 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.
    ExtSum.PNG Calculated dates of the external summary tasks    
    MSExternal.PNG Milstones/master milestones of the external tasks    

    Up to DB 39.5.11

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    VGKalk.png Calculated dates of the tasks Unkritisch.png Uncritical
    kritisch.png Critical     		Calc. start and Calc. end are calculated by clicking on the calculation button 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.
    MSgreen.PNG / MS.PNG Milestones/
    Master milestones         		MSgreen.PNG / MS.PNG Uncritical
    MSred.PNG / MMS_krit.PNG Critical
    MS_erl.PNG / MMS_erl.PNG With actual end     		Uncritical means: Total float 0
    Critical means: Total float < 0
    Sammel.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule that consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    Ist.png Actual dates   Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
    Puffer.png Latest dates   Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
    VGueberkrit.PNG Task date delay   A date delay occurs if the Calc. end of a task is later than its Latest end.
    Ueberlappung.PNG Overlapping   Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
    ExtTAUncrit.PNG Calculated dates of the external tasks ExtTA.PNG Critical
    ExtTAUncrit.PNG Uncritical     		Calc. start and Calc. end of the external tasks are calculated by clicking on the calculation button 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.
    ExtSum.PNG Calculated dates of the external summary tasks    
    MSExternal.PNG Milstones/master milestones of the external tasks    

    Legend: Todo item

    Symbol Meaning Comment
    aufgabenbeschreibung.PNG Todo item date The date value for the bar is calculated from the Date (DT804) field.

    Schedule and Tasks

    Information
    • A schedule is a total of all terminated and calculated tasks (work loads) of a project. If tasks are structured, a work breakdown structure forms part of the schedule. If tasks are also connected via links so that the processing structure of the project becomes visible, a network cycle will also form part of the schedule.
    • Tasks are the core elements of each schedule. In PLANTA project, you can create schedules by recording tasks individually or by using already predefined complete schedules from templates which can be copied to your own projects. Schedules of the already existing projects can be used as a source for copying.
    • In the Schedule module, task records are spread throughout window 3. In the first two windows, tasks are displayed in lines (in table form), in which task attributes (parameters) can be edited in individual data fields. In window 3, a date bar for already existing task dates (requested dates, calculated dates, actual dates) is mapped graphically for each task.

    Note

    • Structure tasks are a peculiar form of tasks. Structure tasks are links between main and subprojects in structured projects.
    • Structure tasks are available in schedules of structured projects, but they are not visible to the user.

    Copy Schedule

    Procedure
    • When opening the Schedule module, the following confirmation prompt is displayed: Is a schedule to be copied in?
    • Confirm the message with Yes.
    • The Copy Schedule module is opened at the bottom of the panel.
    • Select the project the schedule of which is to be copied from the listbox.
    • Start copy operation by clicking on the Copy schedule button.
    • The schedule that was copied into the project is displayed and can be edited.

    Notes

    • If the confirmation prompt was negated accidentally, the Copy Schedule module can be reopened by right-clicking on the project header and selecting the command of the same name.
    • You can also copy schedules additively via the context menu (by right-clicking and selecting the Copy Schedule command).

    Record Tasks Individually

    Procedure
    • When opening the Schedule module, the following query is displayed: Is a schedule to be copied in?
    • Answer the confirmation prompt with No.
    • Insert an empty task line, e.g. by pressing F4 or by clicking on the Insert button in the toolbar.
    • Enter a task name in the Task name field.
    • Save and click on the Generate WBS code button next to the project bar. As a result, an ID will automatically generated for the new task in the Task field. In PLANTA standard, the WBS codes are used as task IDs in schedules. For more information on this subject, see the "Structure Tasks" chapter below.
    • Create further tasks in the same way.

    In PLANTA project tasks can have three different IDs:

    • In the course of this, a technical ID of the task will be generated automatically. This is an incrementing task number and is usually invisible in user modules in PLANTA Standard.
    • A functional task ID is automatically generated but it can also be allocated and changed manually under certain settings.
    • A task WBS code marks the tasks according to their position in the schedule hierarchy.
    • Via the show_psp_instead_of_id global parameter you can set which of these IDs will be used. This will then apply system wide to all user modules in which tasks are displayed.

    Structure Tasks

    Information
    • The hierarchic structuring of tasks results in a work breakdown structure

    • The parent tasks of a structured project plan are called summary tasks in PLANTA project.
    • The work breakdown structure code (WBS code) marks single project tasks in accordance with their hierarchical structure.

    Procedure

    From DB 39.5.9

    • Structure tasks hierarchically as desired by pressing SHIFT + holding down the left mouse button and moving them to the required position.
      • If you have created your project by copying a schedule template, the tasks are already structured. Of course, this structure can be changed.
    • Select the Generate WBS code command from the context menu by right-clicking on the program header or NEW by clicking on the Generate WBS code button (on the right of the project header).
      • The WBS code is generated automatically for every task in the WBS code field in accordance with the structure. Thus, the WBS code is both an identifier for single elements in the schedule and an indicator of the hierarchical structure.
    • Start the calculation of the schedule by clicking on the calculation button in the toolbar.
      • As a result, all parent tasks are marked bold and are therefore visualized as summary tasks.
    Notes
    • The WBS code field is hidden by default in the Schedule module and can be displayed if necessary. Depending on the settings of the show_psp_instead_of_id global parameter, the WBS code is additionally displayed in the Task field.
    • After putting on tasks to another structure level, the changes are to be saved before the WBS code is refreshed (generated anew).
    • If there are less than 10 tasks, the numeration of the codes is done by the 1, 2,... 9 schema, if there are more than 10 tasks, the numeration is done by the 01, 02,... 09, 10, ... schema.

    Up to DB 39.5.9

  • Structure tasks hierarchically as desired by pressing SHIFT + holding down the left mouse button and moving them to the required position.
    • If you have created your project by copying a schedule template, the tasks are already structured. Of course, this structure can be changed.
  • Select the Generate WBS code command from the context menu by right-clicking on the project header.
    • The WBS code is generated automatically for every task in the WBS code field in accordance with the structure. Thus, the WBS code is both an identifier for single elements in the schedule and an indicator of the hierarchical structure.
  • Start the scheduling by clicking on the calculation button in the toolbar.
    • As a result, all parent tasks are marked bold and are therefore visualized as summary tasks.

    • Notes

    • The WBS code field is hidden in the module by default and can be displayed if necessary. Depending on the setting of the show_psp_instead_of_id global parameter, the WBS code is additionally displayed in the Task field.
    • After putting on tasks to another structure level, the changes are to be saved before the WBS code is refreshed (generated anew).
    • If there are less than 10 tasks, the numeration of the codes is done by the 1, 2,... 9 schema, if there are more than 10 tasks, the numeration is done by the 01, 02,... 09, 10, ... schema.

    Attention

    • When working with structured schedules, PLANTA recommends that you use summary tasks as structuring elements only, i.e. you should not carry out effort or cost planning or enter durations on this level. This includes planning resources or reporting directly to the summary task. Instead, PLANTA recommends that you carry out the planning on the subtasks only.
      • Reason: Since the scheduling detects some parameters of the summary tasks from child tasks, there may be collisions between your own planned values and those detected by the date scheduling. As a result, there may be values on summary tasks that are incomprehensible at first sight.

    Edit Tasks

    Information

    • Each task of a schedule can be edited by changing individual task parameters.
    • Please note that depending on the selected variant of the Schedule module, different task parameters will be visible in the task record by default. All other parameters are hidden and can be displayed for editing or to have a look at them.


    Tip: Each task of the schedule can also be opened and edited in the form of a data sheet. To do so, click on the link on the ID of the task or right-click on the required task and select the Edit task command from the context menu.

    Schedule Tasks

    Procedure

    From DB 39.5.12

    Detailed information on the calculation of schedules and on the different factors which can influence the calculation, please see here.

    Up to DB 39.5.12

  • In tabular form:

    • Notes

    (Master) Milestone Tasks

    Procedure

    • Select the required value in the Milestone field in the line of the required task: milestone or master milestone (gate).

    * If a task has been defined as a milestone or master milestone, some specialties must be considered when it is planned (duration, requested dates). For further information, click here.

    New from DB 39.5.0

    Gates
    • If there are master milestones in the schedule and the Schedule with gates checkbox has been activated in the Project Core Data module, master milestones are additionally displayed on the horizontal schedule axis in the Gantt chart directly below the scale and are called gates.
      • If the project is assigned to a program, the master milestones (gates) of the program will additionally be displayed below the scale.
      • If the project is a subproject, the master milestones (gates) of the main project are additionally displayed below the scale (in the same line in which the gates of the project themselves are displayed).

    Master milestones

    • If one of the master milestones has been defined as a master milestone in the Project Core Data as well, it is considered a reference master milestone. The time interval (in weeks) from the main milestone to the other master milestones is calculated and illustrated on the gate symbols. The master milestone has no interval indication on the gate and also differs from other gates in graphical terms, since on a gate it has a darker border.
      • If no master milestone has been defined, the calculated end date of the project is used as a reference point for the calculation of the interval. If there is a master milestone on the calculated end date of the project, the respective gate does not contain an interval indication either (however, it is still not a master milestone and accordingly it has no dark border).
      • The interval calculation is carried out upon start of the client, so that a client restart becomes necessary if you want to have the intervals updated because a main milestone has been newly selected or changed, or if the calculated date of the program has changed.

    Lock Tasks

    Information
    • Individual tasks of a project can be locked against the recording of hours worked, km and expenses, and cost posting.

    From DB 39.5.15

    Procedure
    • Open the NEW Entire Schedule module variant in the Schedule module.
    • To do so, deactivate the Task locked checkbox in the line of the required task.

    Details

    • NEW In other module variants, the checkbox is hidden by default and must be hidden first for editing.

    Note

    • It is possible to prevent the recording of hours worked also on project level using the Locked parameter. This lock applies to all tasks of the project and cannot be overridden by the Task locked parameter.

    Up to DB 39.5.15

    Procedure
    • Tasks can be locked against the recording of hours worked, expenses, km, etc. by activating the Lock task checkbox.

    Note

    • If the recording of hours worked is prevented on project level by the Locked code in the Project Core Data module, this lock cannot be canceled by deactivating the Task locked code.

    Estimate Tasks

    From DB 39.5.15

    Information
    • The project manager can evaluate or estimate each task of the schedule and visualize this by using different symbols.

    Procedure

    • NEW Switch to the Entire schedule module variant.
    • Keep clicking on the » arrow button in the line of the required task in window 1 until the required symbol is displayed.

    Details

    • There are no symbols displayed for new tasks.

    Up to DB 39.5.15

    Information
    • The multi-project manager can write or edit a task note or the task estimate by clicking on the » Change note arrow button (window 1) in the respective task line.
    • The status/estimate is visualized by different symbols.
    • There are no symbols displayed for new tasks.
    Procedure
    • Click on the » arrow button repeatedly until the required symbol is displayed.

    Finish Task

    Procedure
    • Enter the required end date in the Actual end field in the line of the required task.
      • If resources which have no Actual end yet are assigned to the task, the task end date is automatically set for these resources.
      • If all resource assignments of the task have an actual end date, the actual date of the task is automatically filled from the maximum of all resource assignments in the calculation of the schedule.
    • Save and recalculate the schedule (by clicking on the calculation button in the toolbar).

    Details

    • Completed tasks are displayed grayed-out.

    Task Documents

    Information

    • PLANTA project does not include any text processing facilities comparable to standard programs such as Microsoft Word. However, for particular objects (e.g. project documents, task documents, resource notes) it is possible to enter and manage a text in the so called continuous fields.

    Assign documents to the tasks

    • Select the With Documents module variant in the Schedule module.
    • Insert a new task document record for the required task.
    • Enter the desired text for the document in the Note field.
    • You can create a link to a file (a document) in the Linked file field.

    Links

    Information

    • Links are dependencies between tasks that (can) have an effect on the calculated dates.
    • PLANTA project distinguishes between three link types: internal links, external links, and external tasks. Here, internal and external links have an immediate impact on the calculation of dates. external tasks are of informative nature and only show dependencies.

    See also: Create, Edit, Delete Links

    Internal Links

    Information
    • Internal links are links which connect tasks within a project.

    Create internal links in table form

    • To do so, right-click on the required task and select the Insert Link context menu command.
    • Fill the following fields in the new link record:
    • Save and recalculate the schedule (by clicking on the calculation button in the toolbar).

    Create internal links graphically

    • Move the mouse pointer to the bar from which a link is to be created (source bar). Instead of the mouse pointer, a cross will be displayed.
    • Set the cross to the beginning or to the end of the source bar depending on which Link type you wish to create (e.g. for the Finish-Start relationship, set the cross to the end of the source bar).
    • Click and hold the left mouse button and drag the mouse to the beginning or to the end of the target bar depending on what link type you wish to create (e.g. for a Finish-Start relationship drag the mouse to the start of the target bar). As a result, a connection line between the two bars will be displayed.
    • As soon as the destination bar is reached, the start position in the source bar and the destination position in the destination bar are marked by yellow arrows.
    • Release the left mouse button. The new link will be created and will be visualized as a connection line.

    Edit internal link

    • Every link can be edited in the respective fields of the table view by changing the required link parameters. The most important are:

    Delete internal links in table form

    • Mark the required link line.
    • Click on the delete symbol in the toolbar.

    Delete internal links graphically

    • Click on the required link line in the Gantt chart to have it highlighted.
    • Then right-click and select the Delete link context menu command.

    See also: Links

    Read Out Task Chain

    From DB 39.5.14

    Procedure

    • Right-click on the required task.
    • Select the Read out task chain context menu command.
    • The What do you want to do? dialog message is displayed.
    • The user has six options:
      • NEW If you click on the Direct predecessor button, the Task Chain module is opened and the direct predecessor(s) of the task are displayed.
      • If you click on the Predecessor button, the Task Chain module is opened and the predecessors of the task are displayed with their own predecessors.
      • NEW If you click on the Direct successor button, the Task Chain module is opened and the direct successor(s) of the task are displayed.
      • If you click on the Successor button, the Task Chain module is opened and the successors of the task are displayed with their own successors.
      • If you click on the Overall view button, the Task Chain module is opened and the predecessors as well as the successors of the selected task are displayed. As a result, the successors of the predecessors will be displayed as well, however, the predecessors of the successors will not be displayed.
      • If you click on the Cancel button, the action is aborted.

    Up to DB 39.5.14

    Procedure
    • Right-click on the task.
    • Click on the Read out task chain context menu command.
    • The What do you want to do? dialog message is displayed.
    • You have 4 options:
      • If you click on the Predecessor button, the Task Chain module is opened and all predecessor tasks of the current task are displayed.
      • If you click on the Successor button, the Task Chain module is opened and all successor tasks of the current task are displayed.
      • If you click on the Overall view button, the Task Chain module is opened and all predecessor and successor tasks of the current task are displayed.
      • If you click on the Cancel button, the proposal is aborted.

    External Links

    Information
    • External (cross-project) links connect the tasks of different projects. * The interlinkage of projects via external links results in the generation of a total network plan during calculation which covers all projects involved.

    Create external links in table form

    From DB 39.5.15

    • Right-click on the required task and select the Insert External link context menu command.
    • The line for an external link is inserted.
    • Enter the ID of the target project in the PR successor field and select the target task to which the external link is mapped in the Task field.
      • The PR successor is preset with the ID of the current project.

    Up to DB 39.5.15

  • Right-click on the required task and select the Insert Link context menu command.
    • The link line is inserted.
    • Enable the display of the hidden Project successor column (by right-clicking on the caption line)
      • The field is preset with the ID of the current project.
      • Replace it by selecting the ID of the required project from the listbox.
    • Select the required resource from the listbox on the Follow-up task field.

    • It is not possible to create external links graphically.

    Edit external links

    Delete external links

    It is not possible to create external links graphically.

    Details

    From DB 39.5.15

    • NEW In each project, all external links of this project, both outgoing (from the respective project to another project) and incoming (from another project to the respective project itself) are visualized in the schedule.
      • In table view (window 1), all external link records
        • are listed indented, separated from the internal ones
        • and are additionally marked with the respective icon: retweet-light-to-right.png for incoming external links and retweet-light.png for outgoing external links.
      • In graphical view (bar chart in window 3), the external links are visualized as follows:
        • by arrow(s) next to the respective task bar long-arrow-left-light-blue.png for incoming and/or long-arrow-right-light-blue.png for outgoing external links. When you click on the respective arrow, the respective task is expanded and the link line is marked.
        • by arrow(s) next to the project bar. When you click on one of the arrows, all tasks of the project with external links are expanded and the last link line of the schedule, which corresponds to the type of the arrow you have clicked on, is marked.

    Up to DB 39.5.15

  • The external links are only visible in the project from which they were created, i.e., in the source project. They are not visible in the target project.

    • See also: Links

    External Tasks

    Information
    • External tasks are tasks of another project which can be displayed in the schedule of the selected project in order to visualize the dependencies between the projects. External tasks do not have an influence on the schedule of the selected project. Other than external links, which influence the task dates in the selected project, they are of purely informational nature.

    Display an external task

    • Right-click on the required task.
    • Select Insert External task from the context menu.
    • Select the required project and the required task from the respective listbox.
      • The selected external task is displayed in the schedule of your own project.

    See also: External Tasks


    From DB 39.5.0

    Todo Items

    Information

    • In the Schedule module, you can define small todos for single tasks and assign them to the required users (resources) for completion.
    • All todo items of a project are maintained centrally in the Todo Items module.

    Procedure:

    • Switch to the With Open Items module variant in the Schedule module.
    • Right-click on the required task and select the Insert Todo Item context menu command from the context menu.
    • A new todo item record is inserted.
    • Enter the name of the todo item in the Todo item name field.
    • Save.
      • As a result, the ID number (Todo item field) of the todo item is generated automatically.
      • The Created on / Created by: name fields of the todo item are automatically filled with the current date and the current user.
      • Fill the required fields, e.g. the Date up to which the todo item is to be completed (when a todo item is created, today’s date is automatically entered here), Resource whic is to complete the todo item, etc.
    • Save.

    Write Todo Item Notes

    Procedure

    • Right-click on the required todo item and select the Insert Note command from the context menu.
    • A note/document record is inserted.
    • Enter the text in the Note field.
    • In the Linked file field, you can create a link to a file.

    Assign Checklist Items/Check Lists

    Information

    • For todo items, individual steps can be recorded in the form of checklist items. They can either be recorded individually or be copied from the checklist templates as entire checlists.

    * Assign individual checklist items

    • insert an empty checklist item record for the required todo item by right-clicking on the todo item and selecting the Insert Checklist item command.
    • Describe the item.
    • Save.

    * Copy entire checklists from predefined checklist templates.

    • switch to the Todo Item module (by right-clicking or by directly clicking on the ID of the required todo item).
    • In the Todo Item module, right-click on the todo item.
    • Select Copy checklist from the context menu.
    • Select a checklist in the Copy checklist from template area and click on the link on the checklist name.
    • The checklist items of the selected checklist are assigned to the todo item.
    • Save.

    Details

    • Checklists can also be copied additively.
    • The checklist templates are created and administrated in the Checklists module.

    Up to DB 39.5.0

    Open Items

    Information

    • In the Schedule module, you can define small todos for single tasks and assign them to the required users (resources) for completion.
    • All open items of a project are administered centrally in the Open Items module.

    Procedure

    • Switch to the With Open Items module variant in the Schedule module.
    • Insert a new todo item record for the required task.
    • Enter the item name in the Open item name field.
    • Save.
      • As a result, the ID number (Open item field) of the open item is generated automatically.
      • The Created on / Created by: name fields of the open item are automatically filled with the current date and the current user.
      • The entry in the Date field is the completion date. When you create a new todo item, today's date is entered automatically. This can be overwritten by another date, if required.
    • Select the resource that is meant to complete this item from the Resource name listbox.
    • Select a category from the listbox.
    • Enter the priority in the Prio field.
    • Save.

    Resource Planning

    Information

    • Resources are responsible for the completion of tasks.
    • They are assigned (allocated) to individual tasks.
    • Resources must have been created before as part of the Master Data Entry.
    • Which resources (individual employees, entire departments, or machines) can be assigned to the tasks depends on several factors, e.g. planning horizon, project type, etc.
    • When assigning and planning resources in the schedule, PLANTA project distinguishes between resources, which comprise persons, departments, and skills and the effort of which is planned in time units, and revenue and cost resources, the effort of which is planned in monetary units.

    Resources for capacity planning and cost resources can be assigned to a task at the same time. Capacity adjustment then applies, for example, to the resource used for capacity planning, and the cost resource is planned in at the scheduled calc. start/calc. end dates of the task.

    Assign Resources to Tasks and Plan Them

    Assign individual resources to a task

    • Right-click on the required task and select Insert Resource or Insert Revenue and Cost Resource from the context menu.
    • Select the required resource from the resource listbox.
    • Define the required resource parameters.
      • When the resource was assigned to the task, several parameters have already been filled with default settings from the Resource Data Sheet (e.g. Load profile, Cost type). These values can be changed manually here.
      • Attention: If you change the default values for one of the resources assigned to the task and then copy this resource assignment to one of the further tasks, previously changed settings will be included instead of the default settings of the resource.

    Assign several resources to a task simultaneously

    From DB 39.5.12

    • Right-click on the required task and select the Assign resources or Assign revenue and cost resources command from the context menu.
    • The Assign Resources dialog module is opened.
      • Depending on which command has been selected from the context menu, resources of the respective type will be loaded automatically when the dialog module is opened, i.e. either person, department, and skill resources or revenue and cost resources. In order to have resources of the other type displayed, click on the respective button.
    • Select the required resources from the list by activating the Select checkbox.
    • Click on the Assign selected button. The records of the selected resource are now displayed below the respective task.

    From DB 39.5.1

    • Right-click on the required task and select the Assign resources or Assign revenue and cost resources command from the context menu.
    • The Resource List module is opened.

    • When opening the module via the Assign resources context menu command, person, department, and skill resources are loaded automatically.
      • Mark the required resources in the list by
        • clicking or
        • CTRL + clicking (can be used to mark a parent resource (e.g. a department resource) and its child resources at once).
      • Subsequently click on the Copy marked button.
      • To have the revenue and cost resources displayed, click on the button of the same name and proceed as described above.
    • When opening the module via the Assign revenue and cost resources context menu command, person, department, and skill resources are loaded automatically.
      • The procedure here equates to that of the department, employee, and skill resources.
      • To have the department, employee, and skill resources displayed, click on the Person resources button.

    Up to DB 39.5.1

    • Right-click on the required task and select the Assign resources or Assign revenue and cost resources command from the context menu.
    • The Resource List module is opened.

    • To select the required resources, mark them with CTRL + click.
    • Subsequently click on the Copy marked button..

    Plan resources

    • Enter the planned effort for person, skill, and department resources ("days" in standard) in the Remaining effort field.
    • Enter the planned effort for person, skill, and department resources (in the unit of "euros") in the Remaining costs field.
    • Check and possibly change the Load profile for a distribution of effort and costs in time.
    • Enter requested dates if necessary (Requested start/Requested end). This enables you to specify that several resources are working on a task at different times, or that they start or finish their work at different times.


    Tip: * The option to assign resources to tasks and to delete such assignments is also available in the Resource Plan and Task modules.
    • The Resource Plan module shows the selected project with all tasks and their resource assignments. Since the module only contains few parameters and the assigned resources are, unlike in the Schedule module, aligned next to their respective tasks, this module provides an alternative to the schedule, allowing you to get a quicker overview of the assigned resources or the editing of resource assignments. * As in the Schedule module, individual resources, or several resources at once, can be assigned to the tasks. Resources with an Actual end date are not displayed.
    • In the Task module, only the selected task with its corresponding resources is displayed. Resources can only be assigned and deleted individually here.

    See also: Here you can find a detailed description of all resource parameters or you can specifically retrieve information on the respective parameter from the program via F1. Detailed information on the calculation methods of scheduling and on the different factors which can influence the calculation, please see here.


    Resource Effort, Load, Utilization

    Information

    • If resources have been assigned to a task and effort has been defined, you have to recalculate the schedule (by clicking on the calculation button in the toolbar). In the course of this, the project is loaded. This means: A load record will each be generated per resource assignment and day and the planned effort of the resource will automatically be allocated to the individual days. This allocated effort value is the load of the resource. The way in which hours are allocated per day is controlled by the load profile entered on the resource assignment.
    • It is also possible to generate load records manually and to allocate effort manually.
    • A resource can have loads in different projects on the same day. The sum of all loads of a resource per day is their utilization. However, the utilization value of the resource is not displayed in the schedule since the schedule refers to one sole project. However, the schedule does not reflect the involvement of the resource in other projects. For more information, please refer to the "Show Resource Utilization" chapter.

    Details

    From DB 39.5.0

    • Load records show both planned load (remaining load) and possible overload, and, if the project is already in progress and the resources have already reported hours worked, actual loads of the respective resources will be shown as well.
    • Note: To view load records, you have to switch to the With Loads NEW or Entire Schedule module variant.

    Up to DB 39.5.0

  • Load records show both remaining load and possible overload, and, if the project is in progress and the resources already have reported hours worked, actual loads of the respective resources will be shown as well.
  • In order to view load records, you have to switch to the Entire Schedule module variant.

    • Note

    • If capacity scheduling is initiated simultaneously for different projects that share the same resources (or at least share one resource), it is only launched for one project while in the other modules a message is displayed indicating that one or several resources are used by another capacity scheduling. The scheduling must be carried out successively for all projects in question. Projects with different resources, however, can be scheduled simultaneously.

    Display Resource Utilization

    From DB 39.5.1

    Information
    • It is possible to check the utilization of the planned resources in other projects from the Schedule of a particular project.
    Procedure
    • Right-click on the required resource.
    • Select the Display utilization context menu command. By doing so, you change to the Utilization With Cause module, where the utilization of the corresponding resource is displayed.
    Note NEW
    • You can view the utilization of all resources displayed in the schedule, regardless of whether or not the current user generally has access to the respective resources (controlled via the resource structure code).

    Up to DB 39.5.1

    Information
    • It is possible to check the utilization of the planned resources in other projects from the Schedule of a particular project.
    Procedure
    • Right-click on the required resource.
    • Select the Display utilization context menu command. By doing so, you change to the Utilization With Cause module, where the utilization of the corresponding resource is displayed.

    New from DB 19.5.17

    Post to Revenue and Cost Resources

    Information
    • In the Schedule module, not only effort but also costs of the individual tasks and of the entire project are displayed. This also includes actual costs. Planned costs are automatically calculated by the program on the basis of the planned effort of the planned resources and their conversion factors. The actual costs are also calculated on the basis of the recording of hours worked of the person resources and their conversion factors. Revenue and cost resources, however, are not planned as effort but as monetary values and there is no recording of hours worked option for them. The actual costs of these resources are posted in modules which have been designed especially for this purpose (Revenues Posting and Cost Posting). These modules can now also be opened directly from the respective revenue and cost resources in the Schedule module.

    Procedure

    • Right-click on the required revenue or cost resource.
    • Select the Revenues/cost posting context menu command. Depending on the resource which has effected the context menu command, either the Revenues Posting or Cost Posting module will be opened.
    • Record costs/revenues as described in the module topics.

    Compare Planning Statuses

    From DB 39.5.9

    Information
    • The comparison of different planning statuses (fixed in individual status reports) with the current planning status is done in the Deviations module which can be accessed via Project Further... tab Deviations link.

    From DB 39.5.7

    In this version, the Delta View module has been outsourced directly to the project panel and can be found in the Deviations tab. This is why the Compare planning PlanungvergleichenButton.PNG button is no longer available in the Schedule module.

    Up to DB 39.5.7

    Information
    • You can compare planning statuses from several status reports to the current planning status.

    Procedure

    • Activate the Milestone trend analysis checkbox in the Configure Trend Analysis module for the status reports which are to be compared to the current project status.
    • Save.
    • Click on the Compare planning PlanungvergleichenButton.PNG button in the Schedule module. (The button is located in window 1 alongside the project header.)
    • The Delta View module is opened in which planning statuses can be compared.

    Note

    • If the current project is a structured project, the Milestone Trend Analysis checkbox must be activated for the required report on all project levels (in the main project and all subprojects).


    Special Functions

    New from DB 39.5.10

    Quality Gates

    Information
    • Quality gates are a type of controlling element for the portfolio manager to control the progress of the planning objects contained in the portfolio.
    • Quality gates are defined (scheduled, and divided into separate tasks) by the portfolio manager and are assigned to the individual planning objects.
    • The assigned quality gates in the Schedule in the Quality Gates module variant of the respective planning object are displayed to the project managers. They record the degree of completion of the tasks of these quality gates and their probable completion date and thus enable the portfolio manager to observe compliance with the requirements.

    Edit Quality Gates

    • Enter the date estimated for the achievement of the quality gate in the Prob. compl. on field.
    • In the File field, a file relevant for the todo item can be stored.
    • Create or refresh the degree of completion of the respective todo item in the % completed field.

    Attention

    • Since from a technical point of view quality gates are tasks, the requested end dates calculated for them can influence the project dates. Since the quality gates are automatically copied when the planning object is assigned to the portfolio, please check the schedules of the planning objects or the dates of the quality gates for assignments of the planning objects to portfolios.

    New from DB 39.5.9

    Link Tasks with Elements of Alternative Structures

    Information
    • In PLANTA project you have the option to link the created project structure to another project structure (e.g. SAP project structures) by assigning PLANTA tasks to the elements of the alternative structure. This enables you to summarize effort and costs planned in PLANTA project to the other project structure.

    Procedure

    • Switch to the SAP WBS elements module variant
    • Select an element of the alternative project structure in the line of the required task in the SAP WBS elements field.

    Details

    • The alternative structure with the linked PLANTA tasks can be viewed in the SAP WBS module. In this module, tasks and elements of the alternative structure can be linked as well.

    From DB 39.5.15

    Synchronize Tasks with External Systems (for Agile Project Editing)

    Information

    • PLANTA provides an option for linking tasks from projects which are planned in PLANTA project to other systems in order to plan and control them agilely there.
    • Currently, PLANTA provides links to NEW two agile systems by default: PLANTA pulse (in the context of PLANTA Hybrid) and NEW Jira. It can only be linked to one system per project.
    • The linkage of tasks is done from the schedule of the respective project.

    Attention

    • The required tasks can only be linked to an external system from the schedule if the following requirements are met:

    Procedure

    • Activate the PLANTA pulse or Jira checkbox (depending on which external system has been activated) in the Schedule module for the task to be synchronized with the required external system and save.
    • Right-click on the project header bar and select the Synchronize with PLANTA pulse or Synchronize with Jira command from the context menu.
    • As soon as the synchronization is completed, a message is displayed which informs you on whether the synchronization was completed successfully or whether problems occurred.
      • For a description of the further procedures in PLANTA pulse, see here.
      • For a description of the further procedures in the Jira system, see the Jira documentation.

    Details

    • As soon as the PLANTA pulse or Jira checkbox has been activated for a task, a link symbol VorgangExtern.png is displayed at the end of the task record in window 1 and in the graphical window next to the task bar. After synchronization of the task, you will be taken directly to the respective object in the external system (to the corresponding board in PLANTA pulse or to the corresponding epic in Jira).

    See also: PLANTA Hybrid, Jira Interface

    From DB 39.5.12

    PLANTA Hybrid: Synchronize Tasks with PLANTA pulse for Agile Project Editing

    Information

    • PLANTA provides an option for linking tasks from projects which are planned in PLANTA project to other systems where they can be planned and controlled agilely.
    • The linkage of tasks is done from the schedule of the respective project.

    Attention

    • The required tasks can only be linked to PLANTA pulse from the schedule if the interface to PLANTA pulse has been configured upfront. For this purpose, see the description under PLANTA Hybrid.

    Procedure

    • Display the PLANTA pulse relevant column in the Schedule module of the required project.
    • Activate the PLANTA pulse relevant checkbox for the task which is to be synchronized with PLANTA pulse and save.
    • Right-click on the project header bar and select the Synchronize with PLANTA pulse command from the context menu.
    • As soon as the synchronization is completed, a message is displayed which informs you on whether the synchronization was completed successfully or whether problems occurred.
    • For a description of the further procedures in PLANTA pulse, see here.

    Details

    • If a task has already been synchronized with PLANTA pulse, you can select the respective board from the Schedule module via the Switch to PLANTA pulse link in the Open PLANTA pulse field (the field is hidden by default).
      • The link is only displayed if the PLANTA project client is restarted after synchronization.
    • In the schedule, the tasks already synchronized with PLANTA pulse are marked with the PLANTA pulse symbol next to the bar of the respective task in window 3.

    New from DB 39.5.11

    PLANTA Hybrid: Synchronize Tasks with PLANTA pulse for Agile Project Editing

    Information
    • PLANTA provides an option for linking tasks from projects which are planned in PLANTA project to other systems where they can be planned and controlled agilely.
    • The linkage of tasks is done from the schedule of the respective project.

    Attention

    • The required tasks can only be linked to PLANTA pulse from the schedule if the interface to PLANTA pulse has been configured upfront. For this purpose, see the description under PLANTA Hybrid.

    Procedure

    • Display the PLANTA pulse relevant column in the Schedule module of the required project.
    • Activate the PLANTA pulse relevant checkbox for the task which is to be synchronized with PLANTA pulse and save.
    • Right-click on the project header bar and select the Synchronize with PLANTA pulse command from the context menu.
    • As soon as the synchronization is completed, a message is displayed which informs you on whether the synchronization was completed successfully or whether problems occurred.
    • For a description of the further procedures in PLANTA pulse, see here.

    Details

    • If a task has already been synchronized with PLANTA pulse, you can select the respective board from the Schedule module via the Switch to PLANTA pulse link in the Open PLANTA pulse field (the field is hidden by default).
      • The link is only displayed if the PLANTA project client is restarted after synchronization.
    • In the schedule, the tasks already synchronized with PLANTA pulse are marked with the PLANTA pulse symbol next to the bar of the respective task in window 3.


    Request Process Steps

    This function can only be used if the Request PLANTA component has been licensed.

    Procedure

    See also: Date, Resource, and Cost Calculation, Cost and Budget Planning, Links, Work Breakdown Structure, Structuring tasks via drag&drop, Graphical Editing in Gantt Chart, External Tasks
    Attachments Attachments
    Topic attachments
    I Attachment History Size Date Comment
    Pngpng ButtonTR.png r1 1.5 K 2010-12-20 - 11:20  
    Pngpng Ist.png r1 0.3 K 2012-10-30 - 08:21  
    Pngpng Kalk.png r1 0.5 K 2012-10-30 - 08:23  
    Pngpng MMS_krit.PNG r1 0.6 K 2012-10-29 - 14:41  
    Pngpng MS.png r1 0.6 K 2012-10-30 - 08:26  
    Pngpng MS_erl.PNG r1 0.6 K 2012-10-29 - 14:39  
    Pngpng Milestone.PNG r1 0.4 K 2012-10-29 - 14:35  
    Pngpng PlanungvergleichenButton.PNG r1 0.7 K 2014-05-13 - 11:57  
    Pngpng Puffer.png r1 0.4 K 2012-10-30 - 08:24  
    Pngpng Sammel.PNG r1 0.3 K 2012-10-29 - 14:37  
    Pngpng Sumtask.PNG r1 0.3 K 2012-10-29 - 14:37  
    Pngpng Unbenannt.PNG r1 0.5 K 2012-10-29 - 14:42  
    Pngpng Unkritisch.png r1 0.4 K 2011-04-14 - 09:34  
    Pngpng VGKalk.png r1 0.5 K 2011-04-14 - 09:33  
    Pngpng VGueberkrit.PNG r1 0.3 K 2012-10-29 - 14:38  
    Pngpng VorgangExtern.png r1 0.4 K 2020-03-30 - 09:52  
    Pngpng Wunsch.png r1 0.3 K 2013-07-18 - 14:10  
    Pngpng aufgabenbeschreibung.PNG r1 0.4 K 2014-11-06 - 10:12  
    Pngpng kritisch.png r1 0.3 K 2011-04-14 - 09:34  
    Pngpng long-arrow-left-light-blue.png r1 0.3 K 2020-05-12 - 16:26  
    Pngpng long-arrow-right-light-blue.png r1 0.3 K 2020-05-12 - 16:26  
    Pngpng retweet-light-to-right.png r1 1.4 K 2020-05-12 - 16:26  
    Pngpng retweet-light.png r1 0.3 K 2020-05-12 - 16:26  

             PLANTA project







     
    • Suche in Topic-Namen

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