
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>IM and PM, and their integration with Risk</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1788475</link>
<description></description>
<lastBuildDate>Sat, 6 Jun 2026 18:50:43 GMT</lastBuildDate>
<pubDate>Mon, 12 Aug 2024 14:15:38 GMT</pubDate>
<copyright>Copyright &#xA9; 2024 itSMF UK</copyright>
<atom:link href="https://itsmfuk.site-ym.com/forums/topic_rss.asp?id=1788475" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>IM and PM, and their integration with Risk</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1788475</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1788475</guid>
<description><![CDATA[<p>Hi.&nbsp; I'm working with our internal Risk Management team to work out the contact points from Incident and Problem Management, and Risk.&nbsp; The Risk team are setting up a new Integrated Risk Management module in our ITSM tool (ServiceNow) and we're talking about the triggers from one process to another.</p><p>I can see the logic (and also some references in ServiceNow specifically) of how the existence of a Problem could trigger the creation of an issue linked to a risk, and if the Risk is accepted there is another process link to the KEDB.&nbsp; I'm less sure about a connection between IM and Risk.</p><p>If anyone out there has any experience of the same process and tooling work and they could share a few thoughts, I'd really appreciate your perspectives.&nbsp;&nbsp;</p><p>Many thanks</p>]]></description>
<pubDate>Mon, 12 Aug 2024 15:15:38 GMT</pubDate>
</item>
</channel>
</rss>
