ACORD P&C/Surety XML Training

ACORD P&C/Surety XML Training Mark Orlandi

©AC O RD 2 200 005. 5.

Agenda g g g g g g g g g g g g

Who Is ACORD? Introduction Business Functions Definitions Message Design Party Design (Persons & Organizations) Policy Design Data Types Naming Conventions Framework SPX (Service Provider eXtensions) Certification+

SLIDE 2

Agenda g g g g g g g g g g g g

Who Is ACORD? Introduction Business Functions Definitions Message Design Party Design (Persons & Organizations) Policy Design Data Types Naming Conventions Framework SPX (Service Provider eXtensions) Certification+

SLIDE 2

Goals g

Get Programmers and Business Analysts comfortable with the design h

g

Describe and define the standard features and layout h

g

Not to teach XML or SAX/DOM

Not to teach how to use the Commercial Auto Business Message

Point out minimal requirements h h

Describe the options Describ Des cribe e the “gotc “gotcha’s ha’s”” alo along ng the way way

SLIDE 3

ACORD P&C/Surety XML Who Is ACORD? Mark Orlandi

©AC O RD 2005.

ACORD vs. ACCORD g

g

ACORD facilitates Standards development and use for the insurance, reinsurance, surety and related financial services industries. ACCORD is a vehicle available from Honda

SLIDE 5

Who is ACORD? g

g

Association for Cooperative Operations Research & Development Independent and Objective Association h

Serving the Industry since 1970

h

Facilitating Industry-Driven Standards (Carriers, Agents, Solution Providers, Associations)

h

Not For-Profit Corporation

h

Anti-trust Exemption

SLIDE 6

ACORD Membership g g g g g g g

P&C Insurers Life Insurers Reinsurers Independent Agencies Global Brokers Suppliers Lloyds Syndicates

g g g g g g g

Trade Associations Rating Bureaus Financial Service Orgs Risk Managers Service Bureaus Lab Companies Consulting Firms

Plus alliances with numerous industry and standards organizations around the world.

SLIDE 7

ACORD Members….. Leading the Industry g

g g

g g

90% of Top 10 and 64% of Top 25 AM Best Life and Annuity 80% of Top 10 and 72% of Top 25 AM Best P&C 70% of Top 10 and 64% of Top 25 Global Reinsurers Top 5 Brokers representing 80% of the business Over 15,000 independent agents And Growing!!

SLIDE 8

Alliances and Relationships Cross-Industry

Property and Life Insurance and Casualty Insurance Wealth Management

ANSI

CSIO

CLIEDIS

ebXML

eEG7

DTCC

HRXML

IDMA

FUNDSERV

IAA

ISO

LOA

IFX

MISMO

MIB

OMG

POLARIS

NAILBA

UN/EDIFACT

RIMS

LOMA

W3C

WCIO

Se e A C O RD St a n d a rd s Atlas fo r D e t a i ls

SLIDE 9

Evolution of . . .

2002 + Convergence Life/P&C/RLC 1970’s - Forms

2001 Reinsurance

1980’s - AL3 1990’s - AL3 Implementation

2001 XML (P&C)

1996 - Life Standards 1998 XML (Life)

10 © C opyright AC ORD SLIDE 10

C orp.

Why Standards? g

g

g

Decrease Costs h Reduce time/cost to implement partner interfaces h Reduce data transaction/translation errors h Reduce human intervention in routine biz processing Increase Sales/Revenue h Make it easier to do business with you h Decrease time to issue = fewer “not takens” Improve Service h Develop “single-view” of disparate systems h Increase richness of shared information h Reduce cycle time between upgrades in data share SLIDE 11

Business Issues g

Proving Return On Investment (ROI) h

g

Analysts: Celent: $250 million in savings

Not a Single Quarter Investment h

Initially more expensive/time consuming

STANDARDS

Ever-increasing Incremental Cost

t s o C

Ever-decreasing CUSTOM

Incremental Cost

# Implementations / # Trading Partners SLIDE 12

Technical Issues g g g

Fear of XML Move from EDI to XML vocabularies “Not Invented Here” Syndrome h Generally – anxiety of moving from comfort zone to new techniques, strategies, tools and methods. h … but once bridged: h Faster integration, less technical grunt work (use tools!), more sophisticated & challenging work, ability to support more partner/internal interfaces, develop richer & more detailed info sharing

SLIDE 13

Fear, Uncertainty and Doubt g

XML is a an immature technology h

g

“ZML” is coming next h

g

Wrong – Gartner: “64% of all new integration projects are using XML” There is nothing on the horizon to indicate a new technology any time (Gartner/IBM Report)

What about UDDI, WSDL, SOAP, etc. h

h

They are all supporting technologies NOT disruptive technologies. They leverage and build on XML. It all starts with XML!

SLIDE 14

Best Practices g

Team Approach h

g

Start with an Internal Project h

g

g

Involve a Business Leader, Technologist and Operations Guru Practice on easy, low-hanging fruit

Leverage experience of Standards experienced vendor and/or consultant Dedicate internal resources to learn & support spec. (at least part-time) h

Find internal XML supporters – ACORD is the vocabulary they are looking for

SLIDE 15

Best Practices cont’d g

Scour web for XML resources h

Microsoft.com, XML.ORG, W3C.org and much more…

g g

g

g

Survey your vendors for their plans & resources Participate in process – ACORD Standards meetings (WG’s, Mtgs, etc.) Get all the WG deliverables, guides and other resources off the ACORD member site area Support ACORD h

Join with your partners to build “network effect”

SLIDE 16

XML Design Goals 1. 2. 3. 4.

XML shall be straightforwardly usable over the Internet. XML shall support a wide variety of applications. XML shall be compatible with SGML. It shall be easy to write programs which process XML documents. 5. The number of optional features in XML is to be kept to the absolute minimum, ideally zero. 6. XML documents should be human-legible and reasonably clear. 7. The XML design should be prepared quickly. 8. The design of XML shall be formal and concise. 9. XML documents shall be easy to create. 10. Terseness in XML markup is of minimal importance. 17 © C opyright AC ORD SLIDE 17

C orp.

AL3 (Automation Level 3) Example 5DRV176 F200015BPIF10001 ? 0001CJOSEPH M GALLO ? ? OH? 650422M?? ?? 19650422

Hard to read Rigid Versioning problems

• All on one line and run together Ref Data Name Description Start Length ------------------------------------------------------GROUP Driver Group 000 193 HEADR Header 001 030 DRVNO Agency Driver's Number 031 004 DRVNO Company Driver's Number 035 004 DRVNM Driver's Name 039 060 SSNO Social Security Number 099 009 LICNO Driver's License Number 108 025 STATE Licensed State 133 002 ZZMOV Deleted - Date Licensed 135 006 ZZMOV Deleted - Date of Birth 141 006 SEXCD Driver Sex Code 147 001 LICCD License Class Code 148 001 ZZMOV Deleted - Date Hired 149 006 DRTCD Driver Type Code 155 001 FIXID Fixed Identifier 156 005 BIRDT Date of Birth 161 008

18

© C opyright AC ORD SLIDE 18

C orp.

XML Example

Easier to read Free use of whitespace

Gallo, Joseph M. 303508921
Home 108 Dawson St Philadelphia PA 19130 USA
Joseph Michael Gallo Single Male 1965-04-22

Structure can be checked with standard tools and a schema or DTD


C orp.

ACORD P&C/Surety XML Introduction Mark Orlandi

©AC O RD 2005.

Agenda – Introduction g

Time-line

g

Background

g

The Standard

g

Public vs. Members Only

g

Content Organization

g

Deliverables

g

XML Messages

SLIDE 21

Timeline - ACORD PCS V1.x XML g

1999 h

g

2001 h

g

ACORD announced plans to develop an XML Standard for PCS ACORD published PCS XML V1.0.0

2006 h

The V1.x Standard is in daily use by dozens of insurers and vendors and thousands of agents

SLIDE 22

Background g

Originally planned as Chapter 9 of IFX http://www.ifxforum.org

g

Compliance vs. Compatibility

g

AL3 Data Dictionary

g

Old and New Influences: h

IFX rules - no attributes

h

AL3 - inconsistent code list values

h

W3C - XML and others

SLIDE 23

ACORD Specification Release Public

Spec Document Adobe (PDF) Format

Members Only* * Includes Public Materials

Spec Document Help Format 24 © C opyright AC ORD SLIDE 24

C orp.

Content: The Basics g g g g g g g g

Ch 1) Ch 2) Ch 3) Ch 4) Ch 5) Ch 6) Ch 7) Ch 8)

Introduction - Governing Principles Definition of Terms Data Type Definitions Documentation and Naming Conventions Framework Specification (IFX) Transport and Packaging Specification XML Format Specification Standard Features

SLIDE 25

Content: Insurance Business Data g g g g g g g g

Ch 9) Common Service Ch 10) Insurance Service Ch 11) Surety Service Ch 12) Claims Service Ch 13) Accounting Service Ch 14) Service Provider Extensions Service Ch 15) Code Lists Revision History

SLIDE 26

Documentation Deliverables The Specification / Standard

g

h

Adobe formatted file

h

Windows Help file *

g

DTD

g

Schemas / 4 Layouts (all draft) *

g

* ACORD Members Only

h

One set includes TargetNamespace

h

One set omits TargetNamespace

Dump Of ACORD database * h

Includes DTD for layout

SLIDE 27

Schemas: 4 Layouts / 2 Sets Documentation / Tag Descriptions

Code List Data / Code Values

Yes

Yes

ACORD Delivery ACORD Members

Yes

No

ACORD Members

No

Yes

Public

No

No

Public

One set includes TargetNamespace One set omits TargetNamespace SLIDE 28

Schema “Slicing” Each schema contains the entire spec Many users implement only one LOB or spec portion and have requested smaller schema files

g g

g

ACORD can provide you with style-sheets (xsl files) that allow you to output smaller slices of the large schema

SLIDE 29

Conclusion g

Time-line

g

Background

g

The Standard

g

Public vs. Members Only

g

Content Organization

g

Deliverables

g

XML Messages

SLIDE 30

ACORD P&C/Surety XML Business Functions Mark Orlandi

©AC O RD 2005.

Agenda – Business Functions g g

Service Concept Business Messages h h h h h h h

g

Personal Lines Commercial Lines Commercial Schedules Claims Surety Miscellaneous Framework

Conclusion

SLIDE 32

Services: Designed to “Group” Messages g

g g g g g g

Base Service – web services oriented h Pending Response Inquiry Rq/Rs h Service Profile Inquiry Rq/Rs Claims Service Common Service Insurance Service Surety Service Accounting Service Extensions Service h Service Provider Extensions (SPX) SLIDE 33

Personal Lines g g g

g g

g g

Auto Dwelling Fire Homeowners h includes mobile home Inland Marine Package Policy h Any combination of the mono-lines Umbrella Watercraft

SLIDE 34

Commercial Lines g g g g

g g g g g

Auto Aviation Boiler & Machinery Business Owners Policy (BOP) Crime Directors & Officers (D&O) Employers Liability (EPLI) Errors & Omissions (E&O) General Liability (GL)

g g

g g g g

Inland Marine Package Policy h Any combination of the mono-lines Product Liability Property Umbrella Workers Compensation (including stat reporting)

SLIDE 35

Commercial Schedule Submit/Respond Pairs g g g g g g g

Drivers Named Insured and Locations Property Umbrella underlying coverage Vehicles General Liability Workers Compensation

SLIDE 36

Claims Message Sets g g g

g g g

Claims Download Claims Investigation Claims Notification (FNOL / FROI) h First Notice Of Loss h First Report Of Injury Claims Subsequent Report Claims Status Inquiry Loss Run

SLIDE 37

Surety Message Sets g

g g g g

Submission / Notify Message Sets h Mimics Insurance Message Set Design 8Quote / Add / Mod / Reissue / Renew 8Partial Image Cancellation 8Partial Image Reinstatement Inquiry Rate Sync Bond Sync Report Of Execution

SLIDE 38

Insurance - Miscellaneous g g g g g g g g g g g

Certificate Of Insurance Dwelling Valuation Farm Flood (not a line of business) Lender Replace Mod Policy Cancellation (partial image) Policy Reinstatement (partial image) Policy Finance Policy Inquiry Policy Sync Premium Audit SLIDE 39

Misc. Business Message Sets g

g

g

Accounting Message Sets h Billing Inquiry Common Message Sets h Account Inquiry h Activities & Notes Download h View Inquiry Service Provider Extensions (SPX) h SP Extensions Inquiry h SP Extensions Sync

SLIDE 40

Framework Message Sets g g

g

Sign On Base Service Message Sets h Service Profile Inquiry h Pending Response h Message Set Request * h Message Set Response * Sign Off * Associated with Notify Messages

SLIDE 41

Conclusion – Business Functions g g

Service Concept Business Messages h h h h h h h

g

Personal Lines Commercial Lines Commercial Schedules Claims Surety Miscellaneous Framework

Conclusion

SLIDE 42

ACORD P&C/Surety XML Definitions Mark Orlandi

©AC O RD 2005.

Agenda – Definitions g g g g g g g g g g

XML Basics Definitions - Terms XML Basics - with Terms Definitions Sources Sample Aggregate Services Aggregates vs. ENTITIES Attributes Empty Elements Versioning

SLIDE 44

XML Basics Shakespeare start tag data end tag Shakespeare William

SLIDE 45

Definitions - Terms %ENTITYA %ENTITYB %ENTITYA SLIDE 46

XML Basics - with Terms Shakespeare William = element = aggregate

SLIDE 47

Definitions Sources Term: %ENTITY @Attribute or Type

Source: IFX W3C, IFX W3C, IFX W3C, IFX IFX

Business Message Service Document or XML Stream

IFX IFX W3C

SLIDE 48

Sample Aggregate

SLIDE 49

Services: Designed to “Group” Messages g

g g g g g g

Base Service – web services oriented h Pending Response Inquiry Rq/Rs h Service Profile Inquiry Rq/Rs Claims Service Common Service Insurance Service Surety Service Accounting Service Extensions Service h Service Provider Extensions (SPX) SLIDE 50

Aggregates vs. ENTITIES Aggregates Only

ENTITY Usage %NAMEENTITY;

%NAMEENTITY

Note: Entity Name not included 51 SLIDE 51

Attributes (Part 1 - W3C) g

Example:

Ross Elizabeth Betsy g

This is permitted in XML, but not used in this manner in ACORD XML

SLIDE 52

Attributes (Part 2 - ACORD) g g

g

The “id’s” serve to uniquely identify tags h (1 id per tag).

g

The “Ref’s” serve as pointers to “id’s”.

g

Both documented in spec with “@” symbol.

SLIDE 53

Referencing Information within the Data

Single Data Stream

54

© C opyright AC ORD SLIDE 54

C orp.

Empty Elements (XML Term) Not Allowed or

Allowed g

g

Tag is defined with data type: Empty Only tag defined as Empty: Notify Replacement Messages

SLIDE 55

Tag Definitions g g

1:1 ratio (tag name: tag description) exception: Supplemental Description h text unique to tag context h text reads “As used here…”

SLIDE 56

Deprecate g

g

g

ACORD term

Element or code exists in the standard, but something has replaced it or is preferred to be used Description should contain information about the replacing element or code

SLIDE 57

Specification Versioning g

g

Three level versioning scheme h version 2.0.0 - defined as breaking backwards compatibility h release 1.1.0 - voted upon changes, backward compatible h maintenance 1.0.1 - minor changes like documentation cleanup Minimum Requirement h Version 1.x lived for 18 months or longer h Requirement exceeded

SLIDE 58

Conclusion g g g g g g g g g g

XML Basics Definitions - Terms XML Basics - with Terms Definitions Sources Sample Aggregate Services Aggregates vs. ENTITIES Attributes Empty Elements Versioning

SLIDE 59

ACORD P&C/Surety XML Message Design Mark Orlandi

©AC O RD 2005.

Agenda – Message Design g

Processing Environment

g

Services

g

Messages Inventory (Scope)

g

Message Design h

Line Of Business

h

Quote, New Business, etc.

SLIDE 61

Processing Environment Client (e.g. Agency)

Server ACORD Request Message

(e.g. Insurer)

I BM

Database IB M

Database

ACORD Response Message 62 © C opyright AC ORD SLIDE 62

C orp.

Messages Are Contained within Services g

g

g

g

g

Accounting Service h Accounting Messages Claims Service h Claims Messages Common Service h Common Messages Insurance Service h Insurance Messages Surety Service h Surety Messages

SLIDE 63

Messages Inventory (Scope) g

Personal Lines

g

Commercial Lines

g

Commercial Schedules

g

Claims

g

Surety

g

Miscellaneous

g

Framework

SLIDE 64

Insurance (Typical LOB Message Sets) g

Lines Of Business h

Commercial 8ex.

h h g

Commercial Auto

Farm Personal

Transaction Type h h h h h h

Quote Add (new business) Mod (modification - policy change) Reinstate (overrides a cancellation) Renew Reissue (correction to a previous issue) SLIDE 65

Insurance Messages g

Typical LOB Message Sets h

Submission Message Sets 8Quote

h

/ Add / Mod / Reinstate / Reissue / Renew (6)

Notification Message Sets 8Update

Message Sets

– Add / Mod / Reissue / Renew / Reinstate (5) 8Replace

Message Sets

– Add / Mod / Reissue / Renew / Reinstate (5) g g

6 + 5 + 5 = 16 Message Sets (transactions) 16 x 2 = 32 individual messages h

1 set of requests / 1 set of responses SLIDE 66

Basic Message Design - Insurance Request Message

Response Message

<*LineOfBusinessRq>

<*LineOfBusinessRs>

%MSGRQINFO Required

%MSGRSINFO

Required

%*POLINFO

%*POLINFO

Optional Echo

Required

Optional

• Represented by actual Line Of Business • Surety, Commercial Schedules, Dwelling Valuation, and Package Policies are different designs • %PERSAUTOPOLINFO • Inconsistency due to administrative error 67 © C opyright AC ORD SLIDE 67

C orp.

Basic Message Design - Insurance 10.3.3.5.1.1 Request Personal Auto Application Submission Request Base Type: (PersAutoPolicyAddRq_Type) Tag

n o i t a c i f i c e p S o t r e f e R

Type

Usage

Description

(%MSGRQINFO;)

Entity

Required

Message Request Information Entity Revision History: MR2907

UUID_NoID

Required

Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Revision History: MR2907

DateTime

Required

The date/time the request was created. This is the client date. Revision History: MR2907

DateTime

Optional

The date on which this transaction takes effect. Revision History: MR2907

OpenEnum

Required

Currency Code. The applicable codes are defined by International Standards Organization (ISO-4217). Revision History: MR2907


C orp.

Insurance – Message Level LOB Entities %*POLINFO Entity (*Actual Line of Business)

Optional Repeating

Required Repeating

<*Policy> or

Required

Required Repeating

<*LineBusiness> * Actual Line of Business

Required

Optional Repeating

Optional Repeating

Comml. Lines has exception s to t his design d ue to handli ng of Lo cation Data 69 © C opyright AC ORD SLIDE 69

C orp.

Conclusion g


g

Services

g

Messages Inventory (Scope)

g

Message Design h

Line Of Business

h

Quote, New Business, etc.

SLIDE 70

ACORD P&C/Surety XML Party Design Mark Orlandi

©AC O RD 2005.

Agenda – Party Design g

Philosophy: Tags vs. Codes

g

Party Design basics

g

General Party Information

g

Miscellaneous Parties

SLIDE 72

Parties (individuals or organizations) g g g g

, h

g

%PCBASICDRIVER

*All contain

SLIDE 73

Producer g g g

Item ID Info General Party Info Producer Info h Contract number h Placing Office h License Info h Role Code

SLIDE 74

Producer

75 © C opyright AC ORD C orp.

Item ID Information g g g g

Agency ID Information Insurer or Carrier ID Information System UUID Other Identifiers

3701234 987654 SLIDE 76

General Party Information g g g g

Name Information Address Preferred Contact Times and Methods Communications (Phone, email, mail)

SLIDE 77

General Party Info


Name Information g g g

g g g

Commercial Name Person Name Family Name

}

XOR’d

Legal Entity Code Government Tax Identifiers Non-Tax Identifiers

SLIDE 79

Name Info


g

g

g

Probably would have been better named “” May be used for commercial names or individuals. Trading Partner issues: h

Driver Names OK in this format?

SLIDE 81

Address g g

Type Code 4 address/street lines h h

g g g

}

XOR’d (9-11 reporting issues)

City, State and Postal Code Codes or strings for State and Country Longitude and Latitude

SLIDE 82

Address


General Party Example Joshua Tree Agency FEIN 35-9348745 USA Small Irving StreetAddress 5275 Franklin St Philadelphia PA 19106 +1-518-5559876

84

© C opyright AC ORD C orp.

Insured or Principal g g g

Item ID Information General Party Information Insured or Principal Information h h h h

g

Role Code Person Info Business Information Principal Information

Time known by Agent

SLIDE 85

Insured or Principal


Business Info


Person Info


Principal Info


Insured or Principal Example 123-45-6789 Ross Elizabeth Griscom Ms. Betsy SSN 123-45-6789 MailingAddress 239 Arch Street Philadelphia PA 19106

BillingAddress PO Box 123 Philadelphia PA 19106 +1-215-6275343 …


g

Can accommodate: h

h

Multiple Names w/one address 8Within one instance of , repeats for each and there would be one instance of One or More Names w/multiple addresses 8repeat for each name/address pair.

SLIDE 91

Miscellaneous Party g g g

Item ID Info General Party Info Miscellaneous Party Info h h

Role code Sub-role code

SLIDE 92

Conclusion – Party Design g

Philosophy: Tags vs. Codes

g

Party Design basics

g

General Party Information

g

Miscellaneous Parties

SLIDE 93

ACORD P&C/Surety XML Policy Design Mark Orlandi

©AC O RD 2005.

Agenda – Policy Design g

Common Policy Data

g

Commercial vs. Personal Lines

g

Line Of Business

g

Underwriting Questions

g

Coverages

g

File Attachments

SLIDE 95

Policy Information g g

* Both begin with single occurrence of %PCPOLICY

SLIDE 96

Property Casualty Policy (PCPOLICY) g g g g

g

g

Quote Information Additional Interests Miscellaneous Party Underwriting Questions and Answers Personal or Commercial Application Info Accident, Violation, driver information for Personal Auto uses

g

g g g g g g g

Policy Number and Version Product Code Billing Information Credit Score Info Renewal Information Binder Form Previous Loss Line of Business Info

SLIDE 97

Personal Policy - pt 1 • Policy Information • Codes • Contract Information • Billing Information • Renewal Information


Personal Policy - pt 2 • Form Information • Loss Information • Payment Information • Quote Information • Binding Information • Additional Interests • Underwriting Questions


Personal Policy - pt 3


Commercial Policy Supplement - Business Information - Coverage Requirements


Line of Business g g

Coverage Information Additional LOB Information h

Auto 8Driver 8Vehicle 8Specific


SLIDE 102

Underwriting Questions g

QuestionAnswer Aggregate Response Code Value NA NO NOTANS YES

1.1

Code Descripti on Not Applicable No Not Answered Yes

ResponseIndicator

Code Value

AGLIA01 AGLIA02 AGLIA03 AGLIA04 AGLIA05 AGLIA06 AGLIA07

Code Description Independent contractors hired to perform any farming operations? Any part of farm used or leased for organized recreational use? Does Applicant Build, Repair or Design Machinery, Equipment or Systems for Anyone at a Charge or Fee? Does Applicant Mix, Process, Slaughter, Butcher or Otherwise Prepare for Any "End Consumer" His or Any Other Grower's Product? Does Applicant Handle any Product, such as Seed, Fertilizer, Sprays, etc. for Resale? Are Any Contract or Service Operations Performed for Others such as Snow Removal, Tilling, Excavating, or Ditching? Are the Farm Premises Open to the Public for Activities such as, Road Side Stands, "U-Pick", recreational, "Rent-a-Garden", auction, sales, show, food, etc.?

SLIDE 103

Coverage Information g g

Coverage Code - Coverages list Coverage Option Code h h h

g g g g

Option type code - Option Benefit list Option code - Coverage Option list Option value - number of or Y/N indicator

Limits Deductibles Form Information Coverage Matrix Implementation Guide

SLIDE 104

Coverage Matrix Implementation Guide g

g

Lists data requirements associated with each coverage code and XML handling Critical Code Lists: h h

g

Data Requirements: h h h

g

Coverages List CoverageOption List Option Types / Codes Limit Data (“Types” and “Applies To”) Deductible Data (“Types” and “Applies To”)

Refer to Guide for detailed examples

SLIDE 105

Coverage


Coverage and Option Codes CoverageOption

Coverages Sublist

Code Value

Code Description

Sublist

Code Value Code Description

Personal Lines ALARM Premises Alarm Alarm Type Codes List Property - Homeowner Alarm Type Codes List and Dwelling Fire Coverages List Alarm Type Codes List

C CC

Alarm Type Codes List

CR

Alarm Type Codes List Alarm Type Codes List Alarm Type Codes List

L P R

Anti-Lock Braking System Type List

02

Anti-Lock Braking System Type List

04

Business Automobile and Truckers List

FG

Business Automobile and Truckers List

MI1

Personal Lines - Property - Homeowner and ALC Dwelling Fire Coverages List

Assisted Living Care Coverage

Personal Lines - Property - Homeowner and APMP Dwelling Fire Coverages List

Additional for Policy Minimum Premium

Personal Lines - Property - Homeowner and APP Dwelling Fire Coverages List

Additional Personal Property Secondary Residence

Personal Lines - Property - Homeowner and APPAW Dwelling Fire Coverages List Personal Lines - Property - Homeowner and BAA Dwelling Fire Coverages List

Additional Amt. of Pers. Prop. Away From Premises Building Additions & Alterations (HO4 or 4A)

CO

Central Alarm Combination burglar alarm and fire alarm that includes a central option (used in Texas) Combination burglar alarm and fire alarm alarm that includes a local (used in Texas) Combination burglar alarm and fire alarm that includes a remote option (used in Texas) Local Alarm Police Alarm (not used in Texas) Remote Alarm (Texas only) 2 Wheel anti-lock braking system 4 wheel anti-lock braking system Full Glass Michigan Municipal Volunteer coverage included


COLL 500 FL COMP 100 FL

Coverage Example

….


File Attachment Information g

g

g g g g g

Additional Document sent in support of an application Generally an image of a form, certificate, photo, or receipt Item ID Info Description and Type Code Responsibility Code MIME Content type and Encoding File name

SLIDE 109

File Attachment AttachmentType Code Value

040 041 042 610 AER APP APR ARP ATD BCL BFA BLT BOS CAB

Code Descripti on ACORD Residential Property Valuation Survey ACORD Residential Property Replacement Cost Worksheet Boeckh Square Foot Method ACORD Residential Property Replacement Cost Information Supplement Premium Payment Supplement Accepted Endorsement/Rider Appraisal/Bill of Sale Appraisal Agings of Receivables/Payables Anti-Theft Device Certificate Bank Credit Line Agreement Burglar/Fire Alarm Certificate Bank Letter Bill of Sale Condo Association by Law's


File Attachment Example DV-12345-09102000.jpg Appraisal for restored 1968 Shelby Cobra APP AG image/jpeg canon7.jpg


XML and Attachments .... f81d4fae-7dec-11d0-a765-00a0c91e6bf6 f81d4fae-7dec-11d0-a765-01a0c61f6bd5 ... Foo Fighter

canon7.jpg

image/jpeg canon7.jpg

In memory or an XML file Auto Quote.xml


Conclusion – Policy Design g

Common Policy Data

g

Commercial vs. Personal Lines

g

Line Of Business

g


g

Coverages

g

File Attachments

SLIDE 113

ACORD P&C/Surety XML Data Types Mark Orlandi

©AC O RD 2005.

Agenda – Data Types g

Simple Data Types

g

Complex Data Types

g

Measurement

g

Currency

g

SLIDE 115

Chapter 3 - Simple Data Types g

C-xx - character - various string lengths h h

g

NC-xx - narrow character, various string lengths h

g

h

g

1 or 0 the only allowed values “not answered” is value if not provided

Long - 32 bit positive or negative integer (whole number) h

g

ASCII characters

Boolean - (true/false) h

g

Unicode Characters, can contain § Æ Ç à ŕ £ etc. < and & need to be escaped < and &

-2147483648 to +2147483647

Decimal - 15 digits excluding the sign or decimal Percentages – value must be divided by 100 before use h h

PercentLong – integer values PercentDecimal – integer or decimal values SLIDE 116

Chapter 3 - Complex Data Types g

Date and Time - Gregorian Calendar, 24hr clock h h h h h h

g

Year = 2002 YrMon = 2001-02 Date = 2001-02-05 Time = HH:mm:ss.ffffff±HH:mm DateTime = YYYY-MM-DDTHH:mm:ss.ffffff±HH:mm Timestamp - same format as DateTime, but no intended business meaning

Enumerated Types - code list values h h

Closed Enum - specific values only allowed Open Enum - specific values but other values allowed as well

SLIDE 117

Chapter 3 - Complex Data Types - cont g

Phone Number - 32 narrow characters h

g

+1-800-5556789+739

URL - up to 1024 narrow characters h h

contains a protocol identifier (http:) need to watch for Internationalized URLs (IURL) that allow Unicode characters

SLIDE 118


Identifiers h h

Assigned Identifier - use or other elements as defined Universally Unique Identifier - (UUID or GUID) - 36 narrow character string - system generated 8f81d4fae-7dec-11d0-a765-00a0c91e6bf6 8Dashes

h

are required Transient Identifier - used in the XML stream not reusable outside the stream - must be unique in stream 8Must

start with a letter, and must be unique in data stream 8Based upon the XML ID attribute type - virtually every element in the Business Message can have ID - see sec 3.9.2 8Create only if used in stream 8

SLIDE 119


Identifier References - Reference to a transient identifier (ID attribute) h

Identifier Reference 8XML

IDREF type - single value 8ID value referenced must exist in data stream 8 h

Multiple Identifier References 8XML

IDREFS type - multiple values separated by whitespace 8ID values referenced must exist in data stream 8

SLIDE 120


XML ID attribute values: h h

Must start with: _ letter : Follow by one or more: letter digits .-_: and Unicode values Valid ID values v1 vehicle1 :1 _1 vehicleÇß

Invalid ID values Çßvehicle 1v -v1

SLIDE 121

Very Complex Data Types g

Entities as data types - Complex types h

h

h

h

h

%DURATION 8, , , %CURRENCY 8, , , %MEASUREMENT 8, , %FORMATTEDNUMBER 8 %BINARY 8,

SLIDE 122

Entities used as Data Types


Entities as Data Types - cont


Entities as Data Types - cont


Measurements

%MEASUREMENT

Optional

The total area of this building, counting both stori es above ground and basements. As us ed here, the expected measurement i n the USA is square feet.

%MEASUREMENT

Optional

The total area of all th e basements in this building. As used here, the expected measurement i n the USA is square feet.


Using a Measurement USD

202.5 HAR 0.405 ...

...

Number of Hectares when converted New Unit of Measurement Conversion Rate from Acres to Hectares Measurement that references the conversio n rate.

500

...

...

Number of Acres


C orp.

Currency Number of decimal places of conversion is calculated to


Using a Currency

USD DEM 1115 2.23 NY Times 2001-07-31 ...

... 500 ...

Default Currency Units

Conversion Rate Dollars to Marks

Deductible References a conversion rate

...

Dollar Amount of 129 Deductible

© C opyright AC ORD

SLIDE 129

C orp.

Code Lists and Aggregate g

A code list is a lists of values h h h

g g

g

ACORD maintained Outside lists (ISO, Federal, State, etc.) Company Unique

Sub Lists in Coverages & Coverage Options Extend/Override with SPX or Extend/Override with better to use SPX

SLIDE 13 130 0

Using a Code List

$ Dan's Dan's Currency Values Values 1.0< tVersion>1.0 US Dollars

Reference Reference to a element that describes the value of the code I have used A desc d esc r i p ti o n o f the code list th at I'm using instead instead of th e standard standard currency code list

DE-MARKS 1115 2.23 NY Times 20010731

...

... ConversionRateRef="cvrate-1"> 500 ...

...

131 13 1 © C o pyri pyright ght AC A C O RD C o rp.

Conc Co nclu lusi sion on – Da Data ta Ty Type pess g

Simple Data Types

g

Complex Data Types

g

Measurement

g

Currency

g

SLIDE 13 132 2

ACORD P&C/Surety XML Naming Conventions Mark Orlandi

©AC O RD 2005.

Agenda – Naming Conventions g

Chapter 4 Overview

g

General Naming Rules

g

Message Naming Rules

g

Standard Abbreviations

g

Non-Abbreviations

g

Custom Tag Names

g

Code Lists & Code Values

SLIDE 134

Chapter 4 - Overview g g g

Type Column Usage Column Naming Rules h h h

g g g

General Tag Names Codes

Extension & Customization Mandatory & Optional Elements Rules For Data Content

SLIDE 135

General Naming Rules – (Elements/Tag Names) g g

Should be designed for clarity - readable Mixed Case (a.k.a. Camel Case) h h

g

ex. PersAutoQuoteInqRq Always start with a capital letter.

Must be Unique regardless of case h

vs. 8W3C

allows this - ACORD does NOT!

8XML is case-sensitive h

g

No names the same between Entities, Aggregates, or Elements/Tags, etc.

Must follow standard abbreviations when possible

SLIDE 136

Message Naming Rules g g

Message names end with “Rq” or “Rs” Message names are constructed in the follow way: h h h h h

Line Of Business name – Personal/Comml Auto Object name – Policy, Quote, etc. Property name - Inquiry Method name – Add, Modify Direction – Request or Response 8Example:

SLIDE 137

Standard Abbreviations g g g g g g g g g g g g g

g g

Acct - account Addr - address App - application Amt - amount Avg - average Bldg - building Cd - code Comml - commercial Cur - currency Desc - description Dt - date Dwell - dwelling EC - extended coverage Exp - expiration Id - identifier

g

g g g g g g g g g g g g g

Ind - indicator (Boolean) Info - information Inq - inquiry LOB - line of business Misc - miscellaneous Msg - message Multi - multiple Op - option Pct - percentage Pers - personal Pkg - package Pref - preferences Prov - province Prem - premium

g g

g g g g g g g

g g

Prod - product Ref(s) - reference(s) (attribute) Res - resident Rq - request Rs - response Sess - session Svc - service Sync - synchronization UUID - universally unique identifier Veh - vehicle WorkComp - workers compensation


Don’t Abbreviate g g g g g g g g g g g g g g g g g

Accessory Additional Anniversary Basic Bond Connection Construction Contract Contractors Coverage Discount Distance Driver Equipment ErrorsAndOmmisions Estimated History

g g g g g g g g g g g g g g g g

Individual(s) Insurance Interest Interior License Watercraft Year(s) or Yrs Schedule Territory Total Transaction Location Material Maximum Number or Num Permanent

g g g g g g g

Policy Premium or Prem Quote Rate Rating Reinstatement Resident


Naming Rules – Custom Tags (Part 1) g

g

Names should be based on established naming conventions and use a name to designate the organization that developed the tag. All custom tag names must have a company specific prefix h h

Avoids potential collisions with ACORD names or other trading partner custom tags SPXPrefix is how this is referred to in the spec 8Reverse

Domain name and add an Underscore 8Example: ABC Corporation’s would use – Domain name: ABC.com – Prefix that must be used: com.ABC_ b

SLIDE 140

Naming Rules – Custom Tags (Part 2) g g

Refer to Chapter 14 (SPX) for more details Note: This was developed before Schemas were released and there was a good way to use Namespaces. This value works like a namespace prefix, but it is unique to ACORD.

SLIDE 141

