By Eugene le Roux, FSAIRAC, and Eamonn Ryan
Once a design has been finalised, it enters the phases of testing and production. This is part two of a two-part series.
Once the system behaviour has been defined, the next step is translating theory into something buildable. Pressfofot | Freepik.com
Prototypes are built, systems are validated, and eventually, products are manufactured at scale and distributed to clients. It is at this stage that another crucial group enters the picture: artisans.
Artisans – such as electricians, fitters and millwrights – operate at the practical end of the engineering spectrum. Their role is defined by hands-on interaction with equipment, systems and installations. Unlike engineers, who work primarily in abstraction, artisans deal directly with hardware.
By the time a product reaches an artisan, its technical baseline has largely been fixed. The design decisions, material selections and system behaviours have already been determined. Maintenance procedures, troubleshooting guidelines and operational limits are typically documented. The artisan’s responsibility is to apply this knowledge in real-world conditions: installing, maintaining and repairing systems as needed.
This does not mean the role is simple or lacks depth. On the contrary, artisans must possess strong practical reasoning skills, developed through technical training and experience. They may not rely heavily on advanced mathematics, but they must understand systems intuitively – diagnosing faults, adapting to unexpected conditions and ensuring safe operation.
A key distinction emerges here: while engineers ask, “How should this system behave?”, artisans ask, “Why is this system not behaving as expected?” Both perspectives are essential, and both require problem-solving – just at different levels of abstraction.
Between these two roles lies another important category: technicians. As systems become more complex – incorporating automation, controls and integrated software – there is a growing need for professionals who can bridge the gap between theory and practice.
Technicians typically have more advanced theoretical training than artisans but remain strongly hands-on. They might calibrate sensors, troubleshoot control systems or assist in commissioning complex installations. In many ways, they function as ‘applied engineers’ capable of interpreting technical documentation while also engaging directly with physical systems.
This layered structure – engineer, draughtsman, technician, artisan – illustrates that engineering is not a single role, but an ecosystem. Each function overlaps with the others, and boundaries are often blurred in practice. In smaller organisations, one person may perform multiple roles; in larger ones, these roles become more specialised.
An interesting question arises when considering certification and responsibility. In many countries, the authority to issue a Certificate of Conformance (CoC) for an installation is legally reserved for qualified tradespeople or licenced professionals, depending on the domain. While engineers may design and specify systems, certification often requires compliance with regulatory standards that fall within the scope of registered artisans or inspectors. This highlights an important reality: engineering is not only about technical capability, but also about legal accountability and professional boundaries.
Ultimately, engineering is best understood not as a job title, but as a continuum of activities that transform ideas into functioning systems. It begins with abstract modelling, passes through detailed design and culminates in real-world application and maintenance. Each role contributes a different perspective, and none can function effectively in isolation.
To ask “What is engineering?” is therefore to ask how humans turn knowledge into utility – how science becomes structure, and how theory becomes something you can touch, use and rely on.
