IANA DVIR Service Overview

I. DVIR Processing

Although differing approaches exist within the industry with regard to DVIR reporting, IANA has proactively developed a standard infrastructure and system interface to produce and deliver DVIRs. IANA initially completed the development of this system at the request or its railroad constituency; however, the system is available to the industry at large to assist with roadability compliance.

Description of IANA DVIR Processing Services

The base procedures for IANA DVIR processing is as follows:

• IANA will receive the following driver-supplied information collected at in-gate or pre-gate:
• Date/Time of Gate Transaction
• Chassis ID Number
• Motor Carrier SCAC Code
• Driver’s License Number/License State
• Location of Interchange
• Roadability Compliance Defect (RCD) Information; Two digit code assigned to each RCD 01–09, 00 will be utilized to designate no defects

• 01 – Coupling
• 02 – Frame
• 03 – Bolster
• 04 – Fastener
• 05 – Slider
• 06 – Wheel
• 07 – Lights
• 08 – Air Line
• 09 – Brakes
• 00 – No defects

• The information will be transmitted electronically to IANA via 322 transaction set with receipt acknowledged by IANA via 997 document.  (See DVIR Processing Agreement, Attachment A for standard 322 format specifications)

• IANA will assign an unique DVIR number and match the data elements provided against the UIIA, IDD and GIER databases and, if match is made, will populate the following additional fields:

• Motor Carrier U.S. DOT Number
• IEP U.S. DOT Number
• Driver’s Electronic Signature

• The driver’s license number/license state, as affirmed by the DVIR provider at the time of transaction, will be checked against the IDD.  If a match is found on the driver’s license number/license state, a unique eight-digit pin number will be used as the electronic signature. IANA will display both the unique pin number and the driver’s first and last names as shown in the IDD on the IANA generated DVIR form to represent the driver’s electronic signature.

There are three possible scenarios during the matching of the chassis number provided against the GIER database:

1. Equipment is registered in GIER and IEP WILL accept DVIR from IANA — IANA will populate the MC DOT Number, EP DOT Number, and include driver’s first and last names and electronic signature on IANA generated DVIR form and then transmit form to the appropriate IEP.
2. Equipment is registered in GIER, but IEP will NOT accept DVIR directly from IANA — IANA will populate the MC DOT Number, EP DOT Number, and include driver’s first and last names and electronic signature on IANA generated DVIR form and transmit form back to the initiating party via 322 EDI.
3. Equipment NOT registered in GIER — IANA will attempt to match MC SCAC to MC DOT Number and include driver’s electronic signature on the IANA generated DVIR form and transmit partial form back to the initiating party via 322 EDI.

Additional Process Comments:

• If the MC SCAC provided to IANA does not match MC SCAC in UIIA database or MC SCAC does not have associated DOT Number, the provider will receive a partial DVIR from IANA with the MC Company Name included as a data element.
• If driver’s license number/license state provided to IANA does not match information contained in the IDD, IANA will not be able to populate the driver’s full name and electronic signature fields on the IANA-generated DVIR form.

Download DVIR Processing Toolkit

Next: II. DVIR Web Service