The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>CustomizingDocumentation>CustomizingDataFields>DT401ModelParameters

DT401 Model Parameters

DI000001 License

License number of the software

DI000065 System title

In this field, the system name is displayed/entered.

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

DI000068 Fix today's date

Here, the date can be entered for the active today line which is to be used for scheduling and for the Gantt chart display.

Values

  • arbitrary date
  • blank: system date of the program server

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

From DB 39.5.12

DI000075 Calculation indicator

The field is filled in the calculation of the schedules (replanning) and must only be set to "0" manually in the case of program termination.

Values

Value Meaning Notes
-1 Replanning As long as the Calculation indicator parameter has the value -1,
  • no further schedule calculation (replanning) can be started
  • no changes to period data must be made

If the calculation is aborted, the value in the Calculation indicator field remains the same and must be set to 0 manually in the Scheduling Status module. Additionally, you have to deactivate the Calculation active checkbox.
0 No individual project calculation is active  
Number 1 Number of active single project calculations Depending on the field format, this value can be output with a "+" symbol. Example: the value +2 means that 2 calculations are in progress at the moment.

If capacity scheduling is initiated simultaneously for different projects that share the same resources (or at least share one resource), it is only launched for one project while in the other modules a message is displayed indicating that one or several resources are used by another capacity scheduling. The scheduling must be carried out successively for all projects in question. Projects with different resources, however, can be scheduled simultaneously.

If the capacity scheduling procedure is aborted, the value in the Calculation indicator field remains the same and must be set to 0 manually in the Scheduling Status module. In addition, you have to deactivate the Calculation active checkbox.

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

Up to DB 39.5.12

DI000075 Capacity scheduling indicator

The field is always filled by the capacity scheduling and must be set to "0" manually if the program is quit.

Values

Value Meaning Notes
-1 Replanning As long as the Capacity scheduling indicator parameter has the value -1,
  • no further capacity scheduling procedure can be started
  • no changes to capacity scheduling period data must be made

If the capacity scheduling procedure is aborted, the value in the Capacity scheduling indicator field remains the same and must be set to 0 manually in the Scheduling Status module. Additionally, you have to deactivate the Capacity scheduling active checkbox.
0 No capacity scheduling in progress  
Number 1 Number of active capacity scheduling procedures Depending on the field format, this value can be output with a "+" symbol. Example: the value +2 means that 2 scheduling procedures are in progress at the moment.

If capacity scheduling is initiated simultaneously for different projects that share the same resources (or at least share one resource), it is only launched for one project while in the other modules a message is displayed indicating that one or several resources are used by another capacity scheduling. The scheduling must be carried out successively for all projects in question. Projects with different resources, however, can be scheduled simultaneously.

If the capacity scheduling procedure is aborted, the value in the Capacity scheduling indicator field remains the same and must be set to 0 manually in the Scheduling Status module. In addition, you have to deactivate the Capacity scheduling active checkbox.

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

DI000076 Utilization code 1

In this parameter, the value of one of the 5 (PLANTA Standard) planning object codes is entered. This is necessary if the utilization of the planning objects is to be displayed according to their codes.

Details

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

DI000077 Utilization code 2

For description, see Utilization Code 1

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

DI000078 Utilization code 3

For description, see Utilization Code 1

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

DI000079 Utilization code 4

For description, see Utilization Code 1

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

DI000085 Project requested dates for float

Option for taking the project requested dates into account during float value calculation

Values

  • Checked: Take into account
  • Unchecked: Do not take into account (for comparison purposes only)

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

DI000086 Task requested dates

Option for taking the requested dates for tasks into account, i.e. a task is fixed at its requested start or requested end, provided that no links conflict with this

Details

Values

  • Checked: Take into account
  • Unchecked: Do not take into account (for comparison purposes only)

Note

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

DI000089 Load limit 2

Determines whether the value specified in the Load limit % field in the Resource Data Sheet module is applicable to the capacity adjustment

Values

  • Checked: The resource will be loaded up to the maximum of Load limit %.
  • Unchecked: The resource will be loaded up to a maximum of 100%.

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

DI000093 Task release

Option for influencing the Task release field through the capacity scheduling when the predecessor task has been completed. Depending on the parameter setting, the successor task is not released for editing until the predecessor has been completed.

Values

  • no entry: no influence, i.e. the field is maintained manually by the user.
  • 1: released, when
  • 2: released, when

