Best Practices

Concurrent Engineering with

3DEXPERIENCE

© Dassault Systèmes | Confidential Information| ref.: 3DS_Document_2020

Version 3.0 - 7/26/2023

Written by: Vedesh JAHAGIRDAR,

Mohammed Shoeb DESHMUKH
Validated by: Lionel ALVES,
Chetanchandra DURUGKAR
Edited by: Arati DESAI

CATIA 3DEXPERIENCE R2022x

 Best Practices

Executive Summary
This document demonstrates the concurrent engineering capability of
3DEXPERIENCE with the help of different use cases. It covers the use of different
commands available in the Collaborative Lifecycle App, and demonstrates the
actual application of these commands with the help of use cases.

This Best Practices document is applicable for all releases from 3DEXPERIENCE
R2022x and above.

Target audience: Designers and Administrators of 3DEXPERIENCE, ENOVIA, and

CATIA.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

2
 Best Practices

Table of contents
1. Introduction .................................................................................................................... 4
1.1. New Revision ............................................................................................................. 4
1.2. Changing Maturity ...................................................................................................... 6
1.3. Restoring Iterations .................................................................................................... 9
1.4. Duplicating Objects .................................................................................................. 10
1.5. Duplicating Objects Using Duplicate Advanced ........................................................ 12
1.6. Creating New Branch for an Object .......................................................................... 12
1.7. Locking and Unlocking Objects ................................................................................ 13
1.8. Moving Objects......................................................................................................... 15
1.9. Deleting Objects ....................................................................................................... 17
1.10. BI Essentials Query .............................................................................................. 18
2. Use Cases ................................................................................................................... 18

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

2.1. Scenario Description ................................................................................................ 18
2.2. Configuring OEM Server to Avoid Data Visibility Between Departments and
Suppliers .................................................................................................................. 18
2.3. Multiple Designers Working on the Same Assembly at OEM in the Same
Collaborative Space ................................................................................................. 20
2.4. OEM-Supplier Use Case .......................................................................................... 25
2.5. Cross Company Collaboration .................................................................................. 27
2.6. Timeline of Complete Scenario ................................................................................. 29
3. Document History ........................................................................................................ 33

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

3
 Best Practices

1. Introduction
The Collaborative Lifecycle app provides commands to manage the objects lifecycle (from
creation to deletion) and collaboration (manage concurrent access to objects).

Co-Design concept in 3DEXPERIENCE mainly depends on the commands available in this

Collaborative Lifecycle App.

• Users require the following Roles to access the Collaborative Lifecycle app:
• A CNV (Collaborative Innovation) role to access the Collaborative Lifecycle on Native
app

Only CSV (Collaborative Industry Innovator) role to access the Collaborative Lifecycle Web
App

Let us understand some of the important Lifecycle commands available in this App:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Collaborative Lifecycle App commands

1.1. New Revision

The New Revision command allows you to capture a particular evolution of an object
during its lifecycle. The new revision belongs to the same branch family as that of the source
revision. You can revise multiple objects together by multi-selecting the content and then
launching the New Revision command.

When creating a new revision, select the linked objects together to keep the link between the
new revisions of the selected objects intact.

If the connected objects are not selected together, the new content might remain connected
to the old content.

Select the New Revision command available in the Lifecycle section of the action bar.

By default, you can create a new revision only from the last revision. You must seek
permission from the Administrator to create a new revision from any revision using the
Collaborative Spaces Configuration Center widget.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

4
 Best Practices

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Setting to activate New Revision from any revision

Note: By default, this option is selected. This option allows you to revise an object from any
older revision (whether it is the BSF or not). If you clear this option, a new revision is created
from the last revision only. Selecting this option will help to reuse the existing design from
any stage.

When the New Revision dialog box appears, the colored arrows in the first column indicate
whether the object is from the last revision or from any intermediate revision:

• The green arrow displays the objects latest created revision.

• The yellow arrow indicates that the user has selected the Allow new revision from
any revision option from the Lifecycle commands. It also indicates that the user has
selected an object that is not the last revised object.
• The red arrow indicates that the user has cleared the Allow new revision from any
revision option from the lifecycle commands. It also indicates that the user has
selected an object that is not the last revised object.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

5
 Best Practices

Color arrows to identify if the object was created from the last revision

1.2. Changing Maturity

The product lifecycle manages transitions of the content from its creation until it becomes
obsolete.

There are five stages (maturity status) in a product lifecycle: Private, In_Work, Frozen,
Released, and Obsolete.

