Agile Diagnostics

Published:  17 September, 2017

Barnaby Donohew examines how the aftermarket can learn from the tech sector to improve diagnostic outcome

Giants such as Apple, PayPal and Google have driven a tech revolution that has impacted all our lives. They have successfully solved hugely complex problems to deliver products and services that have changed the world. Yet, still, they continue to adapt to satisfy shifting consumer demand and out-manoeuvre their competition.


Many of these players have now turned their sights on revolutionising the automotive industry. Rather than running for cover, we should learn from them and improve our own practices in anticipation of the impending technological onslaught; after all, our industry, and diagnostics in particular, is dominated by tech.


Of the tech sector’s many contributions to the world, I believe it is their business and working behaviours that we must adopt; specifically, their agility. In this context, agility is what it implies. It is the ability to be flexible, nimble and responsive to your customers’ needs and in the manner in which you provide solutions to those needs.


In fact, the word, agile, was originally appropriated by software developers to represent a set of principles guiding their work. It has since grown to include a culture and set of working practices that are being incorporated within many industries.


A problem shared
Has the tech sector always been agile? No. During the 1990s, as their complexity accelerated, software projects became increasingly risky undertakings; they frequently failed to launch and meet customer expectations, budgets, or timeframes. At the heart of the problem was uncertainty; their final forms could not be predicted up front, After all, not every problem or solution can be foreseen. The fact that customers were disengaged from the process only made it worse; they were frequently unaware of the impending failure of the work they themselves had commissioned.
In 2001, after realising the need for change, a group of software engineers came together to define an approach that would mitigate against the influence of uncertainty; they devised the ‘Agile Principles.’ You can see these here: agilemanifesto.org/ principles.html.


Their underlying philosophy is that developers should expect, embrace and manage change during the course of a project, be they changes in customer requirements, the nature of the problem, the development team, the business or those arising from other external forces. This software development problem should seem very familiar to any of us with diagnostic experience.
Can we predict the root cause fault at the beginning of a case? No. Do we know in advance all the tests we will conduct to determine a fault? No. Are we fully engaged with our customers throughout the diagnostic processes? It’s unlikely, even though we should expect our customer’s requirements to change during a diagnostic case.
This clear corollary between the worlds of software development and diagnostics has motivated me to adapt the agile principles to see how they might apply to us. I’ll introduce the adapted principles here but, be aware, this overview barely scratches the surface of how agile methodologies might help us.


Principles of Agile diagnostics
1. Our highest priority is to satisfy the customer through early and frequent delivery of diagnostic outcomes. We must continuously update our customers with our diagnostic observations (e.g. test results) and report which systems and components we have discriminated against. We should attach particular significance to the latter, as we can be more engaged with our customers if we discuss tangible concepts, such as physical parts.


2. Welcome changing requirements, even late in a case. Our customers do not have a single requirement equating to ‘fix my vehicle at any cost.’ Their requirements will be formed on the basis of a cost-benefit analysis, pitting the potential costs of diagnostics and repairs against the value of that vehicle. This value, influenced by the age, condition, and the perceived past, current and future utility and reliability, will change as the case progresses. It is also possible that a customer’s personal situation might change during a diagnostic case, e.g., they may have a change of economic circumstances. Therefore, we must expect, embrace and properly manage these changes.

3. Business people and workshop teams must work together throughout cases. Clear communication is essential if high first time fix rates and customer satisfaction levels are to be built and maintained. This requires all members of the business (whether workshop managers, or customer service representatives) to work together to ensure that diagnostic cases are well managed and their outcomes clearly delivered to customers.

4. Build diagnostic case-work around motivated individuals. Give them the environment and support they need, and trust them to get the job done. Motivated individuals will be determined to solve a diagnostic case and will be prepared to undertake the personal investment necessary to iterate themselves toward more efficient and effective practices. Supported and trusted individuals will be more motivated. It’s a win-win situation to uphold this principle.

5. The most efficient and effective method of conveying information to and within workshop teams is face-to-face conversation
Forget emails, messages (whether of the instant or post-it variety) and phone calls. Establish and maintain regular face to face contact across your business and with the customers.

