Skip to content

Accommodate multiple exposure types in db backend #90

@genedan

Description

@genedan

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions