Fleet register
- Vehicles
- Drivers
- Assignments
- Trip logs
Assets And Delivery
차량
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-derived visual
Fleet operations console
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.
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.