Boeing Case Study

Boeing case study

Boeing Australia Ltd. Case

April 14, 2014

Executive Summary

Boeing Austrlia Ltd. is facing limitations with the current legacy ERP and procurement systems it is using. Russell Menere as the National Procurement Manager needs to evaluate the current system in regards to the limitations and capabilities to understand potential cost savings as well as cycle time reductions.

BAL is not large enough to pursue the full ERP systems that would interface with supplier systems and allow more streamlined processes. A system that would allow a fully integrated system with suppliers would push costs onto suppliers through integration and added time on their side.

A balance between the existing legacy system and a full ERP system should be investigated to benefit suppliers, customers, and BAL.

Table of Contents

Executive Summary 1

Issues identification 4

Environment and root cause analysis 4

Alternatives and/or options 4

Recommendation and implementation 6

Monitor and control 6

Conclusion 7

Issues identification

1. BAL’s legacy system does not fully integrate with suppliers and all inputs causing potential double data entry errors.

2. Purchasing a full ERP system would require more capital than the budget requires, but the functionality of the existing system will not allow for scalable growth.

3. The current improvements to processes and allowing credit card purchases allow temporary improvements but may not handle growth and continued improvement.

Environment and root cause analysis

BAL is required to offer a multitude of services to their customers depending on needs. This includes management and maintenance of sites on behalf of clients, modification and upgrade projects, early warning and control systems for 737-700 planes, ground-based air defense, command, control, communication systems, and internal asset purchases. These military based clients require BAL to enter data into their systems to enable...