I'm asking this question to get a general idea of what others may be doing as far as the development of their final work products. Most of our clients still require a traditional plan set (i.e. title, details, tabulation of quantities, plan, profile, cross sections, etc.) as the final deliverable mostly in PDF format BUT sometimes hardcopy.
For those in the same situation, if you don't mind responding, are you using both MicroStation & ORD to develop these plan sets?
Thanks in Advance
I haven't produced a final set of plans yet, but it seems as if OpenRoads contains all of the regular MicroStation toolset, so we will not have to back and forth between software. But we will be using "plain" MicroStation tools as well as ORD tools to produce our plan sets. ORD does a lot, but it doesn't do everything, and not every sheet in a plan set is a plan/profile/cross section.
Microstation 08.11.09.919Power GeoPak 08.11.09.918Power InRoads 08.11.09.918
Thank you for responding. So is your configuration environment setup to allow both ORD and MS access the required resources (DGNLIB's, etc..) to build a consistent plan set. The reason I ask is because I recently encountered an issue w/MS & PD and got Bentley support involved. When I asked about sharing the same standards. This is the response I recieved.
"I just confirmed because MicroStation and Open Roads Designer are separate products and not designed to work together as when are civil products were layered on top of MicroStation the ORD workspace you are getting from the client would need to be move/copy the needed files and settings to the MicroStation workspace. i.e. if you are given a level dgnlib file in the Organization-Civil folder structure, the user will need to copy the file to the MicroStation Organization folder structure.
The Bottom line is that anything in the “Configuration\Organization-Civil\” folder structure that is needed by MicroStation needs to be moved to the “Configuration\Organization\” folder structure and you need to set your MicroStation variable _USTN_CUSTOM_CONFIGURATION=D:/Network/Configuration/
Only ORD Data that is not used by MicroStation should be in the “Configuration\Organization-Civil\” folder structure.
If your clients are delivering the data needed by MicroStation in the “Configuration\Organization-Civil\” folder structure, then the clients are not setting up the configuration correctly. The client data used by MicroStation should actually be in a Workspace and not in the Organization folder structure. That way you can switch between different client data/standards by switching workspaces. If you use the Organization folder structure, it will get used for all clients in MicroStation."
In our case, the client-supplied "environment" was built by Bentley... Seems kind of ODD that both or all three applications couldn't work together.
Just my opinion.
Thank you MaryB, Mark and Benzi for your responses.
MaryB - I 100% agree with you. I have always been able to configure MicroStation and any other "CAD-related" apps to a network going back to MicroStation J (Yes, I am dating myself) and never had the issues I have encountered with Connect. So that's why I was so put-off by supports response.
Ironically, I setup our environment pretty much as Mark described. The only issue I had was having was periodically, both applications (MS and/or ORD) would "stall" either during the initial opening or when closing the applications, not exiting, but closing like if you were to switch from one workspace or workset to another. That's what prompted me to contact support and hence get us where we are here today.
Long story short:
This configuration has provided the best results for both the MicroStation/PowerDraft applications and ORD to share the same resources.
Benzi - I love the idea of pushing those files to the users specific device. I'll talk to our IT group and see if that's something that can be automated through AD or something. If not, I'll definitely do the batch file just like you did.
Thank you all for your responses, its greatly appreciated. I'll keep everyone posted with any issues or observations that may impact using this deployment method.
Just to clarify:
One thing that has prevented issues with loading or crashes is creating fresh DGNLIBS for ORD and the other CONNECT products based on the newly supplied seed files. In other words I didn't copy or upgrade the previous SELECTSeries DGNLIBS or seed files into the CONNECT folders.
I used blank ORD seed files and imported either CSV or XML files created by exporting the various standards from previous SELECT versions using the Migration Tools supplied by Bentley.
The bottom line is that we don't share resources between SELECTSeries 10 and CONNECT products.
Roger that Benzi… I created new DGNLIBS from connect seeds and imported the standards.
Indeed, Benzi. I experienced the same early on and decided to start from scratch importing various XML's to create new libraries. better to build good than build "easy".
Yes, Charles, as well I did modify my ConfigurationSetup.config file as you have mentioned. I forgot about that one in my narrative, but the interesting thing is that I am so glad that I became involved in this thread to refresh my mind of this file. We are just starting to get our users on ORD (network) and I am sure that I would have merely copied the WorskSpaceSetup.config file and would have to eventually answer as to why their machines are not working quite as well as my own!
P.S. Benzi, great work with the bat file; a superior solution for a company with many users.