Skip to main content

Hello All -

The company where I work will be upgrading from Apps 8 to Apps10 in a few months.  We are looking for best practices and approaches for the actual Go-Live weekend.  If you have gone through a major upgrade with IFS, we would like to hear about your go live experiences. 

Not quite sure how far we can discuss \ explain how ready you should be for a Go-Live, but the followings are some of mandatory steps \ tasks.

  • Cutover plan
  • Go & NoGo list
  • Support plan & frontiers
  • Post-Go-Live support
  • Go-Live team (technical \ functional \ management)
  • Performance team (pre and post Go-Live)

But, way before the Go-Live, the followings must have been met with more than at least 95% success rate.

  • Master data management (MDM) and cleansing
  • Change management
  • Low hanging fruits (small to medium open points)
  • Training and KBAs
  • Multiple ASTs
  • UAT, CST
  • Ramp up and Ramp down times (for data migrations, etc)
  • Code freeze before Go-Live, snapshots, backups, etc

As it’s an upgrade, you won’t face certain challenges like User-Training, KBAs, MDM cleansing, etc. as in an implementation project. However, be ready with a proper cutover plan where all the topics including specific date ranges, pre and post Go-Live tasks, migrations, integration testing, etc. 

Change Management is also a topic, even thought it’s an upgrade. Be ready for unexpected pressure from departments \ users about new IFS flows and functional changes. Proper workshops and training will solve this too.

In an upgrade, performance issues might be a surprise attack. Technical and performance team (with specific IFS and Oracle knowledge) should act smart there. 

Feed the front liners (Pre\Post Go-Live support team) with adequate IFS training which will come in handy.

Never done so, but, try to plan a Mock Go-Live, which will early-detect performance issues, etc.

All the best.

 


Reply