EPM Risks to Issues

[Chris]

Dear All,
We are moving towards deploying EPM but a query I'd welcome any comments on
please.

We currently treat risks as potential issues and issues as current, well
issues! We keep these in the same register and filter according to
proximity, impact etc..

I understand that EPM has 2 different categories (risk and issue) and wonder
whether if a risk is set up but its proximity becomes 'current' it is
automatically moved to the issue category?

What I am concerned about is having to type in all the details (some will
obviously need to be changed such as current mitigation plan) again in the
issue section / category.

Best wishes
Chris

 

[Paul Conroy]

You could create a Sharepoint workflow to populate another list (ie issues
list), alternatively you could create a custom column in the risks lists to
identify risks as being current.

Please do not change any of the default columns in the risk/issues list as
this will break WSS publishing.

 

[Chris]

Hi Paul,

I like that, keeps it all in one location (as currently managed) and allows
filter. Many thanks for that - and very rapid response (didn't even finish
my first cup of tea!).

I would welcome a comment on the original query as to actually what happens
to current risks if possible please.

Best wishes
Chris

 

[Paul Conroy]

Risks always stay as risks, even when they become current. You will need to
change the status manually.

Paul

 

[Chris]

Thanks Paul - and by that do you mean retype all existing details into the
issues area?

Cheers
Chris

 

[Paul Conroy]

Most people keep the information in the risk list and don't bother moving it
to the issues list. as long as you can identify risks as current within the
risk list, this should fulfill your requirement. Given your usage scenario,
I would even consider removing the issues list from the site template.

As both risks and issues are populated within OLAP, you need to be mindful
of how you will report on issues/risks when using the cube.

 

[Marc Soester [MVP]]

Hi Chris,

on that, you do have the abillity to move information from risks into issue
should Risks become issues. This is not an out of the box function, but can
be achieved by custimising your workspace with workflow. We have used the
SharePoint Designer which allows you to create a workflow based on the due
date of a risk.

Lets say the due date of a risk has past, the workflow will then create an
issue and copy risk information into the issues. This is actually not too
complicated if you have a little experience in development or the SharePoint
Designer.
Hope this helps

PS: Cheee Paul you are fast for someone living in New Zealand Greetings
from Australia Marc
Thanks

 

[Chris]

Hi Marc,

That is very useful - thanks. I'm not familiar with the SharePoint
designer, however, one of my project managers always enjoys getting stuck
into one of these things. However, if you can recommend any text that would
be welcomed.

On the question of kiwi and Aussie speed of responses, as a UK Worcester
resident I would say that you both appear to be like lightening - just like
your rugby players - who we have to steal to get our game up to scratch over
here. Rico Gear is very much at home with us now and you can't have him
back! .

Cheers
Chris

 

[Marc Soester [MVP]]

Hi Chris,

check out this link. This will introduce you to the SharePoint Designer
http://office.microsoft.com/en-us/sharepointdesigner/FX100487631033.aspx

PS: Well the poms are not to bad either with rubgy

Take are mate
--
Marc Soester [MVP]
State Manager: EPM
http://marcsoester.blogspot.com