There are cases where the 'dateTime -- Date and time from the telematics device' field isn't enough.
When drivers propose edits to events the new event time doesn't fit into the definition of 'dateTime' since the time of edit by the driver is a better fit, leaving the new event time without a home field. When support personnel make proposed changes to Log Events, the new event time cannot reasonably be put into the dateTime field; furthermore the dateTime field is there so that latency as compared to serverTime can be calculated and inserting new event times in there would poison such calculations.
To support events edited by support personnel from systems other than the telematics devices the dateTime field will need to be optional.
A new field for event times will be a required field.
There are cases where the 'dateTime -- Date and time from the telematics device' field isn't enough.
When drivers propose edits to events the new event time doesn't fit into the definition of 'dateTime' since the time of edit by the driver is a better fit, leaving the new event time without a home field. When support personnel make proposed changes to Log Events, the new event time cannot reasonably be put into the dateTime field; furthermore the dateTime field is there so that latency as compared to serverTime can be calculated and inserting new event times in there would poison such calculations.
To support events edited by support personnel from systems other than the telematics devices the dateTime field will need to be optional.
A new field for event times will be a required field.
proposed field name:
eventDateTime