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 in the following module by users with modification rights:
DI000068 Fix today's date
Here, the date can be entered for the Active today’s line which is to be used for scheduling and for Gantt chart display.
Values
- arbitrary date
- blank: system date of the program server
The parameter can be edited in the following module by users with modification rights:
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 | Note |
|---|---|---|
| -1 | Replanning | As long as -1 is entered as a value in the Calculation indicator parameter,
If the calculation is aborted, the value in the Calculation indicator field is retained and must be set to 0 manually and the Calculation active checkbox must be deactivated in the Scheduling Status module. |
| 0 | No active single project calculation | |
| 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 a schedule calculation 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 schedule calculation. The calculation must be carried out for all affected projects one after the other. Projects with different resources, however, can be calculated simultaneously. If the calculation is aborted, the value in the Calculation indicator field remains the same and must be set to 0 manually and the Calculation active checkbox must be deactivated in the Scheduling Status module. |
The parameter can be edited in the following module by users with modification rights:
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 values of the planning objects the codes of which are entered in the Utilization code 1 to Utilization code 4 model parameters will be taken into account in the period IDs (Summarized planned code 1 to Summarized planned code 4) on the basis of which the utilization diagrams are visualized.
- If the planning object code does not match one of the values of the four Utilization code parameters, the utilization of such a planning object with the Utilized planned code 5 symbol DI which is defined in the Histo: summarized planned by code histogram data item is displayed.
The parameter can be edited in the following module by users with modification rights:
DI000077 Utilization code 2
For description, see Utilization code 1.
The parameter can be edited in the following module by users with modification rights:
DI000078 Utilization code 3
For description, see Utilization code 1.
The parameter can be edited in the following module by users with modification rights:
DI000079 Utilization code 4
For description, see Utilization code 1.
The parameter can be edited in the following module by users with modification rights:
DI000085 Project requested dates for float
Option for taking the project requested dates into account during float value calculation
Values
- : taken into account
- : not taken into account (only comparison)
The parameter can be edited in the following module by users with modification rights:
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
- Fixing means that
- if Requested start of the task has been recorded, Earliest start of the task (time recording) and Calc. start of the task (schedule calculation) become Requested start of the task.
- if Requested end of the task has been recorded, Earliest start of the task (time recording) and Calc. start of the task (schedule calculation) become Requested end - Remaining duration of the task.
- The task is then loaded with adherence to schedule.
Values
- : taken into account
- : not taken into account (only comparison)
Note
- If Requested start and Requested end of the task have been recorded, the following applies:
- when scheduling forwards, the Requested start of the task takes effect.
- when scheduling backwards, the Requested end of the task takes effect.
The parameter can be edited in the following module by users with modification rights:
DI000089 Load limit 2
Determines whether capacity adjustment is based on the value specified in the Load limit % field in the Resource Data Sheet module
Values
- : The resource will be loaded up to the maximum of Load limit %.
- : The resource will be loaded up to a maximum of 100%.
The parameter can be edited in the following module by users with modification rights:
DI000093 Task release
Option with which the Task release field can be influenced by the 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
- all task relations (Actual start/Actual end are set) are completed.
- 2: released, when
- all predecessors with Link type FS have an Actual end
- all predecessors with Link type SS have an Actual start
- all predecessors with Link type SF and FF will not be taken into account.
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.
- The Actual start of the task is determined from: latest date from Actual start based on the 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 in the following module by users with modification rights:
DI000095 Structure scheduling with adjustment
Structure scheduling with adjustment
Values
- 0
- There will be 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 will be adjusted between main and subprojects:
- DI001119 Calc. start of the structure task is copied to DI001019 Requested start of the subproject.
- DI001120 Calc. end of the structure task will be copied to DI001020 Requested end of the subproject.
- Other data like Planned duration / Actual / Remaining/structure and DI001123 Structure start will be copied to the main project and can be visualized there for comparison purposes.
- In the cost overview, the costs of all tasks of the main project are summarized.
- The following data will be adjusted between main and subprojects:
- 3
- The main project manager can specify the key dates of the subproject in the Requested start and Requested end 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 of the main project are summarized.
Notes
- For cost calculation purposes you are advised to enter effort and costs only at one level, like e.g. the subproject level. You should avoid entering effort and costs at structure task, main, and subproject level at the same time.
- The standard modules do not contain these data items for structure calculation.
The parameter can be edited in the following module by users with modification rights:
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 not possible to create or change load records with load dates that are on this key date or earlier than this key date.
Note the following exceptions: When you use automatic reverse postings, you have to note that under particular settings of the global Reverse posting variant parameter, the effect of the Time recording key date parameter is virtually softened. 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.
Data items that can be locked by a time recording key date:
The parameter can be edited in the following module by users with modification rights:
See also: Reverse Postings |
DI000158 Active today line
Option with which you can define whether Fix today's date will be taken into account 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
- : Fix today's date taken into account (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
- When Split = : 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.
- When Split = : Calc. start = Actual start. The task is extended.
- : Fix today's date not taken into account (today line active).
- 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
- When Split = : Actual start remains in the past, Calc. start begins dependent on links or other factors. The task is not extended.
- When Split = : Calc. start = Actual start. The task is not extended.
The parameter can be edited in the following module by users with modification rights:
DI000832 Schedule calc. with costs
Values
- 0: Scheduling and replanning without cost calculation. Dates and capacities are calculated
- 1: Scheduling and replanning with cost calculation Dates, capacities, and costs are calculated
The parameter can be edited in the following module by users with modification rights:
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.
DI059356 Manual cost input
The parameter defines whether the cost data
- is recorded manually and the respective fields in the user modules are set to "input" or
- 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
Details
- If the manual cost recording parameter is activated, no capacities are calculated during scheduling (in the individual project or in replanning) but only dates.
- As soon as the manual cost recording parameter is activated, the Time recording 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 switch to manual cost input after having used automatic cost input for a while, all effort data which was calculated before is retained and will not be overwritten during time scheduling.
The parameter can be edited in the following module by users with modification rights:
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 (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 (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 can be created but only one model can be activated and will hence be taken into account during scheduling.
DI026548 Active
By activating this parameter, it is determined which model is active. Only the parameters of the active model are considered during scheduling.
Note
- A license can contain several models, but only one model can be activated.
The parameter can be edited in the following module by users with modification rights:
DI026547 Model name
Name of the current model
The parameter can be edited in the following module by users with modification rights:
DI026597 License
License number of the PLANTA software parameter for controlling the display of the cause of date changes
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
Parameter for controlling the behavior of cross-project links.
Details
- If this parameter is activated, links to external tasks can only be created if they are set to "soft".
The parameter can be edited in the following module by users with modification rights:
DI034658 No link on master milestones
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.
- links on master milestones. If this is required, all links on master milestones must be deleted in all projects.
The parameter can be edited in the following module by users with modification rights:
DI040171 Deactivate generation of planned load
This parameter controls the creation of planned load records for resource assignments with Actual end set.
Values
- : If an actual end is set for a resource which has no actual loads, all existing remaining loads and planned loads are deleted.
- : 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 in the following module by users with modification rights:
DI040172 Status reports from
The date (in mm.dd.yy format) from which on the search will be performed for projects for which the Status report: collective creation parameter is activated in the Project Core Data module and which, however, do not have status reports between the defined date and today. In PLANTA standard, the respective data field in the Check Status Report Creation and Project Applications module is named No status report since and it is preset with the date of the first day of the current year (@42).
Note: This field does not accept the input of system variables which do not contain a date.
See also: Collective Creation of Status Reports |
DI061538 Start task successor + 1 day
Controls the start date of the task successor
Values
- : if a task has a duration of 0 days, the task successor starts one day later.
- : 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) = :
- Calculated dates:
- TA 1: 07/09 - 07/22
- TA 2: 07/22 - 07/22
- TA 3: 07/23 - 08/05
- Project duration = 20 d
- Calculated dates:
- Scheduling with Start TA successor + 1 d model parameter (DI061538) = :
- Calculated dates:
- TA 1: 07/09 - 07/22
- TA 2: 07/22 - 07/22
- TA 3: 07/22 - 08/04
- Project duration = 19 d
- Calculated dates:
The parameter can be edited in the following module by users with modification rights:
See also: Calculation of Successor Dates |
DI061426 Earned value analysis active
This parameter controls whether the earned value function is activated or not.
Values
- : Earned value files are not calculated or summarized.
- : The calculation of the earned value data across all projects and reports is carried out after the query has been confirmed.
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 in the following module by users with modification rights:
Caution: The following parameters are currently not used