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

CurrentEN Web>UserDocumentation>UserModules>ProjectsMOD0099G2

Projects MOD0099G2

From DB 39.5.13

Access path

Multi-Project Management NEW Project Planning Multi-Project Board panel Projects
Resource Management NEW Reports Multi-Project Board panel Projects

From DB 39.5.9

Access path

Multi-Project Management NEW Planning Multi-Project Board panel Projects
Resource Management NEW Reports Multi-Project Board panel Projects

Up to DB 39.5.9

Access path

Multi-Project Management Multi-Project Management Multi-Project Board panel Projects
Resource Management Multi-Project Reports Multi-Project Board panel Projects

Information

From DB 39.5.14

This module provides the multi-project manager with an overview of already existing projects and proposals which the multi-project manager is authorized to view.
- NEW If they are structured projects, the subprojects can be expanded below the main projects.
- Overhead cost projects (Posting type = 0) are not considered in this module.

From DB 39.5.11

This module provides the multi-project manager with an overview of already existing projects and NEW proposals which the multi-project manager is authorized to view.

If the projects are structured projects, only their main projects are displayed.
Overhead cost projects (Posting type = 0) are not considered in this module.

Up to DB 39.5.11

This module provides the multi-project manager with an overview of already existing projects which the multi-project manager is authorized to view.

If there are structured projects among them, only their main projects are displayed here.
Overhead cost projects (Posting type = 0) are not considered in this module.

Details

From DB 39.5.15

The projects displayed in this module are grouped by Code by default. It is, however, possible to change groupings or have projects displayed ungrouped.
- In the Group by field, you can either change the grouping criterion by making a selection from the listbox, or delete it. After you have clicked on the Use changes button, the projects are either displayed grouped by the selected criterion or they are displayed ungrouped.
- If a grouping criterion is selected in one of the modules which use grouping criteria, it automatically takes effect in all modules with groupings.
The projects to be displayed in this module can be filtered using object filters.
- If there already is an object filter, it can be selected from the listbox on the Filter field. After you have clicked on the Use changes button, only projects which correspond to the filter will be displayed.
- You can edit existing object filters or create new ones in the Object Filter module which is opened via the Edit filter button.
- If a grouping criterion is selected in one of the modules which use object filters, it automatically takes effect in all other modules with object filters.
By clicking on the ID of the required project, you can switch to the corresponding Project panel in which you can edit or view the program data depending on your user rights.
By clicking on the New project button, you switch to the Project panel, in which a new project can be created.
- Only users with multi-project manager, multi-portfolio manager, or multi-project/request manager rights can create new projects from this module.
If you have the Type column displayed, you can see which planning object type the respective planning object is of, project or proposal.
NEW When you click on the arrows in the scale area ( for incoming and for outgoing links), external links of the planning object can be opened in a dialog module. By clicking on the arrow once more, the module is closed again.

From DB 39.5.12

The projects displayed in this module are grouped by Code by default. It is, however, possible to change groupings or have projects displayed ungrouped.

In the Group by field, you can either change the grouping criterion by making a selection from the listbox, or delete it. After you have clicked on the Use changes button, the projects are either displayed grouped by the selected criterion or they are displayed ungrouped.
If a grouping criterion is selected in one of the modules which use grouping criteria, it automatically takes effect in all modules with groupings.

The projects to be displayed in this module can be filtered using object filters.

If there already is an object filter, it can be selected from the listbox on the Filter field. After you have clicked on the Use changes button, only projects which correspond to the filter will be displayed.
You can edit existing object filters or create new ones in the Object Filter module which is opened via the Edit filter button.
If a grouping criterion is selected in one of the modules which use object filters, it automatically takes effect in all other modules with object filters.

By clicking on the ID of the required project, you can switch to the corresponding Project panel in which you can edit or view the program data depending on your user rights.

By clicking on the New project button, you switch to the Project panel, in which a new project can be created.

Only users with multi-project manager, multi-portfolio manager, or multi-project/request manager rights can create new projects from this module.

NEW By displaying the Type column, you can see which planning object type the respective planning object is of, project or proposal.

Up to DB 39.5.12

The projects displayed in this module are grouped by Code by default. It is, however, possible to change groupings or have projects displayed ungrouped.

In the Group by field, you can either change the grouping criterion by making a selection from the listbox, or delete it. After you have clicked on the Use changes button, the projects are either displayed grouped by the selected criterion or they are displayed ungrouped.
If a grouping criterion is selected in one of the modules which use grouping criteria, it automatically takes effect in all modules with groupings.

