We have a WIP Workspace that is currently in limbo due to COVID-19 budgetary impacts. It originated as our Ss4 workspace and was migrated with Chuck Lawson's assistance as part of our DOT Amp process. During the migration process, we tested using as many of our legacy settings as possible with the hope that migrating a project from our Ss4 workspace to CONNECT would be as painless as possible. We did see a number of issues that were troubling, but they did not seem insurmountable.
Recent posts in this newsgroup have made me want to revisit those concerns. Here are some of the issues we found:
Has anyone else found that they had to make impactful changes to their default settings and how has that impacted ongoing projects.
Are you talking about taking MicroStation Workstation template files and adjusting them to work within ORD? It seems like it may be best to rebuild your workspaces from training or default templates instead, because the amount of unsolvable (for me anyway) errors I got trying to adapt a MicroStation workspace into ORD was too much.
I had all manner of painful issues with ORD crashing constantly, even with the most minute of tasks like selecting a complex element. Even when it wasn't crashing, it would regularly take 5 minutes plus just to select a simple element. I tried all sorts of things myself and eventually found that I had to just start completely fresh work from a default training workspace. Any mingling of MicroStation workspace settings with ORD workspaces seemed to cause a nightmare amount of errors and crashes in ORD.
Granted I haven't anywhere near the experience you clearly have, nor training (because what forward thinking organization invests in that, right?) but even when I tried troubleshooting some of the issues I was getting with one of the Bentley support gurus, he recommended I just switch to a training workspace and go from there, and it solved the bulk of my problems.
We expect to have to migrate a ORD Workspace to function in plain CONNECT. Our Highway Division is the 800 lb gorilla - we drive the CAD System, with our workspace enhanced to fit others needs. But if someone does not use InRoads (legacy) or Open Roads Designer (still not implemented), they still use our workspace for MicroStation. We are hoping that any legacy projects can be brought forward into CONNECT (ORD or MicroStation) with minimal issues. My post was prompted by other discussions that seemed to indicate that this might not be possible and that can be a big problem. At a DOT, projects are routinely shelved due to changing priorities, politics, funding and many other reasons. When one is brought off the shelf, management does not expect a complete redo, but anticipates that it can be picked up and used as-is. If recommended and possible required settings make that impossible, I need to know as does my management.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
I still remember when we tried this in the first version of ORD - we missed "upgrading" some of our old OR workspace material and any SS4 feature definitions would cause a massive lag doing certain things. We also had some major stability issues at time. My personal opinion is that deployment of ORD should wait till you have a workspace ready, or at least put together a minimal fresh setup and add material as needed - ORD is very temperamental at times (as you probably already know).
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023.1 | ProjectWise CE 3.4
Part of my concern is how far into our Workspace setup before learning of these potential issues. We need s lot of work in our SUDA/SUE and Civil Cells. But as we learn more, we know we will need more Feature Definition and annotation efforts.