1. Creating: TBPM project file is created using an active dialog among project management team members, including L2 managers. First step is to create the Work Breakdown Structure using various sources. Next step is to assign duration and resources including availability and cost. For the TBPM project, an average SWF cost per job category prescribed in the RUNII Upgrade project file is assigned. Actual SWFs for individuals are not tracked currently. This may change later, as the project becomes more stable. All tasks are scheduled using "As Soon As possible" constraint types as default. Following task type assignment convention is used:
   • Reviews: Fixed duration with 1 day as default
   • Tasks other than reviews or summary tasks: Fixed work
   • Tasks involving PO/Procard: Material with fixed unit whenever applicable
2. Tracking: Initial project file is refined and updated until it is baselined (as MSP baseline file) after approval by the project manager. Subsequent baselines are taken as determined by the project manager. After first baseline, status updates are made by the L2 managers on previously agreed upon dates. It is suggested that the L2 managers should update the status update spreadsheet on the project web using red color and e-mail the file to the project assistant. Project assistant is always available for consultation and assistance for status updates. Initially, status updates will occur frequently. Please note any new PO/Procard initiated should be noted on the status update reports.
3. Change control: Once the project file is baselined, any major changes to the scope, schedule and cost should be brought to the attention of the project manager as soon as possible, so that these changes can be authorized properly.

Project Managers: Steve Wolbers (CD)/Bob Webber (AD)

Project Assistant: Bakul Banerjee