Towards Enabling Cross-Organizational Modeling in Automotive Ecosystems

This summer, I visited Canada as an international collaborator of NECSIS (Network for the Engineering of Complex Software-Intensive Systems for Automotive Systems) with the goal to identify synergies between my involvement in software center projects with Swedish industry (especially the Ecosystemability Assessment Method). We found that to a large extent partner industries of the NECSIS project recognize the same opportunities and challenges as Swedish industry, when it comes to engineering tomorrow’s complex software-centric systems.These stem in particular from the fact that development will increasingly be distributed over several organizations and that reliability and efficiency of development needs to be addressed across organizational borders. We will present preliminary results and future plans this week in the context of this work at MD2P2 Workshop at MoDELS 2014.

Eric Knauss and Daniela Damian: Towards Enabling Cross-Organizational Modeling in Automotive Ecosystems. In Proceedings of 1st International Workshop on Model-Driven Development Processes and Practices (MD2P2 ’14), pg. 38-47, Valencia, Spain. 2014

Abstract. Automotive engineering is characterized by relying heavily on complex supplier networks as well as by strong dependence from hardware and software component development. OEMs (original equipment manufacturers) coordinate and integrate the work of hardware and software component suppliers and to an increasing amount develop application software themselves (component suppliers can be internal). For OEMs the transition to model-driven development promises potential reduction in the development lead-time of complex in-vehicle automotive features, such as semi-autonomous driving, but it is not without challenges. For example, the verification of such features is still performed using mainly physical properties such as hardware benches and mule vehicles. While this step is necessary, it is not sufficient, because it does not allow early verification of design decisions to the required extent. In addition, the development speed of hardware and software components is (a) limited by hardware development cycles as well as (b) slowed down by unsynchronized software development cycles of key suppliers. This prevents detailed information from being available early and potentially resulting in expensive and late changes. Understanding this situation as an ecosystem of cross-organizational collaborations allows us to reason about challenges and opportunities of the interaction between the OEM and different component- as well as tool-providers. In this paper, we report first results from an exploratory study that involved interviews with one of our industrial partners, General Motors (GM). First, we describe our understanding of the automotive ecosystem. Second, we explore interactions and roles of different ecosystem actors based on workshops and interviews with engineers at GM.

Keywords. automotive, cross-organizational modelling, software ecosystem


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s