| | |  | Games and Simulations | Home » » » Mapping the Total Value Stream: A Comprehensive Guide for Production and Transactional Processes | | | | | | | Description: | | Mapping the Total Value Stream defines and elaborates on the concepts of value stream mapping (VSM) for both production and transactional processes. This book reshapes and extends the lessons originally put forward in a number of pioneering works including the popular ,Value Stream Management for the Lean Office. It reinforces fundamental concepts and theoretical models with real-world applications and complete examples of the value stream mapping technique. To educate VSM mappers on the specific mechanics of the technique, the text provides in-depth explanations for commonly encountered situations. The authors also provide a more complete perspective on the concept of availability. While they discuss availability of equipment in transactional processes, they extend the concept by elaborating on availability as it applies to employees. The calculation of process lead time for work queues is taken to an advanced level – not only is the calculation of this lead time explained, but the text also covers the very real possibility of having more work in the queue than available time. While previous books have focused on only production process VSM or transactional process VSM, this work meets the real needs of both manufacturers and service sector organizations by dealing with both types. It goes beyond explaining each scenario, to teach readers what techniques are commonly applicable to both, and also explains areas of difference so that mappers will be able to readily adapt to whatever unique situations present themselves. | | | Product Details: | | | Author:
| Mark A. Nash | | Paperback:
| 296 pages | | Publisher:
| Productivity Press | | Publication Date:
| March 01, 2008 | | Language:
| English | | ISBN:
| 1563273594 | | Product Width:
| 212.75 centimeters | | Product Height:
| 272.75 centimeters | | Product Weight:
| 1.83 pounds | | Package Length:
| 10.8 inches | | Package Width:
| 8.5 inches | | Package Height:
| 0.8 inches | | Package Weight:
| 1.8 pounds | | Average Customer Rating:
|  based on 5 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
 ( 5 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
10 of 11 found the following review helpful:
 VSM Details that you are going to NeedMar 11, 2009
By JustAFilmGuy
"JustAFilmGuy"
Last week, I purchased three VSM books off 'zon. Interestingly, this book had no reviews, but is by far the most useful of the three. Some books provide a quick intro to VSM, but when you start to actually build VSM diagrams, you start to have questions. This book is providing plenty of answers. I am well-versed in UML and various software development methodologies, but this VSM stuff is a different animal.
4 of 4 found the following review helpful:
Excellent VSM ResourceJun 17, 2010
By EL MBB
I felt compelled to write a review for the first time since this book has really helped me translate VSM into the transactional environment. I highly recommend this book for its clear instructions and examples. I not only read it through twice but use it as an ongoing reference guide. I may need to buy another copy because I have practically worn this one out!
2 of 2 found the following review helpful:
 50% of the book I requireJun 19, 2011
By eireborn
This book describes how to draw value stream maps and present them. Current State (where you are now) and also future state (were you want to be after you make improvements). Unfortunately you'll need to by another book to figure out how to make those improvements as this book deals exclusively with drawing pictures of a value stream. kind of anti lean (pun intended) at 296 pages just on that topic alone. The numerous examples of before and after VS maps don't tell you why changes were made or how it improved the value stream.
I bought the kindle edition of this book which is good but unfortunately the many diagrams (on which this book I assume depends) are not clear enough to read. I've bought other kindle books which I've no issues with but this one I would not recommend
6 of 8 found the following review helpful:
Excelent ReferenceApr 30, 2009
By A. Stewart
This is an excelent reference if you need to learn Value Stream Map. It includes both manufacturing and transactional processes. This books holds your hand. This approach prevents you from guessing. This book is written by very experienced people, so all "tricks" you need to know are there
Tips and tricks for value stream mappingAug 13, 2011
By A. Panda
Excellent book on mapping value streams, communication flow, etc.
I would like to share one experience we had with mapping, although we were mapping a regular flow chart (not a value stream map) that should serve both as a starting point for an "FMEA" and as a work instruction. Our chart's flow started at the top of the page and should be read downwards. Whenever we encountered a rework we draw an arrow upwards to the box where it was reworked, when we encountered decision points where a yes took us along one path and a no took us along another path, we draw the typical decision box and proceeded with parallel paths, etc. Once we finished we saw that our chart looked like a spider web and that it was useless as a work instruction, since it was difficult to comprehend even for us. By this time we had already finished 4 different flows (mapped by different teams, but with the same approach).
Then we decided to map only the standard flow (it was the "If you do not encounter problems current state flow chart", not the "future state", just the "present state on a sunny day"). This meant that our flow should never go backwards in the chart and we also reduced the decision boxes to the minimum possible; in most charts we eliminated them completely. So we redrew all maps, which made them far simpler and everybody could follow them.
Afterwards we realized that since we only drew the perfect state, it was not clear what to do if things went wrong and since rework was not drawn anymore, the chart was also not very useful for making improvements. Next we decided to write down in text boxes to the right of the corresponding flow chart icons, what to do when a rework was needed or if something went wrong (kind of a trouble-shooting), so we needed to reprocess our charts again. In the meantime all participants were already kind of frustrated.
Had we read this book earlier, we could have saved all of this, since the authors have faced similar situations as well as different kind of problems in very different mapping environments, they have already done this mistakes and have already found solutions to them. In fact the book contains an explanation of exactly the same problem we had and they proposed that maps should only flow to the right, as well as a simple symbol - a kind of connector to represent rework! So in the end, it was more or less the same solution that we found, but told to you right away. This book is full of such tips, so in my opinion it is one of the best books on the topic. Maybe you can find the theory in other sources, but such valuable tips are not in every book.
| | |
|
