Can you point at two separate itl files at the same time?

I don't understand what the big issue is here that would warrant a change right now. InRoads has been using a single ITL for over a decade and this has never come up anywhere that I've been (and I've been at a lot of places). We don't need to make things more complicated in ORD right now. How about putting the focus on things that don't work or are missing (that we've become accustom to having).

Like Jeff mentioned, the Template Library Organizer provides exactly what's needed. And / or just copying the 'master' ITL to the project folder as a "seed ITL" has become pretty standard. I don't know of anyone who is navigating between multiple ITLs. (But apparently some people are.)

I don't see where accessing or opening multiple ITLs gets you, other than into a more complex environment. I sure don't need or want this and don't know anyone who does, or has asked me about it.

Plus, again, as Jeff said, once a template is used by a corridor it can be edited there.

As long as there's a CAD Manager running things (or someone being attentive to that area), there shouldn't be a problem maintaining an updated 'master seed ITL' that's used to start all new projects.

This IS a big issue for WSDOT.  We are testing with multiple engineers, and finding that with everyone able to open the project itl at the same time, that we are often overwriting and losing other engineer's work.  At the very least, the first person that opens the file should be read-write and other engineers get a read-only warning.  A message that shows who is currently read-write would also be nice.  A service ticket has been filed today.  A worse case scenario is that each engineer would have a private itl and a project itl manager would have to use the Template Organizer to compile a single project itl.  The problem with this is that each engineer would then need to go back and re-path all their corridors to the Project itl...

Hi Keith,

We've had to spend our own time putting together some VBA macro's and Powershell scripts (for ProjectWise) to put together tools to let users know if the Template Library is in use by someone else or free it to be available to other users (in ProjectWise).

This was causing us a lot of problems on large team projects for the exact same reasons you mentioned. Native functionality should be relatively easy for a professional programmer to add in I would have thought...

Hi Keith,

We've had to spend our own time putting together some VBA macro's and Powershell scripts (for ProjectWise) to put together tools to let users know if the Template Library is in use by someone else or free it to be available to other users (in ProjectWise).

This was causing us a lot of problems on large team projects for the exact same reasons you mentioned. Native functionality should be relatively easy for a professional programmer to add in I would have thought...

You should market that tool.

The ITL file is one of the files that doesn't seem to interface well with ProjectWise. From pre-ORD, XIN files were also problematic. It's been a while  since I was fully in production in ProjectWise, but we instituted a check out policy for ITL and XIN files as a standard operating procedure, but never had the resources to implement any automated approach. 

To use a line from one of the TV programs seen in the original Robocop movies, "I'd buy that for a dollar!"

I think Bentley has a few professional programmers?  Maybe this will show up in a quarterly update soon?