ECH - Overview

The Equipment Condition History (ECH) is used to record all the information obtained during inspections (except for thickness data). All significant events in the life of the Equipment should be recorded with an ECH. Writing the inspection narrative is the primary and most familiar function of the Condition History. However, there are other major record activities that are also accomplished with the Condition History. It is important to use each of the major functions.

Condition Histories are written for the Equipment IDs (that is why we call them ECH - Equipment Condition History). Once an ECH is written, it will be a permanent record that can be retrieved from either its active location or from a records archive or salvage location.

The ECH window is flexible enough to meet all needs for recording the significant events pertaining to any Equipment. ECHs can be divided into two types:

• Event or Opportunity Driven: This ECH is not linked to a Schedule, but an event is recorded, e.g. rerate performed, significant process change, a fork-lift dented the shell, etc. If no inspection data and codes are recorded either, this is referred to as a “Narrative Only” ECH.
• Schedule Driven: This ECH credits one or more Schedules and describes the work and/or findings associated with the credited Schedule(s).

In PEI Hierarchy - Overview you can see where ECHs fit in in terms of the Hierarchy. The ECH is used to capture the inspection (or other data) as specified in the Schedule. This way a Schedule is credited. Also, Narratives are recorded in the ECH. An ECH is always linked to Equipment.

The figure below explains in more detail the workflow between ECHs and Schedules: First, a Schedule is created and Approved. Then the ECH is created and the Schedule is credited to the ECH. After the inspection has taken place, the findings are recorded in the ECH codes (checklists) and narrative. Then the ECH is Approved. As soon as the ECH is Approved the Credited Schedules will become inactive. In the case of recurring Schedules, new Schedules will automatically be created and Approved.

The ECH Condition Date will become the Last Inspection Date (LID). This is used to calculate the NID for the new Schedule. The NID then becomes, for example, the RBI Maximum Inspection Interval (MII) or a User interval, added to the LID.

Or

The ECH as part of the PEI workflow.

 Note: For PEI, when the ECH is approved the LID is applied to the RBI Analysis. In PLSS it will apply the the PLSS Risk Analysis. For RCM this does not apply.

The ECH Lifecycle (steps)

The ECH lifecycle steps can be summarized as follows:

• Step A: Create an ECH (this can happen from several places in the application).
• Step B: Enter a Condition Date, Responsible Inspector, short Description (e.g. Internal, External, TA), etc.
• Step C: Credit the Schedule(s) or Select “Event/Opportunity Driven“.
• Step D: Specify the Inspection data and codes (use the available checklists and add Observations, Attachments, Photos, and Locations).
• Step E: Write a Narrative (description of actions performed, and conditions found).
• Step F: Create new Schedules / CAIRs if necessary. Note: For recurring Schedules a new Schedule is created automatically.
• Step G: Review the ECH (use the report).
• Step H: Final Approve the ECH (when Witnessing is activated, additional Supervision and Authority steps also come in here).
• Optional: Edit the new Schedules if necessary.
• Optional: If necessary, backout the ECH (e.g., when the Equipment ID is incorrect or when a Schedule was credited incorrectly).

Offline

Remember that it is possible to record your ECH offline in the field!