Search the Community
Showing results for tags 'maintenance'.
Found 2 results
-
Q 539. There are 3 major types of maintenance methods - Corrective, Preventive and Predictive. While we all understand Corrective and Preventive maintenance, what is the concept of Predictive maintenance? How is it different from other two and what are the tools used for predictive maintenance? Note for website visitors - Two questions are asked every week on this platform. One on Tuesday and the other on Friday. All questions so far can be seen here - https://www.benchmarksixsigma.com/forum/lean-six-sigma-business-excellence-questions/ Please visit the forum home page at https://www.benchmarksixsigma.com/forum/ to respond to the latest question open till the next Tuesday/ Friday evening 5 PM as per Indian Standard Time. Questions launched on Tuesdays are open till Friday and questions launched on Friday are open till Tuesday. When you respond to this question, your answer will not be visible till it is reviewed. Only non-plagiarised (plagiarism below 5-10%) responses will be approved. If you have doubts about plagiarism, please check your answer with a plagiarism checker tool like https://smallseotools.com/plagiarism-checker/ before submitting. The best answer is always shown at the top among responses and the author finds honorable mention in our Business Excellence dictionary at https://www.benchmarksixsigma.com/forum/business-excellence-dictionary-glossary/ along with the related term
-
Metrics For " Schedule Variance " For Maintenance Projects In It Industry
Guest posted a topic in Applicability in IT Sector
Hello Guys, Generally, in an IT Industry, there are 2 kinds of Projects "Development" and "Maintenance" project.In a Development project, we could have feature development and span over a period of time followed by stabilization etc. . and is generally a regular development where as in Maintenance, mostly it deals with Bug fixing or Ticket Fixing ... The question is in Development Projects the measurement of Schedule Variance is easy and could be straight forward = (Actual - Planned )/Planed (could be +ve or -ve depending if planned > actual or vice versa), But in Bug Fixing task how can we measure the same. Challenges in Bug Fixing : The customer could come and say that whatever tickets that you were working is not important for you to fix today .I want you to work on 20 new tickets and are of higher priority .and this has been case in ticket fixing mode as the priority keeps on changing .Sometimes ,a low priority tickets (based on classification) becomes a higher priority next day , you may have to leave all the previous working tickets and starts again .Secondly , each ticket has its own complexity and therefore how planning is feasible in such case . How can we factor such changes to plan for a ticket? Are there any schedule variance metrics which can measure this challenge and provide a true reflection of data. and also the planning can be done because ..(please note that even bucketing of tickets does not work because tomorrow you may need to work on the new set of tickets ) Please suggest multiple options for planning and measurement ??
