Troubleshooting is process we as engineers all encounter, in one form or another, on a daily basis. Due the complex nature of issues which engineers face, it is unlikely that any two individuals will follow the same troubleshooting process, step by step.
Which brings us to the apple. There’s a number of ways to eat an apple, likewise, there are also a number of ways to troubleshoot.
Our experience of working with a variety of engineers, on a variety of boats, gives us the chance to further understand the different approaches towards troubleshooting and continue to adapt Seahub to improve this process.
Every engineer sets out to achieve the same thing; To fix the issue and return to normal operation as soon and as safely as possible. The process to get there can be vastly different. So can the view on ongoing equipment management.
Lets look at a few differing troubleshooting approaches we have seen in.
Once an issue is detected, an engineer may approach the component with all the necessary tools to adjust, test and return to service. Typically a visual inspection is carried out, troubleshooting equipment may be used (a Multimeter for example) and if replacement parts are on hand, a replacement is made and returned to service. Most commonly, the component is closely watched for a period of time after the repair ensuring the repairs have resolved the issue. If there is no evidence of the issue persisting, an engineer is often pulled towards the next issue.
More increasing we are seeing a review and log approach used towards troubleshooting. Now, once an issue is detected, a review of any documents relating to the service history or repairs previously performed, are reviewed. This can give invaluable insight in the history of the component and typical areas of failure. These documents can be anything from a recent service report, a note from a previous engineer or an operational manual. In time sensitive scenarios, a small amount of time spent initially to understand the landscape could be the difference between resolving the issue first time around, or needing to return to the scene of the crime to resolve again. One thing is common throughout the engineering fraternity; no one likes this.
Following a successful repair and cooling off period, the results and repair information are logged and made available for the next round of troubleshooting. Engineers and those in the industry have largely guided Seahub’s development and the process of improvement will continue.
Today we have engineers who create components and attach documents directly to the component, allowing them to access serial numbers, supplier information, service history, engineer’s logs and operational manuals in one location through our yacht maintenance software. Others choose to add images of recorded faults and repairs and use as a visual aid during the troubleshooting process. The reality is, there’s no single set way to resolve many issues engineers face throughout the course of a working day.
What is important is that you get the end result, safety and as quickly as possible.
Learn more about the Seahub platform here www.seahub.com.au