3.1.11 Mechatronics
3.1.11 Mechatronics
Definition
A mechatronic supplier is a supplier that delivers to Autoliv, either in serial life or during development phase (prototypes / pre-production parts), components that contain electrical, electronic or software parts with or without mechanical integration of those components.
Common acronyms:
- SW - Software
- HW - Hardware
- WCCA - Worst Case Circuit Analysis
- BOM - Bill of Materials
- PCBA - Printed Circuit Board Assembly
- EMC - Electromagnetic Compatibility
Requirements for Mechatronic Suppliers
General Requirements:
- A supplier interface shall be clearly defined on both sides Autoliv and supplier
- The supplier shall provide a detailed cost analysis to Autoliv for the solution proposed
- Regular follow up meetings shall be set up with Autoliv and/or with the customer depending on Autoliv business strategy
- The supplier shall analyze all the requirements and make a status for each one through a compliance matrix
- The supplier shall provide a clear view of the technology solution proposed for each RFQ with the performance/limitation of the solution proposed
- A detailed action plan shall be provided for each failed test
- If the requirements include items related to ISO-26262, the Supplier shall:
- Develop the system according to the ISO-26262 ASIL level specified in the referenced Requirements document, hereafter referred to as the ‘Autoliv ASIL level’
- Provide Autoliv with documented evidence demonstrating that the development was conducted according to the Autoliv ASIL level (including proofs for third party SW used for the development)
- Test the system to confirm that it meets the Autoliv ASIL level and provide summary results to Autoliv for review
- If the requirements include items related to ISO-21434, the Supplier shall:
- Comply with the requirements from Autoliv Supplier Manual section 3.1.10 Cyber Security
- Confirm that all Cybersecurity activities are included in the project planning and management (TARA & Vulnerability analyses)
- Customer specific requirements (OEM) are received, reviewed, and evaluated – CIA is released
Hardware:
- Supplier shall provide electrical schematic diagrams with component values, tolerances and name
- Supplier shall provide PCBA layout for all layers
- Supplier shall provide BOM for all components including the following:
- All components that are part of the Printed Circuit Board Assembly (PCBA)
- Stand alone passive and/or active components
- BOM shall contain:
- Manufacturer part numbers
- Country of origin of component, wafer fab (if applicable), packaging location (if applicable)
- Supplier shall provide datasheets for all components
- All components are active from the manufacturer
- All components must be automotive qualified
- Supplier shall perform Worst Case Circuit Analysis (WCCA) and ensure component margins are <%90 or obtain a deviation from the responsible Autoliv engineer
Software:
- In regard to ASPICE standard compliance supplier must provide:
- During nomination phase:
- An assessment report(s) performed by an external assessor on previous project with similar products and on the same development teams and location that shall not be older than 2 years from the date of RFQ submission and demonstrates Level 2 capability (for all processes, tasks and activities under the responsibility of the supplier)
- If the certificate shows deviations from the required capability level, an improvement plan to address the deviations shall be presented to Autoliv
- If no assessment has been performed, the Supplier shall provide to Autoliv its Process Improvement Plan for targeting an assessment with the target Capability Level 2 (for all processes, tasks, and activities under the responsibility of the supplier)
- During project development:
- Plan the relevant activities during the project development activities in order to reach the agreed ASPICE level (for all processes, tasks and activities under the responsibility of the supplier)
- Allow Autoliv and/or third-party assessments during the project development in order to assess the ASPICE levels at different stages during the development
- If the ASPICE assessment shows deviations from the required capability level, an improvement plan to address the deviations shall be presented to Autoliv
- The assessments shall be carried out according to ISO / IEC 33002 with the following requirements being fulfilled:
- PAM Name & Version: Automotive SPICE v4.0 or higher
- Guideline name: Automotive SPICE Guidelines for ASPICE v4.0
- Process Context Category: B (entire product /delivery)
- Category of independence: A,B
- Purpose: Identifying and reducing process related product risks (SPICE Guideline V4.0 section 1.2)
- In the case of cybersecurity, the supplier has also achieved A-SPICE level 2 for the SEC Scope (for all processes, tasks, and activities under the responsibility of the supplier)
- During nomination phase:
- Source code developed by the supplier shall comply with MISRA C:2012
- The supplier shall provide SW architecture documentation (if safety requirements present, safety impacted components shall be identifiable in the SW architecture)
- The supplier shall provide Autoliv requirements coverage matrices
- The supplier shall provide a release note for each SW release including:
- SW identification and compatibilities (HW/SW for example)
- Implemented features / corrected bugs on the SW version
- Known issues
- Resources consumption (memory, CPU, stack)
- Status of tests (unit tests, integration tests, qualification tests) including requirements coverage rate
- Static analysis report
- Compiler warning list
- The supplier shall provide/present (on request only) any SW technical document requested by Autoliv (Detailed design, safety analysis, code…)
- If not covered by ASPICE assessment on SUP.8, the supplier shall present their configuration management plan and tools used to manage versions and change control
Manufacturing
Must comply with the applicable S-MPSs related to their process e.g., SMPS-030 and with the ALV-S069 special process assessments.
Latest revision
System upgrade revision, no content change