hopefully this will increasy the easy-of-use and powerfull of the FEMAP graphic user interface, to run geometry & mesh like a CAD system, we will know the details in a few months!!.

This was a query for all of us VARs and resellers of FEMAP in Europe, to support sublevels to include results, geometry, etc. Well, next release of FEMAP V11.2 due for end of this year (or January 2015) will feature an insteresting capability: sub-levels. RE: Model organization approach (layers and automated numbering) rb1957 (Aerospace) 7 Nov 14 07:46

What is your favorite model organization technique when using FEMAP?.

Are there any API collections available for FEMAP besides FEMAP knowledge base?.

Is there any way to solve this limitation? Groups do the work just partially, since their representation in the model tree is anyway flat.

Considering flat layer hierarchy in FEMAP (no sub-layers or sub-assemblies are allowed) presented approach does not scale for the models with large number of parts/interfaces – list of layers becomes too large and difficult to deal with.However, I could not find anything similar yet, so your help is much appreciated. materials, properties, elements per layers etc.Ĭurrently 2) and 3) are implemented via HyperWorks API, but I assume corresponding tools may already exist for FEMAP. It is often required to generate model summaries, e.g. It allows keeping numbering ranges for particular objects/parts in the assembly.ģ. for the layer ID 10,001 each entity is renumbered starting from 10,001. Model numbering (nodes, elements, properties, materials) shall start with part layers and continue with interface layers. Presented approach simply reflects already existing methodology based on components.Ģ. I came across many discussions “groups vs layers”. According to the existing model organization approach, model entities (nodes, elements, properties, materials) for each part (CHEXA, CQUAD etc.) and each interface (CBUSH, RBE2 etc.) are allocated in separate layers. The SDC Verifier add-on adds advanced functions to Simcenter FEMAP for verifying structures according to norms like Eurocode 3 or DIN 15018.I am trying to adapt the existing model organization approach from HyperMesh to the FEMAP environment, and I would be glad to hear your feedback and suggestions.ġ. The FEMPLY add-on expands the range of functions of Simcenter FEMAP for composite materials and offers additional failure criteria. Direct matrix arithmetic programming (DMAP).

Heat conduction calculations (stationary and transient).

Furthermore, the range of functions can be expanded with additional modules for NX Nastran or add-ons for Simcenter FEMAP:

The base module of Simcenter FEMAP with Nastran includes a wide range of functions, which covers the requirements for the usual analysis tasks.

Femap student edition