Details

  • If the Earliest start of the task is not in the future (if the today line is inactive, the today fixing from the model parameters or the computer date is applied) and the task has no Actual start, an Actual start is automatically set for the task.
  • Actual start of the task is determined from: latest date from Earliest start on the basis of links and the Requested start of the task.
  • Any Actual start that has already been set, will be ignored. For tasks that have a subproject, the Actual start will not be set automatically.

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

DI000095 Structure scheduling w. adjustment

Structure scheduling with adjustment

Values

  • 0
    • There is no adjustment between main and subprojects. In the structure tasks of the main project, data of the subprojects is included for comparison purposes.
    • In the cost overview, only the sum of the costs of all structure tasks is displayed in the main project. Amounts that have been posted on the subprojects are only shown in the subproject, not in the main project.
  • 1
    • Durations, effort, dates, and costs are automatically adjusted between main and subprojects. As a result, data entered manually such as actual start dates are overwritten.
    • In the cost overview, the costs of all tasks of the main project are summarized.
  • 2
    • The following data is adjusted between main and subprojects:
    • In the cost overview, the costs of all tasks of the main project are summarized.
  • 3
    • The main project manager can specify the key dates of the subproject in the Requested SD and Requested ED fields.
    • The project requested dates are transferred to the requested dates of the parent structure task. All other durations and dates of the subproject are transferred to the main project for your information only and can be displayed for comparison purposes there.
    • No key dates are transferred from the main project to the subproject.
    • In the cost overview, the costs of all tasks in the main project are summarized.

Notes

  • For cost calculation purposes, you are advised to enter effort and costs only on one level, like e.g. the subproject level. You should avoid entering effort and costs on structure task, main, and subproject level at the same time.
  • The standard modules do not contain these data items for structure scheduling.

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

DI000132 Time recording key date

Key date for putting a date limit on the time period oriented reporting. Once the key date has been set, it is no longer possible to create or change load records with dates that are on or earlier than this key date.

Data items that can be locked by a key date performance

Attention

  • When you use automatic reverse postings, you have to note that under particular settings of the posting_cancelation global parameter the effect of the Key date performance parameter is virtually undermined. Data can still not be created before the key date, however, already created postings can be corrected or deleted. For these postings, reverse postings are then recorded automatically.
The parameter can be edited by users with modification rights in the following module:

See also: Reverse Postings

From DB 39.5.13

DI000087 Time recording date

This parameter is currently without function. For information on the behavior of the time recording date of a task, please refer to the description of the task parameter of the same name.

Up DB 39.5.13

DI000087 Reporting date


From DB 39.5.11

DI000158 Active today line

Option with which you can define whether Fix today’s date is considered in the calculation of a schedule. This option is a means to determine whether tasks that are earlier than "today" are moved or prolonged or whether they remain in the past unchanged.

Values

  • Checked: Consideration of Fix today’s date (today line active).
    • Tasks with requested dates in the past and without Actual start are shifted to today’s date.
    • Tasks with requested dates in the past and Fixing = 1, always remain in the past, the rest is calculated starting from the today line. The AOBs are ignored here.
    • Tasks with Actual start and without Actual end
      • For Split = Checked: Actual start remains in the past, Calc. start is calculated starting from the today line. The task is not extended but the calc. end is moved forward.
      • For Split = Unchecked, Calc. start = Actual start. The task is extended.
  • Unchecked: no consideration of the Fix today’s date (today line inactive).
    • If there are requested dates on the project and they lie in the past, the entire schedule remains in the past accordingly.
    • If there are no requested dates, the schedule is calculated starting from the today line up to the tasks which fulfill the following conditions:
      • Tasks with requested dates in the past and Fixing = 1, as well as all predecessors and successors of these tasks, always remain in the past, the remainder is calculated starting from the today line.
      • Tasks with Actual start and without Actual end and all predecessors and successors of these tasks
The parameter can be edited by users with modification rights in the following module:

Up to DB 39.5.11

DI000158 Consider today's date

Option with which you can define whether the date fixed for 'today' is considered in capacity scheduling

Values

  • Checked: Fix today’s date is considered (active today’s line).
  • Unchecked: Fix today’s date is not considered (today’s line not active).
    • Tasks with requested dates earlier than today and without Actual start (and without links) start at the requested dates, also if they lie in the past. If no requested dates exist either, they start at today’s date.
    • Tasks with Actual start shift the remaining duration, but the task is not extended (as is the case with active today line).

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

DI000300 Delete parent task

Option for deleting subprojects

Values

  • Checked: When a subproject is deleted, the parent structure task will be deleted at the same time.
  • Unchecked : When a subproject is deleted, the parent structure task will not be deleted at the same time.

