Sunday, March 31, 2013

Microsoft Project


            Today my boss came to me with the question, “Would it be beneficial for our company to adopt Microsoft Project?” At first, going on what I had heard from others about the program, I believed that this program could add much value to our organization and I began to research the capabilities of the program. As it turned out Project had many capabilities that were beneficial to our company and had the potential to improve our budgets and timeline in the long run.

 
            My company, DemetriusBerkower, is an accounting firm currently using a Thomson and Reuters program known as CS Engagement. Users are assigned to work papers within various engagements to which the managers wish the users to complete. New documents can either be created within the system or uploaded from the user’s desktop and placed within the engagement. When users have completed work papers they can sign off on them within the program to show they are awaiting managerial review. Unfortunately this program does not necessarily give someone a good idea of the total project progress and gives no help when it comes to budgeting. This is where Microsoft Project becomes applicable.


            Microsoft Project is extremely helpful when it comes to planning as well as keeping track of overall progress. When it comes to the planning meetings, which we have before the start of any project, Microsoft Project can be used to map out the completion of the project from start to finish, determine the most critical aspects of the project, as well as creating a budget and timeline for completion. The budget and timeline can then be tracked throughout the duration of the project to ensure the project is being completed within the budget and within the projected time frame. With Microsoft Project, managers will be able to keep a closer eye on their spending and progress and make adjustments in the schedule when they feel necessary.


            Having done some analysis I realized our company must continue to use the CS Engagement software and unfortunately Microsoft Project could not become a replacement. On the other hand if we were to supplement CS Engagement with Microsoft Project there may be some benefits to be obtained. After examining the costs I found that it would be $58 per user per month which translates to $696 per user per year. Our company has approximately 30 employees which would bring our total costs to $20,880 a year. This amount seemed quite steep and would not bring in enough benefit to cover the program’s total cost. I thought about the situation and realized we have four secretaries that would not need to use the program and if we cut those users we would save $2,784 a year bringing our total cost to $18,096 which still seemed a bit high. Upon closer examination I recognized that many of the aspects of project are not necessary for regular staff works and really only need to be used by managers and partners. There are eleven total partners and managers within our company which if we only purchased users for those eleven would bring our total cost to $7,656 a year. This number seemed much more reasonable and an amount that could be recovered by the ability to keep our budgets down as well as stick to a predetermined timeline. Having fully examined the costs and benefits of Microsoft Project I have determined in my opinion it would be beneficial to adapt Microsoft Project within our company for managers and partners only.

Tuesday, March 12, 2013

Bombardier


This weeks article was able to show how through proper planning, hard work, and a little bit of luck a large scale Enterprise Recourse Planning (ERP) implementation can be completed successfully. Such a large scale operation comes with extremely high risk due to the high costs, resources, and amount of hours that will be spent on training and learning a new system. To make matters even worse it is almost impossible predict the exact benefits of the new system. It is important when implementing such a large system to be able to measure the effects of the process and to be able to administer ERP best practices.


When Bombardier implemented their ERP system they used their own best practiced model which in the end was found to be successful. For other companies looking to make a large implementation there is a world standard for best implementation practices that range from executives endorsing the project to the amount of communication that should be made to ensure success. If I were to go about implementing an ERP system as Bombardier has, I would use the world standard for best implementation. Due to the high risk of such a project the goal should be to minimize your risk as much as possible. By adopting the world standard your company is taking the knowledge of many executives who have attempted to implement a large system such as that of Bombardier. They have been able to tweak these standards based on practices that worked and others that seemed less successful. Unfortunately every business is different, and just because something works for one business does not necessarily mean it will work for another. Even with that fact, I still believe these standards would give my company the best overall odds of succeeding with this implementation.  


If I were a consultant in this situation and I was presenting the case I would focus on risk. So many of these projects end up as failures and result in the loss of millions of dollars that I would try and convince Bombardier to implement the preexisting standards to reduce risk as much as possible. In the case of Bombardier they have had success in the past with their own strategy which is a strong argument but as I mentioned earlier every project is different. In this situation it would be best to attempt the implementation through the world standard best practice. A great example for a system that failed would be Montclair. I am not certain whether or not they used the world standard for best practice but $20 Million later there is still no system. Perhaps had they used the standard best practices the result could have been different. If this example did not sell Bombardier on the idea, I would make it clear how many hours would be spent on planning hours alone. These are precious hours that could be put toward the implementation of the project as opposed to the planning alone.


Bombardier Reflection


I was happy to hear during the Bombardier presentation that the consultants went with the twelve best practice’s as opposed to making their own or adjusting the twelve. The consultants did a strong analysis of Bombardier’s first successful implementation and based on the notes the consultants gave, I believe that Bombardier will be able to increase the effectiveness of another implementation to 96% - 97% effectiveness. It was great to see the consultants truly consult in this situation. At no point did I feel as if I was being sold a product but instead truly being consulted toward a final thought.

 
After sitting though the Bombardier consultation I would agree with my original thoughts of staying with the twelve best practice steps. The way the consultants graded the C-level on each aspect of the practices was an effective way to present this case. The consultants focused on areas they truly believed would bring Bombardier from 93% productivity to a 96%. Had I been one of the consultants in this situation I would have been focused a little more on the importance of all twelve standards and how, when properly used, will produce the most effective implementation.

Tuesday, March 5, 2013

Accenture


I enjoyed reading the Accenture case this week and learning about how this company was able to break off from a very successful accounting firm and form a successful consulting company. The most important part of Accenture’s success had to do with the way they implemented their IT strategy. Instead of working with many companies Accenture was able to consolidate all of their IT needs into one company (Microsoft) which made it easy to have all their applications talk with each other. Accenture also made the decision to run its IT department as if it was its own business, and with good decision making and outsourcing they were able to cut costs by millions. Having implemented this successful strategy Accenture now had another difficult decision of whether or not to implement COBIT 5.

COBIT 5 is a framework created to try and help managers manage the gaps between control requirements, technical issues, and business risks. The goal is to create generally accepted information technology control objectives for day-to-day use by business managers and IT professionals.  COBIT 5 has both positives and negatives when it comes to implementation by Accenture. On the negative side, Accenture has an extremely successful IT department that is run like a business based on it’s own set of principles. By adopting COBIT 5 they may need to change some of the very same principles that made their department as successful as it has been. On the positive side COBIT 5 is constantly updated with the latest laws and regulation to ensure that Accenture will not be doing anything illegal that could lead to litigation of millions.

If I were the consultants for this case I would recommend Accenture adopt COBIT 5. With COBIT 5 they will be up to date with the latest rules and regulations along with being able to operate within any country that has adopted this standard. With COBIT 5 Accenture’s technology will have an even easier time communicating with each other due to the fact that they are following a common set of standards.  This would be my argument for the executive board to take the risk of investing in COBIT 5. If this were to not completely convince them I would once again focus on the importance of their IT division being centralized. I would make the point how becoming centralized worked so well for the company in their first IT decision and how once again this could improve their IT business structure. Accenture has thousands of employees that need to be able to communicate with each other all over the world and if they are all using the COBIT standard communication will become much smoother.

Reflection


The consultants for Accenture really raised the bar this week when it came to their presentation. Their slides were very well done and they were able to show a strong understanding of the industry and the dilemma Accenture is facing. The consultants provided useful insight on both sides of the argument, to implement or not. I really felt that this group consulted as opposed to try to sell a product.  Having sat through this consultation I would still go with my original decision to implement COBIT5. With Accenture being an international company and communication being such an important part of their success I believe the investment in COBIT5 will make be worth the $50 million to implement. COBIT5 will allow all employees to work with the same rules and standards allowing them to communicate much easier than their current situation. All companies must take risks to operate and COBIT5 is a risk I believe Accenture should take.

Sunday, March 3, 2013

Ubuntu

Once again I have been given the task of researching a possible technology change for our company. This time my boss has asked me to research the possible benefits of the operating system Ubuntu. Having now used Ubuntu and learned many of the pros and cons of the operating system I have come to the conclusion that this system is not for our company Demetrius Berkower.

Ubuntu is a free, open source operating system made by the company Canonical. The largest attraction of this software is that it is completely free of charge and is immune to a majority virus's. Most virus's that individuals and companies get will not affect Ubuntu because they are designed for Windows users. Being that we are Windows users this is a pro for Ubuntu do to our exposure to many of these virus. If one or more of our computers becomes affected it could result in hundreds of dollars in IT fees or even render one of our computers unusable. While running Ubuntu this is one problem that we will no longer need to fear.

The main reason I do not believe we should convert to Ubuntu is the fact that many of the programs that we use run on windows and do not work on Ubuntu. The main programs we use everyday are Thompson and Reuters CS Engagement and Go System Tax. These are the top of the line programs in the accounting industry and unfortunately are not compatible with Ubuntu. Along with that, I research other accounting and tax software and non of them are compatible with Ubuntu operating system. To run an accounting and tax software on Ubuntu it would need to be customized specifically for this operating system which would most likely cost our company hundreds of thousands of dollars.

With our company's business focusing primarily on those two programs to function it would be impractical to make the switch to Ubuntu, even with it being free to switch. We have been functioning successfully for many years now using windows and any new computers we purchase come pre-installed with Windows operating system. Until many of the accounting programs begin to adapt to Ubuntu it would be nonsensical to convert to Ubuntu for our operating system.