Implementation of ISO Adoption, Challenges, Efficient Application. Mike Staszel, Bonifaz Maag KUGLER MAAG CIE NA, Inc. May 13 th, 2014.

Transcription

1 Implementation of ISO Adoption, Challenges, Efficient Application Mike Staszel, Bonifaz Maag KUGLER MAAG CIE NA, Inc. May 13 th, 2014 KUGLER MAAG CIE North America, Inc. Page 1

2 Content Kugler Maag Cie ISO At a Glance Obstacles and Challenges as we perceive them Technical and Organizational Competencies required Impact of Development Tools Status Worldwide and Upcoming Changes Summary Page 2

3 Kugler Maag Cie International and independent consulting company in the area of sustainable performance improvement Analysis, assessment, improvement, and operative implementation of Processes Integration of open methods & standards, such as Automotive SPICE, CMMI, Functional Safety, Lean, Agile Management of engineering risks with the development while maintaining the speed of innovation some of our automotive customers Seite 3

4 ISO covers the whole Product Lifecycle. Emphasis is on the Development Phase Page 4

5 ISO Essentially nine parts build the Standard Page 5

6 Obstacles and Challenges as we perceive them (1/4) Process Maturity is important but not sufficient Page 6

7 Obstacles and Challenges as we perceive them (2/4) Maturity Models (e.g. CMMI) Focus: Software and System development Approach to harmonize rating criteria, assessment method and to achieve comparability Objective: efficient, repeatable development of products Target depends on business goals Do not require certain methods ( what ) Result: Certificate for process maturity Functional Safety Standards Focus: Development of safety-related systems (incl. HW) Context dependent assessment method and criteria are dominating Objective: Capability to develop a product with calculable risk Target depends on hazard analysis Require methods ( how ) & characteristics (e.g. SFF) Result: Expertise for a product Page 7

8 Obstacles and Challenges as we perceive them (3/4) Functional Safety impacts many Pieces Process improvement Safety Concepts & Analyses Hardware Components Software Architecture Test methods Qualification Safety Case Field Monitoring Last but not least: Subcontracted elements are in scope, too Page 8

9 Obstacles and Challenges as we perceive them (4/4) Functional safety asks for some more documents, e.g.... Page 9

10 Additional Effort induced by ISO The additional effort required for development according ISO varies significantly. Among the impacting factors are Number of functional safety goals or functional safety requirements Required maximum ASIL per safety goal Product architecture Existing engineering approach Source: Hansen Report October 2011, pg.1 Page 10

11 Key Competencies required Organizational Safety Culture Efficient and safe platform development Functional Safety Merge sequential and iterative approaches Apply ISO during the product lifecycle Work with less mature customers or supplier Page 11

12 Key Competencies required Technical Even if ISO standard is prescriptive, there are still areas when mutual agreement needs to be established which defines sufficiently safe Calculation of hardware metrics Separate safety relevant parts from non-safety related parts Partition the architecture Provide a process that allows tailoring of process Very good configuration management -> Safety Case Integrate testing of functional safety and other requirements Not all functional safety related tests need to be performed for all releases Clear understanding, what tests are related to functional and which aren t Page 12

13 Competencies - Technical and Organizational per Company Type All Manage safety case Process skills Tier 1 Monitor safety activities of Tier 2 supplier Semiconductor Understand how their customer implement functional safety mechanisms OEMs Break down the system, manage the functional safety interdependencies Tool Vendors Provide qualification kits to their customer Page 13

14 Impact of Development Tools In the end... Safety case and Functional safety assessment build on evidences (documents, design, reports,...) Well structured evidences make life easier and arguments clearer Therefore Tools are of great help to organize and provide the various kinds of evidences Achieving functional safety without tools / structured processes is possible but inefficient Are tools safe? Step 1: Determine which tools are critical and which aren t -> Classification Step 2 (based on step 1): Are relevant tools sufficiently safe -> Qualification Page 14

15 Model Based Design and Functional Safety Lacking requirements are found early Tool supported model checking possible Code generation avoids faults (-> tool qualification!) Comparison of model and ECU behavior possible (Back-to-back test) Generation of test stimuli saves time and increases test quality Page 15

16 Status Worldwide and Upcoming Changes ISO is adopted worldwide in all major markets OEMs that want to sell in Europe or North America ask for it China works on a tailored version A new version won t be available, soon Joint efforts (e.g. SAE) are ongoing to harmonize interpretation (e.g. work on common classification of hazards and risks) Definitions of safe state (e.g. loss of steering assist) change Page 16

17 Summary Functional Safety adds burden to organizations However, if you are used to develop safe products in the past, there should be nothing essentially different Robust processes help to keep required artifacts well under control Tools help to do the work efficiently But overall functional safety is a matter of culture without the organizational focus on functional safety, it can t be sustained Page 17

18 Further discussions and queries... KUGLER MAAG North America Columbia Center 101 w. Big Beaver Suite 1400 Troy, MI USA contact me Bonifaz Maag Mobile Page 18

19 Thank you for your kind Attention. KUGLER MAAG CIE GmbH Page 19