Approach and Artefacts
Development takes place in a working group. The work starts with motor insurance. The results are submitted to the steering committee for evaluation.
The use cases covered and the standardised business processes (using BPMN, among others, including an exhaustive list of the permitted process variants) are defined by a parallel working group. They are an input to this initiative, but not part of it.
Standard, reference implementation and tools are developed together and published together (see Tools).
Business Case Types in the Order of Their Implementation
All business case types follow the same model of business case, business objects, operation kinds and process knowledge (Business Objects and Operations). They are worked out one after the other; each type receives its description in the grid of the model, its declaration as process knowledge and its mapping to the existing OMDS 3 services before the reference implementation implements it.
-
Application process (Application Process) – first, because it is the most frequent transaction and contains all operation kinds. Implemented and tried out are product selection, the configuration as a draft at the server with edits, and the calculation; offer, application and contract follow, together with the switch of the existing services to business objects with states of their own.
-
Contract change – existing contract → contract change application → changed contract; the same edits as in the application process, supplemented by reason for change and effective date.
-
Conversion – existing contract → conversion application on a current product → new contract that replaces the old one.
-
Claim notification and claims handling – begins with a creation (claim report for the contract); review, query and settlement lie with the insurer.
The example insurers declare per type which variants they offer (Example Insurers).
Artefacts in the Order of Their Creation
-
Definition of the interfaces for the services: vocabulary for business case, business objects, states and operation kinds, declaration per business case type, OpenAPI operations
-
Sample insurer as a Java web application
-
MCP server based on the sample insurer
-
Reference wrapper on top of the existing SOAP services as proof of backward compatibility: the sample insurer with a SOAP adapter instead of the example tariff (Backward Compatibility)
-
Documentation website
-
Sample broker as an Angular client
-
Self-tests for insurers as JUnit tests
-
Self-tests for brokers as JUnit tests