Administration spécialisée > Prise en charge de la visualisation et de la publication > Getting Started with Windchill Visualization Services > Interference Detection > Interference Detection Considerations > Data Considerations
  
Data Considerations
This section describes the data considerations for the source data and published representation content that will be used for performing interference detection calculations. The integrity and modeling quality of the source model data and representation data published from it is paramount.
There are many possible causes of inaccurate or even invalid Interference Reports and the following best practices should be taken in to account before reporting to PTC Technical Support:
• The WVS Representations to be used for clash detection should be published as double precision (see CS25943.)
For further details, refer to:
◦ The Creo View On-line Help installed with the Creo View application
◦ The Creo View MCAD Adapters Installation and Configuration Guide as a PDF on the Reference Documents site or in the Creo View Help Centers.
• Ensure that the Windchill CAD data can be retrieved in to the relevant CAD application and the model regenerated successfully
• If CAD Regeneration failures occur, ensure that these are resolved and the affected CAD data checked back in (new WVS Representations will need to be published for the same).
• If quilts are involved in the interference, ensure convQuiltAsDatum is set to 0 in proe2pv.rcp. 
• If configuring the source CAD Application to use the Accurate calculation mode, the Interference calculation should be performed by Creo View using the same approach (see CS39266.)
• In its simplest form, Interference Detection can be performed on the entire structure using self-intersection but this can be an impractical and inefficient approach. You can use a combination of the following approaches to concentrate on the data you want to examine:
◦ Modular Approach:
▪ Consider performing the queries between individual modules first, with self-intersection.
▪ Then calculate the interferences at the top-level between those modules, without self-intersection.
◦ Zoning Approach:
▪ Break down a large structure into logical zones.
▪ Run the Batch Interference Queries on each zone.
◦ Exclusion Group Approach:
▪ Use Search Groups to identify parts that you know will interfere, such as fasteners and washers.
▪ Exclude the resulting groups from the Interference Detection calculation or query.