Planning Objects Grouped MOD009BCW
Access
- Portfolio Management → Planning and Reports → Planning Objects Grouped
Information
- This module provides an overview of existing planning objects (projects, ideas, proposals, programs, and requests).
- New planning objects can be created here (provided that the user has the respective rights).
- All planning objects are displayed grouped by two variable group criteria (which can be selected via the respective listboxes in the module header).
- Additionally, the third fixed grouping criterion is used: Own planning object (the current user is manager of this planning object) / External planing object (another person than the current user is manager of the planning object).
Details
- Via the 1st Grouping and 2nd Grouping listboxes, grouping criteria can be changed. After you have clicked on the Apply changes button, main projects are grouped in accordance with the newly selected criteria.
- By right-clicking on the required planning object and selecting the Edit Planning Object context menu command, or by clicking on the ID of the required planning object, you switch to the respective planning object panel (project, idea, proposal, program) in which planning object data can be edited or viewed depending on the user’s rights.
- You can click on the New Planning Object button in order to create new ideas, proposals, projects, programs, or requests.
- Only users with multi-project manager, multi-portfolio manager, and multi-project/multi-request manager rights are allowed to create ideas, proposals, and projects from this module.
Module Variants
Base | In the Base variant, all planning objects (own and other) are grouped by Type and Code by default. |
With evaluation data | For each planning object, evaluation data like, e.g., risk value, objective contribution, capital value, etc., is displayed. |
Only own planning objects | Only planning objects for which the current user is manager will be displayed. |
Only external planning objects | Only planning objects for which a person other than the current user is manager will be displayed. |
Legend
The legend applies to all planning objects except requests, since they have no Gantt charts.
Symbol | Meaning | Color | Comment |
---|---|---|---|
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). | ||
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 . | |
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 calculation of the schedule of the respective planning object by clicking on the calculation button . | |
Float | Float available when the calculated end date (Calc. end) is earlier than the requested end date (Requested end). | ||
Date delay | A date delay occurs when 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. | ||
External links | outgoing incoming | ||
Master milestones | without delay | Tasks are defined as master milestones in the Schedule module. | |
Master milestone delay | Master milestone delay exists if Calc. end of a master milestone is later than its Latest end. |