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.

version must be collected and destroyed to assure th<strong>at</strong> all employees are per<strong>for</strong>ming work based on the<br />

most recent version of the process document.<br />

1.14. Cre<strong>at</strong>ing Links to QBD Documents<br />

At Colorado Springs Utilities, many processes are dependent on or are referenced in other processes. It<br />

may be helpful to cre<strong>at</strong>e links from the Intranet or within documents th<strong>at</strong> will take the user to another<br />

specific document or Process Tool.<br />

For instructions on cre<strong>at</strong>ing links, refer to <strong>at</strong>tachment I04-00002, Linking to QBD Documents.<br />

1.15. Changing Documents<br />

The initial issue of a document establishes a baseline <strong>for</strong> a process. However, as continuous improvement<br />

opportunities are identified or processes are changed, it is necessary to change documents and/or Process<br />

Tools (Refer to 6.9). The Document Control system utilizes a numeric version system. As documents are<br />

changed they are upd<strong>at</strong>ed from version 01 to 02 to 03, etc. The Process Owner is the focal point <strong>for</strong> all<br />

changes. The basic steps <strong>for</strong> a version change are:<br />

• Process Owner is made aware of process changes or improvement opportunities th<strong>at</strong> lead to<br />

changes in the current approved document.<br />

• Individuals who are recommending changes contact the Process Owner to share their<br />

recommend<strong>at</strong>ions. The changes can be shared verbally, through a marked up hard copy, or<br />

through a redlined soft copy. If not sure who owns the document, check the Master<br />

Document List in the Approved Process Documents D<strong>at</strong>abase.<br />

• If the Process Owner reviews the changes and does not agree with the change<br />

recommend<strong>at</strong>ions, he/she explains to the origin<strong>at</strong>or the reasons why the changes are not<br />

feasible.<br />

• If the Process Owner agrees with the change recommend<strong>at</strong>ions, he/she moves a copy of the<br />

current document version from the Approved Process Documents D<strong>at</strong>abase into the Draft<br />

Process Documents D<strong>at</strong>abase and incorpor<strong>at</strong>es the changes. This is done by opening the<br />

document to be moved and clicking on the “Copy to Draft Db” button <strong>at</strong> the top of the page.<br />

• The Process Owner upd<strong>at</strong>es the document and records each major change in a Document<br />

Change Notice (DCN). A DCN is cre<strong>at</strong>ed by clicking on the “DCN” button <strong>at</strong> the top of the<br />

window and then selecting “Add DCN”. There should be only one DCN <strong>for</strong> each version<br />

change.<br />

• The Process Owner follows the instructions in Sections 6.2 and 6.3 to route the revised<br />

document <strong>for</strong> approval. As st<strong>at</strong>ed be<strong>for</strong>e, the review cycle is optional.<br />

• If the change affects an <strong>at</strong>tachment used to record process outcomes, the Process Owner<br />

making the change decides whether to remove all previous versions from use and replace<br />

them with the new version or deplete current available stock first.<br />

1.15.1. Potential Impact of Changes<br />

The Process Owner may need to contact potentially affected interests in order to determine wh<strong>at</strong><br />

effects the proposed change may have upon other systems or process documents. Some potential<br />

impacts include oper<strong>at</strong>ions, regul<strong>at</strong>ions, contract requirements, cost, m<strong>at</strong>erials, and the customer.<br />

Continuous Improvement can assist in this ef<strong>for</strong>t, especially in evalu<strong>at</strong>ing the impact on other<br />

quality system requirements.<br />

1.15.2. Minor Changes<br />

Minor changes in editorial style, typographical errors, layout, and/or any change th<strong>at</strong> has no<br />

detrimental effect on the quality of the product or service can be accumul<strong>at</strong>ed over time. The<br />

changes should be collected and incorpor<strong>at</strong>ed during the next change or <strong>at</strong> the next scheduled<br />

evalu<strong>at</strong>ion d<strong>at</strong>e. (Refer to 6.10)<br />

1.15.3. Multiple Documents Affected<br />

If a change affects multiple process documents, a change process and document approval is<br />

required <strong>for</strong> each affected process document.<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!