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

CurrentEN Web>UserDocumentation>UserModules>MyPlanningObjectsMOD0099RB

My Planning Objects MOD0099RB

Access path

Project Management Planning My Planning Objects
Employee Own Planning Employee Board My Planning Objects

Information

In the My Planning Objects module, active (Status = "active") planning objects which are not yet finished (no Actual end) are displayed,
- for which the current user has modification rights , e.g. if the current user is a project manager or a stakeholder with modification rights (deputy).
- for which the current user only has read access, i.e. for which the user is a stakeholder without modification rights.
The manager's estimate and the calculated status of costs, effort, and dates calculated by the system are visualized with the respective symbols for every planning object.

Details

From DB 39.5.13

All planning objects are displayed grouped by their type: Projects, Ideas, Proposals, Requests, Programs.
Within these groups, planning objects are divided into the following subgroups:
- My Main Projects, My Ideas, My Proposals, My Requests, My Programs: In these subgroups, planning objects are displayed for which the logged on user is Manager.
- My Subprojects: In this subgroup, planning objects are displayed for which the logged on user is manager. This subgroup is only available in the Projects group.
- Stakeholder without modification rights: In this group, planning objects are displayed for which the logged on user is Stakeholder without modification rights.
- Stakeholder with modification rights: In this area, planning objects are displayed for which the logged on user is Stakeholder with modification rights.
- Tasks: In this area, planning objects are displayed, in which the logged on user is defined as person responsible for the task for one or several tasks.
- The respective group or subgroup is only displayed if it contains at least one planning object.
By clicking on the ID of the required planning object, you can directly switch to the panel of this object, where you can view or edit data depending on the user rights.
In the right-hand window, you see the Gantt view with information on requested dates, milestone delay and float of the planning objects. See also the legend below.

From DB 39.5.1

All planning objects are displayed grouped by their type: Projects, Ideas, Proposals, Requests, NEW Programs.
Within these groups, planning objects are divided into the following subgroups:
- My Main Projects, My Ideas, My Proposals, My Requests, NEW My Programs: In these subgroups, planning objects are displayed for which the logged on user is Manager.
- My Subprojects: In this subgroup, planning objects are displayed for which the logged on user is manager. This subgroup is only available in the Projects group.
- Stakeholder without modification rights: In this group, planning objects are displayed for which the logged on user is Stakeholder without modification rights.
- Stakeholder with modification rights: In this area, planning objects are displayed for which the logged on user is Stakeholder with modification rights.
- Tasks: In this area, planning objects are displayed, in which the logged on user is defined as person responsible for the task for one or several tasks.
- The respective group or subgroup is only displayed if it contains at least one planning object.
In the Info field you can see (blue circle with the New title) whether current messages are available for a certain planning object.
- NEW By right-clicking on the info symbol and selecting the Focus new info command from the context menu, you switch to the Info module, in which the current messages can be viewed.
  - Current messages are messages that are not marked as read.
By clicking on the ID of the required planning object, you can directly switch to the panel of this object, where you can view or edit data depending on the user rights.
In the right-hand window, you see the Gantt view with information on requested dates, milestone delay and float of the planning objects. See also the legend below.

Up to DB 39.5.1

All panning objects are grouped by their type.
The following work areas are displayed:
- My Main Projects (My Ideas, My Proposals, My Requests): This area is displayed if the current user is the manager of a planning object.
- My subprojects: This area is displayed if the current user is a subproject manager of the appropriate projects. This area is only displayed for planning objects of the Project Type.
- Stakeholder without modification rights: This area is displayed if the current user is a stakeholder without modification rights.
- Stakeholder with modification rights: This area is displayed if the current user is a stakeholder with modification rights.
- Tasks - This area is displayed if the current user is defined as person responsible.
In the Info field you can see (blue circle with the New title) whether current messages are available for a certain planning object.
- Current messages are messages that are not marked as read.
- You can see current messages either in the Info module in the Inbox area or in the Dashboard module of the corresponding project.
By clicking on the ID of the required planning object, you can directly switch to the panel of this object, where you can view or edit data depending on the user rights.
In the right-hand window, you see the Gantt view with information on requested dates, milestone delay and float of the planning objects. See also the legend below.

Note

From S 39.5.10

NEW In the grouping of the planning objects, the Manager property is dominant. I.e., if a user is a stakeholder with modification rights and manager of a planning object, the planning object is grouped under My Main Projects (My Ideas, My Proposals, My Programs, My Requests) or My Subprojects.
If the rights of the user change in planning objects, the display in the My Planning Objects module is only updated after restart of the program since the rights are checked and reloaded during restart.

From S 39.5.10

In the grouping of the planning objects, the Stakeholder with Modification Rights property is dominant. I.e., if a user is Stakeholder with Modification Rights and Manager of a planning object, the project is grouped under Stakeholder with Modification Rights.

If the rights of the user change in planning objects, the display in the My Planning Objects module is only updated after restart of the program since the rights are checked and reloaded during restart.

Legend

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 shaded in white. The background color depends on the Project Code. Actual start and, if available Actual end, otherwise Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.

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.

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, if available, Actual end, in any other case the Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.

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 shaded in white. The background color depends on the Project Code.	Actual start and, if available Actual end, otherwise Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
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.
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, if available, Actual end, in any other case the Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
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.

39.5 Venus Current EN

PLANTA project

PLANTA pulse

PLANTA project

Suche in Topic-Namen
Suche in Topic-Inhalten