This is a multi-part message in MIME format.
--------------000208020009000901070700
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


To:  ALMA Provisional IPT Leaders and Deputy Leaders
From:  AEC
Subject:  Organization of the ALMA IPTs

We, the ALMA Executive Committee (AEC), would like to begin immediately to
organize and utilize the IPT structure for the ALMA construction project.
Clearly, this is a major enterprise that will require all of us to work
closely together.  This memo is one step in that direction.

There are two PDF files attached here.  One is a short description of the
IPT structure as we intend to adopt it for the ALMA Project; the other file
is a table of the major scheduling events (the ALMA "Metaschedule") that we
have been using to guide our planning.  We would appreciate it if you would
review both of these documents so that we can discuss them at the "ALMA IPT
Teleconference" (ne "DH/TL Teleconference") on Monday January 28th.

Once the issues that these discussions engender converge, the "Actions" we
request of you, the IPT Leaders and Deputies, are the following:

1. IPT Leaders and Deputies to discuss how they intend to organize and
coordinate the work of their IPT.  Identify issues facing the IPT; recommend
processes or structural changes to the Project organization that will
facilitate the work of the IPT.

2. Provide the AEC with a complete list of the professionals who are
participating in the IPT.  (We would like to use this information to
generate unified email distribution lists.)

3. Review the "Metaschedule", discuss how to schedule the Work Elements of
the IPT within that schedule.  Identify problems.

4. Provide major milestones for each Work Element that is the responsibility
of your IPT.

5. Provide a textual description for each Work Element; this will be
associated with the Work Element and used for the project "dictionary".
Include in this description what tasks are part of each Work Element, what
tasks are not included (in cases where there could be some ambiguity), and
any relevant information on how the WE interfaces to other work elements or
subsystems.



--------------000208020009000901070700
Content-Type: application/pdf;
 name="ALMA_Metaschedule.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="ALMA_Metaschedule.pdf"