SUP.1 Quality Assurance | Automotive SPICE
HTML-код
- Опубликовано: 1 авг 2024
- Learn the 3 most important steps to implement the ›Quality Assurance‹ process properly and effectively. Want more? Download a detailed Quality Assurance whitepaper on our site:
White paper in ENGLISH: www.kuglermaag.com/sup1
White paper in GERMAN: www.kuglermaag.de/sup1
🎓 If you want to learn more about Automotive SPICE and become a process improvement expert, check out our training: www.kuglermaag.com/training-a...
-------------------------------------------------------------------
Content
00:00 - Intro
00:22 - Speaker
00:58 - Why does Quality Assurance matter?
02:43 - 1. Have a Quality Assurance strategy
04:56 - 2. Set up effective Quality Assurance methods
06:22 - 3. Solve the Quality problems
07:50 - Outro
-------------------------------------------------------------------
The experts of Kugler Maag Cie provide this free Quality Assurance tutorial for beginners and those who are new in the field of process improvement and Automotive SPICE.
This is your channel if you need knowledge on process improvement topics: Automotive SPICE, Functional Safety, Agile methods and Cybersecurity. We're publishing videos on a regular basis. Subscribe to this channel if you don't want to miss our videos.
Do you need further information? Contact us or leave a comment below!
#automotive #automotivespice #processimprovement
Thanks Hoermann for explaning this.
As explained that QA need to discuss the due date with development engineer. If he/she provides an unrealistic due date to QA, what should be done in this case?
Thanks for the question. If fixing the issue is business critical (e.g., it needs to be fixed before the next customer release), it should be escalated to management immediately. Let's take the complete opposite: if the problem is trivial/unimportant, I would just accept the date. In other words: Choose your battles wisely :)
Hello! Thanks for the nice explanations. What is the relation between quality assurance process and process improvement process? Can we cover process improvement in quality assurance? Is it too complicated to do like this? Will there be a recording for Process improvement? Thanks in advance...
Hi!
There is one very powerful connection between both processes: you can derive valuable process improvement information from the reviews and audits that the independent quality engineers perform. Otherwise these two processes have no real commonalities or synergies.
Mit freundlichen Gruessen / Best regards / Yoroshiku Onegai Shimasu / 致以亲切的问候
Dr. Klaus Hoermann
Hoermann, nicely explained. Can you also share role of a Quality Engineer if escalation mechanism doesn't work effectively.
Thank you, Raspreet, for your comment.
It depends on how the "independence" is implemented. Let's say the quality engineer escalates first to engineering management directly and they don't cooperate. In this case the quality engineer could still escalate through the quality organisation.
If there is no real quality organisation and the quality engineer reports directly to a high level engineering manager and this person does not react, he is in a cul de sac.
Best regards
Dr. Klaus Hoermann
In my experience, independent quality assurance only works if senior management supports an effective escalation mechanism. In particular in case of critical quality deviations before customer delivery at the end of a release cycle, related risks must be identified and carefully analyzed. If serious risks exist, the customer must get involved in the release approval. If the development team can just ignore those risks and deliver due to time pressure, the role of the Quality Engineer and most of the associated effort is meaningless.
Thanks for the great video. Does a paper or other documentation exist on Aspice for product lines? As far as I know, there is a reuse process in Aaspice, but also something beyond that?
@Tjomati thank you very much for your question! Yes, the reuse process is a bit older, but unfortunately there is no process for product lines. Some larger companies have created very efficient solutions with product line management. This usually works in such a way that there is a platform project and numerous customer projects that work together in close coordination. With new functionality, it is always checked whether something is customer-specific and remains so, or whether it will be available to all future projects via the platform.
Hello team 👋 nice explanation !can you send me the link for English version of white paper.for all the process areas English version of white paper is not available,it would be great if you share all white papers link
Hello Ramakrishna, we are happy to read that you appreciated the video! We have updated the link, now the white paper for Quality Assurance is ready to be downloaded in English too. Here is the link: www.kuglermaag.com/fileadmin/05_CONTENT_PDF/05_WHITEPAPER/whitepaper_automotive-spice_en_sup1_quality-assurance.pdf
Enjoy!
Hello , Thanks for Very good presentation on Quality Assurance Process.i am uanble to open the white paper on Quality Assurance can you please share the link.Thank you very much.
Hi there, we're glad you liked it! Please use the following link to download the Quality Assurance Process white paper: www.kuglermaag.com/automotive-spice/sup1-quality-assurance/. We hope this helps! In case you should experience any further issues, please let us know :).
I would at one point to bad quality that it can lead in los of business.
Hello emesde,
you're right, quality first. Let's go one step further: Quality, or the lack of it, was the underlying driver for the introduction of Automotive SPICE. So no quality without qa and no customers without quality. So welcome in the world of process improvement.
Cheers, Your video team at Kugler Maag Cie
@@KUGLERMAAGCIE At our company we follow the processes of ISO9001 (ISO90003) and iso26262 . What would aspice add to this?
Hello emesde,
QA is on processes in general, not on development related processes in particular. The scope of Functional Safety in accordance with ISO 26262 is the whole E/E system: the system view plus the HW and SW domains. And, additionally, the time after the start of production. The scope of Automotive SPICE, contrary, is limited to the system view and the SW domain perspective. There, Automotive SPICE builds the foundation for reliable system/SW engineering capabilities. You can use these capabilities as a base for FS. This is why I won't speak about adding something to your FS activities. With Automotive SPICE, you produce the outcomes you need for your quality and safety activities in a reliable manner. The concepts are complementary.
Cheers, your video team at Kugler Maag Cie