19.11.2014 Views

Organizational Development for Knowledge Management at Water ...

Organizational Development for Knowledge Management at Water ...

Organizational Development for Knowledge Management at Water ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• Ensuring the content of process documents is consistent with documents from other divisions,<br />

departments, sections, units, or teams,<br />

• Maintenance and continuous improvement of the QBD Document D<strong>at</strong>abases.<br />

1.2. Division Officers, General Managers, Managers, and Supervisors<br />

• Supporting document<strong>at</strong>ion ef<strong>for</strong>ts and use of the document control system,<br />

• Assuring assignment of Process Owners within their divisions, departments, sections, units, or<br />

teams,<br />

• In<strong>for</strong>ming employees of changes to process documents as appropri<strong>at</strong>e.<br />

1.3. Process Owners<br />

• Documenting the process using approved templ<strong>at</strong>es,<br />

• Understanding the document control system defined by this process,<br />

• Assuring the integrity of the document’s content and changing it when appropri<strong>at</strong>e,<br />

• Seeking the necessary approvals,<br />

• Serving as the point of contact <strong>for</strong> any proposed changes, including researching the impact of<br />

proposed changes,<br />

• Using the Standard Templ<strong>at</strong>e Checklist, Attachment F01-00002, be<strong>for</strong>e submitting a process<br />

document <strong>for</strong> review or approval to assure compliance to this process,<br />

• Determining stakeholders and users of an initial issue or version change and utilizing the<br />

notific<strong>at</strong>ion field as the communic<strong>at</strong>ion method,<br />

• Upd<strong>at</strong>ing Process Tools as necessary.<br />

1.4. Reviewers<br />

• Understanding the document control system defined by this document,<br />

• Evalu<strong>at</strong>ing the content of each document submitted <strong>for</strong> review <strong>for</strong> <strong>for</strong>m<strong>at</strong>, completeness,<br />

accuracy, and impact on other divisions, departments, sections, units, or teams,<br />

• Indic<strong>at</strong>ing when review of the document is complete,<br />

• Sharing opportunities <strong>for</strong> improvements to the Process Owner.<br />

1.5. Approvers<br />

• Understanding the document control system defined by this document,<br />

• Evalu<strong>at</strong>ing the content of each document submitted <strong>for</strong> approval <strong>for</strong> <strong>for</strong>m<strong>at</strong>, completeness,<br />

accuracy, and impact on other divisions, departments, sections, units, or teams,<br />

• Signing approval of the document in a timely manner,<br />

• Understanding th<strong>at</strong>, as an approver, you agree the process is per<strong>for</strong>med as explained in the<br />

document,<br />

• Notifying employees and/or co-workers of an initial issue or version change as appropri<strong>at</strong>e,<br />

• Ensuring th<strong>at</strong> any necessary training or communic<strong>at</strong>ion rel<strong>at</strong>ed to the initial issue or version<br />

change of a document is accomplished.<br />

1.6. All Colorado Springs Utilities Employees<br />

• Per<strong>for</strong>ming work as defined in approved process documents,<br />

• Assuring approved process documents being used m<strong>at</strong>ch the version found in the Approved<br />

Process Documents D<strong>at</strong>abase,<br />

• Regularly reviewing the QBD Activity Report <strong>for</strong> process documents th<strong>at</strong> may impact them in<br />

their roles,<br />

• Referring to the relevant approved process document when a question arises,<br />

©2011 W<strong>at</strong>er Research Found<strong>at</strong>ion. ALL RIGHTS RESERVED.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!