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 acts as a manager are displayed. |
Only other planning objects | Only planning objects for which another person (who is not the current user) acts as a manager are displayed. |
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 projects | Only planning objects for which the current user acts as a manager are displayed. |
Only other projects | Only planning objects are for which another person (who is not the current user) acts as a manager are displayed. |
Legend The legend applies to all planning objects except requests, since they have no Gantt charts.From DB 39.5.14
Symbol Meaning Color Comment
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 ECalc. 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) of the planning object is earlier than the requested end date (Requested end).
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.
Up to DB 39.5.14
Symbol Meaning Color Comment
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 ECalc. 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) of the planning object is earlier than the requested end date (Requested end).
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.