Information gathered in this phase through a Poka-survey 7 interview:
- Scope out the outcomes targeted, user cases & KPIs impacted
- For increased success, identify priority areas across the plants, lines, equipments & workstations
- Gather basic information about the users included in the scope
- Gather basic info about the equipment in the scope
- Understand IT requirements for Poka usage in the plant.
- Bring together your project team: Project Owner & Coordinator, Executive Sponsor, Design Team, Content Creators and System Administrators
Getting you set up with personalised sessions
- Team members learn about the Poka app, content creation best practices and approaches to poka usage
- The program has weekly 3-hour sessions with your project team until go-live
- Our teams provide a combination of workshops and trainings to allow for hands-on practice
- Synchronous and asynchronous activities make optimal use of the onboarding period
- Sessions will be interspersed with assignments to evaluate learnings
desc s 2
Unlike traditional content and document management solutions built for office workers, Poka makes it possible to capture, share and manage knowledge continuously on the factory floor. Built specifically for manufacturing, Poka mirrors production operations at the plant, line, workstation and equipment level to make information easy to find, when it is needed most.
With support from the Poka Professional Services team, customers can get up and running anywhere from one to three months on average. This varies by client depending on the resources allocated, the number of people involved, and the use cases targeted.
Do you ever get the sense that a recurring production problem could be avoided or resolved faster if only you could tap into the tribal knowledge across operations? Now you can. Poka's troubleshooting knowledgebase empowers workers to find solutions to common problems more quickly and autonomously, resulting in less downtime.
All issues can be seen in a one-view digital Kanban board and consolidated by status, reporter, issue category and location. The Kanban view also showcases the amount of time elapsed since the issue was opened or the resolution time for resolved issues. Once a solution is found, the issue can be marked as resolved with a simple drag-and-drop so supervisors are kept informed. This drives quick resolutions and visibility on performance metrics.
“
ici la typo diminue de taille (de H1 à H3), apres 110 caractères. Ensuite c'est un maximum de 260 caractères. quelques mots de plus pour avoir la taille correcte”
| How We Can Integrate | Benefits of Integration | |
|---|---|---|
| CMMS | News posts can be turned into work orders in the CMMS Status updates on work orders are visible in Poka | Avoids duplicate entry of production issue in CMMS Maintenance can solve problems faster |
| MES | Bi-directional links between SoPs in QMS and instructions Quality issues posted in Poka can push report to QMS | Easier access to SoPs Complements written procedure with video |
