OR Task Team Updates

OR SIG TASK TEAM UPDATES

The following provides an update on the activities of the OR SIG Task Teams. If you have any questions regarding these activities or would like to participate on any of these Task Teams, please contact the Task Team Lead.

FACILITY REPRESENTATIVE TASK TEAM

Co-Task Team Leads: Earl Burkholder, DOE/Amarillo Area Office, (806)477-3170, eburkhol@pantex.com;
Bob Seal, DOE/ID, (208)533-4562, sealrc@id.doe.gov

15 people attended the OR SIG Facility Representative Task Team (FRTT) Meeting held on May 20, 1999, as part of the OR SIG Spring Meeting held in Oak Ridge, Tennessee. During the FRTT meeting it was reported that the OR SIG Steering Committee has voted to accept the first issue completed by the FRTT, which would allow Unusual Reports to be included in the Roll-Up Report process. The status of two additional issues currently being worked by the FRTT, Lockout/Tagout problem reporting and the FRTT policy statement was also presented. Several additional topics for possible action by the FRTT were added to the existing list. The list of issues will be reviewed following the Facility Representative Annual meeting which will be held in June 1999, since it is expected that additional topics will be identified at that meeting. The FRTT has been allowed time on the agenda at the Facility Representative Annual Meeting, and it is hoped that in addition to the identification of new issues, that several new FRTT members will be recruited.

LESSONS LEARNED TASK TEAM

The OR SIG Steering Committee voted to make the Lessons Learned Task Team inactive unless/until some area of concern comes up that is not being addressed by SELLS and/or other lessons learned media such as The Operating Experience Weekly, the Lessons Learned list server, etc.

POLICY TASK TEAM

Task Team Lead: Bob Steitler, WSRC, (803) 952-9786, robert.steitler@srs.gov

The mission of the Policy Task Team is to recommend changes regarding occurrence reporting policy to the Office of Operating Experience Analysis and Feedback (EH-33). The Policy Task Team is finalizing the Interpretation Document now that Rev. 1 to the Order has been issued. The team needs to determine where the document will reside (i.e., on the OR SIG Home Page, the OEAF home page, etc.). A draft document for the Internet has been developed and distributed to task team members and is awaiting final comments. Regardless of which Home Page the Order resides on, there will be a link to the other one(s) and possibly a hyperlink to the Order/Manual.

TRAINING TASK TEAM

Co-Task Team Leads: Lorna Dunn, Kaiser-Hill, L.L.C., (303) 966-5510, lorna.dunn@rfets.gov,
Larry McNelly, Bechtel-Jacobs Company, L.L.C., (423)574-7087, jli@bechteljacobs.org

The Training Task Team provides training and/or course material that can be used at complexes on behalf of the occurrence reporting program. In addition the training task DOE team develops and provides training for SIG members at the OR SIG meetings that will enhance professional development of the OR members. The task team updated the Occurrence Reporting Course Training Materials: Introduction to Occurrence Reporting; Occurrence Report Writing; and Reportable Occurrence Investigative Techniques to DOE Order 232.1 and the associated Manual.

The Training Task Team is currently working on three projects. The first is the production of a CBT occurrence reporting course, a joint project of the OR SIG Training Task Team and the Advanced Training Technologies SIG (ATT SIG). The second project is the concept of an Occurrence Reporting Certification process. The third project is to identify the types of training that the OR SIG members would like to have presented at the OR SIG spring meetings.

The Training Task Team Meeting met during the 1999 OR SIG Spring Meeting and opened with introductions of the eight individuals present, a review of the Purpose statement of the Task Team, and a discussion on how sites assign and conduct the Occurrence Reporting process. In some organizations, line management is responsible for the report preparation process and some use occurrence investigators individually or in teams.

Jeff Long suggested the Task Team send e-mail to each occurrence reporting point of contact listed on the homepage to request identification of the people responsible for conducting and developing training material at each site.
The Task Team will preview the presentation of the Emergency Categorization CBT program to see if something like this could be developed for the occurrence reporting process.

In addition, the following recommendations were made regarding the updating of current training materials:

Recommendation: EH-33 to keep computer classes development and updates to meet existing system (slides and workbook/training guide)
Recommendation: Bill Leonard’s Critiques curriculum be added to the OR SIG curriculum and placed on the OR SIG homepage. Consider consolidating the Critique curriculum with the Investigation curriculum.
Recommendation: Convert the four basic classes to PDF/Power Point formats and place the updated material on the OR SIG homepage. Use what was used at this workshop.
Introduction to Occurrence Reporting – Jeff Long
Occurrence Report Writing – Gary Branson
Occurrence Investigation - ____________
Critique – Bill Leonard
Corrective Action Hints – Cynthia
Lessons Learned Development – Cynthia
CBT – Karen Chandler – willing to become part of the Training Task Team
Discussed Root Cause Analysis class, determined that would remain up to the contractors since there is no sanctioned single methodology mandated by DOE at this time.
Lesson Plans need to be revised – could be just note pages in a Power Point presentation with the formal plan to be developed at the site level. Materials have been updated recently by Tim Quinn and Gary Branson for the Introduction and Report Writing classes. All need to be converted from Word Perfect since most sites are going away from that as a standard.
Glenn Buckly willing to look at the combination of the investigation and the critique classes.
Will schedule a conference call once POCs have all been identified.

TRENDING TASK TEAM

Task Team Lead: Jeff Long, LMER, (423) 574-5324, lng@ornl.gov

In addition to the largely statistical/trending activities previously undertaken by the task team, the team has expanded its scope to focus its efforts on quantitative and qualitative analysis across the complex and ways to utilize ORPS and other tools to meet analytical needs. Further, the team will play a significant role in supporting Departmental ORPS reengineering efforts with respect to trending and analysis enhancements.

The Occurrence Reporting Special Interest Group (OR-SIG) Trending and Analysis Task Team met on May 18, 1999, as part of activities associated with the 1999 ORPS Workshop/OR SIG Spring Meeting held in Oak Ridge, TN. There were eighteen people present (10 contractors, 8 DOE). Following are the minutes from that meeting.

1. The final draft of a table entitled "Occurrence Trending and Analysis Reporting Across the DOE Complex", was approved by the Task Team and later presented to the OR SIG Steering Committee at its meeting on Wednesday, May 19. The Steering Committee approved the table as a OR SIG product and it is now available on the OR SIG web page at:

http://www.orau.gov/or/att23082.htm

2. New discussion items:

A. Related to the product listed in #1 above, it was suggested that the table remain a "living document" allowing changes and additions as they are identified. Any additions or changes may be submitted through Jeff Long, Task Team Lead, for revision of the table.

B. There was discussion related to the use of ORPS data in probabilistic risk analysis to attempt to identify risk reduction received for corrective dollars spent. Since this process is being proposed through other DOE channels, no further action by our Task Team is planned regarding this item at this time.

C. An issue was raised concerning being able to trend occurrences relative to the Integrated Safety Management System's five core functions; Define the Scope of Work, Analyze the Hazards, Develop and Implement Hazard Controls, Perform Work Within Controls, and Provide Feedback and Improvement. It was suggested that a field be added to the ORPS report format to allow the entry of the appropriate Core Function (perhaps similar to the current Activity Field #18). This will be discussed further in future teleconferences.

D. Discussion about adding a standardized set of trending reports or graphs in the ORPS GUI was discussed. This would be a predetermined set of information that many folks create today through Direct Access or manual manipulation. The trending information would be some set of standardized data over time, similar to the graphical presentation available in the ORBITT system but using ORPS data. The makeup of the standardized set is to be determined. This will be discussed further in future teleconferences.

USERS' GROUP TASK TEAM

Co-Task Team Leads: Kim Wilson, West Valley Nuclear Services, Inc. (716) 942-4771, wilsonk@wv.doe.gov ; Dennis Lowry, DynMcDermott Petroleum Operations Company, (504)734-4650, dennis.lowry@spr.doe.gov

The Users' Group Task Team is responsible for providing input for enhancements to ORP, evaluating proposed enhancements and providing recommendations for or against implementation, and beta testing all proposed software changes and any new software relating to ORPS and the use of ORPS data.

The User’s Group met on May 18, 1999. Thirteen individuals attended. The group reviewed the list of issues identified by the User’s Group in the past in order to determine whether they are open, closed, or no longer necessary. A priority was also assigned to the existing open issues. The updated list will be distributed to all User’s Group members and the Steering Committee. New issues can be submitted to Jeannie Boyle ( and Kim Wilson (. Now that the ORPS GUI is operational , the next step for the User’s Group is to begin working on the open items that had been on hold until the system went into production. Stay tuned for more details!

EH-33 has developed two forms for use in requesting enhancements and reporting problems with the ORPS GUI. If you would like a copy of these, please contact Jeannie Boyle and request the ORPS GUI Problem Report and ORPS GUI Recommended Enhancement forms.

One final announcement: Dennis Lowry, of DynMcDermott Petroleum Operations Company, has graciously agreed to become a co-chair of the User’s Group. Dennis has previously served as the chair for this task team, and has continued to provide input as a member of the task team over the years. Dennis can be reached at (504) 734-4650, or by e-mail at Welcome back aboard the ship, co-captain!

OR SIG Home Page

Last Update: September 1999