Model organisation, version control

[Ng2020]

I am working with an airplane internal loads model. The configuration of the wing, fuselage, landing gear etc will change as the project develops, so we want to be able to version control each major subassembly independently.
For example: Airplane Configuration XYZ = Wing version 1.3 + Fuselage version 2.1 etc. where each sub assembly is modelled in separate files.

This can be done with Nastran include files, but is there any way to accomplishvvia FEMAP gui native methods/features? E.g use a master MODFEM that automatically imports data from referenced include files upon opening.
(My guess is no)

 

[rb1957]

"import geometry model" ?

 

[Ng2020]

Rb: no, not 'geometry' in the FE preprocessor sense, rather, for each major assembly I want to be able to define nodes, elements, and properties in entirely separate standalone files that can be individually version controlled, then have a single master file representing a particular design configuration of the airplane which imports the mesh & props for each subassy at the appropriate revision level.

 

[ThomasH]

Have you tried the File-Merge option in Femap?

 

[Ng2020]

File Merge is a manual one off operation effecting permanent changes to the Modfem. I'm after automatic dynamic linking of files.

 

[vvk_187]

In Femap, you can try to do this through the "File-Import" command, but it is very difficult to do this because you will need to track numbers (nodes, points, curves, materials, properties, etc.)
so that in each file they occupy their own niche and do not intersect.

 

[ThomasH]

If you have three different modfem files with different version numbers you can use File-Merge to create a one assembled modfem-file. If you update one of the three files you can create a new assembled modfem based om two of the original files and the up-dated file. Isn't that what you were after? The only modfem file that is permanently changed is the modfem file that you import models into.

Another option is the File-Import based on neural files. It means that you manually need to keep track on the object numbers for everything. And that can be done by using different series for the different models.

If you are after dynamic linking of files I would take a look at the new functionality in Teamcenter.

I think that what you want can be done but probably not completely automatic. That probably requires a bit of api work.

Or, am I misunderstanding what you are looking for?

 

[Ng2020]

Thanks Thomas, ideally i was after dynamic linking. We can live with a manual hack using import or merge.
(We don't have teamcentre)

 

[rb1957]

each sub-model should have unique numbering. So sub-model 1 has all nodes, elements, properties, etc as 100######, sub model 2 200######.
and maybe sub-model 2 version 2 might be 220###### (then sub-model 1 version 1 might be 110######).
possibly data common to all (like coord frames) could be ###### (or 000######).

You may be able to do this "dynamically" with "offset" command.

In the olde days, to get a full airplane model results, we have to do something like this. We needed a librarian (!!??) to keep track of what pieces were assembled in which run, with which loads, OMG ! Runs would take many days to assemble and often crap out on the last operation ... and we'd have to start again ...

"tell that to the kids these days, and they won't believe you"

sigh

 

[Ng2020]

Rb: yes, each subassy requires its own reserved range of node/element/prop numbers.

Model config control is a significant task even to this day, though assembling a modular model is substantially faster now.

 

[rb1957]

using a rigid node and element numbering scheme would also help in debugging the models, or ensuring the model build-up is what you thought it was.

does FeMap have a "super-element" capability ? can you use "restart" ? run you sub-models as stand-alone; I don't know what FeMap calls it but in my olde experience the different parts of the model were joined together by "link" nodes. each component was run in isolation, and the code condensed the stiffness of the model to these "link" nodes, then the "global" model joined these "link" nodes together. Your different sub-models will have the same set of nodes common the the neighbouring sub-model, yes?

let's see what Blas has to say ?

 

[BlasMolero]

Dear RB & RG,
Blas here, but sorry, FEMAP do not support configurations model management to deal with assemblies & subassemblies, this is a dream I have had always with FEMAP, also commented with development, but in FEMAP all is "manual".
But we have available the great FILE > MERGE command: it allows geometric or finite element entities from any model currently open in the same instance of Femap to be “merged” with the active model.
I use this command to assemble BIG models, creating different components is different *.modfem files and finally assembling all (geometry & nodes, elements, material properties, all!!) in the "Master" big assembly model, not too bad.
Attaching very interesting FEMAP training material with PDF tutorial, FEMAP models & VIDEOS, take a look!!. The tutorial explain the following:

• Open two FEMAP models: first is an Aircraft Frame subassembly considered as MASTER and second model containing a Lower Left Frame section.
• Merge the Lower Left Frame into the Frame Assembly using the "Merge" command

To facilitate bringing entities into the active or current model, a number of overall Renumbering and Duplicates Strategy, Entity Selection, Orientation/Transform options, along with some miscellaneous items in the Options section, are available in the Model Merge Manager dialog box. Finally, the Entities to Merge list, located at the top of the dialog box, can be used to choose which entity types to merge into the active or current model using the check marks in the Entity Type column.


Finally all (geometry & fem) is assembled!!, accounting for proper re-numbering, of course:



Enjoy!!.
Best regards,
Blas.

 

[Ng2020]

Thanks for the responses all!