Configuring labor hour registration in the PMFS solution
Select a method
In the PMFS solution you can choose between two methods for registering labor hours via the app:
• Manual registration, based on the number of hours filled in by the app user on the mobile device.
• Automatic registration of running labor hours, based on the
start-date times and end-date times of
Work,
Wait and
Travel actions, registered during the various stages of a work assignment. Also see
Action and reason configuration (MM and PMFS) for more information on configuring actions (and reasons).
| You can only select one labor hour registration method for a sub web definition. Switching between registration methods is possible, but this change will obviously have implications for the app users, of which they should be made aware. |
You can select the Type of labor hour registration per sub web definition, on the Additional settings tab. The following example shows the setting on a sub web definition for Orders (based on user-defined business object Orders).
Labor hour registration based on hours
If you select the hour-based registration method, app users must enter their labor hours manually. To support this, additional configuration is needed on the Labor hours details page of the sub web definition. You must set the action Add labor hours (hour-based) to Is visible = Yes. This will enable the users to enter their working hours and minutes. The maximum number of hours they can add is 24.
For editing purposes, you can enable the action Edit labor hours (hour-based), by going to the Labor hours details block and setting the field Is visible to Yes. This allows app users to edit their entered labor hours until the work assignment is finalized. Please note: the Action date-time field of the work assignment will become non-editable.
Labor hour registration based on date-time (automatic running labor hours)
The PMFS solution can automatically track labor hours on the app, based on date-time data registered during the various stages of the work assignment. Labor hour records are automatically created upon status transitions from and to Work, Wait and Travel.
| Upon selecting the Pause action, worked labor hours will automatically be finalized up to that point. This behavior only applies to 'action-reason' combinations where the Finalize time registration field is set to Yes, in the Action-reason TSI. For each Pause action–reason combination, you can configure whether it triggers a finalized time registration in the back office. See Action and reason configuration (MM and PMFS) for more information on action and reason configuration. |
For this type of registration, go to the Labor hours details page of the sub web definition and set the action Add labor hours (date-time based) to Is visible = Yes.
For editing purposes, you can also enable the action Edit labor hours (date-time based), by going to the Labor hours details block and setting the field Is visible to Yes.
| If users edit their running labor hours to an earlier date-time, the work assignment's Actual start date-time field in the back-office is updated to that earlier date. |
Labor hours that are completed on the app are sent to the back-office as a communication log if the engineer is online. Incomplete (running) labor hours are not sent to the back-office.
| The automatic registration of labor hours only works if an Edit page is configured for the destination status (To) in a status transition. For example: if you want automatic labor hour registration for an engineer's travel time, you have to make sure that the Edit Travel page is configured in the Edit definition field, for each status transition to the Travel status. You can check if an Edit page is configured for the relevant destination statuses on the Summary page of the web definition. |