XCS CLASS

Knowledge Transition Session

© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 The Learning Contract for this session
Title XCS CLASS

SMART Learning Objectives Inputs / Prerequisites for Course

• OBJECTIVE 1 • XCS CLASS Demonstration (AF)

• XCS CLASS Data Structure • EOD Flow diagram
Relationship between broker UCR & COR • XCS CLASS Functional Design (Process Description and
Database Tables Appendices) – do not print or attempt to read in advance.
•OBJECTIVE 2 • XCS CLASS System Map
•XCS CLASS Architecture (Online)
Attunity Interface (Non-MF –> MF)
Quality Gateways
LIDS Interface
Design Principals
Programs / Functions & Documentation • 3 questions for end of week test
Reference allocation

•OBJECTIVE 3
•XCS CLASS End-of-Day processing
CTF Processing
SCM Processing
...

2
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 PLEASE
ASK QUESTIONS
AT ANY TIME

3
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Data Structure

Claim
Header

Transaction Market Claim Policy

Header Details Details Details

Currency Original Signing CLASS (inc. CLASS for Lloyds)

Details Number

Collection
Details COSS (Settlement)

Breakdown Movement
(SCM) Details Details COSS (Advising)

4
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 XCS CLASS Database
TCLCHDA
(Claim Header)
CLASS
(inc. CLASS @ Lloyd’s)

TCLTHDA
TCLMKTA TCLLOSA
(Transaction
(Market Details) (Loss Details)
Header)

TCLCUXA TCLLADA
TCLMKAA
(Currency/ (Lloyd’s Additional
(Market Amounts)
Financial Details) Details)

TCLSGNA
TCLCRDA TCLCRAA
(Original Signing
(Risk details) (Risk Amounts)
Details)

TCLFTXA
(Narrative)

Lloyd’s TCLLSTA
(Lloyd’s Statistical LIDS
Breakdown Split)

TCLLBDA
(Lloyd’s SCM
Breakdown)

TCLLLRA TCLLMOA TCLEXFA

TCLLTXA TCLVATA
(Lloyd’s Loss (Lloyd’s Monetary (Expert
(Lloyd’s Narrative) (VAT Amounts)
Reserve Details) Amounts) Breakdown)

5
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 XCS CLASS Database

Non-Core XCS CLASS Database tables

TCLSESA – Session Table
Drives the whole online application, holding details relating to the current user’s session
TCLLCSA – Lloyd’s Claim Summary
contains details of the latest movement on every XCS CLASS claim
TCLSLGA / B – SCM Log Records
Drives the SCM Extract process
TCLXEFA – ECF Cross-Reference Table
Cross refers decoupled ECF claims to XCS CLASS entries
TCLXRFA – Cross-reference Table
Cross refers Bulk components to their header – and /Contra/ROE Adjustments to their target transaction
TCLGHDA / TCLGCDA – Group Header and Details Tables
Grouping Database - allows claims to be grouped together for business reasons
TCLDRYA – Diary List
User’s Diary List – contains claims to be shown on the Home Page.

6
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Architecture Overview

CICS
Transactio
ns
J2EE (Oracle OC4J)
LY01 LYnn
Attunity Attunity CLASS LIDS
DB
Web Tier EJB Tier Connect Connect
JAVA Servlet State Machine
(JCA) (JCA)
LYnn LIDS I/F
CICS Handlers Daemon
iMac

All COMMAREAS
Web Controller
Web Browser
(Internet Explorer)

•JSP XML

•Javascipt

DB2 DB2
Additional Search
DB

Oracle 9i
CICS CICS

Solaris O/S OS390 O/S OS390

SUN Server IBM Mainframe

7
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Overview of CICS Design Principals (1)

Design Principal Benefits

Session Record - holds all information relating to user and current claim
- Simplifies Java Code
- Allows concurrent Sessions (e.g. History, Bulk)
Standard CICS/GUI - Clarity for HTML/Java programmers
Interface Program
- Functions common to all CICS calls centrally located
(e.g. Updating Session Record, Committing D/B Updates)
Standard Commarea -Clarity for CICS programmers
Layout
-Clarity for HTML/Java Programmers
-Reduction of development time (standard code)
Standard Approach to e.g. Build, Validation and Update
Screens
-Clarity for CICS and HTM/Java programmers
-Flexibility (I.e. circumstances dictate if and when called)

8
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Overview of CICS Design Principals (2)

Design Principal Benefits

Screen Navigation - Standard Navigation Program

- HTML/Java Layer simplified
- Flexibility (Screen flow can easily be adjusted)
- Navigation to any screen supported by use of Currency and
Transaction validation modules
Use of Common - No repetition of complex functions
Modules
- Subsequent Enhancements can be developed with
minimum risk & testing (e.g. Re-Advice)

9
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Core Screen Navigation

COR selected in SCM Advice

Claim Enquiry
Claim Enquiry

Claim Summary

Continue with
Policy Search New Advice Claim Creation Risk Details Market Details Claim Details Financial Details SCM Advice

Create Subsequent Advice

