Why AI-capable OMDS 3 Services?

Under the working title Fit for the Future, a VVO working group is revising the OMDS 3 interface so that AI agents can operate it. The existing SOAP services remain in operation. This page summarises benefits, approach and protection of existing investments.

Benefits for the Market

Lower integration costs. Brokers and software providers can integrate more easily with AI support instead of implementing every interface by hand.
Shorter time to market. Product variants and new product generations go to market without a software release, because the product knowledge can be transmitted at runtime.
Greater distribution reach. If the integration effort drops, more brokers and service providers integrate.
Products without interface compromises. Product variants can be described concretely and rolled out, e.g. for specific sales partners.

What Changes in the Approach

Until now	In future
WSDL, XSD and Word documents	Machine-readable standard: OpenAPI, JSON-LD, SHACL, BPMN
Deviations between insurers described in prose	Permitted process variants listed exhaustively and declared in machine-readable form
New application, contract change and conversion as separate concepts	One common model for all business case types – application process, contract change, conversion, claim notification and claims handling – made of business objects, operation kinds and process knowledge (Business Objects and Operations)
The standard is completed and then validated during implementation	Standard, reference implementation and tools are developed together and published together
Conformance is a promise	Conformance is a test result
Product knowledge cast into software	Product knowledge declarative and retrievable at runtime

Until now

In future

WSDL, XSD and Word documents

Machine-readable standard: OpenAPI, JSON-LD, SHACL, BPMN

Deviations between insurers described in prose

Permitted process variants listed exhaustively and declared in machine-readable form

New application, contract change and conversion as separate concepts

One common model for all business case types – application process, contract change, conversion, claim notification and claims handling – made of business objects, operation kinds and process knowledge (Business Objects and Operations)

The standard is completed and then validated during implementation

Standard, reference implementation and tools are developed together and published together

Conformance is a promise

Conformance is a test result

Product knowledge cast into software

Product knowledge declarative and retrievable at runtime

Why Development with AI Support

The working group builds the validator, test suites, reference implementation and SDKs itself. In the past this would have required budget and external service providers.
Design, example, test case and documentation are created in parallel instead of one after the other. Contradictions become apparent immediately, not only at the first implementation.
Every version of the standard is delivered as an executable release. There is no waiting for a first implementation.
The domain expertise stays with the experts. AI takes over the routine work, not the decisions.

What Do "AI-capable Services" Mean in Practice?

"AI" here does not mean uncontrolled generation, but the automated, error-free operation of the interface by modern software agents:

No risk for core systems and rating: The mathematical premium calculation, risk assessment and policy issuing remain 100 % deterministic and unchanged in the insurer’s data centre. There is no risk of AI "hallucinations".
Model Context Protocol (MCP): Through a standardised MCP server, AI assistants (e.g. copilots in broker management systems) can access the services directly. Brokers can have quotes calculated by voice input or free text without filling in 30 individual fields manually.
Rule checks before submission: The interface supplies plausibility rules in machine-readable form. The client or AI agent checks data locally before submitting it. This avoids unnecessary round trips.
Faster partner integration: Software companies no longer have to implement manuals by hand. AI-supported development tools generate integrations based on the executable standard.

What Remains

Investment protection. The existing SOAP services remain in operation. An insurer can offer the new services as a wrapper on top of them without changing its backend systems, and schedule the switch itself. No cut-off date and no parallel operation of two worlds.
Business substance. The concepts developed for new application, conversion, contract change, status notification and document provision remain valid. This is a revision, not a reinvention: new application, contract change and conversion are placed as business case types on one common model instead of each receiving services of its own.
Expertise stays in the country. The standard and the tools are developed in the Austrian working group. The domain and process knowledge stays with the VVO, the insurers and the domestic software companies instead of becoming dependent on external providers.

Approach

Development takes place in a working group. The work starts with motor insurance and the business case type application process; contract change, conversion and claim notification follow in the same model. 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.