Working in OpenRoads Designer is pretty awesome. It's a really smart, well-designed, extensible system. BIM and Digital Twin ready.
Administering it is its dark underbelly. It's extraordinarily complex. The documentation is scattered. Weird "tricks" are required.
Get help!
Instead of a text based configuration file system, like the .ini's and .xin's of yore (they were easy to build tools for), it's "in the dgn" and multiple levels deep. The documentation is scattered. Weird "tricks" are required.
I remember in 1999, pushing San Diego's support team to use the "Five-level System" to manage the the configuration of multiple departments across the City. There was inertia to just keep making the single msconfig.cfg file more and more coplicated. "'Distributed Simplicity' is what the layering is designed for."
Twenty plus years later, OpenRoads configuration is the hardest part of the platform.
The architecture is designed to be flexible without special customization - IF you are a configuration expert. The architecture serves the most complicated scenario: a mega-corporation serving multiple independent clients with the ability to have variations within each. It works for that and more. But it's hyper-complicated. Add in ProjectWise and it's even more complex. And slow.
I used to say "There are two reasons your management has asked you to administer OpenRoads: 1) they know that you are the type of person that will suffer to help others, or 2) they're trying to get you to quit. It's important to know which reason."
I've been involved in the OpenRoads workspace development since near the beginning; I promoted some pivot, quality-related changes early on.