Risk Calculator in Deltek Vision

Another good practice when pursuing Opportunities or executing Projects is to use a Risk Calculator. The components of the Risk Calculator can varies greatly between firms and services, so it to be implemented effectively you’ll need to identify the most common and ideally the biggest risks associated with your clients and services.

In this example you’ll also see two different and more advanced techniques to update user defined fields (UDF’s), the first is a stored procedure workflow which is used calculate the Risk Level and score based on the selections. The second example uses a nightly routine to update fields overnight.

For this risk example we’ll just use some common issues associated with Contracts… which hopefully all your projects have. The first thing to do is to create some user defined fields that are common to the type of contract risks you have. In this case we’ll use some issues with scope, rates, contract type, being a sub, etc. Another risk type can be associated with how much work you’ve done for a client, both in volume and quantity of projects so that’s shown as well

The revenue and project count in this example will be calculated overnight using Sql Server Agent Jobs. These totals could also be done using a sql stored procedure workflow as well, however it’s good to know how to use the agent and it has some advantages and disadvantages. The main disadvantage is that when a new infocenter is created the fields aren’t immediately completed, or completed after a save or other update to fire the workflow. On the advantage side the infocenter isn’t slowed down by extra workflows and you can get some consistency in reporting, since the fields should always be completed/filled in by the nightly routine, so in this example you could always report on active opportunities and see which of those are for established clients and which are for new clients. One the things to consider when choosing a nightly routine vs a workflow is how soon the fields need to be populated, in this example the assumption is the Opportunity is created at an early stage, and the Risk calculator would be updated at a later stage by then the fields would be completed.

When the fields are all completed and saved a stored procedure workflow is called that tallies up these UDF’s (user defined fields) and a risk score is calculated and then classified into a risk calculator.  You can read about using Stored Procedure Workflows here.

Leave a Reply

Your email address will not be published. Required fields are marked *