Monday, March 25, 2013

Bombardier Case


Case:  Bombardier -- Succesfully Navigating the Skies of a Large Scale ERP
Implementation
 
Problem/Issue Statement

In the early 2000’s Bombardier committed to replacing its legacy systems with a state-of-the-art integrated system that would allow efficiency and effectiveness throughout its operations.  Senior management felt that given the competitiveness in the aerospace market, moving to an ERP system was necessary. 

However, these large systems efforts are complex and frequently result in lower than expected performance.  Bombardier went through multiple rounds of ERP implementations; with the Company’s first attempt – in 2000 – being scrapped mid-project after $130MM had been spent.   After hiring a consulting team, establishing a new “One Company” vision throughout Bombardier, getting senior leadership on board and creating a project plan, Bombardier was ready in late 2001 to move forward with their Bombardier Manufacturing Information System (BMIS) – a new integrated manufacturing system that would be implemented through SAP.  All of these practices proved valuable as the second round of implementation was much more successful.  Bombardier successfully implemented BMIS at its Mirabel plant and followed suit with implementation at Saint-Laurent.

Seeing the improvement and success with these plants, Bombardier would like to further analyze their implementation efforts and look at a Best Practices approach to ERP implementation to further enhance their project.  Senior management would like to evaluate their situation and see how a Best Practices approach could assist with an even more successful next round of implementation.

Situation Assessment

The first step in a Best Practice approach to ERP implementation would be to define clear goals and objectives.  An ERP system will affect many departments and business processes throughout any organization. Making sure goals are clearly defined as well as what objectives and deliverables each group within Bombardier is looking to achieve will help better ensure the system is capable of effectively achieving the overall goals. Having goals and objectives goes along with having strong management support. 

Another best practice is to ensure that you are choosing the right software.  To gain full value from an ERP system, Bombardier must match the software to the organization’s information needs, processes, functional requirements, and workflows. After much consultation, Bombardier chose to use SAP and implement the BMIS system for manufacturing facilities as management felt it was the best option for the Company.

Bombardier should also prepare for business transformation.  ERP is fundamentally about transforming information flows through an organization.  By definition, therefore, both roles and processes are likely to change during the ERP implementation. Bombardier will need to devote time and resources to change management – ensuring that a clear process is defined and implemented to help workers through the process of change from the old system to the new.

Training and support resources are also essential.  A new ERP system will need highly qualified consultants experienced at implementation and training. The vendor chosen should have consultants readily available to train and support users on the daily use of the system and any problems and questions that could arise. A training program should also be established for new hires.

The next step in ERP best practices is to have a clear implementation plan and timeline.  A crucial part of implementing an ERP system is deciding the exact steps of how it will be done and when. Management at Bombardier will need to make sure all affected departments are consulted as to when the best time is to implement the new system. (For example, choosing to implement an accounting ERP system at year-end accounting closing would be a bad decision.) Making the cut over to a new system in the most crucial periods of business is not a good decision.

Bombardier will also need to allocate the necessary resources.  Allocating the necessary resources, across financial, managerial and end to end support for training and change management is necessary in order for a successful implementation of an ERP system.

Recommendation

Looking at the differences between Bombardier’s implementation at both the Mirabel and Saint-Laurent plants, while both were successful, the process went smoother at Saint-Laurent.  Bombardier had more management support, clearer goals, and better training when beginning the implementation at Saint-Laurent.   The changes made during the process made the implementation at Saint-Laurent go smoother.  Below I will outline some of the missteps at Mirabel that were corrected at Saint Laurent and what Bombardier could do to improve even further.

While the VP of Operations and Project Sponsor continued to show support for the project, the plant manager at Mirabel did not agree with the scope of the project and some internal managers and users felt that the system was being forced upon them.  They were not as eager to implement – attendance at meetings was being delegated downward and IT was complaining that users were not providing sufficient information for training materials.  When examining the Saint-Laurent plant, management was much more involved.  The plant managers felt that the project was theirs, not just IT’s, and took control early on in the process.  This aided with getting all other employees on board.  The vision for the project was clearer when it came time for implementation at Saint-Laurent.  Employees had presentations that preceded training which enabled users to have a better understanding of the change leadership that would be occurring.  Employees felt that there was a need for change and were all on board.  These visual aids/presentations should be continued for all further facilities.  It was good for employees to see how Bombardier was doing versus its competitors and to see that the new ERP system will aid in the Company’s vision.

Training was another key issue.  The Mirabel plant felt that they had insufficient training too far in advance of implementation.  When it came time for implementation they could not remember everything they had learned during training and felt “behind the eight ball” when the BMIS system was launched.  Training materials were re-vamped and the users at the Saint-Laurent plant were more satisfied.  Both facilities however felt that support left too soon after implementation.  Management at the Mirabel plant noted that issues may not arise within the first few weeks of implementation, but rather several weeks or even months later (at this point there was no support staff on the premises – other than power users).  At Saint-Laurent there were similar issues, however the issues that came up after the “Go Live” were more specific in nature and not necessarily general.  These required more in-depth and detailed follow-ups without necessary professionals on site.  For the next round of implementation, Bombardier should make sure that there are at least 1 or 2 people that stay on for an extended length of time at facilities to provide needed support.  Even if it is done on a part time basis, users of the new system need to have the proper training and support available to them in order for the implementation to be truly successful.

Also, training is so important for any new system; as previously mentioned some changes were made between the implementations at Mirabel and Saint-Laurent, these should be carried forward to the next stage of facilities for implementation with some further enhancements.  Training should be closer to implementation with a more generalized theme and then have follow-up, more detailed training once the system is up and running and users have a chance to see it with their own eyes and touch it with their own hands.  Going to training on something that you’ve never seen or used in some respects can be a waste of time.  People may not know the right questions to ask until they can “play” with it.

Bombardier now has clear goals and objectives in place, the most important steps are to continue disseminating the goals and objectives throughout all of the Company’s facilities so that they are aware early on of the changes that are going to be made.  Employee buy in is important for any system, if employees are not going to be willing to use the system it is bound to fail.  Everyone wants their life to be a little easier, showing how the system can and will do that is important.

Presentation

In order to present this case, the consultants should go through some of the Best Practice frameworks that exist and give a detailed approach that Bombardier could use.  It would be helpful to see the successes and missteps along the journey in order to see where the Company did a good job and where improvements could be made.

Monday, March 4, 2013

Is Ubuntu the right choice?

Sir

In our discussion of the Ubuntu operating system, I would like to refer back to our discussion of Google Drive. While it is important to save the company money, and Ubuntu is “free,” saving money may come at a higher cost through a need for a new IT infrastructure.

Although Ubuntu on the surface is free (i.e. no license fees), there is an annual service cost for professional use which I will touch on shortly.  The first important thing to note is that we are leasing our laptops currently, and they come pre-installed with the latest version of Windows.  Laptops are typically refreshed every three years and each computer has the most recent Windows operating system already pre-loaded.  The cost for Windows is therefore irrelevant as it is not something that we are technically paying a separate fee for.

Moving away from the discussion of the operating system itself, Ubuntu runs LibreOffice as an alternative to the Microsoft Office Suite of products.  Using the cost analysis of Microsoft from my earlier Google Drive report, the cost of MS Office 2010 professional for our department is roughly $262k ($349*750 employees).  The last time we upgraded the Microsoft suite was 3 years ago, assuming we can annualize the $262k over 3 years – it comes to approximately $87k/year for our department.   This cost savings would be offset by the cost of Ubuntu professional support services which run $165 per laptop or roughly $124k/year (750 employees * $165).  This would be a net increase in costs of $37k annually.

On top of the $37k annual increase in costs, we should definitely factor in downtime for all associates as they attempt to navigate through and find what they are looking for in a new environment.  While I found LibreOffice (which includes word processing, spreadsheet and presentation capabilities) fairly easy to navigate after just a short period of time, there are still many features that would take time before anyone would be at the same knowledge base as they are with Microsoft.   It could take several months before employees are at efficient usage levels of these products.

Going back to my earlier statement about a new infrastructure; in order to implement Ubuntu in exchange for Windows and MS Office, we would need to hire consultants to work with us for integration with our existing systems and programs.  In particular our trading systems and accounting systems to make sure everything can and will run smoothly.  While I am sure there is a way for everything to work well together, it would require a significant upfront cost.  My suggestion would be to work with Canonical as they are the leader of the Ubuntu project and in my opinion have the most knowledge of the system.  We would need to get an official estimate from Canonical (and other possible vendors), but this could run the Company approximately $1-5MM depending on the length of time and the necessary requirements and changes to our IT infrastructure.

To sum it up, while Ubuntu and Libre offer an alternative to our current technology, I do not feel that the costs would be warranted given our systems are running smoothly in our current environment.  Like Google Drive, Ubuntu seems free on the surface, but would take a significant amount of capital in order to implement.

Sunday, March 3, 2013

Zara reflection

As a follow-up to Tuesday night's presentation by the consulting team and our further discussion afterwards, I feel that an upgrade of Zara's DOS based system will definitely be something that we should implement in the future. However, I don't feel that the implementation is absolutely imminent. I do fear that we will lose the ability to have our terminals run on DOS in the future and as such we should begin with new upgraded terminals for any new stores going forward combined with a very slow implementation at existing stores. What we are doing is working and working well, the risk of a complete overhaul and related "down time" in the event of any errors in implementation would be too high.

Overall, my recommendation to the rest of the Board would be to start a slow change over beginning with any new store openings. This will be a good way for us to monitor the new system and really be able to compare and contrast the two operating environments.