We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.


The Requirements of the Data Delivery Platform


Originally published February 4, 2010


To avoid confusion and misconceptions with respect to the data delivery platform (DDP), Rick van der Lans lists the minimum requirements of a DDP-based business intelligence system.

Rick van der Lans
Rick van der Lans



Want to post a comment? Login or become a member today!

Posted February 6, 2010 by Robert Eve reve@compositesw.com

Rick -

It is great to see the progress of your Data Delivery Platform series. 

This practical capabilities checklist is a valuable complement to your earlier conceptual and definitional content. 

You are doing your readers a good service.  Keep it up.

Is this comment inappropriate? Click here to flag this comment.

Posted February 5, 2010 by Rick van der Lans rick@r20.nl

Hi Srini,

Thanks for your comment in my article. The architecture I propose is not a nirvana in the sense it is not feasible. We have tools on the market that allows us to build business intelligence systems based on this architecture today. Check out for example Composite Information Server and Oracle BI Server (at the heart of OBIEE).

And you're right, some tools support metadata layers that hide the data stores. However, those layers can't be accessed by tools from other vendors. In other words, they don't have an open API. The tools above do. Specifications maintained by those tools can be used by tools from all kinds of vendors, they are sharable specifications.

If relationships between data objects change and if those changes are applied for a particular report, then we will have to change both layers. Which makes sense. However, if a relationship is changed but those changes are irrelevant for specific reports, the DDP should be smart enough to translate the new data structure to the old structure (if it can technically be reconstructed), and the reports would stay unchanged.

Hope this explains it well.

Is this comment inappropriate? Click here to flag this comment.

Posted February 4, 2010 by Srini Ganesan

"Data consumers decoupled from Data stores" sounds like nirvana.

Even though tools like BOBJ, MSTR, OBIEE etc., use a (universe/objects/rpd) metadata layer to isolate the data store (db objects) from data consumer (dashboards) any change in the relationship between db objects affects the metadata layer and eventually the dashboards...

Rick, are you proposing or did you have in mind a totally different tech stack?

Is this comment inappropriate? Click here to flag this comment.