Below, you will find descriptions of the project parameters (project data fields) which are used in standard modules.

DI041317 Project

Functional ID of the planning object (project/program/proposal/idea). It is generated automatically (copied from the technical project ID). Unlike the technical project ID, the functional ID can be changed afterwards (in the Project Core Data module) if necessary.

See notes under Project ID

DI001001 Project ID

Technical ID of the planning object (project/program/proposal/idea). It is generated automatically. Unlike the functional ID, it cannot be changed manually in the project DI.

Notes on customizing with functional and technical IDs

  • In PLANTA standard
    • only the functional ID is displayed in most modules (the technical ID is hidden by default and the Data field option and Filter criterion parameters are deactivated)
    • @L variables are always set to the technical ID since
      • only these data items have an index that speeds up the search.
      • Modules with this preset are usually embedded in workflows in which the successor modules also work with it (not only as a filter, but also in the Python macros for accessing the database).
      • In modules that have a filter with @L on main or subproject, no filters at project level are available to the user (the Filter criterion parameter is deactivated for all project fields).
  • PLANTA recommends that you consider this logic for individual customizing.

DI000690 Project name

Name of the planning object (project/program/proposal/idea/)

The parameter can be edited in the following modules by users with modification rights:

DI000141 Locked

This parameter determines whether the planning object is locked for working time recording.

Values

  • : Reporting actual effort or actual hours is not possible
  • : Reporting actual effort or actual hours is possible

Details

  • When a planning object is created, the Locked flag is set automatically so that no reporting hours can be executed unintentionally for the planning object during the initial planning phase.
  • If work reporting is to be enabled for a planning object, the Locked checkbox must be deactivated.

Note on structures projects

  • The value (activated/deactivated) is neither inherited from main project to subproject nor the other way around. It can be Modified on every project level. Changes to subprojects, however, can only be made by users that possess multi-project manager or multi-portfolio manager rights.

The parameter can be edited in the following modules by users with modification rights:

DI009494 Posting type ID

Code (ID) of the posting type of the planning object. For description, see DI056881 Posting type name.

DI056881 Posting type

Name of the posting type of the planning object. The Posting type parameter specifies up to which date the employees can post actual effort to the project. In input mode, a listbox for selection of a posting type is displayed on the respective field.

In PLANTA, actual posting means the recording of actual hours in the course of Time Recording as well as the recording of actual costs (cost which have actually incurred) in the Post Costs module and in the Post Revenues module.

Values

  • 0 - Actual postings up to the end of the current week: Recording of actual postings, actual costs, and actual revenues up to the last day of the current week.
  • 1 - Actual postings also into the future (overhead costs,...) Reporting of actual hours, actual costs, and actual revenues is also possible for future dates.
  • 2 - ... - This value is not preset by default and can be specified by a user with customizing rights in the Listbox values (old) module.

Details

  • New projects are preset with Posting type = "0".

Note on structures projects

  • Each new subproject in a project structure automatically inherits the posting type (upon creation) from its immediate parent project. The value can only be modified in the main project. If you try to change values on a subproject, the following message is displayed: The posting type can only be changed in the main project.

The parameter can be edited in the following modules by users with modification rights:

DI001042 Status ID

Code (ID) of the posting type of the planning object. For description, see DI041499

DI041499 Status

Name of the planning object status. In input mode, a listbox for selection of a status is displayed on the respective field.

Values

  • Template (0)
  • Active (1)
  • Inactive (2)
  • Archive (9)

Details

  • New planning objects are preset with status = Active.
  • For planning objects with Status ≠ "Active" (e.g. project templates which are used for copying) the calculation of schedules is not possible (neither as single calculation nor in the course of a replanning) 
  • Difference between "Archive" and "Inactive"
    • The tasks of the archived projects are not counted in the license level (task limit). The tasks of inactive projects, however, are counted. Inactive projects are only temporarily switched off and can be set to active again at a later point.
    • Archived projects cannot be edited by regular users (regardless of their rights). All fields (except the Status field itself) are "output" and all editing functions are switched off. Only users with customizer rights still have modification rights for archived projects. Inactive projects remain editable for regular users, although they are only available in particular views.
  • Before the status of a loaded planning object can be changed from "Active" to "Archive" or "Inactive", a final scheduling has to be carried out for the planning object and subsequently it must be unloaded. This is indicated by an info message.
  • The status of programs can only be changed from "Active" to "Archive" or "Inactive" if all assigned projects have the "Archive" or "Inactive" status accordingly.
  • If an archived planning object is opened, no current milestones will be displayed in the graphic in the project dashboard (program dashboard), but only the milestones from the baseline and from the active status report. Reason: in the graphic, the calculated dates for the x axis are required. Since in the current planning, however, no calculated dates exist anymore due to the unloading in the archiving procedure, milestones of the current planning cannot be displayed in the graphic.
  • Archived planning objects are no longer scheduled, however, their effort and cost values will still be taken into account in the program.
  • If a project with external links from/to other projects is set to "Inactive" or "Archive", the external links will be converted to links with active external task parameter.

Note on structures projects

  • Each new subproject in a project structure automatically inherits the status (upon creation) from its immediate parent project. The value can only be modified in the main project. If you try to change values on a subproject, the following message is displayed: The project status can only be changed for main project.

The parameter can be edited in the following modules by users with modification rights:

Note

DI056873 Status

Name of the planning object status. For description, see DI041499

DI059323 WBS changes locked

Defines whether generating a WBS code or changing the existing WBS code is allowed for the current project

The parameter can be edited in the following modules by users with modification rights:

DI000260 Short name

Short description of the project/proposal/idea/program

DI000264 WBS code*

Work break down structure code

Details

DI023220 Type ID

Code (ID) of the type of the planning object. For description, see DI057969

DI057969 Type

Name of the type of the planning object. The parameter determines whether the planning object is a

  • Project (0)
  • Proposal (1)
  • Idea (2)
  • Request (10)
  • Program (30)

The type is automatically set in type-specific creation of the planning object. A retrospective conversion of one type into another via the Type parameter can only be carried out by PM administrators in the Edit Planning Objects module.

DI057968 Type

Name of the type of the planning object. For description, see DI057969

DI001037 Planned effort

Planned effort of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

Note

  • Planned effort is only summarized from resource assignment (DT466) to the task (DT463) and subsequently to the project (DT461) if the Effort summarization checkbox is activated in the Resource Data Sheet.

DI001038 Actual effort

Actual effort of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

Note

  • Actual effort is only summarized from resource assignment (DT466) to the task (DT463) and subsequently to the project (DT461) if the Effort summarization checkbox is activated in the Resource Data Sheet.

DI001039 Remaining effort

Remaining effort of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

Note

  • Remaining effort is only summarized from resource assignment (DT466) to the task (DT463) and subsequently to the project (DT461) if the Effort summarization checkbox is activated in the Resource Data Sheet.

DI000687 Total effort

Total effort of the planning object. The value is determined during scheduling as a sum of actual and remaining (manual input not possible).

Calculation

DI000661 Planned costs

Planned costs of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

  • Project: Planned costs = sum of Planned costs of all tasks of the project and of all of its subprojects (if there are any)

DI000662 Actual costs

Actual costs of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

  • Project : Actual costs = sum of Actual costs of all tasks of the project and of all of its subprojects (if there are any)
    • Task: Actual costs = sum of Actual costs of all resources assigned to the task (except revenue resources). For revenue resources, see Actual revenues.
      • Resource assignment: Actual costs = sum of all Actual cost values of all resources assigned to the task.
        • Load: Actual costs per day of the resource assigned to the task. On this level, the actual cost calculation takes place.

DI000673 Remaining costs

Remaining costs of the planning object. The value is determined (summarized) from the values of the child areas (levels) during scheduling. Manual input is not possible. See calculation/summarization

Calculation/summarization

  • Project : Rem. costs = sum of the Rem. costs of all tasks of the current project and of all of its subprojects (if there are any)

DI000674 Total costs

Total costs of the planning object. The value is determined in scheduling as a sum of actual and remaining values (manual input not possible).

Calculation

DI000634 Cost budget

Budget details. Cost budget is planned/allocated in the Budget module (DT281) and the value is fetched to DI000634 (DT461) via Python value range.

Details

  • The values are summarized upwards to the main project via the structure if there are entries in subprojects.

DI000638 Deviation costs: planned - budget

Absolute deviation of planned costs from the cost budget

Details

  • Deviation > 0 means: Budget overrun!

Calculation via value range

DI000641 % deviation costs: planned - budget

Percentage deviation of planned costs from the cost budget

Details

  • Deviation > 0 means: Budget overrun!

Calculation via value range

DI000658 Deviation costs: total - budget

Absolute deviation of total costs from the cost budget

Details

  • Depending on whether the Total costs - budget deviation value is positive or negative, the value is colored red, yellow, or green.
    • Budget undercut: green
  • Deviation > 0 means: Budget overrun!
    • Budget strongly overrun: red
    • Budget slightly overrun: yellow

Calculation via value range

DI000660 % deviation costs: total - budget

Percentage deviation of total costs from the cost budget from the current planning

Details

  • Deviation > 0 means: Budget overrun!

Calculation via value range

DI000676 Deviation costs: total - planned

Absolute deviation of total costs from planned costs

Calculation via value range

DI000686 % deviation costs: total - planned

Percentage deviation of total costs from planned costs

Calculation via value range

DI000687 Total effort

Total effort of the project (program, proposal, idea)

Calculation

DI000688 Deviation effort: total - planned

Absolute deviation of total effort from planned effort

Calculation

DI000689 % deviation effort: total - planned

Percentage deviation of total effort from planned effort

Calculation

DI000692 Group 1

Parameter for grouping the planning objects. In the user modules, the respective field is named Project type.

Details

  • In PLANTA standard, this field is preset with a listbox the content of which can be adjusted via the Miscellaneous Listbox Values master data module.

The parameter can be edited in the following modules by users with modification rights:

DI000693 Group 2

Further parameters for grouping planning objects. The description and listing of the modules for editing are the same as for Group 1

DI000694 Group 3

Further parameters for grouping planning objects. The description and listing of the modules for editing are the same as for Group 1

DI001003 Parent project ID

ID of the parent project in a project structure. When you structure a project and save it, the ID of the parent project is automatically entered for the subproject.

See also: Structure Project / Subprojects

DI001004 Structure task ID

When you structure a project, the ID of the structure task of the parent project is automatically entered for a subproject here. The structure task is a task which links a parent project to a subproject.

Details

  • After projects have been structured and calculated, a structure task is created automatically in each parent project.
  • In standard, structure tasks are hidden in all concerned modules by default and cannot be unhidden by the user. This is to be observed for individual customizing as well.
    • The Structure task parameter defines whether a task is a normal or a structure task.

DI001005 Created on

When a record is created, the creation date is automatically entered here.

DI001006 Changed on

When a record is modified, the modification date is automatically entered here.

DI001008 Created by

When a record is created, the ID (code) of the logged-on user is automatically entered in this field. The creating user is also the owner of a record.

DI001009 Changed by

When a record is modified, the ID (code) of the logged-on user is automatically entered in this field.

DI001014 Code ID

Code (ID) of the code of the planning object. For description, see DI056883.

DI056883 Code

Name of the code of the planning object. In input mode, a listbox for selection of a posting type will be displayed on the respective field.

In PLANTA, codes serve to organize planning objects. In PLANTA standard, the code of the planning objects (or the symbol stored for the respective code) is taken into account in the visualization of the planning object date bars (e.g. in the Projects module) or in utilization diagrams.

Values

  • A - A projects
  • B - B projects
  • C - C projects
  • D - Other projects
  • E - New projects

All newly created planning objects are set to code = E (new projects) by default

Technical details on utilization diagram

  • In PLANTA standard, the planning object utilization is visualized in utilization diagrams according to the code. However, the planning object codes are not directly taken into account but via respective model parameters.
  • Since utilization diagrams in PLANTA can only consider 5 codes, PLANTA recommends to use 5 planning codes accordingly (as is the case in standard). If you wish to use more than 5 planning object codes anyway (e.g. for further project evaluation purposes), they are bundled in one code in utilization diagrams and visualized with the same symbol.

Note on structures projects

  • Each new subproject in a project structure automatically inherits the code (upon creation) from its immediate parent project.

Caution

  • If you want to have the codes changed or extended, please consult your PLANTA contact person.

The parameter can be edited by users with modification rights in the following modules (assignment of the codes to planning objects):

DI001015 Priority

Priority of the planning object

Details

  • You can increase the importance of the planning object using a numeric code to define the priority.
  • Priority controls the sequence in which the resources assigned to the projects are loaded during replanning (calculation of the schedules of all projects).
  • For newly created projects, the priority is set to the lowest priority. This can be adjusted.

Permitted values

  • 0: highest priority;
  • 1: second highest priority, etc.

Technical details

  • The value range of the field checks for the @G296 global variable via which you can set the maximum priority value that can be entered.
    • If you, e.g., want to work with priority values from 0 to 10, you should enter 10 in the variable. Numbers up to 999 are permitted.
  • In PLANTA Standard, the maximum permitted value is preset by default.

Note on structures projects

  • Each new subproject in a project structure automatically inherits the priority (upon creation) from its immediate parent project.

The parameter can be edited in the following modules by users with modification rights:

DI001019 Requested start

Required start date of the planning object. It is the start date for all tasks which have no predecessor(s) and no requested dates of their own. The PR Req. start will be considered if no other conditions (e.g. consideration of the 'today' line) conflict with it. It is also valid if actual data has already been recorded on tasks.

The parameter can be edited in the following modules by users with modification rights:

DI001020 Requested end

Requested end date of the planning object

Details

  • Depending on the project requested dates for float model parameter, the calculation of float times in projects is based on this parameter.
    • If the calculated lead time of the project is shorter than the time between Req. start of the project and Req. end of the project, all tasks will receive additional float.

The parameter can be edited in the following modules by users with modification rights:

DI001023 Calc. start

Calculated start date of the project (proposal, idea, or program).. The value is determined during scheduling.

Calculation

  • Earliest calculated start date of all tasks of the project and all subprojects (if there are any)

DI001024 Calc. end

Calculated end date of the project (proposal, idea, or program).. The value is determined during scheduling.

Calculation

  • Latest calculated end date of all tasks of the project and all subprojects (if there is any)

DI001025 Actual start

Actual start date of the project (proposal, idea, or program).. The value is determined during scheduling.

Calculation

DI001026 Actual end

Actual end date of the project (proposal, idea, or program).. The value is determined during scheduling.

Calculation

  • Latest actual end of all tasks of the project and the subprojects (if available), if all tasks are completed.

Project duration


If Actual start of the project = 0 (project is being planned)If Actual start of the project > 0 (project has already started)
DI001034 Planned duration
If requested date is set: Requested end - Requested start
Otherwise: calc. end - Calc. start 		Unchanged after first Scheduling (analogous to Planned task duration).
Although changes can still be made in the Planned task duration after project start, they will not be written in the Planned project duration in the next calculation.
DI001035 Actual duration
0 Time recording date - Actual start (in analogy to the calculation of Actual task duration).
DI001036 Remaining duration
 calc. end - Calc. start Initial Remaining duration - change in the Actual duration
DI023415 Total duration
 Actual duration + Remaining duration Actual duration + Remaining duration

