Is it possible to link data across different/multiple PWA sites leveraging Master Project with the Subprojects feature?

Question

A couple different questions /similar scenarios
1) Is it possible with Project Server 2010 to have several sites (http://server/pwa1 and
http://server/pwa2 for example) communicate and build a Master Project at a third (or X) site (http://server/pwa3)
2) Is it possible with Project Server 2010 to have several sites (http://server/pwa1 and
http://server/pwa2 for example) communicate and build a Master Project at one of the original sites (http://server/pwa1 (for example))
OR is there a better way to do this/more preferred way to do this. 
We found this (http://social.technet.microsoft.com/Forums/projectserver/en-US/2379c3f2-6c80-46d7-8eac-3bc2ccb2d908/master-projectsubproject-with-sites-in-pwa-2010?forum=projectserver2010general)
but its not what we're looking for
3a) Issue/Example -
We want to set up a site (http://server/pwa100) for just the president of the company - all the schedules of the subsites (/pwa99 + /pwa98) create a feed into an integrated master schedule/master project with subprojects(located
in /pwa100). 
3b-1) We also want to set up sub sites (http://server/pwa99 and
http://server/pwa98) for each division VPs (and specific other people). These two sites would only allow specific user's project files to be viewed by each other...
Can their project files have linkages between the two project sites (/pwa99 and /pwa98)? Meaning if user1 logs in to /pwa99 can he see a project file (given that they have permission) from /pwa98 in the same instance?
3b-2) Can they see the project file in ProjPro and/or PWA ???
3c) is it possible to have:
+ /pwa100 (pres)
++/pwa99 & /pwa98 (two vps)
+++/pwa97 & /pwa96 & /pwa95 & /pwa-etc (minions)
each rolling up to the next level (level 3 rolls up to level 2 which can roll up to level 1)

Answer 1

kbwrecker,
I agree with Dale. Having multiple sites will make this difficult to set up. 
Not knowing how your Custom Groups/Categories have been set up, have you looked into using the "Project Permissions" feature to share projects. These permissions are 'additive' to the category permissions, so you could start out with people looking at the
projects they are authorized to via categories, and then let them share/add people as needed basis. This will also satisfy the requirement of not-loading the projects with resources..
And finally, the department and categories need not align, except that when projects from one dept are shared t another dept resource, the visibility of custom fieds will be affected.
Hope I did not go off on a tangent there :)
Prasanna Adavi,PMP,MCTS,MCITP,MCT TWitter: @prasannaadavi Blog: http://www.prasannaadavi.com
Meant to get back to this earlier - your answer is close (because its what we currently do..sort-of)
From my understanding of this issue the users are separated by department and can only see specific projects; however, when they try to share departments between users (so they can see their projects (dept a sees dept b projects)) this works - but there
is a bigger issue/main issue.  
main issue: when dept B adds a new project dept. A cannot see the new project in dept B.
This can be eliviated by removing the user/s and re-adding them to the permission structure of the deptment but overall doing this several times based on user/s and projects being added it gets to be cumbersome and just plain annoying.
Any help/additional thoughts would be great