By Eugene le Roux, FSAIRAC, and Eamonn Ryan
In the intricate world of technology and industry, the successful creation, implementation and maintenance of complex systems relies on a diverse range of skills and expertise.
Eugene le Roux. © RACA Journal
Often, the roles of artisans and engineers are considered in relation to one another, prompting questions about the fundamental differences in their contributions. Is the distinction merely a matter of the scale of activity they address? Does it lie in the degree of technical uncertainty they navigate? Or perhaps it’s a difference in focus – holistic versus detailed – or the stage at which their primary involvement occurs: development versus operation?
Considering these questions, a compelling argument can be made that the engineer bears the responsibility of encompassing all system levels and addressing any inherent uncertainty related to the overall system’s behaviour. In scenarios involving development, this phase is predominantly the engineer’s domain. However, this is not to say that other roles are insignificant. Crucially, the engineer’s work is informed by vital input from the artisan, who possesses deep practical understanding at a system level (often considered level 5, focusing on the physical implementation and functionality), and from the end-user (system level 6), whose needs and experiences ultimately dictate the system’s success.
Given the engineer’s broad responsibility for the entire system, their focus during development might centre on the most salient aspects of system behaviour, including critical factors like reliability. This then raises the important question of sign-off. A logical delineation of responsibility suggests that the engineer should sign off on the successful development of a system, attesting to its design, functionality and adherence to specifications. Conversely, the artisan, with their hands-on involvement in the operational stage, should be responsible for signing off on the successful performance of the system they have worked on. This includes the crucial aspect of workmanship, where the finest details often hold the key to long-term reliability and efficiency – a realm where the artisan’s meticulous attention is paramount.
It becomes clear that neither the role of the engineer nor the artisan is negotiable. Each occupies a vital link in the chain of creating and maintaining functional systems. A weakness at any system level, whether in the initial design or the final implementation, can compromise the entire operation. The theoretical brilliance of an engineering design can be undermined by poor workmanship, just as the practical skills of an artisan cannot compensate for a fundamentally flawed design.
Where then does the technician fit into this framework? The technician often occupies a complex but typically less uncertain role compared to the engineer. Their work frequently involves more routine tasks, following established procedures and protocols to maintain troubleshoot and repair systems. While the technical knowledge required can be substantial, the degree of uncertainty they face is often reduced due to the existence of established guidelines and diagnostic procedures developed by engineers. The technician acts as a crucial bridge between the theoretical understanding of the engineer and the practical expertise of the artisan, ensuring the ongoing functionality of systems in the operational phase.
Furthermore, the context of an artisan’s employment can also shape their role. A self-employed artisan often takes on an additional layer of responsibility, encompassing the management aspects of running their own business. This entrepreneurial dimension adds a further level of expertise, requiring skills in areas such as client relations, financial management and business development, which extend beyond their core technical abilities. This management aspect inherently broadens their perspective and necessitates a more holistic understanding of their work within a wider business context.
Finally, the approach of an artisan is often characterised by its practicality and heuristic nature. Their deep experiential knowledge allows them to make insightful deductions based on tangible observations. For instance, an artisan might diagnose fluid flow issues by feeling temperature differences in pipes, assess a bearing’s condition by the subtle sounds of its vibration, or judge an engine’s mixture by the color of its spark plug. This hands-on, sensory-driven approach complements the more theoretical and analytical methods of the engineer, providing a vital layer of practical insight and real-world problem-solving that is indispensable in the operational stage of any technical system.
The synergy between engineers, artisans and technicians, each contributing their unique skills and perspectives at different stages and levels of technical complexity, forms the bedrock of a successful and robust technical ecosystem.Their roles are not merely different but fundamentally interconnected and equally essential for achieving optimal system performance and longevity.
