Simulator 2.0 is currently built in with only a Single Payment Transaction Model. By default, it only accepts loss information at individual claim level. If your claim data have transaction details, at this stage, please aggregate all the transactions (payments) for each claim(just like your year-end claim format) Once claim file (csv format) is provided, system will fit it to the [LoB] tab properties as described in previous chapter, thus simulation becomes a realistic loss reserving analysis. (Simulation will help loss reserving analysis by providing close-to-real synthetic claim transactions and rectangles) Select the claim data file by pressing ribbon button [Select Data]. All the data fields in the csv file will be populated (column C) in [ClaimData] tab. User needs to determine whether or not each data field should be used (column D) and its matching data field name (column E), for Simulator to fit from. The following variables are mandatory: ClaimID LoB
Simulator 2.0 is currently built in with only a Single Payment Transaction Model. By default, it only accepts loss information at individual claim level. If your claim data have transaction details, at this stage, please aggregate all the transactions (payments) for each claim(just like your year-end claim format) Once claim file (csv format) is provided, system will fit it to the [LoB] tab properties as described in previous chapter, thus simulation becomes a realistic loss reserving analysis. (Simulation will help loss reserving analysis by providing close-to-real synthetic claim transactions and rectangles) Select the claim data file by pressing ribbon button [Select Data]. All the data fields in the csv file will be populated (column C) in [ClaimData] tab. User needs to determine whether or not each data field should be used (column D) and its matching data field name (column E), for Simulator to fit from. The following variables are mandatory: ClaimID LoB
HowToRunCASSimulator2.docx