1. Interface Specifications www.colan.org Software Download CO-LaN Annual Meeting Leipzig, Germany 13-02-2004 13-02-2004 Unit SIG Report Celeste Colantonio (Shell International Chemicals B.V.)

2. Interface Specifications www.colan.org Software Download Unit SIG members tBen Keeping, Process Systems Enterprise (PSE) Ltd. tCostas Pantelides, PSE and Imperial College tDavid Cameron, Fantoft Process tDidier Paen, Realisation en Systemique Industrielle (RSI) tTommi Karhela, VTT tCeleste Colantonio, Shell International Chemicals B.V. tKnut W. Mathisen, Norsk Hydro (until June 2003)

3. Interface Specifications www.colan.org Software Download 2003 Unit SIG Priority tExtend existing interface to accommodate dynamic simulation  Interest in CO Modular Dynamic Simulation To integrate computationally expensive models in flowsheet simulations. Run these models on another machine and/or with special CFD code.To integrate computationally expensive models in flowsheet simulations. Run these models on another machine and/or with special CFD code. Avoid making native dynamic models for each commercial dynamic simulatorAvoid making native dynamic models for each commercial dynamic simulator t Maintain existing Unit interface, in practice done by the Interoperability SIG

4. Interface Specifications www.colan.org Software Download Summary of work performed tExtend existing interface to accommodate dynamic simulation  Defined common unit categories (Arc, Node, NetworkBoundary) and Flowsheet and Unit Calculation  Defined and specified new Methods  Extended IDL, CO component diagram  Extended UNIT Work Package, CO-CUNIT-1 V2.0  Implemented Dynamic Unit in INDISS (RSI)

5. Interface Specifications www.colan.org Software Download Modular Dynamic Simulation tThree unit categories are common:  Arc: flow module without time lag. Process equipment examples include Valve, ShortPipeSegment, Pump, Compressor, Turbine, ShortHeatExchangerSide  Node: flowsheet module with a small time lag. Examples are usually either flow mixing points like pipe junctions or header or small vessels  NetworkBoundary: either a battery limit for the simulation or a flowsheet module with a large time lag. Examples of the latter class include distillation columns, phase separators and other large vessels

6. Interface Specifications www.colan.org Software Download Flowsheet Solution and Unit Calculation Simulator (PME) tInvokes calculation tSends unit feed information tWaits for completion, sending data and providing services as requested. External UO (PMC) tRequests unit feed information from ports tRetrieves specific data from own storage tBegins calculation tRequests data and services as required during the course of the calculation. tOn completion, sets output ports and returns values to simulator

7. Interface Specifications www.colan.org Software Download Modular Dynamic Simulation tCalculation Sequence for each time step (initially assume that time steps are the same for all networks)  Pass 1/First: Pre-network calculations Module initialisation, variables that are independent of flow- pressure variables Module initialisation, variables that are independent of flow- pressure variables  Pass 2/Network: Network calculation Several iterations required Several iterations required  Pass 3/Last: Post-network calculations All variables that are dependent on, but not required for flow- pressure calculations All variables that are dependent on, but not required for flow- pressure calculations

8. Interface Specifications www.colan.org Software Download Modular Dynamic Simulation

9. Interface Specifications www.colan.org Software Download Dynamic UNIT: Interfaces and Methods Section 3.6.1 Section 3.6.2 Section 3.6.3 Section 3.6.4 NEW NEW NEW

10. Interface Specifications www.colan.org Software Download Dynamic UNIT: Component Diagram tComplete Component Diagram showing the interaction with other CO components  Fig. 3.11 (not readable here), Section 3.5 Added optional interfacesAdded optional interfacesICapeDynamicUnit ICapeNodeDynamicUnit & ICapeArcDynamicUnit to UnitOperation. ( Hint: lower left corner of figure ) to UnitOperation. ( Hint: lower left corner of figure )

11. Interface Specifications www.colan.org Software Download Implementation Dynamic Unit tPilot implementation in INDISS (RSI): Didier Paen  Dynamic Units were developed using the extended “ CAPE-OPEN Open Interface Specifications: Unit Operations ”, Ch. 3 (Ben Keeping)  4 Dynamic Units were included in a demo with steady state modules: Valves, as arcsValves, as arcs Manifolds, as nodesManifolds, as nodes BatteryLimits, as boundariesBatteryLimits, as boundaries Drum two-phase separator, as boundariesDrum two-phase separator, as boundaries Controller, as CO steady state unit operationController, as CO steady state unit operation

12. Interface Specifications www.colan.org Software Download Implementation Dynamic Unit (cont.) tResults of INDISS (RSI) demo:  The communication with other components in INDISS worked well >>> No changes were required.  The same simulator with INDISS native unit operations gives the same results.  CO unit operations can be connected with native INDISS unit operations.  There is the need to specify new numbers for COM components. Ongoing (Didier, Ben, …)

13. Interface Specifications www.colan.org Software Download Implementation Dynamic Unit (cont.) tNext steps:  Pilot implementation in D-SPICE (Fantoft Process): David Cameron  Demo including Dynamic Units in INDISS & D-SPICE Real testReal testModify?Add?…  VTT interested in interfaces for ESO. Check existing implementation and understanding Alternative is to pack ESO for modular simulation and to use existing interfaces (Ben Keeping)Alternative is to pack ESO for modular simulation and to use existing interfaces (Ben Keeping)

14. Interface Specifications www.colan.org Software Download Maintain existing Unit interface tInteroperability SIG Lessons Learnt for Unit SIG 1)Attention Unit SIG  CO standard Unit does not support “string” parameters. Suggestion: add to standard Suggestion: add to standard  Is it legal to have an Option Parameter with an empty Option list? Interop. testing shows that whereas one PME (HYSYS) allows this, another (Aspen Plus) does not. Interop. testing shows that whereas one PME (HYSYS) allows this, another (Aspen Plus) does not. Suggestion: clarify spec. for Option parameters Suggestion: clarify spec. for Option parameters

15. Interface Specifications www.colan.org Software Download Maintain existing Unit interface (cont.) 2)Attention Unit Operation developers Ü DLL for a CO Unit Operation must not be unloaded while the CO Unit is in use Suggestion: provider can control unloading of DLL by implementing the DLLCanUnloadNow. Suggestion: provider can control unloading of DLL by implementing the DLLCanUnloadNow. Ü CO Unit Operations should handle the failure of calls to optional or non-essential Material Objects methods robustly Suggestion: ?? Suggestion: ?? Dev.: Do you need an example of what happens when it fails? Dev.: Do you need an example of what happens when it fails?

16. Interface Specifications www.colan.org Software Download 3)Attention Unit Operation developers and PME vendors  CO Unit operation must be correctly registered. Must at least provide a value for Must at least provide a value for CapeDescription\Version CapeDescription\Version so that PMEs know which versions of CO interfaces they support. so that PMEs know which versions of CO interfaces they support.  PMEs should ignore Unit Operations (and other components) that do not have a version specified. Maintain existing Unit interface (cont.)

17. Interface Specifications www.colan.org Software Download 4)Other for PMEs  ATOFINA tested go:CAPE-OPEN Unit Operation wrapper in gPROMS. The available development version, at that time, did not fully support the Unit Parameter spec. Note from PSE: Note from PSE: “gO:CAPE-OPEN has full support for unit parameters as far as we know, although it is true that the example tried by Michel Pons doesn't have any parameters.” “gO:CAPE-OPEN has full support for unit parameters as far as we know, although it is true that the example tried by Michel Pons doesn't have any parameters.” PSE will try and extend it so that it does. PSE will try and extend it so that it does. go:CAPE-OPEN Unit Operation (steady state) included in the next release (gPROMS v2.3) go:CAPE-OPEN Unit Operation (steady state) included in the next release (gPROMS v2.3) Maintain existing Unit interface (cont.)

18. Interface Specifications www.colan.org Software Download Future work - 2004 tImplementation Dynamic Unit Operation in D-SPICE and gPROMS tTest interoperability: Dynamic Unit Operations provided by different PMEs tExtend standard: interfaces can evolve to integrate new types of basic components in order to handle larger resolution ( e.g. HYSYS) Components should match the resolution of the hydraulic network (pressures and flows as vbles + associated derivatives)Components should match the resolution of the hydraulic network (pressures and flows as vbles + associated derivatives) t2nd. line review for extended document “CAPE-OPEN Open Interface Specifications: Unit Operations” Who? Micheal Halloran still for YES? tMaintain existing CO Unit Interface tNew SIG members: Guidelines from CO-LaN: associate/ full membership?

19. Interface Specifications www.colan.org Software Download Thanks for your time!!!