Ok, I'll do my best to answer some of these...
We use Projectwise with both AutoCad and microstation. We support (at least) two geographical locations, 1 in Florida with (approx. 200 users of PW) and 1 in North Carolina (also with about 200 users). In addition we have numerous contract companies located all over the US that do design work for us and have access to come into ProjectWise to retrieve the necessary files.
How safe is it?
As safe as you make it! Utilize groups and permissions to control what can and cannot be seen. Also make good use of the work flows to control file permissions as well. Example: When our engineering dept. is working on a design and the drawings have not been issued yet, field people cannot see that these drawings even exist. Once they have been completed (and issued) the files are moved to a construction state (in the workflow) and are read-only to everyone (and visible now to the field techs). We use these same methods to prevent our contract companies from seeing each others work as well.
How long does it take to open a drawing? Upload download times?
This is dependent on where your servers are located. We have servers in both Fl. and NC. due to the speed issues.
Is there a way to lock drawings?
Yes, when a file is checked out it is locked down. This does not prevent others from copying it outside of the system but would prevent them from putting it back with the same name. The XM version of PW has the ability to allow multiple users to work on a single drawing at the same time, but in our environment (where the right hand may not communicate with the left hand) we have this feature turned off and considered dangerous
Can you open multiple drawings?
. Yes, no problems, same as with Acad. To open multiple files in Microstation requires a bit more manipulating.
How well does it work with 2000 LT? Windows 2000?
We use it with AutoCad 2000i and some of the features do not work with Autodesk products. When using Microstation xrefs, indexing, etc.... works as described. Things that we know don't/didn't work well was xrefs (unless they are in the same vault (folder)) with relative path set.
Parent/child relationships did not work well in previous versions of PW, although they (Bentley) says this is working correctly for acad files. Batch processing of any kind (from acad) must be done outside of the PW system, we use standard network drives for this and export the files out of PW.
System requirements?
Don't know about this because Bentley (working with our IT dept) set up the servers, etc...
What are some issues people are encountering?
People issues for the most part.
Like any Document Management System or any database, the information in the system is only as good as what has been entered. (IE. search capabilities). We have very stringent processes to control how the information is entered and maintained. Moving the files through the workflow and documenting the files is part of the work package. The project is not complete until the paperwork is done. Because it is easy to see who last touched the files this is not too bad to maintain. People ARE held accountable for their work.
I read someplace there are some problems with using custom menus or workspaces... is this true?
With AutoCad, yes. With Microstation, No.
How does it behave differently than what we are originally used to? For example to save, or to load xrefs…
There is a bit of difference here but you can get around it with good planning. The reason is files sit on the PW server. When you check out a file, a copy of the file is moved to a working directory. This maybe on a network drive or a local drive. Each time/day you open a file, this working directory changes (usually something like DMS0162). Different versions of files causes even more sub-directory breakdowns. So in the acad world you have to account for these changing paths to xrefs, images, etc...
What are we going to have to learn (or my case teach) so that everybody is efficient?
Like any other software package, there is much you will never utilize. Figure out what your work processes (work flow) and setup your system to support it. Use a grace period while folks are learning. Teach only what is necessary to support your processes.
Demand/Ingrain 100% compliance! Have management support for this.... or shut off their permissions until they comply.
Is there a cost to access it?
Yes, per PW client license.
Other things to mention; Have a standard on loading documents and also one on usage. These may not be the same people doing these tasks. We use clerical help for loading of files and they too must maintain accuracy.
Do not leave files checked out for extended time frames. If a computer crashes, the files are checked out to that specific computer and require an Administrator to free them. Do not allow users to work outside the system, unless absolutely necessary! Why circumvent such a costly system? Besides, then you get into multiples of the same file and which one is the current one?
I hope this helps...
Good luck!
