Saving a Manikin

This task describes storage management principles involving manikins in the Human family of products.

This will allow you to reduce the number of manikin reference files to be used for, in particular, complex and complete simulation scenarios where a large number of workers need to be involved, and sometimes changed for trying different modeling alternatives.
You will not see a particular new external behavior.  Access to the highlight will be done through a Tools/Options mechanism and that will be the only interface change involved for this highlight.

The only change is related to the Tools/Options page for Human Builder.

By allowing you to decide the attributes to be saved on the reference and those to be saved on an instance, we want to have the possibility to make each manikin instance unique, but with regards to those attributes that you have chosen to be locally overridden.  This will also support existing industrial scenarios where a reference manikin, put in database, is shared by a large number of users, each user overriding only one small aspect of the manikin locally.  When saving the multiple instances, the local change from each user is NOT expected to go back to the reference, and therefore NOT impact all other users.
This will provide the same results regardless of the environment in which the manikins are saved and the technology used; that is, the results will be the same whether the manikin is saved on a flat file in the local file system, in ENOVIA LCA under a root product, or in a DELMIA V5/Process Engineer environment within a CATProcess detailing.  When you decide to locally override (that is, save on the instance) a particular attribute, all future changes of this attribute will affect the instance only.
At Save time, if you have changed only attributes such as gender for example, and if the option is activated, then the Save Management of V5 will not ask or inform you that a linked CATProduct (the reference manikin file) needs to be saved anymore. Because, this gender information will be saved in the current document where this reference manikin had been instantiated.

A manikin is created in the same document as its father product, thus avoiding file duplication in the saving process. Manikins created in such a manner can further be imported into a new document, and most importantly, manikins created with previous releases of the software will import as well, without any particular required operation from the user (no data migration needed). There is no duplication of files on the user disk unless it is really necessary.

  1. To save a manikin select File > Save As...

  2. The dialog box appears. Select the directory that you would like to save the manikin in.