Project

When you obtain consent from an individual, you must ask for permission to access or record specific data. Obtaining consent does not oblige you to collect this data immediately - you can still decide not to access it even after consent has been given. This principle has been applied to CarNEO. There is a clear distinction between obtaining consent to access or record user data and the actual collection of this data. The main task of a project is to define the maximum scope of data collection by specifying a set of metrics. Creating a project does not initiate data collection.

Data collection is triggered by creating "campaigns". A campaign belong to a project and contains a set of metrics. The set must be a subset of the projects' metrics. For example, you might create a project that contains the metrics A, B and C, and then create a campaign that triggers data collection for metric B only. You have the option to eventually create a new campaign that also includes the metrics A and C. It is also possible to disable campaigns at your own discretion, thereby stopping the actual data collection.

One important element is still missing when it comes to collecting data from our cars: consent.
Once you have obtained a user's consent, we create an entity that contains the project and a VIN or a UserId of an individual that is assigned to one of our vehicles.
Therefore, we will effectively establish a link between a project and a series of physical cars.
These cars will automatically fetch all active campaigns that are assigned to the project and execute them.

Create a Project

After an organization has been created you can create a project.

Frontend:
1. Click "+"-Button.
2. Provide a project name and purpose.
3. Select "Third Party Processor" if available.
4. Select Metrices.

API:

POST /projects/{organization_id}

Note: You can not create a project for a disables/blocked organization.