Notes

  • Project durations are calculated on the basis of work days (Work = ). This means that the number of days with Work = (weekends, public holidays, company holidays) will additionally be subtracted from the results of the above described subtractions. The calculation accesses the calendar which is entered in the @G150 global variable.
  • If the today line is inactive or fixed, it is possible that the Remaining task duration overlaps the Actual task duration (e.g.: Actual duration is up to yesterday, but there is still remaining effort in the last week). For this case, no plausible total project duration can be calculated.
  • If the today line is inactive, the settings in the Split parameter are not taken into account in the project duration calculation.


DI001481 Time recording date

Date on which the last time recording was carried out for the project. The date is determined during scheduling.

Calculation

DI001043 Network cycle

Parameter that signalizes that there is a cycle in the project.

Details

  • If the scheduling run is aborted due to a cycle in the network, this checkbox will be activated. After the cycle has been removed, this checkbox is deactivated in when the next scheduling is performed.

See also: Cycle Search module, Task with cycle parameter

DI001044 Loaded

The parameter indicates whether a scheduling (calculation of the schedule) of the planning object has been carried out.

Values

  • - The schedule has been calculated.
  • - Unloading has been carried out or the schedule has not yet been calculated.

DI001045 Last scheduling date

Date of the last scheduling of the planning object

DI001048 Number of tasks

Number of tasks of the project

Notes

  • The value is determined during scheduling.
  • For archived projects, this field is not filled (i.e. tasks of archived projects are not counted).
  • Structure tasks are not included in the count.

DI002345 Number of tasks

Number of tasks of the project

Notes

  • Unlike the parameter of the same name, DI001048
    • this parameter is also filled for archived projects (i.e. tasks of archived projects are counted).
    • Structure tasks are not included in the count.

Number of Link tasks / links of the project. The counting only includes the links relevant for scheduling, i.e. internal links and external links (incoming and outgoing). External tasks are not included in the counting.

Details

  • The value is automatically determined during scheduling of the planning object.

DI001050 Last scheduling date

Date on which the last scheduling was carried out.

DI001052 Main project ID

Code (ID) of the main project in a project structure

Remarks

  • If no project structure is available, the main project ID (DT001052) equates to the project ID (DI001001).
  • Projects with Level = 0 are always main projects at the same time.

DI001053 Level

Project level. Both initial setting and update of the value take place immediately after the structure has been changed and saved. No scheduling is required.

Values

  • 0: main project (top level)
  • 1: subproject of the first level, etc.

DI001061 Customer

Customer of the project

Note on structures projects

  • Each new subproject in a project structure automatically inherits the customer (upon creation) from its immediate parent project.

The parameter can be edited in the following modules by users with modification rights:


DI001062 Manager ID

Code (ID) of the project (proposal, idea, program, or request) manager For details, see Manager

DI006514 Manager

Name of the project (proposal, idea, program, or request) manager

DI034520 Manager

Name of the project (idea, proposal, program, or request) manager In input mode, a listbox for selection of a manager will be displayed on the respective field.

Notes

  • When creating new planning objects, the current creating user is entered as a manager in the respective core data module (Proposal Core Data, Proposal Core Data, Program Core Data) but can be replaced by another person immediately after creation. For ideas, the Manager field is not contained in the core data, so that the idea manager can only be changed in the Edit Planning Objects module in the Ideas module variant.

The parameter can be edited in the following modules by users with modification rights:

DI007817 Manager name: parent project

Name of the project manager of the parent project

DI007822 E-mail manager: parent project

E-mail address of the project manager of the parent project

DI007823 Main project manager ID

Code (ID) of the main project manager

DI006864 Main project manager

Name of the manager of the main project

DI007821 E-mail main project manager

E-mail address of the main project manager

DI007824 Manager: parent project

Code (ID) of the parent project manager

DI006545 E-mail

E-mail of the project manager

The parameter can be edited in the following modules by users with modification rights:

DI001063 Client

Contact person at the customer’s site

Note on structures projects

  • Each new subproject in a project structure automatically inherits the customer manager (upon creation) from its immediate parent project.

The parameter can be edited in the following modules by users with modification rights:

DI001296 Dev.: project end dates: calc. end - requested end

Absolute deviation of the project end dates calculated in scheduling (Calc. end from Requested end) in days.

DI008143 Dev.: MMS end dates: calc. end - requested end

Absolute deviation of the master milestone end dates calculated in scheduling (Calc. end from Requested end) in days. The highest deviation value from all master milestones is visualized.

DI002051 Bar: calculated dates (traffic light)

Bar (with a traffic light function) for the visualization of the interval between the calculated dates (Calc. start and Calc. end) of the project (program, proposal, idea).

DI002052 Bar: requested dates

Bar for the visualization of the interval between the requested dates (Requested start and Requested end) of the project (program, proposal, idea)

DI002055 Bar: actual dates

Bar for the visualization of the interval between the actual dates (Actual start and Actual end) of the project (proposal, idea, program)

DI002088 Bar: Actual start - Time recording date

Bar for the visualization of the time interval between Actual start date and Last time recording date of the project (program, proposal, idea)

DI002367 Bar: calculated dates by code

Bar for the visualization of the interval between the calculated dates (Calc. start and Calc. end) of the project (program, proposal, idea). The symbol of the bar is determined by the code (of the program, proposal, idea).

DI023412 Bar: float

Bar for the visualization of the date float (positive interval between Requested end and Calc. end) of the project (program, proposal, idea).

DI023373 Bar: delay

Bar for the visualization of the delay (positive interval between Requested end and Calc. end) of the project (program, proposal, idea).

DI002555 Main project name

Name of the main project

DI002771 Created by: Name

When a record is created, the ID (code) of the logged-on user is automatically entered in this field. The creating user is also the owner of a record.

DI003382 Main project customer

Customer of the main project

DI005443 Plan 1 frozen on

Date on which plan 1 was frozen

Note

  • This field can be released by PLANTA for manual editing. If you wish this, please contact your PLANTA consultant.

DI005444 Plan 2 frozen on

Date on which plan 2 was frozen

Note

  • This field can be released by PLANTA for manual editing. If you wish this, please contact your PLANTA consultant.

DI005445 Plan 3 frozen on

Date on which plan 3 was frozen

Note

  • This field can be released by PLANTA for manual editing. If you wish this, please contact your PLANTA consultant.

DI006445 Planning type ID

Code (ID) of the Planning type parameter. For description, see Planning type name.

DI056876 Planning type

Name of the planning type of a project. The planning type determines how the projects are calculated. In input mode, a listbox for selection of a planning type will be displayed on the respective field.

Values

  • 0 = Adherence to schedule
    • Availability of capacity or tasks which have already been loaded are not taken into account when loading tasks. No capacity adjustment takes place.
  • 1 = Adherence to total float
    • In case of capacity shortage, a task can be moved within its total buffer time. If sufficient free capacity is available, the task is loaded. If not, loading will be carried out at its latest dates (Latest start / Latest end). The project end date (Requested end or Latest end) is not overrun due to capacity shortage.
  • 2 = Adherence to capacity
    • A capacity shortage will cause tasks to be moved to a point at which sufficient free capacity is available. The project end date (Requested end) is not taken into account, provided that all other requirements are met:

Note on structures projects

  • Each new subproject in a project structure automatically inherits the planning type (upon creation) from its immediate parent project.

The parameter can be edited in the following modules by users with modification rights:

DI006926 Effort budget

Budget details for effort

Details

  • It is a virtual field. The values are fetched from the Effort budget of DT281 via Python value range.
  • The Effort budget in DT281 is always a calculated value and represents the number of all effort budgets of the current project and of all of its subprojects. Hence, the value of DI006926 is always the value of the entire project structure (if available).
  • The effort budget in the Budget module is planned/allocated in the Effort budget (without subprojects) field at project level or in the Effort budget (without subprojects) field at yearly tranche level.

