About Simulation Processes

A simulation process contains content and simulation activities, as shown in the following figure:

A simulation process contains content and simulation activities.

Content

Content refers to the predefined categories that you use to help organize the data associated with a simulation process. For example, you can use the results category to store documents that contain the results of the simulation process or a simulation activity, such as reports and X–Y plots. See About Categories for more information.

Simulation Activities

In most cases a simulation activity uses a predefined application connector that has been assigned to an OS command step to execute an external application, such as Abaqus/Standard. A simulation activity uses download, upload, and delete steps to manage the data that are passed to the application and generated by the application. Categories describe the content of a simulation activity. A simulation activity can refer to the content of a simulation process and vice versa. See About Simulation Activities for more information.

Simulation processes also contain jobs. When you run a simulation process or a simulation activity, Process Composer creates a job and sends it to the 3DOrchestrate Distribution Server to be executed. Jobs have information related to the applications they need and the 3DOrchestrate Stations on which the applications were run. See About Jobs for more information.

Simulation processes are objects that can be managed by Process Composer. For example, you can do the following:

• Display and change the lifecycle state of the simulation process.
• Change the revision of the simulation process.
• Display the history of the simulation process.
• Specify which users have access to a simulation process.
• Store issues and images relating to the simulation process.