You can define the maturity status of a Product as it evolves through its lifecycle using

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

the Maturity command available in the Lifecycle section of the action bar in the
Collaborative Lifecycle App.

Click Maturity, the following Maturity dialog box appears:

Changing Maturity

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

6
 Best Practices

The following table explains different states of the Object:

Maturity State Description

For regular activities, only the person who owns the content has

Private (PRIVATE) access to this content. Only administrative access roles can
access this content for exceptional tasks.

For regular activities, an authorized user can modify this content.

In Work (IN_WORK)
By default, the new content and new revisions are at this state.

Frozen (FREEZE) For regular activities, fewer users can modify this content.

For regular activities, users cannot modify this content. If this

content belongs to a collaborative space with Protected visibility,
users who are not members of the collaborative space can also
Released (RELEASE) access the content. Same is also applicable for the content that

belongs to the collaborative space with Public visibility.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Obsolete (OBSOLETE) For regular activities, only authorized users can see this content

and replace the obsolete objects in the assemblies.

Administrator users can configure lifecycles for content.

A lifecycle consists of individual states, and the rules that control how the content moves
from one state to another.

This image shows a sample lifecycle:

Sample Lifecycle

Each box shows a lifecycle state. The lines with arrow indicate that the content can be
moved between the two connected states. A right-pointing arrow means the content can be
promoted to that state. A left-pointing arrow means the content can be demoted to that state.
The arrows between states are called transitions.

When editing lifecycles, you can:

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

7
 Best Practices

• Delete states that do not have a lock

• Restore previously deleted states
• Rename transitions
• Add or remove transitions between states
• Add or remove transition controls (rules) to transitions

You cannot add new states to a lifecycle.

Administrator users can configure lifecycles for the content using the Collaborative Spaces
Configuration Center widget.

Go to the Maturity Graph section from the Collaborative Spaces Control Center widget,
select the policy and then modify the Maturity graph as per the requirement. These

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

modifications will be applicable to the selected policy only.

Maturity Graph

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

8
 Best Practices

1.3. Restoring Iterations

You can restore an iteration of a representation to restore its previous content and attribute
values.

Iterations of a representation (3D part, 3D shape or drawing) are automatically created every
time the representation is saved. You can access prior iterations of your representations only
if your Administrator has enabled iterations.

The Administrator can set Retention policy for Iterations from the Collaborative Spaces
Control Center widget. Using this widget, the following dashboard appears:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Retention policy for iterations

The default value for the number of iterations kept per day is three. If the keeping period or
the number of iterations is zero, then the users will not be able to access any prior iterations
of the representations.

When you select the Iteration command, the Restore Iteration dialog box opens with
a list of available iterations numbered from the most recent to the oldest:

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

9
 Best Practices

Restoring Iterations © Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

User can Open Iterations, Compare Iterations, and Restore Iterations using this dialog
box.

1.4. Duplicating Objects

The Duplicate command allows you to create new content from an existing content.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

10
 Best Practices

It is possible to duplicate objects from a different collaborative space into the current
collaborative space.

You can duplicate multiple objects together by multi-selecting content and then launching the
Duplicate command.

If there are linked objects and you want to duplicate these objects, then select the linked
objects together while creating a duplicate to keep the link intact in the new duplicated
content. If the connected objects are not selected together, the new content may remain
connected to the old content.

The Duplicate command is available in the Lifecycle section of the action bar. On
clicking the Duplicate command, the following dialog box opens:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Duplicating Objects

Depending on the content the user selects, the following Propagation Options are
available:

• All Parents: select this option to duplicate the selected object with all its parent
nodes up to the root of the tab.
• Whole structure: select this option to duplicate the whole structure (all parts and
representations) under the selected objects.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

11
 Best Practices

1.5. Duplicating Objects Using Duplicate Advanced

Starting a new design involves creating the required references and representations,
building the assembly structure, producing the geometry, and managing the links.

Creating a new design can be facilitated by using any previous design as a starting point.
The Duplicate Advanced command provides some extra options as compared to the
Duplicate command, see the following image. This gives more control over the resulting
structure.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

B.I. Essentials

Out of all the options available in the above dialog box, the Optimize reuse option is
selected by default. This command uses the PLMAuthoringDefaultPropagationScope
business logic to define if the objects are excluded from the duplicating operation. By default,
the objects that are not in the same collaborative space as that of the Root Context are
removed from the scope of duplication and are reused.

