Mike,
If you were to design a new architect for PDMS to enable work-share around the globe, how would you/*** go about doing it?
How about if the client request pipes to be modeled in city H, but pipe supports to be modeled in city B? This might not be the best work-breakdown, but it was constrained by economics/schedule etc. What kind of check/balance should be built within the "extract" db?
I assume you are familiar with PDMS extracts - it enables user A in city H to work on the pipe and as well as user B in City B to work on the pipe support (on same pipe) via extract and with a claim/flush process. However due to the communication limitations(firewall etc), packet maybe lost during the trip and thus locks up the pipe so no one can work on it.
Mike,
If you were to design a new architect for PDMS to enable work-share around the globe, how would you/*** go about doing it?
How about if the client request pipes to be modeled in city H, but pipe supports to be modeled in city B? This might not be the best work-breakdown, but it was constrained by economics/schedule etc. What kind of check/balance should be built within the "extract" db?
I assume you are familiar with PDMS extracts - it enables user A in city H to work on the pipe and as well as user B in City B to work on the pipe support (on same pipe) via extract and with a claim/flush process. However due to the communication limitations(firewall etc), packet maybe lost during the trip and thus locks up the pipe so no one can work on it.
