Understanding event data collection: Part 1
By Ken Latino -- Plant Engineering, 7/1/2004
Editor's note: This is the first of a two-part series on the importance of effective event data collection for reliability analysis. The second part will appear in the August issue.
Collecting event data is a minimum requirement to measure the effectiveness of your current asset management strategies. Without this information one tends to allocate resources on the "problem of the day." This means you probably do not have a systematic approach to removing defects from your operation. Having a complete set of event data for all asset events provides a much clearer understanding of how to get the greatest return from your human and capital resources.
Sources of event dataEvent data can come from a variety of sources such as a maintenance management system, predictive and inspection systems, as well as production systems. For this discussion, we will focus our attention primarily on collecting event data related to equipment that resides in a computerized maintenance management system (CMMS).
It is important to understand the reasoning behind the data collection effort before getting into the details of how it is actually accomplished. The collection of event data has a double benefit. The primary benefit of comprehensive event data is to alert process owners as to whether their asset strategies are effective. Once ineffective strategies are identified, the same event data are used to drill down and determine the causes of the ineffective strategies.
What is reliability event data?Reliability event data can comprise many items within many contexts. For purposes of this discussion criteria of reliability event data include:
- Work events that occur on equipment
- Type of work performed
- Conditions found at the time of work
- Technical findings after work is completed
- Dates/time associated with the work
- Cost associated with performing the work.
When an event occurs on a piece of equipment, it is critical to record what type of event actually occurred. For example, was it a failure, repair, or preventive maintenance (PM)? What was the condition of the equipment at the time of the event? Some of the most critical information to be included in the recording of any event are the date and time stamps related to the event and the costs associated with that event — for example, labor, material, contractor, and production losses (see "Recommended event data to collect").
After the work is completed, it is necessary to record the technical finding such as the failed item, failure mode, cause, and several other data elements discussed in further detail in Part 2 of this article in the August issue.
A company's balanced scorecard is composed of standardized, enterprise-wide performance measurements related to production assets. A balanced scorecard provides a holistic view of key performance indicators (KPIs) spanning multiple plants and allows management to make strategic, fact-based decisions with greater confidence.
| Author Information |
| Ken Latino is a senior consultant in Meridium, Inc. Asset Performance Management Consulting Group, a root cause analysis practitioner, frequent speaker on the topic at conferences, and an educator. He is author of several root cause analysis courses, books, and trade magazine articles. Ken designed a software program that assists analysts in conducting a disciplined root cause analysis. He can be reached at 540-344-9205 ext. 1176 or KLatino@meridium.com. |
|




















