Table of contents
If you’d first like a little background and a brief history of CATIA versions, you can check out our “What is CATIA?” blog post. Or, if you’d prefer, you can catch up with our recent webinar, “What is so different in CATIA 3DEXPERIENCE in comparison to CATIA V5?” Otherwise, let’s get stuck in.
With CATIA connected to the 3DEXPERIENCE platform, you’re able to enjoy all the benefits that you’d expect from Product Data Management (PDM). Version management, modification rights, release control, etc… are all present and configurable to your organizational needs.
This means that, in addition to all the other features described below, CATIA users migrating from file-based CATIA V5 to CATIA 3DEXPERIENCE will be able to work much more efficiently; All the issues associated with managing collaborative working, such as manually copying files, trying to manage revisions, and accidentally overwriting others’ work are gone in favour of a single source of truth.
Simply put, CATIA 3DEXPERIENCE works quicker by taking advantage of a computer’s resources far more effectively than V5 – reducing the waiting times on rendering, loading large assemblies, and performing complicated mathematics.
It may sound like a trivial change to some, but this affects virtually every operation CATIA makes. And this can amount to a substantial time saving for every user.
Dassault Systémes’ 3DEXPERIENCE platform is designed to be hosted on the web from the ground up. This means that whether you’re connecting CATIA to the 3DEXPERIENCE platform through the web or on the company local network, you’ll be transmitting and receiving data optimized for the current network state.
CATIA will also only request the data it needs when opening assemblies, only loading the full data for the assembly’s component parts when requested by the user. This is like CATIA V5’s cache mode, except that the lightweight files needed for this process are created by a server process beforehand, speeding up the loading process even further.
The web-based nature of ENOVIA also makes it easy for users to connect their session to the database encrypted from anywhere without the need for complex setup on each client machine. This makes collaboration between different sites or businesses convenient.
(Note that CATIA 3DEXPERIENCE remains a ‘client application’, like V5, installed on a user’s PC. CATIA 3DEXPERIENCE communicates with the 3DEXPERIENCE platform via an internet-compatible connection. Non-CATIA users connect through a web browser).
Even with a PDM system managing data, it is often still onerous on the user to fill in a search form for every part or assembly they wish to search for, particularly when using an external program as mentioned before. CATIA 3DEXPERIENCE however, has an ever-present full text bar which can find anything in the platform that the user has access to in one bar, while keeping the more precise filtering tool
On top of all this, the user can also set up lists of favourites and folders to store and organise their own work. Due to the way the database handles the data, designers are free to create any folders or favourites they require without affecting how other users access the data. This is quite unlike using CATIA V5 file based, where moving files into different folders can lead to much frustration, as links between files break because of moving and copying them.
All 3DEXPERIENCE rich client applications can explore the visual structure of assemblies in a quick lightweight mode, without needing to open the full design data. This allows CAD and non-CAD users alike to view the structure of assemblies from the top levels and find the parts they want without needing a powerful computer able to open the top-level assemblies in full design mode.
While other PDM systems can do something similar, they often rely on CAD users constantly opening and updating the top-level assemblies to keep the viewer files up to date.
The 3DEXPERIENCE platform that controls the data can recognize changes to parts and will then automatically update all the affected representations, keeping all stakeholders up to date in how the structure really looks. The data stored can be further enhanced by attaching other file types directly to the CAD data (reference tables, exported PDFs, etc.) This documentation is then fully database controlled and is released alongside the CAD data it is attached to.
Finally, it is possible to use the database to visually colour the 3D objects based on various customizable parameters, most notably identifying if objects are released, obsolete or still in work.
CATIA V5 can integrate with various other PDM and PLM systems, Including 3DEXPERIENCE itself. But this is typically done with a separate program installed onto CATIA which is used to search for objects and load the required files locally for CATIA to use. Whilst this is functional and certainly an improvement over file-based CATIA, they tend to share a few limitations with each other, namely:
Since the CATIA V5 files need to be stored locally, a user could potentially download the files they want and work outside of database control, send uncontrolled copies of drawings or worse, steal the company’s data.
None of these issues are present within the 3DEXPERIENCE platform:
In file-based operation, a problem invariably faced by any design department is the visibility of links between one CATIA file and the next. These are only visible ‘one way’, i.e., from the files that are using linked copies of the data to the files where that data was originally created. This makes it impossible to interrogate a file and determine what other Parts, Assemblies and Drawings are currently reliant upon it. One person moving the file or modifying some important geometry can unwittingly ruin any other file that relies on the now-modified part.
Existing database PDM systems do provide solutions to this problem by removing the need for the user to move files around, while also enabling the user to identify if links exist between two objects.
But CATIA 3DEXPERIENCE goes one step further by allowing the user to identify the exact features being used and where they are used, from any given object. Geometry links, publication links, contextual links, material links and drawing links can all be identified without the need to open the object up fully into session, meaning non-CAD users can see and gain an appreciation for what parts are reliant on what.
CATIA 3DEXPERIENCE features various new Workbenches which exploit the new database functionalities and new graphical capabilities of the CATIA engine. New Workbenches include Natural Sketch, which allows non-CAD users to create concept designs by intuitively drawing on 2D planes in 3D space, creating wireframe geometry which can be directly used by CATIA designers to then create full design specifications.
Existing Workbenches have been modified to directly query the ENOVIA database for its information rather than the local data, meaning that the data you work with is always up to date.
Typically, a PLM system will allow you to create a separate BOM tree from the CATIA structure with the BOM manager overseeing the reconfiguration of this BOM to the real purchased BOM. However, The BOM and the CAD tree seldom agree with each other, and need to be synchronised frequently and often manually, leading to a long-standing rivalry between the Engineering and Design teams.
3DEXPERIENCE solves this by having one tree handling the 3D models from all connected CAD tools – and also the Engineering requirements!
It’s often the case that assemblies are not a simple sum of their parts. Various operations are only performed after the parts have been assembled (drilling new holes, grinding down faces etc.) In most CAD systems, CATIA V5 included, it can be challenging to represent the way that the parts are made individually whilst also showing the finished assembly. This usually involves creating a “Phantom” part to represent the finished assembly.
This is improved in 3DEXPERIENCE where geometry can be inserted directly against the assembly, with a special function called “Derived Representation” which copies all the required geometry of the assembly into one representation. This allows the post-assembly operations to be specified without needing to take out dummy part numbers.
Similarly, the ability to insert geometry directly against assemblies removes the need to create “Skeleton” parts to contain construction geometry for assemblies (patterns, package boundaries, centrelines etc.)
As well as various technical improvements, CATIA 3DEXPERIENCE has also been given a much-needed update to its appearance, with the graphical assets re-created to make better use of the high-resolution screens that are available today, whilst also reducing visual clutter.
To give you an idea of the update, compare these two trees from V5 and 3DEXPERIENCE. This image also further emphasises how despite the visual changes, a designer would still be able to recognise all the features of the tree.
While fundamental enhancements to the data structure behind CATIA have been made, CATIA’s modelling tools remain familiar, with the primary difference being enhancements to the existing tools and additional Workbenches. Users will be able to sit down in front of CATIA 3DEXPERIENCE and be at home without the need for a lengthy transition course.
The underlying kernel for CATIA 3DEXPERIENCE is based on the V5 kernel. This means that data from V5 can be imported, with full history and links of all kinds, into 3DEXPERIENCE with the database. It has the additional ability to recognize when files have already been imported and re-link these files to any new data, preventing unnecessary duplicates. Imported data can even be later updated with newer versions of the V5 data. So, after the import, the users can simply pick up their work where they left off.
Check out our “What is so different in CATIA 3DEXPERIENCE in comparison to CATIA V5?” webinar on-demand