1. ORR Team Leader May 2005 Revision
Detailed Responsibilities
13L

2. Upon successful completion of this topic, the student should be able to:
Describe the ORR Team Leader’s detailed activities and considerations associated with planning and conducting an ORR/RA including:
Startup Authorization Authority
Plan of Action
Event Dates
Implementation Plan
Team Selection Criteria
Team Level of Experience
Team Qualification Requirements
Logistics/Planning
Management of the Team
Interfaces:
- Oversight Entities
- Startup Authority
- Facility Contractor
Necessary Briefings/Meetings
ORR Final Report
13L REV May 2005 Revision

3. Authorization Authority
Your Boss:
Report is for His/Her decision;
Line Decision Maker for Scope Changes.
Close Interface:
Regular Briefings during Review;
Immediate Notification of Major Issues.
Should Formally Direct you to Commence the ORR/RA.
For CORR/CRA, a Senior Line Manager will fill this role.
13L REV May 2005 Revision

4. Plan of Action Should name you as Team Leader.
Specifies “Geographic” Scope:
What the Authorization Authority directs you to review.
Basis for writing your Implementation Plan.
Specifies prerequisites, proposed start dates:
Planning only.
Approved by DOE/NNSA Authorization Authority for both CORR/CRA and DOE/NSA ORR/RA.
13L REV May 2005 Revision

5. Event Dates Be Flexible! Be Alert to Recommend Pre-Event Activities:
Emergency Preparedness (EP) Drills;
Integrated Equipment Tests.
Critical Team Interface Issue . . .
You Must be Proactive . . .
13L REV May 2005 Revision

6. Implementation Plan Your responsibility . . .
You prepare, approve, forward . . .
You resolve/consider comments with oversight organizations (internal, external) . . .
Team Building/Training Opportunity . . .
What you commit to do to answer the question - are the criteria within the POA scope met?
13L REV May 2005 Revision

7. Team Selection Criteria
Your Call!
Requirements:
Technical competence;
Assessment experience/training;
Independence in the Review area.
Good Ideas:
Writing skills;
Team player;
“Big Picture” . . .
Always good to have a Senior Advisor!
13L REV May 2005 Revision

8. Team Level of Experience
Must cover the technical issues within the scope:
Documented and Defendable Expertise.
Pay particular attention to contentious issues . . .
Match the IP . . .
A few ringers . . .
A few “gold nuggets” . . .
13L REV May 2005 Revision

9. Team Qualification Requirements
Specified in Order:
“...team leaders must determine and document qualifications…”
Sample Forms Available:
Standard ( ) and DOE/NNSA Web Pages.
Knowledge of Facility Specific Information:
Tours, Required Reading, etc.
13L REV May 2005 Revision

10. Logistics/Planning Pay attention to this!
Discuss early with Site/Facility . . .
Good Administrative Assistant is critical . . .
Additional Admin support for report may be essential . . .
Work Space and equipment must be a priority . . .
Hints in the Team Leaders Handbook:
DOE-HDBK (
Start early . . .
13L REV May 2005 Revision

11. Managing the Interfaces NO SECRETS!
Oversight Entities:
Full Access - Best Practice;
Candor!
Authorization Authority (Senior Contractor Management for CORR/CRA)
Must be Fully Informed; Brief periodically;
Initiate the Communication;
Local DOE/NNSA Participation.
Facility Contractor:
Fully Informed, Share Draft Information.
13L REV May 2005 Revision

12. Briefings and Meetings
Daily Team Meeting:
Shares information, contractor, DOE/NNSA . . .
Team Synergy.
Closeout Briefing:
Key Issues - Pre-Start Findings;
Startup Recommendation;
Finding Closure Recommendation.
Follow-up:
As Required (LPSO, DNFSB, etc)
13L REV May 2005 Revision

13. ORR Final Report Your Product! Suggested Format in Standard/website:
Select and provide an example to Team.
Unclassified preferred; as required . . .
Key Elements (Order Requirements):
Order Compliance as per POA;
Lessons Learned;
ISMS Statement;
Your Recommendation;
Addressed to Authorization/Startup Authority.
13L REV May 2005 Revision

14. ORR Final Report some keys to success
Plan to complete before team leaves site . . .
Define Timeline and expectations to team early . . .
Provide example formats early-forms & Summary . . .
Develop the report skeleton and background early . . .
Arrange for Admin support to edit, format, collate . . .
Push daily input to individual forms . . .
Emphasize timely factual accuracy . . .
Describe the review/approval process to the team . . .
Continuous classification review of product . . .
13L REV May 2005 Revision

15. If the Results of Review are not Successful
Significant team decision. Facts must support:
Sleep on it; Confront team to defend conclusion.
Discuss situation and options with Authorization Authority (Senior Contractor Management).
Two Options:
Suspend the Review. Interim Report including what was done and areas not done.
Final report for completed Functional Areas (FA);
High level discussion and findings for incomplete FAs.
Terminate the Review. Report results with basis for repeat of entire ORR/RA.
13L REV May 2005 Revision

16. Team Leader (TL) Problem Areas
Team Leader not qualified: Selection criteria guidance not detailed enough (e.g., independence, experience) . . .
TL not assigned soon enough (POA timely approval) . . .
TL does not communicate expectations to team with enough lead time . . .
TL does not communicate drill/evolution expectations to facility . . .
Site access for team not gained ahead of time . . .
Logistic needs not communicated to site with enough lead time . . .
TL does not tailor CRADs based on Pre-Visit or Team not at Pre-Visit, or no Pre-Visit) . . .
CRAD assigned to TL . . .
13L REV May 2005 Revision

17. Final Thoughts Readiness to start is performance-based . . .
Adequacy of infrastructure programs is more audit-like . . .
Determination of adequacy versus perfection . . .
Frequently a RA/CRA may not focus as much on infrastructure programs as an ORR/CORR . . .
13L REV May 2005 Revision