BDR
for Fault ReportingIf you are using fault reporting in IFS/Vehicle Information Management, some of the activities here are mandatory to perform. When registering a fault on a serial, definition of Person Category, Fault Function, Fault Code, Fault Category and Fault Action are mandatory to do. If you want to enable fault deferrals for the entered fault, the activity Grant User Access to Product Model is mandatory to perform. The other activities are optional.
Fault Code - Is used to define the type of fault. An example may be LEAK - Leakage.
Fault Action Code - Is used to tell what actions have been done when the fault was discovered. An example may be RES - Restarted.
Fault Cause - This code is used to register the reason why a serial fault occurred. An example may be CORR - Corrosion. The information is optional when registering a fault.
Fault Category - Fault categories are used to categorize serial faults when registering the fault. An example may be GEN - General Fault, another example C - Cosmetic Fault.
Person Category - Along with person identity, person categories are used when reporting faults on the serial. An example may be PIL - Pilot.
Fault Function - Valid functional breakdowns per fault code. The functional breakdown is used to tell where on the serial a fault has occurred. Depending on the setting of the object property FUNC_LEVEL_REPAIR in IFS/Application Services, the information may be mandatory when registering a fault if the parameter setting is set to require a functional breakdown. Otherwise the functional breakdown is optional when registering a fault. For more information, see Setting up Application Parameters.
Note: Before fault functions may be defined, fault code must be defined (explained above in this document). In addition the product, model and function structure must have been defined in IFS/PDM Configuration. For more information, see process model Describe Product Functions.
Note: If you have a fault code that is valid for the whole function structure (or a branch of the function structure), register the fault code for the top most function. A menu option is available to automatically spread the fault code to all the functions on the lower levels in the function structure.
Fault Mode - Is a tool to standardize functional decomposing recorded upon fault registration. A fault mode can be categorized in three types: Symptoms, Actual Discovered or Both. Symptoms can be used for fault registration, while Actual Discovered are used when reporting a correction of a fault. The fault modes are optional.
Note: Before fault modes may be defined, the Fault Functions must be defined (explained above in this document).
Define User Authorization for Fault Deferrals - Is used to define which users are authorized for enabling fault deferrals, and on which product models. A user may enable fault deferral for a serial fault if the user is granted access to the product model the fault is reported on. This step is mandatory only if you plan to use fault deferrals.