Introduction
Describe the OOTB mayn piping attribute on which the Application is based to define the design rules or filter the parts
Standard
App Internal attribute name : V_Standard
Standard attributs allows to specify to which standard the specification, filter or table objects are applicable. whithin this context the system will propose only the values for the table with the given value of standard which is retreive from datasetup , LineID or from DataInformation/context panel
usualy in piping design , the important is not to check the standard value , it is to check the value of the attribute directly.
so instead of defining multiple standard, you can have only one standard value which will adress all the needed values from the various international/industrial standard.
exemple:
Standard value = "CustomTrigram"
NominalSize table values (with standard attribute="CustomTrigram") = DN40,DN100....,2in,4in, .... OD100, .... 20x2
NominalSize
App Internal attribute name :V_NominalSize
In the nominal size table, you can have size that are applicable for standardized pipe /part connection. (DN40, 2in, ...OD10mm or 10mm)
Some of the size can be applicable to a certain type of connection like in the bellow exemple where we have used code "TH1in " to specify that this value is different from a 1in size for pipe of welded connection
It can be interesting to add column in the Table (user column ar un dark grey) to describe the purpose of each code, it will be easier to remind why it has been done and for which purpose
EndStyle
App Internal attribute name : V_EndStyle
Possible values for End Style . some are Standard, other are TradeMarks or just company codification. the list can contain a mix of them
Treaded value exemple
in red here value for Threaded connections
column "Comment" is the applicability , here the supplier brand names of the parts
Note :
it could be interesting sometime de introduce additionnal Endstyle value to help system to :
- split automaticaly a piping line into spools
- orrient correctly the parts when using automatic part placement
Rating
App Internal attribute name : V_Rating
Rating attribute in 3DExperience is covering "Rating" and "Schedule"
it is use to specify standardized code for pressure class & nominal pipe thickness
Schedule definition
Schedule, abbreviated as SCH, is a measurement that denotes wall thickness of a pipe. Remember, it has no unit such as millimeter or inch as commonly misunderstood. It is a numbering system inspired by Barlow’s formula and introduced by the ASME to simplify the identification of pipe thicknesses.
By formula, Schedule Number = 1,000 x (P/S);
Where, P = working stress or service pressure in (psi) & S = allowable stress in (psi)
Rating definition
"Rating" is for about pressure – temperature rating that defines the maximum allowable working pressure of a connexion part (flange, union, ...).
- Flange classes are usually in 150#, 300#, 400#, 600#, 900#, 1500# & 2500# as per ASME B16.5 up to 24in sizes.
- threaded or socket fitting are usually in 2000, 3000 & 6000 class
Schedule / rating
there are some standard that define the correlation of fittings class with schedule / wall designation of pipe for calculation of ratings per ASME B16.11 are as follows:
Material Name
App Internal attribute name : V_MaterialName
This attribute is used in 3DExperience to define compatibility between components
This attribute can be used as per Material Category, material families or material name
If you decide to use precise material name (A53,A105, ...) then you will have to setup the compatibilty rule table and it will contains large number of lines to ensure that the system will propose the compatible compoennt even if the Material Name value is different
I would recommend to use more generic values like 316L or Stainless Steel
About PLM core Material
In addition you can set on the 3D piping model a PLM Core Material to specify the exact material with corresponding properties
About Piping Material Specification
you have to keep in mind that if you put in place multiple piping specification, the list of parts will be already somehow set (through the Part filter) to be compatible each others in term of material. so in this context it doesn't bring any value to setup precise "MaterialName" values.
At the opposite, if you work with a single specification or specification that is not linke to Material but more to a kind of system, then it can make sense to define the Material name value in a certain way that the system will be able to propose withing the Spec only the part that can fit (in therm of material) to the selected part or context
