grd wrote: ↑Thu May 12, 2022 9:15 am
You are
--completely-- right and I was wrong, I got carried away.
No you're not completely wrong, worst case not completely right...
Zolko wrote: ↑Thu May 12, 2022 8:59 am
grd wrote: ↑Tue May 10, 2022 4:35 pm
Every file inside PLM is of course read only. You can read the contents of that file, but when you want to modify that file ...
how is that supposed to work in real-life : you have a project with 5 engineers, and anyone can decide which part he's gonna modify ? And what if the person forgets to release the rights ? And then goes on vacation for 2 weeks ...
Zolko wrote: ↑Thu May 05, 2022 10:27 am
I have done exactly this for a 5-team project using Siemens NX, because the integrated PDM/PLM (TeamCenter) ....
If you have worked with Teamcenter you should be aware of this work flow. It is exactly the same
Everybody has read-only access by default. writing access to file can only when you request it(check-out a file). After editing the file you can check-in the file what is basically saving it to the server and release it.
By automatically requesting write access you don't need someone who have to do this manually but you can do this automated.
Zolko wrote: ↑Thu May 12, 2022 8:59 am
And what if the person forgets to release the rights ? And then goes on vacation for 2 weeks ...
This goes automatically when saving to the server. And I think that this are task that you should do at least daily and sometimes more often. (If a Team member Don't checking in his files you should kick him ass any way)
Zolko wrote: ↑Thu May 12, 2022 8:59 am
...but can only modify – on the server, in the central repository – those files for which the project manager has given him rights-to.
I don't like the idea that all editing is on the central server. That means if you want to try it out you screwed since ctrl+s is a kind of sickness every engineer need(Specially with SW or Inventor). So if you edit aren't the result you aiming for you have to undo all your work compared to pull the last version on the server!
Zolko wrote: ↑Thu May 12, 2022 8:59 am
If you organise the project such that each sub-system is a sub-assembly
*AND* is in a sub-directory, then you can give write-rights to
*THAT* subdirectory to the corresponding designer. Then, each designer is responsible for a sub-system and has write-access to that sub-system, not the others.
I don't think this is less hassle than than checking in / checking out. This can have other problems On multiple occasions i was working on system level / assembly level stuff while colleagues of mine were busy on part level inside the same directory!