DI006927 Deviation effort: total - budget

Absolute deviation of total effort from the effort budget in the current planning

Details

  • Deviation > 0 means: Budget overrun!

Calculation via value range

DI006928 % deviation effort: total - budget

Percentage deviation of total effort from the effort budget in the current planning

Details

  • Deviation > 0 means: Budget overrun!

Calculation via value range

DI007786 Cost center ID

Code (ID) of the cost center of the planning object. For description, see DI041497

DI007802 Cost center name

Name of the cost center of the planning object. For description, see DI041497

DI041497 Cost center

Name of the cost center of a planning object. In PLANTA project, the Access to planning objects is controlled via the cost centers and their structure codes. In input mode, a listbox for selection of a cost center is displayed on the respective field.

Note on structures projects

  • Each new subproject in a project structure automatically inherits the cost center (upon creation) from its immediate parent project.

The parameter can be edited in the following modules by users with modification rights:

Details

  • You can create and edit cost centers in the Cost Centers module.

DI008837 Cost center structure code

Structure code of the cost center

Details

DI007806 Cost budget overrun

Grouping field with display of the budget overrun category (up to 5%, over 5%). In this field, individual projects (proposals, ideas, programs) are listed, the budget overrun values of which correspond to the value specified in the grouping field.

DI063724 Effort budget overrun

Grouping field with display of the budget overrun category (up to 5%, over 5%). In this field, individual projects (proposals, ideas, programs) are listed, the budget overrun values of which correspond to the value specified in the grouping field.

DI007807 End delay

Grouping field for the display of the delay category (up to 5d, over 5d) In this field, individual projects (proposals, ideas, programs) are listed, the delay values of which correspond to the value specified in the grouping field.

DI007808 Number of projects

The number of projects is displayed in this field

DI007983 Milestone delay

Grouping field for the display of the delay category for master milestones (up to 5d, over 5d). In this field, individual projects (proposals, ideas, programs) are listed, the delay values of which correspond to the value specified in the grouping field.

DI002833 Split

Via the Split parameter, entire projects can be interrupted (split).

Values

  • The project is to be split. In scheduling, all tasks of this project are treated like split tasks.
  • The project is not to be splitted. However, you can set the splitting flag for singular tasks.

Notes

  • The activated split overwrites the non-activated task splitting. The opposite is not true, i.e. the deactivated project split does not overwrite the activated task splitting.
  • Using the combination of project requested start (if this date is later than the project actual start) at main project level and project split at subproject level you can shift (split) the entire project structure very easily and quickly.
  • The project split is to be preset individually for subprojects.

DI010246 Overhead costs

DI023213 Current risk value

Calculated risk value of the planning object in percent. When answering risk queries, the value is continuously calculated and displayed or refreshed.

Details

  • In the Risk Checklist master data module, an own weighting value is stored for Yes or No answers for each risk query.
  • In the Project Core Data / Program Core Data / Proposal Core Data user modules, risk queries are answered with Yes or No.
  • The risk value is then calculated on the basis of the weighting values of the Yes/No answers of the respective queries according to the following formula:
    • Sum of all risk values (Yes or No weighting) / (Yes + No weighting value)] x 100

Caution: the weighting value is the value which is stored in the master data module for Yes and No answers. The weighting is the weighting value * the respective answer, i.e. Yes or No (1 or 0).

Example

  • In the master data module, there are two criteria with the following weighting values:
    • 1) Yes=15 No=0
    • 2) Yes=10 No=0
    • In the user module, the first question is answered with "Yes" and the second with "No".
      • The answer to question 1 results in a weighting of 15 = 15*1 + 0*0
      • The answer to question 2 results in a weighting of 0 = 10*1 +0*1
      • The entire risk value is calculated as follows: (15 / (15 + 10)) * 100 = 60 %
    • In the same use case, both questions are answered with “No”.
      • The answer to question 1 results in a weighting of 0 = 15*0 + 0*1
      • The answer to question 2 results in a weighting of 0 = 10*0 + 0*1
      • The risk value is calculated as follows: (0 / (15 + 10)) * 100 = 0 % (no risk)
    • If you, e.g., increase the Yes value for question 1 in the master data module to 20, and if the questions are answered as in the first use case (Yes, No), the risk value is increased respectively and then amounts to 66%.

DI022774 Fixed risk value

Calculated risk value of the planning object in percent. In contrast to Current risk value, this value is only displayed or refreshed after the Complete evaluation button in the project core data module of the respective planning object has been clicked on (as a result, the value from Current risk value is copied).

DI022780 Current objective contribution

Calculated objective contribution of the planning object in percent. While specifying or changing criterion contributions, this value is continuously calculated and displayed or refreshed.

Details

  • In the Objective Evaluation Criteria master data module, one weighting value is allocated for each criterion.
  • In the Project Core Data / Program Core Data / Proposal Core Data user modules, the criterion contribution is allocated as a percentage value.
  • The objective contribution is then calculated from the criterion contribution values and their weighting values according to the following formula:
    • Sum of (Weighting * Criterion contribution) all criteria / Sum of all weightings * 100

Example

  • There are the following criteria with the following weighting and criterion contributions:
    • K1: weighting 3, criterion contribution 25%
    • K2: weighting 5, criterion contribution 0%
    • K3: weighting 0, criterion contribution 50%
    • K4: weighting 5, criterion contribution 100%
  • The risk value is calculated as follows: (3*0,25+5*0+0*50+5*1 / 3+5+0+5) * 100= 46,15%

DI022781 Fixed objective contribution

Calculated objective contribution of the planning object in percent. In contrast to Current objective contribution, this value is only displayed or refreshed after the Complete evaluation button in the core data module of the respective planning object has been clicked on (as a result, the value from Current objective contribution is copied).

DI023121 Objectives

Here you can define the objectives pursued with the planning object.

The parameter can be edited in the following modules by users with modification rights:

DI023122 Scope and limit

In this field you can describe what is to be done in the planning object and what not.

The parameter can be edited in the following modules by users with modification rights:

DI023123 Conseq. of non-realization

In this field, it is defined what consequences result from non-realization.

The parameter can be edited in the following modules by users with modification rights:

DI023124 Areas involved

In this text field, specialist departments and persons which are involved in the planning object are specified.

The parameter can be edited in the following modules by users with modification rights:

DI023125 Mandatory

Parameter which serves to mark a planning object as a mandatory planning object.

Notes

  • The parameter is meant to be a selection aid for the portfolio manager in the creation of the portfolio. Mandatory projects must be realized, even if other projects appear to be more worthwhile, e.g. projects for complying with statutory requirements.
  • The parameter has no technical impact on the system.

The parameter can be edited in the following modules by users with modification rights:

DI023126 Mandatory: reason

Text entry for justifying why the planning object is marked as a mandatory planning object by activation of the Mandatory checkbox.

The parameter can be edited in the following modules by users with modification rights:

DI023128 ROI

Return on Investment (ROI)

Details

  • The return on investment is a measure of what is expected to be "returned" from the investment. It thus expresses the profit objective.
  • The profit is related to the operating resources invested, because management must achieve the profit with this investment – with the available means.
  • As a key figure, the ROI can be broken down into two basic components:
    • ROI = Sales return * Capital turnover
      • Sales return = Profit/Net revenue
      • Capital turnover = Net revenue/Total capital

The parameter can be edited in the following modules by users with modification rights:

DI023129 Description

Description of the project (idea, proposal, program, request)

The parameter can be edited in the following modules by users with modification rights:

DI023130 Internal interest

Internal interest. The value is used to calculate the NPV value.

The parameter can be edited in the following modules by users with modification rights:

DI023188 Type name

