Information Collection

DOE-STD-1055-93

2.2.3.1

Information Collection

Problems should be coded and clearly defined to permit status tracking.

In addition to maintenance history files, information pertinent to the most

recent occurrence is valuable during problem analysis and may be obtained

from:

Maintenance Job Requests

Shop floor activity logs

Strip-chart and other recording devices

Operator statements (facts and sy mptoms)

Troubleshooting results

Craftsperson statements

Industry experience

Information and data gathered from the most recent occurrence should be

recorded as maintenance history.

2.2.3.2

Information A nalysis, Cause D etermination, and Corrective A ction

The responsibility and authority for performing the analysis, cause

determination and corrective action recommendations should be clearly

defined.

Owner/operators and other involved/informed individuals should be

members of a problem analysis teams.

The problem analysis methodology suitable for the type problem, formality

warranted, and application of the information available should be used.

All information should be evaluated to establish a list of most probable or

associated causes (care should be taken to go beyond simply addressing

sy mptoms).

Each probable cause should be analyzed until the combination of factors

which, when corrected, should prevent recurrence of the problem is

determined. That combination of factors is the actual root cause.