My Watchlist MOD009C9K New from DB 39.5.0

Information

• In this module, the program manager can have programs displayed, which he or she wants to observe.
  • In order to be allowed to use the watchlist function, the logged-on user must be defined in the system as a Stakeholder.

Assign planning objects to the watchlist/remove planning objects from the watchlist

Details

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

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.