Name of the planning object type. Via the Type parameter, planning objects are distinguished as projects, ideas, proposals, programs, etc. The planning object type is determined by the Type parameter.

Notes for customizers

  • DI023188 is used as grouping field.

DI023252 Type name

Name of the planning object type. Via the Type parameter, planning objects are distinguished as projects, ideas, proposals, programs, etc. The planning object type is determined by the Type parameter.

Notes for customizers

  • DI023252 is used as grouping field.

DI063005 OLE dev.: project/MMS end dates: calc. end - requested end

Symbol (traffic light) for the visualization of the deviation of the project/program end dates (Calc. end from Requested end) and master milestone end dates (Calc. end from Requested end) in the current planning

Note

  • The traffic light refers to the highest of all deviation values.

DI023387 OLE deviation: project end dates: calc. end - requested end

Symbol (traffic light) for the visualization of the project end dates (Calc. end from Requested end) in the current planning

DI023388 OLE deviation MMS end dates: calc. end - requested. end

Symbol (traffic light) for the visualization of the master milestone end dates (Calc. end from Requested end) in the current planning

Note

  • The traffic light refers to the highest of all deviation values.

DI023389 OLE deviation costs: total - budget

Symbol (traffic light) for the visualization of the cost deviation (Total costs from Cost budget) in the current planning.

DI023390 OLE deviation effort: total - budget

Symbol (traffic light) for the visualization of the effort deviation (Total effort from Effort budget) in the current planning.

DI023413 Deviation project end dates: calc. end - requested end

Absolute deviation of the project end dates (Calc. end from Requested end) in the current planning

DI023416 Deviation MMS end dates: calc. end - requested. end

Absolute deviation of the master milestone end dates (Calc. end from Requested end) in the current planning

Note

  • The highest deviation value from all master milestones is visualized.

DI023596 Dominance symbol simulation 461

DI023655 Project name

Name of the project

DI028199 Display to manager

Currently without function

DI028338 Planned revenues

Planned revenues of the project. The value is determined during scheduling.

Calculation

  • Planned revenues of the project = sum of the planned revenue values of all revenue resources planned in the project Revenue values of the individual resources are stored in DT472, however, they are not stored in columns specifically designed for revenues but in the cost columns. In the case of planned revenues, they are stored in the Remaining costs column. Whether the value stored in this column is a cost or revenue value is determined by the type of resource to which the value applies.

Layout objects

  • In PLANTA standard, planned revenues of a project are not contained in any module but can be included in the Schedule module via customizing if necessary.
  • The other annual revenue values (remaining, actual, total) of a project can be consulted as a sum in the Budget module.

Note

  • Planned revenues of a project are only displayed if at least one revenue resource is planned in the project (Schedule).

DI028339 Actual revenues

Actual revenues of the project. The value is determined during scheduling.

Calculation

  • Actual revenues of the project = sum of the actual revenue values of all revenue resources planned in the project

Display in modules

  • The parameter (DT461) described here is not contained in any module by default but it can be included, e.g., in the Schedule module via customizing.
  • However, actual revenue values of a project are additionally saved in further parameters (DT861) and can, e.g., be displayed in the Budget module in the Actual revenues (w/o subprojects) and Actual revenues fields in the sum line of the Benefits and revenues area.

DI028340 Remaining revenues

Remaining revenues of the project. The value is determined during scheduling.

Calculation

  • Remaining revenues of the project = sum of the remaining revenue values of all revenue resources planned in the project. Remaining revenue values of the individual revenue resources are stored in DT472, however, they are not stored in columns specifically designed for revenues but in the cost columns. In the case of actual revenues, they are stored in the Remaining costs column. Whether the value stored in this column is a cost or revenue value is determined by the type of resource to which the value applies.

Layout objects

  • The parameter (DT461) described here is not contained in any module by default but it can be adopted in the Schedule module via customizing.
  • However, remaining revenue values of a project are additionally stored in other parameters (DT861) and can, e.g. be displayed in the Budget module in the Remaining revenues (w/o.SP) and Remaining revenues fields in the sum line of the Benefits and revenues area .

DI028341 Total revenues

Total revenues of the project. The value is automatically calculated as a sum of actual and remaining values (manual input not possible).

Calculation

Notes

DI028352 Internal gross profit

DI006516 Estimate date entire project

Date of the estimate of the entire project by the project manager. The date is updated automatically after the estimate of at least one factor in the Status module has been made/changed.

DI006515 Entire project estimate

Numeric estimate value for the entire project, according to which the display of the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI028844 Cost estimate

Numeric estimate value for costs, according to which the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI028845 Effort estimate

Numeric estimate value for effort, according to which the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI028846 Project / master milestone dates estimate

Numeric estimate value for project and master milestone end dates, according to which the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI028847 Quality estimate

Numeric estimate value for project quality, according to which the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI061342 Risks/opportunities estimate

Numeric estimate value for risks and opportunities, according to which the respective estimate symbol is displayed. The value is usually hidden in the user modules.

The parameter can be edited in the following modules by users with modification rights:

Note

  • The change of the estimate and hence of this value is effected by clicking on the arrow symbol ».

DI023380 OLE entire project estimate

Symbol which visualizes the estimate of the entire project/program by the project/program manager

Notes

  • You can change the estimate and hence the symbol shape by clicking on the arrow symbol ».
  • In PLANTA standard, changing is only possible in the Status (projects) and Status (programs) modules. In other modules, it is an output value.

DI029112 OLE cost estimate

Symbol which visualizes the estimate of the project/program costs by the project/program manager

See notes under OLE Entire project estimate

DI029113 OLE effort estimate

Symbol which visualizes the estimate of the project/program effort by the project/program manager

See notes under OLE Entire project estimate


DI029115 OLE project/master milestone end dates estimate

Symbol which visualizes the estimate of the project/program and master milestone end dates by the project/program manager

See notes under OLE Entire project estimate

DI029116 OLE estimate: quality

Symbol which visualizes the estimate of the project/program quality by the project/program manager

See notes under OLE Entire project estimate

DI061345 OLE estimate: risks/opportunities

Symbol which visualizes the estimate of the risks and opportunities of the project/program by the project/program manager

For notes, see OLE Entire project estimate

DI029133 461: OLAP 1 - 029129

DI029160 461: OLAP 1 - txt

It is used for the visualization of the dynamic grouping values in modules with grouping options, e.g. Projects or Projects: 2 Groupings.

DI029161 461: OLAP 2 - txt

It is used to display the values of the 2nd dynamic grouping in modules, in which 2 groupings are used, e.g. Projects: 2 Groupings

DI029190 Comment: entire project

Comment on the entire project/program

The parameter can be edited in the following modules by users with modification rights:

DI029192 Comment: costs

Comment on the costs of the project/program

The parameter can be edited in the following modules by users with modification rights:

DI029193 Comment: effort

Comment on the effort of the project/program

The parameter can be edited in the following modules by users with modification rights:


DI029194 Comment: project/MMS end dates

Comment on the end dates of the project/program and the master milestones

The parameter can be edited in the following modules by users with modification rights:

DI029195 Comment: quality

Comment on the quality of the project/program

The parameter can be edited in the following modules by users with modification rights:

DI061344 Comment: risks/opportunities

Comment on the risks/opportunities of the project/program

The parameter can be edited in the following modules by users with modification rights:

DI029448 WBS code*


DI029872 % deviation costs: total - budget (baseline)

Percentage deviation of total costs from the cost budget from the baseline report The value is copied from the % deviation costs: total - budget parameter of the baseline report.

DI029874 OLE trend cost deviation (current vs. baseline)

Symbol for the visualization of the trend of the cost deviation values from the current planning (% deviation costs: total - budget) compared to the values from the baseline report (% deviation costs: total - budget (baseline))

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029875 % deviation effort: total - budget (baseline)

Percentage deviation of total effort from the cost budget from the baseline report. The value is copied from the % deviation effort: total - budget parameter of the baseline report.

DI029879 OLE trend effort deviation (current vs. baseline)

Symbol for the visualization of the trend of the cost deviation values from the current planning (% deviation effort: total - budget) compared to the values from the baseline report (% deviation effort: total - budget (baseline))

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029876 Dev.: project end dates: calc. end - req. end (baseline)

Deviation of the calculated end date from the requested end date of the project (program) from the active baseline. The value is copied from the Dev.: project end dates: calc. end - req. end of the baseline report.

DI029877 Dev.: MMS end dates: calc. end - req. end (baseline)

Deviation of the calculated end date from the requested end date of the master milestones from the requested end date of the master milestones from the active baseline. The value is copied from the Dev.: MMS end dates: calc. end - req. end of the baseline report.

The highest deviation value from all master milestones is visualized.


DI029878 OLE trend dev.: project end dates (SR vs. active SR) MMS end dates (current vs. baseline)

Symbol for the visualization of the deviation trend of the calculated end date from the requested end dates of the master milestones of the current planning (Dev.: MMS end dates: calc. end - req. end) compared to the deviation value from the baseline report Dev.: MMS end dates: calc. end - req. end (baseline)

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029880 OLE trend dev.: project end dates (current vs. baseline)

Symbol for the visualization of the deviation trend of the calculated end date from the requested end date of the project (program) of the current planning (Dev.: project end dates: calc. end - requested end) compared to the deviation value from the baseline report Dev.: project end dates: calc. end - req. end (baseline)

DI029885 % deviation effort: total - budget (active SR)

Percentage deviation of total effort from the effort budget from the active status report. The value is copied from the % deviation effort: total - budget parameter of the active status report.

DI063793 Dev.: project end dates: calc. end - requested end (active SR)

Deviation of the calculated end date from the requested end date of the project (program) from the active status report with text specification (delay/float). The value is copied from the Dev.: project end dates: calc. end - requested end parameter of the active status report.

DI029886 Dev.: project end dates: calc. end - requested end (active SR)

Deviation of the calculated end date from the requested end date of the project (program) from the active status report. The value is copied from the Dev.: project end dates: calc. end - requested end parameter of the active status report.

DI063794 Dev.: MMS end dates: calc. end - requested end (active SR)

Deviation of the calculated end dates of the master milestones from the requested end date of the master milestones from the active status report with text specification (delay/float). The value is copied from the Dev.: MMS end dates: calc. end - Requested end parameter of the active status report.

The highest deviation value from all master milestones is visualized.


DI029887 Dev.: MMS end dates: calc. end - requested end (active SR)

Deviation of the calculated end date of the master milestones from the requested end date of the master milestones from the active status report. The value is copied from the Dev.: MMS end dates: calc. end - Requested end parameter of the active status report.

The highest deviation value from all master milestones is visualized.


DI029888 % deviation costs: total - budget (active SR)

Percentage deviation of the total costs from the cost budget from the active status report. The value is copied from the % deviation costs: total - budget parameter of the active status report.

DI029890 OLE trend effort deviation (current vs. active SR)

Symbol for the visualization of the trend of the deviation of the total effort from the effort budget in the current planning (% deviation effort: total - budget) compared to the deviation value from the active (last released) status report (% deviation effort: total - budget (active SR))

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029891 OLE trend dev.: project end dates (current vs. active SR)

Symbol for the visualization of the deviation trend of the calculated end date from the requested end date of the project (program) of the current planning (Dev.: project end dates: calc. end - requested end) compared to the deviation value from the active (last released) status report (Dev.: project end dates: calc. end - requested end (active SR)).

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029892 OLE trend cost deviation (current vs. active SR)

Symbol for the visualization of the trend of the deviation of the total costs from the cost budget in the current planning (% deviation costs: total - budget) compared to the deviation value from the active (last released) status report (% deviation costs: total - budget (active SR))

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values


DI029893 OLE trend dev.: MMS end dates (current vs. active SR)

Symbol for the visualization of the deviation trend of the calculated end date from the requested end dates of the master milestones of the current planning (Dev.: MMS end dates: calc. end - requested end) compared to the deviation value from the active (last released) status report (Dev.: MMS end dates: calc. end - requested end (active SR)).

Meaning

  • Arrow up: negative trend
  • Arrow down: positive trend
  • Arrow right: no change to the values

DI029895 Status reports: collective creation

This parameter defines whether the status reports can be created from a check module for a defined period at the click of a button. The function primarily serves to create status reports for several projects at once (collective creation).

Values

  • - Reports can be created from a control module for the defined period for several projects at once.
  • - The status report creation can only be initiated individually for each project from the Status module.

Note

  • The parameter can only be activated or deactivated at main project level. If you try to activate the parameter on a subproject, a message indicating that the function is only available for main projects will be displayed.
    • The setting on the main project automatically applies to subprojects as well.

The parameter can be edited in the following modules by users with modification rights:

See also: Collective Creation of Status Reports

DI040784 Last automatic status report

The last automatically created status report

DI063009 Program ID

Technical ID of the program. It is generated automatically and cannot be changed afterwards, unlike the functional ID. It is usually invisible in the modules.

DI063010 Program name

Name of the respective program

DI063026 Program

Functional ID of the program. It is generated automatically (copied from the technical Project ID). Unlike the technical program ID, the functional ID can be changed afterwards (in the Program Core Data module) if necessary.

DI041089 Process status

Status of the process

DI041184 Current status

Current status of the planning object

DI041195 Phase name

Name of the phase

DI041200 Process model

Code (ID) of the process model. For the description, see Process Model Name.

DI041394 UF info

Use frequency of news

DI041395 UF todo items+risk measures

Frequency of use of todo items ad risk measures

DI041396 OLE info

This field signalizes with an OLE symbol whether current news for the respective planning object are available. If no current news are available, the symbol is grayed out. Current messages are messages that are not marked as read.

DI041409 Production costs: Objective

In this field the desired production cost amount is defined.

The parameter can be edited in the following module by users with modification rights:

DI041410 Production costs: current

In this field the current production cost amount is defined.

The parameter can be edited in the following module by users with modification rights:

DI041411 Production costs: Date

In this field, the date to which the current production costs refer is entered.

The parameter can be edited in the following module by users with modification rights:

DI041412 Production costs: Comments

You can write comments on production costs here

The parameter can be edited in the following module by users with modification rights:

DI041614 Process model name

Name of the process model by which the selected project (idea, proposal, request) is planned and controlled. In input mode, a listbox for selection of a process model is displayed on the respective field.

Details

DI041621 Changed by: Name

When a record is modified, the ID (code) of the logged-on user is automatically entered in this field.

DI041680 Area

Code (ID) of the Area parameter. For description, see Area name.

DI041681 Break even

A break-even point (or break even) is an economic term which describes the point of balance at which costs and revenues are equal so that there is no profit or loss (Source: Wikipedia).

The parameter can be edited in the following modules by users with modification rights:

DI041682 Gross profit probability

Gross profit probability of the project (idea, proposal, program)

The parameter can be edited in the following modules by users with modification rights:


DI041683 NPV (without subprojects)

Net present value (net capital value of the selected project (proposal, idea) without taking its possibly existing subprojects into account). For further information on capital value, see here. The value is automatically calculated, taking different parameters like costs, revenues, internal interest, etc. into account. Formula

  • The calculation is carried out in accordance with the standard formula

  • C0 Capital value with regard to t=0
  • i calculation interest rate (=internal interest, e.g. 5%)
  • N review period
  • Zt Flow of payments (cash flow) (source: Wikipedia)
    • In PLANTA, the flow of payments (cash flow) is calculated on an annual basis: Zt = revenues + benefit - costs

