cacciatorino
Guest
with a client company, we're exploring the possibility to collaborate more efficiently than the current situation, which is:
i_solidedge <--> step/dwg/excel <--> their_cocreated
we have seen that cocreate in cases such as these previews the use of the multisite license: from what I understood the database (oracle or ms-sql) is replicated both sides and synchronized on-demand or on oral scheduling. We both work each in their own lan so there are no complaints.
all very nice, if not that this multisite license costs several thousand euros and needs one from me and one from my client (clearly it is a case studied for the big "corporation"). Considered the levels of turnover we are talking about, it is not a viable road.
Is there any other way to cooperate? I was thinking, for example, to connect me in the morning via vpn with the pdm client, upload the assembly, and save it to local pkg. at the end of the day I resume the pkg and pour it on my client's server, again via vpn and pdm client.
Is that a feasible thing? What happens for example if I load the assieme father containing subassieme_1 and subassieme_2, and while I work on subasieme_1 from me a colleague works on subassieme_2 at the end of the customer? when I reload the pkg overwrite all the changes he made in the meantime? Consider that the customer does not use pkg but writes data on database oracle, in granular form (a part = a file). We consider that the assieme father can be a line consisting of tens of modules and ( dozens of) thousands of parts.
This is a question for "er_president", I invite him to a wedding! :biggrin:
i_solidedge <--> step/dwg/excel <--> their_cocreated
we have seen that cocreate in cases such as these previews the use of the multisite license: from what I understood the database (oracle or ms-sql) is replicated both sides and synchronized on-demand or on oral scheduling. We both work each in their own lan so there are no complaints.
all very nice, if not that this multisite license costs several thousand euros and needs one from me and one from my client (clearly it is a case studied for the big "corporation"). Considered the levels of turnover we are talking about, it is not a viable road.
Is there any other way to cooperate? I was thinking, for example, to connect me in the morning via vpn with the pdm client, upload the assembly, and save it to local pkg. at the end of the day I resume the pkg and pour it on my client's server, again via vpn and pdm client.
Is that a feasible thing? What happens for example if I load the assieme father containing subassieme_1 and subassieme_2, and while I work on subasieme_1 from me a colleague works on subassieme_2 at the end of the customer? when I reload the pkg overwrite all the changes he made in the meantime? Consider that the customer does not use pkg but writes data on database oracle, in granular form (a part = a file). We consider that the assieme father can be a line consisting of tens of modules and ( dozens of) thousands of parts.
This is a question for "er_president", I invite him to a wedding! :biggrin: