YU The Systems Engineering Perspective Summary

YU The Systems Engineering Perspective Summary

Description

 

 

Throughout your many years in school, you have been told what to learn. Throughout your career, it will be up to you continue learning. You’ll want to become an active, lifelong learner to keep your skills relevant and attractive as engineering and business practices shift and to prepare for the next stage in your career. This assignment is a first step in your lifelong learning journey! In this workshop, I’ll also be sharing how DMAIC is applied in industry, as a mechanism for continuous improvement. DMAIC is also the framework for your sr. design project.

Read and summarize an article or a book chapter with a 1-page, single-spaced, well-written summary covering:

  • Article title and authors
  • A key diagram, illustration, list, table, etc. taken from the article or created based on the article
  • A paragraph summarizing the key points of the article
  • A paragraph explaining the implications for an ISE (e.g., skills needed, career opportunities, career threats)
  • Footnote with full bibliographic citation(s) in APA format

You may use any sources you find useful. Here are some examples:

Links to an external site. (Subscribe here

Links to an external site. (Subscribe here

  • Links to an external site. to keep up with the latest ideas. It’s worth it!)
  • Bain.com
  • MIT Technology Review
  • Scientific American

 

Explanation & Answer:

1 Page

INT 221 NJIT Roman Hypocaust Diagram With Written Explanation Paper

INT 221 NJIT Roman Hypocaust Diagram With Written Explanation Paper

Description

 

 

REQUIREMENTS
Create a document using a publishing program such as InDesign, Corel, Word, etc. consisting of 1 total page:
Draw a diagram of the Roman Hypocaust. In your own words, write an essay describing the parts of the
heating system. Please indicate the heating, heat resistance, heat gain, etc. principles that make the Roman
Bath work.

Additional pictures or diagrams illustrating the heating principles that make the systems work are
recommended.

There are two (2) deliverables:
1. You will hand in a printed and stapled copy at the beginning of class on Monday October 2.
2. You will upload a PDF of your homework to Canvas before the beginning of Monday October 2 class.

 

Explanation & Answer:

1 Paper

UT Project Engineering Managing Complex Projects Discussion

UT Project Engineering Managing Complex Projects Discussion

Description

 

 

 

 

Unformatted Attachment Preview

Explanation & Answer:

1 Project

ENGR 2140 Engineering Voltage Divider Circuit & Graphing Data Project

ENGR 2140 Engineering Voltage Divider Circuit & Graphing Data Project

Description

 

 

 

 

Unformatted Attachment Preview

Explanation & Answer:

1 Project

Solidworks Flow Simulation Sphere Aerodynamics Lab

Solidworks Flow Simulation Sphere Aerodynamics Lab

Description

 

 

Unformatted Attachment Preview

This work should be completed and submitted. In this CFD lab, we will learn how to use Solidworks Flow Simulation to study the three-dimensional flow of air past a sphere. A. Creating the Sphere Part: 1. Start Solidworks 2016/2017, and create a New Document. Select File>>New… from the Solidworks menu. 2. Select Part in the New Solidworks Document window and click the OK button. 3. Next, we will sketch a half circle in the Front Plane and revolve it to create a sphere. Click on Front Plane in the Design Tree. Figure 1. Front Plane in Design Tree. 4. Under the Sketch tab, select Line>>Centerline. Figure 2. Centerline tool. 5. Next, draw a vertical centerline in the sketch window (see Figure 3). Start the line directly above the origin. Click and draw the line downward through the origin and end the line approximately the same distance below the origin. Right click anywhere in the graphics window and click on Select. Figure 3. Sketch of vertical centerline. 6. Select the Centerpoint Arc and draw a half circle. First, click on the origin, you should see a red filled circle indicating that you are at the origin. Next, click on the centerline above the origin. Click on the centerline once again but this time below the origin; a half circle should be drawn as shown in Figure 5. Right click anywhere in the graphics window and click on Select. Figure 4. Centerpoint Arc tool. Figure 5. Sketch of half circle. 7. Select Tools>>Options from the Solidworks menu and click on the Documents Properties tab. Click on Units and select MMGS (millimeter, gram, second) as the Unit system. Select OK. Figure 6. Selection of units: MMGS. 8. Select the Smart Dimension tool. Figure 7. Smart dimension tool. 9. Create a radius of 30.0 mm for the half-circle by clicking twice on the half-circle and entering the numerical value (30.0) in the Modify window. Save by clicking on the green check mark. Figure 8. Defining the radius. 10. Under the Features tab, select the Revolved Boss/Base icon. You will get a message that the sketch is currently open and a question if you would like the sketch to be automatically closed. Choose the Yes button. Figure 9. Revolved Boss/Base tool. Figure 10. Answer ‘Yes’ in pop-up window. 11. Use the default Revolve Parameters: Line1, Blind Direction and 360 degrees. Click on the green check mark to exit the Revolve window. Figure 11. Revolve parameters. 12. Save the part. Select File>>Save As… Enter Sphere as the File name and click on the Save button. B. Setting up Flow Simulation –External Flow Around Sphere: 13. Select Tools>>Add-Ins…from the menu and check the SolidWorks Flow Simulation 2016 box. Select OK. A Flow Simulation tab is now created. Figure 12. Check box next to Solidworks Flow Simulation 2016. Figure 13. Flow simulation tab appears. 14. Under the Flow Simulation tab, select Wizard to create a new project. Figure 14. Wizard tool. 15. Enter the Project Name: “Flow around a Sphere”. Push the Next> button. Figure 15. Enter name of project. 16. Choose the SI (m-kg-s) unit system and click the Next> button again. Figure 16. Select SI units. 17. Check the External option for Analysis type and click the Next> button. Figure 17. Select External analysis type. 18. Choose Air as the Default Project Fluid by clicking on the plus sign next to the Gases and selecting Air. Next, select the Add button. Click on the Next> button. Figure 18. Select Air as the fluid. 19. Use the default Adiabatic wall for the sphere and zero roughness on the surface of the sphere. Click on the Next> button. Figure 19. Use default wall conditions. 20. Enter 100 m/s as the Velocity in X-direction. Notice that the pressure is defined as absolute pressure. Click on the Finish button. Figure 20. Set fluid velocity to 100 m/s. 21. Note that flow simulation settings can be changed by selecting the General Settings button. Do not make any changes at this time. Figure 21. General settings tool. 22. Click on the Global Mesh icon. Set the initial mesh resolution setting to 4 using the green circular slider. Click on the green check mark to save. Figure 22. Global mesh tool. Figure 23. Set mesh setting to 4. 23. The mesh can be viewed by right clicking on Mesh in the Design Tree and selecting Show Basic Mesh. Next, hide the mesh by right clicking on Mesh in the Design Tree and selecting Hide Basic Mesh. Figure 24. Show Basic Mesh option. 24. Create a global goal for the project by clicking on the Flow Simulation icon and selecting Global Goals. Figure 25. Global Goals tool. 25. Select the following global goals: Max Dynamic Pressure and Max Velocity (x). The solver will stop once the error has been minimized in the calculation of these two parameters. By setting a goal, the total solution time for the solver will be reduced. Goals can also be defined as an equation (e.g. drag coefficient) and can be defined at a specific point, surface, or volume. Click on the green check mark to save the goals. Figure 26. Selecting Global Goals. 26. Click on the Run icon to start the simulation. In the window that appears, select Run. Figure 27. Run tool. 27. A Solver window will appear. Click on the goals flag to view the progress of each parameter calculation. The CPU time to run the simulation will depend on the speed of your computer and the amount of memory. The simulation is done when the bottom of the window states “Solver is finished” as shown below. Figure 28. Solver window showing simulation completion. 28. All simulation results are saved into a folder called “1” in your working directory (which is most likely the directory where you saved the Sphere part file). The flow simulation file is called 1.fld. To reopen these simulation results at a later date, first make sure the Solidworks Flow Simulation tab is available (Tools>>Add-Ins…from the menu and check the SolidWorks Flow Simulation 2016 box). Then, right click on Results in the Flow Simulation analysis tree and select Load from File… Open the 1.fld file. Figure 29. Results >> Load from file. C. Viewing Results Creating Cut Plots: 29. Expand the Flow Simulation analysis tree by clicking the plus sign next to Results (1.fld). Figure 30. Click on plus sign to expand view. 30. Right click on Cut Plots in the Flow Simulation analysis tree and select Insert. Figure 31. Insert Cut Plot. 31. Click on the Vectors button in the Display section. Choose Velocity from the Contours section drop down menu. Slide Number of Levels to 255. Click the green check mark. Figure 32. Cut plot parameter window. 32. Rename Cut Plot 1 to Velocity around Sphere in the Flow Simulation analysis tree by clicking on the name. Figure 33. ‘Cut Plot 1’ changed to ‘Velocity around Sphere’. 33. Apply lighting by selecting the Lighting icon. Note the colors on the colorbar and in the cut plot. Regions with larger flow velocities appear red, and regions with smaller flow velocities appear blue. Figure 34. Lighting tool. Figure 35. Velocity cut plot. 34. Save the cut plot by right clicking on Velocity around Sphere in the Flow Simulation analysis tree and selecting Save As… The plot can be resized and reoriented by selecting the various options in the drop down menu. Click the Save button. Figure 36. Select Save As Figure 37. Save window. 35. Hide the Velocity Cut Plot by right clicking on Velocity around Sphere in the Flow Simulation analysis tree and selecting Hide. Figure 38. Hide option. 36. Create a Pressure Cut Plot by repeating these steps and choosing Pressure instead of Velocity from the Contours drop down menu. Using Probe Tool: 37. Select the Probe icon. The probe tool can be used to display the numerical value at various locations in your plot by moving the cursor location. Probe the pressure near the stagnation point. Note that the pressures are given in absolute pressure (not gauge pressure). Figure 39. Probe tool. Creating Flow Trajectory Plots: 38. Hide all cut plots by right clicking on the name of the plots in the Flow Simulation analysis tree and selecting Hide. 39. Right click on Flow Trajectories in the Flow Simulation analysis tree and select Insert. Figure 40. Flow trajectory tool. 40. Click on the surface of the sphere. Use the default values, and click the green check mark. 41. Save the flow trajectory plot by right clicking on the name of the plot in the Flow Simulation analysis tree and selecting Save As… The plot can be resized and reoriented by selecting the various options in the drop down menu. Click the Save button. D. Performing a Parametric Study: Parametric studies are often used in CFD analyses. In a parametric study, one or more parameters are varied to study the sensitivity of the solution to the parameter(s). Here, we will change the fluid velocity parameter, and study its effect on the stagnation pressure. 42. Copy the previous simulation by clicking on the Clone Project icon. Figure 41. Clone tool. 43. Name the new project, “Flow around a Sphere – Velocity 2x,” and click the green check mark. Figure 42. Set project name. 44. We will now change the velocity prescribed in the settings. Click on General Settings. Figure 43. General Settings tool. 45. Click on Initial and ambient conditions in the right-hand Navigator section. Then, change the Velocity in X direction to 300 m/s. Click OK. Figure 44. Change velocity to 200 m/s. 46. Click Run to start the simulation. 47. View the results using the methods described in Section C. CFD Lab #1 Report Instructions (35 points): Answer the following questions. Submit your answers in a single typed document. All equations must be typed, and all figures must include a descriptive caption. 1. Include cut plots that show the velocity and pressure distribution around the sphere for both initial flow velocities studied: 100 m/s and 300 m/s. Clearly label the location of the stagnation point in all figures. 2. Using Bernoulli’s equation, calculate the magnitude of the absolute pressure and velocity at the stagnation point. Calculate the answer for both initial flow velocity cases (100 m/s and 300 m/s). Provide your final answers and equations (with explanations of your steps) to show how you arrived at your answers. 3. Probe the values of the pressure and velocity near the stagnation point in your flow simulations. How do they compare to the values that you computed in question 2? Provide calculated values and probed CFD values to support your answer. 4. Based on your plots, what can you conclude about the relationship between pressure and velocity? Is your conclusion in agreement with Bernoulli’s principle? Explain. This report should be completed and submitted via Blackboard in the Lab folder: CFD Lab 1 Turn it In link. Upload the solidworks .prt file in Blackboard to the assignment link in the lab folder. Objective 1. Turn in .sldprt file to Blackboard assignment link on time for the lab submission. Student worked on model creation and simulation during assigned class time. 2. Answer to question number 1 of assignment. Clear label in BOTH plots. 3. Bernoulli’s equation is answered correction in question number 2. Solution is clear and explained each step. 4. Answer to question number 3 of assignment shows probe locations. Comparison of results is clear and descriptive. 5. Conclusion of report. Answer to question number 4 is clear and descriptive. Comments Points 10 5 10 5 5
Purchase answer to see full attachment

Explanation & Answer:

1 Lab

UF Lean Principles and Practices Presentation

UF Lean Principles and Practices Presentation

Description

 

 

Develop a presentation that highlights the key lessons learned from the course. Upload the presentation to the Blackboard discussion board to share with the class or provide a link to the presentation (i.e., slide share, YouTube, etc.).

The presentation should be developed and presented using a Pecha Kucha format. +

Each student will develop a presentation on lessons learned in the course. In a scholarly fashion, using material from the text or other scholarly sources as your reference material, present their information using the format described below. The presentation should be of professional quality and format.

The presentations are due the last week of class.

Pecha Kucha Tutorial http://www.slideshare.net/wmacooper/pecha-kucha-tu…

Pecha Kucha Examples http://www.pechakucha.org/watch

Pecha Kucha Bowling Green http://www.pechakucha.org/cities/bowling-green

 

Unformatted Attachment Preview

The Lean Handbook A Guide to the Bronze Certification Body of Knowledge Anthony Manos and Chad Vincent, editors ASQ Quality Press Milwaukee, Wisconsin American Society for Quality, Quality Press, Milwaukee 53203 © 2012 by ASQ All rights reserved. Published 2012 Library of Congress Cataloging-in-Publication Data The lean handbook / Anthony Manos and Chad Vincent, editors. p. cm. Includes bibliographical references and index. ISBN 978-0-87389-804-1 (alk. paper) 1. Total quality management. 2. Industrial efficiency. I. Manos, Anthony, 1963– II. Vincent, Chad. HD62.15.L4324 2012 658.4’013-dc23 2012010040 No part of this book may be reproduced in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. Publisher: William A. Tony Acquisitions Editor: Matt Meinholz Project Editor: Paul Daniel O’Mara Production Administrator: Randall Benson ASQ Mission: The American Society for Quality advances individual, organizational, and community excellence worldwide through learning, quality improvement, and know ledge exchange. Attention Bookstores, Wholesalers, Schools, and Corporations: ASQ Quality Press books, video, audio, and software are available at quantity discounts with bulk purchases for business, educational, or instructional use. For information, please contact ASQ Quality Press at 800-248-1946, or write to ASQ Quality Press, P.O. Box 3005, Milwaukee, WI 532013005. To place orders or to request a free copy of the ASQ Quality Press Publications Catalog, visit our website at http://www.asq.org/quality-press To Jennifer, who puts up with all my antics. To Judy, who taught me her version of continuous improvement “Do not rest on your laurels” And to George, for supporting me and for helping me reach a higher level of accomplishment. —Tony Manos To my wife, Holly, and my kids, Austin and Miranda, who gave up their time with a husband and father to make this book possible, and whose continued support provides me strength to pursue my dreams. —Chad Vincent Foreword Robert D. Miller Executive Director The Shingo Prize for Operational Excellence Jon M. Huntsman School of Business Utah State University T he Lean Handbook is a terrific compilation of sections written by practitioners who bring their individual and unique experience and expertise to this body of knowledge. I appreciate the connections made with many of the dimensions and principles identified in the Shingo model. We must each be on a journey of continuous improvement, which means we must be constantly looking for new perspectives and approaches to bring about personal and organizational improvement. Anthony Manos is correct when he says that the most difficult and yet important work we will do with lean is to change the culture of the organization. For lean to be successful, the many tools outlined in this handbook must be supplemented with an equally devoted effort to influence the mind-sets and behaviors of people in the organization. At the Shingo Prize we have learned that the best way to do this is to, as Stephen Covey would say, “begin with the end in mind” In other words, while you are learning to use these great tools, you must also keep the deeper meaning, or the “why” behind the tools, very clear. The Lean Handbook can help each of us act our way into a new way of thinking, and then think our way into a new way of acting. By putting the wisdom of this handbook to work every day by every person and never taking your eyes off the prize a new culture that is deeply embedded in the principles of lean we will greatly increase the odds of a sustainable business transformation. As you put this work into practice, you will recognize the shifting roles of leaders and managers in your organization. It is not enough for leaders to just keep doing what they have always done, nor is it enough for them to merely support the work of others. Rather, leaders must lead the cultural transformation and build the principles behind all of these great tools into the mind-sets of their associates. Similarly, managers have to do more than participate in kaizen teams. The emerging role of managers is to focus on designing, aligning, and improving the systems of the business so that they drive ideal behaviors that cause people to change their thinking of what excellence really looks like. Using The Lean Handbook as a roadmap will no doubt be a powerful tool in helping you avoid many of the mistakes made by others over the years. I invite you to visit http://www.shingoprize.org to see how the key points illustrated here support the Shingo model for operational excellence. My thanks to all of the contributing authors! Preface WELCOME TO THE LEAN HANDBOOK What a remarkable journey this has been. Working on this book has been a terrific experience. We have had the great pleasure of working with a number of wonderful and giving individuals. Lean practitioners are truly an amazing and unique family. The energy and willingness of the individuals who helped create this book are evidence of the great profession and network of people of which we take part. So many different points of view and applications of knowledge made for great discussions, contemplation, and collaboration. With so much knowledge and understanding, it was difficult to find a point at which to stop talking and start putting these discussions on paper. In the end, we believe this book embodies the Lean Body of Knowledge (BOK) in a way that is much like the lean journey ever evolving and always adaptable. Lean has been a culmination of multiple individuals, philosophies, systems, tools, and applications throughout history. The challenge has been that all these different contributions are found in different places, called different things, and applied in different manners-making it difficult for the lean practitioner to gain an understanding of lean at a level of its full body of knowledge without great effort, research, experience, and networking. While this book is not a substitute for the effort, research, experience, and networking every seasoned lean practitioner goes through, we hope it provides a sound starting point for those just beginning or expanding their knowledge of lean. NOT AN EXAM PREPARATION MANUAL First and foremost, this book is not a Lean Certification exam preparation manual. The Lean Bronze Certification exam questions are based on material from the five recommended reading books (see Appendix B, “Recommended Reading List for Lean Certification Exam Preparation”): Learning to See Lean Thinking Gemba Kaizen Lean Production Simplified Lean Hospitals Make no mistake this book takes nothing away from the great lean works that have preceded it. As a matter of fact, we believe that this book complements and pays tribute to those works as being pieces of the larger Lean BOK. But that is exactly what they are pieces. Our intent was to put these pieces together in a manner to provide a higher-level overview of the Lean BOK. We realized early on in the project that this task was not something we could do alone. This handbook’s intention is to gather information related to the Lean BOK (see Appendix A, “Lean Certification Body of Knowledge”) into one source. This book will enhance your understanding of the BOK as a whole and give you a more holistic look at lean. As great as the five recommended reading books are, they were not written with the intent of covering all aspects of the Lean BOK individually. Additionally, this book does not rehash the content of the five recommended reading books. What we have done is put together a book whose sole purpose is to embody the entire Lean BOK, section by section. This book is, by design, written at the Bronze Level for certification knowledge. This means that the weightings used in the Lean BOK for the Bronze Certification were considered for the depth and breadth of material considered for each rubric. Therefore, it is by no means all-inclusive of every principle, system, and tool at every level of application related to lean. By addressing the Lean BOK at the Bronze Level, this book provides a basic understanding of the lean principles, systems, and tools at a tactical level to drive improvements with measureable results. The intent is to revise the book over time to encompass the topics of the Silver Level (an integrated application on value stream transformations for lean leaders) and the Gold Level (for strategic application of lean across the entire enterprise, with emphasis on assets, systems, processes, and people). Therefore, this book, much like a lean journey in an organization, will be adapted as the Lean BOK evolves and more knowledge is integrated. Given that the intent of this book is not to rehash the certification reference books, we hope that this book serves as a good starting point for those practitioners who want a holistic view of the Lean BOK, with links to many other lean references for greater detail and understanding. While there are many references, we tried to stay true to the terminology and applications discussed in the core books of the certification reading list. One of the difficulties we faced in creating a book of this magnitude was how to structure it. While we could have structured it alphabetically by topic, organized it by case studies or by organizations, or arranged it by some other method, we wanted to stay true to the Lean BOK structure. While this structure does not allow for a nice flow from one topic to another for easier reading, the writing conforms to the Lean BOK and the Shingo Prize model. We thought that this would provide a traceable reference for those individuals and organizations utilizing those structures for the pursuit of operational excellence. When lean is applied in an organization, the knowledge of the processes and the generations of ideas do not come from the organization’s designated lean experts. They come from those who perform the work on a daily basis. We took the same approach with this book. It would have been easy for us to read all the books and then pull information from those books to create another book. But then it would have been just that another book. We needed to take a lean approach with this book. So, just as you would create a team of individuals who perform the work in a kaizen event, we assembled a team of individuals who perform the work and who apply lean in their organizations every day. MANY VOICES AND MANY STYLES We were lucky to have some of the best minds in lean contribute to this endeavor (see “Contributing Authors and Editors”). There are many voices, many contributors, many styles of writing, and more than one point of view. The contributing authors come from many different backgrounds. Such different life experiences weave a wonderful lean tapestry. This book is not just lean for manufacturing or lean for service or lean for healthcare. The examples given in this book can fit any type of organization. We hope you find these different points of view helpful while finding your voice in lean. It has been a pleasure to not only be authors and share our knowledge of lean but also be editors and work closely with others like us. The great thing about working with all these individuals was learning how they apply the same things we apply, but maybe just a little differently. These differences provided us a different perspective on our version of lean and were wonderful opportunities to expand our personal lean knowledge base. Coming together is a beginning. Keeping together is progress. Working together is success. —Henry Ford We wish you the best of luck and fair weather on your lean journey! Acknowledgments I t would be nearly impossible to mention everyone who had an influence on the creation of this lean handbook, but we would like to make a few special mentions. First and foremost we would like to thank all the contributing authors, who worked tirelessly to help construct and shape this handbook. Their willingness to share their knowledge and experience was exceptional. To learn more about these extraordinary lean thinkers, see “Contributing Authors” A special acknowledgment goes to all the people and organizations that the contributing authors and editors have worked with over the years to help develop and deepen our understanding of lean and influence us as we continue to learn more. This handbook would not have been possible without the support of the Lean Enterprise Division (LED) of the American Society for Quality (ASQ) and the LED Leadership Team Kiami Rogers (chair), Frank Murdock (chair-elect), and Tammy Miller (secretary). We would also like to thank George Alukal, founding member of the LED and the driving force behind lean’s becoming an integral part of ASQ and a resource for its members. The Lean Certification is supported by the four alliance partners: the Society of Manufacturing Engineers (http://www.sme.org), the Association for Manufacturing Excellence (http://www.ame.org), the Shingo Prize (http://www.shingoprize.org), and of course ASQ (http://www.asq.org). We would like to thank Kris Nasiatka from the Society of Manufacturing Engineers (SME) for all her efforts in creating the Lean Certification and for her continued support of the partner organizations and this lean handbook. Also from SME, Kelly Lacroix leads the Lean Certification Oversight and Appeals Committee, which continually monitors and improves the certification process. If it wasn’t for our friends Matt Meinholz and Paul O’Mara at ASQ Quality Press, this book never would have been completed. We appreciate their patience and advice while working on this endeavor. Last, but not least, we would like to give our utmost gratitude to Robert Damelio. As a member volunteer, Robert not only was the driving force behind ASQ’s LED adopting the Lean BOK, but he also guided the certification initiative at ASQ. Without his tireless efforts, ASQ would not have been a partner member of the Lean Certification. A Brief History of the Lean Certification Body of Knowledge Kris Nasiatka, SME HOW IT STARTED The publication of The Machine that Changed the World, in 1990, brought the concept of lean to the masses. It also provided opportunities for many different flavors of lean to be born. With that came a myriad of education, training, and consulting practices, each bringing its own version of lean to the market. In 2001, members of the Society of Manufacturing Engineers (SME) and the Association for Manufacturing Excellence (AME), and constituents of the Shingo Prize came together and determined that some type of validation for professional practice of lean was necessary. There was a need to align practitioners with a common foundation (fundamentals) of lean practice and, more importantly, provide a roadmap to support workforce development and training efforts. After a few stops and starts, development was under way in earnest in 2004. The parties involved agreed that the Shingo Prize model should serve as the basis for the program’s Body of Knowledge (BOK). The initial BOK went deeply into evaluating lean practitioners’ job tasks. The model was modified to make it applicable to people and workforce development efforts versus being a corporate lean transformation model. The proposed Lean BOK was validated in a study in early 2005, thus launching version 2.0. KAIZEN BLITZ WEEK Shortly after version 2.0 was launched, a core development committee was established. With the preliminary validation of the BOK in place, a straw man for program components was outlined. SME hosted a “blitz week” to expedite development of the program. Nearly 60 lean practitioners, representing a breadth of manufacturing industries, consulting practices, and academia, gathered for a week to develop the components of this new certification program. During the blitz, development teams were established to focus on exams, portfolios, and the mentoring requirements for this new program. Throughout the entire development process, nearly 200 lean practitioners were involved in the creation of this program not including the couple of thousands that participated in the study. The first Bronze exam was offered to the public in March 2006. The Silver exam was available in June 2006, and the Gold exam was launched in December of that year. The formal Lean Certification Oversight and Appeals Committee was established and met for the first time in March 2006. UPDATED VERSION OF THE BOK With the program “live” for a year, a second BOK validation study was conducted. It was desired to structure the certification BOK similar to the Shingo Prize model. The Shingo Prize was restructuring its model, which created an opportunity for the certification program to validate proposed changes to the BOK received by certification candidates as well as the oversight body. The validation study was completed in 2007. The Lean Certification Oversight and Appeals Committee used the findings to restructure the BOK and launched version 3.0 in 2008 (see Appendix A). Although the topics did not change, the BOK was reorganized for better flow and improved alignment of topics within each category. Each BOK validation study is structured in a way that derives a weighting factor for each section of the BOK. The weighting factors identify the percentage of exam coverage for each BOK area and help the committee identify priority areas for building the exam bank. THE FUTURE OF THE BOK Validation studies will be conducted every five to seven years. The studies are intended to verify that current topics are still relevant in contemporary practice of lean and to identify any new or emerging topics that should be added to the BOK. Special Dedication Kiami Rogers Chairperson, ASQ Lean Enterprise Division T his handbook is dedicated in loving memory to Wayne Paupst (1957–2010), past chairman of the Lean Enterprise Division (LED). In August 2010, Wayne lost a long battle with cancer. Wayne was a quality professional’s “quality professional” He never complained about his condition. In fact, many of us on the Leadership Team, which worked closely with Wayne, were not even aware of the severity of his condition. Wayne possessed a wonderful sense of humor and had a kind word for everyone. He was always ready with a joke, and always ready to laugh at jokes offered by others. His leadership, instruction, kindness, and humor will be missed by family and friends as well as organizations such as ASQ. I first met Wayne at a meeting of the founders of the LED prior to the LED becoming a forum and subsequently a division. Wayne had been a member of ASQ since 1988. He had more than 25 years in the quality profession, holding positions such as quality engineer, quality systems coordinator, inspector, and quality assurance manager. He had been instructing certification courses for the Lehigh Valley Section of ASQ since 1996 and also had provided instructional courses for many of the top companies in the Lehigh Valley as well. Wayne also held several ASQ certifications: Six Sigma Black Belt, Quality Engineer, Quality Manager, Quality Auditor, Quality Technician, Quality Inspector, Process Analyst, and Quality Improvement Associate. It was during Wayne’s tenure as LED division chair that ASQ introduced the Lean Certification, in partnership with SME, AME, and the Shingo Prize organizations. I have no doubt that Wayne would have pursued obtaining the ASQ Lean Certification himself, as well as teaching and mentoring other lean professionals pursuing this certification. It is with great honor that we dedicate this handbook to Wayne. Prologue Kiami Rogers Chairperson, ASQ Lean Enterprise Division T he purpose of this handbook is to provide a reference guide for lean principles and methods. This handbook on its own is not intended to prepare one for the ASQ Lean Certification (in partnership with SME, AME, and the Shingo Prize organizations). The user of this handbook is a lean professional who has some knowledge of and experience with lean principles and methods. Material from several lean practitioners with differing levels of disclosure of their experiences has been gathered to create this handbook and has been edited to be presented in a consistent and unified format. With 6000 members worldwide, the ASQ Lean Enterprise Division (LED) is a global network of professionals helping individuals and organizations apply proven and leading edge lean principles and practices to achieve dramatic results for personal and organizational success. Whether or not you are a member of the ASQ LED, we hope you find this handbook a useful guide in your lean journey. Contributing Authors and Editors T his handbook was a large collaborative effort, and we would especially like to thank all the contributing authors, who shared their time and wisdom to help make this endeavor possible. CONTRIBUTING AUTHORS Christopher Abrey is a program manager with Northstar Aerospace in Bedford Park, Illinois. He earned a bachelor of engineering in manufacturing systems engineering from Coventry University, UK. He is a senior member of the Society of Manufacturing Engineers (SME) and a member of the Association of Manufacturing Excellence (AME). Christopher has more than 20 years of lean experience in manufacturing and recently completed the Lean Bronze Certification. He can be reached at cabrey@nsaero.com. Section 2.2.5. Total Productive Maintenance (including predictive) Andy Carlino is cofounder and partner of the Lean Learning Center. In addition to over 20 years’ experience in real-world senior management, including president and COO, he has for the past 20 years been providing consulting, training, and coaching services from the boardroom to the shop floor to organizations across the globe. He has published numerous articles and is coauthor of the Hitchhiker’s Guide to Lean: Lessons from the Road. Andy is a frequent speaker for a variety of professional organizations and corporate conferences, including guest speaker for Clemson and Harvard University. He holds a BS in engineering and a BA in psychology and is a member of SME, SAE, AME, ASQ, and numerous other industry and professional associations. Sections 1.2.1. Planning & Deployment 1.2.2. Create a Sense of Urgency 1.2.3. Modeling the Lean Principles, Values, Philosophies 1.2.7. Motivation, Empowerment & Involvement Adil Dalal is CEO of Pinnacle Process Solutions, Intl.; a keynote speaker; thought leader in lean, project management, and leadership; and author of The 12 Pillars of Project Excellence: A Lean Approach to Improving Project Results. He has earned MS degrees in engineering management and mechanical engineering. He is a Certified Lean Bronze Professional, Certified Quality Engineer (CQE), Project Management Professional (PMP), and Board Certified Executive Coach. He is the chair of ASQ’s Human Development & Leadership Division, and certification chair of the Lean Enterprise Division. He served on the Lean Certification Oversight and Appeals Committee. He can be reached at adil@pinnacleprocess.com Sections 1. Cultural Enablers 1.1. Principles of Cultural Enablers 1.1.1. Respect for the Individual 4.3.5. Competitive Impact Grace Duffy is president of Management and Performance Systems. She holds an MBA from Georgia State University and has coauthored numerous books: The Quality Improvement Handbook, Executive Guide to Improvement and Change, Executive Focus: Your Life and Career, The Public Health Quality Improvement Handbook, QFD and Lean Six Sigma for Public Health , Modular Kaizen: Dealing with Disruption, and Tools and Applications for Starting and Sustaining Healthy Teams . She is an ASQ Certified Manager of Quality/Organizational Excellence (CMQ/OE), Improvement Associate, Auditor, Lean Six Sigma Master Black Belt (LSS MBB), and ASQ Fellow. Section 2.2.8. Strategic Business Assessment David S. Foxx is a senior manager and Champion of the Continuous Process Improvement Community of Practice at Deloitte Consulting. He earned an MBA at the University of Phoenix and a bachelor of science in industrial engineering at the University of Texas at El Paso. David is a leader in enterprise transformation and specializes in innovation, product, process, and service design. David presented “Total Quality Design; An Imperative for Survival” at the Annual Quality Congress. He is a senior member of ASQ and a member of the ASQ Quality Press Standing Review Board, the Institute of Industrial Engineers (IIE), and the International Society of Six Sigma Professionals (ISSSP). His certifications include ASQ Certified Six Sigma Black Belt (CSSBB), LSS MBB, Lean Master, and Design and Innovation Master Black Belt. He can be reached at sixsigmalean@aol.com Sections 2.1.2.2. 7 Wastes (Muda), Fluctuation (Mura), and Overburden (Muri) 2.3.5. Product and Service Design 2.3.5.1. Concurrent Engineering 2.3.5.2. Quality Function Deployment 2.3.5.3. Product or Process Benchmarking 2.3.5.4. Design for Product Life Cycle (DFx) – Cradle to Cradle 2.3.5.5. Variety Reduction – Product and Component 2.3.5.6. Design for Manufacturability 4.3.2. Delivery 4.3.2.1. Takt Time 4.3.2.2. Cycle Time 4.3.2.3. Lead Time Dr. Gwendolyn Galsworth is president and founder of Visual Thinking, a training, research, and consulting firm, and the VTI/Visual-Lean Institute, which offers licensing and train-the-trainer in nine core visual workplace courses. Over some 30 years of handson implementations, Gwendolyn has nearly single-handedly created the models, concepts, and methods of workplace visuality that define visual’s distinct and powerful contribution to enterprise excellence and to sustainable cultural and bottom-line results. Gwendolyn serves as a Shingo Prize examiner. She is the author of Visual Systems: Harnessing the Power of the Visual Workplace ; Smart, Simple Design: Using Variety Effectiveness to Reduce Total Cost and Maximize Customer Selection ; two Shingo award-winning books, Visual Workplace, Visual Thinking: Creating Enterprise Excellence through the Technologies of the Visual Workplace and Work That Makes Sense; and many DVDs. She can be reached at gwendolyn@visualworkplace.com Section 2.2.1. Visual Workplace Bruce Hamilton is president of the Greater Boston Manufacturing Partnership, headquartered at the University of Massachusetts Boston campus. He attended Bowdoin College and earned a BA from the University of Arizona. Bruce is the creator of Toast Kaizen2 and other lean training videos, and also coauthor with Pat Wardwell of the eContinuous Improvement System Manual. He posts weekly to his blog: http://www.oldleandude.org both a recipient of the Shingo Prize and an inductee into the Shingo Prize Academy, Bruce is also a Shingo Prize examiner and a member of the Shingo Prize Board of Governors. He can be reached at pokayoke@comcast.net Sections (with Pat Wardwell) 2.1.2. Identification & Elimination of Barriers to Flow 2.1.2.1. Flow & the Economies of Flow 2.1.2.3. Connect & Align Value Added Work Fragments 2.1.2.4. Organize around Flow 2.1.2.5. Make End-to-End Flow Visible 2.1.2.6. Manage the Flow Visually 2.3.7.1. Mistake and Error Proofing (Poka Yoke) 2.3.7.4. Right Sized Equipment 2.3.7.5. Cellular Flow John Kendrick is a principal with Fujitsu in Sunnyvale, California, and has more than 15 years of lean experience in manufacturing, finance, telecommunications, and healthcare. John holds a master of engineering degree in simulation and modeling from Arizona State University, a master of applied statistics from Penn State, and a master of business administration in finance from the University of Pittsburgh. He is a Certified Six Sigma Master Black Belt (CSS MBB) and a senior member of ASQ. He is also a CSSBB, Certified Reliability Engineer (CRE), Certified Software Quality Engineer (CSQE), and CMQ/OE and holds two Lean Certifications. Sections 2.3.1. Work Flow Analysis 2.3.1.1. Flowcharting 2.3.1.2. Flow Analysis Charts 2.3.1.3. Value Stream Mapping 2.3.1.4. Takt Time Analysis 4.2.1. Measurement 4.2.1.1. Understand Interdependencies between Measures and Measurement Categories 4.2.1.2. Align Internal Measures with What Matters to Customers 4.2.1.3. Measure the Results from the “Whole” System 4.2.1.4. Measure Flow and Waste 4.2.3. Analysis – Understand What Moves the Dial on Measures 4.2.4. Reporting 4.2.4.1. Visible Feedback Real-Time Matthew Maio is a quality manager at Raytheon IDS in White Sands, New Mexico. He earned bachelor’s degrees in business and computer science from the College of Santa Fe, New Mexico. He is the author of Quality Improvement Made Simple and Fast! and coauthor of The Six Sigma Green Belt Handbook (both from ASQ Quality Press). Matthew is a member of the International Test and Evaluation Association and the Directed Energy Professionals Society. He is a senior member of ASQ and past regional director (board member) and section chair of ASQ. He holds ASQ certification as a CQM/OE, CSSBB, Certified Six Sigma Green Belt (CSSGB), CSQE, and Certified Quality Auditor (CQA) and Defense Acquisition University Lean Six Sigma Yellow Belt (LSSYB) and Process Quality Management (PQM) certification/recognition. He can be reached at Matt_Maio@comcast.net. Sections 1.2.4. Message Deployment – Establishing Vision and Direction 1.2.5. Integrating Learning and Coaching 1.2.6. People Development – Education, Training & Coaching 1.2.8. Environmental Systems 1.2.9. Safety Systems 2.1.5.1. Quality at the Source 2.1.5.4. Multi-Process Handling 2.2.6. Standard Work 2.2.7. Built-in Feedback 2.2.15. Knowledge Transfer 2.3.7.3. One Piece Flow 2.3.7.4. Right Sized Equipment 2.3.7.6. Sensible Automation 2.3.7.8. Source Inspection David Mann is principal at David Mann Lean Consulting. He is the Shingo Prize-winning author of Creating a Lean Culture: Tools to Sustain Lean Conversions (Productivity Press). David serves on the editorial board of AME’s publication, Target, on the management science faculty at the Fischer College of Business at Ohio State University, and as a Shingo Prize examiner. He earned his PhD in psychology from the University of Michigan. He can be reached at dmann@dmannlean.com. Sections 2.1.1. Process Focus 3.1.1.3. Closed-Loop Thinking to Assure Effective Feedback of Organizational Learning Anthony Manos is a catalyst with Profero and lean champion at 5S Supply in Frankfort, Illinois. He earned an MBA in entrepreneurial studies from the University of Illinois at Chicago. He is the coauthor of Lean Kaizen: A Practical Approach to Process Improvement (ASQ Quality Press), a senior member of ASQ, senior member of SME, cofounder and past chair of ASQ’s Lean Enterprise Division, and a member of the Lean Certification Oversight and Appeals Committee. He is Lean Bronze Certified. He can be reached at anthony.manos@proferoinc.com. Sections 1.1.2. Humility 1.3.5. Coaching & Mentoring 2.2.1.1. 5S Standards and Discipline 3.2.2. Policy Deployment/Strategy Deployment 4.3.5.1. Customer Satisfaction Brian H. Markell is president of BMA in Cherry Hill, New Jersey, and St. Albans, Hertfordshire, England. He has an engineering degree from the University of Sussex, England. Brian is certified with the Chartered Institute of Management Accountants (CIMA) in London, the American Institute of Certified Public Accountants (AICPA), and the Institute of Management Accountants (IMA). He is a Fellow of the American Production and Inventory Control Society (APICS). Brian is the author of eight books, including Making the Numbers Count: The Accountant as Change Agent on the World Class Team (second edition) and Practical Lean Accounting: A Proven System for Measuring and Managing the Lean Enterprise (second edition). He can be reached at bmaskell@maskell.com Section 4.2.1.5. Lean Accounting Timothy F. McMahon is the founder of and a contributor to A Lean Journey Blog (http://aleanjourney.com). He has a BS in chemical engineering from the University of Massachusetts and holds a Lean Certification and Six Sigma Black Belt from Central Connecticut State University. Tim is a member of the regional board of directors for AME and currently serves as the VP of program for northeast region. He can be reached at Tim@aleanjourney.com Sections 1.3.1. Cross Training 1.3.3. Instructional Goals 1.3.6. Leadership Development 1.3.7. Teamwork 1.3.8. Information Sharing (Yokoten) 1.3.9. Suggestion Systems 2.2.14. Pull System 2.3.6. Organizing for Improvement 2.3.6.1. Kaizen Blitz Events 2.3.7. Countermeasure Activities 2.3.7.1. Mistake and Error Proofing (Poka Yoke) 2.3.7.2. Quick Changeover/Setup Reduction (SMED) 2.3.7.3. One Piece Flow 2.3.7.4. Right Sized Equipment 2.3.7.5. Cellular Flow 2.3.7.7. Material Signals (Kanban) Dr. Mark W. Morgan is the associate vice president for institutional effectiveness and research at Seminole State College of Florida. Mark earned his doctorate in educational leadership from the University of Florida and is a three-time examiner for the Malcolm Baldrige National Quality Award. Mark was an improvement consultant for Fortune 500 companies for more than 10 years and is the author of three books on measurement and performance improvement, including his latest, The Path to Profitable Measures: 10 Steps to Feedback That Fuels Performance (ASQ Quality Press). Section 4.1. Principles of Business Results Frank Murdock is senior process engineer at Plymouth Tube Company in West Monroe, Louisiana. He earned a BS in engineering science at Purdue University, an MS in applied mathematics at the University of Michigan, and an MS in industrial engineering at Wayne State University. Frank spent 28 years with the Ford Motor Company, 8 years as an independent consultant, and 6 years as an adjunct professor at Lawrence Technological University. A senior member of ASQ and an ASQ Certified Six Sigma Black Belt, Frank is chair-elect for the Lean Enterprise Division as well as chair of the ASQ Voice of the Customer Committee. He can be reached at fmurdock@plymouth.com. Section 4.2.1.6. Voice of the Customer Mike Osterling has been a lean management practitioner and leader since the mid-1990s and is the lead consultant at Osterling Consulting, a San Diego–based firm. He earned an MBA in international business at San Diego State University and a BS in production and operations management. Mike coauthored The Kaizen Event Planner: Achieving Rapid Improvement in Office, Service, and Technical Environments. He is a certified trainer for the implementation of lean manufacturing (University of Kentucky) and a Lean Six Sigma Black Belt (University of California San Diego). He is certified in production and inventory management (APICS). He can be reached at mike@mosterling.com. Sections 2.1.5. Jidoka 2.1.7. Seek Perfection Mark Paulson is a quality manager for CDI in Minneapolis, Minnesota. He holds a Bachelor of Science degree in business administration. Mark is a senior member of ASQ, president of the Association for Manufacturing Excellence (AME); North Central Region, former Minnesota Quality Award examiner/team leader, approved trainer for Bronze Lean Certification refresher class and associated exam, and member of the Lean Certification Oversight and Appeals Committee. He is an ASQ Certified Manager of Quality/Organizational Excellence, Quality Engineer, Quality Auditor, and Bronze Lean Certified. Sections 2.1.4. Scientific Thinking 2.1.4.1. Stability 2.1.4.2. Standardization 2.1.4.3. Recognize Abnormality 2.1.4.4. Go and See 2.1.5. Jidoka 2.1.5.1. Quality at the Source 2.1.5.2. No Defects Passed Forward 2.1.5.3. Separate Man from Machine 2.1.5.5. Self-Detection of Errors to Prevent Defects 2.1.5.6. Stop and Fix 2.1.7.1. Incremental Continuous Improvement (Kaizen) 2.1.7.2. Breakthrough Continuous Improvement (Kaikaku) Robert (Bob) Petruska works as a performance improvement consultant in Charlotte, North Carolina. He has a Master of Science degree in manufacturing systems from Southern Illinois University. Bob is a senior member of ASQ and a CSSBB. Bob is authoring a book titled Gemba Walks for Service Excellence: The Step-by-Step Guide for Identifying Service Delighters, to be published in 2012 by Productivity Press. Sections 3.2.1. Enterprise Thinking 3.2.1.1. Organize around Flow 3.2.1.2. Integrated Business System and Improvement System 3.2.1.3. Reconcile Reporting System 3.2.1.4. Information Management Govind Ramu is a senior manager for global quality systems for SunPower Corporation. Prior to this role, he was Six Sigma Master Black Belt for JDS Uniphase Corporation. Govind is a professional engineer (mechanical) from Ontario, Canada, and an ASQ Fellow. He holds six ASQ certifications. Govind has had articles published in Quality Progress and in the Six Sigma forum. He coauthored ASQ’s The Certified Six Sigma Green Belt Handbook, for which he received the ASQ Golden Quill Award in 2008. Additionally, Govind was a 2006 and 2011 examiner for the California Awards (CAPE) and a 2010 examiner for the Malcolm Baldrige Award. He can be reached at ramu.govind@gmail.com Sections 2.1.5.1. Quality at the Source 2.1.7.1. Incremental Continuous Improvement (Kaizen) 2.2.9. Continuous Improvement Process Methodology 2.2.9.1. PDCA 2.2.9.2. DMAIC 2.2.9.3. Problem Solving Storyboards 2.2.10. Quality Systems 2.2.11. Corrective Action System 2.3.3.3. Failure Mode and Effects Analysis 2.3.4. Presenting Variation Data 2.3.4.1. Statistical Process Control Charts 2.3.4.2. Scatter and Concentration Diagrams 2.3.5.2. Quality Function Deployment 2.3.5.4. Design for Product Life Cycle (DFx) – Cradle to Cradle 2.3.5.6. Design for Manufacturability Rama Shankar is the managing partner at Delta Management Associates in Glenview, Illinois. She has a master’s degree in engineering management from Northwestern University and a master’s degree in materials management from Indian Institute of Materials Management, India. Rama is the author of Process Improvement Using Six Sigma: A DMAIC Guide (ASQ Quality Press). She is a senior member of ASQ and a past chair, section director, and training institute director of the ASQ Chicago Section. Rama is a past Malcolm Baldrige Award examiner, an ASQ CSSBB, and a CQA. She is also a certified trainer by NIST for lean. Sections 2.1.5. Jidoka 2.1.5.1. Quality at the Source 2.1.5.2. No Defects Passed Forward 2.1.5.3. Separate Man from Machine 2.1.5.4. Multi-Process Handling 2.1.5.5. Self-Detection of Errors to Prevent Defects 2.1.5.6. Stop and Fix With Tim McMahon 1.3.2. Skills Assessment 1.3.4. On-the-Job Training 1.3.6. Leadership Development 1.3.7. Teamwork With Govind Ramu 2.2.9.1. PDCA 2.2.9.2. DMAIC 2.2.9.3. Problem Solving Storyboards 2.2.11. Corrective Action System 2.2.11.1. Root Cause Analysis 2.2.12. Project Management 2.3.2. Data Collection and Presentation 2.3.2.1. Histograms 2.3.2.2. Pareto Charts 2.3.2.3. Check Sheets 2.3.3. Identify Root Cause 2.3.3.1. Cause & Effect Diagrams (Fishbone) 2.3.3.2. 5-Whys 2.3.3.3. Failure Mode and Effects Analysis 2.3.4. Presenting Variation Data 2.3.4.1. Statistical Process Control Charts 2.3.4.2. Scatter and Concentration Diagrams Gregg Stocker is an operational excellence advisor at Hess Corporation in Houston, Texas. He earned an MBA from the University of Houston and a BA from Michigan State University. Gregg is the author of Avoiding the Corporate Death Spiral: Recognizing & Eliminating the Signs of Decline (ASQ Quality Press). He is a certified purchasing manager from the Institute for Supply Management. He can be reached at gstocker1111@gmail.com Sections 2.2.4. 3P Production Process Preparation 2.2.13. Process Design 3.1.1. Systemic Thinking 3.1.2. Constancy of Purpose 3.1.3. Social Responsibility 4.2.2. Goal and Objective Setting Chad Vincent is a lean manufacturing specialist with Greif in St. Louis, Missouri. He earned a BS in engineering management from Missouri University of Science and Technology. Chad is a senior member of ASQ and SME, and the current ASQ Lean Enterprise treasurer. He serves on the Lean Certification Oversight and Appeals Committee. Chad is a CQE, CRE, CMQ/OE, CSSBB, and Lean Bronze Certified. He can be reached at chadvincent88@gmail.com. Sections 2.1. Principles of Continuous Process Improvement 2.1.2.2. 7 Wastes (Muda), Fluctuation (Mura), and Overburden (Muri) (with David Foxx) 2.1.5.1. Quality at the Source (with Govind Ramu and Mark Paulson) 2.1.5.3. Separate Man from Machine 2.1.6. Integrate Improvement with Work 2.1.7. Seek Perfection 2.2. Continuous Process Improvement Systems 2.2.2. Lot Size Reduction 2.2.3. Load Leveling 2.2.4. 3P Production Process Preparation 2.2.10. Quality Systems 2.2.10.1. ISO and Other Standards 2.2.11. Corrective Action System 2.3. Continuous Process Improvement Techniques & Practices 2.3.1. Work Flow Analysis 2.3.1.1. Flowcharting (with John Kendrick) 2.3.1.2. Flow Analysis Charts (with John Kendrick) 2.3.1.3. Value Stream Mapping 2.3.1.4. Takt Time Analysis (with Matt Maio) 2.3.8. Supplier Processes External 2.3.8.1. Supplier Managed Inventory 2.3.8.2. Cross-Docking 2.3.8.3. Supplier Assessment and Feedback 2.3.8.4. Supplier Development 2.3.8.5. Supplier Benchmarking 2.3.8.6. Logistics 2.3.9. Supply Processes Internal 2.3.9.1. Material Handling 2.3.9.2. Warehousing 2.3.9.3. Planning and Scheduling 4.3. Key Lean Related Measures 4.3.1. Quality 4.3.1.1. Rework 4.3.1.2. First Pass Yield 4.3.3. Cost 4.3.3.1. Inventory Turns 4.3.3.2. Queue Time 4.3.3.3. Wait Time (delays) 4.3.3.4. Overall Equipment Effectiveness (OEE) 4.3.3.5. Changeover Time 4.3.4. Financial Impact 4.3.4.1. Cash Flow Pat Wardwell is the chief operating officer at Greater Boston Manufacturing Partnership 2 in Boston, Massachusetts. She holds a BA from the University of Maine and an MBA from Bentley College. Pat is the coauthor of e-Continuous Improvement System. Her accomplishments include SME Lean Gold Certified, past chair of the Lean Certification Oversight and Appeals Committee, Shingo Prize recipient and examiner, AME Manufacturing Excellence Awards committee member and examiner, AME Northeast Board of Directors, and member of SME Boston Chapter Leadership Committee. She can be reached at pwardwell@gbmp.org. Sections (with Bruce Hamilton) 2.1.2. Identification & Elimination of Barriers to Flow 2.1.2.1. Flow & the Economies of Flow 2.1.2.3. Connect & Align Value Added Work Fragments 2.1.2.4. Organize around Flow 2.1.2.5. Make End-to-End Flow Visible 2.1.2.6. Manage the Flow Visually 2.3.7.1. Mistake and Error Proofing (Poka Yoke) 2.3.7.4. Right Sized Equipment 2.3.7.5. Cellular Flow Jerry M. Wright, P.E., is the senior vice president of lean and enterprise excellence for DJO Global in Vista, California. He earned an MBA in 2002 from the University of Phoenix and is a registered professional engineer in the state of California. He is the annual international conference chair for AME for Chicago in 2012 and also a west region director for AME. He is also the chair of the So Cal Lean Network, an affiliation of more than 75 companies focused on lean and sharing in Southern California, as well as a Shingo Prize examiner and a previous Baldrige Award examiner. He can be reached at jerry.wright@djoglobal.com. Sections 3.3.1. A3 3.3.2. Catchball 3.3.3. Redeployment of Resources EDITORS Anthony Manos is a catalyst with Profero, where he provides professional consulting services, implementation, coaching, and training for a wide variety of organizations (large and small, private and public) in many industries focusing on lean enterprise and lean healthcare. Tony has extensive knowledge of lean and quality in a wide range of work environments. He is trained and certified by the National Institute for Standards and Technology (NIST) U.S. Department of Commerce in all elements of lean manufacturing. Tony also is a lean champion for 5S Supply. Relying on his diverse knowledge of business, manufacturing techniques, and applications, Tony has assisted numerous clients in implementing a lean enterprise and lean healthcare. Over the past 10 years, he has helped over 150 companies in several aspects of lean implementation, including team building, standardized work, 5S workplace organization and visual workplace, quick changeover, plant layout, cellular, Kanban, total productive maintenance, kaizen events, and hoshin planning. Tony is an internationally recognized speaker and expert on lean and presents at several conferences a year. As an ASQ faculty member, he teaches a two-day course in lean enterprise and a one-day course on kaizen. Tony is the past chair of the Lean Enterprise Division of ASQ. He is a senior member of SME and a member of AME. Tony is coauthor of the book Lean Kaizen: A Simplified Approach to Process Improvement and author of many articles on lean and its allied subjects. He serves as an ASQ representative to the Lean Certification Oversight and Appeals Committee. Tony is Lean Bronze Certified and was part of the original team to develop the Lean Certification. Tony served in the US Navy nuclear propulsion program. He holds an MBA from the University of Illinois at Chicago. Chad Vincent is a lean manufacturing specialist and corporate operational excellence team member with Greif, Inc. in St. Louis, Missouri, where he provides professional guidance, facilitates implementation, and coaches and trains personnel at manufacturing facilities on lean enterprise and operational excellence. Prior to Greif, he worked as a quality engineer in the medical device field and as a project engineer in the construction industry; he also has worked in management in the logistics and transportation industry. Chad has served as a senior lead examiner and judge for the Governor’s Quality Award (Arkansas’ equivalent of the Malcolm Baldrige National Quality Award) and is past president of the Leadership Arkansas Alumni Association Board of Directors. Chad is an advocate for ASQ’s Socially Responsible Organization (SRO) Initiative and a member of SME’s Lean to Green Committee. He has written articles, such as “Back in Circulation” for Quality Progress, on the utilizing of lean to achieve socially responsible and environmentally favorable results within organizations and on defining the 8 Green Wastes for environment, health, and safety (EHS) professionals to apply lean in their areas of expertise. He is a voting member of the US Technical Advisory Group (TAG) for the ISO 26000 Guidance for Social Responsibility. Chad earned a BS in engineering management, specializing in quality engineering, from the Missouri University of Science and Technology, in Rolla, Missouri. He is a senior member of ASQ and SME, and is currently the ASQ Lean Enterprise treasurer and serves on the SME/AME/Shingo/ASQ Lean Certification Oversight and Appeals Committee. Chad is a CQE, CRE, CMQ/OE, and CSSBB, and he is Lean Bronze Certified. Module 1 Cultural Enablers 1.1. Principles of Cultural Enablers 1.2. Processes for Cultural Enablers 1.3. Cultural Enabler Techniques and Practices Culture is the widening of the mind and the spirit. —Jawaharlal Nehru The first section of the Lean Body of Knowledge is dedicated to culture. Although lean is about the tools, it is more about creating a culture of people who truly believe in continuous improvement. This portion of the book focuses on what it takes to create, change, and lead an organizational culture into operational excellence. There is no lean without people. This section explores the importance of leading with humility, showing respect for people, having a well-crafted plan with a sense of urgency, and developing the people and leaders in your organization. 1.1 Principles of Cultural Enablers A ccording to Pascal Dennis (2007, 145); author of Lean Production Simplified; “Intensity is the soul of lean production, and team members are its heart” In other words, people are the most critical element of lean production, and the culture the team members create is the major source of fuel required to propel lean systems forward in any organization. In a vast majority of cases, the success or failure of any lean, Six Sigma, or other corporate initiative will depend on the people who execute it rather than on any equipment, consultant, software, or other tools and techniques. Thus, organizations that consider people as the prime appreciating asset and invest adequate time, effort, and money in hiring and developing the right people will get unmatched results (Dalal 2011, 584). What Is a Culture? A culture is the sum total of all behaviors, relationships, comprehension, and interactions that fuel overall alignment via collective thoughts, words, and actions. What Is a Lean Culture? Lean is an approach to improve quality, increase productivity, reduce costs, and increase customer satisfaction by eliminating waste and creating value. A lean culture is the sum total of all the lean tools, techniques, and knowledge that exist within an organization at the root level and that fuel the overall organizational alignment via collective lean thoughts, words, and actions toward the elimination of waste and the creation of value. Organizations that have a strong lean culture do two things: 1. They promote at least five key cultural enablers (safety, standards, leadership, empowerment, and collaboration), which allows the lean culture to exist 2. They build their business on the core fundamentals of respect for individuals An Example of a Strong Lean Culture The consistent growth, prosperity, innovation, and operational excellence of Toyota are clearly results of the Toyota Production System (TPS), which is built on the foundation of a strong and dynamic culture and sophisticated “human systems” consisting of highly motivated and well-trained people in plants, dealerships, and offices around the globe. In Toyota Culture, authors Jeffrey Liker and Michael Hoseus (2008) explain Toyota’s fourstage process for building and keeping quality people: attract, develop, engage, and inspire. The “people-centric” culture of Toyota is carefully designed by:  Finding competent, able, and willing employees  Beginning the training and socializing process as they hire the people  Establishing and communicating key business performance indicators at every level of the organization  Training the people to solve problems and continuously improve processes in their daily work  Developing leaders who live and teach your company’s philosophy  Rewarding top performers  Offering help to those who are struggling (Liker and Hoseus 2008, 44) What Is a Cultural Enabler? Just as a sapling requires critical factors like the right soil, adequate sunlight, and water to survive and grow into a strong tree, culture requires factors that allow it to stabilize and pervade throughout the organization. These factors are known as cultural enablers. Cultural enablers are critical to the people on the journey of building a culture of operational excellence within an organization. What Constitutes as Cultural Enablers of a Lean Culture? Cultural enablers of a lean culture include the basic principles of safety, standards, leadership, empowerment, and collaboration. Basic Principles of Safety There are only two types of organizations: safe or lucky. Safety is the prime cultural enabler, as only safe environments can be productive and profitable. Lean organizations believe that merely adhering to all requirements of the Occupational Safety and Health Administration (OSHA) is not sufficient in order to have a safe working environment. The following two principles are engrained in the culture of lean organizations: 1. Safety is the responsibility of every employee within the organization 2. A proactive versus a reactive approach is required in order to create and maintain a clean, safe, ergonomic, and sustainable work environment Lean organizations realize that to attain all-encompassing safety standards, they must focus on education and awareness in safety practices related to people’s health and wellness, and interface with people and equipment and environmental aspects. Personal Safety Personal safety focuses on security and protection from accidents, injuries, fire hazards, equipment malfunction, and any other aspect threatening the health and well-being of every individual in the organization. Fatigue Prevention Fatigue results from a poorly designed workplace, work environment, tools, equipment, and policies and procedures. Practicing workplace ergonomics, which optimizes the comfort of employees while they are interacting with all the elements of their workplace, is the key to reducing fatigue and increasing employee efficiency. Environmental Safety Environmental safety involves reducing the carbon footprint of products and processes on the surrounding environment. It encompasses product and process design from cradle to grave, including use of environmentally conscious raw materials, supplies, and packaging materials requiring minimal transportation and minimal waste, along with proactive implementation of recycling or reuse programs. Some top enablers for creating a culture of safety are the following:  Focus of top leadership Organizational emphasis on safety Clearly defined organizational structure  Clearly defined lines of authority and accountability  Unambiguous communications  Trust and engagement  Ability of organization to learn from failures  Safety training and sharing of lessons learned Some top barriers for creating a culture of safety are the following:     Lack of support from top leadership Minimal emphasis or pseudo-emphasis on safety A culture of blame and retribution Lack of training or sharing of lessons learned Basic Principles of Standards Standards are baselines from which improvements can be easily measured. All standards related to safety, communications, operations, human resources, policies, procedures, and tasks need to be standardized across the entire organization. Standardization is not static but dynamic and requires continuous improvement using the Plan-Do-Check-Act model of the Deming cycle (ASQ). Taiichi Ohno is credited with saying, “Where there is no standard there can be no kaizen” Thus, a standard is “the best known method/process/system at a particular point of time” and is a dynamic point of reference that becomes the baseline for future improvements. Every continuous improvement activity must result in the establishment of a new standard. This “new standard” may require establishing a new standardized work sequence, recalculating takt times and establishing new inventory levels, updating visual work instructions, and setting new inspection or quality control standards. According to Masaaki Imai (1997, 54–56), author of Gemba Kaizen, standards have the following key features:  Represent the best, easiest, and safest way to do a job Offer the best way to preserve       the know-how and expertise Provide a way to measure performance Show the relationship between cause and effect Provide a basis for both maintenance and improvement Provide objectives and indicate training goals Provide a basis for training Create a basis for audit or diagnosis Provide a means for preventing recurrence of errors and minimizing variability Basic Principles of Leadership Without support from the top leaders and executives, lean initiatives cannot survive in an organization. The leader is not only required to support lean initiatives in good times but also required to show persistence and constancy of purpose during tough times. The leader needs to develop a clear vision for lean, communicate it effectively to his or her employees, and empower them to adopt it as their own mission. Thus, leadership is the key cultural enabler that determines whether lean is established as a culture in the organization. Good leaders understand that in an environment of continuous improvement, failures are imminent. But rather than blame people for failures, they ask “why” five times, approach the problem, and create a plan to strengthen the people (Dennis 2007, 130). According to Dalal (2011, 471–85), there are three types of failures: 1. System level failures 2. Process level failures 3. Human level failures Great lean leaders avoid focusing on the human level failures, as this would create an environment of fear, distrust, and a culture of risk aversion lacking creativity and innovation. Instead, great lean leaders:        Focus on system failures (“why”) Spend more time to prevent the failure Believe that 80% of the failures are avoidable by 20% of planning Perform root cause analysis to prevent failures Implement dynamic risk assessment to identify and plan for failures Use Plan-Do-Check-Act cycle to prevent failures Establish a creative and open environment for lessons learning (Dalal 2011, 471–85) Figure 1.1-1 shows a representation of an empowered culture of trust created by leaders using these techniques. Basic Principles of Empowerment A Japanese saying alludes to the fact that a statue of Buddha will not mean much without putting a soul in it (Imai 1997, 242). The soul of a lean organization is employee empowerment. The prime responsibility of a leader in a lean organization is to develop effective problem solvers and decision makers. The only way a leader can achieve an empowered workforce is by helping to set a vision and relinquishing some authority in order to allow the capable employees to make decisions and influence corporate policies. Empowered employees get to the depths of understanding of lean technology and go beyond the know-how of lean and experience and apply lean with a deeper understanding of the know-why. Thus, lean leaders rely on their empowered employees to optimize the benefits of lean initiatives, ensuring superior levels of customer satisfaction. Employee empowerment must be done in six steps: Step 1: Leaders make a commitment to have an engaged workforce Step 2: Roles and responsibilities are clearly defined Step 3: Training is conducted for managers, supervisors, staff, and shop-floor personnel Step 4: Training is conducted for all administrative and support staff Step 5: A formal idea-suggestion or idea-sharing program that involves all employees is implemented Step 6: Action is taken to assign responsibility and accountability Basic Principles of Collaboration The cultural enabler “collaboration” is the backbone of lean. Lean initiatives do not depend on the knowledge of one but achieve breakthrough results due to the deployment of the collective wisdom of many. In lean organizations, collaboration exists across:  Various functions  Different departments  Staff and union workers and even between executives and operators Collaboration and partnerships extend beyond the four walls of the organization and include suppliers, contractors, and, in some cases, competitors. By design, lean tools allow for a collaborative culture throughout the organization. Nemawashi, A3 form, kaizen events, and several other lean tools are designed for automatic collaboration. 1.1.1. RESPECT FOR THE INDIVIDUAL One of the most critical aspects of lean cultures is the inherent importance placed on valuing individuals and treating each individual with dignity. In lean organizations, respect starts with the top leaders and permeates throughout the organization. However, “respect for every individual” does not end at the four walls of the organization; rather, it extends to all customers, suppliers, and stakeholders, including the community in which the organization does business. Respect allows the lean culture to achieve the following goals:  Create a culture of cohesive teamwork Create a culture of continuous improvement Increase employee involvement  Empower employees  Encourage diversity A key requirement and an underlying quality required by employees of lean organizations is humility. Leaders and employees all practice humility as a technique that allows the process of continuous improvement to go on via open collaboration. In lean cultures, everyone is open to learning from one another and to raising their game incrementally on a daily basis in order to generate superior value and increase customer satisfaction. The key traits of a humble environment are as follows:      An open learning environment People form a critical element of the value stream A long-term relationship based on mutual loyalty A mentor-mentee, sensei-student relationship throughout the organization Lack of discrimination throughout the organization and the entire supply chain Thus lean organizations and their leaders focus on operational excellence via a peoplecentric approach by ensuring an empowered, safe, and collaborative environment based on standards and a philosophy of a wholehearted pursuit of long-term excellence. 1.1.2. HUMILITY Humility leads to strength and not to weakness. It is the highest form of self-respect to admit mistakes and to make amends for them. —John J. McCloy Humility ties in directly with respect for the individual (see Section 1.1.1, “Respect for the Individual”). Humility is considered the quality of being modest, unassuming in attitude and behavior. It also can be taken as feeling or showing respect and deference toward other people. Don’t think of humility in the lean sense as being meek, shy, and timid or of lesser value. Of course, the opposite of being humble is being arrogant, overconfident, condescending, or egotistical or displaying hubris. Humility is a principle that enables the people in your organization to learn, improve, and excel. Consider two types of humility: personal humility and leading with humility. This approach helps us understand what it takes to develop our own personal style, along with the similarities and differences in leading people. Personal Humility Personal humility can be thought of as having pride (not boastful), self-respect, and dignity. These traits are created over the years with a commitment to integrity, honor, and pursuing lifelong learning. Being humble means that you understand that you don’t know everything and can continually learn from those around you. As you learn, you improve. This also involves understanding your strengths and weaknesses. Understanding your strengths allows you to be a better team member, as you bring certain skills to your workplace. Appreciate your weaknesses (or opportunities for improvement) so you can continually develop and progress as a person. Another important role of humility includes being able to accept personal responsibility for your actions. Admit when something doesn’t go as planned. Hansei is a Japanese word that means “self-reflection” or to acknowledge a mistake and pledge to improve. It is perfectly acceptable to say, “I don’t know; let’s find out” Humility also includes being authentic to yourself and to others and staying true to your principles or virtues. Another important skill for fostering humility is to perfect your active listening skills and be present for the other person. Humility is also being mindful of others, in your thoughts, speech, and actions. In Stephen Covey’s The 7 Habits of Highly Effective People (1989, 235), habit 5 says to “seek first to understand, then to be understood” This is a classic example of showing your humility. By reserving your desire to jump in, speak up, and be heard and truly trying to understand the other person’s point of view you create a better relationship and find overall solutions to problems. In a way, humility can be thought of as living by the golden rule: Treat others as you would like to be treated. This leads to workplace satisfaction and gratification of a job well done. Leading With Humility Leading with humility is not only for the CEO or the president of your organization. Leading with humility should permeate all the way through the ranks to the level of the value-adder. At any one time, everyone has a chance to lead, from daily meetings or training to large-scale projects. Gary Convis (2011) tells of his mentor at NUMMI, Kan Higahsi, telling him his greatest challenge would be “to lead the organization as if I had no power” This is a sure sign of humility. In his book Good to Great, Jim Collins (2001) talks about Level 5 Leadership, of having personal humility and professional will. Table 1.1.2-1 shows a summary of Level 5 Leadership personal humility traits, adapted from the book. Leading by Deeds Building trust to become trustworthy as a leader starts with personal humility. Building trust can take time. Your words and actions demonstrate your ability to do what you say. An example of this is a leader who says that the customer comes first but then makes it difficult for the customer to contact him or her making the customer search a website for a telephone number or navigate lengthy phone menus that lead nowhere. As a humble leader, you will need to know how to be patient in developing your people. While there are always deadlines, proper planning, tapping into the creativity of your employees, and having the patience to stay the course will pay off dramatically as you create a more engaged workforce. Always make sure to give credit to others for their contributions to the success of the organization, and take personal responsibility for any letdowns. Learn how to shine the spotlight on others; let them shine in the eyes of the company. If you can learn how to talk to the CEO and the value-adding worker in the same way, you are developing the type of skills that will make you invaluable to your institution. As a leader, design your systems with respect and humility. Dwight Davis (2011), associate vice president of Utah State University, on the topic of leading with humility, says, “Humility is a key element in building teams, unifying organizations, unleashing employee capabilities, optimizing relationships, designing systems of accountability and achieving a culture of discipline. Humility simply enables individual and organizational learning and improvement” We come nearest to the great when we are great in humility. —Rabindranath Tagore REFERENCES    ASQ. “Project Planning and Implementing Tools” http://asq.org/learn-about-quality/project-planning-tools/overview /pdca-cycle.html Collins, Jim. 2001. Good to Great. New York: Harper Business. Convis, Gary. 2011. “Lean Leadership: The Toyota Way” Keynote speech at the AME       conference, Dallas, Texas. Covey, Stephen. 1989. The 7 Habits of Highly Effective People. New York: Simon and Schuster. Dalal, Adil. 2011. The 12 Pillars of Project Excellence: A Lean Approach to Improving Project Results. Boca Raton, FL: CRC Press. Davis, Dwight. 2011. “Lead with Humility, Respect Every Individual” Gemba Walkabout blog, October 17. http://gembawalkabout.tumblr.com/post/11595991420/lead-with-humility-respect-every-individual Dennis, Pascal. 2007. Lean Production Simplified: A Plain-Language Guide to the World’s Most Powerful Production System. 2nd ed. New York: Productivity Press. Imai, Masaaki. 1997. Gemba Kaizen: A Commonsense, Low-Cost Approach to Management. New York: McGraw-Hill. Liker, Jeffrey, and Michael Hoseus. 2008. Toyota Culture: The Heart and Soul of the Toyota Way – New York: McGraw-Hill http://www.lean.org/BookStore/ProductDetails.cfm?SelectedProductId=270 1.2 Processes for Cultural Enablers J ust as there are principles for cultural enablers, there are also processes. These processes are the ongoing systems and inherent culture of the organization as it continues to improve itself. 1.2.1. PLANNING & DEPLOYMENT There is an old saying that poor planning guarantees poor execution. It’s actually quite shocking how little time and effort companies put into planning their lean implementation. The more common approach is to simply choose a convenient tool, 5S being the most popular (see Section 2.2.1.1, “5S Standards and Discipline”), and apply it with a broad brush across the organization. Certainly this approach can have some positive results, but it is neither sustainable nor comprehensive. Good planning doesn’t guarantee good execution, but it gives you the best chance of success. Also, there should not be a “one plan fits all” approach. Every lean implementation should be designed on the basis of specific objectives and characteristics of the particular organization. Additionally, every plan should include at least three basic pillars as the foundation (see Figure 1.2.1-1). The first pillar is “quick and measurable improvement” It is obvious that the primary objective of any lean transformation is to significantly improve the performance of all critical measures. Lean isn’t implemented because it’s the nice thing to do for the business; it’s implemented because it is the right, and sometimes critical, thing to do for the business. Experience suggests that if the lean implementation is not providing significant returns in key performance indicators in the first 12–18 months, someone (usually in finance or accounting) will challenge both the relative effectiveness and the need for lean and decide that resources might be better spent elsewhere. Quick results can be achieved through kaizen events (rapid process improvement), targeted lean demonstration projects, or even some basic tool implementation aimed at quick wins. But be cautious that these relatively quick and measurable wins can become a crutch that limits further lean transformation. Be careful of your transformation becoming what is called “event lean” The second pillar, and absolute complement to the first pillar, is the development of a lean culture, embedding lean into daily behaviors. Culture is about shared and common principles, practices, and behaviors that will ultimately determine outcome. There is a very simple formula for pillar number two: principles (thinking) drive behaviors, behaviors drive action, and action drives results. Simply put, the desired thinking will get the desired results. There are two ways that lean thinking can be embedded into the organization. The first is through continued repetition. The messages and experiences simply cannot be repeated enough. Remember how you learned the multiplication tables in school? It was all repetition and it stayed with you for life. The second is through application. A principle or practice must be aggressively applied and applied in varying environments if there can be any expectation of embedding the behaviors. This can be accomplished by taking a slice (inch wide/mile deep) of the organization and deeply immersing it in the principles and practices of lean. Then, based on the lessons learned, expand throughout the organization, slice after slice. The third pillar is the principle of lean leadership. The decision makers in the organization, regardless of level, must be engaged in the lean transformation. This means they provide the direction, participate in the lean activities, provide some of the education, create the tension and need, and certainly exhibit the desired behavior. This can be accomplished through active engagement of leadership in the lean activities and by establishing some sort of lean management structure similar to a steering committee or leadership council. Ideally, the three pillars are implemented simultaneously, but this can be difficult to achieve, as identified in the next section. Any lean transformation requires, or should require, a framework for the implementation. Lean is a journey, and as with any journey, you need a roadmap (see Figure 1.2.1-2). Your roadmap’s route should be based on a series of issues and concerns that must be considered. A few examples include:  Business conditions; If the business is just trying to survive, you can forget culture. Just get quick results.  Baggage; Prior experiences cause people to carry around thinking that might affect implementation. For example, a prior failed continuous improvement implementation can create “program of the month” baggage.  Resources; The availability, or lack thereof, of resources to support the lean transformation will affect the pace of the implementation. Be very cautious of managing expectations.  Culture; A risk-adverse culture require assurances and safety nets. A frugal culture will require proof of return on investment. These and any other issues and concerns must be considered when developing the roadmap. Also consider designing the roadmap in phases and defining each of the following characteristics in each phase:         Objectives Application Education Tools and methods Communication Infrastructure Leadership Expected results The roadmap should be developed with three levels of varying detail. Level one generalizes the content of the roadmap for communication across the organization. It’s like a map that shows only the major cities and primary roads and thus has lots of white space. Level two provides enough detail for the area/department or even the entire organization to assess where it is on the lean journey and what it must do to advance. This is like adding the small towns and secondary roads to the map and provides more guidance and options. Level three is very detailed and provides the specifics for active implementation. This is like adding all the cities, towns, and communities and all the primary, secondary, and tertiary routes to the map. I can’t stress enough how important it is to develop a roadmap. A very well-known Fortune 500 company often benchmarked for its lean implementation openly admits that it did not develop a roadmap but should have. The company is developing one now after what it considers three false starts. How many false starts can you afford? 1.2.2. CREATE A SENSE OF URGENCY Creating a sense of urgency can be difficult in good times but is typically easy in bad times when the economy or business conditions are threatening survival. Futurist Joel Barker, in his video Tactics of Innovation, discusses five pairs of tactics to get someone to accept a new idea. In the video he makes it very clear that, when things are tough, the only tactics you need are Upside/Yes (there is a lot to be gained) and Downside/No (there is little to no risk). In tough times, it’s easy to get people to change just show them the numbers. However, most lean practitioners and leaders will be challenged to create a sense of urgency in an organization when it is doing well or when the employees believe that the organization is doing well. The real challenge is to overcome the belief that an organization needs to improve and improve significantly. Beliefs are embedded in the thinking of the organization. The way to change these beliefs is by building tension in the organization. Tension is not the same as stress. Whereas stress suggests a feeling of helplessness, tension is about recognizing the gap between where you currently are and where you would like to be. Very simply put, tension is about having a deep understanding of the current state and a well-defined vision of the ideal state. Tension can be used to improve a task, an entire process, or even an entire company by narrowing the gap. It all starts with a deep understanding of the current state. There are several means to both understand and document the current state:      Value stream mapping Detailed process mapping Direct observation Videotaping Data collection Regardless of the method used, the key is to understand the real current state not what is desired, not what is documented, but what is real. It is surprising how organizations almost always feel that their current state is better than what is discovered. One of the simplest means to relieve tension, relieve the sense of urgency, is to believe that things are better than they actually are. It’s simple but not helpful. Deeply understanding the current state is only half the formula. The other half is having a well-defined vision of the ideal state. Notice I did not say future state. Future states are simply intermediate gains. The ideal state is a step gain. There may be one or even more than one future state as you move toward ideal, but you must never lose sight of ideal. For example, one company may try to figure out how to fasten a nut and bolt faster (future state), while another company is trying to eliminate the need for the nut and bolt altogether (ideal state). On the surface it may sound difficult to define the vision of an ideal state, but it is actually quite simple. Simply develop a bulleted list of the ideal characteristics of an activity, a process, a department, or even a company. The only restriction is that it must be possible. You can’t violate the laws of nature or science. For example, one consumer goods company defined the ideal state for its warehouse receiving process as:       100% quality incoming parts Correct count (standardize lot sizes) Containerization (direct to line) Radio frequency Bar coding Just-in-time Nothing in the aforementioned ideal-state description is not possible, maybe very difficult but possible. For example, getting 100% quality from a supplier may be very difficult, but it is not outside the realm of possibility. Also, cost should never be considered when defining the ideal state. It might be a barrier that prevents achieving ideal, but it does not make the ideal state impossible. The likelihood of achieving the ideal state is low, especially because ideal is often a moving target. However, if you do not focus on the ideal, you will not make the big step gains, only incremental small gains. Remember, there may be one or more future states as you move toward ideal. A deep understanding of the current state and a well-defined vision of the ideal state will expose the organization to the gap and therefore create the tension, the sense of urgency. The next challenge is to simply identify and remove the barriers to achieving the ideal state. You will most likely not remove all barriers, but the more barriers you do remove, the closer you get to ideal. So, in summary, if you want to create a sense of urgency, follow these three simple steps: 1. Deeply understand the current state 2. Clearly define the ideal state 3. Narrow the gap between steps 1 and 2 1.2.3. MODELING THE LEAN PRINCIPLES, VALUES, PHILOSOPHIES Webster’s dictionary defines modeling as “to display by wearing, using or posing” That could not be a better definition for modeling lean. You must use it both in your professional practice and in your personal practice, and you must wear lean on your sleeve for others to see. It is about exhibiting through action and dialogue the lean thinking and behavior desired of others on a lean journey. Actions always speak louder than words, but both are in their own way a means to model lean behaviors. Waste elimination is the lifeblood of any lean implementation. It’s not enough to ask others to surface waste and then simply support their activities. Every individual, regardless of his or her level in the organization, must be involved in waste elimination. This means that every individual should be performing waste walks routinely and frequently. Develop a standard form for documenting the identified waste and a standard process for providing feedback or entering the suggestions into a structured waste elimination system. Waste walks can be done individually or in teams. It’s preferable, however, to do the waste walks in cross-level and cross-functional teams for two reasons. The first reason is the obvious visibility. The second reason is the opportunity to dialogue. In fact, you will find that the real value and opportunity to model lean is not in the actual application of lean tools (waste walks, 5Ss, process maps, etc.) but in the dialogue that is required to plan and implement the tool. You must be a teacher. Simply subrogating the teaching, either formally or informally, to others is unacceptable. This doesn’t mean just standing in front of a classroom. The transfer of skills and knowledge is too important not to share on a daily basis. While this can be about actually scheduling time to teach, it’s more about taking advantage of situations that could be teaching moments. It might be helping to solve a problem, implementing a tool, resolving a crisis, or responding to any other situation that is a candidate for a lean solution. These teaching moments occur routinely in the daily practices of the organization. You can’t expect a signal (andon) when a teaching moment surfaces. You must seek out these opportunities. There must be an environment for learning. The lean transformation will require experimentation, action, and new thinking. In many cases these activities may involve risk. The challenge is to create an environment to encourage and support experimentation and new thinking. Learning occurs when people are asked to step out of their comfort zone. This doesn’t mean chaos and unorganized change. Stepping out of the comfort zone must be purposeful by setting clear goals and providing effective mechanisms. When people step too far out of their comfort zone, they enter their fear zone. So, in addition to minimizing their comfort zone, you must also eliminate fear. You must provide physical, emotional, and professional safety. If an individual is ridiculed for making a suggestion, you can fully expect that he or she will not venture beyond his or her comfort zone. Regardless of the validity of the idea, it should be a teaching and learning moment, not a moment of embarrassment. Simply proclaiming support of the lean transformation is not enough. Both active and visible participation are required. Support is easy; participation is far more difficult. Back in the early 1990s one of the big three auto companies had its first kaizen event. A member of that kaizen team was the president of the company. He was in jeans and a company Tshirt and came ready to do whatever was asked of him that entire week. Twenty years later that experience still resonates through the organization, even though that president is long gone. The right “model” is not about watching from the sidelines; it’s about active engagement. It’s about committing the time to actively participate. Maybe it is waste walks as mentioned earlier. Or it could be a kaizen event, problem solving, building process maps, or implementing lean tools. This is certainly a case where actions speak louder than words. Lean must also be part of everyone’s daily activities. It is not about others applying lean. It’s about every individual applying lean to his or her self. It’s about individuals aggressively applying lean to daily job functions by developing clearly structured processes for how they perform work and how they spend their time. This can manifest itself in many ways. Performing 5S in your own area is an obvious and simple answer, but it is far more comprehensive than that. Is there scheduled and structured time for reflection? Do you follow a structured problem-solving model? Do you look for the opportunity and the time to teach or coach others? Do you schedule certain critical activities and never vary? Are you auditing the lean implementation? There are likely many more examples of how individuals can model lean principles, values, and philosophies, but it all comes down to two things: (1) exhibit the behavior you desire of others and (2) encourage and participate in the dialogue to develop lean thinking. 1.2.4. MESSAGE DEPLOYMENT-ESTABLISHING VISION AND DIRECTION In their book, Fail-Safe Leadership, Martin and Mutchler (2003) use the analogy of a game of tug-of-war. In this game, two teams are placed at opposite ends, each holding one end of a rope. The objective is to pull the middle of the rope over a line. On one side, the team members are lined up and ready to pull in the same direction. On the other side, the team members are disorganized and ready to pull the rope in different directions. Which team do you think will win? Obviously the team that is aligned and pulling in the same direction will win. What does this have to do with message deployment? Everything! It all starts with the development of the vision, or direction, for the organization. More specifically, in the context of this handbook, what is the vision of the organization’s lean system? What will be the driving force? Perhaps it is. “To eliminate waste and improve customer focus” Or, “To align our processes with the customers’ needs and eliminate waste, while achieving Shingo recognition” The message has to fit your organization. To achieve any vision, the organization must be aligned. One obstacle typically encountered on any lean journey is the fear that doing things right the first time and faster will result in cutbacks or layoffs. The emergence of this fear is a direct result of the vision and message deployment. The lean vision should not focus on the reduction of personnel but rather on the leveraging of those resources now available to grow. Growth can be in skills, new product lines, reduced overtime, and so on. Martin and Mutchler (2003) prescribe clear methods to achieve fail-safe leadership, but key to lean is the alignment described as ensuring that, top to bottom, every employee understands the vision and has goals that directly relate to results. Their model is shown in Figure 1.2.4-1. In the lean journey, this approach, or a similar approach, will ensure that the organization is aligned and that all functions are striving for the same results. The vision is established at the top and communicated across the organization through meetings, webinars, and webcasts or by any other effective means. Be wary of just making posters, hanging them up, and expecting the vision to be achieved this is not communication or message deployment. Allowing for personal interaction and holding question-and-answer sessions will help with alignment. After the vision is defined, strategies, goals, actions, and measures are established. Measures are not always needed and are typically driven by the organization’s culture and size; however, they are helpful in ensuring alignment and fact-based decisions regarding progress. These are established at a level where they are functional to personnel and need to be reviewed to ensure they do not conflict – remember the tug-of-war – from one function to the other. For example, a facility may want to lower electricity costs by shutting down the lights and the heating system at night, but production may want to operate some machines at night to perform maintenance. Personnel will establish goals and actions that align with functional goals and strategies (critical success factors). To achieve this message, deployment has to occur not only for the vision but also for the functional level, after strategies and functional goals or actions are reviewed to ensure there are no conflicts with other functions. This is an investment in time and energy that pays rapid dividends through everyone pulling the rope in the same direction at the same time. Developing the vision at the top, then, involves more levels as each successive item that works in the organization is defined. In other words, don’t change how you do things to fit the model above, but use the model within the organization’s system to ensure alignment and results. Involve appropriate subject matter experts and formal and informal leaders to define the functional goals, actions, and measures. Communicate the overall vision and functional goals to all levels. Ensure each person has goals and actions (one to three is the norm) that align with the overall vision and the function in which he or she works. Check and communicate progress regularly and make adjustments when necessary. Use the checks to ensure continued alignment. Stress the importance of achieving the vision and the benefits. Commit to the lean journey and ensure that it has little or no impact on staffing levels and that it is used to grow skills, people, and business results. 1.2.5. INTEGRATING LEARNING AND COACHING To help the organization shift to a lean culture, learning and coaching must be part of the equation. Learning allows for the sharing of knowledge, personnel growth, removal of barriers, and the demonstration of leadership commitment. Coaching is a method used to enable learning and improvement. Integrating these into the planning and deployment, along with sustainment, provides continual benefits through improved morale, execution, idea generation, and retention. All personnel, from individual contributors to executive leadership, must be involved with the learning process. A key concept of learning is to ensure continual application of the knowledge gained. In other words, once personnel learn a skill or gain knowledge, there should be an established expectation that that skill or knowledge is applied regularly in support of organizational and lean objectives. As part of the lean culture shift and integrated learning, there will be formal and informal learning. Formal learning includes goal setting, teaching or facilitation (classroom, webbased, etc.), verification of knowledge gain (completion of exercises, case studies, testing, projects, etc.), and reinforcement of knowledge gain (a knowledge check following completion of the learning experience). Informal learning includes on- the-job training and coaching and mentoring. Formal learning is structured to account for adult learning styles and needs. A formal learning process includes the following:      Stated objectives Lesson plans Formal verification of knowledge gain Knowledge check Optional qualification or certification Lean Bronze Certification, through the Society of Manufacturing Engineers (SME), the Association of Manufacturing Excellence (AME), the Shingo Prize, and the American Society for Quality (ASQ), is an example of formal learning. Organizations develop their own formal learning with a focus on their implementation of lean. Learning is usually broken down to meet different objectives of awareness, execution, project leadership, and program design. This learning may also include subsets within execution and project leadership based on the expectation (e.g., Lean Bronze, Silver, and Gold or Six Sigma Green Belt, Black Belt, and Master Black Belt). Not all learning is performed at one time, nor is all learning developed at the same level of difficulty, time invested, and length of course. As the lean culture shift starts, all personnel receive lean awareness training, but those leading the initiative receive more in-depth training. Lean awareness training explains the organization’s goals of lean, leadership’s commitment, what will occur, how it impacts personnel, expectations for personnel involvement, top-level training, deployment schedules, and so on. This awareness training should emphasize that the goal of a lean culture is to execute smarter, eliminate waste, and grow skills and capability it is not intended as a program that reduces the workforce. Reduction in personnel is typically a major workforce concern, and thus leadership must emphasize that it is not a goal or intention. In formal training, on-the-job training is done at the lowest levels possible. It usually has top-level goals (e.g., ensure new hire can operate machines in work area effectively and efficiently) but no set agenda, timeline, and so on. It may have some level of competency testing, but it is usually completed when the trainer believes the trainee is able to execute correctly, safely, and efficiently. In formal training, that critical knowledge transfer from one employee to another is something lean wants to leverage throughout time. Every person executing an activity, working with a tool or machine, or dealing with a process knows what works well and what doesn’t. They know the value-added activities and waste (muda). The ability to tap into this knowledge, especially during area lean blitzes or kaizen events, is crucial to success and sustainment of changes and gains. If this knowledge is not captured, leveraged, and utilized once the blitz or kaizen event is done, personnel will revert to their way of doing things. Additionally, understanding how things are really done will help the organization make effective changes and improve worker safety. Coaching generally uses a nurturing approach to achieve an end goal. Good coaches keep the end goal in mind at all times; they recognize that there will be setbacks and know how to overcome them. When a setback occurs, a coach will assess the situation; adapt with small, incremental change (usually); and then guide the team to overcome the challenge and succeed. Coaching relies on the ability to communicate and motivate, ensuring that “leanspeak” can be translated so that all involved understand. Coaching utilizes formal and informal leaders within the organization to ensure acceptance of the lean culture shift. The coaching method engages employees, improves performance, and reduces the effort needed to implement and sustain lean. Learning and coaching are vital cultural enablers for lean. Learning ensures that personnel gain knowledge, apply the knowledge gained, and retain the knowledge, and it lays the foundation for culture shift and lean execution. Coaching reinforces learning, elevates employees to perform, and leverages personnel throughout the organization to adapt and embrace the culture shift and drive improvements to perform effectively and efficiently. 1.2.6. PEOPLE DEVELOPMENT-EDUCATION, TRAINING & COACHING What does the organization do if it has a goal to penetrate a new product line or market? One method is that the organization first learns about that product line or market and then determines how to best leverage its performance to differentiate and penetrate that product line or market. This is an example of education, training, and coaching. In lean, people development through education, training, and coaching is a key cultural component. Education can be formal or informal and external or internal to the organization. Training is also formal or informal and is usually internal to the organization or leverages external training that aligns with the organization’s goals and lean system. Coaching leverages the education and training to guide people to achieve the desired results. Education can take the form of degrees, courses, or certifications offered by external organizations like community colleges and universities or specialized organizations like ASQ and SME. Education is available in lean, components of lean, quality, and the like. In most cases, education involves a broad scope of the entire lean or functional area with depth in most, if not all, aspects of the area. Formal education is a needed investment for subject matter experts, especially those who will guide the organization and serve as coaches. Training, on the other hand, is usually broken down into smaller aspects of lean. It begins with a top-level overview provided to the entire organization to achieve the alignment needed (see Section 1.2.4, “Message Deployment Establishing Vision and Direction”). Then, more specialized training is available, or required, on the critical aspects of lean. The overview ties to the organization’s vision and provides a high-level look at what lean is, how it works, what are its goals and objectives, and how people are engaged and contribute. Specialized training is used to expand on lean principles and tools like value stream mapping and 5S. Specialized training is targeted to those involved with implementing the associated principles and tools to achieve the desired results. Training can include training within the industry and on-the-job training. Coaching is more personal. It is provided by subject matter experts and leaders when and where needed. It may be to help get past a roadblock or to supplement skills where training is not available or needed to execute on a regular basis. For example, coaching may be done to help a team apply a lean principle or tool not ordinarily needed, and thus each individual does not need the training and ability to execute that specific principle or tool on their own. Coaching can also be used to make adjustments in execution to drive alignment. Personnel development through education, training, and coaching provides everyone in the organization with needed skills enhancement and knowledge at the right time to ensure alignment and provide the foundation to achieve the desired results. 1.2.7. MOTIVATION, EMPOWERMENT & INVOLVEMENT Education is not only important to a lean transformation, it’s critical. However, a common mistake that organizations make is that they provide the education (the how) before they provide the purpose (the why). It is difficult to motivate individuals to accept a new idea, and especially difficult if they don’t first understand the purpose or the value of the new idea. Most people will not accept what they don’t value unless they do so only on blind faith. For example, a common lament is how difficult it is to sustain 5S. This is because most people believe the purpose of 5S is only about housekeeping and therefore is not seen as very valuable. What they don’t realize is that the real purpose is the ability to see abnormal conditions and subsequently eliminate waste. They can see a lot more value in 5S when they understand the purpose, the why. Understanding the why establishes the value. There are five phases to any change initiative: Phase I; Enlightenment. This is simply about establishing the purpose the “why” before you provide the education. You can teach a new skill, but getting someone who doesn’t see its value to use it will happen only by demand, not by desire. Phase II; Education. This is self-explanatory. It’s providing the “how” Providing someone with how to do or to accept something without first providing the why will likely diminish the chance for success. Phase III; Empowerment. Once individuals know why and how, you must give them a chance to really learn through application and experimentation. Very important: Never have anyone assume new responsibilities before first providing him or her the skills. Empowerment requires the development of skills and/or knowledge first. Phase IV; Experience. Empowerment provides the opportunity for multiple experiences, and subsequent multiple experiences will develop the expertise. Phase V; Enrichment. This simply means “results” Any change initiative that follows the first four phases can fully expect to get the desired results. As mentioned earlier, education is critical. Phase II is all about education. However, effectively transferring skills and knowledge can be difficult. A proven approach to effective education is “learn, apply, and reflect” Every educational experience should go through these three steps; some cases require more than one cycle. 1. Learn. Individuals must be provided the knowledge and skills required to achieve the desired expectations. 2. Apply. Knowledge without application will not be internalized. Adults in particular learn far better through app…
Purchase answer to see full attachment

Explanation & Answer:

20 Slides

KFUPM The Ethical Implications of Self Driving Cars Essay

KFUPM The Ethical Implications of Self Driving Cars Essay

Description

 

 

Unformatted Attachment Preview

Code of Ethics for Engineers Preamble Engineering is an important and learned profession. As members of this profession, engineers are expected to exhibit the highest standards of honesty and integrity. Engineering has a direct and vital impact on the quality of life for all people. Accordingly, the services provided by engineers require honesty, impartiality, fairness, and equity, and must be dedicated to the protection of the public health, safety, and welfare. Engineers must perform under a standard of professional behavior that requires adherence to the highest principles of ethical conduct. I. Fundamental Canons Engineers, in the fulfillment of their professional duties, shall: 1. Hold paramount the safety, health, and welfare of the public. 2. Perform services only in areas of their competence. 3. Issue public statements only in an objective and truthful manner. 4. Act for each employer or client as faithful agents or trustees. 5. Avoid deceptive acts. 6. Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession. II. Rules of Practice 1. Engineers shall hold paramount the safety, health, and welfare of the public. a. If engineers’ judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate. b. Engineers shall approve only those engineering documents that are in conformity with applicable standards. c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code. d. Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise. e. Engineers shall not aid or abet the unlawful practice of engineering by a person or firm. f. Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. 2. Engineers shall perform services only in the areas of their competence. a. Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved. b. Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control. c. Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment. 3. Engineers shall issue public statements only in an objective and truthful manner. a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current. b. Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter. c. Engineers shall issue no statements, criticisms, or arguments on technical matters that are inspired or paid for by interested parties, unless they have prefaced their comments by explicitly identifying the interested parties on whose behalf they are speaking, and by revealing the existence of any interest the engineers may have in the matters. 4. Engineers shall act for each employer or client as faithful agents or trustees. a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services. b. Engineers shall not accept compensation, financial or otherwise, from more than one party for services on the same project, or for services pertaining to the same project, unless the circumstances are fully disclosed and agreed to by all interested parties. c. Engineers shall not solicit or accept financial or other valuable consideration, directly or indirectly, from outside agents in connection with the work for which they are responsible. d. Engineers in public service as members, advisors, or employees of a governmental or quasi-governmental body or department shall not participate in decisions with respect to services solicited or provided by them or their organizations in private or public engineering practice. e. Engineers shall not solicit or accept a contract from a governmental body on which a principal or officer of their organization serves as a member. 5. Engineers shall avoid deceptive acts. a. Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates’ qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments. b. Engineers shall not offer, give, solicit, or receive, either directly or indirectly, any contribution to influence the award of a contract by public authority, or which may be reasonably construed by the public as having the effect or intent of influencing the awarding of a contract. They shall not offer any gift or other valuable consideration in order to secure work. They shall not pay a commission, percentage, or brokerage fee in order to secure work, except to a bona fide employee or bona fide established commercial or marketing agencies retained by them. III. Professional Obligations 1. Engineers shall be guided in all their relations by the highest standards of honesty and integrity. a. Engineers shall acknowledge their errors and shall not distort or alter the facts. b. Engineers shall advise their clients or employers when they believe a project will not be successful. c. Engineers shall not accept outside employment to the detriment of their regular work or interest. Before accepting any outside engineering employment, they will notify their employers. d. Engineers shall not attempt to attract an engineer from another employer by false or misleading pretenses. e. Engineers shall not promote their own interest at the expense of the dignity and integrity of the profession. 2. Engineers shall at all times strive to serve the public interest. a. Engineers are encouraged to participate in civic affairs; career guidance for youths; and work for the advancement of the safety, health, and well-being of their community. b. Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project. c. Engineers are encouraged to extend public knowledge and appreciation of engineering and its achievements. d. Engineers are encouraged to adhere to the principles of sustainable development1 in order to protect the environment for future generations. 1420 KING STREET • ALEXANDRIA, VIRGINIA 22314-2794 • 888-285-NSPE (6773) • LEGAL@NSPE.ORG • WWW.NSPE.ORG • PUBLICATION DATE AS REVISED JULY 2007 • PUBLICATION #1102 COPYRIGHT NATIONAL SOCIETY OF PROFESSIONAL ENGINEERS. ALL RIGHTS RESERVED. 3. Engineers shall avoid all conduct or practice that deceives the public. a. Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact. b. Consistent with the foregoing, engineers may advertise for recruitment of personnel. c. Consistent with the foregoing, engineers may prepare articles for the lay or technical press, but such articles shall not imply credit to the author for work performed by others. 4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve. a. Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge. b. Engineers shall not, without the consent of all interested parties, participate in or represent an adversary interest in connection with a specific project or proceeding in which the engineer has gained particular specialized knowledge on behalf of a former client or employer. 5. Engineers shall not be influenced in their professional duties by conflicting interests. a. Engineers shall not accept financial or other considerations, including free engineering designs, from material or equipment suppliers for specifying their product. b. Engineers shall not accept commissions or allowances, directly or indirectly, from contractors or other parties dealing with clients or employers of the engineer in connection with work for which the engineer is responsible. 6. Engineers shall not attempt to obtain employment or advancement or professional engagements by untruthfully criticizing other engineers, or by other improper or questionable methods. a. Engineers shall not request, propose, or accept a commission on a contingent basis under circumstances in which their judgment may be compromised. b. Engineers in salaried positions shall accept part-time engineering work only to the extent consistent with policies of the employer and in accordance with ethical considerations. c. Engineers shall not, without consent, use equipment, supplies, laboratory, or office facilities of an employer to carry on outside private practice. 7. Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action. a. Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated. b. Engineers in governmental, industrial, or educational employ are entitled to review and evaluate the work of other engineers when so required by their employment duties. c. Engineers in sales or industrial employ are entitled to make engineering comparisons of represented products with products of other suppliers. 8. Engineers shall accept personal responsibility for their professional activities, provided, however, that engineers may seek indemnification for services arising out of their practice for other than gross negligence, where the engineer’s interests cannot otherwise be protected. a. Engineers shall conform with state registration laws in the practice of engineering. b. Engineers shall not use association with a nonengineer, a corporation, or partnership as a “cloak” for unethical acts. 9. Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others. a. Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments. b. Engineers using designs supplied by a client recognize that the designs remain the property of the client and may not be duplicated by the engineer for others without express permission. c. Engineers, before undertaking work for others in connection with which the engineer may make improvements, plans, designs, inventions, or other records that may justify copyrights or patents, should enter into a positive agreement regarding ownership. d. Engineers’ designs, data, records, and notes referring exclusively to an employer’s work are the employer’s property. The employer should indemnify the engineer for use of the information for any purpose other than the original purpose. e. Engineers shall continue their professional development throughout their careers and should keep current in their specialty fields by engaging in professional practice, participating in continuing education courses, reading in the technical literature, and attending professional meetings and seminars. Footnote 1 “Sustainable development” is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development. “By order of the United States District Court for the District of Columbia, former Section 11(c) of the NSPE Code of Ethics prohibiting competitive bidding, and all policy statements, opinions, rulings or other guidelines interpreting its scope, have been rescinded as unlawfully interfering with the legal right of engineers, protected under the antitrust laws, to provide price information to prospective clients; accordingly, nothing contained in the NSPE Code of Ethics, policy statements, opinions, rulings or other guidelines prohibits the submission of price quotations or competitive bids for engineering services at any time or in any amount.” Statement by NSPE Executive Committee In order to correct misunderstandings which have been indicated in some instances since the issuance of the Supreme Court decision and the entry of the Final Judgment, it is noted that in its decision of April 25, 1978, the Supreme Court of the United States declared: “The Sherman Act does not require competitive bidding.” It is further noted that as made clear in the Supreme Court decision: 1. Engineers and firms may individually refuse to bid for engineering services. 2. Clients are not required to seek bids for engineering services. 3. Federal, state, and local laws governing procedures to procure engineering services are not affected, and remain in full force and effect. 4. State societies and local chapters are free to actively and aggressively seek legislation for professional selection and negotiation procedures by public agencies. 5. State registration board rules of professional conduct, including rules prohibiting competitive bidding for engineering services, are not affected and remain in full force and effect. State registration boards with authority to adopt rules of professional conduct may adopt rules governing procedures to obtain engineering services. 6. As noted by the Supreme Court, “nothing in the judgment prevents NSPE and its members from attempting to influence governmental action . . .” Note: In regard to the question of application of the Code to corporations vis-a-vis real persons, business form or type should not negate nor influence conformance of individuals to the Code. The Code deals with professional services, which services must be performed by real persons. Real persons in turn establish and implement policies within business structures. The Code is clearly written to apply to the Engineer, and it is incumbent on members of NSPE to endeavor to live up to its provisions. This applies to all pertinent sections of the Code. 1420 KING STREET • ALEXANDRIA, VIRGINIA 22314-2794 • 888-285-NSPE (6773) • LEGAL@NSPE.ORG • WWW.NSPE.ORG • PUBLICATION DATE AS REVISED JULY 2007 • PUBLICATION #1102 COPYRIGHT NATIONAL SOCIETY OF PROFESSIONAL ENGINEERS. ALL RIGHTS RESERVED. Engineering Ethics 1.0 Introduction Ethics is the study of the characteristics of morals, and involves the moral choices made by individuals as they interact with other persons. Engineers need to be aware of ethics as they make choices during their professional practice of engineering. Engineering ethics will be defined as the rules and standards governing the conduct of engineers in their roles as professionals [1]. Most engineering educational institutions include discussion of ethics in their curriculum; in fact the Accreditation Board of Engineering and Technology (ABET) has mandated that engineering educational programs include ethics in their undergraduate curriculum. Some institutions require a specific course in engineering ethics; others require their students to take a Humanities course (such as Philosophy) on ethics and morals. Our MAE department at MU has decided to focus on engineering ethics in two courses: MAE 1000 (Introduction to Mechanical Engineering), which is primarily a freshman course; and MAE 4980 (Capstone Design), which is a senior course taken in the student’s final semester. Engineering ethics is also discussed in other courses throughout the MAE curriculum. It is important for engineering students to study engineering ethics so that they will be prepared to make (sometimes difficult) ethical decisions during their professional careers. As you read this handbook, you will note that many case studies in engineering ethics do not have a single clear-cut correct answer, but may have many correct solutions, where some solutions are better than others. Therefore, ethical problems can be similar to open-ended engineering design problems, where multiple solutions exist. The purpose of this handbook is to provide students with an introduction to engineering ethics. The goals of this handbook include 1) fostering an increased awareness of ethical behavior, 2) presenting the accepted codes of ethics for professional engineering societies, and 3) presenting engineering case studies that illustrate ethical (or unethical) decisions. It is our hope that this handbook will invigorate and supplement the discussion of ethics in our MAE courses. 2.0 The Engineering Profession Engineering practice can be defined as a “profession,” as opposed to an “occupation” or “job.” A profession has the following attributes: • • Work requires sophisticated skills, judgment, and exercise of discretion (work is not routine) Membership in the profession requires formal education Page 1 of 22 • • Special societies (controlled by members of the profession) establish standards for admission into the profession and conduct of its members Significant positive public service results from the practice of the profession Obviously, law and medicine are professions, and their practices are regulated by strong societies such as the American Medical Association (AMA) and the American Bar Association (ABA). Engineering is a profession, but differs from law and medicine in the following ways: • • • Most engineers are not self-employed, but work for large companies (the exceptions include civil engineers and consulting engineers) Education is different: only a BS degree is required to practice engineering Engineering societies are not as powerful as the AMA or ABA, since BS degree holders can practice engineering without a Professional License 3.0 Codes of Ethics Codes of ethics have been established by various professional engineering societies, such as the National Society of Professional Engineers (NSPE), the American Society of Mechanical Engineers (ASME), the Institute of Electrical and Electronics Engineers (IEEE), etc. These codes serve as a framework for ethical judgment for a professional engineer. The codes also express the rights, duties, and obligations of the members of the profession. Obviously, the codes of ethics are not comprehensive enough to cover all possible ethical dilemmas that an engineer might encounter in his or her career. The codes serve as starting points for making ethical decisions. It is important to note what a code of ethics does not represent: • • • A code of ethics is not a legal document, so a professional cannot be arrested for violating its provisions Although violating the code of ethics may result in expulsion from a professional society (such as NSPE or ASME), expulsion from a society generally will not result in an inability to practice engineering A code of ethics does not create new moral and ethical principles; these principles are rooted in centuries of societal and human interactions Codes of ethics for engineers were developed along with their respective professional societies, which began formal organization in the late 19th century. Initially, codes of ethics involved standard business practices. As the professional societies matured over the years, their codes of ethics were updated and modified. For example, clauses for public safety, public service, and environmental protection are more recent amendments to the various codes of ethics. While each society’s code of ethics exhibit similar themes, they have different formats. The NSPE Code of Ethics is very specific and detailed, while the IEEE Code of Page 2 of 22 Ethics is general and fairly concise. The NSPE code is reproduced in Appendix A, and the ASME code is reproduced in Appendix B. Note that the ASME code is also very detailed and specific, and is similar to the NSPE code. First, let us look at the Fundamental Canons of the NSPE Code of Ethics: • • • • • • Engineers shall hold paramount the safety, health and welfare of the public Engineers shall perform services only in areas of their competence Engineers shall issue public statements only in an objective and truthful manner Engineers shall act for each employer or client as faithful agents or trustees Engineers shall avoid deceptive acts Engineers shall conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession The Fundamental Principles of the ASME Code of Ethics are: Engineers uphold and advance the integrity, honor, and dignity of the engineering profession by • • • Using their knowledge and skill for the enhancement of human welfare; Being honest and impartial, and serving with fidelity the public, their employers and clients; and Striving to increase the competence and prestige of the engineering profession Note that the ASME code includes seven provisions under the Fundamental Principles that are nearly identical to the NSPE Fundamental Canons (compare Appendices A and B). Codes of ethics can be used to support engineers who are being sanctioned by an employer for uncovering unethical behavior. Finally, it should be noted that many corporations have developed their own codes of ethics for their employees. In many cases, these codes of conduct can be found on the websites of various large corporations. Companies often provide periodic ethical training sessions for their employees in order to explicitly express their accepted policies on business practices, relationships with vendors and government agencies, compliances with government regulations, health and safety issues, environmental issues, equal employment opportunities, sexual harassment, and diversity in the work place. Corporate codes are often very detailed and explicit, and they hold much more weight than professional society codes, since employment can be terminated if compliance is not met. By comparison, the professional codes have diminished power since the majority of professional engineers are not members of professional societies. Page 3 of 22 4.0 Catastrophic Engineering Failures: Case Studies Several high-profile engineering failures can serve as case studies for discussions on ethics, whistle-blowing, and questions that arise in the course of engineering practice. A partial list of catastrophic engineering failures is shown below: 1. 2. 3. 4. 5. Space Shuttle Challenger accident Ford Pinto exploding gas tanks Kansas City Hyatt Regency walkway collapse Teton Dam failure DC-10 multiple failures Detailed discussions of some of these case studies can be found on the excellent website for engineering ethics, http://ethics.tamu.edu/ethicscasestudies.htm [2]. 5.0 Case Studies We choose to present smaller-scale case studies to illustrate engineering ethics. Practicing engineers are more likely to confront these fictional scenarios in their careers than a catastrophic failure such as the Challenger accident. The case studies presented here can also be found on the engineering ethics website [2]. 5.1 Case Study 1: “Suppressed Data” The first fictional case study was developed by Dr. Michael S. Pritchard at Western Michigan University for class discussion of ethical decision making [2]: A recent graduate of Engineering Tech, you have been employed in the R & D Chemical Engineering Division of Larom, Inc. for the past several months. You were hired because of the promising research you did with catalysts as a student at Engineering Tech. A meeting of your division is called by your supervisor, Alex Smith. He announces that your unit must make a recommendation within the next two days on what catalyst should be used by Larom in processing a major product. The overwhelming consensus of the engineers in your unit, based on many years of experience, is that catalyst A is best for the job. But the research you have been conducting at Larom provides preliminary evidence that catalyst B might be more reliable, more efficient, and considerably less costly. So, you ask if the recommendation can be delayed another month to see if firmer evidence can be found. Alex replies, “We don’t have a month. We have two days.” He then asks you to write up the report, leaving out the preliminary data you have gathered about catalyst B. He says, “It might be nice to do some more research on B, but we’ve already taken too much time on this project. This is one of those times we have to be decisive–and we have to look Page 4 of 22 decisive and quit beating around the bush. Management is really getting impatient with us on this one. Besides, we’ve had a lot of experience in this area.” You like working for Larom, and you feel fortunate to have landed such a good job right out of Engineering Tech. You have no desire to challenge your colleagues. Besides you don’t necessarily disagree with them about which catalyst is best. Still, you wish you had been given more time to work on catalyst B, and you feel uncomfortable about leaving the preliminary data out of the report. What should you do? 1. Write up and sign the report as instructed. 2. Write up the report as instructed, but refuse to sign it. 3. Refuse to write up the report, threatening to go around Alex to the next level of management if a fully accurate report is not made. 4. Other. Commentary from the Author: Engineering students may respond to cases like this in a variety of ways. A rather large percentage of students select the first option, indicating that they really have no choice if they are to keep their jobs. Some insist that, since they would only be following orders, they would not really be responsible if something goes wrong. A few immediately select the third option, adding that they might make sure they have another job offer first. What is surprising is how few select “Other.” Yet, a sensible alternative seems to be to suggest that catalyst A be recommended, but that the data about B be included. After all, it might be argued, if the data about B has not engendered serious doubts among the experienced engineers in the unit, why should they fear that management would counter their recommendation of A? For those students who favor suppressing the data, there is a second scenario, “The Suppressed Data Strike Back.” You write the report as instructed, and Larom proceeds with catalyst A. Two months later Charles Trent, Vice-President for Re search at Larom, learns that a major competitor has just begun using catalyst B in a similar process. Its engineers discovered that B is ideal for this process. It is more reliable, more efficient, and much less expensive. VicePresident Trent is very upset that Alex Smith’s unit “missed the boat,” and he personally meets with the entire unit to make his irritation known. He complains, “Larom has invested a lot of money in this process–only to find out that it’s now falling behind a major competitor. It’s going to cost us time and money to convert the process–and it’s probably going to cost us a few customers as well.” At this point many students say, “Let’s go back to the first situation.” The point is not that giving further thought to the initial situa tion will yield an obvious and non-problematic solution. (Any option here might have some undesirable consequences.) It is that, through the use of moral imagination, more satisfactory alternatives may be discovered. Page 5 of 22 5.2 Case Study 2: “Machine Failure” This fictional case was developed by Dr. Michael S. Pritchard and Dr. Kenneth L. Carper from Washington State University [2]. Part 1 R&M Machinery had for years provided XYZ Inc. with sophisticated equipment and reliable repair service. XYZ Inc. returned a failed piece of equipment. A meeting was held which included Archie Hunter, a representative from XYZ Inc.; Norm Nash, R&M’s returned goods area representative, and Walt Winters, an R&M engineer intimately acquainted with the kind of equipment XYZ Inc. had returned. Norm Nash represented R&M’s “official position”: the piece of equipment is all right. However, during the course of the meeting it becomes apparent to Walt Winters that the problem has to be R&M’s. He suspects that the equipment was not properly tested out by R&M, and that it failed because of an internal problem. Discussion Question #1: Should Walt say anything about this in the presence of the customer, or should he wait until after the meeting to discuss this with Norm Nash? Part 2 Walt keeps silent during the meeting. After the meeting he talks with Norm about his diagnosis. He suggests they tell XYZ Inc. that the problem is R&M’s fault, and that R&M will replace the defective equipment. Norm replies, “I don’t think it’s wise to acknowledge that it’s our fault. There’s no need to hang out our wash and lessen XYZ Inc.’s confidence in the quality of our work. A ‘good will’ gesture to replace the equipment should suffice.” R&M management decides to tell XYZ Inc. that they will adjust to the customer’s needs “because you have been such a good customer all these years.” Although R&M replaces the equipment at its own expense, it does not tell XYZ Inc. the real nature of the problem. Discussion Question #2: Discuss R&M’s resolution of the problem. Should R&M’s way of handling the problem be of any concern to Walt Winters at this point, or is it basically a “management problem”? Part 3 Many engineers eventually move into management positions. If Walt Winters moves into management, what lessons, if any, might he take with him from the above situation? Page 6 of 22 Commentary from the Authors: The fundamental moral concept of honesty is at stake in this case study. Norm Nash, representing the position of management, has made the decision to deny the possibility of a defective product. This decision has been made on the basis of public image and ignores the technical opinion given by Walt Winters, one of the firm’s engineers. Winter’s silence is probably appropriate in the first meeting with the client. His position is one of technical support, not public relations. Also, his suspicions are not yet confirmed, and a preliminary contradiction of Nash’s statement is unwarranted. Winters is correct in raising his objections directly with Nash following the meeting with the client. Norm Nash’s reaction is unfortunate. Walt Winters should be distressed by this reaction. His first move should be to disassemble the equipment to confirm his diagnosis, if possible. If the evidence supports his hypothesis, he should then press Nash vigorously to deal honestly with the client. While this one experience with one executive may not be indicative of the attitudes of all management executives in the corporation, Winter should observe corporate management decisions carefully for other moral deficiencies. The expression that this is merely a “management problem” of little concern to technical staff can lead to serious consequences. If management decisions routinely overrule factual technical information, placing public relations over honesty, the stage has been set for potential moral disaster. There are many examples from all engineering disciplines. One well-documented case is the Morton-Thiokol treatment of the events leading up to the Challenger Space Shuttle accident. One puzzling question comes to mind: What is the cost of honesty here? The relationship between R&M and XYZ Inc. is firmly established, based on years of reliable service. An honest admission of equipment failure will not damage such a relationship. Confidence is built, not destroyed, by honesty and integrity. This client is left with unanswered questions: Is this an equipment deficiency? Is it an installation problem? Has the breakdown occurred due to operator error or improper maintenance? These unanswered questions may lead to suspicions. Unanswered questions are far more likely to undermine client confidence than an honest admission of potential manufacturing defects. And Nash has already agreed to replace the equipment at no cost to the customer. What possible economic cost could honesty demand beyond this? It is precisely the lack of economic cost that makes this case so disturbing. The lessons for Winters, potentially a future manager, are clear: If honesty can be compromised in such a trivial instance, why should one insist on integrity when the costs are high? Honesty is not always this inexpensive. Sometimes it costs a great deal. When the stakes are high, surely it will be easier to dismiss moral commitments. Page 7 of 22 The image of infallibility cultivated by managers like Nash, and their unwillingness to admit fault leads to unrealistic expectations by clients. When failures do occur, society is unprepared for the consequences. The concept of risk is not at all well understood by the public. Instead of providing assistance in understanding this concept, many engineers and managers like Nash have encouraged unrealistic expectations by their attitudes. The public has become more intolerant of failure and more suspicious of the technical experts who are unable to deliver the promised risk-free society. In fact, the very foundation of engineering design is based in trial-and-error experience. The state-of-the-art cannot be advanced without failure. The implication of a condition where failure does not occur is that techno logy is not advancing. When products do not fail once in awhile, one must conclude that they are inefficient and over-designed. Technical professionals and product manufacturers have a clear ethical responsibility to communicate honestly about failures, thus contributing to the safety and reliability of products and the advancement of engineering design practice. Admittedly, this communication has been greatly hindered by the expanding litigiousness of contemporary American society. Finally, some additional questions ought to be considered. It has been noted that the cost of honesty is very small in this case. What if the anticipated cost were higher? What if XYZ Inc. were a new prestigious client, with no established business relationship? An honest admission of fallibility might destroy the relationship in its infancy, with implications for many employees of R&M. What if the equipment failure had resulted in great economic losses to XYZ Inc., as products and other equipment may have been damaged by the fa ilure? What if serious injuries, or even deaths, were caused by failure of this equipment? Should the actions of Nash and Winters be any different? Do these more serious consequences and potential costs create an intrinsically different moral situation, or is the situation merely made more complex by the legal implications? Does the fear of litigation dictate the appropriate moral response? Unfortunately, the example provided by Norm Nash gives Walt Winters very little to encourage principled moral reasoning. 5.3 Case Study 3: “Fabricated Data” This fictional case was developed by Dr. Gale Cutler, a management consultant in Michigan [2]. Part 1: Project leader Bruce Barton was being sorely pressed to complete the development of several engineering prototypes for a field test of a new appliance model for the XYZ Page 8 of 22 company. One particular plastic component of the new model had given difficulty in laboratory tests as it failed repeatedly before reaching the stress level necessary for successful operation. Bruce had directed a redesign of the component using a tough new engineering plastic recommended by the Research Laboratory’s Material Science Department. Stress tests needed to be run on the redesigned component, but Bruce was running short of time and needed to get on with building the prototype. Bruce sought out the manager of the Material Science Department for help in running stress tests on samples of the new component. With this assistance he could go ahead with prototype building and conduct the tests concurrently. The prototypes, of course, would not be released to field test until the stress tests on the redesigned component proved its design to be satisfactory. Tom Mason, manager of the Material Science Department, was willing to assist because he knew how critical completion of the development was to XYZ’s future appliance plans. However, this was also a busy time for Tom’s department. So, Tom suggested to Bruce that he could assign the test work to one of the engineering co-op students. Tom was also coordinator of engineering co-op students, and he liked to use the co-op students in demanding situations to give them practical experience. Tom assigned the test work to Jack Jacobs, an engineering co-op student from the State University who was completing his second work session at XYZ. Jack was familiar with the test equipment and previously had done similar test work. Jack was a good student and his co-op work had been usually well done. Tom commented to Jack that he would need to work diligently to complete the tests before he had to return to State University. Jack completed the tests on schedule and turned in a report to Tom indicating the component had successfully passed the stress tests. Upon completion of the test report Jack returned to the university for his next school session. Tom gave Bruce the good news. The prototypes were completed and the field test of these prototypes got underway on schedule. A few weeks later, Bruce rushed into Tom’s office to tell him that most of the prototypes were out of operation because of a catastrophic failure of the component that had been tested in Tom’s lab. Bruce wanted to discuss the test immediately with Jack; but since Jack had already returned to the university, he and Tom settled for studying Jack’s lab notebook in detail. After review Tom said, “Bruce, I hate to say it but these data look too good. I know the equipment and there should be more scatter in the measurements Jack took. I think some, if not all, these measurements are in error or they have been faked! At best, Jack probably took a few points and ‘extrapolated’ the rest!” Discussion Question #1: What ethical issues, if any, does this scenario raise? Page 9 of 22 Part 2: Bruce and Tom made plans to run all the tests again. Meanwhile, Tom phoned Dr. Frank Thompson, Co-op Coordinator at State University, to discuss his fear that Jack had falsified data. In the course of the conversation he asked Dr. Thompson if any effort was made to discuss professional ethics with co-op students before their first work session and if the importance and value of engineering test results were stressed to these students. Dr. Thompson explained that no specific instruction on professional ethics was given to co-op students, but all lab courses emphasized the need for accuracy in data taking. Dr. Thompson added that he found it hard to believe that a co-op student would “fake” data! Discussion Questions #2: Was it appropriate for Tom to discuss his concerns about Jack with the university’s Co-op Coordinator prior to discussing the matter with Jack? Should Tom have a conversation with Jack about his concerns? If so, what type of conversation should Tom have with Jack when he talks with him? Should he refuse to have Jack return to XYZ as a co-op student? Commentary from the Author: Question #1 If Jack Jacobs, the co-op student, either faked the test results or took a few points and extrapolated the rest, he was taking credit for work without doing it, which is like cheating on a test or plagiarizing a paper. He was also making the company count on work which hadn’t been done properly, trusting in something which turned out to be unreliable. There are other possibilities, however, that shouldn’t be discounted. The test may have been carried out properly but be an inadequate test for whether the part can operate under the strain of regular use. The test results may be in error is some other way. Jack may have not run the test properly. Although Jack was familiar with the test equipment and had previously done similar work, he may still have misused it and made honest mistakes. There is only presumptive, not conclusive, evidence that Jack did not run the tests to the best of his ability. Another issue is whether Jack was getting proper supervision in his work session at XYZ. It is good for co-op students to get demanding work to give them practical experience, but shouldn’t their work be checked, both while doing it and after done, so that they and the company know if they are doing it properly? Commentary from the Author: Question #2 If Tom had talked with Jack first, what could that have achieved? If Jack falsified the data, he might have lied about it and simply gotten himself into deeper unethical water. And if he did lie, what more would Tom know than he already knew? There would Page 10 of 22 still be presumptive evidence that the results were falsified, but no more proof than before the conversation. On the other hand, if Jack had misused the equipment or had extrapolated from a few tests, that might be found out, and Jack would be known to be guilty of the lesser of the suspected errors. And Jack might not realize that extrapolation from a few tests could have the dire consequences that did in fact occur from passing on materials which would not stand up under complete tests. The re would be two reasons, then, for having a conversation with Jack. One would be to find out more about what really happened. The other would be to impress upon Jack the consequences of his poor performance. But is it Tom’s responsibility to get in touch with Jack? Students are hard to reach at the University. Jack may not have a private telephone, and to write a letter hoping for an answer is a slow way of doing something. Furthermore, the case is not just about Jack. It is about preparation of students for co-op work and, ultimately, for their professional work. Tom wants the Co-op Coordinator to be informed that a student probably falsified data or at least extrapolated from a few tests, which is not adequate job performance. The Coordinator should be told, for Jack’s performance reflects on the University and its training of its students. Jack’s identity would be hard to keep secret, in case Tom wanted to do so; but there isn’t any reason to keep it secret. There is evidence that Jack failed to do honest work. Another question is whose job it is to discipline Jack if he has done dishonest work for XYZ. XYZ could refuse to have him return as a co-op student. It could also write a letter to the coordinator to put into writing the charge. It could inform all the people at XYZ with whom Jack had worked that if he asked for letters of reference, they should be aware of this failing. But ultimately, the University has to be responsible for dealing with Jack’s dishonesty. How should it be dealt with by the University? If Jack is getting academic credit for the co-op work, should it be denied? If he deliberately falsified the data, should he be dismissed from the University? What procedure should be used for ascertaining the facts and assigning a penalty? Should this be treated in the same way as a case of cheating on a test or plagiarizing a paper, and by the same procedures? Or is honesty something that the University should leave to society in general and the conscience of the individual? Bibliography [1] Fleddermann, C.B., “Engineering Ethics,” Pearson Prentice Hall, Upper Saddle River, NJ, 2004. [2] Rabins, M.J., Harris, E., Pritchard, M.S., and Lowery, L.L., “Engineering Ethics,” http://ethics.tamu.edu Page 11 of 22 Appendix A: NSPE Code of Ethics Preamble Engineering is an important and learned profession. As members of this profession, engineers are expected to exhibit the highest standards of honesty and integrity. Engineering has a direct and vital impact on the quality of life for all people. Accordingly, the services provided by engineers require honesty, impartiality, fairness, and equity, and must be dedicated to the protection of the public health, safety, and welfare. Engineers must perform under a standard of professional behavior that requires adherence to the highest principles of ethical conduct. I. Fundamental Canons Engineers, in the fulfillment of their professional duties, shall: 1. Hold paramount the safety, health and welfare of the public. 2. Perform services only in areas of their competence. 3. Issue public statements only in an objective and truthful manner. 4. Act for each employer or client as faithful agents or trustees. 5. Avoid deceptive acts. 6. Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession. II. Rules of Practice 1. Engineers shall hold paramount the safety, health, and welfare of the public. a. If engineers’ judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate. b. Engineers shall approve only those engineering documents that are in conformity with applicable standards. c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code. d. Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe are engaged in fraudulent or dishonest enterprise. e. Engineers shall not aid or abet the unlawful practice of engineering by a person or firm. f. Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. Page 12 of 22 2. Engineers shall perform services only in the areas of their competence. a. Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved. b. Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control. c. Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment. 3. Engineers shall issue public statements only in an objective and truthful manner. a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current. b. Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter. c. Engineers shall issue no statements, criticisms, or arguments on technical matters that are inspired or paid for by interested parties, unless they have prefaced their comments by explicitly identifying the interested parties on whose behalf they are speaking, and by revealing the existence of any interest the engineers may have in the matters. 4. Engineers shall act for each employer or client as faithful agents or trustees. a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services. b. Engineers shall not accept compensation, financial or otherwise, from more than one party for services on the same project, or for services pertaining to the same project, unless the circumstances are fully disclosed and agreed to by all interested parties. c. Engineers shall not solicit or accept financial or other valuable consideration, directly or indirectly, from outside agents in connection with the work for which they are responsible. d. Engineers in public service as members, advisors, or employees of a governmental or quasigovernmental body or department shall not participate in decisions with respect to services solicited or provided by them or their organizations in private or public engineering practice. e. Engineers shall not solicit or accept a contract from a governmental body on which a principal or officer of their organization serves as a member. 5. Engineers shall avoid deceptive acts. Page 13 of 22 a. Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates’ qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments. b. Engineers shall not offer, give, solicit or receive, either directly or indirectly, any contribution to influence the award of a contract by public authority, or which may be reasonably construed by the public as having the effect of intent to influencing the awarding of a contract. They shall not offer any gift or other valuable consideration in order to secure work. They shall not pay a commission, percentage, or brokerage fee in order to secure work, except to a bona fide employee or bona fide established commercial or marketing agencies retained by them. III. Professional Obligations 1. Engineers shall be guided in all their relations by the highest standards of honesty and integrity. a. Engineers shall acknowledge their errors and shall not distort or alter the facts. b. Engineers shall advise their clients or employers when they believe a project will not be successful. c. Engineers shall not accept outside employment to the detriment of their regular work or interest. Before accepting any outside engineering employment they will notify their employers. d. Engineers shall not attempt to attract an engineer from another employer by false or misleading pretenses. e. Engineers shall not promote their own interest at the expense of the dignity and integrity of the profession. 2. Engineers shall at all times strive to serve the public interest. a. Engineers shall seek opportunities to participate in civic affairs; career guidance for youths; and work for the advancement of the safety, health, and well-being of their community. b. Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project. c. Engineers shall endeavor to extend public knowledge and appreciation of engineering and its achievements. 3. Engineers shall avoid all conduct or practice that deceives the public. a. Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact. b. Consistent with the foregoing, engineers may advertise for recruitment of personnel. Page 14 of 22 c. Consistent with the foregoing, engineers may prepare articles for the lay or technical press, but such articles shall not imply credit to the author for work performed by others. 4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve. a. Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge. b. Engineers shall not, without the consent of all interested parties, participate in or represent an adversary interest in connection with a specific project or proceeding in which the engineer has gained particular specialized knowledge on behalf of a former client or employer. 5. Engineers shall not be influenced in their professional duties by conflicting interests. a. Engineers shall not accept financial or other considerations, including free engineering designs, from material or equipment suppliers for specifying their product. b. Engineers shall not accept commissions or allowances, directly or indirectly, from contractors or other parties dealing with clie nts or employers of the engineer in connection with work for which the engineer is responsible. 6. Engineers shall not attempt to obtain employment or advancement or professional engagements by untruthfully criticizing other engineers, or by other improper or questionable methods. a. Engineers shall not request, propose, or accept a commission on a contingent basis under circumstances in which their judgment may be compromised. b. Engineers in salaried positions shall accept part-time engineering work only to the extent consistent with policies of the employer and in accordance with ethical considerations. c. Engineers shall not, without consent, use equipment, supplies, laboratory, or office facilities of an employer to carry on outside private practice. 7. Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action. a. Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated. b. Engineers in governmental, industrial, or educational employ are entitled to review and evaluate the work of other engineers when so required by their employment duties. Page 15 of 22 c. Engineers in sales or industrial employ are entitle d to make engineering comparisons of represented products with products of other suppliers. 8. Engineers shall accept personal responsibility for their professional activities, provided, however, that engineers may seek indemnification for services arising out of their practice for other than gross negligence, where the engineer’s interests cannot otherwise be protected. a. Engineers shall conform with state registration laws in the practice of engineering. b. Engineers shall not use association with a nonengineer, a corporation, or partnership as a “cloak” for unethical acts. 9. Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others. a. Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments. b. Engineers using designs supplied by a client recognize that the designs remain the property of the client and may not be duplicated by the engineer for others without express permission. c. Engineers, before undertaking work for others in connection with which the engineer may make improvements, plans, designs, inventions, or other records that may justify copyrights or patents, should enter into a positive agreement regarding ownership. d. Engineers’ designs, data, records, and notes referring exclusively to an employer’s work are the employer’s property. The employer should indemnify the engineer for use of the information for any purpose other than the original purpose. e. Engineers shall continue their professional development throughout their careers and should keep current in their specialty fields by engaging in professional practice, participating in continuing education courses, reading in the technical literature, and attending professional meetings and seminars. Page 16 of 22 Appendix B: ASME Code of Ethics THE FUNDAMENTAL PRINCIPLES Engineers uphold and advance the integrity, honor, and dignity of the Engineering profession by: I. II. III. using their knowledge and skill for the enhancement of human welfare; being honest and impartial, and serving with fidelity the public, their employers and clients, and striving to increase the competence and prestige of the engineering profession. THE FUNDAMENTAL CANONS 1. Engineers shall hold paramount the safety, health and welfare of the public in the performance of their professional duties. 2. Engineers shall perform services only in the areas of their competence. 3. Engineers shall continue their professional development throughout their careers and shall provide opportunities for the professional development of those engineers under their supervision. 4. Engineers shall act in professional matters for each employer or client as faithful agents or trustees, and shall avoid conflicts of interest. 5. Engineers shall build their professional reputations on the merit of their services and shall not compete unfairly with others. 6. Engineers shall associate only with reputable persons or organizations. 7. Engineers shall issue public statements only in an objective and truthful manner. THE ASME CRITERIA FOR INTERPRETATION OF THE CANONS The ASME criteria for interpretation of the Canons are guidelines and represent the objectives toward which members of the engineering profession should strive. They are principles which an engineer can reference in specific situations. In addition, they provide interpretive guidance to the ASME Committee on Ethical Standards and Review on the Code of Ethics of Engineers. 1. Engineers shall hold paramount the safety, health and welfare of the public in the performance of their professional duties. a. Engineers shall recognize that the lives, safety, health and welfare of the general public are dependent upon engineering judgments, decisions and practices incorporated into structures, machines, products, processes and devices. b. Engineers shall not approve or seal plans and/or specifications that are not of a design safe to the public health and welfare and in conformity with accepted engineering standards. c. Whenever the Engineers’ professional judgments are over-ruled under circumstances where the safety, health, and welfare of the public are endangered, the Engineers shall inform their clients and/or employers of the possible consequences. Page 17 of 22 d. 2. (1) Engineers shall endeavor to provide data such as published standards, test codes, and quality control procedures that will enable the users to understand safe use during life expectancy associated with the designs, products, or systems for which they are responsible. (2) Engineers shall conduct reviews of the safety and reliability of the designs, products, or systems for which they are responsible before giving their approval to the plans for the design. (3) Whenever Engineers observe conditions, directly related to their employment, which they believe will endanger public safety or health, they shall inform the proper authority of the situation. If engineers have knowledge of or reason to believe that another person or firm may be in violation of any of the provisions of these Canons, they shall present such information to the proper authority in writing and shall cooperate with the proper authority in furnishing such further information or assistance as may be required. Engineers shall perform services only in areas of their competence. a. Engineers shall undertake to perform engineering assignments only when qualified by education and/or experience in the specific technical field of engineering involved. b. Engineers may accept an assignment requiring education and/or experience outside of their own fields of competence, but their services shall be restricted to other phases of the project in which they are qualified. All other phases of such project shall be performed by qualified associates, consultants, or employees. 3. Engineers shall continue their professional development throughout their careers, and should provide opportunities for the professional and ethical development of those engineers under their supervision. 4. Engineers shall act in professional matters for each employer or client as faithful agents or trustees, and shall avoid conflicts of interest or the appearance of conflicts of interest. a. Engineers shall avoid all known conflicts of interest with their employers or clients and shall promptly inform their employers or clients of any business association, interests, or circumstances which could influence their judgment or the quality of their services. b. Engineers shall not undertake any assignments which would knowingly create a potential conflict of interest between themselves and their clients or their employers. c. Engineers shall not accept compensation, financial or otherwise, from more than one party for services on the same project, or for services pertaining to the same project, unless the circumstances are fully disclosed to, and agreed to, by all interested parties. Page 18 of 22 d. Engineers shall not solicit or accept financial or other valuable considerations, for specifying products or material or equipment suppliers, without disclosure to their clients or employers. e. Engineers shall not solicit or accept gratuities, directly or indirectly, from contractors, their agents, or other parties dealing with their clients or employers in connection with work for which they are responsible. Where official public policy or employers’ policies tolerate acceptance of modest gratuities or gifts, engineers shall avoid a conflict of interest by complying with appropriate policies and sha ll avoid the appearance of a conflict of interest. f. When in public service as members, advisors, or employees of a governmental body or department, Engineers shall not participate in considerations or actions with respect to services provided by them or their organization(s) in private or product engineering practice. g. Engineers shall not solicit an engineering contract from a governmental body or other entity on which a principal, officer, or employee of their organization serves as a member without disclosing their relationship and removing themselves from any activity of the body which concerns their organization. h. Engineers working on codes, standards or governmental sanctioned rules and specifications shall exercise careful judgment in their determinations to ensure a balanced viewpoint, and avoid a conflict of interest. i. When, as a result of their studies, Engineers believe a project(s) will not be successful, they shall so advise their employer or client. j. Engineers shall treat information coming to them in the course of their assignments as confidential, and shall not use such information as a means of making personal profit if such action is adverse to the interests of their clients, their employers or the public. (1) They will not disclose confidential information concerning the business affairs or technical processes of any present or former employer or client or bidder under evaluation, without his/her consent, unless required by law or court order. (2) They shall not reveal confidential information or finding of any commission or board of which they are members unless required by law or court order (3) Designs supplied to Engineers by clients shall not be duplicated by the Engineers for others without the express permission of the client(s). k. Engineers shall act with fairness and justice to all parties when administering a construction (or other) contract. l. Before undertaking work for others in which Engineers may make improvements, plans, designs, inventions, or other records which may justify seeking copyrights, Page 19 of 22 patents, or proprietary rights, Engineers shall enter into positive agreements regarding the rights of respective parties. 5. m. Engineers shall admit their own errors when proven wrong and refrain from distorting or altering the facts to justify their mistakes or decisions. n. Engineers shall not accept professional employment or assignments outside of their regular work without the knowledge of their employers. o. Engineers shall not attempt to attract an employee from other employers or from the market place by false or misleading representations. Engineers shall build their professional reputation on the merit of their services and shall not compete unfairly with others. a. Engineers shall negotiate contracts for professional services on the basis of demonstrated competence and qualifications for the type of professional service required. b. Engineers shall not request, propose, or accept professional commissions on a contingent basis if, under the circumstances, their professional judgments may be compromised. c. Engineers shall not falsify or permit misrepresentation of their, or their associates, academic or professional qualification. They shall not misrepresent or exaggerate their degrees of responsibility in or for the subject matter of prior assignments. Brochures or other presentations used to solicit personal employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or their accomplishments. d. Engineers shall prepare articles for the lay or technical press which are only factual. 1) Technical Communications for publication (theses, articles, papers, reports, etc.) which are based on research involving more than one indiv idual (including students and supervising faculty, industrial supervisor/researcher or other co-workers) must recognize all significant contributors. Co-authors listed on proposed and accepted publications should have entered the joint authorship arrangement by mutual consent prior to submittal of the document for publication and should have received written permission to use any unpublished work of others which serves as the major basis or key component of the publication. 2) Technical Communications should adhere to clearly defined and appropriately disseminated guidelines on authorship. These guidelines should be promulgated and publicized in corporate, university or other employer policies and should take cognizance of professional technical socie ty recommendations on ethical practice. 3) Plagiarism, the act of substantially using another’s ideas or written materials without due credit, is unethical. Page 20 of 22 6. 7. 8. e. Engineers shall not maliciously or falsely, directly or indirectly, injure the professional reputation, prospects, practice or employment of another engineer, nor shall they indiscriminately criticize another’s work. f. Engineers shall not use equipment, supplies, laboratory or office facilities of their employers to carry on outside private practice without consent. Engineers shall associate only with reputable persons or organizations. a. Engineers shall not knowingly associate with or permit the use of their names or firm names in business ventures by any person or firm which they know, or have reason to believe, are engaging in business or professional practices of a fraudulent or dishonest nature. b. Engineers shall not use association with non-engineers, corporations, or partnerships to disguise unethical acts. Engineers shall issue public statements only in an objective and truthful manner. a. Engineers shall endeavor to extend public knowledge, and to prevent misunderstandings of the achievements of engineering. b. Engineers shall be completely objective and truthful in all professional reports, statements or testimony. They shall include all relevant and pertinent information in such reports, statements or testimony. c. Engineers, when serving as expert or technical witnesses before any court, commission, or other tribunal, shall express an engineering opinion only when it is founded on their adequate knowledge of the facts in issue, their background of technical competence in the subject matter, and their belief in the accuracy and propriety of their testimony. d. Engineers shall issue no statements, criticisms, or arguments on engineering matters which are inspired or paid for by an interested party, or parties, unless they preface their comments by identifying themselves, by disclosing the identities of the party or parties on whose behalf they are speaking, and by revealing the existence of any financial interest they may have in matters under discussion. e. Engineers shall be truthful in explaining their work and merit, and shall avoid any act tending to promote their own interest at the expense of the integrity and honor of the profession or another individual. Engineers shall consider environmental impact in the performance of their professional duties. a. Engineers shall concern themselves with the impact of their plans and designs on the environment. When the impact is a clear threat to health or safety of the public, then the guidelines for this Canon revert to those of Canon 1. 9. Engineers shall consider sustainable development in the performance of their professional duties. Page 21 of 22 a. Engineers shall consider development that meets the needs of the present without compromising the ability of future generations to meet their own needs. When the impact of the trade-off between economic, ecological, and social issues forms a clear threat to health or safety of the public, then the guidelines for this Canon revert to those of Canon 1. 10. Engineers accepting membership in The American Society of Mechanical Engineers by this action agree to abide by this Society Policy on Ethics and procedures for its implementation. July 25, 2005 Page 22 of 22 ENGINEERING ETHICS – CASE STUDIES 1. What is Engineering Ethics? 2. Why study Engineering Ethics? 3. The scope of Engineering Ethics 4. Case studies in Engineering Ethics a. Killer Robot b. DC – 10 c. Whistle Blowing d. Citicorp Building e. The Challenger case 1. Sample Codes a. Hammurabi’s code b. ABET code 1. Further case studies a. Bhopal b. Three Mile Island c. Chernobyl 7. Concluding remarks WHAT IS ENGINEERING ETHICS  Engineering Ethics is the study of moral issues and decisions confronting individuals and organizations engaged in engineering.  The Study of related questions about moral ideals,character,policies and relationship of people and corporations involved in technological activity. WHY STUDY ENGINEERING ETHICS  What is the point in studying engineering ethics?  What can be gained from taking a course in ethics?  Engineering ethics course is not about preaching virtue rather, its objective is to increase your ability as engineers to responsibly confront moral issues raised by technological activity. THE SCOPE OF ENGINEERING ETHICS Moral Reasoning & Ethical Theories Engineering as Social Experimentation Scope of Engineering Ethics Engineers and Managers, Consultants and headers Global Issues The Engineers Responsibility for safety Responsibility to Employees Rights of Engineers ENGINEERING ETHICS – CASE STUDIES CASE 1 : THE CASE OF THE KILLER ROBOT Jane McMurdock, prosecuttting attorney for the city of Silicon Valley, announced today the indictment of Randey Samuels on charges of manslaughter. Samuels employed as a programmer at the Silicon Techtronic’s Inc. The charge involves the death of Bart Matthews, who was killed last May by an assembly –line robot. Matthews worked as robot operator at Cybernetics Inc.,in Silicon Heights. He was crushed to death when the robot he was operating malfunctioned and started to wave its hands violently. The Robot arm struck Matthews, throwing him against a wall and crushing his skull. Matthews died almost instantly. According to the indictment, Samuels wrote the particular piece of computer program responsible for the robot malfunction. “There’s a smoking gun!” McMurdock announced triumphantly at a press conference held in the hall of Justice.” We have the hand written formula ,provided by the project physicist, which Samuels was supposed to program. But he negligently misinterpreted the formula leading to this huge gruesome death. Society must protect itself against programmers who make careless mistakes. The Sentinel – observer has obtained a copy of the handwritten formula in question. There are actually three similar formulas ,scrawled on piece of yellow legal pad paper. Each formula describes the motion of the robot in one direction: east-west, North-south and up –down. The Sentinel-Observer showed the formulas to Bill Park a professor of physics at Silicon Valley University. He confirmed that these equations could be used to describe the motion of a robot arm. The Sentinel – Observer then showed Park the program code written by the accused in the programming language. We asked Park who is fluent in C and several other languages, whether the program code was correct for the given robot – arm formulas. Parks response was immediate. He exclaimed, “By Jove! It looks like he misinterpreted the formula. He’s guilty as hell, if you ask me”. The Sentinel – Observer was unable to contact Samuels for comment. “He is deeply depressed about all this,” his girl friend told us over the phone,” but Randy believes he will be acquitted when he gets a chance to tell his side of the story. Issues: CASE 2: DC – 10 JUMBO JET The fuselage of the DC – 10 Jumbo jet of which the cargo door is a part was developed by Convair, a sub contractor for McDonnell Douglas. Convair’s senior engineer directing the project, Dan Applegate had written to the Vice president of the company: “The Cargo door could burst open, leading to crash of the plane. Hence the door has to be redesigned and the cabin floor has to strengthened”. Top Management at Convair neither disputed the technical facts or the predictions made by Applegate. The liabilities and the cost of redesign were to high. Two years went by. In 1974 the cargo door of DC – 10 Jumbo burst open and the jet crashed near Paris killing 346 . Issues: CASE 3: WHISTLE BLOWING  Definition: Whistle blowing is alerting relevant persons to some moral or legal corruption, where “Relevant persons” are those in a position to act in response.  No topic in Engineering ethics is more controversial than whistle – blowing.  Carl Houston was a welding supervisor for a nuclear power facility in Virginia (1970) for Stone & Weber He saw  Improper welding procedures  Use of wrong materials  Welders were not trained properly  The Situation was dangerous He reported to Stone & Weber’s Manager, who ignored him. He threatened to write to Stone & Weber’s Headquarters. Shortly thereafter he was fired on trumped – up charges. Finally he wrote to Senators Howard’s Baker and Albert Gore. The Senators prompted the Atomic Energy Commission to investigate, which confirmed his allegations. Issues : CASE 4: CITICORP BUILDING Structural Engineer Bill LeMessurier faced a big design problem when he worked on the Citicorp Centre, N.Y – fifth highest skyscraper in New York. The 900 feet bank would rise from 9-storey (114’) high columns. The columns are positioned as follows: one at the center and the other at the CENTER OF EACH SIDE OF THE TOWER and not at the CORNERS OF THE TOWERS (as is usual) This was because of a corner of the plot belonged to a church and the church had to be accommodated there. The building was completed in 1977. An engineering student like you questioned: what will happen when the wind loading is oblique? y x (a) (b) (c) Calculations should show that in Case (c) resultant force is 40% larger. the While LeMessurier designed welded joints, the contractor, Bethlehem Steel changed them to bolted joints. Recalculation was not done to check what the construction change would do. Wind Tunnel Tests proved that the diagonal wind loading (with a return period of 16 years) can lead to the failure of the critical bolted joints and therefore the building. LeMessurier was deeply troubled. He considered his options  Silence  Suicide Then he told himself: • I have information that nobody else in the world had. • I have power to effect extraordinary events that only could initiate. I He explained the problem to his client Citicorp. The building was strengthened by welding two-inch thick steel plates over each of the 200 bolted joints. With only welding half the number of bolts hurricane Ella was threatening to strike the building. Luckily Ella’s direction changed. Despite the fact that nothing happened as the result of the engineering gaffe, the crises was kept hidden from the public for almost 20 years. LeMessurier was criticized for  Insufficient oversight leading to bolted rather than welded joints. For misleading the public about the extent of the danger during the reinforcement process   For keeping the engineering insights from his peers for decades.  However his act of altering Citicorp to the problem inherent in his own design is now used as an example of ethical behavior in several engineering textbooks. Issues: CASE 5. THE CHALLENGER CASE After a lot of delays CHALLENGER’S 8th flight was set up for 28th Jan 1986 Allan McDonald of Morton – Thiokol who designed the solid–rocket booster knew the problems with the field joints on previous cold weather joints. And 28th Jan was expected to be cold. Seal experts Arnold Thompson and Roger Boisjoly of Morton – Thiokol, explained to NASA representatives how upon launch the booster rocket walls bulge and the combustion gases can blow past one or even both of the Orings that make up the field joints. The rings char and erode, as had been observed on many previous flights. In cold weather the problem is aggravated because the rings and the putty packing are less pliable then (more brittle) Senior Vice President Jerry Mason told Bob Lund (Vice President Engineering) “TO TAKE OFF YOUR ENGINEERING HAT AND PUT ON YOUR MANAGEMENT HAT”. The managers (not engineers) voted that the seals COULD NOT BE SHOWN TO BE UNSAFE. The count down ended at 11.38 AM. The temperature was 36 degrees. As the rocket carrying the Challenge Rose from the ground, cameras showed smoke emanating through the O rings. Soon these turned into a flame that hit the external fuel tank and a strut holding the booster rocket. The hydrogen in the tank caught fire, the booster rocket broke loose, smashed into Challenger’s wing, then into the external tank. At 76 seconds into the flight, by the time Challenger and its rocket had reached 50,000 feet, it was totally engulfed in a fire ball. The crew cabin separated and fell into the ocean, killing all abroad. Mission Commander: Francis Scobee. Pilot: Michael Smith. Mission specialist: Gpegory Jarvis, Ronald McNair, Ellison Onizuka, Judith Resnick. Teacher in space: Christa MacAuliffe (Chosen from 11,000 applicants) Issues: SAMPLE CODES Babylon’s Building Code (Hammurabi’s Code) If a builder has built a house for a man and has not made his work sound, and the house which he has built has fallen down and so caused the death of the house-holder, the builder should be put to death …………… CODE OF ETHICS FOR ENGINEERS THE FUNDAMENTAL PRINCIPLES Engineers Uphold and advance the integrity, honor and dignity of the engineering profession by: I.Using their knowledge and skill for the enhancement of human welfare; II. Being honest and impartial, and serving with fidelity the public, their employers and clients: III. Striving to increase the competence and prestige of the engineering profession; and I.Supporting the professional and technical societies of their disciplines. Fundamental Canons 1. Engineers shall hold paramount the safety, health and welfare of the public in the performance of their professional duties. 2. Engineers shall perform services only in the areas of their competence. 3. Engineers shall issue public statements only in an objective and truthful manner. 4. Engineers shall act in professional matters for each employer or client as faithful agents or trustees, and shall avoid conflicts of interest. 5. Engineers shall build their professional reputation on the merit of their services and shall not compete unfairly with others. 6.Engineers shall act in such a manner as to uphold and enhance the honor, integrity and dignity of the profession. 7. Engineers shall continue their professional development throughout their careers and shall provide opportunities for the professional development of those engineers under their supervision. CONCLUDING REMARKS When you leave this Lecture Hall today you must leave with the knowledge and conviction that you have a professional and moral responsibility to yourselves and to your fellow human beings to defend the truth and expose any questionable practice that will lead to an unsafe product or process REFERENCES 1. Martin, Mike & Schinzinger, Engineering, 3rd Ed. McGraw Hill Ronald: Ethics in 1. http://temp.onlinethics.org/cases/robot/article- 1.htm/ Includes the 2016 Cases! The NSPE Ethics Reference Guide NSPE Ethics Reference Guide Table of Contents Page Foreword ……………………………………………………………………………………… 1 Engineers’ Creed ………………………………………………………………………….. 2 NSPE Code of Ethics ………………………………………………………………….3-4 Subject Reference Guide to NSPE Code of Ethics ……………………………. 5 Consolidated Table of Contents to the Opinions of the Board of Ethical Review ………………………………………………………..6-19 NSPE Code of Ethics Case Index ……………………………………………..20-23 (4/17) Board of Ethical Review Cases Honesty, justice and courtesy form the moral philosophy which, associated with mutual interest among mankind, constitute the foundation of ethics. The engineer should recognize such a standard, not in passive observance, but as a set of dynamic principles guiding the engineer’s conduct and way of life. It is the engineer’s duty to practice according to these Canons of Ethics. Foreword Professionalism and ethics are twins, inseparably bound together in the concept that professional status and recognition must be based upon public service under a higher duty than mere compliance with the letter of the law. Ethics provides the framework within which engineers may travel the “second mile,” so ably defined by Dr. William E. Wickenden, former president of Case Institute of Technology: It is in the spirit of these cogent observations and principles that the National Society of Professional Engineers (NSPE) has adopted a Code of Ethics to lend aid and understanding to all engineers who strive for the dignity and true worth of the professional. Every calling has its mile of compulsion: Its round of tasks and duties, its prescribed man-toman relationships, which one must traverse daily if one is to survive. Beyond that is the mile of voluntary effort where one strives for special excellence, seeks self-expression more than material gain, and gives that unrequited margin of service to the common good which invests work with a wide and enduring significance. The best fun of life and most of its durable satisfaction lies in this second mile and it is only here that a calling can attain the dignity and distinction of a profession. This Code of Ethics is the result of extensive study and deliberation by the NSPE Board of Ethical Review, the review of the codes of ethics of engineering societies and those of other professions, and consultations with a broad cross section of the engineering profession. A code of ethics is not a static document; its purpose is to live and breathe with the profession it serves. Experience and changed circumstance will require continual review and revision of this Code of Ethics to reflect the growing understanding of engineering professionalism in public service. Comments and suggestions from all members of the engineering profession are solicited toward this end. The voluntary assumption of a higher duty imposed by individual conscience is the root principle of ethics. The Foreword of the 1947 ECPD Canons of Ethics expresses these principles for the professional engineer in the following terms: 1 Engineers’ Creed As a Professional Engineer, I dedicate my professional knowledge and skill to the advancement and betterment of human welfare. I pledge: To give the utmost of performance; To participate in none but honest enterprise; To live and work according to the laws of man and the highest standards of professional conduct; To place service before profit, the honor and standing of the profession before personal advantage, and the public welfare above all other considerations. In humility and with need for Divine Guidance, I make this pledge. Adopted by National Society of Professional Engineers June, 1954 2 3 4. Engineers shall act for each employer or client as faithful agents or trustees. a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services. b. Engineers shall not accept compensation, financial or otherwise, from more than one party for services on the same project, or for services pertaining to the same project, unless the circumstances are fully disclosed and agreed to by all interested parties. c. Engineers shall not solicit or accept financial or other valuable consideration, directly or indirectly, from outside agents in connection with the work for which they are responsible. d. Engineers in public service as members, advisors, or employees of a governmental or quasi-governmental body or department shall not participate in decisions with respect to services solicited or provided by them or their organizations in private or public engineering practice. e. Engineers shall not solicit or accept a contract from a governmental body on which a principal or officer of their organization serves as a member. 3. Engineers shall issue public statements only in an objective and truthful manner. a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current. b. Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter. c. Engineers shall issue no statements, criticisms, or arguments on technical matters that are inspired or paid for by interested parties, unless they have prefaced their comments by explicitly identifying the interested parties on whose behalf they are speaking, and by revealing the existence of any interest the engineers may have in the matters. qualified by education or experience in the specific technical fields involved. b. Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control. c. Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment. 2. Engineers shall at all times strive to serve the public interest. a. Engineers are encouraged to participate in civic affairs; career guidance for youths; and work for the advancement of the safety, health, and well-being of their community. b. Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project. c. Engineers are encouraged to extend public knowledge and appreciation of engineering and its achievements. d. Engineers are encouraged to adhere to the principles of sustainable development1 in order to protect the environment for future generations. 1. Engineers shall be guided in all their relations by the highest standards of honesty and integrity. a. Engineers shall acknowledge their errors and shall not distort or alter the facts. b. Engineers shall advise their clients or employers when they believe a project will not be successful. c. Engineers shall not accept outside employment to the detriment of their regular work or interest. Before accepting any outside engineering employment, they will notify their employers. d. Engineers shall not attempt to attract an engineer from another employer by false or misleading pretenses. e. Engineers shall not promote their own interest at the expense of the dignity and integrity of the profession. III. Professional Obligations 5. Engineers shall avoid deceptive acts. a. Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates’ qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments. b. Engineers shall not offer, give, solicit, or receive, either directly or indirectly, any contribution to influence the award of a contract by public authority, or which may be reasonably construed by the public as having the effect or intent of influencing the awarding of a contract. They shall not offer any gift or other valuable consideration in order to secure work. They shall not pay a commission, percentage, or brokerage fee in order to secure work, except to a bona fide employee or bona fide established commercial or marketing agencies retained by them. 1420 KING STREET • ALEXANDRIA, VIRGINIA 22314-2794 • 888-285-NSPE (6773) • LEGAL@NSPE.ORG • WWW.NSPE.ORG • PUBLICATION DATE AS REVISED JULY 2007 • PUBLICATION #1102 COPYRIGHT NATIONAL SOCIETY OF PROFESSIONAL ENGINEERS. ALL RIGHTS RESERVED. 2. Engineers shall perform services only in the areas of their competence. a. Engineers shall undertake assignments only when 1. Engineers shall hold paramount the safety, health, and welfare of the public. a. If engineers’ judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate. b. Engineers shall approve only those engineering documents that are in conformity with applicable standards. c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code. d. Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise. e. Engineers shall not aid or abet the unlawful practice of engineering by a person or firm. f. Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. II. Rules of Practice Engineers, in the fulfillment of their professional duties, shall: 1. Hold paramount the safety, health, and welfare of the public. 2. Perform services only in areas of their competence. 3. Issue public statements only in an objective and truthful manner. 4. Act for each employer or client as faithful agents or trustees. 5. Avoid deceptive acts. 6. Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession. I. Fundamental Canons Engineering is an important and learned profession. As members of this profession, engineers are expected to exhibit the highest standards of honesty and integrity. Engineering has a direct and vital impact on the quality of life for all people. Accordingly, the services provided by engineers require honesty, impartiality, fairness, and equity, and must be dedicated to the protection of the public health, safety, and welfare. Engineers must perform under a standard of professional behavior that requires adherence to the highest principles of ethical conduct. Preamble Code of Ethics for Engineers 4 Footnote 1 “Sustainable development” is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development. 9. Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others. a. Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments. b. Engineers using designs supplied by a client recognize that the designs remain the property of the client and may not be duplicated by the engineer for others without express permission. c. Engineers, before undertaking work for others in connection with which the engineer may make improvements, plans, designs, inventions, or other records that may justify copyrights or patents, should enter into a positive agreement regarding ownership. d. Engineers’ designs, data, records, and notes referring exclusively to an employer’s work are the employer’s property. The employer should indemnify the engineer for use of the information for any purpose other than the original purpose. e. Engineers shall continue their professional development throughout their careers and should keep current in their specialty fields by engaging in professional practice, participating in continuing education courses, reading in the technical literature, and attending professional meetings and seminars. 8. Engineers shall accept personal responsibility for their professional activities, provided, however, that engineers may seek indemnification for services arising out of their practice for other than gross negligence, where the engineer’s interests cannot otherwise be protected. a. Engineers shall conform with state registration laws in the practice of engineering. b. Engineers shall not use association with a nonengineer, a corporation, or partnership as a “cloak” for unethical acts. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action. a. Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated. b. Engineers in governmental, industrial, or educational employ are entitled to review and evaluate the work of other engineers when so required by their employment duties. c. Engineers in sales or industrial employ are entitled to make engineering comparisons of represented products with products of other suppliers. Note: In regard to the question of application of the Code to corporations vis-a-vis real persons, business form or type should not negate nor influence conformance of individuals to the Code. The Code deals with professional services, which services must be performed by real persons. Real persons in turn establish and implement policies within business structures. The Code is clearly written to apply to the Engineer, and it is incumbent on members of NSPE to endeavor to live up to its provisions. This applies to all pertinent sections of the Code. It is further noted that as made clear in the Supreme Court decision: 1. Engineers and firms may individually refuse to bid for engineering services. 2. Clients are not required to seek bids for engineering services. 3. Federal, state, and local laws governing procedures to procure engineering services are not affected, and remain in full force and effect. 4. State societies and local chapters are free to actively and aggressively seek legislation for professional selection and negotiation procedures by public agencies. 5. State registration board rules of professional conduct, including rules prohibiting competitive bidding for engineering services, are not affected and remain in full force and effect. State registration boards with authority to adopt rules of professional conduct may adopt rules governing procedures to obtain engineering services. 6. As noted by the Supreme Court, “nothing in the judgment prevents NSPE and its members from attempting to influence governmental action . . .” In order to correct misunderstandings which have been indicated in some instances since the issuance of the Supreme Court decision and the entry of the Final Judgment, it is noted that in its decision of April 25, 1978, the Supreme Court of the United States declared: “The Sherman Act does not require competitive bidding.” Statement by NSPE Executive Committee “By order of the United States District Court for the District of Columbia, former Section 11(c) of the NSPE Code of Ethics prohibiting competitive bidding, and all policy statements, opinions, rulings or other guidelines interpreting its scope, have been rescinded as unlawfully interfering with the legal right of engineers, protected under the antitrust laws, to provide price information to prospective clients; accordingly, nothing contained in the NSPE Code of Ethics, policy statements, opinions, rulings or other guidelines prohibits the submission of price quotations or competitive bids for engineering services at any time or in any amount.” 1420 K…
Purchase answer to see full attachment

Explanation & Answer:

1 Essay

Engineering Economy Making Annual Deposits in An Account Question

Engineering Economy Making Annual Deposits in An Account Question

Description

 

 

 

 

Explanation & Answer:

1 Question

UM Boeing 737 MAX Ethical Analysis Paper

UM Boeing 737 MAX Ethical Analysis Paper

Description

 

 

Paper Instructions

The purpose of this assignment is to demonstrate knowledge of key terms and concepts from the course materials and related readings. You will need to conduct additional research in other to answer the question(s) asked. The focus of your paper is to concentrate on the ethical concerns. Time spent on any technical math or science concerns is to be kept to a minimum. Your answers must devote much of the paper to an examination of the ethical issues, theories and solutions.

For this paper, you will write a paper of approximately 5 pages (approximately 1,500 words, 12 point font, 1 inch margins and 1.5 line spacing) on the topic provided below related data science ethics.

At least five (6) additional primary reference sources must be used and appropriately cited according to the APA style guide. Cites and quotes are necessary. Appropriate reference sources include case law, scholarly research papers, articles published in academic journals or government websites, but not personal webpages or Wikipedia. Traditional news articles may be used if necessary to provide appropriate context.

Submission of this Assignment must be made by the date and time indicated above in either Word or PDF format. Failure to submit on time, or in an improper format will not be accepted.The purpose of the paper is to develop a response to the ethical issues … not to restate the technical problems. A suggested breakdown of the paper is to have only one third of the content cover the technical engineering issues, and the remainder to discuss the ethical issues, the failures and solutions. In presenting the solutions, students are to consider what obviously what went wrong and how the engineers involved in the scandal performed their duties, did or did not follow corporate policy or other regulations, if criminal laws were broken … and how, if management was changed, new policies and procedures could be implemented to prevent a repeat of the disaster/tragedy/controversy. Just as in the Discussions, a review of the corporate culture and the breakdown in communication is necessary. Commentary and opinion matter … but, critically, there is a need for offering solutions backed up by use of the readings and references. A successful paper will review the issues and make use of the key terms and concepts from the readings. Each stakeholder will be mentioned, their perspective examined and, again, solutions will be offered.

Topic – BOEING 737 MAX PROBLEM

You are to apply the process of ethical analysis and apply theoretical ethical principles to the Boeing 737 Max case. Outside research will be necessary. You are to answer the following questions:

What were the technical problems in the case?

Who were the stakeholders in the case?

What were the ethical problems in the case?

What were the engineers’ responses to the ethical problems?

What were the corporate responses to the ethical problems?

What professional codes or standards were implicated?

What was the role of government oversight or regulation?

What are your recommendations about the 737 Max case?

How could it have been prevented?

A reminder again to cite and quote heavily. Consider the following references:

Boeing’s 737 Max Software Outsourced to $9-an-Hour Engineers

https://www.bloomberg.com/news/articles/2019-06-28/boeing-s-737-max-software-outsourced-to-9-an-hour-engineers

Ex-Boeing 737 MAX Engineer Says Team Was Pressured To Cut Costs As Grounding Continues

https://www.forbes.com/sites/isabeltogoh/2019/07/29/ex-boeing-engineer-says-workers-were-pressured-to-keep-costs-down-amid-737-max-grounding/#17149e782e9a

A former Boeing 737 Max engineer said he was ‘incredibly pressurized’ to keep costs down and downplay new features to avoid FAA scrutiny

https://www.businessinsider.com/boeing-737-max-former-engineer-pressure-costs-avoid-faa-scrutiny-2019-7

SPEEA engineer breaks silence on Boeing’s MAX 737. Read this letter

https://www.kuow.org/stories/boeing-engineers-break-silence-on-max-737-read-this-letter

 

Explanation & Answer:

5 pages

 

Master Petroleum Worksheet

Master Petroleum Worksheet

Description

 

 

Unformatted Attachment Preview

PETE 521 Engineering the Development of Unconventional Hydrocarbon Resources Lecture 8A: 1D Solutions Stress Interference: Between Perforation Clusters 1 Parts of this Lecture 1. US Shale Business News: Sale of Pioneer Natural Resources 2. Course Agenda Adjustments & Mid-Term Project Planning 3. 1D Stress Shadow Analysis Methodology 4. Strain Response Computations 2 Relax 3 Shale News • Oct 11, 2023: ExxonMobil acquires Pioneer via Merger; Pioneer suffered deeply during the oil price downturn. • Now sells for $59.5 billion; 856,000 acres; almost $70k/acre. • Jafurah 17,000 km2 ~ 4,200,792 acres; at $70k/acre Jafurah would be valued at $294 billion… • Pioneer currently has roughly 5,706 wells in production, Midland Basin. • Exxon says the acquisition represents 10 year drilling inventory replacement; 6,300 drilling locations (Enverus) • Previously, Dec 2009, ExxonMobil acquired XTO Energy in a $36 billion deal; 317,000 acres of the Marcellus. ? Scott Sheffield is one of the few Pioneer executives who will have a post-deal role – he is set to join Exxon’s board. 4 Oil Price DownTurn (2014-2020): Response and Performance Let’s briefly look at 4 companies: – Pioneer Natural Resources – South Western Energy – Range Resources – Laredo Energy Suffering during 2014-2020 downturn – First we look at Retained Earnings – Then at Headcount Reduction 5 WTI Crude Oil vs HH Natural Gas – 25 Year Daily Chart Tough Period US Shale Business 2014-2020 6 Pioneer Natural Resources Retained Earnings (Accumulated Deficit) 2006-2021 | PXD billions Excellent Financial mmt Acreage in Midland Basin Over its entire history, PXD generated ‘only’ $4 billion (+ dividends); is this company really worth $60 billion? 7 Pioneer Natural Resources: Number of Employees 2006-2021 | PXD 4,203 1,853 https://www.macrotrends.net/stocks/charts/PXD/pioneer-natural-resources/number-of-employees 8 Laredo Petroleum Retained Earnings (Accumulated Deficit) 2009-2021 | LPI Acreage in Midland Basin billions Disastrous Financial mmt Instead of Retained Earnings we see Accumulated Losses ($2.5 Billion) 9 Laredo Petroleum Number of Employees 2009-2021 | LPI 491 257 https://www.macrotrends.net/stocks/charts/LPI/laredo-petroleum/number-of-employees 10 Southwestern Energy Retained Earnings (Accumulated Deficit) 2006-2021 | SWN billions Acreage in Marcellus & Utica Shale Disastrous Financial mmt Instead of Retained Earnings we see Accumulated Losses ($7 Billion) 11 Southwestern Energy: Number of Employees 2006-2021 | SWN 2,781 900 12 Range Resources Retained Earnings (Accumulated Deficit) 2006-2021 | RRC billions Disastrous Financial mmt Instead of Retained Earnings we see Accumulated Losses ($4.5 Billion) 13 Range Resources Number of Employees 2006-2021 | RRC 990 533 https://www.macrotrends.net/stocks/charts/RRC/range-resources/number-of-employees 14 US E&P Bankruptcies (2015-2021) 15 Parts of this Lecture 1. US Shale Business News: Sale of Pioneer Natural Resources 2. Course Agenda Adjustments & Mid-Term Project Planning 3. 1D Stress Shadow Analysis Methodology 4. Strain Response Computations 16 2 Year Program MX-UHR Weijermars Mahmoud Ayranci Weijermars Ibrahim Abdulraheem Al Jawad 17 PETE 521 Course Plan 18 Mid-Term Project Compute a scalar measure for 1D stress intensity interference: • Start from Sneddon equations. Well Fracture Stage A • Simplify equations for our purpose. • First obtain some results in HW 8. Fracture Spacing B Perforation Cluster Toe • Then apply and complete analysis in Mid-Term Project, 3 fractures in the stage. 1D-analysis: along Lines A and B 19 Parts of this Lecture 1. US Shale Business News: Sale of Pioneer Natural Resources 2. Course Agenda Adjustments & Mid-Term Project Planning 3. 1D Stress Shadow Analysis Methodology 4. Strain Response Computations 20 Stress Shadowing Static Model • Complex process of stress and elastic strain interference initiated by spatial changes in the stress state around hydraulic fractures as they grow. • For adjacent fractures, if they are sufficiently close, we see interference of the stress changes induced by the opening of the fractures. Dynamic Model • Leads to curvature of the outer fractures and stumping off inner fractures. 21 Problem to be Solved Use Sneddon’s analytical solution. Let’s take a closer look at Sneddon equations (again) – good stuff never tires! Well Fracture Stage A A Fracture Spacing B Perforation Cluster B Toe C 1D-analysis: along lines A and B Simplified solutions we have previously used (HW3) for the 1D-solution along Line C. • Let’s look at that again, and see how it was obtained ( x2 =0 and θ= θ1= θ2=0). • Then we will do something similar for Lines A and B. 22 Sneddon Stress-Test Solution Simplified Solution   x3  xx = pNET 1 − 2 2 3/2   (x + L )   x3 + 2 xL2   yy = pNET 1 − 2 2 3/2   (x + L )   zz =  ( xx −  yy ) Fracture half-length = 100 ft Pnet =200 psi C 23 Sneddon Stress Function Solution 1. Radial coordinates to Cartesian: 2. The induced stress (delta): what is added to the existing stress due to opening of the crack (hydraulic fracture): Sneddon’s original solution is for Plane Strain boundary condition, meaning we have Δε33=0 ; so therefore Δσ33>0 3. Parameters affecting induced stress: • Fracture half-length (Wf or a) • Net pressure =pfrac-ppore-shmin (deviatoric) • Location (r, r1, r2, θ, θ1, θ2) distance to the fracture) • Poisson ratio v 24 Full Stress Tensor Solutions Pnet=200 psi; Wf=100 ft 25 Full Stress Tensor Solutions Pnet=200 psi; Wf=100 ft 26 Assignment HW8, Part A • Determine the simplified solution for the stress tensor elements along Line A • Plot the three solutions. • Also compute the associated strain tensor elements along Line A Pnet=2000 psi; Wf=100 ft 27 Parts of this Lecture 1. US Shale Business News: Sale of Pioneer Natural Resources 2. Course Agenda Adjustments & Mid-Term Project Planning 3. 1D Stress Shadow Analysis Methodology 4. Strain Response Computations 28 What is Strain? • Deformation of solids and fluids occurs due to a force causing displacement. • We can represent the force field by a stress tensor, and the displacement gradients by a strain tensor. • A constitutive equation links the stress and strain tensors Distortional displacements in elastic media and fluid bodies (dashed box region) can be described by compatibility equations (Weijermars and Ettehad, 2019). 29 For Non-Rigid Body Description of the elastic distortion process can take two possible paths: 1. Force -> Stress -> Strain 2. Displacement -> Strain-> Stress Whatever solution path you take, for elastic body deformation you’ll need to use the stress tensor Rigid Body Translation 1 2 http://www.conceptualdynamics.com/files/rbnewt/rbnewt_tran_page1.htm For rigid-body translation, no internal stresses need be computed to solve the displacement. There may be (elastic) stresses on the car body, but these are irrelevant for the rigid body dynamics. 30 Strain Tensor in Sneddon Context Sneddon’s original solution is for a Plane Strain boundary condition, meaning we have Δε33=0 ; so therefore Δσ33>0. So we only need to consider strains in the (x,y)-plane (because Δε33=0). What are these strains in the (x,y)-plane? Constitutive equation: σij=Cijkl = εij or For general 3D strain condition: 31 Strain Tensor for Plane Stress For general 3D Stress State For Plane Stress 32 Tensors for Plane Strain ε33=0 Sneddon gives you the stresses, and the associated strains follow from above constitutive equations 33 Written Out for Plane Strain Knowing the strain is interesting, because you can start to think how it may affect the aperture of a central fracture incase we have three perforation clusters per stage 34 Poisson Ratio = 0 No distinction between plane stress and plane strain possible when the Poisson ratio is zero; 35 Assignment HW8, Part A • Determine the simplified solution for the stress tensor elements along Line A • Plot the three solutions. • Also compute the associated strain tensor elements along Line A Pnet=2000 psi; Wf=100 ft 36 PETE 521 Engineering the Development of Unconventional Hydrocarbon Resources Lecture 8B: 1D Solutions Stress Interference: Between Fracture Tips 1 Cartoon of the Week 2 Parts of this Lecture 1. Line B solutions Frac Tip stresses 2. Stress Superposition 3. Proppant crushing 4. Proppant embedment 5. Mid-Term Project: What inputs are needed for a “realistic” or useful 1Dstress interference analysis? 3 Assignment HW8, Part B • Determine the simplified solution for the stress tensor elements along Line B • Plot the three solutions. • Also compute the associated strain tensor elements along Line B Pnet=2000 psi; Wf=100 ft Well Fracture Stage A Fracture Spacing B Perforation Cluster Toe 1D-analysis: along lines A and B Line B stresses trickier than Line A stresses, because: • Along line B the tensor elements are no longer principal stresses, there are shear stresses. • The principal stress orientations are systematically rotating as we move along line B. 4 Stress Trajectories • Stress trajectories show the principal stress orientations and how they rotate in space. • For the hydraulic fractures, see how the principal stress orientations change spatially. a) Prior to Fracturing b) During Fracturing A B Line B stresses is trickier than Line A stresses, because: • Along line B the tensor elements are no longer principal stresses, there are shear stresses. • The principal stress orientations are systematically rotating as we move along line B. 5 Stress Trajectories • Stress trajectories are tangent lines of the principal stresses (σ1 and σ2 ). Trajectories • Given by Isoclines • Tangent lines give stress trajectories • Contouring of same values give socalled stress trajectory isoclines 6 Line B solutions Use Sneddon’s analytical solution A B C 1D-solution along Line C really easy, because all angles in Sneddon become 0. 1D-solution along Line A also easy, because Ɵ=90, Ɵ1+Ɵ2 =180, r1=r2 and r=r1sinƟ1. 1D-solution along Line B: Ɵ2=90, r2=r sinƟ, more simplification? 7 Sneddon Stress Function Solution 1. Radial coordinates to Cartesian: 2. The induced stress (delta): what is added to the existing stress due to opening of the crack (hydraulic fracture): Sneddon’s original solution is for Plane Strain boundary condition, meaning we have Δε33=0 ; so therefore Δσ33>0 3. Parameters affecting induced stress: • Fracture half-length (Wf or a) • Net pressure =pfrac-ppore-shmin (deviatoric) • Location (r, r1, r2, θ, θ1, θ2) distance to the fracture) • Poisson ratio v 8 Strain and Stress Tensors for Plane Strain Knowing the strain is interesting, because you can start to think how it may affect the aperture of a central fracture incase we have three perforation clusters per stage 9 Parts of this Lecture 1. Line B solutions Frac Tip stresses 2. Stress Superposition 3. Proppant crushing 4. Proppant embedment 5. Mid-Term Project: What inputs are needed for a “realistic” or useful 1Dstress interference analysis? 10 Stress Superposition a) Prior to Fracturing • Stress superposition along Line A easy, because all stresses are principal stresses: σ11= σ1; σ22= σ2; σ33= σ3 • Nice thing about principal stresses is that you can simply sum them. • But as soon as there as the principal axes are angled with respect to the coordinate system, as applied to Line B, the tensor components need to be added using tensor addition rules, which involves the angles made by the principal stresses to the coordinate system axes. b) During Fracturing A B • Cumbersome to work with the stresses; one can switch to the strains and superpose them. Because the strains can be related to displacement vectors. 11 Shift Fracture and Superpose 12 Strain Doubling Up • Between two adjacent fractures, the displacements will double up but in a mirrored fashion. • If the distance is d, the total strain due to superposition is: • Total εyy(y)= εyy(y) + εyy(d-y) y d X • Same for principal stresses 13 Parts of this Lecture 1. Line B solutions Frac Tip stresses 2. Stress Superposition 3. Proppant crushing 4. Proppant embedment 5. Mid-Term Project: What inputs are needed for a “realistic” or useful 1Dstress interference analysis? 14 Proppant Strength •During hydraulic fracturing, we open the fractures by hydraulic fluid ‘transmitting’ the pressure •But after flowback, the elastic strain in the wall of the fracture wants to snap back and relax •The proppant must prevent fracture closure from happening •The relaxing elastic strain will exert point load pressures on the proppant grains; will the grains survive the pressure? 15 Micro-Proppant Tests TBA= Tetrabromobisphenol A and borosilicate mixture Mineral powder used was byproduct of pig iron smelting TBA 16 Mineral Powder Least Crush Mineral Powder gave highest Perm but at high closure stress loses its lead 17 Production Simulation Fracture Morphology Results suggest the micro-proppant boosts the well rate and cumulative 18 Data was from below paper 19 Parts of this Lecture 1. Line B solutions Frac Tip stresses 2. Stress Superposition 3. Proppant crushing 4. Proppant embedment 5. Mid-Term Project: What inputs are needed for a “realistic” or useful 1Dstress interference analysis? 20 Proppant Embedment Tremendous stresses where there are arches, pillars, low proppant concentrations, etc The complex geometries of hydraulic fracs are pushing companies towards using smaller, higher strength proppants to achieve greater transport and conductivity SPE 90698 21 Proppant Mechanisms during Flowback Katende et al., 2021 22 Impact on Production Katende et al., 2021 N Dakota (Besler et al., 2007) Weijermars (ARMA-IGS-2023-446) 23 Models for Mechanical Embedment Embedment Model Reviewed in Katende et al. (2021) 24 Parts of this Lecture 1. Line B solutions Frac Tip stresses 2. Stress Superposition 3. Proppant crushing 4. Proppant embedment 5. Mid-Term Project: What inputs are needed for a “realistic” or useful 1Dstress interference analysis? 25 Mid-Term Project Compute stress shadow magnitudes along lines A&B for a stage with three fractures. Show how the stress changes during the frac job fro a central fracture and for an outer fracture. What will be the final fracture aperture close to the perfs? Investigate in Sensitivity Analysis effect of reduced fracture spacing. How will the fracture aperture be affected? Assume proppant pads are emplaced near the perforations. What will be the proppent embedment after flow back? What crushing occurs? What will be the fracture aperture? 26 Inputs Needed? • Sneddon computes the change in stress in response to PNET • We can use the PFrac computed by Oshaish & Weijermars in ARMA paper, showing how it accumulates during the pump job. • Ppore is the reservoir pressure. • And σ3 = ISIP from frac report. PNET=Pfrac-Ppore-σ3 • Elastic properties follow from the geomechanical tests on core, or from the velocity logs in the well. • Values will all be given with HW8. 27 Stress Shadowing Static Model • Complex process of stress and elastic strain interference initiated by spatial changes in the stress state around hydraulic fractures as they grow. • For adjacent fractures, if they are sufficiently close, we see interference of the stress changes induced by the opening of the fractures. Dynamic Model • Leads to curvature of the outer fractures and stumping off inner fractures. 28
Purchase answer to see full attachment

Explanation & Answer:

1 Worksheet