Codes - Code List Values g

g

Should be Mixed (Camel) Case - Always begin with a capital letter Should be mnemonic, but some situations a numeric value is best (for example deductibles or limits) h

Place most descriptive word first

8“RoofType” g

vs. “TypeOfRoof”

Must not include: h

Spaces

8“ AlarmType” not “ Alarm h h g

Type”

Non-alphanumeric characters Punctuation Characters like: % & _ - . , ; :

Must not end with: h h h

CodeList Code List SLIDE 142

Conclusion – Naming Conventions g

Chapter 4 Overview

g

General Naming Rules

g

Message Naming Rules

g

Standard Abbreviations

g

Non-Abbreviations

g

Custom Tag Names

g

Code Lists & Code Values

SLIDE 143

ACORD P&C/Surety XML Framework Mark Orlandi

©AC O RD 2005.

Agenda – Framework g


g

Request / Response Model

g

Message Status

g

Error Management

g

Extended Status

g

Changed Element Process

g

Pending Response

g

Modification Messages

g

Sign-On / Sign-Off

SLIDE 145

Processing Environment Client (e.g. Agency)

Server ACORD Request Message

(e.g. Insurer)

I BM

Database IB M

Database

ACORD Response Message 146 © C opyright AC ORD SLIDE 146

C orp.

Data Stream or Document XML Document - Request

ACORD Signon Request

XML Document - Response ACORD Status ? Signon Response

Service Request * Request UID xxx L OB Request *

Service Response* Status ? Request UID xxx LOB Response *

Signoff Request ? Signoff Response ?


Framework vs. Business Data Chapter 5

Chapters 9-14

SLIDE 148

Request / Response Model g

g

Server not allowed to send anything without a request from Client One or many messages allowed per XML stream or Document h

Can mix any combination of Request Messages from any combination of Services: g g g g

h g

Accounting Base Claims Common

g g g

Extensions Insurance Surety

Can mix personal lines with commercial lines

Keep in mind Pending Response Process and possible complexity

SLIDE 149

Service and Stream Level - Status Code Value

Code Description

Severity

0 1000

Success Duplicate

Info Error

1360 1380

Error Error

1620

Invalid within is invalid invalid not valid No

1740 1800

1420 1600

1820 1840 1880 1900 1910

Condition The service provider successfully processed the request. A request with this client message identifier has already been received and processed. The Service Provider name specified in a request was not found or is invalid The Service Provider Name specified within a customer identification aggregate is invalid.

Error Error

The customer identifier specified is invalid or not found. not valid or not supported.

Error

Ambiguous request, required

Authentication Failed

Error

The client could not be authenticated due to an incorrect login ID or password.

Service Not Authorized For Client Client Session Already In Progress No Client Session In Progress Client Locked Out

Error

Customer is not eligible to use this service. (I.e. Insurance or Surety)

Error

The service provider supports only one session at a time per customer and there is already an active session for this . Please try again later.

Error

The specified client does not have a session in progress.

Error

The service provider has received too many failed authentication attempts for this client or has detected other suspicious activity. Please call the technical support telephone number.

Password Change Required Must Change Password

Warn

The Logon is successful but the client must enter a new password before any other messages will be allowed.

Error

The client must change their password before any other messages will be allowed. [This means the password has expired or is invalid. We will not continue any processing.] The service provider does not support messages from the client application identified by .

2760

Unsupported Application Error ID Invalid Language Code Error

300

System Not Available

Error

The service provider for this transaction is not available due to a technical problem. Try again later. This code should only be used at the Root level in conjunction with a server failure.

351 500

Service Not Available Unsupported Service

Error Error

ACORD: The service selected is not available. Try again later.

1980

The service provider does not support the specified language or the language code is not valid in International Standards Organization 639.

The service provider does not support the specified service offering.

SLIDE 150

Status Locations

… … …

Top Level Status Information Sign on Level Status Information Service 1 Status Information

Transaction 1 Message Status Information

Transaction 2 Message Status Information Service 2 Status Information


Business Message Level - Error Management g g

Message Status File Based Error Recovery

SLIDE 152

Message Status Codes g

MsgStatusCd (applies to specific message) h h h h h h

Error - invalid data Rejected - refuse to add policy, unable to complete for business reasons ResponsePending - future processing Success - processed exactly as sent SuccessWithChanges - changes in data SuccessWithInfo - may include changes as well as request for more info

SLIDE 153

Extended Status g

g

Additional information about the Message Status code Points directly to the data element h

Uses XPath notation

Code Value

DataInvalid

Code Description The value(s) of the data element(s) element(s) identified are not valid for th is message. See the descripti ons of idrefs, , and for more information on identifying the data. The must be Error to use this cod e.

DataMissing

The data element(s) element(s) identified w ere missing fr om the stream and are required for th is message. See the descrip tions of id refs, , and for more info rmation on id entifyin g the data. Th e must be Error Error to use this code.

VerifyDataAbsence

The data element(s) identif ied were absent from the stream. This is alerted as an an unus ual condition and may warrant action action from the user to confirm the absence absence of data was correct or incor rect. (Note that since this is a "Succ ess" cod e, the message was successful ly processed. Service providers must no t use this to indicate a required action on th e part of the client.) See the descriptions of idrefs, , and for more information on identif ying the data. The must be SuccessWith SuccessWith Info to use this code.

VerifyDataValue

The data element(s) identi fied have a suspect valu e. This is alerted as an unusual cond ition and may warrant action from the user to confirm the value of data was correct or inco rrect. (Note that since this is a "Success" code, the message message was successfully processed. Se Service rvice providers must not use this to indicate a required required action on the part of the client.) Se See e the descriptions descriptions of idrefs, and for more information on identifying the data. The must be SuccessWithInfo to us e this code.

SLIDE 15 154 4

Changed Element Process g

Sometimes the server can make changes to the data. Examples: h h

g g

Auto - rated driver was the father father,, but it should should have been the teenage son Wrong territory code

Quotes are embedded in the data Standard way to indicate these changes h

Based upon XPath notation

SLIDE 15 155 5

f81d4fae-7dec-11d0-a765f81d4fae-7dec-11d0-a765-00a0c91e 00a0c91e6bf6 6bf6 f81d4fae-7dec-11d0-a765f81d4fae-7dec-11d0-a765-01a0c61f6bd5 01a0c61f6bd5 2001-09-13T9:30:00.000-5:00 USD

Changed Element

...

518-5559876 …

Griscom Ms. Betsy ... AUTOP

AB-234u548 AB -234u548 50000

SuccessWithChanges T +1-5185559876 D Deleted >Deleted th e value > A Added esc>Added the qu ote inf o as well as subelem subelements ents of the quote information

156 15 6

...

© C o pyri pyright ght AC A C O RD C o rp.

f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Missing Information

SuccessWithInfo f81d4fae-7dec-11d0-a765-01a0c61f6bd5 2001-09-13T9:30:00.000-5:002001-09-13T9:30:00.000-5:00 ansactionResponseDt> USD DataMissing Carrier requires this info before we can accept the policy based upon ... this quote. 518-5559876518-5559876 mber> InsuredOrPrincipal/InsuredOrPrincipalInfo/PersonInfo ...

... Ross Elizabeth GriscomGriscom > Ms. Betsy ...

AUTOP AB-234u AB-234u548 umber> 50000 ... ...

Insert an InsuredOrPrincipalInfo/PersonInfo here in the structure and all its subelements.

157 15 7 © C o pyri pyright ght AC A C O RD

C o rp.

Pending Response g g

g

MsgStatus Code of ResponsePending PendingResponseInfo sent in Response messages SuppressNotificationInd to suppress standard notification mechanisms h

g

g

Send a SignonRq to generate a SignonRs that might contain PendingResponseInfo

Each Pending Message will have a PendingResponseInfo block until retrieved or it expires Client in control SLIDE 15 158 8

Pending Response Flow Client

Server 1)

Monda onday, Receive ceives s one one docum docume ent with with 5 mess messa ages ges and forms the foll owin g response (1 (1 document): • PersAutoQuote rsAutoQuoteR Rs - Success uccess • PersAutoQuote rsAutoQuoteR Rs - Sucess ucess • ClaimsNotifica ClaimsNotificationRs tionRs - PendingRe PendingResponse sponse • DwellFireP wellFirePolicyModR olicyModRs s – PendingRe PendingResponse sponse • DwellFireP wellFirePolicyAddRs olicyAddRs – PendingRe PendingResponse sponse

Monda onday, Receive ceives s Re Respon sponse se and se sends quote quotes s to customer.

2)

Monda onday, y, late laterr in day day Cla Claim imsN sNot otif ific ica ation tionR Rs and DwellFirePolicyModRs DwellFirePolicyModRs now ready. ready.

3)

Tuesd uesda ay, Send ne new docu docume ment nt wit with h one one quot quote e request request and SuppressNotification SuppressNotification = true.

3)

Tuesd uesda ay, Answ Answe er ne new quo quote te requ reque est, st, no notifications sent.

4)

Tuesd uesda ay, Receive ceive quot quote e resp respon onse se,, send send to customer.

4)

5)

Wednesd dnesda ay, Ready to proce process ss back backlog log,, send send SignonRq, with no other content.

Wedne dnesda sday, Proce rocess ss empty mpty Sig Signo nonR nRq q and se send Pending Pending status information for ClaimsNotifi ClaimsNotifi cationRs and DwellFirePolicyModRs. DwellFirePolicyModRs.

5)

Wednesd dnesda ay, a little little late laterr Dwe DwellF llFire ireP Policy olicyAdd AddR Rs is ready, ready, but client doesn’t k now about it .

6)

Wednesd dnesda ay, Receive ceive Pending ndingR Respon sponse seIInqR nqRq for for ClaimsNotif ClaimsNotif icationRs. Form th e Pendin Pendin gResponseInqRs gResponseInqRs with ClaimsNotif ClaimsNotif icationRs and add add inf ormation about t he availability availability of t he DwellFirePolicyAddRs.

7)

Thursd hursda ay, Receive ceive Pending ndingR Respons sponse eInqRq nqRq for DwellFireP DwellFirePolic olic yModRs and DwellFireP DwellFirePolicyA olicyA ddRs. 159 15 9 Form the PendingResponse PendingResponseInqR InqRs s with DwellFireP DwellFirePolic olic yModRs and DwellFirePolicyAddRs. DwellFirePolicyAddRs. © C o pyri pyright ght AC A C O RD

1)

Monda onday, Sends nds one one docu docume ment nt with with 5 mess messa ages: ges: • PersAutoQuoteRq • PersAutoQuoteRq • ClaimsNotificationRq • DwellFirePolicyModRq • DwellFirePolicyAddRq

2)

6)

Wedne dnesda sday, rece receive ive list list of rea ready mess messa ages. ges. Send Send Pendin Pendin gRespons gRespons eInqRq eInqRq for ClaimsNotificationR laimsNotificationRs s only.

7)

Wedne dnesda sday, re receiv ceive e Cla Claim imsN sNot otif ific ica ation tion infor mation and status of other message. message.

8)

Thurs hursda day, y, Send Pendin ndingR gRe espon sponse seIInqR nqRq for for DwellFireP wellFirePolicyModR olicyModRs s and DwellFirePolicyAddRs .

9)

Th ur ur sd sd ay , Pr oc oc es s re r es u lt lt s .

C o rp.

Pending Response Information ‘ResponsePending’

1) Response comes back with a of ‘ResponsePending’. I 2) A later Response to any Request from the Client, the server will send the to indicate it is available.


Pending Response Inquiry Request You know the information is available and when it will expire on the server so, you send the request to retrieve that information


Probably a mistake that this is required

Pending Response Inquiry Response

Pending Response Response (one for each Request sent) is returned, possibly with additional 162 © C opyright AC ORD C orp.

Modification Process “Mods” g g

Policy Change / Endorsement Processing Examples: h h

g

Uses Aggregate with IDRef in Request Messages h h h

g

Add a car/driver/coverage Correct the policyholder’s date of birth

See example

SLIDE 163

f81d4fae-7dec-11d0-a765-00a0c91e6bf6 f81d4fae-7dec-11d0-a765-01a0c61f6bd5 2001-08-02T9:30:00.000-5:00 USD M 1776-07-04 Corrected named date of birth from 1776-07-04 to 1976-07-04 ... Ross Elizabeth F 1976-07-04 Fabric Engineer Note: The id BD1 did no t exist in the orig inal ... Request, this was added to th e response so the change could be point ed to.

1976-07-04

164


Notify Vs. Submission Messages g g

Refer to Section 5 (v 1.2.0 release) Submission messages begin as client requests for the server to do something h

g

Notification messages are statements of an action previously taken h

g

Ex. Quote, New Business, Policy Change

Ex. Automated Renewals

Two Types Of Notify Messages h h

Update Replace 8Empty

tags have meaning and are allowed (the exception) 8Can only be used with DTD due to schemas handling of empty tags SLIDE 165

Miscellaneous Items g g

Whitespace matters in Elements Response “echos” the Request

SuppressEcho in SignonRq - may not be honored by server h Required for Changed Element process h

g

Namespaces not allowed in ACORD XML streams (previously a v1.0.0 requirement) h

Now with Schemas you may start to see them used

SLIDE 166

Security - optional in design g

Sign on Message h h h h

g

Sign on Certificate Transport Certificate Session Key Customer ID and Password

Client Information (Required) h h h

DateTime on Client System Language Preferences Application information - Vendor, product name, version

SLIDE 167

Sign on Request/Response


Sign off Request/Response g

Optional

SLIDE 169

Services – Designed to Aggregate Messages g g

Accounting Service Base Service h h

g g g

Claims Service Common Service Extensions Service h

g

Pending Response Inquiry Rq/Rs Service Profile Inquiry Rq/Rs

Service Provider Extensions (SPX)

Surety Service

SLIDE 170

Service Profile g g g g g

g

Web based service discovery (UDDI) What do you support? Where do I send it? Who do I contact if I have a problem? Base service has a Service Profile Request/Response pair to report Surety and Insurance Service Profiles Extensions Service has a similar but different approach

SLIDE 171

Service Profile

Sublist

B as eSv c Msg B as eSv c Ms g Extensi xtensionsS onsSvcM vcMsg sg Extensi xtensionsS onsSvcM vcMsg sg

Code Value

Pen d i n g Res p o n s eIn q Sv c Pr o f i l eIn q SPExte Extensio nsionsI nsInq nq SPExtensio xtensionsS nsSync ync

