{"id":42652,"date":"2026-09-08T07:52:11","date_gmt":"2026-09-08T05:52:11","guid":{"rendered":"https:\/\/www.logicline.de\/service-knowledge-base-machinery-and-equipment"},"modified":"2026-09-08T07:57:34","modified_gmt":"2026-09-08T05:57:34","slug":"service-knowledge-base-machinery-and-equipment","status":"publish","type":"post","link":"https:\/\/www.logicline.de\/en\/service-knowledge-base-machinery-and-equipment","title":{"rendered":"Organizing Service Knowledge: How Machinery and Equipment Manufacturers Build a Knowledge Base That Technicians Actually Use"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"42652\" class=\"elementor elementor-42652 elementor-42638\" 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>A technician stands in front of a machine that has stopped running, opens the ticket for serial number 4711, and searches the knowledge base for the error symptoms. He gets two hundred hits for \u201cvibration\u201d or not a single one for that specific model series. <\/strong> In both cases, he ends up calling the colleague who knows the machine. The database exists, but it&#8217;s not helpful.\n\nThe bottleneck is the structure, not the number of articles. A service knowledge base in machinery and equipment stands or falls on whether knowledge is tied to a specific asset or is organized into a flat list of topics. The short version for the head of service and operations:\n<ul>\n \t<li><strong>The same symptom has a different solution for each model series.<\/strong> A category structure such as \u201cElectrical \/ Mechanical \/ Software\u201d therefore leads the technician nowhere.<\/li>\n \t<li><strong>Knowledge is anchored in the machine context.<\/strong> Asset type, configuration, and fault code are the three key factors that define each item.<\/li>\n \t<li><strong>Each article follows a set format.<\/strong> Symptom, verified cause, troubleshooting steps, required spare parts\u2014in that order, always the same.<\/li>\n \t<li><strong>A structured machine file is required.<\/strong> Without it, there is no anchor to which the article can be attached.<\/li>\n<\/ul>\n<h2>Why Most Knowledge Bases Gather Dust in the Department<\/h2>\nAlmost all guides on building a knowledge base come from the IT support field. In that context, a problem is usually reproducible: a password reset works the same way for every user. This is not the case in machine service. The same symptom\u2014such as a temperature alarm on the spindle\u2014indicates a sensor defect in the 2014 model series but a problem with the coolant line in the revised 2019 version. If you categorize both cases under \u201cSpindle \/ Temperature,\u201d you\u2019ll create an article that misleads users in half of all cases.\n\nAdded to this is the growing volume of documentation. In many service organizations, knowledge is stored in a folder structure following the pattern \u201cManuals \/ 2019 \/ Electrical,\u201d supplemented by PDFs on a network drive and notes stored in people\u2019s heads. The same error is described three different ways there, and twice it\u2019s outdated. The technician, under time pressure, searches briefly, finds conflicting information, and picks up the phone. The system was expensive to set up and is dead capital in day-to-day operations.\n\nA robust knowledge base fulfills two tasks at once: It must link the article to the correct machine, and it must convert it into a format that guides the decision-making process. Both are matters of structure, not a question of the tool used.\n<div style=\"border: 1px solid #e00817; background: #fdf5f6; padding: 18px 22px; margin: 28px 0; border-radius: 4px;\">\n<p style=\"margin: 0;\"><strong>Is your knowledge base going unused, even though it contains content?<\/strong>\nIn 30 minutes, we\u2019ll use a specific machine model to see how your service items can be linked to the asset and where the current structure falls short. No PowerPoint presentation\u2014just a look at your records.\n\u2192 <a href=\"https:\/\/www.logicline.de\/en\/contact\"><strong>Schedule an introductory call<\/strong><\/a><\/p>\n\n<\/div>\n<h2>Anchoring Knowledge in the Machine Context<\/h2>\nThe key decision is decided before the first article: What is the basis of this knowledge? The answer is the machine context, which consists of three levels.\n<ul>\n \t<li><strong>Asset Type \/ Series<\/strong> \u2013 the machine generation to which the article applies. A fault description for Series H is often incorrect for the successor series.<\/li>\n \t<li><strong>Configuration<\/strong> \u2014custom design, installed options, software version. Two systems from the same series may differ in these respects.<\/li>\n \t<li><strong>Fault Code \/ Symptom<\/strong> \u2013 the specific entry point from the service case that the technician uses to find the part.<\/li>\n<\/ul>\nThis link requires that the installed base be organized in a structured manner. That is exactly what the <a href=\"https:\/\/www.logicline.de\/en\/services\/digital-machine-file\">Digital Machine File (IOTAM)<\/a> does: it provides one data record per machine, including the model series, configuration, modifications, software versions, and service history. Only this data record provides the knowledge article with a specific reference. When opening the ticket for serial number 4711, the articles that match this model series and configuration appear, rather than the general topic folder.\n<figure><img fetchpriority=\"high\" decoding=\"async\" src=\"\/wp-content\/uploads\/2026\/09\/servicewissen-flach-vs-verankert-en.svg\" alt=\"Comparison of two storage structures for service knowledge: on the left, a flat list of folders and topics where articles are hard to find and out of date; on the right, a knowledge article anchored to the machine context\u2014comprising asset type, configuration, and fault code\u2014and following the structure: symptom, cause, solution steps, and spare parts.\" width=\"1600\" height=\"820\" \/><figcaption>Same content, two locations: It is only by linking the item to the model series, configuration, and fault code that it can be located when service is required.<\/figcaption><\/figure>\n<h2>The Structure of a Knowledge Article<\/h2>\nOnce the anchor is established, the second structural decision follows: the internal structure of each article. Free-form text describes what an expert knows, but it doesn\u2019t guide anyone through a diagnosis. A beginner needs a fixed sequence, and that sequence is the same for every article.\n<div class=\"tbl\">\n<table>\n<thead>\n<tr>\n<th>Module<\/th>\n<th>Contents<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Symptom \/ Fault Code<\/strong><\/td>\n<td>The observable entry as it appears in the ticket<\/td>\n<td>Fault code E-42, spindle temperature above threshold<\/td>\n<\/tr>\n<tr>\n<td><strong>Scope<\/strong><\/td>\n<td>Series, configuration, software version (if applicable)<\/td>\n<td>H Series, starting with software version 3.2<\/td>\n<\/tr>\n<tr>\n<td><strong>Confirmed Cause<\/strong><\/td>\n<td>The confirmed cause, not the assumption<\/td>\n<td>Coolant flow rate too low, filter clogged<\/td>\n<\/tr>\n<tr>\n<td><strong>Steps to the Solution<\/strong><\/td>\n<td>Numbered testing and action steps with results<\/td>\n<td>1. Measure the flow rate, 2. Check the filter, 3. Replace it<\/td>\n<\/tr>\n<tr>\n<td><strong>spare parts<\/strong><\/td>\n<td>Specific part numbers for the configuration<\/td>\n<td>Filter Cartridge Part No. 55-2071<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\nStandardized templates for these modules are the most effective way to ensure consistency. If every article follows the same structure, the technician will find the solution steps in the same place, regardless of who wrote the article.\n<h3>Pros and Cons: A Comparison<\/h3>\nA weak article is titled \u201cProblems with the Spindle\u201d and consists of three paragraphs of continuous text without specifying the model series. While the content may be accurate, it is useless in practice because it remains unclear whether it applies to the machine in question, and because the reader must deduce the steps to take from the text itself.\n\nA good article is titled \u201cE-42 Spindle Temperature, H Series, SW 3.2 and Later,\u201d states the verified cause in a single sentence, and lists four numbered steps with the corresponding part numbers. It is shorter than the poor one and immediately usable in the field. The rule behind this is: better to be concise and immediately available than comprehensive and unused.\n<h2>Keep Metadata and Maintenance Simple<\/h2>\nFor the tagging to work, each item requires a few mandatory pieces of information as metadata: product series, configuration, fault code, and processing status. These fields decide whether the item appears automatically in the ticket. Everything else is optional.\n\nThe second condition is frictionless maintenance. Knowledge that is maintained outside the work process becomes obsolete. A streamlined approval process has proven effective: A technician creates the article when a case is opened, and a knowledge coordinator with service experience reviews and publishes it. The coordinator does not write all the content themselves; otherwise, they become a bottleneck. It also makes sense to set an update rate as a target so that outdated articles are flagged before a technician follows them. We described how this knowledge capture can be methodically embedded into the service processes in our 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>What the platform runs on<\/h2>\nThe structure is the real work; the tools are already well-developed. For a specialized knowledge base with guided diagnoses, we rely on Empolis Service Express. logicline helped develop the Salesforce integration for Empolis Service Express: Knowledge articles and guided diagnostic flows appear filtered by the specific machine directly in the service console while the employee is processing the case. The structural principles described here apply regardless of the tool and can also be implemented with Salesforce Knowledge; the key factor remains anchoring them to the machine context.\n\nGoing one step further, the platform extends beyond manual search. Through <strong>Service Decision Intelligence (SDI)<\/strong>, the verified knowledge base\u2014along with machine, order, and sensor data\u2014is made available to inside sales representatives on the phone and to AI agents in Salesforce. Every recommendation includes a source citation to the underlying article, and SDI runs on the customer\u2019s infrastructure. Without a structured knowledge base, such AI in customer service remains piecemeal because it lacks a citable foundation.\n<h2>Classification: A structured knowledge base belongs in the \u201cConnect\u201d stage<\/h2>\nIn the <strong>\u201cDigitize \u2192 Connect \u2192 Decide \u2192 Automate\u201d<\/strong> model, the service knowledge base is located at level two. Level one provides the prerequisite: the structured machine file as an anchor. At level two, the knowledge associated with this anchor is combined with service history and operational data. This lays the foundation for level three, where AI supports decisions in a transparent manner.\n\nTwo related topics are addressed in separate articles: The overview article on <a href=\"https:\/\/www.logicline.de\/en\/knowledge-management-in-the-mechanical-engineering-service-sector\">knowledge management in service<\/a> provides an in-depth look at the methodology behind it\u2014namely, KCS principles and measurement. The article on <a href=\"https:\/\/www.logicline.de\/en\/wissenstransfer-service-maschinenbau-2\">knowledge transfer prior to retirement<\/a> addresses how individual expert knowledge is incorporated into the knowledge base in the first place. This article focuses on the structure of the knowledge base itself.\n<h2>Next step<\/h2>\nWith a service knowledge base, the structure of the database decides its usefulness: It must identify the connection to the specific machine. The first step, therefore, is to take an honest look at 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 when the installed base is currently spread across ERP systems, Excel, and file storage systems. Without a structured machine file, the knowledge base lacks a foundation.<\/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 determine specifically which taxonomy and templates are suitable for your machine fleet and in which service area the pilot project will begin.<\/li>\n<\/ul>\nIn both cases, the rule is: Start with the product lines that generate the most escalations. That&#8217;s where a structured approach pays off first.\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\"> How do I structure a service knowledge base in machinery and equipment? <\/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>Based on the machine context. Each knowledge article is linked to an asset type, model series, configuration, and fault code so that it appears for the specific machine when the ticket is opened. A category structure such as \u201cElectrical \/ Mechanical \/ Software,\u201d on the other hand, is misleading because the same symptom can have different causes depending on the model series.  <\/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\"> What should a service knowledge article include? <\/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>Five standard sections: the symptom or fault code as the starting point, the scope (model series and configuration), the verified cause, the numbered troubleshooting steps, and the required spare parts with part numbers. This order remains consistent in every article so that technicians can always find the information in the same place. <\/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 folder or topic structure enough? <\/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>Because in day-to-day service operations, the entry point is a serial number, not a topic folder. Without a link between the part and the machine, the technician can only find the information if he knows it exists. Add to that the maintenance aspect: In a flat filing system, the same error is often recorded multiple times and inconsistently, and no one notices when a part becomes obsolete.  <\/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 metadata does a knowledge article need? <\/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>The required fields are Series, Configuration, Fault Code, and Processing Status. These few pieces of information decide whether the item automatically appears under the correct case. Additional tagging is optional and should not complicate data maintenance.  <\/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\"> Salesforce Knowledge or a specialized knowledge base? <\/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>That depends on the complexity. For structured service articles and variants, Salesforce Knowledge is often sufficient. For guided diagnostic flows and complex variant logic, a specialized platform such as Empolis Service Express\u2014whose Salesforce integration was co-developed by logicline\u2014is suitable. The structural principles are the same in both cases: alignment with the machine context and a fixed article schema.   <\/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 do I keep the knowledge base up to date? <\/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>Through a streamlined approval process: Technicians create articles as needed, and a knowledge coordinator with service experience reviews and publishes them. A target update rate ensures that outdated articles are flagged. Knowledge that must be maintained outside of this process, on the other hand, becomes obsolete with every software release.  <\/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>A technician stands in front of a machine that has stopped running, opens the ticket for serial number 4711, and searches the knowledge base for the error symptoms. He gets two hundred hits for \u201cvibration\u201d or not a single one for that specific model series. In both cases, he ends up calling the colleague who [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":42640,"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-42652","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\/42652","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=42652"}],"version-history":[{"count":4,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts\/42652\/revisions"}],"predecessor-version":[{"id":42656,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/posts\/42652\/revisions\/42656"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/media\/42640"}],"wp:attachment":[{"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/media?parent=42652"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/categories?post=42652"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicline.de\/en\/wp-json\/wp\/v2\/tags?post=42652"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}