Enterprise Information Architecture Frame work should cover what needs to be considered for virtualisation (like server virtualisation, network, storage, application), why do we need to virtualise (purpose and benefits), if we decide then when do we do it (timelines, phased approach) and how do we go about (strategy, plan, challenges, cost).
Integration: When we virtualise, it is important to ensure that the integration with non-virtualised IT systems and applications is seamless so the business is not disturbed.
Performance and Speed: Speed of applications must be tested prior to Go Live. Comparisons should be made of what the performance was pre-virtualisation and post-virtualisation – simulated environment can enable monitoring and measuring in real-time for continual improvement. Also it should be determined what the impact will be on applications which may not support virtualisation. Possibilities should be explored on how that application can work in virtualised environment.
Security: Security policies might have been framed and deployed for non-virtualised environment. How will the same be applied and acted in virtualised environment? We have to put in controls to ensure compliance to monitor and measure the virtualised environment.
Skill Sets: People managing both environments must be trained and have required skills sets to manage and support both environments. This is an important aspect, if not addressed well ahead, can be an impeding factor for change.
Applications: Applications, in-house or packaged applications like ERP, must be tested thoroughly in virtual environment for performance and continual working without any impact to business operations.
Cost: Cost of License, Hardware and deployment must be evaluated for both - one time and recurring costs, to ensure the savings are identified upfront and value drivers are communicated.


)
)
)
)
)
)
)
)