Code Description Pending Response Inquiry Service Profile Inquiry Service Provider Extensions Inquiry Service Provider Extensions Synchronization Business Owners Policy Application Submission

In su su ra ran ce ceSv cM cMs g

B OP OPPo lili cy cy Ad Ad d

Insura nsurance nceS SvcM vcMsg Insura nsurance nceS SvcMsg vcMsg

BOP BOPPolic olicyQ yQuo uote teIInq Comml ommlAu AutoP toPol olic icyA yAdd dd

Insura nsuranc nce eSvcMsg vcMsg

CommlA ommlAuto utoP Polic olicyQ yQuo uote teIInq

Insura nsurance nceS SvcM vcMsg

Comml ommlAu AutoS toSche chedul dule eSubmi ubmitt

Commercial Auto Schedule Submit

Insura nsurance nceS SvcMsg vcMsg

CommlD ommlDrive riverS rSche chedul dule eSubmit ubmit

Commercial Driver Schedule Submit


CommlN ommlNa amedI medInsur nsure edAndLoca dAndLocatio tionS nS cheduleSubmit CommlP ommlPrope ropertyS rtySche chedul duleS eSubm ubmit it

Commercial Named Insured And Location Schedule Submit


Business Owners Policy Quote Commercial Auto Policy Application Submission Commercial Auto Policy Quote

Commercial Property Schedule Submit


Process Flow - web services services discov discovery ery process process Client 0) Identif Identif y partner and init ial URL, URL, login , and and SPName PName Info (somehow) (somehow) 1) Request Service Profile 2) Review Review Servic e Pro Profil fil e and and Determi ne if Carri Carri er does the sort of bus iness you are interested in, Yes Yes - Request Request Extension s (SPX) (SPX) 3) Process SPX SPX info (magic (magic happens here!) - build hybrid hybrid DT DTD - extract xtract code list information information - add new new fields to GU GUI - impleme implement nt business edits edits 4) Now we can do bu siness! Send Send fir st busi ness request and the relationsh relationsh ip is establish ed

** May May need to update SPX SPX infor mation on a daily basis

Server 1) Create Create Servi Servi ce Profi le Respo Respo nse - serve serverr information information - messa message ges s supported

2) Dete Determin rmin e level level o f su ppo rt and generate generate SPX SPX infor mation - add CarColorCd arColorCd to Vehicle Vehicle aggregate aggregate - create create list of colors, associate associate list with element - edit “ If Make= Make=Corve Corvette tte and and CarColorCd=Red reject”

3) Create Response to business request


Service Profiles and SPNames STEP 1

Service Profile Request

Web Servi ces Server Servic Servic e Prof Prof ile Respo Respo nse Provides Act ual Server Server Locations

Client/Agent

SPName SPName = Fred Commercial Auto

STEP 2 Central Routing Server

SPName SPName = Sue Perso Perso nal Auto Quotes

Routin g Server Server based on SPName

SPName = Joe Surety B OP Home Owners Inland Marine

Client/Agent


Conclusion – Framework g g g g g g g g g g

Processing Environment Request / Response Model Message Status Error Management Extended Status Changed Element Process Pending Response Modification Messages Notify Messages Sign-On / Sign-Off SLIDE 175

ACORD P&C/Surety XML SPX (Service Provider eXtensions)

Mark Orlandi

©AC O RD 2005.

Agenda – SPX g

Extensibility

g

Business Rules

g

SPX Design Guidelines

g

Naming Conventions

g

Examples

SLIDE 177

Extensions to the Standard g

When is it an Extension vs Just Missing? h

g

80-20 rule

SPX - standard way to document in a processable manner, your: h h h h

extensions edits business rules - relationships GUI requirements 8Field

Labels 8Prompt, Error, Help Text

SLIDE 178

Design Guidelines for SPX g g

Support XML 1.0 second edition DTDs Support the following XML Design principals h h h h

Terseness is not a requirement Readability of the stream is important Hierarchies are used to group related information Attributes and elements can be used, but attributes are currently limited to ID/IDREF types

Note: SPX was developed before W3C Schemas was a released specification. We need to update SPX capabilities, but you can also use schema methods to extend the ACORD schema if that is all you need to do

SLIDE 179

Naming Conventions g

g

Refer to Chapter 4 and follow those rules whenever possible for both Tags and Codes SPXPrefix – use is similar to namespace prefix h h h

ACORD unique methodology until we can update to schema support Reverse the Domain Name, add an underscore acord.org’s SPXPrefix is

com.acme_

SLIDE 180

Extension Service


Element Definition Add an A CORD aggr egate t o an ACORD agg regate

Existing Definition ACORD DTD Definti on

Add to Definition CodeList Addr Opt

Result

New elements and aggregates add t o the end of th e original definition.

New Hybrid DTD (ACORD Spec pl us SPX infor matio n)


Codelist Definition 1) Create the Code list

2) Associate an Element

com.fred_CarMakes A For d Mus tang FMustang Ford Mustang A Shelby A C Cobra SCobra Shelby Cobra A Chevro let Sting ray Corvette CVett Chevy Stingr ay

com.fred_CarMakeCd OpenEnum The make and m odel of a car. com.fred_CarMakes

3) Insert in ACORD Element PersVeh com.fred_CarMakeCd Opt

Updated ACORD DTD Defintion
com.fred_CarMakeCd ?))">

183


Relational and Field Edits

• Business Rules • Help, Prompt, Error Text • Content Restrictions and Relationships 184 © C opyright AC ORD C orp.

Parameter Sets

• Relate groups of edits - by State, Date, Line of Business, etc. •Set specific requirements to apply group


Conclusion – SPX g

Extensibility

g

Business Rules

g

SPX Design Guidelines

g

Naming Conventions

g

Examples

SLIDE 186

ACORD P&C/Surety XML Certification+ Mark Orlandi

©AC O RD 2005.

Agenda – Certification+ g

Why Certify?

g

OARS: On-Line Adoption & Report Survey

g

Activities

g

Contacts

SLIDE 188

Why Certify?

Schema Test Your Data ACORD can help!

g

Member Benefit Get to advertise conformance Should help leverage your partners Provides a third-party opinion on conformance If everyone conforms, then integration is easier Quiz your vendors - two different statements

g

We implement ACORD h We are certified by ACORD http://www.acord.org/Services/certification.aspx

g g g g

g

h

SLIDE 189

OARS: Online Adoption Report & Survey

g

Opportunity to report your implementation activities to ACORD Reports available for download from web

g

http://www.acord.org/Resources/im_reports.aspx

g

Content sorted by:

g

h

Organization & Implementation/Business Message

SLIDE 190

Collaboration & Communications g

ACORD Teams area: http://teams.acord.org/home

g

Working Groups h h h h

Members and “invited” guests only Refer to www.acord.org for current listing of active working groups Must be registered user of ACORD website: http://acord.org/registration/webregistration.aspx 8Provides

email notifications 8Web archive 8Calendars h g g

Specific Working Groups - Announcements of meetings and conference

Best resource for asking questions of your peers Also call ACORD staff – we are here to help

SLIDE 191

Contacts g

g

g

http://www.acord.org 845-620-1700 Mark Orlandi Program Director, P&C/Surety [email protected] x 478 Alan Stitzer Program Manager (XML business topics) [email protected] x 410

SLIDE 192

ACORD P&C/Surety XML Training

Recommend Documents