Upgrading Aging Oracle Applications and Software 2

How to upgrade your aging Oracle Applications and Software infrastructure

Many Federal agencies who invested in implementation of Oracle E-Business Suite and its supporting infrastructure are now grappling with questions about how to upgrade and take advantage of new functionality and keep the support cost in check. They may want to consider using a methodology called “Upgrade On-Line.”

Most agencies with customized application processes, reports, and workflows, have concerns that fall under one of the following categories.

  • Is this upgrade going to be a re-implementation that will cost me additional time, effort, and money?
  • Do I need to maintain two environments during the upgrade process? How will I pay for the additional cost?
  • How will I train my workforce in new processes and modules? How will I pay for it?
  • If I cannot upgrade using my existing implementation, how do I migrate my data over and how will I pay for it?
  • How do I avoid yet another ERP nightmare?

I am sure there are many more questions and worries, but there is a solution for government agencies: Use the Oracle E-Business Suite Upgrade On-Line.

Oracle E-Business Suite Upgrade On-Line is a very simple offering that enables agencies to take the risk out of upgrades and eliminate the risk associated with the project.

CSC has recently developed the Oracle Development and Test as a service offering targeted to Federal agencies. CSC takes the existing environment from the customer and hosts it in an FISMA certified data center. CSC performs the analysis of the environment using CSC’s proprietary tool. It will provide quick assessment of the effort required and if the Agency wants to move forward, CSC will perform the upgrade and manage all the different environments to support the upgrade development life-cycle.

When the application is tested and ready for production deployment, CSC will deploy it in the customer’s datacenter. If the customer wants to use a Cloud licensing model (pay per use), CSC will convert the licenses into a cloud model. From that point on, the customer will not have to worry about future upgrades.

How this is different from Salesforce.com or other Cloud providers?

The biggest difference is customer choice.

Customers can decide to take their applications back in-house when they want it—there is no lock-down.

Using Cloud services does not translate to vendor lock-down.


  1. Manish,
    I’m curious how many upgrade environments are typically used in the “upgrade development life-cycle”? Also, who does the testing? CSC or the client or both? Who writes the test scripts? Got a couple clients getting ready to upgrade so I was just curious. Thanks.

    • There is no right answer to the how many environments question. It really depends on your Configuration Management processes and Development lifecycle processes. Typically you have patching environment (as with every upgrade, you will need patches), Development / Unit testing Environment, Integration Test Environment, User Acceptance Environment, Pre-Production Environment and Production Environment. Some of these environments can also be combined based on size of your user base, modules involved, functionality deployed, velocity of changes to your production environment while upgrade is underway etc. There are many more factors to consider.

      I recommend writing test scripts and testing should be collaborative effort. Typically CSC will bring industry expertise and technical expertise and client has there specific business/environment knowledge. Where I have seen most success when there is joint effort. The client ultimately has the responsibility to ensure all the test scenarios are covered and sign-off on expected results. I also want to stress that test scenarios and expected results should be defined during or before the development/unit testing phase. This will minimize that “oops” moment for client and CSC.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s