oracle fusion applications overview_s318276s2_trans
TRANSCRIPT
<Insert Picture Here>
Oracle Fusion Applications OverviewSteve MirandaSenior Vice President, Applications Development
Presenter
Presentation Notes
Transcript: STEVE MIRANDA: Thank you all for coming. After the party last night showing up at 9:00 is to be commended, so I appreciate all the die-hards that got out here to hear a little bit about Fusion Applications. Author’s Original Notes: Tuesday, September 21 | 11:00 a.m. - 12:00 p.m. | Moscone West L3, Room 3002/3004�Thursday, September 23 | 9:00 a.m. - 10:00 a.m. | Moscone West L2, Room 2002/2004 Oracle Fusion Applications Overview In this must-attend session for Oracle Applications customers, Oracle Applications Development Senior Vice President Steve Miranda reveals the details of the Oracle Fusion Applications suite. Learn how Oracle's investments in each product line, together with Oracle's investments in technology and next-generation applications, can improve manageability, increase user productivity, and provide agility to your business processes. Leave with an understanding of how your organization can begin leveraging Oracle Fusion Applications to transform itself into a next-generation enterprise that empowers your people with the power to know, act, and change as your business evolves. Steve Miranda | Senior Vice President, Applications Development, Oracle
Questions
What is Oracle’s Applications Strategy?
What are Fusion Applications?
What is Oracle’s commitment to Applications Unlimited?
What is the path to Fusion Applications?
11
22
33
44
Presenter
Presentation Notes
Transcript: So what we're going to cover today is these four things, so when you walk out of this door I want to make sure you understand what Oracle's overall applications strategy is, where we're investing, how fusion plays a part in that overall application investment. What Fusion Applications are, so I'm going to go into a lot of detail on what they are from a functional perspective, and I'll bring in some of the technical aspects of Fusion. I'll also walk through kind of why we're investing in what we're calling a next generation application platform or a next generation business applications, why Oracle's going through and making this investment. Can't leave an applications session without tripling down on our commitment to all the investment that we have in all of the existing product lines today. So I'll give you a little bit of background on what we're doing and how we've been investing over the last five years, I'll walk you through the roadmap very quickly. And then one of the questions that we get asked the most is what is the path if I want to consider some level of adoption for Fusion Applications, what is the path that I should be considering. So these are the four topics that we'll cover today as we go through, so jot them down and check them off as we go through. Author’s Original Notes: As a leader in innovation, Oracle has always invested in next generation technologies and Fusion Applications are no exception. Just like Oracle was the first to deliver global client/server applications and then an internet-based complete suite of applications, Oracle leads again in delivering a suite built on 100% open standards. 1990: the first global client/server applications 2000: Oracle announced the availability of E-Business Suite, the first and still the most complete, internet-enabled, integrated suite of business applications that spans both front- and back-office operations. 2010: Oracle announces Fusion Applications, the first 100% standards-based applications.
3
Why did we build Fusion Applications?
Why did we build Fusion Applications?
Presenter
Presentation Notes
Transcript: So why did we go about and build Fusion Applications? I'll start with the story and then I'll get into some of the details behind it. I actually came from PeopleSoft, I was acquired into Oracle. I can tell you PeopleSoft, and JD Edwards at the time was part of PeopleSoft, had a pretty big investment that we were looking to make. We recognized that there was an inflection point in the market and our customers would soon be requiring a platform that was significantly easier to manage, lower cost to upgrade and support and patch and integrate to other systems. And we had a pretty big investment on the plate prior to being acquired around getting to that modern standards-based platform. When we got acquired Oracle had a very similar plan. The E-Business Suite was going through a similar modernization, they had a strategy to do that. And then shortly down the road Siebel was acquired and they had a brand-new tool set that was almost done or nearly done and it was on a standards-based platform, and they were trying to progress to this modern business application platform that was going to carry them through for the next 10 to 15 to 20 years. So we all saw as different separate individual companies this inflection point happening. I'll go into more details about how it's laid out. And so instead of making that investment four or five separate times we're making that investment once and really offering it as a choice to customers over time to consume pieces of Fusion Applications or have a choice to look at broader deployments as the business need arises within your organization.
The Driving Force: A New Inflection PointThe Driving Force: A New Inflection Point
Presenter
Presentation Notes
Transcript: Let me go through that in a little bit more detail. Oracle has really always been on the front line of new technology adoption, and if you look at how application platforms have progressed over the last 20 to 25 years, it really started in with mainframes and moved into character mode. New vendors came and went as we went into client server. This is when PeopleSoft came into fruition or came to be, this is when Siebel entered the market, new platform, new capabilities. We moved to an Internet architecture where we tried to lower the cost to deliver more business applications to everybody's desktop, and we think we're entering in another inflection point here. And at each stage of that change to a new application platform it wasn't that the mainframe system couldn't close your books, couldn't pay suppliers, couldn't collect receipts or character mode or client server. It was as the platforms progressed and if you stayed back on prior platforms, it became significantly more costly for your organization to support those products, to integrate them with other systems, to patch them, to upgrade them, to configure them, to add additional business applications or modules and have them run alongside of those older platforms. So one of the key reasons we're investing in a next generation platform is we see this as a way to modernize the application platforms that we have today. The second inflection point that was key is we have seen and we spent a lot of time -- actually Debra Lilley who chairs and is kind of the head of all User Groups was up here in the last session, this is a repeat session. And we had a lot of User Group involvement, a lot of customer involvement when we were designing Fusion Applications. And one of the things that became very clear was that users of our applications are operating differently than they did 5, 10, 15 years ago. They're used to operating in social applications like Facebook or on the web looking at how their stocks are performing and seeing embedded charts and graphs and intelligence alongside of information that they care about on a day-to-day basis. And we saw this and we said we really need to redesign the user experience. We need to make the user experience much closer to what you're doing on a day-to-day basis in modern web applications that you operate on day-to-day. And so you'll see some of that, and we really want to take a step forward to modernize the UI and bring in collaboration and bring in Business Intelligence and make it part of the system that you're operating in. Versus how it happens in most organizations today where you have a transaction processing system, and then you go completely outside in a different context to collaborate, create Wikis and group spaces. Or to get analytic information you go to a completely separate system and then come back in, remember what you were doing and complete your task or complete the process that you were trying to execute on. So what we saw is we need to really change that user experience, change our products to respond to how you want to do work in business applications. And then on the technology front, the kind of third component of the inflection point and why we made this investment in Fusion Applications, is really from a couple of perspectives. We heard loud and clear that organizations want to get business value without having to continually rip and replace their in-place ERP or CRM systems. And they want to get that business value so they want to consume capabilities over time, add value in their business. And so that's part of why we developed a Services-Oriented Architecture, but delivering, and I'll talk about some of the coexistence opportunities, delivering a lot of our solutions in modular form so you can connect them to your in-place ERP or CRM systems very, very quickly. And then finally the other component from a technology perspective is recognize that business models are changing and organizations no longer only want to run their entire ERP and CRM footprint on premise. They want to have a choice, and they want to have a choice where sometimes they might want to run it 100% in the cloud, they might want to run it 100% on-premise. But a lot of organizations might want to run it in a hybrid mode where they're running some of their applications in the cloud, whether that's regionally split. So maybe in South Korea or Turkey I'm going to run in the cloud, and in North America I'm going to run on-premise, so they could start to break up regional components of their application and run them separately. Or certain functional areas might lend themselves more to SaaS versus on-premise. So we needed to build in this capability to support a significantly more flexible deployment options for our customers. So those are really kind of three key inflection points that we went through in designing Fusion Applications, but really the background as to why we're making this investment. Author’s Original Notes: So, what are the inflection points that shaped our new approach to building business applications? First, customers are moving to service-oriented applications and want a standards-based applications platform. Second, businesses are seeing a dramatic shift in the way people work. Employees are used to connecting with friends through chat, social networking sites and online communities and expect these kinds of Web 2.0 capabilities in the workplace. The nature of people’s work also has changed, from doing routine tasks to managing exceptions and making rapid decisions. Finally, customers want to be able to deploy new technologies quickly and selectively, either in the cloud or on premise, with modules that address specific business problems.
What are Fusion Applications?
5
What are Fusion Applications?
Presenter
Presentation Notes
Transcript: So what are Fusion Applications? Fusion Applications are business applications, front office and back office business applications, they're built on a standards-based modern architecture. We've redesigned the UI to incorporate Business Intelligence and collaboration, and they're available in the cloud or on-premise or in a hybrid fashion. That's top level, in a nutshell.
The Making of Fusion Applications
Started with a Modern PlatformIndustry-leading, standards-based, configurable, adaptive and secure Fusion Middleware
Built Best Practice Business Processes Based On Hundreds of Years of LearningE-Business Suite, PeopleSoft, JD Edwards, Siebel
Reinvented the User ExperienceRole-based user interface, embedded decision support, pervasive collaboration
Made Ready for the Cloud Private or public cloud
All in Collaboration with Oracle’s Customers and Partners
Presenter
Presentation Notes
Transcript: When we went through and began to design Fusion Applications, I'll give you a little bit of information of what is underneath the covers. So certainly you heard in Larry's session, you'll hear multiple times in this session we started with a standards-based platform. So what does this mean, why is this important? What this means is all of the middleware components or the majority of the middleware components that are commercially available today that customers are using to run their businesses in certain areas, that is the backbone of Fusion Applications. So what I mean by that is we no longer are as application developers developing middleware technology. So every single application platform has an ability to provision new users into the system. They have kind of a built-in security model, they have a built-in provisioning model. We have a standard-based identity management suite that does that better than any application developer could ever build. We're leveraging that capability as the way to provision new users into the systems, all baked into the Fusion Applications platform. And you don't have to worry is it going to support maybe another provisioning, maybe an enterprise set of roles in your organization, it can be expanded to do that. But that's what we use to provision new users into the system. We didn't build a whole set of net new Web 2.0 capabilities. We have a great web center product that has been working on collaborative capabilities, collaborative group spaces, RSS feeds, all of these things. And what we did is we took those capabilities and we built them in in the right places into Fusion Applications. So we leveraged a lot of the standards that is already available in a middleware technology stack to design and build and support the next generation Fusion Applications. I will tell you it's built on standards, and I can give you one example. Probably halfway through our development process we acquired BEA, and prior to that we were building on Oracle's iAS, Applications Server, and the virtual machine was OC4J. And in one build we were using OC4J as the VM, in the next build we swapped it out and we were using WebLogic Server, and everything worked, wasn't any missteps. So being standards-based allows you to have those types of choices, and I'll give you some more examples as we go through the presentation. The next area that we focused on was taking some of the best capabilities that we had and the years of learning that we had across all the different product lines, and brought them in and tried to design what we thought was going to be the most robust and capable platform to support our next generation application. So from a starting point we started with the most robust ERP data model and that was the E-Business Suite had the most robust ERP data model. We brought in the customer model from CRM, very robust, had a very strong set of industry capabilities, we brought that in. Then we took some of the unique capabilities from PeopleSoft and PeopleSoft had developed a person model in HR in their 8.9 time frame, and it's one layer abstracted from the employee model. So they could support multiple worker assignments or make it significantly easier to transfer one person from one country to another country without having to fire them and rehire them. So we took the person model and we, obviously, conformed customer and employee or person throughout the data model, and I'll talk about one common definition of each of the major objects, and we started with that from a data model perspective. And then we took some of the better ideas around functional architecture and some of the unique capabilities that the different product lines brought to bear. So I'm just giving you a few examples, but PeopleSoft had some unique capabilities around the ability to share reference data across multiple business units. So if you've ever had a set of suppliers that you wanted to create a global set of contracts with and you wanted to share those across all of your org units or all of your business units, you would have to replicate those suppliers in every single org unit that you were creating. PeopleSoft has something called SetID which allowed you to create a global set of suppliers one time and you could share that across all of your business units, so you could create much more robust shared service environments to operate your business. In some instances like this one we took it to the next step where not only did we support that ability to have a central set of global suppliers, we also said in some instances customers want to have a local set of suppliers as well. And so we provided that level of flexibility to share reference data where it makes sense and to have local reference data where it makes sense as well, so we tried to take some of those concepts. Another key one is trees. So if you've ever worked in PeopleSoft and you had this notion of a tree for navigating hierarchies, it was a very easy concept, easy to understand, easy to reports off of. We used trees as an underlying concept in how we designed our hierarchy infrastructure, whether it's a manager hierarchy or a chart of accounts hierarchy, all of those things we used trees as a key component. So we tried to take a lot of, and there's many more examples, but we tried to take a lot of the key capabilities, whether it's data modeled or functional architecture and kind of bring those together to form the kind of backbone of Fusion Applications. And then we completely redesigned the user experience, so I have a couple of demos that I'll show you today and I'll talk through kind of how we went about the user experience and design. But we worked with thousands of customers and you probably have been involved in a usability study at Oracle, we're at every conference, and I'll give you some more details as we go forward. And we designed it to work in the cloud, in on-premise or some hybrid. But what's key about how we built these applications is we worked with customers from the beginning to the middle to now we're in our early adopter program, we have a number of customers that are implementing the products right now, unprecedented. We started with 150 companies and then personnel in each one of those companies in different functional areas, and we stayed with that group from beginning to middle to we finally go GA, and they've been part of the process from requirements to design through testing, and we have robust testing through early adopters. So we had a very large set of functional testers that stayed with us and gave us a significant amount of input through this process.
Fusion Applications The New Standard for Business
The New Standard for Innovation
Complete applications platform that adapts to your
business
The New Standard for
Work
Complete user experience that
shows what you need to know or do
The New Standard for
Adoption
Complete choice of options, from cloud to
device and suite to module
Presenter
Presentation Notes
Transcript: So I'm going to go through these three key areas. First is why we think it's a new standard for innovation, and I'll give you some details there, why we think it's a new standard for work, and the new standard for adoption,
The New Standard for Innovation Complete Applications Platform
Role-Based User ExperienceWhat You Need to KNOWKNOW
What You Need to DODOWHOWHO Can Help
HOWHOW to Get it Done
Unified Information
Services
Intelligent Business Processes
Business Unit
Employee
Product Customer
Date EffectivityLedgerOrganization
TreesTerritory
…
Java, BPEL, XML, HTML, AJAX, Portlet,
RSS, Mobile, etc.
100% Open Standards
100% Open Standards
Presenter
Presentation Notes
Transcript: and I'll go through each one of these sections. So let me give you a little bit more details on kind of the platform itself and I'll start at the unified data model. So I said we took data models the same, we brought them together. We have one definition of customer, one definition of supplier, one definition of organization, one definition of person or employee, and that is shared in a unified data model. So I'll give you some details on how we can deploy and much more flexible deployments, but we have a complete end-to-end front office to back office unified data model. And I'll tell you how we can deploy that in smaller components, but everything is in one, it's been completely unified. The other thing that we did was we recognized that we needed to make this system significantly more open. So in Release 1 we have about 11,000 business services, nearly 11,000 business services that we deliver. So these are standard Java web services with a business connotation to them, so enter invoice, enter order, create employee record, create purchase order, enter expense. So these are all business services that we delivered as part of our application foundation. And why we think this is important, number one it helps us be able to deliver these applications in a much more modular fashion, so have clean interfaces. We can deliver chunks to you so you can consume these without ripping and replacing your in-place ERP or CRM system. Second is we think it'll benefit you from an innovation perspective, being able to be creative how you use these web services. And one of the examples and we've seen internally in Oracle Development is if you've heard of this iPhone app, I don't know it it's still around but it was called Jott. And what Jott did was allow you to record your voice, you could say I need to go to the store, pick up eggs and milk and whatever else I get at the store, and it would convert that into a shopping list for you. So just a straightforward shopping list, and a couple of minutes and you get that shopping list. And what they had was they had an open Java web service that they produced, and what somebody did in Development was basically create a service to say task 37 on project X, complete. And what that did is it produced a web service call, went to the projects application and updated task 37 and was signed off as complete. So those are some of the unique opportunities because we're creating an open system and because we're leveraging standard web services that organizations like yourself, without breaking the foundation of the application can take advantage of and extend our applications. From a business process perspective we really feel we've raised the bar in the configurability of the application, and I'll give you a few examples. So we designed Fusion Applications based on a business process model, so we designed it based on a business process model and all of our workflows, so we had workflows in all of our systems. All of our workflows, human task flows are built on a technology standard called BPEL. And all BPEL does is connect those 11,000 task flows to create process flows or human task flows within our applications. But we recognized that we're not going to nail some of your processes right out of the box. So because we're open and we produced these web services you can extend at a service, and I'll give you an example, very easily, and that can be maintained over time. We can store that for you. So let me give you the example. If it's a procure to pay process, simple, I'll make it three steps. You create an invoice, you receive goods and then you pay the vendor. If you wanted to add another step after you create the purchase order to check OFAC for people you cannot do business with, the Patriot Act, you wanted to add that step and you have a list of suppliers that you can't do business with, you could easily add that step in the process. It could be outside of our system, you could step out, come back in, complete the process, no problem. We'll store that new process flow, we have layered extensions that you can put into our application. We'll store that process flow and when we go apply a patch, when we go to upgrade you, there's going to be no issue with that step being changed. Now if you go to the next step and you really start to jumble around our process flows, we will identify where there's dependencies that you have created to other objects within our system and we'll make it very easy for you to know and to make changes if we apply a patch if it's going to impact one of those services that you've changed. So we've tried to be really smart about where you can make changes and make them as little impactful as possible. And where there is an impact we'll identify quickly if this is going to impact your ability to upgrade or apply a patch. So we think that's important. And then from a business perspective we really took a design principle around we think organizations work significantly more on an exception basis than they ever have in prior years and what we developed was a design principle around kind of these four key concepts. So throughout Fusion Applications, and when I demo the applications to you you'll see these four concepts come to light. So it's really about what I need to know, what I need to do, which is I'm going to push information, notifications, alerts, events to my work list so I know exactly what's critical for me to get done. I'm going to give you the information right there that you need to make a decision around that activity or action that you need to take. And if you can't get that activity done we're going to put collaboration in the system to point you to the right person that you can contact in order for you to ask for help or leverage that person to get your job done. So these are the design principles that you'll see throughout the 11,000 task flows that we've created in Fusion Applications. This is the core design principle and you'll see this come out.
The New Standard for Innovation 100% Open Standards-Based Applications
Lower Cost IT TalentLower Cost IT Talent Lower Cost IntegrationLower Cost Integration UpgradeUpgrade--Friendly Friendly CustomizationCustomization
11x more Java programmers than ABAP programmers
50% lower maintenance costs with standards- based integration
Extensive configuration options with zero impact on upgrades
Presenter
Presentation Notes
Transcript: Why we think standards are important, I think I've hit this long enough. We think it's going to lower your IT costs over time. We think building on standard technologies, standard programming languages like Java, using standard technologies like BPEL, HTML, SAML for security, XML, all of those things we think that is where over time will be the lowest cost way for you to manage, upgrade, integrate, support your applications. And that's why we think standards are important and that's why we've built them as kind of a core principle of Fusion Applications. I'll give you one more, extensibility. So we built in extensibility pretty robustly from two perspectives. One, there's a lot of extensibility native in the application. We had to design these applications to be SaaS-ready, and what that means is you can't call IT if you have to change a territory assignment in your system. You have to be able to easily go in and change a territory assignment or create a new report or create a new field in your application without always calling IT, or change a step in a workflow process without always calling IT. So we put a lot of configurability directly into the application. And then beyond that if you need something unique to your business, and I'll give you a customer example, so if you segment your customers based on gold, silver, bronze and you need to add that customer object into our system, you can add that business component. You can relate it to our core customer object, and as soon as you do that it is treated as a first class object or citizen in the application. What that means is any time you want to create a new report, a new BI report, add a field, look at it in the list of values, add it to a page, it's available. And it's protected in an upgrade scenario as I went through before, but you can easily extend the application of these objects without impacting your ability to patch or upgrade or support the application. Author’s Original Notes: Sources: 11x more Java programmers than ABAP (Charles Homs, Competitive Intelligence) 50% less to maintain standards-based integrations (Oracle Case Study on SOA transformation in Telecoms 2008 referenced in Insight presentation “The Business Case of AIA”) Configuration is done at the metadata layer, which doesn’t impact an upgrade
The New Standard for Work Customer-Driven User Experience
Up to Up to 60%60%Productivity
Gain*
Field Studies
User Experience Program
Usability Testing
• 180 roles• 6 countries• E-Business Suite, Siebel, PeopleSoft, JD Edwards
• 18 usability labs• 8 locations worldwide• Recording of eye- hand-screen behavior
* Estimate based on models
700 Users 4,000 Hours
1,000 Customers
Presenter
Presentation Notes
Transcript: So let me go in new standard of work. So from a usability perspective, we invested significantly in the usability of our applications. So thousands of hours, thousands of customers we worked with. You've probably been involved in some of our usability labs. We looked at our screens versus competitor screens and tried to do the best to make them as user-friendly based on the role that you have within the organization. So we performed really three types of tests, and I'll go through those quickly. So first was really unassisted tests. These are a lot of the self-service tasks that you do. I need to order a new computer, what are the steps in a self-service procurement flow. So we see if you can complete that process without being assisted, go in, order a computer. And we measure it, see how quickly you do it, what percentage of people can complete it and with the right help and prompts and those things. The next area is for really heads-down users, it's called unassisted testing. And this is where it's a more complex scenario but more of a heads-down worker, maybe an order entry person. And basically we let them use hot keys and how quickly they can complete the task with some assistance, you tell them what they're going to do. If you're a heads-down worker you don't want to be prompted, are you sure you want to enter that order, are you sure you want to do this. If you know what you're doing, you're hitting three hot keys and you're moving to the next step. So assisted, unassisted, and the last one which is if you've never participated in one of these tests it's really eye-opening and it's more of a psychological test I think sometimes, but it's called ergonomic testing. And you sit in front of a glass pane and they ask you to perform tasks, and they follow, they track your eyes to where you look on the page. So the one that is more psychological testing I guess is they'll say find the save button, and if you look in the lower left hand corner then you have other issues that you have to deal with, but everybody looks in the upper right hand corner. And we do those types of things to see what is the most likely place you're going to look when you're trying to complete a task, so those are the types of things we've done around usability testing.
The New Standard for Work
WHO do I need to reach?
What do I need to KNOW?
How do I get it
DONE?
What do I need to
DO?
Exception-based Management Embedded Business Intelligence
Configurable Applications & Processes Embedded Collaboration
Presenter
Presentation Notes
Transcript: This is the concept and I'm going to show you a couple of demos here in just a second if they're still up when I flip over, these are the concepts that we have as far as our design principles. So you're going to see what I need to do, so we're going to have a worklist in everybody's home page that prioritizes the key activities that you need to get done on a day-to-day basis, and that's in your worklist. Then you can go to what I need to know, so once you drill in it'll give you analytic information, intelligent information to help you make a better decision and this is pretty pervasive throughout the applications. It'll support you with workflow, what I need to get done. If it's a multi-step process you can go through the multiple steps. And then finally you'll see contextual actions throughout, which is who I need to contact. So on every person in the system there's a little orange carrot in the upper left hand corner and you can click on that. And if you want to VoIP them, you want to see if they're available through IM, all of those things is available throughout the system, so you can easily figure out who you need to work with.
Line of Business RoleLine of Business Role
The New Standard for Work Role-Based User Experience
Manager RoleManager Role
Presenter
Presentation Notes
Transcript: Everything in Fusion Applications is role-based from how we designed the application to the responsibilities that you have. Most people -- I shouldn't say most, a lot of people have multiple roles that they perform. They're usually a line of business function. So I'm an accounting manager and I'm also a manager of employees, so those are two roles that you would have, and we'll have home pages and dashboards and you can mix and match these easily, but those are the roles and how we'll outline how you get information into the system. Beyond that our security is based on roles, how you navigate is based on roles, everything is very role-oriented within the application.
Contextual Actions Contextual Actions
Contextual Action Contextual Action
The New Standard for Work Context-Driven Applications
Presenter
Presentation Notes
Transcript: I talked about contextual actions, this is one of the collaboration capabilities that we have. And this allows you, you can see on this contextual action or can sort of see, maybe not if you're in the back, that I could chat with this person, I could schedule an appointment. There's a lot of information directly in context to I want to do something with this employee, right. So I might want to call them, I might want to schedule an appointment, I might want to add them to my address book so I can call them later. All those things are available right here in context to the application, and not only for an employee, for a supplier, for an office location. All those things, it's available right here, one area of collaboration. Also we've included a lot of other collaborative capabilities throughout the applications, and you'll see those if you go to the demo floor -- that's not me. If you go to the demo floor, you'll see the different collaborations. So if you're in a project and you want to create a collaborative group space and you want to invite different project team members to participate in that PowerPoint, share information, those capabilities are inherent in the application. And people say why, I have this on the side, I can kind of do my own Wikis, and there's a lot of security, infrastructure, permissions that we create out of the box so you don't have to worry. As I say, critical document that I can't share with these five employees, or these five employees are on three different projects that I'm working with and I can't share all that project information across those, you don't have to worry about that. We create team space, you can collaborate completely secure, you can share information, we record history. All of that is available in another one of the collaborative environments. The one we did for any of you who stayed to the end of Larry's presentation yesterday, we demoed one in a sales situation where we created a sales team where they could share ideas around a particular deal. So these teams can come and go based on the situation that you're in. So sales teams work on an opportunity and then they disperse and go on, so they don't have to be long-running teams or group spaces that you can inject, and a lot of other capabilities. But what we didn't do was just put in a bunch of Web 2.0 stuff and say hey, go to town, figure it out. We tried to be smart and work with customers about where we injected these capabilities and made sure that they were in context to some task flow that you were trying to complete.
Demo
Demo
Presenter
Presentation Notes
Transcript: So if my demos are still running here I'm going to show you two quick demos. And we tried to make them different from sales scenarios, so let me show you a Financials flow. So this is a home page for maybe a general accounting manager that comes into the system and wants to understand what ledgers are open, what ledgers are closed as one of the pivot points. I'm going through a month-end close, this is the kind of process I'm going to go through. I'm going through the month-end close, I want to see have I closed a lot of my subledgers, so I can come down and I can see that information. And I can see down here that I have a journal entry late in the cycle, it's close plus four, so way late to be making journal entries, but somebody's made one, it's a receipt, I probably should see about approving it. So I could drill down on that and get to all the information that I need to have about this particular receipt. What you'll see on this page, and this is an accounting flow, is some interesting things. So first you'll see a lot of concepts like show more and show less. So a lot of times if you're a power user you don't need to see all the detail, so you'll go to show less. If you want to see more you can show more, so we have flexibility in how we can deliver information to you in the UI. Also we'll do some calculations for you, we'll tell you that this is what it's going to look like after you make this journal entry, so you can see some information about what is going to be transpiring. You can see the account information and all those things. So I'm going to go ahead and approve this journal entry, say yes, I'm done. So I've updated my system, and what you can see here is, and I didn't show you this, these trending indicators were trending in the wrong direction prior to making that journal entry. Now they're trending in the right direction. So we can have account level indicators as far as is this account balance higher, lower, trending in the right direction versus the previous period or two periods back. So we can put some intelligence directly in the accounting system to help you make better decisions about approving or not approving a particular journal entry, so intelligence kind of built into the system. So after I'm done with that I want to go look at reporting. So I'm going to come over here and I'm just going to go to my reporting page. And what I can see here and one of the things that we built in, we took some of the great technology that came over from an acquisition of Hyperion and we're supporting that in this process. So we're leveraging capabilities like Essbase to create our management reporting books. So it's very dimensional, easy to slice and dice, or you can create static in-place reports that are very robust and configurable. So we create a report here, and I can drill down on this report. And a very nice looking report, but I have pages that I can filter through it so it might be pages with different locations on them, so same report, multiple locations. So I have a lot of flexibility in order to create very, very rich and dynamic reports in our financials application. So quick Financials preview, showed you a couple of the capabilities there. Let me show you a procurement flow, hopefully still running, okay. So I'm coming in, what I'm going to walk through is just a purchasing flow. So I'm a category manager and I'm looking at my purchasing information, I want to see where I'm spending in my data center. And then I want to go through and start a negotiation. So negotiation is part of our sourcing application, but what I want to do is in order to get a better bid from multiple vendors I'm going to put an auction up. I'm going to get a bid, and then I'm going to select the vendor that best meets my RFQ and lowers my cost and give them my business. So that's the flow, I'm going to walk you through that pretty quick. So here I have a lot of analytic information. This is part of our Business Intelligence applications today, this is Spend Analyzer and this will be tightly integrated with Fusion Applications. But this is a product that you could leverage today to get a handle on category spend, so if that was important to you this is an application you can handle today. So I'm going to go in, and I can drill down on suppliers, and I want to see spend by summary. So I know I'm not doing great, I can see servers are a big spend area, so I'm going to drill down on that. And I can see here that this is what I spent with Oracle, this is what I spent with Natisa. And we had these demos built long before there was any acquisition so this is not a back-ended anything to IBM, so this is just for demo purposes. So I can see here if I want to see a scorecard I could drill down and see a supplier's scorecard and see how these vendors, so a little bit more information about these vendors before I start my negotiation. So I'm going to come in and I'm going to actually start a negotiation. So I'm in sourcing, and I come in and I'm a IT category manager and I come into my sourcing application and I have a lot of information that's available to me right away. I can see my negotiation calendar -- I need one of these with my wife, no I'm kidding, that was terrible. Okay, negotiation calendar, I have recent activity. I have my ongoing negotiations and these are negotiations that I have open, and I'll walk you through that. And then I have a draft so I'm creating an RFQ, an RFP to go out for bid to procure a new server at a lower cost than what it's costing me today, it's a high cost in my data center. So I'm going to drill down on this high-performance server, and I'm brought to this RFQ. So, obviously, content management is kind of built in so I have a document look and feel. I can create the request for quote in my RFQ. You can see here we have a train, so these are all the workflows that you'll see throughout Fusion Applications. There's a notion of a train concept and you can go to different steps in the train. In some cases they don't have to be in order, so it could be a long-running process like an on-boarding process where I can do some tasks outside of other tasks. But I'm going to drill down on the overview, I'm going to look at the overview. This is where I have rules for the particular RFQ, I won't go into all the features and functions. I want to see who is on my collaboration team, who's on my team. As I'm creating this sourcing event, I can see that I have Claire here. I get a contextual action that can bring up Claire. If I want to see where Claire is located I could bring up a map. And you can use any map plug-in that you want, it'll bring up a map, a location identifier of where Claire is. So great, I could collaborate with her if I want, it's not something I'm going to do right now. I'm going to go ahead and publish out this proposal, so I've sent this out to all the vendors that might or suppliers that might want to participate. And then this is the fun part in a category manager's day is you get to watch and monitor ongoing auctions. So I come in, I see my high-performance server's now in an auction, I can come in and I can start to monitor it. So I can see the bids as they're coming in, I can see the savings that I'm going to make, I'm like I'm going to get my bonus this quarter, look how much I'm going to save. And so I can monitor this as much as I want, I can close that out. I can see that my auction has closed, so my auction is done. I'm going to highlight that, I'm going to take some sort of action, I'm going to award the negotiation. So I've seen, I can see all the details for this particular RFQ, I can see clearly that Oracle Exadata is the clear winner here. So I'm going to go ahead and save that and close that out, and I can see the savings at the end that were created. So what I showed was a couple of things. I showed kind of the embedded intelligence, I showed some of the collaboration capabilities that's built in natively, and you'll see that in different key points throughout the business flows. And then I show kind of the analytics at the end, what is the result that we've just made in this change. So I tried to show you a few of the key concepts in a sourcing application which maybe not a lot of you enter into on a day-to-day basis, but it's a concept or a kind of flow that kind of highlights some of the key attributes that I've been talking about.
The New Standard for Adoption Choice of Deployment Options
Public Cloud Private Cloud
On Premise Hybrid
Deployment Options
Presenter
Presentation Notes
Transcript: So let me come back into the presentation and we'll go into the new standard for adoption. So I won't spend a ton of time on this, just a couple of key points here. I talked about deployment, so we'll have multiple flexible deployment options and we've architected this in from the ground up. And what's unique about this offering is whether it's deployed in a cloud, in a SaaS environment or it's deployed on-premise, there's only one code line, meaning we don't have a separate set of code lines for what we have in the SaaS world, for what we have in on-premise world. And what this allows us to do is you could migrate over time. You could start for the first year in a SaaS deployment model, and then if you want to take that and put it on-premise, we'll pick up the stack, we'll move it over, and we'll put it on your premise and you can manage it from there. So it gives our customers a -- and it's not a different code line, it's that same code line, and you have a level of flexibility that has never been offered before, so pretty critical and pretty important point.
The New Standard for Adoption Choice of FunctionalityOracle FusionOracle Fusion
Financial ManagementFinancial ManagementGeneral Ledger
Accounts Payable
Payments & Collections
Asset Management
Accounts Receivable
Cash & Expense
Management
Common Modules KPIs, Dashboards, & Extensibility FW
Oracle Fusion Oracle Fusion Human Capital ManagementHuman Capital Management
Oracle FusionOracle Fusion Supply Chain ManagementSupply Chain Management
Product Master Data
Management
Distributed Order
Orchestration
Inventory Management
Global Order Promising
Cost Management
Shipping & Receiving
KPIs, Dashboards, & Extensibility FW
Oracle FusionOracle Fusion Project Portfolio ManagementProject Portfolio Management
Project Costing
Project Billing
Project Control
Project Performance
Reporting
Project Integration Gateway
Project Contracts
KPIs, Dashboards, & Extensibility FW
Oracle FusionOracle Fusion Customer Relationship MgmtCustomer Relationship Mgmt
Customer Master Sales Marketing
Incentive Compensation
Mobile & Outlook
IntegrationTerritory &
Quota Mgmt
KPIs, Dashboards, & Extensibility FW
Financial Compliance
Issue & Risk Manager
Access Controls
Transaction Controls
Configuration Controls
KPIs, Dashboards, &
Extensibility FWOracle FusionOracle Fusion
Governance, Risk & ComplianceGovernance, Risk & Compliance
Global Human Resources
Workforce Lifecycle
ManagementBenefits
Compensation Management Talent Review Performance
& Goal Mgmt
Global Payroll
Network @ Work
KPIs, Dashboards, Extensibility
Oracle FusionOracle Fusion ProcurementProcurement
Purchasing Self-service Procurement Sourcing
Supplier Portal
Spend & Performance
Analysis
KPIs, Dashboards, & Extensibility FW
Procurement Contracts
Presenter
Presentation Notes
Transcript: So scope, hair scope for Release 1. So Release 1 is targeted, we'll working with early adopters today, targeted for Q1 of next calendar year to be generally available. We have a lot of customers and if you're interested in our early adopter program you can come up, and Carr's been working with a lot of customers already today. Here's scope, kind of core Financials, core Human Capital, core Supply Chain Management, although manufacturing like BOM and WIP and Warehouse Management, those kind of core manufacturing's not in Release 1. We focused on some of the supply chain applications and some unique offerings like Distributed Order Orchestration that could work with in-place deployments of manufacturing and I'll give you some examples when we get into co-existence. One of my favorite areas Project Portfolio Management is available in Release 1, Fusion Procurement, Customer Relationship Management and, of course, a full suite of Governance, Risk and Compliance.
The New Standard for Adoption Choice of Adoption Scenarios
Existing Apps Co-Existence Fusion Apps
Presenter
Presentation Notes
Transcript: Adoption options, so one of the things that we wanted to be able to identify was six patterns of adoption that our customers we believe, at least our early adopters have communicated to us how they will start to adopt Fusion Applications. Pattern #1 is I'm heads down, I'm going to stay on my current path, I'm just going to upgrade to the latest release and I'm not going to do anything with Fusion Applications, and that is perfectly fine. You could continue down that path, we'll continue to invest in all of the application and limited product lines and no issue there. Adoption option #2 is I want to adopt a component, but I'm really not going to integrate with anything else, just kind of a standalone component. In this bucket it might be Fusion CRM, I might want to do salesforce automation in the cloud, territory management, quota management. And I'm not going to integrate with anything else, I'm just going to run that separate, another pattern that we're seeing customers adopt and I'll give you some more examples of those. What we're calling Pattern #3, which is kind of loose interoperability. So this is one where it's not real-time updates of changes that are happening in the different transaction systems, so we're calling it loose because it's a kind of one-time batch feed and then a synchronization maybe nightly. The example here is that we see some customers that are looking at one of our talent management applications like Performance Management and having that integrate back to an in-place HR system like PeopleSoft or E-Business Suite. And the exchange of information is around employee skills and competencies, maybe performance evaluation criteria. And it's a batch feed to start and then it's a synchronization maybe nightly or every couple of weeks as to how often that information changes. So we're calling that design Pattern #3, kind of loose integration but a synchronization process nonetheless. And then the fourth kind of co-existence option is what we're calling tight integration, and this is more that this is a real-time level of integration that we need to have. So one of the products that customers are looking at from a co-existence opportunity, which is basically I'm going to leave my ERP system in place or my many ERP systems in place, and I want to deploy a Fusion Application to co-exist with that in-place ERP system. And one of these, a great example of Pattern #4 is Distributed Order Orchestration. And what Distributed Order Orchestration does is it connects front CRM-related capture systems, so I might have an online store, might have Siebel capture, might have a custom capture system, to many fulfillment systems. On the backend I might have E-Business Suite, I might have JD Edwards, I might have a drop-ship warehouse that I drop-ship from. And Distributed Order Orchestration sits in the middle and acts as an order hub brokering requests from a capture perspective to fulfillment from multiple warehouses, and it can do available to promise and lead times in one central environment. So we need tight interoperability or integration for that because as an order comes in, I need to make sure what availability I have so I can commit that order on the backend to my fulfillment system. So that's an example of tight integrations, Pattern #4. Pattern #5 is I'm going to replace an existing Oracle application with a Fusion Application. Perfectly legit, we're going to offer like-for-like exchanges for those types of opportunities and customers can look at that if the footprint is right. And then last, which it's going to be great is we can replace third parties, so non-Oracle applications. Obviously we can plug those in as part of this foundation. So six design patterns, the co-existence in the middle is where most of our customers have been looking.
Fusion Co-Exist Pillars• Talent Management• Distributed Order Orchestration• 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• etc…
Fusion Co-Exist Modules
Pillar 1:Financials & Supply Chain Management
Pillar 2:Human Capital Management
Pillar 3:Customer Relationship Mgmt
The New Standard for Adoption Fusion Applications Work with Your Existing Applications Investments
Presenter
Presentation Notes
Transcript: So that's why the next slide is a little bit more detail on those three design patterns in the middle around co-existence, so I'll give you a few examples of how we see these applications co-existing. So talent management, I gave you that example, it could be in the cloud, it could be on-premise, existing with an in-place HR system. Distributed Order Orchestration, gave you that example, multiple capture, multiple fulfillment, order hub in the middle. The accounting hub, so this is one where a number of financials customers, I might have multiple general ledgers, I might have other line of business systems, so I might be a bank and I have my banking system. But I want to create a standard set of accounting rules across all of my systems. The accounting hub can be standalone, it's the GL and basically Hyperion or Essbase 4, very robust management reporting. But I can create a standard set of accounting processes, accounting rules that cut across all of my legacy or subledgers outside, so I can bring those together for financial reporting. So the accounting hub is there. I talked about sales performance management. Spend, sourcing and contracts is another one that customers have approached us, they want to get a handle on their rogue spending within their organization. And so what they start with is a combination of Spend Analytics, so I want to see where we're spending. Then I want to start to renegotiate those purchasing contracts with suppliers, and then I want to create auctions and negotiations to drive the cost down of some of those supplier costs. And that package of Spend, Sourcing and Contracts is another coexistence opportunity that we're talking to with customers. I'll give you two more, Workforce Lifecycle Management is an on-boarding process, can work with our systems or other systems. So a much more human-oriented way to walk you through or walk a new employee through all the steps of on-boarding. So get your office, get your PC, take these training courses, do these other things, and it can be an multi-month process for on-boarding. And then the data hubs are there, so if you want to get a handle on master data, reference data, customer data or product data, those could be standalone and you could run them. And the way we architect this, we have a number of opportunities for these modules to coexist with in-place deployments that you have within your organization. On top of that we support different more broader-based deployment options. So if you were a PeopleSoft only and a Siebel only customer, you deployed CRM separate from HR, separate from Financials and Supply Chain. In Fusion you will have the ability to do that just the same. I could have CRM and HR separate from Financials and Supply Chain. You can actually deploy Fusion in some smaller chunks, the ones that I said on the left. Or if you're a traditional where you came from EBS or JD Edwards you can deploy it as a single integrated instance where HR, CRM, Financials and Supply Chain is in one physical instance and one physical deployment. So a lot more flexibility in how you can consume and deploy Fusion Applications.
What is Oracle’s commitment to Applications Unlimited?
19
What is Oracle’s commitment to Applications Unlimited?
Presenter
Presentation Notes
Transcript: A session like this is not complete unless I talk about our commitment.
Continued Investment
Presenter
Presentation Notes
Transcript: So walking out of here one of the things that I want to make sure that you leave with is we've been investing in PeopleSoft and JD Edwards and Hyperion and Siebel and all of the major product lines with new releases for the last five years. We will continue to do that, we will continue to enhance and bring these product lines forward, and just our commitment to doing that hasn't wavered. We still have dedicated teams doing this and we will continue to invest.
Oracle Applications Strategic Approach
Oracle ApplicationsOracle Applications
Complete and Integrated Middleware Suite to Enable SOA
Oracle Fusion MiddlewareOracle Fusion Middleware
Presenter
Presentation Notes
Transcript: And not only will we invest in feature functions, we'll look to adopt some of the middleware technology where it makes sense. So you can start to standardize at least your IT platform where it makes sense now, and simplify the moving parts in your IT organization if it makes sense. So if you want to deploy Identity Management, or you want to deploy the SOA Suite for integrations, all of those are available and have integrations to our existing product lines out there.
What is the path to Fusion Applications?
What is the path to Fusion Applications?
Presenter
Presentation Notes
Transcript: So some opportunities -- or a BI application, I'll give you some examples in the next couple of slides, so continued investment. What's your path, and I have a few customer examples on Fusion after this.
Now that Fusion Applications are in the mix, what should be my next step ?Now that Fusion
Applications are in the mix, what should be my
next step ?
Fusion 1.0?
Extended Support?Upgrade?
Early Adopter?
On Premise? On Demand?
Presenter
Presentation Notes
Transcript: The majority of customers or a large portion of customers are upgrade delays released. They see a lot of value, a lot of big investment there. They can hopefully do away and simplify some of the customizations that they might have had to put in older releases. So a large number of customers are upgrading. Author’s Original Notes: So what are the next steps?
Complete Choice Choose Your Next Steps
Presenter
Presentation Notes
Transcript: This is really the strategy and when I talk to customers what I outline for them. Number one, what the majority of customers are doing is continuing on their current path, continuing down the current path, continue to add value with their deployment of PeopleSoft or JD Edwards or Siebel. They're looking at sprinkling in some additional business capabilities in a co-existent fashion with Fusion. And how I look at that is you have your center of gravity, that is your ERP or CRM, and then you're going to look to add value. Maybe it's in the cloud, maybe it's sitting side by side with a Fusion Application that wasn't available or wasn't available in the deployment model that it's now available in. So we're giving you some flexibility to not rip and replace, to keep your center of gravity ERP system and add some value with a Fusion Application where it makes sense. And then over time if you see the value, you'll have a choice to replace larger business processes or upgrade to a larger business process in a Fusion equivalent application. So these are the kind of the three paths that we see customers deploying.
Recommended Actions Upgrade, Adopt, Extend
E-Business Suite 12.1
E-Business Suite 12.1
Oracle SOA Suite and AIA Oracle SOA
Suite and AIAOracle OBIEE Oracle OBIEE
JD Edwards E1 9.0
JD Edwards E1 9.0
Oracle ADF & WebCenter
Oracle ADF & WebCenter
Oracle Identity Mgmt
Oracle Identity Mgmt
Fusion AppsFusion AppsVCP 12.1Demantra 7.3
VCP 12.1Demantra 7.3
Oracle Content Management
Oracle Content Management
Oracle Enterprise Mgr
Oracle Enterprise Mgr
Supply Chain:- VCP- Demantra- Agile
Supply Chain:- VCP- Demantra- AgileJD Edwards
World A9.2JD Edwards World A9.2
OTM 6.1WMS 12.1OTM 6.1
WMS 12.1
PeopleSoft Enterprise 9.1
PeopleSoft Enterprise 9.1
Agile PLM 9.3Agile PLM 9.3
Agile PLM for Process 6
Agile PLM for Process 6
BI AppsBI Apps
CRM On Demand
CRM On Demand
Hyperion EPM
Hyperion EPM
GRCGRC
Industry AppsIndustry Apps
Siebel CRM 8.2Siebel
CRM 8.2
Presenter
Presentation Notes
Transcript: As they go down these paths this is the recommendation, it's really a reiteration of the last slide. Upgrade to the latest release, look at adopting some technology standards, and then extend with some co-existence opportunities where you could add value around the edges but you don't disturb the kind of center of gravity ERP or CRM system that you have in place. And so these are the kind of steps that you can look at. Author’s Original Notes: We recommend that customers consider the following: 1) Upgrade to the latest applications version in order to benefit from the functional and technology advances in every one of the new releases. Each of these releases delivers business value, and each one is certified with Fusion Middleware, the same platform on which Fusion Applications are built. 2) Adopt standards-based Fusion Middleware components if you plan to optimize your existing applications, whether it’s standardizing on an enterprise business intelligence platform; implementing a SOA-based approach to process integration; or adding a composite application. Your investment in any of these Fusion Middleware components is protected, since they are identical to what you get in Fusion Applications. In addition, you can start developing new IT skill-sets that will be critical in the future. 3) If you have a business challenge and identify a Fusion module that fits, then you can adopt a co-existence strategy without having to upgrade or modify your existing applications. Then, over time, you can choose to move to a Fusion product family.
Fusion Early Adopter: Eaton Industrial Manufacturing Customer
• Multiple custom order capture systems
• Legacy ERP (40+) – Oracle, SAP, MfgPRO, Baan
• Custom integration between capture and ERP systems
• Add Fusion Distributed Order Orchestration (DOO) & Global Order Promising (GOP)
• Pilot project focused on single plant, select set of products
• Add additional plants, products and business lines to DOO and GOP systems
• Consolidate capture systems
Solution Objectives:• Improve key business decisions through improved inventory management
and centralized views of global sources and shipping • Improve customer satisfaction through decreased lead times, more
accurate promise dates and fast, accurate order status updates• Increase employee effectiveness through streamlined, consistent order
processes
Presenter
Presentation Notes
Transcript: So in the last section I'm going to walk through a couple of the Fusion early adopter customers that we have and just give you a couple of examples. I've kind of tried to walk you through them as I went through the slides earlier on, but a couple of co-existence examples of early adopters that are deploying the applications today. So this one is obviously Eaton Corporation. They have a lot of moving parts in their supply chain. They've acquired a lot of companies, they have a lot of disparate manufacturing systems, some very old, some Baan, MAPICS, BPICS, and what they want to do is they want to centralize that order orchestration process. So this is a customer that's looking in a couple of divisions first to start to create that centralized order hub, and plug that into their multiple capture and multiple fulfillment systems, as a high-value co-existence opportunity with a product called Distributed Order Orchestration, so they could decrease lead times, have a more seamless process to manage these for their organization. Author’s Original Notes: Current: Multiple Custom Order Capture Systems Legacy ERP (40+) – Oracle, SAP, MfgPRO, Baan Custom Integration between capture and ERP systems Phase One Add Distributed Order Orchestration and Global Order Promising Pilot project focused on single plant, select set of products Future Phases Add additional plants, products and business lines to Distributed Order Orchestration and Global Order Promising infrastructure Consolidate Capture Systems
Fusion Early Adopter: Principal Financial Group Financial Services Customer
• PSFT HCM 8.9• PSFT FMS 8.8• Custom Compensation
Solution• Niche Contracts,
Sourcing, Spend Analysis & Supplier Master
• Upgrade to PSFT FMS 9.1
• Add Fusion Talent Management and Compensation Management
• Replace existing solution with Fusion Procurement
• Upgrade PSFT FMS to Fusion Financials
• Upgrade PSFT HCM to Fusion HCM
Solution Objectives:• Deliver globally scalable compensation solution• Improve financial control• Achieve single source of supplier information for statutory compliance• Reduce TCO by modernizing and standardizing applications
Presenter
Presentation Notes
Transcript: The next one is a financial services organization, Principal Financial Group. They are looking at a couple of modules. One of them, they have a custom compensation module so they do a compensation round semi-annually, they want to retire that custom compensation so they're going to look at Fusion compensation. They also have that sourcing, spend issue that I identified earlier, so they're going to look to take our procurement products and deploy those. And they're going to connect -- as well as talent management, and connect that to PeopleSoft 9.1 and replace their existing system with Fusion Procurement. And then over time, Phase Two, maybe three, four, five years from now they'll upgrade to a broader Fusion footprint on Financials and HCM. So kind of a phased approach to up-taking Fusion Applications. Author’s Original Notes: Current Pillar deployment of PeopleSoft Financials and HCM. Integration with custom applications and niche providers. Phase I Take advantage of significant business and architecture benefits of PeopleSoft Financials 9.1 Implement Fusion Talent Management and Compensation Management and leverage delivered integration to PeopleSoft HCM 8.9 Replace niche providers of Procurement services with Fusion Procurement including Supplier Management, Spend Analysis, Sourcing and Contract Management Phase II Upgrade PeopleSoft Financials to Fusion Financials Upgrade PeopleSoft HCM to Fusion HCM
Fusion Early Adopter: Siemens PL Software High Tech Customer
• SalesForce CRM• CRM On Demand• EBS ERP, SCM,
HCM 11.5.10
• Proof of Concept to implement Fusion CRM On Demand
• Continue deployment of CRM On Demand
• Upgrade CRM On Demand to Fusion CRM across other Siemens businesses based on a successful PoC
Solution Objectives:• Standardize Siemens on Oracle CRM On Demand across Marketing and Sales• Improve customer data quality and achieve 360° view of customer across Siemens PL• Create global pipeline system for marketing, sales planning and forecasting• Increase user acceptance with state-of-the art CRM system using Outlook
planned analysis
Presenter
Presentation Notes
Transcript: The next one is CRM, another great example, this is more of a standalone, this is Siemens. They're looking to replace a lot of custom CRM systems with an in the cloud extensible Java-based platform for CRM.
Fusion Early Adopter: Public Sector Customer
Current
• 140+ custom legacy applications to support PPM and Financials
• PSFT HCM 9.1• PSFT PRC 9.1
Future Phases
• Continue legacy replacement with Fusion Financials Applications
• Evaluate adoption of Fusion CRM
• Fusion HCM
Phase One
• Begin phased replacement of custom legacy with Fusion PPM, Financials & GRC
• Upgrade and integrate Primavera P6 with Fusion PPM
Solution Objectives:• Create next generation IT and project portfolio management platform • Improve decision making & project prioritization• Increase Project Manager productivity and project execution efficiency• Reduce complexity of compliance and improve financial controls• Integrate risk management into core PPM and compliance processes• Drive role-based collaborative business processes and reduce manual effort
Presenter
Presentation Notes
Transcript: That's Release 1 and then they'll expand beyond that, so another great example. And then we have a tremendous public sector customer that is actually looking at projects. If you're in this type of public sector organization, projects is the center of what they do, everything's a project and relates to a project. So they're looking at Project Portfolio Management as the application they're going to deploy. They'll have Financials under the covers, and they need some additional risk management capabilities on their projects. They deal with like nuclear plants and energy-type things, so they need some risk management activities to help mitigate the risk that they have. So they're going to look at GRC, Project Portfolio Management and Financials as a early adopter customer, just as one example of kind of Phase One that they've already started to work on right now. And they're going to integrate this to our P6 Primavera product which is really robust at scheduling employees on particular projects, so it'll be a very nice solution for them. Author’s Original Notes: Current: Recent upgrades to 9.1 Psoft HCM and PRC Phase One: PPM is the core of the first phase in concert with Fin and GRC (manager and intelligence) . Co-existence with GBU Primavera P6 latest release; with packaged integration thru Fusion Project Integration Gateway for true enterprise project portfolio management. Future: Continue to reduce dependence on custom legacy. Current thought to add in CRM, then migrate Psoft HCM to Fusion. Comments below are taken from the CTO’s email to as background: What I have positioned is a multi-year roadmap and investment (you don’t need to state the timeframe) moving to Oracle Fusion Applications, assuming everything works as planned with these. This also includes us looking at Fusion Middleware as our overarching enterprise integration backbone middleware. As you know, GRC isn’t technically part of the EAP Program; but will be in parallel with Phase one due to close ties to PPM processes for project risk. We are looking at integrating Risk Management into our core processes (e.g. project business processes). The productivity certainly benefits project managers, but also other people involved with project related work. We will evaluate both CRM and HCM applications for future adoption (CRM likely first) and is targeted on our roadmap around FY13 with HCM following that. Our upgrade path for PeopleSoft HCM 9.1 will be to Fusion HCM (version TBD) around FY14.
100% Open Standards
Key Takeaways
Embedded Business Intelligence
Web 2.0 Collaboration
On Premise and Cloud
Presenter
Presentation Notes
Transcript: So these are the key takeaways on Fusion Applications. One, 100% standards-based, and I'm talking about this from a business perspective. From a business perspective it's easier to manage, upgrade, support over time, and the skill sets that you need to manage this are standard. It has embedded throughout Business Intelligence and Collaboration. So you've seen that on some of the demos, you'll see that if you go to the demo floor, key components. And it's available on premise, in the cloud or some combination of the two.
Fusion Application Sessions at Open World
* Repeat session
Presenter
Presentation Notes
Transcript: All of these sessions, I'm just showing you all the sessions you missed. There's a few more coming up on Thursday after this session, so this is the first one. We have a technical architecture overview starting at 10:30, which is great. So if you're super interested and you want to get the next level of technical detail, there's a session. There's a DNA session that is fantastic, Amy up here in the front row is going to be leading that session. And then there are some drill downs on Financials and Human Capital Management. So first I think you for coming and taking the time after the party last night, for coming here, so I really appreciate that. Hopefully, you got those four questions at the beginning answered, you understand where Fusion fits in, understand how it co-exists with your current deployments of applications within your organization, and I thank you for coming.