Situations - Run Types Group
Parameters associated with run types are grouped under Run Types Situation.
| Situation | Description |
|---|---|
| Number of Runs | This situation contains parameters that have a lower and upper limit with
corresponding penalties. They are soft rules, therefore, if you use small
penalties, BlockBuster compiles results that are more than the upper limit or less
than the lower limit if doing so would result in the most cost- effective
runcut. To prevent BlockBuster Web from creating results that are more than
the upper limit or less than the lower limit (so instead fall between the two
limits), use large penalties to make the creation of runs outside the parameters
too expensive to create. If it is impossible for BlockBuster Web to comply with the Upper and Lower limits, then BlockBuster Web creates the extra runs. For example, if you have five blocks out between 06:00 and 10:00 and you specify an Upper and Lower limit of four “earlies”, since it is impossible to create only four “earlies”, the system has to produce five. |
| Number of Pieces | This situation is used to control the number of pieces a run can have. |
| On Time “Driver” | This refers to the time that an operator reports to work. it usually includes report, preparation, and related times. The minimum is the earliest on time for a run type while the maximum is the latest on time. |
| Start Time “Vehicle” |
This refers to the time when the operator starts driving the vehicle. (It excludes the time before this point.) For example, an operator reports for work at 7:50 a.m. (considered On Time) but actually starts his piece of work at 8:00 a.m. (Start Time). |
| End Time “Vehicle” | End time and Off time are applied in the same manner as On time and Start time to the end of a piece of work. End time is either Pull-in time or Relief time. The minimum is the earliest end time while the maximum is the latest end time for a run type. |
| Off Time “Driver” | This includes the time after an operator ends a piece of work for which he/she may be paid an allowance. Off time usually includes Turn-in allowances. The minimum is the earliest off time while the maximum is the latest off time for a run type. |
| Pay Time | This situation lists parameters that establish the pay time rules for a run
type. This refers to the period of time for which an operator receives payment for
his or her work. In other words, the amount of time for which an operator is paid
for the day. Note:
Commonly Used ParametersMinimum Pay Time is time prior to any Guarantee allowances. This also applies to minimum values or penalties. Some of the more commonly used
parameters associated with the Run Types situation are:
|
| Piece Break Time | The situation covers the length of the break that an operator is allowed in between pieces of a run. |
| Piece Pay Time | This situation applies to the minimum and maximum amount that an operator may be paid for a piece of work on a two-piece or three-piece run. |
| Piece Platform Time | This situation refers to the minimum/maximum driving time of a piece. |
| Platform Time | The situation refers to the minimum/ maximum amounts of time an operator is scheduled to operate a vehicle. |
| Road Relief Time | This situation controls the placement of reliefs on a piece. For example, a piece may not be cut before 8:00 a.m. Type 8:00 on the Minimum field in the appropriate column. |
| Shift Break Time | The situation refers to breaks that an operator is allowed between shifts. This is usually longer than a Piece break. You need to specify the minimum and maximum values of this time in the Parameters table. For example, an operator with a five-hour run must have a break of at least 30 minutes. |
| Shift Time | This situation applies restrictions on the amount time before a shift break
must occur. Note: The system initially considers a break as a Piece break and a
Shift break when runcutting. Based on the parameters that you set, the system
assigns a break as a Piece break or a Shift break depending on what creates the
cheapest solution. |
| Meal Break Time | This situation defines how much time of an operator’s meal break is paid and when a meal break is placed within a run. |
| Spread Time | This situation refers to the extent of time of the run. It covers the earliest time to the latest time of the run depending on the parameters you have decided to include within this duration. |
| Travel Pay Time | This situation refers to the amount of travel time paid to an operator. Note that only the maximum (the highest) value is set. |
| Travel Time | Travel Time is similar to Travel Pay Time. It limits the total amount of time that an operator is allowed to travel during a run. Note that only the maximum (the highest) value is also set for this parameter. |
| Work Time | This situation determines the minimum/maximum total period of time that an operator works on a run. |
| Cumulative Break Pay | This situation allows you to set the threshold of the payment of operator breaks based on the total value of all breaks in the run. It does not depend on how long the breaks are or when they occur. For example, based on the union contract, only 30 minutes of an operator’s total breaks should be paid. |
| Shift Layover | This situation allows you to set the minimum and maximum amount of layover in
a shift. A parameter in this situation also allows you to set the minimum amount
of layover that can be included in the cumulative calculations. The Shift Layover column on the Runs screen displays the total layover for each shift. |
| Wheel Turning Time | This situation refers to platform time without a layover. It is calculated by subtracting positive shift layover from the platform time. |
| Wheel Turning Percentage | The situation sets AM straight runs to have this percentage no greater than 0.00%. If set to 100.00%, this parameter is not activated. |
| Miscellaneous Run Types |
This situation is a collection of various parameters that do not fall under any
of the other situations. Rank is a parameter associated with run types.
|