IKVision Logo IKVision

From Data to Decisions and Actions

IKVision combines RAG, Law as Code, relational databases, vector databases, and LLM agents into controllable decision and action systems.

Selected Use Cases

Application Review and Benefit Recommendation

An LLM agent analyzes incoming applications, identifies the requested benefit, compares the provided information against legal requirements, and generates a traceable recommendation.

Application
Identify Benefit
Evaluate Rules
Recommendation

AI Unit Operations

1
📥Input
Application, PDF, form
2
📚Knowledge
RAG, legal texts
3
⚖️Logic
Law-as-Code model
4
🧠Reasoning
LLM agent
5
Action
Recommendation
6
🛡️Control
Case worker, approval

Why This Approach?

Structured pre-assessment instead of manual document review

Government agencies, insurance providers, and organizations receive a large number of applications every day. Each application must be reviewed, classified, and evaluated against applicable legal requirements.

This work is highly repetitive, yet at the same time critical. Incorrect assessments, overlooked exclusion criteria, or missing information lead to delays, additional inquiries, and dissatisfaction.

The LLM agent therefore performs a structured pre-assessment. It identifies the requested benefit, retrieves the relevant legal foundations from the database, and systematically evaluates the applicant’s information against these requirements.

The result is not an automated decision, but a well-founded and traceable recommendation, including justification and references to relevant legal provisions.

Intelligent Knowledge System with RAG

Corporate knowledge is distributed across documents, emails, databases, and business systems. RAG unlocks this information semantically and provides it in the right context.

Documents
Embeddings
Vector Database
Answer

AI Unit Operations

1
📥Input
User question
2
📚Knowledge
Documents, vector database
3
⚖️Logic
Source and access control
4
🧠Reasoning
LLM with context
5
Action
Verifiable answer
6
🛡️Control
Sources, audit, access

Why RAG?

Context-aware answers instead of generic AI output

Without access to approved internal sources, AI-generated answers remain risky. RAG reduces hallucinations, improves traceability, and makes knowledge accountable.

A technician asks a seemingly simple question: 'Can we postpone maintenance of this system by one month?'

A generic AI would provide a broad answer based on assumptions. A RAG system, however, incorporates approved maintenance manuals, service bulletins, and internal operational documentation.

The system identifies that a specific installed component has a documented increased failure risk if maintenance intervals are exceeded. In addition, the system is operating in a production environment.

The resulting answer is therefore not 'probably safe,' but:

"Postponing maintenance is not recommended. Component Z has a documented increased risk of failure if the maintenance interval is exceeded. We recommend performing maintenance within the planned service window."

RAG does not generate plausible answers—it delivers context-based and accountable decisions.

Event Invitation Agent

An LLM agent creates personalized invitation messages based on customer data, event information, and approved content templates.

Customer Data
Template
Draft
Approval

AI Unit Operations

1
📥Input
Customer data
2
📚Knowledge
Event data, templates
3
⚖️Logic
Approval rules
4
🧠Reasoning
LLM agent
5
Action
Invitation message
6
🛡️Control
Explicit approval

Why Controlled Automation?

Communication requires context, tone, and approval

Automation without approval can damage trust. The agent creates the draft, but delivery only takes place after human review.

A company is planning an exclusive customer event. Customer information, agenda details, and text templates are already available. Fully automated delivery would be technically possible—but communicatively risky.

The LLM agent therefore first creates a personalized invitation message. It considers the recipient’s role, relationship, and context, and highlights sensitive aspects such as tone and timing.

Only after explicit approval by marketing or sales is the invitation sent. The result is controlled, high-quality communication instead of uncontrolled automation.

Decision Support and Recommendations

Agents analyze internal information, identify dependencies, and prepare well-founded recommendations. The final decision remains with the human.

Request
Analysis
Evaluation
Recommendation

AI Unit Operations

1
📥Input
Business request
2
📚Knowledge
Internal documents, databases
3
⚖️Logic
Policies, technical rules
4
🧠Reasoning
LLM agent
5
Action
Recommendation
6
🛡️Control
Human decision

Why Recommendations Instead of Decisions?

The agent improves decision-making but does not replace it

An agent can collect information, identify risks, and evaluate options. Responsibility remains where it belongs: with the human decision-maker.

A customer asks support: 'Is the latest firmware suitable for my storage system?' What sounds simple is, in reality, technically complex.

The LLM agent does not provide a generic answer. Instead, it restructures the request, identifies missing information, and retrieves relevant content from approved knowledge sources such as release notes and upgrade guides.

After evaluating the available information, the agent determines that the new firmware is compatible but requires a prior hard drive firmware update. A direct upgrade would involve significant risk.

Instead of providing a guess, the agent delivers a justified recommendation, including the correct sequence of steps, risk mitigation guidance, and maintenance recommendations.

The final decision remains with the human—but it is based on complete context, validated rules, and documented expertise.

Agentic Process Execution

Agents trigger specific actions based on events, context, and rules—controlled, documented, and, where required, subject to approval.

Event
Context
Rule
Action

AI Unit Operations

1
📥Input
Event, status change
2
📚Knowledge
Process data, history
3
⚖️Logic
Rules, thresholds
4
🧠Reasoning
Agentic context evaluation
5
Action
Workflow, API, notification
6
🛡️Control
Logging, approval, escalation

Why Agents?

Rules alone do not understand context

Traditional automation triggers actions based on predefined rules. Agents additionally evaluate context, dependencies, and risks before acting or requesting approval.

An inventory level falls below a defined minimum threshold. A traditional automation system would immediately trigger a replenishment order.

An LLM agent, however, evaluates the broader context: outstanding deliveries, production schedules, supplier status, and historical consumption patterns.

Instead of placing an order automatically, the agent prepares a recommendation, suggests alternatives, and presents the decision for controlled approval.

Agentic processes reduce costs without sacrificing control.

Unsere Leistungen

Strategische KI-Beratung

Analyse von Prozessen, Daten und Rahmenbedingungen. Entwicklung realistischer KI-Roadmaps mit Fokus auf Nutzen, Datenschutz und Umsetzbarkeit.

RAG-Wissenssysteme

Semantische Erschließung von Dokumenten, Datenbanken und Fachwissen. Antworten auf Basis kontrollierter Unternehmensdaten.

Law as Code

Transformation von Gesetzen, Richtlinien und Regelwerken in nachvollziehbare, maschinenlesbare Entscheidungslogik.

LLM-basierte Business-Agenten

Agenten zur Analyse von Informationen, Vorbereitung von Entscheidungen und kontrollierten Ausführung von Prozessschritten.

Get to Know IKVision

We would be happy to discuss your processes, your data and your goals with you.

Contact IKVision