Attention

  • This option should be used with care.

From DB 39.5.12

DI000832 Schedule calc. with cost planning

Values

  • 0: Date scheduling and replanning without cost calculation. Dates and capacities are calculated
  • 1: Date scheduling and replanning with cost calculation Dates, capacities, and costs are calculated

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

Up to DB 39.5.12

DI000832 Capacity scheduling with cost planning

Values

  • 0: Date scheduling and replanning without cost calculation
  • 1: Date scheduling and replanning with cost calculation
The parameter can be edited by users with modification rights in the following module:

DI059356 manual cost input

From DB 39.5.0

The parameter defines whether the cost data
  • Checked is recorded manually and the respective fields in the user modules are set to "input" or
  • Unchecked are calculated automatically (load table DT472) and the respective fields in user modules are set to "output". If this option is selected, the definition in the Schedule calc. with costs parameter is required in addition
Additionally, the parameter determines which variant of the Budget module is loaded by default when opening the module. Base or Costs from load profile.

Up to DB 39.5.0

This parameter determines whether cost data can be entered manually and the respective cost fields in user modules are input fields or automatically calculated cost data from load data table DT472 is output (fields are output fields). Additionally, the parameter determines which variant of the Budget module is loaded by default: Base or Costs from Load Table.

Details

  • If the Manual cost recording parameter is activated, no capacities are calculated in date scheduling (in the individual project or in replanning) but only dates.
  • As soon as the manual cost input parameter is activated, the Time scheduling options parameter is set to 1 automatically in order for bars for calculated dates to be visible in the schedule after time scheduling has been carried out.
  • If you change it to manual cost input after having used automatic cost input for a while, all effort data which was calculated before is maintained and will not be overwritten upon time scheduling.

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

DI002353 Last replanning by

ID (code) of the user who performed the last replanning. This field is filled automatically.

DI058238 Last replanning by name

Name of the user who performed the last replanning

DI002354 Last replanning on

Date on which the last scheduling was performed. This field is filled automatically.

DI002355 Start last replanning at (time)

In this field, the start (time) of the last replanning is displayed, regardless of whether the replanning has been run successfully or not.

DI002356 End last replanning at (time)

In this field, the end (time) of the last replanning is displayed, regardless of whether the replanning has been run successfully or not.

DI026596 Model

ID of the model. It is automatically generated upon saving.

Details

  • Model means a scheduling model.
  • Per license, several models are created but only one model can be activated and hence considered by the scheduling.

DI026548 Active

By activating this parameter, it is determined which model is active. Only the parameters of the active model are considered in date scheduling.

Note

  • A license can contain several models, but only one model can be activated.

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

DI026547 Model name

Name of the current model

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

DI026597 License

License number of the installation

Parameter for controlling the display of date change causes

Values

  • 0: All causes of a chain are displayed.
  • 1: Only the direct cause of a chain is displayed (inheritance)

DI034657 Cross-project links soft

From DB 39.5.7

This parameter is currently non-functional.

Parameters for controlling the link behavior

Details

  • If this parameter is activated, links to external tasks can only be created if they are set to "soft".
    • To do so, activate the Soft link checkbox (this checkbox is hidden in the Schedule module by default but can be displayed) after you have created a new link record. Only then the external task can be selected from the listbox.
The parameter can be edited by users with modification rights in the following module:

Up to DB 39.5.7

The parameter is currently non-functional.

Parameters for controlling the link behavior

Details

  • If this parameter is activated, links to external tasks can only be created if they are set to "soft".
    • To do so, activate the Soft link checkbox (this checkbox is hidden in the Schedule module by default but can be displayed) after you have created a new link record. Only then the external task can be selected from the listbox.

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

DI034658 No links on master milestones

From DB 39.5.7

This parameter is currently non-functional.

Parameters for controlling the link behavior

Details

  • If this parameter is activated, no links to master milestones can be created in the Schedule module. This is indicated by a message.
  • This parameter cannot be activated if there already are links on master milestones. If this is required, all links on master milestones must be deleted in all projects.

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

Up to DB 39.5.7

The parameter is currently non-functional.

Parameters for controlling the link behavior

Details

  • If this parameter is activated, no links to master milestones can be created in the Schedule module. This is indicated by a message.
  • This parameter cannot be activated if there already are links on master milestones. If this is required, all links on master milestones must be deleted in all projects.
The parameter can be edited by users with modification rights in the following module:

DI040171 Deactivate generation of planned load

This parameter controls the creation of planned load records for resource assignments with Actual end set.

