Poka captures the knowledge your experts find time to record. FieldPal unlocks what you already wrote down.
Your organisation is already sitting on OEM manuals, service bulletins and years of repair history. Nobody has to create it. FieldPal makes it answerable out loud, at the asset.
Who this is for
Organisations worried about experienced people retiring and taking three decades of judgement with them. Poka built a good business on that problem, and the concern is entirely legitimate.
What Poka does well
Poka's insight was that tribal knowledge lives in people, not documents, and the way to get it out is to make recording it easy and socially rewarding. Short videos, made by the operator who solved the problem, findable by the next person who hits it. Add structured problem-solving and skills tracking and you have a plant floor engagement programme that genuinely works when it takes hold. Poka is now part of IFS.
Where FieldPal starts
From an asset you already own. OEM manuals, service bulletins, technical instructions and the repair history sitting in your existing systems: enormous, already written, and effectively unreadable at the point of work, because nobody searches a 400-page PDF on a phone under a vehicle. Find makes that material answerable by voice.
Head to head
| Capability | FieldPal Find | Poka |
|---|---|---|
| Works from documents you already have | Yes | Limited |
| Requires a content creation programme | No | Yes |
| Knowledge format | Spoken answer | Video and articles |
| Hands-free operation | Yes | No |
| Head-mounted devices (RealWear) | Yes | No |
| Captures fixes as they happen, in the worker's words | Via Capture | Core to the product |
| Skills matrix and training management | No | Extensive |
| Plant floor engagement and gamification | No | Extensive |
The argument
The dependency worth examining
Poka’s knowledge base contains what people took the time to record.
That is a content programme. It needs champions, encouragement, management attention, and a culture where recording a fix is normal rather than an imposition. Where it lands, it is powerful. Where it stalls, you have a licence and an empty library, and the technicians go back to phoning the one person who knows.
Watching versus asking
A four-minute video is an excellent record of a repair and a poor answer to a question. The technician has to find the right one, watch it, and hold the useful thirty seconds in their head while working.
Find is asked, and answers.
“The computer is flagging an overheat, do I check the heating system or the battery first?”
Back comes the relevant guidance from the bulletin that covers it, spoken aloud, with the source named, while the technician’s hands stay exactly where they are.
Where the two ideas meet
Poka is right about the important thing: knowledge generated at the point of work is the most valuable kind.
FieldPal Capture collects it as a by-product of the job rather than as an extra task. The technician describes the repair, the structured record is built, and that record becomes part of what Find can answer from tomorrow.
No separate recording step. Nothing that depends on anyone feeling like making a video at the end of a long shift.
Which one is right for you
Choose Poka if
- You are running a plant floor engagement and training programme and want the tooling for it
- Skills matrices and competency management are a core requirement
- Video is genuinely the right format for your knowledge
- You are already an IFS customer
Choose FieldPal if
- Your knowledge already exists in manuals, bulletins and repair history
- You can't bet the outcome on a content creation programme succeeding
- Your workers are mobile, in the field, with their hands occupied
- You want the answer, not the video
Point us at the documents you already have
Send a set of manuals and bulletins and a slice of repair history. We'll show your technicians asking real questions and getting answers from your own material, hands free.