An Automated Framework for the Integration between EVM and Risk Management

Earned Value Management (EVM) and Project Risk Management are normally considered separately in Project Management. Referring PMBoK®, EVM is part of Project Time Management and Project Cost Management knowledge areas, while Project Risk Management is a different knowledge area with no apparent relation with the previous ones, although the fundamentals of EVM are fully influenced by risk management. This paper seeks to clarify the mechanisms of this relation, and in which points they meet or affect each other. The interconnection between the two methods was explored in this study and a framework of integration between them was proposed. The framework was implemented in Excel resulting in a set of tools that can be useful in monitoring and controlling a project.


INTRODUCTION
The use of project management is relatively recent and has been motivated by the need for rapid and effective responses to the changing business environment (Kerzner, 2009). One of the components of project management with the greatest need of development, due to increasing global competition and rapid technological growth, is project monitoring and control. Project monitoring and control allows to verify the state of the project during its execution and thus to conclude on its continuity within the parameters considered adequate. In case the parameters are outside the appropriate range, corrective measures can still be taken, which aim to promote the improvement of the state of the project and finally its conclusion with success, that is, within the objectives.
Another way to promote project success is by risk management, but in this case minimizing the risk of not achieving the project objectives is achieved by creating early responses to the risks that may arise.
One of the methods used to monitor and control project status is EVM (Earned Value Management) (Fleming and Koppelman, 2002). In this method, the values estimated in the planning phase are compared with the project execution values, to determine project's state, and in this way create any adjustments that lead to project success. Given the increasing need for project monitoring and control techniques, one of the issues to be addressed is the possibility of using these two methodologies together to obtain additional monitoring and control information. This brings the need to investigate in detail possible connections between these two methodologies.
The two methodologies, having very different approaches, lead to the construction of a framework to summarize the links between EVM and Risk Management. After the link between the two methodologies is clarified, the idea of the possibility of transforming this information into something with practical utility in the monitoring and control of projects arises immediately. Based on the above, the goals of this research were: • Investigate the linkage between EVM and Risk Management; • Build a framework for integrating the two methodologies; • Use the framework to create project monitoring and control tools. The integration between EVM and Risk Management is an area with several lines of research, mainly in the area of the introduction of uncertainty in EVM (Acebes et al., 2014;Pajares and Paredes, 2011).
The approach taken in this paper is similar to that proposed by the Association for Project Management (APM) (APM, 2008), but based on the Project Management Body of Knowledge (PMBoK®) from Project Management Institute (PMI) (PMI, 2013). This type of approach is based on risk stratification, the different responses to each form of risk, and the introduction of the various risk components into the EVM methodology. This approach aims to include all forms of risk and risk responses and not just uncertainty (Tereso et al., 2017).

LITERATURE REVIEW
Due to the increase in global competition and rapid technological development, many companies have begun to pay more attention to improving project control (Kivila et al., 2017). This change took place both at the level of internal and external projects, which generated a growing interest in project monitoring and control techniques (Kim et al., 2003).
The unique nature of the projects creates uncertainty (Vaagen et al., 2017). This uncertainty generates several scenarios in which one or more project objectives may be affected by uncertain events or conditions, leading to the need to make risk assessment during planning. In PMBoK® this area of expertise is called project risk management (PMI, 2013).
On the other hand, when the project is already in execution, in the monitoring and control phase, it is necessary to have tools that allow the evaluation of the state of the project so that, in case of cost or time slippage, one can act and thus avoid or limit the problem (Hazır, 2015). One of the methods recommended in PMBoK® is known as Earned Value Management (EVM) (PMI, 2013).
Traditional project cost management is done by simply analyzing costs over the project time, without an accurate measurement of the work that has actually been performed. We may be within budgeted cost but not have the expected work done. In the EVM methodology, the project performance is measured at each moment in relation to a cost baseline, which is constructed based on the costs of each task. As these are implemented, we have metrics that indicate whether the project is ahead or behind schedule, whether it is spending more or less than planned, and we have the possibility to predict the total final cost of the project (Fleming and Koppelman, 2010).
The method is based on three values that allow obtaining control indices of the project and predictions of costs and deadlines at the end of the project, namely the Planned Value (PV), Actual Cost (AC) and Earned Value (EV). PV is the authorized budget assigned to scheduled work. AC is the realized cost incurred for the work performed on an activity during a specific time period. EV is the measure of work performed expressed in terms of the budget authorized for that work (PMI, 2013).
With these values we can evaluate Cost Variance (CV = EV -AC), and Schedule Variance (SV = EV -PV) or Cost Performance Index (CPI = EV/AC) and Schedule Performance Index (SPI = EV/PV). If CV=0 and CPI =1, cost is as planned. If CV>0 and CPI>1, cost is under planned value. If CV<0 and CPI<1, cost is over planned value. The same reasoning can be done with the schedule, which may be ahead of schedule (SV>0 and SPI>1), on schedule (SV=0 and SPI=1) or behind schedule (SV<0 and SPI<1) (PMI, 2013).
Both PV and EV are based on the Performance Measurement Baseline (PMB), which is built from the Work Breakdown Structure (WBS) and its schedule in the planning phase (Robinson, 1997;Sequeira and Lopes, 2015). Therefore, in order for the EVM to be used as a realistic monitoring and control technique for project execution, the first step will be to understand and organize the project work during the planning phase.
At this planning stage it is necessary to detail the scope of the project using the WBS. Through the WBS the work can be organized into more manageable and executable elements, called work packages (or another element of the division of work considered appropriate for the project in consideration). Then the work has to be scheduled logically until all project work is included. Once the work is scheduled and the resources allocated, the scope, schedule and costs have to be integrated and recorded in a cost table, depending on the time/division of the work that is called PMB, like the one created during this research project (see Figure 1), adapted from PMI (2005).
This plan, with the budget based on the work package per month, can be used to measure project performance. It is also necessary to have a technique that matches the physical progress of the work, in order to calculate the earned value of each work package, like the one created during this research project (see Figure 2), adapted from Anbari (2003).

EVM AND RISK MANAGEMENT INTEGRATION MODEL DEVELOPED
One of the objectives of this work was the creation of a model that seeks to integrate EVM with risk management, which will be presented in this section. In the first part the risk is stratified in order to create different responses to each type of risk and then is shown how each response can influence the EVM or how the EVM can be used in conjunction with the results of risk management. Practical methods for estimating management and contingency reserves are also described. A second part presents a proposal for a high-level framework, which is not intended to be exhaustive, but rather an example that can be further explored. As risk responses influence the different phases of the EVM methodology, the framework will also be a sequence that will allow each operation to be placed in its temporal position.

Include Exposure to Risk in the EVM Methodology
Based on the approach of EVM to Risk management presented in PMBoK® (PMI, 2013), Practice Standard for Earned Value Management (PMI, 2011) and Practice Standard for Project Risk Management (PMI, 2009), the different types of risks were summarized in Figure 3.
The steps to deal with the known and proactively manageable risks are: • Risks identification, characterization and documentation.
• Qualitative analysis including the determination of probabilities and their impact on project objectives, leading to prioritization of risks.
• Depending on the results of the impact on the project objectives, responses will be developed that include avoiding, transferring, mitigating and accepting the risk. Avoid, transfer, and mitigate causes changes in cost and time planning.
Project changes brought about by the qualitative analysis translate into a more realistic Cost Baseline and therefore better EVM indices.
As for the known and proactively unmanageable risks, there is no way to treat them, either because it is impossible to eliminate the risk or because the risk has been accepted. This type of risk is guaranteed by a   contingency reserve. Since this reserve will only be used in case the risk actually occurs, the EVM indexes are corrected whenever the risk occurs. This is because the contingency value is only considered in the Performance Measurement Baseline (PMB) if the risk materializes.
Unknown risks correspond to a part of the overall project risks and represent unspecified project uncertainty. These risks exist in all projects and since no measure can be taken, a management reserve is usually allocated to address this uncertainty.

EVM and Risk Management Integration Framework
In this section we propose a high level framework where risk management is integrated into the development of EVM (Figure 4). During the planning phase, the steps proposed are: develop the PMB based on the WBS and the schedule; analyze known risks; make the necessary modifications to the project; update PMB due to project modifications; with the global uncertainty, estimate the management reserve; include risk components that are known and proactively unmanageable; create in the control accounts the contingency reserves; approve the cost baseline; and obtain an estimate for the project budget where the risk is explicit and documented. Then, during control and monitoring phase, the steps proposed are: control management reserve through EVM; and control and check EVM indexes.