1.6. Creating New Branch for an Object

You can create branches of an object to track major content modification. A branch is a
clone of an existing content that maintains a historic link to the source content.

This enables you to create a new content (with a new part number) that maintains a historic
link to the source content. You can easily interchange this content with the source or other
branches.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

12
 Best Practices

Following are few instances where you can use the New Branch command:

• Study multiple technical alternatives of a Part: User can create different branches of
the same part with different technical specifications (such as material, minor design
changes, and so on.) and study its effects. Later, the user can select any one part for
production and discard the other branches.
• For parallel development of two alternatives of a product: the user can create a new
branch and parallelly develop two different alternatives of the same product.

For creating a new branch, click the New Branch command available in the
Lifecycle Commands section and select the required Product in the following dialog box:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Creating New Branch

Click Branch, to create a new branch with a new part number in a new tab.

1.7. Locking and Unlocking Objects

In releases prior to 3DEXPERIENCE R2022x, the Lock and Unlock commands were known
as Reserve and Unreserve, respectively.

Prior to R2022x 3DEXPERIENCE R2022x

You can perform concurrent engineering with the help of Lock and Unlock commands.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

13
 Best Practices

Locking and Unlocking Objects

Security rules prevent the user from saving a modification to an object locked by another

user. The Lock and Unlock commands are available in the Collaboration
section of the action bar. Select the required objects from the specification tree and click on
the Lock (or Unlock) command. The Lock (or Unlock) dialog box opens.

3DS_Document_2020
© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020
Object selection window

When all the selected objects are reference objects, the Lock (or Unlock) dialog box will not
be displayed and the reference object will be directly locked or unlocked.

Based on the object you select, you can lock an Instance and/or Reference.

When you open an object, each object in the tree is displayed with a symbol indicating the
lock status of the reference and the instance (or blank if no lock or unlock exists). When
applicable, the Lock column in the Save dialog box displays the identity of the user who
locked the reference and/or the instance along with the corresponding lock symbol.

Icon Meaning

None The object is not locked.

The instance and the reference are locked by you.

The instance is locked by you and the reference is locked by someone else.

The instance is locked by someone else and the reference is locked by you.

The instance and reference are locked by someone else.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

14
 Best Practices

1.8. Moving Objects

Moving an object could be required in many cases, for example, when people change job
roles or when one part of a design has been completed. It might require to release an object
so that the new owner can begin to work.

In 3DEXPERIENCE R2019x, the Move command was known as Transfer Ownership.

3DEXPERIENCE R2019x 3DEXPERIENCE R2022x

This command helps the user to transfer the entire ownership of objects including products,
folders, and documents. Using this command, it is possible to move an object between

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

different collaborative spaces and organizations.

The Move command is available in the Collaboration section.

Select the required objects from the Specification tree and click the Move command. The
Move dialog box opens. Using this command, the user can select a new owner to whom the
ownership needs to be transferred.

An Incident Report dialog box appears when you select items that cannot be transferred,
listing the reason why the items cannot be transferred.

Moving Objects

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

15
 Best Practices

Note: An Administrator can control access to the Move command.

From 3DEXPERIENCE R2022x:

Collaborative Spaces Control Center > Content > Access Rules > Ownership
Operations using the Collaborative Spaces Control Center App.

From 3DEXPERIENCE R2023x:

Collaborative Spaces Control Center > Content > Permission Rules > Change

Ownership and Move Operations using the Collaborative Spaces Control Center App.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Permission Rules 3DEXPERIENCE R2022x

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

16
 Best Practices

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Permission Rules 3DEXPERIENCE R2023x

1.9. Deleting Objects

You can delete the content using the Delete command from the Lifecycle section. You can
run the Delete command from a Finder tab, an Authoring tab, or a Search Result tab.

Explore content or display it in a Search result, by activating the Collaborative Lifecycle or

Collaborative IP Management app.

Select the content you want to delete and click the Delete command.

You cannot delete:

• Content that is reserved by someone else.

• Content that is loaded in a session.
• A reference that is instantiated under another reference or in another assembly. You
must first delete all instances of a reference before you delete the reference.
• References that are EBOM-controlled.
• Content that belongs to a distant site.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

17
 Best Practices

1.10. BI Essentials Query

The B.I. Essentials is an intelligent command that provides visual display of critical
information by applying color shading and labels to the content in your session. By revealing
key information, it enables you to make decisions based upon multi-criteria data analysis on
a scale ranging from global to precise.

The B.I. Essentials command is available in the Tools section. Select an object

