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?
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.##)
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
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"
...
%endif
Rod WingSenior Systems Analyst
that does not control version though.
I know it is only theory right now , but I was basing it off of the naming convention you used for your folders.
You have it defined with the product and the version - so I thought OBM would be set the same way.
That's probably OK.
For the DOT's that roll out their configurations this way, they are upgrading both ORD and OBM at the same time. Then you manage the OBM _USTN_CUSTOM_CONFIGURATION the same as you do for ORD.
I guess the other thing is I haven't run into any client using OBM who isn't also using ORD. I also haven't had any requests so far to access OBM only WorkSpaces from MicroStation.
I'm sure that day will come too.