Iterative Process
for each currency Non-Settlement
on Claim Schedule
Summary

Claim Creation Financial Details SCM Advice

Iterative Process
for each currency Settlement
Schedule
on Claim Summary

10
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 CICS Processing (1)

Claim Details Financial Details

Screen HTML Control Screen

Java

Attunity

CICS/GUI Interface program (LY01)

Claim Claim Navigation Build Build

Details Details Program Navigation FDC
Validation Update (LY11) Bar Screen
(LY35) (LY36) (LY12) (LY37)
CICS

11
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 CICS Processing (2)
Schedule Non-Settlement
Screen HTML Summary Screen

Java

Attunity

CICS/GUI Interface program (LY01)

Schedule Schedule Navigation Build Build Non-

Screen Screen Program Navigation Settlement
Validation Update (LY11) Bar Summary
(LY57) (LY58) (LY12) (LY59)

CICS Currency Transaction Delete Un-used Assign

Validation Validation Collections Movement
(LY19) (LY17) (LZ04) Refs (LY60)

12
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Session Record

Field Category Field Name Comments

Unique Identifier SESSION_NO Sequential Number, allocated using TCLSENA

User Details ACC_CODE Login details from TSANUSA
NET_USER_ID
PROFILE_ID
SY_SECTION_CODE Selected on login
Key fields for current transaction UCR_TR_SYS_REF See next slide
CURR_NO
SDN_NO
STAT_SPLIT_NO
BREAKDOWN_NO
Session Characteristics UPDT_ENQ_IND Set to ‘U’ or ‘E’ depending on whether the user is updating or enquiring.
This will depend on te Login used and/or the Status of the claim - e.g.
Will always be ‘E’ if Status is ’40’ (complete)
UPDATED_TIMESTAMP The time the Session was last updated (updated whenever CICS
accessed – to indicate session active)

RETURN_SCREEN Screen from which claim was accessed

SESSION_TYPE Type of Session – i.e. Blank (Normal), H (History), B (Bulk), G
(Grouping)
Key fields for associated ASSOC_SYS_REF Details of any associated transaction – only populated where Session
transaction ASSOC_CURR_NO Type not = spaces.
ASSOC_SDN_NO E.g. Where Session type is ‘B’, the user is navigating through a bulk
ASSOC_BREAKDOWN_NO component and these fields contain the details of the associated Bulk
Header
ASSOC_SPLIT_NO
Miscellaneous LOGIN_WARN Used when logging back into existing session
GROUP_REF_S Contains Group Reference for current claim (where applicable)

13
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Session Record

Screen

SCM Advice (Breakdown)

Non-Settlement Summary
Financial Details Control
OSND Search Results

Settlement Summary
Home / Find Claim

Subsequent Advice
Policy/Risk Details
Claim Transaction

Market Details

Claim Details

Loss Reserve

Schedule
Creation

Screen
Field Category Field Name

Key fields for current

transaction
UCR_TR_SYS_REF
           
CURR_NO
           
SDN_NO
           
STAT_SPLIT_NO
           
BREAKDOWN_NO
           

14
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Programs / Functions
XCS CLASS Online – COBOL/CICS/DB2 Transactions (Prefixed ‘LC0’)

Endevor System:- CLAIMS

Endevor Sub-systems (and program prefix):-
LC00 – System Control
LC01 – Login / Logoff
LC02 – Policy / Claim Search
LC03 – Core Data Entry
LC04 – Claim Grouping
LC05 – Functions
LC06 – History
LC07 – Narrative
LC08 – Scheme Canada
LC09 – Historical Claims Settlement Enquiry

15
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Programs / Functions

XCS CLASS Batch – COBOL/DB2 Programs:-

Endevor System:- CLAIMS

Endevor Sub-systems (and program prefix):-
CLB – General Batch Programs (inc. reporting, etc.)
SCM – Programs related to the Syndicate Claims Message
CTF – Programs related to the CTF Extract (Completed Transaction File) to LIDS
DWH – Programs related to the Data Warehouse
SCF – Scheme Canada Batch Programs

16
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Documentation

All Functional and Component Specifications are currently stored in the following
location in repository:-

Home Xsdf XIS Systems XCS Class

Key documents:-
• Functional Design – Process Description
• Functional Design – Appendices
• XCS CLASS – System Map

17
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 XCR/XTR Allocation

XCR’s and XTR’s are formatted as follows:-

(Note:- On a first advice, XTR’s are allocated after XCR’s)

XCCCCYYMMDDSSSSSS

X = Source Indicator – always set to ‘X’ (Third-Party)

CCCC = Source Code – either XCHU (new claims) or CONV

(claims converted from COSS)

YY = Last two digits of current signing year, including leading zero where
applicable

MM = Current signing month, including leading zero where applicable

DD = Day from current signing date, including leading zero where

applicable

SSSSSS = Sequence Number (using SIGN_SERIAL, obtained from TGLNUMA

where RANGE_ID = ‘SCR’ – and incremented by 1)

18
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 COR Reference Allocation (LC0398R0)

