Last year in OOW, Oracle introduced a set of "coexistence scenarios," which explain how the "augmentation" approach to Oracle Fusion Applications can work and to guide customers on how they deploy Oracle Fusion Applications alongside existing Oracle products or non Oracle Products.

Co-existence approach implies that a customer is not upgrading or implementing an entire Applications Unlimited products to Fusion, but they will keep adding Fusion Application solutions (May be atleast any of the segments from Fusion Application pillar[see the details at end] ). In that case Customers will always look for opportunities that Fusion brings that address their critical needs while minimizing the risk to their current Applications Unlimited investment. This is the heart of the co-existence adoption model. Selecting the application that fits the customer’s needs and that complements the customer’s current applications footprint is Focal point. Oracle has crafted clear paths for application that there customers can choose today. Working with their strategic advisors they will determine based on their business needs, which of these fits their strategy best.

1. For customers that are tracking with Apps Unlimited today and are meeting their business objectives, the path is clear. To Stay on Apps Unlimited Products. Apps Unlimited means Oracle will continue to make investments in their current application product lines whether it be EBS, PeopleSoft, Siebel or JD Edwards. With that strategy Oracle encourages customers to consider standardizing on Fusion Middle ware components. Whether it be the application development environment, reporting with BI, IDE, webcenter, or embracing a centralized SOA strategy. This is basically leveraging a the common FMW stack is future proofing your investments.
2. For customers who do decide that Fusion Application do fit into their roadmap, there are two clear choices.
   1. Move to Fusion in an incremental approach
   2. Upgrade an entire pillar or combined global single instance to Fusion.

Oracle believes that a significant number of customers who move to early releases of Fusion Applications are going to do so in an incremental fashion. They will look for opportunities that Fusion brings that address their critical needs while minimizing risk.That’s what co-existence is all about.

This strategy will immediately open up the entire Oracle Apps install base for potential adoption.

What/How are in Fusion Co-Exist Pillars

• Pillar 1:Financials & Supply Chain Management
• Pillar 2:Human Capital Management
• Pillar 3:Customer Relationship Management

Fusion Co-Exist Modules

• Talent Management
• Distributed Order Orchestration(DOO)
• Accounting Hub (GL+Hyperion)
• Sales Performance Management
• Territory Management
• Quota Management
• Incentive Compensation
• Project Portfolio Management
• Spend, Sourcing & Contracts
• Incentive Compensation
• Workforce Lifecycle Mgmt
• Workforce Directory
• Procure-to-Pay
• Customer Data Hub
• Product Data Hub
• Governance, Risk & Compliance

Hope this post helps you to understand the BI in term of fusion.

Other Fusion Post

• BI in Oracle’s Fusion Applications : An Quick Overview ^[1]
• Fusion’s Functional Setup Manager ^[2]
• Oracle Fusion Supply Chain Management – A Brief Overview ^[3]
• Oracle Fusion Procurement ^[4]
• Oracle Fusion Project Portfolio Management ^[5]
• Oracle Fusion Financials Application ^[6]
• Oracle Fusion and Oracle Fusion Applications : Overview ^[7]

1 Comment To "Oracle’s Co-Existence Strategy"

#1 Pingback By OFA: Oracle Enterprise Scheduler | OracleApps Epicenter On July 4, 2011 @ 7:57 am