Amacom - Modern Project Management (Ocr) - 2001 ! - (By Laxxuss)

Consequently you should enter 1 in the variance

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: is tool is activated by clicking on the Cost Variance Entry/Edit button on the Modern Project Main Menu. The cost line items associated with the three variances you have already entered into the system are shown in Figure 310c. To enter a variance cost line item, you must first enter the Variance Number, the Work Package ID and the Cost Account it is associated with. This tells the cost variance entry and edit tool which variance and which cost accounts within which work package to associate this line item with. Variance 1 has four cost line items associated with it. They are all associated with the Siteprep work package. Each variance cost line item corresponds to a different cost account. The first cost line item for Variance 1 corresponds to the 601 cost account, and the cost is $1,000. Consequently, you should enter "1" in the Variance Number field, "Siteprep" in the Package ID Figure 3-1 1c. Variance Transactions (Costs) Entry/Edit form. Page 97 field, "601" in the Cost Account field, and $1,000.00 in the Cost field. Now enter the rest of the variance cost line items shown in Figure 3 -10c. Other changes associated with these variances also need to be made to the example project database. The first are changes to the schedule dates of the affected tasks. The second are changes to the quantifications of summary level control packages. Often a variance will cause a change to all the schedule dates of tasks associated with the line items of quantity and man-hour variances; a change in the scope, quantity, or productivity rate usually affects how long it will take to complete work on the task. To change these start and end dates, you must enter new dates for the task, using the Task Entry/Edit tool discussed in Chapter 2. However, it is wise not to change the original start and end dates because once they are changed, they are lost. Then you will not be able to see what the original schedule was unless you saved the original reports. A better way is to enter new Client start and Client end dates for tasks with change orders, Control start and Control end dates for tasks with change orders or quantity variances, and Forecast start and Forecast end dates for tasks with any type of variance. These schedule changes can be determined manually or by rerunning the scheduling system. However, trying to determine these new dates with an automated scheduling system is often tricky, as is explained in Chapter 7. First, if additional tasks have been created, these must be entered into the scheduling system. Since you probably will not want to lose your original schedule in the scheduling system, you will probably want to create a new Control Schedule that includes these new tasks caused by the change orders and quantity variances. We defer changing the schedule dates in the example project database until Chapter 7, where we discuss automated scheduling in detail and introduce an automated interface between the Microsoft Project scheduling tool and the Modern Project project management toolset. Page 98 Usually project managers keep a copy of the original schedule for historical purposes but use the sc...
View Full Document

This note was uploaded on 01/11/2011 for the course ACC 9 taught by Professor Yeetan during the Spring '10 term at Sunway University College.

Ask a homework question - tutors are online