Asset Maintenance Management

Conference Communication 1999
Book review by Joel Levitt
February 13, 2001

This is an excellent book for serous students of maintenance management. I say serous because it takes something to get through the conversions between UK and US models and modes of communication.

 I would consider it a good addition to my library even given its limitations. It is an extremely complete view of the field. The editor did a good job of choosing topics. The individual writers seemed to know their respective fields. s.

 There are several very well thought out sections that show an all-inclusive view of maintenance not commonly used in the US. This was one of the most interesting points and a great example of how useful an expansion of vision can occur when one looks to a body of knowledge outside their normal channels (another countries’ body of maintenance management knowledge).

 One of the strengths and one of weaknesses was the incredible depth that they went into some topics and the 20,000’ high overview of other topics. In short, the book covers topics that are probably outside the scope of asset maintenance management. An example is the detail in the discussion around page 316 (and the figure on debris generation rates). This is something more appropriate for a treatise on predictive maintenance. Asset management is usually thought of as a higher up the food chain kind of discussion.

 In the areas I looked at in depth there was only one mistake in fact. The mistake concerns the technique of picking a maintenance interval. The author used an older (and not accurate) model. I consider this a minor point because one of the other authors covered the issue correctly from a different point of view.

 The minor issues are in the law differences, governmental agency names and units of measure. Most of the appendixes could be eliminated for the US market. Obviously any discussion about computers becomes outdated quite quickly. They did a good job of making the subject generic and still up to date. The more important issues deal with ways of looking at maintenance that are slightly different then the corresponding US explanations.

 For example, on page 16, the use of “corrective” is diametrically different and somewhat confusing for a US reader. We view “corrective” as a good thing- it is all work derived from PM inspection. There are many other examples. A serous student could work through the concept to see what the message is. A casual reader would be confused if they have US training.

 In fact the biggest single problem of this work is the figures. Few of the figures are explained by the text. Since they do not use common US usage it was impossible for me to determine what many of the figures meant. The figured appeared without an explanation and with a different context. That was extremely frustrating.

Executive Summary

Asset Maintenance Management is an excellent book for serious students of maintenance management as it takes something to get through the conversions between UK and US models and modes of communication. The book contains many well thought-out sections that show an all-inclusive view of maintenance.  One of the strengths and one of weaknesses was the incredible depth that they went into some topics and the 20,000’ high overview of other topics. In short, the book covers topics that are probably outside the scope of asset maintenance management. An example is the detail in the discussion around page 316 (and the figure on debris generation rates). The minor issues are in the law differences, governmental agency names and units of measure. 


Whoops, looks like something went wrong.

1/1 ErrorException in Filesystem.php line 111: file_put_contents(): Only 0 of 298 bytes written, possibly out of free disk space

  1. in Filesystem.php line 111
  2. at HandleExceptions->handleError('2', 'file_put_contents(): Only 0 of 298 bytes written, possibly out of free disk space', '/var/www/html/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php', '111', array('path' => '/var/www/html/storage/framework/sessions/FbD4wARKWEcxT7W5KXJyimUujKxC4bASfRGLTqYy', 'contents' => 'a:4:{s:6:"_token";s:40:"09IMZdloKG9AN2ioMzDNXf3qkkp7PwOlgrDhcoP4";s:9:"_previous";a:1:{s:3:"url";s:60:"http://www.maintenancetraining.com/articlesubpageLinkView/14";}s:9:"_sf2_meta";a:3:{s:1:"u";i:1566767309;s:1:"c";i:1566767309;s:1:"l";s:1:"0";}s:6:"_flash";a:2:{s:3:"old";a:0:{}s:3:"new";a:0:{}}}', 'lock' => true))
  3. at file_put_contents('/var/www/html/storage/framework/sessions/FbD4wARKWEcxT7W5KXJyimUujKxC4bASfRGLTqYy', 'a:4:{s:6:"_token";s:40:"09IMZdloKG9AN2ioMzDNXf3qkkp7PwOlgrDhcoP4";s:9:"_previous";a:1:{s:3:"url";s:60:"http://www.maintenancetraining.com/articlesubpageLinkView/14";}s:9:"_sf2_meta";a:3:{s:1:"u";i:1566767309;s:1:"c";i:1566767309;s:1:"l";s:1:"0";}s:6:"_flash";a:2:{s:3:"old";a:0:{}s:3:"new";a:0:{}}}', '2') in Filesystem.php line 111
  4. at Filesystem->put('/var/www/html/storage/framework/sessions/FbD4wARKWEcxT7W5KXJyimUujKxC4bASfRGLTqYy', 'a:4:{s:6:"_token";s:40:"09IMZdloKG9AN2ioMzDNXf3qkkp7PwOlgrDhcoP4";s:9:"_previous";a:1:{s:3:"url";s:60:"http://www.maintenancetraining.com/articlesubpageLinkView/14";}s:9:"_sf2_meta";a:3:{s:1:"u";i:1566767309;s:1:"c";i:1566767309;s:1:"l";s:1:"0";}s:6:"_flash";a:2:{s:3:"old";a:0:{}s:3:"new";a:0:{}}}', true) in FileSessionHandler.php line 83
  5. at FileSessionHandler->write('FbD4wARKWEcxT7W5KXJyimUujKxC4bASfRGLTqYy', 'a:4:{s:6:"_token";s:40:"09IMZdloKG9AN2ioMzDNXf3qkkp7PwOlgrDhcoP4";s:9:"_previous";a:1:{s:3:"url";s:60:"http://www.maintenancetraining.com/articlesubpageLinkView/14";}s:9:"_sf2_meta";a:3:{s:1:"u";i:1566767309;s:1:"c";i:1566767309;s:1:"l";s:1:"0";}s:6:"_flash";a:2:{s:3:"old";a:0:{}s:3:"new";a:0:{}}}') in Store.php line 263
  6. at Store->save() in StartSession.php line 88
  7. at StartSession->terminate(object(Request), object(Response)) in Kernel.php line 177
  8. at Kernel->terminate(object(Request), object(Response)) in index.php line 58
  9. at require_once('/var/www/html/public/index.php') in index.php line 21