You can now view the recording of the Assessing systems thinking through student-created AI simulations webinar, as part of the Complex Systems Toolkit, supported by Quanser. The webinar was live on 12th November 2026.

This webinar explored assessing systems thinking through student-created AI simulations, and was delivered by Dr. Stuart Grey, demonstrating a new assessment approach, developed from his teaching at the University of Glasgow and shared through the EPC’s Complex Systems Toolkit.

Students create and debug interactive AI simulations of complex sociotechnical scenarios, making their understanding of stakeholders, relationships, feedback and trade-offs visible through their design decisions and documented revisions. Participants try the activity themselves, examine what students’ work can reveal about their understanding, and explore how to set, support and mark this type of assessment in their own disciplines.

For more about the webinar, including the event programme and speaker bios, click here.

To enable closed captions on Vimeo, click the CC button in the video player.

This webinar is part of the Complex Systems Toolkit, supported by Quanser.

 

This post is also available here.

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Toolkit: Inclusive Engineering Toolkit  

Author(s):  Jenny McLaughlin, MA APMQ 

Resource type:  Knowledge article: Inclusion in engineering contexts (e.g. how inclusion shapes engineering practice, design decisions, teamwork, and outcomes in real engineering contexts) 

Topic: Explore the relationship between inclusion, human-centred design, safety, and systems thinking in engineering practice. Drawing on examples including the Heathrow Inclusive Design programme, Inclusive Design Overlay, Accessible and Inclusive Airport standards, and the Equitable Safety Initiative to demonstrate how inclusive approaches can influence engineering decisions and outcomes. 

Title: Inclusion as a Core Engineering Competency: Improving Safety, Systems and Engineering Outcomes.

Relevant disciplines:  Any.

Keywords:  Inclusive Engineering; Systems thinking; Risk; Inclusive or Responsible design; Equity, Diversity and Inclusion; Accessibility; Engineering practice; Reflective practice; Professional conduct; Teaching and learning; Knowledge or Guidance

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.   

Downloads: A PDF of this resource will be available soon. 

QAA Inclusive Higher Education Framework mapping:  Toolkit resources are designed to be applicable across engineering disciplines, but educators may find it useful to understand their alignment with the QAA Inclusive Higher Education Framework. The framework sets out five areas of activity that support inclusive practice across higher education, covering curriculum design, teaching and learning, assessment, learner support, and institutional approaches to inclusion.     

This resource aligns most closely with the following QAA Inclusive Higher Education Framework area of activity:  Curriculum Design and Delivery and Community and Belonging. 

Within the Inclusive Engineering Toolkit, these areas provide a reference point for understanding how resources support inclusive engineering education and practice, rather than defining a rigid taxonomy or classification system.    

AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Equality, Diversity and Inclusion. In addition, Design, Integrated or systems approach, Ethics and Risk. 

Education Level: Beginner. 

 

Upon successful engagement with this resource, learners will be able to: 

Teachers have the opportunity to: 

   

Central argument

Inclusion is not an add-on to engineering; it is an essential part of good engineering practice. By applying systems thinking and understanding the full diversity of human needs, engineers can identify risks, uncover opportunities and design solutions that work for more people. The result is safer, more resilient and more successful outcomes. Inclusion should therefore be viewed as a core engineering competency, not simply an EDI consideration.  

 

Introduction  

Engineering has always been about solving complex problems. Whether designing infrastructure, transport systems, digital technologies, products or services, engineers make decisions that shape how people experience the world around them. Yet engineering practice has often relied on assumptions about a hypothetical ‘average’ user. The challenge is that no such person exists.  

People experience products, environments and systems differently. Disability, age, neurodiversity, health conditions, language, culture, socioeconomic circumstances, caring responsibilities, confidence and previous lived experiences all influence how individuals interact with engineered solutions. When these differences are not considered, barriers emerge. Sometimes those barriers create inconvenience. Sometimes they create exclusion. In many cases, they create safety risks.  

This is where inclusion becomes an engineering issue, not a separate social aspiration. Inclusion asks engineers to move from awareness to action: to notice when a system has not been designed for the full diversity of people who will use, build, maintain or be affected by it, and to respond before harm, exclusion or workaround becomes normalised.  

Inclusion should therefore be recognised as a core engineering competency: a practical route to better decision-making, safer systems, more ethical practice and stronger outcomes for society. It is part of how engineers understand context, interrogate assumptions and design with responsibility.  

 

Why inclusion is an engineering issue  

Inclusion is often discussed in relation to accessibility, representation or equality. Whilst these are essential considerations, the implications for engineering practice are frequently overlooked. Every engineering decision is based on assumptions: who will use a system, how they will behave, what capabilities they have, what risks they may encounter and what constitutes acceptable performance.  

When those assumptions are narrow, engineering solutions can unintentionally exclude people or introduce risks that remain hidden until late in delivery or operation. A standard face mask, a colour coded indicator, a risk assessment, a site access route or an evacuation procedure may appear neutral, but each one carries assumptions about bodies, cognition, confidence, communication, culture and context.  

The human cost of those assumptions is often felt first at the edges. A person may find themselves adapting silently to a design that has not considered them. They may work harder, move more cautiously, rely on unofficial support or decide not to speak up because the system around them signals that the issue sits with them rather than with the design. Those experiences are not marginal. They are evidence that the engineering problem has not been fully understood.  

Inclusive engineering is therefore not about designing for a ‘minority’ group. It is about recognising human diversity as a design parameter. It asks engineers to move from designing for an assumed norm to designing with awareness of variability, context, interdependence and lived experience. This is not separate from technical excellence. It is part of it.  

Many innovations now considered mainstream originated from efforts to address exclusion or access barriers. Captions, voice recognition, predictive text, touch screens and video calling show how designing for difference can improve usability and participation for many people, including those with temporary or situational needs. Inclusion can therefore be a source of innovation as well as a route to equity.  

 

Inclusion, safety and human-centred design  

One of the strongest reasons for embedding inclusion into engineering practice is the relationship between inclusion and safety. Traditional safety approaches rightly focus on hazards, controls, compliance and risk reduction. However, if those approaches assume a standard user, worker or maintainer, they may overlook the fact that safety is experienced differently by different people.  

The principle of equitable safety* is grounded in a simple but powerful proposition: safety is experienced uniquely by everyone. This shifts the question from ‘Is this safe?’ to ‘For whom is this safe, in what context, and under what conditions?’ That reframing matters. A maintenance access route may appear adequate for one worker while creating significant barriers for another. An evacuation process may assume sensory, cognitive or physical capabilities that not everyone possesses. A site welfare arrangement may meet minimum requirements while still failing to provide dignity, confidence or psychological safety for all.  

*The Equitable Safety Initiative is a group of organisations driving change within standards, policy and practice, recognising that safety is experienced differently by everyone. The initiative is referenced in the Construction Leadership Council’s Equity, Diversity, Inclusion and Culture Change workstream objectives (Construction Leadership Council, n.d.). 

A personal example illustrates the point. During a health and safety visit, walking across rebar on a construction site, I knew I was not safe. Yet even as the client and project manager, I did not feel safe enough to speak up in that moment. That experience matters because it exposes a wider systems question: if someone with formal authority can hesitate, what happens for a subcontractor, a new apprentice, a disabled worker or anyone who already feels they have less power in the system?  

This is why equitable safety1i must include physical and psychological safety. A person cannot raise a safety concern if the culture, language, process or hierarchy around them makes speaking up feel unsafe. Engineers must therefore consider not only whether a control exists, but whether people can understand it, access it, trust it and challenge it when it does not work for them.  

Human-centred design (ISO, 2019)  helps engineering teams recognise these differences by considering the full range of people who interact with a system across its lifecycle: those who design, build, operate, maintain, use, visit, regulate, clean, respond to emergencies and live alongside it. By anticipating difference, engineers can identify risks that remain hidden when decisions are made around the perceived majority.  

This does not mean adding complexity for its own sake. It means recognising the complexity that already exists and responding to it with empathy, evidence and professional judgement. If safety is non-negotiable, then safety should be equitable.  

 

Why systems thinking matters  

