Functional Safety Concepts (FSC) - ISO 26262 | Engineering Expertise EE #06

  Рет қаралды 8,967

UL Solutions – Software Intensive Systems

UL Solutions – Software Intensive Systems

Күн бұрын

After hazard analysis and risk assessment, the Functional Safety Concept (FSC) is the next logical step in controlling faults in automotive electronic systems.
In this video, we will explain:
What the Functional Safety Concept is
What it must specify
The creation process of the Functional Safety Concept
For more detailed information you can download the white paper here for free: www.kuglermaag...
🎓 If you want to learn more and become an expert in Functional Safety, check out our trainings: www.kuglermaag...
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 if you don't want to miss any videos.
Do you need further information? Contact us or leave a comment below!
#Automotive #functionalsafety #iso26262

Пікірлер: 5
@murli777
@murli777 Жыл бұрын
Normally system and sub system level functional requirements will be "what" the system should do not "how" or "implementation. When it comes to Functional Safety, is FSR and TSR written in "what" vehicle or System should do when failure occurs or is it "how"
@ULSolutionsSIS
@ULSolutionsSIS Жыл бұрын
In general requirements are more “what” must be done or implemented, not so much “how” to do or implement it. But of cause is a TSR already the “how” to implement a FSR. That kind of relationship applies to any hierarchical levels of requirements. We hope this helps you further!
@makzmakz
@makzmakz Жыл бұрын
As a supplier I have noticed that the fsc is never given by the OEM. Usually just vague "safety requirements" without any supporting info or rational. When I request item definitions and fsc's you usually get vague answers like "its protected by ip". For the safety of the complete system I think its critical that work products from the concept phase is given as input to the development at the system level phase. Comments?
@ULSolutionsSIS
@ULSolutionsSIS Жыл бұрын
Yes, it is normal that the OEM does not provide the FSC. It is his responsibility. And yes, the OEM must then provide (good!) functional safety requirements with ASILs allocated. The supplier does not need to know the full FSC and should however know for which item(s) his development is. And that is normally the case. We hope this helps you further!
@makzmakz
@makzmakz Жыл бұрын
@@ULSolutionsSIS Thanks for the answer. As part of the safety culture I usually insist on understanding the FSC, especially when FSR's are badly written or incomplete. Just saying "it's the OEM's responsibility" is not ok if you suspect incompleteness or incorrectness in upstream work products.
Automotive SPICE Assessments - Part 3: What is an ASPICE Assessment? | Engineering Expertise E/E #07
9:42
UL Solutions – Software Intensive Systems
Рет қаралды 2 М.
Hazard Analysis and Risk Assessment (HARA) | Engineering Expertise EE#4
24:31
UL Solutions – Software Intensive Systems
Рет қаралды 12 М.
Крутой фокус + секрет! #shorts
00:10
Роман Magic
Рет қаралды 29 МЛН
ISO 26262 - Functional Safety at the System level
13:20
UL Solutions – Software Intensive Systems
Рет қаралды 32 М.
Demystifying Functional Safety: SIS, SIL, and MooN Explained
8:26
ISO 26262 - Software Level of Functional Safety
19:33
UL Solutions – Software Intensive Systems
Рет қаралды 50 М.
ISO 26262 - Safety Analysis (2021)
20:52
Matrickz TV
Рет қаралды 15 М.
ISO 26262 - Concept Phase of Functional Safety
10:54
UL Solutions – Software Intensive Systems
Рет қаралды 28 М.
FMEDA Random HW Fault Classification
10:01
Functional Safety First
Рет қаралды 2,3 М.
Functional Safety with ISO 26262 - Principles and Practice
1:03:59
Vector Consulting Services
Рет қаралды 75 М.
ISO 26262 - Management of Functional Safety
13:43
UL Solutions – Software Intensive Systems
Рет қаралды 29 М.
ISO 26262 - Functional Safety at a Glance
13:17
UL Solutions – Software Intensive Systems
Рет қаралды 141 М.