Fault and Breakdown Workflow - End to End Guide (G4466333)

Fault and Breakdown Workflow supports retailers with symptom led diagnostics and repairs. This guide will outline the Fault and Breakdown Workflow process.

To start a new Fault and Breakdown workflow Select Diagnose a fault. To continue an existing workflow select Resume, reference Section 7 - History in this guide for more information.

1. SYMPTOM SELECTION

Vehicle symptoms are connected to test plans to help guide you to correct level of repair. Tools are available to help define the vehicle concern and view its history. You must select at least one symptom to proceed in the workflow.

Add Vehicle Symptoms

• Use the Search for Symptom field to find and add relevant symptoms
• You can type keywords or browse by category
• When added, selected symptoms appear below the search boxes
• You must select a symptom to continue to the next stage of the workflow
• For more information refer to the links below
• Refer to: DTC Timeline Viewer
  (TOPIx Cloud Diagnostics/Overview).
• Refer to: Network Topology
  (TOPIx Cloud Diagnostics/Overview).
• If a required symptom is missing, raise a TOPIx Feedback Case in Help, Support and System Status

View and Filter Diagnostic Trouble Codes (DTC)

• DTC read from the vehicle can be filtered by source
• DTC data includes, Module, DTC, Status, Description, Date, Odometer Reading, Available Test Plan (if applicable)
• If a test plan is available, it will be shown next to the DTC
• To add related symptoms, select See related symptoms, then select Add symptoms
• Select a DTC to view snapshot data and help text

Abort Applications or Workflow

• If the application or workflow becomes unresponsive select Abort.
• If a diagnostic test or application is already running a red banner will appear stating 'A vehicle application/diagnostic test is already in progress'. This applies to any application, including those launched from the Repair step, not just diagnostic tests
• For further guidance follow the video Aborting stuck applications

View Network Integrity Test (NIT)

• All data collected can be viewed, including Module communication status, Module software part numbers, Module hardware part numbers

1.1 COMPARE DATA COLLECTION

The data shown in the Network Topology and DTC Read From The Vehicle is populated from the last NIT.

• Compare Data Collects compares NIT data with historic NIT information. Refer to this video guide for historic NIT view and compare Historic Network Integrity Test (DTC) View and Compare
• Differences are highlighted in red, showing where
• Module hardware has been changed
• Module software has been changed
• DTC that are now present
• When the appropriate symptom is selected, select Complete Step.
  Refer to: Historic NIT View and Compare
  (TOPIx Cloud Diagnostics/Overview).
• The Vehicle last read (NIT) Data and time must be up to date. If the data is out of date, and or the DTC cleared before the workflow is run this will impact the user experience and prevent TOPIx from presenting the correct available test plans

2. TEST PLAN

Test plans are created to assist you to diagnose a vehicle concern, mapped to applicable vehicle lines, feature qualifiers and DTC.

• Where there is a test plan available associated to the selected symptom it is be presented in Recommended Action
• The following information is provided
  • What the test is for
  • How to complete actions such as removal of components for access
  • When possible the screen will be split into two with the workshop manual presented to aid you
  • An area to enter test results
  • Test results from Data Identifiers (DIDs) will be displayed automatically where possible
  • You will be informed of the test result

2.2 ROOT CAUSE

At the end of a test plan if a fault has been found, the test will indict a component noted in the results section of the test plan and shown in the ROOT CAUSE section of the workflow.

• If a test plan is expected but not shown, use Select a test. When added, the test will be highlighted blue to indicate it has been added to the test plan.
• If test plan is available, manual diagnosis is required. From the test plan screen there are the following tools:
  • Launch Datalogger
    Refer to: Datalogger
    (TOPIx Cloud Diagnostics/Overview).
  • Launch Wiring Diagrams
    Refer to: Electrical Wiring Diagrams - Overview
    (TOPIx User Guide/Electrical Information).
  • Investigate a DTC
    Refer to: Fault and Breakdown Workflow
    (TOPIx User Guide/Workflow).
  • To investigate DTC and launch datalogger, refer to this video guide Investigate DTC and launch Datalogger (from workflow)
• If a test plan has found a root cause and indicted the component the Root Cause section will be populated
• If the populated cause needs to be changed select Re-Select from Actions
  • If a component is greyed out, it can only be selected by a test plan
  • If an expected component is not present select Component Not Found to continue the workflow and raise a TOPIx Feedback Case. See Help, Support and System Status
