Simulation Process Lifecycle

The simulation process lifecycle is used for simulation processes that do not require a formal review procedure. A simulation process is created in the In Work state.

For more details about working with simulation processes, see the SIMULIA Process Composer (Web) User's Guide.

The simulation process lifecycle includes these states:

This page discusses:

Private

The Private lifecycle state makes an object semi-hidden and modifiable only by the owner. Private simulation processes are accessible only to the owner and are not shared in the collaborative space. The owner of the simulation process can demote it to the Private state. When the owner promotes the simulation process to the In Work state, members of the collaborative space can access it.

If the simulation process is created in a public collaborative space, users with the Author baseline access role can access the simulation process as can users with a customer-specific access role that allows that you to create simulation processes.

In Process (or In Work)

The simulation process, and new versions of simulation processes, are created in the In Process state and can be modified or deleted by the owner. This state represents the simulation process while it is being developed, and all members of the collaborative space can modify the simulation process. The owner can demote the simulation process to Private or promote it to Complete; the Leader can promote the simulation process to Released.

Complete (or Frozen)

The simulation process is complete and being reviewed for approval. All members of the collaborative space have read-only access. Users can demote and promote simulation processes between the In Work and Frozen states and from the Complete to Released states without creating new versions. The Leader can demote the simulation process to Private or promote it to Released.

Released

The simulation process is available for production or delivery. Other protected collaborative spaces can access the simulation process. Released simulation processes cannot be deleted or demoted. When the simulation process is no longer valid, the owner promotes it to the Obsolete state.

You use the Released state to share the object with other collaborative spaces within the organization. The Released state is most often used with protected collaborative spaces, where the access rights change between the Frozen and Released states. In public and private collaborative spaces, there is no access difference between the Released state and the Complete state.

Obsolete

The simulation process is no longer used, is not expected to be executed, and must not be used in a collaborative space. The owner can delete the simulation process in the Obsolete state or create a new version of the simulation process.