-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Property] Clarify value in BITIV as annualised in field description #216
Labels
documentation
Improvements or additions to documentation
Comments
Good update to make the documentation clearer. Apologies for missing this in the first iteration of OED. |
thanks - will move to agreed and ready in OED v4 |
Changed description to "Business Interruption (BI) Total Insured Value. Enter an annualized amount, and use LocDed4BI and LocLimit4BI fields for non-annualized values". as this is what people need to know to model the values correctly. |
johcarter
changed the title
Clarify value in BITIV as annualised in field description [Property]
[Property] Clarify value in BITIV as annualised in field description [Property]
Nov 28, 2024
johcarter
changed the title
[Property] Clarify value in BITIV as annualised in field description [Property]
[Property] Clarify value in BITIV as annualised in field description
Nov 28, 2024
Merged
github-project-automation
bot
moved this from Waiting for Review
to Done
in Oasis Dev Team Tasks
Jan 9, 2025
github-project-automation
bot
moved this from Agreed and ready
to Done
in Open Data Standards
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The proposal is to update the BITIV field description to make clear the TIV is an annualised figure. The Period Of Indemnity 'BIPOI' default value is 365, meaning that the maximum sum insured is equal to the annualised BITIV. The BIPOI may be entered differently, but BITIV would remain as the annualised figure.
New description:
“Business Interruption (BI) Annualised Value, if POI is not 365 days please enter a valid value in BIPOI”
Reasons for change
This will make the relationship between BITIV and BIPOI clearer in the spec, as the BITIV could currently be interpreted as an annualised figure or a limit for a different POI.
Scope of change
Impact of change
None - this is just a field description update.
The text was updated successfully, but these errors were encountered: