DT466 Resource Assignment

DI001410 Planned effort

Planned effort of the resource assignment (in resource units). For the revenue and cost resources, the respective data field is named Planned costs.

Details on editing/calculation

• Resource assignment: * Planned effort = Remaining effort as long as no Actual start is set. Once an Actual start has been set, Planned effort will no longer be changed by the calculation of the project schedule. However, it can still be adjusted manually.

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

• Schedule (project/proposal)

DI001423 Remaining effort

Remaining effort of the resource assignment (in resource units). For cost and revenue resources, this field is called Remaining costs.

Details on editing/calculation

• If there is no Actual start of the resource assignment,
  • the planned effort is entered manually in the Remaining effort field ( Exception: Resource assignments with MAN load profile, see the entry below).
• If there is an Actual start but no actual end of the resource assignment,
  • the Remaining effort of the resource assignment is determined in the calculation of the project schedule:
    • Remaining effort of the resource assignment - Change Actual effort of the resource assignment
  • the calculated value, however, can be adjusted manually if necessary (e.g. if the enhanced effort is determined from the forecasts). Manual input is not overwritten in the course of the next calculation of the project schedule.
• If there is no Actual end of the resource assignment,
  • the Remaining effort of the resource assignment = 0 (if there is remaining effort when the actual end is set, it is set to zero).

Reduction of the remaining effort by working time recording.

• If the working time reporting results in the creation of a new resource assignment, the Remaining effort for existing resource assignments is calculated as follows:
  • If the new resource is a child resource of one of the existing resources, the remaining effort of the respective parent resource is reduced.
  • If the new resource is no child resource of any of the existing resources, the effort of the already assigned resources is not reduced, but the additional effort is added to the task.

Application example:

• Service orders are scheduled with adherence to department.
• Employees of the department record hours worked, As a result, the planned Remaining effort of the department resource and thus the Remaining effort of the task are reduced by the recorded actual effort.
• If employees from other departments post to the task in an unplanned manner, this is treated as unplanned additional effort for the task, which will not reduce the remaining effort of the task but will increase the total effort by the additional effort.

For the MAN load profile, the following applies:

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

• Schedule (project/proposal)
• Outline Plan
• Task in the Resources area

DI001416 Actual effort

Actual effort of the resource assignment (in the unit of the resource). It is a summarized value (is set when the project schedule is calculated, no manual input possible). For the revenue and cost resources, the respective data field is named Actual costs.

Calculation/summarization structure

• Resource assignment: Actual effort = Sum of the Actual load of all load records of the assigned resource.
  • Load: * Manual input in the Actual load field.

Details

• An Actual effort of the resource assignment sets the Actual start of the resource assignment to the date for which the reporting was made, in case there is no earlier work recording date for this task. This means that there is never an actual effort without an actual start date.
• The date of the last time recording is stored in the Time recording date field.

Exception:

• If desired, the Actual effort field can be customized as an input field in which the actual effort is entered manually.
  • This actual effort (DT466) is automatically allocated to the load records (DT472) during each calculation (from earliest start of the resource assignment to the work reporting date of the resource assignment according to the load profile) (top-down), as long as no loads are entered manually.
  • As soon as at least one load ID (DT472) has been created manually, the actual effort (DT466) is no longer treated "manually" and is automatically overwritten with the sum of the load records during each scheduling (bottom up).
• PLANTA, however, recommends that you do not use this procedure!

DI000817 Total effort

Total effort of the resource assignment (in resource units). It is a calculated value (manual input not possible).

Calculation via value range

• Actual effort of the resource assignment + Remaining effort of the resource assignment

DI000096 Actual costs

Actual costs of the resource assignment. In the calculation of the schedule, the value is determined (summarized) from the values of the subordinate areas (levels). Manual input is not possible. See calulation/summarization structure

Calculation/summarization structure

• Resource assignment: * Actual costs = Sum of the Actual costs of all load records of the assigned resource.
  • Load: * Actual costs: On this level, the actual cost calculation takes place.

DI000097 Planned costs

Planned costs of the resource assignment. In the calculation of the schedule, the value is determined (summarized) from the values of the subordinate areas (levels). Manual input is not possible. See calulation/summarization structure

Calculation/summarization structure

• Resource assignment: * Planned costs = Sum of the Planned costs of all load records of the assigned resource.
  • Load: * Planned costs: On this level, the actual cost calculation takes place.

DI000098 Rem. costs

Remaining costs of the resource assignment. In the calculation of the schedule, the value is determined (summarized) from the values of the subordinate areas (levels). Manual input is not possible. See calulation/summarization structure

