Access

Information

Details

  • All panning objects are 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 a manager.
    • My Subprojects: In this subgroup, planning objects are displayed for which the logged on user is a 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 a stakeholder without modification rights.
    • Stakeholder with modification rights: In this area, planning objects are displayed for which the logged on user is a stakeholder with modification rights.
    • Tasks: In this area, planning objects are displayed, in which the logged on user is defined as a 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.
  • By clicking on the number in the Forecasts field, you automatically switch to the Progress module in which you can have a look at details of existing forecasts.
  • In the right window the graphical display is realized in the form of date bars with information on the calculated dates, requested dates, float, delay, and master milestones of the planning objects. See also the legend below.

Note

  • 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.

Legend

SymbolMeaningColorComment
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 .
The code of the planning objects is defined and changed in the Edit Planning Objects module (the code of projects and proposals can also be defined and changed in the Project Core Data and Proposal Core Data modules.

Actual datesThe 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
with delay
with Actual end

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.