ຂ້າມໄປຫາເນື້ອຫາ
ERPStack

ຊັບສິນ ແລະ ການສົ່ງມອບ

ຍານພາຫະນະ

Fleet control for vehicles, drivers, assignments, trips, fuel, inspections, maintenance, incidents, expenses, and provider sync.

ນຳໃຊ້ແລ້ວ Evidence-first module page
Primary users
Fleet manager Dispatcher Driver supervisor Operations reviewer
/app/fleet
App-derived visual
Fleet operations console
Open app route
Vehicles
Assigned
Maintenance
Due tracked
Provider sync
Monitored
ພື້ນທີ່ ສະຖານະ ຫຼັກຖານ
Assignments Driver linked Custody record
Inspections Safety tracked Inspection proof
Maintenance Provider aware Sync event

ຂັ້ນຕອນຫຼັກ

What the module helps operators complete.

Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.

Step 1
Maintain vehicles, drivers, and assignment history
Step 2
Record trips, fuel logs, inspections, maintenance, and incidents
Step 3
Review provider sync and operational exceptions
Step 4
Analyze fleet expenses, utilization, and safety evidence

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Fleet register

  • Vehicles
  • Drivers
  • Assignments
  • Trip logs

Maintenance and safety

  • Fuel logs
  • Inspections
  • Maintenance
  • Incidents

Cost and providers

  • Fleet expenses
  • Provider sync
  • Exception evidence
  • ລາຍງານ

Connected module map

How this module exchanges business context with the rest of ERPStack.

Module ຄວາມສຳພັນ
ຊັບສິນຖາວອນ Vehicle asset registration and custody
ຄ່າໃຊ້ຈ່າຍ Fuel, maintenance, and travel expense evidence
ໂຄງການ Vehicle assignment and project delivery context
ປະຕິບັດການຄວາມປອດໄພ Provider sync and high-risk fleet events

Governance and reporting

Controls and management visibility expected from a serious ERP module.

ການກຳກັບດູແລ
  • Provider sync SIEM events
  • Maintenance evidence
  • Inspection traceability
  • Incident audit
ລາຍງານ
  • Fleet register
  • Fuel usage
  • Maintenance due
  • Incident trend

AI coverage policy

What ERPStack can honestly claim for this module today.

AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.

AI L2 ready
Coverage claim Current AI coverage: Fleet L2/L2 ready through the official Agent Tool Registry.
Governance evidence Governance evidence: 2 registered tools, 2 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence.
Scheduled monitor Scheduled monitor readiness: not in the current proactive-agent monitor wave.
L4/L5 boundary Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable.

Evidence-first standard

Module pages explain value, workflow, control, and proof in one place.

This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.

Feature clarity

Buyers can see concrete function groups instead of vague capability claims.

Operational fit

Workflows, users, and connected modules show where the module belongs.

Governance proof

RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.

Review path

Public pages link back to app routes so reviewers can compare page claims to product surfaces.