Calculation/summarization structure

• Resource assignment: * Remaining costs = Sum of the Remaining costs of all load records of the assigned resource.
  • Load: * Remaining costs: On this level, the actual cost calculation takes place.

DI000814 Total costs

Total costs of the resource assignment. It is a calculated value (manual input not possible).

Calculation

• Actual costs of the resource assignment + Remaining costs of the resource assignment

DI000815 Deviation total planned costs

Deviation of total costs of the resource assignment from planned costs of the resource assignment

Calculation via value range

• Total costs of the resource assignment - Planned costs of the resource assignment

DI000816 % deviation total planned costs

Percentage deviation of the total costs of the resource assignment from the planned costs of the resource assignment

Calculation via value range

• (Total costs of the resource assignment - Planned costs of the resource assignment) / Planned costs of the resource assignment * 100

DI000828 Unit

This field serves to output the basic unit of the resource.

DI000921 Min. load/day

Minimum load of the resource assignment per day

Details

• The respective field is preset with the default value (Default min. load) from the Resource Data Sheet.
• If the resource is being scheduled with the CAP load profile, the minimum load per day can be entered here.
• In case of scheduling with adherence to float or capacity, only periods are loaded for which the remaining load value is higher or equal to the Min. load/day value.
• If no Min. load/day has been specified, the periods with a low remaining load are planned as well. In this case the task will be heavily fragmented.
• The field value is ignored when scheduling with other load profiles.

Examples

• Remaining effort of the resource assignment = 100, Min. load/day = 1
• Only periods which have remaining loads greater than 1 are loaded.

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

• Outline Plan
  • The respective data field is hidden by default and can be displayed by the user if necessary.
• Task in the Resources area
  • The respective data field is hidden by default and can be displayed by the user if necessary.

DI001390 Project ID

ID of the project

DI001391 Task ID

ID of the task

DI001393 Cost type

Code (ID) of the resource assignment

Details

• This field is automatically preset with the Default value of the resource (from the Resource Data Sheet).
• In the calculation of the project schedule, the cost type of the resource assignment is applied to the load records (transmitted). The Cost type of the load records is then essential for the summarization of the costs to the cost type group and the display in cost and budget modules, e.g. in the Budget module.

Notes

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

• Schedule (project/proposal)
• Task in the Resources area
  • The respective data field is hidden by default and can be displayed by the user if necessary.

See also: Create and assign cost types

DI004338 Requested start

Required start date of the resource assignment. Once requested dates are set on the resource assignment, the respective resources are automatically loaded with adherence to schedule. This takes place regardless of the project planning type of the project or of the load profile of the resource assignment. There is no load adjustment for overload. By setting the requested dates on the resource assignment it becomes possible to have resources working on a task at different defined points in time.

Rule

• Resource requested dates must always be within the requested or calculated dates of the task.
• Requested dates set on task level:
  • TAR Requested start TA Requested start or TA Calc. start
  • TAR Requested end TA Requested end or TA Calc. end
• Requested dates not set on task level:
  • TAR Requested start TA Calc. start
  • TAR Requested end TA Calc. end
• Requested dates not set at task level and resource requested dates outside the calculated TA dates
  • ignored

Behavior of the scheduling

• The treatment of the requested dates on the resource assignment follows the top down planning of the scheduling.
  • Scheduling first determines the calculated start and end dates of the task.
    • As far as the TAR requested dates lie within the TA Calc. start and TA Calc. end, they are planned on the TAR requested date with adherence to schedule and are possibly overloaded with each planning type.
    • As far as the TAR requested dates lie outside the TA Calc. start and TA Calc. end, they are loaded with respect to TA Calc. start and TA Calc. end. The TAR requested dates of the resource are ignored.
  • If there is only one TAR Requested start and no Requested end, the resource is not scheduled earlier than the TAR Requested start, provided that the TAR Requested start lies within the calculated start and end dates of the task.
  • If there is only one TAR Requested end and no Requested end, the resource is not scheduled earlier than the TAR Requested start, provided that the TAR Requested end lies within the calculated start and end dates of the task.
• This applies to all TAR requested dates, regardless of the planning type for the project (adherence to schedule, buffer, capacity).

Notes

• Links may cause tasks to be shifted and fall outside the TAR requested dates. In this case, they are ignored. If you want to employ the resource on the respective days only, you have the following options:
  • Set the Fix parameter for the task and enter the TAR requested dates within the fixed period.
  • Use the MAN load profile for this resource.

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

