User Tools

Site Tools


en:infra-convert:user:functions:coldrw_workflow

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
en:infra-convert:user:functions:coldrw_workflow [2019/03/25 10:42]
me
en:infra-convert:user:functions:coldrw_workflow [2019/03/25 11:19]
me
Line 3: Line 3:
 ^  1  ^ Create project | Create a new project and name it according to your documentation requirements. In this project, you create the inspection plans for all component variants in the next steps. | The project is created and named.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_projekt_erstellt.png?​direct&​350 |}} | ^  1  ^ Create project | Create a new project and name it according to your documentation requirements. In this project, you create the inspection plans for all component variants in the next steps. | The project is created and named.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_projekt_erstellt.png?​direct&​350 |}} |
 ^  2  ^ Creating a generic test plan | **1)** Load the drawing sheets and name the first test plan version "​Generic"​. The generic inspection plan version will contain all characteristics that may occur (in different versions) in the component variants.\\ \\ In the "​Version"​ input field, put a number in front of the version number with which you can count the variants. This is because the variant inspection plans are mapped with inspection plan versions and these must be differentiated using the "​version"​. | **1)** The drawing sheets were loaded. In the example, the generic variant is counted as "​0"​.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_generischer_pruefplan_erstellt.png?​direct&​350 |}} | ^  2  ^ Creating a generic test plan | **1)** Load the drawing sheets and name the first test plan version "​Generic"​. The generic inspection plan version will contain all characteristics that may occur (in different versions) in the component variants.\\ \\ In the "​Version"​ input field, put a number in front of the version number with which you can count the variants. This is because the variant inspection plans are mapped with inspection plan versions and these must be differentiated using the "​version"​. | **1)** The drawing sheets were loaded. In the example, the generic variant is counted as "​0"​.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_generischer_pruefplan_erstellt.png?​direct&​350 |}} |
-^  :::  ^ ::: | **2)** Stamp all relevant drawing entries. | **2)** All relevant characteristics have been created. Entries with code letters are automatically recognized as word specifications,​ "​a ​- 6H" and "​b ​±0.3" for example as follows:\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_a_01.png?​direct&​350 |}}\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_b_01.png?​direct&​350 |}} |+^  :::  ^ ::: | **2)** Stamp all relevant drawing entries. | **2)** All relevant characteristics have been created. Entries with code letters are automatically recognized as word specifications,​ "​a"​ and "​b"​ for example as follows:\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_a_01.png?​direct&​350 |}}\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_b_01.png?​direct&​350 |}} |
 ^  :::  ^ ::: | **3)** Change the characteristic properties of these characteristics so that they correspond to the first component variant for which an inspection plan is to be created. | **3)** All characteristics have been created correctly. The properties of the example characteristics have been changed as follows:\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_a_02.png?​direct&​350 |}}\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_b_02.png?​direct&​350 |}} | ^  :::  ^ ::: | **3)** Change the characteristic properties of these characteristics so that they correspond to the first component variant for which an inspection plan is to be created. | **3)** All characteristics have been created correctly. The properties of the example characteristics have been changed as follows:\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_a_02.png?​direct&​350 |}}\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_beispiel_kennzeichen_b_02.png?​direct&​350 |}} |
 ^  3  ^ Derive variant test plans | **1)** Create the variant test plans by creating test plan versions. Name them and load the drawing sheets. | **1)** The variant test plans are created, correctly named and contain the drawing sheets.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_variantenpruefplaene_angelegt.png?​direct&​350 |}} | ^  3  ^ Derive variant test plans | **1)** Create the variant test plans by creating test plan versions. Name them and load the drawing sheets. | **1)** The variant test plans are created, correctly named and contain the drawing sheets.\\ {{ :​en:​infra-convert:​user:​terms:​sammelzeichnung_variantenpruefplaene_angelegt.png?​direct&​350 |}} |
en/infra-convert/user/functions/coldrw_workflow.txt · Last modified: 2020/05/15 14:27 by me