There have been other questions here about having MSCE open ORD configurations, which is not really a problem by itself, but now the plot thickens....
This is a bit long, but stay with me, some of you may be facing the same issue.
Within the past week I have been contacted by two clients about setting up the MicroStation configurations so that they can utilize WorkSpaces from different versions of ORD, and also accessing non-ORD based configurations.
The situation is as follows...
How do you configure MicroStation to access three different sets of standards stored under three different Configurations?
The solution I have come up with so far is:
This seems to work well, however...
DOT A also has older projects in ORD 10.9 that are not being moved to ORD 10.10. How can I tell MicroStation to access the ORD 10.9 WorkSpace instead of ORD 10.10?I can't change the WorkSpace name because the dgn's are branded to the other WorkSpace name, changing the branding would introduce all sorts of other problems.
I also haven't tested this with any ORD configurations that implement Roles. That might be another sticking point.
Anybody else having the same problem?
I keep bringing this issue up "in house" to get feedback on possible solutions going forward.
This is going to become a nightmare for anyone managing this.
I wonder if the ProjectWise Managed workspace will handle this any better ? (I am not currently using this which is why I posted the question).
CADD Manager | CADD Department
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
question: what happens when you have OBD (bridge) involved here as well ? would you have another set of folders for this product since it's configuration and version needs to be a separate entity ? (IE: P:\CAD\OBD\OBD 10.##)
I'm not that up on ProjectWise either. From what I understand it will handle the multiple ORD configurations, but I don't know if it would handle throwing MicroStation into the mix as well.
FYI... I tested the latest NCDOT ORD 10.10 configuration that uses the Role configurations in my scenario and it worked without issue.
Rod WingSenior Systems Analyst
that does not control version though.
I haven't had to deal with OBD, yet.
For OBM it hasn't been a problem, as several DOT's include the OBM standards with their ORD download using the same configurations.
In their configs they have this structure to load the additional OBM resources
%if $(_ENGINENAME) == "OpenBridgeModeler"