1. TA-V eB Performance Improvement Overview
Title slide
Sandia National Laboratories is a multi-program laboratory  managed  and operated  by  Sandia Corporation, a wholly owned subsidiary of  Lockheed Martin  Corporation, for the U.S. Department of Energy’s National  Nuclear  Security Administration under contract   DE-AC04-94AL85000.

2. Topics Background and Pedigree Definitions Implementation in eB
Condition Report and Corrective Action Walkthrough
Demonstration using eB Performance Improvement Processes

3. Performance Improvement Program
A set of processes to enable the capture, tracking, analysis, and resulting actions taken as a result of a specific event.
Reactive Events – Adverse conditions. Examples: radiation leak, hazardous sidewalk, using cell phone while walking.
Proactive Events – Opportunities for improvement. Examples: Training survey, workplace suggestions, better mousetrap.
Mission. Purpose. Flags. 3

4. Origin 2005 - R.E. Ginna Plant in Ontario, NY
1 of 5 nuclear plants within the Constellation Energy Nuclear Energy Group
Existing eB customer for their Master Equipment Lists (MEL), Configuration Management (CM), Records Management (RM) and Information Management (IM).
CEG wanted to merge 4 independent Performance Improvement programs: Self-Assessment, Trending Activities, Corrective Action, and Human Performance
Institute of Nuclear Power Operations (INPO®)
Published INPO Guidelines for Performance Improvement at Nuclear Power Stations. This document detailed an overall model of performance improvement processes and practices.
eB CAP was formulated, based on the INPO Performance Improvement Model, as a solution to CEG’s requirements.

5. Performance Improvement Model

6. Condition Reporting Condition Report (CR) Corrective Action (CA)
This event reports the occurrence of a condition (generally, non-desirable) that must be dealt with. Typically, any person can generate a Condition Report. Each Condition Report is evaluated, possibly resulting in one or more Corrective Actions. The Corrective Actions are created as Successor Events to the CR, with some CA’s (depending on their CA Class) preventing completion of the CR until its CA’s are completed.
Corrective Action (CA)
Events of this class are created in response to a CR and are successor events to the CR. They may be reactive in the sense of correcting a problem, or proactive in the sense of taking steps to prevent a recurrence or enhancing the business system. ETM has built-in rules regarding the relationship between a CR and a CA.
Effectiveness Review (ER)
Events of this class are in the general classification of Corrective Actions but ERs evaluate the effectiveness of a related Corrective Action in resolving the original Condition Report. ERs remain open past the timeframe of the Condition Report to which they are associated.

7. Action Items Action Item (AI) Action (A)
These are generic events that may be created at will. They have no pre-defined focus. Action events are created as a Nested event of the Action Item, for the purpose of tracking the individual action(s) taken. The Action Item event cannot be completed until Nested Actions have been completed.
Action (A)
Action events are created as a Nested event of the Action Item, for the purpose of tracking the individual action(s) taken. As a Nested event, the Action must be completed before the related Action Item event can be completed.

8. Operating Experience Operating Experience (OE) Proactive events.
If warranted, one or more CR events might be created and attached to the event.
Experiences from outside entities are evaluated for possible applicability to the current entity. INPO provides a service to subscribers, collecting and distributing Operating Experiences from all nuclear facilities.
Internal Operating Experiences are also generated. They are also evaluated for applicable to other customer departments and/or sites. These may also be uploaded to INPO for distribution to other nuclear vendors.

9. Human Performance Observation (OB or OBS) Benchmark (BM)
The observer decides to observe others performing their work and fills out a survey recording the observed activities. These can also be reactive in response to noticing activities that deserve comment. If warranted, one or more CR events might be created and attached to the observation event.
Benchmark (BM)
These represent a comparison of a part of the operation for the purpose of determining best practices. Communication with outside entities is commonly involved. Surveys may be attached. If warranted, one or more CR events might be created and attached to the event.
Self-Assessment (SA)
These are evaluations conducted of the entities own operations, equipment, etc. Surveys are completed to record the findings in detail. If warranted, one or more CR events might be created and attached to the event.
Knowledge Item (KI)
These are events for recording and developing items for a knowledge base (BoK). These include such concepts as lessons learned, problem solutions, key decisions or assumptions, metrics, industry and reference information, experience or know-how.
First Notification (FN)
Provides ability to notify a group of users (ie, Management) of an occurring event or condition, possibly related to existing objects in eB (documents, events, projects, etc).

10. CR Workflow Steps
Depending on Level assessment of CR, workflow is 4 to 8 steps.
Initiator creates the CR
CR is Screened and appropriate Level assessed – A-D, Invalid, or Duplicate
CR is Evaluated and Appropriate CA’s completed.
If Invalid or Duplicate, CR proceeds to CR Closure
For Levels A and B additional Reviews/Approvals needed after this step.
CA Completion step is holding point until all CA’s are completed.
If Level A, additional Reviews/Approvals needed after this step.
CR Closure validates information and completes CR.

11. Demonstration CR Workflow

12. eB Corrective Action Workflow

13. Higher Risk / Rigor Lower Risk / Rigor
Graded Workflows in eB
Higher Risk / Rigor
Lower Risk / Rigor

14. Initiation

15. Relating Documents, Components, and More
At ANY point of a CAP
workflow any items may
be related to the item

16. Screening and Category Selection

17. Acceptance of Category and Workflow
Assign trending option
here if applicable
To be shown on
later screen

18. Create Corrective Action

19. Corrective Action Implementation

20. Corrective Action Completion

21. CR Closure

22. Condition Report Summary

23. Search and Report Functionality

24. Questions?