Many attempts to improve inclusion focus on individual adjustments or isolated interventions. These can be important, but they rarely address the wider systems that shape people’s experiences. Systems thinking offers a more useful perspective because it considers the relationships between people, processes, environments, behaviours, technologies, governance and culture (Meadows, 2008).  

In engineering, a design decision rarely affects only one outcome. A change to layout can influence movement, wayfinding, staffing, emergency response, maintenance access, perceived safety, passenger confidence and operational resilience. A procurement decision can influence who is consulted, whose knowledge is valued and which risks are prioritised. A standard or process can either enable inclusive decisions early or push them into late-stage remediation.  

The difficulty is that systems often give us comfort. They provide process, standards, sign-off routes and familiar evidence. These are necessary, but they can also create a false sense that someone else has already checked the assumptions. Inclusive practice asks engineers to stay curious within those systems: to ask what the evidence is based on, whose experience has informed it and what bias may sit inside the data, standard or precedent being used.  

At Heathrow, inclusive design work has used approaches such as the Accessible and Inclusive Airport Standards (Heathrow, 2025), the Inclusive Design Overlay (RIBA, 2023), and the Wheel of Considerations (Heathrow, 2026) to encourage project teams to ask wider questions. These approaches prompt consideration of people, environments, activities, risks, legacy and system interactions. The intention is not to make every engineer an inclusive design specialist. It is to equip engineers to ask better questions, recognise assumptions and identify when additional expertise or lived experience is needed.  

The Wheel of Considerations is particularly useful because it makes inclusion discussable and trackable across a project lifecycle. By considering people who use a space and people who do not, the environments they move through, the activities they need or want to undertake, the risks created by low agency, the legacy of previous projects and the wider systems connected to the design, teams can make inclusion part of everyday engineering judgement rather than a late-stage review.  

In this sense, inclusion is a practical application of systems thinking. It helps engineers see how decisions interact across an asset lifecycle and how unequal outcomes can be designed in or designed out.  

 

Inclusion as a professional competency  

Engineering education has traditionally emphasised technical competence, analytical capability and problem-solving. These remain essential. However, engineering is fundamentally a social activity, shaped by the needs, behaviours and experiences of the people it serves. The complex challenges facing society increasingly require engineers to combine technical expertise with human-centred judgement, ethical reasoning and systems awareness in order to create solutions that are both technically effective and socially successful.  

Future engineers will need to design for diverse populations, anticipate unintended consequences, balance competing stakeholder needs, manage complex risks and demonstrate responsibility for the social outcomes of their work. These capabilities cannot be developed through technical knowledge alone. They require students to understand exclusion, engage with different perspectives, challenge assumptions and evaluate the implications of engineering decisions for people who may experience systems differently from themselves.  

This is also a matter of professional responsibility. Safety duties require engineers and project teams to consider foreseeable risks to people affected by construction, operation and use. Inclusive engineering strengthens that responsibility by widening what teams are able to foresee. It challenges the idea that risk can be fully understood if the people most likely to experience barriers are absent from the conversation.  

Inclusion should therefore be treated as a core professional competency, alongside safety, sustainability and ethics. It is not an optional addition at the end of a design process. It is a discipline of thinking that should influence problem definition, data collection, user research, design development, risk assessment, testing, commissioning, operation and post-occupancy learning.  

 

Implications for engineering education  

If inclusion is a core engineering competency, it cannot be confined to a standalone lecture or optional module. Engineering educators can embed inclusion throughout curricula by connecting it to the activities students already undertake: defining problems, setting requirements, analysing risk, developing concepts, testing prototypes, evaluating trade-offs and reflecting on outcomes.  

Students should be asked not only whether a solution works technically, but who it works for, who it may disadvantage, what assumptions were made and what evidence was used to understand diverse needs. They should encounter case studies where exclusion has created harm or poor performance, as well as examples where inclusive approaches have improved safety, usability, resilience or innovation.  

The Equitable Safety framing offers a useful classroom shift. Instead of asking students to design for a generic user, educators can ask them to design for the edges and then examine how that improves the centre. What risk becomes visible when we consider a neurodivergent maintainer, a short-statured worker, a person with colour vision deficiency, someone managing fatigue, or a passenger under stress? What changes when students consider confidence, dignity and agency as design outcomes, not just technical performance?  

This does not require all educators to become inclusion specialists. It requires curricula to make inclusive thinking visible, assessable and connected to engineering judgement. It also requires educators to create learning environments where students can ask difficult questions, recognise what they do not know and learn from people with different lived experiences.  

 

Reflective questions for educators and students  

The following questions can support classroom discussion, design reviews, project-based learning and assessment:  

Understanding people  

Understanding assumptions  

Understanding safety  

Understanding systems  

Understanding outcomes  

 

Conclusion  

Inclusion is often associated with social outcomes, but the evidence presented in this article demonstrates its relevance to engineering practice. Engineering decisions influence how people interact with infrastructure, technology, products and services, shaping outcomes related to safety, accessibility, usability and participation. Understanding the diversity of the people affected by those decisions is therefore an important aspect of effective engineering practice.  

The application of human-centred design, systems thinking and equitable safety principles provides engineers with practical approaches for managing complexity, identifying risks and improving outcomes. In this context, inclusion is not simply a matter of compliance or representation; it supports sound engineering judgement and contributes to the delivery of solutions that perform more effectively across a wider range of users, environments and operating conditions.  

The evidence base for inclusion extends beyond equity considerations alone. Research and practice demonstrate its contribution to safer systems, more informed decision-making, improved risk identification, enhanced user experiences and better overall system performance. As engineering challenges become increasingly complex and interconnected, the ability to recognise and respond to human diversity becomes an important element of professional competence.  

 

Suggested educator use  

 

References

 

Further reading

McLaughlin, J. (2025) The edges protect the centre: Equitable safety and inclusive design in the built environment. IOM3. Available at: IOM3 | The edges protect the centre (Accessed: 24 September 2026).

  

Acknowledgements

This contribution draws on previous work, including PEARLS and Wheel of Considerations, co-authored by Emily Castle, Carly Dickson and Jenny McLaughlin.

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.        

All contributions published through the Inclusive Engineering Toolkit have been subject to a structured peer review process to support quality, relevance, and consistency.     

The Inclusive Engineering Toolkit recognises that inclusive language and terminology may vary across contexts and communities, and that contributors may use different approaches depending on context and preference, including identity-first and person-first language. Users are encouraged to contact us at admin@epc.ac.uk with any questions, concerns, or feedback regarding language used within toolkit resources.    

Toolkit: Inclusive Engineering Toolkit

Author(s):  Dr Pallavi Joshi (The Open University, UK), Prof Dinar Kale (The Open University, UK), Dr Aravinda Meera Guntupalli (University of Aberdeen), Prof David Wield (The Open University, UK)

Resource type:  Knowledge article: Inclusion in engineering contexts (e.g. how inclusion shapes engineering practice, design decisions, teamwork, and outcomes in real engineering contexts)

Topic: Conceptualising inclusivity using case studies of AI-based MedTech for cancer detection in India.

Title: Conceptualising inclusivity in engineering-driven inclusive innovation: case of Indian AI-based MedTech

Relevant disciplines: Bioengineering, medical & biomedical engineering; IT, systems sciences & computer software engineering

Keywords:  Inclusive Engineering; Equity, Diversity and Inclusion; Technology; Innovation; Access and participation; Stakeholders; Systems thinking; Collaboration; Enterprise and innovation; Knowledge or Guidance

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Downloads: A PDF of this resource will be available soon.

QAA Inclusive Higher Education Framework mapping:  Toolkit resources are designed to be applicable across engineering disciplines, but educators may find it useful to understand their alignment with the QAA Inclusive Higher Education Framework. The framework sets out five areas of activity that support inclusive practice across higher education, covering curriculum design, teaching and learning, assessment, learner support, and institutional approaches to inclusion.

This resource aligns most closely with the following QAA Inclusive Higher Education Framework area of activity: Curriculum Design and Delivery; Community and Belonging

Within the Inclusive Engineering Toolkit, these areas provide a reference point for understanding how resources support inclusive engineering education and practice, rather than defining a rigid taxonomy or classification system.

AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Equality, Diversity and Inclusion. In addition, Design and Integrated or systems approach.

Education Level: Intermediate.

 

