SmarTeam - Life Cycle
Below is a group of How-to's that are related to the topic of 'Ready for check in PLM' in the SmarTeam - Life Cycles 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 concept of “Responsibility” relate to the Ready for Check-in PLM SmarTeam feature?
- 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?
Below is a group of How-to's that are related to the topic of 'Creating Life Cycles' in the SmarTeam - Life Cycles subcategory. Click on their links to find more information on these topics.
- What is "Ready For Check" transition?
- How to use baselines in SmarTeam?
- How to use Valid For Integration in SmarTeam?
- How to use Released For Integration in SmarTeam?
- When is needed the Catch Up tool?
- How to find drawings I am responsible for and that are in Checked lifecycle state?
Ready For Check 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 to reset/abandon a Ready For Check in PLM?
- How to deal with objects in "Ready for Check (RFC)" or "Checked" state when running a "RFC in PLM"?
- How does the state of CAD Documents migrated via Ready For Check in PLM change after performing a Design Verification Workflow ?
- 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 Life Cycles' in the SmarTeam - Life Cycle subcategory. Click on their links to find more information on these topics.
Below is a group of How-to's that are related to the topic of 'Terminology' in the SmarTeam - Lifecycle subcategory. Click on their links to find more information on these topics.
- What is an overview of the "Life Cycle" implementation?
- What is "New Release" state? How to perform a "New Release"?
- What is "Ready For Check" transition?
- What is the "Ready For Check in PLM" SmarTeam command ?
- What is "Checked" state? How to perform "Set to Checked"?
- What is "Released" state? How to perform "Set to Released"?
- What is "Rejected" state? How to perform "Set to Rejected"?
- What is "Cancelled" state? How to perform "Set to Cancelled"?
Below is a group of How-to's that are related to the topic of 'Troubleshooting Life Cycles' in the SmarTeam - Life Cycles subcategory. Click on their links to find more information on these topics.
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 schematic of this example below, where the BOM structure was defined using the ‘BOM Compare tool’ in SmarTeam.
Currently a structure of this type will be blocked during the ‘Ready for Check in PLM’ action, due to the master document not being in the BOM. A warning message will be shown stating "This component in the CAD structure of the parent document is not found in the BOM".
This check is in place to aid the smooth migration of other use cases and prevent an out-of date BOM migrating to the PLM, which will affect what is validated during the sign off procedure.
To avoid causing issues to other use cases, or creating over complex migration rules, we have taken the decision to not change this rule. Therefore, if you have a structure of this type, we would kindly ask you to use CDD to validate it.
Please note, once the documents are released, they will be migrated to the PLM via simpler checks. This will be done by the CAD-Support team before all users move over permanently to the PLM. In addition, for CAD structures created natively in the PLM, there is a system in place to create a BOM of this nature. Please see here for more information on this topic.
Please be aware, if CAD B is ‘Non Master’ RFC in PLM can still be used. In this case you will be shown a warning message reminding you to attach the ‘Non Master’ document as a root object of your workflow in the PLM, else it will not be released.
This may be an issue with the access rights of your user account in SmarTeam. Please contact CAD Support using catia.support@cern.ch so they can check if this is the problem.
Here is how to proceed to easily retrieve all drawings you are responsible for and that are pending for the CDD second control signature (whose lifecycle state is currently “Checked”):
- Run a SmarTeam Query by clicking on the command “Find by attributes”:
- Then fill the following properties in the SmarTeam query menu:
- Select the document type to be queried -> CATIA Drawing
- Specify that the document must have a CERN Drawing Reference by stipulating that the value of the “CDD Number” field must not be empty -> To do so, enter > in this field.
- Select the Life Cycle state -> “Checked”
- Specify the name of the responsible for the documents to be retrieved -> Click on the button located at the right of the “Responsible” field and browse for your name.
- (Optional step) If needed you can select additional properties to be displayed in the result grid by clicking on the “Attributes…” button.
- Click on the “Run” button to proceed with the query.
- All drawings with a CDD Reference, under your responsibility and currently in “Checked” lifecycle state will be listed in the result grid:
- You can then contact the project leaders that have the appropriate rights to proceed with the signature control 2 on these drawings.
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".
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 "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
- 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
When the document is not used, or the lifecycle is not very mature it may be possible to delete, but it will not be possible due to all the documents that it depends on. In these cases, you can use the command “Cancel”. It abandons a document that is "In Work", "Preliminary" or "Rejected".
"Set to Cancel" is like deleting a document, but the differences are that:
- people are still able to see the document in the system,
- it will be possible to "Set to Cancel" a document that is used by others.
If you want to study this process, please follow the link below.
More: Cancelled
After having validated the quality of the documentation, verified that the standards are respected and that the 2D and 3D are consistent with each other, it is possible to change the state of the document (2D) to “Checked”. Until now the actions were performed in SmarTeam, validation steps must be performed in CDD.
Please follow the document below to explore more about this action.
More: Checked
The image below in the document shows the overview of the "Life Cycle" implementation.
PDF Version: Lifecycle Implementation in PDF
The "New Release" is the action of creating a new revision, in work, when the previous revision is "Released" in SmarTeam and "Archived" in CDD.
Please click on the document below if you want to understand more about this process.
More: New Release
The "Ready For Check" state means that, according to the person responsible for the project, the document:
- is complete,
- respects the design rules and methodologies,
- corresponds to the requirements and to the specifications,
- is consistent with the documents it depends on,
- is thus ready for validation.
If you want to know more details, please follow the document below.
More: Ready For Check
The "Rejected" is the status when a project is cancelled after it is checked (or even if it is "In Work" or in "Preliminary"). It may be rejected even if it is passed on to the second control after the first check, which was positive.
For more details about how to perform "Set to Rejected", please follow the document below which describes this process.
More: Rejected
"Released" is an operation which involves validating the object's feasibility and the fulfillment of the technical requirements. It must be done by an engineer.
If you want to know more how to "Set to Released", please follow the instruction which is in the link below.
More: Released
The command "Set Released For Integration" allows any user with proper access rights to release a structure (3D part or product) following a certain number of prerequisites. Once finished the process, these structures will show a green tick (in both SmarTeam and Catia) and will be usable as "Released" elements inside other assemblies.
In the document below, there are the common requisites to respect (whatever the use case is) and the procedure how to do it.
More: Released For Integration
The command “Set Valid For Integration” allows any user with proper access rights to validate a structure without drawings (3D part or product). Once finished the process, these structures will show a green tick and will be usable as “Released” elements inside other mechanical assemblies.
To know more about the procedure, please check the document which is under.
More: Valid For Integration
Due the new lifecycle implementation there will be a lot of data which state will be:
-
“Archived” in CDD.
-
“In Work” or “Preliminary” in SmarTeam.
To learn more how to use the Catch Up tool, please consult the following document.
The integration baseline feature allows to freeze any integration structure, in order to keep a trace. This feature sets all documents belonging to a structure to “Preliminary” if they are not already in this state and tags all of them as a part of a Baseline.
In order to discover more on how to use baselines in SmarTeam, please consult the following document.