In my Bentley world, none of our local DOT's have developed any DGNLIBS needed for Open Roads. In fact, their XIN files are woefully inadequate for Roadway Designer and many other InRoads Ss2 tools.
I have not been able to spend any time migrating many of their items into Open Roads as I would need to go out pretty far on a limb making many assumptions that could prove to be a waste of time if the DOT decides to do it differently.
Update: Well, now I am one of those local DOT's - Maryland, to be specific. And we are embarking on the Yes column. We actually are revamping the level name convention, and our featured names, point names and more to finally address the various deficiencies of our Ss2 workspace. We are still trying to improve it as well, but most efforts are now in the Open Roads side of things.
So I am making my first Poll. Enjoy
Feel free to reply with any comments or thoughts, too.
Aucivil,
I'm guessing you're from Huntsville?
As the one who started this particular thread, let me answer a few things. I started with InRoads at MD DOT - and we have a single main office that does design. This also did not include the toll facilities, airport, mass transit or rail. Of those, only tolls was also a MicroStation shop. Although when we migrated from IGRDS to InRoads, tolls went to GEOPAK. In fact, within our highway department, the traffic department started with Autodesk and DCA before eventually migrating to Bentley.
As DOT's go, we are pretty small potatoes. From what I understood, PA and Texas (and probably others) had district based design offices that were as big as our HQ office. So now, I work for a minority owned firm. We have approximately 12 seats each of Bentley PowerInRoads products and 11 seats of Civil 3D. Most of my users (I'm the CADD Manager as well as a designer) have to be able to work in either. We also do a fair amount of Survey work, probably equally split too.
My plan, is to stay in Ss2 until the DOT clients develop DGNLIB's capable of being used with Ss3/4. I have seen some US COE workspaces that look promising. For my world, I even have to deal with probably 5 or 6 different level naming conventions. At least where you are, you hopefully have one.
At the DOT, the mass transit department has migrated to Bentley, but decided the V8 level names that the highway and tolls departments were using was not good enough, so they opted for a modified NCS approach xx-xxxx-xxxx. Unfortunately, their system is different than the Army Corps NCS system.
So, between Civil 3D and Open Roads, I still prefer Open Roads. The initial setup for Civil 3D is as daunting as Open Roads. Survey alone is far more complicated and their is no XIN file. Eveything must be done in a Civil 3D seat and all settings are stored in DWT (templates) so managing them is much more complicated. Are there some Civil 3D things I like? Yes. But other areas are annoyingly over complicated.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration