{"id":42545,"date":"2026-08-16T11:42:04","date_gmt":"2026-08-16T09:42:04","guid":{"rendered":"https:\/\/www.logicline.de\/knowledge-transfer-service-machinery-and-equipment-manufacturers"},"modified":"2026-08-16T11:46:32","modified_gmt":"2026-08-16T09:46:32","slug":"knowledge-transfer-service-machinery-and-equipment-manufacturers","status":"publish","type":"post","link":"https:\/\/www.logicline.de\/en\/knowledge-transfer-service-machinery-and-equipment-manufacturers","title":{"rendered":"When the Best Technician Retires: Preserving Service Knowledge Before It Leaves the Company"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"42545\" class=\"elementor elementor-42545 elementor-42535\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-7c03afc0 e-flex e-con-boxed e-con e-parent\" data-id=\"7c03afc0\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-61419d4e elementor-widget elementor-widget-text-editor\" data-id=\"61419d4e\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<strong>The best troubleshooter on the service team is rarely the colleague with the most entries in the system. It\u2019s the one who already knows which assembly is being referred to when the call comes in, because he\u2019s been working with that model series for twenty years. <\/strong> If this colleague retires, his knowledge will remain available only as long as the team remembers his personal phone number.\n\nKnowledge transfer in the service department is therefore decided by the data structure\u2014and this happens long before the notice period begins. The bottom line for the head of service and executive management:\n<ul>\n \t<li><strong>The risk lies with just a few people.<\/strong> At mass-production manufacturers with a large installed base, diagnostic expertise is concentrated among a handful of senior technicians per machine generation.<\/li>\n \t<li><strong>Recording the data is the easier part.<\/strong> Interviews, tandem assignments, and AI-powered note-taking help capture knowledge that\u2019s stored in people\u2019s minds.<\/li>\n \t<li><strong>The benefit is realized only when the data is retrieved.<\/strong> A knowledge article is useful when it appears when you open a ticket for a specific machine, not when it&#8217;s just sitting in a wiki.<\/li>\n \t<li><strong>A prerequisite is a complete machine file.<\/strong> Without reference to the model series, configuration, and serial number, verified knowledge remains a pool with no recipient.<\/li>\n<\/ul>\n<h2>What Goes with the Technician and What Stays Behind<\/h2>\nWhat is usually documented is the target state: circuit diagrams, maintenance schedules, spare parts lists. What\u2019s missing is the experience gained from instances of deviation. Which fault pattern in the 2011 model series indicates bearing play and which indicates a sensor failure. Which customer operates their system in three shifts and therefore exhibits different wear patterns. Which modification made six years ago was never properly documented.\n\nThis knowledge is specific to each individual and can be identified by the following signs:\n<ul>\n \t<li>When things escalate within the team, it&#8217;s always the same two or three people.<\/li>\n \t<li>The first-time resolution rate varies greatly among technicians, but not among machine types.<\/li>\n \t<li>A coworker&#8217;s vacation is causing some appointments with certain clients to be rescheduled.<\/li>\n \t<li>It takes new technicians months before they can take charge of a product line on their own.<\/li>\n \t<li>Repeat visits are becoming more common for older generations of machines.<\/li>\n<\/ul>\nDemographic pressures follow a different rhythm than the shortage of skilled workers caused by economic conditions. The cyclical shortage has recently eased: According to <a href=\"https:\/\/www.ifo.de\/pressemitteilung\/2026-02-18\/fachkraeftemangel-nimmt-ab\" target=\"_blank\" rel=\"noopener\">the ifo Business Climate Survey \u201cSkilled Labor Shortage Is Declining\u201d (February 2026)<\/a>, about 19 percent of companies in the machinery and equipment sector reported a shortage of skilled workers\u2014significantly fewer than in previous years. This does not change the fact that service team members are retiring. These retirements are tied to birth cohorts rather than the order situation, and they can be planned years in advance. That\u2019s the good news: you know when the time will come.\n<div style=\"border: 1px solid #e00817; background: #fdf5f6; padding: 18px 22px; margin: 28px 0; border-radius: 4px;\">\n<p style=\"margin: 0;\"><strong>How many of your product lines are connected to a single head?<\/strong>\nIn 30 minutes, we\u2019ll walk you through your service organization: where knowledge is tied to specific individuals, which departures are expected over the next three years, and where it makes the most sense to start capturing that information. No slide presentations.\n\u2192 <a href=\"https:\/\/www.logicline.de\/en\/contact\"><strong>Schedule an introductory call<\/strong><\/a><\/p>\n\n<\/div>\n<h2>Why Wikis and Explanatory Videos Rarely Solve the Problem<\/h2>\nThe usual response before retirement is a knowledge capture initiative. The colleague is given four weeks to write down whatever comes to mind and shoot a few videos at the machine. The material ends up on the intranet. Two years later, no one looks for it there anymore.\n\nThe problem is availability when service is needed, not data entry. Three reasons why inventory isn&#8217;t getting where it needs to be:\n\n<strong>No machine reference.<\/strong> The article is titled \u201cNotes on the H Series\u201d and is stored in a folder. However, his starting point in his daily work is the ticket with serial number 4711. There is no connection between the two, so he can only find the article if he knows it exists.\n\n<strong>No need for maintenance.<\/strong> If knowledge isn&#8217;t maintained as part of the work process, it becomes obsolete. After two software releases and a change in vendors, half of it is no longer accurate, and no one notices because no one looks into it.\n\n<strong>No format for diagnosis.<\/strong> Free-form text describes what the expert knows. It doesn\u2019t guide anyone through a decision. Someone new to the field needs a clear sequence: symptom, diagnostic step, result, next step. We\u2019ve described how knowledge can be meaningfully embedded in the process in a separate article on <a href=\"https:\/\/www.logicline.de\/en\/how-the-integration-of-knowledge-management-simplifies-service\">integrating knowledge management into service<\/a>.\n<h2>Three Ways to Put Your Knowledge into Practice<\/h2>\nWhen it comes to data collection itself, three methods have proven effective in service organizations. They are not mutually exclusive; rather, they come into play at different stages.\n<figure><img fetchpriority=\"high\" decoding=\"async\" src=\"\/wp-content\/uploads\/2026\/08\/wissenstransfer-vom-kopf-zur-struktur-en.svg\" alt=\"Three steps in knowledge transfer for service: Collection via interviews, tandem assignments, and AI-supported data collection; integration into the machine context via the Digital Machine File; and retrieval during service calls via the Service Console and SDI.\" width=\"1600\" height=\"740\" \/><figcaption>Capture, embed, retrieve: The value is realized in the second step, when the knowledge is linked to the machine context.<\/figcaption><\/figure>\n<h3>Structured Expert Interviews<\/h3>\nThe format is a guided interview based on real-life cases. You\u2019ll take twenty completed service calls from the past two years that the expert has resolved and work through each one individually: What was the symptom described in the call? What did you check first, and why? How did you recognize the incorrect assumption? The case serves as the anchor; otherwise, the expert will end up stating the obvious because their own knowledge seems self-evident to them.\n\nTwo hours per session, a meeting minutes taker who comes from the service department and can ask follow-up questions. The result is error profiles with test logic, not just descriptions.\n<h3>Tandem and Shadowing Assignments<\/h3>\nThe senior technician goes on a call with a younger colleague, following this sequence: first, the junior observes; then, he works under supervision; and finally, he takes over, with the senior technician available only by phone. This conveys exactly the aspects that no interview can capture: practical skills, prioritizing tasks under time pressure, and interacting with the customer on-site.\n\nThe effort involved is real; a tandem requires a second technician for each assignment. Plan for this based on the product lines where the reduction takes effect first, not across the board.\n<h3>AI-Powered Data Collection in the Workflow<\/h3>\nFor some time now, service reports, phone notes, and call logs have been automatedly analyzed and condensed into drafts for knowledge base articles. A voice-guided interview is also possible: After a call, the technician dictates what was unusual, and receives a structured draft in return, which they simply need to review and correct.\n\nThe advantage lies in the threshold. Someone who stops writing articles after ten hours on the job might still speak for another three minutes. The final decision on technical accuracy remains with a human; otherwise, half-baked knowledge masquerading as authority finds its way into the system.\n<h3>What to Include and What to Omit<\/h3>\nThe most common mistake in data collection projects is the desire for completeness. A technician with thirty years of experience can fill weeks of work without any of it translating into practical results in day-to-day operations. Instead, apply a filter before the first session begins.\n\nIt is worth noting anything that meets three conditions: The issue occurs repeatedly, the solution cannot be derived from the existing documentation, and a mistake costs time or requires a second trip to the site. Anything already listed in the schematic, maintenance schedule, or spare parts catalog does not belong in an interview. Nor should anything that has happened only once in twelve years.\n\nIn practice, this filter results in a manageable number of error patterns per product series, and these few account for the majority of escalations. The list serves as the work queue. It can be worked through in just a few sessions and supplemented later as operations continue.\n<table>\n<thead>\n<tr>\n<th>Method<\/th>\n<th>Suitable for<\/th>\n<th>Effort<\/th>\n<th>Limit<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Structured Interviews<\/td>\n<td>Fault Patterns and Test Logic by Product Series<\/td>\n<td>2\u20133 days per expert, spread out<\/td>\n<td>Records only what the expert remembers<\/td>\n<\/tr>\n<tr>\n<td>Tandem\/Shadowing Assignments<\/td>\n<td>Procedures, Prioritization, Customer Interaction<\/td>\n<td>Second technician per assignment<\/td>\n<td>Not scalable; requires preparation before departure<\/td>\n<\/tr>\n<tr>\n<td>AI-powered data collection<\/td>\n<td>Continuous flow of knowledge from operations<\/td>\n<td>Low per case; one-time setup<\/td>\n<td>Requires subject matter expert approval and clean source data<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Anchoring Knowledge in the Machine Context<\/h2>\nThis is where it is decided whether the data collection is worthwhile. A knowledge article must be linked to the specifics of the service case: the model series, the configuration, and the serial number. This linkage requires that the installed base be organized in a structured manner to begin with. This is exactly what the <a href=\"https:\/\/www.logicline.de\/en\/services\/digital-machine-file\">Digital Machine File (IOTAM)<\/a> provides: one data record per machine, including its history, modifications, software versions, and service history.\n\nOnce this structure is in place, knowledge can be linked to it. logicline helped develop the Salesforce integration for Empolis Service Express: Diagnosis knowledge that has been recorded appears in the service console in a context-specific manner for the specific machine while the employee is processing the case. The technician sees the relevant fault patterns for the system in front of them without having to search through an archive first. We\u2019ve covered the methodological aspects of this\u2014namely, structure, peer review, and KCS\u2014in our overview article on <a href=\"https:\/\/www.logicline.de\/en\/knowledge-management-in-the-mechanical-engineering-service-sector\">knowledge management in service<\/a>.\n\nA typical scenario in machinery and equipment: A senior technician is familiar with the characteristic failure pattern of an older generation of machines because he has seen it repeatedly over the years. None of this is documented. After he leaves the company, the number of escalations for that exact model series increases, and younger colleagues are sent out on follow-up calls more frequently. If these cases are reviewed in advance during interviews and linked to the model series as knowledge articles, the next technician will find the troubleshooting steps when opening the ticket, without even knowing they exist.\n\nThis knowledge extends even further beyond the field service team. Through <strong>Service Decision Intelligence (SDI)<\/strong>, the verified knowledge base\u2014along with machine, order, and sensor data\u2014is made available to the inside sales staff handling phone calls and to AI agents in Salesforce. The key here is source citation: Every recommendation shows which product and which data record it is based on, and SDI runs within the customer\u2019s infrastructure, ensuring that the company\u2019s expert knowledge stays within the company. That is the difference between being documented and being actionable.\n<h2>Classification: Knowledge retention belongs in the \u201cConnect\u201d stage<\/h2>\nIn the &#8221; <strong>Digitize \u2192 Connect \u2192 Decide \u2192 Automate<\/strong> &#8221; model, knowledge transfer occurs at stage two. Stage one provides the prerequisite: the structured machine file. Without it, the documented knowledge has nowhere to be anchored.\n\nIf you reverse the order and record data first, you\u2019ll end up with material that will have to be painstakingly reorganized later. Those who consider the integration process at the same time lay the groundwork for step three: As soon as knowledge is linked to the asset and combined with service history and operational data, decisions regarding service can be supported in a traceable manner rather than merely described.\n<h2>Next step<\/h2>\nThe loss of expert knowledge is a planning problem with a known timeline. The key factor is whether the recorded information can be retrieved when service is needed, and that depends on the database.\n\nTwo pragmatic approaches:\n<ul>\n \t<li><strong><a href=\"https:\/\/www.logicline.de\/en\/services\/installed-base-assessment\">Installed Base Assessment<\/a><\/strong> \u2013 if your installed base is currently scattered across ERP systems, Excel, and file storage systems. Without a clean machine record, the anchor points for knowledge are missing.<\/li>\n \t<li><strong><a href=\"https:\/\/www.logicline.de\/en\/contact\">introductory call<\/a><\/strong> \u2013 once the database is set up and you want to know exactly how data entry and retrieval work together, including which product lines will be addressed first.<\/li>\n<\/ul>\nIn both cases, the rule is: Start with the product lines where the next discontinuation is scheduled, even if the documentation for those lines is the most limited.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<section data-dce-background-color=\"#00000000\" class=\"elementor-element elementor-element-c254285 e-flex e-con-boxed e-con e-parent\" data-id=\"c254285\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;}\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t<div data-dce-background-color=\"#FFFFFF\" class=\"elementor-element elementor-element-55aff5e e-flex e-con-boxed e-con e-child\" data-id=\"55aff5e\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;}\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t<div class=\"elementor-element elementor-element-48de356 e-con-full e-flex e-con e-child\" data-id=\"48de356\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t<div class=\"elementor-element elementor-element-4b7d6a6 e-flex e-con-boxed e-con e-child\" data-id=\"4b7d6a6\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-0fa94fe elementor-widget elementor-widget-heading\" data-id=\"0fa94fe\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">FAQs<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ed3a7f2 elementor-widget elementor-widget-n-accordion\" data-id=\"ed3a7f2\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;default_state&quot;:&quot;expanded&quot;,&quot;max_items_expended&quot;:&quot;one&quot;,&quot;n_accordion_animation_duration&quot;:{&quot;unit&quot;:&quot;ms&quot;,&quot;size&quot;:400,&quot;sizes&quot;:[]}}\" data-widget_type=\"nested-accordion.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"e-n-accordion\" aria-label=\"Accordion. Open links with Enter or Space, close with Escape, and navigate with Arrow Keys\">\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2480\" class=\"e-n-accordion-item\" open>\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"1\" tabindex=\"0\" aria-expanded=\"true\" aria-controls=\"e-n-accordion-item-2480\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> What exactly does knowledge transfer mean in the context of service? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2480\" class=\"elementor-element elementor-element-8046bac e-flex e-con-boxed e-con e-child\" data-id=\"8046bac\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-e3a4f16 elementor-widget elementor-widget-text-editor\" data-id=\"e3a4f16\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Knowledge transfer in service means capturing and structuring person-specific diagnoses and expert knowledge in such a way that it can be retrieved for the next service call. This involves two steps: capturing the information through interviews, tandem assignments, or AI-supported logging; and linking the results to the specific machine\u2014that is, its model series, configuration, and serial number. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2481\" class=\"e-n-accordion-item\" >\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"2\" tabindex=\"-1\" aria-expanded=\"false\" aria-controls=\"e-n-accordion-item-2481\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> When should you start documenting your knowledge before retiring? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2481\" class=\"elementor-element elementor-element-5414f61 e-con-full e-flex e-con e-child\" data-id=\"5414f61\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1e5ed46 elementor-widget elementor-widget-text-editor\" data-id=\"1e5ed46\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Twelve to eighteen months before departure. Interviews can be conducted in a few weeks, but tandem assignments require significantly more lead time because they are tied to actual service assignments, and a younger colleague should accompany several cases from the same model series. A four-week notice period is only enough for a rough assessment of the situation.  <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2482\" class=\"e-n-accordion-item\" >\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"3\" tabindex=\"-1\" aria-expanded=\"false\" aria-controls=\"e-n-accordion-item-2482\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> Why isn't a wiki enough for preserving knowledge? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2482\" class=\"elementor-element elementor-element-cca8e05 e-con-full e-flex e-con e-child\" data-id=\"cca8e05\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-7504c5c elementor-widget elementor-widget-text-editor\" data-id=\"7504c5c\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>A wiki is a storage location and does not interfere with the work process. The technician accesses a serial number via the ticket. If there is no link between the item and the machine, the technician can only find the information if he knows it exists. Added to this is the maintenance aspect: knowledge that lies outside the process becomes outdated with every software update without anyone noticing.   <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2483\" class=\"e-n-accordion-item\" >\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"4\" tabindex=\"-1\" aria-expanded=\"false\" aria-controls=\"e-n-accordion-item-2483\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> What role does the Digital Machine File play in knowledge transfer? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2483\" class=\"elementor-element elementor-element-4fc6b46 e-con-full e-flex e-con e-child\" data-id=\"4fc6b46\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-79f5387 elementor-widget elementor-widget-text-editor\" data-id=\"79f5387\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>It provides the foundation. The Digital Machine File (IOTAM) maintains a structured record of each machine\u2019s life cycle, modifications, software versions, and service history. Only then can a knowledge article be assigned to a specific model series or configuration and automatically displayed when the case is opened. Without this structure, verified knowledge remains a pool with no specific audience.   <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2484\" class=\"e-n-accordion-item\" >\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"5\" tabindex=\"-1\" aria-expanded=\"false\" aria-controls=\"e-n-accordion-item-2484\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> Can AI replace the expert knowledge of retiring technicians? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2484\" class=\"elementor-element elementor-element-0e62110 e-con-full e-flex e-con e-child\" data-id=\"0e62110\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-60b8663 elementor-widget elementor-widget-text-editor\" data-id=\"60b8663\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>It doesn\u2019t replace them, but it lowers the data capture threshold and improves retrieval. Voice-guided data capture after a service call takes the technician minutes instead of an hour of paperwork. When retrieving information, an intelligence layer such as Service Decision Intelligence (SDI) ensures that knowledge articles, machine data, and service history are evaluated together, with source citations for each recommendation. Technical approval of the content remains the responsibility of an experienced colleague.   <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t\t<details id=\"e-n-accordion-item-2485\" class=\"e-n-accordion-item\" >\n\t\t\t\t<summary class=\"e-n-accordion-item-title\" data-accordion-index=\"6\" tabindex=\"-1\" aria-expanded=\"false\" aria-controls=\"e-n-accordion-item-2485\" >\n\t\t\t\t\t<span class='e-n-accordion-item-title-header'><h4 class=\"e-n-accordion-item-title-text\"> How can you tell if service knowledge is too heavily reliant on individual employees? <\/h4><\/span>\n\t\t\t\t\t\t\t<span class='e-n-accordion-item-title-icon'>\n\t\t\t<span class='e-opened' ><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t<span class='e-closed'><svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t<\/span>\n\n\t\t\t\t\t\t<\/summary>\n\t\t\t\t<div role=\"region\" aria-labelledby=\"e-n-accordion-item-2485\" class=\"elementor-element elementor-element-b64a09a e-con-full e-flex e-con e-child\" data-id=\"b64a09a\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-857ea34 elementor-widget elementor-widget-text-editor\" data-id=\"857ea34\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Recurring patterns in everyday life: Escalations always involve the same two or three names; the first-call resolution rate varies more widely among technicians than among machine types; a colleague\u2019s vacation causes customer appointments to be rescheduled; and follow-up visits are more common for older model series. Each of these signals indicates that the solution lies in people\u2019s minds, not in the organizational structure. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/details>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>The best troubleshooter on the service team is rarely the colleague with the most entries in the system. It\u2019s the one who already knows which assembly is being referred to when the call comes in, because he\u2019s been working with that model series for twenty years. If this colleague retires, his knowledge will remain available [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":42530,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[43052],"tags":[],"class_list":["post-42545","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-service-processes-field-service"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts\/42545","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/comments?post=42545"}],"version-history":[{"count":5,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts\/42545\/revisions"}],"predecessor-version":[{"id":42550,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts\/42545\/revisions\/42550"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/media\/42530"}],"wp:attachment":[{"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/media?parent=42545"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/categories?post=42545"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/tags?post=42545"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}