Session 3 : Neutrinos Reels Master Class Assignment: Motor Insurance Pricing

[Eldho]

@Rocky @Muhammed_Sinan Please Help

[Rocky]

Hi @Simphiwe , based on the description, the deductible itself is not directly linked to the car’s make or model but rather is a user-defined input. However, the Excess Loading is influenced by this deductible input, and that affects the overall premium calculation.

[Simphiwe]

Hey @Rocky

Thank you for your response. I see now that deductible is user-defined(Entered as number between 0 and 10000) and thank you for bringing that to my attention, but If a user inputs a value that does match any of the values(deductible) in the Excess loading since deductible are specific amounts there . For example if a user enters 500 and in the Excess loading the is no loading for that amount or even a range that will cover for 500.

[Simphiwe]

Please see the attached image

[Rocky]

The Sum Insured is determined based on vehicle make, model, and age.
The values 0_Rec_SI to 10_Rec_SI are likely a series of predefined sum insured values in the master data that correspond to different ranges of vehicle ages. For instance:
0_Rec_SI might correspond to vehicles aged 0-1 years.
1_Rec_SI could correspond to vehicles aged 1-2 years, and so on.
These values are essentially a mapping of sum insured values depending on the age of the vehicle and the specific make/model combination.

[Rocky]

You are correct in pointing out that the deductible values entered by the user must exactly match those present in the Excess Loading master data.
Currently, the system does not automatically validate whether the entered deductible value exists in the master data. Therefore, the user should only enter a deductible value that is part of the predefined values in the master data. If the user attempts to enter a deductible value (e.g., 500) that is not included in the master data, the system should prompt the user with an error message.

[Simphiwe]

Okay, thanks. So sum insured is/not a sum of values 0_Rec_SI to 10_Rec_SI based on vehicle make, model, and age ?

[Simphiwe]

Okay the deductible is noted and thanks again.

[Rocky]

Yes, the sum insured is not a sum of the values from 0 _Rec_SI to 10_Rec_SI.

[Simphiwe]

Okay, thanks. So if “the values 0_Rec_SI to 10_Rec_SI are likely a series of predefined sum insured values” and that’s a sum insured, how do I link these specific values to the vehicle age since the is 10 values which are in 0_Rec_SI to 10_Rec_SI column. So how do I figure out if 0_Rec_SI correspond to vehicles aged 0-1 years or 1_Rec_SI correspond to vehicles aged 1-2 years for that vehicle. The master data doesn’t provide ranges like how you putting it that “0_Rec_SI might correspond to vehicles aged 0-1 years.”

[Eldho]

@Rocky @Muhammed_Sinan please help

[Gowtham_Balram]

@Simphiwe - Data shared for the assignment is in raw format i.e., you may want to modify the master data to suit as per the rules planned to configure. In most of the day to day scenarios, data cleaning / enriching is part of the definition of data tables / rules.

Hint: You could create a MD to check if age is BETWEEN two ranges and decide the column to pick the data.

[adarshks]

The new version of reels doesn’t have an option of enabling runtime in constant creation. How can i create and assign value to the constant in runtime

[Eldho]

@Rocky @Muhammed_Sinan please support

[Gowtham_Balram]

@adarshks - Thats correct, we have updated the way constants work in Rules.

As the name suggest, constants are static values that are meant to be used for variables with fixed values like value of pi, square root of 2 etc.,

If the requirement is to have dynamic values for variables, please use the input object.

[Rocky]

@adarshks In new Reëls platform, there is no need to create constants at runtime.For constants, you should provide a static value, similar to defining a variable with an associated value. If you want to use a constant within a rule, you should declare it in the format {keyname}. Similarly, if you need to reference an input key within a rule, it should be declared as {IP_keyname}, and for an output key, it should be formatted as {OP_keyname}.

[Revathi]

Hi @Eldho , im trying to add a check ponit for knockout conditions but im unable to save, after clicking save it get disabled and not closing.
This is the my knout rules decision table

This is where the save option getting disable and not saving the condition.

Please can any one help on this, where im doing wrong.

[Eldho]

@Rocky please help revathi

[Rocky]

Hi Revathi, Press Enter after entering the ‘Rejected’ value in the operand.

[Revathi]

Thanks @Rocky , its worked