Abstract

International audience; Automation, embedded software, stringent regulation and customer expectations have increased the complexity of ship design and requirements management. The requirements management approach described here brings two innovations with respect to existing tools used in the shipbuilding industry. First, requirements are assigned to operational scenarios rather than physical components to emphasize the focus on customer needs rather than subsystem optimization. Second, a tool based on a microservices architecture is introduced to manage scenario-centered " communities of interest " to which system architecture blocks and requirements subscribe depending on their involvement in the scenario. System architecture, operational scenarios, customer requirements are designed and managed in separate tools and the overall consistency of the design – reflected in the compliance matrix model-is preserved within each " community " they belong to. Collaborative ship design where partners provide diverse contributions to the design of a single vessel could benefit from such an approach. Document type: Conference object

Abstract

Mobility as a Service (MaaS) is a concept that aligns with both current and future mobility demands of users, namely intermodal, personalized, on-demand and seamless. Although the number of shared mobility, electric mobility and multimodal passenger transport users is rapidly growing, until now, the list of MaaS and electric Mobility as Service (eMaaS) providers is quite short. This could partly be explained by the lack of a common architecture that facilitates the complex integration of all actors involved in the (e)MaaS ecosystem. The goal of this publication is to give an overview of the state of the art regarding (e)MaaS&rsquo ecosystems and architectures. Moreover, it aims to support the further development of eMaaS by proposing a definition and a novel system architecture for eMaaS. Firstly, the state of the art of the MaaS ecosystem is reviewed. Secondly, the eMaaS ecosystem that builds upon our definition of eMaaS is described and the MaaS system- and technical- architectures found in literature are reviewed. Finally, an eMaaS architecture that focuses on the integration of MaaS and electric mobility systems is presented. With the definition, ecosystem and system architecture presented in this work, the aim is to support the further development of the eMaaS concept. Document type: Article