What's Next for One World Users?

By now, you probably know that the Release of One World you're on – 8.9, 8.10, or 8.11 – will eventually be phased out to make room for "Fusion." There will be no “Release 9” of the One World product line.

That’s the bad news. The good news is that you have many options, including continuing to use the software that you’re already using.

If you do not foresee upgrading, ask yourself the following questions:

• Are there new business processes you want to implement but haven't yet?
• Does your current system have features or functionality you plan to implement, but haven’t?

If the answer to either of these questions is yes, it's best to investigate the issues and resolve any questions as soon as possible. If you don’t, you may learn about software problems (bugs) or missing functionality at a much less convenient time.

If the answer is no, it's still advisable to team up with a service provider to help you maintain the system, train new users, etc. until you are ready to upgrade.

Release 8.10 offers significant enhancements, and supports traditional client-server architecture. The latest Release (8.11) will get you the most functionality, a "pure internet" environment (no more client/server).

Users of Release 8.10 and earlier can upgrade to 8.11 or wait for 8.12* and upgrade in 2006. Oracle has promised a "direct upgrade" from Releases 8.11 and 8.12* to Fusion, which is the next generation of software (it will be taking the place of a Release 9.0 for One World).

Fusion, the software, is different from Oracle’s “Project Fusion,” which is Oracle’s next big step in applications technology. While Project Fusion will provide for more cost-effective integration, flexible business processes, and improved extensibility, “Fusion” is a series of applications that will come online based on Project Fusion’s information architecture.

Upgrading may be a big project (though not as big as an implementation). If you decide to upgrade, here are the Acuity Seven Upgrade Decision Steps you'll need to take:

1. Determine how long the current release will be supported by the vendor.
   1. What upgrade paths does the vendor provide?
   2. What are the costs (internal and external) of upgrading?
2. Define your upgrade targets.
   1. Which version do you want to be on, by when?
3. Assess the need for consulting support in planning and executing the transition.
   1. What kind of assistance do you need?
      • Technical (computer hardware and networking)
      • Applications (vendor software modules and what they do to support the business)
      • Business consulting (the evolution of processes within the business itself)
4. Perform an impact analysis
   1. How will the upgrade affect your business?
5. Retrofit necessary modifications
   1. Are you going to need to have any modifications that you made to prior Releases made to your new release? Or will your upgraded software have the functionality you need built-in, so retrofits won't be required?
6. Plan the change
   1. How are you going to test the system and put it into production?
   2. What can you do to minimize the impact and risks during the upgrade?
7. Determine requirements for new hardware or middleware?
   1. If so, which should be upgraded first? Hardware, software, or middleware?

You will have to select the answer that gives your business the highest ROI. Our deep experience with World software has been used by our clients to:

• Get more out of existing software and avoid upgrading.
• We've helped clients choose and implement upgrade paths.