Shared Learning Library
Welcome to PEMAC's Shared Learning Library, a growing body of community created knowledge, built up and maintained by the PEMAC member community. Explore a range of articles, presentations and webcasts covering a wide range of maintenance, reliability and asset management subject areas. You can even find presentations from past MainTrain conferences and PEMAC Lunch & Learn webcasts.
To easily find what you are looking for the content of the Shared Learning Library can be filtered by both Maintenance Management and Asset Management subject areas using the options in the menu to the left of the screen.
Displaying 1 - 1 of 1
BoK Content Type:Article / NewsletterBoK Content Source:Practitioner ProducedOriginal date:Thursday, January 11, 2018Jeffboat is a company with a long history. Originally named the Howard Steamboat Company, Jeffboat is America’s largest inland ship builder and has been manufacturing ships for over 100 years. Jeffboat has built such famous ships as the Mississippi Queen, the General Jackson showboat and the Casino Aztar riverboat casino. Like most manufacturing firms, Jeffboat has an enormous amount of equipment stretched out over a shipyard that is over a mile in length that is needed to make its boats. Also like many old-line manufacturing firms, Jeffboat has both equipment and employees who have been there for several decades. Overall, because of the size of the shipyard and age of the equipment, Jeffboat’s maintenance was used to working in reactive mode. There was no CMMS software in place and equipment was put into numerous Excel spreadsheets. In addition, it was often hit or miss whether the right parts were in the stores room and finding the right equipment often took maintenance technicians a significant amount of time. There was no Scheduler/Planner and maintenance procedures were done informally and based on need at that particular moment.When implementing a maintenance management strategy, a critical component is the resistance to change. Whether it is the introduction of new software or a complete overhaul of the maintenance function, the process of change represents disruptive technology (Christenson, …). According to Christenson, most changes are really improvements on something old and the old paradigms can be used. However, there are changes that organizations need to make that disrupt the dominant paradigm, rather than sustaining it. These are disruptive technologies and make the old things less important or obsolete. The problem with these disruptive changes is that people are still applying the old paradigms to the new realities. They are trying, in a sense, to understand the car as nothing more than a carriage without horses.