While creating Pipe elements, we may face with situation when we need to preview category elements, that’s in current specification. Continue reading Pipe Component Preview
To find clashed elements in CSV format in customizeable way you can you such request. This example search thought pipes under /STABILIZER.
1;# HH CLASH; NOZZLE 2 of EQUIPMENT 1 of ZONE 1 of SITE /AFG-CX01.HVAC; NOZZLE 2 of EQUIPMENT 1 of ZONE 3 of SITE /AFG-CX01.HVAC; at E11299 N1299 U1501;user
2; # HH TOU; NOZZLE 2 of EQUIPMENT 1 of ZONE 1 of SITE /AFG-CX01.HVAC; BOX 1 of EQUIPMENT 1 of ZONE 3 of SITE /AFG-CX01.HVAC; at E11300 N1125 U1500;user Continue reading Clash Report in CSV format
This macro may be used to find out, what END is closer to PANE (or all other types) that is intersects SCTN.
We use clash tool, to find out at what point we have collision and than check which end is closer to it.
Usually we need text in 3D model for explanation of structural blocks.
Customers sometime require flow arrows in Review model, exported from Aveva Pdms \ E3D, to indicate flow direction.
Sometimes the task is to extract the Dblisting of branch for the subsequent transfer to another place (for example, technical support AVEVA for verification). Since the branch elements are referenced through the catalog specification, then one Datal branch is not enough for the download – you need a catalog and a specification.
Sometimes we need to find out position of some P-point in Paragon
but if we use expression with different trigonometric functions and a lot of calculations its very hard to check values.