I have a few projects that are active with SS2 and SS4. I need to know if I can open and run the drawings in the OpenRoads Designer (CONNECT) Version 10.06.00.38, then continue designing. If that is not possible then I may have a problem.
I don't thinks so. Openroads Designer (CONNECT) runs under Microstation CONNECT. Where SS2 and SS4 runs under Microstation V8i. But I am sure someone can verify this.
Joe Lukovits
User Since TDP in the 80's,
Vax based Unix Workstations - Interpro32,
from the Intergraph Corp.
Luke
What SS2/4 product are you running? If (for example) you were using InRoads, you would need to import your alignments from your .alg file(s) into ORD (as ORD stores the geometry in the DGN file).
What do you mean by 'run the drawings'?
I and my company are running inroads from SS2 and/or SS4 depending on the project or client. We are also using .alg / .sdb / .dtm / .csv / .ird / .itl / .dat / .xin / .dft / .idf / .mdb / .rpl / .set / .cel / .pen / .tbl and of course .dgn All file types are being used in one way or another.
Our company wants to begin to use OpenRoads. It is impractical to immediately switch all employees and train all employees at the same time. A cascade switch and training makes sense. During this process, I need to know if the trained users can use OpenRoads on a project while untrained users can use SS2 or SS4 for the same project. Is there a process that needs to occur with the data? Is the data transfer only a one way transfer? Is there a loss of data integrity with the transfer?
Will I need to segregate my projects within my company based on who has been trained or not?
Luke, you import.alg from SS2 and Dtm’s from SS2 and Templates. The templates may need to be changed to match the feature definition in ORD. But I don’t think that SS4 is compatible with ORD due to the file structure as SS4 has built in terrain models and geometry that is not compatible with ORD. We plan on a slow transition to ORD and still use SS2. We will use SS2 and import to ORD as needed. SS4 is out of the picture for me
I would also suggest as a training program to take an existing project from SS2 to ORD. I am doing that now. You can see what you will be up against when doing this
Short answer: yes.
It's may not even an issue of training, though that will play a huge role. Moving projects from SS2 to either SS4 or ORD is nothing less than a pain in the a$$. Moving projects back is ten times worse.
Feature definitions, element templates, text favorites, annotation groups, and more need to be set up to match the standards you currently have set up in your .xin and other standard preference files. DTMs and terrains work quite differently and, while SS4 and ORD can import DTMs, the only way to convert a terrain to a DTM is to export a LandXML for import into SS2. Geometry projects must be imported into the OpenRoads products but, again, the only way back is through LandXML. Template libraries "can" be shared between the three but several settings will need to be changed when moving between the products. There is a process for converting roadway definitions (.ird) to corridors but there is no way to go back.
To make things worse, you can't count on moving data easily between the various releases of ORD.
Even though we're starting the transition now, we will have projects in SS2 for several years due to the complexities of data translation.