Studies On Second Development Interface Method For Process Simulation Software

With the development of process systems engineering and computer technology, process simulation technology grows up day after day. At present, the most representative general process simulation software is Aspen Plus of ASPEN TECH Corporation and PRO/â…¡ of SIMSCI Corporation overseas, the best one in our country is the ECSS system developed by the computer and chemical engineering research institute in Qingdao University of Science&Technology.However, the production of simulative software has its limit after all and with the time gone and the development of the research on theory , we must add new design thought and academic research achievement into the system, and unceasingly expand and renew its content to enhance the system performance. This work is not the mission of the software developer alone. The users should also take part in it and develop the software for the second time using their knowledge and experience. Simultaneous, because of the complexity and concrete of certain chemical production processes, the function modules of simulative software are impossible to simulate all actual processes. This also request the user develop the user model based on actually process. The above two points propose the second development interface topic for the software developer.Aspen Plus and PRO/â…¡ already have self-contained second development interfaces, but the users know less about them. The ECSS system does not have the sccond development interfaces before now. This limits its development in great degree. Therefore it is necessary to launch the research on second development method of above software. The main research content of this article is:(1)1 have used Aspen Plus and consulted correlation literature, in order to understand the function and the unique feature of the software fully. Based on above work, I explore the second development method of this software, the concrete work includes: discuss and summarize adding step and method of its user model, the user model specification, as well as the way in which user model is called.