break/fix incidents
| 10:08 Sep 11, 2018 |
|
| English to French translations [PRO] Tech/Engineering - SAP | |||||
|---|---|---|---|---|---|
|
|
| Summary of answers provided | ||||
|---|---|---|---|---|
| 5 -2 | incidents couverts par un/le contrat [de maintenance] de type Panne-Réparation |
| ||
| 4 -1 | incidents liés à une panne ou a une réparation |
|
| Summary of reference entries provided | |||
|---|---|---|---|
| Break/fix model |
|
Answers
1 day 6 hrs confidence: 
peer agreement (net): -2
peer agreement (net): -2incidents couverts par un/le contrat [de maintenance] de type Panne-Réparation Explanation: "break/fix" is a type of contract which is basically limited to ONLY "fixing what's broken - when and if it's broken" [= reactive action], as opposed to a contract for regular maintenance [=preventative action] or a contract for providing IT services. Les services après-vente ont longtemps été partisans du modèle Break-Fix (ou Panne-Réparation), méthode réactive consistant à effectuer les réparations en fonction des besoins, en opposition à la méthode prédictive qui consiste à intervenir avant même qu'un dysfonctionnement ne survienne. Cependant, à mesure que les attentes clients évoluent et que le secteur de la production se consolide, il est plus important que jamais de réduire au minimum les temps d'arrêt, et idéalement, de les éliminer. https://www.lesechos.fr/idees-debats/cercle/cercle-174434-as... |
| ||||||||||||||||||||||||
2 hrs confidence:  peer agreement (net): -1
| |||||||||||||||||||||||||
2 hrs peer agreement (net): -1 |
| Reference: Break/fix model Reference information: break/fix model Posted by: Margaret Rouse WhatIs.com Contributor(s): Spencer Smith For IT services companies, break/fix is a method of providing IT support to customers. Break/fix services are generally fee-based and rely on a customer contacting the IT services company when repairs and upgrades are needed. While break/fix usually works on a time-and-materials basis, in which the contractor charges an hourly rate plus the cost of parts, there are some exceptions. For example, a break/fix company might offer discrete services, such as virus removal, at a flat rate instead of an hourly rate, usually because the contractor has a clear idea of the time involved. Break/fix is sometimes distinguished from managed IT services, an approach in which IT service companies take responsibility for customers' IT systems and provide monitoring and management. Whereas break/fix companies resolve their customers' IT issues only when support is required, managed service providers (MSPs) focus on preventing potential IT issues from disrupting business operations and use service-level agreement (SLA) contracts to guarantee the monitoring and management of customer IT systems at a flat fee. In the IT services industry, the break/fix service model has received criticism for being a "reactive" method for caring for customers' IT systems. Some argue that the model inherently creates a situation where break/fix companies will see greater financial gain from fixing customers' IT issues than from taking preemptive measures to prevent issues from occurring in the first place. The managed services model therefore is seen by many as a superior IT support model, because MSPs proactively monitor and manage customers' IT systems and offer a billing structure that customers can control through SLAs. While in the past, break/fix was a prevalent model for providing IT support, many IT services companies have since transitioned to the managed services model. However, numerous MSPs continue to offer and derive a portion of their annual revenue from break/fix services. This was last updated in June 2015 https://searchitchannel.techtarget.com/definition/break-fix-... -------------------------------------------------- Note added at 2 hrs (2018-09-11 12:26:34 GMT) -------------------------------------------------- What is an Incident? An incident is an event that leads to an unplanned disruption of service. The important part to remember is ‘disruption of service,’ because if an issue does not disrupt service, even if it was unplanned and unexpected, it is not an incident. For example, if a piece of hardware fails after hours when nobody is using the system, it is not an incident, because it did not disrupt service. However, if the same equipment failed during the regular workday, it would be defined as an incident because service was, in fact, disrupted. The IT help desk is often the first ones to be made aware of an incident, as they are usually the first point of contact for users experiencing issues with the system. https://blog.samanage.com/it-service-management/whats-the-di... |
| |
| Login to enter a peer comment (or grade) | ||
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.
KudoZ™ translation help
The KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.
See also:
Search millions of term translations
Your current localization setting
English
Select a language
Close search