Best workflow for sharing TIA Portal projects and Global Libraries in a small team

Do you plan to work concurrently on projects? If not, Multiuser Engineering is not required.

I am assuming you have existing projects from the past 10 years (and hopefully before you arrived) archived onto a company server.

If so, continue using that server as your sharing source.  However, never actively open anything from that server (without something like project server - which is easy enough to avoid the added costs ...).  Instead, copy project archives, libraries, and documentation to your local PG/PC.

Create your own revision control methods and never check-in (overwrite existing projects/libraries) without confirming with your peer(s) they do not also have a local copy currently in test (being modified).

With 2 people, that is not awful to manage.

Once all your projects and libraries are upgraded to Portal V21, you can integrate TIA Portal version control using git with your PG/PCs and that same archival/library/documentation server.

Then you can be a bit more loose with change control.  But until then, copy from server to PG/PC, work, coordinate, copy back to server.  Never copy between PG/PCs else the server will get out of sync and bad things can / will (eventually) happen.

I'm sure there are better suggestions out there.

VersionDog is an option if you have the budget and infrastructure to support it.

Tum-tummetje

For the past 10 years, I have been the sole programmer within our organization. Recently, a new colleague has joined the team.

I am looking for advice on the best practices to store projects and Global Libraries centrally. We need a solution where both of us can easily access and work on the data without conflicts.

What is the recommended workflow for a small team? Should we look into TIA Portal Multiuser Engineering / Project Server, or are there other standard methods for managing shared libraries and projects?