Status: guided proposal for review. Not an approved implementation instruction until confirmed by the business and software owners. The current repository verifies a fleet mirror and a preferred vehicle/helper snapshot only; the external Ops repository and production contracts require separate review.
Published 12/08/2026. Source:
wiki/products/sales-module/bu/encik-beku/vehicle-operations-workflow.md
There is only one Vehicle Listing. Asset Management owns it in Utopia Space.
The Encik Beku Sales Module shows a BU-filtered view of that listing. The Utopia Ops PWA shows a vehicle picker from the same listing. Neither module creates a second vehicle record.
The vehicle picker appears only in Utopia Ops PWA. Sales and Indoor do not choose the vehicle used by the field team.
Availability and Service Request status answer different questions:
| Question | Answered by |
|---|---|
| Can the team use this vehicle now? | Available / Unavailable |
| Where is the repair or service work now? | Service Request status |
Both views read the current Vehicle ID and status from the same master.
| Module | What it does | What it must not do |
|---|---|---|
| Asset Management Vehicle Listing | Owns the vehicle, plate, Company fields, lifecycle, compliance and Visible to BUs | Must not store field-job usage as a permanent vehicle property |
| Sales Module BU Vehicle List | Shows Encik Beku-visible vehicles and lets authorised OE review availability | Must not create or copy a vehicle master |
| Utopia Ops PWA | Suggests, selects and changes the vehicle actually used by the field team | Must not add, merge, retire or freely edit a vehicle master |
| Service Request | Owns the approved repair/service status flow and the Out of Service flag | Must not become the vehicle usage history |
The Sales BU Vehicle List and the Ops picker show only vehicles allowed by Visible to BUs and the user's permission.
Staff-facing labels: Available (may be selected) · Unavailable (visible, cannot be selected now) · Retired (no longer offered for new use).
Do not use "In Service" as the staff-facing availability label. It can be understood as either usable or being serviced.
An authorised OE or Vehicle Manager may apply a manual Unavailable hold from the Sales BU Vehicle List. Sales and Indoor users are view-only unless they hold the specific vehicle-management permission.
A manual Unavailable requires a reason, and the system records the actor and time. The new state appears in Sales and Ops from the same master record. A repair, service or breakdown reason directs OE to create and submit a Service Request.
Overall availability is derived:
Active SR Out-of-Service flag OR active manual hold OR retired master → Unavailable
No active SR flag AND no manual hold AND active master → Available
OE cannot use the manual control to make a vehicle Available while an active Service Request keeps Out of Service on. Show: Controlled by SR-{number}.
Use the exact status flow from Service Request — Vehicle. Do not invent another status list in Sales or Ops.
| SR status | Vehicle shown in Sales and Ops as |
|---|---|
| Draft | Available, unless another hold exists |
| Pending to Send | Unavailable |
| Sent to Bengkel | Unavailable |
| In Repair | Unavailable |
| Ready to Return | Unavailable |
| Completed | Available, unless another hold exists |
| Cancelled before receipt | Available, unless another hold exists |
| Transferred | Unavailable, through the linked active request |
Submit Request turns the canonical Out of Service flag on. Confirm Pickup or Confirm Return Received completes the request and turns it off.
Plate as the largest text · availability badge · vehicle model and type · BU or branch · current team or driver · active SR number and status when present · View Details or View SR.
| Column | Meaning |
|---|---|
| Plate Number | Main vehicle identity |
| Vehicle | Brand, model and type |
| BU / Branch | Current operational context |
| Availability | Available or Unavailable |
| Current Assignment | Team or driver using it |
| Service Request | Active SR number and exact SR status |
| Last Updated | Actor and time of the latest status change |
| Action | View details, history, or permitted availability action |
Keep the availability control inside Vehicle Details, not as an unprotected one-tap switch on the main list.
The picker opens during Clock In. It suggests one vehicle in this order:
Use "last confirmed vehicle", not literal yesterday, because staff may not work every day.
Do not suggest a vehicle that is Unavailable, retired, outside the user's visibility, or no longer eligible for that team. The picker may still show it disabled with the reason.
Sections: 1. My BU Vehicles · 2. Borrowed Vehicles
The field team confirms the suggested plate or taps Change Vehicle. There is no separate Start Vehicle or End Vehicle button.
CURRENT VEHICLE
VCA 1234 — Toyota Hilux
[ Change Vehicle ]
When the user taps Change Vehicle:
Changing the vehicle does not move or reassign the job. The job stays with the assigned person or team.
Vehicle time follows actions staff already perform:
VCA 1234: Clock In → 2:15 PM
VBB 8899: 2:15 PM → Clock Out
Never overwrite the first plate when a vehicle changes. One day and one job may legitimately link to two plates.
Vehicle History must support both directions:
Each history event records plate, driver, start and end time, BU or branch, job links, change reason, actor and timestamp. The shared history principle remains canonical in Fleet Management.
| Role | Vehicle list | Availability | Ops picker | History |
|---|---|---|---|---|
| Sales / Indoor | View permitted BU vehicles | View only | No | View only when required for the order |
| OE | View permitted BU vehicles | May apply a manual hold with reason; SR-controlled state is locked | No normal field selection | View within permission scope |
| Field Lead / Driver | View selectable vehicles in Ops | Report an issue; no free master toggle | Confirm and Change Vehicle | View own relevant usage |
| Vehicle Manager / Admin | Manage the master within permission | Manage allowed non-SR holds and master lifecycle | No normal field selection | Full permitted history |
Story. As a field lead or Driver, I may want Clock In to suggest an eligible vehicle and Change Vehicle to preserve usage periods, so that plate history is accurate.
Acceptance. Before approval, owners must confirm the source fleet, borrowing rules, the Service Request status contract and offline behavior.
Story. As the system, I would preserve the central Vehicle ID and append usage history rather than overwrite it, so that one day can include several plates.
Acceptance. A future contract must define actor, start and end time, reason, branch context and job linkage.
Only what is on Helper and vehicle roster and Daily pairing. Everything above that line is a proposal.
Note on Encik Beku specifically: there is no driver. The technician drives.