I have a number of legacy InRoads SS2 projects where the project data will have to be moved to the current version of ORD. The designer(s) at the time made extensive use of feature point controls as well as other advanced SS2 features. Without maintaining a SS2 computer and license for ever so that in the future, the legacy design can be reused as in BIM, What is the best way to handle this legacy data?
Bentley has been blowing the BIM horn a lot lately, so I am wondering how that they are handling this? ORD must be able to read legacy data and convert it to the current version of ORD, what ever that version is as legacy data will be here for a long time, or is BIM just a bunch of hot air?
It is possible to migrate data to the newest version of ORD, but the workflow required depends on the type of data. You can import alignments into ORD using the import IRD tool, and there is a Version Checker application that upgrades DGNs to be compatible with ORD. The Version Checker can't convert from SS3 or older, so you would have to open files in SS4 to upgrade the schema. Once civil geometry is opened in SS4, you should be able to convert to ORD. I have also placed a Help link below that talks more about the IRD tool. Hope it helps!
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Thank you Jacob:
I am trying to figure out ways to bring InRoads SS2 data forward, when SS2 and SS4 will no longer be available. My client is still using SS2, so I can recommend how to store the data in a better way. DTM can be saved as 3D linework. Alignments, the same. IRD files as long as the point control is kept as 3D linework, that will work also. Keeping the corridor as 3D linework is even better as long as enough levels are used. The saving grace is ORD is able to import linework and use it. It is not as friendly as reading legacy files directly, (BIM) but it is a work around.
David E. Stewart
Good afternoon Charles:
As I understand it, InRoads SS2 users can pick a feature and use it as point control. The corridor looks for the feature by name. ORD works in a similar way, it wants a feature definition or an alignment.
I am trying to future proof the data as I expect that SS4 will not be around in a few years or at least not supported as it will be 10 years old also.
Ss4 is being succeeded by Ss10. Ss10 is basically Ss4 but using CONNECT licensing. It will be supported for at least a year and a half, unling Ss2 and Ss4 which will stop functioning 30 days after the Select Server License Server is turned off - Dec. 31, 2020. Unless you convert some pooled seats to Node Locked Seats.
So the question still stands - what does an InRoads ss4 user have to do to bring an IRD file into Ss4 or ORD if that IRD used a DTM Features as a Point Control. When a DTM is brought into a Terrain Model, the Feature Styles are discarded unless you elect to bring in all features, which it reported to be a bad idea due to the amount of extra overhead it brings to the Terrain Model.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
I believe it is possible to bring in the terrain in without the features, then go back and "add graphics" for just the features you actually need (which will become terrain features with feature definitions once added). But I don't know if that would preserve the features as point controls, or if that would all need to be redone.
Microstation 08.11.09.829Power GeoPak 08.11.09.878Power InRoads 08.11.07.615
Mary: When the SS2 IRD is imported into ORD, the SS2 Feature names need to be redefined. The entire corridor has to be checked. If SS2 is not available, then it is impossible to determine what SS2 feature should become what feature definition. It is like starting all over again.
At the moment, if SS2 is not available, then importing the SS2 3D model into ORD is a lot faster and easier.
I have a data set that was used for training at MoDOT that was GEOPAK based Ss2 into SS3/4 that I was able to modify to work in InRoads and Ss10. I even made their features point at our Named Symbologies or their Element Templates point at our levels for most of the features. Since our Ss4/10 Features were used to create our migrated ORD workspace, I'm also planning on testing bringing that data into ORD.
As part of our migration process, I am recommending everyone write all features and components from their Ss2 projects into a series of DGN files and/or models.