Chad Kymal is the CTO and founder of Omnex Inc., an international consulting and training organization headquartered in the United States. After graduating from the General Motors Institute, Chad spent a number of years working at General Motors and KPMG before founding Omnex Inc. in 1986. Over the course of Chad’s successful career, he has served on the Malcolm Baldrige Board of Examiners and has received numerous quality achievement awards, including the Quality Professional of the Year award by the American Society for Quality (ASQ) Automotive Division in 2005. In addition to his bachelor’s degree from GMI, Chad holds both a master’s degree in industrial and operations engineering from the University of Michigan and an MBA from the University of Michigan.
Chad both developed and teaches auditor training for ISO 9001, ISO 14001, and OHSAS 18001 / ISO 45001, as well as an Integrated Management Systems Lead Auditor training course where all three standards are combined in a single audit. Chad is the founder of AQSR, a global registrar that routinely provided integrated audits in QMS, EMS, and OHSMS.
Omnex has been working in the Automotive industry for 30 years and Omnex principals been active in writing different automotive standards including QS 9000, ISO TS 16949, Semiconductor Supplement, APQP, FMEA and Core Tools.
Chad is the author of seven books and more than 100 papers including several on integrated management systems.
Planning a Winning Safety Case- ISO 26262 relevant
Chad Kymal is the CTO and founder of Omnex Inc., an international consulting and training organization headquartered in the United States. After graduating from the General Motors Institute, Chad spent a number of years working at General Motors and KPMG before founding Omnex Inc. in 1986. Over the course of Chad’s successful career, he has served on the Malcolm Baldrige Board of Examiners and h...read more
One of the key requirements of ISO 26262 for new products is a Safety Case. They are similar in many ways with PPAP documents in that they show the evidence that ISO 26262 has been conformed to successfully. Additionally, ISO 26262 Conformation Measures and Functional Safety Assessments review Safety Cases. Furthermore, the Distributed Interface Agreement or DIA established between a customer and a supplier can include a Safety Case Review based on ASIL levels. In short, Safety Cases are an important output of the ISO 26262 application, especially since the product cannot be released without an acceptable and conforming Safety Case.
Part 2 which is the normative (or auditable) is the only part of the ISO 26262 that provides specific requirements for a Safety Case. In fact, it says “Safety Case is a comprehensive collection of work products generated as an item progresses in the safety life cycle.” Clear enough? Okay, so the project could simply collect all the work products of the Safety Life Cycle and the documents would constitute the safety case, right? Well, if this is all that is done, then we are most probably going to fail. What, then, constitutes a winning safety case?
When do we start a Safety Case? Is this like a PPAP, can we think about it at the end of the development? What should we do in the start, middle, and end to have a Winning Safety Case?
Interested in Membership?
Take charge of your career and education. Join us today and get access to a wealth of webinars covering cutting edge topics important in reliability engineering today!
Find out more