In our company we want to start a project.
this project ha been divided to 4 parts and each part is in scope of different companies.
I am not familiar with Global Project.
I have some questions about [COLOR="Red"]Global Project[/COLOR]:
1- To create a Global Project which points should be considered?
2- Should all companies have PDMS with same service pack?
3- I have worked only with non global projects. which difficulties I may encounter in Global Project?
4- we can use non global project and transfer and update proects with file sharing. which system do you suggest for us, global or non global?
5- which network problems is possibly occur in global project system?
6- during updating project in global project is it possible for all companies to continue modeling ?
I would really thank you if answer my questions.
Thanks
[QUOTE=rabizadeh;34296]In our company we want to start a project.
this project ha been divided to 4 parts and each part is in scope of different companies.
I am not familiar with Global Project.
I have some questions about [COLOR="Red"]Global Project[/COLOR]:
1- To create a Global Project which points should be considered?
2- Should all companies have PDMS with same service pack?
3- I have worked only with non global projects. which difficulties I may encounter in Global Project?
4- we can use non global project and transfer and update proects with file sharing. which system do you suggest for us, global or non global?
5- which network problems is possibly occur in global project system?
6- during updating project in global project is it possible for all companies to continue modeling ?
I would really thank you if answer my questions.
Thanks
Welcome to Global....
Your project environment can be as simple or complicated as you choose to make it. I'll try to answer some of your questions, and give you some advice...
1. In my opinion, the most important issue you will have (based on your description) is connectivity between locations (IT line of sight). You mention that scope is between different companies. I am assuming that these companies likely don't share the same network infrastructure which will limit your global setup options. Depending on the Scale of the project, you'll either have to work with IT to setup some hosting DMZ environment for all companies (very costly, but effective), or you'll have to use Offline Locations (meaning you'll increase your admin load by FTP'ing or moving data between companies in another manner). Your frequency of update between locations will help determine your options.
2. I would not mix versions, nor would I mix fixes... If you are running PDMS 11.6.SP4.x, then I would ensure all other companies are running the same. This is especially true with GLOBAL. Many fixes have been put in place to accommodate bugs for Global (which is much better these days). Also, PDMS 12x requires a databases upgrade, so you definitely can't mix it with any prior versions.
3. Many difficulties... depending on communication reliability, user practices, etc... The Global Daemon is definitely more robust than it used to be, and has better error checking and recovery built into it than before. Still, most issues stem from Communications dropping in the middle of an update, Daemons not communicating, etc... Also, Firewalls can stop you short from running Global. Global passes Commands across port 135 (for online location configurations), and then uses a dynamic port range (RPC) defined by your IT guys. These ports have to be opened, which will lead to many IT Security conversations and headaches in compromising. Also, use of Extract Databases will drive your setup. If a Parent Extract sits at on location (HUB), and the Child DB wants to do some work, then Communications across Global will have to occur to reserve "buckets" of database references numbers for the Child to continue working. This issue has been known to hang some projects. There are many debates on here as to extracts and their use... Unless you are a HIGHLY skilled PDMS Administrator who understands ADMIN, GLOBAL, and Databases connectivity, I would avoid extracts. With all of the above said, GLOBAL is still far better than FTP'ing information back and forth. It will considerably decrease your workload.
4. See above comments... It really depends on update frequency, size of project, and communications between companies. I've done both. I prefer Global.
5. Covered above... Also consider licensing, who will be the HUB, and who will be satellites.
6. Yes, modeling can continue. If Global attempts to update when someone is still working it can defer the transaction until later (no writers to the database).
One more thing.... FTP means that you will be copying whole databases. Global only copies changes. It is much more efficient. Think about going to your printer and copying a Reference manual... would you copy the entire manual or only the couple of pages you needed to read.
