Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accommodate multiple exposure types in db backend #90

Open
genedan opened this issue Feb 21, 2023 · 0 comments
Open

Accommodate multiple exposure types in db backend #90

genedan opened this issue Feb 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@genedan
Copy link
Collaborator

genedan commented Feb 21, 2023

Various reserving methods may use some kind of exposure measure, for example, the expected loss method often involves claims per unit of exposure:

Selection_081

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
@genedan genedan added the enhancement New feature or request label Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant