WIXLIB

regon Administrative Rule 735-050-0131DMV Form 735-7483C (6-21)ALIRTECHNICALSPECIFICATIONSMANUAL

1 TABLE OF CONTENTSIntroduction to Oregon Automobile Liability Insurance Reporting(ALIR) .223Definitions .34Transaction Processing Specifications .54.15High Level Specifications Overview .5Create a Flat Data File for Input/Upload to ALIR .55.1Data (.Dat) File Format Requirements . 55.1.16789Sections include mandatory header, detail and end of file constant. . 5Data (.DAT) File Specifications . 66.1Header Data . 66.2Header Row Data Element Description and Validation Rules . 66.3Detail Data . 76.4Detail Row(s) Data Element Description and Validation Rules . 86.5Mandatory End of File . 116.6End Of File Data Element Definitions and Validation Rules . 11Data Validation . 127.1File Level Validation . 127.2Record Level Validation. 12ALIR Acknowledgment File . 158.1Acknowledgment (.ack) File Format and Properties . 158.2Acknowledgment (.ack) File Contents . 158.2.1Acknowledgment File Responses . 158.2.2Acknowledgment File: Header Row. 158.2.3Acknowledgment File: Detail Row(s) . 168.2.4Acknowledgment File: End of File Row . 178.2.5Acknowledgment Messages and Error Codes . 17Testing Requirements for New Trading Partners . 181

2 INTRODUCTION TO OREGON AUTOMOBILE LIABILITY INSURANCEREPORTING (ALIR)The ALIR system is Oregon Department of Transportation Driver and Motor VehicleServices’ (DMV’s) platform for receiving Oregon motor vehicle liability insurance information.Oregon Revised Statute (ORS) 742.580 requires Trading Partners to report motor vehicleliability insurance to DMV through DMV’s ALIR system.Trading Partners include organizations partnered with DMV to electronically exchangemotor vehicle liability insurance information with DMV.ORS 806.195 provides DMV authority, by Oregon Administrative Rule (OAR) 735-0500131, to establish the information and the format in which motor vehicle liability insuranceinformation must be reported to DMV.This document includes information regarding file exchange testing requirements and filetechnical specifications.OAR 735-050-0131 includes business requirements and not all business requirements areoutlined within this manual. To ensure a successful exchange of insurance information, review OAR735-050-0131.2

3 DEFINITIONSAcknowledgment Messages and Error Codes: The means by which DMV indicates filetransaction Success or Failure. Failure messages indicate File or Record Level errors in data filesreceived with missing, invalid, or improperly formatted data. See Section 5 and Section 6.ALIR: Automobile Liability Insurance Reporting.Customer ID /Customer ID Jurisdiction: The state, territory or province that issuedthe customer identification number.DTL: Detail Record.Error: Results in the rejection of the record or transaction set.EOF: End of FileFile: Container for detail records.FTP/SFTP: Communication protocol, File Transfer protocol (FTP)/Secure File Transferprotocol (SFTP).Insured: The primary person or organization identified on the insurer records as thenamed holder for the coverage in force as described in ORS 806.080.Insurer: A person or organization engaged in the business of issuing motor vehicleliability insurance coverage designed to meet either the financial or future responsibilityrequirement of ORS Chapter 806.Match: A match occurs when the insurance record corresponds to a vehicle record.MAX LEN: Data elements must not exceed the maximum length (including whitespace).NAIC: The National Association of Insurance Commissioners.NBS: New Business. Processed as New Policy.No Match: A no match occurs when a vehicle record (VIN) cannot be found. These arekept for 90 days while DMV continues to attempt to match the record.Policy: Motor vehicle liability coverage issued by an insurer.Record: A single vehicle policy or one vehicle specific policy. A Detail row.Record Reject: Insufficient or inconclusive insurance information received at DMV,returned to insurance company for corrected information.Sender ID: Seven-digit identification number assigned by DMV.Termination Date: The date a policy or vehicle coverage is canceled, or the datecoverage is no longer valid due to failure to renew policy.3

Third-Party Service Bureau: A third-party organization which sends ALIR data onbehalf of one or more insurance companies.Trading Partner: Trading partners can be insurance companies or third-party servicebureaus which send ALIR data on behalf of one or more insurance companies. Alsoreferred to as a Sender.Transmission ID: Unique value for each file transmission.XLC: Policy cancellation or non-renewal; processed as policy termination.4

4 TRANSACTION P ROCESSING SPECIFICATIONS4.1 High Level Specifications OverviewFile/Record format must comply with the specifications within this manual. Files mustbe sent through Oregon DMV’s FTP servers via SFTP protocol.In response to files, DMV returns Acknowledgment messages and error codes (Section 6.7).Trading Partner system functionality must include the ability to receive Acknowledgmentmessages and error codes.5 CREATE A F LAT DATA F ILE FOR INPUT/UPLOAD TO ALIR5.1Data (.Dat) File Format RequirementsFile Type (extension): .datRequirements of ALIR Data (.dat) filesField (Data Element) Delimiter: ‘pipe’ characterLine Ending: [CR LF] or [LF]Encoding: UTF-8File Name Convention: The file naming convention requires 2 elements, the assignedSender ID and a unique Transmission ID.TP99999 2020012901.datTP99999Trading Partner assigned ID(Sender ID)2020012901Transmission ID - Unique and sequencingto avoid resubmitting the sameTransmission ID twiceEvery file sent must have a uniqueTransmission ID.This example uses the date January 29th, 2020 and the sequence of ‘01’.Using this method, the sequence number (01) can be utilized only once and itcan be increased when multiple files will be uploaded on the same date.5.1.1Sections include mandatory header, detail and end of file constant.5

6 DATA (.DAT) F ILE SPECIFICATIONS6.1 Header DataData ElementType*MAX LENM/O/X **Constants/FormatTransmission TypeA5MOALIRTransmission IDN10MSubmission DateN8MCCYYMMDDSender IDAN20MReceiver IDAN20MOregonDMVTotal RecordsN10M* A Alpha N Numeric AN Alphanumeric**M mandatory O optional X dependent upon the presence of another data element.Data Elements: Must not exceed the Maximum Length (including white-space).6.2 Header Row Data Element Description and Validation RulesData ElementTransmissionTypeDescriptionThis code is for internal useby Oregon DMVRequiredMValidation RulePresence of ‘OALIR’, elseFile Rejected: File LevelError 97Transmission IDUnique ID for transmissionMFile name Transmission IDmust match Header RowTransmission ID, elseFile Rejected: File LevelError 96MBlank date(e.g. 001 or 2018122501)Submission DateThe date the insurancecompany submits thetransaction to DMV.File Rejected: File LevelError 97 File Format.(empty value)File Rejected:Incorrect date format(YYYYDDMM), orSubmission Date greaterthan the actual submissiondate:6

Data ElementDescriptionRequiredValidation RuleFile Level Error 95 (InvalidSubmission Date)Sender IDALIR trading partner’s 7digit Sender IDMSender ID must be presentand correct, else FileRejected: File Level Error97(e.g. TP00001, TP00002,etc.)Receiver IDDMV internal use only.MPresence of ‘OregonDMV’,else File Rejected: FileLevel Error 97Total RecordsTotal number of Detail‘DTL’ rows that are includedin the input .dat file.MPresence of total records,else File Rejected: FileLevel Error 97Header and EOF rowsshould not be included in thisvalue.**M mandatory O optional X dependent upon the presence of another data element.Data Elements: Must not exceed the Maximum Length (including white-space).6.3 Detail DataData ElementType*MAXLENM/O/X **Constants/FormatRecord TypeA3MDTLMessage IDN10MNAIC NumberN20MPolicy TypeA2MTransaction TypeA3MPolicy NumberAN30MEffective DateN8XCCYYMMDDTermination DateN8XCCYYMMDDInsured DOBN8OCCYYMMDDPerson or OrganizationIndicatorN1M7

Insured’s Last orOrganization nameAN36MInsured’s First nameAN20OInsured’s Middle nameAN20OInsured’s customer IDAN20OCustomer ID jurisdictionAN2OInsured’s addressAN36MInsured’s cityAN30MInsured’s stateA2MInsured’s ZIP codeAN5OVehicle IdentificationNumberAN20MVehicle yearN4OVehicle makeAN5OVehicle plateAN7OCCYY* A Alpha N Numeric AN Alphanumeric**M mandatory O optional X dependent upon the presence of another data element.Data Elements: Must not exceed the Maximum Length (including white-space).6.4 Detail Row(s) Data Element Description and Validation RulesData ElementRecord TypeDescriptionDetail record typeM/O/X**MValidation RuleConstant, ‘DTL’, existsMessage IDRow number. Uniquenumber identifying eachrecord.MNumeric value existsNAIC NumberThe NAIC Number is addedto a table in DMV's system.MPresence of valid NAIC8

Data ElementPolicy TypeDescriptionIndicator distinguishes policytypes:VTransactionTypeM/O/X**MValidation RuleA vehicle-specific policymust contain the VIN.MPresence of TransactionType NBS or XLC.Policy number is matched toexisting policy number ifpresent.Vehicle-specificA vehicle-specific policylists individual vehicles.Two acceptable codes:NBS (New Business):Processed as New PolicyXLC (Cancellation):Processed as TerminationPolicy NumberThe motor vehicle or nonowner insurance policynumber.MEffective DateThe policy effective date.MandatoryforTransactionType NBSPresence of properlyformatted Date for allTransaction Types.Date cannot be greater than1 year into the future.If DMV receives atermination date on a newbusiness policy code (NBS)even if the date is zerofilled, DMV will reject therecord.TerminationDatePolicy cancellation or nonrenewal date.The termination date mustinclude all lapses of coverageperiods including graceperiods, etc.Insured DOBDate of birth of the primaryinsured.MandatoryforTransactionType XLCPresence of properlyformatted Date for allTransaction Types.If DMV should receive aneffective date on atermination code 'XLC', theeffective date will beignored and the transactionwill continue to process.OProperly formatted Date9

Data ElementPerson orOrganizationIndicatorDescriptionThe indicator thatdistinguishes an individualperson from an organization.M/O/X**MValidation RuleIf the data element is notpresent, DMV will reject thetransaction.Presence of valid indicators:'1' person'2' organizationInsured LastName orOrganizationNameDepending on the type ofentity, this is the last name ofthe primary insured if theinsured is a person, or thename of an organization.MName data existsInsured FirstNameFirst name of the primaryinsured if the insured is aperson.ON/AON/AThis field is left blank if theinsured is an organization.Insured MiddleNameMiddle name of the primaryinsured if the insured is aperson.This field is left blank if theinsured is an organization.InsuredCustomer IDThe primary insured's driverlicense number,identification card number,permit number, or DMVcustomer number.ON/ACustomer IDJurisdictionThe code for the jurisdictionthat issued the Customer IDNumber to the insured.ON/AInsured AddressAddress of the insured.MAddress data existsInsured CityCity for the address of theinsured.MCity data existsInsured StateState for the address of theinsured.MState data existsInsured ZIPCodeFive-digit ZIP code for theaddress of the insured.ON/A10