Event Data

Defines the properties containing the actual payload sent to the end consumer.

"eventType": "tachoActivity"
"eventVersion": 1
"eventData":

The core event data contains the following fields:

• Driver ID
• Vehicle ID
• Driver role (driver or co-driver)
• Origin
• Start time
• Work code of the 5 tacho statuses (driving, resting, working, availability, unknown).
• Ferry/Train status
• Out of scope status
• Multiple driver status
• Mileage

Each time, for this scenario, a new event will be generated with the same start time as a previous one to correct for the same driver, indicating a tacho status change for this driver and so an event to correct in the timeline. This new event will provide the same work code as before the event to correct, retrieving the initial state for the concerned driver.

• Customers only need to check “driverId” and timestamp and apply correction to what is identical to the data compared to the available data.
• For “Push Tacho times” functionality, the data is based on the OBC tacho source and is extracted from the DRT module.

Event example,

{
  "eventBatchId": "bd420fec-c288-4b82-8559-271733818760",
  "eventSubscriptionId": "17082862-10f2-41f7-aade-a2c1b463e597",
  "eventBatchTime": "2025-01-30T08:32:16.9682811Z",
  "eventsData": [
    {
      "eventType": "driverSocialActivity.drivingAndRestingTimes.tachoActivity",
      "eventVersion": 1,
      "eventData": {
        "driverId": "7c5c6eb3-39e3-4f43-8f7b-1f9ddfdd4492",
        "vehicleId": "9f64d12c-822b-40c0-9d96-c470087d34d8",
        "driverRole": "driver",
        "origin": "obcTacho",
        "workCode": "working",
        "ferryTrain": false,
        "outOfScope": false,
        "multipleDriver": false,
        "mileage": 553720,
        "organizationId": "1a911872-0a62-427e-b7d5-6433a40c591a",
        "registeredOn": "2025-01-30T08:30:00Z",
        "eventId": "3b836694-cefa-4024-b02a-ce8eaa4b13b7",
        "occurredOn": "2025-01-30T08:30:00Z"
      }
    }
  ]
}