[QUOTE=pitch;61771]I still do not understand the need for the majority of the Datasets being used in Piping.
Why have a reference to an RPRO that points you to a parameter when you can point straight to the parameter?
Diferent if you want to apply some sort of calculation to get the answer eg (0.75 * parameter x)
Just adding extra work in my opinion.Flanged components are the perfect place to use DKEY to define Bolt Length. As you know, in order for new bolting to work you have to have all flanged components use the same parameter number to define the bolt length/flange thickness. At my job, when I got thrown into cats&specs, there are many flanged components already built in our catalog and they are all built by different people. Since they used to use old bolting the flange thickness parameter my be para2 for some components, para5 for others and so on. In order to make these components work I would have to shuffle the order of the paras to get fthk where we want it which is a huge pain. Much easier to just create a DKEY in each component category named BLEN for example and then map it to the parameter already used for the flange thickness. Then just set the BTHK attribute of your BTSE elements to (ATTRIB RPRO BLEN) and you are good to go. =)
This brings me to a question I have for you experts. You can set the BDIA BTYP and BTHK of the BTSE in this way but you cannot set the NOFF. Why? It is creating a problem for me. Does anyone know of a way around this? I need to pull the number of bolts from the component SCOM and I can't find a way to do it. I can use the BSEL as a workaround for now but it is not a final solution. The major problem is how do you have two SPCO in the same bolt spec that have the same BDIA but different NOFF? For example a 4xM20 and an 8xM20 pattern in the same bolt spec? You can use BSEL but what if you have both patterns on the same valve? Can't set BSEL on one valve to two different values. =(
[QUOTE=pitch;61771]I still do not understand the need for the majority of the Datasets being used in Piping.
Why have a reference to an RPRO that points you to a parameter when you can point straight to the parameter?
Diferent if you want to apply some sort of calculation to get the answer eg (0.75 * parameter x)
Just adding extra work in my opinion.Flanged components are the perfect place to use DKEY to define Bolt Length. As you know, in order for new bolting to work you have to have all flanged components use the same parameter number to define the bolt length/flange thickness. At my job, when I got thrown into cats&specs, there are many flanged components already built in our catalog and they are all built by different people. Since they used to use old bolting the flange thickness parameter my be para2 for some components, para5 for others and so on. In order to make these components work I would have to shuffle the order of the paras to get fthk where we want it which is a huge pain. Much easier to just create a DKEY in each component category named BLEN for example and then map it to the parameter already used for the flange thickness. Then just set the BTHK attribute of your BTSE elements to (ATTRIB RPRO BLEN) and you are good to go. =)
This brings me to a question I have for you experts. You can set the BDIA BTYP and BTHK of the BTSE in this way but you cannot set the NOFF. Why? It is creating a problem for me. Does anyone know of a way around this? I need to pull the number of bolts from the component SCOM and I can't find a way to do it. I can use the BSEL as a workaround for now but it is not a final solution. The major problem is how do you have two SPCO in the same bolt spec that have the same BDIA but different NOFF? For example a 4xM20 and an 8xM20 pattern in the same bolt spec? You can use BSEL but what if you have both patterns on the same valve? Can't set BSEL on one valve to two different values. =(
