Project and Portfolio Management
Version 27 Version 26 39.5.25 39.5.23 39.5.22 39.5.21 39.5.20 39.5.19 39.5.18 39.5.17 German English
Version 27 Version 26 39.5.25 39.5.23 39.5.22 39.5.21 39.5.20 39.5.19 39.5.18 39.5.17 German English

Schedule (Gantt) - Program MOD009E6L

Introduction

  • Planning → Programs panel → Click on the ID of the required program → Program panel → Schedule (Gantt)

Alternative Introduction

Alternative Introduction

  • There are several ways to access the desired planning object or portfolio panel and its associated modules:

    • via Quick Access in the user menu (My Objects and Favorites)

    • via the Global Search function in the user menu (Direct Entry)

    • via links on planning objects or portfolios in various modules


For information

  • In this module you can

    • create and edit program tasks (in graphically or in table form)

    • connect program tasks via links

    • see tasks and milestones of the corresponding projects

    • connect tasks of the corresponding projects in table form via links

    • connect tasks (master milestones) of the program and of the assigned projects graphically or in table form via links

Caution

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

  • Resource planning is not possible in the program schedules.

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

Displays the quality gates predefined by the portfolio manager and their activities to be completed.

Show legend...

Legend: Program/Project

Symbol

Meaning

Color

Comment

WunschDB14.png


Requested dates


Requested start and Requested end are defined in the Key dates area in the respective core data module (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 determined during the calculation of the schedule of the respective planning object (by clicking on the calculate_schedule.png Calculate Schedule button).
You can define and change the code of the planning objects in the Edit Planning Objects module, for projects and proposals you can also do this in the Project Core Data and Proposal Core Data modules.

ActDB14.png


Actual dates

The bar is hatched in white. The background color depends on the code of the planning object.

Actual start and Actual end (if available, otherwise Latest time recording date ) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) during the calculation of the schedule of the respective planning object (by clicking on the calculate_schedule.png Calculate schedule button).

Puffer.png


Float


Float available when the calculated end date (Calc. end) is earlier than the requested end date (Requested end).

Verzug.png


Delay


A delay occurs when the calculated end date (Calc. end) is later than the requested end date (Requested end).
The delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.

AOBAus.png


External Links

AOBAus.png outgoing
AOBEin.png incoming


MMSbigDB14.png


Gates

MMSbigDB14.png Gate without delay

MMSredbigDB14.png Gate with delay

HMSDB14.png Main gate/main milestone

A gate is a master milestone of the planning objects.
Without delay means: Total float >= 0
With delay means: Total float < 0

Gates are only displayed in the Schedule module if the Schedule with gates checkbox has been activated in the core data module of the respective planning object

Master milestones with Actual end are not displayed as gates.

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.


Legend: Task

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 in the bar chart.

KalkDB12.PNG


Calculated dates of the tasks

KalkDB12.PNG uncritical

CalcCritDB12.PNG critical

Calc. start and Calc. end of a task are determined during the calculation of the schedule (by clicking on the calculate_schedule.png Calculate Schedule button).
Uncritical means: Total float > 0
Critical means: Total float <= 0
Since in PLANTA project the definition of requested dates on tasks leads to Total float = 0, tasks which 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 consisting of sub-tasks which are summarized here. 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 hatched in white color if the Splitting parameter is deactivated, and gray hatched if the parameter is activated.

The Actual start and, if available, the Actual end, or otherwise the Latest time recording date of a task, are determined when calculating the schedule (by clicking on the calculate_schedule.png Calculate Schedule button) from the corresponding dates of the resources assigned to the process, or they can be set manually.

Puffer.png

Latest Dates


Latest start and Latest end of a task are determined when calculating the schedule (by clicking on the calculate_schedule.png Calculate Schedule button).

VGueberkrit.PNG

Task delay


A delay exists if Calc. end of a master milestone is later than its Latest end.

Ueberlappung.PNG

Task overlapping


Overlapping = possible delay of task successor when using soft links. For further information, see here.

AOBAus.png


External Links

AOBAus.png outgoing

AOBEin.png incoming



External Tasks

Symbol

Meaning

Color

Comment

KalkExtDB12.PNG


Calculated dates of external tasks

KalkExtDB12.PNG uncritical
KalkExtredDB12.png critical

