4 ways to interface with CHEMCAD
With CC-API, any application can use CHEMCAD and a flowsheet – and even hide this fact effectively. CC-API protects your intellectual property and provides a user-centric experience in non-engineering environments.
This way, another application can use CHEMCAD’s thermodynamic calculations, i.e. access property data and thermodynamic models.
CC-API is a member of the CHEMCAD Suite, just like CC-STEADY STATE, CC-DYNAMICS, CC-THERM, CC-SAFETY NET, CC-FLASH, or CC-BATCH.
CC-API is the official Application Programming Interface for interfacing with CHEMCAD. It is endorsed by Chemstations, Inc. in Houston, TX (USA). CHEMCAD® is a registered trademark of Chemstations, Inc.
CC-API is a Capital-Gain Consultants project. It was designed in partnership with Chemstations, one of the leading suppliers of process simulation software in chemical engineering.
.NET Interface is the center piece of CC-API. It is a class library and an object model to access parameters in a CHEMCAD flowsheet.
CHEMCAD flowsheets contain unit operations, streams and physical properties. These objects have many parameters. With .NET Interface you can read any of these parameters, change their values, and write them back to the flowsheet.
Unitops and add-on manager
Custom add-ons extend the CHEMCAD functionality.
Our Add-on Manager administers DLL files for any number of unitops, enthalpy models, k value models, pipe models, or kinetic reaction rates.
You can get these from our shop or from anyone who specializes in programming DLL files.
Read more about Add-on Manager here.
Application Engineering - based on CHEMCAD
CHEMCAD is a powerful process simulator. Applications based on CHEMCAD use CHEMCAD’s power in their own logic. They provide an interface to end-users, who do not have to know how to navigate the CHEMCAD GUI, as engineers in a process engineering department usually do.
Applications based on CHEMCAD prevent users from seeing and changing the flowsheet, which underlies the simulation. They focus on the end-user’s workflow, and not on the process design engineer’s requirements.
As software engineering calls it, “an application is used to deploy a CHEMCAD flowsheet to end-users” other than the process engineers who create and modify the CHEMCAD flowsheet.
For example, users of CHEMCAD-based applications at an owner-operator can be located in operations. For operators, a CHEMCAD-based operator training system (OTS) mimics the OTS screens that operators are used to, but allows to operate a virtual plant instead of the real plant.
For example, users of CHEMCAD-based applications at an equipment manufacturer can be located in pre-sales or sales. In sales, a CHEMCAD-based equipment configuration application allows to vary stream components (with varying physical properties) and operating conditions, but proposes only a selection from the manufacturer’s catalog.
For example, users of CHEMCAD-based applications at an EPC company can be located in detailed design or 3D design. For these designers, a CHEMCAD-connected engineering system or asset life cycle management system can check the legal conformity of the planning depending on the stream conditions in the background, and without requiring the designer to apply the conformity rules manually.