OpenRoads itl - Delta File Transfer

Good day

When multiple users work on a OpenRoads Designer / OpenRail project users need access to the same template file .itl

The first user that access PW will be checking out the itl file and will be the only user that will be able to make changes to the file. If the user forget to check the file back in the teams in other offices is basically stuck. This cause allot of frustration among users.

Question:

Would it be possible for multiple users to check out the same file and when they check the file back into PW only transfer the deltas back into PW?

This will mean the file on PW is the master document.

What formula/variable is used by PW to distinguish between what is a delta in a document?

Also submitted this question in the ProjectWise Content Management Forum.

Parents
  • Johannes,

    Unfortunately, this is a fifteen year old problem.  I have asked Bentley multiple times about this issue, as have others.  Never really getting an answer.  I even brought up this issue at the last Bentley Learn conferences and person I asked didn't seem to understand the problem.  Why do you need multiple people sharing an itl file?  Very disappointing to see how out of touch some of the Bentley folks are with real work being done on projects.  Over the years , I have worked on projects with 10-20 users trying to share a single itl file.  Basically your options are to have multiple itl files or share the one , taking turns updating it.  Having multiple itl files can work well if your project is broken into areas or zones for design.  i.e., an interchange can have a individual ramp or mainline itl , which a user can open when working on that area.  I have also setup itl's for each individual user on a project.  This can even be loaded using a variable.  This option usually takes a little more effort to manage the files (templates) though.

    I can't wait until they just put the standard templates in an dgnlib and allow new templates libraries to be stored in the dgn the corridor is housed in.

  • Hi Zane,

    Agree, current workflows don't seem to cater for large projects and collaborated working. I think something that needs to be included as an evolution of the Inroads Template Editor to OpenRoads Designer.

    Essentially a method of having an ITL consist of Template "nodes" that can be locked out when being edited, but keeps the ITL itself available for editing. When saved the "nodes" are made available to other users - essentially like a PW Delta transfer. We have live referencing of design elements, so why not templates. Its "just" an XML file so surely achievable?

    Regards,

    Mark


    OpenRoads Designer 2022 R3 (10.12)  |  Microstation 2023.1  |  ProjectWise CE 3.4

  • What about splitting the itl file into a folder structure. The template libraries read all the templates in the folder and make allow the software to read all the files in the folder. Almost like the dgnlib files. This way user can create new files or edit a individual template while team members are busy. This way you can copy a file to another project template folder.

    Senior Highway Design

    ZUTARI SOUTH AFRICA & AURECON

  • Yep, and that would work perfectly with current PW integration and managed workspaces too

    I'd add that to the Ideas section (if anyone reads it that is)...

    Regards,

    Mark


    OpenRoads Designer 2022 R3 (10.12)  |  Microstation 2023.1  |  ProjectWise CE 3.4

  • Yes also not sure what will happen but at least we can try. Will support your enhancement.

    Senior Highway Design

    ZUTARI SOUTH AFRICA & AURECON

Reply Children
No Data