Phenomenon-driven process design methodology : computer implementation and test usage
|Online Access:||PDF Full Text (PDF, )|
|Publish Date:|| 2005-05-20
|Thesis type:||Doctoral Dissertation
|Defence Note:||Dissertation for the degree of Doctor of Technology to be presented, with the permission of the Department of Process and Environmental Engineering of the University of Oulu, for public discussion in Auditorium L10, on September 8th, at 12 noon.
This work focuses on how to develop a generic computer tool support for a design methodology proposed for chemical engineering purposes. The applied methodology is called Phenomenon Driven Process Design methodology (PDPD), and the formal language of the methodology is called PSSP language (an acronym for Purpose, Structure, State and Performance attributes). The focus of this work is divided into two theses
1. "Multi-characteristic and creative chemical process research and development work can be supported in a systematic manner - based on PDPD - and implemented as a computer system."
2. "The use of this computer system is expected to result in comprehensive process models and modelling work with efficient documentation and data management. These are prospective advantages for any chemical engineering R&D organisation."
The developed tool is tested and evaluated by employing it in a few academic and industrial pilot projects, but the methodology has not been taken into practice by industrial companies. The introduced test cases illustrate the formalisation of research data and knowledge of both the project and process models. The test cases also illustrate a phenomenon-driven way to argument process models and project management. The analysis and argumentation of both the developed tool and the test cases are written transparently for discussion. In addition, the usage and characteristics of the meta-level tool for capturing the methodology is analysed in an open-formatted way. The use of the developed prototype application is expected:
a) to save project meeting time a nd to improve meeting performance,
b) to enhance data and knowledge exchange among project staff,
c) to improve project and process model data retrieval,
d) to ease the utilisation of various process modelling software and
e) to improve the comprehension of the linkages between numerical results, conceptual process models and the set project goals.
|Copyright information:||This publication is copyrighted. You may download, display and print it for your own personal use. Commercial use is prohibited.|