from the Specification tree and activate the B.I. Essentials command. The B.I. Essentials
dialog box opens. Choose the information to reveal on the selected object from the drop
down list:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

B.I. Essentials Query

Colors are applied to all objects in the tree and in the work area, accordingly.

2. Use Cases
Let us understand the industrial application of the above commands with the help of the
following use cases.

2.1. Scenario Description

An automobile OEM wants to design a new car. Different departments for example, Chassis,
Interior, Seating, Engine, Electrical, and so on are involved in the designing process.

Before moving on to the actual use cases, let us first understand the configuration of
different collaborative spaces at the OEM server.

2.2. Configuring OEM Server to Avoid Data Visibility Between

Departments and Suppliers
The 3DSpace app allows an administrator to create and manage collaborative spaces that
are dedicated to content storage and collaboration on content.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

18
 Best Practices

OEM may not want every user connecting to the server to have access to the entire content.
This is why configuring the collaborative space is one important task considering the security
reasons.

Access to the content in collaborative spaces can be public, protected, or private. Accessing
content means the ability to search for, explore, view and open the content. Depending on
the access provided, there are three types of collaborative spaces:

• Public: Content is visible to users logged into the same or different collaborative
space owned by the organization, unless the content is in the Private (PRIVATE
internal state) maturity state.
• Protected: Content in the Released or Obsolete state is visible to users logged into
same or different collaborative space owned by the organization. Access to the
content in Private, In Work, or Frozen states is protected.
• Private: Content is not visible to users that belong to other collaborative space.
Content is only accessible to the users who have explicit Private collaborative space
credentials.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

The following image shows one such example of how access to the content is secured with
the help of different types of collaborative spaces.

Organization and Collaborative Space Structure

The following image shows how the maturity state of data affects its visibility in different
types of collaborative spaces:

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

19
 Best Practices

State of Maturity Vs Collaborative Spaces

Let us take a look at the following use cases. A Seating department has been considered for
the purpose of these use cases.

2.3. Multiple Designers Working on the Same Assembly at OEM

in the Same Collaborative Space

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

The Seating department receives a clay model of the seat designed by Designers. All four
Designers are involved in designing the seat as per the responsibilities described in the
following image. The Seating department has four Designers and one Leader.

Seat Assembly

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

20
 Best Practices

At the beginning, the Leader creates a Product structure with a root product named, “Seat
A.1”.

1. Designer1 has been assigned the task to work with this clay model of the seat for
extracting the geometries and creating a wireframe structure. This wireframe will be
provided as a reference to other Designers.

Designer1 wants to restrict the access of wireframe to any other user as it is still in
the initial stage of designing.

• Solution:

Use Private maturity state for wireframe.

• Description:

Designer1 creates Wireframe A.1 sub Product under Seat A.1 root product.
As this wireframe is in its initial state, the maturity is kept as Private, so that
other Designers will not be able to search/see/refer to it until the reference

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

points are finished.

• B.I. Essentials:

Designer 1 confirms Private maturity state of the wireframe with the help of
the Design State query in BI essentials.

• The below table lists the accessibility of the skeleton wireframe at this stage:

Edit Change
Who Search
Maturity

Designer 1 Yes Yes Yes

Designer 2 No No No

Designer 3 No No No

Designer 4 No No No

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

21
 Best Practices

2. Designer1 finishes the wireframe design and reference points for further design of
the seat which can be published for other Designers. Now, the Designer wants to
make this reference point visible to other Designers and also restrict the access and
continue with the design.
• Solution:

Change the maturity of wireframe to In Work and Lock the wireframe entity.

• Description:

For other Designers to start the work, some reference points of the wireframe
are required. After finishing the design of reference points, Designer 1 will
change the maturity of wireframe to In Work so that it is visible to other
Designers. Also, Designer1 will Lock the wireframe so that other users
cannot edit it.

• B.I. Essentials:

Designer 1 confirms that the wireframe is published to In Work with the help

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

of the B.I. Essentials “Design state” query:

Seat Assembly by Designer 1

• The below table lists the accessibility of wireframe at this stage:

Edit Change
Who Search
Maturity

Designer 1 Yes Yes Yes

Designer 2 Yes No No

Designer 3 Yes No No

Designer 4 Yes No No

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

22
 Best Practices

As the wireframe is published, other Designers (Designer 2, Designer 3 and

Designer 4) can take reference geometries and start working on the creation
of Class-A Surface of the assigned sub-assemblies.

