The AFD model consists of a collection of entities and attributes. An entity describes an object or thing from reality, for example a policy, party or claim. An attribute describes a characteristic of an entity, for example the date of birth of the policyholder, or the expiry date of the policy. One entity consists of multiple attributes.

AFD 2.0 consists of about twenty entities, divided into four categories: core entities, supporting entities, technical entities and structure entities.
Note that AFD 2.0 facilitates a changing world. The need for entities will change over time. The support chapter explains how to request changes and additions to the AFD.

Entity types

In AFD 2.0 the number of entities has been reduced considerably compared to AFD 1.0. This makes the model clearer by less entity definitions and general grouping of attributes by entity. Nevertheless, a subdivision within entities remains through so-called entity types. The entityType attribute indicates a specialization within an entity. For example, coverage includes the entity types personalAccidents, rental and glass, comparable to the PO, VR and GP AFD 1.0 entities respectively.

Attributes are grouped by entity in AFD 2.0, but the entity types provide a filtering in which attributes can be used. For example, amountInsuredForStorage only occurs in combination with entityType = liability.

Overview of entities

Core entities

Core entities are the entities that form the core of the AFD data catalog. These are the seven entities with which the financial world can be modeled. This means that the entire standard for data exchange rests on the seven pillars of policies, loans, pensions, parties, objects, coverages and claims. See the chapter about core entities for more information.

Entity Description
party Data about a person or organization.
policy The legal document issued to the insured setting out the terms of the contract of insurance.
loan A sum of money that is lent, usually with an interest fee.
pension Information about the pension contract between a party and a pension fund.
object The insured or financed object which represents an interest for the owner.
coverage The protection provided by the policy against a certain risk.
claim Request made by the insured for insurer remittance of payment due to loss incurred and covered under the policy agreement.

Supporting entities

Supporting entities are the entities that support other entities. These entities will always be used in combination with one or more core entities. However, that does not mean that supporting entities must always be nested under another entity. See the chapter about supporting entities for more information.

Entity Description
address An indication of a location that a person can visit or has been recognized by a postal service.
clause Information about a clause that is included in a contract (such as a policy).
condition The details of a condition, for example policy condition.
discountOrSurcharge Information about a discount or surcharge.
document Information about an attachment/document.
financialTransaction Information about a financial transaction.
financialInformation The recording of financial data not pertaining to a transaction.
poolShare The relative size of the participation from an insurer in a contract.
premium Information about a premium.
process Information about a status associated with (for example) an application or change.
underwriting Inquiry to determine whether or not the risk is sound, and to establish all facts that might affect the risk.
incident Information about the circumstances and damage/loss due to an incident.
partyDetails Specific collections of information about a party, such as income or health information.
settlement Agreement(s) regarding the handling of a claim.
masterData Used for grouping data as data in itself, and not as the usual collection of attributes.
masterAgreement Used for grouping data about a master agreement, such as a package policy.
order General information about an order or task for, for example, inspection, appraisal or repair of damage.
customAttribute Freely definable attribute within the context of AFD. Custom attributes can be used within other entities in addition to existing attributes.

Technical entities

The AFD has three technical meta-data entities in which information about the message can be stored. The commonFunctional entity covers all information about the content of the message. This is typically domain-specific information, while the commonTechnical entity primarily provides technical message-related meta-data. The third technical entity is specifically meant for error messages. Normally, content from technical entities is not stored in local databases, but only used for the exchange of data. See the chapter about technical entities for more information.

Entity Description
commonFunctional The commonFunctional entity covers all information about the content of the message. This is typically domain-specific information.
commonTechnical The commonTechnical entity covers all information about sending or storing the message. This is typically technical information.
error Technical information about an error message.

Structure entities

Structure entities do not have any proprietary attributes, but only serve to define a set of entities and their respective relationship(s). Some structures are allowed to contain a refKey attribute to make it easy to refer to the top level of the structure, i.e. within a container or message structure. See the chapter about AFD structures for more detailed information about structures and structure entities.

Entity Description
policyStructure Represents the policy structure.
loanStructure Represents the loan structure.
pensionStructure Represents the pension structure.
masterAgreementStructure Represents the master agreement structure, for example a package policy.
groupStructure Represents the group structure.
claimStructure Represents the claim structure.
orderStructure Represents the order structure.
partyStructure Represents the party structure.
message Represents the message structure.
container Represents the container structure.
masterDataStructure Represents master data in a tabular structure.


Thanks for your feedback.

Post your comment on this topic.

Post Comment