Chris,
I did a project like that across many countries. In the 1990's and at
least we had a global corporate network to facilitate the transportation
of the MPP files.
To do exactly as you ask, to "push out" individual tasks to distributed
MPP files around the world ... probably being unrealistic. That's not
how Project MPP files work and you probably should adjust your expectations.
The first thing to do is to build some sort of
infrastructure/architecture for the collection of MPP files (where they
are stored, who is responsible for them, etc.). Then it is an issue of
managing the change to the MPP files.
The process would work no different than if you had 36 copies on your
own PC. Just the locations are different. But it gets more comlicated
because for technical and political reasons it's probably not a good
idea to go updating/changing remote MPP files.
Without knowing more about your distributed project and the people
involved ... I would probably think of having a centralised stored of
MPP files (1 to 36 or more) in one location in SharePoint. I would use
ProjectPublisher to "publish" those project plans into SharePoint lists
and use SharePoint as the mechansim to "push" out tasks to the folks
around the world. Synchronisation between the site access to the
SharePoint team site and the centralised MPP file store would be almost
automatic. This approach would eliminate a lot of complexity and is low
cost. It's also "teachable" so that you can easily establish the
project expectatations that people around the world *will* understand it
and use it.
Just my two bits ...
--rms
www.rmschneider.com