.svg)
Training Competent Functional Safety Systems Engineer
Your path to becoming a Certified Competent Safety Systems Engineer
Why this training?
The "Safety Systems Engineer" training course provides detailed preparation for the successful completion of a Systems developer's tasks in accordance with ISO 26262:2018.
The special thing about our training courses for functional safety:
- Theory and practice are given equal weight
- Over one hundred training questions come with each certification course
- Live or on-demand online learning at any time of the day - anything is possible.
Training core information
-10% for freelancers/private individuals
Experience in developing embedded systems is recommended.
What you'll learn
- Concept Phase
- System Development
- System Verification
- Supporting Processes
Why with Knüvener Mackert?
More information about the training
1. Objective
The training seminar "Safety Systems Engineer" contains the detailed preparation for successfully completing the tasks of a Systems developer in accordance with ISO 26262:2018.
For enabling the developer to successfully collaborate with the safety manager, the basics of the safety management are explained, together with the typical supporting processes that a developer is using throughout the project.
The Safety Systems Engineer has detailed knowledge of the requirements of the ISO 26262:2018 towards a safe Systems development, including the correct understanding of the V development model. The approach to random Systems failures and quantitative measures are well known after the training.
The respective competence is established by applying this knowledge to a simple piece of Systems in a group work exercise. In this exercise, central work products for functional safety are created, including requirements, architecture, design, reviews, and safety analysis.
Theory (Level 1)
1. Theoretical Content
The theoretical part contains both the expectations from the ISO 26262:2018 towards the project and organization, as well as a self-check with training questions in the style of the examination. The online training is spread over four training sprints and one examination sprint. Each sprint has the theoretical elements available as online content that can be viewed, suspended, resumed, and repeated at any time. In addition, there are dedicated time slots each sprint for asking the training questions that arise during the theoretical part.
2. Theoretical Examination
The knowledge achieved on functional safety is tested in a multiple-choice examination. As the examination is designed as an on-demand online examination, you can take your time to prepare and select your favorite time to take the exam. Upon successful completion of the theoretical examination, the first certification level, the "Certified Safety Systems Engineer" is achieved.
Practical (Level 2)
3. Practical Exercise
The practical part is designed synchronously with the theoretical part and puts an equal focus on practical exercises that allow the trainees to gain vital understanding on how to achieve work products compliant with ISO 26262:2018. The practical exercise sends the group to create typical work products for a safety related development according to ISO 26262:2018. Within the group, discussions and exchange of experience enhances the learning experience, being supplemented with trainer meetings as part of the practical examination.
4. Practical Examination
The practical exercise is accompanied with the practical examination, where the trainer is providing feedback to the created content with the rigor that will be encountered in functional safety assessments. The respective examination record is shared with the team each sprint and rates the degree of conformity with review questions answered by the trainer. This allows the trainer to provide detailed feedback on the actual competence presented and prepares the team for any upcoming functional safety assessment. Upon successful completion of the theoretical and practical examination, the second certification level, the "Certified Competent Safety Systems Engineer" is achieved.
2. Content
Training Sprint 1: Concept Phase
Introduction to ISO 26262 (ISO 26262:2018−2, Clause 4)
Introduction to functional safety and core aspects for achieving this. The ISO 26262 is introduced and explained, including how to read this standard.
Item Definition (ISO 26262:2018−3, Clause 5)
The item definition is a central specification for all safety-related development in the context of the whole vehicle. It not only defines the scope of the safety lifecycle and is the basis for all development activities, but also serves as the central synchronisation document between this item and the other items of the vehicle.
Hazard Analysis and Risk Assessment (ISO 26262:2018−3, Clause 6)
The Hazard Analysis and Risk Assessment is determining the technical risk emanating from the vehicle in the different operating scenarios and classifies this risk into the ASIL. Based on this ASIL that has been determined for a representative set of operational scearios, the Safety Goals are defined as top-level safety requirements for the item. This module explains this whole evaluation procedure step-by-step.
Functional Safety Concept (ISO 26262:2018−3, Clause 7)
The Functional Safety Concept sets the path for achieving safety for the item at vehicle level. It includes functional degradation, user interactions, and requirement from and to other items.
Documentation Management (ISO 26262:2018−8, Clause 10)
This module explains the definition and handling of the documentation that is the basis for the Safety Case and the Release for Production. It discusses the differences between work products and documents, as well as expected document properties and attributes.
Training Sprint 2: System Development
Requirements Management (ISO 26262:2018−8, Clause 6)
The hierarchical structure of the safety requirements are explained as well as their proper notation. Both expectations on individual requirements as well as the entire set of requirements are explained. This module finishes with a detailed discussion on requirement verification and a short explanation of ASIL tailoring.
Technical Safety Concept (ISO 26262:2018−4, Clause 6)
This module addresses the systems level design activities. The iterative nature of the system level and its boundaries are explained, followed by a detailed discussion on the definition of the technical safety concept and its technical safety requirements. The iteration loop of achieving functional safety is explained as well as its exit criteria: the hardware metrics.
Architectural Design (−)
Generic introduction to the concept of architectures that can be applied in any discipline - system, hardware, or software. We discuss the iterative nature of architectural design and discuss what an architectural design process is all about. This modules concludes with the expected verification activities.
System Architectural Design (ISO 26262:2018−4, Clause 6)
System architecture in compliance with ISO 26262. This module covers the system breakdown structure required, the architectural desig process at system level as well as the ASIL allocation methodology. The core architectural concepts are explained using a small example.
Verification (ISO 26262:2018−8, Clause 9)
This module covers the generic approach to verification used throughout the safety lifecycle. The three main pillars of verification are introduced: Verification, Testing and Analysis. Their interactions are explained and the generic safety verification process is detailed.
Training Sprint 3: System Verification
Testing (ISO 26262:2018−8, Clause 9)
This module covers the expectations for the tests performed in a safety lifecycle. The testing process is explained in detail with all the expected work products. This is followed by a discussion of the two main categories of testing: functional testing and robustness testing. Finally, some specific test environments are considered.
Hardware-Software integration (ISO 26262:2018−4, Clause 7)
A general Introduction to the system integration, followed by the requirements on the first integration step: the hardware-software integration.
System and Item Integration (ISO 26262:2018−4, Clause 7)
The requirements on the intermediate integration steps of a vehicle from the lowest system level up to the item.
Vehicle Integration (ISO 26262:2018−4, Clause 7)
How to integrate and test the integrated item into the vehicle.
Safety Validation (ISO 26262:2018−4, Clause 8)
How to demonstrate that the item is safe when used within the vehicle. The validation is the counter-part of the concept phase on the right leg of the V development cycle.
Safety Analysis (ISO 26262:2018−9, Clause 8)
The concepts explained in this module are core to any safety analysis required for safety related elements. The role of the safety analysis is explained as well as the procedure for conducting this analysis. The different types of safety analyses are discussed and the methods explained before this is illustrated with a small and simple example.
Training Sprint 4: Supporting Processes
Reusing Components (ISO 26262−2, Clauses 6.4.4, 6.4.6.7)
Avoiding to reinvent the wheel is one of the key approaches to efficiency. The ISO 26262 does not stand in our way, yet, the key concepts for re-using elements in accordance with ISO 26262 must be understood. This module explains the basic reuse flow, the different categories of component sources, as well as the interesting topic of trusting release collaterals.
Reusing Systems (ISO 26262:2018−2, Clauses 6.4.3 and 6.4.4; ISO 26262:2018−8, Clauses 14 through 16)
This module focuses on eth system level reuse, discussing internal reuse and reuse management, followed by considering off-the-shelf reuse that may come with safety evidence from other safety standards.
Reviews (−)
A detailed explanation for one of the three main pillars of verification: the review. It starts with explaining the conduct of a review, then relating the review to the change management. Subsequently, this module covers different review methods that you may come across, deep diving into the review method ""inspection"".
POSD in a Nutshell (ISO 26262:2018−7)
A short introduction to the Production, Operation, Service, and Decommissioning Phase. In this module the product safety lifecycle is matched to the three areas of safety management, and the interactions between the different activities explained.
Training Sprint 5: Examination
Time to prepare for the exam with practice questions and Q&A with the instructor.
3. Target group
Systems Developers, as well as Project Managers, Safety Managers, Line Managers, Process Owners, Product Owners, and Scrum Masters for Systems related projects.
4. Added value after training
The Systems developer knows his responsibilities and can counteract the technical risks of the development object with a systematic approach and appropriate safety concepts.
The manager knows the challenges the Systems developer faces and can provide the best possible support.
Waste no more time. Learning creates competence.
The training process
1. Online registration/inquiries
You sign up for a training session online and choose from the various payment options. After completing the registration, you will receive an invoice by email.
If you have any inquiries, you will receive an offer that you or your employer simply order.
2nd payment
We accept the following payment options: PayPal, credit card, invoice.
3. Online login details
The trainer emails the online invitations with the login details to the participants at least one week before the start.
4th training
With practical examples and lots of interaction, we work together to develop the content and understanding and deepen the application. In this way, you will be fit for the exam and master the implementation in everyday working life.
6. Certificates
After the training, the trainer emails the certificate of participation.
7th follow-up
4-6 weeks later, participants and trainers meet again online and report and discuss the implementation successes.
The exam process
In our functional safety training courses, the test is carried out directly by the training provider, but supervised by Saphire Certification eG. Your certificate is issued accordingly by Saphire Certification eG. You will be registered for the exam even before the training. The exam is conducted as an online exam; you need a stable Internet connection and a webcam with microphone to take part. Please ensure that you have the technical infrastructure for the exam well in advance of the examination date.
Exam structure
The theory test comprises 30 multiple choice questions, in which each of the four selectable answers is either true or false regardless of the other answers. The correct answers must be marked as correct or incorrect by the participants accordingly. The exam time is 120 minutes. The theoretical examination is to be taken as an individual examination and is conducted in English.
Passing the exam
One point is awarded for each answer correctly marked as correct or correct as incorrect. The theoretical test is considered passed if at least 90 points are achieved.
Allowed materials
Only printed course materials (from any course provider), published works, dictionaries and personal notes are allowed for the theoretical examination. We would like to point out that the use of sample exams and practice questions is expressly prohibited and will result in immediate disqualification.
Technical requirements
Participants must have the usual technical devices and an Internet connection. The standard technical equipment includes a PC with audio playback and recording functions and a webcam. The required software comprises an office suite and a current version of a widely used Internet browser program. The documents created as part of the practical exercises must be uploaded or sent by e-mail to the respective examiner.
Legal
Payment deadline
Invoices must be paid within 14 days. For seminars, the money must be received 10 days before the start. Different agreements can be made.
Rebooking
Before the start of the seminar, participants can name a replacement person for the entire training in writing by email. This rebooking is free of charge.
Participants can inquire in writing by email whether they can rebook to a specifically named other training (or just another date). For inquiries 10 days from the start of the seminar, we can often rebook.
Schedule changes by Knüvener Mackert
If training cannot be carried out as planned, Knüvener Mackert can set a later training date. We will communicate any changes as soon as possible. We are unable to reimburse associated costs.
Cancellations
The following cancellation costs apply:
- Up to 30 days before the start of the seminar: 0% (full refund of the invoice amount)
- Up to 14 days before the start of the seminar: 50%
- Otherwise: 100% (no refund)
Effective learning
We pay attention to lots of interaction, mutual exchange and meaningful discussion, as in our experience, learning is particularly good. We explain the theory in a simple and structured way and support understanding with many practical examples and exercises. We keep attendance limited to maximize learning and encourage participation.
Don't waste time. Learning creates competence.