We hear many people wonder how they can get access to the Plant 3d database from ACC. Some companies have been using SQL Server to host their projects internally, but need to move to the cloud to support multi-office collaboration. The downside of this is that when you move to the cloud, you lose direct access to the SQL Server data you formerly connected to.
Our Project mirror tool closes the gap between the Plant 3D ACC database, and your previous workflow. The project mirror tool can be download your data, on a schedule and then push it to a SQL Server of your choice.
Overall, we are fans of having full control of our data, and the project mirror tool is the step you need to start that process.
Another feature we’re evaluating right now is merging the 5 Plant 3d databases into a single database. On the roadmap, we would like to start making databases accessible via AWS, and pushing a single project to a database will definitely ease that transition. Here’s what we were thinking for the schema changes, basically appending the database type (PnId, Piping, Iso, Ortho, Misc) to the table name.
What other steps are you taking to own your #plant3d data in your own environment?