Values

  • Checked: If an actual end is set for a resource which has no actual loads, all existing remaining loads and planned loads are deleted.
  • Unchecked: If an actual end is set for a resource which has no actual loads, all existing remaining loads are deleted and planned loads are retained on the record as a sum.

Notes

  • The parameter controls the behavior of planned loads in resources which have no actual loads yet. If a resource has actual loads, the planned loads are distributed evenly among all actual records when an actual end is set.
  • If this parameter is activated, the data amount can be kept at a minimum.

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

DI040172 Status reports from

From DB 39.5.11

In this field, the start date is entered from which it is searched for projects for which the Status reports: summary creation is activated but which do not contain any status reports from the defined date NEW up to today's date. The end date is entered in the Status report to field.

Details

  • You can define both system variables (incl. @ maximum 3 digits) and a date in MM/DD/YY format.
  • You can also combine system variables with date entries.
  • In the Standard, the respective field (No status report since) is NEW preset with @42 (first day of the current year).

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

See also: Collective Creation of Status Reports

From DB 39.5.10

In this field, the start date is entered for the period in which it is searched for projects for which the NEW Status reports: summary creation is activated but do not contain any status reports in the defined period. The end date is entered in the Status report to field.

Details

  • You can define both system variables (incl. @ maximum 3 digits) and a date in MM/DD/YY format.
  • You can also combine system variables with date entries.
  • In the Standard, the respective field is preset with @42 (first day of the current year).

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

See also: Collective Creation of Status Reports

Up to DB 39.5.10

In this field, the start date is entered for the period in which it is searched for projects for which the Automatically create status report is activated but which, however, do not contain any status reports in the defined period. The end date is entered in the Status report to field.

Details

  • You can define both system variables (incl. @ maximum 3 digits) and a date in MM/DD/YY format.
  • You can also combine system variables with date entries.
  • In the Standard, the respective field is preset with @42 (first day of the current year).

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

See also: Collective Creation of Status Reports

DI040173 Status reports to

From DB 39.5.11

From this version, the field is no longer used. For the summary creation function, only the Status reports from parameter is used.

From DB 39.5.10

In this field, the end date is entered for the period in which it is searched for projects for which the NEW Status reports: summary creation is activated but do not contain any status reports in the defined period. The start date is entered in the Status report from field.

Details

  • You can define both system variables (incl. @ maximum 3 digits) and a date in MM/DD/YY format.
  • You can also combine system variables with date entries.
  • NEW In the Standard, the respective field is preset with @43 (first day of the current year).

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

See also: Collective Creation of Status Reports

Up to DB 39.5.10

In this field, the end date is entered for the period in which it is searched for projects for which the Automatically create status report is activated but which, however, do not contain any status reports in the defined period. The start date is entered in the Status report to field.

Details

  • You can define both system variables (incl. @ maximum 3 digits) and a date in MM/DD/YY format.
  • You can also combine system variables with date entries.
  • In the Standard, the respective field is preset with @42 (first day of the current year).

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

See also: Collective Creation of Status Reports

DI061538 Start task successor + 1 day

Controls the start date of the task successor

Values

  • Checked: if a task has a duration of 0 days, the task successor starts one day later.
  • Unchecked: if a task has a duration of 0 days, the task successor starts on the same day.

Example

  • Initial situation: a project with 3 tasks
    • TA 1 duration 10, link to TA 2
    • TA 2 duration 0, link to TA 3
    • TA 3 Duration 10

  • Scheduling with Start TA successor + 1 D model parameter (DI061538) = Checked:
    • Calculated dates:
      • TA 1 07/09 - 07/22
      • TA 2 07/22 - 07/22
      • TA 3 07/23 - 08/05
    • Project duration = 20 D
  • Scheduling with Start TA successor + 1 D model parameter (DI061538) = Unchecked:
    • Calculated dates:
      • TA 1 07/09 - 07/22
      • TA 2 07/22 - 07/22
      • TA 3 07/22 - 08/04
    • Project duration = 19 D

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

See also: Calculation of successor dates

DI061426 Earned value analysis active

This parameter controls whether the earned value function is activated or not.

Values

  • Unchecked: Earned value files are not calculated or summarized.
  • Checked: The calculation of the earned value data across all projects and reports is carried out after the query has been confirmed.

New from DB 39.5.7

Note
  • Upon reactivation of the checkbox, the The activation of the earned value analysis leads to a recalculation of the earned value files in all existing projects. This may take some time. Continue? message is displayed.

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



