Your help is needed to apply ISO 26262 to a new project.

M

marianir

#11
Hi Pinenboa,

to write a safety plan is somehow complex and it is one of the key point of all the process. One of the key topics in my experience is the planning of V&V activities, a really crucial part to give evidences of the goodness and completeness of the whole safety case.

Unfortunately, I cannot send you any template for free. But I can answer here to more detailed questions, if you have some particular issue to be solved.

And, in case you may need, my company is able to give support in those kind of activities, esp. on HW side.

Best regards
Riccardo
 
Elsmar Forum Sponsor
M

Murphys Law

#12
Isabulg - I work for one of your competitors so can only give you generalities.

Firstly you will not be able to apply ISO26262 directly as it is a functional safety standard at the SYSTEM level. In otherwords, your customer will own system level safety. Application usage and severity/probability of occurance / controlability of vehicle will determine it's ASIL rating. ASIL-D would be brakes. ASIL-A could be headlight control. That however, will vary by end car customer itself and you must get feedback from your customers

You will only be able to apply to ICs, chapters 2 (Safety mgt), 5 (Hardware) and 7 (Production). Unless you have custom chip, it is unlikely you'll have visibility to full system fan down. As such, you'll have to do initiate something called SEooC : Safety Element out of Context. Basically, your application engineering, product marketing, design team and chip architect will have to brainstorm how your chip will be used in a safety application and work to potential hazards from there. (ie/ you attempt some reference designs). You safety plan will start here.

Secondly, ISO26262 should not be responsibility of the quality dept. ISO262626 also has nothing to do with TS16969 or ISO9001. It is NOT a quality system per se but really a business model for functional system safety. IMO, It belongs in your new product development process as an addendum to what you do already. Owners maybe project management or a parallel safety function with you Product development process team.

Finally, Chapter 10 will be working on an example of how you apply it to ICs.

On the subject of standard maturity. Chapters 1-9 are not longer taking comments so is pretty much locked. Chapter 10 is still open but final working stages. Intent is release EO 2010 and apply to MY 2011. I don't believe the later due to the long design cycles.
 
V

vanputten

#13
My organization designs and manufactures analog integrated circuits (semiconductors.) All of our designs are proprietary. We do not offer anything designed by customers or others. We design an IC and then put it in our catalog. The auto customers choose the product they want from our catalog.

Once the customer chooses the product, at that time they may want some evidence of complying with ISO 26262.

We are just beginning to get pressure from auto customers for ISO 26262 documentation.

Along with the SEooC, I thought the Development Interface Agreement is a key piece of the puzzle for organizations only providing hardware for the customer's safety system.

In a white paper for my employer, I wrote:

"A supplying organization should learn of about the customer’s Safety Goals, Functional Safety Requirements, Technical Safety Requirements and System Design Specification via a Development Interface Agreement (DIA.) See definition of DIA in 1.24 of Part 1. Section 5 of Part 8 describes responsibilities within a development project distributed between the customer and supplier(s). This is the essence of a DIA. Annex B, Table B.3, page 45 of Part 8 describes a “Customer – Supplier data exchange in hardware development cycle.” This table gives some of the better information, within the standard, as to what a supplying organization may be required to do when providing a hardware part as a piece of a safety system."

I hope this thread continues since ISO 26262 is incredibly confusing and not well written.
 
V

vanputten

#14
Dear Murphy's Law:

You stated "Finally, Chapter 10 will be working on an example of how you apply it to ICs."

Are you saying that you have knowledge that the Technical Committee writing ISO 26262 will be providing an example in Chapter 10 as to how the standard applies to IC"s?

If so, how did you get that knowledge? That is some terrific info.

Thank you,

Dirk
 
M

marianir

#15
Hi

I'm the guy in charge in the ISO 26262 group to prepare this IC guideline..... if you have specific questions, do not hesitate to contact me directly.

Riccardo
 
M

marianir

#17
Ah OK, no problem - just take into account that micro guideline in Part 10 is currently a draft of the HW subgroup to be discussed in the coming ISO international meeting in US - so still subject to changes.
But I'll glad to answer to questions in that forum. Riccardo
 
V

vanputten

#18
Hello Marianir:

Do you agree with the following posting? My organization designs its own analog semiconductors.

"You will only be able to apply to ICs, chapters 2 (Safety mgt), 5 (Hardware) and 7 (Production). Unless you have custom chip, it is unlikely you'll have visibility to full system fan down. As such, you'll have to do initiate something called SEooC : Safety Element out of Context. Basically, your application engineering, product marketing, design team and chip architect will have to brainstorm how your chip will be used in a safety application and work to potential hazards from there. (ie/ you attempt some reference designs)."

