<?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: Tuesday and Wednesday at Collaborate&#8217;06</title>
	<atom:link href="http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/</link>
	<description>Delivered Intelligence</description>
	<lastBuildDate>Wed, 10 Mar 2010 13:01:07 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Rittman</title>
		<link>http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/comment-page-1/#comment-901</link>
		<dc:creator>Mark Rittman</dc:creator>
		<pubDate>Wed, 03 May 2006 06:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rittmanmead.com/wp2/2006/04/27/tuesday-and-wednesday-at-collaborate06/#comment-901</guid>
		<description>Hi Brian
Where I was coming from, was that I was trying to think up ways to justify the BI EE Suite pricetag, i.e. what existing parts of the architecture can it replace. My thinking was that, in a traditional BI / reporting project, one of the first things you think you need is a database, into which you&#8217;ll copy all the data you wish to report on. Now, the Siebel Analytic Server does away for the need for this integration layer, you can point it direct to your data sources, and it gives you an OLAP-style analysis capability, hence conceivably you could do away with the DB+OLAP Option.
In reality though, you&#8217;re right, you&#8217;re still going to want an Oracle database - either again, to do some integration and data cleansing (the latter being the key part), and to just provide your data. Also, given my talks with the SA people last week, realistically you&#8217;re still going to want access to an OLAP server (Oracle OLAP, MS AS) as the SA analytic engine isn&#8217;t a MOLAP server as we know it, it&#8217;s more akin to a ROLAP engine, so for your true high-end forecasting, OLAP calculations, even access to pre-aggregated data, you&#8217;ll still want the OLAP Option.
I&#8217;m working through a presentation and paper on this very subject actually, once I&#8217;ve done it, i&#8217;ll post it to the blog and get some feedback. It&#8217;ll be along the lines of &#8220;How the Oracle BI Analytic Engine fits into a traditional Oracle DW architecture&#8221;.</description>
		<content:encoded><![CDATA[<p>Hi Brian<br />
Where I was coming from, was that I was trying to think up ways to justify the BI EE Suite pricetag, i.e. what existing parts of the architecture can it replace. My thinking was that, in a traditional BI / reporting project, one of the first things you think you need is a database, into which you&#38;#8217;ll copy all the data you wish to report on. Now, the Siebel Analytic Server does away for the need for this integration layer, you can point it direct to your data sources, and it gives you an OLAP-style analysis capability, hence conceivably you could do away with the DB+OLAP Option.<br />
In reality though, you&#38;#8217;re right, you&#38;#8217;re still going to want an Oracle database &#8211; either again, to do some integration and data cleansing (the latter being the key part), and to just provide your data. Also, given my talks with the SA people last week, realistically you&#38;#8217;re still going to want access to an OLAP server (Oracle OLAP, MS AS) as the SA analytic engine isn&#38;#8217;t a MOLAP server as we know it, it&#38;#8217;s more akin to a ROLAP engine, so for your true high-end forecasting, OLAP calculations, even access to pre-aggregated data, you&#38;#8217;ll still want the OLAP Option.<br />
I&#38;#8217;m working through a presentation and paper on this very subject actually, once I&#38;#8217;ve done it, i&#38;#8217;ll post it to the blog and get some feedback. It&#38;#8217;ll be along the lines of &#38;#8220;How the Oracle BI Analytic Engine fits into a traditional Oracle DW architecture&#38;#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Macdonald</title>
		<link>http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/comment-page-1/#comment-900</link>
		<dc:creator>Brian Macdonald</dc:creator>
		<pubDate>Wed, 03 May 2006 02:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rittmanmead.com/wp2/2006/04/27/tuesday-and-wednesday-at-collaborate06/#comment-900</guid>
		<description>Mark,
Can you comment on why you stated &#8220;(which could remove the need for an Oracle database + OLAP Option)&#8221;  I don&#8217;t think the analytical server would remove the need for a database.
I would love to understand your thoughts in more depth.
Thanks,
Brian</description>
		<content:encoded><![CDATA[<p>Mark,<br />
Can you comment on why you stated &#38;#8220;(which could remove the need for an Oracle database + OLAP Option)&#38;#8221;  I don&#38;#8217;t think the analytical server would remove the need for a database.<br />
I would love to understand your thoughts in more depth.<br />
Thanks,<br />
Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/comment-page-1/#comment-899</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sun, 30 Apr 2006 22:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rittmanmead.com/wp2/2006/04/27/tuesday-and-wednesday-at-collaborate06/#comment-899</guid>
		<description>Hi Pete
I&#8217;m still trying to come to terms with the EE pricetag - $225k per CPU, which means $1m for a reasonable, 4 CPU deployment, is certainly not a mass market proposition. It also significantly reduces the amount of potential customers for a consulting practice such as ours (and yours I presume).
As you say, the $25k per CPU for the SE-1 offering is good, but it lacks the alerting and delivery options of the EE, which doesn&#8217;t really leave you with much more than you get with the standard, Standard edition. Certainly I think the SE-One edition is the one we&#8217;ll come into contact with most, in realistic terms it&#8217;ll be the only version most small to medium size organisations in the UK will be able to afford.</description>
		<content:encoded><![CDATA[<p>Hi Pete<br />
I&#38;#8217;m still trying to come to terms with the EE pricetag &#8211; $225k per CPU, which means $1m for a reasonable, 4 CPU deployment, is certainly not a mass market proposition. It also significantly reduces the amount of potential customers for a consulting practice such as ours (and yours I presume).<br />
As you say, the $25k per CPU for the SE-1 offering is good, but it lacks the alerting and delivery options of the EE, which doesn&#38;#8217;t really leave you with much more than you get with the standard, Standard edition. Certainly I think the SE-One edition is the one we&#38;#8217;ll come into contact with most, in realistic terms it&#38;#8217;ll be the only version most small to medium size organisations in the UK will be able to afford.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete_S</title>
		<link>http://www.rittmanmead.com/2006/04/27/tuesday-and-wednesday-at-collaborate06/comment-page-1/#comment-898</link>
		<dc:creator>Pete_S</dc:creator>
		<pubDate>Thu, 27 Apr 2006 19:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rittmanmead.com/wp2/2006/04/27/tuesday-and-wednesday-at-collaborate06/#comment-898</guid>
		<description>At first I thought 1/4 million per cpu sounded expensive.. but the price stacks well against other tools - and the SE-1 price of $25,000 for upto 50 users and including database and OWB, well!</description>
		<content:encoded><![CDATA[<p>At first I thought 1/4 million per cpu sounded expensive.. but the price stacks well against other tools &#8211; and the SE-1 price of $25,000 for upto 50 users and including database and OWB, well!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
