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

Deviations MOD009AC1 From DB 39.5.7

Description for versions < S 39.5.7


Access path

From DB 39.5.9

Up to DB 39.5.9

  • Project panel Deviations
  • Information

    • In this module, the current project status can be compared to the status of already existing, released status reports.

    Procedure

    From DB 39.5.10

    • When you open the Deviations module for the first time, the current planning data and the data from the most recent of the selected status reports is displayed. If the status reports have already been compared for the selected project, data of the last compared status report is loaded by default when you open the Deviations module.
    • If there are further released status reports in the project which are also released for analysis. You can have them displayed in a dialog module and select them for comparison via the NEW Report selection button at the bottom margin of the Deviations module.
      • Newly created and released status reports are also released for analysis by default and are automatically available in the report selection dialog module of the Deviations module for comparison purposes.
    • Click on the number of the required status report. The data of the report is displayed next to the current data of the project and can be compared.

    Up to DB 39.5.10

  • When you open the Deviations module for the first time, the current planning data and the data from the most recent of the selected status reports is displayed. If the status reports have already been compared for the selected project, data of the last compared status report is loaded by default when you open the Deviations module.
  • At the bottom of the module, in the Report selection area, further status reports are possibly offered for selection. Whether and which status reports are listed here depends on whether they have been released for analysis in the Configure Trend Analysis module by activating the Milestone trend analysis checkbox.
    • For newly created and released status reports, the Milestone trend analysis checkbox is active by default, so that they are automatically available in the Deviations module for comparison purposes.
  • Click on the number of the required status report. The data of the report is displayed next to the current data of the project and can be compared.
  • Details

    • The New traffic light indicates new tasks of the current schedule, i.e. tasks which had not existed in the schedule at the time of creation of the selected status report.
    • For tasks which are neither contained in the status report nor in the current planning, no traffic lights are displayed.
    • In the No longer available in the current plan area, tasks are displayed which had still existed in the schedule at the time of creation of the selected status report but which have already been removed from the current schedule.

    New from DB 39.5.9

    Notes
    • If changes are made to other modules which have an influence on the data in the Deviations module while the Deviations module is running, the Refresh button is displayed at the bottom margin of the Deviations module, which
      • signalizes that there are changes which are not yet represented in the running Deviations module, and
      • is furthermore used to refresh the display in the module.

    Module Variants

    From DB 39.5.7

    Base Only tasks the deviation values of which are > 0 or NEW < 0 (indicated by red, yellow, or green traffic lights) are displayed.
    Tasks are displayed grouped by three criteria: end date, costs, and effort.
    In every grouping area, only data of the respective grouping criterion is displayed for each task.
    All end dates All tasks of the project are displayed with end date values.
    All effort data All tasks of the project are displayed with effort values.
    All cost data All tasks of the project are displayed with cost values.

    Up to DB 39.5.7

    Base Only tasks the deviation values of which are > 0 (indicated by red or yellow traffic lights) are displayed.
    Tasks are displayed grouped by three criteria: end date, costs, and effort.
    In every grouping area, only data of the respective grouping criterion is displayed for each task.
    All end dates All tasks of the project are displayed with end date values.
    All effort data All tasks of the project are displayed with effort values.
    All cost data All tasks of the project are displayed with cost values.

    Legend

    Project

    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.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
    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.
    KalkSBDB13.png Calculated dates from status report   Calc. start and Calc. end of the planning object from the selected status report.

    From DB 39.5.13

    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.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
    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.
    KalkSBDB13.png Calculated dates from status report   Calc. start and Calc. end of the planning object from the selected status report.

    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.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
    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.
    KalkSBDB12.png Calculated dates from status report The color of the bar equates to that of the project code (see the legend above), however, it is slightly lighter. Calc. start and Calc. end of the planning object from the selected status report.

    From DB 39.5.7

    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.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
    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.
    KalkSB.PNG Calculated dates from status report   Calc. start and Calc. end of the planning object from the selected status report.

    Up to DB 39.5.7

    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.
    KalkSB.PNG Calculated dates from status report   Calc. start and Calc. end of the planning object from the selected status report.

    Task

    From DB 39.5.14

    Symbol Meaning Color Comment
    WunschDB14.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical
    Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item.
    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can be critical as well.
    MSDB14.png / MMSDB14.png Milestones/
    Master milestones
    MSDB14.png / MMSDB14.png Without delay
    MSredDB14.png / MMSredDB14.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end
    Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    KalkSBDB13.png Calculated dates of the tasks from status report   Calculated dates of the tasks from status report Calc. start and Calc. end of the tasks from the selected status report.
    MSextDB13.png / MMSExtDB13.png Milestones/master milestones of the tasks from the status report    
    SammelVGSBDB12.png Calculated dates of the summary tasks from status report   Calc. start and Calc. end of the summary tasks from the selected status report.

    From DB 39.5.13

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical
    Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item.
    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can be critical as well.
    MSDB12.png / MMSDB12.png Milestones/
    Master milestones
    MSDB12.png / MMSDB12.png Without delay
    MSredDB12.png / MMSredDB12.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end
    Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    KalkSBDB13.png Calculated dates of the tasks from status report   Calculated dates of the tasks from status report Calc. start and Calc. end of the tasks from the selected status report.
    MSextDB13.png / MMSExtDB13.png Milestones/master milestones of the tasks from the status report    
    SammelVGSBDB12.png Calculated dates of the summary tasks from status report   Calc. start and Calc. end of the summary tasks from the selected status report.

    From DB 39.5.12

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    KalkDB12.PNG Calculated dates of the tasks KalkDB12.PNG Uncritical
    CalcCritDB12.PNG Critical
    Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item.
    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can be critical as well.
    MSDB12.png / MMSDB12.png Milestones/
    Master milestones
    MSDB12.png / MMSDB12.png Without delay
    MSredDB12.png / MMSredDB12.png With delay
    MSdoneDB12.png / MMSdoneDB12.png With actual end
    Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGDB12.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    KalkExtDB12.PNG Calculated dates of the tasks from status report KalkExtDB12.PNG Uncritical
    KalkExtredDB12.png Critical
    Calculated dates of the tasks from status report Calc. start and Calc. end of the tasks from the selected status report.
    MSextDB12.png / MMSExtDB12.PNG Milestones/master milestones of the tasks from status report MSextDB12.png / MMSExtDB12.PNG Without delay
    MSextRedDB12.png / MMSextRedDB12.png With delay
    Without delay means: Total float 0
    With delay means: Total float < 0
    SammelVGSBDB12.png Calculated dates of the summary tasks from status report   Calc. start and Calc. end of the summary tasks from the selected status report.

    Up to DB 39.5.12

    Symbol Meaning Color Comment
    Wunsch.png Task requested dates   Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
    VGKalk.png Calculated dates of the tasks Unkritisch.png Uncritical
    kritisch.png Critical
    Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item.
    Uncritical means: Total float > 0
    Critical means: Total float 0
    Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
    Sammel.PNG Calculated dates of the summary tasks   A summary task is a task in the structured schedule that consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
    KalkSB.PNG Calculated dates of the tasks from status report   Calc. start and Calc. end of the tasks, the milestones, and the master milestones from the selected status report.
    SammelVGSB.PNG Calculated dates of summary tasks from status report   Calc. start and Calc. end of the summary tasks from the selected status report

    Topic attachments
    I Attachment History Size Date Comment
    Pngpng KalkSB.PNG r2 r1 0.3 K 2015-06-15 - 11:40  
    Pngpng MMS_krit.PNG r1 0.6 K 2015-06-12 - 16:41  
    Pngpng MS.png r1 0.6 K 2015-06-12 - 16:40  
    Pngpng MS_erl.PNG r1 0.6 K 2015-06-12 - 16:41  
    Pngpng Milestone.PNG r1 0.4 K 2015-06-12 - 16:40  
    Pngpng Sammel.PNG r1 0.3 K 2015-06-12 - 16:39  
    Pngpng SammelVGSB.PNG r1 0.3 K 2015-06-15 - 11:13  
    Pngpng Unkritisch.png r1 0.4 K 2015-06-12 - 16:42  
    Pngpng VGKalk.png r1 0.5 K 2015-06-12 - 16:40  
    Pngpng Wunsch.png r1 0.3 K 2015-06-12 - 16:40  
    Pngpng kritisch.png r1 0.3 K 2015-06-12 - 16:42  

             PLANTA project









     
    • Suche in Topic-Namen

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