Calc. start and Calc. end of the external tasks are calculated by clicking on the calculate_schedule.png Calculate schedule button.
Uncritical means: Total float > 0
Critical means: Total float <= 0
Since in PLANTA project the definition of requested dates on tasks leads to Total float = 0, tasks which do not necessarily lie on the critical path can be critical as well.

SammelExtVGDB14.png


Calculated dates of external summary tasks



MSextDB12.png / MMSExtDB12.PNG

Milestones/master milestones of the external summary tasks

MSextDB12.png / MMSExtDB12.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

MMSmitIstEnde MMSmitIstEnde

Requested dates of external tasks


Requested start and Requested end are defined in the Key dates area in the respective core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).


Create Schedule

Information

  • The schedule of a program is automatically created when you create individual tasks which are milestones at the same time.

Procedure

  • Insert an empty task row, e.g., by clicking the New Task button in the action bar or the green plus icon directly below it.

  • Enter a task name in the Task name field.

  • Create further tasks in the same way.

  • Save and click on the Rad_One_Rand.png Generate WBS code button. As a result, an ID will automatically be generated for the new task in the Task field. In PLANTA standard, the WBS codes are used as task IDs in schedules.

Tasks in PLANTA project have two IDs:

  • A technical task ID is automatically created. It is an incrementing task number which is usually invisible in user modules in the PLANTA standard system.

  • A functional task ID is either generated automatically or allocated manually.

    • Via the global Use WBS code instead of ID parameter you can define which of these three variants will be used as functional ID. The chosen functional ID then applies system-wide to all user modules in which tasks are displayed.


Tasks (Master Milestones)

Information

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

Edit task

Information

  • By entering or changing the task parameters in the required fields of the Task module the individual tasks of a program schedule can be edited.

Terminate Task

Procedure

  • Enter Requested start and Requested end in the respective fields or define the Remaining duration.

  • Click on the Calculate schedule button in the action bar. In doing so, calculated dates of the task (Calc. start and Calc. end) are calculated automatically.

    • If you do not define any requested dates for tasks but only durations, the Requested start of the project will be used as start date for the calculation. If you have not defined any requested dates for the project either, the tasks will be defined from today’s date on.


Change Note/Estimate Flag

The note or the estimation of a program task (master milestone) can be changed in the Task module.

Read Out Task Chain

Procedure

  • Right-click on the required task.

  • Select the Show predecessor/successor context menu command.

  • The What do you want to do? dialog message is displayed with selection options (via the buttons) for the display of the data in the Task Chain module.

    • Depending on the selection made in the dialog module, the following is displayed in the Task Chain module:

      • direct predecessors or direct successors of the selected task or

      • all predecessors or all successors of the selected task or

      • all predecessors and successors of the selected task (i.e. the entire network).


Finish Task

Procedure

  • Enter the required end date in the Actual end data field in the line of the required task.

  • Save and recalculate the schedule.

Links map dependencies between tasks of in a project and have an impact on the calculation of the project dates. For information on the options for mapping dependencies between projects, please click here.

Information

  • Internal links in a program schedule are links between individual tasks (master milestones) at program level.

  • External links in a program schedule are links from the program's tasks to the tasks of the assigned projects and vice versa, or from the tasks of an assigned project to the tasks of another assigned project.

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.

Quality Gates

Information

  • Quality Gates are a type of controlling element of the portfolio manager for monitoring the progress of the planning objects contained in the portfolio.

  • Quality gates are defined by the portfolio manager, scheduled and assigned to the individual planning objects.

  • Project managers or program managers can see the assigned quality gates in the Schedule in the Quality Gates module variant of the corresponding planning object and record the probable date of completion of the quality gates and therefore enable the portfolio manager to monitor the compliance with the specifications.

Edit Quality Gates

  • Enter the estimated date for the completion of the quality gate in the Prob. completed on field.

  • In the % completed field, enter or update the degree of completion of of the quality gate.

    • Note: the Actual end field is filled by the project manager by setting the Approval in the Quality Gates module.

Since, from a technical point of view, quality gates are tasks, the requested end calculated for them can influence the project dates. As quality gates are automatically transferred to the planning object when the planning object is assigned to the portfolio, you may have to check the schedules of the planning objects or the dates of the quality gates after assigning the planning objects to portfolios.