Seems like lots of customers and potential customers are struggling with a good approach for implementing Fusion Applications. With the discussion starting to build momentum, I thought I'd throw in my two cents.
Approach the implementation project as a solution-driven implementation rather than a requirements-driven project.
1. Install the apps, which is an entirely different discussion in and of itself.
2. Use Oracle Fusion Functional Setup Manager to configure and setup the applications. Nothing fancy here...just follow the directions.
3. Enter some seed data, execute the business processes as designed in Fusion Applications, then evaluate those business processes against your business.
4. Only after completing step 3, extend, personalize and tailor as needed. Use the Composers and this effort will be smaller than you expect.
5. Test, test, test.
6. Go Live
Step 3 is where most folks are missing the boat. Oracle went to huge efforts to build best business practices into Fusion Apps, researching hundreds of enterprises and collecting the best from each. The resulting product is the Fusion Applications Business Process Model.
Chances are that the model fits your business a little better than you might think. Heck, you might even pick up a nifty business process improvement or two.
So my suggestion...bring it up, explore how it works out-of-the-box, and consider the fit for your business. I think you'll be pleasantly surprised.
- Posted using BlogPress from my iPad
2 comments:
As per your analysis, the Business Process (and perhaps data model) is a great one for Fusion Apps. However, the architecture and infrastructure requirements are so gigantic that very few companies will ever implement Oracle Fusion Apps on premise. Unless a hosted solution is available, Oracle Fusion Apps will be limited to the 1%
Mohan, I agree. The real play for Fusion Apps is SaaS and OnDemand...even for the Co-Existence customers.
Post a Comment