Action and reason configuration (MM and PMFS)
MM & PMFS configuration (in Accelerator: > ) is a TSI that is used to configure actions and reasons that can be displayed on the layout of any relevant communication log. In addition, you can link specific PMFS actions to reasons which can subsequently be displayed in the communication logs of work orders and PPM orders and displayed on the PMFS app. Finally, your action and reason configuration can support the SLAs used by the back-office and enforce feedback from engineers on maintenance checklist items. The following selection steps are available for this purpose on the Actions selection level:
• Actions: enables the creation of configurable actions. These actions can be displayed in any type of communication log in Planon.
• PMFS actions: displays pre-configured, read-only actions, only to be used in Planon Mobile Field Services (AppSuite and Planon Live app). Some pre-configured PMFS actions can be linked to reasons, which are also configurable. The following table includes the available PMFS actions:
Code | Description | Additional info |
|---|---|---|
1 | EHS accepted | |
2 | EHS declined | |
3 | Start work | |
4 | End work | |
5 | Start travel | |
6 | End travel | |
7 | Wait | |
8 | Discontinue | |
9 | Pause | |
10 | Resume work | |
11 | Bar code scan | |
12 | Temporary fix | |
13 | Team order decline | |
14 | Asset updated | |
15 | Refuse | |
16 | Reassign | |
17 | Unknown asset | |
18 | Debug snapshot | Planon AppSuite only |
19 | Time registration | Planon AppSuite only |
20 | Accept | PMFS Live app only |
21 | Apply temporary fix and continue | PMFS Live app only |
22 | Sign off | PMFS Live app only |
23 | Engineer's sign -off | PMFS Live app only |
24 | Tradesperson's comment | PMFS Live app only |
25 | Confirm asset | PMFS Live app only |
PMFS actions and any linked reasons are displayed on PMFS mobile devices, where they can be selected by engineers. Back-office personnel will see the PMFS actions and reasons reflected in the communication logs ensuing from PMFS orders.
 | For information on PMFS system settings, see AppSuite - Configuration Guide > Non-property set dependent PMFS order settings. |
See the following examples, to get an idea of the type of information that is conveyed to the back-office:
The following communication logs are created on the order for the PMFS actions:
• EHS declined - created if the field engineer declines the EHS check. The communication log includes: the name of the PMFS action, the engineer's name, the start date-time entered by the engineer, the reason for declining the EHS check, the engineer's comment.
• Start travel - created if the field engineer selects the Start travel screen. The communication log includes: the name and code of the PMFS action, the engineer's name, the start date-time entered by the engineer.
• Bar code scan - created when the field engineer scans an asset bar code. This communication log includes: the date-time the engineer scanned the bar code, the name of the PMFS action and the engineer's name. The Comment field includes the scanned asset code.
• Refuse - create if the Refuse button is tapped by a signatory on the app. In order to meet any SLAs, the order is still moved to Technically completed, even though the customer is not (entirely) satisfied.
Optional: if your back-office requires a status transition to reflect this Refuse action, you must first create and configure a corresponding 'Refuse' status in Field definer. The status transition must from go from Technically completed to [Refused]. Next, you can also link a Refuse 'action-reason' pair to this status transition.