• Use of B.I. Essentials at this stage:

Before starting the design, Designers 2, 3, and 4 confirm that the products are
reserved using the BI Essentials ‘Reserve status’ query:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Seat Assembly by Designer 2

• Designers confirm the modified Assemblies and newly created components

by all the Designers using the ‘Modification Status’ BI Query:

Seat Assembly by Designer 2

3. Designer 2 saves wrong modification in data unintentionally.

• Solution:

Use the Iteration command to restore the previous iteration of 3DPart.

• Description:

Unintentionally, the Designer may save wrong modifications in the data.

Reverting back such changes is painful and a time consuming task.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

23
 Best Practices

In such a situation, the Designer can use Iteration command to restore any
previous iterations of 3DPart.

4. Designer2 has multiple head rest design options, requires to study all options and
finalize one:
• Solution:

Use the New Branch option.

• Description:

The New Branch option can be used to study multiple alternatives for the
same component.

Designer2 can create new branches of back rest assembly for alternatives of
head rest (one branch for each head rest design). The Designer can then
study all alternatives for fitments, finalize one branch, and discard all other
branches except the finalized one.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

The seat design is now complete. All Designers will now freeze the data using the
Freeze option from the Change Maturity command.

The Leader will now review the design. Before starting to review, the Leader will
confirm that all components are in Frozen state and have the latest major revision
using the Design State and Major Revision Status BI Query.

BI Essentials for Design State and Revision Status

5. While reviewing, the Leader finds some clashes between the objects.
• Solution:

Responsible Designer will now change the maturity of the required part to In
Work and start the required modifications. The Designer will freeze the part
after finishing the modifications to review the data objects again.

Now, the Leader completes the design review and releases data using the
Release option from the Change Maturity command.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

24
 Best Practices

2.4. OEM-Supplier Use Case

OEM wants to outsource manufacturing of seats to the Supplier. For this purpose, the Class-
A surface data of the designed seats is provided to the Supplier by OEM. Suppliers design
the seat frame, generate manufacturing drawings, and then proceed with seat
manufacturing. Also, the Supplier decides to outsource the design and manufacturing of the
head rest assembly to the Tier-2 Supplier.

1. OEM wants to send the Class-A surface data to the Supplier Collaborative Space.
• Solution:

Use the Move command.

• Description:

OEM Leader transfers the ownership of ‘Seat Assembly A.1’ to the Leader in
Supplier’s organization using the Move command.

• B.I. Essentials:

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Using the Context Allocation BI query, the OEM Leader confirms that the
data is now under the ownership of Supplier’s context. Also, the Supplier’s
Leader confirms that the data is in Supplier’s Current Context.

BI Essential for Context Allocation

Before starting the seat frame assembly design, the Supplier checks if the existing
seat frames can be reused or not. The Supplier finds the best match available for the
frame to start the frame assembly design.

The Supplier creates a new frame assembly having all the components from the
existing frame that can be reused and have duplicates of components that need to be
redesigned.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

25
 Best Practices

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Seat Assembly

2. The Supplier wants to create duplicate components that need to be redesigned as

per the OEM seat design.
• Solution:

Use the Duplicate Advanced command.

• Description:

The Duplicate Advanced command creates a new frame assembly and

provides the user with an option to select which components need to be
duplicated, reused, or to be excluded.

• B.I. Essentials:

The Duplication Status BI query is automatically displayed when using the

Duplicate Advanced command. It provides a visual display of the
components that will be either duplicated, reused, or excluded.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

26
 Best Practices

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

BI Essentials for Duplication Status

3. The Supplier Designer completes the design of duplicated components and changes
its Maturity state to Freeze using the Change Maturity command.
4. The Supplier’s Leader reviews the frame design and changes its aturity to Released
after review using the Change Maturity command.

2.5. Cross Company Collaboration

Supplier wants to outsource the head rest design to the Supplier Vendor. The Supplier
Leader is supposed to provide references and scope of work to the Designer from Supplier
Vendor. The Vendor then produces the required head rest.

1. Supplier wants to create the geometric references and the scope of work for the
Vendor organization.
• Solution:

Use Publication and other GSD features, like Wrapping.

• Description:

Supplier Leader creates a new subproduct ‘Headrest Assembly A.1’ and

inserts a 3DShape representation into it. Then inserts a Wrapping

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

27
 Best Practices

