BOP Package Included Perils Lookup

Audit actual BOP loss-peril annotations against caller verified included-peril map, unknown cause evidence separate; no universal BOP package contents, causation or coverage verdict.

Description

Businessowners policy (BOP) peril checks require an independently verified included-peril map.

Businessowners policy (BOP) peril checks require an independently verified included-peril map. Unknown cause evidence must remain unresolved.^[1]

The returned values include Caller included observed peril ids, Caller excluded observed peril ids, Unknown loss peril ids. The How section below explains the calculation, input rules and interpretation.

When to use BOP Package Included Perils Lookup

Use BOP Package Included Perils Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No universal BOP contents, causation or policy coverage verdict is supplied.

Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.

How to use BOP Package Included Perils Lookup and understand its results

Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
Enter callerBopPerilIds, callerVerifiedIncludedPerilFlags, observedLossPerilIds, lossPerilEvidenceFlags using the field table and calculation rules, then run the tool.
Read callerIncludedObservedPerilIds, callerExcludedObservedPerilIds, unknownLossPerilIds. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
callerBopPerilIds	Caller bop peril ids	list of string	Required
callerVerifiedIncludedPerilFlags	Caller verified included peril flags	list of number	Required
observedLossPerilIds	Observed loss peril ids	list of string	Required
lossPerilEvidenceFlags	Loss peril evidence flags	list of number	Required

Enter aligned nonempty unique nonblank peril IDs and binary included flags, plus aligned nonempty observed perils and binary evidence flags. Exact-match known observations; unknown observations require no catalog match. Return included, excluded and unknown observed IDs in order.

known observations→exact included/excluded map; unknown observations→unknown list

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
callerIncludedObservedPerilIds	Caller included observed peril ids	list of string
callerExcludedObservedPerilIds	Caller excluded observed peril ids	list of string
unknownLossPerilIds	Unknown loss peril ids	list of string

json

{
  "input": {
    "callerBopPerilIds": [
      "fire",
      "flood"
    ],
    "callerVerifiedIncludedPerilFlags": [
      1,
      0
    ],
    "observedLossPerilIds": [
      "fire",
      "flood"
    ],
    "lossPerilEvidenceFlags": [
      1,
      0
    ]
  },
  "output": {
    "callerIncludedObservedPerilIds": [
      "fire"
    ],
    "callerExcludedObservedPerilIds": [],
    "unknownLossPerilIds": [
      "flood"
    ]
  }
}

Limitations and assumptions

No universal BOP contents, causation or policy coverage verdict is supplied.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Cyber First vs Third Party Cover Lookup: Cyber cost categories can belong to first-party, third-party, both or neither supplied maps. Overlap must be visible before totals are combined. For a complementary task, use Sump Overflow Coverage Checker: A sump-loss evidence audit separates known cause exclusions from unresolved annotations. Coverage mapping must already have been verified.

References

BOP Package Included Perils Lookup — tool.io

Similar or alternative tools

Cyber First vs Third Party Cover Lookup
Cyber cost categories can belong to first-party, third-party, both or neither supplied maps. Overlap must be visible before totals are combined.
Sump Overflow Coverage Checker
A sump-loss evidence audit separates known cause exclusions from unresolved annotations. Coverage mapping must already have been verified.