Joyson – JLR, VW, SKODA, SEAT, Porsche, Audi – HOD (5/2020 – 7/2022):
- Perform functional safety activities for Management, System, Software, Hardware levels such as (Safety plan/case, DFD, TSC, FTA, FMEA, DFA, FFI, etc.)
- Support teams to comply with ISO26262.
- Participate in the functional safety assessments.
Overview of the feature can be found here: https://www.facebook.com/watch/?v=274991630396076
Detailed Job description:
- Management level activities - Part 2
- Contribute in Safety Plan/Case updates.
- Safety plan/case were created by the functional safety manager and I contributed by updating them and review the updates with the functional safety manager.
- Create/contribute in Confirmation Measure reports.
- I created some confirmation measures as per the ISO26262; Ex: safety plan/case
- Create/contribute in the Impact Analysis
- I created the impact analysis document from scratch with development teams support.
- Participate in the functional safety assessments
- I was the responsible one for the communication between TUV (assessor) and our developmentteams.
- Concept phase activities - Part 3
- Specify/review Functional Safety Requirements (FSRs) from customer requirements
- We receive the whole concept phase from the customer and I just reviewed the FSRs.
- System-level activities - Part 4
- Create/contribute in Functional System Architecture diagram
- Create/contribute in Technical Safety Concept (TSC)
- Adding Technical Safety Requirements (TSRs) and review them with responsible teams in DOORS.
- Add information/diagrams related to the project.
- Ensure TSRs Traceability.
- Specify the safe states (which agreed with the customer).
- Ensure system safety requirements traceability and consistency in DOORS.
- Create/contribute in the system safety analysis (FTA, FMEA, DFA)
- I created FTA (using drawing tool), FMEA (using IQ-APIS, Plato), DFA (using excel sheet) from scratch and reviewed them with the functional safety manager.
- Create a system safety analysis report
- Identify new safety mechanisms and integrate them into the system
- Support system team to comply with ISO26262
- Software-level activities - Part 6
- Create/contribute in the software safety requirements.
- Ensure software safety requirements traceability and consistency in DOORS.
- Create/contribute in the software safety analysis (FMEA, FFI)
- I created FMEA on high level SW architecture, and perfromed FFI/GWA on SAD level.
- Identify new safety mechanisms on the SAD level and integrate them into the software
- Create a software safety analysis report
- Support software team to comply with ISO26262
- Hardware-level activities - Part 5
- Create/contribute in the hardware safety requirements
- Ensure hardware safety requirements traceability and consistency
- Create/contribute in the hardware safety analysis (FMEA, FMEDA)
- I created high level FMEA.
- Ididn't create FMEDA, but I reviewed it to make sure it complaint with the ISO requirements.
- Identify new safety mechanisms and integrate them into the hardware requirements
- Support hardware team to comply with ISO26262
- Supporting activities
- Create/contribute in the verification plan and reports
- I created verification plan for the reviews only (not the testing/validation plan)
- Create/contribute in the DIA specification
- I reviewed the DIA and added my comments to the Functional safety manager
- Create safety requirements for assumptions of use of SEooC
- I added TSRs for the AOUs (the SEooC here was SBC [system basis chip]).
- Create/contribute in software tools evaluation and qualification report
- I didn't create from scratch, I just updated it with adding some usecase and remove some.
- Create/contribute in software component documentation report
- With the support from the SW architect I created this report and reviewed it with him.
- Review Test reports to analyze and assess the software defects
- If I find a safety defect I analyzed it more with the testing team and if it's something critical without a solution then I add it to the safety case.