Model Data Reuse (MDR) - Intergraph Smart 3D - Administration & Configuration

Intergraph Smart 3D Project Management

Intergraph Smart 3D
Administration & Configuration
12.1 (2019)

Supports the following tasks:

  • Copying large amounts of data from a source model in one site to a destination model in a different site.

  • Copying large amounts of data from a source model and reuse that data within the same site, either within one model or from one model to other models.

Clicking Tools > Model Data Reuse opens a wizard that you use to set up the data reuse operation. You use the wizard to do the following:

  • Identify the source model that the data is copied from and the source object selection method that you are using. You can select source data by Source System or Source Objects by Filter.

  • Identify disciplines to copy in order to filter unnecessary objects.

  • Identify the destination model where the data is copied and the destination parent system in the destination for the copied objects.

  • Identify the permission group for the copy destination and perform any permission mapping, if necessary.

  • Select the mode of transformation to determine where the copied objects appear in the destination.

  • Resume Model Data Reuse (MDR) copy operations that are stopped manually or interrupted by a hardware or software failure.

The full set of objects to be copied is divided into a sequence of smaller partitions, and each partition is copied in a separate transaction. Relationships between objects in different partitions are copied along with the objects in later transactions. If a single partition cannot be copied, the operation does not stop, but instead continues with the next partition.

When the MDR operation completes, the Operation Properties dialog box displays and shows the general information of the operation, the status of the operation, and a breakdown of the number of design objects copied, copied successfully, and failed to copy.

If you encounter low memory conditions while running Model Data Reuse, the current operation stops, and an error message displays. To continue, you must first restart Project Management, and then you must restart Model Data Reuse to continue. After completion, the Operation Status displays as Stopped: Low Memory in the Operation Properties dialog.

For more information, see Model Data Reuse Wizard.


You can exclude any objects from the source select set and MDR will copy the remaining objects.

Copying small quantities of individual children objects without a parent system is not supported in MDR. For example, copying piping features without the parent pipe run is not supported. Copying marine profiles or seams without the parent plate is not supported.

Compatibility between Sites

Model Data Reuse can only copy between models from compatible sites. Compatibility includes the following criteria:

  • DBMS Provider - MDR can only copy between models that are based on the same type of underlying database management system (Microsoft SQL Server or Oracle). The Select Site Dialog only allows the selection of a site from a compatible server.

  • Software Version - MDR can only copy between models that were created with (or upgraded to) the same software version. If you select a source site with a different version from the active site, an error dialog box displays, and you are prevented from continuing.

  • Catalog and Schema - MDR can copy between models with different catalogs and catalog schemas. If you copy across sites, or if you have multiple catalogs in the same site, the source and destination models are attached to different catalogs and catalog schemas. In this situation, a warning dialog box displays stating that the catalogs are different. You can still proceed with the copy operation. Later in the Model Data Reuse Wizard, the Compare Catalogs page displays. Use this page to compare the catalogs and catalog schemas to identify differences in the catalog schema before you start the Model Data Reuse operation. The Compare Catalogs page also allows you to map the catalog's content, if there are differences. During the MDR operation, the copied objects are automatically adapted to their destination environment. The adaptation logic ensures that the schema identifiers (GUIDs) stored in the model are updated to be consistent with the destination schema.

    When you copy pipe specs across two different catalogs, make sure that the source and destination specs are in the same units of measurement (NPD). If the units are different, computing errors may occur. For more information, see Model Data Reuse Wizard: Compare Catalogs.

  • Compatibility Verification - Only compatible sites are available for you to select. Incompatible sites display, but they are not selectable. If you select an incompatible site, the software displays a message box explaining why that site is invalid.

Oracle Tablespace Extension Before Large Copy Operations

The Oracle database system is normally configured to automatically extend the tablespaces by a small increment. During interactive work, data is added in small increments, and the automatic extension of the tablespaces works fairly well. However, during a large MDR copy operation, in which a large amount of data is added, many incremental extensions of the tablespaces can cause slower performance. To address this issue, you can extend the tablespaces one time to accommodate all of the new data before starting the MDR operation. This allows the MDR operation to proceed at full speed without waiting for the software to extend the tablespaces multiple times.

You can calculate how much to extend each tablespace by determining the total amount of data in your database and multiplying by the percent of the model intended for copying. For example, if your current model occupies 1.2 GB of storage space in a tablespace and you will be copying one quarter of that model, you can estimate that you will need at least 1.5 GB to hold the model after the copy is complete. You can calculate the amount to extend the tablespace by finding the difference between the current tablespace and the required size. Follow a similar procedure for both the data and the index tablespaces, rounding up to the next larger 100 MB. Contact your database administrator for details about how to extend the tablespace.

Model Data Reuse Wizard

What do you want to do?