WO2002071281A1

WO2002071281A1 - Data exchange between insurer and repairer

Info

Publication number: WO2002071281A1
Application number: PCT/AU2002/000176
Authority: WO
Inventors: John Uren; Brett Lyons
Original assignee: Nrma Insurance Limited
Priority date: 2001-03-01
Filing date: 2002-02-20
Publication date: 2002-09-12
Also published as: NZ527509A; AUPR346201A0; AU2007200869A1

Abstract

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. In each case a message transceiving station operates 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 operates to unpack received messages to retrieve their data content. A message data content parser operates 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 operates 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.

Description

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. 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. 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

Re que stForQuote QuoteSummary Quoteltem Quote SummaryRate

Invoice QuoteNote ClaimVehicle

System Parameter Tables

Code

CodeType Action ActionS tatus QuoteStatus

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

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. 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 Quoteltem records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Quoteltem 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. 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 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 15 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 25.

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 may be 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 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 Repairerld.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. 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 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

Quotelmage

Bonus

Invoice

RequestForQuote

QuoteNote

Quote S ummaryRate

QuoteUserDefined

QuoteStatus

Quote S ummary

Software Action Work Diary 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:

CREATE TABLE TB_VCP_ACTION ( CDE_REPAIRMODELTYPE VARCHAR2 (20) NOT NULL, CDEJ EPAIRMODELCODE VARCHAR2 (20) NOT NULL, CDE_QUOTESTATUS VARCHAR2 (20) NOT NULL, CDE_ACTIONΓΥPE VARCHAR2 (20) NOT NULL, CDE ACTIONCODE VARCHAR2 (20) NOT NULL,

PRIMARY KEY ( CDE_REPAIRMODELTYPE, CDE_REPAIRMODELCODE, CDE_QUOTESTATUS, CDE_ACTIONTYPE, CDE_ACTIONCODE )

CREATE TABLE TB_VCP_ACTIONSTATUS ( CDE_ACTIONTYPE VARCHAR2 (20) NOT NULL,

CDE_ACTIONCODE VARCHAR2 (20) NOT NULL, CDE_QUOTESTATUS VARCHAR2 (20) NOT NULL,

CDE_RESULTINGQUOTESTATUS VARCHA 2 (20),

PRIMARY KEY ( CDE_ACTIONTYPE, CDE_ACTIONCODE, CDE_QUOTESTATUS )

CREATE TABLE TB_VCP_AREA ( CDE_AREATYPE VARCHAR2 (10) NOT NULL, CDE_AREA VARCHAR2 (20) NOT NULL,

CDE_PARENTAREATYPE VARCHAR2 (10), CDE_PARENTAREA VARCHAR2 (20),

TXT_DESCRIPTION VARCHAR2 (30) NOT NULL,

PRIMARY KEY ( CDE_AREATYPE, CDE_AREA )

CREATE TABLE TB_VCP_AREAASSESSOR ( CDE_AREATYPE VARCHAR2 (10) NOT NULL, CDE_AREA VARCHAR2 (20) NOT NULL, CDE ASSESSOR VARCHAR2 (20) NOT NULL,

PRIMARY KEY ( CDE_AREATYPE, CDE_AREA, CDE_ASSESSOR )

CREATE TABLE TB_VCP_AREAREPAIRER ( CDE_AREATYPE VARCHAR2 (10) NOT NULL, CDE_AREA VARCHA 2 (20) NOT NULL, CDE_REPAIRER VARCHAR2 (20) NOT NULL,

PRIMARY KEY ( CDE_AREATYPE, CDE_AREA, CDE_REPAIRER )

CREATE TABLE TB_VCP_AREATYPE ( CDE_AREATYPE VARCHAR2 (10) NOT NULL, CDE_PARENTAREATYPE VARCHAR2 (10), TXT_DESCRTPTION VARCHAR2 (30) NOT NULL,

PRIMARY KEY ( CDE_AREATYPE )

CREATE TABLE TB_VCP_ASSESSOR ( CDE_ASSESSOR VARCHAR2 (20) NOT NULL, NAM_FIRSTNAME VARCHAR2 (30) NOT NULL, NAM SURNAME VARCHAR2 (30) NOT NULL, TXTJPHONE VARCHAR2 (20), TXT_FAX VARCHAR2 (20), TXT_EMAIL VARCHAR2 (60), ADR_STREET1 VARCHAR2 (60), ADR_STREET2 VARCHAR2 (60), ADR_STREET3 VARCHAR2 (60), ADR_SUBURB VARCHAR2 (30), ADR_STATE VARCHAR2 (10), ADR_POSTCODE VARCHAR2 (10), TXT_MOBILE VARCHAR2 (20),

PRIMARY KEY ( CDE_ASSESSOR )

CREATE TABLE TB_VCP_BONUS ( CDE_REPAJJRER VARCHAR2 (20) NOT NULL, TXT_QUOTENO VARCHAR2 (20) NOT NULL, NUM_SEQ NUMBER (38) NOT NULL,

CDE_CLAIM VARCHAR2 (20) NOT NULL,

CDE_REGO VARCHAR2 (10) NOT NULL, NUM IEINSTATEMENTSEQ NUMBER (38) NOT NULL, CDE_SETTLEMENTTYPE VARCHAR2 (20) NOT NULL, CDE_REFERUNDERWRITING VARCHAR2 (20), CDE_REGOSTATE VARCHAR2 (20), CDE_WRITEOFFREPAIR VARCHAR2 (20), AMTJPRIORVALUE NUMBER (10,2) NOT NULL, AMT_SALVAGEVALUE NUMBER (10,2) NOT NULL, AMT_TOWING NUMBER (10,2) NOT NULL, CDE_SALVAGECENTRE VARCHAR2 (20), CDEJOWINGPROVLDER VARCHAR2 (20), DTE_CUSTOMERNOTIFIED DATE,

AMTJREMOVEREPLACE NUMBER (10,2) NOT NULL, AMT_REPAIR NUMBER (10,2) NOT NULL, AMΓ_PAΓNT NUMBER (10,2) NOT NULL,

AMT PARTS NUMBER (10,2) NOT NULL, AMT~SUNDRYMISC NUMBER (10,2) NOT NULL,

PRIMARY KEY ( CDEJ EPAIRER, TXT_QUOTENO, NUM_SEQ )

CREATE TABLE TB_VCP_CAPABILΠΥ ( NAM_PRINCEPAL VARCHAR2 (30) NOT NULL, NAM_RESOURCE VARCHAR2 (30) NOT NULL, CDE PRIVS VARCHAR2 (30) NOT NULL,

PRIMARY KEY ( NAM_PRINCIPAL, NAM_RESOURCE )

CREATE TABLE TB_VCP_CCISAUDIT ( NUM_CCISAUDITID NUMBER (38) NOT NULL,

TXT VERSION VARCHAR2 (10), CDE_REPAIRER VARCHAR2 (20) NOT NULL,

NAM_REPAIRERNAME VARCHAR2 (60),

CDE_CLAIMNUMBER VARCHAR2 (20) NOT NULL, DTE_INCIDENTDATE VARCHAR2 (20),

TME NCroENTTIME VARCHAR2 (20),

TXT_INCIDENTDESCRIPTION LONG, FLG_VEHICLETOWERRNDICATOR CHAR (1), TXT DAMAGEDAREA VARCHAR2 (20), AMT_SUMINSURED VARCHAR2 (20), AMΓ_ΓNSURANCEEXCESS VARCHAR2 (20), AMΓ_OWNERSCONΓRIBUTION VARCHAR2 (20), DTE_QUOTEDATE VARCHAR2 (20), CDE_REGO VARCHAR2 (10),

CDE_VTN VARCHAR2 (30),

TXT_VEfflCLEDETAILS VARCHAR2 (200),

NAM_CUSTOMERNAME VARCHAR2 (200), TXT_CUSTOMERHOMEPHONE VARCHAR2 (20), TXT_CUST0MERBUS1NESSPH0NE VARCHAR2 (20), FLG_AUTHORISEDINDICATOR CHAR (1), CDEJOBCATEGORY VARCHAR2 (20), FLG_HIRECARΓNDICATOR CHAR (1), PPJMARY KEY ( NUM_CCISAUDΓΠD )

CREATE TABLE TB_VCP_CLAIMVEHICLE ( CDE_CLAIM VARCHAR2 (20) NOT NULL, CDE_REGO VARCHAR2 (10) NOT NULL,

CDE_VIN VARCHAR2 (30) NOT NULL,

CDE_BODYSTYLE VARCHAR2 (30), TXT_SERTES VARCHAR2 (30),

DTE_BUILD DATE, DTE_MANSTART DATE,

DTE_MANEND DATE,

CDE_MANPAINTGROUP VARCHAR2 (10), CDE_MANTRIM VARCHAR2 (10),

CDE_OPTION VARCHAR2 (10), CDE_PAINT VARCHAR2 (10),

TXT_ENGTNENO VARCHAR2 (30) . NOT NULL,

AMT_ODOMETER NUMBER (38),

NUM_ENGΓNESIZE NUMBER (5,2), NUM_CYLINDERS NUMBER (38), TXT_COLOUR VARCHAR2 (20),

CDE_MAKE VARCHAR2 (20) NOT NULL,

TXT_EQUTPMENTLEVEL VARCHAR2 (10), CDE_TRANSMISSIONTYPE VARCHAR2 (20) NOT NULL, CDE_TRANSMISSIONCODE VARCHAR2 (20) NOT NULL, CDE_MODEL VARCHAR2 (20),

TXT_DESCRIPTION VARCHAR2 (30), CDE_ODOMETERTYPE VARCHAR2 (20), CDE_ODOMETERCODE VARCHAR2 (20), PRIMARY KEY ( CDE_CLAM, CDE_REGO ) CREATE TABLE TB_VCP_CODE ( CDE_CODETYPE VARCHAR2 (20) NOT NULL,

CDE_CODE VARCHAR2 (20) NOT NULL,

TXT_DESCRTPTION VARCHAR2 (30) NOT NULL, TXT_SHORTDESCRIPTION VARCHAR2 (15) NOT NULL, NUM_SORTCODE NUMBER (38),

PRIMARY KEY ( CDE_CODETYPE, CDE_CODE )

CREATE TABLE TB_VCP_DIARY ( NUMJDIARY NUMBER (38) NOT NULL,

CDE_WORK NUMBER (38),

CDE_ASSESSOR VARCHAR2 (20), CDE_REPAIRER VARCHAR2 (20), TXT_QUOTENO VARCHAR2 (20),

NUM_QUOTESUMMARYSEQ NUMBER (38), DTE_CREATED DATE NOT NULL,

DTE_ACTION DATE, CDE_REASONTYPE VARCHAR2 (20), CDE_REASONCODE VARCHAR2 (20), TXT_DOCUMENT LONG,

PRIMARY KEY ( NUM_DIARY )

CREATE TABLE TB_VCP_ERRORLOG ( CDE_USERTD VARCHAR2 (100) NOT NULL,

TXT_APPLICATIONID VARCHAR2 (lOO) NOT NULL, TXTJPKTIME VARCHAR2 (21) NOT NULL,

TXTJREPAIRERABN VARCHAR2 (4000),

TXT_INSURANCECLAIMNO VARCHAR2 (4000),

TXT_REGISTRATIONNO VARCHAR2 (4000), NUM_REINSTATEMENTNO VARCHAR2 (4000), TXT_QUOTENO VARCHAR2 (4000),

NUM_RELATESTOMESSAGENO NUMBER (3), TXT_REPAΓRERΓD VARCHAR2 (4000),

NAM_REPATRERNAME VARCHAR2 (4000),

TXT_SEVERITY VARCHAR2 (4000), TXT JERRORTYPE VARCHAR2 (4000),

TXT_VALΓDITYDESCRIPTION VARCHAR2 (4000), TXT_VALIDITYLINENO VARCHAR2 (4000),

TXT_VALIDπΥCOLUMNNO VARCHAR2 (4000),

TXT_DATATYPEDESCRIPTION VARCHAR2 (4000), TXT_DATATYPEELEMENTNAME VARCHAR2 (4000), TXT_DATATYPEVALUE VARCHAR2 (4000),

TXT_DATACONTENTDESCRIPTION VARCHAR2 (4000), TXT_DATACONTENTELEMENTNAME VARCHAR2 (4000), TXT_DATACONTENTVALUE VARCHAR2 (4000), TXT_MESSAGEORDERDESCRIPTION VARCHAR2 (4000), NUM_MESSAGEORDEREXPECTEDNO NUMBER (3), NUM_MESSAGEORDERRECEIVEDNO NUMBER (3), TXT_MESSAGETYPEDESCRIPTION VARCHAR2 (4000), TXT_DTDVERSIONDESCRIPTION VARCHAR2 (4000), TXT_DTDVERSI0NRECEIVEDVER VARCHAR2 (4000), TXT_MISCELLANEOUSDESCR]PTION VARCHAR2 (4000), TXT_DTDVERSION VARCHAR2 (4000),

TXT_SOURCE_ABN VARCHAR2 (4000),

TXT_SOURCE_ORGNAME VARCHAR2 (4000),

TXT_DEST_ABN VARCHAR2 (4000),

TXT_DEST_ORGNAME VARCHAR2 (4000), TXT_APPVERSION VARCHAR2 (4000),

TXT APPNAME VARCHAR2 (4000),

TXT_TIMESTAMP VARCHAR2 (4000),

FLG_PROCESS_INBOUND CHAR (1),

TXT_TIMESTAMP_N_INBOUND VARCHAR2 (4000), TXT_TIMESTAMP_Y_INBOUND VARCHAR2 (4000), FLGJPROCESSJ3UTBOUND CHAR (1),

TXT_TIMESTAMP_N_OUTBOUND VARCHAR2 (4000), TXT_TIMESTAMP_Y_OUTBOUND VARCHAR2 (4000)) CREATE TABLE TO VCP LD (

CDE D VARCHAR2 (10) NOT NULL, NAM TABLE VARCHAR2 (30) NOT NULL, NAM_COLUMN VARCHAR2 (30) NOT NULL, PRIMARY KEY ( CDE_D )

CREATE TABLE TB_VCP_INVOICE ( CDE_REPATRER VARCHAR2 (20) NOT NULL, TXT_QUOTENO VARCHAR2 (20) NOT NULL, NUM_SEQ NUMBER (38) NOT NULL,

NUM_INVOICESEQ NUMBER (38) NOT NULL, TXT NVOICENO VARCHAR2 (20) NOT NULL, DTE NVOICE DATE NOT NULL, DTE_COMPLETION DATE NOT NULL, TXT_ABN VARCHAR2 (20) NOT NULL,

TXT_DESCRIPTION VARCHAR2 (100) NOT NULL, AMT_GSTRATE NUMBER (10,2) NOT NULL, AMTJNVOICE NUMBER (10,2) NOT NULL, CDE_LNVOICESTATUSTYPE VARCHAR2 (20), CDEJNVOICESTATUSCODE VARCHAR2 (20), DTE_TRANSACTIONDATE DATE, TXT_TAXLΓΓERAL VARCHAR2 (30), NUM_TOTALEXCLUDINGGST NUMBER (10,2),

NUM ΓOTALGSTAMT NUMBER (10,2), NUM_TOTALINCLUDΓNGGST NUMBER (10,2), NUM_EXCESSTOCOLLECT NUMBER (10,2), NUM_OWNERSCONTRIBUTION NUMBER (10,2), NUM_TOTALPAYABLEAMT NUMBER (10,2), NUM_SUPPLYDIFFAMT NUMBER (10,2), PRIMARY KEY ( CDE_REPAIRER, TXT_QUOTENO, NUM_SEQ, NUMJNVOICESEQ )

CREATE TABLE TB_VCP_PERIOD ( CDE_PERIOD VARCHAR2 (20) NOT NULL,

TXT DESCRLPTION VARCHAR2 (30) NOT NULL, NUM_DAYS NUMBER (38), AMT_HOURS NUMBER (10,2), PRIMARY KEY ( CDE_PERIOD )

CREATE TABLE TB_VCP_PRINCIPAL ( NAM_PPJNCIPAL VARCHAR2 (30) NOT NULL, CDE_TYPE VARCHAR2 (30) NOT NULL,

TXT PASSWORD VARCHAR2 (30) NOT NULL, NAM_BONUSID VARCHAR2 (30), TXT_BONUSPASSWORD VARCHAR2 (30), NAM_TOWERTD VARCHAR2 (30), TXT TOWERPASSWORD VARCHAR2 (30),

PRIMARY KEY ( NAM_PRINCIPAL )

CREATE TABLE TB_VCP_QUOTEJMAGE (

CDE_CLAIM VARCHAR2 (20) NOT NULL,

CDE_REGO VARCHAR2 (10) NOT NULL,

CDE_REPAIRER VARCHAR2 (20) NOT NULL,

NUM_REINSTATEMENTSEQ NUMBER (38) NOT NULL, CDE FN NUMBER (38) NOT NULL,

PRIMARY KEY ( CDE_CLAIM, CDE_REGO, CDEJREPATRER, NUM_REINSTATEMENTSEQ, CDE_IFN )

CREATE TABLE TB_VCP_QUOTEIMPACT (

CDE_CLAIM VARCHAR2 (20) NOT NULL,

CDE_REGO VARCHAR2 (10) NOT NULL,

CDE_REPATRER VARCHAR2 (20) NOT NULL, NUM_REΓNSTATEMENTSEQ NUMBER (38) NOT NULL,

CDE_IMPACTAREATYPE VARCHAR2 (20) NOT NULL,

CDE_IMPACTAREACODE VARCHAR2 (20) NOT NULL,

CDE_IMPACTSEVERITYTYPE VARCHAR2 (20) NOT NULL,

CDE_IMPACTSEVERITYCODE VARCHAR2 (20) NOT NULL,

PRIMARY KEY ( CDE_CLAIM, CDE_REGO, CDE_REPAIRER, NUM_REINSTATEMENTSEQ, CDE_IMPACTAREATYPE, CDE_IMPACTAREACODE )

CREATE TABLE TB_VCP_QUOTEITEM (

CDE_REPALRER VARCHAR2 (20) NOT NULL,

TXT_QUOTENO VARCHAR2 (20) NOT NULL, NUM_SEQ NUMBER (38) NOT NULL,

NUMJTEMSEQ NUMBER (38) NOT NULL,

CDE_PARTSOURCE VARCHAR2 (11),

CDE_PARTORIENTATION VARCHAR2 (20), AMTNALUE NUMBER (10,2),

CDEJTEM VARCHAR2 (20),

TXT_rTEMDESCRIPTION VARCHAR2 (40),

FLG_SUBLET CHAR (l),

TXT_SUBLETABN VARCHAR2 (20), AMTJHOURS NUMBER (10,2),

AMT_OVERRIDEHOURLYRATE NUMBER (5,2),

CDE_PARTNUMBER VARCHAR2 (30),

NUMJNVOICE NUMBER (38),

AMT_PARTQUANTITY NUMBER (10,2), CDE_REPAΓRCATEGORYTYPE VARCHAR2 (20) NOT NULL,

CDE_REPATRCATEGORYCODE VARCHAR2 (20) NOT NULL,

CDE_REPAΓRSUBCATΕGORY VARCHAR2 (20) NOT NULL,

CDE_QUOTEΠEMSTATUSTYPE VARCHAR2 (20) NOT NULL,

CDE_QUOTEΓTEMSTATUSCODE VARCHAR2 (20) NOT NULL, CDE_OCCURANCEORIGINTYPE VARCHAR2 (20) NOT NULL,

CDE_OCCURANCEORIGINCODE VARCHAR2 (20) NOT NULL,

TXT_COMMENT VARCHAR2 (100),

CDE_REASONTYPE VARCHAR2 (20),

CDE_REASONCODE VARCHAR2 (20), CDE_ASSESSOR VARCHAR2 (20),

DTE_TRANSACTIONTIMESTAMP DATE,

AMT_UNITVALUE NUMBER (10,2),

NUM_CYCLE NUMBER (38),

FLG_REPORTON CHAR (1), CDE_PARTSOURCETYPE VARCHAR2 (20),

CDE_PARTORIENTATIONTYPE VARCHAR2 (20),

PRIMARY KEY ( CDEJ EPAIRER, TXT_QUOTENO, NUM_SEQ, NUMJTEMSEQ )

CREATE TABLE TB_VCP_QUOTEITEMUSERDEFINED ( CDE_REPAIRER VARCHAR2 (20) NOT NULL, TXT_QUOTENO VARCHAR2 (20) NOT NULL,

NUM_SEQ NUMBER (38) NOT NULL, NUMJTEMSEQ NUMBER (38) NOT NULL,

TXTJDEFΓNEATTRIBUTE VARCHAR2 (40) NOT NULL, TXT DEFINEVALUE VARCHAR2 (40) NOT NULL, NUM_MESSAGENO NUMBER (38), CDEJXAIM VARCHAR2 (20),

PRIMARY KEY ( CDE_REPAIRER, TXT_QUOTENO, NUM_SEQ, NUMJTEMSEQ,

TXT JDEFΓNEATTRΓBUTE, TXT_DEFΓNEVALUE )

CREATE TABLE TB_VCP_QUOTENOTE (

NUM_QUOTENOTE NUMBER (38) NOT NULL, NAM_AUTHOR VARCHAR2 (30) NOT NULL, CDE_CLAIM VARCHAR2 (20) NOT NULL,

CDE_REGO VARCHAR2 (10) NOT NULL,

CDE_REPAIRER VARCHAR2 (20) NOT NULL,

NUM_REINSTATEMENTSEQ NUMBER (38) NOT NULL,

DTE 3REATED DATE,

TXT_DOCUMENT LONG NOT NULL,

CDE_NOTETYPE ■ VARCHAR2 (20),

CDE_NOTECODE VARCHAR2 (20),

TXT_QUOTENO VARCHAR2 (20),

NUM_SEQ NUMBER (38),

PRIMARY KEY ( NUM_QUOTENOTE )

CREATE TABLE TB_VCP_QUOTESTATUS ( CDE_QUOTESTATUS VARCHAR2 (20) NOT NULL,

CDEJDEFAULTPRIORITYTYPE VARCHAR2 (20) NOT NULL, CDE_DEFAULTPRIORITYCODE VARCHAR2 (20) NOT NULL,

TXTJDESCRIPTION VARCHAR2 (30) NOT NULL,

CDEJvIODETYPE VARCHAR2 (20),

CDEJMODECODE VARCHAR2 (20), PRIMARY KEY ( CDE_QUOTESTATUS )

CREATE TABLE TB_VCP_QUOTESUMMARY ( CDE_REPAIRER VARCHAR2 (20) NOT NULL, TXT_QUOTENO VARCHAR2 (20) NOT NULL,

NUM SEQ NUMBER (38) NOT NULL,

CDE_CLAIM VARCHAR2 (20) NOT NULL,

CDE_REGO VARCHAR2 (10) NOT NULL,

NUMJ^EΓNSTATEMENTSEQ NUMBER (38) NOT NULL, CDE_ALLOCATED ASSESSOR VARCHAR2 (20) NOT NULL,

DTE_QUOTATION DATE,

NUM_MESSAGE NUMBER (38),

CDE_QUALITYSURVEYTYPE VARCHAR2 (20), CDE_QUALITYSURVEYCODE VARCHAR2 (20), CDE_CUSTOMERSURVEYTYPE VARCHAR2 (20), CDE_CUSTOMERSURVEYCODE VARCHAR2 (20), CDE_COSTCOMPARISONTYPE VARCHAR2 (20), CDE_COSTCO PAWSONCODE VARCHAR2 (20), DTEJSTART DATE, DTE JND DATE,

CDE_REPAΓRMODELTYPE VARCHAR2 (20) NOT NULL,

CDEJREPAIRMODELCODE VARCHAR2 (20) NOT NULL, CDE_QUOTETYPE VARCHAR2 (20) NOT NULL,

CDE_QUOTECODE VARCHAR2 (20) NOT NULL, CDE_QUOTESTATUS VARCHAR2 (20),

AMT DWNERCOLLECTCONTRΓBUTION NUMBER QO,2), TXTJJSERDEFINED LONG, CDE_SOFTWARE VARCHAR2 (10) NOT NULL,

TXT_SOFTWAREVERSION VARCHAR2 (10) NOT NULL,

CDE_OCCURANCEORIGINTYPE VARCHAR2 (20),

CDE_OCCURANCEORIGINCODE VARCHAR2 (20), TXT_REPAIRERCONTACT VARCHAR2 (30), CDE_EVALUATIONTYPE VARCHAR2 (20), CDE_EVALUATIONCODE VARCHAR2 (20), CDE_PROGRESSTYPE VARCHAR2 (20),

CDE_PROGRESSCODE VARCHAR2 (20), NUM_CYCLE NUMBER (38),

CDE_VEHICLELOCATIONTYPE VARCHAR2 (20), CDE_VEHICLELOCATIONCODE VARCHAR2 (20), CDE_ASSESSOR VARCHAR2 (20),

DTEJΓRANSACTIONTΓMESTAMP DATE,

PRIMARY KEY ( CDE ffiPAIRER, TXT _.QUOTENO, NUM SEQ )

CREATE TABLE TB_VCP_QUOTESUMMARYRATE ( CDE_REPAIRER VARCHAR2 (20) NOT NULL,

TXT_QUOTENO VARCHAR2 (20) NOT NULL,

NUM JSEQ NUMBER (38) NOT NULL,

CDEJREPAIRCATEGORYTYPE VARCHAR2 (20) NOT NULL,

CDE_REPALRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDE_REPAIRSUBCATEGORY VARCHAR2 (20) NOT NULL,

AMT HOURLYRATE NUMBER (5,2),

CDE 3CCURANCEORIGINTYPE VARCHAR2 (20),

CDE DCCURRANCEORIGINCODE VARCHAR2 (20),

CDE_QUOTERATESTATUSTYPE VARCHAR2 (20), CDE_QUOTERATESTATUSCODE VARCHAR2 (20),

PRIMARY KEY ( CDEJ EPALRER, TXT_QUOTENO, NUM_SEQ, CDEJREPAIRCATEGORYTYPE, CDE_REPAΓRCATEGORYCODE, CDE_REPAΓRSUBCATEGORY )

CREATE TABLE TB J CP_QUOTEUSERDEFINED (

CDE_REPAΓRER VARCHAR2 (20) NOT NULL,

TXT _.QUOTENO VARCHAR2 (20) NOT NULL,

NUM_SEQ NUMBER (38) NOT NULL, TXTJDEFINEATTRIBUTE VARCHAR2 (40) NOT NULL,

TXT_DEFINEVALUE VARCHAR2 (40) NOT NULL,

NUMJvlESSAGENO NUMBER (38),

PRIMARY KEY ( CDEJREPAIRER, TXT_QUOTENO, NUM_SEQ, TXT_DEFINEATTRIBUTE, TXT DEFINEVALUE )

CREATE TABLE TB J CP JRATE ( CDE_AREATYPE VARCHAR2 (10) NOT NULL, CDE_AREA VARCHAR2 (20) NOT NULL,

CDEJIATETYPE VARCHAR2 (20) NOT NULL, CDE_RATECODE VARCHAR2 (20) NOT NULL, DTE _EFFECTIVED ATE DATE NOT NULL,

AMTJRATE NUMBER (12,4) NOT NULL,

PRIMARY KEY ( CDE_AREATYPE, CDE_AREA, CDEJIATETYPE, CDE tATECODE, DTE FFECTΓVEDATΈ )

CREATE TABLE TB_VCP_REPATREFFECTIVERATE ( CDEJIATEGROUPTYPE VARCHAR2 (20) NOT NULL, CDEJRATEGROUPCODE VARCHAR2 (20) NOT NULL, CDE_REPAIRCATEGORYTYPE VARCHAR2 (20) NOT NULL, CDE_REPAIRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDEJREPAIRSUBCATEGORY VARCHAR2 (20) NOT NULL, DTE_START DATE NOT NULL,

AMT_HOURLYRATE NUMBER (5,2) NOT NULL, PRIMARY KEY ( CDEJRATEGROUPTYPE, CDEJRATEGROUPCODE,

CDE_REPAIRCATEGORYTYPE, CDE_REPALRCATEGORYCODE, CDE_REPAIRSUBCATEGORY, DTE_START )

CREATE TABLE TBJVCPJREPAIRER (

CDE_REPAIRER VARCHAR2 (20) NOT NULL,

TXT_ABN VARCHAR2 (20),

TXT_URL VARCHAR2 (60),

TXT_EMAIL VARCHAR2 (60) NOT NULL, CDEJDEFAULTASSESSOR VARCHAR2 (20),

CDE_PAYMENTMETHODTYPE VARCHAR2 (20) NOT NULL,

CDE J-AYMENTMETHODCODE VARCHAR2 (20) NOT NULL,

CDE COMMSMETHODTYPE VARCHAR2 (20) NOT NULL,

CDE X>MMSMETHODCODE VARCHAR2 (20) NOT NULL, TXTJREPAIRERNAME VARCHAR2 (66),

CDEJ30NUSREPACRER VARCHAR2 (20),

PRIMARY KEY ( CDE JREPAIRER )

CREATE TABLE TB_VCPJREPATRERRATEGROUP ( CDE_COMPANYID VARCHAR2 (30) NOT NULL, CDEJIATEGROUPTYPE VARCHAR2 (20) NOT NULL, CDEJRATEGROUPCODE VARCHAR2 (20) NOT NULL, CDE_REPAIRER VARCHAR2 (20) NOT NULL, TXTJDESCRIPTION VARCHAR2 (30) NOT NULL,

PRIMARY KEY ( CDE_COMPANYID, CDE_RATEGROUPTYPE, CDE_RATEGROUPCODE, CDEJREPAIRER )

CREATE TABLE TBJVCP JREPAIRSUBCATEGORY ( CDE JREPAIRCATEGORYTYPE VARCHAR2 (20) NOT NULL, CDE_REPAlRCATEGORYCODE VARCHAR2 (20) NOT NULL, CDE JREPAIRSUBCATEGORY VARCHAR2 (20) NOT NULL, TXTJDESCRTPTION VARCHAR2 (30) NOT NULL, NUM_SORTCODE NUMBER (38),

TXTJ3HORTDESCRIPTION VARCHAR2 (15),

PRIMARY KEY ( CDE_REPAIRCATEGORYTYPE, CDE_REPAIRCATEGORYCODE, CDE_REPAIRSUBCATEGORY )

CREATE TABLE TB JVCP_REQUESTFORQUOTE ( CDE XAIM VARCHAR2 (20) NOT NULL, CDEJREGO VARCHAR2 (10) NOT NULL,

CDEJREPAIRER VARCHAR2 (20) NOT NULL,

NUMJREINSTATEMENTSEQ NUMBER (38) NOT NULL, CDE_QUOTETYPE VARCHAR2 (20) NOT NULL,

CDE_QUOTECODE VARCHAR2 (20) NOT NULL, CDE_REPAT MODELTYPE VARCHAR2 (20) NOT NULL, CDE JREPATRMODELCODE VARCHAR2 (20) NOT NULL, CDE OMPLETIONREΓNSPECTIONTYPE VARCHAR2 (20), CDE_COMPLETIONREINSPECTIONCODE VARCHAR2 (20), FLGJTOW CHAR (1) NOT NULL, FLGJHRECAR CHAR (L) NOT NULL,

AMTJNSURANCEEXCESS NUMBER (10,2), NUMJMESSAGE NUMBER (38),

DTEJREQUESTTIME DATE, DTE_QUOTEEXPECTED DATE, CDE_QUOTESTATUS VARCHAR2 (20),

TXT_CONTRACTTEXT VARCHAR2 (1000),

PRIMARY KEY ( CDE _CLAIM, CDEJREGO, CDEJREPAIRER, NUMJREINSTATEMENTSEQ )

CREATE TABLE TB_VCP JRESOURCE ( TXTJDESCRΓPTION VARCHAR2 (60) NOT NULL, NAM_RESOURCE VARCHAR2 (30) NOT NULL, PRIMARY KEY ( NAMJRESOURCE )

CREATE TABLE TBJVCP JROLE ( CDEJROLENAME VARCHAR2 (30) NOT NULL, NAMJPRINCIPAL VARCHAR2 (30) NOT NULL,

PRIMARY KEY ( CDEJROLENAME, NAM PRINCIPAL )

CREATE TABLE TBJVCP J30FTWARE ( CDEJSOFTWARE VARCHAR2 (10) NOT NULL,

TXT_VERSION VARCHAR2 (10) NOT NULL,

CDE_CERT CATIONTYPE VARCHAR2 (20), CDE J.ERTMCATIONCODE VARCHAR2 (20), TXTJDOCUMENT LONG NOT NULL,

DTE_CERTIFICATIONDATE DATE,

PRIMARY KEY ( CDEJSOFTWARE, TXT_VERSION )

CREATE TABLE TBJVCP JWORK ( CDEJWORK NUMBER (38) NOT NULL, DTΈ CREATED DATE NOT NULL,

DTE_ACTIONDUE DATE,

CDE_ALLOCATED ASSESSOR VARCHAR2 (20) NOT NULL, CDE_PRIORITYTYPE VARCHAR2 (20) NOT NULL, CDE jPRIORITYCODE VARCHAR2 (20) NOT NULL, CDEJREPALRAREATYPE VARCHAR2 (10) NOT NULL, CDEJREPAIRAREA VARCHAR2 (20) NOT NULL, CDE_WORKREASONTYPE VARCHAR2 (20), CDE_WORKREASONCODE VARCHAR2 (20), CDE_QUOTESTATUS VARCHAR2 (20), CDE_CLAIM VARCHAR2 (20),

CDEJREGO VARCHAR2 (10),

CDEJREPAIRER VARCHAR2 (20),

NUMJREINSTATEMENTSEQ NUMBER (38), TXT_QUOTENO VARCHAR2 (20), NUM_QUOTESUMMARYSEQ NUMBER (38), CDE_PROGRESSTYPE VARCHAR2 (20), CDEJPROGRESSCODE VARCHAR2 (20),

PRIMARY KEY ( CDE_WORK )

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

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.

5. A computer system according to claim 1, where monitoring software runs continuously to check for errors in the validation done by the data collector.

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

Quote S ummaryRate

Invoice

QuoteNote

ClaimVehicle

System Parameter Tables

Code

CodeType

Action ActionStatus

QuoteStatus

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

CCISAudit (temporarily implemented) ErrorLog

User Defined Information

QuoteUserDefined QuoteltemUserDefined

10. 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 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.

15. 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;-

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.

20. 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.

25. A method according to claim 17, where the second database has one or more of the following tables:

Core Tables

Work RequestForQuote

QuoteSummary Quoteltem Quote S ummaryRate Invoice QuoteNote ClaimVehicle

System Parameter Tables

Code

CodeType

Action

ActionStatus

QuoteStatus

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

CCISAudit (temporarily implemented) ErrorLog

User Defined Information

QuoteUserDefined QuoteltemUserDefined

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 Quoteltem records for each QuoteSummary and therefore the QuoteSummary primary key forms part of the Quoteltem 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