See a worldwide directory.

 

ReliaSoft > Softwares > Enterprise Software > QTMS > Tour [1]
A Tour of QTMS: A Conceptual Overview
Closing the loop on problem resolution...
ReliaSoft's Quality Tracking and Management System - QTMS

  [1]  [2]  [3]  [4]  [5]  [6]  [7]

Go to Step 2

Section 1 introduces QTMS's unique ability to individually address both incidents and problems and expands on the incident/problem relationship. This section also presents high-level flow charts of the QTMS process and the 8D problem resolution process. 

QTMS is unique in its design and framework in the fact that it can be used to address both individual incidents and the underlying problems. In QTMS terminology, a single problem can have many incidents. Incidents are dealt with as they occur, while problems (the underlying causes of the incidents) are analyzed and resolved through a formal Problem Resolution Process (PRR).

QTMS uses an incident/problem relation in its FRACAS process.  Incidents are issues/failures reported by customers, found during testing, etc. As an example, consider a product with a faulty component. Multiple customers may experience/report a failure due to that faulty component. Each failure is an incident. From an engineering perspective, all of these incidents are due to the faulty component; thus the problem is the faulty component. In this scenario, customer support or repair technicians will attempt to resolve the incident (i.e. get the customer up and running). However, resolving individual incidents does not resolve the problem. The problem is resolved by dealing with the faulty component.

  

In QTMS terminology, problems are solved through Problem Resolution Reports (PRRs). A PRR may have one or more incidents associated with it. The resolution of a PRR follows an 8D process.

A high level flowchart of the process. The following graphic depicts a high level overview of the incident resolution process and the subsequent assignment of incident reports to PRRs (click the graphic to see a larger, clearer version).

Click to enlarge... High Level Flow Chart [Click to Enlarge]

Click to enlarge...

Addressing problems. Once incidents have been classified into problems, responsible engineering teams address and resolve the problems (PRRs) through an 8D process, as depicted in the next graphic (click the graphic to see a larger, clearer version). 

Click to enlarge... Resolving Incidents [Click to Enlarge]

Click to enlarge...

The entire process is managed by QTMS, which in turn also becomes the data repository for subsequent analysis and lessons learned. Next...

  [1]  [2]  [3]  [4]  [5]  [6]  [7]

Go to Step 2

QTMS v4.1

 Enterprise Software
  
 QTMS Home
 Summary
 Overview Tour
 Demo/Info
 FAQ
 Benefits
Contact ReliaSoft...
Questions? 
Additional Info?
Call 
1.888.886.0410
(U.S. & Canada) or
+1.520.886.0410
(international) or e-mail 
Sales@ReliaSoft.com

 

[Home]   [Softwares]   [Treinamentos]   [Consultorias]   [Painel de Confiabilidade]   [A Empresa]   [Clientes]   [weibull.com]

Copyright ©1998-2005 ReliaSoft Brasil, Todos os Direitos Reservados
Última Alteração: 24-02-05
 

LEGAL [Termos de Uso] [Links]
[Privacidade das Informações]

Contate Webmaster
Tel:
+55 11 5584-5456