Buckeye Power Company Case Study

3068 Words 13 Pages
Register to read the introduction… In the beginning there were only five members and it took the company a year to get the first electric pole up and ready for service. They spent the next decade developing their memberships, trustees and employees and learn how to function as an organization. After WWII the company really started to develop by hiring more employees, purchasing trucks and installing new services.
In the 1960’s is really were you see the most growth in the company. In that year the doubled there service territory by purchasing another company, and in 1962 they again doubled their service territory thru the acquisition of another company. Today we are governed by a board of directors that are in charge of making policies, procedures, decisions, and choosing a president to see that these things are done. There are a total of two hundred and fifty people that are divided into five different offices that server over 110,000 members that span over 24 counties in Ohio that puts the Co-Op at one of the largest in the
…show more content…
(Weiss, 2010) 1. Is your app a web app? It sounds basic, but before you migrate to the web, you need to make sure that your application is a web application. Today, there are simple tools that can easily convert it, but make sure to convert it. 2. Is your app native .NET/Java? Before you start to migrate your app to the cloud, understand what it is you are transferring and the technological aspects of it. This is important because you need to know which clouds support your stack of technologies. 3. Do you use any interop to other technologies? Prepare yourself. If you do use any interop, it is important to make sure that those technologies are also supported by the cloud you are targeting 4. What database type do you use? When you are planning to migrate, make sure that the target cloud can support the database you are using. If not, can you change the database? Alternatively, you can consider running the application on the cloud and connect to an on-premise database; some DB vendors already support securing these

Related Documents