I'll be following the Microsoft OneDrive conversation closely as it may yield some potential answers, but I wanted to ask a parallel question here without muddying the waters there.
DOTs will typically provide localization via custom workspaces with cells, levels, linetypes, etc., and those resources will typically be placed on the C. I'm based in Atlanta and have (thus far) set up GDOT and NCDOT to coexist (largely harmoniously) on my machine. But we do share work frequently across offices, states, etc., and I'm wondering if anyone's had experience with successfully locating DOT workspaces in a shared environment (read cloud here rather than a local network). The explicit advantage would be the maintenance of a single instance per jurisdiction (keeping current and complete one workspace for Georgia, one for Florida, etc.) and the explicit disadvantage being that the instructions for localization (if these first two are any indication of the norm) are plainly intended to be entirely contained within and exercised from a local drive.
The thought of having to instantiate a new workspace (and its attendant linkages to GEOPAK or InRoads or whatever until we're all sufficiently open-roaded to smile and sing together) each time I add a state (actually, this I don't mind so much, but the thought of everyone - and inevitably some for whom it'll be uphill and intimidating - having to do it every time) isn't particularly comforting, and that process is just particular enough not to be well served by global/remote IT support.
So, now that we've rambled a bit: can custom workspaces be resourced from non-local drives (step 1) and can multiple custom workspaces be organized on a non-local drive such that I could potentially pull up a Texas or Wyoming or Iowa DOT launch and be ready to go from the drop?
My guess is that there's an actual technical barrier to doing so, but my hope is that it's virtually impossible (and thus, by definition, possible if only remotely so) and that someone might have made a bit of progress in this direction already. We can't be the only ones for whom this would offer a huge benefit.
Thanks in advance, and happy Wednesday.
Michael Schultz
Kennesaw, Georgia
Michael,
I'll second Kevin's recommendation for ProjectWise's Managed Workspaces. We've been using them for about 8 years now. They provide the ability to centralize the workspace for multiple users/offices. If there's a downside, it would be that many of these workspaces and custom apps. were not created with PW in mind. This can mean some trial and error when it comes to workspace set up. There are also separate levels of workspaces so if you want to have a base set of standards that will never change, but give people the ability to add on/override/update standards, you can. I've noticed some DOT's are starting to host projects on their own ProjectWise servers giving them control over the workspace.
Tom F