IoT Life-Cycle Management

The overall goal of this WP is to define a conceptual model for the “digital twin” of industrial products and to develop a prototype data management infrastructure that keeps track of these digital twins.

  • Be fully up-to-date with leading edge IoT data models in manufacturing and automotive.
  • Develop a stakeholder model which is then mapped to a technical infrastructure that is capable of capturing and managing all data generated in those environments.
  • Understand boundaries to neighbouring systems in the context of automotive and industrial eco-systems.
  • Connect life cycle data model with security & safety related concepts from WP3-WP7.
  • Specify the concept of digital twin, then implement mechanisms that capture data from physical systems and finally, “play the data back” as digital twin of the product, in a digital environment

Method

WP5 will re-visit the state of the art in reference architectures, which is developing at a fast pace, at present. This will include oneM2M, RAMI and IIRA Reference Architectures; and we will aim at a subset of concepts that is sufficient for the purpose of IoT life-cycle data management. The task will involve mainly desktop-research to ensure an updated baseline for the project.
WP5 investigates the technical infrastructure of the “multi-tenant ecosystem” around connected, autonomous cars. Therefore, the task is set up as continuous activity covering technical challenges; legislative developments in EU, US and Asia; and emerging standards for data and information exchange. An understanding of the technical challenges of in-car data capture will be created, on-line car data archiving, and connected car data streaming, from the perspectives of different stakeholders (data controllers) who also have different IT infrastructures at their disposal. The core question is the nature of interoperation and data exchange happening between these platforms. WP5 specifically addresses those aspects of the PLCDM where identity management, security features and safety issues need to be represented as data points over the product life cycle. This task ensures that research done in WP3 and WP4 is reflected in the PLCDM and that it is well connected with the hardware-enabled identity management. This should also add semantic enhancements to the component tracing explored in WP7. WP5 will use the RAMI Administration Shell and experiment with “loosely coupled” components and the data they acquire when in use. In a prototype application, we will demonstrate life cycle data management of automotive components in use, with stakeholder control over subsets of the data and – through customisation – compliant with different regulations regarding privacy and third party use of data. A permissive open source software implementation of the proof of concept prototype is planned.