Objects

The coverage tree is the central element of a calculation, an application or a contract. Its core remains the same for all these objects, but it is extended depending on which object (configuration, calculation, application, contract) is concerned.

Nevertheless, there is a need to keep separate objects in these objects next to the contract tree, which are referenced in the contract tree or which reference the contract tree.

When is an object defined next to the product tree:

  • Something exists independently of the contract and is therefore potentially managed in the systems independently of the contract: persons, addresses, vehicles, aircraft, buildings, machines…​

  • A group of fields has an inner connection, such as account holder, BIC and IBAN, or risk information on a person. The group of fields is always handled together; together it describes a circumstance.

  • An object is used several times in the application. Instead of listing the values again and again and checking whether they are the same, an object is defined that is referenced.

Risk Objects

A special kind of object are the risk objects, also called "insured interests" in the contract: vehicle, risk address, building, household, person. They carry the risk characteristics, are kept in a list of the instance and are referenced by the components. More on this on the page Risk Objects.