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

Schedule MOD009C9E New from DB 39.5.0

Access path

Information

From DB 39.5.11

  • In this module, you can do the following:
    • for the program you can
      • create and edit tasks (in graphical or table form)
      • connect tasks via links
    • for the projects of the program.you can
      • have a look at tasks and milestones
      • connect tasks of the project in table form via links
    • connect tasks (master milestones) of the program and of the assigned projects in table form via links
    • NEW connect tasks (master milestones) of the program and of the assigned projects graphically via links For further information, see here.

Up to DB 39.5.11

  • In this module, you can do the following:
    • for the program you can
      • for the program (in graphical or table form).
      • define milestones and summary tasks for the program.
      • create links.
    • for the projects of the program.you can
      • for the projects of the program.

    • Attention

    From DB 39.5.11

    • NEW All newly created tasks of a program are milestones by default.
    • There is no resource planning possible in the program schedules.

    Up to DB 39.5.11

  • There is no resource planning possible in the program schedules.

    • Notes

    • In this module, dates of the program and its tasks, or the assigned projects and their tasks are displayed. Budget, costs, and effort of the program or of the assigned projects can be looked at as summarized total values or per yearly tranche in the Budget module. For detailed information on effort or costs of individual tasks of the assigned projects, please switch to the Project panel of the corresponding project (by clicking on the project ID).
    • Subprojects of the assigned projects which may exist will not be displayed in this module. By clicking on the project ID, you can switch to the corresponding project and have a look at the subproject data.

    From DB 39.5.10

    Module Variants
    Base Tasks are displayed with the assigned links. New program tasks and links can be created and edited for both programs and projects.
    Print A variant of the Schedule optimized for printing is displayed.
    Quality Gates NEW Displays the quality gates predefined by the portfolio manager and their todo items to be completed.

    Up to DB 39.5.10

    Module Variants
    Base Tasks are displayed with the assigned links. New program tasks and links can be created and edited for both programs and projects.
    Print A variant of the Schedule optimized for printing is displayed.

    Show legend... Hide legend

    Legend: Program/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    

    Create Schedule

    Information
    • The schedule of a program is created by creating individual tasks.
    Procedure
    • 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.

    Note

    • If you copy existing tasks, the following message will be displayed in the status line: The selected task IDs are already used. New IDs will be generated.

    Form WBS Code

    Procedure

    From DB 39.5.9

    • Structure the tasks hierarchically as required by moving them to the required position by holding down SHIFT + left mouse button.
    • Select Generate WBS code from the context menu by right-clicking on the program header NEW or click on the PSP.PNG Generate WBS code button (on the right of the program header).
      • The WBS code is generated automatically for every task in accordance with the structure and then appears in the WBS code field. Thus the WBS code is both an identifier for single elements in the schedule and an indicator of hierarchical structure.
        • Depending on the settings, the WBS code in the Task field is displayed. The WBS Code field in the Schedule module is hidden by default and can be displayed if necessary.
    • 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.

    Up to DB 39.5.9

  • Structure the tasks hierarchically as required by moving them to the required position by holding down SHIFT + left mouse button.
  • By right-clicking on the project header, select the Create WBS code command from the context menu.
    • The WBS code is generated automatically for every task in accordance with the structure and then appears in the WBS code field. Thus the WBS code is both an identifier for single elements in the schedule and an indicator of hierarchical structure.
      • Depending on the settings, the WBS code in the Task field is displayed. The WBS Code field in the Schedule module is hidden by default and can be displayed if necessary.
  • 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.

    • Tasks

    Edit Task

    Information
    • You can edit every task of a program schedule by editing its task parameters:

    Note

    • If some tasks have been defined as master milestones and the Schedule with gates checkbox has been activated in the Program Core Data module, master milestones are additionally displayed as gates directly below the scale.

    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.

    Terminate Task

    Procedure

    From DB 39.5.12

    Up to DB 39.5.12

    Notes

    Master Milestones

    Information

    From DB 39.5.11

    • NEW All newly created tasks of a program are milestones by default.

    Up to DB 39.5.11

    Procedure
    • Program tasks are to be defined as milestones or master milestones (gates) in the Milestone field.
      • In milestone planning, (duration, requested dates), some peculiarities must be considered. For further information, click here.

    Details

    • If the Schedule with gates checkbox has been activated in the Program Core Data module, master milestones will additionally be displayed in graphical view on the horizontal schedule axis in the program schedule directly below the scale and are called gates.
    • If one of the master milestones has been defined as a master milestone in the Program 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 as a master milestone, the last master milestone of the schedule is used to calculate the interval. If there is a master milestone on the calculated end date of the program, the respective gate also receives an interval indication (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 calculated because a main milestone has been newly selected or changed or if the calculated date of the program has changed.

    Change Note or Estimate

    From DB 39.5.15

    The note or estimate on a program task (master milestone) can only be changed in the Task module, which can be opened by clicking on the ID of the program task.

    Up to DB 39.5.15

    Information
    • The program 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.


    New from DB 39.5.14

    Read Out Task Chain

    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.

    Finish task

    Procedure

    Details

    • Completed tasks are displayed grayed-out.

    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.

    Internal and External Links

    Information
    • Internal links in a program schedule are links between individual tasks on program level.
    • External tasks in a program schedule are links
      • from the tasks of the program to the tasks of the child projects and vice versa or
      • from the tasks of a child project to the tasks of another child project.

    The procedure for creation of internal and external links in the program schedule is always the same.

    Tabular procedure

    • To do so, right-click on the required task and select the Insert Link context menu command. * A new, empty link record is created.
    • Fill the following fields in the new link record:
      • Project successor is preset by default with the project in which the link is created.
        • If an internal link is created, the preset remains.
        • If an external link is created, select the required project from the listbox.
      • Task successor
      • Link type (here the "ES" link type is preset by default).
      • Time interval (if required).
    • Save and recalculate the schedule by clicking on the calculation button in the toolbar.

    Graphical procedure

    From DB 39.5.11

    • move the mouse pointer to the bar from which a link is to be created (source bar).
      • Instead of the mouse pointer, a cross is displayed.
        • place the cross at the beginning or at the end of the source bar depending on which link type you wish to create (e.g. for the Finish-Start relationship, place the cross at 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).
        • A connection line between the two bars is 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 is created.

    Notes

    • For the creation of external links, you have to take into account that the target project is expanded far enough so that the target task is visible.
    • You can graphically create external links
      • from program to project, but not the other way around, or
      • from a program-project to another program-project
    • You can graphically edit all existing links.

    Up to DB 39.5.11

    Note
    • The graphical creation of external links is not possible in the program schedule.

    • For the creation of internal links
      • move the mouse pointer to the bar from which a link is to be created (source bar).
      • Instead of the mouse pointer, a cross is displayed.
        • place the cross at the beginning or at the end of the source bar depending on which link type you wish to create (e.g. for the Finish-Start relationship, place the cross at 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).
        • A connection line between the two bars is 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 is created.

    See also: Create, Edit, Delete Links

    External Tasks

    Information
    • External tasks are tasks of another project/program which can be displayed in the schedule of the selected program in order to visualize the dependencies between the program and other projects.

    Display an external task

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

    Note

    • In the program schedule, only external tasks on program level can be displayed. If you want to insert external tasks in program projects as well, you have to switch to the schedules of the respective program projects.

    See also: External Tasks


    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.

    See also: Date, Resource, and Cost Planning, Links, Work Breakdown Structure, Structuring tasks via drag&drop, Graphical Editing in Gantt Chart, insert records, External Tasks

    Attachments Attachments
    Topic attachments
    I Attachment History Size Date Comment
    Pngpng A.png r1 0.3 K 2014-03-03 - 13:31  
    Pngpng B.png r1 0.3 K 2014-03-03 - 13:31  
    Pngpng C.png r1 0.3 K 2014-03-03 - 13:31  
    Pngpng D.png r1 0.3 K 2014-03-03 - 13:31  
    Pngpng E.png r1 0.3 K 2014-03-03 - 13:32  
    Pngpng Ist.png r1 0.3 K 2014-03-03 - 13:33  
    Pngpng Kalk.png r1 0.5 K 2014-03-03 - 13:34  
    Pngpng PSP.PNG r1 1.3 K 2016-12-02 - 13:36  
    Pngpng Puffer.png r1 0.4 K 2014-03-03 - 13:35  
    Pngpng Verzug.png r1 0.5 K 2014-03-03 - 13:35  
    Pngpng Wunsch.png r1 0.3 K 2014-03-03 - 13:35  

             PLANTA project







     
    • Suche in Topic-Namen

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