1 / 23

S P I R I T

PROCESS IMPROVEMENT. S. S. P. I. R. I. T. S P I R I T. @ RESTRAINT SYSTEMS. SPIRIT Base Training - Overview. Motivation / History. VW Assessment in June/2002 with the result: SPICE level 0 on some of the process areas (SPICE is from 0 … 5)

daisy
Download Presentation

S P I R I T

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PROCESS IMPROVEMENT S S P I R I T S P I R I T @ RESTRAINT SYSTEMS

  2. SPIRIT Base Training - Overview

  3. Motivation / History • VW Assessment in June/2002 with the result: • SPICE level 0 on some of the process areas (SPICE is from 0 … 5) • Supplier level C ( not accepted for further business) • Conclusion: • Short-term all processes which were assessed on SPICE Level 1 • Midterm all processes which were assessed on CMMI Level 2 • Long-term all processes which were assessed on CMMI Level 3 Improvement program SPIRIT was stablished

  4. Roadmap on SV C RS Process Improvement 2002 2005 2003 2004 Spirit 1 Spice 1 Spirit 2 CMMI Level 2 Spirit 3 CMMI Level 3 1 2 3 Spirit 1 Rollout Spirit 2 Rollout Spirit 3 Rollout 4 5 5 Level 3 Level 2 Important SPICE processes realised CMMI Level 3 processes defined 2 4 1 “SPIRIT” Kick off Siemens Process Assessment 5 CMMI Level 2 processes defined 3

  5. ProcessInfluencesandSources Car Manuf. Spirit 1+2 Internal Procedures Legal Standards SV C RS Process Improvement Domains: HW, SW, Algo, Mech, Q, M C M M I FINAL GOAL: CMMI LEVEL 3 TUM REQM SWI@SV CT SE 3 Support System- & Function Dev. SV Initiatives (PM, QA,..)

  6. Transition from Phase I to Phase II Focus of SPIRIT II Requirements Engineering DocumentationManagement Test Process Project Management SW Quality Assurance Problem Resolution Requirements Eng. Architecture Rbg: L. Pfau TSR: M. Weickhmann Web: K. Tretter Tro: D. Talbot Rbg: D. Brasin TSR: D. Macra Web: W. Rochowiak Tro: Scott Morell Rbg: Th. Langner TSR: C. Mihaly Web: R. Novotni Tro: Scott Morell Quality Assurance Configuration Management Supplier Management Rbg: R. Hamperl TSR: Z. Pall Web: M. Seitz Tro: K. Koshorek Rbg: M. Kiening Rbg: P. Gruen TSR: L. Margineanu Web: R. Novotni Tro: A. Ali SPIRIT I SPIRIT II

  7. Levels of Development System consisting of eg. SRS + SAT + Rollover + … Single Products, such as 1 SRS unit, 2 Satellites, LIDAR, BSD … Software, Hardware, Algorithm, Mechanic HW component, SW code, … What does SV RS deliver to the customer? What does SV RS develop? Depending on the customer, SV C RS delivers systems consisting out of SRS and peripheral units or single products, completing the restraint system of the vehicle. The products consist of Software, Hardware, Algorithm and Mechanic. Hardware + Mechanic consists out of components, Software + Algo out of .c/.h files.

  8. Levels of Development System Product Discipline Component Siemens Restraint System has identified 4 Levels of Development. These development levels are very important for process improvement: How are requirements handled from top to down and bottom to top. Tests for each level must be defined in scope and delimited to upper and lower levels. Project Management and Quality Assurance has to be defined for relevant levels. Support processes (eg. configuration management) must be installed.

  9. Example I want to have a restraint system, with front airbags, side airbags, rollover curtains. Also low- g crashes shall be detected. Eric Customer SYSTEM Integration Functionality Main ECU Satellite Rollover Unit Early Crash Sensor HW SW ... HW SW Algo HW SW .... HW SW Algo Mech

  10. Project Management M0 M1 M2 M3 M4 M5 Sample Verification / Design Validation Opportunity Selection Acquisition/ Quotation Concept Introduction to Production and Validation Production Ramp up M3c M3a.x M3b.x Sublevel Phase 3a Sublevel Phase 3b Sublevel Phase 3c Sublevel Phase 3end The Project Management Process: lists all project management relevant activities shows them sorted in the milestone plan with adaptations for easier use in the development levels Key Points: • Clear structure of roles for project team members and clear responsibilities • Effort estimation and scheduling procedure embedded • One project-wide Risk Mgmt Level 1 (System) PM Level 2 (Product) Level 3 (Discipl.)

  11. Requirements Engineering Requirement Engineering defines: how requirements are derived (Method) Customer Customer the way of requirements during development Level 0 (Vehicle) Level 0 (Vehicle) the tracing of requirements (tool support) Level 1 (System) Level 1 (System) trace Level 2 (Product) Level 2 (Product) trace Level 3 (Discipl.) Level 3 (Discipl.) trace Development Process Test Process Level 4 (Comp.) Level 4 (Comp.) trace V-Cycle

  12. Test Process The Test Process defines: timing and content of test plan, test spec, test report Customer for all development levels. Level 0 (Vehicle) Level 1 (System) Level 2 (Product) Test Plan Test Spec Test Report Level 3 (Discipl.) Test Process Level 4 (Comp.)

  13. Quality Assurance M0 M1 M2 M3 M4 M5 Sample Verification / Design Validation Opportunity Selection Acquisition/ Quotation Concept Introduction to Production and Validation Production Ramp up M3c M3a.x M3b.x Sublevel Phase 3a Sublevel Phase 3b Sublevel Phase 3c Sublevel Phase 3end The Design Quality Assurance Process: lists all development relevant quality activities shows them sorted in the milestone plan with adaptations for easier use in the development levels Key Points: • Similar Q process for all development levels, separated in independent roles • Responsibilities: Planning and Tracking for QA activities (eg. reviews), checking for process compliancy Level 1 (System) QA Level 2 (Product) Level 3 (Discipl.)

  14. Configuration Management Configuration Management: administers work products (documents) of the development. CM for example maintains the codes of SW development. CM consists basically out of 3 sub- topics: Document Management … shows where documents are stored Change Management … shows how changes are handled Release Procedure … shows documents that needs to be released Configuration Management is also a typical support process. Key Points: • Transparent structure for documents and work results • One common Change and Error Management • Tasks are supported by PVCS tools

  15. SPIRIT III Activities 02 Training"Develop organisational management of competences and training" 03 Metrics and Repository"Align process measurement and analysis activities" 01 Process Definition and Maintenance:"Set up organisational administration of our processes" 04 Function Development"Development of reusable objects" 05 Internal Process Reviews"Measure process conformance of projects at RS using SPICE " 06 Completion of M and Q Workflow"Complete process definition of manufacturing and quality" 07 Doors Introduction"Provide tool to support requirement engineering" 08 Functional Safety (IEC 61508)"Analyze gaps between SPIRIT processes and IEC61508" 09 SPIRIT 2 Process Maintenance"Continue roll out of SPIRIT II processes" Legend :OrganisationalProject LevelInternal Issue

  16. How to get to the RS Process Web Siemens VDO Home RS Page Process Web

  17. Web based repository of processes Siemens Reference Process House SV C RS Process Variants

  18. Phase Oriented Phase-view Diagram: Shows all tasks between two milestones (=yellow rhomb). Related tasks have the same colour (eg. one colour for all project management tasks).

  19. Workflow Oriented Workflow-view Diagram: Shows all related tasks over all milestones. Related tasks are similar as regards content. (eg. engineering tasks) continued

  20. Task Descripion Input what documents are necessary to start this task? Roles who is involved? who is responsible (in bold letters)? Workflow and Phase where/ when is this task relevant Output what document should be issued with this task? (link to templates) Auxiliaries how should it be done? (link to method descriptions) Goal what aims the task? Action/ Description what items are necessary to be performed?

  21. Process Support RS Page

  22. Customer Feedback • 02 / 04 Ford Q-Labs: Excellent feedback – All processes >= Spice Level 1 • 03 / 04 Siemens Interim Profile: CMMI Level 2.5 • 08 /04 Positive statements on our RE-Methode from DC • 12 / 04 VW assessment: Upgrade as A-Supplier All processes >= Spice Level 2

  23. Growing from "C" to "A": Assessment: Siemens AG (SIP) Assessment: DaimlerChrysler Assessment: Nissan Process Improvement SPIRIT Assessment: Siemens AG (SPA) Assessment: Ford VW assessment in June 2002 VW assessment in December 2004 A supplier: "able to deliver quality" C supplier: "not able to deliver quality"

More Related