Process Owner Concept

DOESTD107393

design basis information, design requirements, facility configuration, or is used in any manner to make

technical or safety decisions would fall within the scope of the CM program. Like other changes,

software changes need to be identified, evaluated, approved, implemented (with post-implementation

acceptance criteria for verification and validation), and documented prior to use.

Process Owner Concept. Each identified change control process encompasses a group of

subprocesses, activities, and tasks that take an input, add value to it, and provide an output to an

internal or external customer. The process owner is the individual assigned by management to be

responsible for ensuring that the total process is both effective and efficient. As part of this

responsibility, the process owner ensures that CM change control functions are accomplished.

Processes often have a natural owner, the person who produces the final process result, makes the

significant process decisions, or facilitates the process flow. The process owner also needs to have

process knowledge, leadership ability, and the power to act on the process (eg., resources, authority,

influence).

Within the context of the CM program, once valid change control processes are identified, facility

management would assign a process owner for each process. The process owner would lead the

evaluation of existing CM controls to determine their effectiveness and recommend upgrade actions, if

needed. After upgrade is complete, the process owner would continue to ensure that the CM change

control functions are effectively performed. If needed, personnel with CM training and expertise would

be provided to assist the process owner, particularly during process evaluation and improvement.

System Engineer Concept. One of the challenges of change control is to be cognizant of many ongoing

changes--from proposal, through development, to implementation--and to understand the integrated effect of

the various changes. The system engineering concept has been used in the commercial nuclear industry to

provide a technical focal point for each system. The system engineer develops resident technical expertise and

facility knowledge, centralizes resolution of SSC performance problems for more timely and effective response,

and interfaces between the facility operations and maintenance organizations and the design engineering

organization. The systems engineering concept benefits configuration management as well as many other facility

activities including facility status and troubleshooting, operations support, coordination of testing and other system-

related activities, and communication among departments. For the purpose of change control, it is recommended

that DOE contractors, in a manner similar to the commercial industry, institute the systems engineering concept.

The duties, responsibilities, and interfaces of each system engineer need to be clearly defined, documented,

communicated to and understood by supporting facility organizations. System engineer responsibilities should

include these major items: (1) monitoring and tracking the status of the system, especially during changes (e.g.,

physical changes in progress and temporary physical changes); (2) conducting and/or observing equipment

performance monitoring, evaluating the results of performance monitoring and surveillance, trending, important

data, and initiating corrective actions; (3) reviewing and approving post-modification, post-maintenance,

surveillance, and special test procedures and test results; (4) providing assistance to operations and

maintenance, as needed; and, (5) identifying any situation where the design engineering organization should be

consulted for advice or services.

To implement systems engineering, selected facility engineers would be assigned the responsibility of

important systems. These individuals should have an engineering degree or a strong technical background

combined with a knowledge of the assigned system and how it relates to overall facility operation. An

understanding of the policies, procedures, and organizational interfaces is also important. The number of

systems assigned to each engineer should be limited (e.g., two to five) based on system complexity, the

experience of the individual, and time considerations.

I-B-12