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.

• T15-00002 is used as a high-level introductory parent document <strong>for</strong> Customer Care Policies.<br />

• T18-00002 is used to define an IT system in terms of its architecture, policies, and processes.<br />

If a templ<strong>at</strong>e th<strong>at</strong> meets your needs cannot be found please contact Continuous Improvement (8-4357,<br />

option 4).<br />

Templ<strong>at</strong>es may be modified or added to this process document without processing a version change of the<br />

parent document. The version of the templ<strong>at</strong>e is noted in the footer of each.<br />

1.8.1. Titling Documents<br />

The document title should be a brief description of the document’s purpose or process being<br />

per<strong>for</strong>med. For Title guidelines refer to the Process Owner Manual, I01-00002.<br />

1.8.2. Document Classific<strong>at</strong>ion<br />

When a new document is cre<strong>at</strong>ed it is assigned a unique number. This unique number remains<br />

with the document throughout its life although the process may move to another division,<br />

department, or section.<br />

Other key in<strong>for</strong>m<strong>at</strong>ion regarding the document is recorded in the QBD D<strong>at</strong>abases. This<br />

in<strong>for</strong>m<strong>at</strong>ion is used to differenti<strong>at</strong>e and sort the documents according to Division, Department,<br />

Section, Loc<strong>at</strong>ion, or Function.<br />

The only required field is Division. All other fields are optional with the exception of the 5 digit<br />

unique number. Use Department, Section, Loc<strong>at</strong>ion, and Function codes only if it will assist users<br />

in easily sorting through the d<strong>at</strong>abase to loc<strong>at</strong>e a particular document. Drop down menus are<br />

loaded into the Draft Process Documents D<strong>at</strong>abase to provide a view of available options <strong>for</strong> each<br />

field.<br />

Loc<strong>at</strong>ion codes should be used on a limited basis. Loc<strong>at</strong>ion is used only when the process<br />

document pertains to one physical loc<strong>at</strong>ion. An example is a security plan <strong>for</strong> a specific facility or<br />

site.<br />

Determin<strong>at</strong>ion of document level is based on the definitions in Section 3.0 and made by<br />

Continuous Improvement <strong>at</strong> the time the unique document number is requested based on the<br />

description of the process provided by the Process Owner.<br />

1.8.3. Numbering Attachments<br />

The overall effectiveness of documents can be improved if associ<strong>at</strong>ed <strong>for</strong>ms, charts, graphics, etc.<br />

can be included. Attachments are usually left in their original applic<strong>at</strong>ion, such as Word, Excel or<br />

PowerPoint. They are assigned an <strong>at</strong>tachment design<strong>at</strong>or followed by a sequential number and<br />

then the unique number of the Parent Document. For example, the first <strong>for</strong>m <strong>for</strong> this document is<br />

numbered F01-00002, the second <strong>for</strong>m, F02-00002, etc. The <strong>at</strong>tachment version is design<strong>at</strong>ed by<br />

a month and year placed within parentheses. An example is (01/2003). Both the <strong>at</strong>tachment<br />

number and the version must be indic<strong>at</strong>ed in the <strong>at</strong>tachment’s footer.<br />

If the <strong>at</strong>tachment is more than one page, the page number should also be placed in the footer.<br />

The <strong>at</strong>tachment design<strong>at</strong>ors available are as follows:<br />

A = Agenda (used to provide <strong>for</strong>m<strong>at</strong> <strong>for</strong> meeting agendas)<br />

C = Chart (a flowchart or reference table th<strong>at</strong> does not require in<strong>for</strong>m<strong>at</strong>ion to be entered into it)<br />

D = Drawing (used <strong>for</strong> CAD drawings, schem<strong>at</strong>ics, etc.)<br />

E = Exercise (used <strong>for</strong> training exercises and in-class practice; not scored or measured)<br />

F = Form (used when in<strong>for</strong>m<strong>at</strong>ion of a restricted size is to be filled into pre-design<strong>at</strong>ed fields; can<br />

be filled out on paper or electronically)<br />

G = Graphic (used <strong>for</strong> graphics or pictures, such as examples of completed <strong>for</strong>ms, templ<strong>at</strong>es,<br />

reports, or screen prints)<br />

I = In<strong>for</strong>m<strong>at</strong>ion/Instructions (used <strong>for</strong> instructions, user’s guides, manuals, scripts, etc.)<br />

M = Measurement (used <strong>for</strong> evalu<strong>at</strong>ing or measuring understanding of course m<strong>at</strong>erial of the<br />

participant/student)<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!