PROTOTYPE FOR PROJECT MONITORING AND CONTROL SUPPORT
A prototype was created in Excel to demonstrate the application of the integration between EVM and risk management proposed. For the construction of these spreadsheets, MS Excel version 2013 was used with some subroutines written in Visual Basic for Applications.
As PMB is the basis of EVM, it will be the mechanism used to summarize the cost and time of the project. To create a PMB one needs to organize the work, schedule the work and establish the budget.
The PMB is a time-phased cost table based on the Work Breakdown Structure (WBS) and on the project schedule. See in Figure 5 an example of a PMB with the cumulative graph of planned costs or cumulative Planned Value (PV).

Figure 4. EVM and risk management integration framework proposal
In the figure, PV 0 would be an initial version before the risk analysis in which the values were memorized for comparison with future versions. Approved changes to the project would result in PV 1. That is, after the risk analysis, responding to identifiable and treatable risks could result in a change to the PMB similar to the example shown.
To estimate the final value of the project taking into account the uncertainty we can construct a table in which the cost values of the various work elements are not fixed, but rather, a probabilistic distributions. Although the uncertainty is present, both in cost and time, in this model we only considered the cost uncertainty.
Using Monte Carlo simulation (Mooney, 1997) with the cost model, we can obtain a probabilistic distribution of the possible cost results for the project. For this purpose we used @Risk, an add-in for Microsoft Excel from Palisade Corporation (Palisade, 2017).
The three point estimation technique of PERT (Program Evaluation and Review Technique) was also used to improve the accuracy of the estimates for the costs of the activities (Moder & Phillips, 1964).
The management reserve is the amount added to the total project budget to respond to the overall project risk and therefore should be dependent on uncertainty.
The following is a practical example (Figure 6) where the management reserve is estimated from the 3 point technique in conjunction with the Monte Carlo simulation.
In this example the columns (Min), (Budget), and (Max) represent the pessimistic, most likely, and optimistic budget values respectively. The (Result) column represents the budget evaluated by Monte Carlo simulation for the work package. The distribution obtained using Monte Carlo simulation is shown in Figure 7. The risks identified and not treated proactively are guaranteed by a contingency reserve. In the example presented, the table shown on Figure 8 serves to relate each element of the work to all risks identified and not treated proactively. Adding the exposure value to each risk gives the value of the total risk exposure for the work package. The total column shows the value of the contingency reserve for each work package. In Figure 9, the contingency value appears as a total added to the PMB. This figure shows the total value of the contingency reserve for the project, taking into account the risks registered. As the contingency reserve is only allocated in case the risk materializes, the amounts are only added to the PMB during the execution of the project. In practice, the Figure  9 allows controlling the total value of the reserve for the identified risks.
The sum of the total value of the PMB with the total contingencies and with the management reserve results in a total for the project with the risks included.

PROTOTYPE STEPS IMPLEMENTATION
In the previous chapters we described the possibilities of using PMB, uncertainty together with PMB and risk with PMB. At this point we will present details of the implementation of the prototype to support the integration framework between EVM and risk management.
For this purpose, a sequence of pages were created in excel that record some of the steps of the framework and present the results in graphic format. These pages will be explained in the following sections.

PMB Creation Page
The values of the cost estimates for each work item and per time period are entered in this page (see Figure  10). At this stage of planning, the schedule, the WBS, and the allocation of resources should already be defined.
Regarding the page, it is necessary to insert the schedule and the costs: 1. Fill in the beginning and the duration for each work item (in this version it is only possible to use 100 time periods). 2. Complete the blue cells scheduled with the respective costs. PV records the cumulative values of planned costs to be used in the remaining phases of the project. Before the modifications generated by the analysis of known risks, store the values in PV -1. In this way we have the possibility of graphically monitoring the evolution of PMB. This function is obtained by pressing the insert button (Figure 10).

Management Margin Calculation Page
This page has the objective of obtaining several estimates for the management margin, depending on the degree of guarantee required for the project and the most optimistic and pessimistic values for the cost of the work elements.
The first step will be to fill in the most optimistic and pessimistic values, besides the standard deviation (σ) to be considered in the analysis (Figure 11).

Figure 10. PMB creation page
For a 97.72% probability that the total cost is less than a given value, we need 2σ. In this example, MR = 4.87 (Figure 7). The value of the last simulation will be used to calculate the total project budget.

Risk Introduction Page
All known risks are recorded in this page (Figure 12). For each risk it is necessary to indicate the cost value, in case the risk materializes, and its probability of occurrence.

Page of Calculation of Contingency Reserves
A summary page is created (Figure 13) with the total costs, including the reserves obtained from previous pages.
Project Budget = MR + CR + Total WBS

