Some issues I have with piping assembly (drain assembly):
1. Using the aveva sample project, I tried using the distance command on the olet in the header pipe but it doesn't work. Tried it on the branch pipe and it works. The distance command would be very handy in setting the distance of the olet from a fitting weld(ie. elbo, tee etc.)
2. It seems that an assembly consisting of an olet (tee is fine) would only work on the sample project (aveva piping specs) but not on our company specs. Apparently the problem was in the connection, "incompatible connection types". In aveva sample project, elbow and olet connections have both BWD while on our company specs, the elbow connection is BWD and olet is OLT (p1 & p2). Is there a work around on this? Can we use force connect the olet to the previous component then set the distance? We can't change our company specs as there's another reason why it's done like that.
Anybody else interested in this fuctionality, please log a ticket with you local aveva support, you can copy below. The more customers requested the more it will likely get "enhanced" :-)
Dear Aveva Support,
Is there a way to "FORCE" the Tee Piece in such assemblies, ie default it to an e.g YYmmx20mm tee-Piece. In other words users are not given the option to select the Tee Piece from the Catalog and hence make selection errors ?
One can read C:\AVEVA\Plant\PDMS12.0.SP6\Manuals\Docs\Pipework Design User Guide.pdf Chapter 12.3.5 Piping Assembly Component Rules. You can create "Selection Rules". I.e.g. SEL WITH PBOR3 20
However please advise how this would work as below does not seem to do the trick for us
[COLOR=#333333]hi i create an assemblie for use in tool pipe splitting (simply a weld)[/COLOR]
[COLOR=#333333]i copy [/COLOR]/flangeset-PIPE from aveva and change for my weld but i dont know how you do to place weld in the good spec when you split youre pipe.
if you see the valid value of /flangeset-PIPE
you have VALIDV ( '/A3B%WN%FALSE' )but i dont undertsand because the template flange gasket flange is build with spec A150
Yes i do this but rules(validv for valid value) not done..and i dont understand why
Someone tell me that assembly with 12.0 and may be upper version..dont work with intelligent rules..
So i think need to build same assembly for each spec but not afain try this way