A Methods Developer develops the Simulation Template in a dedicated ‘Protected’ collaborative space where the Simulation Analyst does not have access. When the Simulation Template is ready to use for future consuming users, the lifecycle state of this Simulation Template can be modified from the ‘Development’ state to the ‘Released’ state. Thus, a Simulation Analyst from the same organization but from other collaborative space can access it. This avoids the Simulation Analyst from the ‘Public’ collaborative space to consume a premature or incomplete Simulation Template.

This methodology can be deployed in organizations where the visibility of the Simulation Template is automatically taken care of.

Prerequisites and recommendations: The user referring to this document must be a beginner level expert in using the SIMULIA Process Composer apps. The best practice assumes beginner level expertise in the following roles: Multidisciplinary Optimization Engineer (MDO), Simulation Process Engineer (SPF).

Target Audience: Methods Developer, Simulation Analysts, Design Engineers, and so on.

In this Best Practice, you will learn about:

• Effective usage of lifecycle states using different collaborative spaces to consume the Simulation Template for different roles.
• Understand the object management in Public, Protected and Private Collaborative Space.

Looking for more such Best Practices? Get them HERE.

Please note that you will need a valid DS Passport account with appropriate user role to access Best Practice Documents. Please contact your Dassault Systèmes representative for issues related to your account.