YENRA TELEMATICS INTEGRATION PILOT
Guide: https://yenra.com/telematics/
Complete for one operational workflow. Use your provider's documented API
semantics and your organization's approved vehicle/driver data practices.

Pilot owner/date:
Operational decision and person taking action:
Vehicles/device types and selection reason:
Pilot period and time zone:
Provider/API/version and documentation:

DATA CONTRACT (repeat per field)
Field and meaning:
Source and availability on selected vehicles:
Units/time basis:
Stable identity and assignment history:
Missing/invalid/late-record handling:

CLOCKS
Observation timestamp:
Integration receipt timestamp:
User-visible timestamp:
Freshness = display time minus observation time.
Acceptable age for this workflow and owner approving it:
Stale-data display and alternative action:

Example only: observation 14:00 UTC, receipt 14:07, display 14:08 gives
7 minutes before receipt + 1 minute downstream = 8 minutes observation age.
These are fictional times, not service performance claims.

INTEGRATION TESTS
[ ] Initial history/start position chosen explicitly.
[ ] Complete batch durably stored before checkpoint advancement.
[ ] Retry after interruption creates no unintended duplicates or gaps.
[ ] Empty response, late event and malformed record handled.
[ ] Identifier reassignment reconciled.
[ ] Vendor limits and backfill behavior understood.

For Geotab GetFeed specifically, consult the linked guide: persist the
returned toVersion after processing, then use it as fromVersion next time.
Other providers may use different fields and checkpoint semantics.

ACCEPTANCE
Independently established reference events and selection method:
Count of reference events:
Count matched using the agreed rule:
Unresolved events and causes:
Match percentage = 100 x matched/reference (when reference is greater than 0).
Example only: 96/100 = 96%; investigate all 4 unresolved events.
Other required quality/performance checks:
Decision, limitations, next action and owner:

Access roles/retention policy/approved exports:
Revisit after device, API, assignment or operational-purpose changes.