When MARKET-CODE is ‘M’ (Marine)

Format is:- kyymmnnnnnc

k = MARKET_CODE (i.e. ‘M’)
yy = last two digits of current signing year (e.g. ‘10’)
mm = current signing month, including leading zero where
applicable.
nnnnn = sequence number (using SIGN_SERIAL, obtained from
TGLNUMA, RANGE-ID = ‘COM’ – and incremented by 1)
c = Currency indicator – allocated using ORIG-CURR as
follows:
‘GBP’ c = ‘1’
‘USD’ c = ‘5’
‘CAD’ c = ‘7’
others c = ‘3’

19
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 COR Reference Allocation (LC0398R0)

When MARKET-CODE is ‘N’ (Non-Marine)

Format is kcrnnnddmmyy
k = MARKET_CODE (i.e. ‘N’)
c = Currency indicator – allocated using ORIG-CURR as follows:
‘GBP’ c = ‘2’
‘USD’ c = ‘6’
‘CAD’ c = ‘8’
others c = ‘4’
r = if Letter of Credit (LOC) claim, then set to ‘4’. Otherwise, set to ‘0’
nnn = Sequence Number (using SIGN_SERIAL, obtained from TGLNUMA
where RANGE-ID = ‘CON’ - and incremented by 1)
dd = Day from current singing date, plus 40, i.e. ‘01’ becomes ‘41’, ’23
becomes ‘63’, etc.
mm = current signing month, including leading zero where applicable
yy = last two digits of current signing year, including leading zero where
applicable.

20
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 COR Reference Allocation (LC0398R0)

When MARKET-CODE is ‘A’ (Aviation)

Format is kcnnnnddmmyy

k = MARKET_CODE (i.e. ‘A’)

c = Currency Indicator – obtained using ORIG-CURR as follows:
‘GBP’ c = ‘2’
‘USD’ c = ‘6’
‘CAD’ c = ‘8’
others c = ‘4’
nnnn = Sequence Number (using SIGN_SERIAL, obtained from TGLNUMA
where RANGE-ID = ‘COA’ – and incremented by 1)
dd = Day from current signing date, plus 40, i.e. ‘01’ becomes ‘41’, ’23’
becomes ‘63’, etc.
mm = current signing month, including leading zero where applicable
yy = last two digits of current signing year, including leading zero where
applicable.

21
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Movement Reference allocation

Movement references are incremented as follows:-

AA, AB, AC ……..….AY, AZ, BA, BB, ………. BY, BZ, CA, CB, ……..TY, TZ.

The maximum movement reference allocated to normal claim movements is TZ.

References beyond this are (or have been) used for other purposes – e.g. for Euro
conversion.

The only other movements currently in use are X movements – allocated by the quarterly
“Revaluation of Outstanding Losses” (or ROE Revision) program (CLB900).

22
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 TDN Allocation
The Taking Down Number and Date is formatted as follows:-

CSRRR * DD/MM/YYYY

C = Currency Indicator – set as follows:-

Settlement Currency Market Code TDN – 1st digit
USD M 5
USD N or A 6
CAD M 7
CAD N or A 8
Other M 1
Other N or A 2

S = Sign – set as follows:-

Paid This Time TDN – 2nd digit

>= Zero 0
< Zero 6
i.
RRR = Sequential Reference (using SIGN_SERIAL, obtained from TGLNUMA
where RANGE_ID of 1st 2 TDN digits, as set above – and incremented by 1)

DD/MM/YYYY = Signing Date

23
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 End-of-Day Processing

24
24
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 End-of-Day Processing

25
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 …What We Have Learned
Summary of Knowledge Transferred

• XCS CLASS Data Structure

Relationship between broker UCR & COR
Database Tables

• XCS CLASS Architecture (Online)

Attunity Interface (Non-MF –> MF)
LIDS Interface
Design Principals
Programs / Functions & Documentation
Reference allocation
• XCS CLASS End-of-Day processing
CTF Processing
SCM Processing

26 …What We Have Learned

© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Know ledge Transition Course Evaluation

Date of Course: Course Title:

Facilitator’s Name: Delegate’s Name:

Which 3 or more aspects of the w orkshop did you find most helpful in preparing you for service take-on?
 _
 _

•Please complete the course

 _

Which aspect(s) of the w orkshop did you find least useful in preparing you for service take-on?
 _
evaluation form
Which aspects did the course not cover, but w hich you felt should have been covered?
 _

Please comment the standard of training delivery (place an x next to the box), thinking about how the
trainer has prepared you for service take-on:
Training delivery V. Good Good Acceptable Poor
Training handouts V. Good Good Acceptable Poor
Overall Session Standard: V. Good Good Acceptable Poor
After this session, how confident are you that you are prepared to take on the elements of the service
covered in the course? (place an x next to the box)
Confidence levels V. Confident Confident Acceptable Unconfident

Other comments

27
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.
 Preparing for KT: Next

Any Questions?

28
© Xchanging 2009, no part of this document may be circulated, quoted or reproduced without prior written approval of Xchanging.