![oracle business intelligence applications require coding oracle business intelligence applications require coding](https://i.pinimg.com/736x/b5/ab/ff/b5abff251b404388557a40ef20d30467.jpg)
With BI Apps, we have the ability to install the out-of-the-box (OOTB) product fairly quickly and allow users to see what the OOTB dashboards and subject areas will look like with their own data. Personally, I don’t like this approach in general and I certainly think that there is a better approach for BI Apps projects (see a description of Extreme BI by Stewart Bryson for Agile methodology with OBIEE). Often, big waterfall-style IT projects go through requirements and design phases before users begin to understand exactly how the final product will look and function. Let’s start at the beginning of the Project Life Cycle. Now, how do we go about achieving these goals? Well, the answer is long enough to merit a few blog posts! Before we focus on anything too technical, let’s talk about how we handle requirements and design. Ideally, there should be some measurable ROI.
![oracle business intelligence applications require coding oracle business intelligence applications require coding](https://docs.oracle.com/cd/B14099_19/bi.1012/b16378/img/owb_mapedit.gif)
In either case, data from Oracle source systems is loaded into the Oracle Business Applications Warehouse (OBAW) using prebuilt Informatica / ODI metadata. Now, Oracle also provides BI Apps versions that use Oracle Data Integrator as the ELT tool. It uses OBIEE as a reporting platform and until recently, Informatica as the ETL tool. Oracle Business Intelligence Applications (OBIA or BI Apps) is a packaged BI solution for use with Oracle source systems such as EBS, JD Edwards, Siebel and PeopleSoft. Successful BI Apps Implementation Part 2: BI Apps 7.9.6 Introduction to BI Apps Successful BI Apps Implementation Part 1: Introduction and the Project Life Cycle I will add the links in as the postings are published, but here are the topics and links for the other parts of the series: Looking ahead to 2014, I will look at BI Apps 11g and how our steps to a successful project are affected by the architectural changes to the product. In Part 2, I will look at BI Apps with Informatica and DAC, focusing on good technical implementation and aspects of customisation that are often overlooked. Most of this will be non-technical and will examine the BI Apps project lifecycle as a whole.
Firstly, I will try to justify why BI Apps can add so much value to a business and how best to extract this value from the product. Over the next two postings I will be looking at what makes an OBIA project successful. Being an OBIA consultant, my work combines CRM, ERP, ETL, data warehousing and analytics. I have a background in Siebel CRM and many of my BI projects have involved integration with Siebel. I am Mike and I have been working at Rittman Mead for the last year, mainly focusing on Oracle BI Applications. Since I am new to the Rittman Mead blog, let me first introduce myself.