Moving A Plant Project to Vault

29 September 2020All, plant 3d, Vaultplant, Tips and Tricks

Partager

image-12.png

We have many clients who are use Vault with Plant for a variety of reasons. For some they must have their data living on their own servers, for others, they have workflows and approval processes not supported by BIM 360. In any, we have helped each get their projects into Vault and have an idea of the types of issues people run into.

New call-to-action

A couple pieces need to be in place before you attempt putting your project in Vault.

  1. Vault Server Configured
  2. User Permissions Configured
  3. Plant 3D SQL Server configured

Each of these items is a significant undertaking and will not be addressed in this post.

New call-to-action

The main steps to getting your project on Vault are:

  • Run Plant Project To Vault Command
  • Troubleshoot
  • Validate

PlantProjectToVault

The first step in migrating a project is to make sure you project doesn’t have folders or drawings outside of the project folder before attempting the conversion.

In short, while the folder names or sub-paths may be different, all of your data (specs, P&IDs, models, etc) needs to be fully encapsulated within your project folder.

When ready to start the conversion, by entering PLANTPROJECTTOVAULT at the command line, you’ll have a dialog that will walk through the process. The most critical point here is that you must have Vault Administrator permissions the first time you put a project in Vault.

First is the login screen.

Next, you’ll get the screen for capturing the information on where to place your project.

After filling out the dialog with the appropriate information, click start and the migration process will begin.

Troubleshoot

In a lot of cases, this process goes perfectly. However, we do run into a few common issues.

  1. Content not in project folder (you have to move it).
  2. Bad Xrefs (detach, and then re-attach later.
  3. Bad File paths (remove from project, and add later).

In general the fixes involve removing offending files, and then using Copy Drawing to project to put them in the Vault project.

Validate

To make sure everything went well, and that you don’t run into weird issues down the road, we recommend validating the project.

  1. Make sure off page connectors functionality works for previewing, and opening connected drawings.
  2. Make sure Orthographic drawings can utilize update views, locate object in model, and annotations
  3. Run some isometrics.
  4. Test reports.

If you’re still having trouble, we’d love to help. Also, we have a full guide documenting adopting Vault with Plant 3d in our Plant 3D Boost product.

 

 

New call-to-action

System Requirements for Bluebeam Revu 21

15 January 2024All, BluebeamRick Kremer

following are minimum and recommended requirements when using Bluebeam Revu with office documents and construction project documents

System Requirements for Autodesk Revit 2024

10 April 2023All, Architecture and Engineering, autodesk, Digital Transformation, MEP, RevitEric Daniel

List of system requirements for using Autodesk Revit 2024 and Revit LT 2024, entry level and performance level, plus Citrix,…

Important Bluebeam Announcement

4 April 2023All, Bluebeam, IT Services, Services & SupportDiana Ramirez

Bluebeam has announced the updated End of Life (EOL) date for Bluebeam Revu 2019 and older versions will now be…