⚠️ Project Status: Archived

This blueprint repository has been archived and is no longer under active maintenance.

📄 For the formal discussion and rationale, please refer to: eclipse-sdv-blueprints/blueprints#20

Status and Scope

Following the outcome of the community discussion documented in the issue above, this repository has transitioned to an inactive state. It is retained under the project for archival and reference purposes only.

Contribution Policy

Effective immediately:

• Issues will not be monitored or triaged
• Pull Requests will not be reviewed or merged
• No further development activities will be carried out

As such, this repository should be considered read-only.

Guidance to Users

Consumers of this repository are encouraged to:

• Evaluate alternative, actively maintained projects within the ecosystem
• Fork the repository if continued development is required for specific use cases

Archival Intent

The repository remains available to:

• Preserve the historical record of the project
• Provide visibility into prior design and implementation decisions
• Support reuse in downstream or derivative work, where appropriate

Description

The Eclipse SDV Blueprints project is a collaborative initiative led by Eclipse SDV members to bring the software defined vehicle concepts to life.

The project hosts a collection of blueprints that demonstrate the application of technologies developed in the context of the Eclipse SDV Working Group.

This repository contains the Insurance Blueprint.

Overview

The maneuver detection module consist of a collection of event detectors. Each detector monitors a number of signals (for example, speed, brake pedal position or steering wheel angle) at high resolution. When the monitor is triggered, it collects relevant signals associated to the event from the circular buffer. The event detector creates an event payload with additional metadata information. A cloud connector transports the event to the telematics platform.

The telematics platform (representing a vehicle OEM) stores all insurance events in an insurance landing zone. An Eclipse Dataspace component provides a catalog that describes both aggregated and individual datasets. A second Eclipse Dataspace component, representing the insurance company, uses the catalog to discover relevant signals and can connect to the event stream.

The code is organized in three parts:

• Edge contains examples for risk event detectors and integration with the Eclipse Orchestration Blueprint
• Telematics Platform contains examples to receive vehicle data, store it and process it as a data product.
• Insurance Platform showcases consumption of data using Eclipse Dataspaces

Local Testing

To trigger all Unittests and generate a coverage report execute the following command:

./dev ./bin/unittest

This builds a docker image, runs it in a container and executes the Unittest script.