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

Programs MOD009C9U New from DB 39.5.0

From DB 39.5.13

Access path

From DB 39.5.9

Access path

Up to DB 39.5.9

Access path

Information

  • This module shows an overview of all programs created and all projects contained in the programs.

From DB 39.5.15

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.
  • By expanding the tree structure, the projects assigned to the programs can be displayed or hidden.
  • Below the scale, the dates of programs and projects as well as their master milestones are additionally visualized by the bars.
  • NEW When you click on the arrows in the scale area ( AOBEin.png for incoming and AOBAus.png for outgoing links), external links of the planning object can be opened in a dialog module. By clicking on the arrow once more, the module is closed again.

Up to DB 39.5.15

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.
  • By expanding the tree structure, the projects assigned to the programs can be displayed or hidden.
  • Below the scale, the dates of programs and projects as well as their master milestones are additionally visualized by the bars.

Legend: Program/Project

From DB 39.5.15

Symbol Meaning Color Comment
WunschDB14.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
KalkPRDB14.png Calculated dates The color of the bar is determined by the code of the planning object.
CodeADB14.png Code A
CodeBDB14.png Code B
CodeCDB14.png Code C
CodeDDB14.png Code D
CodeEDB14.png 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.
ActDB14.png 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.
Verzug.png 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.
MMSbigDB14.png Gates MMSbigDB14.png Gate without date delay
MMSredbigDB14.png Gate with date delay
HMSDB14.png Main gate/main milestone
Gates are master milestones of planning objects.
Without date delay means: Total float 0
With date delay means: Total float < 0

Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
VGueberkrit.PNG Master milestone date delay   A master milestone date delay occurs if its Calc. end is later than its Latest end.
AOBAus.png external links AOBAus.png outgoing
AOBEin.png incoming
 

From DB 39.5.14

Symbol Meaning Color Comment
WunschDB14.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
KalkPRDB14.png Calculated dates The color of the bar is determined by the code of the planning object.
CodeADB14.png Code A
CodeBDB14.png Code B
CodeCDB14.png Code C
CodeDDB14.png Code D
CodeEDB14.png 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.
ActDB14.png 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.
Verzug.png 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.
MMSbigDB14.png Gates MMSbigDB14.png Gate without date delay
MMSredbigDB14.png Gate with date delay
HMSDB14.png Main gate/main milestone
Gates are master milestones of planning objects.
Without date delay means: Total float 0
With date delay means: Total float < 0

Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
VGueberkrit.PNG Master milestone date delay   A master milestone date delay occurs if its Calc. end is later than its Latest end.

From DB 39.5.12

Symbol Meaning Color Comment
Wunsch.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Program Core Data).
KalkPRDB12.PNG Calculated dates The color of the bar is determined by the code of the planning object.
CodeADB12.PNG Code A
CodeBDB12.PNG Code B
CodeCDB12.PNG Code C
CodeDDB12.PNG Code D
CodeEDB12.PNG 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.
ActDB12.png 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.
Verzug.png 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.
MMSbig.png Gates MMSbig.png Gate without date delay
MMSredbig.png Gate with date delay
HMS.png Main gate/main milestone
Gates are master milestones of planning objects.
Without date delay means: Total float 0
With date delay means: Total float < 0

Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
VGueberkrit.PNG Master milestone date delay   A master milestone date delay occurs if its Calc. end is later than its Latest end.

From DB 39.5.11

Symbol Meaning Color Comment
Wunsch.png Requested dates   Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Program Core Data).
Kalk.png Calculated dates The bar color is defined by the code of the planning object.
A.png Code A
B.png Code B
C.png Code C
D.png Code D
E.png Code E
Calc. start and Calc. end of a planning object are determined in the calculation of the schedule of the respective planning object.
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.
Ist.png 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.
Verzug.png 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.
MMSbig.png Gates MMSbig.png Gate without date delay
MMSredbig.png Gate with date delay
HMS.png Main gate/main milestone
Gates are master milestones of planning objects.
Without date delay means: Total float 0
With date delay means: Total float < 0

Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
VGueberkrit.PNG Master milestone date delay   A master milestone date delay occurs if its Calc. end is later than its Latest end.

From DB 39.5.9

Symbol Meaning Color Comment
Kalk.png Calculated dates The bar color is defined by the code of the planning object.
A.png Code A
B.png Code B
C.png Code C
D.png Code D
E.png Code E
Calc. start and Calc. end of a planning object are determined in the calculation of the schedule of the respective planning object.
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.
Ist.png 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.
Verzug.png 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.
MMSbig.png Gates MMSbig.png Gate without date delay
MMSredbig.png Gate with date delay
HMS.png Main gate/main milestone
Gates are master milestones of planning objects.
Without date delay means: Total float 0
With date delay means: Total float < 0

Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
VGueberkrit.PNG Master milestone date delay   A master milestone date delay occurs if its Calc. end is later than its Latest end.

Up to DB 39.5.9

Symbol Meaning Color Comment
DauerProjekt.PNG Calculated project dates   Calc. start and Calc. end of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
MS.PNG Master milestones MMS_krit.PNG with date delay
MS.PNG without date delay
Tasks are defined as master milestones in the Schedule module.
Topic attachments
I Attachment History Size Date Comment
Pngpng DauerProjekt.PNG r1 0.4 K 2014-03-06 - 19:52  

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl