AU2002231471B2 - Data exchange between insurer and repairer - Google Patents

Description

WO 02/071281 PCT/AU02/00176 DATA EXCHANGE BETWEEN INSURER AND REPAIRER.

Technical Field This invention concerns a data exchange, and in particular a computer system for exchanging data between an insurer and a repairer, for instance between software applications of a vehicle insurer and a crash repairer. The invention also concerns the structure of a database in which the messages are stored. In a further aspect it concerns a method of exchanging the data.

Summary of the Invention The invention is a computer system for exchanging data between a software application of an insurer and a repairer, comprising A message transceiving station, to send messages to and receive messages from the repairer. The messages being one of a closed set in the form of data wrapped in syntax to allow them to be mapped into a complex database structure which obeys relationship constraints and has referential integrity. The incoming messages are usually zipped.

A message receiver to unpack received messages to retrieve their data content.

A message data content parser to parse the data content and write it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity.

A data collector to extract the data from the first database, validate it and store it in tables organised in the predetermined schema in a second database that does have the relationship constraints and referential integrity.

An applications server may subsequently transfer data between the second database and applications software for processing.

WO 02/071281 PCT/AU02/00176 2 The data collector may operate to retrieve data from the database at set time intervals, such as once a minute.

As a result of actioning incoming messages an outgoing message is usually produced, marked up in XML format and written to the repairer's mailbox so that the repairer can receive it. In contrast to incoming messages the outgoing messages are generally not zipped.

Monitoring software may run continuously to check for errors in the validation done by the data collector. The monitoring software may display any error and probable resolution. It has a connected knowledge base that is dynamic and allowed to grow and record resolutions to new errors as they are detected for the first time.

The monitoring software may also raise an alarm when a record has not been collected within a specified time, for example ten minutes, so that support staff may intervene.

The monitor software program is scalable to include the use of technologies such as paging, short message service (SMS), wireless application protocol (WAP) or auto e-mail.

The system can effectively and efficiently communicate quote information because it takes advantage of an efficiently built database structure, intelligent message transportation and a high level of quality control of the data through error checking and correction procedures.

The implementation of a data exchange between repairers and assessors via the Internet allows for quicker response times, and allows for a paperless process for detailed quote information transmission. The reduction in intermediary staff between repairers and assessors also reduces the risk of human error when using this data exchange mechanism. This mechanism as envisaged would direct and manage the communication process to the most appropriate assessor, thus allowing the most optimum method in handling particular claims.

WO 02/071281 PCT/AU02/00176 3 From the repairer and customer's perspective the repair process would be transparent, and the complex processes of validation, approval and other associated checking and data extraction of the repairing process would be done typically on the transmission of the first message by the repairer to the assessor.

The invention also concerns the database which has been constructed to accept all relevant information concerning the insurance claims process between repairers and assessors, and keeps the relevant information stored in tables, where a list of tables is given below: Core Tables Work RequestForQuote QuoteSummary QuoteItem QuoteSummaryRate Invoice QuoteNote ClaimVehicle System Parameter Tables Code CodeType Action ActionStatus QuoteStatus Reference Tables RepairEffectiveRate Rate Assessor Repairer Area WO 02/071281 PCT/AU02/00176 4 AreaType RepairSubCategory RepairRateGroup Software Period (not yet implemented) Cross Reference Tables AreaAssessor AreaRepairer RepairRateGroup Security Audit Tables Principal Role Capability Resource CCISAudit (temporarily implemented) ErrorLog User Defined Information QuoteUserDefined QuoteltemUserDefined The User Defined tables contain information belonging to the sender that is guaranteed to be returned unchanged. This enables the sender to funnel multiple categories of information into a single category for the recipients benefit but allows the dissemination of this information back into the senders categories on return.

The key relationships between the core set of tables for the passing of information are: The primary key of a RequestForQuote is a foreign key of the QuoteSummary table.

WO 02/071281 PCT/AU02/00176 The QuoteSummary table has a primary key of the Repairer Id, the Quote Number generated by the Repairers Quotation Software package plus a blind key to allow multiple occurrences of QuoteSummary records and the keeping of quotation history.

There are multiple QuoteSummaryRate records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the QuoteSummaryRate table key.

There are multiple QuoteItem records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the QuoteItem table key.

There are potentially multiple Invoice records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Invoice table key.

The QuoteNote table has a blind primary key but contains the foreign keys of the RequestForQuote and QuoteSummary that it pertains to.

The Claim Vehicle table primary key is comprised of the Claim Number and Vehicle Registration Number which form part of the primary key of the Request for Quote.

In a further aspect the invention is a method for exchanging data between an insurer application software and a repairer, comprising the steps of: Receiving a message from the repairer, where the message is one of a closed set in the form of data wrapped in syntax to allow it to be mapped into a complex database structure which obeys relationship constraints and referential integrity, and usually being zipped.

Unpacking the received message to retrieve its data content.

WO 02/071281 PCT/AU02/00176 6 Parsing the data content and writing it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity.

Extracting the data from the first database, validating it and storing it in tables organised in the predetermined schema in a second database that does have the relationship constraints and referential integrity.

Then, transferring data between the second database and the applications software.

Brief Description of the Drawings Examples of the invention will now be described with reference to the accompanying drawings, in which: Fig. 1 is a block diagram of the network topology and hardware.

Fig. 2 is a message flow diagram of the message transportation.

Best Modes of the Invention Referring to figure 1, the diagram can be divided into three distinct groups. The first group is the repairers 10, the second is the Internet 11 and the third is the assessor's system ("the system") 12.

The system 12 is protected by a firewall 20 and comprises of three servers.

The Websuite server 21 is connected to the Gentran server 22 that in turn is connected to the Forte App server 23. The system 12 uses two Oracle databases, the Gentran database 24 that is connected to the Gentran server 22 and the ORM/Forte database 25 that is connected to the Forte applications server 23.

The Assessing Centre 26 connects to the Forte App server 23 to serve data out to individual assessors 27.

Messages 28 are transmitted between the repairers 10 and the system 12 via the Internet 11 in the form of data wrapped in XML syntax and zipped using WO 02/071281 PCT/AU02/00176 a known protocol such as HTTP or FTP. These messages pass through the firewall 20 to and from the websuite server 21. The XML, once it has been unpacked is passed 14 to the Gentran server 22. The XML is parsed and sent through ODBC to the Gentran oracle database 24. The Forte applications server 23 runs a program called Forte Collector to transfer data 16 between the Gentran database 24 and the ORM/Forte database Turning now to Fig. 2, the flow of messages will be described in more detail. In this example the system 12 belongs to an insurer and communicates over the Internet 11 with repairers 10. The repairer 10 prepares a message 13 and transmits it to a mailbox 30 on the websuite server 21.

The message 13 comprises Data fields wrapped into an XML syntax which allows the specification of data type, length, valid values, grouping, nesting of elements of data and the assignment of mandatory/optional attributes. Because the reference data sets may be different at the repairer and insurers computer systems, the data is denormalised into specific tags or a series of valid values are specified for a given element. As a result the apparently flat messages include intelligence to allow them to be mapped into a complex database structure which obeys relationship constraints and referential integrity.

The Gentran server 22 duplicates the message and sends the duplicate to an application inbox where it is enacted upon by a delivery rule. The delivery rule assumes that the message is a zip file and initiates an Unzipper software 31 program to load, passing the name of the zip file as a parameter.

The unzipper software program ensures validity of the zip file, and that the XML file extracted from the zip file is valid and parses correctly. The unzipper is not responsible for validation of the data types or lengths of fields.

However, the unzipper extracts any images 33 that maybe in the zip file.

Provided the XML file unzips correctly it is checked, by checking a message log 35, to verify that it is not a duplicate of an earlier message. Provided it is not a duplicate, a message is written to the message log 35 detailing that the WO 02/071281 PCT/AU02/00176 8 message has been received. The XML file is then taken 14 by the Gentran server and parsed 32.

If the zip file contains any images 33, they are written to a single directory on the local DASD 36. The images are subsequently moved 37 from the NT DASD to a tower Unix server 38 where they are stored with index files.

Images abide by set naming conventions. The naming conventions could be: RepairerId.QuoteNo.MsgNo.PicNo.jpg or RepairerId.QuoteNo.MsgNo.PicNo.idx In the event there is a problem with an incoming message, the unzipper will write a message 39 to an error table 40. An entry in the error table 40 causes an outbound XML error message to be prepared and placed in the outbound mailbox of the relevant repairer for transmission 41 back to the repairer. It is the repairer's responsibility to rectify any error.

If there is a validation problem during parsing the Gentran system writes an error message to one of its internal tables. The problem is then either actioned automatically or user intervention is sought.

After parsing is complete the Gentran system attempts to write the data into a set of tables 34 that are organised in a predetermined schema. These are tables in a Gentran Oracle database which has no relationship constraints or referential integrity. As a result all messages that will parse are stored.

The assessing centre 26 retrieves data from the Gentran system using collector software 43. The collector 43 extracts the data from each of the incoming message tables, validates it and creates new records 44 within the ORME/Forte database 25. This database includes relationship constraints and referential integrity so the validation includes examination for error conditions including referential integrity. The collector software 43 runs at a set time interval, currently once a minute.

WO 02/071281 PCT/AU02/00176 9 The ORM Forte server 23 uses applications software 45 to action the incoming messages, either automatically or using the assessing centre 26. As a result of actioning incoming messages an outgoing message 46 is usually produced, marked up in XML format and written to the repairer's mailbox 30 so that the repairer can receive it 47. These outgoing messages are not zipped.

A monitor software program 42 (which could be located on either a client machine or server depending on the support structure of the business group, supporting this system) is run continuously to check the errors arising in the validation being performed by the collector software 43. The program 42 also displays any system error and probable resolution. It has a connected knowledge base that is dynamic and allowed to grow and records/catalogues methods of resolutions to new errors detected.

Another function of the monitor software program 42 is to verify that the collector 43 is running at all times. The monitoring software 42 will raise an alarm when a record has not been collected within a specified time, for example ten minutes, so that support staff may intervene. The method by which the monitor software program's alarm is raised is through the comparison of the time stamp in the message log 35 to the time stamp in the Gentran tables 34 held by the Gentran database 24. If the difference between the two times is greater than a specified period, say 10 minutes, the alarm is raised.

The monitor software program 42 is scalable to include the use of technologies such as paging, short message service (SMS), wireless application protocol (WAP) or auto e-email.

In a typical scenario, the insurer transmits a "Request for Quote" message to the repairer 10 with insurance information on the property, the property details for example, make, model, engine number, and the customer's contact details. After receipt of a "Request for Quote" message, the repairers 10 in response, transmit their "Quotation" message containing an extensible mark-up WO 02/071281 PCT/AU02/00176 language (XML) file and images, zipped into a single file via the Internet 11 to reach the system 12. Message communication is done through the Internet using a known protocol such as HTTP or FTP.

In particular, an incoming message from a repairer 10, could be one of the following: Job declined Quotation (original variation) Total Loss Request Tax Invoice Adjustment Note Re-activate Invoice Tables used in the VCP database: ClaimVehicle QuoteImage Bonus Invoice RequestForQuote QuoteNote QuoteSummaryRate QuoteUserDefined QuoteStatus QuoteSummary Software Action Work Diary WO 02/071281 PCT/AU02100176 11 RepairRateGroup Repairer RepairSubcategory RepairEffectiveRate QuoteltemUserDefined Quoteltem Rate AreaType Area AreaRepairer AreaAssessor Assessor CCISAudit ErrorLog Period

ID

Code CodeType Resource Capability Principal Role Listed on the following pages, in order in which they are listed here, is the detail for each of the Tables: CREATB TABLE TBVCPACTION( CDEREPMERMODELTYPE VARCHAR2 (20) NOT NULL, CDEPEPATRMODELCODE VARCHAR2 (20) NOT NULL, CDE:QUOTESTATUS VARCHAR2 (20) NOT NULL, CDEACTIONTYPE VARCHAR2 (20) NOT NULL, WO 02/071281 WO 02/71281PCT/AU02/00176 12 CDEACTIONCODE VARCHAR.2 (20) NOT NULL, PRIARY KEY CDE REPAIRMODELTYPE, CDEREPAIRMIODELCODE, CDEQUOTESTATUS, CDEACTIONTYPE, CDEACTIONCODE) CREATE TABLE TBVCPACTIONSTATUS( CDE_-ACTIONTYPE VARCIIAR.2 (20) NOT NULL, CDEACTIONCODE VARCHAR2 (20) NOT NULL, CDE:QOTESTATUS VARCHAR2 (20) NOT NULL, CDERESUJLTINGQUOTESTATUS VARCHAR2 PRIMARY KEY CDE ACTIONTYPE, CDEACTIONCODE, CDEQUOTESTA'rUS) CREATE TABLE TBVCPAREA( CDEAREATYPE VARCHAR2 (10) NOT NULL, CDEAREA VARCHAR.2 (20) NOT NULL, CDEPARENTAREATYPE VARCHIAR.2 CDE_-PARENTAREA VARCIIAR.2 TXTDESCRIPTION VARCHAR2 (30) NOT NULL, PRIMARY KEY CDE AREATYPE, CDE AREA) CREATE TABLE TBVCPAREAASSESSOR CDEAREATYPE VARCHAR.2 (10) NOT NULL, CDE_-AREA VARCHAR.2 (20) NOT NULL, CDEASSESSOR VARCHAR.2 (20) NOT NULL, PRIMARY KEY CDEAREATYPE. CDEAREA, CDEASSESSOR) CREATE TABLE TBVCPAREAREPAIRER( CDEAREATYPE VARCHAR2 (10) NOT NULL, CDEAREA VARCIIAR2 (20) NOT NULL, CDEREPAIRER VARCHAR2 (20) NOT NULL, PRIMARY KEY CDE AREATYPE, CDE AREA, CDE REPAIRER) CREATE TABLE TBVCPAREATYPE( CDEAREATYPE VARCHAR-2 (10) NOT NULL, CDEPARENTAREATYPE VARCHAR2 TXTDESCRIPTION VARCHAR2 (30) NOT NULL, PRIMARY KEY (CDE-AREATYPE) CREATE TABLE TBVCPASSESSOR( CDEASSESSOR VARCHAR2 (20) NOT NULL, NAM_-FIRSThAME VARCHAR.2 (3 0) NOT NULL, NAM_ SURNAME VARCHAR.2 (30) NOT NULL, WO 02/071281 WO 02/71281PCT/AU02/00176 13 TXT_-PHONE VARCHAR.2 TXTFAX VARCHAR.2 TXT_-EMAIL VARCITAR2 ADR_ -STREET 1 VARCHAR2 ADR_ STREET2 VARCHAR2 ADRSTR.EET3 VARCHAR2 ADR. SUBURB VARCHAR2 ADRSTATE VARCHAR2 ADR_ POSTCODE VARCHAR2 TXTMOBILE VARCHAR2 PRIMARY KEY CDE ASSESSOR) CREATE TABLE TBVCPBONUS( CDEREPAIRER. VARCHAR.2 (20) NOT NULL, TXTQUOTENO VARCHAR2 (20) NOT NULL, NUM-SEQ NUMVBER (38) NOT NULL, CDE_-CLAIM VARCRAR2 (20) NOT NULL, CDEREGO VARCHAR.2 (10) NOT NULL, NUJM REINSTATEM[ENTSEQ NUMBER (38) NOT NULL, CDE_-SETThEMENTTYPE VARCHAR2 (20) NOT NULL, CDE_-REFERUNDERWRITJNG VARCHAR.2 CDEREGOSTATE VARCHAR'2 CDE WRITEOFFREPAIR. VARCHAR.2 AMT_ PRIORVALUE NUMIBER (10,2) NOT NULL, AMTSAL-VAGEVALUE NUMER (10,2) NOT NULL, AMT_-TOWING NUMBER (10,2) NOT NULL, CDE_-SALVAGECENTRE VARCHAR2 CIDE -TOWINGPROVIDER VARCHAR.2 DTECUSTOMTERNOTIFIED DATE, AMTREMOVEREPLACE NUMBER (10,2) NOT NULL, AMTREPA[R NUMER (10,2) NOT NULL, AMT_-PAINT NUMBER (10,2) NOT NULL, AMT_-PARTS NUMBER (10,2) NOT NULL, AMTSTJNDRYNvIISC NUMBER (10,2) NOT NULL, PRIMARY KEY CDE REPAIRER, TXT -QUOTENO, NJM-SEQ) CREATE TABLE TBVCPCAPABILITY NAMPRINCIPAL VARCHAR2 (30) NOT NULL, NAMRESOURCE VARCHAR2 (30) NOT NULL, CDEPRIVS VARCHAR.2 (30) NOT NULL, PRIMARY KEY NAM PRINCIPAL, NAM-RESOURCE) CREATE TABLE TBVCPCCISAUDIT( NUMO CISAUDITID NUNMER (3 8) NOT NULL, TXT VERSION VARCHAR.2 CDEREPAIRER VARCIIAR.2 (20) NOT NULL, NAM_-REPAIRERNAMvE VARCHAR2 CDECLAIMvIBER VARCHAR2 (20) NOT NULL, WO 02/071281 WO 02/71281PCT/AU02/00176 14 DTETNCIDENTDATE VARCIIAR2 TAMNC]DENTTIME VARCHAR2 TXTTNCIDENTI)ESCRIPTION LONG, FLGVEICLETOWERIhDICATOR CHAR TXTDAMAGEDAREA VARCHAR2 AMTSUMINSURED VARCHAR2 AMTINSURANCEEXCESS VARCHAR2 AMrOWNERSCONTRIBUTION VARCHAR2 DTEQUOTEDATE VARCIIAR2 ODEREGO VARCHAR2 ODEVIN VARCHAR2 TXTVETECLEDETAILS VARCHAR2 (200), NAM_ CUSTOMERNANvIE VARCHAR2 (200), TXTCUSTOMERHOMEPHONE VARCHAR2 TXTCIJSTOMERBUSINESSPHONE VARC}{AR2 FLGAUITHORISEDINDICATOR CHAR ODEJOB CATEGORY VARCHAR2 FLUHIRECAR11'DICATOR CHAR PRIMARY KEY (NUMCCISAIJDITID) CREATE TABLE TBVCPCLAIMVEHEfCLE ODEO LAIM VAROHAR2 (20) NOT NULL, ODEREGO VARCHAR2 (10) NOT NULL, ODE -yIN VARCHAR2 (30) NOT NULL, CDE_-BODYSTYLE VARCIIAR2 TXT_-SERIES VARCHAR2 DTE_-BUILD DATE, DTEMANSTART DATE, DTEMANEND DATE, ODEMANPAINTGROIJP VARCHAR2 ODEMANTRIM VARCHAR2 ODE_-OPTION VARCHAR2 ODEPAINT VARCHAR2 TXTENGINENO VARCIAR2 NOT NILL, AMTODOMIETER NUMBER (38), NIJMENGINE-SIZE NUMBER NUM_-CYLINDERS NUNMER. (38), TXT_-COLOUR VARCHAR2 ODE_ MAKE VAROIIAR2 (20) NOT NULL, TXITEQUIPMIEN'ILEVEL VARCHAR2 ODETRANSMISSIONTYPE VARCHAR2 (20) NOT NULL, ODETRANSMISSIONCODE VARCHAR2 (20) NOT NULL, ODEMODEL VARCHAR2 TXTDESCRIPTION VARCHAR2 ODEOIDOMETERTYPE VARCHAR2 ODEODOMETERCODE VARCHAR2 PRIMARY KEY ODE CLAIM, ODEREGO) WO 02/071281 WO 02/71281PCT/AU02/00176 CREATE TABLE TBVCPCODE( CDE-CODETYPE VARCHAR2 (20) NOT NUJLL, CDE_-CODE VARCHAR2 (20) NOT NULL, TXTDESCRIPTION VARCHAR2 (30) NOT NULL, TXITSHORT1DESCRIPTION VARCHAR2 (15) NOT NULL, NUMSORTCODE NUMBER (38), PRIMARY KEY C CDE -CODETYPE, CDE CODE) CREATE TABLE TBVCPDIARY( NUM_-DIARY NUMIBER (38) NOT NULL, CDEWORK NUTMBER (38), CDE_-ASSESSOR VARCHAR2 CDEREPAIRER VARCHAR2 TNT -QUOTENO VARCHAR2 NUM-QUOTESUMMARYSEQ NUMBER (38), DTE_-CREATED DATE NOT NULL, DTE_-ACTION DATE, CDE_-REASONTYPE VARCHAR2 CDE_-REASONCODE VARCHAR2 TXTDOCUMENT LONG, PRIMARY KEY (NUMLDIARY) CREATE TABLE TBVCPERRORLOG( CUE_-USEPJD VARC1-AR2 (100) NOT NULL, TXTAPPLICATIONID VARCHA4R2 (100) NOT NULL, TXT_-PKTIME VARCHAR2 (2 1) NOT NULL, TNTREPAIRERABN VARCHAR2 (4000), TNTINSURANCECLAIM4NO VARCHAR2 (4000), TXTREGISTRATIONNO VARC1IAI2 (4000), NUMREINSTATEMIENTNO VARCHAR2 (4000), TXT QUOTENO VARCHAR2 (4000), NUJMRELATESTOMESSAGENO NUMBER TNTREPAIREPJD VARCHAR2 (4000), NAM_-REPAIRERNAMIE VARCffAR2 (4000), TXTSEVERITY VARCHAR2 (4000), TNTERRORTYPE VARCHAR2 (4000), TNT_-VALIDITYDESCRIPTIOIN VARCHAR2 (4000), TNT_-VALIDITYLINENO, VARCHAR2 (4000), TNT_ VALIDITYCOLUMNNO VARCHAR2 (4000), TNTDATATYPEDESCRIPTION VARCHAR2 (4000), TNTDPATATYPEELEMEfNTNAME VARCHAR2 (4000), TNTDATAPLPEVALUE VARCHAR2 (4000), TNT_-DATACONTENTDESCRIPTION VARCHAR2 (4000), TNT_-DATACONTENTELEM[ENTNAME VARCHAR2 (4000), TNT_ DATACONTENTVALUE VARCHAR2 (4000), TNTMESSAGEORDERDESCPION VARCHAR2 (4000), NUMMIESSAGEORDEREXPECTEDNO NUNMER NUMMESSAGEORDERRECEIVEDNO NUMBER WO 02/071281 WO 02/71281PCT/AU02/00176 16 TXTMESSAGETYPEDESCRIPTION VARCHAR2 (4000), TX]?_DTDVERSIC)NDESCRIPTION VARCHAR2 (4000), TNTDTDVERSIONPECEWVEDVER VARCIINR2 (4000), TX]?_MISCELLANEOUSDESCRIPTION VARCHAR2 (4000), TNTDTDVERSION YARCHAR2 (4000), TXTSOURCEABN VARCHAR2 (4000), TXTSOURCE_-ORGNAME VARCHAR2 (4000), TX]?DESTABN VARCI-AR2 (4000), TXT_-DESTORGNAME VARCHAR2 (4000), TXTAPPVERSION VARCHAR2 (4000), VARCHAR2 (4000), TXT_-TIMIESTAMP VARCHAR2 (4000), FLGPROCESSINBOUND CHAR TXT_-TIrMSTANMN_-INBOUND VARCHAR2 (4000), TXT_-TINvIESTAMP_-YINBOUNT) VARCHAR2 (4000), FLGPROCESSOUTBOUND CHAR TTTIMESTAM4PNOUTBOUND VARCHAR2 (4000), TX]?_TM4E STAMPYOUTBOUND VARCHAR2 (4000)) CREATE TABLE TBVCPID CDEID VARCHAR2 (10) NOT NULL, NAM_-TABLE VARCHAR2 (30) NOT NULL, NAMCOLUMN VARCHAR2 (3 0) NOT NULL, PRIMARY KEY CDE-ID) CREATE TABLE TBVCP-INVOICE( CDEREPAIRER VARCHAR2 (20) NOT NULL, TXTQUOTENO VARCHAR2 (20) NOT NULL, NUMSEQ NUMBER (3 8) NOT NULL, NUM -INVOICESEQ NUMBER (3 8) NOT NULL, TNT_-INVOICENO VARCHAR2 (20) NOT NULL, DTE_-INVOICE DATE NOT NULL, DTECOMPLETION DATE NOT NULL, TNTABN VARCHAR2 (20) NOT NULL, TNTDESCRIPTION VARCHAR2 (100) NOT NULL, AMTGSTRATE NUMBER (10,2) NOT NULL, AM]?INVOICE NUMER (10,2) NOT NULL, CDEINVOICESTATUSTYPE. VARCHAR2 CDE_-INVOICESTATUSCODE VARCHAR2 D)TETRANSACTIONDATE DATE, TNTTA-XL1TERAL VARCHAR2 N-UMTOTALEXCLUDINGGST NUMBER (10,2), NUMTOTALGSTAMT NUMBER (10,2), NUM_ TOTALINCLUDINGGST NUMBER(10,2), NUMEXCESSTOCOLLECT NUMER (10,2), NUMOWNERS CONTRIBUTION NUMBER (10,2), NUMTOTALPAYABLEAMT NUMBER (10,2), NUMvfSUPPLY'DIFFAMT NUMBER (10,2), WO 02/071281 WO 02/71281PCT/AU02/00176 17 PRIMARY KEY CDE REPAIRER, TXT _QUOTENO, NM-SEQ, NUM_1NVOICESEQ) CREATE TABLE TIBVCPPERIOD CDE_-PERIOD VARCHAR2 (20) NOT NULL, TXTDESCRIPTION VARCHAR2 (30) NOT NULL, NUMDAYS NUIMER (3 8), AlvfrHOURS NUMBER (10,2), PRIMARY KEY CDE-PEPJOD CREATE TABLE TBVCPPRINCIPAL NAM_-PRINCIPAL VARCHAR2 (30) NOT N-ULL, CDE_-TYPE VARCHAR2 (30) NOT NULL, TXTPASSWORD VARCHAR2 (30) NOT NULL, NAM_-BONUSID VARCHAP.2 TINTBONIJSPASSWORD VARCHAR.2 NAMTOWERID VARCHAR2 TXTTOWERPAS SWORD VARCIIAR2 PRIMARY KEY (NAM-PRINCIPAL) CREATE TABLE TB VCPQUOTETMvAGE CDE_-CLAIM VARCHAR.2 (20) NOT NULL, CDEREGO VARCHAR.2 (10) NOT NULL, CDEREPAIRER VARCHAR2 (20) NOT NULL, NUM_-REINSTATEMENTSEQ NUMBER (3 8) NOT NULL, CDEIFN NUMVBER (38) NOT NULL, PREIARY KEY CDE CLAIM, CDEREGO, CDEREPAIRER, NEJMREIN'STATEMENTSEQ,

CDEIFN)

CREATE TABLE TB VCP-QUOTEIM4PACT CDECLAIM VARCHAR2 (20) NOT NULL, CDEREGO VARCHAR2 (10) NOT NULL, CDEREPAIRER. VARCHAR2 (20) NOT NULL, NUM_-REINSTATEMENTSEQ NUTMER (38) NOT NULL, CDE -ilvIPACTAREATYPE VARCHAR2 (20) NOT NULL, CDEIMPACTAREACODE VARCHAR2 (20) NOT NULL, CDEIMPACTSEVERITYTYPE VARCHAR2 (20) NOT NULL, CDEIMPACTSEVERITYCODE VARCIIAR2 (20) NOT NULL, PRIMARY KEY CDE CLAIM, CDEREGO, CDEREPAIRER, NUMREJNSTATEMENTSEQ, CDEIPACTAIREATYPE, CDEIMPACTAPREACODE) CREATE TABLE TB VCP-QUOTEITEM( CDEREPAIRER VARCHAR2 (20) NOT NULL, TXT QUOTENO VARCIIAR.2 (20) NOT NULL, WO 02/071281 WO 02/71281PCT/AU02/00176 18 NUNM SEQ NUMER (3 8) NOT NULL, NUJM ITEMSEQ NUM4BER (3 8) NOT NULL, CDE_-PARTSOURCE VARCHAR2 (11), CDEPARTORJENTATION VARCHAR2 AMTVALUE NUMvBER (10,2), CDE_-ITEM VARCHAR2 TNT_-ITEMDESCRIPTION VARCHAR2 FLGSUBLET CHAR TNTSUBLETABN VARCHAR2 AMTHOURS NUMIBER (10,2), AMT_-OVERRIT)EHOURLYRATE NUMIBER CDEPARTNUMIBER VARCHAR2 NUJM INVOICE NUM[BER. (38), AMT -PARTQUANTITY NUM4BER (10,2), CDEREPAIRCATEGORYTYPE VARCHAR2 (20) NOT NULL, CDEREPAIRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDEREPAIRSUB CATEGORY VARCHAR2 (20) NOT NULL, CDE QUOTE1TEMSTAThSTYPE VARCHAR2 (20) NOT NULL, CDE-QUOTEHTEMSTAThS CODE VARCHAR2 (20) NOT NULL, CDE_-OCCURANCEORIGINTYPE VARCHAR2 (20) NOT NULL, CDE_-OCCURANCEORIGINCODE VARCHAR2 (20) NOT NULL, TNTCOMMvENT VARCHAR2 (100), CDE_-REASONTYPE VARCHAR.2 CDE_-REASONCODE VARCHAR2 CDE_-ASSESSOR VARCHAR2 DTETRANSACTIONT~vIESTAMiP DATE, AMTUNITVALUE NUMIBER (10,2), NUM_-CYCLE NUMER (38), FLGREPORTON CHAR CDE_-PARTSOURCETYPE VARCHAR2 CDEPARTORIENTATIONTYPE VARCHAR2 PRIM[ARY KEY CDE REPAIRER, TNT QUOTENO, NUM SEQ, NUMITEMSEQ) CREATE TABLE T B-VCP-QUOTEITEMvUSERDEFINED CDEREPAIRER VARCHAR2 (20) NOT NULL, TNT QUOTENO VARCHAR2 (20) NOT NULL, NUM SEQ NUMBER (38) NOT NULL, NUM -ITEMSEQ NUMER (389) NOT NULL, TNTDEFINEATTRIBUTE VARCHAR2 (40) NOT NULL, TNYTDEFINEVALUE VARCHAR2 (40) NOT NULL, NUMMNESSAGENO ,NUMER (38), CDECLAIM1 VARCHAR2 PRDMARY KEY CDE REPAIRER, TNT-QUOTENO, NUM SEQ, NUMITEMSEQ, TNTDEFINEATTmIBUTE, TXTDEFINEVALUE) CREATE TABLE TBVCPQUOTENOTE NUM-QUOTENOTE NUMBER (38) NOT NULL, NAM-AUTHOR VARCHAR2 (3 0) NOT NULL, WO 02/071281 WO 02/71281PCT/AU02/00176 19 CDECLAIM VARCHAR2 (20) NOT NULL, CDEREGO VARCHAR.2 (10) NOT NULL, CDEREPAIRER VARCHAR2 (20) NOT NULL, NUM_-REINSTATEMENTSEQ NUMBER (38) NOT NULL, DTECREATED DATE, TXTDOCUMENT LONG NOT NULL, CDENOTETYPE VARCHAR2 CDENOTECODE VARCHAR2 TXTQUOTENO VARCHAR2 NUM-SEQ NUMBER (38), PRIMARY KEY (NUM-QUOTENOTE) CREATE TABLE TIB VCP-QUOTESTATUS( CDEQUOTESTATUS VARCHAR2 (20) NOT NULL, CDEDEFAULTPRIORITYTYPE VARCHAR2 (20) NOT NULL, CDEDEFAULTPPJORITYCODE VARCHAR2 (20) NOT N ULL, TXTDESCRIPTION VARCHAR2 (30) NOT NULL, CDEMODETYPE VARCHAR2 CDEMODECODE VARCHAR2 PRIMARY KEY (CDE-QUOTESTAThS) CREATE TABLE TBVCP-QUOTEUMMARY CDEREPAIRER VARCHAR2 (20) NOT NULL, TXT QUOTENO VARCHAR2 (20) NOT NULL, NUJMSEQ NUMBER (38) NOT NULL, CDE_-CLAIM VARCI{AR2 (20) NOT NULL, CDEREGO VARCIIAR2 (10) NOT NULL, NUM_-RETNSTATEMENTSEQ NUMBER (38) NOT NULL, CDEALLOCATEDASSESSOR VARCHAR2 (20) NOT NULL, DTEQUOTATION DATE, NUMMESSAGE NUMBER (38), CDEQUALT~YSU~vEYTYPE VARCHAR2 CDELQUALITYSUR-VEYCODE VARCHAR2 CDECUSTO]MERSURVEYTYPE VARCIIAR2 CDECUSTOMERSURVEYCODE VARCHAR.2 CDECOSTCOMPARISONTYPE VARCIIAR.2 CDECOSTCOMPARISONCODE VARCHAR2 DTE_-START DATE, DTEEND DATE, CDEREPAIRMODELTYPE VARCHNR2 (20) NOT NULL, CDEPEPAIIRMODELCODE VARCHAR.2 (20) NOT NULL, CDEQUOTETYPE VARCHAR2 (20) NOT NULL, CDEQUOTECODE VARCHAR.2 (20) NOT NULL, CDE-QUOTESTATUS VARCHAR-2 AMTOWNERCOLLECTCONTRIBUTION NUMBER (10,2), TXTUSERDEFINED LONG, WO 02/071281 WO 02/71281PCT/AU02/00176 CDESOFTWARE VARCHAR2 (10) NOT NULL, TXTSOFTWAREVERSION VARCHAR2 (10) NOT NULL, CDEOCCURANCEORIGTNTYPE VARCHAR2 CDEOCCURANCEOPJGINCODE VARCHAR2 TXTREPAIRERCONTACT VARCHAR2 CDEEVALUATIONTYPE VARCHAR2 CDEEVALUATIONCODE VARCHAR2 CDEPROGRESSTYPE VARCHAR2 CUEPROGRESSCODE VARCHAR2 NUMCYCLE NUMIBER (3 8), CDEVEfICLELOCATIONTYPE VARCHAR2 CUEVEIHCLELOCATIONCODE VARCI{AR2 CDEASSESSOR VARCHAR2 DTE_'IRANSACTIONTIESTAMP DATE, PPJMARY KEY CDE REPAIRER, TXTQUOTENO, NUM-SEQ) CREATE TABLE TB -VCPQUOTESUMMARYRATE( CUEREPAIRER VARCHAR2 (20) NOT NULL, TXT QUOTENO VARCH-AR2 (20) NOT NULL, NUMSEQ NUMIBER (3 8) NOT N-ULL, CDE_-REPA]RCATEGORYrYPE VARCHAR2 (20) NOT NULL, CUE_-REPAIRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDEREPAIRSUB CATEGORY VARCHAR2 (20) NOT NULL, AMTHOURLYRATE NUMIBER. CUEOCCURANCEORIGINTYPE, VARCHAR-2 CDE_-OCCIJRRANCEORIGINCODE VARCHAR2 CDEQUOTERATESTAT-USTYPE VARCHAR-2 CDEQUOT'ER-ATESTATUSCODE VARCI{AR2 PRIMARY KEY CDE REPAIRER, TXTQUOTENO, NUJM SEQ, CDEREPAIRCATEGORYTYPE, CDEREPAIRCATEGORYCODE, CDEREPAIRSUBCATEGORY) CREATE TABLE TB-VCP-QUOTEUSERDEFINED( CUEREPAIRER VARCHAR2 (20) NOT NULL, TXT QUOTENO VARCHAR2 (20) NOT NUTLL, NUM -SEQ NUMIBER (38) NOT NULL, TXT_-DEFINEATTRIBUTE VARCIIAR2 (40) NOT NULL, TXTDEFINEVALUE VARCHAR2 (40) NOT NULL, NUMMIESSAGENO NUMER. (3 8), PRIMARY KEY CDE REPAIRER, TXTQUOTENO, NUM SEQ, TXT _DEF1NEATrRIBUTE,

TXTDEFINEVALUE)

CREATE TABLE TBVCPRATE( CDE_-AREATYPE VARCHAR2 (10) NOT NULL, CDE_-AREA VARCHAR2 (20) NOT NULL, CDERATETYPE VARCHAR2 (20) NOT NULL, CDERATECODE VARCHAR2 (20) NOT NULL, WO 02/071281 PCT/AU02/00176 21 DTEEFFECTIVEDATE DATE NOT NULL, AMT _RATE NUMER (12,4) NOT NULL, PRTWvARY KEY CDE -APEATYPE, CDEAREA, CDERATETYPE, CDERATECODE, DTEEFFECTIVEDATEff) WO 02/071281 WO 02/71281PCT/AU02/00176 22 CREATE TABLE TBVCPREPAIREFFECTIVERATE( CDERATEGROUIPTYPE VARCHAR2 (20) NOT NULL, CDERATEGROUPCODE. VARCHAR2 (20) NOT NULL, CDE REPAIRCATEGORYTYPE VARCHAR.2 (20) NOT NULL, CDEREPAIRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDE_-REPA]RSUBCATEGORY VARCHAR2 (20) NOT NULL, DTESTART DATE NOT NULL, AMT_ HOURLYRLATE NUMBER NOT NULL, PRIMARY KEY CDE -RATEGROUP7IYPE, CDERATEGROUPCODE, CDE_-REPAIRCATEGORYTYPE, CDEREPAJRCATEGORYCODE, CDEREPAIRSUE CATEGORY,

DTE_START)

CREATE TABLE TBVCPREPAIRER( CDE_-REPAIRER VARCIIAR.2 (20) NOT NULL, TXTABN VARCITAR2 TXTURE VARCHAR2 TNT_-EMAIL VARCHAR2 (60) NOT NULL, CDEDEFAULTASSESSOR. VARCHAR.2 CDE_-PAYMENTM[ET'HODTYPE VARCHAR.2 (20) NOT NULL, CDEPAYMENTM[ETHODCODE VARCHAR.2 (20) NOT NULL, CDE_-COMMSMETHODTYPE VARCHAR2 (20) NOT NULL, CDE_-COMMSMETHOD CODE VARCHAR.2 (20) NOT NULL, TXT REPAIRERNAME VARCHAR2 (66), CDEBONIJSREPAIRER VARCHAR.2 PRIMARY KEY (CDE REPAIRER) CREATE TABLE TBVCPREPAIRERRATEGROUP CDE_-COMPANYID VARCHAR.2 (30) NOT NULL, CDERATEGROUPTYPE VARCHAR.2 (20) NOT NULL, ODERATEGROUPCODE VARCHAR-2 (20) NOT NULL, CDE_-REPAIRER VARCHAR.2 (20) NOT NULL, TXTDESCRIPTION VARCIIAR.2 (30) NOT NULL, PRIMARY KEY ODE COMANYID, CDER.ATEGROUPTYPE, CDERATEGROUPCODE,

CDEREPAIRER)

WO 02/071281 WO 02/71281PCT/AU02/00176 23 CREATE TABLE TBVCPREPAIRSUBCATEGORY( CDE_-REPAIRCATEGORYTYPE VARCHAR2 (20) NOT NULL, ODE_-REPAIIRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDE_-REPAIRSUBCATEGORY VARCHAR.2 (20) NOT NULL, TXTDESCRIPTION VARCHAR2 (30) NOT NULL, NUMSORTCODE NUMBER (38), TXTSHORTIDESCRIPTION VARCHAR2 PRIMARY KEY ODE-REPAIRCATEGORYTYPE, CDEREPAIRCATEGORYCODE, CDEREPAIRSIB CATEGORY) CREATE TABLE TBVCPREQUESTFORQUOTE ODECLAIM VARCHAR2 (20) NOT NULL, CDEPEGO VARCHAR2 (10) NOT NULL, CDEREPAIRER VARCHAR-2 (20) NOT NULL, NUM_ REINSTATEMENTSEQ NUMBER (3 8) NOT NULL, CDE-QUOTETYPE VARCHAR2 (20) NOT NULL, CDE-QUOTECODE VARCHAR.2 (20) NOT NULL, CDEREPAIRMODELTYPE VARCHAR2 (20) NOT NULL, CDE_-REPAIRMODELCODE VARCHAR2 (20) NOT NULL, ODECOMPLETIONREINSPECTIONTYPE VARCHAR.2 CDECOMIPLETIONREINSPECTIONCODE VARCJ{AR2 FLG_-TOW CHAR NOT NULL, FLGHIRECAR CHAR NOT NULL, AMTINSURANCEEXCESS NUMBER (10,2), NUM_-MESSAGE NUMBER (38), DTE REQUESTTIME DATE, DTEQUOTEEX-,PECTED DATE, ODE _QUOTESTATUS VARCHAR2 TXTCONTRACTTEXT VARCHAR.2 (1000), PRIMARY KEY CDE CLAIM, CDEREGO, CDEREPAIRER, NUMRETNSTATEMENTSEQ) CREATE TABLE TB_-VCP_-RESOURCE( TXTDESCRIPTION VARCHAR.2 (60) NOT NULL, NAM-RESOURCE VARCHAR2 (30) NOT NULL, PRIMARY KEY (NAM-RESOURCE) CREATE TABLE TBVCPROLE CDEROLENAME VARCHAR.2 (30) NOT NULL, NAM-PRINCIPAL VARCHAR2 (30) NOT NULL, PRIARY KEY CDE-ROLENAME, NAM-PRINCIPAL) CREATE TABLE TBVOPSOFTWARE ODE_-SOFTWARE VARCI{AR2 (10) NOT NULL, TXTVERSION VARCHAR2 (10) NOT NULL, ODECERTIFICATIONTYPE VARCHAR2 WO 02/071281 PCT/AU02/00176 24 CDE CERTIFICATIONCODE VARCHAR2 TXTDOCUMENT LONG NOT NULL, DTE CERTIFICATIONDATE DATE, PRIMARY KEY (CDE SOFTWARE, TXTVERSION) CREATE TABLE TBVCP WORK CDE_WORK NUMBER (38) NOT NULL, DTECREATED DATE NOT NULL, DTE_ACTIONDUE DATE, CDEALLOCATEDASSESSOR VARCHAR2(20) NOTNULL, CDEPRIORITYTYPE VARCHAR2 (20) NOT NULL, CDE PRIORITYCODE VARCHAR2 (20) NOT NULL, CDE REPAIRAREATYPE VARCHAR2 (10) NOT NULL, CDEREPAIRAREA VARCHAR2 (20) NOT NULL, CDE WORKREASONTYPE VARCHAR2 CDE WORKREASONCODE VARCHAR2 CDE_QUOTESTATUS VARCHAR2 CDE_CLAIM VARCHAR2 CDE REGO VARCHAR2 CDEREPAIRER VARCHAR2 NUMREINSTATEMENTSEQ NUMBER (38), TXT QUOTENO VARCHAR2 NUM QUOTESUMMARYSEQ NUMBER (38), CDEPROGRESSTYPE VARCHAR2 CDEPROGRESSCODE VARCHAR2 PRIMARY KEY (CDEWORK) 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 broadly described. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims (27)

1. A computer system for exchanging data between software applications of an insurer and a repairer, comprising: a message transceiving station, to send messages to and receive messages from the repairer, where each message is one of a closed set and is in the form of data wrapped in syntax to allow it to be mapped into a database structure which obeys relationship constraints and has referential integrity; a message receiver to unpack received messages to retrieve their data content; a message data content parser to parse the data content and write it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity; a data collector to extract the data from the first database, validate it and store it in tables organised in the predetermined schema in a second database that does have the relationship constraints and referential integrity.

2. A computer system according to claim 1, further comprising an applications server to subsequently transfer data between the second database and applications software for processing.

3. A computer system according to claim 1 or 2, where the data collector operates to retrieve data from the database at predetermined time intervals.

4. A computer system according to any preceding claim, where, as a result of actioning an incoming message, an outgoing message is produced, marked up in XML format and written to the repairer's mailbox so that the repairer can receive it. A computer system according to claim 1, where monitoring software runs continuously to check for errors in the validation done by the data collector. WO 02/071281 PCT/AU02/00176 26

6. A computer system according to claim 5, where the monitoring software displays errors and their probable resolution.

7. A computer system according to claim 6, where the monitoring software has a knowledge base that is dynamic and allowed to grow and record resolutions to new errors as they are detected for the first time.

8. A computer system according to claim 5, where the monitoring software raises an alarm when a record has not been collected within a specified time.

9. A computer system according to claim 1, where the second database has one or more of the following tables: Core Tables Work RequestForQuote QuoteSummary Quoteltem QuoteSununaryRaLe Invoice QuoteNote ClaimVehicle System Parameter Tables Code CodeType Action ActionStatus QuoteStatus Reference Tables RepairEffectiveRate Rate Assessor WO 02/071281 PCT/AU02/00176 27 Repairer Area AreaType RepairSubCategory RepairRateGroup Software Period (not yet implemented) Cross Reference Tables AreaAssessor AreaRepairer RepairRateGroup Security Audit Tables Principal Role Capability Resource CCISAudit (temporarily implemented) ErrorLog User Defined Information QuoteUserDefined QuoteItemUserDefined A computer system according to claim 9, where the key relationships between the core set of tables for the passing of information include the primary key of a RequestForQuote being a foreign key of the QuoteSummary table.

11. A computer system according to claim 9 or 10, where the QuoteSummary table has a primary key of the Repairer Id, the Quote Number generated by the Repairers Quotation Software package plus a blind key to allow WO 02/071281 PCT/AU02/00176 28 multiple occurrences of QuoteSummary records and the keeping of quotation history.

12. A computer system according to claim 9, 10 or 11, where there are multiple QuoteSummaryRate records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the QuoteSummaryRate table key.

13. A computer system according to any one of claims 9 to 12, where there are multiple Quoteltem records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Quoteltem table key.

14. A computer system according to any one of claims 9 to 13, where there are multiple Invoice records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Invoice table key. A computer system according to any one of claims 9 to 14, where the QuoteNote table has a blind primary key but contains the foreign keys of the RequestForQuote and QuoteSummary that it pertains to.

16. A computer system according to any one of claims 9 to 15, where the Claim Vehicle table primary key is comprised of the Claim Number and Vehicle Registration Number which form part of the primary key of the Request for Quote.

17. A method for exchanging data between an insurer software application and a repairer software application, comprising the steps of: receiving a message from the repairer, where the message is one of a closed set in the form of data wrapped in syntax to allow it to be mapped into a complex database structure which obeys relationship constraints and referential integrity; unpacking the received message to retrieve its data content; parsing the data content and writing it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity; and extracting the data from the first database, validating it and storing it in tables organised in the predetermined schema in a second database that does have the relationship constraints and referential integrity;- WO 02/071281 PCT/AU02/00176 29

18. A method according to claim 17, further comprising the subsequent transferring of data from the second database to the insurer applications software for processing.

19. A method according to claim 17 or 18, where the data collector operates to retrieve data from the database at predetermined time intervals. A method according to any one of claims 17, 18 or 19, comprising the further step of producing an outgoing message as a result of actioning an incoming message, the outgoing message being marked up in XML format and written to the repairer's mailbox so that the repairer can receive it.

21. A method according to claim 17, comprising the further step of running monitoring software continuously to check for errors in the validation done by the data collector.

22. A method according to claim 21, comprising the further step of the monitoring software displaying errors and their probable resolution.

23. A method according to claim 22, comprising the further step of the monitoring software having a knowledge base recording resolutions to new errors as they are detected for the first time.

24. A method according to claim 21, comprising the further step of the monitoring software raisings an alarm when a record has not been collected within a specified time. A method according to claim 17, where the second database has one or more of the following tables: Core Tables Work RequestForQuote QuoteSummary QuoteItem QuoteSummaryRate Invoice WO 02/071281 WO 02/71281PCT/AU02/00176 QuoteNote ClaimVehicle System Parameter Tables Code CodeType Action ActionStatus Quote Status Reference Tables RepairEffectiveRate Rate Assessor Repairer~ Area AreaType RepairSubCategory RepairRateGroup Software Period (not yet implemented) Cross Reference Tables AreaAssessor AreaRepairer RepairRateGroup Security Audit Tables Principal Role Capability Resource CClSAudit (temporarily implemented) WO 02/071281 PCT/AU02/00176 31 ErrorLog User Defined Information QuoteUserDefined QuoteItemUserDefined

26. A method according to claim 25, where the key relationships between the core set of tables for the passing of information include the primary key of a RequestForQuote being a foreign key of the QuoteSummary table.

27. A method according to claim 25 or 260, where the QuoteSummary table has a primary key of the Repairer Id, the Quote Number generated by the Repairers Quotation Software package plus a blind key to allow multiple occurrences of QuoteSummary records and the keeping of quotation history.

28. A method according to claim 25, 26 or 27, where there are multiple QuoteSummaryRate records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the QuoteSummaryRate table key.

29. A method according to any one of claims 25 to 28, where there are multiple QuoteItem records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the QuoteItem table key.

30. A mehtod according to any one of claims 25 to 28, where there are multiple Invoice records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Invoice table key.

31. A computer system according to any one of claims 25 to 30, where the QuoteNote table has a blind primary key but contains the foreign keys of the RequestForQuote and QuoteSummary that it pertains to.

32. A computer system according to any one of claims 25 to 31, where the Claim Vehicle table primary key is comprised of the Claim Number and Vehicle Registration Number which form part of the primary key of the Request for Quote.