These instructions apply to Vertex G4Plant version 2024 (30.0.0) and later.
General
Until version 2023, adding your own primary supports to the standard supports in Vertex G4Plant was, in practice, technically impossible. Vertex G4Plant 2024 introduces a library technology that allows you to create and save your own custom primary supports in a library.
You can now build your support library using dimension-driven part models, which are then used to create the actual assemblies. The item data of the supports is stored in a library-specific database that provides versatile options for controlling support behavior when supports are added to a pipeline. The instructions below describe how the standard Vertex library has been created. You can use the models we have created as templates for your own supports or start from scratch.
In any case, we recommend that you familiarize yourself with the support models provided by Vertex before you begin modeling your own supports. Models for all support types can be found in the standard section of the component library under Plant > Primarysupports and its subfolders.
Modeling a clamp and requirements
We modeled the clamp using feature-based modeling tools. Formulas and dimension tables were used to create dimension-driven models. Standard dimensions and variables were utilized when parameterizing the clamp model. As an example, see the model PSK7307 in the standard section of the component library under Plant > Primarysupports > Clamps.
The origin of the clamp model must be located at the center point of the model, as illustrated in the image on the right.
The clamp requires a guide curve along its centerline from edge to edge. We added handles (insertion points) to both ends of this centerline using the Edit named elements function. These handles enable the automatic attachment of stoppers to the clamp. The handle identifiers must be STOPPER_IN and STOPPER_OUT. See the image below for details on how the other handle properties must be defined. The blue arrows of the handles must point along the centerline, that is, in the direction of the Y-axis (see the lower clamp image on the right).
The identifier of each dimension variant stored in the dimension table is also important. Using the variables defined in these identifiers, the software can correctly vary the created supports for pipes with different outside diameters. The checkbox Selected variable values only from list must be enabled in the dimension table.
The identifier of a clamp variant must end with the nominal pipe size, separated from the rest of the identifier by a hyphen:
-
Clamp A: ...PSK7307-DN100, PSK7307-DN125, PSK7307-DN150...
NOTE! Before saving the clamp to the library, ensure that it has not been converted into a pipe component (parts’s Properties). This can happen if the handles are added in the same way as they are typically added to pipe components. If the clamp is saved to the library as a pipe component, it will not vary correctly in assemblies.
Modeling a slide support and requirements
1. Slide shoes
We modeled the slide shoe using feature-based modeling tools. Formulas and dimension tables were used to create dimension-driven models. Standard dimensions and variables were utilized when parameterizing the slide shoe model. As an example, see the model PSK7321-SHOE in the standard section of the component library under Plant > Primarysupports > Slides.
The origin of the slide shoe model must be located on the centerline of the supported pipe and centered longitudinally along the support (in the Y-axis direction). This is illustrated in the image on the right. We created a guide curve for the slide shoe at the centerline of the supported pipe (in the Y-axis direction), extending from edge to edge.
We also created a second guide curve. This curve must run in the X-axis direction (red arrow). It must be positioned at the bottom of the support so that its endpoints are located at the midpoints of the bottom edge. We added handles (insertion points) to the ends of this line, enabling the automatic attachment of lugs and guides to the slide shoe. The handle identifiers must be LUG1 and LUG2. See the image below for details on how the other handle properties must be defined. The green arrows of the handles must point downward, that is, in the negative Z-axis direction (see the image on the right).
The identifier of each dimension variant stored in the dimension table is also important. Using the variables defined in these identifiers, the software can correctly vary the created supports for pipes with different outside diameters. The checkbox Selected variable values only from list must be enabled in the dimension table.
The identifier of a slide shoe variant must end with the nominal pipe size, separated from the rest of the identifier by a hyphen:
-
Slide shoe PSK7321: ...PSK7321-SHOE-DN150, PSK7321-SHOE-DN200, PSK7321-SHOE-DN250...
2. Slide supports
A slide support is an assembly that we created from a slide shoe and clamps using assembly constraints. As an example, see the model PSK7306-A-PSK7321-DN200-500 in the standard section of the component library under Plant > Primarysupports > Slides.
First, we created a new assembly. It is recommended that the assembly be saved as a file in an appropriate location. Next, we added a new local sub-assembly. This sub-assembly can be named freely (for example, ASSEMBLY).
We added the slide shoe to the sub-assembly from the component library. Custom parts created by the user can be found in the component library under (shared). We positioned the slide shoe so that its origin coincided with the assembly origin and the assumed pipe routing direction followed the Y-axis. The slide shoe was fixed in place using assembly constraints. The default assembly planes were used when creating the constraints.
Next, we added the required number of clamps to the assembly from the component library. They were positioned in the assembly using constraints. The STOPPER_OUT handle must point away from the support origin. To allow the clamps to be rotated to different installation angles, we added an angular constraint to the assembly with the formula ANG.
Note! Lugs and stoppers must not be added to the assembly. Adding them to the assembly is handled automatically through the database.
Modeling a hanger support and requirements
1. Part models
We modeled the hanger support components using feature-based modeling tools. Formulas and dimension tables were used to create dimension-driven models. Standard dimensions and variables were utilized when parameterizing the models. As examples, see the models PSK7342-A...PSK7350 in the standard section of the component library under Plant > Primarysupports > Hangers.
Particular attention must be paid to the hanger support components whose dimensions vary on a case-by-case basis. In practice, these are the hanger rod (PSK7341) and the cross beams (PSK7346-A and PSK7346-B). These components cannot be added to an assembly directly from the component library. Instead, they must be modeled as local parts within the assembly. An example can be found by opening the model PSK7340-YK1-AR4-PSK7321-200-500 from the component library under Plant > Primarysupports > Hangers.
There is no mandatory location for the origin of a hanger support component. However, we recommend that the component geometry be referenced to the part model origin. Clamps must be modeled as described in the earlier instructions.
The identifier of each dimension variant stored in the dimension table is also important. Using the variables defined in these identifiers, the software can correctly vary the supports for pipes with different outside diameters. The checkbox Selected variable values only from list must be enabled in the dimension table.
The identifiers of hanger support components must end with the load class, separated from the rest of the identifier by a hyphen:
-
Attachment B: PSK7344-1, PSK7344-2, PSK7344-3...
-
Eye nut: PSK7347-1, PSK7347-2, PSK7347-3...
2. Hanger supports
A hanger support is an assembly built using components according to the selected upper and lower attachment types. The components are connected using assembly constraints. As examples, see the models PSK7340-YK1-AK1 and PSK7340-YK1-AR4-PSK7321-200-500 in the standard section of the component library under Plant > Primarysupports > Hangers.
First, we created a new assembly. It is recommended that the assembly be saved as a file in an appropriate location. Next, we added a new local sub-assembly. This sub-assembly can be named freely (for example, ASSEMBLY).
The first components added to the sub-assembly from the component library were the clamp or clamps. Custom parts created by the user can be found in the component library under (shared). In assemblies containing two clamps, additional components may be required when creating the assembly constraints, so these should be added at the beginning if necessary.
-
In assemblies with a single clamp, we positioned the clamp origin at the assembly origin so that the clamp centerline follows the assumed pipe routing direction (Y-axis). The clamp was fixed in place using assembly constraints. The default assembly planes were used when creating the constraints.
-
In assemblies with two clamps, the clamps were positioned around the origin according to the design requirements.
After the clamps had been added, the remaining hanger support components were inserted from the component library. Assembly constraints were used to position the components. The hanger support was assembled from the bottom upward, that is, in the positive Z-axis direction (example: PSK7340-YK1-AK1).
Note! A hanger support intended for a vertical pipe must be built so that the pipe routing direction in the assembly is along the Y-axis. This means that the other support components must also be oriented along the Y-axis (example: PSK7340-YK1-AK2). This allows the software to place the support correctly on a vertical pipe.
Each hanger support contains either one or two hanger rods. This component must be modeled locally within the assembly. Using a dimension table, we defined all variables except the length. In the support models provided by Vertex, the hanger rod is constrained to both the lower and upper attachments. The rod automatically "stretches" to the required length as the upper attachment moves. The upper attachment is constrained to the assembly XY plane using a Distance constraint with the formula LEN. The installation length (dimension L in PSK standards) is ultimately defined when the support is inserted. If the support contains two hanger rods, the formulas are LEN1 and LEN2.
The upper attachment may need to be rotated depending on the installation situation. We added an Angle constraint to the upper attachment and assigned it the formula ANG. If two upper attachments are used, the formulas are ANG1 and ANG2.
The cross beam must also be modeled locally within the support assembly because its length varies according to the beam hole spacing (example: PSK7340-YK1-AR4-PSK7321-200-500). For heavy-duty beams, the profile used may also vary depending on the application.
Modeling a foot support and requirements
Foot support A consists of a clamp, a U-beam, and an attachment plate (except structure A3).
Foot support B consists of a clamp, a tube spar, and an attachment plate (except structure B3).
Foot support C consists of a pipe and an attachment plate (except structure C3).
Of the components listed above, only the clamp comes from the component library. The other components are modeled locally. As examples, refer to the models available in the standard section of the component library under Plant > Primarysupports > Foots (for example, PSK7364-A1-DN50-500 and PSK7364-C1-DN40-500).
Structure A and B
First, we created a new assembly. It is recommended to save it as a file in an appropriate location. We then added a new local sub-assembly to it. This sub-assembly can be named freely (for example, ASSEMBLY).
A local part named SUPPORT was created in the local sub-assembly. In this model, we created a reference plane whose offset in the negative Z-axis direction from the assembly origin is defined by the formula LEN.
The first component added to the sub-assembly from the component library was the clamp. You can find the parts you create in the shared component library. We positioned the clamp by aligning its origin with the assembly origin so that the centerline of the clamp is in the direction of the assumed pipe run (Y-axis). The clamp was fixed in place using assembly constraints. The default assembly planes were utilized in the constraints.
We modeled the attachment plate as a local part on the previously defined reference plane. Variables for the attachment plate were defined using a dimension table. The last characters of the attachment plate identifier must correspond to the nominal size of the associated pipe, for example PSK7365-DN150. This allows the software to select the correct attachment plate variation. The plate was fixed in place using constraints.
Finally, we modeled the beam as a local part. Variables for the beam were defined using a dimension table. The last characters of the beam identifier must correspond to the nominal size of the associated pipe, for example PSK7364-PART1-DN150. This allows the software to select the correct beam variation. The beam was fixed in place using constraints so that it follows either the attachment plate (structures A1, A2, B1, and B2) or directly the reference plane (structures A3 and B3). The installation length (dimension L in the PSK standards) is ultimately defined when the support is inserted, based on which the beam "stretches" to its required length.
Structure C
First, we created a new assembly. It is recommended to save it as a file in an appropriate location. We then added a new local sub-assembly to it. This sub-assembly can be named freely (for example, ASSEMBLY).
A local part named SKELETON was created in the local sub-assembly. In this model, we created a reference plane whose offset in the negative Z-axis direction from the assembly origin is defined by the formula LEN.
First, we modeled the attachment plate as a local part on the previously defined reference plane. Variables for the attachment plate were defined using a dimension table. The last characters of the attachment plate identifier must correspond to the nominal size of the associated pipe, for example PSK7365-DN150. This allows the software to select the correct attachment plate variation. The plate was fixed in place using constraints.
Finally, we modeled the pipe as a local part. The curved surface at the end of the pipe must be oriented so that the Y-axis (green arrow) points away from the "cup", as shown in the image below.
Variables for the pipe were defined using a dimension table. The last characters of the pipe identifier must correspond to the nominal size of the associated pipe, for example PSK7364-PART1-DN150. This allows the software to select the correct beam variation. The beam was fixed in place using constraints so that it follows either the attachment plate (structures C1 and C2) or directly the reference plane (structure C3). The installation length (dimension L in the PSK standards) is ultimately defined when the support is inserted, based on which the beam "stretches" to its required length.
Modeling of Stoppers and Guides Requirements
1. Stoppers
We modeled the stoppers using feature-based modeling tools. Formulas and dimension tables were used to create scalable models. Dimensions and variables from the applicable standards were utilized when parameterizing the models. As an example, refer to model PSK7362-A1 located in the component library under Plant > Primarysupports > Stoppers.
The origin of the stopper model shall be located on the centerline of the supported pipe and centered along the length of the stopper (Y-axis direction). This is illustrated in the image on the right. We drew a reference line (guide curve) for the stopper along the centerline of the supported pipe (Y-axis direction), extending from one edge of the stopper to the other.
A handle (insertion point) was added to one end of the centerline using the Edit named elements function. This handle enables the stopper to be automatically connected to the clamp. The handle identifier must be STOPPER. See the image below for the required handle properties. The blue arrow of the handle must point parallel to the centerline, i.e., in the Y-axis direction.
The identifiers of the size variants stored in the dimension table are also important. Based on the variables defined in these identifiers, the software can correctly vary the created stoppers for pipes with different outside diameters. The Selected variable values only from list checkbox must be enabled in the dimension table.
The stopper identifier must end with the nominal pipe size, separated by a hyphen:
-
Stopper A1: PSK7362-A1-DN50, PSK7362-A1-DN65, PSK7362-A1-DN80...
NOTE! Before saving the model to the library, ensure that the stopper has not been converted into a pipe component (part’s Properties). This may occur if the handle is added in the same way as for pipe components. The stopper will not vary correctly in assemblies if it is saved to the library as a pipe component.
2. Lugs
We modeled the lugs using feature-based modeling tools. Dimensions and variables from the applicable standards were utilized. As examples, refer to models PSK7360-A and PSK7360-B located in the component library under Plant > Primarysupport > LugsGuides.
There is no absolute requirement for the location of the model origin for a lug. In the components created by Vertex, the origin is located at the center of the part in the Y-direction and at the "left edge" of the part in the X-direction. An example is shown in the image on the right.
A centerline was added to the models to assist with positioning the handle (insertion point). The handle was added using the Edit named elements function. This handle enables the lug to be automatically connected to the slide shoe. The handle identifier must be LUG. See the image below for the required handle properties. The blue arrow of the handle must point parallel to the centerline.
The identifiers of the size variants stored in the dimension table are also important. Based on the variables defined in these identifiers, the software can correctly vary the created lugs for pipes with different outside diameters. The Selected variable values only from list checkbox must be enabled in the dimension table.
The lug identifier must end with the nominal pipe size, separated by a hyphen:
-
Lug A: PSK7360-A-DN50, PSK7360-A-DN65, PSK7360-A-DN80...
NOTE! Before saving the model to the library, ensure that the lug has not been converted into a pipe component (parts's Properties). This may occur if the handle is added in the same way as for pipe components. The lug will not be positioned correctly in assemblies if it is saved to the library as a pipe component.
3. Guides
We modeled the guides using feature-based modeling tools. Dimensions and variables from the applicable standards were utilized. As examples, refer to models PSK7361-A and PSK7361-B located in the component library under Plant > Primarysupports > LugsGuides.
There is no absolute requirement for the location of the model origin for a guide. In the components created by Vertex, the origin is located at the center of the part in the Y-direction and at the "left edge" of the part in the X-direction. An example is shown in the image on the right.
A centerline was added to the models to assist with positioning the handle (insertion point). The handle was added using the Edit named elements function. This handle enables the guide to be automatically connected to the slide shoe. The handle identifier must be LUG. See the image below for the required handle properties. The blue arrow of the handle must point parallel to the centerline.
The size variant identifier stored in the dimension table is the same as the model identifier. The Selected variable values only from list checkbox must be enabled in the dimension table. The guide length and clearances are freely definable values when the guides are positioned in completed support assemblies on piping systems.
NOTE! Before saving the model to the library, ensure that the guide has not been converted into a pipe component (parts's Properties). This may occur if the handle is added in the same way as for pipe components. The guide will not be positioned correctly in assemblies if it is saved to the library as a pipe component.
How to build own primary support library
The easiest way to start creating your own primary support library is to use Vertex’s standard primary support componenets and assemblies.
We will publish the instructions soon.