We are having a difficult time determining what our product is in terms of the ISO 26262 definitions. We design our own semiconductors and then list them in a catalog. The auto customer chooses which device to buy from the catalog. Does that make our device a Commercial of the Shelf (COTS) product? Or is our product an SEooC? Both?

Section 7.4.4.4, Note 1 on Page 13 of Part 4 states, “Architectural constraint described in Part 5, clause 8 are not directly applicable to Commercial of the Shelf (COTS) parts and components because suppliers usually can not foresee the usage of their product in the end-item and the potential safety implications. In such a case, basic data such as failure rate, failure modes, failure rate distribution per failure mode, built-in diagnosis, etc. are to be provided by the part supplier in order to allow estimation of architectural constraints at overall hardware architectural level.”

Is our product a Hardware Part? An Element? A Component?

1.55 hardware part – hardware element whose function cannot be further sub-divided. Example resistor, integrated circuit, microcontroller, capacitor, bus, cable, connector.

Thank you,

Dirk
 
M

marianir

#19
Hi sorry I was in a conference for all the week, I will drop a reply on monday. Anyway we are trying to improve the SEooC definition as well. Riccardo
 
M

marianir

#20
Hi Dirk sorry I was very busy in the last weeks due to travels.

As I told you, in the ISO26262 WG we are preparing a guideline for microcontrollers.

Some quick feedbacks to your questions (sorry no much time today):

"You will only be able to apply to ICs, chapters 2 (Safety mgt), 5 (Hardware) and 7 (Production). Unless you have custom chip, it is unlikely you'll have visibility to full system fan down. As such, you'll have to do initiate something called SEooC : Safety Element out of Context. Basically, your application engineering, product marketing, design team and chip architect will have to brainstorm how your chip will be used in a safety application and work to potential hazards from there. (ie/ you attempt some reference designs)."
Also parts 8 and 9 are applicable to an IC (e.g. dependent failures analysis). About SEooC, yes, the IC and micros are the best candidates to be SEooC. The following text is what we are going to include in the guideline:

"Microcontroller is developed in accordance with the safety requirements, which are derived from the top-level safety goals of the item. Targets for HW architectural metrics and Probabilistic Metric for random Hardware Failures are allocated to the item: in this case the microcontroller is just one of the elements. According the example of ISO°26262-5 clause 8.2, to facilitate distributed developments, target values can be assigned to the microcontroller itself. The safety analysis of a microcontroller is performed according to the requirements and recommendations defined in ISO°26262-5 clause 7.4.3 and in ISO°26262-9 clause 8. In the case that the target item does not yet exist, the microcontroller can be developed as a Safety Element out of Context (SEooC) according to ISO°26262-10 clause 10. In this case, the development is done based on assumptions of condition of the microcontroller usage (Condition of Use), and then the assumptions are verified with the requirements derived from safety goals of the item at system-level verification phase."
We are having a difficult time determining what our product is in terms of the ISO 26262 definitions. We design our own semiconductors and then list them in a catalog. The auto customer chooses which device to buy from the catalog. Does that make our device a Commercial of the Shelf (COTS) product? Or is our product an SEooC? Both?
Good question. There is still a discussion on-going about differences between qualification of components (like COTS) as described in part 8 and SEooC as described in part 10. The idea is that part 8 applies for products not initially thought for functional safety while a product focusing functional safety would be a SEooC. Other differences exist but sorry today I don't have time to write more... next time.

Is our product a Hardware Part? An Element? A Component?
1.55 hardware part – hardware element whose function cannot be further sub-divided. Example resistor, integrated circuit, microcontroller, capacitor, bus, cable, connector.
We did some modification to part 1 and part 10 definitions as follows:
- the example below 1.55 has been removed because microcontroller isn't an element that cannot be further sub-divide
- we added the following example in part 10:

EXAMPLE In case of a microcontroller or ASIC, the following partitioning can be used; the whole microcontroller is a component, the processing unit (e.g. a CPU) is a part, the registers inside the processing unit (e.g. the CPU register bank) is a sub-part or unit.

Sorry no more time today for the reply.

Riccardo

PS: I will do a speech in Euroforum conference in Stuttgart on 28 september with the following agenda:

Safety Elements out of context (SEooC) in ISO 26262: benefits and risks
* Developing and using HW and SW SEooC in ISO 26262
* Benefits and risks behind the SEooC approach
* A practical example: the microcontroller seen as a SEooC

[FONT=&quot] [/FONT]
 
