Are you going to put a bunch of Fusion-esque things in the next E-Business, PeopleSoft and JD Edwards suites? Or is it just the few youve outlined today? There are a few key things: the reports, the Web registryidentifying all the Web services were going to have. First of all, we started publishing Web services more aggressively in all the current product lines to ease integration capabilities. So if people did use Fusion Middleware they could actually start building component applications ... using services that weve exposed from our existing applications. Were basically going to publish all the Web services were going to have as Fusion, so people can start designing their business processes, which they then will be able to move forward to Fusion applications and transactional systems when theyre delivered.Oracle unveils more of its plans for Siebel. Click here to read more.The other thing that we started talking is something called Fusion Analytics. So we started a project last year called BI Menuing, because one thing we found is the typical way people get access to their systems is basically they have a hierarchical menus tree and they say, OK, Im going to go do this now, and Im going to go do that now. And one of the things we realized is we built a set of tools called DBI, on the Oracle E-Business side starting a few years ago, and they became primary dashboards for a lot of our customers. Really what were trying to do is blend those concepts. What we want to deliver is a business intelligent menu approach that says, OK, you guys, heres your major dashboard, heres whats happening in your part of the world, and heres the major things you ought to start going and doing something about. Thats the way you actually get into doing your work on a day-to-day basis. Its kind of like the in box concept, but spread across the whole domain of the businessthis thing called BI menuing. PeopleSoft had some really cool technology to help you do that called EPM, which allowed you to be much more open, so if you had data sources that arent in the applications running, you can actually bring that in. It turns out Siebel has some really strong analytics as a part of that. But what we want to do is build essentially the way people are going to get access and get into Fusion applications, on top of the current versions of the products that theyre running. So this BI Menu, consistent with Fusion Analytics, would be the way they actually got in to go do their work in a PeopleSoft Enterprise application, or the E-Business Suite. But now the idea is youve changed the way people think about accessing their transaction systems. Its a much more intelligent, rich way to [think about] this is what I should do at my job. Youve changed the reporting outputs to allow them to define their business process, so now when they move to Fusion, what are they changing? Their underlying transactional systems. So yes, there will still be some changes for them, but youve changed the way people think about getting in to do their work, but the way you get information out of the system doesnt change, and the way you build your business process doesnt change. So youve made it a much more graceful on-ramp to moving to Fusion applications. By the time you get there, the hope is that as PeopleSoft customers move, they kind of go, Not that much change, because Ive got all this cool stuff the last couple of years, and Im starting to use it now. But youre talking about actually now changing the process of the way a person gets into their applications? The process doesnt change, but what will change is understanding where I should start instead. And what we are trying to do is give people information like our notification systems. Youve got an employee expense report, youve got a new hire process, but youll get really rich information about what you care about, and say thats the one I want to go to. Thats the idea. Its a pretty simple concept, but theres a lot of technology that we have now that makes it a lot easier for us to deliver. When do you plan on delivering the analytics capability? 2007. We talk about 2007 applications, and thats a key one. Our hope is well get it done this year, but were being a little conservative. Did you determine a user interface for Fusion? Basically in [E-Business Suite] 12 were going to go much more to a PeopleSoft look and feel because the user experience work that theyve done. They did a lot of work at PeopleSoft in terms of getting very good feedback [determining] what is easier on the eyespeople work very long hours, and what is easier on the eyes in terms of color scheme, font type, the general flow. So we actually learned a lot. When we did 12 we brought all those pieces in. Click here to read how Oracle defines the future of Fusion. Then we have a team thats really been driving out UI prototypes from two standpoints: Whats really productive for people to work in; and what is going to be easier for people to transition from, whether theyre Oracle or PeopleSoft. So that changed something were factoring in, trying to make sure that the new releases are as productive as possible, but also that they are very similar to what they had before. There is something called skinning, a technology called JavaServer Faces that basically segregates exactly how the thing looks, and the business logic underneath. So if you want to design something thats exactly like the way PeopleSoft or JD Edwards used to work, you can do that. So one of our obvious deliverables is when we deliver Fusion applications its like, Id like it to look like the E-Business Suite, or Id like it to look like JD Edwards, or Id like the look of PeopleSoft. It wont change every behavior, but basically that first impression is, This doesnt look that much different. And, by the way, there will be another one that says, We think this looks better, so if you push this button you tell us if you actually like it better. Next Page: Whats going on with Nexus?