Hi, We are about to setup a new 4D planning with Synchro 4D Pro for a big project with multiple bridge and road renovations. We can either go for the traditional 3D import method or the iModel connection, which both have pros and cons. The biggest pro with the traditional import is that we can easily import 3D equipment models and create 3D workspaces and simple 3D objects, which is not possible with the iModel connection. We want to use the iModel connection for the road models to subdivide 3D objects, create work areas with Synchro Modeler and let stakeholders follow the 4D planning and progress with Synchro Control. We are considering to use both methods to get the best result with the following workflow: The 4D planning with bridges will be setup with traditional import as we will need to create 3D work areas and import many 3D equipment models. This will be a traditional .SP file. The 4D planning for the road construction will be setup with the iModel connection as we need to subdivide and create work areas for those 3D models. This will be an iModel connection. We can export the .SP file from iModel . Then we can import both .SP files into an empty .SP file and upload that .SP file to a new iModel Connection. When we need to modify the 4D planning bridges we can modify the original .SP file and synchronise that file to the combined .SP file. When we need to modify the 4D planning road we can modify the original iModel, export to .SP and then synchronise with the combined .SP file. Afterwards we can create a new Synchro Control project and upload the 4D overall planning. Or is it possible to synchronise .SP files in an iModel environment? Unforunately we will need to export, synchronise and upload multiple files, probably weekly. Is this a recommended workflow? If there are any better alternatives I would love to hear so Kind regards, Stephan Klotz
↧
