Implementating a new system is the most critical part of the system. If you do that wrong, everything else is at risk.
OpenRoads in paricular does not lend itself to a trial and error approach to success. Because of its native file integration, its object relationships (and interdependency), and multi-layered technical stack (particularly in its administration), poor practices and errors may not show up until late; mitigation is often time-consuming and difficult.
Experience matters with OpenRoads.
I've first led large-scale Civil Software implementations in 1995 and have been deeply involved with account success ever since. For details, see JeffMartinPE.com Implementation.
Whether it's managing the full software administration-to-training project or simply talking to subject matter experts (like the hydraulic leads of multiple DOTs), I can help.
Want to save time and money? Agile Implementation accelerates (xlr8s) the traditional discrete-phased process by progressing multiple tasks simultaneously. The key to this is continuous communication (rather than large infrequent "deliveries").
