Posts Tagged "configurations"

CATIA has many naming conventions and packaging options. In this post, we’ll be looking specifically at CATIA V5, with future posts examining CATIA V6 and 3DEXPERIENCE.

Version 5 began back in the late 90s as a complete re-write of the previous version. As development progressed, new releases were produced. A release indicates enhanced or new functionality over prior releases – however, still on the same version. A collection of bug fixes would be referred to s Service Pack, and specific bug fixes are referred to as a Hot Fix. Putting it all together we would see something like:

V5 R19 SP 9 HF 108

This would translate to:
Version CATIA 5, release 19, service pack 9, hot fix 108

Why is this important? Because many OEMs require their suppliers to deliver designs that specifically match their own.

Classic vs. PLM Express

When looking for a seat of CATIA, you would be looking for what Dassault calls a configuration. Configurations are commonly referred to by their trigram (a character letter acronym) that is specific to the type of design required. For instance, a mechanical designer would be interested in either an “MD1” or “MD2” – “Mechanical Design 1” or “Mechanical Design 2,” respectively – depending on level of complexity. We call these configurations Classic.

Later, to support their data management solution, SmarTeam, Dassault came up with new bundles called “CATIA PLM Express.” These bundles included licenses for SmarTeam, encouraging use by lowering the cost of entry. This also the first time we see the idea of roles. Rather than bundling functionality by the type of design, in CATIA PLM Express, the bundles are made more intuitive by considering the role of the designer. You could get these bundles, or modules, specific to Manufacturing Engineers, or Layout Engineers. The idea is to gather the modules required by the desired outcome (lathe machined parts, structural steel frames), rather than the methodology (mechanical design). You can build your own PLM Express here.

cat-1074657_1280There are a few additional terms to define when working with PLM Express. It all starts with the bundle called “CATIA TEAM PLM,” or in trigram speak “CAT,” which includes most of the basic design tools and some data management licenses. This is the base configuration upon which everything else is built.

The next level of bundles are called Enablers. Enablers form the starting point of the role-based package. A designer that needs to produce structural steel frames would start their selection in the “Layout Engineer” group of enablers, and would select the one named “CATIA Structure & Steelwork Layout,” or “SSE.” A tooling engineer would look at the group “Mechanical Product Engineer,” and the enabler of choice would be “CATIA Jigs & Tooling Creation,” or “JTE.” In the tooling example, the common way of referring to the package is “CAT+JTE.”

If enablers start the specialization bundles, the next level called Extensions round out. These bundles are very specific to a role or outcome. Case in point is “CATIA Composites Design,” or “CPX.” Another example would be “CATIA Electrical Cable Layout,” or “ECX” found in the “Layout Engineer” grouping, and could be added to the enabler “CATIA Layout & Annotations,” or “LOE.” That would create the final package of “CAT+LOE+ECX.”

A special note: in order to get access to an extension bundle, an enabler bundle must accompany it. In turn, to access an enabler, you must first start with CAT. Think of them as levels of a house: CAT, the base configuration, would be the first floor. The second floor consists of enablers, and the third floor are enablers. You can’t get to the third floor without the second. You can have any combination of enablers and extensions, regardless of the role grouping. So our tooling designer (CAT+JTE), may, for some reason, need access to the Electrical Cable Layout extension (ECX), found in the “Layout Engineer” grouping.

One final note, and this is a biggie.

When an OEM specifies a version level, say V5 R22 SP5 HF 16, they may also prescribe a classic configuration like MD2. This is not gospel. You may use a PLM Express bundle instead; both use the same file formats. They are both V5, and are interchangeable.

This can be extremely confusing, especially for new people just entering the CATIA world, and all these trigrams and bundles can be daunting. Our team can help you determine what you need and put together the bundle that makes the most sense for your situation. Just let us know how we can be of service.

ABAQUS CONFIGURATION PACKS

From a packaging perspective, Abaqus includes a user interface called Abaqus CAE and a solver that includes implicit, explicit, and computational fluid dynamics capabilities. The post-processing or result visualization can be done in either Abaqus CAE or Abaqus Viewer, which is the visualization module of Abaqus CAE. Collectively, these products are called the Abaqus unified FEA suite of products.

From a licensing perspective, the Abaqus pre-processor, solver, and viewer are available in two different configurations: Analysis pack and portfolio pack.

Analysis pack and analysis tokens

In an analysis scheme, Abaqus CAE\Abaqus Viewer are available as an independent seat. This means that the number of user interfaces that can be run concurrently depends on number of seats available in the license.

The solver works on the concept of tokens. The user utilizes a certain number of tokens depending on simulation needs. Each token has all three functionalities of solver: implicit, explicit, and CFD. Each single core non-linear job of Abaqus consumes five tokens. With a greater number of cores, the token consumption varies, as shown in the illustration below. The analysis pack is the pre-requisite configuration that includes one seat of Abaqus CAE and five analysis tokens. This means that the analysis pack is enough for a concurrent session of a single user interface and a single core Abaqus job. More user interfaces can be added in license as separate seats of Abaqus CAE. More solver functionality for multiple cores can be added as separate analysis tokens. More post-processing interfaces can be added as separate seats of Abaqus viewer.

Portfolio pack and portfolio tokens

In a portfolio scheme, Abaqus CAE, Abaqus Viewer, and the solver all work on tokens. The token utilization for a single session of Abaqus CAE and Abaqus viewer are mentioned below. The portfolio pack is the pre-requisite configuration that includes five portfolio tokens. This means that a portfolio pack can be used to run either a single core Abaqus job or one Abaqus CAE at a time. More functionalities for concurrent sessions of Abaqus CAE or multi-core jobs can be added through additional portfolio tokens as add-ons to the portfolio pack. The token consumption number as a function of multiple core jobs remains the same for portfolio configuration as for analysis configuration.

Program Portfolio Tokens Used
Abaqus/CAE 4
Abaqus/Viewer 2


A FEW HANDY EQUATIONS FOR ABAQUS LICENSING

  • T = INT(5*N^(0.422))

T = number of tokens consumed

N = number of cores utilized in a single Abaqus job

^ = power function

INT = greatest integer function that converts a real number to the equivalent integer number

This equation is used to estimate token consumption based on given number of cores. The first table mentioned in the article is a direct derivative of this equation.

  • 1 QAP = 1 QAE + 5 QAT

QAP = abbreviation for analysis pack

QAE = abbreviation for Abaqus pre-processor

QAT = abbreviation for Abaqus analysis token

This equation means that a single analysis pack configuration contains one interactive seat of Abaqus pre-processor and five Abaqus solver tokens. These functionalities are sufficient to execute one Abaqus pre-processor and one single core Abaqus job concurrently.

  • 1 QPP = 5 QPT

QPP = abbreviation for portfolio pack

QPT = abbreviation for Abaqus portfolio token

This equation means that a single portfolio pack configuration has five portfolio tokens inside it. These tokens are enough either to execute a single core Abaqus job or a single session of Abaqus pre-processor but not both at the same time.

Do you have any questions, or need assistance figuring out which configuration you need? Leave a comment or click on Contact Us at the top of the page to talk to someone directly.

© Tata Technologies 2009-2015. All rights reserved.