Scribd
Upload
293 views6 pages

AVEVA E3D - 02 MVC - Structures - 7. Storage and Automatic Hierarchy

Uploaded by

mhmd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
293 views6 pages

AVEVA E3D - 02 MVC - Structures - 7. Storage and Automatic Hierarchy

Uploaded by

mhmd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

AVEVA Everything3D™2.

1
Structures
Storage and Automatic Hierarchy
Manual Storage
 There are two options for storing GENSECs and PANELs,
Manual Storage and Grid Storage.
 When Manual Storage is selected the user must navigate to
the required FRMW or SBFR before modelling commences.
 The FRMW or SBFR and the owning STRU names are
displayed in the Storage group gadgets.

 If another FRMW or SBFR is selected, or a GENSEC or PANEL


selected in the 3D view, the Manual Storage gadgets will
change to reflect the current storage location.
 The Manual Storage location may be locked so that the
storage location remains the same despite changes to the CE.
Copyright © 2013 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Grid Storage and Automatic Hierarchy (1)

 If a Reference Grid is used to place GENSECs or


PANELs, hierarchy elements are created
automatically.
 SITE, ZONE, STRU and FRMW elements are created
automatically or only the STRU and FRME elements if
the SITE and ZONE already exist.
 The STRU element has a GrdRef attribute which
points to the REFGRD element.
 The FRMW element’s RefGrd attribute points the
appropriate GRIDPL (Grid Plane) element.

Copyright © 2013 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Grid Storage and Automatic Hierarchy (2)

 New FRMW elements are created if a member is


placed using a different GRIDPL with it’s RefGrd
attribute pointing to the appropriate plane.
 If a FRMW already exists for the GRIDPL, additional
members are stored in the correct FRMW.
 Where it may be ambiguous which GRIDPL an
element may belong to, e.g. a corner column or edge
beam, rules are applied to select a plane.
 Alternatively, a GRIDPL may be selected by clicking
on it’s label and the Grid Storage locked.

Copyright © 2013 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Grid Storage and Automatic Hierarchy (3)

 If members on one GRIDPL, i.e. owned by one


FRMW, are copied and pasted onto different
GRIDPLs, new FRMWs for the GRIDPLs they are
copied to are created (if they don’t exist).

Copyright © 2013 AVEVA Solutions Limited and its subsidiaries. All rights reserved.

You might also like