Process Considerations
This section describes the process considerations and best practice approaches required to ensure that you get the most value from your interference detection product.
What is the size of data set to be analyzed?
• Top level assemblies
• Lower level modules
• Individual components
What are you seeking in the results?
• Top 100 Interferences?
• Will you be detecting Contact + Clearances?
 |
If you enter tolerance >0, the number of Contacts increases, while the number of the others interferences is reduced.
|
How are you going to exclude parts from the query? For instance, you can use groups to identify fasteners.
Which Interference Detection product(s) will you use?
• Desktop Interference Analysis?
◦ Desktop Interference Analysisis a Creo View optional module.
◦ Users can load structures and interactively create and runInterference Detection Queries in real time and save the resulting Reports to Windchill.
◦ These Creo View Interference Detection Reportsare stored as Creo View Annotation Sets and do not create related Interference objects in Windchill.
◦ Refer to “Interference Detection” in the Creo View Help Centers.
• Batch Interference Detection?
◦ Part of the optional Windchill Interference Management Services module.
◦ Requires the Creo View Adapters Interference Detection Engine (CLASH Worker).
◦ Used to define an Interference Detection Definitions (IDD) that can process the largest structures in batch, against a CLASH job, managed by the WVS CLASH queue set.
◦ Results in the creation of an Interference Detection Report (IDR), that is related to the IDD, and related Interference objects for tracking the analysis of each interfering pair of objects.
◦ This also integrates with Windchill Change Management.
◦ Refer to Windchill Interference Management Services in the Windchill Visualization Services Administrator's Guide and Creating an Interference Detection Definition and succeeding topics in the Windchill Help Centers.
Approximate versus Accurate Mode
Approximate Mode:
• Calculations in Approximate Mode are based on the tessellation data.
• It is quicker but less precise
• Use for the first pass on large assemblies, for example to identify where problems might require more accurate analysis.
• Use during the earlier stages of design to identify major issues, for example, choose this mode for interactive Desktop Interference Analysis sessions.
Accurate Mode:
• Calculations in Accurate Mode are based on precise BREP solid data.
• It is more precise but slower.
• Reserve for the final passes on large data, for example, to confirm that issues identified in earlier, approximate passes have been resolved.
• Use for more detailed or focussed analysis, such as smaller sub-assemblies identified as potential problem areas in earlier approximate passes.
• More likely to be performed non-interactively, using the Batch Interference Detection approach, because it takes longer.