You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Various reserving methods may use some kind of exposure measure, for example, the expected loss method often involves claims per unit of exposure:
The challenge for FASLR is to anticipate any kind of exposure and to store it in the backend. Thus, having predefined types and only allowing those will do no good if a user has a type of exposure we didn't anticipate. Therefore, we need to be able to, either by extensions or some clever way of engineering the db, to accommodate multiple exposure types.
I'm thinking maybe something like:
Accident Year
Exposure Value
Exposure Type
1998
5000
employee count
2000
20000000
payroll
The text was updated successfully, but these errors were encountered:
Various reserving methods may use some kind of exposure measure, for example, the expected loss method often involves claims per unit of exposure:
The challenge for FASLR is to anticipate any kind of exposure and to store it in the backend. Thus, having predefined types and only allowing those will do no good if a user has a type of exposure we didn't anticipate. Therefore, we need to be able to, either by extensions or some clever way of engineering the db, to accommodate multiple exposure types.
I'm thinking maybe something like:
The text was updated successfully, but these errors were encountered: