Education in Process Systems Engineering: Why it matters more than ever and how it can be structured

Ian T Cameron, Sebastian Engell, Christos Georgakis, Norbert Asprion, Dominique Bonvin, Furong Gao, Dimitrios Gerogiorgis, Ignacio E. Grossman, Sandro Macchietto, Heinz A. Preisig, Brent R. Young

Research output: Contribution to journalArticlepeer-review

Abstract

This position paper is an outcome of discussions that took place at the third FIPSE Symposium in Rhodes, Greece, between June 20–22, 2016 (http://fi-in-pse.org). The FIPSE objective is to discuss open research challenges in topics of Process Systems Engineering (PSE). Here, we discuss the societal and industrial context in which systems thinking and Process Systems Engineering provide indispensable skills and tools for generating innovative solutions to complex problems. We further highlight the present and future challenges that require systems approaches and tools to address not only ‘grand’ challenges but any complex socio-technical challenge. The current state of Process Systems Engineering (PSE) education in the area of chemical and biochemical engineering is considered. We discuss approaches and content at both the unit learning level and at the curriculum level that will enhance the graduates’ capabilities to meet the future challenges they will be facing. PSE principles are important in their own right, but importantly they provide significant opportunities to aid the integration of learning in the basic and engineering sciences across the whole curriculum. This fact is crucial in curriculum design and implementation, such that our graduates benefit to the maximum extent from their learning.
Original languageEnglish
Pages (from-to)102-112
JournalComputers and Chemical Engineering
Volume126
Early online date6 Apr 2019
DOIs
Publication statusPublished - 12 Jul 2019

Fingerprint Dive into the research topics of 'Education in Process Systems Engineering: Why it matters more than ever and how it can be structured'. Together they form a unique fingerprint.

Cite this