Eventually, the time for the projects to be released for production has come, the development team did all that was planned, every deadline was met, the customer is more than happy and has no objections. Everyone did their job perfectly, everything is in its exact place, all documentation is prepared and each step of each relevant process is followed and documented. There is nothing to fix, there are no gaps identified and the team can move to other exciting activities. 

يبدو هذا أشبه بالخيال؟ السبب أن الموقف المذكور أعلاه… لا يحدث أبدًا. 

In today’s interconnected world, functional safety (FuSa) is more critical than ever. Projects, especially those that are system-of-systems – incorporating multiple suppliers across different locations – bring their own set of challenges. And when deadlines approach, issues such as organisational differences, varying work cultures, and time-zone differences can intensify the pressure.

For industries like automotive, where safety-critical systems are at the core of all road vehicles, ISO 26262 provides a global standard for ensuring that systems meet rigorous safety requirements. This is especially true in systems that integrate both hardware and software, where the risk of failure can have devastating consequences. Verifying that an automotive application, a specific device or solution is fully reliable and compliant is crucial for protecting the life and health of users.

The real pressure point often arises when the project is nearing its final stages, and the critical tasks such as the “ISO 26262 Audit,” “Assessment,” “Safety Case Delivery,” or “FuSa Release Report” appear on the calendar. It’s at this point that the project and FuSa management team must reassess their approach to Functional Safety (FuSa).

لماذا نحتاج إلى التقييم على الإطلاق؟ وما هو الهدف؟

A Functional Safety (FuSa) assessment, audit, or safety case isn’t just a formality. It’s necessary to certify the compliance of safety-critical systems with the ISO 26262, a global standard for automotive safety. Without proper evidence, arguments about safety are weak, and without clarity, they are ineffective.

Presenting safety arguments in an organised manner, with all assumptions, limitations, and potential risks considered, is critical. Without reaching a consensus between stakeholders on the safety of the product, the risks remain unaddressed.

This is where preparation becomes key. Think of it as a marathon, much like the famous Ancient Greek race – there are no shortcuts. Every step, every piece of documentation, and every safety-related component must be in place to ensure success.

عملية التدقيق والتقييم 

إن عملية التحضير لتقييم ISO 26262 (تقييم FuSa) هي عملية منهجية. وبينما يقدم هذا المقال نظرة عامة، لمزيد من التفاصيل حول المعيار نفسه، راجعدليل ISO 26262.

Remember that the scope of the assessment may vary. In many cases, the development area might be limited (e.g., software development and testing lifecycle). The key to passing any assessment, however, lies in well-documented project materials.

Many projects falter due to poor or neglected documentation. You can’t avoid preparing bulletproof, robust, and diligent project documentation, as it can be the deciding factor in keeping up with the project schedules and passing or failing the assessment.

هل ترغب في معرفة المزيد عن ISO 26262؟

اقرأ دليلنا

كيف تستعد لتقييم السلامة الوظيفية 

بعدم الاستعداد، أنت تستعد للفشل – بنجامين فرانكلين 

Preparation is everything. Like any battle, an assessment should not be faced without thorough planning. Below are a few common steps which might seem trivial but often trip up even the most experienced teams as an Achilles’ heel in the entire assessment process.

هل جدول أعمال التقييم معروف لجميع الأطراف المعنية؟

Do we have a specific slot to discuss a given topic, and is each relevant team member aware of it? Ensure that all subject matter experts know the assessment topics and are ready to present their arguments or findings.

هل تُسنَد بنود التقييم إلى شخص محدد؟

حدد المسؤولية الواضحة عن كل مستند وتأكد من إسناد مهام محددة للخبراء المسؤولين. لست متأكدًا من المسؤول في مؤسستك عن أي مسؤوليات؟ إليكمن يجب أن يتولى السلامة الوظيفية.

هل هناك دليل على أنشطة محددة، وهل هو موثق جيداً؟

For software development, especially when using strongly typed languages like C or C++ for embedded systems, ensure that coding guidelines are followed and documented. Tools like static code analysis should provide proof that guidelines are being adhered to.

هل الدليل محدّث؟

Confirm that all safety analyses and documentation reflect the latest project version and include recent developments. Remember that e.g. safety analysis performed on the initial architecture might not consider safety-related components that were implemented in the latest release – assess if it is all up-to-date.

هل توجد "خطة إصلاح" للفجوات المحددة؟

If gaps are discovered during the assessment, track and resolve them systematically. Establish clear deadlines and responsibilities for any missing documents or incomplete tasks. If the Software Qualification Report is missing for a specific development tool, how is such a task tracked? Who is responsible for it? What is the deadline?

أفضل الممارسات في تقييم السلامة الوظيفية

عند التحضير لتقييم FuSa، تأكد من مراعاة النقاط التالية:

  • الامتثال والتوثيق: التأكد من أن جميع الوثائق ذات الصلة، مثل خطة السلامة وملف السلامة وتحليل المخاطر والأخطار (HARA)، محدّثة وتستوفي متطلبات ISO 26262.
  • أدوار ومسؤوليات واضحة: Ensure clear ownership for every safety-critical task, including coding guidelines, tool qualification, and safety analysis reviews. It will simplify the process, not only by helping to reduce the risk of overlooking an important step, but also by allowing each task owner to take care of it in a comprehensive way.
  • التحقق والتحقق من الصحة: Confirm that all safety-related work products, including those from ASIL B projects, are reviewed using appropriate methods such as technical reviews, walk-throughs, or inspections. Reviews should consider the required level of independence and the relevant technical roles, and be verified by qualified independent technical experts

كلمات ختامية: تحقيق شهادة ISO 26262 بدعم من الخبراء 

Your project’s release for production depends on the outcome of the FuSa assessment. If you’re unsure where to start or how to prepare for the assessment, consider a pre-assessment evaluation. This process can help you identify potential issues and address them proactively.

Our Spyrosoft Functional Safety team has hands-on experience in preparing and passing assessments for various major OEMs. We understand the complexities of FuSa and, based on our expertise, can provide guidance to ensure that your project meets all ISO 26262 standard compliance requirements.

لمزيد من المعلومات، قم بزيارة موقعنا واتصل بنا.

A FuSa assessment is an independent evaluation that determines whether a system meets the requirements of ISO 26262. It typically includes a review of documentation, development processes, and risk analysis, ensuring that safety objectives for automotive systems are met.

Ideally, you should begin preparing early in the project lifecycle. Waiting until the release phase often leads to delays, as documentation gaps, missing safety analyses, or tool qualification issues can be time-consuming to resolve.

تشمل بعض أكثر العوائق شيوعاً:
• وثائق السلامة غير المكتملة أو القديمة
• نقص الأدلة على إرشادات الترميز أو تأهيل الأدوات
• تتبع مفقود أو ضعيف
• مسؤوليات غير محددة للأنشطة المتعلقة بالسلامة
• ثغرات في مراجعات التحقق أو التأكيد
يمكن تجنب كل هذه الأمور من خلال أدوار واضحة والتخطيط المبكر والمراجعات الداخلية المنتظمة.

Functional Safety is a shared responsibility across multiple roles in the organisation. Typically, the Functional Safety Manager oversees the safety process, ensuring all requirements are met. The System Architect integrates safety features into the design, while Software and Hardware Engineers ensure compliance with safety standards. Safety Engineers conduct hazard analyses, and Verification and Validation Teams ensure safety measures are correctly implemented. Ultimately, the Project Manager coordinates these efforts, ensuring deadlines and safety milestones are met.

While both involve evaluating compliance, an assessment focuses on whether the product meets ISO 26262 objectives for Functional Safety. An audit usually checks if processes and procedures are followed. The assessment is the step that supports the safety case and the product release decision.

تشمل المخرجات النموذجية:
• خطة السلامة
• ملف السلامة
• تحليل المخاطر والأخطار (HARA)
• مفاهيم السلامة الوظيفية والتقنية
• خطط وتقارير التحقق والتحقق من الصحة
• خطط وتقارير تأهيل الأدوات
• سجلات مراجعة التأكيد
يجب أن يكون كل منها حديثًا وقابلًا للتتبع ومصممًا وفقًا لنطاق المشروع.

If any gaps are identified, they must be tracked, prioritised, and resolved. A strong repair plan with clear responsibilities and deadlines is crucial. In many cases, a pre-assessment or internal dry run helps uncover and address issues earlier. You can also explore Spyrosoft’s Automotive Functional Safety Analysis support offer.