No one can deny that delivering a capital project within the approved budget is one of the must objectives if the project could be labelled as a successful project. For the project budget to be attainable, it must be based on the approved project cost estimate which will be prepared and detailed during the design development stages. The cost estimate must be comprehensive and covers all direct and indirect costs, contingencies and financial charges during implementation.
Using Project Management Information Systems (PMIS) like PMWeb helps in transforming the approved cost estimate into a budget in a seamless process. PMWeb allows creating the project cost estimate by using the cost database for all items and labor and non-labor resources. PMWeb also allows creating building assemblies to capture the organization’s lessons learned and knowledge in estimating the project cost.
Nevertheless, what is more important is that PMWeb allows importing the cost estimate from any other cost estimating source using the MS Excel import option. PMWeb allows mapping all the fields for the cost estimate source into PMWeb cost estimate module. Those include in addition to the items, unit price, quantity, project schedule activity ID, cost breakdown structure among others ten additional fields that can be customized to capture more information on the cost estimate.
Similar to all other PMWeb modules, the attachment tab can be used to attach all drawings, specifications, quotes, proposals and other documents that were used in developing the cost estimate. All those documents will be uploaded and stored in PMWeb document management repository to maintain a complete history of all documents used in developing the cost estimate. In addition, the attachment tab can be used to link all PMWeb records that are related to the cost estimate. Those could include for example the risk register, request for information and other queries, meeting minutes and other project communications.
In addition, a workflow will be assigned to the cost estimate module to ensure that it get reviewed and approved by the authorized project team members and other organization members before its status get changed to approved. Only when the cost estimate status is set as “approved”, the cost estimate can be transformed into a project budget.
The project budget will reflect the approved transformed cost estimate where cost items will be summarized by their assigned cost breakdown structure. In addition, PMWeb allows creating the budget spending plan projection for each line item. Further, budget line items could have their cost in different currencies if needed. Similar to other PMWeb records, documents can be attached to the budget and workflow can be assigned to formally review and approve the budget.
It is highly recommended that all changes to the approved budget, as long as the approved cost estimate is still valid, get managed using PMWeb budget requests module. This module allows transferring budget funds from one cost center to another to detail the changes in the allocated cost for each budget line item. Similar to other PMWeb records, documents can be attached to the budget request form and workflow can be assigned to formally review and approve all budget changes. The workflow will incorporate the conditions to ensure that approvals are aligned with the predefined approval authority levels.
Similar to the option of creating the project budget from the approved cost estimate, PMWeb also allows creating budget requests from the cost estimate module. Accordingly, for additional or revised scope of work which might impact the estimated project cost, the cost estimating team will use PMWeb cost estimate module to provide the estimated cost following the same steps used in transforming the cost estimate into the project budget. The created budget requests can be categorized as original budget or budget revisions. This again helps in maintaining track of all budget changes and the basis for estimating the cost of those changes.
The approved budget will provide the two important Earned Value Management (EVM) measures of Budget At Completion (BAC) and Planned Budget Spending Value (PV). The approved budget is also the basis for the calculating the third EVM measure of Earned Value (EV) which will be based on the updated project schedule percent complete multiplied by the Budget At Completion (BAC) value. PMWeb will be used to import the updated schedule for which the EV will be automatically calculated. The Actual Cost (AC) measure will be based on the actual cost reported in each commitment progress invoice or any other miscellaneous invoice captured in PMWeb.
PMWeb forecast module will automatically capture those EVM measures and calculate the EVM performance metrics that include Schedule Variance (SV), Cost Variance (CV), Schedule Performance Index (SPI), Cost Performance Index (CPI), Estimate To Complete (ETC), Estimate At Completion (EAC) and Variance At Completion (VAC).
Although PMWeb allows the authorized users to adjust the Estimate To Complete (ETC) value, nevertheless it is highly recommended not to allow this practice. Instead, the potential changes module can be used to capture the details of all potential changes that could impact the project’s estimated to complete cost. This will help in keeping track of all those potential changes including their details as well as who have submitted, reviewed and approved those potential changes. In addition, it helps keep track of potential change orders that were approved as change orders and for which the project budget needs to be adjusted to reflect those changes.
This alignment between the approved cost estimate, approved project budget, approved budget adjustments, earned budget performance, actual cost incurred and potential changes that could impact the cost to complete will prevent any reporting discrepancies between what was estimated to build and what has actually cost to build. This will ensure that the cost estimating team, the cost management team as well as executive management are communicating the same language.