User Tools

Trace: • first_steps

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:training_workflows [2020/02/03 14:36] – dgroezingeren:training_workflows [2023/04/25 10:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== 7. Release process ======+====== 6. Release process ======
  
-===== 7.1 Fundamentals =====+===== 6.1 Fundamentals =====
  
 In Teamcenter, processes (workflows) are implemented for several release levels. A release of a revision in Teamcenter means that this revision can no longer be changed and receives a certain status. In addition, a release date and the releasing person are noted on the revision and a neutral format generation takes place, where the formats can be selected. Possible formats are JT, PDF, Tiff, STEP, IGES, DXF and DWG.  In Teamcenter, processes (workflows) are implemented for several release levels. A release of a revision in Teamcenter means that this revision can no longer be changed and receives a certain status. In addition, a release date and the releasing person are noted on the revision and a neutral format generation takes place, where the formats can be selected. Possible formats are JT, PDF, Tiff, STEP, IGES, DXF and DWG. 
Line 17: Line 17:
 A distinction is made between "initial release" and "subsequent release". With the first release, a revision of a part is set to the status "PS" for the first time; this does not have to be revision 00, since only the status "ER" can be set beforehand. For a follow-up release, a change is mandatory so that the changes can be tracked.  A distinction is made between "initial release" and "subsequent release". With the first release, a revision of a part is set to the status "PS" for the first time; this does not have to be revision 00, since only the status "ER" can be set beforehand. For a follow-up release, a change is mandatory so that the changes can be tracked. 
    
-===== 7.2 Engineering Release (release after "Er") =====+===== 6.2 Engineering Release (release after "Er") =====
  
 During release, certain conditions are checked without which the workflow does not start. These are conditions for a design release: During release, certain conditions are checked without which the workflow does not start. These are conditions for a design release:
Line 77: Line 77:
  
  
-==== 7.2.1 Release with Reviewer ====+==== 6.2.1 Release with Reviewer ====
  
 When releasing according to ER, you also have the option of specifying a "Reviewer", i.e. releasing according to the "4-eye-principle". To do this, select "Peer Review" instead of "Self Review" in the release dialog. When releasing according to ER, you also have the option of specifying a "Reviewer", i.e. releasing according to the "4-eye-principle". To do this, select "Peer Review" instead of "Self Review" in the release dialog.
Line 114: Line 114:
  
    
-===== 7.3 Engineering Release (release after "Er") for parts with AutoCAD drawing =====+===== 6.3 Engineering Release (release after "Er") for parts with AutoCAD drawing =====
  
 The approval process of a part with an AutoCAD drawing is essentially identical to the approval process of all other parts. The only difference is that a Tiff is always generated from the AutoCAD drawing.  The approval process of a part with an AutoCAD drawing is essentially identical to the approval process of all other parts. The only difference is that a Tiff is always generated from the AutoCAD drawing. 
Line 137: Line 137:
  
  
-===== 7.4 Serial release (release after "SE") =====+===== 6.4 Serial release (release after "SE") =====
  
 When you release a series, that is, release it to status SE, the data is transferred to SAP. The material master, structure (if available) and documents (info records and files) are transferred. When you release a series, that is, release it to status SE, the data is transferred to SAP. The material master, structure (if available) and documents (info records and files) are transferred.
Line 228: Line 228:
  
  
-===== 7.5 Changes and release after changes =====+===== 6.5 Changes and release after changes =====
  
 If a part that already has series release is to be released again after a change, a change notice is required. In general, this is also referred to as a change.  If a part that already has series release is to be released again after a change, a change notice is required. In general, this is also referred to as a change. 
Line 265: Line 265:
  
  
-==== 7.5.1 Adding participants ====+==== 6.5.1 Adding participants ====
  
 In order to be able to work on a change, you must be assigned to it as a participant. The person who created the change can assign participants with different roles to it. For the sake of simplicity, we at FFG will only use the role "Change Contributor".  In order to be able to work on a change, you must be assigned to it as a participant. The person who created the change can assign participants with different roles to it. For the sake of simplicity, we at FFG will only use the role "Change Contributor". 
Line 283: Line 283:
 Then press "OK". Then press "OK".
  
-==== 7.5.2 Solution Items and Problem Items ====+==== 6.5.2 Solution Items and Problem Items ====
  
 A change is used to track changes under a common change number. Due to changes, so-called "solutions" are created and assigned to the change. The items to be changed (i.e. those that cause "problems") are assigned to the change as "problems". In this example, revision 00 is a "problem" and revision 01 is the "solution". New parts that do not have a previous revision can also be created as part of a change.  A change is used to track changes under a common change number. Due to changes, so-called "solutions" are created and assigned to the change. The items to be changed (i.e. those that cause "problems") are assigned to the change as "problems". In this example, revision 00 is a "problem" and revision 01 is the "solution". New parts that do not have a previous revision can also be created as part of a change. 
Line 293: Line 293:
 Then you can release the "Solutions". Note that it is not the Change itself that is released, but the "Solutions" it contains.  Then you can release the "Solutions". Note that it is not the Change itself that is released, but the "Solutions" it contains. 
  
-==== 7.5.3 Start of the release process ====+==== 6.5.3 Start of the release process ====
  
 To release, select one or more revisions of the "Solutions" and press "Ctrl+P" or "Ctrl+P". To release, select one or more revisions of the "Solutions" and press "Ctrl+P" or "Ctrl+P".
Line 310: Line 310:
  
  
-==== 7.5.4 Review and Release ====+==== 6.5.4 Review and Release ====
  
 When you receive a share request, select the appropriate task in your worklist and press the "Perform" button.  The dialog for sharing opens. When you receive a share request, select the appropriate task in your worklist and press the "Perform" button.  The dialog for sharing opens.
Line 325: Line 325:
  
  
-===== 7.6 SAP transfer ("Growing bill of materials") =====+===== 6.6 SAP transfer ("Growing bill of materials") =====
  
-==== 7.6.1 Introduction ====+==== 6.6.1 Introduction ====
  
 Even during the development process, bills of material can be transferred to SAP without actually being released. In this case, parts and bills of material are not write-protected and can be processed further.  Even during the development process, bills of material can be transferred to SAP without actually being released. In this case, parts and bills of material are not write-protected and can be processed further. 
Line 339: Line 339:
  
  
-==== 7.6.2 Starting the SAP update ====+==== 6.6.2 Starting the SAP update ====
  
 Select one (or more) revision(s) to be transferred to SAP. You can do this in the Teamcenter Navigator or in the Structure Manager. Select one (or more) revision(s) to be transferred to SAP. You can do this in the Teamcenter Navigator or in the Structure Manager.
Line 353: Line 353:
 {{ :uc_approvalprocess_en_047.png?direct |}} {{ :uc_approvalprocess_en_047.png?direct |}}
  
-===== 7.7 standard and purchased parts =====+===== 6.7 standard and purchased parts =====
    
-==== 7.7.1 Basics ====+==== 6.7.1 Basics ====
    
 The concept of standard and purchased parts provides that a designer can first create such parts himself. When these parts are released, they are "handed over" to the standards body, i.e. they are assigned to the group (KV) "ST" and are also marked "Standard part = Yes" or "Standard part = Yes".  The concept of standard and purchased parts provides that a designer can first create such parts himself. When these parts are released, they are "handed over" to the standards body, i.e. they are assigned to the group (KV) "ST" and are also marked "Standard part = Yes" or "Standard part = Yes". 
Line 361: Line 361:
 The actual approver is always the standards body, i.e. a person from the group/role "ST.FFG/Design-Admin". This person also has the option of editing the part before releasing it, if necessary, or rejecting the release to the initiator. The actual approver is always the standards body, i.e. a person from the group/role "ST.FFG/Design-Admin". This person also has the option of editing the part before releasing it, if necessary, or rejecting the release to the initiator.
    
-==== 7.7.2 Release of standard and purchased parts by the design engineer ====+==== 6.7.2 Release of standard and purchased parts by the design engineer ====
  
-=== 7.7.2.1 Start of the release process ===+=== 6.7.2.1 Start of the release process ===
  
 As a designer, you create a part in the familiar way. This part belongs to your current group (KV), e.g. EI.FFG. As a designer, you create a part in the familiar way. This part belongs to your current group (KV), e.g. EI.FFG.
Line 384: Line 384:
 This concludes your work as a designer for the time being. This concludes your work as a designer for the time being.
  
-==== 7.7.3 Release of standard and purchased parts by the standard authority ====+==== 6.7.3 Release of standard and purchased parts by the standard authority ====
  
 All persons of the standards bodies, i.e. with the group/role "ST.FFG/Design-Admin", receive a release task in their "Worklist".  All persons of the standards bodies, i.e. with the group/role "ST.FFG/Design-Admin", receive a release task in their "Worklist". 
Line 398: Line 398:
 In the following dialog press on the "Decision" entry in the line with your account.  In the following dialog press on the "Decision" entry in the line with your account. 
  
-=== 7.7.3.1 Release / Approve ===+=== 6.7.3.1 Release / Approve ===
  
 Press "Approve". Press "Approve".
Line 428: Line 428:
 {{ :uc_handling_standard_purch_parts_en_009.png?direct |}} {{ :uc_handling_standard_purch_parts_en_009.png?direct |}}
    
-=== 7.7.3.2 Reject ===+=== 6.7.3.2 Reject ===
    
 If release is not possible from the standards body, the workflow can be rejected with the "Reject" decision to the designer. If release is not possible from the standards body, the workflow can be rejected with the "Reject" decision to the designer.
Line 458: Line 458:
 Note: If you select "Cancel | Cancel", the workflow is terminated in a controlled manner and no release takes place. The part(s) can later be re-set in the release process. Note: If you select "Cancel | Cancel", the workflow is terminated in a controlled manner and no release takes place. The part(s) can later be re-set in the release process.
    
-==== 7.7.4 Release of standard parts and purchased parts the standard position ====+==== 6.7.4 Release of standard parts and purchased parts the standard position ====
    
 If standard and purchased parts have been created by the standards body itself, they can be released with a simplified workflow. If standard and purchased parts have been created by the standards body itself, they can be released with a simplified workflow.

Page Tools

Site Tools