Playbook: Oracle EBS AMS transition and governance
A general method for moving Oracle EBS support to an AMS provider and running it through regular reviews and KPIs.
- Collect the module list, customisation and integration inventories, patch history, runbooks and open tickets.
- Hold business and IT walkthroughs, with focus on period close and key interfaces.
- Review environments, cloning, the adop history and outstanding CPUs.
- Shadow: the new team watches live ticket handling.
- Reverse shadow: the new team handles tickets under supervision.
- Sign off readiness against agreed exit criteria.
- Stabilise with relaxed service levels through the first close and CPU cycle.
- Apply full service levels and review backlog age, repeat incidents and CPU status monthly.
- Hold quarterly sponsor reviews to reset priorities and scope.