Parameters involved (current planning)

Variable from the NPV calculationDI041683 NPV (without subprojects)DI023127 NPVFind end valuesSource values recordable/editable
RevenuesDT861 Total revenues (without subprojects) DT861 Total revenues Budget module, Revenues areaTotal revenues is the sum of Remaining revenues and Actual revenues.
  • Remaining revenues are planned on revenue resources in the Schedule module,
  • Actual revenues result from the postings made in the Post Revenues module.
BenefitDT861 Resulting benefit (without subprojects) DT861 Resulting benefit Budget module, Benefit areaResulting benefit is either determined from Planned benefit or Achieved benefit. Both values are created/edited in the Key performance indicators area in the Project Core Data.
CostsDT282 Total costs (without subprojects) DT282 Total costs Budget module, Costs areaTotal costs is the sum of Actual costs and Remaining costs.
  • Remaining costs are either planned directly for cost resources in the Schedule module or they automatically result from effort values of regular resources which have also been planned in the Schedule module.
  • Actual costs are either posted manually for cost resources in the Post Costs module or they result from the actual hours worked of regular resources recorded in the Time Recording module.
i interest rateDT461 Internal interest DT461 Internal interest Project Core Data, Evaluation data areaProject Core Data, Evaluation data area
N review periodThe planned years in the project (yearly tranches from DT861)The planned years in the project (yearly tranches from DT861)


DI023127 NPV

