When you have multiple PlantSight Projects or multiple iTwins within a PlantSight Project, switching between them before opening OPM can be come cumbersome, when you have 50 PlantSight Projects it become a nightmare to manage users opening the correct one.
ProjectWise workspaces can be used but when you have multiple workspaces due to contractor settings, you can end up with 200+ workspaces/Application setups in ProjectWise.
Ability to also select a PlantSight Project and iTwin separate to selecting a WorkSpace and WorkSet, before or after or in ProjectWise just have the ability to select PlantSight Project and iTwin.
| How frequently will feature be used? | A few times a week |
| How much time will you save? | This will reduce the confusion of how to setup multiple PlantSight Projects and reduce errors |
| Your Industry | Oil & Gas |
| Other Industry | All other |
Thanks @Guest Got your point.
Hi Waqas,
I have 50 operational facilities all in different PlantSight iModels and 2 major contractors doing small projects on any of these 50 PlantSight iModels. I am the administrator so have OPA installed, but Designers and our contractors do not have OPA.
Scenarios
As the administrator I can use OPA to switch between the PlantSight iModels, but this is slow and cumbersome, so I have 50 sets of workspace .cfg and .dgnws I manually replace in the workset using Explorer before starting OPM.
How can I manage 50 PlantSight iModels with 2 contracting companies with different designer’s accessing different PlantSight iModels? (the answer is not 50 worksets)
How can I manage the 50 PlantSight iModel connections in ProjectWise using Managed Workspaces, I have a Workspace for each major contractor setup? (the answer is not 100 (50 x 2) Workspace setups and OPA will not help)
Something is needed to be able to select the PlantSight iModel in OPM like you do a Workset.
Thanks Ray.
@Guest I need a bit of clarity here.
Currently, the association between the PlantSight project, iModel, and WorkSet is established using OpenPlant Project Administrator (OPPA) before launching OPM. This setup ensures that the correct project configuration is loaded when OPM starts.
From what I understand, you are looking to:
Independently choose a PlantSight project and iTwin, rather than being strictly bound by the WorkSet configuration.
Have this flexibility directly within OPM instead of setting it up via OPPA.
Wouldn't this approach also be somewhat cumbersome since it would still involve a manual selection process similar to the current setup?
Also, could you clarify your specific use case:
Are you looking to switch the same workset association with different PlantSight projects and their iTwins?
Are you envisioning this functionality directly within OPM rather than through OPPA?
Understanding this will help in exploring potential solutions.