EVM Calculation Page
The previous pages are used to enter the data that is part of the planning phase. In this page, this data is used for comparison with the actual data according to the EVM methodology. This will be the main page during project monitoring and control. Whenever an EVM time frame is completed, the project manager must update the respective AC and EV values. The "Enter" key calculates the indexes for the indicated period (Figure 14).
The values obtained are used to create the variance, performance, EAC and VAC graphs.

Activating Contingencies
If a risk materializes, it is necessary to activate the respective contingency, which changes the PV and EV (Figure 15).
To exemplify, assume that risk 1 is materialized by causing an increase of one unit in work package 1. In this case the AC becomes AC = 20. If there were no contingency for this work package, the values of the indexes would be affected, meaning an inferior performance. Since the contingency has exactly the value = 1, the performance indexes remain (Figure 15 and Figure 16 -blue square).
As the contingencies are reserves organized by work element (in this case work package) and because each work element normally occupies several time periods, in this implementation we have chosen to distribute the total value of the reserve for this work element in proportion to the cost of each time period. This option of distributing the reserve throughout the work item is due to the need to maintain the consistency of the EVM, since making resources available before the date planed changes the EVM indexes. For example, if a risk occurs at the beginning of the work package, activating the total reserve immediately (in case resources are only needed over time) distorts the indexes straightway. On the other hand there are risks where the need for resources may not be distributed and in this case the whole value should be made available at the time of the risk event.

Graphics Pages
In order to monitor performance, the following graphics pages were created: Variances, Index, EAC and VAC. All graphs were created with the intention of measuring the performance in relation to time, since the trend type presentation, besides being the simplest to understand by users, is also a valuable indicator to evaluate the evolution of the indices and act accordingly (Tereso, 2002). The graphs shown are relative to Figure 14 and 15. Figure 16 shows the graph of the variances for the four last periods. In period four as the EV and AC are equal to 23, the variation is zero, i.e., the project is neither late nor ahead of schedule and costs are as planned.
The graph of Figure 17 shows the CPI and SPI for the periods referred in Figure 16. A unit line was added to create a simple reference value. It is very easy to follow the evolution of the graph because the lines that join the points create the idea of how the project will evolve. In this case, the values below the unit represent, for the CPI a cost overrun and for the SPI a delay.
The graph in Figure 18 compares the planned project budget (BAC) value, the baseline, with the EVM estimate for the project conclusion (the EAC). The highest value for the estimate as expected corresponds to the lower CPI period. Using the management margin as reference (the value obtained in the risk analysis) we can verify if the margin is enough to guarantee the variation of the estimated final cost of the project in the EVM (Figure 19).

CONCLUSIONS AND FUTURE RESEARCH
The objective of this work was the proposal of a framework to support the monitoring and control of projects, based on the integration of EVM with risk management.
Risk management and EVM share the same role in project management; promote project success. However, each uses different means to achieve this result. Risk management seeks to anticipate possible responses to noncompliance with the objectives and EVM is intended to monitor the status of these objectives.
At first glance there seems to be no further connection between the two methodologies, but the fundamentals of EVM are fully influenced by both risk management and risk analysis. In PMBoK®, integration is implicit and is not even referred to as "Integration between EVM and risk management", which makes necessary to clarify each risk component within the EVM methodology (PMI, 2013).
The framework presented in this paper integrates EVM and risk management. It was inspired on PMBoK® with influences of APM (2008) and the integration proposed by Hillson (2004).
The proposed integration is based on the EVM methodology, risk stratification and risk management methodology. Because EVM is based on the comparison of project execution values with planned values, introducing the components of risk or changes in planning produced by risk management, we get an EVM with more monitoring and control capabilities. On the other hand, risk is now recorded as one of the variables on which EVM depends. Finally, we state that the main characteristic of this model is the correction of the EVM performance indexes introduced by the risk management, and therefore the better quality on the information they provide.
Because EVM is dependent on other components of project management, such as WBS, timeline, cost accounting methods, a more advanced framework would need to include these components, making the process . VAC and MR more complete. The same can be said of risk management, where for example the analysis of known risks requires a well-developed qualitative treatment.
In the prototype presented, the costs and schedule are manually placed on the PMB page. One possibility of extension would be the interconnection of the page with commercial software, such as MS Project.
Finally, in the current model, only the influences of the risk in cost were considered, but the time or schedule is also influenced. A natural extension would be the inclusion of time in the framework.