Learning and teaching materials:

The contribution requires reading and analysis of the article:

 

Premise

Early detection of cancers is a major challenge in India due to the limited availability and access to early detection modalities in low-resource healthcare settings. Recent artificial intelligence (AI)-driven point-of-care (PoC) medical technology (MedTech) innovations for early detection of cancer have shown some signs of bridging this gap. This contribution presents evidence from three detailed case studies of PoC AI-based MedTech inclusive innovations developed by Indian start-ups for the early detection of breast, cervical and oral cancers. There are two main results. First, the work shows the importance of integrating health policy and industrial policy. Surprisingly, such integration is rare. Health policy has assumed that globally available technologies can readily be accessed given appropriate funding mechanisms. The early period of the COVID-19 pandemic disproved this assumption. Second, it builds a conception of inclusiveness as applied to innovation processes, and the implications for early detection of cancer in India.

 

Main body

The article has a range of materials that are useful for building concepts and practices of inclusive engineering.

The abstract and introduction illustrate that the focus on context-specific inclusive innovations for Indian cancer care is relevant to many geographies in low- and middle-income countries and in situations of low-resource healthcare. The article focuses on two key research questions:

1. What are the actors and networks, knowledge and technologies, and institutions shaping different early detection modalities, particularly contextualising AI-based PoC MedTech’s, in the Indian context?

2. How can inclusiveness be conceptualised in emerging AI-based PoC innovations, and what implications does it hold for the early detection of cancer in India?

 

Section 2

Section 2 explains the qualitative research methods used in the article. The article uses 16 online semi-structured interviews undertaken with policymakers, representatives of key industry associations, incubators, and senior management of diagnostic firms offering various screening modalities of cancer, venture capitalists, clinical research scientists, and biomedical engineers in 2021 and 2022. These participants were chosen for their direct involvement in the innovation ecosystem or their role in shaping the trajectory of AI-based MedTech in India within the landscape of early detection of cancer in India. The secondary data, collated between 2019 and 2023, were used to triangulate findings and enhance the validity of the results. These included reports and publications of the Indian government, the Clinical Trial Registry of India, key industry reports, multilateral organisations, relevant podcasts, and publicly available interviews of innovators.

 

Section 3

Section 3 of the article examines the actors and networks, knowledge and technologies, and institutions shaping these early detection modalities in India. It provides a detailed analysis of the context surrounding potential inclusive innovations. It allows analysis of different levels of technology in differing geographies.

 

Section 4

Section 4 contains the detailed case studies.

As a teaching and learning activity, here are two questions that can be answered from studying the three case studies:

1. What constitutes the engineering in each case?

2. What makes the engineering innovation inclusive in each case?

 

Section 5

Conceptualisation of inclusiveness is the focus of section 5. Section 5 is, perhaps, the most relevant section for readers more narrowly interested in inclusiveness. Broadly, inclusive innovation is defined as the inclusion of marginalised groups in certain aspects of innovation. The article expands this definition to highlight the role of key institutions, actors and factors shaping inclusiveness in the innovation processes and innovation outcomes.

The cases illustrate a range of elements of inclusiveness.

There is inclusivity in the Innovation process. The AI-based MedTech products increased the potential for cancer diagnosis in difficult-to-reach social groups and geographies. The innovators framed unmet needs as their focus and spent major effort building understanding of the needs of users. The products enabled screening and early diagnosis at the point of care. Many inclusive innovations are framed as low-tech and low-cost. Interestingly, these showed the importance of high technology to address low-resource healthcare challenges.

There is inclusivity in the outcomes of innovation. The products could be accessed in rural areas and by more marginal social groups. Policy initiatives to support women innovators involved in shaping MedTech that are meant for women users emerged as a crucial finding. And end users were able to contribute to improvements in design and use due to the nature of the machine learning algorithms, necessitating data privacy and regulatory norms.  Table 2 has a detailed summary of elements of inclusivity. Can you think of further elements of inclusivity?

Table 3 summarises the variety of business models used to diffuse the innovations based on different strategies that include specific settings for screening.  Might other business models be useful? 

 

Conclusions

The main conclusions are:

1. There is great potential for high-tech MedTech to reshape health care access in low-resource healthcare settings

2. There is a new trajectory of inclusive innovation, not driven by large companies, but by engineers and researchers with personal motivation to improve cancer and health care

3. There is a role for private actors in low- and middle-income countries as producers of innovations. The innovations were driven by engineers and scientists leveraging advanced computing technologies, yet designed to meet specific needs in low-resource healthcare settings

4. The innovations allow for more equitable access, addressing both vertical inequalities (income and wealth related) and horizontal inequalities (like gender, geographical and cultural access barriers – all particularly important in these cases. Inclusivity involves a broader approach, rethinking innovation systems that integrate local needs with industrial production, the creation of new markets, and strong governance that bring together actors, institutions, and so on in creative ways.

Details can be found in Section 6 of the article.

 

References

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

All contributions published through the Inclusive Engineering Toolkit have been subject to a structured peer review process to support quality, relevance, and consistency.    

The Inclusive Engineering Toolkit recognises that inclusive language and terminology may vary across contexts and communities, and that contributors may use different approaches depending on context and preference, including identity-first and person-first language. Users are encouraged to contact us at admin@epc.ac.uk with any questions, concerns, or feedback regarding language used within toolkit resources.

You can now view the recording of the ACE-Lab and agentic engineering workflows webinar, as part of the Complex Systems Toolkit, supported by Quanser. The webinar was live on Monday 29th June 2026, 11am-1pm BST.

This free webinar introduces practical engineering workflows, from requirements capture through to verification and validation. These concepts are demonstrated using the ACE-Lab, a low-cost, hands-on engineering learning platform, alongside MATLAB and Simulink to illustrate key stages of the workflow. The webinar also explores the emerging role of agents in engineering workflows. Through practical examples and demonstrations, it shows how agent-enabled approaches can support engineers in solving problems more effectively. During this webinar we also launched a new call providing you with an opportunity for your content to be featured in the Complex Systems Toolkit.

During this webinar we also launched a new call for contributions, providing you with an opportunity for your content to be featured in the Complex Systems Toolkit.

For more about the webinar, including the event programme and speaker bios, click here.

To enable closed captions on Vimeo, click the CC button in the video player.

 

Resources mentioned in the webinar:

 

This post is also available here.

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Toolkit: Complex Systems Toolkit.

Author: Dr. Zareena Gani (University College London); Mohammed Alabdullatif, (University College London).

Topic: Designing and evaluating additively manufactured heat sinks: A systems approach to digital manufacturing.

Title: Teaching complex systems in advanced manufacturing.

Resource type: Teaching activity.

Relevant disciplines: Mechanical engineering; Production and manufacturing engineering.

Keywords: Additive manufacturing; Prototype evaluation; LabVIEW; Data acquisition; Systems thinking.

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 

Downloads: A PDF of this resource will be available soon.

Related INCOSE Competencies: Toolkit resources are designed to be applicable to any engineering discipline, but educators might find it useful to understand their alignment to competencies outlined by the International Council on Systems Engineering (INCOSE). The INCOSE Competency Framework provides a set of 37 competencies for Systems Engineering within a tailorable framework that provides guidance for practitioners and stakeholders to identify knowledge, skills, abilities and behaviours crucial to Systems Engineering effectiveness.    A free spreadsheet version of the framework can be downloaded.

AHEP4 mapping:  This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Analytical Tools and Techniques (critical to the ability to model and solve problems), and Integrated / Systems Approach (essential to the solution of broadly-defined problems).

Educational level:  Intermediate; Advanced.

Learners have the opportunity to:

Teachers have the opportunity to:

 

Materials and tools required:

This activity utilises both computational design tools and an experimental thermal testing facility to establish a complete system feedback loop:

The experimental facility integrates the following components:

 

Learning and teaching resources:

Pre-reading includes literature on additive manufacturing, design for manufacture, and systems thinking in engineering. Students can review the references listed below to learn the fundamentals of heat sinks, guidance on heat sink design, and important considerations.

 

Overview:

This teaching activity introduces students to complex systems thinking by having them design, fabricate, and experimentally evaluate additively manufactured heat sinks. It can form part of an advanced manufacturing module, in which learners apply systems engineering principles to understand the interdependencies among design, manufacturing, and performance. The activity demonstrates how complex systems principles—such as feedback, emergence, and uncertainty—manifest in physical engineering systems. Students are guided to see the design–test–evaluate cycle as an iterative, data-driven process that links digital design environments with real-world performance outcomes.

 

Activity description:

The experiential learning activity links digital design, manufacturing, and physical evaluation using a complex systems framework. Students iterate designs, fabricate prototypes, and measure thermal performance, reflecting on interdependencies and feedback loops.

 

Session 1: Introduction:

Students are introduced to complex systems and additive manufacturing principles. Variables affecting heat sink performance – geometry, material, surface finish – are identified. The session frames these variables as part of an interconnected thermal management system.

Notes for educators:

 

Session 2*: Design and manufacture:

Teams create CAD models in Fusion 360 and prepare designs for metal additive manufacturing. Students analyse trade-offs between thermal performance, printability, and material efficiency, applying complex design thinking to balance competing requirements. Feedback from earlier simulations informs iterative design refinement.

Notes for educators:

Provide a design prompt (e.g. “Optimise heat sink geometry for maximum heat dissipation under given constraints”).

Share an evaluation rubric that assesses the following: design rationale, manufacturability, thermal performance, and discussion/reflection, including consideration of environmental and societal impacts.

Encourage peer-review sessions in which teams critique one another’s designs before fabrication.

*Advanced option:
Academics may incorporate Thermal Analysis Tools within Fusion 360 or CFD simulations (e.g. ANSYS Fluent) to evaluate design performance and refine heat sink geometry for optimal efficiency.

 

Session 3: Experimental set-up and evaluation:

Each prototype is tested using the dedicated testing facility, as shown in Figure 1.

 

Figure 1: Schematic of the experimental facility for heat sink testing.

The experimental set-up used for evaluating the heat sink performance consists of a DC power supply (i.e. Velleman LABPS3003 30V, 3A), a polyimide-insulated flexible heater (i.e. OMEGA KHLVA-202/40), thermocouples (i.e. K type), a data acquisition system (i.e. NI USB-6210), and a computer for data recording, as shown schematically in Figure 1. A flexible heater is mounted beneath the heat sink, powered by a DC supply to simulate heat generation in microprocessors. Thermocouples are positioned at the heat sink base and calibrated to ASTM E230. A DOWSIL 340 thermal paste layer ensures optimal thermal contact. This enables accurate measurement of the thermal performance of fabricated heat sinks under controlled heat flux conditions.

 

Session 4: Data analysis and comparison:

A custom LabVIEW interface is developed to acquire, visualise, and log temperature and power data in real time, thereby providing a digital bridge between the physical test rig and the data analysis environment. Temperature and power data are acquired using LabVIEW with the NI USB-6210 DAQ card.

The evaluation and comparison of thermal performance among heat sink geometries designed by various student groups are conducted by recording the base temperature of each configuration as a function of time under a constant heat flux and identical ambient conditions. The transient temperature response, illustrated in Figure 2 (a), provides insight into the rate at which each design approaches steady state, whereas the steady-state base temperature indicates its overall heat dissipation capability. This procedure can be applied to any heat sink to assess and compare its thermal behaviour.

Figure 2: (a) Transient base temperature variation with time for the reference and three heat sink configurations. (b) Enhanced heat dissipation relative to the reference block, illustrating the method used to compare thermal performance across different designs. 

Students compare results and interpret the impact of geometry on heat dissipation. They connect observed variations to systemic dependencies between design, manufacture, and experimental performance.

The computed enhancement values, shown in Figure 2 (b) allow direct comparison of heat dissipation efficiency among the different designs. By examining both the temperature–time response and the enhancement ratio, the effect of geometric modification on thermal performance can be quantitatively assessed within a unified experimental framework.

The experimental facility thus forms a closed digital loop connecting design, fabrication, and performance evaluation. The data acquired through LabVIEW and the DAQ system feed back into the design process, enabling iterative optimisation of heat-sink geometry and thermal-management strategies.

 

Session 5: Reflection:

Teams map out interdependencies between process variables, performance metrics, and uncertainties. They construct feedback diagrams (flowcharts) using Microsoft PowerPoint SmartArt, linking design iterations, measurements, and outcomes to identify emergent system behaviour.

 

Assessment and reflection:

The assessment can comprise a reflective report and a presentation.

Reports should include:

Presentations should summarise:

 

 

Additional image:  Heatsink fabricated using a metal 3D printer. 

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Toolkit: Complex Systems Toolkit.

Author: Dr. James E. Pickering, PhD, SFHEA, MIET, MInstMC (Harper Adams University); Dr. George Amarantidis (MathWorks).

Topic: Developing competence in model-based systems engineering.

Title: Practical control engineering education through the ACE-Model.

Resource type: Teaching activity.

Relevant disciplines: Systems engineering; electrical engineering; control engineering.

Keywords: Automatic Control Engineering (ACE); ACE-Box; ACE-Model; Control theory; Control systems; Simulink; MATLAB; Model-based design.

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 

Downloads: A PDF of this resource will be available soon.

Learning and teaching resources:

Related INCOSE Competencies: Toolkit resources are designed to be applicable to any engineering discipline, but educators might find it useful to understand their alignment to competencies outlined by the International Council on Systems Engineering (INCOSE). The INCOSE Competency Framework provides a set of 37 competencies for Systems Engineering within a tailorable framework that provides guidance for practitioners and stakeholders to identify knowledge, skills, abilities and behaviours crucial to Systems Engineering effectiveness.   A free spreadsheet version of the framework can be downloaded.

This resource relates to the Systems Thinking, Systems Modelling and Analysis, Integration, and Technical Leadership INCOSE competencies. 

AHEP4 mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Analytical Tools and Techniques (critical to the ability to model and solve problems), and Integrated / Systems Approach (essential to the solution of broadly-defined problems). 

Educational level: Beginner; Intermediate. 

 

Learning and teaching notes:

Modern engineering is increasingly digital, interconnected, and system oriented. To prepare students for this evolving landscape, the Automatic Control Engineering (ACE) Model offers  a systems-driven, application-focused framework for practical control engineering education. Developed through a MathWorks-funded project launched in the summer of 2025, the ACE-Model unifies three complementary components that together cultivate systems thinking and model-based systems engineering competence: 

Learners have the opportunity to: 

Teachers have the opportunity to: 

 

What does the ACE-Model consist of?:

 

Figure 1: The ACE-Model: Integrating the Toolkit (ACE-Box), with the Processes (ACE-CORE), to Lead to the Real-Life Application (ACE-Apply) to build a progressive mastery in Automatic Control Engineering (ACE).

The ACE-Model is closely aligned with Bloom’s Taxonomy, see (Anderson and Krathwohl, 2001) and Figure 2(a) providing a structured pathway for students to progress through the cognitive hierarchy, while developing capabilities across multiple levels of system abstraction. Figure 2(b) offers a schematic view of the three stages of the ACE-Model, as introduced in Figure 1. An initial overview of the ACE-Model is presented here, with further details provided in the following sections.  

 The ACE-Box is a portable, self-contained hardware tool that brings ACE to life beyond the traditional costly, full-scale laboratories. All that is required is a laptop and the ACE-Box. Designed to support the ACE-CORE methodology, ACE-Box can be set up on a desk, in a classroom, or even at home. MATLAB and Simulink serve as the primary platforms for model-based design, enabling system modelling, control system development, and the deployment of control algorithms to physical hardware (e.g. Arduino Uno) through code generation tools. 

 ACE-CORE guides learners through successive levels of Bloom’s framework: 

At each stage of CORE, learners move from recognising system components to synthesising complex interactions, mirroring the systems engineering lifecycle from requirement capture through verification and validation. This alignment supports AHEP4’s emphasis on analytical and problem-solving competence and INCOSE’s System Definition and Integration competencies. 

Finally, learners progress to Create, the highest stage of Bloom’s Taxonomy, by applying their knowledge to design complete control systems for real-world applications such as drones, vehicles, and automation systems. In this way, the ACE-Model scaffolds learning in parallel with Bloom’s progression, from foundational comprehension to advanced problem-solving, design and innovation. 

Together, these three pillars form a cohesive learning ecosystem: the toolkit, the process, and the application. 

Figure 2: Bloom’s Taxonomy (Anderson and Krathwohl, 2001) (a) and the ACE-Model Three Stages (b).

 

Collaborative community:

The ACE-Model ‘sits’ within the ACE-Lab, a collaborative community of academics and industry professionals committed to developing, validating, and disseminating open-access systems education resources. The ACE-Lab approach embodies complex adaptive systems principles, where the community evolves through continuous feedback, iteration, and co-design. Membership to the ACE-Lab is open to anyone who shares our vision of advancing control engineering teaching tools and practices. Through this approach, the ACE-Model equips graduates with the knowledge and hands-on skills required to excel in modern ACE careers. Find out more about the ACE-Lab through the following website: www.ace-lab.co.uk 

As an evolving community, ACE-Lab continually expands its open-access content through the active contributions of its members. New materials are regularly developed and shared, ensuring the resources remain current and relevant. Through this dynamic, collaborative approach, embodied in the ACE-Model, students not only gain technical knowledge but also develop the capacity to understand, navigate, and work effectively with complex, interconnected engineering systems. 

 

ACE-Box: The toolkit:  

The ACE-Box is based on the early development work of Control-Lab-in-a-Box (Pickering, 2023; 2025). CLB integrates sensors, actuators, and microcontroller to allow students to experience dynamic behaviour, and feedback control. 

 For now, two ACE-Box kits have been developed: 

1. Base and sense 

2. Actuate  

 The ACE-Box (base and sense) is illustrated in Figure 3, with the 15 key components labelled, along with an exploded view of the main parts in Figure 4. The ACE-Boxes integrate the essential microcontrollers, electronics, sensors, and actuators needed to design, implement, and test elements of digital control algorithm development, e.g. control algorithms in real time. It bridges the gap between theory and practice, allowing learners to see how abstract concepts behave in physical systems. The ACE-Box is also available as an open-access resource, with laboratory exercises included, with details provided later in this article. The ACE-Box (labelled (1) in Figure 3) and the tray (labelled (2) in Figure 3) are manufactured using 3D printing, with the necessary files available on the project website referenced above. A list of the required components and their sources is also provided on the project website, corresponding to labels (3) to (15) in Figure 3. Due to the open-source design of ACE-Lab, the library of exercises will continue to expand, supported by contributions from both academia and industry. The ACE-Box (Actuate) is illustrated in Figure 5, with the key actuator components detailed in (a), along with some typical lab set-ups (b, c and d). Figure 6 illustrates both the ACE-Box (Base + Sense) and also ACE-Box (Actuate).    

Figure 3: The ACE-Box (Base and Sense).

 

Figure 4: Assemble of the 3D Printed ACE-Box (Base and Sense).

 

Figure 5: The ACE-Box (Actuate).

 

Figure 6: ACE-Box (Actuate) Alongside the ACE-Box (Base + Sense).

 

ACE-CORE: The methodology:

ACE-CORE is a four-step framework designed to scaffold learning from components to system-of-systems understanding: 

The methodology explicitly develops systems thinking, and integration competencies, core to both AHEP4 and INCOSE frameworks.  

ACE-CORE is intentionally designed to offer a scaffolded learning experience, allowing students to build confidence step by step as they deepen their understanding. Due to its flexible structure, students can also follow a completely practical route, i.e. avoiding the modelling and simulation. The emphasis is not on rote memorisation of theory, but on progression through understanding the fundamentals of control engineering, e.g. the components that form a feedback control system. These routes enable learners to apply concepts in practical control engineering contexts and develop genuine competence. 

 

ACE-Apply: Real-world application:

ACE-Apply is the project stage, where the skills and knowledge gained from ACE-Box and ACE-CORE are consolidated by tackling authentic challenges aligned with the expectations of industry and professional engineers, see Figure 2(b). At this stage, learners prove their mastery by addressing engineering application problems that reflect the standards of industry practice. The focus is on: 

This stage reinforces AHEP4 Themes 3 and 5, particularly:  

It also strengthens INCOSE competencies in System Realisation, Integration, and Technical Project Management, encouraging students to act as systems integrators capable of managing interfaces and dependencies across mechanical, electrical, and software domains.   

By bridging theory, simulation, and hardware using industry-standard digital tools, ACE-Apply nurtures the ability to navigate complex adaptive systems, anticipate emergent behaviour, and work collaboratively within multidisciplinary engineering ecosystems.  

 

ACE-Box activities:

Upon visiting the ACE-Lab website (www.ace-lab.co.uk), under the tab ‘ACE-Box’, the following tabs exist (with the links provided):  

The “What is the ACE-Box?” page introduces educators and students to the ACE-Box platform, outlining its purpose, key features, and practical considerations such as sourcing components and 3D-printing enclosure parts.  

The “Prior Exercises” page provides essential onboarding material designed to help users become familiar with MATLAB and Simulink. This includes links to the relevant OnRamp courses, guidance on installing the required software packages, and short tutorial videos that introduce the MATLAB and Simulink graphical user interfaces (GUIs).  

The “Base + Sense” section contains a set of introductory tutorial exercises that use the ACE-Box (Base + Sense configuration). These activities help users get started with Simulink code generation for the Arduino Uno, while working with a range of basic sensors and electronic components.  

Finally, the “Base + Sense + Actuate” section builds on the previous material by introducing actuation hardware. Using both the Base + Sense and Actuate modules, students and educators learn how to interface with and control devices such as DC motors, servomotors, and stepper motors. This section is designed to familiarise users with actuator integration and reinforce practical control engineering workflows.  

 

Example use of ACE-Box (Base + Sense):

To demonstrate the use of the ACE-Box (Base + Sense), an introductory activity is provided, i.e. the on-off blinking of an LED. Prior to this activity, through ACE-CORE, students should receive a short introduction to microcontrollers covering key concepts such as digital input/output pins, analogue pins, and pulse-width modulation (PWM). Once students are familiar with these fundamentals, they progress to the initial exercise detailed here, which is aligned with defined learning outcomes. 

Since MATLAB and Simulink are the primary software tools used with the ACE-Box, students are first guided through installing the Simulink Support Package for Arduino Hardware. After the hardware and software setup is complete, they assemble a simple circuit, see Figure 7(a), and configure a Simulink model for the first exercise, see Figure 6(b). This initial activity requires students to control the state of a digital output pin on the Arduino, switching it on and off. The Simulink model, provided in Figure 7(b), enables students to quickly build the exercise using a visual programming approach. To run the activity, they follow a sequence of steps that includes code generation, which compiles the Simulink model into embedded C code and deploys it onto the Arduino Uno microcontroller. Once completed, the LED connected to the circuit blinks on and off according to the settings of the Simulink pulse generator. A visual of the complete set-up for this initial exercise can be found in Figure 8. At this stage, students are encouraged to experiment with the pulse generator parameters in real-time, observing how changes to the signal properties immediately affect the LED’s behaviour. Scopes can also be used (see Figure 7(b)) to visualise the pulse generator’s square-wave output, including its amplitude, period, and pulse width. This hands-on interaction reinforces the link between the initial set-up and hardware implementation while deepening their understanding of microcontrollers. 

Figure 7: LED Simple Circuit (a) and Simulink for Code Generation for the on-off Blinking of an LED.

Figure 8: LED Simple Circuit Set-Up using Simulink for Code Generation for on-off Blinking of an LED.

The initial exercise is designed to familiarise students with the ACE-Box and the use of Simulink’s code generation tools. This type of activity is typical for introducing students to a new software and hardware environment. The next exercise involves using pulse width modulation (PWM) to vary the brightness of the LED. This exercise involves using additional blocks in Simulink, see Figure 8, where multiple scopes are used to visualise the signals in real-time. Once students understand the fundamental building blocks of Simulink, they can quickly progress to developing feedback control systems that meet a variety of application requirements. In the authors’ view, student familiarity with Simulink makes it a more accessible platform for designing advanced control algorithms, particularly when working with sub-systems. 

Figure 9: LED Simple Circuit Set-Up using Simulink for Code Generation Varying Brightness of an LED using Pulse Width Modulation (PWM).

Building on this foundation, a wide range of laboratory exercises can be developed using the electronic components involved in ACE-Box (Base + Sense), as illustrated in Figure 3, with the option to expand further by incorporating additional components. Examples of extended exercises include: 

In addition to sensing activities, the ACE-Box (Actuate) provides four actuators: a servomotor, a DC motor with encoder, a stepper motor, and a DC motor fan. This unit can be used independently or in combination with the Base and Sense ACE-Box to enable more advanced control experiments, such as DC motor speed control or motor control based on light intensity measurements from an LDR. 

The flexibility of the ACE-Box system ensures that the number of possible exercises is effectively unlimited, as new experiments can be designed by combining existing sensors and actuators or by integrating additional measurement devices. This also allows unique coursework assignments to be created. 

 

Summary:

The ACE-Model provides a systemic and holistic framework for practical control engineering education that: 

 

Acknowledgements:  

Dr James E. Pickering gratefully acknowledges the support from MathWorks, whose funding made this project possible. He also extends his sincere thanks to Hari Sudeskkumar for his exceptional engineering design contributions and 3D-printing work. The authors would like to thank the Project Advisory Group (PAG) for their valuable guidance throughout the development of this work.  

 

References:

 

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Toolkit: Complex Systems Toolkit.

Author: Professor Michael Ward, CEng, FIMechE, FIET (University of Strathclyde).

Topic: Defining and understanding complex systems.

Title: The role of Wicked Problems thinking to help understand the extent of engineering involvement in complex systems.

Resource type: Knowledge article.

Relevant disciplines: Any.

Keywords: Interdisciplinary; Wicked problems; Collaboration; Climate change; Decarbonisation; Research; Complexity framework; Scaffolded development framework.

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. The work on which this project has been based was funded by the Engineering and Physical Sciences Research Council of the UK through the UK FIRES Program (EP/S019111/1) and the Future Electrical Machines Manufacturing Hub (EP/S018034/1). Earlier work supported by High Value Manufacturing Catapult has also been essential in developing the basis for this work.

Downloads: A PDF of this resource will be available soon.

Who is this article for?: This article should be read by educators at all levels in higher education who are seeking an overall perspective on teaching approaches for integrating complex systems in engineering education. 

Related INCOSE Competencies: Toolkit resources are designed to be applicable to any engineering discipline, but educators might find it useful to understand their alignment to competencies outlined by the International Council on Systems Engineering (INCOSE). The INCOSE Competency Framework provides a set of 37 competencies for Systems Engineering within a tailorable framework that provides guidance for practitioners and stakeholders to identify knowledge, skills, abilities and behaviours crucial to Systems Engineering effectiveness. A free spreadsheet version of the framework can be downloaded. 

This resource relates to the Systems Thinking and Critical Thinking INCOSE competencies. 

AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Analytical Tools and Techniques (critical to the ability to model and solve problems), and Integrated / Systems Approach (essential to the solution of broadly-defined problems).  

 

Premise:

Engineering is crucial to achieving imperatives such as decarbonisation. Yet engineering typically addresses specific, well-defined challenges rather than broad, ambiguous ones. Education and practice reinforce this approach, with even postgraduate and academic engineers often focusing on problem depth over breadth. While this produces deep technical insights and tangible technological capability, it risks delaying uptake and impact unless multidisciplinary teams are involved. Recognising this gap between aspirations and execution suggests a role for structured frameworks and tools to trigger bridging activity. Wicked problem thinking is a way to understand complex problems and systems thinking, and it is related to situations which are ambiguous, contested, sometimes lacking an end state, evolving over time, requiring collaboration, adaptability, and inherently cross-disciplinary.  

 

Background:

Climate change is a helpful case in illustrating the gap between global ‘wicked’ problems, and the work of the engineer.  Engineering’s success, by underpinning industrialisation and thereby enabling mass consumption, can also be seen as its biggest failing in contributing to climate change (Datea & Chandrasekharana, 2022) and other environmental impacts. Going forward, engineers must help mitigate it, through better deployment of existing technologies and creation of new ones.  Clearly climate change is complex, spanning scientific, technological, behavioural, and political dimensions, and this complexity limits what can be achieved solely from engineering consideration. Conventional engineering methods, though highly effective at the project and programme level, risk drifting away from the original issue and producing isolated solutions with limited systemic effect. 

 

Wicked problems thinking:

Global challenges like climate change are sometimes labelled “super-wicked” problems—time-limited, caused partly by the problem-solvers, lacking central authority, and often deferred (Levin et al.). In engineering, wicked problems present a risk, because engineers are inherently tasked with addressing a part of the wider problem and often via particular approaches.  Perhaps it is not surprising, then, that engineers are trained for structured problems with clear solution methods (Schuelke-Leech, 2021). Unfortunately such approaches are rarely transferable directly to wicked contexts, except when problem structure and solution approaches align unusually well. Education reinforces this, as engineering curricula focus on well-defined challenges (Lönngren, 2017).   

At the research level, problems are often entangled, requiring both high-level perspective and detailed work. Sustainable engineering science (Seager et al., 2012) calls for ethical awareness, adaptive methods, and “interactional expertise” drawn from other disciplines. While this opens opportunities to measure cause and effect across scales, tangible short-term indicators often dominate. 

 

A structured approach to Wicked Problems:

Alford & Head’s (2017) typology places problems on a spectrum from “Tame” to “Very Wicked.” Most engineering projects are tame, even when complex, because specification and management processes reduce ambiguity. Issues like decarbonisation-related engineering research, however, often involves wicked characteristics.  This framework has recently been extended (Fehring, 2025) to allow consideration of a wider range of engineering research scenarios, Figure 1.   

 

Figure 1.  A framework for categorising complexity of engineering research scenarios (Fehring) 

 

Each of the identified scenario types is somewhat distinctive, as follows: 

 

Conclusions:

 

References:

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters. 

Toolkit: Complex Systems Toolkit.

Author: Professor Nici Zimmermann (University College London).

Topic: Illuminating complex interactions in a system through participatory modelling methods.  

Title: Using a participatory modelling approach to urban regeneration.

Resource type: Teaching activity.

Relevant disciplines: Any; civil engineering.

Keywords: Systems thinking; System dynamics; Built environment; Causal loop diagrams; Participatory modelling; Modelling or simulation; Health or wellbeing; Cognitive map.  

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 

Related INCOSE Competencies: Toolkit resources are designed to be applicable to any engineering discipline, but educators might find it useful to understand their alignment to competencies outlined by the International Council on Systems Engineering (INCOSE). The INCOSE Competency Framework provides a set of 37 competencies for Systems Engineering within a tailorable framework that provides guidance for practitioners and stakeholders to identify knowledge, skills, abilities and behaviours crucial to Systems Engineering effectiveness.  A free spreadsheet version of the framework can be downloaded.

This resource relates to the Systems Thinking, Systems Modelling and Analysis and Critical Thinking INCOSE competencies. 

AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4):  Analytical Tools and Techniques (critical to the ability to model and solve problems), and Integrated / Systems Approach (essential to the solution of broadly-defined problems). In addition, this resource addresses the AHEP themes of Design and Practical and workshop skills. 

Educational level: Intermediate; Advanced.

 

Learning and teaching notes: 

This activity is suitable for those having acquired some familiarity with complex systems and related concepts – especially causal loop diagrams, stock and flow diagrams, cognitive maps or participatory maps – who are looking for additional ideas for activities or who have a specific interest in participatory modelling. The activity is also useful at the point when students learn about interaction between different elements of a complex system or when they learn about the importance of human factors. 

Learners have the opportunity to:  

Teachers have the opportunity to: 

 

Downloads: 

 

Learning and teaching resources:

 

Overview:

This activity introduces students to a participatory systems thinking – or more specifically –  participatory modelling exercise. This is an approach used in group settings to explore complex issues and represent them via models. In this activity, students assume the roles of stakeholders involved in an urban regeneration project and take part in a group model-building workshop.  

It teaches students core principles of a participatory modelling method called group model-building or participatory system dynamics, but it can also be used to teach the underlying system structure of a specific phenomenon. This makes it well-suited for modules that contain elements of systems thinking and system dynamics (including causal loop diagramming and simulation modelling) or modules that contain an element on group facilitation and participatory methods.  

The activity is designed to run over 1.5 to 2.5 hours and is adaptable. While the current example focuses on the phenomenon of urban dynamics around the population development in a city, the activity can be reframed using a case and model from a project management, water management, energy or other sustainability-related context. 

