Use the Inspection Settings tab in myAvail to configure your electronic DVIR (driver vehicle inspection report) screens. Using an electronic form, rather than paper, saves an agency time, possibly lost or damaged paper sheets, and the system files all results away to reports for maintenance review. Vehicle operators can quickly review already documented DVIR results on the MDT, too, by simply touching the Pretrip button.
Video Demo
ETMS Navigation
Begin by navigating to ETMS, then login in. Open the Operations product suite, then open the Launch Dispatch card, or simply search for 'Launch Dispatch' to open it:
Then open Inspection Settings:
Checks
Use the Checks tab to setup the pass/ fail inspection items for the DVIR. You can include multiple failure reason codes and easily make adjustments when needed.
Add New Check
- Click the delete icon
to remove a check.
- Click the edit icon
to edit a Check.
- Click the add icon
to add a new check.
- Clicking either the edit or add icon displays the following window:
Check Name
- Enter a descriptive name for the area to be checked.
Vehicle Type(s)
- Check the vehicle type(s) that should undergo this type of inspection.
- This list is specific to each Your list might differ from this example.
Failure Reason(s)
- This list presents the possible reasons that an inspection can fail. The operator chooses a reason from this list when a vehicle fails an inspection.
- Click the add icon
to add a new failure reason. You can add up to 20 reason codes here.
- Click the delete icon
to remove a Failure Reason.
MDT Layout
Use the MDT Layout tab to setup the visual appearance of the inspections as they will display on the MDT. You must assign each check on the Checks tab to a page and position to display them on the MDT screens.
- Vehicle type defaults to fixed route service
- Use the dropdown menu to select a different mode/ service type
- Then start entering page and position numbers for all check names
- The page numbers must be sequential
- For example, you cannot assign a check name to page 3 before assigning at least one entry to pages 1 and 2
- The positions on the page do not have to be sequential, nor does the page need to be filled
Body Damage
Use the Body Damage tab to add reason codes for failures. Operators will use these when checking the exterior of the vehicle. The operator will simply touch a quarter panel on vehicle diagrams that display on the MDT, to document damage and type.
- Click the add icon
to add a new body damage reason.
- Click the delete icon
to remove a body damage reason.
- IMPORTANT: Be sure to save your work when done. Press the Save located in the top right corner of the screen:
IMPORTANT: A files deployment must be setup on the Build & Deploy tab to download the DVIR screens to your fleet vehicles, so vehicle operators can begin using them.
HINT: Accessing the Build & Deploy tab is based on permission settings in ETMS (HR product suite).
Deploy Files to Vehicles
To enable the screens to populate on the MDT for vehicle operator use, a deployment of the files is required. Follow the steps below:
- Navigate to Build & Deploy
- Open the Deploy tab
- Leave the default setting at Future Schedule ( always work in the future schedule)
- Update to Current Schedule if needed
- Leave the default setting at Future Schedule ( always work in the future schedule)
- Select Other Files (not Schedule Data)
- Select Pre-Trip Inspections
- Select Vehicles
- The Vehicles button will 'light up' to alert you that the vehicles should be selected to receive the download
- Press it and select all vehicles that should receive the files, including any BIBs or MTSs
- The Vehicles button will 'light up' to alert you that the vehicles should be selected to receive the download
- Effective Date- Set the date for the files to begin downloading to vehicles
- Select Deploy
- The new DVIR files become available when the vehicle is cycled/ logged in to
- In some cases, a vehicle reboot may be needed to populate the DVIR checks on the MDT
- WHY: All files scheduled for use in fleet vehicles are downloaded then stored in the vehicle IVU (in-vehicle unit). A reboot triggers use of the new files
-
When the files are available on the MDT, the vehicle operator will complete the DVIR checks first, then proceed to the three standard pretrip checks (1. ADA announcements, 2. APCs, 3. wheelchair ramp cycling)
Related Articles
Interested in reviewing more information about deploying files to vehicles? Check this article: Using the Build & Deploy Processes
Interested in reviewing related maintenance reporting? Review more information here: Maintenance Live Queue Report