Supports disconnected workshares
Because you publish the data to files at the source site and attach as a reference
at the target site, the software does not require a live connection between the databases.
Periodic publish and update of the R3D models would allow multiple partners to work
on a joint venture product in a disconnected manner.
Preserves intellectual property in joint venture projects
The publisher can control the quality of published information which can protect intellectual
property of individual firms participating in joint venture projects. In addition,
sensitive data such as piping specifications are not published.
Allows for better security in joint venture projects
This solution allows for better security because trusted network connectivity is not
required. Published files can be transferred using any appropriate mechanism.
Provides compatibility between datasets from different Smart 3D versions
You can publish 3D model data to a relatively neutral format that allows mapping.
Therefore, data from different versions of Smart 3D can be mixed and matched.
Bridges differences between Smart 3D datasets on disparate databases
Because the data is published to a set of files, the underlying database platform
(MS SQL Server or Oracle) is not a concern.
Work with datasets from external tools such as PDMS and XMpLant
Data from other tools such as PDMS and XMpLant can be translated to the format recognized
by R3D and then referenced into Smart 3D. This allows for heterogeneous tools to be used on a single project.
Supports parallel design for increased productivity
If a project has many similar units, only one unit can be modeled and published. This
published unit can then be attached multiple times with the required positioning.
Additional modeling such as civil work can be performed simultaneously on all the
units by working with the references. In addition, if the original unit is changed,
using R3D can be more productive because R3D is more flexible for updates. When the
original unit is completed, Model data reuse functionality can be used to replicate
the unit to obtain real Smart 3D objects.
-
You can attach R3D models at the host and at the satellite. You must attach an R3D
model at the host location before you can attach a model at the satellite location.
-
The software does not automatically copy files from the host to the satellite location.
The file path for the R3D models can be modified at the satellite location so that
the graphic files (.zvf files) can be accessed from the local satellite folders. However,
the files must be copied to the satellite location by other means to keep the folders
synchronized.
-
You must specify the complete path to the folder. The software does not accept a relative
path such as a path relative to the symbol share.