The activity is directly aligned with systems thinking by immersing students in a participatory modelling process. It develops students’ awareness of system content and its interactions by teaching them qualitative modelling skills. It develops their skills in managing complexity and representing system elements with visual models consisting of items and their relationships depicted in causal loop diagrams and/or stock and flow diagrams. This serves to build students’ analysis skills and ability to apply systems approaches to problems. It also develops their practitioner, practical and workshop skills of collaborating with stakeholders. It does so by advancing their facilitation skills essential for collaborative systems work. This includes rules of conduct and techniques for managing a group discussion and group dynamics, making a broad range of ideas heard, prioritising them and mapping them visually. 

 

Materials or software required:

For in-person sessions, the following materials are recommended: 

If software or an online tool are used, these are used to collate concepts (variables suggested by students) and to build a diagram of their interactions. This will be projected to the in-person and/or online participants, replicating the participatory nature of in-person workshops. 

 

Detailed explanation of the activity:  

This activity introduces students to participatory modelling, an approach used in group settings to explore and understand complex issues and represent them via models. In this case, participatory modelling is introduced through a structured group model-building workshop, using a simplified version (Alfeld & Graham, 1976; Richardson, 2014) of Jay Forrester’s (1969) famous Urban Dynamics model, which sparked quite some debate because of its counter-intuitive insights. The session begins with a brief historical overview of urban growth and decline in major cities up to the 1980s (e.g. New York, Boston, London; see files under ‘Downloads’, above), before focusing on the London Docklands in London in 1981, as an example of an opportunity for urban redevelopment to counter the trend of population decline. Student groups are assigned stakeholder roles from that time, including the founder of the London Docklands Development Corporation (1–2 students), the Surrey Quays Housing Action Group (2–6 students), the London Chamber of Commerce (2–6 students) and the Greater London Council (2–6 students). Each student group receives a role sheet outlining their perspective and a small set of key variables relevant to their stakeholder position (see linked files). These variables are intentionally curated to align with the Urban Dynamics model and to ensure that collaboration is necessary to draw the interlinkages between the variables, i.e. the relevant system structure.  

