DVIR Operations

Execute DVIR with confidence: pre-trip, post-trip, daily requirement, and trailer/truck swap scenarios.

Overview

This page documents the current DVIR behavior in SimDuty and the practical operator flow for daily use.

Use it whenever inspection state looks unclear, submit is blocked, or post-trip/pre-trip requirements appear after identity or day changes.

Estimated time: 6 minutes Result: clean DVIR status with valid records Scope: Truck + Trailer, PreTrip + PostTrip
Required

Use the correct inspection type and unit before submitting (Truck/Trailer and PreTrip/PostTrip)

Required

Complete checklist review, signature, and minimum inspection time before submit

Required

Handle day-change and swap pending requests in order to clear sticky requirements

Recommended

Treat telemetry and advisory findings as risk guidance, then record your final inspection decision

Recommended

Use DVIR History filters to validate what was submitted and for which unit/session

Optional

Use PostTrip notes to leave context for follow-up maintenance or support reviews

Current behavior note: DVIR is enforced through pending status, overlays, and dispatch guidance. It is not a speed lock gate in current production behavior.

Inspection workflow

  1. Open the DVIR tab and choose the required inspection type: PreTrip or PostTrip.
  2. Select the correct unit: Truck or Trailer.
  3. Review checklist items and mark each condition as pass/fail with accurate notes when defects exist.
  4. Confirm signature and wait until inspection time gate is complete.
  5. Submit and re-check pending indicators in header/overlay and the DVIR status area.

Practical order for common operations:

  • Start of duty period: Truck PreTrip, then Trailer PreTrip (if trailer is attached).
  • Truck swap: complete Truck PostTrip for previous truck, then Truck PreTrip for new truck context.
  • Trailer drop/hook: complete Trailer PostTrip for previous trailer, then Trailer PreTrip for new trailer.
  • Daily rollover (new game day): complete pending DVIR requests triggered by day-change before normal operation resumes.

Requirement triggers

  • Day change: a new game day can require fresh PreTrip inspections (midnight game-day boundary).
  • Truck identity change: changing to another truck can create sticky DVIR requirements until expected inspection is submitted.
  • Trailer identity change: drop/hook or trailer swap can trigger trailer-specific pending workflow.
  • PostTrip swap workflow: after drop/swap contexts, post-trip confirmation may remain pending until correct unit/type is submitted.
  • Delivery completion: delivery alone does not automatically create a mandatory PostTrip request in current behavior.
  • Unsafe/advisory context: dispatch and UI can escalate warnings when operation remains unsafe without completed inspection follow-up.

Submission rules

  • Submit is blocked until the minimum inspection timer is reached (5-second gate).
  • Checklist progress and signature state must be valid for the selected inspection context.
  • PreTrip and PostTrip states are context-isolated per unit/session; complete the one actually requested.
  • Telemetry advisories help identify risk but do not hard-force fail all items; operator judgment is still required.
  • History records include time, status, unit, type, defects, truck/trailer identity, and session context for traceability.
Important: if you submit the wrong combination (for example, Trailer PreTrip when Truck PostTrip is pending), the requirement can remain active even after a successful submit.

Wrong-context submit examples

Example 1: Truck PostTrip pending, Trailer PreTrip submitted

  • What happened: submit succeeded technically, but pending state did not clear.
  • Why: the requested context was Truck PostTrip, but a different unit/type was sent.
  • Fix: switch to Truck + PostTrip, complete checklist/signature, then submit again.

Example 2: Trailer swap flow without previous trailer PostTrip

  • What happened: trailer requests keep returning even after new trailer PreTrip.
  • Why: previous trailer PostTrip was still expected in swap closure sequence.
  • Fix: complete old trailer PostTrip first, then new trailer PreTrip, and validate both records in History.

Path and reference

Main path: DVIR tab

  • Inspection type selector: PreTrip or PostTrip
  • Unit selector: Truck or Trailer
  • Checklist panel: review and mark inspection items
  • Submit area: signature + submit state + block reason
  • History tab: filter by Unit, Type, and Status

Validation checkpoint

  • All pending DVIR requests are resolved for the expected unit and inspection type.
  • Minimum inspection time gate is respected before each submit.
  • Submitted records appear in History with coherent unit/type/status data.
  • After swap or day-change scenarios, no stale pending indicator remains.
  • Unsafe or warning contexts are reviewed and documented with practical defect notes.

Quick support

Symptom: Submit button stays blocked.

  • Check: timer gate, signature field, and remaining unchecked items.
  • Fix: wait for timer completion, validate checklist progress, and re-submit.

Symptom: DVIR pending did not clear after submit.

  • Check: whether you submitted the exact required unit/type (Truck vs Trailer, PreTrip vs PostTrip).
  • Fix: run the missing inspection context and verify status again.

Symptom: New DVIR request appeared after midnight while driving.

  • Check: day-change event and pending indicators.
  • Fix: stop safely, complete required inspection(s), then continue operation.

Symptom: Trailer-related requests keep returning after trailer operations.

  • Check: whether both trailer PostTrip (old trailer) and trailer PreTrip (new trailer) were completed in swap flow.
  • Fix: complete missing step in sequence and validate History entries.

Symptom: Warning/unsafe indicator appears even after checklist review.

  • Check: defect marks, notes, and current telemetry risk state.
  • Fix: register accurate item state, apply maintenance when needed, then re-run required inspection.

FAQ

  • Does delivery completion force PostTrip DVIR? No, delivery alone does not force PostTrip in current flow.
  • Why does pending remain after I clicked submit? Usually because the submitted context did not match the required unit/type.
  • What is the fastest safe routine before starting a trip? Run Truck PreTrip first, then Trailer PreTrip if a trailer is attached.
  • Do telemetry warnings automatically fail inspection? No, advisories are guidance; final inspection status is still your explicit record.
  • Where can I confirm exactly what was submitted? Open DVIR History and filter by unit, type, and status for the active session.