AnsweredAssumed Answered

Best practice to share information across to local sites?

Question asked by Ian Pillay on Jul 14, 2011
Latest reply on Sep 29, 2011 by Ian Pillay

Like • Show 0 Likes0
Comment • 7

Ok, we have two sites here in sunny Sheffield UK, only 3 miles apart, we would like to share data between sites and keep the integrity that the vault offers. We have a spare double bondd braod band connection which we can use to link the sites.

I was just wondering if anyone has done somethign simliar and if so what did you do, and was there any issues with it.

We have looked at EPDM but the cost is too high to justify the impementation. We only have three users on the other site and they only want to use our standard parts library.

Thoughts please,

Many thanks,

Ian

No one else has this question

Outcomes

7 Replies

Scott McFadden Jul 14, 2011 6:43 AM
Mark Correct
Correct Answer
Hi Ian,
Welcome to the forum.
Well, I am not going to be much help from the hardware technical end of this,
other then to say it can be done. At my old job we had 5 plants accross the region
and they were 5-8 miles away from each other and we were able to see each others
vaults. Checking in and out using PDM workgroup.
Like • Show 0 Likes0
Actions
- Ian Pillay @ Scott McFadden on Jul 14, 2011 7:54 AM
  Mark Correct
  Correct Answer
  Scott,
  
  Thanks for the information, sounds more promissing than I had been told.
  
  Ian
  Like • Show 0 Likes0
  Actions
  - Scott McFadden @ Ian Pillay on Jul 14, 2011 8:26 AM
    Mark Correct
    Correct Answer
    Ian.
    No problem. I just wish I could give you more details.
    I just know they did it and it can be done. Just don't know how
    because I wasn't involved in that area.
    
    Listen, what I can do is if you email me, I still have contacts back there.
    Maybe I can put you in touch with one of the IT guys there and they can tell you
    what equipment they used.
    Like • Show 0 Likes0
    Actions
Jeff Holliday Jul 14, 2011 8:29 AM
Mark Correct
Correct Answer
As you might imagine, distance is not the problem. The problem lies in how the access to the server where the vault is located is managed (I am not the person to ask about that). We have 3 locations in the US that are able to access the vault. Workgroup is not designed to do it gracefully and the file transmission is subject to a lot of slowdown, but it works. Another option may be to use the Vault Viewer application which allows for several concurrent users to view and copy from the vault. They cannot check files in with it. It does give visibility to the contents of the vault. There is a cost to buy and maintain the program (I think in the area of $1800 US to buy and about $1000 for the annual subscription. Vheck with your VAR.
Like • Show 0 Likes0
Actions
Chaofeng LI Jul 14, 2011 9:13 AM
Mark Correct
Correct Answer
Try Dropbox, 2GB free space, just like a extra hard drive.
Like • Show 0 Likes0
Actions
Tom Strohscher Jul 14, 2011 12:02 PM
Mark Correct
Correct Answer
We have one workgroup vault used between 2 sites. It's slower for one site then the other because the server in at 1 of the sites.

The bigger problem is Tool Box and Design Library. Each site has their own and are stored on a server local to the site.

The uses a site 1 map to their server as "S" drive.
The uses a site 2 map to their server as "S" drive.
The folder structure on the servers is the same so references in the SW files don't complain.

We use a software called ViceVersa to keep the toolbox and design library files in sync.

If I had to to it over again I would not use Design Library folders at all for "common", "simple", "reusable" part files. All of these parts should go into the vault as well.

I think I would continue to use toolbox though.
Like • Show 0 Likes0
Actions
Ian Pillay Sep 29, 2011 4:56 AM
Mark Correct
Correct Answer
I just wanted to round this topic off for anyone who has a similar need in the future. We have managed to over come the multisite working issues, by using a deadicated internet connection and a piece of software called Viceversa. We mapped the library file locations on both site and the vault just seemed to work anyway between sites. So far we have been using this system for 4 -5 weeks and all is well. The other site does suffer from slow download and up load time with large files. A typical assembly file for one of our products takes about 6mins to open up from the vault and about 10mins to check back in. However this is reasonable within our normal working practices.

Thanks for all the input and suggestions thay have all been helpful.

All the best,

Ian
Like • Show 0 Likes0
Actions

Best practice to share information across to local sites?

Outcomes

Related Content

Recommended Content