It is common for Field Service organizations to require the tech capture a problem, cause and Repair code on a work order. These codes are then used to rank solutions from highest to lowest probable fix for any give problem. Cause is often then used to determine chargeability or to make recommendations to stop problems form occurring. for example a power surge caused a component to fail, the recommendation would be to add a power conditioner. As problem, cause and repair codes are captured a counter would be incremented to indicate how many time this repair code fixed the problem. Then on the WO they tech is presented with the repair codes and the ranking for any given problem.
Comments
Doing a Fit Gap for a Field Service solution, and this is a gap for D365 Field Service
Category: Field Service
Need to be able to have multiple Problems/Symptoms, Causes, Repairs/Actions for a single work order
Category: Field Service
Jason jacoh@microsoft.com (administrator) on 8/20/2021 12:08:55 AM
In wave 1, 2021 we introduced WO Resolutions. Combined with the existing Incident Type feature, we think this meets the need for this concept. A single work order can have many WO Resolutions which can be related to different Work Order Incidents and Customer Assets. If we're still missing some key capabilities in this area, please reach out and/or raise a new idea to improve the feature.
Thanks, again, David.
- Jason Cohen
PM, Microsoft