Business Case Types

Part of Process Knowledge. Application process, contract change, conversion and claim handling in the same grid of business objects, states, transitions and derivations.

A business case type (Geschäftsfalltyp) defines which business objects a business case can carry, which states, edits, transitions and derivations exist and who is responsible for what. The standard starts with four types in the same grid:

	Application process	Contract change	Conversion	Claim notification and claims handling
Business objects	calculation, offer, application, contract; in the motor line of business additionally the insurance confirmation for the registration of the vehicle	existing contract (reference, not part of the business case), contract change application, changed contract	existing contract (reference), conversion application on the new product, new contract	contract (reference), claim report; whether settlement and benefit decision are objects of their own is defined by the declaration of the type
Assessed states	calculable (calculation), acceptable (offer), submittable (application); otherwise draft	submittable (contract change application); otherwise draft	submittable (conversion application); otherwise draft	reportable (claim report); otherwise draft
Set states	calculated; accepted (offer); submitted, under review, query, accepted, rejected (application); cancelled, expired	submitted, under review, query, accepted, rejected	as contract change	reported, under review, query, settled, rejected
Edits	include and exclude a component, set an attribute value, set up and assign a risk object, add persons and application questions	the same, at the contract change application; set reason for change and effective date	the same, at the conversion application	add course of events and parties involved, add a document (also during a query)
Transitions	calculate (calculation), accept (offer), submit and close query (application), cancel	submit, close query, cancel	as contract change	report, close query, withdraw
Derivations	calculation → offer, offer → application (broker, optional); application → contract (insurer, always); motor: application → insurance confirmation (insurer, at the request of the broker)	existing contract → contract change application (broker); contract change application → changed contract (insurer, always)	existing contract → conversion application (broker); conversion application → new contract (insurer, always)	claim report → settlement (insurer), if the declaration provides for it as an object of its own
Subprocesses	discount approval, approval reservation/acceptance, certificate, previous damage inspection, identification of persons, registration – under offer, application or contract; which of them block and when they are merged is declared by the insurer (Subprocesses)	registration and inspection at a change of vehicle, approval reservation at an increase of cover – under the contract change application; plus the subprocess under the existing contract whose result triggers the change	as contract change, under the conversion application	expert assessment, cost estimate, inspection – under the claim report; the actor is mostly a third party
Particularities	first type implemented and tried out; approval gate with confirmation token at submission; offer with validity period and premium guarantee; motor: the insurance confirmation is a business object of its own that the insurer derives from the application before the contract exists (State Diagram Motor)	no "change offer" as an object of its own: premium and consequences of the change are results at the contract change application; the changed contract is a new version of the existing one (OMDS 3: reason for change)	the new contract replaces the existing one (OMDS 3: replacement policies); which products qualify for the conversion is an inquiry on the existing contract	begins with a creation, not with a derivation; review, query and settlement are states or derivations of the insurer; documents as edits

Application process

Contract change

Conversion

Claim notification and claims handling

Business objects

calculation, offer, application, contract; in the motor line of business additionally the insurance confirmation for the registration of the vehicle

existing contract (reference, not part of the business case), contract change application, changed contract

existing contract (reference), conversion application on the new product, new contract

contract (reference), claim report; whether settlement and benefit decision are objects of their own is defined by the declaration of the type

Assessed states

calculable (calculation), acceptable (offer), submittable (application); otherwise draft

submittable (contract change application); otherwise draft

submittable (conversion application); otherwise draft

reportable (claim report); otherwise draft

Set states

calculated; accepted (offer); submitted, under review, query, accepted, rejected (application); cancelled, expired

submitted, under review, query, accepted, rejected

as contract change

reported, under review, query, settled, rejected

Edits

include and exclude a component, set an attribute value, set up and assign a risk object, add persons and application questions

the same, at the contract change application; set reason for change and effective date

the same, at the conversion application

add course of events and parties involved, add a document (also during a query)

Transitions

calculate (calculation), accept (offer), submit and close query (application), cancel

submit, close query, cancel

as contract change

report, close query, withdraw

Derivations

calculation → offer, offer → application (broker, optional); application → contract (insurer, always); motor: application → insurance confirmation (insurer, at the request of the broker)

existing contract → contract change application (broker); contract change application → changed contract (insurer, always)

existing contract → conversion application (broker); conversion application → new contract (insurer, always)

claim report → settlement (insurer), if the declaration provides for it as an object of its own

Subprocesses

discount approval, approval reservation/acceptance, certificate, previous damage inspection, identification of persons, registration – under offer, application or contract; which of them block and when they are merged is declared by the insurer (Subprocesses)

registration and inspection at a change of vehicle, approval reservation at an increase of cover – under the contract change application; plus the subprocess under the existing contract whose result triggers the change

as contract change, under the conversion application

expert assessment, cost estimate, inspection – under the claim report; the actor is mostly a third party

Particularities

first type implemented and tried out; approval gate with confirmation token at submission; offer with validity period and premium guarantee; motor: the insurance confirmation is a business object of its own that the insurer derives from the application before the contract exists (State Diagram Motor)

no "change offer" as an object of its own: premium and consequences of the change are results at the contract change application; the changed contract is a new version of the existing one (OMDS 3: reason for change)

the new contract replaces the existing one (OMDS 3: replacement policies); which products qualify for the conversion is an inquiry on the existing contract

begins with a creation, not with a derivation; review, query and settlement are states or derivations of the insurer; documents as edits

The conversion is a business case type of its own, not a variant of the contract change: it produces a new contract on another product that replaces the old one, instead of forming a version of the same contract.

The application process is one of these four types. The pages Application Process and State Diagram Motor describe it in this grid.