File branding by Product is problematic for Organizations where multiple software solution are deployed like OpenSite, OpenRoads, OpenRail and OpenBridge. The schema(s) within the file should be analyzed at file open rather than the last authoring product to determine whether any schema alignment needs to take place. This creates lots of extra work to maintain multiple products on a machine.
For instance - Assuming same major versions of products:
File with only an alignment created in OpenSite Designer:
OpenRoads prompts to rebrand from OpenSite to OpenRoads
The file would have to be re-aligned back to OpenSite for use with Civil File Manager.
OpenBridge cannot open the file for edit, without 1st running the Civil File Manager.
The file would have to be re-aligned back to OpenSite for use with Civil File Manager Or re-aligned to OpenRoads depending on the user.
File with only an alignment created in OpenRoads Designer:
OpenBridge OR OpenSite cannot open the file for edit, without 1st running the Civil File Manager.
File with only an alignment created in OpenBridge Modeler:
OpenRoads OR OpenSite cannot open the file for edit, without 1st running the Civil File Manager.
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer, OpenRail Overhead Line Designer , OpenTunnel Designer, OpenBridge Designer, OpenBridge Modeler |
Hola. Completamente de acuerdo con esta solicitud de mejora, el empleo de diferentes esquemas es un obstáculo para el uso compartido de librerías, por ejemplo, entre ORD y ORLD. Para ahorrar trabajo y evitar errores, queremos compartir algunas librerías, pero de momento existen problemas de compatibilidad que nos obliga a mantener (con el trabajo que supone) librerías por separado o tener que degradar los archivos compartidos. Gracias!