Under a CATE you can find a DTSE element.
DTSE owns DATAs element
If you query the attribute of a DATA you will find a DKEY attribute.
That's where you can find something like THA
So RPRO THA means that it gets the BTHK value from there (it could be a Design Parameters or other)
I suggest you to search for DATA or DATASET on this forum to get other info....
I'm setting up new bolting method and referring every post here to understand the New bolting mithod, I do not undertstand 'Bthkness ( ATTRIB RPRO THA )' when I BLTP attributed.
Please let me know whta is this stands for Bthkness ( ATTRIB RPRO THA )[/U]
One reason is that you can give a default value to design parameters so when you create the piping element in design it will be immediately visible....
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.
Very often people attending Piping Cats & Specs training courses asks me about having "jolly" instruments.
For example Control Valves. They need to create them in design before knowing the vendors that will supply instruments.
So the give temporary dimensions (actuators dimensions and even the overall length) to this kind of user defined components waiting for the final values.
Then I have customers using ATTAs with geometry to represents piping supports.
And they are variables (user defined) too.
It is all about discipline.
Dimensions of 99% of piping items are fixed according to industry or vendor standards so should not be using design parameters.
Dimensions should be fixed in the catalogue.
We still allow variations in design where allowable, Angle, Radius, Height.
You cannot allow designers to change dimensions as he wishes.
If he knows the correct length then so should cats & specs and it should be fixed in the catalogue.
We have previously had one designer on this site wanting to know how to change the length of a valve because the length in the catalogue did not suit his design.
It is different for structural where lengths and widths of many items, like plates, are dictated by the design.
Then the use of design parameters is useful.
Instruments need to be centrally controlled to ensure latest revision of vendor data is in place for QA/QC reasons
Responsibility for particular pipelines may change more than once during the life of a project so we need to ensure that what is in the model is up to date.
Cats & specs can issue a preliminary component and update as required.
[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. =(
dank69, BDIA, BTYP and BTHL are STRING type attributes so they can contain expressions, NOFF is REAL.
So you need to create as many BTSE elements as many holes_x_diameter combinations you have.
Bthkness ( ATTRIB RPRO THA )[/U]
