In FieldEx, faults and resolutions are the building blocks of job reporting. Technicians use them to describe what went wrong and how they fixed it. By mapping these to specific systems, you ensure consistency in field inputs, simplify reporting, and improve planning for future issues.
Create a System
Path: Settings > Modules > Job Orders > Fault and Resolutions
System represents a functional area of an asset such as “Engine,” “Electrical,” or “Hydraulics.” When creating a job, this system categorises the type of issue being reported.
Go to the System section
Click New
Enter a name such as Cooling System or Hydraulics
Click Save
Use Case: A planner logging a repair job for a forklift selects Hydraulics to limit the fault and resolution list to only relevant issues like leaks or pressure loss. |
Create a Fault
A Fault defines the specific issue discovered on an asset. Technicians will select one or more faults when documenting a job.
Go to the Fault section
Click New
Enter a descriptive fault name (e.g., “Hydraulic Leak – Main Arm”)
Click Save
Why This Matters: Faults give your team clarity on what’s going wrong across asset types. Standardized labels prevent duplication like “Oil Leak” vs. “Leaking Oil.” |
Create a Resolution
A Resolution is how the technician resolved the fault. It should describe the action taken, not just the outcome.
Go to the Resolution section
Click New
Enter an action like “Replace damaged hydraulic hose”
Click Save
Use Case: For a fault like “Overheating Engine,” possible resolutions might include “Refilled coolant” or “Replaced radiator fan.”
Tip: Avoid vague labels like “Fixed.” Resolutions should be clear, like “Tightened fitting” or “Updated firmware.” |
Mapping Faults and Resolutions to Systems
After creating Systems, Faults, and Resolutions, map them together. This ensures that when a user selects a system in a job, only relevant faults and resolutions will appear.
1. Map Faults to a System
Path: Fault and Resolutions > Map System to Fault
Select a system such as Hydraulics
Move the relevant faults into the “Allowed” column (e.g., “Hydraulic Leak – Main Arm”)
Click Save
Why This Matters: Keeps dropdowns short and focused for the technician. A user working on an electrical issue won’t see irrelevant hydraulic faults. |
2. Map Resolutions to a System
Path: Fault and Resolutions > Map System to Resolution
Select the same system (e.g., Hydraulics)
Move valid resolutions into the Allowed column (e.g., “Replace hose”, “Refill fluid”)
Click Save
Benefit: Ensures that only valid fix options appear for that system, helping guide technicians to proper actions. |
3. (Optional) Link Specific Resolutions to Specific Faults
This adds another layer of precision. Resolutions shown will depend on the fault selected.
Edit the desired fault from the Fault section
Scroll to Linked Resolutions
Select only the valid fixes for that specific fault
Example: Fault = “Pump Pressure Low”
Use Case: Helps new technicians select the right fix even if they aren’t deeply experienced with the equipment. |
Best Practices
Group faults and resolutions under practical systems like Electrical, Mechanical, Safety
Keep fault/resolution wording consistent. E.g., avoid "Leak" vs. "Leaking" duplicates
Use the optional fault-to-resolution linking to increase precision