492 words, 1.8 minutes read.
ISO 26262 1 big thing: Decompose new vehicle level functional requirements into system, subsystem, and component level requirements.
The big picture: Design and develop state of the art Electronic Chassis Systems, and the interactions with Powertrain and ADAS, covering a variety of engineering tasks.
Why it matters: Make sure your workforce is involved in fta, fmeda, functional hazard and safety analysis Interface with your operation is involved in developing technical safety concepts and system safety requirements.
Meanwhile: Make sure your process is working with software and system teams to lead the AUTOSAR development workflow including system description, development of components, integration of components to the system, deployment on target hardware, debugging using tools for embedded systems.
State of play: Lead development activities while providing direction to the extended software development team Additional responsibilities which need to be in place include current product support of the legacy embedded controller.
The backdrop: Ensure your process is using enterprise architect (ea, or similar), documents system architecture in an unambiguous, clear, and understandable way that electrical and software engineers know exactly what they have to do in order to meet customer expectations.
Yes, but: Make certain that your company promotes efforts to acquire additional business from the customer including recommendations for future products and designs by providing solutions through designated channels.
What they’re saying: “Lead and support internal and external ISO 26262 efforts, understanding technical details well enough to generate documents and work products required by the ISO 26262 standard.“, Cynthia C. – Automated Driving + ADAS Compute System Architect
Go deeper: Liaison with your staff is responsible for the systems requirements and design architecture for motor control, power management, and thermal protection in electronic steering systems.
What to watch: Own the business cases for all new and existing sensor products by evaluating P and L and ROI throughout each phase of development.
Between the lines: Ensure that appropriate technical interface during the product development cycle is established and maintained with the customer including providing support during field failures or other failed components when necessary.
The bottom line: Work alongside the Functional Safety development teams to ensure transfer of functional safety knowledge from the vehicle development phase to the production phase.
What’s next: Be certain that your company is planning and tracking of work packages and tasks in accordance with the safety plan and project plan.
ICYMI: Ensure you are expanding your go to market team of Application Engineers, who work alongside the sales team to ensure customer success and satisfaction.
A MESSAGE FROM THE ART OF SERVICE
Trusted by: FLIR Systems, Dana Incorporated, General Motors, Sensata Technologies, NVIDIA, Navistar, Inc., Aptiv, ZF, Apple, Aurora, Lucid Motors, Molex, Gentherm, Rivian Automotive, Nexteer Automotive Corporation, Underwriters Laboratories Inc., Cresttek LLC, GKN, Syncroness, Tata Technologies Inc., Astronics CSC, HORIBA, FORT Robotics, Intertek, Ford Motor Company, Virgin Hyperloop, Faurecia, MathWorks, Stoneridge, Real-Time Innovations, Torc Robotics, ADAC Automotive, Cummins Inc., Knorr-Bremse North America, BorgWarner, Tesla, Garrett Advancing Motion, Enersys, Schaeffler Group, Lear Corporation, Wabco, Ricardo, May Mobility, Amazon.com Services LLC, Microchip Technology, PACCAR, ON Semiconductor, dura auto, Marvell, Meritor, EATON, SL America