<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Wake Up To Continuous Compliance for Breakfast with CA</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2006/07/19/wake-up-to-continuous-compliance-for-breakfast-with-ca/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2006/07/19/wake-up-to-continuous-compliance-for-breakfast-with-ca/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<lastBuildDate>Fri, 03 Feb 2012 10:35:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Thomas Otter</title>
		<link>http://www.redmonk.com/jgovernor/2006/07/19/wake-up-to-continuous-compliance-for-breakfast-with-ca/comment-page-1/#comment-1745</link>
		<dc:creator>Thomas Otter</dc:creator>
		<pubDate>Fri, 21 Jul 2006 17:25:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/wp/?p=665#comment-1745</guid>
		<description>James,
I like the CA story. CA has had a tough time with complicance issues themselves, and have come a long way to fix it. They have the scars, and really understand the value of a compliant intrastructure. This gives them the cred to talk about it. 

 Key though, the compliance architecture is a rock solid transaction platfrom, good old boring ERP!! I explore this a bit in my post this morning, but I think this is a topic we ought to explore further. 

Your compliance architecture paper is prescient, given when you wrote it and it remains the best analyst paper I&#039;ve read on compliance. It is now ready for an update though. The solutions to support continuous compliance have moved on significantly in the last couple of years. The CA pitch is good evidence of this, but you need to check out 

My own view is continous risk management will become much more important than compliance. Understanding, measuring and reacting to risk is where I see the next big play. I dont mean risk in a audit sense, but risk in the sense of a portfolio risk. risk sounds a conservative word, one that inhibits innovation, but I dont believe it is. It allows you to understand better what you are letting yourself and your investors in for. 


</description>
		<content:encoded><![CDATA[<p>James,<br />
I like the CA story. CA has had a tough time with complicance issues themselves, and have come a long way to fix it. They have the scars, and really understand the value of a compliant intrastructure. This gives them the cred to talk about it. </p>
<p> Key though, the compliance architecture is a rock solid transaction platfrom, good old boring ERP!! I explore this a bit in my post this morning, but I think this is a topic we ought to explore further. </p>
<p>Your compliance architecture paper is prescient, given when you wrote it and it remains the best analyst paper I&#8217;ve read on compliance. It is now ready for an update though. The solutions to support continuous compliance have moved on significantly in the last couple of years. The CA pitch is good evidence of this, but you need to check out </p>
<p>My own view is continous risk management will become much more important than compliance. Understanding, measuring and reacting to risk is where I see the next big play. I dont mean risk in a audit sense, but risk in the sense of a portfolio risk. risk sounds a conservative word, one that inhibits innovation, but I dont believe it is. It allows you to understand better what you are letting yourself and your investors in for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Governor</title>
		<link>http://www.redmonk.com/jgovernor/2006/07/19/wake-up-to-continuous-compliance-for-breakfast-with-ca/comment-page-1/#comment-1744</link>
		<dc:creator>James Governor</dc:creator>
		<pubDate>Thu, 20 Jul 2006 22:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/wp/?p=665#comment-1744</guid>
		<description>that is right on the money. if organisations are not automating spreadsheet aggregation. its almost impossible to be compliant with ANYTHING if your approach is management by excel.</description>
		<content:encoded><![CDATA[<p>that is right on the money. if organisations are not automating spreadsheet aggregation. its almost impossible to be compliant with ANYTHING if your approach is management by excel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Ayres</title>
		<link>http://www.redmonk.com/jgovernor/2006/07/19/wake-up-to-continuous-compliance-for-breakfast-with-ca/comment-page-1/#comment-1743</link>
		<dc:creator>Phil Ayres</dc:creator>
		<pubDate>Thu, 20 Jul 2006 06:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/wp/?p=665#comment-1743</guid>
		<description>James,

Great feedback from CA. I&#039;m happy to see that organizations of this stature are starting to understand and promote the importance of internal control improvement.

It seems that I have been involved in this area more than I would like! In this post [ &lt;a href=&quot;http://improving-nao.blogspot.com/2006/07/bpm-modeling-as-easy-as-spreadsheet_12.html&quot; rel=&quot;nofollow&quot;&gt;http://improving-nao.blogspot.com/2006/07/bpm-modeling-as-easy-as-spreadsheet_12.html&lt;/a&gt; ] I introduced a similar CMM model for internal controls that I had tried to promote. It&#039;s a shame I don&#039;t have the clout of CA! 

[... in a previous life I tried to convince finance groups that there was value in automating spreadsheet processes. How? Imagine there is something like the software CMM model for internal controls and processes...]

&lt;a href=&quot;http://photos1.blogger.com/blogger/3211/1309/1600/levels%20of%20efficiency%20for%20controls%20and%20processes.0.png&quot; rel=&quot;nofollow&quot;&gt;http://photos1.blogger.com/blogger/3211/1309/1600/levels%20of%20efficiency%20for%20controls%20and%20processes.0.png&lt;/a&gt;

[...On explaining that every organization starts on the left and the aim is to take the most complex, highest volume or most risky processes up to the right using workflow and integration tools there were nodding heads. But the audience had little time to concentrate on the problem at any level above managing their compliance documents in a repository (the 2nd level). The best they could do was migrate a bunch of spreadsheets that represented the documentation of the whole organization&#039;s SOX internal controls and processes to a document management system with a compliance skin on it...]

Again, great feedback.

Phil
&lt;a href=&quot;http://improving-nao.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt;http://improving-nao.blogspot.com/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>James,</p>
<p>Great feedback from CA. I&#8217;m happy to see that organizations of this stature are starting to understand and promote the importance of internal control improvement.</p>
<p>It seems that I have been involved in this area more than I would like! In this post [ <a href="http://improving-nao.blogspot.com/2006/07/bpm-modeling-as-easy-as-spreadsheet_12.html" rel="nofollow">http://improving-nao.blogspot.com/2006/07/bpm-modeling-as-easy-as-spreadsheet_12.html</a> ] I introduced a similar CMM model for internal controls that I had tried to promote. It&#8217;s a shame I don&#8217;t have the clout of CA! </p>
<p>[... in a previous life I tried to convince finance groups that there was value in automating spreadsheet processes. How? Imagine there is something like the software CMM model for internal controls and processes...]</p>
<p><a href="http://photos1.blogger.com/blogger/3211/1309/1600/levels%20of%20efficiency%20for%20controls%20and%20processes.0.png" rel="nofollow">http://photos1.blogger.com/blogger/3211/1309/1600/levels%20of%20efficiency%20for%20controls%20and%20processes.0.png</a></p>
<p>[...On explaining that every organization starts on the left and the aim is to take the most complex, highest volume or most risky processes up to the right using workflow and integration tools there were nodding heads. But the audience had little time to concentrate on the problem at any level above managing their compliance documents in a repository (the 2nd level). The best they could do was migrate a bunch of spreadsheets that represented the documentation of the whole organization's SOX internal controls and processes to a document management system with a compliance skin on it...]</p>
<p>Again, great feedback.</p>
<p>Phil<br />
<a href="http://improving-nao.blogspot.com/" rel="nofollow">http://improving-nao.blogspot.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

