Transition Draft Plan

2 OBJECTIVES

The Transition plan is needed due to new structure organization and to cater requirement from existing customer and to continue the activity that is being carried by current resources. The transition plan is to cater for:

1. Transition from a project based organization to a Solutions and Services organization inclusive of transition from the previous organization structure (Establish and Operate) to the current TAS structure

2. Current outstanding activities with XX IP Core project and moving forward for setup of multi-technology solutions and services for multi customers

3 TRANSITION PLAN

The main agenda of the plan is to ensure that smooth undertaking of AES’ responsibilities, without compromising the deliverables of the IP Core xxxxx. The transition plan caters for resource and task planning up till end September 2011 that is when all IP Core extension activities is expected to be completed. However, if IP Core does continue in whatever form beyond September 20xx, a revision of this plan is required to streamline with any changes to the Organization’s priorities and objectives.

The following table lists the expected number of available resources and task deliverables for the corresponding months. Due to the circumstances of having minimal number to run the activities the following are recommended:

1. We do not run strictly by Unit function. This strategy is aimed at familiarizing the whole department with its end to end deliverables and after experiencing that, they would know how their unit fits in the overall scheme of things and they would immediately see gaps and take steps to resolve it. This also prepares the team for the eventual Solution architect role that will be formally introduced at a later stage

2. Provide