6. Definitive diagnostic outcomes are the primary measure of progress. A diagnostic observation acts to increase or decrease the remaining ‘search-space’: i.e. it increases or decreases the set of components (candidates) that might contain the root cause fault; therefore, this diagnostic outcome, the search-space reduction, can be the only measure of progress within diagnostics.
Only a suitably designed diagnostics system could define a search-space and track its changes – at present, no such system exists.

7. The process should be sustainable. Excessive pressure and demands on a diagnostician’s physical and intellectual state are not sustainable. Diagnostics requires learning, action and reflection and diagnosticians should be afforded the appropriate time for each. Pressure to reduce any of these is unsustainable for both the diagnostician and the business.

8. Continuous attention to technical excellence and informed and accurate decision-making enhances agility. he acquisition and application of knowledge it is at the heart of agility. It is also central to diagnostics. In either case it’s a principle that we should always champion.

9. Simplicity – the art of maximising the amount of work not done – is essential. Is there a quicker or simpler, diagnostic test, which will provide an equivalent diagnostic outcome? If so, find it and use it.

10. The best diagnostic analyses emerge from self-organising teams. Structured teamwork does not exist within automotive workshops. It should. The development of a diagnostic team would increase the potential range of expertise,
maximising the likelihood of correct diagnostic decision-making. Practices such as paired diagnostics (two diagnosticians working simultaneously on the same case) and swarm diagnostics (the gathering of the whole diagnostic team to work on a case) should be strongly encouraged.


All teamwork has the benefits that it facilitates the transfer of knowledge amongst diagnosticians, increasing their effectiveness and reducing business risks, such as those arising from diagnostic roadblocks (difficult cases) and the loss of knowledge when a key staff member leaves. Furthermore, the resulting teamwork and learning promotes a happy and satisfied, and therefore more productive group of diagnosticians.


Members of a team should be able to select their own cases depending on their expertise and problem preferences (e.g. classed according to the initial symptoms) as their motivation, efficiency and effectiveness will remain high.

11. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly
Progress through an agile diagnostic case should be broken down in to a series of incremental steps, with each taking the form a repetitive three-phase learn-act-reflect cycle.


Each cycle should deliver a diagnostic outcome of value to the customer. Within the learning phase, the business should determine the customer’s requirements and the diagnosticians should increase their understanding of the problem before them and decide on their next actions. At the end of the cycle the business and diagnosticians should reflect on any new knowledge and what went well or what could have gone better. The reflective output should be fed back in to the learning phase of the next cycle, and so on.


Behaviour
The above principles may seem a little wishy-washy and it still may not be clear why they should be adopted. However, consider this: If you have made significant investments in equipment and training and found that your first time fix rates and customer satisfaction levels have not improved, then you will understand that there must be one remaining component in which you must invest; your behaviours. I strongly suggest you learn from the world-domination of tech sector businesses and make them agile behaviours.


Automotive Analytics Limited is producing a white-paper entitled ‘Agile diagnostics’, which fully explores diagnostic agility and its potential to revolutionise diagnostics. You will be able to download it for free by signing up at: http://automotiveanalytics.net/
agile-diagnostics


For more tech innovations make sure to follow us on facebook.com/aftermarketmagazine