• Technician Comments; you can write and document findings from diagnosis and attach the evidence. Comments are mandatory when the causal component is selected manually. The component data, and comments are sent to warranty claim portal
• Evidence; to capture evidence, select Evidence. You can capture images and videos to support claims
• When the Root Cause section is completed, select Complete Step

3. REPAIR PLAN

Components are linked to associated repairs plans. Possible Repair Plans details recommended repair plans these can consist of.

• Workshop Manual WSM Content; Removal and Installation, General Procedures.
  • Refer to: Repair Bill of Materials (RBoM)
    (TOPIx User Guide/Maintenance and Repair Information).

• Review the name of the Repair plans, duration and preview the document by selecting the eye icon
  Refer to: Network Topology
  (TOPIx Cloud Diagnostics/Overview).
• If there is a spanner icon in the Duration section this means that the repair has multiple steps; Sequential Repairs
• For example, if a component is replaced it may have to be calibrated or have a setup application run
• If a component is subject to FRED approval Add FRED icon will be available to select
  Refer to: FRED in Workflow
  (TOPIx User Guide/Workflow)..
• If there is no recommendation, select Recommend a Repair and search components for the correct repair and Service Repair Operation (SRO)
• If the SRO is not present, select 01.01.80 SRO Not Listed
• When added the repair will be shown and highlighted blue to indicate it has been added to the repair plan
• Select the repair plan that is required to repair the concern, and generate a Repair Validation Code (RVC) by selecting Generate
• The RVC code is generated and shown. There is no need make a record of the RVC, as it is captured in the summary screens
• To advance to the next select Complete Step

4. REPAIR SELECTION and REPAIR

If there was no sequential repair, the WSM will be presented or a TOPIx diagnostic application will start.

• If there was a sequential repair, a sequential list of actions will be present
• Follow the repair list by selecting Start
• The completed step is captured in the actions field, by username and date
• Select the next repair item on the list by selecting Start
• Select Complete Step when repair is completed

5. REPAIR CHECKS

Repair Checks confirms if the repair is completed through a series of questions. The DTC Read From The Vehicle checks if the impacted DTC are still present.

• The NIT Data and time must be up to date, if required select Re-Run NIT
• To progress to the next step select Complete Step
• Features such as Compare Data Collects, Network Topology and DTC Timeline, are also available to use
• Have you repaired the vehicle?; If the repair is complete and the vehicle symptoms are resolved, Select Yes then select Complete Step to progress to the next step
• Do you want to start a new workflow?; If the vehicle symptoms not resolved or have changed, select No.
• Select Complete Step to progress to the next step, or start a new workflow by selecting Yes
• Do you want to use the already captured NIT test?; consider if a component has been replaced or a module software updated, the DTCs and module statuses may have changed
• Do you want to resume with the same symptoms in place? If the vehicle symptoms have changed following a repair select Yes. If the same symptoms are present select No and select Start New Workflow
• You have completed the Diagnose a Faultworkflow

6. WORKFLOW COMPLETION

In the last section rate the session and provide comments whenever possible. Constructive feedback allows Jaguar Land Rover (JLR) to improve system and content for all system users.

• Complete the session rating including comments where possible.
• Comments are reviewed by the JLR support team, and must be constructive and include the following
  • If content or system does not meet user expectations
  • if there are improvements that could be made
  • If there was an issue - provide the What, Why, and When so that it can be investigated byJLR support team
• To finish the workflow select Return to Vehicle Park.

7. HISTORY

History is available for ongoing and completed workflows.

• History fields include the following
  • Date and Time
  • Workflow
  • Diagnose a fault for when no symptom has been selected yet
  • Symptom(s) selected
  • Odometer Reading
  • Status
  • Progression step
• There is the option to Resume workflow
• If the workflow has been completed, the RVC code will be displayed
• Select Workflow Summary to view additional information about the workflow. Details from the workflow are captured within the workflow summary, examples are
  • Root Cause Component and Condition
  • Repair Plan
  • What procedures were competed
  • RVC Code

8. DIAGNOSTIC RECORD

The diagnostic record confirms what tests were offered by the workflow, and what tests were completed.

• There is information to confirm:
  • If the test has been manually added Added manually?
  • Root cause component from a test has been used Indictment used
  • If there were no relevant tests, and the Investigate a DTC feature from the test plan was used details will be populated

Definitions