Navis Manage 2013 - clash detection rules

[markewbank435686]

HiI am trying to work out the best way to clash different MEP services against each other. I have 1 model file that contains all the MEP services. I have previously created search sets for each type of system and then clashed each type against each other. This has worked quite well, but takes time to set up each clash test, and to keep on top of as new system gets added.Whilst i not sure of the solution, I am convinced there must be a more effective way of setting up the clash test, using the rules. Does anyone know if it is possible to set up a clash test that ignores all the 'connections' within the same system type. My thoughts are that this would allow me to simply run 1 clash test - MEP vs MEP, that would only identify the true clashes of different services.

[VCDwhiz]

See this post:


http://beyonddesign.typepad.com/post...detective.html

[ballj]

I'm a little bit confused as to what you mean by "connections", but to help clear this up I'm going to throw out a thought. Assuming you truly mean MEP vs MEP, then you don't have any desire to prioritize conflict resolution correct? That being said, could you make a separate NWC for each system, append all of those, and then run all NWCs vs. all NWCs with the rule for "ignore items in same file" checked?

[dgorsman]

With most system-style modelers, the components shouldn't be generating a clash when properly connected e.g. socketweld elbow with plain end pipe. Unless this is a different type of connection? Or are connections not the real issue, but streamlining the process of creating clash tests?

[dhurtubise]

You can add a rule to ignore clash in the same... (layers for example)