User Tools

Site Tools


tutorials:vec_v1_4:documentation:6_complex_part_descriptions

Differences

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

Link to this comparison view

tutorials:vec_v1_4:documentation:6_complex_part_descriptions [2016/05/12 14:27] (current)
Line 1: Line 1:
 +~~NOTRANS~~
 +[[..:​start|Index]] - [[5_2_mating_specification| Previous ]] - [[7_external_mapping | Next ]] 
 +====== 6 Complex Part Descriptions ======
 +<​html> ​  <​head> ​    </​head> ​  <​body> ​    <​p>​ This section is about the definition of Harnesses, Modules and Assemblies. ​     </​p> ​   </​body>​ </​html>​ ===== Module =====
 +{{map> ​ ..:​diagrams:​6_1_module.jpg?​479x408 ​ }}
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 45,​171,​168,​193 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 171,​171,​294,​193 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 304,​171,​427,​193 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 283,​269,​450,​315 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 17,​276,​184,​322 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​compositionspecification|CompositionSpecification @ 136,​10,​305,​68 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 10,​353,​197,​399 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 283,​353,​470,​399 ]]
 +{{<map}}
 +<​html> ​  <​head> ​    </​head> ​  <​body> ​    <​p>​ The figure shows how a module can be defined in a 150% environment. A module basically consists of a number of PartOccurrences. In a 150%-Harness the PartOccurrences can be shared between modules. Therefore a single container is needed, which defines a PartOccurrences that belong to the Harness, independent from the Module. This is done by a CompositionSpecification. The PDM information of a module is stored in the PartVersion. The PartOccurrences belonging to the Module (the “Bill Of Material”) are defined by a PartStructureSpecification. ​     </​p> ​   </​body>​ </​html>​ ===== Harness =====
 +{{map> ​ ..:​diagrams:​6_2_harness.jpg?​486x457 ​ }}
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 24,​227,​157,​273 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 311,​220,​444,​266 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 290,​10,​457,​56 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 10,​10,​177,​56 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 150,​311,​321,​357 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 17,​115,​204,​161 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 290,​115,​477,​161 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 143,​402,​330,​448 ]]
 +{{<map}}
 +<​html> ​  <​head> ​    </​head> ​  <​body> ​    <​p>​ In the philosophy of the VEC a harness is quite the same as a module. A module is formed by a set of occurrences of components. A harness is formed by a set of occurrences of modules. This approach has the advantage that the same module can be used in different harnesses with for example different VariantConfigurations. The figure shows a simple configuration of a 150%-harness. The harness has a PartStructureSpecification,​ which defines the BOM of the Harness. This BOM contains the two PartOccurrences of the modules from the previous example. Each PartOccurrence can carry a VariantConfiguration. Since the two modules share a component, they are mutually exclusive (see the different VariantConfiguations). ​     </​p> ​   </​body>​ </​html>​ ===== Assemblies =====
 +{{map> ​ ..:​diagrams:​6_3_assemblies.jpg?​493x539 ​ }}
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 269,​175,​370,​209 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 60,​476,​161,​510 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 283,​476,​384,​510 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 283,​301,​384,​335 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partoccurrence|PartOccurrence @ 60,​294,​161,​328 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​compositionspecification|CompositionSpecification @ 10,​168,​174,​202 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partstructurespecification|PartStructureSpecification @ 241,​91,​418,​137 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partwithsubcomponentsrole|PartWithSubComponentsRole @ 17,​385,​203,​407 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partwithsubcomponentsrole|PartWithSubComponentsRole @ 241,​392,​427,​414 ]]
 +  * [[:​models:​vec_v1_1_2:​classes:​partversion|PartVersion @ 234,​14,​421,​60 ]]
 +{{<map}}
 +<​html> ​  <​head> ​    </​head> ​  <​body> ​    <​p>​ The figure above displays the usage of assemblies in the VEC. Assemblies are more complex components, which are built out of a number of other components (e.g. a prebuild wire with connectors attached to it). There are multiple reasons, why the inner structure of an assembly is relevant, but the most important one is that the inner components are needed to describe the correct usage of the assembly in the harness. For example in the case of the prebuild wire, the connectors are needed to define their position in the topology and the wire is needed to define the routing of the assembly through the topology. ​    </​p> ​     <p> In the upper area of the figure (highlighted in yellow) the master data of the assembly is shown (for simplification it contains only one PartOccurrence “B”). When the assembly is used in a Harness it is instantiated (highlighted in blue). In the example the assembly is instantiated twice (PartOccurrence ASS1 &amp; ASS2), since an assembly can be used multiple times in the same context. All subcomponents of the the assembly <​b>​must</​b>​ be instantiated as well (PartOccurrence B1 &amp; B2). These PartOccurrences carry a reference to the PartOccurrence in the Part Master Data they represent. The instantiated PartOccurrences are used to define the concrete usage of the Assembly. It is also possible, that the concrete usage has properties different to the represented occurrence. The most common use case for this is the naming of the PartOccurrence. Another use case, which is not so obvious, is for example that a prebuild wire can have only one connector attached to it and the other side is left open. When the wire is used, it is cut to needed length and then contacted on the open side. In this case the wire length of the instantiated wire would be different to master data definition of the assembly. ​     </​p> ​   </​body>​ </​html> ​
 +
 +----
 +
 +[[..:​start|Index]] - [[5_2_mating_specification| Previous ]] - [[7_external_mapping | Next ]] 
 +~~DISCUSSION~~
  
tutorials/vec_v1_4/documentation/6_complex_part_descriptions.txt · Last modified: 2016/05/12 14:27 (external edit)