AU2007229413A1 - Quotation data exchange - Google Patents

Description

O1 Title Quotation Data Exchange 0

C)

00 Technical Field This invention concerns the control of an insurance repair process. In one aspect it is a quotation data exchange for the control of an insurance repair process, and in another aspect it is a protocol for the control of an insurance repair process.

Background Art Motor vehicles need to be repaired after they are damaged for example, as a ,i result of traffic accidents, malicious acts or hailstorms. The repair is typically not a simple transaction between the vehicle owner and a repairer, but will often involve a vehicle insurer. The insurer will generally wish to exercise some control over the repair, for instance in selection of the repairer and authorisation of repair items and their cost.

Summary of the Invention In a first aspect, the invention is a quotation data exchange for the control of an insurance repair process, including: A host computer operating to enable communications between an insurer and a repairer where the communications are selected from a set of electronic messages having predetermined content fields in which data is entered, the message set including: A request for quotation in response to a claim, from insurer to repairer in respect of specified damage; A quotation between repairer and insurer for repair of the damage specified in a request for quotation; An assessed quotation that may or may not contain an authority to proceed with the repair; A tax invoice (request for payment) from repairer to insurer in respect of an authorised repair; A payment authority from insurer to repairer in response to a request for payment.

F

2 c The set of messages may also include: A request for an inspection from the repairer to the insurer to cause the insurer to 00 inspect the damage.

Rather than quote, the repairer may send a message declining a repair.

The insurer may send a message to the repairer declining payment.

Other notifications and error messages may also be exchanged.

The host computer may reside at the insurer's premises, and the system will typically involve a communications network, such as the Internet, and remote computers at the repairers. The host and remote computers may have relational databases in which the quotation data is stored. When a message is sent from one party NI to the other, this data is gathered together and used to populate the messages before transmission.

The electronic messages enable a vehicle re-instatement lifecycle to be communicated between the repairer and insurer in a common format. There is no specific processing dependent on a repairer. The messages are sufficiently flexible that they can drive different repair models.

The data requirements may be expressed in a specific implementation of eXtensible Markup Language. This is a self-describing data protocol with syntactical facilities for mandatory fields, field grouping and allowable values. Each message is described in a Document Type Definition (dtd) which describes each element and its attributes plus the tags required to identify the element. For a specific occurrence of a message, each data element value is enclosed in the defined tags.

Where data occurrences belong to limited data reference sets, allowable values may be defined in the dtd. This allows the sending and receiving applications to crossreference to their proprietary reference sets.

The dtd is a de-normalised data definition that contains syntax and nesting of elements such that complex relationships and data categorisation of the target relational database are implied in the message.

It should be noted that although the result has an appearance of being simple because of its flat structure, there may be equivalent intelligence embedded in the message definition to the databases, and their complex relationships, where the messages originate and terminate.

The system aims to streamline current paper and fax-based processes, thus increasing efficiency and accuracy of data transfer. Enforcement of data 3 integrity is achieved by use of an electronic record. Efficiency is achieved through o easier storage of the quotation data for statutory requirements and also electronic 00 records will allow robotic checking for Parts and Hours submissions. The system also offers an opportunity for expansion to support richer and more powerful forms of communication. In particular, more detailed information may be passed between the two parties, allowing better informed decisions to be made. One example of a process enhancement is the support for digital photos. By building an infrastructure for the Scommunication of digital images, sufficient information can be gained by assessors Nwhile reducing the need for on-site visits.

In another aspect the invention is a protocol for the control of an insurance repair ,I process, involving the steps of exchanging electronic communication between an insurer and repairer where the communication is selected from a set of electronic messages having predetermined content fields, the message set including: a request for quotation in response to a claim, from insurer to repairer in respect of specified damage; a quotation between repairer and insurer for repair of the damage specified in a request for quotation; an assessed quotation that may or may not contain an authority from insurer to proceed with the repair; a tax invoice (request for payment) from repairer to insurer in respect of an authorised repair; and a payment authority from insurer to repairer in response to a request for payment.

Brief Description of the Drawings An example of the invention will now be described with reference to the accompanying drawings, in which: Fig. 1 is a schematic diagram showing the architecture of a data quotation exchange.

Fig. 2 is a block diagram of the operation of the exchange.

Fig. 3 is a flowchart of the workflow.

Fig. 4 is all elevations of a vehicle with the sections identified by numbers.

4 _Best Modes of the Invention O The quotation data exchange (QDE) 1 facilitates communications between an C)insurer 2 and a number of repairers 3.

The insurer has a software solution that integrates with its overall claims process, while the repairers are using software packages developed by third-party Cc vendors.

The two parties communicate via the Internet 4, using a protocol, with the CK1 content of the communications encapsulated in messages (Ni This is summarised in Fig. 1.

SQuotation Data Exchange Architecture The exchange consists of the following key components: Messaging architecture Quotation Markup Language (QML) The Messages The system provides an "interface" between the insurer's and repairers' systems.

It allows either party to implement their internal systems to meet their internal business needs, while retaining the confidence that other parties can be communicated with, in a standard way.

Both the insurer and repairer systems store the quotation information in a database. When a message needs to be sent to the other party, this information is gathered together, and used to populate a message for transmission.

When a message is received, another process of conversion will occur, to map the data into the internal database model of the software system.

As can be seen, the messages are only used during the communication of quotation information, and therefore only have to capture the information needed for this process. The storage of quotation information is the responsibility of the systems designers, and can be done using any method that meets the overall functional requirements.

This model of operation can be seen in Fig. 2.

Request for Quote The Request for Quote message is sent from the insurer to the repairer, and contains: 0 Details of the incident such as an accident, vandalism, hail etc.

O

Insurance information such as: sum insured, etc.

*Vehicle details, such as: make, model, and engine number.

0 Customer contact name and address.

00 0 The message also specifies whether: 9 The partnered model should be used for this job.

C0 The assessed model should be used.

0 The request is for comparison quotation purposes only, and no repairs will be conducted by the repairer.

Once a request has been received by the repairer, a quotation is made and is sent to the insurer. Alternatively, the repairer may decline the job.

Job Declined The repairer sends this message to the insurer, indicating that they have declined the job, and provides a reason.

Quote The Quote message is the primary mechanism for communicating details between the two parties, and is used in the following cases: 0 the initial quote.

e an adjustment made by the insurer.

a and a variation made by the repairer.

This message type contains: General details on the repair, including: repair dates, updated incident reports, etc.

Extensive vehicle details, including: make, model, paint colour, options, etc.

9 Global hourly rates for categories of repair, such as: paint, repair, mechanical, etc.

Quote items: providing details on the actual work to be completed.

An indication that the most recent quotation from the repairer has been accepted.

An indication that an assessor will need to make an on-site examination of the vehicle to be repaired with reasons.

For each quote item, there are four status flags used to manage the flow of changes between the insurer and the repairer: added.

changed.

deleted.

acknowledged delete.

The flags are used in the following manner: :6 When a new quote is generated, all the items are marked as 'added'.

O The 'added' flag is also used if a new item is added as part of a variation or 00 adjustment.

SIf an adjustment or variation needs to be made, the quote items details are changed to the new values, and each modified quote item is marked as 'changed'. The updated Quote is then sent to the other party.

e If an item is to be removed from the quote, it is marked as 'deleted'. It is not, CI however, omitted from the Quote message, such that an audit trail is maintained.

Such an item should be shipped as 'acknowledged delete' in subsequent quote messages.

The absence of all 4 flags means the item is unchanged by the recipient. This means that items unchanged by the insurer are implicitly authorised.

Total Loss This message is used by either the repairer or insurer. If used by the repairer it acts as a request which the insurer may accept by returning the message or decline by asking the repairer to submit a quotation.

Job Cancelled This message is sent if the insurer does not wish to proceed with his original request. This may be because of a variety of reasons from the insured wishing to have another repairer allocated to the submission of a totally unacceptable quotation.

Authority Withdrawn The insurer uses this message to notify that the repairer should immediately halt any work on the repair, and not start any new repair work.

Tax Invoice (Payment Request) A payment request message is sent from the repairer to the insurer to indicate that the job has been completed, and to request payment. Additional information needed to manage the GST is also included. Due to the GST, a payment request may be a Tax Invoice, an Adjustment Note or a Re-activate Invoice depending on previous workflow.

7 SPayment Authorised The insurer uses this message to notify that payment has been made, and 00 includes payment details such as invoice number, and actual payment date.

Payment Declined The insurer uses this message to notify the repairer that a requested payment will not be made and provides a reason.

Parts Reference This message is used by the parts reference data supplier and is sent to the cK, insurer to communicate the detailed information on car parts.

Vehicle Reference This message is used by the parts reference data supplier and is sent to the insurer to communicate the detailed information of a car.

Error This message is used by either party to signal any errors encountered in incoming messages. An error message will have 1 of 4 severities: 9 Informational Information for the Repairer.

Warning Warning for the repairer, but Inbound Message still processed.

Critical Critical error for Repairer. Inbound Message not processed. Needs response by quotation application.

System Errors indicating that the system is not working. Eg database is down.

System errors are not sent to the repairer.

An Error message will have 1 of 5 types: DataContent The content of an element is not valid according to the defined business rules.

Miscellaneous An error that does not belong to any of the other types.

Message Order The Inbound Message has an invalid Message Number.

Data Type The content of an element does not match the data type restrictions described in the QDE Data Definitions. Eg. Characters for a numeric element.

Validity The Inbound Message fails to parse correctly against the appropriate

DTD.

Quotation Markup Language (QML) The Quotation Markup Language (QML) defines a specification for all messages O passed between the insurer and repairers. This specification is defined using the 00 eXtensible Markup Language (XML), an open standard for the development of industry-specific data formats.

Use of XML brings with it a number of important benefits: It is an open, vendor-neutral standard.

It is platform-independent.

C Many software vendors are providing support for XML.

It allows complex data to be stored in a simple format.

It is self-documenting: QML can be read and understood directly from the file without needing complex supporting documentation.

Future extensions can be made to the business processes, while minimising the need for systems re-engineering.

Validity can be easily checked, and integrity ensured.

To a large extent, the XML is self-explanatory, when read in conjunction with the following basic design principles: XML consists of tags, which are surrounded by angle brackets. An example of a tag: <QuoteDetails>.

In general, an element consists of a start and end tag. The content of the element is then located between these tags, and can consist of either text, or more elements.

For example: <RegistrationNo>UAA 169</RegistrationNo> or: <Vehicle> <BuildDate>199001 </BuildDate> <KilometresTravelled>25000</KilometresTravelled> </Vehicle> An element may also have attributes, which define additional information about the element. For example: <Transmission Value="Automatic"/>.

The rules that define the names of the elements, and how they can be used are stored in a Document Type Definition (DTD).

The simplest way of explaining a DTD is to work by example: In the DTD, lines such as the following can be found: <!ELEMENT Vehicle (BuildDate, KilometresTravelled, EngineSize)> This defines the element Vehicle, and indicates that it contains BuildDate, followed by KilometresTravelled and EngineSize.

9 In the XML file, this would allow the following to be used: o <Vehicle> <BuildDate> 199001 </BuildDate> <KilometresTravelled>25000</KilometresTravelled> <EngineSize>2.6</EngineSize> S</Vehicle> These lines are also common: C <!ELEMENT BuildDate (#PCDATA)> This is just a complex way of saying the content of the element is text. For example:

C

I <BuildDate> 199912</BuildDate> It is also possible to create more complex rules: <!ELEMENT Model (Make, ModelID, Description?, DateManufactureStart?)> This means that the Model must contain a Make, ModelID, optionally a Description, and optionally a DateManufactureStart.

The question mark is an example of an operator in XML that specifies when an element may appear. The full list: ?=may optionally be used *=may appear 0 or more times +=must appear at least once An XML file must meet the rules defined in its matching DTD. If it does so, it is considered valid, otherwise an error is generated.

The DTDs specify the structure of QML, but they do not detail the meaning of the elements, nor the format of the element content. For example, a DTD can specify that an element only contains text, not that it must contain a five digit number.

This document therefore provides a detailed data definition for QML, along with some brief explanatory information about each element.

Note that: There is one definition for each DTD.

The tag names in the definitions match exactly those defined in the DTDs.

In this example the columns in the data definitions are used as follows: Tag name the name of the element in the DTD Lvl (Level) the hierarchical level at which the element exists. This is used to specify the parent child relationships between fields and which elements are grouped together.

c- Content type "Group" for an element that only contains other elements; "Char" for character data (text); "Flag" for an empty element; "Attr" for a 00 character attribute assigned to another element; "List" for a list of valid values; and "Numeric" for a decimal or floating point number.

For "Char", "Attr", and "List" types, the maximum allowable length of the data is currently restricted to 4000 bytes due to technical limitations. Note: carriage returns are not a valid value in a Gentran message and should be specifically excluded by the parsing software.

In the case of "Numeric", the required format for the data is defined in the description column. This is in the form "zz99.99", where and denotes a single digit. For example, "zz9.99" means that there may be up to three digits, which can be followed by a decimal point and up to two decimal places. The use of"z" indicates that the digit is optional and does not have to be zeropadded. Any decimal places specified in the format description are optional and only need to be included in the data if necessary.

Valid examples.: "999":987;001 ;015 "zz9":987; 1 "zz9.99":2.00,1.7;999.98; Content Length the length defined for an element is the maximum length expected by the recipient. Note that the exchange mechanism will not enforce this limit but delinquency will be an issue in certification testing.

Req (Requirement) the requirement specification for a field. This is defined by a set of codes as follows: M Mandatory. For a Group, must always be present. For an element, if the group the element belongs to is present, the element must be present.

Note: ifa field is marked as mandatory it may not appear if its parent group is marked as optional. In addition, a mandatory field may not be blank or zero unless specifically described as such.

O Optional Element. Does not need to be sent with every message.

SMS Mandatory Select of Element. This requirement is specified for a group of elements, from which there must always be one and only one of the elements specified in the report.

OS Optional Select of Element. This requirement is specified for a group of elements, from which there can either be none or only one of the elements specified in the report.

0' 11 II OL Optional Linked Element. This requirement is specified for an O element that is linked to another element(s) where either both (all) must be 00 specified or none of them can be present.

M+ Mandatory List. This indicates that the element can be specified multiple times but there must always be at least one instance of it in a Smessage.

S0+ Optional List. This indicates that the element can either be specified CN multiple times or not at all.

MS+ Mandatory Select List. This requirement is specified for a group of elements and it indicates that at least one of the elements from the group must be specified but there can be multiple instances of one or more of the elements.

Rep (Repairer) U Update, R Read Only, F Fixed by way of being system generated or derived.

Ins (Insurer) U Update, R Read Only, F Fixed by way of being system generated or derived.

Description a brief description of the element, along with any default values or other implementation notes.

All QML files created must use 7-bit ASCII. That is, no special characters must appear in the documents, beyond alphanumeric characters and punctuation.

If high-order characters are required, they must appear in the form: &#zzz; For example, character number 151 would be written as Furthermore, there are a number of special characters that must not be directly used in XML. Instead, the "escaped" form should be used, as follows: Character Use instead &It; &gt; &amp; &quot; _&apos; Note: these requirements are part of the XML specification, and are not particular to QML.

12 Request for Quote This message is sent by the insurer to the repairer once only. Any information sent that requires updating will be contained in another message.

Tag name LAi Content Data Req Description __yp ~izej QML RequestForQuote 0 Group M DVersion 2 Gup M DTVersion 1 Fgrop M Value 3 Attr 5 M The current version of the DTD.

J____This value is fixed Source 2 Group M ABN 3 Char I11 M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NRMA will use: "NRMA ____Insurance Ltd" AppVersion 3 Char 8 M The version number of the software used to create this message AppName 3 Char 20 M IThe name of the software usedto- ____create this message Destination 2 Group M ABN 3 Char I11 M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation eg Repairer Name TimeStamp 2 Char 14 M The creation date and time of this message, as generated by the system This is of the format: yyyymmdd hh: mm MessageNo I Numeric 3 M TFormat: "zzz" The unique ID for this message. See elsewhere for a discussion of the message number and its uses.

Header I~ Group M RepairerABN 2 Char 1I I RepairerlD 2 Char 8 M The NRMA allocated code for the ______repairer.

IRepairerName 2 1Char 145 1M The full name of the repairer Tag name Lvl Content Data Req Description type Size RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired InsuranceClaimNo 2 Char 15 M The NRMA claim number. This must be sent if known. If not known, an empty tag should be used.

ReinstatementNo 2 Numeric 10 M Format: "zzzzzzzzz9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair. Eg Temporary, Repair, Rectification RequestDate 2 Char 8 M The date on which the request was made.

This is of the format: yyyymmdd ContractText 2 Char M Contractual text required for statutory reasons. This field is not length limited.

RequestType 1 Group M Assessed 2 Flag MS The assessed model is to be used for this job Partnered 2 Flag MS The partnered model is to be used for this job ComparisonOnly 2 Flag MS This quote is for comparison purposes only, no repairs are to be made RequestDetails I Group M IncidentDateTime 2 Char 14 O The date and time when the incident occurred.

This is of the format: yyyymmdd hh:mm IncidentDescription 2 Char A free text description of the incident.

This field is not length limited.

VehicleTowed 2 Flag If the vehicle has been towed, this element is used in the message; otherwise, the element is omitted.

DamagedAreas 2 Group O Contains the list of damaged areas.

DamagedArea 3 Char 2 0+ The NRMA damaged area code. See Appendix 1 for coded values.

Sumlnsured 2 Numeric 10 M Format: "zzzzzz9.99" The sum insured for the vehicle BasicExcess 2 Numeric 10 O Format: "zzzzzz9.99" Mandatory but may be zero. The cost of repairs must exceed the excess to be a valid claim.

This field is set to zero viz not used from Release Esti matedQuote Date 2 Char 8 0 The time booked with the customer for the quoting of the repair.

is of the format: yyyymmdd HireCarindicator 2 Flag 0 The presence of this tag indicates that the customer will require a hire Vehicle 1 Group M BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Enieo2 Char 30 0 VN2 Char 30 0 This information will be sent if _____applicable to the vehicle.

Mae2 Char 20 0 This information will be sent where _____available.

Model 2 Char 20 0 Series 2 Char 20 0 BodyStyle 2 List 20 0 Permissible Values: Sedan4Door, Hatch3 Door, Wagon, Coupe2 Door, Convertible2 Door, 4wd2 Door, 4wd2DoorSoftTop, 4wd4Door, Utility2Door, Utility4Door, Van, e Commercial Customer I Group M Name 2 Char 45 M This is of the form: first name, last HomePhone 2 Char 20 0 BusinessPhone 2 Char 20 0 This information will be sent _____where available.

Fax 2 Char 20 0 MobilePhone 2 Char 20 0 Declined Repair This message is sent by the repairer to the insurer once only and is an end state for the referenced Request for Quote.

Tag name _LviA Content Data Req Description QML Declined Sizeou M Version__ Io Group* f_ DTD)Version .21 Flag M Value 3 Attr 5 M tThe current version of the DTD.

1 if__ jThis value is fixed Source 2 Group M ABN 3 Char I I M The. ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation Repairer Name App Version 3 Char 8 M The version number of the software used to create this AppName 3 Char 20 M The name of the software used to _____create this message Destination 2 Group M ABN 3 Char 11I M The ABN of the destination _____organisation.

OrgName 3 Char 45 M The full name for the destination organisation For NRMA, use "NRMA Insurance TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the stem.

MessageNo 1 uei 3 M Format: "zz9" The unique ID for this message. See elsewhere for a I discussion of the message number it eu e Header JIi Group I IMI RepairerABN J2 Char I11 M Tag name Lvl Content Data Req Description type Size RepairerID 2 Char 8 M The NRMA allocated code for the repairer.

RepairerName 2 Char 45 M The full name of the repairer RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired InsuranceClaimNo 2 Char 15 M The NRMA claim number. This must be sent if known. If not known, an empty tag should be used.

ReinstatementNo 2 Numeric 10 M Format: "zzzzzzzzz9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair.

Eg Temporary, Repair, Rectification QuoteNo 2 Char 10 M Unique ID for quote, allocated by repairer DeclinedDate 2 Char 8 M When the repair was declined.

This is of the format: yyyymmdd Reason 1 Char M The reason for declining the repair.

This field is not length limited.

17 Quote This message may be sent by the repairer to the insurer and vice versa multiple times.

Tag name L I Content TData Req Rep Ins Description type 2 Size QMLQuote 01 Group M Version 1 Mroup__ DTD)Version 2 Flag M F F Value 3 Attr 5 M F F The current version of the DTD. This value is fixed Source 2 Group M ABN 3 Char I11 M F F The ABN of the source _____organisation OrgName 3 Char 45 M F F The full name for the source organisation.

eg. NR-MA will use: "NR-MA _____Insurance Ltd" AppVersion 3 Char 8 M F F The version number of the software used to create this _____message AppName 3 Char 20 M F F The name of the software used to create this message Destination 2 Group M AIBN 3 Char I I M F F The ABN of the destination OrgName 3 Char 45 M F F The full name of the destination organisation. eg.

for NRMA, use "NR-MA Insurance Ltd", for the repairer, the _____Repairer Name TimeStamp Char Format: Tag name Lvi Content Data Req Rep Ins Description Size___ yyyymmdd hh:mm The creation date and time of this message, as generated by the ystM.

MessageNo 1 Numeric 3 M F F Format: "zz9".

The unique ID for this message. See elsewhere for a discussion of the message number its uses Header I Group RepairerABN 2 Char I I M F F RepairerID 2 Char 8 M F F The insurer allocated code for repairer.

RepairerName 2 Char 45 M F F The full name of repairer RegistrationNo 2 Char 9 M U U The registration number of the vehicle to be _____repaired InsuranceClaimNo 2 Char 15 M R F The NRMA claim number. This must be sent if known.

If not known, an empty tag should us ed ReinstatementNo 2 Numeric 10 M R F Format: "4zzzzzzzzz9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair. Eg Temporary, Repair, ication QuoteNo Char Unique ID for quote, allocated by repairer Tag name Lvi Content Data Req Rep Ins Description QuoteDate 2 Char 8 M F R The date on which the quote was made.

This is of the format: yyyymmdd Note: NRMA validates as Ju12000 QuoteStatus I Group M The Status of the quotation at the time of ______transmission.

Quoted 2 Flag MS U R Default setting by the repairer Authorised 2 Flag MS R U Authority is given to enact repairs based on this _____quotation.

AuthorityText 3 Attr M R U Text pertaining to the authority. This field is not length _____limited.

AuthorityWithheld 2 Flag MS R U This quotation has been assessed but authority to proceed is temporarily _____withheld.

WithheldReason 3 Attr M R U The reason for withholding the authority. This field is not length limited.

CashSettlement 2 Flag MS R U This claim will be settled via a cash settlement with the insured. The client may opt to have the vehicle repaired for this assessed quotation _____amount.

[InspectionRequested I Flag 0 U R Optional setting Mby the repairer Inspection Reason j2 Attr U R The reason for Tag name Lvi Content Data Req Rep Ins Description typ Size requesting an inspection. This field is not length limited.

QuoteDetails I Group M UpdatedIncident 2 Char 0 R U To be used by the Report insurer to notify any changes to the incident report.

This field is not limited.

EstimatedStartDate 2 Char 8 M U R These dates are specified in the initial quote, but may be updated in later quote messages.

These are of the format: _____yyyymmdd EstimatedEndDate 2 Char 8 M U R ExcesstoCollect 2 Numeric 10 M R U Format: "1zzzzzZ9.99" Mandatory but may be zero.

This value is set by the insurer may be revised by the insurer at any time prior to payment. It cannot be amended by the repairer.

OwnersContribution 2 Numeric 10 M R U Format: ToCollect "1zzzzzz9.99" Mandatory but may be zero. This value Is set by the assessor and may not be revised by the repairer. It is

GST.

Open ext 2 Char 0 U U Comments by the or Tag name Lvi Content Data Req Rep Ins Description pe Size___ ______assessor QuoterName 2 Char 45 0 U R This is the name of the staff member who conducted the quote at the ______repairer.

Changed 2 Flag 0 U U This flag is used to indicate (by either party) that a change has been made to the QuoteDetails information since last message.

QuoteType I Group Assessed 2 Flag MS R U The assessed model is to be ___used for this job Partnered 2 Flag MS R U The partnered model is to be for this job ComparisonOnly 2 Flag MS R U This quote is for comparison purposes only, no repairs are to be made Vehicle I Group EngineNo 2 Char 30 0 U R VIN 2 Char 30 0 U R This information will be sent if applicable to the vehicle BuildDate 2 Char 8 0 U R This is of the format: yyyn~d Odometer 2 Group 0 OdometerReading 3 Char 7 M U R Format of zzzzzz9' OdometerUnitKm 3 Flag MS U R OdometerUnitMiles 3 Flag MS U R EngineSize 2 Char 4 0 U R This is in units of litres in the formnat of z9.9'.

0 Tag name Lvi Content Data Req Rep Ins Description type. Size NoOfCylinders 2 Char 2 0 U R Should be in the format of V9 or Transmission 2 List 9 0 U R Values: Automatic, _____Manual Colour 2 Char 15 0 U R ManufacturerPaint 2 List 2 M U U Values: SI1, S2, Group Ml1, M2, M3 ManufacturerTrimCode 2 Char 10 0 U R PaintCode 2 Char 10 0 U R OptionCode 2 Char 13 0 U R VehicleLocation 2 List 8 M U R The location of the vehicle at the time the insurer will receive the quote.

Values: 'Repairer', Customer' Model I Grou M Make 2 Char 20 M U R ModeliD 2 Char 20 M U R Series 2 Char 20 0 U R EquipmentLevel 2 Char 20 0 U R BodyStyle 2 List 20 M U R Permissible Values: Sedan4Door, Hatch3 Door, Hatch5 Door, Wagon, Coupe2 Door, Convertible2D oor, 4wd2 Door, 4wd2DoorSoft Top, 4wd4 Door, Utility2Door, Utility4Door, Van, Commercial Description 2 Char 30 0 U R Hourl Rates I Group M 0 Tag name Lvi Content Data Req Rep Ins Description Size Mechanicall-lourlyRate 2 Numeric 6 M U U Format: "zz9.99" May be zero PaintHourlyRate 2 Numeric 6 M U U Format: "zz9.99" RepairHourlyRate 2 Numeric 6 M U U Format: "zz9.99" RemoveReplace Hourly 2 Numeric 6 M U U Format: "zz9.99" Rate___ Defines I Group 0 These are used to include information that is of value to the sender, but is not defined by the DTD. The receiver of the message must echo back any data in these tags unchanged.

See elsewhere for a discussion of how this system may be used to implement cycle numbers, for _____example.

Define 2 Char 40 M+ U U Name 3 Attr 100 M U U Quoteltems 1 Group 0 Quoteltem 2 Group ItemNo 3 Numeric 4 M F R Format: "zzz9" A sequentially generated unique ID for the quote item.

Code 3 Char 9 0 U R A generic description code for the item. A full list of valid codes will be specified in a future release of this Ification.

Description 3 Char 40 M U R A full =description the item.

Tag name LAi Content Data Req Rep Ins Description ype Size Sublet 3 Flag OL U R This flag is used to indicate that the repairer has sublet this item. If specified, SubletABN must be specified.

SubletABN 3 Char I11 OL U R The ABN of the business to whom the work has been sublet. Required if the quote item has sublet.

QuoteltemValue 3 Numeric 10 M U U Format: "1zzzzzz9.99" Mandatory but may be zero This is a calculated value, determined as follows: Quoteftem Value (Hours DefaultHourlyRat e) or (Hours* HourlyRate) or (PaintValue) or (Quantity PartValue) or (Quantity Sundry Value) or (Quantity MiscellaneousVal RemoveReplace 3 Group MS Hours 4 Numeric 6 M U U Format: "zz9.99" Mandatory but may be zero eg Report Item HourlyRate Numeric Format: "zz9.99" If specified, overrides the RemoveReplaceH ourly- Rate in the HourlyRates group.

Tag name iLvil Content [Data [Req ]Rep] Ins 1Description ]typ Size J II Repair 3 Group Hours 4 Numeric 6 M U U Format: "zz9.99" Mandatory but may be zero eg _____Report Item HourlyRate 4 Numeric 6 0 U U Format: "zz9.99" If specified, overrides the RepairHourlyRate in the HourlyRates group.

PaintLabour 3 Group MIS Hours 4 Numeric 6 M U U Format: "zz9.99" Mandatory but may be zero eg ___Report Item HourlyRate 4 Numeric 6 OL U U Format: "zz9.99" If specified, overrides the PaintLabourHourl yRate in the HourlyRates group.

If used then OtherPaintGroup is mandatory, OtherPaintGroup 4 List 2 OL U U Values: SI, S2, Ml1, M2, M3 If this tag is used then the HourlyRate tag is _______mandatory.

PaintMaterials 3 Group NI__ S PaintValue 4 Numeric 10 M U U Format: "1zZzzzz9.99" Paint material costs specified as value.

Part 3 Group NI__ S PartValue 4 Numeric 10 M U U Format: "6zzzzzz9.99" Mandatory but may be zero eg Report Item Unit Price for this _____quote item.

Tag name Lvi Content Data Req Rep Ins Description tpe Size PartQuantity 4 Numeric 3 M U U Format: "zz9" PartOrientation 4 List 5 M U R Values: Left, Right, Other PartSource 4 Group M Aftermarket 5 Flag NI S U U Exchange 5 Flag NI S U U Used 5 Flag NI S U U OEM 5 Flag NI S U U PartNumber 6 Attr M U U Miscellaneous 3 Group MS Quantity 4 Numeric 3 M U U Format: "zz9" MiscellaneousValue 4 Numeric 10 M U U Format: "4zzzzzz9.99" Mandatory but may be zero eg Report Item Sundry 3 Group NI__ S U Quantity 4 Numeric 3 M U U Format: "zz9" Sundry Value 4 Numeric 10 M U U Format: "izzzzzz9.99" Mandatory but may be zero eg -I Report Item Mechanical 3 Group NI__ Hours 4 Numeric 6 M U U Format: "zz9.99" Mandatory but may be zero eg ____Report Item HourlyRate 4 Numeric 6 0 U U Format: "zz9.99" If specified, overrides the Mechanical Hourly Rate in the HourlyRates Comment 3 Char 100 0 U U An option comment, providing more information about item.

Added 3 Flag OS U U This flag indicates that this item detail has been added in this _____message.

Tag name Lvl Content Data Req Rep Ins Description type Size Changed 3 Flag OS U U This flag indicates that the item details have been changed since the last message. This includes if the ReportOn has been changed.

Deleted 3 Flag OS U U The item detail has been deleted by either the Repairer or Assessor.

AcknowlegedDelete 3 Flag OS U U The item detail has been deleted acknowledged and requires no more action. The item is present for information completeness only.

This setting is required on subsequent cycles of deleted items.

ReportOn 3 Flag U U This tag indicates that the validity of this item in the quote is an outstanding issue.

Defines 3 Group O These are used to include information that is of value to the sender, but is not defined by the DTD. The receiver of the message must echo back any data in these tags unchanged.

See elsewhere for a discussion of how this system may be used to implement cycle numbers, for example.

Define Char Tag name Lvi Content Data Req Rep Ins Description yp Size Name 5 Attr 100 M U U Totals I Group M GrandTotalExGST 2 Numeric 10 M F F Format: ZZZZZZ9.99" A calculated value consisting of the sum of all the ____QuoteltemValues.

GSTRate 2 Numeric 6 M F F Format: "z9.99" Set by the ______repairers system GSTAmount 2 Numeric 10 M F F Format: "izzzzzz9.99" Calculated as GrandTotalExGST *GSTRate.

Assessment I Group 0 AssessmentDate 2 Char 8 M R F AssessorName 2 Char 45 M R F This is of the form: first name, name.

AssessorPhone 2 Char 20 M R F AssessorMobile 2 Char 20 0 R F This information will be sent where _____available.

AssessorFax 2 Char 120 10 j R F AssessorEmail 2 Char 40 0 1R F Attachments 1 Group 0 Details of all supporting files (such as images) that have been sent by the repairer to insurer.

ImageCount 2 Char 3 M F R Format: "zz9" The count of the number of images sent with the message. May be zero.

29 Authority Withdrawn This message is sent by the insurer to the repairer and may occur at any time when the quotation has already been authorised.

Version I Grou M DTD Version 2 Flag M Value 3 Attr 5 M The current version of the DTD.

value is fixed Source 2 Group M ABN 3 Char I I M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NR-MA will use: "NRMA ______Insurance Ltd" AppVersion 3 Char 8 M The version number of the software to create this message AppName 3 Char 20 M The name of the software usedt _____create this message f Destination 2 Group M ABN 3 Char I1I M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation Repairer Name TimeStamp 2 Char 14 M Format: yyyymmdd hh:m The creation date and time of this message, as generated by the ______system.

MessageNo I Numeric 3 M Format: "zz9" The unique ID for this message.

See elsewhere for a discussion of message number and its uses Header I Group M RepairerABN 2 Char 11I M RepaireriD 2 Char 8 M The NR-MA allocated code for the Tag name Lvi Content Data Req Description Size repairer.

RepairerNamne 2 Char 45 M The full name of the repairer QuoteNo 2 Char 10 M Unique ID for quote, allocated by I repairer Reason I Char- M The reason for the authority withdrawal, in words. Not length limited.

Job Cancelled This message is sent by the insurer to the repairer and is an end state. Note that it may be sent prior to the receipt of a quotation.

Tag name LvI Content JData TReq Description j Size j__ QML JobCancelled 0 Group j ~M Version 1 Group M Value 3 Attr 5 M The current version of the DTD.

value is fixed Source 2 Group M ABN 3 Char I11 M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NRMA will use: "NR-MA _____Insurance Ltd" AppVersion 3 Char 8 M The version number of the software used to create this message AppName 3 Char 20 M K4 The name of the software used to this message Destination 2 Group M ABN 3 Char I I M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation g. Repairer Name TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the system.

MessageNo Il Numeric 3 M Format: "zz9" II The unique ID for this message.

elsewhere for a discussion of message number and its uses [Header ~I Group M [RepairerABN 121 Char 11 M RepairerID 12 Char 8 M The NR-MA allocated code for the I 11 __repairer.

Tag name Lvi Content Data Req Description tpe Size RepairerName 2 Char 45 M The full name of the repairer RegistrationNo 2 Char 9 M The registration number of the _____vehicle InsuranceClaimNo 2 Char 15 M The NRMA claim number.

This must be sent if known. If not known, an empty tag should be ReinstatementNo 2 Numeric 10 M Format: "zzzzzzzzz9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair.

Eg Temporary, Repair, ________Rectification QuoteNo 2 Char 10 0 Unique ID for quote, allocated by repairer Reason 1 Char M The reason for the job cancellation, in words. Not length limited.

33 Total Loss This message may be sent by the repairer to the insurer and vice versa. It may occur prior to or subsequent to a quotation.

Tag name Lvi Content 1Data Req Description Si*__ QML TotalL-oss 0 Group M Version I Group M DTDVersion 2 Flag M Value 3 Attr 5 M The current versi'on of the DTD.

value is fixed Source 2 Group M ABN 3 Char I I M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NRMA will use: "NRMA Ltd" App Version 3 Char 8 M The version number of the software used to create this _______message AppName 3 Char 20 M The name of the software used to this message Destination 2 Group M AkBN 3 Char I I M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation g. Repairer Name TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the ______system.

Messae~o 'T Nmeri 3 M The unique ID for this message. elsewhere for a discussion of message number and its uses Header I1 I Group I M RepairerABN 121 Char 11 1M I Tag name Lvi Content Data Req Description Size RepaireriD 2 Char 8 M The NRMA allocated code for the RepairerName 2 Char 45 M The full name of the repairer RegistrationNo 2 Char 9 M The registration number of the to be repaired InsuranceClaimNo 2 Char 15 M The NR-MA claim number. This must be sent if known. If not known, an empty tag should be used ReinstatementNo 2 Numeric 10 M Format: "zzzzzzzZZ9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair.

Eg Temporary, Repair, ______Rectification QuoteNo 2 Char 10 M [Unique ID for quote, allocated by I repairer Attachments I Group 0 Details of all supporting files (such as images) that have been sent by repairer to the insurer.

ImageCount 2 Char 3 M Format: "zz9" The count of the number of images sent with the message. May be zero.

Tax Invoice (Payment request) This message is sent by the repairer to the insurer to request payment on the authorised quotation.

Tag name Lvi Content Data Req Description type Size QMLTaxInvoice 0 Group Version I Group M DTDVersion 2 Flag M Value 3 Attr 5 M The current version of the DTD.

value is fixed Source 2 Group M ABN 3 Char I11 M The ABN of the source _____organisation OrgName 3 Char 45 M The full name of the source _____organisation.

AppVersion 3 Char 8 M The version number of the software used to create this ______message AppName 3 Char 20 M The name of the software used to ______create this message Destination 2 Group M ABN 3 Char I11 M The ABN of the destination ______organisation.

OrgName 3 Char 45 M The full name for the destination organisation For NRMA, use "NR-MA _____Insurance Ltd" TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the MessageNo I Numeric 3 M Fnnt z9 I The unique ID for this message.

I See elsewhere for a discussion of the message number and its uses Header I Group M TaxInvoice 2 Flag M To satisfy the statutory literal _____requirement Repairer-ABN 2 Char I I M Repairer's Australian Business umber RepairerlD 2 Char 8 M The NRMA allocated code for the- Tag namne Lvi Content Data Req Description ype ______repairer.

RepairerName 2 Char 45 M The full name of the repairer InsurerABN 2 Char I11 M Insurer's Australian Business _______Number InsurerName 2 Char 45 M The full name of the insurer QuoteNo 2 Char 10 M Unique ID for quote, allocated by RepairerTaxInvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, allocated by repairer PaymentDetails I Group M CompletionDate 2 Char 8 M When the repair was completed.

is of the format: yyyymmdd InvoiceDate 2 Char 8 M The date of this invoice.

is of the format: yyyymmdd Total ExcludingGST 2 Numeric 10 M Format: "zzzzzz9.99" TotalGSTAmount 2 Numeric 10 M Format: "zzzzzz9.99" Total IncludingGST 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Format: "zzzzzz9.99" Owners~~~ontribMandator 2u Numri 10 Mzoratro.zz9.

Value expected to be as per authorised quote.

______Inclusive of GST.

TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" Description 2 Char 100 M A description of the services.

Eg.'Repairs to vehicle agreed as quote on above claim' GSTRate 2 Numeric 6 M IFormat: "zz9.99" 0\ 37 Adjustment Note This message is sent by the repairer to the insurer to adjust a previously submitted Tax Invoice. This message is an increment or decrement to what has been sent previously. It contains a full version of the quotation with only the summary or those items that are added changed deleted since the tax invoice flagged.

Tag name Lvl Content Data Req Description type Size QML AdjustmentNote 0 Group M Version 1 Group M DTDVersion 2 Flag M Value 3 Attr 5 M The current version of the DTD.

This value is fixed Source 2 Group M ABN 3 Char 11 M The ABN of the source organisation OrgName 3 Char 45 M The full name for the source organisation NRMA will use: "NRMA Insurance Ltd" AppVersion 3 Char 8 M The version number of the software used to create this message AppName 3 Char 20 M The name of the software used to create this message Destination 2 Group M ABN 3 Char 11 M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation For NRMA, use "NRMA Insurance Ltd" TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the system.

MessageNo 1 Numeric 3 M Format: "zz9" The unique ID for this message.

See elsewhere for a discussion of the message number and its uses 1~ Tag name Lvi Content Data Req Description typ Size Header I Group M AdjustmentNote 2 Flag M To satisfy the statutory literal requirement RepairerABN 2 Char 11 M Repairer's Australian Business Number RepaireriD 2 Char 8 M The NR-MA allocated code for the repairer.

RepairerName 2 Char 45 M The full name of the repairer lnsurerABN 2 Char 11I M Insurer's Australian Business InsurerName 2 Char 45 1M The full name of the insurer QuoteNo 2 Char 10 M Unique ID for quote, allocated by _____repairer RepairerTaxInvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, by repairer PaymentDetails I Group M AdjustmentNoteDate 2 Char 8 M Format: yyyymmdd date of this adjustment note.

TaxinvoiceDate 2 Char 8 M Format: yyyymmdd The date of the original tax _____invoice.

SupplyDifferenceAmount 2 Numeric 10 M Format: "zzzzzz9.99" Mandatory but may be zero.

This field is a statutory value containing the difference in the taxable amount. It could be zero if the adjustment is in the _____ExcessToCollect StatutoryStatement 2 Char M eg 'The difference in the taxable suply ncldes GST' Total ExcludingGST 2 Numeric 10 M Format: "zzzzzz9.99" TotalGSTAmount 2 Numeric 10 M Format: "zzzzzz9.99" Total IncludingGST 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Formnat: "zzzzzz9.99" Mandatory but may be zero.

Value expected to be as per _____authorised quote.

OwnersContributionTo 2 Numeric 10 M Format: "zzzzzz9.99" Collect Mandatory but may be zero.

Value expected to be as per _____authorised quote.

Total Payab IeAmount 2 Numeric 10 M Format: "zzzzzz9.99" GSTRate 2 Numeric 6 M Format: "zz9.99" Re-Activate Invoice This message is sent by the repairer to the insurer to re-activate a previously submitted Tax Invoice. This implies that the amounts requested are as originally submitted and some variation has been made to the quotation to make the payment requested balance with the authorised quotation.

Tag name LvI Content Data Req Description ~Si*_ QML ReActivateInvoice 0 Group M Version 1 Group M DTDVersion 2 Fa M Value I3 Attr 5 M The current version of the DTD.

This value is fixed Source 2 Group M ABN 3 Char I11 M The ABN of the source _____organisation OrgName 3 Char 45 M The full name for the source organisation NRMA will use: "NRMA _________Insurance Ltd" App Version 3 Char 8 M The version number of the software used to create this AppName 3 Char 20 M The name of the software used to this message Destination 2 Group M ABN 3 Char I11 M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation For NRMA, use "NRMA ____Insurance Ltd" TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the system.

[MessageNo 1 Numeric 3 [M Format: "zz9" [Header I [Group M RepairerABN 2 Char I I M Repairer's Australian Business I ____Number Tag name Lvi Content Data Req Description type Size RepairerID 2 Char 8 M The NRMA allocated code for repairer.

RepairerName 2 Char 45 M The full name of the repairer InsurerABN 2 Char I1I M Insurer's Australian Business _______Number InsurerName 2 Char 45 1M The full name of the insurer QuoteNo 2 Char 10 M Unique ID for quote, allocated repairer RepairerTaxinvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, by repairer PaymentDetails I Group M ReActi vate Invoice Date 2 Char 8 M Format: yyyymrnmdd date of this ReActivation.

TaxInvoiceDate 2 Char 8 M Format: yyyym-mdd The date of the original tax voice.

Total ExcludingGST 2 Numeric 10 M Format: "zzzzzz9.99" TotalGSTAmount 2 Numeric 10 M Format: "zzzzzz9.99" Total Includi ngG ST 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Format: "zzzzzz9.99" Mandatory but may be zero.

Value expected to be as per ____authorised quote.

OwnersContributionTo 2 Numeric 10 M Format: "zzzzzz9.99" Collect Mandatory but may be zero.

Value expected to be as per ____authorised quote.

Total PayableAmnount 2 Numeric 10 M Format: "zzzzzz9.99" GSTRate 2 Numeric 6 M Format: "zz9.99" Payment Authorised This message is sent by the insurer to the repairer once only and serves to confirm that payment will be made as requested.

Source 2 Group M ABN 3 Char 1I M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NRMA will use: "NRMA Insurance Ltd" AppVersion 3 Char 8 M The version number of the software used to create this message AppName 3 Char 20 M The name of the software used to create this message Destination 2 Group M ABN 3 Char 11 M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation eg. Repairer Name TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the system.

MessageNo 1 Numeric 3 M Format: "zz9" The unique ID for this message.

See elsewhere for a discussion of the message number and its uses Header 1 Group M 0 Tag name Lvi Content Data Req Description type Size RepairerABN 2 Char I I M RepairerID 2 Char 8 M The NRMA allocated code for the repairer.

RepairerName 2 Char 45 M The full name of the repairer QuoteNo 2 Char 10 M Unique ID for quote, allocated repairer 0 43 Payment Declined This message is sent by the insurer to the repairer and serves to inform him that the requested payment will not be made for the given reason.

Tag name Lvi Content Data Req Description QMLPaymentDeclined 1 Grou Siz M Version 1 Group M DTD Version 2 Flag M Value I3 Attr 5 M The current version of the DTD.

value is fixed Source 2 Group M ABN 3 Char I1I M The ABN of the source organisation.

OrgName 3 Char 45 M The fuill name for the source organisation eg. NR-MA will use: "NR-MA _________Insurance Ltd" App Version 3 Char 8 M The version number of the software used to create this ____message AppName 3 Char 20 M The name of the software used to this message Destination 2 Group M ABN 3 Char I I M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation Repairer Name TimeStamp 2 Char 14 M Format: yyyymmdd hh:mm The creation date and time of this message, as generated by the system.

MessageNo JI Numeric 3 [M {Format: "zz9" The_ unique ID for this message.

Header 1 Group M RepairerABN 2 Char I I M RepairerlD 2 Char 8 M The NRMA allocated code for the repairer.

RepairerName 12 1Char 1 45 1- M IThe full name of the repairer LastlnvoiceDetails I Group M InvoiceDate 2 Char 8 M Format: yyyymmdd The date of the invoice or _____adjustment being rejected.

Total ExcludingGST 2 1Numeric 10 M Format: "zzzzzz9.99" TotalGSTAmount 2 Numeric 10 M Format: "zzzzzz9.99" Total IncludingGST 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Format: "zzzzzz9.99" Mandatory but may be zero.

Value expected to be as per _____authorised quote.

OwnersContributionTo 2 Numeric 10 M Format: "zzzzzz9.99" Collect Mandatory but may be zero.

Value expected to be as per authorised quote.

TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" GSTRate 2 Numeric 6 M Format: "zz9.99" ExpectedPaymentDetails I Group M Total ExcludingGST 2 Numeric 10 M Format: "zzzzzz9.99" TotalGSTAmount 2 Numeric 10 M Format: "zzzzzz9.99" Total IncludingG ST 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Format: "zzzzzz9.99" OwnersContributionTo 2 Numeric 10 M Format: "zzzzzz9.99" Total PayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" GSTRate 2 Numeric 16 M Format: "zz9.99" Reason 2 Ca M The reason the payment was _____declined.

Parts Reference This message is sent by the Parts Reference data supplier to the insurer.TanmeC tnt Da Rq Dscpio L type Size PML PartsReference 0 Group M Version I Group M DTD Version 12 [Flag M I Value 3 Attr 5 M The current version of the DTD.

____This value is fixed Source 2 Group M ABN 3 Char I11 M The ABN of the source organ isation.

OrgName 3 Char 45 M The full name for the source _______organisation AppVersion 3 Char 8 M The version number of the software used to create this _____message AppName 3 Char 20 M The name of the software used to this message Destination 2 Group M ABN 3 Char 11I M The ABN of the destination _____organisation.

OrgName 3 Char 45 M The full name for the destination _____organisation TimeStamp 2 Char 14 M The creation date and time of this message, as generated by the system This is of the format: yyyymmdd :mm MessageNo I Numeric 3 M Format: "zzz" The unique ID for this message.

See elsewhere for a discussion of message number and its uses.

Part I Group M PartNumber 2 Char 45 M The manufacturers Part Number PartSeq 2 Numeric 0 Format zz9 Delimiter to enable the recognition of duplicate use of Part Number by manufacturers.

Tag name Lvi Content Data Req Description type Size DateEffective 2 Date PartDetail 1 Group M PartSource 2 1Group M Aftermarket 3 Flag NI S Exchange 3 Flag MS Used 3 Flag MS OEM 3 Flag MS SupercedingPart 2 Char 45 0 Number SupercedingPartSeq 2 Numeric 0 Format zz9 Delimiter to enable the recognition of duplicate use of Part Number by manufacturers.

Description 2 Char 1000 RawPartNumber 2 Char 45 0 Part number as received from the manufacturer including display characters Wb. Absence of this tag implies same as Part Number.

PartPrices 1 Group M PartPrice 2 Group M+ AreaCode 3 Char 20 M Geographical Area. Code list to be _____specified Make 3 Char 20 M ListPrice 3 Numeric M Format zzzzzzzz9.99 TaxRate 3 Numeric 0 Format zzzzzzzz9.99 47 Vehicle Reference This message is sent by the Parts Reference data supplier to the insurer.

Tag name 1Lvi Content Data Req Description __yp p Size* PML VehicleReference 0 Group M Version 1 Irou_ DTD Version 12 Flag M Value 3 Attr 5 M The current version of the DTD.

I This value is fixed Source 2 Group M ABN 3 Char I I M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation App Version 3 Char 8 M The version number of the software used to create this essage AppName 3 Char 20 M The name of the software used to this message Destination 2 Group M ABN 3 Char I11 M The ABN of the destination _____organisation.

OrgName 3 Char 45 M The full name for the destination _____organisation TimeStamp 2 Char 14 M The creation date and time of this message, as generated by the system This is of the format: yyyymmdd hh:mni MessageNo I Numeric 3 M Format: "zzz" The unique ID for this message.

See elsewhere for a discussion of message number and its uses.

Vehicle I Group M AreaCode 2 Char 20 M Geographical Area. Code list to be specified Make 2 Char 20 M Tag name Lvi Content Data Req Description Size Model 2 Char 20 M Series 2 Char 20 M EquipmentLevel 2 Char 20 M Bodystyle 2 List 20 M Permissible Values: Sedan4 Door, Hatch3 Door, Wagon, Coupe2Door, Convertibl e2 Door, 4wd2Door, 4wd2DoorSoftTop, 4wd4Door, Utility2Door, Utility4Door, Van, Commercial VehicleDetails I Group 0 EngineSize 2 Char 2 0 Engine capacity in litres No~fCylinders 2 Char 4 0 Number of cylinders of engine ManStart 2 Date 0 Manufacture Start Date ManEnd 2 Date 0 Manufacture End Date Parts I Group 0 Part 2 Group M PartNumber 2 Char 45 M The manufacturers Part Number PartSeq 2 Numeric 0 Format zz9 Delimiter to enable the recognition of duplicate use of Part Number by _____different manufacturers.

DateEffective 2 Date

C.)

O

O0 49 Error This message is sent by the insurer to the repairer for the purpose of reporting an error with a previous message. There may be multiple error messages generated for the same original message. Upon receiving one of these error messages, the repairer's system should report the error to the user and if the message has a severity of "Critical" then it should update their system to reflect that the insurer has not accepted their original message.

Tag name Lvl Content Data Req Description type Size QML Error 0 Group M Version 1 Group M DTDVersion 2 Flag M Value 3 Attr 5 M The current version of the DTD.

This value is fixed Source 2 Group M ABN 3 Char 11 M The ABN of the source organisation.

OrgName 3 Char 45 M The full name for the source organisation eg. NRMA will use: "NRMA Insurance Ltd" AppVersion 3 Char 8 M The version number of the software used to create this message AppName 3 Char 20 M The name of the software used to create this message Destination 2 Group M ABN 3 Char 11 M The ABN of the destination organisation.

OrgName 3 Char 45 M The full name for the destination organisation eg. Repairer Name TimeStamp 2 Char 14 M The creation date and time of this message, as generated by the system This is of the format: yyyymmdd hh:mm Tag name Lvl Content Data Req Description type Size Header 1 Group M RepairerABN 2 Char 11 M RepairerID 2 Char 8 M The NRMA allocated code for the repairer.

RepairerName 2 Char 45 O The full name of the repairer RegistrationNo 2 Char 9 O The registration number of the vehicle to be repaired InsuranceClaimNo 2 Char 15 O The NRMA claim number. This must be sent if known. If not known, an empty tag should be used ReinstatementNo 2 Numeric 10 O Format: "zzzzzzzzz9" Identifier of a vehicle repair in the context that a given claim may give rise to multiple sets of repair. Eg Temporary, Repair, Rectification QuoteNo 2 Char 10 O Unique ID for quote, allocated by repairer RelatesToMessageNo 2 Numeric 3 O Format: "zz9" The message which caused the errors ErrorDetails I Group M Contains the errors encountered, with one entry per error Severity 2 List 20 M Values: Informational, Warning, Severe Informational Message accepted but there may be some minor issues.

Warning Message accepted but some none critical details were in error.

Critical Message rejected. The error must be corrected and the message resent with a new message number.

ValidityError 2 Group MS The message fails to parse correctly against the appropriate DTD (ie the message is not a valid XML file) Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved LineNo 3 Char 5 M The line that the error was ________reported on by the XML parser.

ColumnNo 3 Char 5 M The column that the error was ________reported on by the XML parser.

DataTypeError 2 Group MS The contents of an element does not match the data type restrictions described in this document (ie chars instead of numeric, etc) Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ElementName 3 Char 100 M The name of the element where the problem occurred Value 3 Char 4000 M The contents of the element that was in error.

DataContentError 2 Group MS The contents of an element are not meaningful according to the defined business rules.

Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ElementName 3 Char 100 M The name of the element where the problem occurred Value 3 Char 4000 M The contents of the element that was in error.

MessageOrderError 2 Group MS The received message has an invalid message number (out of order) Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ExpectedMessageNo 3 Numeric 3 M Format: "zz9" The message number that was expected to be received ReceivedMessageNo 3 Numeric 3 M Format: "zz9" The actual message number of the received message MessageTypeError 2 Group MS The message type cannot be used at this point in the conversation (eg. Payment request before initial quote, etc) Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved DTDVersionError 2 Group MS The message does not match the current DTD version.

Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ReceivedVersion 3 Numeric 5 M Format: "z9.99" The version of the DTD which was received MiscellaneousError 2 Group MS An general error that does not belong to any of the other types.

Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved Glossary Term Definition Damaged Area Coded part of vehicle that is damaged as specified by the claimant Impact Area Coded part of vehicle that is damaged as specified by the assessor.

Usually accompanied by a level of severity.

Markup An insurer allowed percentage the repairer adds to the value of materials for storage handling (and pre GST, WST) OEM Original Equipment Manufacturer QDE Quotation Data Exchange QML Quotation Markup Language QSV Quotation Software Vendor Re-instatement Generic term used to signify settlement of a claim, including Repair, Total Loss Cash Settlement.

Report On Items of the repair on which some issue exists that could not be resolved at the time of compilation or assessment of the quote message.

VCP Virtual Claims Pocket 54 Workflow

C=)

Referring to Fig. 3 the workflow can be seen to begin after a vehicle has been 00 damaged and when the claim 31 is lodged. A repairer is allocated 32 and a request for quote 33 is sent to the repairer 34. The repairer has a number of choices. First the repairer may decline the job 35. Second the repairer may quote 36 to repair the vehicle.

In this case an on-site inspection may be requested 37 and this on-site inspection may subsequently take place 38. A quotation assessment 39 then takes place.

IC Alternatively the repairer may request total loss 40. This may be refused 41 and the request for quote 33 may then be repeated. If it is accepted 42 then a total loss advice 43 is made.

NK, The quotation assessment 39 will result in either: the return of a Quote message 44 with possible adjustments, the settlement method (Repair or Cash Settlement) 59 and optional authority to proceed with the repair or; a total loss message 43.

The quote authority will then enable the repairer to perform the repairs During the repair additional repairs may become evident, in which case a variation quote 46 may be prepared and assessed 47 before authority is granted 48 for the additional repairs to take place. After the repairs have taken place, or after the total loss advice has been made, the repairer generates a tax invoice (payment request) 49 which is received by the insurer and assessed for payment 50. Payment may be authorised 51 and made to the repairer 52.

Alternatively payment may be declined 53 in which case the repairer has three options. The first a variation quote 54 which is assessed at 55 and a quote authority given at 56. An adjustment note may be generated at 57 or an invoice may be reactivated at 58 in which case the process continues at the payment assessment A Job Cancelled message may be initiated by the assessor at any time and has been omitted from the graphic to aid clarity of the remaining flow.

Authority may be withdrawn at any time between authority being given and the completion of repairs.

It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the invention as shown in the specific embodiments without departing from the spirit or scope of the invention as 0 broadly described. The present embodiments are, therefore, to be considered in all 00 respects as illustrative and not restrictive.

Claims (33)

1. 2. A quotation data exchange according to claim 1, wherein the quotation contains a request for an inspection from repairer to insurer to cause the insurer to inspect the damage.
2. 3. A quotation data exchange according to claim 1 or 2, wherein the assessed quotation contains settlement information in respect of the specified repair.
3. 4. A quotation data exchange according to claim 1, 2 or 3, wherein the message set includes a total loss request by either the insurer or repairer, which is subsequently rejected or accepted by the insurer.
4. 5. A quotation data exchange according to any of claims 1 to 4, wherein the message set includes a further tax invoice (payment request) in the form of an adjustment note or a re-activate invoice based on a previously communicated tax invoice. 57
5. 6. A quotation data exchange according to any of claims 1 to 5 wherein the message set includes an authority withdrawn message from insurer to repairer at any O 00 time after an assessed quotation has been made containing an authority. 00
6. 7. A quotation data exchange according to any of claims 1 to 6, wherein the message set includes a cancel job message from insurer to repairer at any time after a request for quotation has been received by the repairer.
7. 8. A quotation data exchange according to any of claims 1 to 7, wherein the message set includes a decline payment message from insurer to repairer upon receipt ,I of any tax invoice (request for payment).
8. 9. A quotation data exchange according to any of claims 1 to 8, wherein the message set includes a decline job message from the repairer upon receipt of a request for quotation, and once included into the message set, prevents the communication of further messages in relation to the specified damage. A quotation data exchange according to any of claims 1 to 9, wherein the message set includes a Parts Reference message from a part reference data supplier to insurer to communicate car part information.
9. 11. A quotation data exchange according to any of claims 1 to 10, wherein the message set includes a Vehicle Reference message from a parts reference data supplier to insurer to communicate car information.
10. 12. A quotation data exchange according to any of claims 1 to 11, wherein the message set includes an error message from either the insurer or repairer on the receipt of any message containing invalid fields or is received in an invalid sequence.
11. 13. A quotation data exchange according to claim 1, wherein the host computer resides at the insurer's premises, and the system will typically involve a communications network, such as the Internet, and remote computers that reside at the multiple repairer's premises. 58
12. 14. A quotation data exchange according to claim 13, wherein the host and remote computers contain relational databases in which their respective quotation data is stored.
13. 15. A quotation data exchange according to claim 14, wherein the data collected and stored within the relational database is used to populate the messages before transmission.
14. 16. A quotation data exchange according to any of claims 1 to 15, wherein the S 10 predetermined content fields for each message are expressed in a specific N implementation ofeXtensible Markup Language (XML).
15. 17. A quotation data exchange according to any of claims 1 to 16, wherein syntactical facilities of the predetermined content fields are described in a Document Type Definition (dtd) that is a de-normalised data definition that contains syntax and nesting of elements such that complex relationships and data categorisation of the target relational database are implied in the message and the Document Type Definition defines each message, mandatory fields, field grouping, limited data reference sets and allowable values.
16. 18. A quotation data exchange according to claim 17, wherein the syntactical facilities within the Document Type Definition (dtd) are translated to predefined identifying tags that surround each specific occurrence of a message and individual fields during transmission.
17. 19. A method for controlling an insurance repair process using a quotation data exchange according to claim 1, comprising the steps of: entering and storing the required quotation information into an insurer's computer system in response to a claim; sending a request for quotation that is automatically populated with stored quotation information in respect of specified damage; receiving a quotation for the repair of the specified damage; automatically retrieving information contained within the quotation and storing the information on the insurer's computer system; 59 sending an assessed quotation that is automatically populated with quotation o information stored on the insurer's computer system, that may or may not contain an O oO authority to proceed with the repair; receiving a tax invoice (request for payment) in respect of an authorised repair; automatically retrieving information contained within the tax invoice (request for payment) and storing the information on the insurer's computer system; sending a payment authority in response to a request for payment that is automatically populated with quotation information stored on the insurer's computer system.
18. 20. A method for controlling an insurance repair process according to claim 19, further comprising the step of inspecting the damage upon receiving such a request from the repairer within the quotation.
19. 21. A method for controlling an insurance repair process according to claim 19 or further comprising the step of including settlement information in the assessed quotation.
20. 22. A method for controlling an insurance repair process according to claim 19, or 21, further comprising the step of sending or receiving a total loss request, automatically retrieving information contained within the total loss request and storing the information on the insurer's computer system.
21. 23. A method for controlling an insurance repair process according to any of claims 19 to 22, further comprising the step of receiving an additional tax invoice (payment request) in the form of an adjustment note or re-activate invoice, automatically retrieving information contained within the additional tax invoice (request for payment) and storing the information on the insurer's computer system.
22. 24. A method for controlling an insurance repair process according to any of claims 19 to 23, further comprising the step of withdrawing authority at any time after an assessed quotation has been sent containing an authority.
23. 25. A method for controlling an insurance repair process according to any of claims 19 to 24, further comprising the step of cancelling ajob at any time after a request for 00 quotation has been received by the repairer.
24. 26. A method for controlling an insurance repair process according to any of claims 19 to 25, further comprising the step of declining a payment upon receipt of any tax invoice (request for payment).
25. 27. A method for controlling an insurance repair process according to any of claims 19 to 26, further comprising the step of receiving a decline job message from the repairer and sending the request for quotation to an alternate repairer.
26. 28. A method for controlling an insurance repair process according to any of claims 19 to 27, further comprising the step of receiving a parts reference message from a parts reference data supplier, automatically retrieving information contained within the parts reference message and storing the information on the insurer's computer system.
27. 29. A method for controlling an insurance repair process according to any of claims 19 to 28, further comprising the step of receiving a vehicle reference message from a parts reference data supplier, automatically retrieving information contained within the vehicle reference message and storing the information on the insurer's computer system. A method for controlling an insurance repair process according to any of claims 19 to 29, further comprising the step of receiving or sending an error message based on any message containing invalid fields or is delivered in an invalid sequence.
28. 31. A protocol for the control of an insurance repair process, involving the steps of exchanging electronic communication between an insurer and repairer where the communication is selected from a set of electronic messages having predetermined content fields, the message set including: a request for quotation in response to a claim, from insurer to repairer in respect of specified damage; 61 a quotation between repairer and insurer for repair of the damage specified in a 0 request for quotation; 00 an assessed quotation that may or may not contain an authority from insurer to proceed with the repair; a tax invoice (request for payment) from repairer to insurer in respect of an authorised repair; a payment authority from insurer to repairer in response to a request for N, payment.
29. 32. A protocol for the control of an insurance repair process according to claim 31, wherein the protocol is expressed in a specific implementation of eXtensible Markup Language (XML) containing syntactical facilities for mandatory fields, field grouping and allowable values for the specific set of allowable messages within the transmissions.
30. 33. A protocol for the control of an insurance repair process according to claim 31 or 32, wherein each message is described in a Document Type Definition (dtd) detailing the syntax and nesting of each element including limited data reference sets and allowable values for each element and its attributes.
31. 34. A protocol for the control of an insurance repair process according to claim 31, 32 or 33, wherein each message is regulated during transmission through the use of predefined tags that enclose each message and each specific occurrence of a field contained within a message transmission. A protocol for the control of an insurance repair process according to any of claims 31 to 34, wherein the possible transmission order of the allowable messages is predefined.
32. 36. A quotation data exchange for the control of an insurance repair process as substantially herein described with reference to the accompanying drawings. 62 0 N37. A method for controlling an insurance repair process using a quotation data Sexchange as substantially herein described with reference to the accompanying 00 drawings.
33. 38. A protocol for the control of an insurance repair process as substantially herein described with reference to the accompanying drawings. DATED this eighteenth day of October 2007 i^ Insurance Australia Limited Patent Attorneys for the Applicant: F.B. RICE CO.