Knowledge management

Knowledge management for production

Your operation's entire knowledge in one place, retrievable as a question: documents, manuals and tutorials from every system, plus the hands-on knowledge of your people.

ISO 27001
GDPR-compliant
Made in Germany
Trusted by
Klinkenberg KempchenRothkötter UnternehmensgruppeWAGU Rubber TechnologyAVOTress BrüderParlascaAuburg Quellecoolback
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 decisive part is written down nowhere

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

It walks out with the 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 stores and applications

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

  • SharePoint and OneDrive
  • Upload documents directly
  • Any further system with an interface
EffortConnect once
Source 02 · Content from Kraka

What is created in the operation 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
EffortCreated on the side
02 · Capture

Knowledge out of the 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 search, in every language

At the machine you ask, you don't research. Kraka takes the question by voice, follows up when something is unclear and answers with the source. From everything that was connected and everything that was captured.

Question by voiceThe packaging line stops and shows error E42. What do I do now?
KrakaSo I take the right manual: is this line 2 or line 3? The two have different sealing stations.
Line 3.
KrakaE42 means the sealing temperature is below the setpoint. First check the temperature sensor on the upper sealing jaw, then acknowledge the fault at the control panel.Source: Line 3 operating manual, section 6.4 · 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 type

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 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

And that in over 30 languages

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
+ 20 more
Frequent questions

What operations want to know before connecting

Does everyone then see everything?
No. The knowledge sits behind a detailed permission system in Kraka. You define which areas, roles and sites can access which content, and the chat answers exclusively from what is released for the person asking.
Do we have to move our documents?
No. Existing stores like SharePoint or OneDrive are connected, the documents stay there and continue to be maintained there. Individual files can also be uploaded directly.
Which systems can be connected?
Besides SharePoint and OneDrive, in principle any system with an interface. 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 follows up and turns the conversation into structured knowledge blocks. A conversation of about 30 minutes usually covers one station.
Is what lands in the knowledge base reviewed?
Yes, always. New content goes through a review before it is released, with the roles your operation designates for it.
How do the answers reach the workstation?
Via the kiosk on the shop floor, a QR code at the machine, the app on the phone or on the desktop. You can ask by voice, which is the only practical way with gloves on at the machine.
Ready to get started

Ready to secure your knowledge?

30 minutes. Using one of your own instructions, we'll show you exactly what we'd do with it.

Together we analyse the challenges in your operation and show how Kraka solves them.
We show you live how Kraka works — as an LMS, a knowledge base or for video processing.
By the end it will be clear whether Kraka pays off for your operation.
Johannes Oel, Gründer und Geschäftsführer von Kraka
Johannes Oel
Founder & Managing Director

I'll help you tailor Kraka precisely to your use case. Book your demo now.

Request a demo

30 minutes on your own instructions.

Book your first session with Kraka within 24 hours!