Strategy of AIServices.com

Question: Discuss the strategy of AIServices.com. Answer: Introduction AIServices.com is a growing enterprise that has its corporate office in Sydney, Australia and is expanded in three other locations as Singapore, New Zealand and US. The company has yearly revenue of USD 130 million and is composed of 250 employees. The various services and solutions provided by the company include travel and tourism, ticket booking platform, job portal and access to health professional, teachers etc. Implementation Strategy The proposed solution and strategy that has been designed for AIServices.com includes IT strategy along with the cloud strategy. The cloud model that has been suggested for implementing cloud computing is Software as a Service (SaaS). There are various implementation strategies that are present to implement the solution to the enterprise. The strategies that were considered and analyzed were: Big Bang Implementation It is the implementation that happens at a single instance and at one go. All the users and existing systems move to a newer system altogether and at a specified date and time (Anya Ciecierski and Anya Ciecierski, 2010). Phased Rollout It is the strategy that takes place in a number of phases that is on a step by step basis. It generally takes longer time to get all the users moved to the new system. Parallel Adoption The existing as well as the new system runs on a simultaneous basis in this system and the users learn about the new system while working on the old one (WhatIs.com, 2016). Suggested Implementation Strategy Phased Rollout The business strategy that has been suggested over Big Bang and Parallel Adoption is Phased Rollout. The reasons for selecting the same have been described as listed below: Risk The solutions that implement the Big Bang strategy tend to have higher risks that the phased approach. It is because everything is implemented at once in the Big Bang approach which means that if a single thing goes wrong then the entire system fails. There is no scope left for rolling out or correcting a part of the system and continuing with the rest of it. Also, the complete end-to-end testing is rather difficult owing to the hugeness of the system. It leaves the errors go unnoticed and undetected before the final implementation takes place (The Manufacturer, 2016). Multiple Sites The business location that AIServices.com is expended in to is four and the complexity that is introduced in implementing the solution at once at all the location is massive. It is easier to implement the strategy one at a time and thus phased rollout is encouraged (It.toolbox.com, 2016). Impact on the organization The entire organization is impacted at once in the case of Big bang approach as the entire systems need to be moved to a newer one at one go. Whereas, in the case of a phased rollout, only the project or the team that is moving out is impacted, this does not hamper the working or the productivity of an organization as a whole. Future benefits of the Phased Rollout Strategy Low Risk Phased rollout does not have a single point of failure. It would benefit the enterprise as it can be effectively implemented and would also provide scope for adjustments. Steady Performance The staff would get more time to get trained by the time the entire system is moved to a newer solution. This would enable the members to perform productively and as per the requirements of the new solution. Milestone for Business It is always considered the best to move in a phased approach rather than moving all at once. Phased approach would allow the business to achieve all the milestones one by one (Turnkey Technologies and Turnkey Technologies, 2015). These are expected to be achieved by: Implementing the solution starting with US as it has the least number of employees that is 25. Once the positive results are received from that location, the solution would be implemented in the other three locations one by one. The solution would be applied on an industry wise basis as well starting with Travel and Tourism and expanded to the other services on a later stage in the lifecycle of the project. The risks and occurrences of such events that will take place during the implementation phase would be backed by a countermeasure for the same. Risk Mitigation Shared Access Multi-inhabitant design is a typical practice in distributed computing which implies that various clients get the power to share a typical arrangement of assets, for example, stockpiling, memory and equipment. The same element may bring about the danger to the private information with the common assets. Occurrences, for example, look into other inhabitant's memory space or IP location are extremely regular and lead to potential danger to the client information. (Grimes, 2016) Cost and time Moving the whole framework from existing practice to the cloud is difficult particularly when a framework is as expansive as AIServices.com. It is certain to include a considerable measure numerous expenses and will take generous measure of time to finish the whole procedure. Enactment and Regulation There will be a number of legislative policies and regulations that apply to the data and adherence to the same would be necessary (Business.qld.gov.au, 2016) Confirmation, approval and access control This is yet another issue that emerges and needs to be tacked effectively. For instance, if there is a decision on the use of encryption, then the confirmation of public, private and shared keys need to be made and communicated to every concerned person (Grimes, 2016) Accessibility Adaptation to internal failure and accessibility is something that each cloud supplier cases to give yet for the most part does not succeed in accomplishing the same. The data should be accessible on the cloud at all times for the clients and the instrument of giving the same must be chosen. Accessibility of data is another potential danger. Information Authority and Ownership There may be more than one party involved as the business is expanded to various locations and places. The final decision of ownership to each bit of data must be made. Cost Analysis In the phased rollout approach, the time that is taken for implementing the strategy to the entire business would be a little longer. The various costs that would be involved in the system would be: Cost of the new equipment Migration cost Implementation cost Cost of the temporary interface Cost of the network design Capacity Assessment There are a number of different teams and workforce that would be required in the successful implementation of the new business strategy. These would include the members belonging to the following departments: Interface design team Interface development team Network design team Support and maintenance team Development team Testing team Operation head and team Database management team References Anya Ciecierski, C. and Anya Ciecierski, C. (2010). Caseygrants.org. (2016). Grimes, R. (2016). The 5 cloud risks you have to stop ignoring. It.toolbox.com. (2016). Big Bang vs. Phased Rollout: Which ERP Implementation Strategy Is Best?. Tbs-sct.gc.ca. (2016). Organizational Project Management Capacity Assessment Tool. The Manufacturer. (2016). ERP Implementation Strategies: Big Bang vs. Phased.