representation of the back rest assembly into 3DShape to avoid revealing the
complete design to the Supplier Vendor. Also, the Supplier Leader inserts the
published geometries like axes, and the bottom plane in the Part body that will
be used as a reference by the Vendor Designer.

Reference and scope of work creation for Supplier

2. Supplier wants to send the created scope of work to the Vendor Collaborative Space.

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

• Solution:

Use the Move command.

• Description:

The Leader transfers the ownership of ‘Headrest Assembly A.1’ with a

reference 3DShape to the Designer of the Vendor’s organization.

3. Vendor Designer completes the design of head rest and freezes the design using the
Freeze option available in the Change Maturity command.
4. Vendor Designer wants to submit the completed design back to the Supplier Leader.
• Solution:

Use the Move command.

• Description:

The Vendor Designer transfers the ownership of ‘Headrest Assembly A.1’

with all the newly created components under this root.

5. The Leader finishes the design review and releases the data using the Release
option from the Change Maturity command.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

28
 Best Practices

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Seat Assembly to Release

2.6. Timeline of Complete Scenario

The following color coding is used:

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

29
 Best Practices

Leader Designer 1 Designer 2 Designer 3 Designer 4

Multiple designers working on same assembly at OEM

Creates root
product Seat

A.1 and assigns

task to all 4

Designers

Creates
Wireframe A.1
sub-product
and starts
extracting
elements from

clay model

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

Once reference Create and Create and Create and
points finalized, Lock Back Rest Lock Seat Lock Bottom
changes Assembly Accessories Assembly
maturity of
Wireframe A.1
to “IN WORK”

from “Private”
status. Also
“Locks”

Wireframe A.1

Freezes the Propagates Freezes the Freezes the

data after wrong design data after data after
completion of unintentionally. completion of completion of
design Uses Iteration design design
command to
restore previous

iteration.

Uses the New

Branch option
to study
multiple
alternatives of
head rest

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

30
 Best Practices

Design and
finalizes one.

Freezes the
data after
completion of

design

Review the
design

Releases the
data

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

OEM-Supplier Use Case

Leader
Transfers
Ownership of

Seat A.1 to
Supplier Leader
Supplier Leader Supplier Designer
Finds existing frame which can be reuse

Uses ‘Duplicate Advance’ on existing frame and

selects components ‘To be reused’ and ‘To be

duplicated’

Assigns task to Supplier Designer to modify

duplicated components

Completes the required

modifications
Freezes the Product

Releases the data after review

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

31
 Best Practices

Cross Company Collaboration

Supplier Leader Vendor Designer

Creates Geometrical References and scope of work

in a 3DShape under Product

Transfers ownership of Product to its Vendor

Designs the head rest as per the

requirement

Freezes data after completion of

design

Transfers ownership back to

Supplier Leader
Releases data after review

Transfers back the complete design of seat with

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

headrest back to OEM.

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

32
 Best Practices

3. Document History
Document Revised By Changes/Notes
Date
Revision
1.0 11/15/2019 Mohammed Shoeb Original
DESHMUKH

Vedesh
JAHAGIRDAR

2.0 04/20/2022 Mohammed Shoeb - Checked

DESHMUKH applicability to
Vedesh cloud.
JAHAGIRDAR
- Updated some
command names
and dialog box
images in line with

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

the latest
3DEXPERIENCE

R2022x level.

- Section 1: Added
roles required to
access the
Collaborative
Lifecycle app.

- Section 1.2: Added

details for Data
Lifecycle changes and
Maturity Graph
customization.

- Section 1.5: Added

information about
'Optimize Reuse'.

- Section 2.3: Added a

Use case explaining
the ‘New Branch’
functionality.

- Section 2.6:
Updated the Timeline

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

33
 Best Practices

with ‘New Branch’

Use case.

3.0 7/26/2023 Vishal PATADE - Validated

the applicability
Mayur GORE
On Cloud.

- Updated some
command names and
dialog box images in
line with the
latest 3DEXPERIENC
E R2023x level.
- Section 1.8: Updated
the Moving Objects
functionality.
- Change in path for
Permission Rules on

© Dassault Systèmes | Confidential Information | ref.: 3DS_Document_2020

R2023x to control the
access
- Section 2.3:

Changed the
instances of “To
release” to “Release”
and “To Freeze” to
“Freeze”

Confidential information. Copyright Dassault Systèmes [2019 – 2023].

This document is provided for information purpose only and may be used by authorized users only for their own internal use. Any other use
without prior written authorization from Dassault Systèmes is strictly prohibited, except as may be permitted by law.

34