Related Articles

  • Would you like to diagnose more vehicles first time? 

    As we reach March, 2019 is well and truly underway. In fact by the time you read this one third of the year will have whizzed by never to be seen again. Now, I’m not one for New Year’s Resolutions (they’re so last year), but I am the type of chap that likes constant progress when it comes to developing a technician’s career.
        
    There’s so much to be said for small steps taken everyday that on first look appear don’t appear to make a difference, but when gazed back upon over a 12 month period have a staggering affect on your capability to diagnose a vehicle first time, in a timely manner.

    Pitter-patter of tiny feet
    Small steps are all well and good but where do you start? After all, you don’t know what you don’t know, and you’d like to start your journey to diagnostic success off on the right foot. In this instance I’d start with the end in mind and reverse engineer the outcome you desire. It’s a logical process that works, and can be replicated time and time again in your diagnostic routine.
        
    Your ‘end in mind’ in this instance is a vehicle where the fault no longer exists, that won’t appear back across the threshold of your workshop anytime soon. But how do you guarantee that?

    One test to rule them all
    I love nothing more than when the delegates working through our training programs have a technical epiphany. This happens at many points on their path of learning, but none more than with bypass testing.
        
    Bypass testing is step nine in Johnny’s diagnostic circle of love (our 15 step routine), and often the key element in the first time fix. The good news for you is that it doesn’t require mythical creatures to forge their magical powers into an object that only one technician can possess. It’s something that every tech can learn, and become a diagnostic wizard.

    What is bypass testing?
    Quite simply it’s fixing the vehicle before you fix the vehicle. Let me explain.
        
    Wouldn’t it be great if you suspected that a Mass Air Flow sensor was at fault and you could prove that you were right before you fitted a new part, or spoke to the owner of the vehicle. If you could do that then the positive effect it would have on you and the business you work for would blow you away.
        
    Picture this: Your customer has reported that the vehicle is low on power. You’ve diligently questioned them, experienced the problem with them on a road test, and the bought the vehicle into the workshop.
        
    You’ve pulled codes and found none present, followed by taking a look through serial data to hunt for diagnostic clues. It doesn’t take you long to identify that the MAF sensor frequency looks a little low at 1.5 Khz and your fuel trim data is incorrect and making a positive corrections. You’ve seen a bunch of these before and know that 1.85 Khz is a suitable value for this vehicle.
        
    You’re keen to prove that the serial data is leading you in the right direction so confirm the sensor output with your oscilloscope. The oscilloscope frequency mirrors that of the serial tool and your starting to get that warm fuzzy feeling that an you’re onto something.

    Steady the buffs
    You’ve been close to success before though, only to be thwarted in the final moments so you’re keen not to be caught out twice. You know that documenting the reasons that the MAF output could be incorrect is the way to go, and duly make a list of tests required to confirm your theories.

  • And the worst MOT tester in the UK is… YOU 

    To save money and raise efficiency, the DVSA has turned to automation. They no longer need an army of Vehicle Examiners wandering from MOT bay to MOT bay. Instead they are collecting data all the time.
        
    Let’s say I am the boss and my business is low on revenue. I beat up the manager and he in turn influences the tester to fail everything coming through the door. The customer is now stuck with no MOT and I have some simple high yield repairs.
        
    Here’s where it gets interesting. The DVSA computer is monitoring individual tester behaviour and looking at averages. The pattern is really easy for a computer at the DVSA to see because it’s just not possible that lots of cars fail on the same items every day.  The DVSA’s fix is to target garages where data shows they are hunting for work and send in a VE to crosscheck. He needs only to wait nearby until our tester issues his favourite fails and then arrive to retest the car.
        
    We all, as testers, now have access to our TQI. Lots of testers that I speak to have the sentiment that this data is all rubbish but, here is the rub. The DVSA have a team of very capable data processors looking at this data and writing algorithms that alert them to trends that need investigation.

    Take my example of one of my longest-serving testers and allow the DVSA computer to tell me every car that he has tested in the last two weeks of November for the last seven years and add in that we only want to know about cars tested after 4:30pm. We find only one car; a Y reg (2001) BMW 320i convertible, always tested after 5pm with a longest test time of thirty-two minutes and shortest of twenty-seven. Guess what, it’s my guy’s brother-in-law’s car!
        
    For me the horror is that the car has never failed an MOT. It’s also never been in the workshop for any repairs. It looks absolutely dogged out and is on around 180,000 miles. Worst still my guy has never once even advised anything on this car. The VE would assume  Barry’s guy is prepared to let things slide at the end of the day, so maybe he plans to visit me after 5pm on a Thursday.

    Conflicting vehicle locations
    This is a fun story from a close and trusted friend. My guy is at a DVSA IVA check and overhears a conversation by a couple of Vehicle Examiners. It goes like this; VE no.1 is suspicious of an MOT bay offering fraudulent MOT tests. He parks down the road from an MOT bay in Kent and checks which vehicle is logged on and being tested. He takes the registration number of the vehicle in question and calls the DVLA, identifies himself and asks if the vehicle has been seen on the DVLA camera system anywhere in the last half hour. The car was last seen on the M25 twelve minutes ago near Watford in Hertfordshire over 70 miles away.
      
    So, our VE is in Kent and the car is in Hertfordshire. If this works today in a manual sense how long will it be before computers can do this to every single test? Talk about an easy way to stop fraudulent MOTs, just using computers that the government already own.



  • Classic move 

    All my recent writing has involved modern cars and techniques, but this month I have decided to write about my main passion of classic cars. The classic car market is huge and people are now seeing a lot of classic cars as an investment.
        
    Recently I set about scouring eBay and Gumtree for a restoration project or ‘barn find’ as people like to classify anything that has stood unused for a length of time. The reason for the project is that it is my Dad’s 70th birthday was just before Christmas and what better present than a dusty and rusty old MGB GT? The British classic is top of my shopping list. Dad used to have a white MGB GT and I have always wanted an affordable classic so I have come to the conclusion that the MGB fits the bill perfectly.

    Bargin
    Luckily I have found the perfect car. A lot of money can be lost due to poor bodywork issues. Welding is definitely not my forte, but luckily this particular MGB is solid underneath. That said, the interior needs a good clean and some repair and the engine requires a good service and tune up. The previous owner hadn’t used the car for over seven years but the little 1.8 litre engine ignited just fine. Admittedly it was running slightly lumpily, but it was drivable and solid for well under £1,000. In my eyes it was an absolute bargain.
        
    As I write this I haven’t yet unveiled the car to Dad but I have ordered the parts catalogues with a view to what this ‘blank canvas’ can become. I am keen on a Sebring kit and Minilites. While getting a complete respray, the exterior paint is as dull as a wet February day. However, I keep having to remember that it is a present and not my car. I will certainly push what I think is best for the car.

    Connection
    Over the years I have restored and re-commissioned plenty of vehicles. It is something I thoroughly enjoy doing and means you can really implement simple engineering techniques such as turning the mixture screw on a carburettor. I always feel that when a classic car comes in for work that the owner has a closer connection with this vehicle rather than their everyday one. I enjoy communicating with the owner in how they would like to restore the car, cars such as the iconic British Mini and MGB can be customised without losing their vintage style. Parts are so plentiful for most classics that there isn’t that time delay when restoring.

    Escapism
    The MGB GT I have purchased comes with a thorough and plentiful file full of receipts mounting up to tens of thousands of pounds, and this certainly is not uncommon. Classic cars are a great chance for escapism in this modern world where an OBD port is the most commonly used part of the car. Instead I get to  enjoy being able to tune an engine with just a flat head screwdriver.



  • MOT tester Annual Training & Annual Assessment: Time is running out  

    Well it’s that time of year again when the MOT tester must complete their Annual Training and Annual Assessment and the time is running out quickly. The cut off for this year is 31 March; As in the end of the month. Any MOT testers not completing the Annual Training and Annual Assessment will be automatically suspended from carrying out vehicle MOT tests.
        
    Once suspended, becoming re-approved will mean that the MOT tester will have to carry out a demonstration MOT test observed by a DVSA representative as well as completing the previous year’s Annual Training and Annual Assessment anyway. Not to mention the loss of garage revenue that may accompany the loss of an MOT tester.
        
    The DVSA have highlighted that the following require a demonstration test:

  • No self control? 

    Having witnessed the growth of passive driver assist systems and the intent to move towards fully autonomous vehicle control, my topic this month is to raise both thought and debate towards the implications. My first intention is to separate assistance from autonomy.

    I fully support assistance as it provides a safer environment for the driver to concentrate on vehicle control. Many of these systems have been available for a very long time, including possibly the very first, power steering and power windows.

    ABS to power steering
    Anti-lock braking systems (ABS) are, I think, an excellent example where drivers may be misled as to the safety improvements. However, the laws of physics still apply, and the co-efficient of friction and kinetic energy will always dictate the retardation distance and vector. Obvious enhancements to ABS work as a fully integrated system, including dynamic chassis stability.
    Early variants simply monitored the wheel speed sensor frequency, reducing the engine throttle angle to reduce torque through the driving wheels when a significant differential existed. Recent additions now include variable geometry anti-roll bar and adjustable rate shock absorber damping with self- levelling.

    Evolving in parallel with these systems, and this is where there is an arguable transition from passive to active or automatous control, is the steering system. The introduction of power steering does have great advantages in reducing driver fatigue and improving mechanical response to steering wheel input. The next evolution was variable rate steering assist, whereby the assistance is proportional to steering angle and road speed. with the evolution of brushless motors and highly accurate position sensor technology, steering systems now offer corrective suggestion to the driver via a subtle torsion bar within the upper steering column. Should the driver resist this small force the system will disengage leaving the driver fully in control.
    I am choosing to ignore for the moment fully autonomous steering control as it embodies a whole array of additional control input requirements.  This allows me to focus on some of the more peripheral driver support systems which I do fully endorse. Matrix vehicle lighting control is possibly one of the best safety improvements. This enables full beam lighting always, yet avoiding oncoming vehicle light stray. Smart cruise control is also especially useful on motorways in uniform traffic conditions.

    Compliance
    The next group of driver assist starts to cross the boundaries of assistance, this is due to the introduction of long- range transmitters and receptors, lane divergence, and vehicle proximity awareness. This technology does of course lend itself to other previously mentioned systems.  

    There should be a very sobering pause at this point.  To maintain system integrity and accuracy from the above systems a little thought should be given to the almost non- existent function called calibration.it is critical. If you fully consider the implications of everyday servicing and repairs that affect these systems, compliance is the responsibility of the repairer. This means you.
    This is the point where I cannot avoid the transition towards full driverless autonomous control. Due to several critical considerations, technical compliance, political compliance, legal compliance, and public acceptance, it is to be rolled out in five steps over several years. Ford recently suggested it could be implemented by 2021, with level zero full human control, to level five where the human has no input responsibility.

    What of the globe’s biggest commerce giant’s? Intel has just purchased an Israeli autonomy tech company for $15 billion. Google has spent a modest $30m, and Facebook is in it too. All hellbent on convincing us of the benefits in total vehicle automation. Given their past and current dishonesty, self-interest, and responsibility avoidance you can bet it all going to be a financial beartrap.
     However, my personal feelings are more complex. Humans has evolved over many thousands of years by overcoming and controlling a multitude of challenges. It has enabled our brain and cognitive functions to develop to incredible levels. Imagine then, being trapped in an autonomous container with absolutely no functional requirement. What will you do by way of brain stimulation or choices. I accept traffic jams are worst than toothache, but driving is a socially shared experience. Think of the simple activities that release endorphins, such as cycling and walking. Why? because of the brain stimulation and cognitive responses, a form of achievement.

    If you must have total autonomy for your travel requirements, then public transport is available now. My acid test for the techno maniacs out there is, given that the technology is currently available and has been proven over several years, would you choose to fly in an aircraft with no pilot? Remember that even in autopilot there are teams of humans constantly monitoring the flight path and technical systems.

    Credibility
    I’m not ignorant of the accident statistics that give credibility to automation, if that was the true motivation, then smoking and alcohol would be banned tomorrow as they kill and maim an awful lot more.

    It has been suggested that our home environment would be improved as our car could drop us off and then park its self in a less congested place, so if you live in central London your car could end up in a South Downs village. On a more sinister note, if an autonomous vehicle faced with an inevitable collision from a oncoming car, would it mount the pavement and choose the mother with a pram as the better survivable outcome for its occupants?

    The very best qualities of life always come back to interaction, be it with other people, pets or machines, what next? When do machines decide we are the redundant component? Disagree, or debate, but don’t accuse me of not embracing technology, I have spent my life trying to master it.





Most read content


Search

Sign Up

For the latest news and updates from Aftermarket Magazine.


Poll

Where should the next Automechanika show be held?



Facebook


©DFA Media 1999-2019