By Eugene le Roux, FSAIRAC, and Eamonn Ryan
Engineering is often misunderstood as either purely theoretical or purely practical. In reality, it exists along a spectrum that stretches from abstract scientific modelling to hands-on implementation. This is Part one of a two-part series.
Once the system behaviour has been defined, the next step is translating theory into something buildable. Mindandi | Freepik.com
To understand what engineering actually is, we need to unpack the roles within the discipline – and how they overlap, interact and depend on one another.
At its core, engineering begins with modelling. The engineer’s primary function is to interpret real-world problems and translate them into structured, solvable systems using the principles of mechanics, thermodynamics, fluid mechanics, heat transfer, electrical engineering, mechatronics and increasingly, software engineering. These disciplines provide the mathematical and scientific framework needed to predict how systems behave under different conditions.
This modelling process is not superficial. It extends all the way down to the smallest components. In mechanical systems, for example, engineers must consider torque specifications, material properties, tolerances and even the size and type of washers and fasteners. Every variable influences performance, safety and longevity. The outcome is often highly abstract – expressed through equations, simulations and digital models rather than physical objects.
Because of this, engineering is sometimes perceived as a ‘paperwork’ or ‘software-heavy’ profession. While that may sound reductive, there is truth in it: the engineer’s output is frequently a detailed set of instructions, calculations and specifications that define how something should exist and function. It is a specialised role that demands precision, foresight and the ability to anticipate failure before it occurs.
However, these models do not exist in isolation. Once the system behaviour has been defined, the next step is translating theory into something buildable. This is where the draughtsman – or more broadly, the design technologist – enters the process.
Using advanced CAD (computer-aided design) tools, the draughtsman works closely with the engineer to ‘package’ the system. This involves arranging components spatially, ensuring manufacturability and producing detailed drawings that can be used for fabrication and assembly. While the engineer defines what must happen, the draughtsman defines how it is physically realised.
This is not a secondary or lesser role. Errors at this stage – incorrect tolerances, misaligned components or unclear drawings – can lead to costly failures in production. In many ways, the draughtsman acts as the bridge between abstract theory and physical reality.
At this point in the lifecycle, we have moved from concept to design. The system has been modelled, refined and translated into buildable documentation. But engineering does not end here. In fact, this is where it begins to intersect more visibly with the real world.
