Spelling suggestions: "subject:"helpdesk"" "subject:"helpdesks""
1 |
Informační systém pro Helpdesk / Information System for Help DeskHavelka, Ondřej January 2015 (has links)
The goal of this thesis is to design and implement information system for Help Desk purposes. In the first part there are specifications of theoretical bases, standard procedures and contracts concerning Help Desk operation and also summary of advantages and requirements of such system. Second part contains description of parameters and processes using the BORM method. In the practical part is the implementaion of the designed system on the platform Microsoft Sharepoint 2010. The analytical part contains description of requirements to use this platform and description of functions which are used during the implementation. Final part contains description of the implementation itself. It is based on the parametrs and processes designed in the theoretical part and uses the Sharepoint functions described in the analytical part.
|
2 |
Implementace metrik help desk v malé IT firmě / Help Desk Metrics Implementation in a Small CompanyBraverman, Jan January 2007 (has links)
V této práci byla navržena sada metrik vhodných pro měření help desku a ta byla podrobena mutlidimenzionální analýze. Základním konceptem pro celé řešení je metodika ITIL, proto je v práci obsažena i analýza odpovídajících procesů ITIL. Pro vyzkoušení některých metrik, byly tyto nasazeny v help desk aplikaci. Navržená sada metrik byla zúžena na ty, které jsou uplatnitelné v malé firmě. Závěr práce vyhodnocuje provoz vybraných metrik nad reálnými daty a zkoumá možné způsoby interpretace získaných výsledků.
|
3 |
Creating a Help Desk using SharePoint WorkflowQuist, Harald January 2009 (has links)
<p> </p><p>Abstract</p><p>Xeratech AB is a medium-sized company in Karlstad, Sweden. Part of their business involves support of their products. This support has been managed manually; incoming errands has been received, by phone or by e-mail, and afterwards sent to a consultant for processing. This approach lacks the ability to efficiently store these errands, to make useful reports based on the work done with it, and to automatically send out notifications and e-mail to support members involved with the errand.</p><p> </p><p>The goal of this dissertation is to implement an errand support system (a help desk) able to do the above things automatically. Since Xeratech use mostly Microsoft products, and uses SharePoint as their intranet platform, a choice has been made to implement this help desk system as a SharePoint State Machine Workflow. A state machine workflow is a workflow consisting of states, transitions and events. This type of workflow has been chosen because of its resemblance to the life cycle of an errand: errands will, during its life time, change from one state to another in a non predetermined way. For instance, when an errand is created, it will start in the <em>New </em>state, the workflow will then, when a person has started working with it, transition to the <em>In Progress </em>state, followed by a number of states until finally its state is <em>Completed</em>, and the work with the errand is done.</p><p> </p><p>This workflow will then be evaluated considering its ability to facilitate the implementation of the help desk system.</p><p> </p>
|
4 |
A Comparison of the Rule and Case-based Reasoning Approaches for the Automation of Help-desk Operations at the Tier-two LevelBryant, Michael Forrester 01 January 2009 (has links)
This exploratory study investigates the hypothesis that case-based reasoning (CBR) systems have advantages over rule-based reasoning (RBR) systems in providing automated support for Tier-2 help desk operations. The literature suggests that rule-based systems are best suited for problem solving when the system being analyzed is a single-purpose, specialized system and the rules for solving the problems are clear and do not change with high frequency. Case-based systems, because of their ability to offer alternative solutions for a given problem, give help-desk technicians more flexibility. Specifically, this dissertation aims to answer the following questions:
1. Which paradigm, rule-based or case-based reasoning, results in more precise solutions to problems when compared to the solutions derived from system manuals?
2. Which paradigm, rule-based or case-based reasoning, is more convenient to maintain in terms of knowledge modification (i.e. addition, deletion, or modification of rules/cases)?
3. Which paradigm, rule-based or case-based reasoning, enables help-desk technicians to solve problems in shorter time, and therefore at lower cost?
This is an exploratory study based on data collected from field experiments. RBR and CBR based prototypes were set up to support Tier-2 help desk operations. Trained help desk operators used the system to solve a set of benchmark problems. Data collected from this exercise was analyzed to answer the three research questions.
This exploratory study supported the hypothesis that the case-based paradigm is better suited for use in help desk environments at the Tier-2 level than is the rule-based paradigm. The case-based paradigm, because of its ability to offer alternative solutions for a given problem, gave the help-desk technician flexibility in applying a solution. Alternatively, the rule-based paradigm provided a solution if, and only if, a rule existed for a solution meeting the exact problem specifications. Further, in the absence of a rule, problem research time, using the rule-based paradigm, extended the time required to formulate a solution thereby increasing the cost.
This research provided sufficient information to show that the help-desk knowledge based system utilizing the case-based shell provided better overall solutions to problems than did the rule-based shell.
|
5 |
Knowledge Management in an IT-Help Desk environmentOmarsson, Gunnar Ingi January 2010 (has links)
<p>The help desk serves as the first support level for solving IT problems but sometimes they have their own problems. These problems can be linked to the lack of access to the right knowledge which could be solved by implementing knowledge management so that agents have all the knowledge they need available to them when they need it. There is statistical data available to confirm that, by implementing this knowledge management-centric approach, there is a significant improvement in throughput and reduced times spent on calls. Yet there seems to be that there is no research available to show us the cultural, process, resource and responsibility impact of knowledge management in this environment. This is the focus of this project and by creating a special knowledge management system prototype, for a working help desk, these aspects are analyzed. The results show a minimal culture barrier, more structured processes, better access to resources and increased responsibilities.</p>
|
6 |
Creating a Help Desk using SharePoint WorkflowQuist, Harald January 2009 (has links)
Abstract Xeratech AB is a medium-sized company in Karlstad, Sweden. Part of their business involves support of their products. This support has been managed manually; incoming errands has been received, by phone or by e-mail, and afterwards sent to a consultant for processing. This approach lacks the ability to efficiently store these errands, to make useful reports based on the work done with it, and to automatically send out notifications and e-mail to support members involved with the errand. The goal of this dissertation is to implement an errand support system (a help desk) able to do the above things automatically. Since Xeratech use mostly Microsoft products, and uses SharePoint as their intranet platform, a choice has been made to implement this help desk system as a SharePoint State Machine Workflow. A state machine workflow is a workflow consisting of states, transitions and events. This type of workflow has been chosen because of its resemblance to the life cycle of an errand: errands will, during its life time, change from one state to another in a non predetermined way. For instance, when an errand is created, it will start in the New state, the workflow will then, when a person has started working with it, transition to the In Progress state, followed by a number of states until finally its state is Completed, and the work with the errand is done. This workflow will then be evaluated considering its ability to facilitate the implementation of the help desk system.
|
7 |
Technická podpora managementu incidentů / Technical Assistance of Incident Management SupportSoukup, Zdeněk January 2012 (has links)
The topic of this Master Thesis is Incident Management process as well as other processes which are inseparably linked to it, such as Problem Management, Change Management, Knowledge Management, etc. Main focus of this work is taken to the mentioned processes implementation in the real environment of the real company. Those processes are to be supported by selected information system whereas the selection itself is also part of the project. The processess are compared and optimized with use of Information Technology Infrastructure Library (ITIL).
|
8 |
Avaliação da recuperação no raciocínio baseado em caso estrutural e textual em um sistema de help-deskSá, Fábio Pessôa de 02 February 2007 (has links)
Made available in DSpace on 2015-02-04T21:45:27Z (GMT). No. of bitstreams: 1
fabio pessoa de sa.pdf: 639587 bytes, checksum: dd40b9a42e4fa77bca19755ccf66e42b (MD5)
Previous issue date: 2007-02-02 / Raciocínio Baseado em Casos (RBC) é uma técnica da Inteligência Artificial que pode ser utilizada para diagnóstico, com a finalidade de resolver problemas. Esta dissertação apresenta uma avaliação da etapa da recuperação em duas abordagens de RBC: estrutural e textual. Para a recuperação dos casos é utilizada uma base de casos existente do domínio
de help-desk. Essa base de casos é modelada de acordo com as abordagens de RBC estrutural e textual. As modelagens são desenvolvidas através de fundamentos teóricos da área de RBC e da contribuição do engenheiro de conhecimento. A recuperação no RBC estrutural utiliza a base de casos estruturada na forma de pares atributo-valor. A recuperação no RBC textual utiliza uma FAQ (Frequently Asked Questions) como base de casos.
No RBC estrutural é utilizado o método do vizinho-mais-próximo em conjunto com a medida de similaridade denominada coeficiente de casamento simples. No RBC
textual são utilizados modelos da área de Recuperação de Informação: préprocessamento do texto, pesagem de termos e uma medida de similaridade baseada no modelo de vetor.
|
9 |
Knowledge Management in an IT-Help Desk environmentOmarsson, Gunnar Ingi January 2010 (has links)
The help desk serves as the first support level for solving IT problems but sometimes they have their own problems. These problems can be linked to the lack of access to the right knowledge which could be solved by implementing knowledge management so that agents have all the knowledge they need available to them when they need it. There is statistical data available to confirm that, by implementing this knowledge management-centric approach, there is a significant improvement in throughput and reduced times spent on calls. Yet there seems to be that there is no research available to show us the cultural, process, resource and responsibility impact of knowledge management in this environment. This is the focus of this project and by creating a special knowledge management system prototype, for a working help desk, these aspects are analyzed. The results show a minimal culture barrier, more structured processes, better access to resources and increased responsibilities.
|
10 |
Měření SPA v organizaci poskytující IT služby / Measuring SPA in an organization providing IT servicesSmrček, Martin January 2007 (has links)
This diploma work concentrates on metrics for providers of IT support. Its origins are in a project for DHL IT Services. This company has recently moved centre of support for IT services serving to logistic giant DHL in EMEA region to Prague. The goal of the project was to find suitable metrics for measuring support requirements of IT services and productivity of people who provide the support. The objective of this paper is to introduce reasons for creation, principles, benefits, risks and experience from pilot implementation newly developed metric Support Point Analysis (SPA). To meet all objectives, the diploma was split into three integral parts. In the first part there are briefly summed general theoretical theses about metrics in IT, in the second part all aspects of the metrics Support Point Analysis were described in detail. In the last part there is analysis of possible areas of using SPA. There is also experience from pilot implementation in DHL IT Services write down in the last part. The main benefit of this paper consists in evaluation of SPA results and analysis of its strengths and weaknesses. Besides there are suggestions of possible ways of SPA further development.
|
Page generated in 0.0297 seconds