Objective
Note
Note
You can find the result in the message log in the Travel Path Evaluation. If you have activated Labor Management, you can also find it in the planned workload and in the executed workload.
EWM provides a standard BRFplus application /SCWM/TDC_SYS and function /SCWM/TDC_CALC_TIME to which you can assign your own rulesets, or create one or more rulesets in BRFplus and assign them to your own BRFplus function and application. You do this by implementing the Business Add-In (BAdI) Travel Time Calculation (/SCWM/EX_TDC_BRF_CALC_TIME). The interface of the standard function includes the following:
The total horizontal travel distance
The total vertical travel distance
Consolidated section information of horizontal movements
Section information of vertical movements
Resource type information (such as speed)
Business information (such as activity area)
When you define your own rules, you can use any or all of the above information as input.
In contrast to the total travel distance, consolidated section information lets you consider each section of the calculated travel path separately. For example, you might want to consider turns and stops in the travel path, because they limit the maximum speed of a resource. The shorter a straight segment is, the less likely it is for the resource to travel at its maximum speed.
Technically, a travel path is defined as a list of points. These points can either be nodes (N) of edges or bins (B). A pair of consecutive points defines a section of the travel path. Two consecutive sections define a turn angle for the resource. Sometimes, the turn angle is zero, which indicates that both involved sections can be consolidated into one straight section. However, if the shared point of both sections is a bin - where the resource needs to stop - the sections cannot be consolidated, even if the turn angle is zero.
The resource type RT01 has a horizontal velocity of 10 m/s. It travels along two horizontal sections:
| Section | Length |
|---|---|
| Section 1 | 100 m |
| Section 2 | 200 m |
You can model this in BRFplus as follows: You define a rule that encapsulates the travel time calculation in a loop expression over the horizontal sections. In each iteration, you can check for conditions (for example, whether the resource type is RT01) before proceeding with the calculation. You encapsulate the calculation for each section in a formula, in which the section distance is divided by the resource type velocity. You add 10 seconds flat to account for turns between sections. The resulting time for each iteration is then added to the total travel time up until the current iteration. The final total travel time is then:
1[ 100m/(10m/s) + 10s ] + [ 200m/(10m/s) + 10s ] = 20s + 30s = 50s