By Eugene le Roux, FSAIRAC, and Eamonn Ryan
In Parts 1 and 2, we explored engineering as both a continuum and an economic system – from abstraction through to production, maintenance and lifecycle realities. In Part 3, we move into more complex territory: how control, responsibility and ethics evolve as engineering systems become more integrated, software-driven and commercially pressured. This is Part A of part three of a three-part series.
As systems become more interconnected, the boundary between engineering design and commercial strategy becomes increasingly blurred. Senivpetro | Freepik.com
If Part 2 revealed the economic tensions between production and maintenance, Part 3 exposes a more subtle layer: the influence of commercial pressure on design decisions themselves.
Engineering does not take place in isolation. Every system exists within a competitive environment where profitability, efficiency and market positioning shape outcomes. As a result, design is not always driven purely by technical optimisation or long-term maintainability. It is often influenced by strategic considerations – some explicit, others less visible.
One example lies in how components are integrated into larger assemblies. In principle, good engineering practice favours modularity: the ability to replace a single failed component, such as a bearing, without dismantling or discarding surrounding systems. In practice, however, designs are sometimes configured in ways that make such replacement difficult or uneconomical. A relatively minor failure can necessitate the replacement of an entire subassembly.
This has direct implications for lifecycle economics, discussed in Part 2. Maintenance becomes more complex and costly, while production benefits from simplified assembly and increased parts turnover. The tension between these outcomes is not accidental – it reflects the competing priorities embedded within modern engineering systems.
A similar dynamic is evident in electronically controlled systems. In contemporary vehicles, for example, components are increasingly tied into integrated communication networks such as the Controller Area Network (CAN bus). Individual parts – even something as seemingly simple as a headlight – may carry unique identifiers recognised by the system. If a non-approved or aftermarket component is installed, the system can respond by limiting functionality, sometimes placing the vehicle into a reduced-performance or “limp” mode.
This level of integration enhances control, safety and diagnostics. However, it also restricts flexibility in maintenance and repair, reinforcing dependence on original equipment supply chains. As systems become more interconnected, the boundary between engineering design and commercial strategy becomes increasingly blurred.
These developments raise broader questions. When does optimisation become restriction? At what point does system control limit user autonomy? And how should engineers navigate these trade-offs?
The growing role of software adds another layer of complexity. Unlike purely mechanical systems, software can be modified after deployment – sometimes remotely. This introduces powerful capabilities, such as performance updates and fault corrections, but also raises concerns around transparency and consent. The possibility that functionality could be altered without direct user intervention challenges traditional assumptions about ownership and control of engineered systems.
At the same time, the convergence of disciplines is accelerating. Mechanical systems, electronics and software are no longer separate domains but tightly integrated layers of a single system. This is often described under the umbrella of Mechatronics – a term that captures the fusion of physical and digital engineering into unified, responsive systems.
As this integration deepens, so too does the responsibility carried by engineers. Decisions made at the design stage now ripple across the entire lifecycle, influencing not only performance and cost, but also accessibility, repairability and user trust.
