PLM - Workflow & Lifecycle
Below is a group of How-to's that are related to the topic of 'Ready for Check in PLM' in the PLM - Workflow & Lifecycle subcategory. Click on their links to find more information on these topics.
- What is the "Ready For Check in PLM" SmarTeam command ?
- How to get access to the "Ready For Check in PLM" SmarTeam command?
- What requirement must be met to use Ready For Check in PLM?
- How to launch a Ready For Check in PLM on a SmarTeam Document?
- How does the state of CAD Documents migrated via Ready For Check in PLM change after performing a Design Verification Workflow ?
- How to deal with objects in "Ready for Check (RFC)" or "Checked" state when running a "RFC in PLM"?
- How to reset/abandon a Ready For Check in PLM?
- How does the concept of “Responsibility” relate to the Ready for Check-in PLM SmarTeam feature?
- How to deal with Integration Data and Ready for Check in PLM?
Below is a group of How-to's that are related to the topic of 'The Concept of Different Workflows' in the PLM - Workflow & Lifecycle subcategory. Click on their links to find more information on these topics.
- What is the "Ready For Check in PLM" SmarTeam command ?
- What is the concept of the Design Verification Workflow?
- What is the concept of the Fast-Track Promotion Workflow?
- What is the concept of the Assign Drawing(s) Label workflow?
- What is the purpose of creating a baseline?
- What is the concept of the Release workflow?
- What is the concept of the Withdrawal workflow?
- What is the concept of the Approved By Integration Workflow?
- What is the concept of the Release for Integration Workflow?
- What is the concept of the Valid For Integration Workflow?
Below is a group of How-to's that are related to the topic of 'Creating Workflows' in the PLM - Workflow & Lifecycle subcategory. Click on their links to find more information on these topics.
General:
- How to create and launch the Design Verification Workflow?
- What are the prerequisites for creating a Design Verification Workflow?
- How can I run the Design Verification workflow Preconditions Report ?
- How to define the set of data that needs to be approved by the Design Verification Workflow?
- How to define the assignees of the Design Verification workflow control activities ?
- How to define the list of Additional Reviewers on a given Part ?
- How to define the Approval Group responsible for the old CDD Control 3 / Approval Process ?
- What are the Control Rules allowed for validating data with the Design Verification workflow ?
- What to do in case all the activities of a workflow under edition are not visible?
- How to access the Workflow Profile Card?
- How to reassign the Design Verification Workflow activities?
- How can I discard / abandon an active Design Verification Workflow ?
- How to create the Release workflow?
- How to create and launch the Withdrawal workflow?
- How to replace an Object (CAD Document/Document/Part) with another one ?
- What is the difference between the regular Titleblock stamp and the Mini stamp?
- How is the position of the mini stamp defined?
- How to create a workflow template?
- How to validate a CAD structure where a master document is not in BOM (PLM)?
Design Collection & Drafts Container:
Drawing Workflows:
- How to validate a Drawing in the PLM Platform ?
- What are the prerequisites to perform an Assign Drawing(s) Label Workflow ?
- How to create and launch the Assign Drawing(s) Label Workflow ?
Fast Track Workflow:
Baseline:
- How to create the baseline?
- What are the consequences of generating a baseline?
- What is the baseline's behaviour?
Integration:
- How to create the Valid For Integration Workflow?
- How to create and launch the Approved By Integration Workflow?
- How to create and launch the Release For Integration Workflow?
- How to deal with Integration Data and Ready for Check in PLM?
RFC in PLM:
- How to get access to the "Ready For Check in PLM" SmarTeam command?
- What requirement must be met to use Ready For Check in PLM?
- How to launch a Ready For Check in PLM on a SmarTeam Document?
- How does the state of CAD Documents migrated via Ready For Check in PLM change after performing a Design Verification Workflow ?
- How to deal with objects in "Ready for Check (RFC)" or "Checked" state when running a "RFC in PLM"?
- How to reset/abandon a Ready For Check in PLM?
- How does the concept of “Responsibility” relate to the Ready for Check-in PLM SmarTeam feature?
Below is a group of How-to's that are related to the topic of 'Checking Workflows' in the PLM - Workflow & Lifecycle subcategory. Click on their links to find more information on these topics.
- How does the state of CAD Documents migrated via Ready For Check in PLM change after performing a Design Verification Workflow ?
- How to delegate a Design Verification Workflow activity ?
- How can I control the Design Verification workflow activities I am responsible for ?
- How can I be informed I have been assigned to a Design Verification Workflow activity ?
- How to retrieve the list of all workflows activities that I have been assigned to ?
- How to perform the CDD Control 2 in the PLM?
- How to perform the CDD Control 1 in the PLM?
- How to access the Workflow Profile Card?
- How to visualize a drawing to check it in Design Verification Workflow?
- How to reassign the Design Verification Workflow activities?
Below is a group of How-to's that are related to the topic of 'Lifecycle States & Versions' in the PLM - Workflow & Lifecycle subcategory. Click on their links to find more information on these topics.
- What is the overview of the PLM "ISO Lifecycle and Workflow" implementation?
- How to use the "Life Cycle" command to see the possible states and transitions?
- How to view other versions of an object?
- How to replace an Object (CAD Document/Document/Part) with another one ?
- What is the "History" command used for?
- How does the state of CAD Documents migrated via Ready For Check in PLM change after performing a Design Verification Workflow ?
- Versioning of non-connector-managed CAD documents
In the case a SmarTeam Item contains Integration data (a non-Master CAD Document that is a simplified representation of the 3D Master for instance), you can proceed with the Ready For Check in PLM only if you ask the Integration team to transfer you the responsibility.
Once the data is available in the PLM after "Ready for Check in PLM", you need to add the Integration Team as Additional Reviewers for the data verification process.
Additional Reviewers are used to involve additional people in the verification process of a given Part, on top of the standard assignees of the Design Verification Workflow control activities.
Assigning Additional Reviewers is typically optional. However, from methodology perspective, it becomes mandatory if the Part contains Integration models.
Depending on your Project, you will need to assign a specific reviewer group.
Please find the full list of reviewers groups in this EDMS document provided by the EN-ACE-INT section.
In most situations all master CAD documents in a CAD structure are contained in the assembly’s BOM. However, there is a valid use case where this is not true.
For example, a component in a structure will be manufactured from a standard SCEM part, such as a long tube. The component is ‘Master’, but very simple and does not require its own drawing (dimensions will be placed on the assembly drawing). Rather than putting the modified CAD part in the BOM, the SCEM part is included instead to aid purchasing and manufacturing. See the example below.
To create a BOM structure that includes the Part of CAD C instead of CAD B, we can use the ‘marked as’ attribute in the PLM. There are different properties that can be applied to this attribute which alter how Parts are shown in the parent assembly BOM. The four different options are, ‘ ‘ (default), ‘IN-BOM’, ‘Not IN-BOM’ and ‘Phantom’. For this use case we will use the ‘ ‘ (default) and ‘Not IN- BOM’ property, but you can read more about the other attributes through the link at the bottom of this ‘How-to’.
The image below shows how to alter this property in CATIA. Select the document you want to change, then open the PDM properties window by selecting the icon on the connector toolbar. From here, there is a drop-down list to select the required marked as attribute.
For our structure above, we can set CAD B to ‘Not IN-BOM’, therefore it will not be included in BOM A. CAD D is left at the default option, meaning that because it is a master document, its Part will be included in BOM A. Finally, to add Part C this must be done manually in the PLM by following the steps below, but for more information please read the FAQ linked at the bottom of this page.
- Open the profile card of Part A. Put it into edit mode and navigate to the BOM tab at the bottom.
- Click on the ‘Add Parts’ button.
- A query box will be displayed, search for Part C and press ok.
- The part will be added to the BOM table.
It will be highlighted as manually managed. In addition, the quantity and position override boxed will be ticked as they cannot be computed from the CAD structure. The position box can be left empty, meaning it will be assigned the next available position, or a value can be provided. - If required, modify the quantity value. By default, it is set to 1.
- Click done on Part A’s profile card to save the changes.
Part A’s BOM is now updated and includes the required parts. The schematic below shows the resultant BOM structure compared to the CAD structure.
It is important to note, when creating a workflow to verify the structure, Part B must be added as a root object of the workflow, else it will not be approved and remain in preparation as a baseline.
BOM management FAQ: BOM management in CATIA / PLM
If you have multiple workflows to create, that will use the same properties (e.g workflow behaviour, drawing label & reviewers) it’s possible to create a workflow template so the properties do not have to be repetitively assigned.
- Optional: Create a new part for each workflow template you would like to create. The name of the part can be used to give a description of the workflow attributes, to help you keep track of your different templates. These parts can be stored in a folder.
- Create a Workflow as standard and fill out all the desired attributes.
- Favourite the workflow using the star in the header.
- All favourited workflows can be found under the Change items in the TOC. If you un favourite them, they will be removed from this shortcut.
- When creating a workflow to validate your new documents, use the ‘apply workflow template’ button below. This opens a new window where all the favourited workflows are shown, including the various attributes so they can easily be differentiated. Press the button on the left to apply the template, and the attributes will automatically be set.
(Please note: If reviewers are set using the template they are still subject to access rights. These will be checked during the precondition workflow)
More: Design Verification Workflow FAQ
Regular Titleblock stamp:
Case 1: you are working at CERN with an official CAD tool and a PLM Connector (ex: BricsCAD, CATIA etc…).
Thus, you must generate an official CERN Titleblock on your Drawing prior to validating it. Then when a Design Verification Workflow is launched and the Drawing is Approved, this Titleblock will be stamped:
- The banner “Draft for discussion, not valid for execution” will be removed,
- The name of the person(s) who approved the drawing will be added, as well as the date of approval.
- The label defined in the Workflow (ex: For Execution, or For Tender…) will replace the default “Not Valid For Execution”.
Regular CERN Titleblock before validation.
Regular CERN Titleblock after validation.
Mini Stamp:
Case 2: you are not using a PLM Connector, does not matter if you are working at CERN or outside CERN, and you are uploading a native file only.
Examples:
- you are working at CERN with a CAD tool for which there is no connector, therefore no Titleblock Editor, but the format is supported by the PLM,
- you are working at CERN with a CAD tool for which there is a connector, but you chose to not use it,
- you are working in a sub-contractor design office with AutoCAD or BricsCAD, not on the CERN site, thus you do not have access to the CERN connectors, but you have access to the CERN PLM via the web interface,
- you are working at CERN and you receive some drawings as PDF or as DWG from another institute, a contractor etc… that you must upload in the PLM as native file,
For all these cases, it is not possible to have a CERN Titleblock on these drawings, first either because the Titleblock Editor is not available, or because there might be already a Titleblock from another company.
As a result, the regular stamping described in case 1 cannot be done.
Instead, the system will put in place a mini-stamp, which position is customizable, and that will contain the most relevant information (name of the persons who controlled the drawing, date, Label, Reference…).
Mini stamp.
Case 3: you manually upload a viewable file in addition of the native file.
In such a case, does not matter if the native file is connector managed or not, or what the native file type is, the viewable file will always be used for the stamping, with the mini stamp.
Example:
- you are working at CERN with AutoCAD or BricsCAD, and you are working with a multi-sheet drawing.
This feature is not supported by the CERN Multicad connector. But you can save the Native file (*.dwg) via the CERN connector and upload the multi-sheet drawing as a viewable file previously exported as a pdf.
Note: This is not possible for CATIA Drawings.
Native File and Viewable File properties on a CAD Document Profile Card.
- You are working with an authoring tool not supported by the PLM, you upload the native files in a zip file, then, you can upload a pdf as a viewable file.
Said otherwise, as soon as a viewable file is manually uploaded, this viewable file will be used for the stamping, and in that case, a mini stamp will be applied.
In the case that the Drawing was CERN Connector managed, and even if there is a CERN Titleblock generated with the CERN Titleblock editor, this Titleblock will not be used for the stamping, and the mini stamp only will be filled after the validation.
In such a case, it is normal that the banner “Draft for discussion, not valid for execution” remains visible on the bottom right corner.
The position of the mini stamp is defined via the “Design Office” property, that sets a specific position for the mini stamp for each drawing format (A0, A1…).
As a result, this property becomes mandatory and must be filled for any Drawing that is not Connector managed or for which there is a viewable file uploaded.
To see the position that will be applied, from the CAD Document profile go to the Detailed information tab and locate the Design Office property in the Titleblock info & 2D information block.
Click on the link to open the Design Office Profile Card, then check the positions in the relationship grid at the bottom.
The origins are the bottom left corner of the drawing and the bottom left corner of the mini stamp. The units are millimetres.
For instance, in the picture below, we can see that the position of the bottom left corner of the mini stamp for a A4 drawing that is using the EN-EL Design Office property, will be at 30mm of the left edge of the sheet, and at 252mm of the bottom edge.
The Approved By Integration Workflow can be created from the CAD Document profile card.
There are few basic pre-requirements that the CAD Document must fulfil:
- The CAD Document needs to be in “In Preparation” lifecycle state.
- A Design Code needs to be assigned to the CAD Document through the Part.
In the Profile Card of a given CAD Document, the workflow can be created by selecting the "Create New Workflow" button:
You then need to choose the assignee of the "Design Documentation Check" activity and set the group responsible of the "Review by Approval Group" activity.
Once this is done, the preparation of the Workflow can be finalized by using the "Done" button:
Then launch the Precondition Checks and if you don't meet any issues during this step, you can launch the Workflow. In case there is a precondition check that "FAILED", a specific error message is included for this precondition to help you correct the problem.
As result of the Workflow, the root object and its dependencies will evolve to Approved status.
Complete documentation: Approved By Integration Workflow FAQ
The Approved by Integration Workflow is used to approve Conceptual Drawings and 3D Models, or the envelope of a given equipment.
Its aim is the validation of positions related to functions and beam line equipment, plus reserving space for the development of future equipment.
This Workflow operates on the Integration CAD Structure, meaning the Integration Assembly itself and all its CAD Dependencies, or the Integration (Layout) Drawing.
For this reason, it can only be launched by users holding the “Senior Integrator” role.
The Approved by Integration Workflow is composed of two mandatory control activities that happen “In Series”:
- Design Documentation Check
- Review by Approval Group
Complete documentation: Approved By Integration Workflow FAQ
Manually imported CAD documents cannot be versioned automatically via a connector. Versioning must therefore be done manually in the PLM once the necessary modifications have been made to the CAD document.
The process to follow can be found in the following documentation
The Withdrawal Workflow can be created from the Profile Card of Parts, CAD Documents and Documents.
You can then generate the "Precondition Report" that checks the following pre-requirements:
1. You must hold at least one of the following Roles in the Design Code set on the Root Object:
- Contributor
- Equipment owner
- Configuration Manager
- Senior Integrator
Or be member of the Responsible Project Group.
2. That the lifecycle state of the objects affected by the Workflow is not "In Review"
Complete documentation: Withdrawal Workflow FAQ
The Withdrawal workflow is used to withdraw a Part (and all its content), a single CAD Document or a single Document.
According to ISO standards, once withdrawn, an object is no longer available as an active object.
A withdrawn version of an object must no longer be used for any purpose. This means it will not be possible to approve or version any object containing a withdrawn object.
Complete documentation: Withdrawal Workflow FAQ
The Release Workflow can be created from the Part Profile Card.
You can then generate the "Precondition Report" that checks the following pre-requirements:
- Part needs to be in "Approved" or "Replaced" lifecycle state.
- The initiator of the Workflow needs to have the Equipment Owner role in Design Code set on the Part
If all them are fulfilled, you can launch the Workflow that will make the lifecycle state of the Part evolving to Released.
Complete documentation: Release Workflow FAQ
The Release workflow is used to declare that a given Part (and its BOM) is allowed to be used for its intended purpose, meaning that the required item function has been validated.
A Part should be Released when the first asset created from this design is accepted.
Complete documentation: Release Workflow FAQ
To reset/abandon a "Ready For Check in PLM" command, you need to:
Access the object in your CS Dashboard select More Life Cycle "Reset (abandon) Ready For Check in PLM".
As a consequence:
- the selected CAD Document will be reset to the "Preliminary" state in SmarTeam, and can be edited again.
- The corresponding CAD Document in the PLM will transition to "In Preparation" and baselined (frozen).
The transition from "Ready For Check" or "Checked" to "Ready For Check in PLM" is not allowed.
When executing the "Ready For Check in PLM" command on CAD documents that are either in the "RFC" or "Checked" state, or contain dependencies in those states, the report will display:
"Current workflow state (Ready for Check/Checked) is not valid for this workflow transition"
To proceed, you need to:
- Either reject them: you can then check them out and in again to create a new minor version.
- Or wait for the second control to be performed, so that the CAD Documents transition to "Released".
The Fast-Track Promotion Workflow can be created from the Part Profile Card.
You can then generate the "Precondition Report" that checks the following pre-requirements:
- Part needs to be in "In Preparation" lifecycle state.
- The initiator of the Workflow needs to have on of the following roles in Design Code set on the Part:
- Equipment Owner
- Senior Integrator
- Configuration Manager
If all them are fulfilled, you can launch the Workflow.
Complete documentation: Fast-Track Promotion Workflow FAQ
The Fast-Track Promotion can be used to approve the Part without going through a Design Verification, in case the Master CAD Documents are in Approved/Released state.
Once the Part is Approved/Released, you may have the need to just attach to the Part additional documentation, without modifying the Master CAD Documents. In such a case, you need to:
- Version the Part.
- Attach the additional documentation needed.
- Promote the Part by using the Fast-Track Promotion, without going through a formal signature process.
Complete documentation: Fast-Track Promotion Workflow FAQ
It is not possible to validate a single CAD Document in the PLM platform.
The Design Verification Workflow acts on the Part and collects all the CAD Documents and Documents attached to the Part, plus its BOM.
Complete documentation: Design Verification Workflow FAQ
In case the Design Verification Workflow is successfully completed, the state of the objects collected by the Workflow evolves to:
- Approved in the PLM and EDMS.
- Released in SmarTeam.
The signatures performed in the PLM will be available in CDD as well.
In case one control activity is rejected, the state of the objects collected by the Workflow transitions back to:
- In Preparation in the PLM and EDMS
- Preliminary in SmarTeam
The CAD Documents can be worked on again in SmarTeam and the Ready For Check in PLM command can be re-launched on their new version.
The "Replace By" command can be accessed directly from the profile cards of the following object types:
- Parts
- CAD Documents
- Documents
The command is accessible from the "More" menu 
.
Please note that the name of this command adapts according to the object from which this command is accessed from. Below shows the "Replace CAD" functionality, available from the CAD Document profile card:
This action opens a popup window from which you will be able to search for the object that replaces the "original" one:
As a result:
- The lifecycle state of the "original" object transitions to "Replaced".
- The Profile Card of the "original" object displays information about the object that replaces it, including a direct link to this replacement Profile Card.
For more information, and explanation of the propagation of this tool, please see the following documentation.
There are few basic pre-requirements that must be fulfilled for being able to perform an Assign Drawing(s) Label Workflow.
CAD Documents set as Root Objects must:
- Be of type "Drawing".
- Be in "Approved" or "Released" lifecycle state.
- Have a Design Code assigned through the parent Part.
Additionally, the initiator of the workflow must hold the "Equipment Owner" role in all the Design Codes set on the Root Objects.
Complete documentation: Assign Drawing(s) Label Workflow FAQ
The Assign Drawing(s) Label Workflow can be created from CAD Documents of type Drawing:
Once the Change Item profile card appears, fill in its Description and choose the Drawing Label you need to apply:
You can change the Label of multiple Drawings with the same Change Item.
To do that, you simply need to add the Drawings by accessing the "Root Objects" tab from Workflow profile card, and selecting the highlighted icon:
You can then launch the Workflow by using the following icon from its Profile Card header:
Complete documentation: Assign Drawing(s) Label Workflow FAQ
The Assign Drawing(s) Label workflow is used to change the Label of one or multiple Drawings. This workflow only operates on CAD Documents of type “Drawing”.
As soon as the workflow is launched, this triggers the archiving of the Drawing, taking into account the up-to-date Label, and the generation of the viewable file.
Complete documentation: Assign Drawing(s) Label Workflow FAQ
The "Ready for check in PLM" command is available to all SmarTeam users with lifecycle modification rights. if you require access to this please get in touch with the Support Team at: plm.support@cern.ch
The aim of Ready For Check in PLM is to validate SmarTeam data via the PLM, instead of CDD.
This command needs to be executed in SmarTeam and triggers the migration of the collected data to the PLM.
The Design Verification Workflow replaces the CDD control process and it is composed by:
- Design Documentation Check: replaces the CDD Control 1
- Part Design Approval: replaces the CDD Control 2
- Review by Approval Group: replaces the CDD Control 3 / Approval Process (mandatory for QAC A Control Rule, optional otherwise)
Complete documentation:
The user must be responsible for the documents in SmarTeam and the status of the documents in SmarTeam must be Checked In or Preliminary, with the last version.
Each document must be linked to a single Item in SmarTeam and incorporate the latest changes made to all its related documents.
The drawings must have a title block created with the current TitleBlock Editor tool and a CDD number.
All documents related to the document concerned must already be in one of the following states: In Work, Preliminary or Released.
Complete documentation: Ready for Check in PLM FAQ
To launch the Ready for Check in PLM command in SmarTeam, you have to be set as "Responsible" on all the CAD Documents (Master and non-Master) attached to the Item.
Moreover, you must also take “Responsibility” for the CAD Documents attached to the Items that compose the BOM.
In other words, you must be “Responsible” of all the CAD Documents collected by the Ready for Check in PLM command (dependencies that are not already "Ready for Check in PLM" or "Released".)
Complete documentation: Ready for Check in PLM FAQ
The Preconditions Report can be run by using the 
button from the Workflow Profile Card.
All preconditions have to be “PASSED” for being able to launch the Workflow.
In case a precondition check is “FAILED”, you will receive a specific error message for this precondition so that you can easily fix the problem.
Complete documentation: Design Verification Workflow FAQ
The Design Verification workflow activates the “Control Activities” on the basis of the Control Rule defined on the Design Code set on the Root Objects and on the Parts composing their BOM (as well as on the attached Documents).
The allowed Control Rules are:
Complete documentation: Design Verification Workflow FAQ
Users holding the Contributor role on the Design Code set on the Root Objects of the Workflow can discard / abandon it when the workflow is still in "Active" state.
This implies that there is at least one control activity that must still be completed.
You can abandon the workflow by using the 
button → Discard Change Item
Complete documentation: Design Verification Workflow FAQ
You can delegate the Design Verification Workflow activity you have been assign to, to another user holding the role required for its completion (Design Reviewer or Equipment Owner).
To do that, you need to access the "Workflow Activity Completion form" --> Select the "VOTE" button --> Delegate --> choose the new assignee
Then select the "COMPLETE" button to confirm.
Complete documentation: Design Verification Workflow FAQ
Once you access the Profile Card of the Workflow, either using the hyperlink from the notification e-mail, or with My InBasket or via the notification icon on the Dasboard, click on the "VOTE NOW" button (1) available in the "Signs Off" tab, then on "VOTE", and select "Approve" or "Reject" (2).
If you decide to reject, it is mandatory to add a comment.
Then confirm with the "COMPLETE" button (3).
Complete documentation: Design Verification Workflow FAQ
As soon as the workflow is launched, the workflow assignees receive a notification email that contains:
• The reference of the workflow
• The name of the workflow activity the user is asked to vote on
• The direct link to the workflow Profile Card
• The link to the PLM “My InBasket” feature to access the list of all workflow tasks you are responsible for
The My InBasket feature is used to access the list of workflow tasks you are responsible for.
You can access this functionality from the Table of Content → Workflows → My InBasket
You can then access a each workflow Profile Card by clicking on the related hyperlink, in the "Work Item" column
Complete documentation: Design Verification Workflow FAQ
The Valid For Integration Workflow is used to freeze an Integration Assembly at a given point in time. This Workflow operates on the Integration CAD Structure only, meaning the Integration Assembly itself and all its CAD Dependencies.
For more information, please follow the document below:
The Valid For Integration Workflow can be created from CAD Documents.
There are few basic pre-requirements that the CAD Document must fulfil:
- The CAD Document needs to be in “In Preparation” lifecycle state.
- A Design Code needs to be assigned to the CAD Document through the Part.
One the Change Item window appears, then the preparation of the Workflow can be finalized by using "Done" button.
After launch the Precondition Checks and if you don't meet any issues during this step, you can launch the Workflow. In case there is a precondition check that "FAILED", a specific error message is included for this precondition to help you correct the problem.
After approving the Workflow, the impacted objects will be Baselined.
To know more details about this specific Workflow, please follow the document below:
You can define the additional reviewers in the "Additional Reviewers" tab of the Part:
Once the Part is collected by a Design Verification workflow, this will automatically assign them a control activity that must be validated to complete the workflow successfully.
Be careful!! In case you add a group as additional reviewer, an additional control activity will be assigned to each member of this group and the workflow will only be completed once every single user will have validated the control activity they have been assigned to.
Complete documentation: Design Verification Workflow
In case the Control Rule defined on the Design Code set on the Root Object is “QAC A”, the “Review by Approval Group” workflow activity is mandatory, and the system automatically suggests you the Approval Group to use. However, you can decide to assign this workflow activity to another Approval Group defined in the PLM.
For selecting/changing the Approval Group, you need to access the “Approval Group” tab from the Design Verification workflow profile card and select the following icon: 
that appears after you have clicked in the field:
Complete documentation: Design Verification Workflow FAQ
The Release For Integration Workflow can be created from a CAD Document.
There are few basics pre-requirements that the CAD Document must fulfill:
- The target CAD Document needs to be in “In Preparation” lifecycle state.
- A Design Code needs to be assigned to the CAD Document through the Part.
In the Profile Card of a given CAD Document, the workflow can be created by selecting the "Create New Workflow" button.
Then the preparation of the Workflow can be finalized by using the "Done" button.
Then launch the Precondition Checks and if you don't meet any issues during this step, you can launch the Workflow. In case there is a precondition check that "FAILED", a specific error message is included for this precondition to help you correct the problem.
The root object of the Workflow will be set to to the Approved status and the impacted objects will be frozen.
For more information, please follow the document below:
The workflow initiator has to select the people in charge of the “Design Documentation Check” and “Part Design Approval” activities from the “Reviewers” tab, available from the Design Verification workflow profile card.
Design Documentation Check: to be assigned to users holding the “Design Reviewer” role.
Part Design Approval: to be assigned to users holding the “Equipment Owner” role.
For assigning the activity to a Reviewer you need to select the icon that appears after you have clicked in the field:
Complete documentation: Design Verification Workflow FAQ
Root Objects represent the set of data you want to approve.
In case you created the Design Verification workflow from the Part profile card, this Part is automatically added as Root Object of the workflow.
It is possible to add multiple Root Objects to the workflow, so that you can approve different Parts with the same Change Item.
To do that, you simply need to access the "Root Objects" tab from the Design Verification workflow profile card, and select the following icon:
Complete documentation: Design Verification Workflow FAQ
The CDD Control 2 corresponds to the Part Design Approval activity in the new PLM platform.
The assignee of this control activity receives a notification email containing the direct link to the workflow object.
Steps:
- Select the link contained in the email to access the workflow object
- Check the objects affected by the workflow in the Impact Tree
- Click on the Vote Now button to sign off the Control activity through the Activity Completion Form
Complete documentation: Design Verification Workflow FAQ
The CDD Control 1 corresponds to the Design Documentation Check activity in the new PLM platform.
The assignee of this control activity receives a notification email containing the direct link to the workflow object.
Steps:
- Select the link contained in the email to access the workflow object
- Check the objects affected by the workflow in the Impact Tree
- Click on the Vote Now button to sign off the Control activity through the Activity Completion Form
Complete documentation: Design Verification Workflow FAQ
- Open the CS Dashboard.
- Click on "More..." from the document you want to set, then on "Life Cycle" and "Set to Ready For Check in PLM". This command can be executed on any of the CAD Documents linked to the Item, and as a result, all the CAD Documents attached to the Item will transition to RFC in PLM (this differs from the regular RFC). Please contact the support if this command is not available for you.
If you want to know more about the criteria, please see the How To below:
What requirement must be met to use Ready For Check in PLM?
Complete documentation: Ready for Check in PLM FAQ
The Release by Integration Workflow is used to validate an Integration Assembly.
This workflow operated on the Integration CAD Structure only, meaning the Integration Assembly itself and all its CAD Dependencies if it has a valid lifecycle state (Approved, Released or Replaced). Once we identify the data we need to validate, we must prepare the workflow object (Change Item) and if all the pre-condition checks are passed, then launch the workflow. This sets the “Approved” lifecycle state on the Integration Assembly and automatically completes without any additional control activity.
For more information, please follow the link below: