EPC - Engineering Process Clash 2.0
Life Cycle Management for Clashes: Identification, Analysis and Management
The management of clashes across the entire product life cycle constitutes a challenge in product development for many companies. One reason, among others, for this is the spatial and interdisciplinary segregation of development teams within global organisational structures. In order to meet the requirements for modern life cycle management for clashes, CADS Engineering has developed the Clash Management System (CMS) called Engineering Process Clash (EPC). Via EPC, it is possible to visualise all information contained in the clashes and thus, for example, to draw conclusions regarding the product maturity level and/or the current development level.
Clash Check upon the Basis of the Creo View Data – Throughout the Entire Component’s Life Cycle
As the basis for the identification of component clashes and their elimination, the Creo View Batch Interference Engine* from PTC is used whose results are then entered into a clash database. The continuously-repeated testing process has been conceived to be scalable in order to meet an ever-increasing number of projects/products. Because the data are based upon Creo View, it is possible to also stably assess data from various CAD systems (MultiCAD). Another advantage is that errors cannot occur that are typical for CAD when retrieving data because the data have already been published as Creo View data. *Own license required
Reuse the Results
The required time for the clash sequence can be reduced by only testing the clashes between the main assembly units. The logic for the testing of the components to be controlled is defined by an EPC algorithm which removes all non-relevant data automatically from the clash sequence. Thus, the data quantities that are sometimes quite immense can be reduced to a number which can be manageably processed.The main assembly units are found in the structure automatically based upon pre-defined criteria, e.g. level or parameter. When the clash pairings have been identified, all changes are analysed. Thus, it is ensured that only those pairings are tested again which have been changed. Thus, the time required for the clash sequences can be reduced by up to 99%. Through this and many additional optimisation measures, the EPC solution will provide you with daily updated clash reports regarding your project, product or product portfolio.
In EPC’s visualisation area, the designer has the possibility of viewing the clashes efficiently and quickly. Based upon the model tree, he can display the clashes that are important to him in filtered form on the clash chart. The chart contains the names of the clashing components, their clash volumes as well as the relevant meta-data. Identical clashes of multiple components, e.g. fittings, are then automatically grouped and summarised under one ID thanks to EPC. The selected clashes are simultaneously displayed in the Creo View (Overall) Model so that the user can also conduct a visual control. Moreover, the designer has the possibility of commenting on clashes and setting a status (traffic light). The comments and the status remain intact as long as the clash exists, until they are deleted by the user or until the user decides to make the status (traffic light) and/or with his comments with the command to “Publish” accessible to all project participants.
A continuous management of clashes can only then be ensured if all tools and interfaces are designed for this. Via the EPS integration for EPC, CADS Engineering offers the possibility of opening and editing the affected pairings within the CAD system (Creo Parametric or CATIA V5) directly from the clash chart. The modification can then be tested via the EPS functionalities within the overall context and, if successful, can be checked in quite normally. Then the modified component will be assigned to the clash process and will no longer be available in the next clash sequence.
Clash Monitoring – From the Start to the End
The analyses provided by EPC enable companies and/or the Development Divisions to obtain completely new perspectives for their projects and products. From the data, they can, for example, read whether an insufficient number of resources has been provided for eliminating the clashes or whether suppliers have been provided with your data too late and that is the reason why the clashes are occurring. All this information can only then be purposefully used if it is recorded, analysed and maintained throughout the entire life cycle. EPC makes precisely this possible.
The standard configuration of EPC contains 3 views which depict all relevant data. As required, the views can be accordingly adjusted.
Clashes which already existed during a previous clash sequence (old clashes)
Clashes which initially occurred during a clash sequence (new clashes)
Both old and new clashes upon a cumulative basis