Get Started with Aeion Fleet
Set up your first fleet in 5 steps. OBD-II diagnostics, geofencing, VRP route optimization, AI predictive maintenance, and drone dispatch—all in under 20 minutes.
Add Your Vehicles
| Type | Use Case |
|---|---|
| van | Delivery, last-mile |
| truck | Freight, heavy load |
| car | Executive, service |
| motorcycle | Quick delivery |
| drone | Autonomous delivery |
Set Up Geofences
| Action | Description |
|---|---|
| alert | Internal fleet alert |
| notification | Push/SMS/email to driver |
| webhook | HTTP POST to external system |
| task_update | Update linked task status |
| cyber_physical_toggle | Toggle physical device |
Create and Optimize Routes
Go to Fleet → Routes → New Route.
Route Stop:
typescript
{
id: "stop-1",
location: { lat: 40.7580, lng: -73.9855, address: "Times Square" },
type: "delivery",
duration: 10, // minutes at stop
priority: "high",
timeWindow: { start: "09:00", end: "12:00" },
requirements: {
skills: ["forklift"],
vehicleType: "van",
capacity: 500
}
}
Optimization Settings:
typescript
{
stops: [stop1, stop2, stop3, ...],
startLocation: { lat: 40.7128, lng: -74.0060 }, // depot
constraints: {
maxDistance: 200, // km
maxDuration: 480, // minutes (8 hours)
maxStops: 20,
vehicleCapacity: 2000, // kg
driverShiftEnd: "17:00",
avoidTolls: false,
prioritizeTime: false
}
}
Route Optimization Output:
typescript
{
stops: [ordered list],
totalDistance: 142, // km
totalDuration: 385, // minutes
totalCost: 127.50, // USD
efficiency: 87, // 0-100 score
estimatedStart: "2026-05-11T08:00:00Z",
estimatedEnd: "2026-05-11T14:25:00Z"
}
2-Opt Algorithm: The optimization uses nearest neighbor for initial solution, then 2-opt local search to improve by swapping route segments.
Enable Predictive Maintenance
| Component | Indicator | Warning | Critical |
|---|---|---|---|
| Brake pads | Pressure | <80% | <60% |
| Engine oil | Level | <30% | <15% |
| Tires | Pressure | <32psi | <28psi |
| Battery | Voltage | <12.4V | <11.8V |
Dispatch Your Fleet
Task Assignment: Go to Fleet → Dispatch → New Task.
typescript
{
type: "delivery",
title: "Deliver Package to 123 Main St",
priority: "high",
vehicleId: "van-001",
driverId: "driver-042",
stops: [
{ location: { lat: 40.7580, lng: -73.9855 }, type: "delivery", duration: 10 }
],
scheduledStart: "2026-05-11T09:00:00Z",
scheduledEnd: "2026-05-11T11:00:00Z"
}
Bulk Assign:
- Select multiple tasks
- Choose available drivers
- System validates driver/vehicle compatibility
- Bulk assign updates all tasks
Drone Dispatch (Last-Mile):
typescript
// For packages under 5kg in accessible areas
{
droneId: "drone-001",
packageId: "package-12345",
destination: { lat: 40.7484, lng: -73.9857, altitudeMeters: 30 },
waypoints: [
{ lat: 40.7489, lng: -73.9852, altitudeMeters: 50 }
]
}
// Returns: { status: "dispatched", missionId: "mission-789", estimatedFlightTimeMs: 180000 }
Drone Mission Flow:
- AI generates MAVLink mission protocol
- Binary streamed to drone via Bridge (GCS)
- Drone executes GPS waypoints
- Servo releases package at destination
- Drone returns to launch point
- RTK GPS provides telemetry
Driver Mobile App: Drivers receive tasks via mobile app:
- Live route with turn-by-turn
- Customer ETA updates
- Delivery confirmation with photo
- Issue escalation
Quick Reference
Vehicle API:
```bash # Add vehicle POST /v1/fleet_vehicles { "name": "Van #1", "type": "van", "vin": "..." }
# Get vehicle health (OBD-II) GET /fleet/metrics/vehicle/{id}
# Link telematics device POST /fleet/telematics/devices { "vehicleId": "uuid", "type": "obd2", "provider": "geotab" } ```
Geofence API:
```bash # Create geofence POST /fleet/geofences { "name": "Depot", "type": "circle", "center": {...}, "radius": 500 }
# Get geofence events GET /fleet/geofences/{id}/events
# Trigger manual action POST /fleet/geofences/{id}/trigger { "entityId": "vehicle-uuid", "action": "alert" } ```
Route Optimization API:
bash
# Optimize route
POST /fleet/optimize/route
{
"stops": [...],
"startLocation": { "lat": 40.7128, "lng": -74.0060 },
"constraints": { "maxDistance": 200, "maxStops": 20 }
}
Telematics API:
```bash # Register device POST /fleet/telematics/devices
# Send telemetry data POST /fleet/telematics/data { "deviceId": "...", "location": {...}, "diagnostics": {...} }
# Get ELD logs GET /fleet/drivers/{id}/eld-logs?date=2026-05-11 ```
Predictive Maintenance API:
```bash # Get predictions GET /fleet/vehicles/{id}/maintenance/predictions
# Schedule maintenance POST /fleet/maintenance { "vehicleId": "uuid", "type": "predictive", "component": "brake_pads" } ```
Drone Dispatch API:
```bash # Dispatch autonomous drone POST /fleet/drones/dispatch { "droneId": "drone-001", "packageId": "package-123", "destination": { "lat": 40.7484, "lng": -73.9857, "altitudeMeters": 30 } }
# Get drone status GET /fleet/drones/{id}/status ```
Fuel Card API:
```bash # Add fuel card POST /fleet/fuel-cards { "cardNumber": "...", "vehicleId": "uuid" }
# Get transactions GET /fleet/fuel-cards/{id}/transactions ```
Performance Metrics API:
```bash # Get driver score GET /fleet/drivers/{id}/performance
# Get fuel efficiency GET /fleet/vehicles/{id}/efficiency?period=30d ```
FAQ
Aeion Bridge connects to the vehicle's OBD-II port via ELM327 adapter. It sends PID requests (010C = RPM, 010D = speed, etc.) and parses responses. Vehicle health data streams to the dashboard in real-time. Browser-only mode works without Bridge but shows last known state.
Aeion generates a real MAVLink mission from your waypoints — a genuine serialized MAVLink v2 binary, not a placeholder. The binary is uplinked to the drone via Aeion Bridge over 900MHz/2.4GHz radio, which requires a connected Bridge + Ground Control Station (you get an honest error if it's disconnected — never a fabricated dispatch). Once uplinked, the drone executes GPS waypoints autonomously and drops payload at destination.
Aeion uses nearest neighbor for the initial solution, then 2-opt local search to improve it. It respects constraints: time windows, vehicle capacity, driver shift end, max stops. Output includes ordered stops, distance, duration, cost, and an efficiency score (0-100).
Aeion creates virtual boundaries (circle or polygon). When a vehicle's GPS enters, exits, or dwells inside a geofence, an event is generated. Actions can be triggered: alerts, notifications, webhooks, task updates, or cyber-physical device toggles.
Aeion gathers vehicle telemetry, maintenance history, and usage data, then sends it to your configured AI provider for analysis. AI returns predictions with confidence scores, severity, estimated cost, and the indicators behind each prediction. Predictions are stored and notifications go out automatically for high-severity items.
Electronic Logging Device (ELD) compliance tracks Hours of Service (HOS). Drivers log duty status (driving, on-duty, off-duty, sleeper berth). The system detects violations and notifies fleet managers. Required for commercial drivers in the US.
Aeion Bridge reads NFC/RFID driver badges, matches the badge to a driver record, and on a match automatically clocks the driver in and associates them with the current vehicle/shift.
Yes. Aeion supports Geotab, Samsara, Verizon, and custom providers. Configure in Fleet → Settings → Telematics. Data flows into a unified dashboard regardless of provider.
Aeion tracks every fuel transaction and calculates per-mile cost, fuel efficiency (MPG), and trends. Set budget limits and get alerted on anomalies. Route optimization also minimizes distance traveled, which cuts fuel spend directly.
Aeion replays historical trips on a map, showing the GPS track with speed/heading overlay. Incident markers (hard brake, speeding) appear on the timeline — useful for driver coaching and accident investigation.