Thread starter Similar threads Forum Replies Date
D Help needed for Compliance Road-Map - Startup making their first device (IVD) IEC 62304 - Medical Device Software Life Cycle Processes 1
V Root Cause help needed - Sheet metal breaking at press Problem Solving, Root Cause Fault and Failure Analysis 9
W TL9000 transition from 5.5 to 6.0 - help needed TL 9000 Telecommunications Standard and QuEST 1
K Processing Time Tracking Software Program Help Needed Lean in Manufacturing and Service Industries 3
N VDA 1 Critical Characteristics Requirements Help needed VDA Standards - Germany's Automotive Standards 6
G Help needed on 2 TS 16949 Elements - 7.5.5 & 7.5.3 IATF 16949 - Automotive Quality Systems Standard 2
R Excel 2003 and Capability Studies for Dummies - Help needed! Excel .xls Spreadsheet Templates and Tools 4
R ISO 13485 Software Validation Requirements - Help needed ISO 13485:2016 - Medical Device Quality Management Systems 4
D Generating a detailed Process Plan - Help needed Process Audits and Layered Process Audits 6
R ISO 9001 Implementation in the Bus/Coach Industry - Confused and Help needed ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6
O ISO 9000 section 7.2.1(c) Compliance help needed ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
E Help needed on the TS 16949 External Auditor Exam IATF 16949 - Automotive Quality Systems Standard 8
Q Regression Analysis for the Attached Data - help needed - TIA Reliability Analysis - Predictions, Testing and Standards 13
S Interpreting Level of Confidence - Round Robin for Tensile Testing - Help needed Statistical Analysis Tools, Techniques and SPC 4
J ISO 9001 and Improvement of Business Performance - Research help Needed ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 11
S Dew Point Meter: DPL4000 - help needed Manufacturing and Related Processes 1
W Australian Approval for Class I Medical Device - Help needed. Other Medical Device Regulations World-Wide 1
R Student Question - Help needed with statistics questions Statistical Analysis Tools, Techniques and SPC 6
L Definition Throughput Yield (TPY) or First Pass Yield Calculation - Help Needed Definitions, Acronyms, Abbreviations and Interpretations Listed Alphabetically 3
P Sample Size Calculation help needed Reliability Analysis - Predictions, Testing and Standards 4
6 Preventive Action - Help Needed. Input for Training and Sustenance Preventive Action and Continuous Improvement 3
R ISO 13485 Surveillance Audit Nonconformances and Report Help Needed ISO 13485:2016 - Medical Device Quality Management Systems 9
V Help needed with ISO 14001 Procedures please ISO 14001:2015 Specific Discussions 7
A Help needed for Fighting a specifically identified Organism found during Dose Audit Miscellaneous Environmental Standards and EMS Related Discussions 2
D AASHTO R18 Accreditation (quite similar to ISO 17025) QMS - Help needed ISO 17025 related Discussions 4
L Gage Linearity and Bias Study Analysis - Minitab help needed Using Minitab Software 4
H Husky 1750PSI Pressure Washer - Help needed! Manufacturing and Related Processes 3
L Medical Device FDA Product Classification help needed 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
S Cross Tabulation in Attribute MSA - Help Needed Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 2
S Trend Review and Process Improvement help needed Capability, Accuracy and Stability - Processes, Machines, etc. 6
L Easy Access of Obsolete Documents - Corrective Action help needed ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 13
T FDA Single Use Instruments - Classification Help Needed 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
T PFMEA of Die casting Process--Help needed? FMEA and Control Plans 5
P Design FMEA (DFMEA) Basics - Help needed IATF 16949 - Automotive Quality Systems Standard 3
K ISO 13485 Audit help needed General Auditing Discussions 20
U Issue with Labelling of Outer Container - help needed for clarification EU Medical Device Regulations 3
B 5 Why help needed Please kindly review Problem Solving, Root Cause Fault and Failure Analysis 15
S Excel Spreadsheet Conditional Formatting help needed Excel .xls Spreadsheet Templates and Tools 12
G Help needed to complete a Financial Audit of a Nonprofit Organization Various Other Specifications, Standards, and related Requirements 7
K Low Volume Products Data Analysis help needed Statistical Analysis Tools, Techniques and SPC 6
somashekar Water and Air Pollution Load Calculations help needed Miscellaneous Environmental Standards and EMS Related Discussions 6
S Master Document Register Project Procedures help needed Document Control Systems, Procedures, Forms and Templates 2
Ajit Basrur Tabulating Improvement Plan Status - Help and suggestions needed Excel .xls Spreadsheet Templates and Tools 9
R Sample Audit Report of an Investment Company - Audit help needed Document Control Systems, Procedures, Forms and Templates 1
E FDA New Product Introduction Regulations help needed 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
R Process VSM (Value Stream Mapping) help needed Lean in Manufacturing and Service Industries 5
K Virtual DMIS vs. PC-DMIS - Help needed Calibration and Metrology Software and Hardware 3
T Excel Time Calculations and Formulas help needed Excel .xls Spreadsheet Templates and Tools 15
C TS 29001/API spec Q1- help needed Oil and Gas Industry Standards and Regulations 1
P HiPot Calibration help needed General Measurement Device and Calibration Topics 10

Similar threads

Top Bottom