SFFS310A April 2022 – May 2022 TPS3704 , TPS3704-Q1
Texas Instruments carried out this assessment with respect to relevant requirements from the ISO 26262:2011 standard.
| ISO 26262:2011 | Requirement | Status | Compliance Argument | Evidence |
|---|---|---|---|---|
| Part 1: Vocabulary | No requirements in this part | N/A | N/A | N/A |
| Part 2: Management of Functional Safety | a. Safety Culture | Pass | Texas Instruments maintains worldwide corporate policies related to; product and function safety; facility and materials safety, environment & health safety, risk and insurance management and customer satisfaction thru total qualify. These policies are implemented thru requirements and specification at the business units and factory level. Continuous improvement is integral to all processes. The semiconductor group has completed TUV certification of its processes for functional safety hardware and software development. | TI Functional Safety Hardware development flow |
| Part 2: Management of Functional Safety | b. Competence Management | Pass | Qualification and competence for the project safety manager is review during nomination of functional safety manager. Team members are assigned by their supervisors and supervisor ensure that the persons involved in the project execution have a sufficient level of skills, competencies and qualifications corresponding to their responsibilities. | Documented Nomination of Functional Safety Manager |
| Part 2: Management of Functional Safety | c. Quality Management | Pass | Texas Instruments sites first achieved the International Organization for Standardization´s (ISO) Quality Management System (ISO 9001) and Environmental Management System (ISO 14001) Certifications in 1996 and have maintained compliance to the ISO requirements since that time. TI is also TS 16949 certified; an international quality system standard specifically formulated for the global automotive industry. In addition, TI sites first achieved OHSAS 18001 certification in 2007, and has achieved Sony Green Partner certification | Ti.com/Quality |
| Part 2: Management of Functional Safety | d. Tailoring of the Safety Lifecycle | Pass | Functional safety process and deliverables are tailored by TI Functional Safety Hardware flow to be applied in addition to the requirements of the Automotive IC development process. The TI Functional Safety Hardware flow has been reviewed and certified by external assessors to satisfy the requirements For ISO-26262:2018 and IEC 61508:2010. | TI Functional Safety Hardware development flow |
| Part 2: Management of Functional Safety | e. Safety Management | Pass | Project manager and Safety manager were appointed to this project. Functional Safety Plan was generated and necessary audits and assessments were scheduled. | Documentation of Nomination of Safety Manager |
| Part 2: Management of Functional Safety | f. Functional Safety Plan | Pass | A functional safety plan was generated and followed throughout the project. | Functional Safety Plan |
| Part 2: Management of Functional Safety | g. Confirmation Measure | Pass | An independent confirmation measure of I3 performed the appropriate reviews and audits for this project. | Documented Selection of Functional Safety Assessor, End of Phase Audits |
| Part 2: Management of Functional Safety | h. Safety Management After Release to Production | Pass | A process is in place for handling safety management after release for production. | Periodic Audit Report of Sustaining Operations, TI Quality Processes |
| Part 3: Concept Phase | a. Item Definition | N/A | Requirements do not apply, however assumptions were made for the SEooC development. | N/A |
| Part 3: Concept Phase | b. Initiation of the Safety Lifecycle | Pass | Most requirements do not apply, however assumptions were made for the SEooC development. Additionally, a safety plan is generated for activities in the scope of the SEooC development. | System Functional Safety Assumptions and Component Safety Requirements, Functional Safety Plan |
| Part 3: Concept Phase | c. Hazard Analysis and Risk Assessment | N/A | Requirements do not apply, however assumptions were made for the SEooC development. | N/A |
| Part 3: Concept Phase | d. Functional Safety Concept | Pass | Most requirements do not apply, however assumptions were made for the SEooC development. | System Functional Safety Assumptions and and Component Safety Requirements |
| Part 4: Product Development at a System Level | not applicable for a hardware component SEooC development | N/A | N/A | N/A |
| Part 5: Product Development at a Hardware Level | a. Initiation of Product Development at the Hardware Level | Pass | In this hardware component SEooC development, the focus of the activities are around the requirements for product development at a hardware level. | Documented Target Functional Safety Capability |
| Part 5: Product Development at a Hardware Level | b. Specification of Hardware Safety Requirements | Pass | Hardware safety requirements have been generated from assumptions on the intended system. | Target Functional Safety Capability, System Functional Safety Assumptions and Component Safety Requirements, SRS |
| Part 5: Product Development at a Hardware Level | c. Hardware Design | Pass | Safety requirements have been incorporated into the design. Safety Analysis Report generated. | Design Specification |
| Part 5: Product Development at a Hardware Level | d. Evaluation of the Hardware Architectural Metrics | N/A | The requirements in this section are at the item level and do not apply to SEooC development. The calculations for the SEooC hardware component have been generated. | Functional Safety Analysis Report |
| Part 5: Product Development at a Hardware Level | e. Evaluation of Safety Goal Violations Due to Random Hardware Failures | N/A | The requirements in this section are at the item level and do not apply to SEooC development. The calculations for the SEooC hardware component have been generated. | Functional Safety Analysis Report |
| Part 5: Product Development at a Hardware Level | f. Hardware Integration and Testing | N/A | The requirements in this section are not applicable to SEooC development. | N/A |
| Part 6: Product Development at a Software Level | All sections | N/A | There are no software requirements for this SEooC development. | N/A |
| Part 7: Production and Operation | a. Production | Pass | Production details related to this SEooC are documented. The majority of the requirements in this section are not applicable to this SEooC development. | Production Plan |
| Part 7: Production and Operation | b. Operation, Service, and Decommissioning | N/A | The requirements in this section are not applicable to this SEooC development. | N/A |
| Part 8: Supporting Processes | a. Interfaces within distributed developments | N/A | The requirements in this section are not applicable to this SEooC development. A DIA is included in the Safety Manual for clarification of responsibilities. | N/A |
| Part 8: Supporting Processes | b. Specification and Management of Safety Requirements | Pass | Attention was given to safety requirements traceability throughout this project. | System Functional Safety Assumptions and Component Safety Requirements, SRS, Functional Safety Plan |
| Part 8: Supporting Processes | c. Configuration Management | Pass | Configuration management has been put in place for the work products created for this project. | TI Functional Safety Hardware development process, Functional Safety Plan |
| Part 8: Supporting Processes | d. Change Management | Pass | Change management requirements have been followed for this project and any changes that would impact safety have been addressed. | Functional Safety Plan |
| Part 8: Supporting Processes | e. Verification | Pass | Verification activities have been planned and executed. | Verification Plans and Reports for each safety work product per Safety Plan |
| Part 8: Supporting Processes | f. Documentation | Pass | This project follows TI Functional Safety Hardware documentation strategy. | TI Functional Safety Hardware development flow, Functional Safety Plan |
| Part 8: Supporting Processes | g. Confidence in Use of Software Tools | Pass | Software tool confidence has been documented. | Software Tool Plan |
| Part 8: Supporting Processes | h. Qualification of Software Components | N/A | Software components are not an aspect of this product. | N/A |
| Part 8: Supporting Processes | i. Qualification of Hardware Components | Pass | IC was qualified per AEC-Q100 requirements. Qualification requirements related to the applicability of the IC to be integrated into the system do not apply to SEooC development. | Qualification Plan and Report |
| Part 8: Supporting Processes | j. Proven in Use Argument | N/A | Proven in use argument is not claimed. | N/A |
| Part 9: ASIL Analysis | a. Requirements Decomposition | N/A | ASIL requirements were not decomposed. | N/A |
| Part 9: ASIL Analysis | b. Criteria for Coexistence of Elements | N/A | No coexisting requirements | N/A |
| Part 9: ASIL Analysis | c. Analysis of Dependent Failures | Pass | Dependent failure analysis was considered at the hardware component level. | Dependent Failure Analysis |
| Part 9: ASIL Analysis | d. Safety Analysis | Pass | FMEA, FMEDA, FIT calculations and others are included for the hardware component. | Functional Safety Analysis Report |
| Part 10: Guideline on ISO 26262 | No requirements in this part | N/A | ISO 26262-10 is an informative reference. There are no requirements in ISO 26262-10, however the work products and analysis techniques that are recommended by this part are incorporated into the TI Functional Safety Hardware development flow and work product templates that have been used for this project. | N/A |
| Part 11: Guidelines on Application of ISO 26262 to semiconductors | No requirements in this part | N/A | ISO 26262-11 is an informative reference. There are no requirements in ISO 26262-11, however the work products and analysis techniques that are recommended by this part are incorporated into the TI Functional Safety Hardware development flow and work product templates that have been used for this project. | N/A |
| Part 12: Adaption of ISO 26262 to Motorcycles | All sections | N/A | The tables of ISO 26262-12 only apply at the system level for motorcycles, they do not apply to a hardware component SEooC. These tables are the responsibility of the system integrator if applicable. | N/A |