Moving from MX Rail to ORD

RE: Moving from MX Rail to ORD

jpln — Thu, 26 Mar 2020 13:23:32 GMT

Yes please, email to jp.laville-noel@bentley.com

RE: Moving from MX Rail to ORD

Adam Riley — Thu, 26 Mar 2020 10:20:05 GMT

Hi - thanks for the offer. I can't seem to upload files via private message. Can I email them to you, please?

RE: Moving from MX Rail to ORD

jpln — Tue, 10 Mar 2020 12:20:18 GMT

Yes there are some typical plans to do upgrade from MX/INROADS/GEOPAK to OpenRoads/OpenRail.

You should talk with yiour bentley sales contact.

I know Robert Nice is actually developing workspace for UK.

Could you send me pss/fns for the track I can have a look ?

For detailed survey, we don't have anymore to display data from a model (database) but we are using the graphics instead (DGN/DWG). So it is a matter of receiving the good representation then usually we are using a graphical filter to create the terrain model from the graphics.

RE: Moving from MX Rail to ORD

Adam Riley — Fri, 06 Mar 2020 10:10:39 GMT

Hi. Thanks for the reply. Would we be able to get a quote for someone to do this conversion for us? Otherwise, NR will end up with the same confusing situation it had when BRT was rolled out. MX came with the standard parameter file and these style sets, but BRT was so messy that different teams had so many variations on dgnlibs that it was a disaster. If an expert in your company is able to take the files I've posted above and convert them through whatever process necessary to make something that works with OpenRail, it would be ideal. That's our main starting point, and then we can move forward with testing ORD properly.

RE: Moving from MX Rail to ORD

jpln — Mon, 06 Jan 2020 10:09:41 GMT

Hi Adam,

As per annotation capabilities (PSS), nothing can be imported from MX to OpenRail. It is totally new, with new technology.

Only OpenRail feature definitions (a kind of MX string styles) can be created from PSS by using MX SS4. Through Project Explorer you can import PSS to create feature defintions. You must do this in a dgnlib. Then, this dgnlib can be upgraded to OpenRail Designer.

Then you will have to complete the feature definitions in the DGNLIB to get the same you had in MX.
Basically, Feature Definitions are using feature symbologies that are using element templates that are using levels. Feature symbologies are also using Annotation group to produce different types of annotations.
Annotations are using Text Favorites. If you don't know anything about text favorites, then it is probably the main thing you will have to become familiar with. Evrything else is quite basic.

The best is to have a look on delivered workspaces and on learning content about OpenRoads workspaces.
https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=111346

You don't have thousands of styles so you can start creating from scratch at least for design style.

Look into C:\ProgramData\Bentley\OpenRail Designer CE\Configuration\Organization-Civil\_Civil Default Standards - Metric\Dgnlib\Feature Definitions to do the same in a workspace or workset so that it will be automatically loaded when using this workspace or workset.

File names include words to indicate what is being loaded. Example *feature*.dgnlib or *Elem Tem*.dgnlib

Almost everything is configured through DGNLIbs set through workspace/workset (configuration files and folders).
Most of parameters (prm) are by default set in "C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\Organization-Civil\_Civil Default Standards - Metric.cfg" or in File>Settings>File>DesignFile Settings