• Schedule (project/proposal)
• Outline Plan

DI004349 Requested end

Required end date of the resource assignment

For description and details, see Requested start

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

• Schedule (project/proposal)
• Outline Plan

DI001441 Calc. start

Calculated start date of the resource assignment. It is automatically determined in the calculation of the project schedule.

DI001442 Calc. end

Calculated end of the date resource assignment. It is automatically determined in the calculation of the project schedule.

DI001420 Actual start

Actual start of the resource assignment. It is determined in the calculation of the project schedule but can be entered/edited manually as well.

Calculation

• Date of earliest posting (i.e. the first load record with recorded Actual load).
• A manual input will be overwritten if it is later than this date.

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

• Schedule (project/proposal)
• Outline Plan
  • The respective data field is hidden by default and can be displayed by the user if necessary.

DI001422 Actual end

Actual end date of the resource assignment. It is determined in the calculation of the project schedule (applied to the task in case there is no own date entered on the resource assignment) but can also be entered/edited manually.

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

• Schedule (project/proposal)
• Outline Plan
  • The respective data field is hidden by default and can be displayed by the user if necessary.

DI001452 Load profile

The load profile of the resource assignment controls how the effort (in cost resources of the costs) of the respective resource is spread across the duration of the task .

• When creating the resource assignment, the Default load profile of the resource (from the Resource Data Sheet module) is applied, which can be changed from the resource assignment if necessary.
• If no load profile is entered, the load is distributed linearly.
• When the effort is distributed from a source resource to a new resource, the value of the Load profile parameter which is stored on the resource assignment ( Achtung: nicht der Wert der Default-Belastungskurve) is copied from the source resource to the new resource.
  • If no load is saved on the resource assignment of the source resource, the resources own default load profile is used for the new resource.

Details

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

• Schedule (project/proposal)
• Outline Plan
• Task in the Resources area

See also: Detailed informationen on Load Profiles

DI001464 Effort used in %

Effort used of the resource assignment in percent. The value is automatically determined in the calculation of the project schedule.

Calculation

• Actual effort of the resource assignment / (Actual effort of the resource assignment + Remaining effort of the resource assignment) * 100

DI001467 Max. load/day

Required maximum load of the resource assignment per day

Details

• This field is automatically preset with the value from Default max. load of the resource from the Resource Data Sheet.

The value entered here has an effect on the following load profile:

• CAP
  • The Max. load/day value is a threshold for capacity scheduling which is exceeded if necessary, e.g. if duration or requested dates are predefined for the respective task.
  • If no Max. load/day has been set, the entire available capacity left is available for planning.
  • The mere exceeding of the Max. load/day limit does not yet represent an overload, as overload is only determined on the basis of the available capacity of a resource. The resource only has overload when the availability is overrun.
  • The calculation of the schedule works with the Max. load/day parameter as follows (provided that there are no further restrictions on the resource assignment, like e.g. requested dates):
    • The required duration of the resource assignment used in scheduling is calculated from Remaining effort / Max. load/day.
    • This duration is the starting value for capacity adjustment.
      • Example: Remaining effort of the resource assignment = 100, Max. load/day = 5 The duration of the resource assignment is calculated as follows: 100/5 = 20 days.
      • If several resources are assigned to the task, the task duration is determined as the maximum duration of all resource assignments.
• BLD
  • If the Max. load/day field is filled in a resource assignment with BLD, the Remaining effort is automatically calculated as follows:
    • Remaining duration * Max. load/day.
    • During calculation of the project schedule, manual changes made to the Remaining effort are overwritten by calculated values. If you do not want this, you have to clear the Max. load / day field.
• For all other load profiles, an entry in this field has no effect.

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

• Schedule (project/proposal)
• Outline Plan
• Task in the Resources area

DI002090 Bar: actual dates

Bar for the visualization of the interval between the actual dates (Actual start and Actual end) of the resource assignment

DI002091 Bar: actual start work reporting date

Bar for the visualization of the interval between the Actual start date and the latest Reporting date of the resource assignment

DI023391 TDI: 1

Technical data item: Display Y/N

DI002093 Bar: calculated dates

Bar for the visualization of the interval between the calculated dates (Calc. start, and Calc. end) of the resource assignment

DI002347 Number of load records

Number of load records of the resource assignment

DI002501 Project name

Name of the project to which the resource assignment belongs

DI002502 Task name

Name of the task to which the resource assignment belongs

DI002531 Bar: latest dates

Bar for the visualization of the interval between the latest start and the latest end of the task to which the resource assignment belongs

DI002503 Task latest start

Latest determined start date of the task to which the resource assignment belongs, as determined in the calculation of the project schedule.

Details

• Internal calculation field

DI002504 Task latest end

Latest end date of the task to which the resource assignment belongs, as determined in the calculation of the project schedule.

Details

• Internal calculation field

DI002774 Task total float

Float of the task to which the resource assignment belongs. The value is copied from the task.

DI003018 Overload

On resource assignment level: Total overload of the selected resource in the selected task (sum of the Overload values from the respective load records (can be looked at in the With loads variant in the Schedule module))

On task level: Total overload of all resource assignments for the selected task (sum of the Overload values of all resource assignments of the task)

Notes

DI003295 Main project

ID of the main project

DI003296 Main project name

Name of the main project

DI004321 Bar: requested dates

Bar for the visualization of the time interval between the requested dates (Task requested start and Task requested end) of the task

DI004322 Task requested start

Requested start date of the task

DI004323 Task requested end

Requested end date of the task

DI006446 Duration

Duration of the resource assignment

DI006530 Forecast

Forecast value on the remaining effort of the resource assignment

DI006889 Remaining effort

Remaining effort of the resource assignment

DI006890 Actual effort

Actual effort of the resource assignment

DI007633 Project code

Code of the project in which the resource is planned. See also Code in DT461 Project.

DI009063 Resource cost center

Code (ID) of the cost center of the resource assignment

Details

• In resource assignment, this field is automatically preset with the Default cost center value of the resource from the Resource Data Sheet.
• In the calculation of the project schedule, the cost center of the resource assignment is applied to the load records. The cost center of the load records is applicable to the summarization and display of costs by cost center in the evaluations.

Notes

• The cost center can be changed both as a default value (Default cost center) and on both levels of a project (cost type of the resource assignment and cost type of the load) at any time. However, the impact of the changes must be considered.
  • If the cost center of the resource assignment (DT466) is changed, it is applied to all new load records (DT472) of the resource assignment in the calculation of the project schedule. In order for the cost type to be applied to the existing load records as well, the schedule of the project must first be unloaded and subsequently be recalculated.
    • Exempt therefrom are actual load records and manually created load records (i.e. those with MAN load profile). They are neither changed during unloading nor during calculation of the project schedule and must be adjusted manually if necessary.
  • If the default cost center of the resource is changed (DT467), the new value is used for all resource assignments (DT466) that are created afterwards. The cost center of existing resource assignments, however, is not changed automatically, but equates to the default cost type applicable at the time of insertion of the resource assignment. It must be changed manually if required.

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

• Schedule (project/proposal)

Attention

• The Resource Cost Center field cannot be displayed in the Schedule module by default. In case manual changes are required here, the field must be made displayable.

See also: Create and edit cost centers

DI023356 Bar: calculated dates (code)

Bar for the visualization of the interval between the calculated dates (Calc. start, and Calc. end) of the resource assignment. The color of the bar is determined by the code of the respective project.

DI023422 Bar: calculated dates (code dominance)

Bar for the visualization of the interval between the calculated dates (Calc. start, and Calc. end) of the resource assignment. The color of the bar is determined by the code of the respective project.

DI041371 Project

Functional ID of the project

DI041558 Date status

Date status (today, future, and delayed) of the task of the resource assignment in relation to the calculated dates of the resource assignment

DI041607 Task

Functional ID of the task

DI056870 Probably completed on

DI056871 Completed

Note

• In the Schedule module, the respective field is hidden by default but can be displayed if necessary.

DI057814 Task locked

Parameter which shows whether the task to which the resource is assigned is locked for work reporting. The value is copied to the respective task by the parameter of the same name.

DI009502 Project locked

Parameter which shows whether the project in which the resource is planned is locked for working time recording. The value is adopted by the Locked parameter on the project.

DI057684 Main project cost center

Cost center ID of the main project

DI057685 Main project cost center name

Cost center name of the main project

DI057686 Resource cost center name

Cost center name of the resource

DI034593 Summary task

Parameter that defines a task as a summary task. The value is copied via exit from the data item of the same name in DT463 Task.

Information

• Tasks can be structured hierarchically.
• As a result, all parent tasks are summary tasks.
• Information on parent tasks, such as duration and dates, is automatically determined from the child tasks.

See also: Work Breakdown Structure

DI034537 Actual duration

Actual duration of the work of the resource assignment

DI058999 Parent task name

Name of the parent task