Support for Handling Large Publishes - Intergraph Smart 3D - Help - Hexagon

Intergraph Smart 3D Reports

Intergraph Smart 3D
Drawings and Reports
Search by Category
Smart 3D Version

The number of objects published from Smart 3D can become so large that the normal update and publish processing uses up the resources such as memory and address space on the client and server computers. To address these resource issues, Smart 3D now supports the concept of using a cache to keep track of objects that have changed and to only publish these objects. Thus, the software avoids processing objects that have not changed. The mechanisms for doing this are called parallel update, delta publish, and auto-scoping. These processes are not visible to the user.

  • Parallel update - Updates all the objects. The update process determines the number of processors on the system and uses this information to partition the objects so that multiple updates can happen at the same time. Because the updates are happening in parallel, the system can update a larger number of objects faster.

  • Delta publish - Leverages the cached information provided by parallel update to determine which objects must be published. Because only changes are published, you can produce larger files in the data warehouse.

    Because the complete set of objects will not be published each time, it is up to Smart 3D to keep track of deleted and moved objects. These moved or deleted objects will be sent with the published objects, eliminating the need to probe the adapter for the existence of missing objects.

    When you publish a 3D model, you must now enable the Scheduler and Loader in SmartPlant Foundation to make the 3D model data document retrievable. The load, consolidate, and merge tasks must complete successfully before the 3D model document can be retrieved.

Both parallel update and delta publish can publish larger documents by automatically splitting the data into smaller sections in Smart 3D. If your publish data is split into smaller sections, the document version number increments for each section.

For example, if you publish a document that is split into four smaller sections, the Version field contains all resulting version numbers. In the following dialog, the published documents are published to SmartPlant Foundation as 4 different versions (11-14). The last version contains all of the updated information from the publish.