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

Critical Projects MOD009AIR

From DB 39.5.13

Access path

From DB 39.5.9

Access path

Up to DB 39.5.9

Access path

Information

From DB 39.5.0

  • This module provides the multi-project manager (project manager, department manager) with an overview of the main projects that have date delay, milestone or master milestone delay, or budget overrun.
  • If there is need for clarification, you can send a message to the project manager directly from the Critical Projects module.

Up to DB 39.5.0

  • This module provides the multi-project manager (project manager, department manager) with an overview of the main projects that have date delay, milestone or master milestone delay, or budget overrun.
  • If there is need for clarification, you can send a message to the project manager directly from the Critical Projects module.
  • Details

    • The projects to be displayed in this module can be filtered using object filters.
      • If there already is an object filter, it can be selected from the listbox on the Filter field. After you have clicked on the Use changes button, only projects which correspond to the filter will be displayed.
      • You can edit existing object filters or create new ones in the Object Filter module which is opened via the Edit filter button.
      • If a grouping criterion is selected in one of the modules which use object filters, it automatically takes effect in all other modules with object filters.
    • By clicking on the ID of the required project, you can switch to the corresponding Project panel in which you can edit or view the program data depending on your user rights.

    Module Variants

    New from DB 39.5.9

    Base Shows all projects that are critical by defined criteria.
    My projects NEW Only shows the projects that are critical by defined criteria and in which the logged-on user is project manager.

    Bar legends

    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 module (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 shaded in white. The background color depends on the Project Code. Actual start and, if available Actual end, otherwise Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
    Verzug.png 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.
    MMSDB14.png Master milestones MMSDB14.png Without date delay
    MMSredDB14.png With date delay
    Tasks are defined as master milestones in the Schedule module.

    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 module (Project Core Data, Idea Core Data, Proposal 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.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
    Verzug.png 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.
    MMSDB12.png Master milestones MMSDB12.png Without date delay
    MMSredDB12.png With date delay
    Tasks are defined as master milestones in the Schedule module.

    Up to 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 module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
    Kalk.png Calculated dates The color of the bar is determined 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 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.
    Ist.png Actual dates   Actual start and, if available, Actual end, in any other case the Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
    Puffer.png Float   Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
    Verzug.png 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.
    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.

    Date Delay

    Information

    • In the Date delay area, all main projects are displayed, which have a date delay (Calc. end is later than Requested end).
      • Projects are displayed in categories of up to 5 days delay and over 5 days delay.
      • The Deviation field contains a traffic light.

    From DB 39.5.0

    Master Milestone Delay

    Information
    • In the Master milestone delay area, all main projects the milestones or master milestones of which have a date delay (Calc. end is later than Requested end) (there must be at least one master milestone with date delay).
      • Projects are displayed in categories of up to 5 days delay and over 5 days delay.
      • By opening the requested project, all affected milestones and master milestones are displayed.

    Up to DB 39.5.0

    Milestone and Master Milestone Delay

    Information
    • In the Milestone and master milestone delay area, all main projects the milestones or master milestones of which have a date delay (Calc. end later than Requested end).
      • Projects are displayed separated by up to 5 days delay and over 5 days delay.
      • By opening the requested project, all milestones and master milestones are displayed.

    Budget Overrun: costs

    Information

    Budget Overrun: effort

    Information

    Contact Project Manager

    Information

    • In all of the areas mentioned above, the project manager of the affected projects can be contacted via e-mail in case of inquiries or need for clarification.

    Procedure

    From DB 39.5.13

    • Click on the Message to project manager button in the required area.
      • A dialog message window is opened with a query whether the messages are to be sent to all project managers or only to selected ones.
      • Select the required option.
      • For every marked project (or for all projects) of the affected area, the Send Info dialog module is opened automatically.
        • All opened dialog modules are aligned in a row, so that only the Send Info module of a project is visible at first sight. If you move the module aside, the next one becomes visible, etc. If you want info to be sent for all (marked) projects, you have to process the Send Info modules successively in their order of appearance. If you move some modules aside and activate one of the modules situated below, the moved modules disappear.
    • Activate the Send Info dialog module of the requested project.
      • The module already contains the most important project data with a reference to overrun or delay.
    • The message text can be edited/completed if required.
    • Click on the send button at the right hand top margin of the module.
      • The message is sent to the project manager via e-mail. Furthermore, the project manager can access all messages sent to him/her via the Info module.

    From DB 39.5.10

  • Click on the Message to project manager button in the required area.
    • NEW A dialog message window is opened with a query whether the messages are to be sent to all project managers or only to selected ones.
    • Select the required option.
    • For every marked project (or for all projects) of the affected area, the Send Info dialog module is opened automatically.
      • All opened dialog modules are aligned in a row, so that only the Send Info module of a project is visible at first sight. If you move the module aside, the next one becomes visible, etc. If you want info to be sent for all (marked) projects, you have to process the Send Info modules successively in their order of appearance. If you move some modules aside and activate one of the modules situated below, the moved modules disappear.
  • Activate the Send Info dialog module of the requested project.
    • The module already contains the most important project data with a reference to overrun or delay.
  • The message text can be edited/completed if required.
  • Click on the send button at the right hand top margin of the module.
    • Depending on the info reception type set for the respective project manager, he/she receives the notification via e-mail, as a pop-up message on his/her screen, or both. Furthermore, the project manager can access all messages sent to him/her via the Info module.
  • From DB 39.5.0

  • Click on the Inform project manager button in the required area.
    • For every project of the affected area, the Send Info module is opened automatically.
    • The number of opened Send Info modules corresponds to the number of projects of the respective area.
    • NEW All opened dialog modules are aligned in a row, so that only the Send Info module of a project is visible at first sight. If you move the module aside, the next one becomes visible, etc. If you want info to be sent for all projects, you have to process the Send Info modules successively in their order of appearance. If you move some modules aside and activate one of the modules situated below, the moved modules disappear.
  • Activate the Send Info dialog module of the requested project.
    • The module already contains the most important project data with a reference to overrun or delay.
  • The message text can be edited/completed if required.
  • Click on the send button at the right hand top margin of the module.
    • Depending on the info reception type set for the respective project manager, he/she receives the notification via e-mail, as a pop-up message on his/her screen, or both. Furthermore, the project manager can access all messages sent to him/her via the Info module.
  • Up to DB 39.5.0

  • In the requested area click on the Inform project manager button.
  • For every project of the affected area, the Send Info module is opened automatically.
    • The number of opened Send Info modules corresponds to the number of projects of the respective area. The modules are minimized automatically and the tabs of the called modules are displayed at the bottom of the program window.
  • Activate the Send Info module of the requested project.
    • The module already contains the most important project data with a reference to overrun or delay.
  • The message text can be edited/completed if required.
  • Click on the Send button.
    • Depending on the info reception type set for the respective project manager, he/she receives the notification via e-mail, as a pop-up message on his/her screen, or both. Furthermore, the project manager can access all messages sent to him/her via the Info module.
  • Note

    • This function is also available via the Inform project manager context menu command (right-click on the required project). In this case, the Send Info module is only opened for the project that was clicked on.
    Topic attachments
    I Attachment History Size Date Comment
    Pngpng MMS_krit.PNG r1 0.6 K 2012-10-26 - 10:50  

             PLANTA project









     
    • Suche in Topic-Namen

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