A list of variables provided to the student groups via the role sheets is included below. Note that not all variables that are necessary to draw the model are included; students need to infer a few variables to train their thinking. 

Before the workshop begins, students are introduced to core concepts of participatory modelling (see linked slides), including facilitator roles (based on Richardson & Andersen, 1995) and common workshop scripts (e.g. hopes and fears, variable elicitation, voting, model building, policy option elicitation and system storytelling, as described in Scriptapedia and Andersen & Richardson, 1997). 

The workshop proceeds in three main phases: 

1. Variable elicitation: After a short introduction by the student playing the founder of the London Docklands Development Corporation into the setting and by the facilitator/teacher into the process, each group sketches behaviour-over-time graphs of their assigned variables (10 minutes). These are presented using a round-robin or nominal group technique, meaning one variable per group at a time only, and placed on a whiteboard/blackboard or digital canvas. The round-robin collection is a technique useful to foster inclusivity and avoid talking heads. Behaviour-over-time graphs rather than just variable names are useful because the final model is believed to explain a behavioural trend over time, linking model structure and dynamics. However, it is also possible to simplify by letting students just write the variable names on sheets of paper. 

2. Voting and prioritisation: To decide on a starting point for modelling, each student votes on which variables they consider to be the most important to include in the model, e.g. giving the students as many votes as there are variables on the board and freedom of how to distribute their votes. While all variables will be included in the model, the voting activity provides a basis for reflection on different priorities and students’ personal vs. their group’s perspective, after the modelling activity. 

3. Model building: The class collaboratively constructs a stock and flow diagram (see Figure 1). Stocks such as Housing Structures, Business Structures, and Population are identified, and their net rates of change are discussed. To connect the variables, some more variables need to be added such as the ratio of population to jobs, total land available, and land occupied. To help students identify these variables, the teacher can ask questions: “Population and housing are linked by a ratio. What concepts and respective variables could link the other stocks?”. Students are encouraged to identify feedback loops and classify them as reinforcing or balancing. 

It is useful to pay attention to uncovering less obvious relationships, such as the spatial competition between housing and business infrastructure. Once the diagram is complete, the facilitator reviews the model with the class, highlighting key feedback structures. 

After the modelling activity, students can be shown images of the Docklands after the redevelopment as well as urban population trends of London and other major cities until today, prompting discussion on the long-term impacts of different types of development and prioritisation of a business vs. housing focus. The session can conclude with a reflection on the participatory process and its relevance to real-world decision-making and the value of participatory modelling in complex policy environments. 

A more comprehensive version of this activity – including a more introductory group model-building exercise that teaches basic causal loop diagramming concepts and an alternative context using project management as an example – is available: https://discovery.ucl.ac.uk/id/eprint/10160261/   

 

Figure 1: Stock and flow diagram of urban dynamics (produced with Vensim software). This figure is intended for educators and serves an illustrative purpose. It provides educators with a reference for how the model built during the activity is expected to look. 

 

Note: The author was originally inspired to focus on this case by the historical accounts found on the London Docklands Development Corporation (LDDC) History Pages (http://www.lddc-history.org.uk/index.html, now inactive).  

 

References:

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Toolkit: Complex Systems Toolkit.

Authors: Dr. Natalie Wint (University College London); Dr. Mohammad Hassannezhad (University College London); Dr. Manoj Ravi (University of Leeds).

Topic: Complex systems competencies.

Title: Understanding complex systems competencies required in engineering graduates. 

Resource type: Knowledge article.

Relevant disciplines: Any.

Keywords: Systems thinking; Problem-solving; Critical thinking; Digital literacy; Modelling and simulation; Design; Project management; Life cycle; Risk; Collaboration; Communication; Professional conduct; Social responsibility.

Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 

Downloads: A PDF of this resource will be available soon.

Learning and teaching resources:

Who is this article for?: This article should be read by educators at all levels in higher education who are seeking an overall perspective on teaching approaches for integrating complex systems in engineering education. 

Related INCOSE Competencies: Toolkit resources are designed to be applicable to any engineering discipline, but educators might find it useful to understand their alignment to competencies outlined by the International Council on Systems Engineering (INCOSE). The INCOSE Competency Framework provides a set of 37 competencies for Systems Engineering within a tailorable framework that provides guidance for practitioners and stakeholders to identify knowledge, skills, abilities and behaviours crucial to Systems Engineering effectiveness. A free spreadsheet version of the framework can be downloaded. 

AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4). 

 

Premise:

This article outlines the core competencies required for engineering students to effectively engage with complex systems. Such systems involve a range of technical and non-technical components that interact in non-linear and unpredictable ways. Working effectively with such complex systems requires collaboration across engineering disciplines, as well as other fields and stakeholder groups.  

Within AHEP4, complex problems are referred to as those which “have no obvious solution and may involve wide-ranging or conflicting technical issues and/or user needs that can be addressed through creativity and the resourceful application of engineering science” (p.26). The ability to work productively with complex systems is therefore essential for engineers and helps them address problems increasingly experienced in business and society, which have many interdependent components and lack clear or stable solutions.  

The aim of this article is to provide a foundational framework that integrates the knowledge, skills and attitudes necessary for undergraduate and graduate engineering students to navigate complexity. In so doing, it serves educators, curriculum designers, and students seeking to develop the mindset and skills required to tackle the challenges of the 21st century within an increasingly volatile, uncertain, complex, and ambiguous (VUCA) world (SEFI, 2025).  

This knowledge article, informed by the INCOSE Competency Framework for Systems Engineering (INCOSE, 2018), categorises complex systems competencies into eight core competencies. These competencies encompass mindset and foundations, technical methods and tools, management and delivery, and attributes and behaviours. The description of each competency references learning outcomes (LOs) outlined in AHEP4 (Engineering Council, 2025) and the International Engineering Alliance (IEA) Graduate Attributes (2021) to establish a common baseline for all engineering graduates (see Appendix for mapping).  

 

The eight core complex systems competencies:

1. Systems thinking and problem framing 

The ability to take a holistic approach, to consider a problem from multiple perspectives and to understand how a system’s parts interact to produce emergent behaviour.  

Students must be able to understand what makes a system ‘complex’ and move beyond narrow problem-solving to identify root causes. This involves understanding fundamental Systems thinking concepts including hierarchies and interfaces (structural dimension), holism and cause-effect (dynamic dimension), lifecycles (time dimension), and multiple perspectives (perception dimension).  

Systems thinking enables engineers to anticipate ripple effects, emergent behaviours, and trade-offs, designing solutions that remain robust under uncertainty. AHEP4 requires students to “formulate and analyse complex problems to reach substantiated conclusions” (LO2) and to “apply an integrated or systems approach to the solution of complex problems” (LO6).  

2. Critical thinking 

The ability to question assumptions, evaluate evidence, apply logical reasoning, and justify decisions based on reasoned arguments and evidence.  

Navigating complex systems involves working with a variety of (often conflicting) goals, information, and data types from across discipline and stakeholder groups. Critical thinking is thus necessary to enable engineers to identify biases, avoid oversimplification and flawed reasoning, and to make ethical, transparent and evidence-informed decisions with consideration for unintended consequences. AHEP4 requires graduates to “critically evaluate technical literature and other sources of information to solve complex problems” (LO4). 

3. Simulation, modelling and data literacy 

The ability to apply scientific, mathematical, and engineering principles to model, test, and improve complex systems.  

Working with complex systems involves a range of resources including people, data and information, tools and appropriate technologies. Students must be able to create, apply and validate system models (as physical, mathematical, or logical representation of systems) and demonstrate competence in simulation and data literacy to address uncertainty and complexity at scale. This may involve using models and data to justify assumptions, explore scenarios, predict the consequences of actions, solve difference equations, conduct sensitivity and stability analysis, and predict the probability of risk.  

This aligns with several AHEP4 outcomes: “apply mathematics, statistics, and engineering principles to solve complex problems” (LO1); “apply computational and analytical techniques while recognising limitations” (LO3); and “select and critically evaluate technical literature and other data sources” (LO4).  

4. Design for complexity and changeability 

The ability to design adaptable, robust, and resilient systems across their lifecycle.  

Changes (both planned and unplanned) are inherent in complex systems. Long-term success of a system therefore requires design for resilience to first hand/internal (by the system), second hand/external (to the system) or third hand (around the system) change. Design for complexity and changeability ensures systems can evolve and integrate new capabilities across their lifecycle.  

AHEP4 requires engineers to be able to innovatively “design solutions that meet a combination of societal, user, business and customer needs” (LO5). This may involve designing systems that deliver required functions over time, including evolution, adaptability, and integration across subsystems (capability engineering), and supports evaluation of alternatives, balance competing objectives, and justify transparent decisions (decision management).  

5. Project and lifecycle management 

The ability to plan and deliver engineering activities across the system lifecycle, ensuring outcomes are delivered on time, on cost, and with integrity.  

Complex systems involve many subsystems with various purposes and lifecycles. This necessitates effective coordination and delivery processes and a focus on early planning and lasting systemic impacts. Project and lifecycle management allows for concurrent engineering (parallelisation of tasks), and verification and validation of tasks in dynamic environments. Graduates must “apply knowledge of engineering management principles, commercial context, project and change management” (AHEP4, LO15).  

This aligns with the Engineering Attribute of Project Management and Teamwork and the INCOSE Framework competencies in Lifecycle Processes, Integration, and Project Management, emphasising coordinated delivery and long-term value creation across socio-technical systems. Lifecycle awareness prevents short-term optimisation and emphasises aspects such as maintainability, whole-life value delivery and total expenditure (TOTEX) thinking, all of which support efforts towards sustainability and net-zero.  

6. Risk and uncertainty management 

The ability to identify, assess, and manage technical, social, environmental, and ethical risks at multiple levels of complex systems.  

Complex systems are inherently uncertain, with cascading risks that must be anticipated and managed proactively. Risk management enables students to quantify source and impact of uncertainties where possible and apply precaution where uncertainty is irreducible, ensuring safety, sustainability, and governance.  

AHEP4 requires graduates to “use a structured risk management process to identify, evaluate and mitigate risks (the effects of uncertainty)” (LO9), ranging from project-specific challenges to systemic threats, which need to “adopt a holistic and proportionate approach to the mitigation of security risks” (LO10).  

7. Collaboration and communication 

The ability to work effectively across disciplines, boundaries, and cultures, while conveying complex insights clearly to technical and non-technical audiences. 

Complex systems challenges cannot be solved by individuals alone and include consideration for stakeholders across industry, policy and society. Such collaborative processes involve participatory problem-solving, learning from others, inclusive communication, and negotiation and persuasion strategies, all of which necessitate emotional intelligence.  

AHEP4 expects graduates to “function effectively as an individual, and as a member or leader of a team, being able to evaluate own and team performance” (LO16). They must be able to influence stakeholder decisions, foster alignment, and shape outcomes across industry, policy, and society (AHEP4, LO17).  

8. Professional responsibility 

The ability to apply professional and societal responsibilities in decision-making, with awareness of ethical implications and long-term impacts and unintended consequences of engineered systems.  

Engineers increasingly work on complex systems that shape lives, societies, and ecosystems. Ethical responsibility ensures that technical competence aligns with social good and involves consideration for trade-offs between factors including environmental impact, affordability and social acceptance. This aligns with AHEP4, IEA, and INCOSE principles on ethics, professionalism, and leadership, ensuring engineers act responsibly within complex systems and contribute positively to society and sustainability. AHEP4 requires graduates to “identify and analyse ethical concerns and make reasoned ethical choices informed by professional codes of conduct” (LO8) and “evaluate the environmental and societal impact of solutions to complex problems” (LO7).  

 

Conclusions:

This article defines a set of eight integrated competencies that prepare engineering graduates to navigate complex systems. Together, they combine knowledge (what graduates must know), skills (what they can do), and attitudes (how they behave and think). Embedding these competencies requires project-based learning, interdisciplinary collaboration, and reflective exercises, while assessment should include portfolios, teamwork, and scenario analysis. Employers and professional bodies can reinforce these competencies through mentoring, internships, and early career development. 

By aligning with INCOSE, AHEP4, and IEA GA frameworks (see Appendix for mapping), this guidance provides an internationally consistent foundation that can be adapted to local contexts, equipping engineering graduates to address complex, interdependent challenges of the 21st century with competence, integrity, and resilience.  

 

Appendix:  

Mapping between Eight Core Competencies and Standard frameworks 

Proposed Core Competency   INCOSE * AHEP4 ** IEA GA *** 
Systems Thinking & Problem Framing ST LO2, LO6 WA2
Critical Thinking   CT LO4 WA4, WA11 
Simulation, Modelling & Data Literacy  IM, SM  LO1, LO3, LO4  WA1, WA4, WA5
Design for Complexity & Changeability  CP, DM, DF LO5  WA3 
Project & Lifecycle Management   LC, PL, CE, CP  LO15  WA10 
Risk & Uncertainty Management  CE, PL, RO  LO9, LO10 –
Collaboration & Communication   CC, TD, TL, EI  LO16, LO17  WA8, WA9 
Professional Responsibility  EI, EP  LO7, LO8  WA6, WA7 

 

* INCOSE Competency Framework, 2nd edition (2018) 

** AHEP4 Learning Outcome (LO) (2025) 

*** International Engineering Alliance (IEA) Graduate Attributes (GA) (2021) 

 

CC = Communications 

CE = Concurrent Engineering  

CP = Capability Engineering 

CT = Critical Thinking 

DF = Design For … 

DM = Decision Management 

EI = Emotional Intelligence 

EP = Ethics and Professionalism 

IM = Information Management 

LC = Life Cycle 

LO = Learning Outcome 

PL = Planning 

RO = Risk and Opportunity Management 

TD = Team Dynamics 

TL = Technical Leadership 

SM = Systems Modelling and Analysis 

ST = Systems Thinking 

WA = Washington Accord 

 

References:

 

Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.  

Let us know what you think of our website