| - | Manually identify clash records in ENOVIA as penetration candidates (clash records result from an interference check) |
| - | Generate a Penetration request (a penetration request is a special Action type) |
| - | Delete Penetration request if a clash ceases to exist (another design change may have caused it to disappear) |
| - | Query clash occurrences assigned to Penetration requests |
| - | Query Actions of type "Penetration" and identify related clashes |
| - | Queries of clashes and penetrations in a specific compartment |
| - | Assign candidates to a Penetration Action |
| - | Merge multiple penetrations into a single penetration |
| - | Automatic Penetration Action ID Generation |
| - | Manual generation of penetration geometry |
| - | From CATIA, select a Penetration Action affected object and create CATIA session with associated part instances |
| - | Use ENOVIA life cycle management functions to control Penetration request progress |
| - | Transfer affected objects and data from an existing to a new Penetration Action |
| - | Create clash & Penetration Action reports using the ENOVIA Business Reporting Hub |
| - | Send clash or Penetration result directly to authoring tool (CATIA V4 or CATIA V5) |