Tektronix Case

Good Essays

As Tektronix decided to implement the new Oracle ERP system, the company chose to introduce it in phases, based around the specific functionality or a particular geographic region. Implementing in phases, or in waves as Tektronix called it, allowed the company to experience regular feedback on specific areas of implementation, allowing time to adjust processes and scheduling as needed. The phased approach enabled the company to achieve frequent victories, which kept team and employee morale high throughout the process and provided encouragement to the Board despite the high cost and long timeline of the overall implementation.
To ensure Tektronix's success, the ERP implementation was divided into five manageable sub-groups: (1) …show more content…

A full-scale approach requires less down-time in the system, which is crucial for smaller companies and companies who have a tighter time frame for implementation.
Because Tektronix previously had problems implementing IT projects, the company was mindful that replacing their legacy systems could be a risky undertaking. Further, it was well-known that wide-scale ERP implementation would be a very costly endeavor. Consequently, Tektronix managed the risks of its ERP implementation by having a coherent, guiding vision entailing: 1) separability of the businesses; 2) leveraging shared services; and 3) staying as "plain vanilla" as possible.
Deriving from this structure, with regard to separate businesses, each division demanded standardization and had an overall "Frankfurt is Orlando" mindset. However, it was recognized that each division was very different than the next and had varying distribution and selling methodologies. Hence, each division would have its own instance of the system to manage the customer fulfillment process, and a decentralized approach to implementation details (such as each division choosing its own partners). This minimized the risk of having the relative requirements of one organization driving the practices of another.
Leveraging shared

Get Access