Attention: The following parameters are currently not used

DI022743 Time scheduling options

Options for the calculation of the dates with Time scheduling menu item

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

Values

  • 0: Time scheduling only calculates the earliest and latest dates of the tasks.
  • 1: Date scheduling takes the Planning early task parameter into account and calculates the dates: calculated start and calculated end of the task. A cost calculation is not run. Date scheduling then equates to a capacity scheduling without load, capacity adjustment and cost calculation.

DI002930 Scheduling opt.exec. time

The parameter is contained in the Model and Model Parameters module, however, it is without function.



Attention: The following parameters are no longer used and are no longer contained in the Model and Model Parameters module.

Removed in DB 39.5.10

DI000088 Adjustment limit

DI000090 Deviation start 1

DI000833 Deviation start 2

DI000834 Deviation start 3

DI000835 Deviation start 4

DI000836 Deviation start 5

DI000091 Deviation end 1

DI000837 Deviation end 2

DI000838 Deviation end 3

DI000839 Deviation end 4

DI000840 Deviation end 5

DI034607 Deviation control

Removed in DB 39.5.7

DI000081 Scheduling forward

Original descriptions

DI000088 Adjustment limit

In releases from 39, this parameter is without function.

DI000090 Start 1 deviation

This option defines the calculation procedure for the start date deviation fields of projects and tasks.

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

Values for task scheduling

Note

  • For value 9: x=1 is invalid

DI000833 Start 2 deviation

For description, see Start 1 deviation

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

DI000834 Start 3 deviation

For description, see Start 1 deviation

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

DI000835 Start 4 deviation

For description, see Start 1 deviation

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

DI000836 Start 5 deviation

For description, see Start 1 deviation

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

DI000091 End 1 deviation

This option defines the calculation procedure for the project and task date deviation fields of the end dates.

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

Values for task scheduling

Note

  • For value 9: x=1 is invalid

DI000837 End 2 deviation

For description, see End 1 deviation

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

DI000838 End 3 deviation

For description, see End 1 deviation

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

DI000839 End 4 deviation

For description, see End 1 deviation

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

DI000840 End 5 deviation

For description, see End 1 deviation

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

DI034607 Deviation controlling

The causes of the date changes must be determined and visualized for a project manager in the schedule environment.
  • The controlling that determines which deviation is calculated is carried out across the system in the same way for all projects using the model parameters.
Values
  • 0: the Cause data table will not be filled or possibly existing data will be deleted.
  • 1: deviation required dates:
    • Dev. fixed task: calculated end cause for requested start task
    • Dev. fixed successor: calculated end task to requested start moved
    • Dev. soft task: earliest end soft cause for requested start task
    • Dev. soft successor: earliest end soft task to requested start moved
  • 2: deviation planned dates 1:
    • Dev. fixed task: calculated end cause for planned start1 task
    • Dev. fixed successor: calculated end task to planned start1 moved
    • Dev. soft task: earliest end soft cause for planned start1 task
    • Dev. soft successor: earliest end soft task to planned start1 moved
  • 3: deviation planned dates 2:
    • Dev. fixed task: calculated end cause for planned start2 task
    • Dev. fixed successor: calculated end task to planned start2 moved
    • Dev. soft task: earliest end soft cause for planned start2 task
    • Dev. soft successor: earliest end soft task to planned start2 moved
  • 4: deviation planned dates 3:
    • Dev. fixed task: calculated end cause for planned start3 task
    • Dev. fixed successor: calculated end task to planned start3 moved
    • Dev. soft task: earliest end soft cause for planned start3 task
    • Dev. soft successor: earliest end soft task to planned start3 moved
  • 5: deviation planned dates 4:
    • Dev. fixed task: calculated end cause for planned start4 task
    • Dev. fixed successor: calculated end task to planned start4 moved
    • Dev. soft task: earliest end soft cause for planned start4 task
    • Dev. soft successor: earliest end soft task to planned start4 moved
  • 6: deviation planned dates 5:
    • Dev. fixed task: calculated end cause for planned start5 task
    • Dev. fixed successor: calculated end task to planned start5 moved
    • Dev. soft task: earliest end soft cause for planned start5 task
    • Dev. soft successor: earliest end soft task to planned start5 moved

DI000081 Scheduling forward

Values

Note

  • In both cases, the earliest and latest task and project dates are always calculated. Forward and backward scheduling do not depend on whether a task is planned in as early or as late as possible. The only difference is the starting point of the calculation.

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

         PLANTA project







 
  • Suche in Topic-Namen

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