Net present value (net capital value of the selected project (program, proposal) and all of its subprojects. For further information on capital value, see here. The value is automatically calculated, taking different parameters like costs, revenues, internal interest, etc. into account.

For the calculation formula and the parameters involved, see NPV (without subprojects)


DI041688 Possible damage

In projects: Possible damage of the selected project and all of its subprojects, if available (sum of the Possible damage (without subprojects) values of the selected project and of all of its subprojects).
In programs, ideas, and proposals: Possible damage of the respective planning object since no structures are possible here (here: Possible damage = Possible damage (without subprojects)).

DI063802 Possible damage (without subprojects)

Possible damage of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Possible damage values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI028280 Probable damage

In projects: Probable damage of the selected project and all of its subprojects, if available (sum of the Probable damage (without subprojects) values of the selected project and of all of its subprojects).
In programs, ideas, and proposals: Probable damage of the respective planning object since no structures are possible here (here: Probable damage = Probable damage (without subprojects)).

DI063801 Probable damage (without subprojects)

Probable damage of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Probable damage values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI028281 Actual damage

In projects: Actual damage of the selected project and all of its subprojects, if available (sum of the Actual damage (without subprojects) values of the selected project and of all of its subprojects).
In programs, ideas, and proposals: Actual damage of the respective planning object since no structures are possible here (here: Actual damage = Actual damage (without subprojects)).

DI063800 Actual damage (without subprojects)

Actual damage of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Actual damage values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI041690 Possible damage (active SR)

In projects: Possible damage of the project and all of its subprojects from the active (last released) status report.
In programs: Possible damage of the program from the active (last released) status report. The value is copied from the Possible damage of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI041691 Probable damage (active SR)

In projects: Probable damage of the project and all of its subprojects from the active (last released) status report.
In programs: Probable damage of the program from the active (last released) status report. The value is copied from the Probable damage parameter of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI041699 Actual damage (active SR)

In projects: Actual damage of the project and all of its subprojects from the active (last released) status report.
In programs: Actual damage of the program from the active (last released) status report. The value is copied from the Actual damage parameter of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI041693 Possible gross profit

In projects: Possible gross profit of the selected project and all of its subprojects, if available (sum of the Possible gross profit (without subprojects) values of the selected project of and all of its subprojects).
In programs, ideas, and proposals: Possible gross profit of the respective planning object since no structures are possible here (here: Possible gross profit = Possible gross profit (without subprojects)).

DI063799 Possible damage (without subprojects)

Possible gross profit of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Possible gross profit values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI029618 Probable gross profit

In projects: Probable gross profit of the selected project and all of its subprojects, if available (sum of the Probable gross profit (without subprojects) values of the selected project and all of its subprojects).
In programs, ideas, and proposals: Probable gross profit of the respective planning object since no structures are possible here (here: Probable gross profit = Probable gross profit (without subprojects)).

DI063798 Probable gross profit (without subprojects)

Probable gross profit of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Probable gross profit values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI029619 Actual gross profit

In projects: Actual gross profit of the selected project and all of its subprojects, if available (sum of the Actual gross profit (without subprojects) values of the selected project and all of its subprojects).
In programs, ideas, and proposals: Actual gross profit of the respective planning object since no structures are possible here (here: Actual gross profit = Actual gross profit (without subprojects))

DI063797 Actual gross profit (without subprojects)

Actual gross profit of the selected project without its possibly existing subprojects (program, proposal, idea).
The value is a sum of Actual gross profit values of the individual risks of the project (program, proposal, idea) for which the Active checkbox is activated in the Risks/Opportunities module.

DI041695 Possible gross profit (active SR)

Possible gross profit of the project and all of its subprojects from the active (last released) status report. The value is copied from the Possible gross profit parameter of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI041696 Probable gross profit (active SR)

Probable gross profit of the project and all of its subprojects from the active (last released) status report. The value is copied from the Probable gross profit parameter of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI041698 Actual gross profit (active SR)

Actual gross profit of the project and all of its subprojects from the active (last released) status report. The value is copied from the Actual gross profit parameter of the active status report.

Note

  • Here, the sum value from all planning objects assigned to the portfolio is displayed.

DI058033 Status report: report name

Name of the status report

DI051808 Main project

ID of the main project

DI051885 Calc. start (selected SR)

Calculated project start date from the selected status report. The value is copied from the Calc. start parameter in DT823 Project/report.

DI056393 Deviation total effort: current - selected SR

Deviation of the total effort of the project from the current planning from the total effort of the task from the selected status report

DI056844 Deviation total costs: current - selected SR

Deviation of the total costs of the project from the current planning from the total costs of the task from the selected status report

DI056856 Bar: calculated dates (selected SR)

Bar for the calculated dates of the project from the released status report (Calc. start (selected SR) and Calc. end (selected SR)).

DI056860 Main project (functional) + Main project name

DI056875 VR: Posting type name

Name of the posting type

DI056884 Information

Information on the project

DI041684 Active baseline ID

ID of the active baseline. An active baseline is a baseline that has been created last, in case there are several available.

DI041685 Active status report ID

ID of the active status report. An active status report is a last released status report.

DI056903 Text: active status report

Here, specifications on the active status report are displayed: ID and date of creation

DI056904 Text: active baseline

Here, specifications on the active baseline are displayed: ID and date of creation

DI057673 Area name

Name of the area which is used to group evaluation criteria of a planning object. In input mode, a listbox for selection of an area is displayed on the respective field.

See also: Objective Evaluation Criteria

DI057712 Project name

Name of the project. In input mode, a listbox for selection of a project is displayed on the respective field.

DI001021 Earliest start

Earliest start date of the project which is determined during scheduling.

Calculation

DI001022 Earliest end

Earliest end date of the project which is determined during scheduling.

Calculation

DI001479 Latest start

Latest start date of the project which is determined during scheduling.

Calculation

DI001480 Latest end

Latest end date of the project which is determined during scheduling.

Calculation

DI062551 Position

Defines the position of the subprojects in the project structure. Is automatically set when moving subprojects within the Subprojects module.

DI061310 Main milestone

Milestone of the planning object. A listbox is implemented on the field which displays all master milestones of the planning object. You can define one of them as main milestone. Master milestones are used as reference point for different calculations and analyses, a.o. for the calculation of time intervals from the main milestone to other master milestones..

Note

  • If you select a main milestone, you have to activate the Schedule with gates checkbox so that the time interval (in weeks) from master milestones to the main milestone can be displayed on the gates.
  • The master milestone has no interval indication on the gate and also differs from other gates in graphical terms, since on a gate it has a darker border.
  • If no master milestone has been defined but the Schedule with gates checkbox is activated, the calculated end date of the project will be used as a reference point for the calculation of the interval. If there is a master milestone on the calculated end date of the project, the respective gate does not contain an interval indication either (however, it is still not a master milestone and accordingly it has no dark border).
  • The interval calculation is carried out when the client is started. A client restart therefore becomes necessary if you want to have the intervals updated after you have, e.g., selected a new main milestone or changed an existing one or if the calculated date of the project has changed.

The parameter can be edited in the following modules by users with modification rights:

DI061292 Main milestone date

The scheduled date of the main milestone. It is automatically displayed as soon as you have selected the main milestone for the project from the Main milestone listbox.

DI061314 Schedule with gates

Checkbox which serves to define whether in the schedule master milestones are to be displayed additionally on the horizontal date axis directly below the scale. If the checkbox is activated and the master milestones are displayed as gates below the scale, a time interval to the main milestone is displayed on every gate. If it is not defined the interval to the calculated end of the project will be displayed. 

The parameter can be edited in the following modules by users with modification rights:

DI059689 % actual costs to total costs

Percentage ratio between Actual costs and Total costs

DI059690 % actual costs to cost budget

Percentage ratio between Actual costs and Cost budget

DI059691 % actual costs to planned costs

Percentage ratio between Actual costs and Planned costs

DI059692 % actual effort to total effort

Percentage ratio between Actual effort and Total effort

DI059693 % actual effort to effort budget

Percentage ratio between Actual effort and Effort budget

DI059694 % actual effort to planned effort

Percentage ratio between Actual effort and Planned effort

DI060763 Arrow down

This DI is used to customize the function for transferring values from one column to another. The DI is, e.g., used in the Budget module and is realized in the form of arrows pointing downwards.

DI061427 Earned value analysis active

Help DI. Is used as a filter DI in data areas that are only to be displayed if the Earned value analysis active model parameter is activated.

DI063717 Number of deviating tasks

Outputs the number of tasks that have been changed

DI060746 Year virt.

Listbox for selecting the years for manual yearly tranche input

DI063831 Risk green

Parameter which displays the number of risks in the project (program) with a green traffic light

Details


DI063832 Risk yellow

Parameter which displays the number of risks in the project (program) with a yellow traffic light

For details, see Risk green


DI063833 Risk red

Parameter which displays the number of risks in the project (program) with a red traffic light

For details, see Risk green

DI063217 Decisions

Text field for entering comments

DI063216 Measures

Text field for entering comments

DI063109 Bar: calculated dates (dotted)

Bar for the visualization of the calculated duration of a project below the scale in milestone overview modules.

DI008759 Comment

Text field for writing a comment

DI063189 Date of last budget calculation

Here, the date on which the budget data was recalculated the last time is stamped.

See also: Calculation Matrix for Dates, Costs, and Budgets

DI063188 Time of last budgeting calculation

Here, the time at which the budget data was recalculated the last time is stamped.

See also: Calculation Matrix for Dates, Costs, and Budgets

DI063979 Date of last cost calculation

Here, the date on which the costs were recalculated the last time is stamped.

See also: Calculation Matrix for Dates, Costs, and Budgets

DI063980 Time of last cost calculation

Here, the time at which the costs were recalculated the last time is stamped.

See also: Calculation Matrix for Dates, Costs, and Budgets

DI063607 Select

Checkbox for selecting a project for the creation of a controlling status report

The parameter can be edited in the following modules by users with modification rights:

DI064208 Opportunity red

Parameter which shows the number of opportunities in the project (program) with "red" traffic light.

Details

DI064209 Opportunity yellow

Parameter which shows the number of opportunities in the project (program) with "yellow" traffic light.

For details, see Opportunity red

DI064210 Opportunity green

Parameter which shows the number of opportunities in the project (program) with "green" traffic light.

For details, see Opportunity red

064550 Road map: start

In this field, the start date from the last released road map will be displayed if the current project is planned in a road map and the Show road map dates global setting = 1.

Note

  • If the project is assigned to several portfolios, the earliest roadmap dates will be displayed.

064551 Road map: end

If the current project is planned in a road map and the Show road map dates global setting = 1, the end date from the last released road map will be displayed in this field.

Note

  • If the project is assigned to several portfolios, the earliest roadmap dates will be displayed.

DI064672 Date of last liability import

Is set if all yearly tranches for a project are imported correctly during liability import

DI064673 Time of last liability import

Is set if all yearly tranches for a project are imported correctly

DI065828 External system

Parameter which defines with which external system the data from PLANTA project is to be synchronized. The respective field with a listbox for the selection of an external system is only displayed in the Project Core Data module and it will only be displayed once the interfaces to the corresponding systems (PLANTA pulse and/or Jira) have been configured.

  Values

  • If Jira is configured: Jira
  • If pulse is configured: pulse
  • If both are configured: Jira; pulse

  Note

  • A project can only be synchronized with one system, with PLANTA pulse or with Jira

  Details

  • If "Jira" is selected,
    • PLANTA project checks 
      • whether the project is unlocked in PLANTA project. Otherwise, a message will be displayed and the value in the external system field will be reset.
      • whether the functional ID of the project complies with the Jira specifications for project IDs. According to these specifications, a project ID must not contain more than 10 characters. It must begin with a letter and must not contain any special characters. Otherwise, a message will be displayed and the value in the external system field will be reset.
    • Jira checks whether the project name already exists. If it does exist, a message will be displayed and the value in the external system field will be reset.
  • If you have selected an external system, the     Synchronize button is displayed next to the External system field in the Project Core Data module via which you can open the Synchronizable Tasks module  to synchronize tasks with PLANTA pulse or Jira.

  See also:  Application under:  PLANTA project and PLANTA pulse (PLANTA Hybrid),  PLANTA project and Jira, Setting up Interfaces under:  PLANTA project and PLANTA pulse (PLANTA Hybrid), PLANTA project and Jira.

DI065857 Select

Checkbox for the selection of a project, e.g. in the Assign Planning Objects to the Portfolio module

DI066014 Resource requests

Parameter that defines whether and in what form Resource Planning with Requests/Approvals is active in the project. The respective field with a listbox for selection will be displayed in the Edit Planning Objects module.

Values

  • inactive: Resource requests/approvals are inactive, i.e. all resources can be planned freely in the schedule. Modules and buttons which belong to resource requests/approvals are not visible.
  • active on project level: Project resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved on project level via the request/approval process.
  • active on task level: Task resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved on task level via the request/approval process.

Notes

  • The listbox is only displayed in the Edit Planning Objects module if resource requests are activated on global level (Resource requests active = 1 or 2).
  • For new projects, the global setting is used by default. In the Edit Planning Objects module, the setting can be changed per project.
  • If the setting is to be changed after requests have already been created, a query will be displayed asking whether the existing requests are to be archived. The setting will only be saved upon confirmation.
  • If resource requests are activated in the project after resources have already been planned, no requests will be generated retroactively for these resources.

DI065942 Forecast

Here the number of forecasts on additional effort issued for a project in the course of the recording of hours worked will be displayed. A link is implemented on the number which leads to the Progress module in which you can either view details on forecasts or edit forecasts.

DI066146 Days up to project start/end

In this field, the number of days up to project start or end will be displayed.

Details

  • The time up to project start will be displayed for projects the project start (Calc. start) of which lies in the future.
  • The time up to project end will be displayed for projects the project start (Calc. start) lies in the past and the project end (Calc. end of which lies in the future.

DI062199 Dependency exists

The active Dependencies checkbox shows that the respective project depends on other projects.