Plant Layout Design File-Based Design Import

The File-Based Design Import (FBDI) product translates documents from V5 to V6. Not all material entities created in V5 can be imported in V6. This topic provides information on how Plant Layout Design features are migrated in V6 release.

Version 5 Version 6
Importing Files from the Previous Version

V5 Human Walk Activity Pointing to Area

In V5, Plant Layout provides a command to create Area. V5 plane-based Human Walk-Activity points to this Area.

V6 Human Walk Activity Pointing to Footprint

In V6, FBDI for Area is not available.

In the case of V5 plane-based Human walk-activity, the V5 Area is converted to a Plant Layout Design footprint during FBDI. For details about FBDI of the human walk activity, refer to the Ergonomics Evaluation User's Guide.

In V5, if the Area product is listed under Product list, then that Area product will be migrated as product under the root product node in V6.

V5 Attachment

If V5 Attachment is modified after doing FBDI to V6, you need to reimport the entire file with all the pointing documents to V6 again to get the changes done in V5.

V6 Attachment

Currently entries related to Attachment are not stored in mapping tables. Consequently, the Attachments formed during FBDI are deleted during reimport in the initial step of the FBDI in 'Update' mode. In its place, a new V6 attachment corresponding to the V5 attachment is created.

Note:

The existing session needs to be closed before FBDI is undertaken. If the session is open, it causes a migration error.

Duplicate copy of data is not created. The changes are updated in the existing documents.

V5 Footprint

If V5 Footprint is modified after doing FBDI to V6, you need to reimport the entire file with all the pointing documents to V6 again to get the changes done in V5.

V6 Footprint

Currently entries related to Footprint are not stored in mapping tables. Consequently, the Footprint formed during FBDI is deleted during reimport in the initial step of the FBDI under 'Update' mode. In its place, a new V6 Footprint corresponding to the V5 Footprint is created.

Note:

The existing session needs to be closed before FBDI is undertaken. If the session is open, it causes a migration error.

Duplicate copy of data is not created. The changes are updated in the existing documents.