The projects to be displayed in this module can be filtered using object filters.

If there already is a filter, it can be selected from the listbox on the Filter field. After you have clicked on the Use filter button, the projects which correspond to the filter are displayed in groups.
You can edit existing filters or create new ones in the Object Filter module which is opened via the Edit filter button.
If a grouping criterion is selected in one of the modules which use grouping criteria, it automatically takes effect in all modules with groupings.

By clicking on the ID of the required project, you can switch to the corresponding Project panel in which you can edit or view the program data depending on your user rights.

By clicking on the New project button, you switch to the Project panel, in which a new project can be created.

Only users with multi-project manager, multi-portfolio manager, or multi-project/request manager rights can create new projects from this module.

Module variants

From DB 39.5.14

Base	All active projects are displayed, i.e. projects with Status = 1 (active) and NEW proposals are displayed.
Inactive projects	All inactive projects are displayed, i.e. projects with Stats = 2 (inactive).
Template projects	In the listbox, all projects with Status = 0 (template) are displayed. These projects can be used as a template when creating a schedule in new projects.
Archived projects	All inactive projects are displayed, i.e. projects with Status = 9 (archive).
Overhead cost projects NEW	All overhead cost projects are displayed, hence projects with Posting type = 1 (Actual postings also in the future).

From DB 39.5.11

Base	All active projects are displayed, i.e. projects with Status = 1 (active) and NEW proposals are displayed.
Inactive projects	All inactive projects are displayed, i.e. projects with Stats = 2 (inactive).
Template projects	In the listbox, all projects with Status = 0 (template) are displayed. These projects can be used as a template when creating a schedule in new projects.
Archived projects	All inactive projects are displayed, i.e. projects with Status = 9 (archive).

From DB 39.5.0

Base	All active projects are displayed, i.e. projects with Status = 1 (active).
Inactive projects	All inactive projects are displayed, i.e. projects with Stats = 2 (inactive).
Template projects	In the listbox, all projects with Status = 0 (template) are displayed. These projects can be used as a template when creating a schedule in new projects.
Archived projects	All inactive projects are displayed, i.e. projects with Status = 9 (archive).

Up to DB 39.5.0

Base	All active projects are displayed, i.e. projects with Status = 1 (active).
Inactive projects	All inactive projects are displayed, i.e. projects with Stats = 2 (inactive).
Templates	All projects with Status = 0 (standard) are displayed. These projects can be used as a template when creating a schedule in new projects.
Archived projects	All inactive projects are displayed, i.e. projects with Status = 9 (archive).

Legend

From DB 39.5.15

Symbol Meaning Color Comment

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

Calculated dates The color of the bar is determined by the code of the planning object.
Code A
Code B
Code C
Code D
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.

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.

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

Date delay A date delay occurs if the calculated end date (Calc. end) 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.

Master milestones Without date delay
With date delay Tasks are defined as master milestones in the Schedule module.

external links outgoing
incoming

From DB 39.5.14

Symbol Meaning Color Comment

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

Calculated dates The color of the bar is determined by the code of the planning object.
Code A
Code B
Code C
Code D
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.

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) in the calculation of the schedule of the respective planning object.

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

Date delay A date delay occurs if the calculated end date (Calc. end) 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.

Master milestones Without date delay
With date delay Tasks are defined as master milestones in the Schedule module.

From DB 39.5.12

Symbol Meaning Color Comment

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

Calculated dates The color of the bar is determined by the code of the planning object.
Code A
Code B
Code C
Code D
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.

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.

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

Date delay A date delay occurs if the calculated end date (Calc. end) 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.

Master milestones Without date delay
With date delay Tasks are defined as master milestones in the Schedule module.

Up to DB 39.5.12

Symbol Meaning Color Comment

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

Calculated dates The color of the bar is determined by the code of the planning object.
Code A
Code B
Code C
Code D
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.

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.

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

Date delay A date delay occurs if the calculated end date (Calc. end) 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.

Master milestones With date delay
Without date delay Tasks are defined as master milestones in the Schedule module.

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D 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.
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.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) 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.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.
external links	outgoing incoming

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D 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.
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) in the calculation of the schedule of the respective planning object.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) 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.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D 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.
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.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) 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.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D 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.
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.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) 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.
Master milestones	With date delay Without date delay	Tasks are defined as master milestones in the Schedule module.