Talk to salesStart for free
Start for free
Knowledge management

Knowledge management for production

Kraka brings your operation's knowledge into one place: documents, manuals and tutorials from your systems, plus your people's hands-on experience. Anyone with a question at the machine simply asks it.

ISO/IEC 27001
GDPR-compliant
Hosted in Germany
Trusted by
Starting point

The knowledge is there. Just not where the work happens.

No operation has too little knowledge. It sits scattered across systems, folders and heads, and the moment it is needed, nobody can find it. So you ask a colleague. And when they're not around, you try your luck.

Scattered across systems

SharePoint, drives, folders at the workstation, manufacturer portals. Every source has its own logic.

Searching assumes knowledge

Anyone who doesn't know what the document is called won't find it. At the machine there is no time for that.

The crucial part isn't written down

How the fault is really fixed is in a colleague's head. Nobody ever wrote it down.

It walks out the door with your people

With every retirement and every resignation, a part of the operation's knowledge leaves the building.

01 · Connect

Everything you already have, usable in one place

The documents stay where they are. Kraka sits on top and makes them searchable, without anyone maintaining anything twice.

Source 01 · Your systems

Existing file stores and applications

Whatever is already documented today is connected rather than re-created.

  • SharePoint and OneDrive
  • Upload documents directly
  • Further systems on a project basis
EffortConnect once
Source 02 · Content from Kraka

What your operation creates anyway

Every tutorial and every instruction you create becomes part of the knowledge base.

  • Video tutorials, down to the single moment in the video
  • Work instructions and training
  • Operating and maintenance manuals
EffortBuilds up along the way
02 · Capture

Knowledge out of people's heads, without anyone writing it down

Most of an operation's knowledge has never been documented, because documenting is too tedious. So Kraka runs the interview itself: it asks the questions, follows up and turns the conversation into findable knowledge. Your people just talk.

Kraka asksYou said the line often runs rough after a product change. What do you notice first?
Your expert answersBy the sound. If it clacks briefly on start-up, the pre-tension is usually off.
Kraka follows upAnd what exactly do you do then?
Retighten, but only a quarter turn. Any more and the chain runs hot.
How it runs in the operation
Kraka leads, not you

The questions come automatically and adapt to what was just said. Nobody has to prepare or moderate an interview.

Spoken, not written

A conversation of about 30 minutes usually covers one station. No form, no writing, no follow-up work.

Always with review

Nothing becomes part of the knowledge base without approval. Review is done by the roles you define.

Typical occasions

Upcoming retirement
Resignation and handover
One-off knowledge capture per station
After a major fault
Conversion or new machine
Ongoing in day-to-day shifts
The differenceDocuments describe how it is meant to be. Your people know how it really runs. Afterwards both sit in the same place.
03 · Ask

Ask instead of searching, in your own language

At the machine, people ask rather than research. Kraka takes the question by voice, follows up when something is unclear and answers with the source. The answer draws on everything that has been connected or captured.

Animation: searching for error E42 across SharePoint, a network drive and folders becomes an answer from Kraka with its source: Line 3 operating manual, section 6.4, and the tutorial “Check sealing station” from minute 2:15.
Why this is more than a search
It asks back

With multiple machines, types or variants, Kraka clarifies instead of guessing.

Answer with source

Every answer points to the document or the spot in the video it came from.

Speak instead of typing

With gloves on at the machine, you speak. The answer comes in the language of the question.

Honest about gaps

If nothing solid is found, Kraka says so instead of inventing an answer. Such gaps become the list of what gets captured next.

04 · Result

One knowledge base built from both

What was connected and what came out of people's heads sit in one base. It grows with every document, every tutorial and every conversation, and it shows everyone exactly what they are allowed to see.

Knowledge graphExample
Line 3
Error E42
Sealing station
Temp. sensor
Manual L3SharePoint
Check sealingTutorial
Start-upInterview
Machines & topicsConnectedCreated in Kraka
What makes it dependable
Permissions

A detailed permission system controls who sees which knowledge, down to area, role and site.

Traceable sources

Every answer can be traced back to the document or the point in the video it came from.

Grows with the operation

Every new tutorial and every interview is instantly part of the base, with no extra effort.

Review
New knowledge is reviewed before release
Up to date
Changes to the source flow through into the answers
Roles and rights
Visibility per area, role and site
Access
At the kiosk, via QR code, on mobile and on desktop

In over 35 languages, too

People ask in the language they think in, and the answer comes back in that same language. Even when the underlying manual only exists in German.

Deutsch
Polski
Türkçe
Română
Українська
Български
Magyar
Čeština
Hrvatski
Italiano
Español
English
and more

“For us, quality, process reliability and the structured transfer of knowledge come first. With Kraka, we can document production workflows digitally and make them available for training. That creates transparency, supports our employees and helps us preserve knowledge for the long term.”

Marc NeuschlManaging Director, AVO-Werke August Beisse GmbH
Common questions

What operations want to know before connecting

Can everyone see everything?
No. The knowledge sits behind a detailed permission system in Kraka. You decide which areas, roles and sites can access which content, and the chat only answers from what the person asking is cleared to see.
Do we have to move our documents?
No. Existing file stores such as SharePoint or OneDrive are connected. The documents stay where they are and are still maintained there. You can also upload individual files directly.
Which systems can be connected?
Besides SharePoint and OneDrive, we connect further systems on a project basis. On top of that comes the content from Kraka itself: tutorials, training and work instructions are automatically part of the knowledge base.
How does undocumented knowledge get in?
Through an AI-led interview. The experienced colleague talks, Kraka asks follow-up questions and turns the conversation into structured pieces of knowledge. A conversation of about 30 minutes usually covers one station.
Is what goes into the knowledge base reviewed?
Yes, always. New content is reviewed before it is released, by the roles your operation assigns to the task.
How do the answers reach the workstation?
Via the kiosk on the shop floor, a QR code at the machine, the app on a phone, or the desktop. Questions can also be asked by voice, which with gloves on at the machine is often the only practical way.
Personal consultation

Book a personal consultation

30 minutes. Bring a recording or a document, and we'll show you live what Kraka makes of it.

When suits you?

We'll get back to you within 24 hours.

What to expect

  • 30 minutes, on your own exampleWe take one of your examples and show you what Kraka can do with it.
  • Where your plant gets stuckTogether we look at where things get stuck, and show what Kraka changes.
  • Kraka live in actionAs an LMS, as a knowledge base and in video processing.
  • A clear answerBy the end, it will be clear whether Kraka pays off for your plant.

These companies trust Kraka.

  • AVO
  • Klocke Gruppe
  • KLINGER Kempchen