Porsche AG’s Post

Case Study Showcase A client in the automotive manufacturing industry had difficulty achieving improvements in vehicle design and performance. Here's how Aetos Design and Engineering helped them through the use of Siemens' advanced simulation software. And the results? 15% increase in fuel efficiency 30% reduction in time-to-market 20% increase in cost savings

🚗 Mastering Requirements in Automotive Software Development 🚗 In automotive engineering, the foundation of a successful project is clear, well-defined requirements. Here's how it all comes together for building smarter, safer, and more reliable vehicles: 🔑 Business Requirements: Outline project goals, timelines, and market needs.  👥 Stakeholder Requirements: Capture expectations from customers, suppliers, and regulatory bodies.  🛠️ System Requirements (SYS): Define how hardware and software interact to create a seamless system:   - SYS.1 – Capture high-level system needs.   - SYS.2– Analyse and refine requirements.   - SYS.3 – Design system architecture and define component interactions.   - SYS.4 – Detailed component-level design.   - SYS.5 – Integrate and test subsystems for seamless functionality.   - SYS.6 – Validate against customer needs and safety standards.   - SYS.7 – Release and deploy the final system. ⚙️ Functional Requirements: Specify what the system should do, like ECU communication or feature control.  💡 Non-Functional Requirements: Address performance, safety, reliability (think ISO 26262 for functional safety and cybersecurity). With the right requirements, we build the future of automotive excellence! 🚀 #AutomotiveEngineering #RequirementsManagement #VModel #FunctionalSafety #ISO26262 #AUTOSAR #EngineeringInnovation #SmartVehicles #BMW

The automotive industry's embrace of electronic systems is accelerating rapidly, leading to vehicles with enhanced connectivity, security, driveability, and comfort compared to previous models. This expansion brings a surge in electronic control modules (ECUs) and complex software, necessitating a robust development process to ensure quality and efficiency while eliminating bugs. Enter the V-cycle, the standard software development process in automotive. It divides development into two phases: requirement analysis, design, and change management on the left, and verification and validation on the right. Key Steps: 1. Function Requirements: Define what the software should do. 2. Function Development: Design and test functionality using model-based development. 3. Software Development: Code the software, considering functionality and optimization. 4. Software Integration: Combine and test all modules at the system level. 5. Function Integration: Test the developed function in the vehicle. 6. Function Calibration: Fine-tune parameters for optimal performance. Advantages of the V-cycle include simplicity, clear roles, and efficiency with clear requirements. However, it lacks flexibility in emergencies and doesn't provide early prototypes, and problem resolution during testing phases can be unclear. #AutomotiveTech #SoftwareDevelopment #VCycle

Differentiating Full Vehicle Integration Testing and Electrical-Electronics Bench Testing: Insights from the V-Cycle and Automotive SPICE In the world of automotive engineering, **Full Vehicle Integration Testing (FVIT)** and **Electrical-Electronics Bench Testing (EEBT)** play crucial but distinct roles. FVIT focuses on ensuring that all components of the vehicle work together seamlessly, simulating real-world conditions, whereas EEBT emphasizes component-level testing in a controlled environment. ⚠️⚠️⚠️⚠️⚠️⚠️⚠️ **Key differences:** 1. **Scope and Environment**: FVIT involves the entire vehicle, including mechanical systems, while EEBT isolates electrical/electronic components. 2. **Real-world Simulation**: FVIT replicates actual driving scenarios, whereas EEBT checks specific functions without full vehicle integration. 3. **Development Stage**: FVIT often occurs at later stages of the development cycle, while EEBT is a critical step during earlier component-level validations. When we examine these differences in the context of the **V-Cycle** and **Automotive SPICE** standards, the relationship between process maturity and testing approaches becomes evident. The V-Cycle emphasizes a structured and iterative approach to system development, aligning with the integrated, comprehensive focus of FVIT. Meanwhile, Automotive SPICE's structured approach to software quality maps closely to the detail-oriented, isolated nature of EEBT. Understanding these distinctions ensures a more targeted approach to both testing phases, aligning with industry best practices and quality benchmarks. **In the R&D organization, Electrical-Electronics Bench Testing should be performed by the Electrical-Electronics Systems team, as they hold the expertise in this domain.**

🌎 In the world of automotive and mechanical engineering, ensuring the reliability and efficiency of power transmission systems is critical. This is where reducer and transmission test benches come into play, each designed to meet the specific demands of industrial and automotive applications. 🌌 While the reducer test bench focuses on mechanical performance and durability, the transmission test bench evaluates dynamic performance and integration within vehicles. Advanced tools like the Electric drive EMC Dynamometer System further enhance these testing processes, ensuring comprehensive assessments. #Atestman #EngineeringExcellence #PowerTransmission #AutomotiveTesting Cblog/unveiling-the-distinctions-between-reducer-and-transmission-test-benches.html

What does the code P0000 signify in automotive computer diagnostics when checked by mechanical engineers?

I’m sure that lately, you’ve been hearing more and more about the importance of software for automotive OEMs.   It’s increasingly being seen as a major differentiator and key to providing satisfying and safely connected mobility experiences. But it’s also a major challenge for OEMs, many of whom have built their brands and businesses around mechanical engineering expertise.   Should they follow their rival digital upstarts, or transform on their own terms? It’s an interesting dilemma.   Check out more here 🔗https://bit.ly/3VyMneH And let me know in the comments about your thoughts on software for automotive OEMs.

I’m sure that lately, you’ve been hearing more and more about the importance of software for automotive OEMs.   It’s increasingly being seen as a major differentiator and key to providing satisfying and safely connected mobility experiences. But it’s also a major challenge for OEMs, many of whom have built their brands and businesses around mechanical engineering expertise.   Should they follow their rival digital upstarts, or transform on their own terms? It’s an interesting dilemma.   Check out more here 🔗https://bit.ly/3VyMneH And let me know in the comments about your thoughts on software for automotive OEMs.

I’m sure that lately, you’ve been hearing more and more about the importance of software for automotive OEMs.   It’s increasingly being seen as a major differentiator and key to providing satisfying and safely connected mobility experiences. But it’s also a major challenge for OEMs, many of whom have built their brands and businesses around mechanical engineering expertise.   Should they follow their rival digital upstarts, or transform on their own terms? It’s an interesting dilemma.   Check out more here 🔗https://bit.ly/3VyMneH And let me know in the comments about your thoughts on software for automotive OEMs.

You can reduce your e-drive development time and effort by 50%. 💵 But how is this possible?   Let me explain. The common development process of an e-drive includes several iterations (A-phase, B-phase, …). This means creating a prototype and testing it to identify issues in the design after every single phase. Not only is this a costly process, it also takes a lot of time to build the prototypes.   With an approach that focuses on simulation, it is possible to reduce development effort and time by about 50%. The AVL Advanced Design Verification Plan (DVP) works by creating a prototype in the A-phase and focus the test on gaining the data for the validation of the simulation model. After that, all following tests can be conducted on validated simulation models.   Lean more: https://lnkd.in/dWANGwrE #virtualtwin #edrive #electricvehicle