on-imac

Standardize Your Software Architecture for the Vehicle of the Future 

Convert legacy code into AUTOSAR framework architecture, and integrate advanced workflows with AUTOSAR tools

 

Get Started Today!

CONTACT US
 

Standardize Your Software Architecture for the Automotive Industry

 

With the growing complexities of the vehicle’s electrical/electronic control systems, there was growing concern in the automotive industry of legacy code that could not be duplicated or changed without compromising the integrity of the system. In 2003, a worldwide consortium of automotive partners founded AUTOSAR in order to mitigate the risk of legacy embedded code being tied to a specific OEM or product. 

Today, new products and vehicle sub-systems need to be more flexible, and solutions need to be found across product lines. For this reason, it is expected that AUTOSAR is applied not only to software development but to the entire manufacturing process from product development to verification and validation. 

Functional safety is forcing software standardization, and AUTOSAR is how the automotive industry is standardizing. 

A one-off AUTOSAR implementation needs to be scalable across your organization and global footprint. Migration to AUTOSAR will require retraining of your software developers and management. This is comparable to the MBD-to-code movement of 20 years ago. 

Balancing the requirement of functional safety on your embedded code with the AUTOSAR standard is key to a successful implementation.

 

AdobeStock_222591309

Streamlining complex software system integration and standardizing on an architecture and development platform is crucial in the new automotive landscape.

 

Simplifying the AUTOSAR Adoption Process

 

LHP has over a decade of working knowledge in AUTOSAR migration, adoption, and configuration. LHP will engage your organization at any level of AUTOSAR development while creating a custom plan that takes into account the customer’s current needs and future goals. 

 

LHP's AUTOSAR Work Packages 

 

    • Migration to AUTOSAR
      • Define Requirements
        • LHP clearly defines customer requirement while understanding the different motivations for migrating to AUTOSAR
      • Evaluate Toolsets
        • LHP guides customers through the tool selection process
      • Previous AUTOSAR Migration Success 
        • LHP lays out a multi-year roadmap for AUTOSAR adoption - from the first prototype to production development 
        • LHP integrates the latest industry standards and plans ahead for impact on tools and methodology 
      • Analyze existing Code 
        • LHP analyzes the existing code base and plans the required re-architecture to adapt to the AUTOSAR methodology


    • BSW Configuration, Integration, and Complex Driver Development
      • BSW Vendor Selection
        • LHP has an in-depth understanding of major BSW vendors to provide realistic estimations of the broad MCAL development roadmap
      • CDD Development
        • LHP has developed CDDs for many of the common hardware systems such as fuel controls, speed sensor processing, and complex IO
      • BSW Configuration
        • LHP is experienced with the configuration of the BSW components for a variety of applications
      • Advanced Operating Systems
        • LHP has worked with advanced operating system integration for high-level functional safety and torque security


    • AUTOSAR Software Development and Integration
      • AUTOSAR Methodology for Software
        • LHP understands AUTOSAR development and AUTOSAR methodology for software development, and can help you extract maximum benefit from the flexible deployment architecture
      • Maximize Efficiency
        • LHP maximizes the reusability of software, effectively utilizes variant management, and implements system configuration for functional safety and cybersecurity
      • Integrated Design Tools
        • LHP integrates design tools to allow design information to be automatically imported from the system design into the software with no loss of fidelity
          • Example: J1939 
      • Integration of OEM Extension
        • LHP is experienced in adding OEM extensions and customizations 


  • AUTOSAR Workflow Process: Customized Tool Integration and Training
    • Software Development
      • LHP understands that software development is not a product, it is a process for consistent development of quality software across a diverse product line
    • Custom Development for Customers
      • LHP works with customers to customize and develop tools to manage the AUTOSAR workflow and training to take the best advantage of the available toolsets
lhp-stock-resized1
Get Started Today 

Need Guidance on How to Approach AUTOSAR Adoption? 

 

CONTACT US