HC42581: BEAM / EDIT / SESSION NOT DOCUMENTED IN CATIA.BODY IN WHITE TEMPLATES. USER'S GUIDE(SH52-7380).

APAR status

• Closed as documentation error.

Error description

• BEAM / EDIT / SESSION not documented in CATIA. Body in White
  Templates. User's Guide (SH52-7380)
  

Local fix

Problem summary

• BEAM / EDIT / SESSION not documented in CATIA.Body In White
  Templates . User's Guide
  

Problem conclusion

• THIS MODIFICATION WILL BE INCLUDED IN CATIA DOCUMENTATION
  DELIVERED WITH CATIA VERSION 4 RELEASE 2.0 REFRESH 2
  
   DOCUMENTATION REFERENCE:
   MANUAL  ===> SH52-7380
   MANUAL  ===> CATIA.Body in White Templates User's Guide
   CHAPTER ===> BEAM Interoperability
   PAGE    ===> 59
   .
   MODIFICATION:
  The following sections have been added to the
  421 documentation. It explains how to use the
  EDIT --> SESSION items in the BWT product:
  ******************************************
  .
  BEAM in a Multi-Model Environment:
  .
  In order to allow concurrent engineering keeping
  associativity, users may need to create beams
  in a multi-model environment. Parent geometry,
  such as wireframe features, planes, surfaces, skins,
  and so forth, could be accessed by a body-in-white
  engineer while keeping associativity.
  The BEAM function allows to select parent geometry
  from another model when creating beams.
  .
  .
  A Unique Identifier for Each Element:
  .
  This technology is based upon the concept of
  Universally Unique Identifier (UUID). This identifier
  is used for the identification of any element. It
  contains all the information necessary to detect the
  element among many others, whatever they are. Besides,
  it is never associated with a model, which guarantees
  the environment consistency.
  A time stamp is associated with each identifier so as
  to distinguish the time when the element was edited.
  If you work in single model mode and you need to erase
  an element identified by a UUID, the message
  "linkable object(s)" warns you that this identifier
  may be used in another model.
  .
  .
  What You Should Know:
  .
  In a multi-model environment, the source model may
  contain several types of elements (procedural or not).
  However, you can reference any wireframe elements,
  planes, surfaces, faces, skins, and exact solids, as
  well as nodes of *SKD elements (created using the SKIN
  function, refer to CATIA.Generative Modeling User's Guide).
  Before using these elements, make sure that they are
  not "private". Otherwise, key in the /GENUUID command
  to generate an identifier for each element. You will
  then be able to access them.
  For solids, choose the FEATURE + SOLIDE items to be
  able to reference them.
  .
  .
  Model Synchronization:
  .
  When working with several models, there may be a number
  of actions performed on the passive models that may
  lead to de-synchronization between the models.
  Synchronization is based on the comparison of all
  time stamps of the elements involved, and of the model
  location when the link was created. It implies the
  modification of the elements which time stamps are
  different. Several causes may ask for synchronization:
  .
  - The Source Model has been Renamed/Moved
  - A Referenced Element has been Deleted in the Source
    Model
  - The Source Model has been Modified
  .
  Use the EDIT --> SESSION items to display the Multi-
  Model Elements dialog box: (graphic)
  .
  All BEAM and SKIN elements involved in multi-model
  work are displayed in this dialog box, along with
  their location and statuses. They are classified
  by directory and model name. The status of the
  elements is a hint to what happened and how to
  synchronize the models.
  .
  The Session graph tab helps you visualize all model
  dependencies, based on a color code:
  .
  - Green when the multi-model element is in the
    current session
  - Yellow when the multi-model element is in session,
    but not current (before clicking Expand all models)
  - White for geometry created using other CATIA V4
    functions
  - Red when the model is not loaded in session.
  .
  Furthermore, a contextual menu is available on the
  model boxes to load models displayed in the Session
  graph, and another is available anywhere in the graph
  (Reframe and Print capabilities).
  .
  .
  Load All Models:
  .
  When working in a multi-model environment, make sure
  that all models have been loaded. If any referenced
  model has not been loaded, the identifiers of the
  referenced elements are not displayed in the session
  models, and their status is Unknown. You still can
  work in the current model, and updates are available.
  .
  To load your models, here is what you should do:
  .
  Step 1: Click on the element in the Multi-Model
          Elements dialog box.
  Step 2: Click on the Load Model button.
          - If the model is found at the referenced
            location, it is added as a passive model.
          - If the model is not found, an error message
            is displayed indicating that the model
            cannot automatically be loaded.
            You need to manually load the model using
            the File --> Open menu item from the CATIA
            toolbar, select the model, choose Add as
            passive and click OK.
  .
  The model is loaded, and the element status changes
  to either:
  .
  - Synchro when everything is fine
  - Conflict when several elements present the same UUID
  - Not Sync when the model has been renamed or moved
  - Modified when elements of the model have been modified
  - Deleted Element when a referenced element has been
    deleted from the passive model.
  .
  For the last three cases, see below how to synchronize
  the models:
  .
  The Source Model has been Renamed/Moved:
  A model may have been moved from one directory to
  another, or simply renamed. The system cannot find
  the element where it previously was. Its status is
  No sync. To synchronize your models, here is what
  you should do:
  .
  Step 1: Click on the element in the Multi-Model
          Elements dialog box.
  Step 2: Click on the Synchronize button.
          The models are synchronized.
  .
  .
  A Referenced Element has been Deleted in the Source Model:
  The reference model still exists. it is located in
  the same directory, but a referenced element has been
  deleted. This element is identified by the Deleted
  Element status.
  You can work with your model as such. The element,
  deleted in the passive model, still exists in the
  active model. It no longer is associative, but does
  not prevent you from working in the models.
  .
  .
  The Source Model has been Modified:
  Now imagine that designer A has modified the source
  model. When designer B opens model A and his own model,
  associativity is kept. Element status is Modified.
  To synchronize the models, here is what you should do:
  .
  Step 1: Click on the element in the Multi-Model
          Elements dialog box.
  Step 2: Click on the Synchronize button.
          The element status changes to Synchro.
  .
  The same applies if the source model has different
  versions, the B elements reference the elements
  contained in the last version of model A. In the
  following example, three versions exist for model A:
  A1, A2 and A3. A3 is the last created version. When
  reading model B, the links between the elements of
  reference are those contained in model A3.
  
     (GRAPHIC)
  .
  Similarly, if B is the active model and another two,
  or more, passive models containing elements with the
  same UUID are loaded, element status is Conflict.
  In this case, you need to explicitly select the
  element which should be referenced, in the adequate
  model.
  .
  .
  When all passive models have been loaded, use the
  Synchronize all button to synchronize all models
  at a time.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  HC42578

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels