Skip to content

TrakarIA product overview

TrakarIA is an application for recording information about vehicles and carrying out work connected to them. A vehicle record brings together its identity, photos, documents, mileage, inspections and dated history. Teams can use that context in the Sales, Rental and Fleet spaces. Each space has its own workflow.

This page describes concepts shared by the product. For its customer-facing presentation, see the TrakarIA website.

The vehicle is the common reference point. Work completed in one part of the application can add information or evidence to its record, subject to the rules of that workflow. A later action can use the relevant existing context.

Part of the recordWhat it represents
Identity and detailsThe vehicle and the descriptive information held about it
EvidenceSource photos, documents and observations associated with a specific action
Reviewed informationInformation confirmed or corrected by a person, distinguished from an automated suggestion
HistoryDated changes and operations that help explain the vehicle’s current state
OutputsReports or presentations produced by a specific workflow, with their own access rules

A common vehicle record does not make every field visible to every user or reusable in every output. Access, provenance and the rules of the active workflow still apply.

  1. A person creates or opens a vehicle record in a group.
  2. They add information or capture evidence while carrying out a task.
  3. Where a feature proposes information from a photo or document, a person reviews it before it becomes confirmed business information.
  4. The application records the resulting action and its context. Depending on the workflow, this may produce an inspection report, a vehicle presentation or another operational result.

The exact steps and available outputs depend on the product space. A suggested finding should not be read as a confirmed finding before review.

A group is a shared workspace for users, vehicles and related records. A person signs in with their own account. Their membership, role and permissions determine what they can see and do. Groups can be organized into a hierarchy when an organization needs separate teams or sites. Read organizations and groups for the access model.

Software can connect to TrakarIA where a public integration exists. A software credential identifies the integration; it does not replace a person’s account or approval. The public API currently documents Rental only. Application features in Sales or Fleet do not imply that public API routes exist for them.

SpaceWork centered on the vehicleDocumentation here
SalesPreparing vehicle information and presentation for saleSales area — public API contract pending
RentalRecording vehicle condition at handover and comparing it at returnRental workflow — public API available
FleetFollowing vehicle condition and operational history across a fleetFleet area — public API contract pending

Authorized people carry out work in the TrakarIA application. The space guides describe their own workflows and available integrations.