|
Work Management Productivity Initiative
Word version of this document
On
March 2, 2004 members of the Work Management productivity initiative
met at the Savanna River Site. Participants included representatives
from Savanna River Site (SRS), Oak Ridge, Fluor Hanford, Los Alamos,
and CH2MHILL Hanford along with the contracted services of Perot
Systems Government Services. The agenda for the meeting is attached.
The purpose of the workshop was to agree on
work management concepts, definitions, best practices, lessons
learned, and current challenges along with a method of communication
to be used by DOE complex members in improving our productivity
while maintaining safety and quality using the work management
process.
We agreed on the following goal and objective
for the Work Management productivity initiative:
Goal – Effectively communicate, using each DOE
contractors information (challenges, lessons learned, best
practices) to improve work management productivity.
Objective – Develop a Web site that houses
agreed upon work management concepts, definitions, best practices,
lessons learned, and current challenges to be used as a tool to
assist DOE complex members in improving their productivity while
maintaining safety and quality using the work management process.
The team started with a presentation of a
general overview of each of the contractor’s facilities and a brief
view of the organizational layout of the management team in place to
operate the facility.
We clarified key definitions to ensure that the
participants would all understand them and how we meant them to be
used in our communications.
We reviewed Institute of Nuclear Power
Operators (INPO) documents INPO 928, “Work Management Excellence”
elements of work management and each of the participants provided
input on the make up of the element for inclusion in the draft of
each of the element.
We identified challenges and best practices
that we felt were pertinent in each of the elements of work
management and a format for submittal of challenges and best
practices to the Work Management section of the EFCOG website.
We established a path forward and schedule
fragnets for completing a DOE Contractor Work Management Excellence
Guidance document, challenges, and best practices for distribution
on the EFCOG website.
We also identified several activities that are
needed in parallel with the development of the documents in order to
better utilize the EFCOG website.
Assignments overview by
Facility
CH2MHILL Hanford
Tony Jennings, Randy Cook
Element:
|
Draft of Work Planning Element |
Complete |
3/29/2004 |
Global Document:
|
Other definitions in Global
Document |
Complete |
4/26/2004 |
|
References in Global Document |
Complete |
4/26/2004 |
|
Discussion of Website in Global
Document |
Complete |
4/26/2004 |
|
Format Global Document |
Complete |
4/26/2004 |
|
Incorporate Key Definitions into
Global Document |
Complete |
4/26/2004 |
|
Draft of Global Document |
Complete |
5/3/2004 |
Challenges:
|
Element/Title |
Due Date |
|
Draft of Challenge for select
work - Overcoming the practice of wanting everything now |
Complete |
3/22/2004 |
|
Draft of challenge for Plan Work
- Optimization of work package approval process |
Complete |
3/22/2004 |
|
Draft of challenge for Plan Work
- Proper use of Standard Hazard Analysis tools |
Complete |
3/22/2004 |
|
Draft of challenge for Plan Work
- Getting all groups on board with electronic routing and
approval process |
Complete |
3/22/2004 |
|
Draft of challenge for Execute
Work - Mechanic “white space” |
Complete |
3/22/2004 |
|
Draft of challenge for Execute
Work - Define field work supervisor duties |
Complete |
3/22/2004 |
|
Draft of challenge for Close
Work - Engineering acceptance of modification work |
Complete |
3/22/2004 |
|
Draft of challenge for Critique
Work - Identification of Performance Indicators for different
levels of management |
Complete |
3/22/2004 |
|
Draft of challenge for Critique
Work - Consistent input of information |
Complete |
3/22/2004 |
Best Practices:
|
Draft Best practice -
Comprehensive, low threshold, electronic work initiation/problem
identification system in Identify work element |
Complete |
5/7/2004 |
|
Draft of Best Practice for Plan
Work - Senior Review Committee for complex/high risk work
packages |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Scheduling - Senior Management involvement (Frequent and
Regular) - Critical Path Meetings |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Scheduling - Resource load schedules, Assign support resources
to schedule (Radcon, QA, Operations) |
Complete |
5/7/2004 |
Website development:
|
Web Site - Establish Contact
point for Best Practices |
Complete |
4/19/2004 |
|
Web Site - Establish Topical
Area for WM in Best Practices and Operating Experiences |
Complete |
5/3/2004 |
|
Web Site - Make sure we are
established as a recognized work group/contact |
Complete |
5/3/2004 |
Savanna River Site
Tim Flake, Rick Flemming
Element:
|
Draft of Scheduling Element |
Complete |
3/29/2004 |
|
Draft Critique Work element |
Complete |
3/29/2004 |
Global Document:
|
Provide Global Challenges Write
up |
Complete |
3/22/2004 |
|
Inconsistent Execution of Work Management Program |
Complete |
3/22/2004 |
|
Ownership
of Work Management Program |
Complete |
3/22/2004 |
|
Lack of
Automation Integration |
Complete |
3/22/2004 |
|
Training on
elements of Work Management |
Complete |
3/22/2004 |
|
Quick Fix
|
Complete |
5/7/2004 |
|
Expedited/FIN processes |
Complete |
5/7/2004 |
|
Selection
of work method using the graded approach |
Complete |
5/7/2004 |
Challenges:
|
Element/Title |
|
Due Date |
|
Draft of challenge for
Scheduling element - Proper tools and parts staged/available vs.
Just In Time delivery |
Complete |
3/22/2004 |
|
Draft of challenge for
Scheduling element - Weather |
Complete |
3/22/2004 |
Best Practices:
|
Draft of Best Practice for Plan
Work - Work Management Centers |
Complete |
5/7/2004 |
|
Draft of Best Practice for Plan
Work - Rolling Work Week Process allows adequate planning time
and sets planning priorities |
Complete |
5/7/2004 |
|
Draft of Best Practice for Plan
Work - Work package only contain what’s needed by mechanic in
field |
Complete |
5/7/2004 |
|
Draft of Best Practice for Plan
Work - Electronic routing and approval process
|
Complete |
5/7/2004 |
|
Draft of Best Practice for
Scheduling - Outages |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Scheduling - Metrics to measure success |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Scheduling - Rolling Work Week process |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Execute Work - Delay codes, Recording mechanic down time |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Execute Work - Define responsibilities of Work Window Manager
|
Complete |
5/7/2004 |
|
Draft of Best Practice for
Execute Work - FLM oversees work; WWM resolves schedule issues |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Execute Work - Comprehensive worker feedback (worker involvement
in updating WMS |
Complete |
5/7/2004 |
|
Draft of Best Practice for Close
Work - Electronic operations acceptance and closure process |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Critique Work - Standard work week critiques |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Critique Work - Electronic worker feedback |
Complete |
5/7/2004 |
|
Draft of Best Practice for
Critique Work - Work Management Reporting System |
Complete |
5/7/2004 |
Oak Ridge
Tim Marks
Element:
|
Draft "Execute Work" Element |
Complete |
3/29/2004 |
Challenges:
|
Element/Title |
|
Due Date |
|
Draft of challenge for Identify
Work - Identify clear path for all work to enter the Work
Management Process |
Complete |
3/22/2004 |
|
Draft of challenge for Critique
Work - Integration of software programs |
Complete |
3/22/2004 |
Fluor Hanford
Rich Reddekopp
Element:
|
Draft "Select Work" element |
Complete |
3/29/2004 |
Challenges:
|
Element/Title |
|
Due Date |
|
Draft of Challenge for Identify
work - Consistent documentation of work scopes in the WMS
|
Complete |
3/22/2004 |
|
Draft of Challenge for Identify
work - Ensuring verbal requests get documented in WMS
|
Complete |
3/22/2004 |
|
Draft of Challenge for Identify
work - Clear identification of work scopes |
Complete |
3/22/2004 |
|
Draft of Challenge for Select
work - Refine work description / scope sufficiently to support
adequate screening and validation |
Complete |
3/22/2004 |
|
Draft of challenge for
Scheduling element - Understand what perturbations do to
scheduled work |
Complete |
3/22/2004 |
|
Draft of challenge for Execute
Work - Use of working copies in Rad area |
Complete |
3/22/2004 |
|
Draft of challenge for Close
Work - Operations acceptance of work |
Complete |
3/22/2004 |
|
Draft of challenge for Close
Work - Close packages once work scope is complete |
Complete |
3/22/2004 |
Best Practices:
|
Draft of Best Practice for Plan
Work - Standard Hazard Analysis tools |
Complete |
5/7/2004 |
Los
Alamos
John Tseng
Element:
|
Draft "Close Work" element |
Complete |
3/29/2004 |
Challenges:
|
Element/Title |
|
Due Date |
|
Draft of challenge for Plan Work
- Reducing work package contents to only what’s needed for field
work |
Complete |
3/22/2004 |
Perot Systems Government Services
Steve Krahn
Element:
|
Draft "Identify Work" element |
Complete |
3/15/2004 |
Global Document:
|
Element/Title |
Complete |
Due Date |
|
Introduction for Global Document |
Complete |
4/26/2004 |
|
7 elements in Global Document |
Complete |
4/26/2004 |
|
Correlation of 7 elements to
ISMS core functions |
Complete |
4/26/2004 |
|
